CPL 556-T320-151.07.01 Secured

Common Photonic Layer
Operations and Maintenance -

Overview
Student Guide
Part Number: 556-T320-151.07.01
Issue: 5.0
Information in this courseware is provided

for training. This courseware may not be
reproduced without written permission.
Copyright 2012 Ciena, All Rights Reserved
Publication date: May 2012
1
Publication History
May 2012
Updated with CPL R5 content. Reintroduction of prerequisite web
based Product Overview P101.
October 2010
Updated with the Ciena template
August 2009
Courseware updated and aligns to software release 4.0.
June 2008
Courseware updated and aligns to software release 3.21
Copyright © 2012 Ciena
All rights reserved.
LEGAL NOTICE
This document contains Ciena confidential and proprietary information. It is not to be copied,
disclosed or distributed in any manner, in whole or in part, without Ciena’s express written
authorization. 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.
Warning
For training purposes only. Always refer to the procedures described in the Ciena standard
documentation that are appropriate for the system and software release that you support.
Failure to use the appropriate documentation can result in serious technical difficulties and
damage to your system.
For additional information about Ciena documentation, visit www.ciena.com/support or
contact your local Ciena sales office or account representative.
Ciena, the Ciena logo and the Globemark are trademarks of Ciena. Microsoft, MS, MS-DOS,
Windows, and Windows NT are trademarks of Microsoft Corporation. All other trademarks are
the property of their respective owners.
Visit us at: Ciena.com/training
FOR TRAINING PURPOSES ONLY 2

Course introduction
Overview
Description
Common Photonic Layer (CPL) Operations and Maintenance – Overview
describes the basic applications of this product family, modules,
configurations, other related hardware and an overview of the management
platforms.
Intended audience
Anyone requiring an overview of the Common Photonic Layer (CPL) .
Prerequisites
This course has the following prerequisites:
• Laser safety and fiber handing for Optical Fiber Communication
System (OFCS).
Objectives
After completing this course, you will be able to …
• Identify configurations and applications
• Identify hardware components
• Identify shelf configurations
• List the different access methods including the Craft GUI
• Identify the possible data communications strategies
CIENA CONFIDENTIAL – FOR TRAINING PURPOSES ONLY 3

References
The following documents provide additional information:
NTT840FH CPL Planning Guide release 5.0
323-1951-120 Optical Modeler User Guide
323-1661-221 SLAT and Channel Procedures
323-1661-310 Provisioning and Operating Procedures

Performance Monitoring Description and
323-1661-520
Procedures
Trouble Clearing and Module Replacement

323-1661-543

Contents
• Lesson 1 CPL Introduction 7
• Lesson 2 CPL Configurations and applications 15
• Lesson 3 CPL Hardware 41
• Lesson 4 Signal Flow 101
• Lesson 5 CPL Network Management and Craft Interface 113
• Lesson 6 Data Communications 127
• Lesson 7 Optical Control and Adjacency 147
• Addendum A Ciena Documentation 183
• Addendum B List of terms 191

This page is intentionally left blank
6
7
8
The Common Photonic Layer concept
The Ciena Common Photonic Layer (CPL) is a self-optimizing, agile DWDM transport
platform designed for cost-effective optical networks.
CPL is separate from the service layer in order to provide a set of building blocks
(wavelength filters, amplifiers, and other related equipment) that can be configured to
provide cost-optimized metro, regional and long haul DWDM transport applications.
The service enabling network elements (like the Optical Metro 5200) complement the
photonic layer to deliver the reach and capacity requirements of these various
applications.
As such, the key goal of CPL is to dramatically simplify the transport layer to ensure
that the multiservice switches, DWDM terminals, optical core switches and other
service elements that connect into it can have their services carried end-to-end —
seamlessly and efficiently.
9
The CPL product
Its modular design provides an extremely small footprint and delivers significantly
lower power consumption compared to current technologies.
The platform offers operational simplicity by providing a high level of automation that
facilitates network planning, engineering, configuration and deployment as well as
accelerates the setup of end to end wavelengths.
10
Key benefits of the CPL product
One of the main benefits of the CPL product is obtained with the separation of the
service and optical layers. By separating both of these layers it is now possible to
deploy a single optical (or photonic) layer that can be shared between multiple
service layer equipment. The CPL product currently supports many Ciena service
layer equipment but also has the ability to support non-Ciena equipment.
Other benefits provided by the CPL product:
• Scalability
• Operational simplicity
• Network flexibility
11
Key benefits of the CPL product
Scalability
The CPL is not designed with a traditional backplane architecture. It's modular
design, where low-power individual components are interconnected using an
Ethernet virtual backplane for data communications, allows for an initial system
with a significantly small footprint that scales modularly and provides a pay-as-
you-go like structure that can grow as revenue generating opportunities or
capacity exhaust drive expansion of the network.
Operational simplicity
CPL has been designed from the start with the goal of introducing new levels of
operational simplicity into the market. The platform provides highly automated
functions for the following network deployment activities:
• Initial system turn-up and incremental wavelength additions:
— The embedded Domain Optical Control or DOC software performs a
series of automated processes for equipment provisioning. Combined
with in-skin electronic Variable Optical Attenuators (eVOAs), rapid
initialization and adjustment of system components is achieved for a
complete deploy-and forget process.
• Optical control architecture
— CPL offers a dynamic and continuous system optimization to ensure
optimal performance of the wavelengths transported end-to-end. This
autonomous process alerts the operations center of any degradation
warning signs that cannot be corrected automatically.
Network flexibility
CPL release 2.0 introduced the ROADM (Reconfigurable Optical Add/Drop
Multiplexer) architecture that delivers any wavelength, anywhere, anytime,
without impact to the existing traffic. The ROADM is a CPL functional module that
enables dynamic “on the fly” configuration of individual wavelengths (express or
add/drop).
CPL release 3.0 introduced branching. This allows for more flexible networks and
allows for the removal of channel terminating regenerators at branching sites.
CPL release 3.1 extended it's hardware portfolio and capability by introducing the
CMD44 which is an all passive channel mux/demux and the Distributed Raman
Amplifier (DRA), a counter propagating amplifier that increases the span reach
and improves the signal to noise ratio.
12
Check your learning
1. True or False: CPL is designed to operate strictly in Long Haul Networks.

____________________________________________________________________
2. Which of the following is not a CPL feature.

a. Support of non-Ciena wavelengths
b. Manual topology discovery
c. Automated wavelength activation
d. Remotely Configurable Optical Add-Drop Multiplexer (R-OADM)
13
14
15
16
Wavelength plan
Common Photonic Layer multiplexer/demultiplexer capability is intended to inter
operate with a wide range of different DWDM transmitter/receiver options for both the
edge and core application spaces.
The wavelength plans for the Common Photonic Layer include ITU grid options:
• OSC
• 100 GHz (groups separated by one skipped channel)
• 50 GHz (groups separated by two skipped channels)
Depending on the CMD equipment type used, the skipped channels in between
groups can be added. This action increases the following capacity:
• 100 GHz spacing capacity going from 36 to 44 channels
• 50 GHz spacing capacity going from 72 to 88 channels
When using group based CMDs for Greenfield deployments, Ciena suggests to
start with group 5 followed by 6,7,8,9,4,3,2 and 1.
17
Supported configurations
The Common Photonic Layer supports the following basic site configurations:
• Channel access (Terminal or OADM)
— GMD based terminal and OADM
— Thin based terminal and OADM
— WSS based OADM
• Amplifier
• Dynamic Gain Flattening Filter (DGFF)
— Coarse DGFF
— Fine DGFF
• Branching
— T-Branch
— Y-Branch
18
CPL Terminal site
The channel access configuration represents configurations where channels are
accessible to service layer equipment. One type of channel access configuration is
the terminal site.
At the Terminal site all channels that form the photonic layer are added or dropped at
the service layer.
The building blocks of a single direction Terminal site are:
• One Group Mux/Demux (GMD)
• One to nine Channel Mux/Demux (CMD)
• One SLA/MLA/MLA2/LIM
Note 1: Circuit packs are covered in more detail in another lesson.
Note 2: Dual direction Terminals use two of each of the above components
19
OADM site
In the event that not all channels need to be added and dropped to the service layer
equipment, OADM site are used. At these locations, groups of wavelengths can be
configured to add and drop or to pass-through the site. The pass-through groups are
know as express groups.
The OADM site is comprised of the following elements:
• Two GMDs
• Two to eighteen CMDs
• Two SLAs/MLAs/LIMs (This example shows MLAs)
The GMD provides group-level granularity while the CMDs provide the per channel
add/drop capabilities.
All passthrough groups are fibered via back to back GMDs.
20
Thin based configurations
CPL release 2 introduced new hardware that allowed for a lower-cost version of the
channel access site configurations. The thin based configuration are obtained by
cascading SCMD. This improves on the previous configuration that required both a
Group Mux/Demux (GMD) and a Channel Mux/Demux (CMD).
For Release 2 deployments, up to 4 SCMDs are supported in cascade. The building
blocks of the thin based configurations are:
• Two UOSCs
• Two to eighteen SCMDs
• Two SLAs/MLAs/MLA2s/LIMs (This example shows MLAs)
SCMDs cascading rules
It is recommended that the SCMD be interconnected according to the following
guidelines:
• For the left NE, the SCMDs are optically connected in ascending group number
order (group 1, 2, …9).
• For the right NE, the SCMDs are optically connected in descending group number
order (group 9, 8, …1).
This order is to limit the attenuation it experiences through the SCMD cascade.
Release 1’s CMD4 cannot be used in a T-OADM site as it lacks an upgrade port.
21
WSS based configuration
These configurations allow for remote non-service affecting reconfigurations of
express and add/drop channels.
With a WSS based configuration, the user can provision any wavelength to be
added/dropped or pass-through at anytime.
The building blocks of the WSS based configurations are:
• Two WSSs
• Two UOSCs
• One OPM
• Two to eighteen SCMDs
22
Amplifier node
Amplifier sites are used to amplify the wavelengths in the network. Many variations of
amplifier sites can be used based on the requirements of the network. Dispersion
and Slope Compensation Modules (DSCM) can be used if required to compensate
for chromatic dispersion in the network.
The building blocks of an Amplifier site are:
• One Dual Optical Service Channel (DOSC) used for inter-site communications
• A combination of two LIMs/SLAs/MLAs/MLA2s (this example shows MLAs) used
for line amplification.
• Optional DSCMs modules.
Depending on the recommendations of the Optical Modeler link design tool, an

OPM can also be deployed at a line amplifier site.
23
Interior SLA configuration
Interior SLAs have been supported between the preamplifier and the WSS demux to
provide a loss-less DSCM function. The Line B of the SLA is usually bypassed to
eliminate the insertion loss of this connection.
Pre-Release 3.2, these SLAs have been used in a ‘set and forgot’ mode (no DOC
control).
Release 3.2 included enhancements which allow the interior SLAs to be controlled by
DOC. DOC adjusts the gain of the SLA to meet provisioned peak power targets.
24
DGFF site
The coarse Dynamic Gain Flattening Filter (DGFF) site, shown here is a variant of an
OADM site with all channels pass-through. The coarse DGFF provides a per-group
attenuation profile for control purposes to overcome the accumulation of gain tilt in an
optical link
The DGFF site is comprised of the following elements:
• Two GMDs
• Two MLAs/SLAs/LIMs
This site type provides optimization of the Optical Signal to Noise Ratio (OSNR).
25
Fine DGFF
Much like the coarse Dynamic Gain Flattering Filter (DGFF), the fine DGFF provides
compensation of accumulated gain tilt on the optical fiber.
Because of the WSS per wavelength attenuation profile, the fine DGFF provides gain
tilt compensation on a wavelength level instead of the group level compensation
provided by the coarse DGFF site. This allows for improved link budgets.
The building blocks of the fine DGFF site are:
• Two WSSs
• Two UOSCs
• One OPM
26
Linear spur
The linear spur site is a backbone and remote site where traffic can be dropped off of
the main backbone because the remote site is a short distance from the backbone.
In this example, at the main backbone location, the linear spur is comprised of three
Network Element (NEs):
• Two GMD based NEs are part of the main ring.
• One Thin based NE is part of the linear spur.
27
Y-Branch Site:
The Y-Branch site is a 3-Way branch site involving 3 different domains. The Y-Branch
site consists of 3 WSS modules from 3 different domains. Each WSS can be
connected to (S)CMD for local add/drop.
TID consolidation
As soon as a branched site consists of 2 or more optical domains, TID consolidation
is provisioned. TID consolidation allows multiple shelves at a site to be managed
under the same TID and is required to provision across domain cross connections.
Each shelf shares the same TID, but has a unique shelf number.
28
T-Branch Site:
The T-Branch site is a 3-Way branch site involving 2 different domains. The T-Branch
site contains 3 WSS modules, 2 WSS modules in one domain and the other WSS
module in a different domain. Each WSS can be connected to (S)CMD for local
add/drop.
29
4-Way branching
Release 3.2 extends branching to include 4-way and 5-way branching in addition to
the 3-way branching configurations supported in Release 3.1.
Branching saves unnecessary optical-electrical-optical (OEO) conversion
(regeneration) at nodes where a channel leaves one line and enters another branch.
The 4-way branch site involves 4 different domains. The 4-way branch site consists
of four WSS modules from four different domains. Each WSS can be connected to
(s)CMDs for local add/drop.
30
5-Way branching
The 5-way branch site involves five different domains. The 5-way branch site
consists of five WSS modules from five different domains. Each WSS can be
connected to (s)CMDs for local add/drop.
31
Direction Independent Access (DIA) Site Configuration
Previous ROADM configurations are directionally dependant. A TX/RX pair
connected to a CMD can only be sent out of the site in the direction of the line ports
of the WSS it is connected to. A DIA increases the amount of remote reconfiguration
available.
The DIA allows the user to determine the optical direction of a channel out of a site
via software and not a physical connection. This simplifies the planning of ROADM
sites / network. It allows wavelengths to be remotely re-directed to other direction as
the bandwidth requirements change.
DIA supports directional control of 44 (100GHz eCMD44) or 88 (50GHz CMD44s)

wavelengths. Each optical direction has capacity up to 88 wavelength via
combination of passthrough, DIA add/drop and local add/drop.
The DIA OTS has no OSID provisioned nor has a DOC facility created. The DIA OTS
is controlled by the other domains’ DOC. All outgoing lines are in different domains.
The amplifier in the DIA node has its shutoff mode disabled and is provisioned in a
set and forget mode.
32
Module Interconnections
In the DIA shelf, the main difference is that the LIM is not facing the backbone fibers,
thus not facing a far end LIM. For this, the OSC channel is not connected and not in
use. Another parameter that is affected by this is Automatic Laser Shut Off: ALSO is
disabled.
Shown here is the LIM connected to a BMD2. The BMD2 is required for 50Ghz
deployments. When we use 100Ghz deployment, the LIM is fibered to an eCMD44.
33
Dual DIA with 4 way branch
This configuration allows no local add/drop on line facing WSS modules.
The Dual-DIA in this type of configuration allows the user to:

• Increase the route diversity and the high available links
• Increase the channel count (can use the same wavelength as active in 2
directions)
• Redundancy on the functionality of the DIA equipment
34
Dual DIA with 3 way branch
This configuration allows local add/drop on line facing WSS modules.
The Dual-DIA in this type of configuration allows the user to:

• Increase the route diversity and the high available links
• Increase the channel count and redundancy on the functionality of the DIA
equipment
• Allows to drop specific traffic per domain
35
Engineering rules
DIA is only supported at ROADM sites and must be TID-Consolidated with the line
facing ROADM NEs
A wavelength can either be dropped to a CMD on a backbone WSS or the DIA CMD
at the same site. Once the channel is dropped at a CMD on a backbone WSS it is
blocked by software from dropping at a DIA CMD at the same site
A wavelength can either be added at a CMD on a backbone WSS or the DIA CMD at
the same site. Once the channel is added at a CMD on a backbone WSS it is
blocked by software from being added in the same optical direction at the DIA CMD
at the same site.
DIA does not contain a DOC facility. No OSID is configured for the DIA. All line side
WSS modules the DIA connects to must be in different optical domains. DIA can be
controlled by a UOSC or DOSC which controls another WSS direction.
DRA amplifiers or DSCMs are not supported within the DIA. Maximum number of
DIAs per site is 2.
CMD4, sCMD4, sCMD8, and CMDA are not supported in the DIA configuration and
are blocked by software.
36
CPL/6500 interworking
The 6500 Photonic Layer (PL) platform provides similar features and functionality as
the CPL platform.
The 6500 PL cards reside in a card cage. Common Photonic Layer network elements
are supported in a network comprising 6500 equipment.
For all types of CPL nodes including GMD based network elements to be supported
in interworking with 6500, CPL nodes must be at Release 5.0 and 6500 nodes must
be at Release 9.1.
Interworking CPL line amplifier nodes with 6500 network elements was supported
with CPL Release 4.0 and 6500 nodes Release 6.
Refer to planning guide NTT840FH for a complete list of operational considerations.
37
Consolidated TID
TID consolidation is required for Branching functionality. TID consolidation allows
multiple CPL shelves (up to 5) at a site to be managed under the same TID. All
shelves in a TIDc nodes are interconnected using the ILAN ports.
This reduces the number of TIDs and nodes requiring management in the network.
Each shelf shares the same TID, but has a unique shelf number.
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 network elements.
Starting at CPL release 5 and 6500 release 9.1, mixed TIDc is supported as long as
the primary shelf is a 6500. The primary shelf must be a 6500 shelf equipped with an
SP2 Shelf Processor (NTK555CA or NTK555FA).
Refer to planning guide NTT840FH for a complete list of operational considerations.
38
Check your learning
1. Which of the following modules is not part of an amplifier site?

a.GMD
b.MLA
c. DOSC
d.OPM
2. True or False: A terminal site can be GMD or WSS based?

____________________________________________________________________
3. An R-OADM site is comprised of Uni-OSC, CMDs and amplifiers. What additional two
modules allow the remote configuration of wavelengths?
____________________________________________________________________
4. CPL supports wavelengths at 100 GHz spacing (using CMD4).

5. With the addition of the CMD44 50 GHz Red and Blue Bands, CPL supports:
a) 36 wavelengths
b) 44 wavelengths
c) 72 wavelengths
d) 88 wavelengths
39
40
41
42
CPL Shelf Equipment
The Common Photonic Layer product is based on a backplane-less architecture so
required modules are simply interconnected to provide optimized low-cost solutions.
A power cable harness and Ethernet cable connections from a Breaker Interface
Panel (BIP) provide power and inter-module communications to the various CPL
components.
The Common Photonic Layer is a global platform with a single Network Equipment
Building System/European Telecommunications Standards Institute (NEBS/ETSI)
footprint.
43
General Equipping Rules
Each shelf has one virtual shelf controller (VSC). A VSC can be either a GMD, a
DOSC or a UOSC.
The network element type is automatically determined by the type of VSC.
The VSC is always located in virtual slot 4.
For sites containing CMD4s, SCMD4s or SCMD8s, one CMD of each group
(regardless of type) is allowed in each shelf. For example, a CMD4 group 4 and a
sCMD8 group 5 can be provisioned on the same shelf, but two CMD4 group 4s
cannot.
44
Equipment slots and modules
In initial release 1, the following hardware components were available:
• Group Mux/Demux (GMD)
• Dual Optical Service Channel (DOSC)
• Channel Mux/Demux (CMD)
• Amplifier/ Line modules
• Fiber Manager Tray (FMT)
• Dispersion Slope Compensation Module (DSCM)
• Breaker interface panels (BIP)
45
WSS based ROADM; slots/modules
The following hardware components are available:
• Uni-Optical Service Channel (UOSC)
• Serial Channel Mux/Demux (SCMD4 and SCMD8)
• Mid-Stage Line Amplifier 2 (MLA2)
• Wavelength Selective Switch (WSS)
• Optical Power Monitor (OPM)
• Universal Breaker interface panels (BIP)
• Multi-Slot Carrier (MSC)
• 44 Channel Mux/Demux (CMD44)
• Distributed Raman Amplifier (DRA)
46
Virtual ports
Some circuit packs are not monitored or detected. These circuit packs are
manually provisioned in virtual ports.
An example of these modules are:

• DSCM
• BMD2
• CMD44/eCMD44.
Previous releases of CPL would only have Slot 14-15 as virtual slots. With the
introduction of many new circuit packs and different configurations that do not
need to be monitored or controlled by DOC, the number of virtual ports has
increased with the range from 14 to 30 inclusively.
DOSC at TOADM and ROADM

Release 4.0 introduces the support for Dual OSC (DOSC) at ROADM and TOADM
sites to replace two Uni-OSCs (UOSCs).
47
Group Mux/Demux (GMD)
The Group Mux/Demux (GMD) module provides the group multiplexing/
demultiplexing stage and interface to the amplified line system. It also provides an
out-of-band Optical Service Channel (OSC).
The GMD is a Virtual Shelf Controller (VSC) and provides:
• A communication infrastructure that enables the Common Photonic Layer node to
interface with other nodes.
• Communications of the elements within the node and the outside world.
• Storage of the information pertaining to network management, configuration,
communication, optimization and control.
• Standard alarms and telemetry support.
• Brownout robustness: If the GMD loses power, the eVOAs on the mux ports
revert to 0 dB of attenuation allowing all signals to pass through the GMD.
Note: The VSC role can be compared to a shelf processor.
48
GMD block diagram
Power monitoring and adjustment:
• Total optical power monitoring at the common port on the multiplexer side.
• Total optical power monitoring at the common port on the demultiplexer
Side.
• Per group optical power adjustment through an eVOA on the multiplexer side.
GMD Type 1 was designed to be used with the Wavelength Blocker (WB)
technology for ROADM sites. The wavelength blocker would have been
connected in between back to back GMD’s using their upgrade ports. Since
Wavelength Selective Switch (WSS) technology was preferred over the WB,
most deployments use type 2 GMDs.
49
The external interfaces allow access to the following OAM&P features:
• Network element management and communications subnet
• Total optical power monitoring at all common ports
• Optical power control
• Transaction Language 1 (TL1) Craft interface
• TL1 based remote network management interface
• TL1 gateway / northbound simple network management protocol (SNMP)
• Wayside access for customer usage
• Node consolidation/subnet
• Alarm and fault correlation
• Software load management
• Browser graphical user interface (GUI) Craft support
• Network and local optimization control
• Private dynamic host configuration protocol (DHCP) address pool for
subtending circuit pack presence detection
• 10Base-T, RS-232, modem access
• Visual alarm indicators
50
Dual Optical Service Channel (DOSC) module
The Dual Optical Service Channel (DOSC) module provides the VSC and OSC
functionality for those sites at which a GMD will not be deployed (that is, at Line
Amplifier sites).
The DOSC provides the following functional elements of the Common Photonic
Layer architecture:
• Two OSC facilities.
• Optical generation and termination of each OSC facility.
• TL1 craft interface.
• TL1 based remote network management interface.
• Wayside access for customer usage.
• Private Ethernet communications interfaces in support of subtended Amplifier
modules.
51
The external interfaces allow access to the following OAM&P features:
• Network element management and communications subnet
• Total optical power monitoring at all common ports
• Optical power control
• TL1 Craft interface
• TL1 based remote network management interface
• TL1 gateway / northbound SNMP
• Node consolidation/subnet
• Alarm and fault correlation
• Software load management
• Browser GUI Craft support
• Network and local optimization control
• Private DHCP address pool for subtending circuit pack presence detection
• 10Base-T, RS-232, modem access
52
Uni-OSC (UOSC)
Introduced in CPL release 2.0, the UOSC is a depopulated GMD used for ROADM
and TOADM applications. It works in conjunction with the Optical Power Monitor
(OPM) for better channel power/noise estimations.
It has a built-in 155 Mb/s OSC and provides all the Virtual Shelf Controler (VSC)
functions such as:
• NE Mgmt (TL1 Gateway / Bi-directional SNMP)
• DCN / local craft access
• Alarm and Fault correlation
• Load management
• Optical generation & termination of single OSC facility
• Private DHCP address pool, communications connections for subtending module
presence detection
• 10BaseT, RS232, modem access
53
Similar to the GMD, the UOSC provides a DB-25 connector for NE-level alarm and
telemetry termination in support of Bay-level connections and alarming.
The UOSC provides alarm connections via the DB-25 connector for the following:
• Normally Open / Normally Closed / Common relay contacts used to aggregate
the following functionality:
• Critical, Major and Minor Visible alarms (LEDs): 9 pins
• Critical, Major and Minor Audible Alarms: 9 pins
• Remote ACO Relay inputs
• Parallel Telemetry inputs (2)
• Parallel Telemetry output (1)
The UOSC software must allow the provision of these pins such that they activate
the appropriate alarm both locally at the site and via the EMS.
54
Wavelength Selective Switch (WSS)
The WSS is the building block of the ROADM site. It provides per-wavelength
switching (5 switch ports ). For example, a pass-through wavelength can be
converted to an add/drop wavelength.
Under the guidance of the Domain Optical Controller (DOC), the WSS Middle Optical
Controller (MOC) maintains a per-channel loss profile. The MOC collects data from
the amplifiers upstream and downstream of it in order to contribute to the system
optimization on a per-channel basis.
The WSS creates one Channel Control facility (CHC) per wavelength that provides
for a per wavelength attenuation profile as well as switch and blocking states. .
There are currently two models of WSS modules:
• Introduced in Release 2.0, a 88 channels, 50 GHz WS. (shown above)
• Introduced in Release 3.0 as a lower-cost version for 100GHz applications which
allows up to 44 channels.
55
WSS ports recommendations
Since any of the switch ports can add/drop or pass-through any groups and any
wavelengths provisioned by the user, the following planning guidelines help provide
consistency throughout multiple site:
• Switch ports 1 and 2: express wavelengths or branching (note that any 5 ports
can be used for branching)
If using CMD groups:

• Switch port 3 = groups 7, 4 and 1
Each channel control facility has key editable parameters such as:
• Blocking state (opaque or not)
• Switch (path) selector
• Target Loss for the eVOA
56
WSS engineering rules
The following rules apply to the WSS deployments:
• One WSS module required per node direction ROADM:
• WSS should occupy logical Slot 3 for ROADM node and DGFF node
• Add/Drop of SCMD groups is possible on any port (although it is recommended to
follow previously stated guidelines)
• Cascade order can be pre-provisioned
• Mixed SCMD4/SCMD8/CMD44 topology supported
• CMD4 can be connected to WSS port. Should be positioned as last CMD in a
cascade (because it lacks upgrade port)
57
Common Photonic Layer amplifier/ Line Interface Modules (LIM)
The CPL Amplifier modules are low-noise, high input power modules with fast
transient control, integrated eVOAs, and remote software-provisionable gain control
that delivers enhanced reach capabilities to ensure each wavelength is amplified
equally. One amplifier or line interface module per direction is always required to
interface with the backbone fibers. It is also in these modules that the OSC signal is
multiplexed and demultiplexed from the DWDM signals.
The OAM&P features of the Amplifier are:
• Local optical control (LOC)
• Optical power monitoring
• Power control modes (peak/total/tilt)
• Automatic Line Shut Off (ALSO)/Automatic Power Reduction (APR) software
mechanisms
58
Amplifier / Line interface modules variants
The CPL architecture includes two different amplifier modules and one line interface
module:
• The Line Interface Module (LIM) is used for point-to-point and unamplified edge
applications
• The Single Line Amplifier (SLA) is a single (pre-amplifier) erbium-doped fiber
amplifier (EDFA), is primarily used for edge applications.
• The Mid-stage Line Amplifier (MLA/MLA2) is a dual (pre-amplifier/booster) EDFA,
is used for both edge and core applications. Introduced in CPL release 2.0, the
MLA2 provides a higher pre-amplifier output than the MLA.
• The Mid-stage Line Amplifier 3 (MLA3), which is a dual (pre-amplifier/booster)
EDFA, is used for both edge and core applications. The MLA3 provides support
for a 96-channel 50 GHz grid (88 supported by software) and supports higher
total output power than the MLA2 (maximizes reach for 88 x 100G links).
59
LIM variants power specifications
This table summarizes the optical specifications of the different line interfaces
modules.
60
The port descriptions shown here use the Mid-stage Line Amplifier (MLA) as an
example.
61
Channel Mux/Demux Amplifier (CMDA)
The Channel Mux/Demux Amplifier (CMDA) is a hardware module that provides

amplification in the demux path and multiplexes/demultiplexes signals to/from the
CMD44 (50 GHz and 100 GHz) modules to support 88 channels.
Having the amplifier and the CMD44 as separate circuit packs reduces cost for
applications that don’t require amplifiers. This allows the CMD44 to be completely
passive
The CMDA connects to the WSS to boost output power to the passive CMD44.
62
Channel Mux/Demux Amplifier (CMDA)
The Channel Mux/Demux Amplifier (CMDA) module contains:

• A single erbium-doped fiber amplifier (EDFA) that provides high input power to 50
GHz spaced channels in the demultiplexer path
• Filters for mux and demux of the 50 GHz Blue and Red channels
The OAM&P features of the Amplifier are:
• Local optical control (LOC)
• Optical power monitoring
• Power control modes (peak/total/gain/tilt)
• Automatic line shutoff (ALSO)/automatic power reduction (APR) software
mechanisms
The CMDA:
• Connects to the WSS to boost output power to the passive CMD44
• Can be connected to any WSS port
• Is similar to the sCMD8 demux amplifier
63
Distributed Raman Amplifier (DRA)
The Distributed Raman Amplification (DRA) module, provides a counter propagating
Raman amplifier solution that can minimize the impact of long loss spans in multi-
span applications. DRA extends span reach up to 33 dB and reduces network
regeneration, when it is deployed on spans which are impacting the overall system
reach and forcing regeneration points.
Network topology, traffic patterns, expected network growth and typical reach
requirements determine if DRA has a value in your network and identifies the specific
links that are candidates for DRA.
The DRA has hardware ready monitoring points for signal power, OSC power,
Raman pump power and Raman reflected pump power.
64
Raman concept
DRA provides gain across the entire C-band spectrum and has the ability to flatten
and or adjust the gain profile across the entire spectrum. This module is capable of 8
to 12 dB Raman gain depending on fiber type. DRA also provides limited gain on the
OSC channel.
Raman pumps in the DRA module inject power into the fiber which interacts with the
fiber to produce gain on the traffic carrying signal. The optical gain occurs in the
transmission fiber and is distributed along the transmission line.
Distributed Raman amplification is compatible with all fiber types and gain can be
achieved at any wavelength depending on the availability of the pump. The DRA
module has the following 4 pumps:
• Pump 1 wavelength 1 1424.5 nm
65
CMD4
The 4 Channel Mux/Demux (CMD4) module provides the channel
multiplexing/demultiplexing stage in the two-stage Common Photonic Layer
multiplexing scheme and interfaces to the terminal equipment. The CMD4 supports
four DWDM channels in the 100 GHz-spaced ITU grid. Nine different CMD4 modules
are required to cover the entire C-band for a total of 36 wavelengths. The CMD4
provide the following OAM&P features:
• Local optical control (LOC) support.
• Serial port debug interface.
• Private communications interfaces in support of subtending modules that connect
to the GMD module.
• Visual alarm indicators.
• Ingress eVOAs for wavelength optimization support.
• Brownout robustness: If the CMD4 loses power, the eVOAs on the multiplexer
ports and demultiplexer port revert to 40 dB of attenuation.
66
CMD block diagram
Power monitoring and adjustment:
• Total optical power monitoring at the common port on the multiplexer side.
• Total optical power monitoring at the common port on the demultiplexer side.
• Total optical power adjustment through an eVOA on the demultiplexer side.
• Per channel optical power adjustment through an eVOA on the demultiplexer
side.
67
Serial Channel Mux/Demux 4 (SCMD4)
The SCMD4 is based on the release 1 group filters and has an optical upgrade port
used for cascading. It is targeted for OADM/TOADM/ROADM applications.
It provides 4 channels into 1 group muxing.
Engineering rules
• SCMD4 cascaded order from a WSS port must be provisioned by user
• Max of 4 cascaded groups on amp (TOADM) or WSS (ROADM) ports in R2
• Located in slots 5 to 13 of CPL NE
Internal VOAs & Taps

• Mux inputs have channel-level taps, and ingress eVOA to allow for leveling
launch power
• Demux has group-level eVOA to ensure gain spectrum as flat as possible
68
69
SCMD8 - Serial Channel Mux/Demux 8
The SCMD8 provides 8 channels to 1 group muxing/demuxing at 50 Ghz spacing.

The mux side provides per channel attenuation through eVOA. The Demux side
provides an high output power through an EDFA to the receive ends.
Engineering rules:
• SCMD8s cascaded order from a WSS port must be provisioned by user
• Can be cascaded in any order to allow multiple groups to be added or dropped at
a site
• Maximum of 4 cascaded groups on WSS (ROADM) ports in R2
• Located in slots 5 to 13 of CPL NE
70
71
The external interfaces on the CMD are:
• 1 x RS-232 Craft Access (through an RJ-45/DB-9 adaptor)
• 1 x 10base-T IP over Ethernet (RJ-45) Private Access
• Dual LC Connectors for all optical interfaces
72
44 Channel Mux/Demux 100 GHz C-Band (CMD44)
Common Photonic Layer Release 3.1 introduced the 44 Channel Mux/Demux
(CMD44) module which provides low cost 100 GHz Mux/Demux for ROADMs, WSS-
based terminals, and point-to- point TOADM terminals.
The CMD44 provides a cost-efficient ROADM 100 Ghz branching evolution.
Optical features
The CMD44 uses the existing Common Photonic Layer 100 GHz ITU grid 36
wavelength plan, plus an additional eight skip channels between the nine Common
Photonic Layer wavelength groups for a total of 44 wavelengths.
The CMD44 has no VOAs, optimization is carried out through the WSS. OPTMON is
the only PM type supported on the CMD44. Optical monitoring occurs with an OPM
and although OPTMON facilities are associated with each of the channel input ports,
its value is scaled appropriately. The CMD44 module does not supply OPTMON
facility related information to the WSS or UOSC, instead the information is generated
by the optical monitoring ability of the OPM component on the WSS circuit pack and
then correlated back through the adjacency software to the correct port on the
CMD44. In the case of a point-to-point TOADM terminal with a CDM44, there is no
OPTMON support.
73
44 Channel Mux/Demux 100 GHz C-Band (CMD44) (cont’d)
Power and provisioning
The CMD44 is a passive module, and therefore does not require power. Since the
CMD44 is passive, it is not detected or auto-provisioned by the Common Photonic
Layer shelf. To add this equipment to the shelf inventory, it must be manually
provisioned. Provisioning of the CMD44 module is supported in slots 14 to 30. As
with the CMD4, SCMD4 and SCMD8 modules, the CMD44 facilities are auto-
provisioned upon the creation of the CMD44 equipment.
CMD44 facilities include:
• Tx and Rx adjacencies against the Channel In/Out ports
• WSS adjacencies against the Common In/Out ports
• OPTMON facilities associated with the channel In ports
74
CMD44 100GHz with demux amplifier
This deployment applies to Terminals and OADM sites.

The whole C band is designated 100GHz.
75
CMD44 100GHz without demux amplifier
The CMD44 100 GHz is connected directly to WSS. If CMD44 100 GHz deployed,
whole C-band is designated 100 GHz.
76
CMD44 Skip Channels
The following 16 ‘skip channels’ are available on the CMD44 50GHz:
• Also available on the CMD44 100 GHz
— 1533.47 nm, 1537.40 nm, 1541.35 nm, 1545.32 nm, 1549.32 nm, 1553.33
nm, 1557.36 nm, 1561.42 nm
• New in CPL release 3.2
— 1533.86 nm, 1537.79 nm, 1541.75 nm, 1545.72 nm, 1549.72 nm, 1553.73
nm, 1557.77 nm, 1561.83 nm
Note: These channels would be lost through a TOADM, GOADM, or group based
DGFF node.
• The SW in Rel3.2 will not prevent customers from deploying channels that may
be lost at these nodes (in line with behavior in Release 3.1)
77
44 Channel Mux/Demux 100 GHz C-Band (CMD44) (cont’d)
CMD44 supported deployment
The CMD44 is deployed at a WSS-based ROADMs (100GHz wavelength
branching) or WSS-based terminals where the CMD44 connected to one of the
five switch ports on either the WSS 50 GHz or WSS 100 GHz module. SCMD4
modules and CMD44 modules can be connected on the same WSS module as
long as they are connected on different switch ports. Cascading CMD44 and
SCMD4 modules from each other is not supported.
(S)CMD4 based TOADMs can co-exist in the same network as CMD44s,
however the skip channels are not supported to pass-through a (S)CMD4
TOADM.
CMD44 modules can be used at a point-to-point TOADM terminal site (single

amplified span), however there is no OPTMON, DOC or topology support.
The CMD44 modules cannot:
• Be used in a ROADM 3-way Y branch using CMDs (or spurs)
• Be used at GMD based OADM sites
• Interwork with SCMD8 modules
78
44 Channel Mux/Demux 50 GHz (CMD44)
CPL release 3.2 supports the CMD44 C-Band 50 GHz modules, which use the
existing Common Photonic Layer 50 GHz ITU grid 72 wavelength plan, plus an
additional 16 skip channels between the nine Common Photonic Layer wavelength
groups for a total of 88 wavelengths (44 per module). When both CMD44 C-Band 50
GHz Blue and CMD44 C-Band 50 GHz Red are deployed, a total of 88 wavelengths
are available.
The channels on the CMD44 module have 100% add/drop capability, allowing one to
44 channels to be added, dropped, and or passed-thru for each module.
The CMD44 has no VOAs, optimization is carried out through the WSS and CMDA (if
deployed). OPTMON is the only facility type that PMs are supported on the CMD44.
Optical monitoring occurs with an OPM and although OPTMON facilities are
associated with each of the channel input ports, its value is scaled appropriately.
The CMD44 module does not supply OPTMON facility related information to the
GMD or UOSC. In Common Photonic Layer, the OPM module provides the optical
monitoring. In the case of a point-to-point TOADM terminal with a CDM44, there is no
OPTMON support.
79
Blue 44 Channel Mux/Demux 50 GHz
The Blue CMD44 50GHz (NTT862BA) covers wavelengths ranging from 1530.33nm
to 1547.32nm (channels 1 to 44).
The Red CMD44 50GHz (NTT862BB) covers wavelengths ranging from 1547.72nm
to 1565.09nm (channels 45 to 88).
80
CMD44 50GHz without demux amplifier
This deployment applies to Terminals and OADM sites.
The CMD44 (50 or 100GHz) can be connected to any WSS port(s). Typically, ports 5
& 4 would be used to reserve the lower numbered ports for branching.
The following configurations are supported:

• Red and Blue CMD44 50GHz
• Only Red CMD44 50GHz
• Only Blue CMD44 50GHz
81
CMD44 50GHz with demux amplifier
This deployment only uses one WSS port and allows for additional branching
82
Overview
Introduced at CPL R4, the PEC is NTT862FAE5.
The eCMD44 100GHz has all the same features and implementation rules as a
CMD44 100Ghz that was introduced in R3.1 except for an embedded isolator feature
which is needed for the DIA configuration.
The isolator is used to prevent the MLA in the DIA configuration to go into APR if the
Tx/Rx are connected in reverse. Therefore traffic of all other channels will not be
affected.
The insertion loss of the isolator is 0.4dB therefore we are keeping the same values
of the regular cmd44 100GHz.
The insertion loss of the mux/demux component is 4 to 6.4 dbs
83
Overview
In a DIA site, the CMD44 is connected to an amplifier as opposed to a WSS in a
ROADM site.
The use of the isolator is to prevent the amplifier to go in APR mode (Automatic
Power Reduction) if Tx fibers are wrongly connected to a Rx port. APR goes into
action when the amplifier sees power reflected back to itself. This would happen in
the following scenario.
Let’s pretend that we already have four existing channels dropped as indicated by
the blue arrows. Let’s also pretend that we want to add four new channels but we
improperly connect the transmit fibers to the receive ports of the CMD44.
Without the isolator, the amplifier would suddenly see power propagating in the
opposite direction of its line out port as indicated by the red arrow. The amplifier may
measure this as reflected power and if it is over the threshold, it will go in APR. APR
would reduce the power and could impact the existing channels in blue. The use of
an isolator prevents the preceding scenario to happen.
84
Enhanced CMD44 50 GHz C-Band (Blue/Red)
The Enhanced 44 Ch Mux/Demux (CMD44) C-Band 50 GHz include a passive 5%
monitor port on the common mux output which allows the output to be monitored via
an optical power monitor (OPM) or external optical spectrum analyzer (OSA).
Two additional LC connectors are available on the faceplate: Port 91 (unlabeled) is
empty and Port 92 (labeled) is connected to the tap.
The Enhanced CMD44 50 GHz C-Band modules are supported in reconfigurable
optical add-drop multiplexer (ROADM) or direction independent access (DIA) optical
transport section (OTS) configurations.
When using an OPM during SLAT and for on-going monitoring, connect the CMD44
monitor ports to an OPM. Each WSS node has its own local OPM (instead of sharing
OPM across two WSSs). Two ports on the OPM (1 and 2) are connected to the
Preamp and Booster of the LIM as normal and the other two ports (3 and 4) are used
for the Enhanced CMD44 50 GHz C-Band modules.
When a new transmitter is plugged in and tuned to the correct wavelength, the power
level can be read from the CHMON / OPTMON PMs. The software automatically
accounts for the tap loss, providing a more accurate power reading than an external
OSA.
85
Overview
This module is introduced at CPL R4.
This unit is used in DIA configuration when deployed at 50GHz spacing. It allows to
connect both standard Red and Blue CMD44 to the DIA amplifier and provides the
full 88 wavelengths capacity.
86
Overview
Introduced at CPL R4, the Optical Module PEC is NTT862DAE5.
Optical Features
• Contains two 50/50 wide-band optical couplers that perform the function of
coupler on the Mux side and splitter on the Demux side
• Contains an isolator on the Common In port (Demux side). It is there to prevent
traffic to be affected incase the Tx/Rx are connected in reverse.
• C-band only: 1528nm-1570nm
• No LOS alarm (no Tap)
• Passive coupler / splitter with ~ 2.7 dB – 3.9 dB loss
Manually provisioned
• Automatic discovery not available in CPL
• Virtually connected to any slot between 14 and 30 which are not already in use
87
Physical design
The BMD2 does not use 1U/2U/Multi-Slot carriers. It fits the PTE2000, 19” or 23”
frames with adaptor brackets.
It is a 1U module:
• 70.0 x 120.0 x 5.25 (mm)
• 11.372 x 17.250 x 1.73 (in)
Stand alone tray and is equipped with LC connectors. It is a passive Device therefore
no power is required. The fibers will go directly into fiber risers and has no intra-
shelf bend limiters. The unit has no connector sliders. This means that there is no
backside fiber cleaning function.
Attention:
The RJ-45 connector is not used in CPL R4.0. Proprietary serial interface for future
use
88
OPM
The OPM provides the ability to monitor and report the per-wavelength optical
powers on the 50 GHz ITU grid across the entire C-band via the inter-
connection of up to two Common Photonic Layer amplifiers within a site.
The OPM is required at ROADM sites and can be shared by two WSS.
For non-WSS sites, the OPM is optional. Its deployment is a function of the
number of spans, channel count, and application. It connects to the amplifier
module's Line A / B out monitoring ports
89
Engineering Rules
• Required at WSS (ROADM) sites
• 1 OPM shared among two facing NEs with WSSs at ROADM site
• For non-WSS sites, OPM optional. Deployment is a function of the number
of spans, channel count, and application
• Connected to amplifier module Line A / B out monitoring ports (local
amplifier and remote amplifier
The connections for OPM and LIM (SLA, MLA, MLA2) are:
• LIM LineB_MON (port 1 of local amplifier) -> OPM Port 1
• LIM LineA_MON (port 2 of local amplifier) -> OPM Port 2
• LIM LineB_MON (port 1 of remote amplifier) -> OPM Port 3
• LIM LineA_MON (port 2 of remote amplifier) -> OPM Port 4
Optical Specifications
• C-Band only
• 4 LC optical ports with taps
• Operational Measurements at 50 GHz
90
Fiber Manager Tray
The FMT is a frame-mountable, 1 unit (1U) high chassis and drawer assembly that
serves to contain either a slack-storage drop-in plate assembly or a DSCM drop-in
plate assembly.
The slack-storage drop-in plate assembly provides 12 flip trays (spools) for up to 6 ft
8 in. (2m) of discrete slack storage for 24 fibers. The slack-storage drop-in plate
assembly secures to the FMT drawer and is a field-replaceable unit.
91
Dispersion Slope Compensation Module (DSCM)
Dispersion Slope Compensation Modules (DSCMs) are used to provide chromatic
dispersion compensation and maximize the performance of the CPL system.
DSCMs Type 1 are used for the compensation of NDSF fiber spans. DSCM Type 1
units are available in 10 km increments up to 140 km in length to compensate for
different amounts of accumulated dispersion.
FM drawer and protects the fiber as the FM drawer is opened and closed.
92
93
94
Multi-Slot Carrier (MSC)
In CPL release 2, new Multi-Slot Carrier (MSC) are available for standard
configurations and will replace individual 1U/2U carriers
• Type 1 - covers base slots for ROADM configuration
• Type 2 – covers base slots for Line Amp configurations
• Type 3 – covers base slots for OADM and TOADM configurations
Multi-slot carrier will allow shipment of modules in place, which will save time during
installation phase of deployment. These MSCs include fiber management trays.
Standard cable harness orderable for above configuration in which 1 NE less than
22U of rack unit space. If non-standard configuration (e.g. 3rd party BIP/FIP used),
and 22U rack space exceeded, then custom cable harness must be ordered.
Associated upgrade kits used to install MSC in non-PTE 2000 frame
• NTT899AM (For Type 1 MSC)
• NTT899AN (For Type 2 MSC)
• NTT899AP (For Type 3 MSC)
95
Check your learning
1. Which of the following devices/modules combines channels into groups?
a. DOSC
b. LIM
c. CMD
d. GMD
2. Which devices provide the laser for the OSC channel?
a. Single Line Amplifier (SLA) and Mid-stage Line Amplifier (MLA)
b. Channel Mux/Demux (CMD)
c. Breaker Interface Panel (BIP)
d. Group Mux/Demux (GMD)
3. A Virtual Shelf Controller is mandatory for each site type. Select all modules that provide
this functionality.
a. Single Line Amplifier (SLA) and Mid-stage Line Amplifier (MLA)
b. Channel Mux/Demux (CMD) and Mid-stage Line Amplifier (MLA)
c. Breaker Interface Panel (BIP) and Channel Mux/Demux (CMD)
d. Group Mux/Demux (GMD), Dual OSC (DOSC) and Uni-OSC (UOSC)
4. True or False: Should the GMD lose all battery power, all the ingress eVOAs will be set
to 40 dB attenuation.
a. True
b. False
5. True or False: LIM, SLA, MLA and MLA2 are all Line interface modules/amplifiers.
a. True
b. False
6. Which of the following modules provide amplification for both directions?
a. Single Line Amplifier (SLA)
b. Mid-stage Line Amplifier 2 (MLA2)
c. Line Interface Module (LIM)
d. Dual OSC (DOSC)
96
Check your learning (cont’d)
7. Which of the following modules provides counter propagating amplification?
a. Distributed Raman Amplifier (DRA)
b. Mid-stage Line Amplifier 2 (MLA2)
c. Line Interface Module (LIM)
d. Single Line Amplifier (SLA)
8. The CMDA circuit pack is used to amplify the signal that is going to be:
a) Multiplexed or demultiplexed by the CMD44
b) Multiplexed by the CMD44
c) Demultiplexed by the CMD44
9. The CMD44 50GHz cannot be used with sCMDs.
a) True
b) False
10. There is no option to increase the capacity of an existing CMD44 100 GHz.
a) True
b) False
97
98
99
100
101
102
Signal flow legend
This section contains diagrams of the signal flow within typical CPL site types. The
following site types will be covered:
• GMD based shelf
• Amplifier site
• ROADM (WSS based)
Shown above are commonly used pictograms and what they represent.
103
GMD based Terminal site signal flow - Transmit direction
A: From subtending equipment to CMD
• The signal is received from the subtending network element. It is from a 100GHz
source (for a SCMD4 or CMD4) or a 50 GHz source (for a SCMD8). Per channel
power levels are adjusted through eVOAs. Performance monitoring is evaluated
to record the optical level of that individual signal.
B: CMD MUX
• The signal is combined with the other existing wavelengths present to create a
group. There is a maximum of 4 wavelengths for a SCMD4/CMD4 and 8
wavelengths for a SCMD8.
C: CMD common out and upgrade ports
• Using a splitter/combiner, this newly created group can be combined with any
other signal present in port 11 (upgrade in port) (should another SCMD be
connected to this port). Note that this application is not valid for a GMD based site
as this SCMD cascade is only allowed in a WSS based node or in a Thin OADM
(TOADM) site.
D: From CMD to GMD
• The port 2 (Common OUT) port of the SCMD (or CMD) is then connected to the
"Group in" port (ports 1 to 17 odds only), on the GMD. The GMD has 9 "Group in"
ports, one for each of the groups. Each group (consisting of 4 or 8 wavelengths)
are individually conditioned by eVOAs. Group performance monitoring is
evaluated at this point.
104
GMD based Terminal site signal flow - Transmit direction
E: GMD MUX and OSC
• All groups are combined into an optical transport signal. Up to 9 groups can
propagate on a CPL network (72 wavelengths at 50 GHz spacing, 36 at 100GHz
spacing). Performance monitoring is evaluated at the aggregated level. As the
Virtual Shelf Controller (VSC), the GMD generates the 1510nm Optical Services
Channel (OSC).
F: From GMD to LIMs (or MLA, MLA2, SLA)
• The optical transport signal and the OSC are transmitted to the Line Interface
Module (LIM) via separate fibers. Please note that we use LIM as a generic term,
since we could also use an MLA, MLA2 or SLA.
G: Amplification and power measurements
• The optical signal is amplified by the "B" booster EDFA (except for SLA or LIM
which are not equipped with a "B" booster). Performance monitoring taps provide
before and after amplification power readings for the optical signal as well as an
optical return loss value for the amplifier (if equipped).
H: Common output to LIM
• The amplified optical signal and OSC are combined before transmission on the
backbone fibers.
105
GMD based Terminal site signal flow - Receive direction
A: Common input of the LIM
• The line signal is received by the Line Interface Module. The OSC signal is
separated from the traffic wavelengths.
B: Amplification
• If the module is equipped with a pre-amplifier "A" EDFA (LIM are not equipped
with pre-amplifiers) the DWDM signal is amplified. Performance monitoring taps
provide before and after amplification power readings as well as an optical return
loss value for the amplifier (if equipped).
C: LIM to GMD
• The 1510 nm OSC signal is transmitted to the GMD for processing. On a
separate fiber, the optical transport signal is sent to the GMD port 22 (Common in
port).
D: GMD Demux
• On the GMD, the aggregated signal (comprised of a maximum of 9 groups of 4 or
8 wavelengths) is monitored through a tap at the input of the demultiplexer stage.
The signal is then demultiplexed into 9 groups.
106
GMD based Terminal site signal flow - Receive direction
E: GMD to SCMD
• Each group is then passed on to the appropriate SCMD.
F: SCMD common in and upgrade port
• A splitter separates this SCMD's group from the remaining traffic which is sent to
the port 12 (Upgrade out port). The upgrade port is only used when cascading
SCMDs (WSS based or thin-based sites). An eVOA located before the SCMD (or
CMD) demux allows for attenuation of the entire group. Performance monitoring
provides total group power at this location.
G: SCMD demux
• The group of 4 wavelengths (SCMD4/CMD4) or 8 wavelengths (SCMD8) is
attenuated and monitored before the final group-to-channel demultiplexing stage.
Note that the SCMD8 provides an additional pre-amplification stage through an
EDFA
H: SCMD to subtending equipment
• Individual channels are transmitted to the subtending network element through a
fiber connection.
107
Line amplifier site signal flow
A: Common input of the LIM
• The line signal is received by the Line Interface Module (LIM) or amplifier module. The OSC signal is separated
from the traffic wavelengths.
B: Amplification and performance monitoring
• If the module is equipped with a pre-amplifier "A" EDFA (LIM are not equipped with pre-amplifiers) the DWDM
signal is amplified. Performance monitoring taps provide before and after amplification power readings as well as
an optical return loss value for the amplifier (if equipped).
C: LIM to DSCMs
• The optical signal is transmitted from the interface module’s "Line A out" port. Mid stage components can be
connected to this port; DSCMs, if required will compensate for chromatic dispersion or attenuator pads could be
used to provide a mid-stage loss. The value of these components depends on the link design.
D: LIM to DOSC
• The 1510 nm OSC signal is sent to the DOSC (OSC1- IN) for processing. In lieu of a DOSC, it is possible to use
two UOSCs. In this case, both UOSCs would have to be interconnected via the ILAN ports for internal
communications.
E: DSCMs to LIM
• The optical signal goes from DSCMs (if equipped) to the next module’s port 6 (line B In).
F: DOSC to LIM
• The 1510nm OSC signal (OSC2- OUT) is connected to the LIM or amplifier module.
G: Amplification and performance monitoring
• If the module is equipped with a post-amplifier "B" EDFA (LIMs and SLAs are not equipped with post-amplifiers)
the DWDM signal is amplified. Performance monitoring taps provide before and after amplification power
readings as well as an optical return loss value for the amplifier (if equipped).
H: Common output of the LIM
• The amplified optical signal and OSC are combined before transmission on the backbone fiber.
108
Line amplifier site with DRA signal flow
1. MLA Amplifier site 1: The signal enters the Line B in port (6) of the MLA at Amplifier site 1 to
be pre-amplified.
2. DRA B Amplifier site 1: Going from Line B out (5) to Line B in (2) of DRA B, which works in
pair with DRA A at Amplifier ste 2, the signal reaches the Line B out port (1) of DRA B.
3. DRA A Amplifier site 2: Then the Raman pumps in the DRA A module of Amplifier site 2
inject power into the fiber and produce gain on the traffic signal coming from Amplifier site 1.
This optical gain occurs in the transmission fiber and is distributed along the span.
4. MLA Amplifier site 2: The amplified traffic signal then goes through Line A out (3) port of
DRA A, reaches Line A in of the MLA at Amplifier site 2, is amplified and then dropped through
Line A out (7) port.
109
ROADM site signal flow
A: Signal Flow within the MLA
• The line signal is received by the Mid-Stage Line Amplifier (MLA) or Line Interface Module (LIM)
for amplification (if equipped with amplifier). After amplification, a small portion of the signal is sent
to the monitoring tap (ports 2). The OSC signal is separated from the traffic wavelengths.
B: MLA to OPM
• MLA port 2 is connected to port 1 of the local OPM module. Ports 3 and 4 are connected to the
east side LIM. This provides each site with per-wavelength power measurements at this location.
C: LIM to DOSC
• The 1510 nm OSC signal is sent to the UOSC (OSC1- IN) for processing. Both UOSCs (one for
each of the shelves) would have to be interconnected via the ILAN ports for internal
communications.
D: LIM to WSS
• The optical signal is transmitted from the "Line A out" port (port 7) to the "Common in" port (port
11) of the WSS.
E: WSS Demux
• All wavelengths are received on the WSS "Common in" port (port 11). The aggregate power is
monitored and every wavelength is split. Based on user provisioning, wavelengths are then either
blocked or allowed through each of the five out ports. For example, if a number of wavelengths are
provisioned for switch port 1 (WSS ports 1 and 2), they will automatically be blocked on all the
other ports.
F: West WSS to East WSS
• Per Ciena's engineering guidelines, switch port 1 (ports 1 and 2) are used for passthrough
connections between shelves. The passthrough channels are transmitted from the "switch 1 out"
port (port 2) of the first WSS to the "switch 1 in" port (port 1) of the second WSS.
G: WSS to SCMD (or CMD)
• Switch ports 3, 4 and 5 (ports 5 - 10) are used to connect the WSS module to SCMD. Up to three
SCMDs can be cascaded off each of the switch ports. The "Switch port out" is connected to the
SCMD "Common in" port.
110
ROADM site signal flow
H: West WSS to East WSS
• The aggregate signal is sent to the "switch port 1 in" of the second WSS, at this
point, power monitoring is performed on the aggregated signal.
I: SCMD (or CMD) to WSS
• The signal from the SCMD or SCMD cascade is sent to the "Switch port in "
(ports 5, 7 and 9) of the WSS module.
J: WSS Mux
• The WSS combines the traffic from each of the ports on the "Common out" port
(port 12).
K: WSS to LIM
• The "Common out" port (port 12) of the WSS is connected to port 6 of the LIM.
L: OPM to LIM
• The OPM is connected to port 1 of the LIM. At this point per channel power
measurements are available.
M: UOSC to LIM
• The UOSC's out port is connected to port 3 of the LIM.
N: Signal Flow within the LIM
• Traffic from the WSS is amplified after which a small amount of power is sent to
the OPM. The LIM then combines the traffic wavelengths with the signal from the
UOSC and sends that new signal out the "Common out" port.
111
112
113
114
Network management requirements
The Common Photonic Layer operates on an Internet protocol (IP)-based network
management system, which is based on the open shortest path (OSPF) routing
protocol standard.
On the carrier side, access to CPL is provided by Optical Manager Element Adapter
(OMEA). On the enterprise side, northbound simple network management protocol
(SNMP) interface SNMP Version 2 (SNMP v2) is supported. SNMP Version 3 (SNMP
v3) is supported at release 5.0.
Local network element access is obtained by using the CPL Craft interface.
OMEA
Ciena Optical Manager Element Adapter (OMEA) is used to manage the Common
Photonic Layer network. The Optical Solution Release (OSR) has reach-through
access to the Common Photonic Layer Craft interface through the OMEA.
Common Photonic Layer Craft (nodal) interface
The Common Photonic Layer’s Craft management solution is a browser-based GUI,
served from a Common Photonic Layer network element..
115
Optical Manager Element Adaptor
Optical Manager Element Adapter (OMEA) is a software application that provides
network management access to Optical Metro network elements (NE’s). OMEA
allows Ciena's ONM and associated network management applications to manage
Optical Metro network elements.
This management solution simplifies day-to-day network operations in a high-
availability, secure environment, ensuring both containment of operational
expenditures and business continuity. The following features are provided when
using OMEA with CPL:
• TL1 translation and session management from the NE
• NE Navigation, Administration, Security
• Resiliency
• Common & Specific PM Collection & Viewer
• Mediation
• Support of RADIUS authentication for CPL network elements
Using OMEA, this configuration supports the following products:
• Advanced Services Platform 5100/5200
• Packet-Optical Platform 6500
• Common Photonic Layer (CPL)
116
Traditional Local Account Management
• Five User Privilege Classes (UPC 1-5)
• Password Management
NE Centralized Security Administration (CSA)
• RADIUS (RFC2865) protocol support
— Primary / Secondary RADIUS server
— NE login requests forwarded by RADIUS gateways (GMDs configured as
GNEs)
• OMEA or 3rd party RADIUS server support
– One or other at same time, not both
• Provisionable RADIUS server timeout (retry)
Fallback Authentication if RADIUS servers unavailable
• Challenge Response or Local
Intrusion Detection System (IDS)
• Provisionable login attempt threshold
Security Alarms, Events and Log Audit Trail
• Intrusion Detection Alarm
• RADIUS server unavailable
117
CPL Security Solution
Force-out user command
Ability for a level 4 user to force out any unwanted logged on user.
Simultaneous login limit
Ability to limit the number of simultaneous login sessions from the same user
account.
118
SSH overview
SSH (Secure Shell) is an application layer protocol and suite of network connectivity
tools providing:
• User/Host Authentication
• Data Integrity (SHA-1, MD5)
• Data Encryption (e.g. AES, 3DES, …)
SSH is used for secure remote access:

• replaces telnet, rlogin which are insecure (passwords sent in clear)
• SFTP - secure file transfer instead of the insecure FTP
SSH protects against threats of confidentiality and integrity, man-in-the-middle,

sniffing, data manipulation, etc.
SSH uses a client/server architecture. SSH applications are widely available for most
popular operating systems.
The figure above illustrates that the EMS, craft and user desktop will use an SSH
client to connect to the CPL’s SSH server. The CPL will use an SFTP client to
send/retrieve data for a number of different applications.
119
Secure HTTP-HTTPS protocol
CPL release 4.0 and higher supports Secure HTTP. This feature provides end users
with a new means to securely access the CPL network elements via HTTPS protocol
using Site Manager or Internet Browsers to perform different configuration and
management related functions.
For example, when a user enters the IP address of the CPL network element in an
Internet Browser specifying https as the protocol, i.e., HTTP//, then a default Web
page allowing access to NE data is presented. With this feature, the underlying
communication path that data travels through between the NE and the user
browser/PC is secured by encryption methods implemented in the standard Secure
Socket Layer (SSL) protocols which control this communication.
The secure HTTP service will build upon the standard HTTP server currently
available on the CPL. The CPL will support both the standard HTTP server, and the
secure HTTP server. The secure http server runs on port 443.
By default, both standard (insecure) and secure HTTP servers will be enabled. The
user will be able to disable or enable those servers.
120
CPL Site Manager
Site manager is an integrated management platform that allows service providers to

manage their most important assets – their customer and the services they sell.
The CPL network element supports a comprehensive suite of OAM&P functionality
managed through the Site Manager craft user interface. It is a graphical nodal
management tool, running natively on Windows, UNIX and Solaris workstations.
The 6500 Site Manager is a common launch tool for craft interfaces in different optical
products like HDX, 6500, 6110, 6130, 6150, OM3000, and CPL.
121
Consolidated Application for Craft Access
Single or common launch point to access all Craft tools for 6500 and CPL
Consolidated alarms view for 6500 and CPL
Common Navigator for 6500 and CPL
• single and multiple NE login/logout support
• mixed product profile support
• alarm banner summary counts
Nodal Manager integrated in Launcher
• Context and window management for both 6500 and CPL via Windows tab
Platform support
Windows, HP-UX and Solaris
Installation and Delivery
Each product (6500, CPL) is delivered with its individual craft component
Each craft (6500, CPL) is installed and configures itself into the common launcher
6500 Packet Optical platform and CPL can be TID consolidated (TIDc) at CPL
release 5.0 and 6500 Release 9.1. A Site Manager option allows to login in this node
type.
Site Manager is locally installed on a PC or launched from an internet browser.
122
Site Manager Java Web Start (JWS)
Site Manager for CPL4.0 and higher can be launched from a web browser
using Java Web Start. It is a similar access method to CPL3.21 web-based
Craft.
CPL4.0 merges the framework for the OME and CPL management
platforms. It provides a common look and feel for management of CPL and
OME nodes.
Both installed and browser based Site Manager are fully compatible with
Java 6.
The web launch tool has a new feature, the “Nodal SLAT Assistant Tool”
which will allow you to commission and provision the NE.
123
124
Check your learning
1. True or False: The OMEA is used for local access to a node
__________________________________________________________________
2. True or False: The Craft interface has to be installed on a PC

____________________________________________________________
125
126
127
128
Common Photonic Layer communications summary:
• OAM&P communications are TCP/IP based
• OSPF routing protocol is used within the CPL sites
• Support for DHCP to manage connected users (DOSC, GMD)
• TL-1 & Craft UI are used to configure external ports (craft, COLAN, ILAN)
• Ethernet communications to all internal Subtending Cards (STCs)
— DHCP-managed, not visible to DCN
— Built-in hub in GMD/DOSC for STC ports
• Dual IP stack: private (VSC to STC communications, ILAN), public (COLAN DCN
access)
• RS-232 (DB-9) serial modem port with flow control on GMD/DOSC
• OSC Ethernet wayside channel (10BaseT)
— 10BaseT clear-channel from site to site
— No IP provisioning required
• RS-232 ports on all CPL modules for field support
129
Serial communications
The Group Mux/Demux (GMD) module provides for RS-232 serial modem access on
its front panel for local provisioning and debug purposes. All other modules have RS-
232 access for debugging purposes only (no modem access capabilities).
IP communications
Common Photonic Layer elements (GMD, 4 Channel Mux/Demux [CMD4], Dual and
Uni Optical Service Channel [DOSC/UOSC], Amplifier etc.) within a site are
interconnected using 10/100Base-T Ethernet links. Ethernet ports are also provided
for connections to data communication networks (DCN) and wayside networks. DCN
connections are made through the GMD/DOSC/UOSC to access subtending
modules. Only the IP addresses of the GMD/DOSCs/UOSCs are visible on the
customer DCN.
Internal communication network –
• Allows elements to communicate with each other for the purposes of provisioning,
operation, and optical control.
• Not directed towards external ports such as DCN or wayside.
External communication network –
• Provides access to all nodes for operations, administration, maintenance, and
provisioning (OAM&P) functions stemming from the network operating center
(NOC)
130
• Communication between the line system and the network operating system
is accomplished through the DCN.
• Connection to this network is through the corresponding port on the GMD
Wayside network –
• Shared with wayside traffic flows that originate and terminate external to the
line system.
• Acts as a pipe to allow the transfer of these flows between sites.
• Enter the system through one wayside port and exit the system through
another wayside port.
• Not allowed to terminate at any element within the system.
• Limited to 10 Mbit/s half duplex
• Does not support quality of service (QoS) or virtual local area network
(VLAN) capabilities.
DHCP server description
Subtending module interface -
• Provides an IP address to connected subtending modules.
• DHCP server is always enabled.
• No provisioning of the subtending module DHCP server is permitted or
required.
DCHP on the Craft interface –
• Not required if all you want is default IP for craft to reach local node
• Provides an IP address, subnet mask and default gateway for the Craft PC.
Enabled by default.
• The customer interface to provision the Craft DHCP server is through TL1
and Graphical User Interface (GUI).
• Default value IP address for the Craft PC is 10.0.0.2
• Default value IP address for the network element is 10.0.0.1
OSC communications
• Point-to-point data communications using Ethernet over SONET/SDH (EOS)
mapping protocols
• Operates at the OC-3/STM-1 data rate on a 1510 nm wavelength
• A transmit and receive fiber pair provides a bidirectional channel between
sites
131
The COLAN/Craft/ILAN ports can be configured in two options.
Host Only Mode ON or OFF:.

When ON, the interface only accepts packets that terminate at its IP address and
routing updates and packets to be forwarded through other circuits are dropped.
In the example showed here, the OMEA server needs to connect to both CPL
shelves for surveillance and administration. Since there is only a single node
connected to the DCN (GNE1), all requests need to go through GNE1 to reach
CPL2.
Should the GNE1’s COLAN port set to ‘Host Only ON’, all packets intended for CPL2
would be dropped by GNE1; CPL2 would not be visible to the OMEA workstation.
The same behavior can be expected for the ILAN and Craft ports.
132
In this configuration, the OSC network is not used for OAM communications.
• Every NE is connected to the DCN.

• Each NE is assigned a COLAN and circuitless IP address from the same subnet.
• Each CPL NE looks like a host on the DCN (no OSPF).
• If the OMEA/Optical Solution Release (OSR) servers use the circuitless IP
address, a static ARP entry must be added to the customer DCN routers for each
NE.
This solution does not provide redundant access to the CPL network in the case of
DCN failures.
133
In this configuration, one NE is connected to the DCN and acts as Gateway Network
Element (GNE) for other network elements
• The GNE is assigned a circuitless IP address and COLAN IP address.
• Other NEs are assigned DCN IP addresses from the same subnet as the GNE.
• The GNE looks like a host on the DCN (no OSPF).
• Static routes must be added to R1 for each of the NE’s traffic to be routed via
GNE1.
This solution does not provide redundant access to the CPL network in the case of
DCN or OSC/ILAN failure.
134
DCN Tunnels
This design is to be used when the customer does not want to assign DCN IP
addresses to each network element. The CPL NE’s are in a VPN and can only be
accessed through an IP tunnel. This makes them secure from unwanted access on
the customer DCN.
• The GNE network elements are assigned a DCN COLAN address.
• All network elements (including GNEs) are assigned a circuitless IP address from
a private IP space selected by the customer to be unique for the Common
Photonic Layer network.
• A tunnel must be created from R1/R2 to routers on each management segment
that needs access to the Common Photonic Layer network (OMEA/ Optical
Solution Release (OSR)/simple network timing protocol [SNTP]/RADIUS).
• Multiple OSPF instances must be run on the router at each management site to
separate the Common Photonic Layer network from the DCN network.
• If multiple instances are not possible, a new router must be installed at each
management site.
This solution has the biggest impact on the customer DCN (tunnels, OSPF
instances, routers) and should only be used if address isolation is required between
the Common Photonic Layer and DCN networks.
135
Advantages:
• Provides Dual GNE redundant access (any number of GNEs)
• The GNEs look like a host on the DCN (no OSPF)
• Proxy ARP feature makes configuring of single or dual GNE configurations easier
• No compatibility issues with 3rd Party OSS
• Static routes do not need to be provisioned on customer DCN
• Time to market
Deployment considerations:
• Requires 2 customer IP addresses per NE
• OMEA provisioning of primary and secondary IP addresses to support polling of
IP/ switching
• Switch forwarding can’t be used at GNEs
Note: A circuitless IP address is one that is assigned to a logical port within the CPL
internal OSPF backbone. (There is no physical cable connection to this logical port).
136
Advantages:
• Same TTM option as “Dual GNE using NAT private IP address” option but with
different deployment
• Offers easier upgrade path for current deployments using R1 single GNE solution
• Takes advantage of L3 switch forwarding (improved performance) at primary
GNE (GNE1)
• Proxy ARP feature makes configuring of single or dual GNE configurations easier
Deployment considerations:
• Requires 2 customer IP addresses per NE
• OMEA provisioning of primary and secondary IP addresses to support polling of
IP/ switching
137
138
Redundant GNE DCN configuration using Layer 2 ARP
GNEs may be deployed to manage arbitrary “sections” of a larger CPL line or ring.
That is, GNEs are configured to be in specific “Redundancy Groups”.
In the figure, GNE1A and GNE2A are both in the same redundancy group and
manage section ‘A’ of the network. Managed network sections should be limited to 10
NEs. When using Wayside with Spanning Tree groups then a further restriction of 7
switch hops applies (Spanning Tree uses a default TTL of 7).
Each GNE pair provides redundant DCN comms access to the RNEs within the
section. The GNE pairs must co-exist on the same L2 network.
CARP (Common Address Redundancy Protocol) is used to determine which GNE is
currently active, and thus providing DCN comms access, for each RNE.
GNEs use “proxy ARP” and “Gratuitous ARP” to notify external routers of the RNE
IP addresses for which they are providing gateway services.
A GNE negotiates Master/Backup responsibilities for each IP in its Proxy IP table,
individually. That is, the GNE may become “master” for one of the IPs in its Proxy list
but may be “backup” for another IP in its Proxy list. (A GNE that is master for an IP
provides DCN comms access to the RNE.)
Each CPL NE is provisioned with 1 public IP only. This address can serve as the
Shelf IP and the COLAN IP. The IPs assigned to NEs that are in the same managed
CPL section must be from the same subnet. (required in order to receive ARP from
DCN Router).
The ILAN ports support un-numbered OSPF circuits (thus removing the requirement
for public IPs on the ILANs).
139
Redundant GNE DCN configuration using Layer 2 ARP (cont)
The GNEs need to be co-located on the same L2 network. You must provide this L2
network and you must ensure that it provides the required level of redundancy (i.e.
for full redundancy, the L2 network must also be fully redundant). Where the GNEs
are not co-located at the same site, the Wayside can be used to provide this L2
network. When using the Wayside for the L2 network, the Wayside must be
configured as a ring for full redundancy.
Note: The Redundant ARP GNE configuration does not detect L2 failures (on your
L2 network) other than the COLAN port to the GNE being down.
The figure shown on the previous page, shows a deployment that uses the CPL
wayside channel to provide the L2 network.
In this configuration, GNE1A and GNE2A are not co-located, but are at diverse sites.
Wayside (running over the OSC) is used to provide the L2 network for this section.
Assuming the NEs, in section “A” of the CPL network, are assigned IP addresses
that belong to the same subnet as the customer DCN R1 router interface. Then:
Router R1 ARPs for the assigned NE IPs
The switch (connected to COLAN port & Wayside port of GNE1A) delivers the ARP
request to the COLAN port of GNE1A and to the wayside channel
The ARP request travels over the wayside channel to the remote switch connected to
the COLAN port of GNE2A and to the wayside channel
The remote switch then delivers the ARP request to the COLAN of GNE2A
GNE1A or GNE2A (depending upon who is the current master) responds to the ARP
request with an ARP reply
140
141
Database Replication Service (DBRS)
End-to-end management of optical channels requires AR/TR (address

resolution/topology resolution) data, which is shared through OSPF opaque LSAs
(Link Statement Announcement) . Opaque LSAs are not used for routing.
However, due to system resource limitations, OSPF network size needs to be limited.
OSPF convergence time also benefits from smaller network size.
DBRS is a mechanism that allows sharing of AR/TR data between adjacent OSPF
networks without the sharing of OSPF routing information, thereby helping to limit the
use of system resources.
DBRS gateways are provisioned between domains
• No OSPF routing between domains, use static routes to interconnect domains.
• Gateways can share AR/TR data between OSPF networks.
• DBRS creates a database for the AR/TR data that needs to be exchanged.
• Can have several, smaller OSPF networks joined together via gateways.
142
Recommended provisioning
TID is required for Branching functionality The CPL shelves supports un-numbered
links on the ILAN Ports. DBRS runs on each shelf
DBRS Provisioning Recommendations:

• Un-Numbered ILANs between co-located NEs.
• Routing setup for best redundancy:
— Provision Static Routing against ILAN port
— OSPF will still be used on OSC as always
— OSPF can be used on COLAN depending on DCN
143
Check your learning
1. True or False: The RS-232 ports on any module can be used to connect a modem to a
CPL site.
__________________________________________________________________
2. If there is no DHCP server set up for a Craft interface access, what will be the IP
address assigned to the PC?
__________________________________________________________________
3. The OSC is a nm wavelength with a Mbit/s line rate.
4. True or False: In a CPL network, each site needs to be connected to the DCN.
__________________________________________________________________
5. The DCN is connected to which modules? Choose all that apply.
a. CMD
b. MLA
c. GMD
d. DOSC
6. The DCN is connected to which one of the following port:
a. ILAN
b. COLAN
c. WAYSIDE
d. CRAFT
144
145
146
147
148
Advanced optical control
The Common Photonic Layer’s automated optical control algorithm, which is used to
optimize the transport performance through a photonic domain, is founded on the
following three principles:
• Minimize non-linearities:
— self-phase modulation [SPM]
— cross-phase modulation [XPM]
— four wave mixing [FWM]
• Control gain tilt of the transmission medium in order to minimize degradation of a
wavelength’s optical signal-to-noise ratio (OSNR).
• Equalize: distribute finite available power such that all wavelengths are treated
equitably (the equitability currency is generally either power or OSNR).
In order to achieve system optimization, the Common Photonic Layer incorporates a
three-level optical control hierarchy:
• Domain: comprised of multiple sectional optical controllers (SOCs)
• Sections: comprised of multiple local optical controllers (LOCs)
• Local optical controller: effective on every optical building block
149
Domain Optical Control (DOC)
The DOC is the highest form of control and seeks to maximize end-to-end
performance across the entire optical control domain. One domain optical controller
exists for each photonic domain.
The DOC communicates with the network management application. The user
provides input to the DOC, which decides which system action to perform:
• System Optimization: in which the domain performance is optimized either in a
service-affecting or non-service-affecting manner.
• Non-service-affecting Capacity Upgrade: also known as “in-service wavelength
addition,”
• Non-service-affecting Capacity Downgrade: also known as “in-service
wavelength delete”.
• Monitoring: assesses whether the current domain operating point is optimal.
• Re-Optimization: in which the system performance is optimized in a non-service-
affecting manner. Generally, this optimization tracks aging and very slow
changes in operating conditions.
The DOC provides the following:
• Single view of photonic domain
• Automates line conditioning by sequencing Sectional Controllers (SOCs)
• Reports alarm and status to Optical Solution Release (OSR) / TL-1 if the set-up
fails and provides ongoing monitoring.
150
Optical Control boundaries
This figure shows a simple two-section optical control domain that consists of two
sectional optical controllers under the control of a single domain optical controller.
The optical control hierarchy takes the characteristics of the topology into account as
the optical multiplexed section serves as a key physical de-limiter between sectional
and domain optical control.
Sectional Optical controllers (SOC) set targets for all LOCs within their sections.
There is one sectional controller (SOC) per Optical Multiplexed Section (OMS).
Essentially, the GMD de-limits one section from another.
Local Optical Controllers (LOC) in each circuit pack maintain targets set by the
SOC.
The Optical Controller layer relies on equipment presence detection
151
Section optical control (SOC)
A sectional optical controller requires the following information from its domain optical
controller:
• which wavelengths are to be optimized within its section
• which optimization approach is to be used:
— Power equalization
— Estimated OSNR equalization
— Bit error ratio [BER] optimization along with optimization targets (if
applicable).
The SOC :
• Coordinates local controllers
• Optimizes section performance
• Tracks long term variations (aging)
• Has a response time in the 10’s of seconds
Note: The sectional optical controller is not user-visible.
152
Local optical control (LOC)
The LOC is generally localized within a circuit and seeks to maintain a set-point for a
given hardware component.
Typical examples of local optical control would be:

• Amplifier gain,
• Amplifier design flat gain (DFG) offset,
• GMD per group output power,
• CMD group drop output power,
• Amplifier electronically-controlled variable optical attenuator (eVOA) attenuation,
Note: The local optical controller is not user-visible.
153
New to R2:
The WSS Middle Optical Controller (MOC) resides between LOC and SOC layers.
The SOC SA Add algorithms take into account the WSS.
• Middle Optical Control (MOC) shall control 88 loss targets, one per wavelength.
• MOC shall maintain the loss of the WSS profile of the WSS by collection per
channel data from the amplifiers connected upstream and downstream of it.
154
Further information in OPM placement:
Within a DOC:
- Typically, there is no OPM at amplifier sites
- 1 OPM at DGFF and ROADM site
- 1 OPM at a regen site
At a DOC boundary
- Before CPL release 3, an OPM cannot be shared by 2 different DOC domains
therefore:
• 2 OPM at a regen site if it is a DOC boundary
- A generic "ROADM" model at a DOC boundary is in reality an add/drop/regen site
with no optical pass-through allowed (the WSS are not interconnected). An OPM is
required for each DOC.
Spurs
- The one span linear spur does not require an OPM.
155
DOC in a branch network.
A distributed optical control model is implemented in CPL R3 where each DOC

controls the individual SOCs in their domain and a communication link exists
between the different DOCs to hand-off control information.
The optimization model is moving toward a “peer-to-peer” model instead of a
centralized hierarchical model.
The peer-to-peer model must:

• Ensure that actions (i.e., add, delete, reoptimization) done in one domain do not
impact other domains
• Provide a method to add or delete channels across multiple domains. i.e. prevent
the user from having to manually perform the add or delete action in each domain
• Provide 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)
156
Enhanced DOC (eDOC) Automation Mode
Rel. 4.0 adds a new DOC Automation mode called Enhanced (eDOC) with the
objective to dramatically improve DOC speed and to increase availability of system
functions
Channel actions (add/delete) are done in a single step. For channel add, the WSS
loss element for the channel being added is set to the best “fit” loss value and, when
doing the first channel add, the amplifier gains are set. For channel delete, the WSS
loss element is set to block the wavelength being deleted. In previous releases, the
loss element was set in multiple steps.
This mode separates the channel action (add/delete) steps from the optimization
steps.
• The system does not have to be in an optimal state to be able to perform a
channel action.
• After adding a channel there may be some margin that can be gained by
optimizing the channel but it is not required for the channel to be available.
Two minutes after a capacity change (add/delete), DOC attempts a background re-
optimization.
• Re-optimization attempted every 2 minutes until successful.
• TCA baselines are reset on first successful re-optimization after a capacity
change.
• DOC reverts to the regular Monitor <-> Re-opt cycle after the first successful re-
optimization.
157
eDOC vs sDOC behavior
DOC channel actions will now use a new algorithm that bundles more than 2
channels at a time. This new algorithm is applied to domains containing pass-
through ROADMs, GOADM or TOADM Terminals, and line AMPs. For domains
containing pass-through TOADM or GOADM will be processed one at a time
• No pre-check is done as part of a channel add. Pre-check is still available as a
manual step prior to channel add
• Channel actions are no longer blocked by optimization state. Channel actions can
be performed on a:
• “Non-Optimal” domain
• Domain with Partially added/deleted channels
• Channel actions are allowed to interrupt any on-going Re-optimization or Power
Preserve operation
• Channel actions do not require any downstream domain(s) to enter Power
Preserving Mode (PPM)
• 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 channel(s)
• DOC attempts to add any partially added channel every two minutes as long as the
active flag of the channel remains as True and the DOC Auto add channels
parameter is Enabled
158
DOC attempts to delete any partially deleted channel every two minutes when DOC
Auto delete channels parameter is Enabled
A user can manually re-add or delete a partially added channel and can manually
delete a partially deleted channel
Fault Detection enhancements:
• Without Enhanced automation mode, a DOC Fault Detected event (other than
pre-check fail) blocks any further actions in that domain. With branching, this
could also block neighbours since Power Preserve Mode (PPM) would not be
sustained.
• With Enhanced automation mode, the objective is to minimize both inter-domain
and intra- domain (add/delete) blocking in cases where the fault only affects a
subset of the domain/channels. With eDOC only partially added and deleted
channels will not block actions but the presence of faulted channels will block
adds and deletes. Note: In all cases, a re-optimization is blocked by a fault in any
section of the domain.
Reduction in the time it takes for DOC to act on “ACTIVE” flag transitions and
reduction in the time it takes DOCTRAIL to build
• As a result, adjacency provisioning is reflected in the DOC channel list quicker
When DOC Auto add channels is Enabled, the time between completing the
adjacencies and DOC beginning the channel add is almost instantaneous
159
New parameters:
• New DOC Automation mode parameter: Enhanced
• New OTS parameter that applies to the CHA (Channel Access) OTS type:
Minimum MUX Power Output
• This parameter represents the minimum channel power expected over the life-
time of the system at the output of the WSS when all CHC target losses are set
to 0 dB. Used by DOC algorithms to calculate a “forecast-tolerant” CHC target
loss to allow for faster single step provisioning of channels. It is like a peak
power target at the output of the WSS.
Channel Condition changes:
• DOC sets the Channel Condition of an added channel to “In-Service” after the
channel has been successfully added.
• DOC triggers an automatic re-optimizing after two minutes if there is any In-Service
channel in the system.
• DOC sets the Channel Condition of any In-Service channel to “Optimal” after a
successful 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.
• DOC sets the Channel Condition of any In-Service channel to “Non-optimal” after a
failed re-optimization.
160
Backwards compatibility
After an upgrade to Rel. 4.0, DOC Automation Mode is not set to Enhanced resulting
in DOC controlling channels in the same way as in previous releases. For
greenfield deployments, DOC Automation Mode defaults to Enhanced.
If a network is not optically connected, then a portion of the network can run Enhanced
DOC and the other portion Standard DOC.
All optically interconnected OTSs and Photonic Domains need to be upgraded to Rel.
4.0 in order to use Enhanced Automation Mode (engineering rule, not enforced by
software).
In a network consisting of several optically interconnected Photonic Domains, it is

supported to have some Photonic Domains running Rel 4.0 sDOC mode and other
Photonic Domains running software less than Rel. 4.0.
• it is not supported to have some Photonic Domains running Rel. 4.0 with eDOC
mode and other Photonic Domains running software less than Rel. 4.0.
• As a result, before setting DOC Automation Mode to “Enhanced” in any Photonic
Domain, the whole network (i.e., all optically interconnected Photonic Domains)
needs to be running Rel. 4.0.
161
Backwards compatibility
Moving away from generic DOC “Fault Detected” alarms in scenarios where we have
a more specific alarm in the network.
For example, Automatic Power Reduction doesn’t need a duplicate DOC alarm, but
having an AMP facility OOS-MA, which does not generate a specific alarm, continues
to trigger DOC Fault Detected .
The following DOC “standard” (sDOC) automation modes are no longer supported in
Rel. 5.0:
• No Auto Monitoring
• Auto Monitor Only
• Auto Re-optimize As Necessary
The DOC Enhanced automation mode introduced in Rel. 4.0 along with the Rel. 5.0-
introduced DOC Enhanced Auto Monitor Only mode can be used
The DOC Enhanced Auto Monitor Only mode operates like the Enhanced mode
except that 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.
162
In previous releases, before a photonic domain runs an optimization operation it
waits for the downstream photonic domain to enter Power Preserve Mode (PPM).
This was an attempt to prevent changes being made in upstream domains
impacting power levels downstream. However the power levels being maintained
were often already in a degraded state, and therefore there is no benefit in keeping
them constant . In Rel. 5.0, PPM is removed from the platform. As a result, a
photonic domain no longer requires that the downstream photonic domain be in
PPM mode before starting an optimization.
The DOC “Path Optimizer” parameter is formally removed from the platform in Rel.
5.0. Users can still enable Path Optimizer through TL1, however, the setting is
ignored by DOC software.
In Rel. 5.0, the DOC “Auto delete on channel LOS” parameter is no longer
supported. If the parameter was enabled before an upgrade to Rel. 5.0, it will be
forced to disabled after the upgrade. The parameter cannot be edited using Site
Manager after the upgrade.

Optical Transport Section (OTS)
CPL is adopting OME Photonics OTS object to simplify feature propagation in the
future. The new OTS object is created to hold the attributes that were accessed as
shelf level attributes in the CPL platform.
One of the main functions of introducing the OTS on CPL is to be able to allow a
DUAL-OSC to control 2 shelves (cost reduction for Greenfield deployments). Ex: at a
ROADM and TOADM
An Optical Transport Section (OTS) is defined as a group of equipment all serving the
same fiber pair.
• A maximum number of OTS per Shelf is 1 with a UNI-OSC
• A maximum number of OTS per Shelf is 2 with a DUAL-OSC
• An OTS object can be created and edited. An OTS may be deleted but only if there
is no equipment provisioned in any of the slots that is referenced by the OTS
• OTS does not need to be provisioned before a circuit pack is provisioned, it can be
done in either order
• OPM is not part of the OTS (manual provisioning is required)
• OBM (Optical Bandwidth Management) supports the creation of cross connections
between any two OTSs
• The two OTSs must have the same TID but have different OSIDs
• Channel AID now includes path ID
• NC-shelf-ingresssite-ingressshelf-pathid-wavelength
164
When upgrading from previous releases to 4.0
Using UNI-OSC or GMDs at all Channel Access sites. The Tx Path ID is consistently
odd (or consistently even) for a direction.
Channel Access Node uses 1 (2) and 2 (1) for Tx Path ID (Rx Path ID) and Line Amp
node uses 1 (2) and 2 (1).
165
Using DOSC at ROADM
In this example, a DOSC is shared by two shelves in a ROADM site. Two different
OTS are assigned.
There is a consistent use of ODD and EVEN path Ids but since we are the same
VSC module (DOSC) for both shelves, a different path ID needs to be provisioned; 3
and 4 in this example.
166
Optical Transport Section (OTS)
Here is an example of the OTS menu. All components are defined as well as DOC
relevant information if applicable.
The Enhanced Topology field is supported starting at CPL release 5. It allows for
Raman amplifiers and DSCM to be part of the Visualization menu.
167
TID consolidation.
TID consolidation is required for OBM to function. It allows multiple shelves (up to 3)
at a site to be managed under the same TID. Site refers to co-located NEs that can
be daisy chained via ILAN ports
This reduces the number of TIDs and nodes requiring management in the network.
Each shelf shares the same TID, 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
NEs.
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 NEs. The primary shelf maintains
synchronization of all its members for things like time synchronization, new or
missing shelves, and security.
Optical Bandwidth Manager
A new CPL application (OBM) is introduced in CPL R3 to provision cross-connections
at branch sites across an OSID boundary. This application is launched when the
Craft is logged into the primary shelf of a consolidated node.
The OBM application allow users to query, create, and delete bi-directional (2WAY)
or uni-directional (1WAY) channel level routing.
168
Photonic Connections menu
At CPL release 4, optical connections that spans across different optical domains
(OTS that have different OSIDs) is provisioned through the Photonic Connections
menu.
169
Common Photonic Layer adjacency
The Common Photonic Layer defines the concept of adjacency as being two
elements of the optical network that are physically linked. Knowledge of such
adjacencies is crucial for the automatic discovery of wavelengths and nodes, and for
automatic optimization.
Common Photonic Layer Release 1 supports the following inter-shelf messaging:
• Line (or nodal) adjacency (Common Photonic Layer node to node)
• Tx/Rx adjacency (Tx/Rx to Common Photonic Layer node).
170
Line adjacency
Line adjacency is adjacency between the local CPL network element and the
neighboring CPL network element.
The GMD/DOSC discovers and manages adjacency between nodes, based on the
OSC signal. The GMD/DOSC creates, modifies and deletes the following data that
defines the connection between the two nodes (fiber pair):
• Far-end point of connection:
— OSID
— Site ID
— Network element target identifier [NE TID])
• Span attributes (fiber type)
The GMD also discovers the co-located GMD at optical add-drop multiplexer
(OADM) sites with the same OSID using interconnect local area network (ILAN)
communication ports.
171
Line adjacency
Line adjacencies are discovered on amplifier or line interface module ports. A line
adjacency is always provisioned from a OUT port (port 5) to an IN port (port 8). The
nodal adjacency format is Shelf TID-Shelf number-Slot-port.
In the example shown here, there are two adjacencies that need to be provisioned,
one on each shelf:
• At the Site_A_WEST-2-2-5: This port is adjacent to Site_B_EAST-1-2-8.
• At the Site_B_EAST-1-2-5: This port is adjacent to Site_A_WEST-2-2-8.
The user must provision this information is the adjacency screen under the expected
far-end field. The fiber type must also be provisioned.
Once the information provided by the user and the information detected by the
system match-up, the adjacency will be considered reliable.
172
Transmitter/receiver (Tx/Rx) adjacency
Tx/Rx adjacency is adjacency between a Tx/Rx device in a non-CPL network
element and a CPL network.
The user must provision the information that will characterize the link and subtending
equipment. This information is crucial to the DOC software, without this information,
the channels cannot be created in the DOC screen of the craft interface.
In this example the adjacency is between the CPL equipment and the subtending
Optical Metro 5200 product.
Data used to create Tx/Rx adjacencies
The data used to create the Tx/Rx adjacency includes:
• Ciena product identifier (Ciena or other)
• Far-end function (Tx or Rx)
• Tx or Rx address (NE TID, shelf TID, slot ID, port ID)
• Tx/Rx attribute profile
• Transmitter: bias, Tx type, label, wavelength, rate, Forward Error Correction
(FEC) and minimum, maximum and current launch power
• Receiver: Rx type, sensitivity, overload/damage thresholds, maximum, positive
and negative transients
173
Transmitter/receiver (Tx/Rx) adjacency
Tx/Rx adjacencies are created at the CMD level. Each port that is connected to
subtending equipment most have it's Tx/Rx adjacency provisioned. The Tx/Rx
adjacency format is ADJ-Shelf number-Slot-port.
By default the Rx port adj. (adjacency) is paired with the Tx port adjacency data. The
user has the option to un-pair the Tx and Rx ports and enter each separately. When
paired the creation of the Tx adjacency will create an Rx adjacency for the same
wavelength.
In the example shown here, the following Tx/Rx adjacency pair needs to be created:
On Port 3 (Tx-adj.) and 4 (Rx-adj.) of the CMD needs to be provisioned for the type
of equipment. In this case, the adjacency AIDs would be : ADJ-2-5-3 paired with
ADJ-2-5-4.
Note: Since there is no communication between the CPL and the subtending
equipment, the Tx/Rx adjacencies remain UNVERIFIED
174
CPL release 2 adjacencies
The adjacencies available in release 1.0 were adjacencies between shelves (inter-
shelf adjacencies), either between two CPL Network Elements (NE) or between the
CPL and the subtending NE (for example Optical Metro 5200 or the OME 6500). In
release 2, a new inter-shelf adjacency is introduced: Wavelength Selective Switch
(WSS) to WSS.
In addition, intra-shelf adjacencies are also introduced. These adjacencies are
"derived" by the CPL system based on hardware installed and provisioned
information such as the SCMD cascade order. The new Intra-shelf adjacencies
available are:
• GMD based OADM network elements:
— LIM - GMD
— GMD - CMD
• TOADM network elements:
— LIM - CMD
— CMD - CMD
• ROADM network elements:
— LIM - WSS
— CMD - WSS
— OPM - LIM
175
Intershelf adjacency.
The WSS in a CPL NE is physically linked to another CPL NE for flexible per-
wavelength add/drop and passthrough and per-wavelength switching. This adjacency
identifies how the WSS are physically connected to one another.
176
GMD-GMD Adjacency
The GMD in a Common Photonic Layer GOADM network element is physically linked
to another Common Photonic Layer GMD for per-group add/drop and passthrough
The GMD manages the provisioned adjacency between two GMDs. The GMD
creates, modifies and deletes the following data that defines the connection between
the two GMD group ports:
• Adjacency Type (GMD)
• Adjacency Facilities (GMD)
• GMD Far End Port
177
Intra-site adjacencies.
This type of adjacency is derived by the system based on user provisioned
information and equipment present at the site.
User provisioned information
• Shared OPM
— At ROADM sites, the OPM is a required module. The OPM has 4 monitoring
ports, that can be connected to two different NE (providing the OSID is the
same for both NEs). The OPM must be physically connected to one of the
NEs and will need to be set-up as shared equipment on the other NE.
• SCMD cascading order
— Since SCMD can be cascaded, it is important to provision the order in which
the SCMD are connected. This information is required for the domain optical
control software.
• eCMD44 Red/Blue with tap to OPM
— To support an OPM for the Enhanced CMD44 50 GHz C-Band module, a Far
End Address (FEA) must be provisioned manually at the Enhanced CMD44
50 GHz C-Band module monitor port (port 92) pointing to the ‘correct’ OPM
port (3 or 4). The corresponding adjacency at the OPM port will be derived.
178
Service and photonic layer interoperability (SPLI)
The SPLI feature simplifies channel provisioning within a siteID by enabling the
photonic layer to discover the transmitter/receiver provisioning information that feeds
into it and auto-provision the corresponding CMD/SCMD ADJ-TX transmitter type
and the ADJ-RX receiver type (the Auto Discovered parameter must be set to Auto).
For a bi-directional channel, service and photonic layer interoperability (SPLI) can be
used to autoprovision the Tx power and Tx wavelength. If using SPLI to
autoprovision the Tx power and Tx wavelength, ensure that the following parameters
are set in the Edit ADJ-TX dialog box:
• Paired Rx is set to Yes
• Auto Discovered is set to Auto
• Sync Provisioned is set to True
The SPLI feature also matches WSS-WSS adjacencies. When the expected far end
address is entered correctly at both ends of the WSS-WSS adjacency, a WSS-WSS
SPLI match occurs and the actual far end address is auto-populated.
179
Check your learning
1. Associate the three controller types with their definitions.
is comprised of multiple Sectional Optical Controllers (SOCs)
is effective on every optical building blocks
is comprised of multiple Local Optical Controllers (LOCs)
a. Local Optical Controller
b. Section Optical Controller
c. Domain Optical Controller
2. What does the DOC perform? Choose all that apply
a. System Optimization
b. Capacity upgrade
c. Capacity downgrade
d. Monitoring
e. Re-optimization
3. On what module does the DOC reside?
a. DOSC
b. GMD
c. CMD
d. WB
4. True or False: The GMD to a GMD is counted as a section.
__________________________________________________________________
5. True or False: Many LOC (Local Optical Controllers) can be in a single module.
_________________________________________________________________
6. Connection from a CPL site to another one would be considered as what type of
adjacency??
a. Nodal (Line) adjacency
b. Tx/Rx adjacency
180
181
182
Lesson Overview
This lesson provides an overview of Ciena’s Product Documentation.
Disclaimer
“The Ciena 6500 Packet-Optical Platform, formerly known as the Optical Multiservice
Edge (OME) 6500, will be referred to as “6500”, in this document.”
“The Ciena Common Photonic Layer (CPL), formerly known as the Common
Photonic Layer (CPL), will be referred to as “CPL”, in this document.”
“The Ciena 6110 and 6130 Multiservice Platform, formerly known as the Optical
Multiservice Edge (OME) 6110 and 6130, will be referred to as “6110”, “6130” or
“6110/6130” in this document.”
“The 565/5100/5200 Advanced Services Platform, formerly known as the Optical
Metro (OM) 565, 5100, and 5200, will be referred to as “565”, “5100” or “5200” in this
document.”
183
184
Characteristics of Ciena Product Documentations
Ciena products are supported by a set of technical documents that describe the
operational features and functions of the product.
There are four important characteristics of Ciena’s Product Documentation:
• Considered part of the equipment: In order to use Ciena equipment properly,

you must know how to find the information you need in a specific document.
• Accessible via Ciena portal: www.ciena.com/support/product-documentation.
• Updated with each major software release: Before using any documentation,
check to make sure you are using the correct version of the documentation for
your equipment's software release. Release numbers and information about the
type of document are found on the cover page of each document and in the
footer of each page of the document.
• Unique in their numbering system: Some of the product documentation

numbering follows a format such as 323-yyyy-zzz where « yyyy » and « zzz »
represents numbers of each product line and documentation section. With each
numbered document suite you can perform many activities with the equipment
such as installation, routine maintenance, alarm clearing, commissioning and
provisioning.
185
Product Documentation Library – CPL
The roadmap shown above illustrates the structure of a Product Documentation

library.
186
Accessing Product Documentation
Customers that wish to access Ciena’s Product Documentation by way of the web
must have an account on Ciena’s portal.
Ciena’s customer portal always contains the most recent version of the product
documentation.
The customer portal also contains other pertinent information relating to that
customer or any of the products that customer has.
187
Accessing Product Documentation (cont’d…)
Customers that already have a Ciena web portal account, can use their e-mail
address and password to log into the portal.
Customers that do not have a web portal account, can select the Register button to
request a Ciena web portal account.
Once logged to the portal, simply select the « Documentation » tab and browse for
the available documentation per product line.
188
Check Your Learning
1. Which of the following are characteristics of the Product Documentation ?

a) Considered part of the equipment.
b) Updated every 6 months.
c) All of the above.
2. Ciena’s customer portal always contains the most recent version of the product
documentation.
a) True
b) False
189
190
191
Term Definition
ACO Alarm Cut-off
ADJ Adjacency
ADM Add/Drop Multiplexer
AID Access Identifier
AINS Automatic In-service
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
ALSO Automatic Line Shut Off
AM Analog Maintenance
AMP Amplifier
ANSI American National Standards Institute
AP Access Panel
APD Avalanche Photo Diode
APR Automatic Power Reduction
APS Automatic Protection Switch
ATM Asynchronous Transfer Mode
AW Allwave
AWG Athernal Arrayed Waveguide Grating Athernal
BBS Broad Band Services
BIP Breaker Interface Panel
BLSR Bidirectional Line Switched Ring
BT Base T (Ten)
CAP Change Application Procedure
C-band Conventional Band (1530 Nm To 1565 Nm)
CCAT Contiguous Concatenation
CD Compact Disk
192
Term Definition
CHC Channel Control
CLE Customer Line Equipment
CMD44 44 Channel Mux/Demux
COM Common Return
CPL Common Photonic Layer
CWDM Coarse Wavelength Division Multiplexing
dB Decibel
dBm Decibels Above One Mill Watt
dc Direct Current
DCC Data Communication Channel
DCE Data Circuit-terminating Equipment
DCN Data Communication Network
DISP Dispersion
DOC Domain Optical Controller
DOSC Dual Optical Service Channel Module
DPO Dwdm Pluggable Optics
DS1 Digital Signal Level 1 (1.544 Mbit/S)
DS3 Digital Signal Level 3 (44.736 Mbit/S)
DSF Dispersion-shifted Fiber
DSM DS1 Service Module
DSCM Dispersion Slope Compensation Module
DSF Dispersion Shifted Single Mode Fiber
DTE Data Terminal Equipment
DWDM Dense Wavelength Division Multiplexing
E1 European Level 1
EC-1 Electrical Carrier Level 1 (51.84 Mbit/S)
EDFA Erbium-doped Fiber Amplifier
ELEAF Enhanced Effective Area Fiber
ETH Ethernet
EMC Electro-magnetic Compatibility
193
Term Definition
EoL End Of Life
ESI External Synchronization Input
ESD Electro-static Discharge
ESM Ethernet Service Module
ESI External Synchronization Output
ETSI European Telecommunications Standards Institute
eVOA Electronically-controlled Variable Optical Attenuator
FC Fibre Channel / Failure Count / Ferrule Connector
FICON Fibre Connection
F-GFP Framed-generic Framing Procedure
FL Freelight
FM Fiber Manager
FX Base Ten (Optic)
FTP File Transfer Protocol
Gbit/s Gigabits Per Second
GE (GbE) Gigabit Ethernet
GFP Generic Framing Procedure
GUI Graphical User Interface
HDLC High-level Data Link Control
HO High Order
ID Identifier
I/F Interface
ILAN Inter Shelf Local Area Network
iISIS Integrated Intermediate System To Intermediate System
IOF Inter Office Facility
IP Internet Protocol
IR Intermediate Reach
IS In-service
ITU-T International Telecommunication Union - Telecommunication
Standardization Bureau
194
Term Definition
J-SDH Japan Synchronous Digital Hierarchy
Km Kilometer
L2 Layer 2
LAN Local Area Network
LBO Line Buildout
LCAS Link Capacity Adjustment Scheme
LEAF Large Effective Area Fiber
LED Light-emitting Diode
LIM Line Interface Module
LR Long Reach
LO Low Order
LOC Local Optical Controller
LS Lambda Shifted Single Mode Fiber
MAA Manual Area Address
MAC Media Access Control
MIC Maintenance Interface Circuit Pack
Mbit/s Megabits Per Second
MHz Mega Hertz
MLA Midstage Line Amplifier
MOC Middle Optical Controller
MOTR Mux Optical Transponder
MPLS Multi Protocol Label Switching
MSP Multiplex Section Protection
MSPP Multi Service Provisioning Platform
MS Millisecond, Multiplex Section
MS-SPRing Multiplexer Section Shared Protection Ring
MTU Maximum Transfer Unit
NDSF Non-dispersion Shifted Fiber
NE Network Element
NEBS Network Equipment-building System
195
Term Definition
NNI Network To Network Interface
Technical Ciena Networks Technical Publication Or Network Timing
Publication Protocol
NNI Network To Network Interface
NSAP Network Service Access Point
OAM Operations, Administration, And Maintenance
OAM Operations, Administration, Maintenance, And Provisioning
OC-n Optical Carrier Level N
OC-3 Optical Carrier Level 3 (155.52 Mbit/S)
OC-192 Optical Carrier Level 192 (9.6 Gbit/S)
ODU Optical Data Unit
OE Optical Ethernet
OE-AD Optical Ethernet Auto Discovery
OMEA Optical Manager Element Adaptor
6500 6500 Packet Optical
OMX Optical Multiplexer
OOS Out-of-service
OPM Optical Power Monitor
OPR Optical Power Received Un-normalized
OPRN Optical Power Received Normalized
OPT Optical Power Transmitted
OPTMON Optical Monitor
OPTN Optical Power Transmitted Normalized
ORL Optical Return Loss
OSA Optical Spectrum Analyzer
OSC Optical Service Channel
OSI Open Systems Interconnection
OSID Optical System Identifier
196
Term Definition
OSNR Optical Signal-to-noise Ratio
OSPF Open Shortest Path First
OSS Operations Support System Or Operation Sub-system
OST Optical System Topology
OTM2 Optical Transport Module2 (10G signals)
OTM3 Optical Transport Module3 (40G signals)
OTN Optical Transport Network
OTS Optical Transmission Section/Optical Trail Section

OTSC Optical Transponder and Service Channel
OTU Optical Transport Unit
P2P Point-to-point
PC Personal Computer
PCN Product Code Number
PDH Plesiochronous Digital Hierarchy
PEC Product Engineering Code
PG Planning Guide
PID Password - Identifier
PIN P-intrinsic-n
PM Performance Monitoring
POP Point Of Presence
PPP Point To Point Protocol
PSC Protection Switch Count
PSD Protection Switch Duration
PSTN Public Switched Telephone Network
PWR Power
QoS Quality Of Service
197
Term Definition
RAU Rack Alarm Unit
ROADM Reconfigurable Optical Add-drop Multiplexer
RPR Resilient Packet Ring
RS Regenerator Section
RS Reduced Slope
Rx Receive
SDH Synchronous Digital Hierarchy
SDTH Signal Degrade Threshold
SF Signal Failure
SFP Small-form Factor Pluggable
SLA Service Level Agreement
SLA Single Line Amplifier
SMF Single-mode Fiber
SNCP Subnetwork Connection Protection
SNMP Simple Network Management Protocol
SOC Section Optical Controller
SoL Start Of Life
SONET Synchronous Optical Network
SP Shelf Processor
SPE Synchronous Payload Envelope
SR Short Reach
SSM Synchronization Status Messaging
SSMF Standard Single Mode Fiber
STM-1 Synchronous Transport Module, Level 1
STS Synchronous Transport System
SWT Shelf Wavelength Topology
198
Term Definition
SDTH Signal Degrade Threshold
SF Signal Failure
SFP Small-form Factor Pluggable
SLA Service Level Agreement
SLA Single Line Amplifier
SMF Single-mode Fiber
SNCP Subnetwork Connection Protection
SNMP Simple Network Management Protocol
SOC Section Optical Controller
SoL Start Of Life
SONET Synchronous Optical Network
SP Shelf Processor
SPE Synchronous Payload Envelope
SR Short Reach
SSM Synchronization Status Messaging
SSMF Standard Single Mode Fiber
TCP/IP Transmission Control Protocol/Internet Protocol
TDM Time Division Multiplexing
T-GFP Transparent Generic Framing Procedure
TL-1 Transaction Language 1
TOD Time Of Day
TPE Transparent Payload Envelope
TSA Time Slot Assignment
199
Term Definition
TSI Time Slot Interchange
TTI Trail Trace Identifier
Tx Transmit
TWc Truewave Classic
TWP Truewave Plus
TWRS Truewave Reduced Slope
U Standard Unit Of Measurement = 1.75"
UID User - Identifier
UNI User To Network Interface
UPC User Privilege Code
UPSR Unidirectional Path Switched Ring
UX Unix
VOA Variable Optical Attenuator
VC Virtual Container
VCAT Virtual Concatenation
VDC Volts Direct Current
VLAN Virtual Local Area Network
VOA Variable Optical Attenuator
VPLS Virtual Private Line Service
VPN Virtual Private Network
VT Virtual Tributary
VTG Virtual Tributary Group
WAN Wide Area Network
WSC Wayside Channel
WSS Wavelength Selective Switch
XC Cross-connect
XFP Large-form Factor Pluggables
XPM Cross-phase Modulation
200
201

CPL 556-T320-151.07.01 Secured

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CPL 556-T320-151.07.01 Secured

Încărcat de

Drepturi de autor:

Formate disponibile

Common Photonic Layer

Operations and Maintenance -

Part Number: 556-T320-151.07.01

Information in this courseware is provided

Copyright 2012 Ciena, All Rights Reserved

Publication date: May 2012

Copyright © 2012 Ciena

All rights reserved.

Visit us at: Ciena.com/training

FOR TRAINING PURPOSES ONLY 2

CIENA CONFIDENTIAL – FOR TRAINING PURPOSES ONLY 3

NTT840FH CPL Planning Guide release 5.0

323-1951-120 Optical Modeler User Guide

323-1661-221 SLAT and Channel Procedures

323-1661-310 Provisioning and Operating Procedures

Trouble Clearing and Module Replacement

CIENA CONFIDENTIAL – FOR TRAINING PURPOSES ONLY 4

CIENA CONFIDENTIAL – FOR TRAINING PURPOSES ONLY 5

1. True or False: CPL is designed to operate strictly in Long Haul Networks.

2. Which of the following is not a CPL feature.

Depending on the recommendations of the Optical Modeler link design tool, an

DIA supports directional control of 44 (100GHz eCMD44) or 88 (50GHz CMD44s)

This configuration allows no local add/drop on line facing WSS modules.

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

This configuration allows local add/drop on line facing WSS modules.

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

Refer to planning guide NTT840FH for a complete list of operational considerations.

Refer to planning guide NTT840FH for a complete list of operational considerations.

1. Which of the following modules is not part of an amplifier site?

2. True or False: A terminal site can be GMD or WSS based?

4. CPL supports wavelengths at 100 GHz spacing (using CMD4).

An example of these modules are:

DOSC at TOADM and ROADM

If using CMD groups:

The Channel Mux/Demux Amplifier (CMDA) is a hardware module that provides

The Channel Mux/Demux Amplifier (CMDA) module contains:

Internal VOAs & Taps

The SCMD8 provides 8 channels to 1 group muxing/demuxing at 50 Ghz spacing.

The CMD44 provides a cost-efficient ROADM 100 Ghz branching evolution.

This deployment applies to Terminals and OADM sites.

CMD44 modules can be used at a point-to-point TOADM terminal site (single

The following configurations are supported:

This module is introduced at CPL R4.

Introduced at CPL R4, the Optical Module PEC is NTT862DAE5.

SSH is used for secure remote access:

SSH protects against threats of confidentiality and integrity, man-in-the-middle,

Site manager is an integrated management platform that allows service providers to

Site Manager is locally installed on a PC or launched from an internet browser.

2. True or False: The Craft interface has to be installed on a PC

Host Only Mode ON or OFF:.

• Every NE is connected to the DCN.

End-to-end management of optical channels requires AR/TR (address

DBRS Provisioning Recommendations:

3. The OSC is a nm wavelength with a Mbit/s line rate.

The Optical Controller layer relies on equipment presence detection

Note: The sectional optical controller is not user-visible.

Typical examples of local optical control would be:

Note: The local optical controller is not user-visible.

A distributed optical control model is implemented in CPL R3 where each DOC

The peer-to-peer model must:

In a network consisting of several optically interconnected Photonic Domains, it is

CIENA CONFIDENTIAL – FOR TRAINING PURPOSES ONLY 163

This lesson provides an overview of Ciena’s Product Documentation.