6500 Packet-Optical Platform Commissioning and Testing

6500 Packet-Optical Platform
Commissioning and Testing

Release 12.7
What’s inside...
SLAT process overview
Nodal SLAT procedures
Photonic layer provisioning procedures
Photonic layer site testing procedures
Fixed-plan terminal node procedures
Passive OTS network procedures
Wavelength addition and deletion
Appendix A: Observing product and personnel safety guidelines
Appendix B: Quick-start turning-up using the Node Setup application—examples
Appendix C: Zero touch provisioning
323-1851-221 - Standard Issue 1

May 2020
Copyright© 2010-2020 Ciena® Corporation. All rights reserved.
LEGAL NOTICES
THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA
CORPORATION AND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE
OR DISCLOSE ITS CONTENTS, OR TO MANUFACTURE, USE, OR SELL ANYTHING THAT IT MAY DESCRIBE.
REPRODUCTION, DISCLOSURE, OR USE IN WHOLE OR IN PART WITHOUT THE SPECIFIC WRITTEN
AUTHORIZATION OF CIENA CORPORATION IS STRICTLY FORBIDDEN.
EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS
COMPLETE AND ACCURATE AT THE TIME OF PUBLISHING; HOWEVER, THE INFORMATION CONTAINED IN
THIS DOCUMENT IS SUBJECT TO CHANGE.
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed
to in writing CIENA PROVIDES THIS DOCUMENT “AS IS” WITHOUT WARRANTY OR CONDITION OF ANY
KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to
change without notice. For the most up-to-date technical publications, visit www.ciena.com.
Copyright© 2010-2020 Ciena® Corporation. All Rights Reserved
Use or disclosure of data contained in this document is subject to the Legal Notices and restrictions in this section
and, unless governed by a valid license agreement signed between you and Ciena, the Licensing Agreement that
follows.
The material contained in this document is also protected by copyright laws of the United States of America and
other countries. It may not be reproduced or distributed in any form by any means, altered in any fashion, or stored
in a data base or retrieval system, without express written permission of the Ciena Corporation.
Security
Ciena® cannot be responsible for unauthorized use of equipment and will not make allowance or credit for
unauthorized use or access.
Contacting Ciena
Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com
Customer Technical Support/Warranty www.ciena.com/support/
Sales and General Information North America: 1-800-207-3714 E-mail: [email protected]
International: +44 20 7012 5555
In North America 410-694-5700 or 800-207-3714 E-mail: [email protected]
In Europe +44-207-012-5500 (UK) E-mail: [email protected]
In Asia +81-3-3248-4680 (Japan) E-mail: [email protected]
In India +91-22-42419600 E-mail: [email protected]
In Latin America 011-5255-1719-0220 (Mexico City) E-mail: [email protected]
Training E-mail: [email protected]
For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.
6500 Packet-Optical Platform Commissioning and Testing

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

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

v
Contents 0
New in this release and documentation roadmap xi
SLAT process overview 1-1

Abbreviations used in this chapter 1-1
How to use this document 1-3
SLAT prerequisites 1-6
Commissioning script file 1-6
Equipment requirements 1-6
Supporting equipment requirements 1-6
Provisioning parameters for node setup 1-7
Other customer provisioning information 1-32
Nodal SLAT procedures 2-1

Abbreviations used in procedures 2-1
Node setup solutions 2-4
Fixed-band plan thin terminals 2-9
Standard reach and Extended reach configurations 2-11
6500 commissioning—provisioning information 2-12
List of procedures
2-1 Powering up a new network element and connecting a craft computer 2-28
2-2 Checking the current software release 2-32
2-3 Commissioning the network element using scripts 2-36
2-4 Quick-start turning-up using the Node Setup application 2-42
2-5 Launching Advanced SLAT and logging in 2-56
2-6 Commissioning a network element using Advanced SLAT 2-59
2-7 Enabling or disabling auto-equipping 2-65
2-8 Performing a lamp test 2-67
2-9 Provisioning OSPF router parameters 2-68
2-10 Provisioning ILAN 2-70
2-11 Provisioning Shelf IP address 2-73
2-12 Provisioning IISIS router parameters 2-75
2-13 Provisioning COLAN 2-76
2-14 Provisioning proxy ARP (IPv4)/ND Proxy Provisioning (IPv6) 2-78
2-15 Provisioning NAT 2-80
2-16 Provisioning Dynamic NAT 2-81
2-17 Provisioning Port Filtering 2-82

vi Contents
2-18 Provisioning Reverse Port NAT 2-83

2-19 Provisioning Neighbor Discovery Protocol 2-84
2-20 Provisioning static routes 2-85
2-21 Provisioning OSPF routes distribution 2-87
2-22 Provisioning IISIS routes distribution 2-88
2-23 Provisioning SNMP 2-89
2-24 Provisioning security 2-91
2-25 Provisioning SSH/TELNET and HTTP/HTTPS Server 2-92
2-26 Provisioning craft access 2-93
2-27 Provisioning craft OSPF/IISIS 2-96
2-28 Checking, clearing, and provisioning alarms 2-97
2-29 Post SLAT commissioning 2-98
2-30 Commissioning fixed-plan terminal nodes using CLI 2-103
2-31 Commissioning 6500 Line Amp nodes using the CLI 2-110
Photonic layer provisioning procedures 3-1

List of procedures
3-1 Provisioning photonic parameters 3-6
3-2 Provisioning adjacencies 3-14
3-3 Changing amplifier provisioning targets and differential provisioning settings
on an existing network 3-32
3-4 Updating SPLI entries 3-37
3-5 Recalibrating the SRA circuit packs 3-38
Photonic layer site testing procedures 4-1

List of procedures
4-1 Connecting intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM
sites 4-5
4-2 Adding a new CMD44, CMD64, CMD16, CMD24, CMD96, or BMD2 4-85
4-3 Adding a new OMD4 or OMX 4-90
4-4 Adding a new SCMD4 4-94
4-5 Adding a new CCMD12 4-98
4-6 Adding a new CCMD8x16 or a CXM C-Band Type 1 4-101
4-7 Testing ROADM channel access continuity 4-105
4-8 Testing a CDC ROADM configuration 4-133
4-9 Testing TOADM channel access continuity 4-155
4-10 Testing a DIA configuration 4-164
4-11 Testing a low channel count DIA configuration 4-173
4-12 Testing a Colorless OADM configuration 4-178
4-13 Connecting intra-site fibers and testing a Colorless Direct Attach configuration
(COADM OTS connected to 1x9 or 1x2 WSS or RLA) 4-191
4-14 Connecting intra-site fibers for a Colorless Direct Attach configuration
(CCMD12/CMD44/CMD64 connected to 1x20 WSS) 4-211

Contents vii
4-15 Testing Colorless Direct Attach with Direct Attach CMD44/CMD64

configurations (CCMD12/CMD44/CMD64 connected to 1x20 WSS) 4-227
4-16 Testing a line amplifier node 4-243
4-17 Testing DGFF nodes 4-286
4-18 Connecting intra-site fibers for Coherent Select sites 4-293
4-19 Testing a Coherent Select line amplifier node 4-311
4-20 Testing a Coherent Select Terminal - Colored node 4-317
4-21 Testing Coherent Select Directionless or Directional nodes 4-322
4-22 Connecting inter-NE fibers and testing the photonic layer 4-329
4-23 Configuring a single span 100 GHz CMD44 point-to-point terminal 4-335
4-24 Configuring a single span 100 GHz CMD16/CMD24 point-to-point
terminal 4-339
4-25 Configuring a single span OMD4/CMD44 or OMX point-to-point
terminal 4-343
4-26 Equalizing a thin terminal system 4-349
4-27 Configuring a remote CMD44 terminal 4-362
4-28 Connecting intra-site fibers for 1x20 Colorless Directionless (CD) ROADM
with FIM4 sites 4-363
4-29 Site testing for 1x20 Colorless Directionless (CD) ROADM with FIM4 4-370
4-30 Connecting intra-site fibers for 1x20 Colorless Directionless (CD) ROADM
with FIM Type 3 sites 4-392
4-31 Site testing for 1x20 Colorless Directionless (CD) ROADM with FIM Type
3 4-399
Fixed-plan terminal node procedures 5-1

List of procedures
5-1 Connecting intra-site fibers for the fixed-plan terminal nodes and performing
site testing 5-3
5-2 Adding transponder information for SPLI and adding adjacencies 5-25
5-3 Connecting the inter-site fibers for fixed-plan terminal nodes, performing
additional provisioning, and testing the photonic link 5-27
5-4 Creating 6500 and transponder fiber connections for a Fixed-96, Fixed-88,
Fixed-44, Fixed-64, or Flex-12 configuration 5-30
5-5 Verifying 6500 threshold and power level settings for protected
configurations 5-33
5-6 Setting Line B target gain for Extended Reach and line-amp
configurations 5-37
5-7 Resetting the TCA baselines 5-41
5-8 Calibrating the SRA circuit packs 5-43
5-9 Verifying traffic continuity for unprotected Fixed-96, Fixed-88, Fixed-44,
Fixed-64, and Flex-12 configurations 5-46
5-10 Verifying traffic continuity for Fixed-96, Fixed-88, Fixed-44, and Fixed-64 OPS
protected configurations 5-48
Passive OTS network procedures 6-1


viii Contents
List of procedures
6-1 Adding passive components 6-4
6-2 Creating a passive OTS and defining its configuration 6-10
6-3 Provisioning line adjacencies 6-11
6-4 Equalizing a passive layer network 6-12
6-5 Equalizing the OTS TX at a ZPT node 6-33
6-6 Equalizing OTS RX and OTS TX at an express node 6-35
6-7 Equalizing the OTS RX at a ZPT node 6-40
6-8 Equalizing a line amplifier node with one FGA 6-42
6-9 Equalizing a line amplifier node with two FGA 6-44
6-10 Adding a new channel over a passive OTS network 6-47
6-11 Inserting a new add/drop filter 6-49
6-12 Turning up channels over a Passive Bridge to ROADM configuration 6-52
6-13 Turning up channels over a Passive Bridge to ROADM—one passive tail
configuration 6-56
Wavelength addition and deletion 7-1

Guidelines for provisioning the Expected far end address (EFEA) between a CMD and
a transponder 7-2
Wavelength addition and deletion procedures 7-2
List of procedures
7-1 Adding bidirectional optical channels 7-4
7-2 Adding unidirectional optical channels 7-21
7-3 Deleting bidirectional optical channels 7-35
7-4 Deleting unidirectional optical channels 7-41
7-5 Force deleting optical channels 7-47
7-6 Express deleting optical channels 7-50
7-7 Adding the first optical channel to a Stretched Span 7-53
Appendix A: Observing product and personnel safety guidelines

8-1
Audience 8-2
Precautionary messages 8-2
Safety standards 8-3
Grounding standards 8-4
Laser radiation—optical transmission systems 8-4
International standards 8-4
Laser radiation hazards 8-5
Labeling 8-6
Circuit pack labels 8-6
Using optical fibers 8-32
Handling optical fibers 8-32
Splicing optical fibers 8-33
Repairing optical fibers 8-34
Working with systems cooled by forced air 8-34

Contents ix
Working with power 8-35

Grounding requirements 8-36
Working with AC power 8-39
Working with DC power 8-40
Dissipating static electricity 8-43
Preventing circuit pack damage and pluggable module damage 8-48
Handling, installing, storing, or replacing circuit packs and pluggable
modules 8-48
Transporting circuit packs and pluggable modules 8-50
Controlling equipment access 8-50
Controlling equipment environment 8-50
List of procedures
8-1 Applying a 1M Hazard Level Caution label on NTK552AAE5, NTK552BAE5,
NTK552FAE5, NTK552FB, and NTK552GAE5 circuit packs 8-56
8-2 Applying Hazard Level 3B and/or 1M laser safety labels on OMC2 8-65
Appendix B: Quick-start turning-up using the Node Setup

application—examples 9-1
Direct Connect—configuration example 9-2
Gateway Connect—configuration example 9-6
Appendix C: Zero touch provisioning 10-1

Overview 10-2
Terminology 10-5
Support details 10-6
Operational considerations 10-7
Prerequisites 10-7
Triggering ZTP out-of-the-box 10-7
ZTP details 10-8
ZTP flow - topology based 10-8
ZTP flow - client-ID based 10-9
DHCP options 10-10
ZTP sequence diagrams 10-11
Directly connected 6500 10-12
Non-directly connected 6500 10-12
ZTP files 10-13
Boot file 10-13
Configuration file 10-15
Boot file transfer 10-16
Configuration file transfer 10-17
TIDc and Shelf-Sync 10-17
6500 DHCP relay agent provisioning 10-18
Security 10-19
ZTP completion 10-20
ZTP error handling 10-21
6500 DHCP client 10-21
6500 DHCP relay 10-25

x Contents
Troubleshooting other ZTP scenarios 10-28

DHCP lease acquired, shelf uncommissioned 10-28
ZTP status stays at 'running' 10-28
Configuration examples 10-30
Redundant OSPF GNE with TIDc 10-30
Private-IP GNE 10-36
Procedures 10-42
Site Manager navigation 10-43
List of procedures
10-1 Retrieving and editing the ZTP settings 10-44
10-2 Retrieving and editing the DHCP relay agent parameters 10-45
10-3 Adding a DHCP relay agent server 10-46
10-4 Deleting a DHCP relay agent server 10-47
10-5 Retrieving DHCP relay agent statistics 10-48
10-6 Retrieving DHCP relay agent interface parameters 10-49
10-7 Adding a DHCP relay agent interface 10-50
10-8 Deleting a DHCP relay agent interface 10-51
10-9 Encrypting and provisioning shared secrets 10-52

xi
New in this release and documentation

roadmap 0
This technical publication supports 6500 Packet-Optical Platform (6500)

Release 12.7 software and subsequent maintenance releases for
Release 12.7.
ATTENTION
In the current release, software support for CMD16 and CMD24 modules is
limited to inventory display. Any software feature descriptions that refer to
CMD modules, other than those related to inventory, do not apply to the
CMD16 or CMD24 unless stated otherwise
Issue 1
The following new/enhanced features are covered in this document.:
• CMD42 112.5 GHz
The following has been removed from this publication as they are no longer
supported in Release 12.7:
• Hardware
— Shelf Processor with Access Panel (SPAP)
– Shelf Processor w/Access Panel (NTK555LA)
– 2-slot Shelf w/SP + OTN Flex MOTR 8xSFP
(NTK503MAE5/NTK503NAE5)
— Cross-connect circuit packs
– Cross-connect circuit packs (NTK557AAE5, NTK557BAE5,
NTK557EAE5, NTK557GAE5, NTK557NAE5, NTK557PAE5,
NTK557QAE5, NTK557ES, NTK557GS, NTK610BBE5)
– Multi-service cross-connect circuit pack (NTK557BE5)
— Electrical circuit packs
– 63xE1 circuit packs (NTK541BAE5/NTK541PAE6)
– 24xDS3/EC-1 circuit packs (NTK543NAE5/NTK544NAE5)

xii New in this release and documentation roadmap
– 24xDS3/E3 circuit packs (NTK543CAE5/NTK544CAE5)

– 16xSTM-1e circuit packs (NTK546CAE5/NTK546NAE5)
– DSM shelf assemblies (NTK407AC/NTK407AC)
– DSM 84xDS1 TM circuit packs (NTN313AA/NTN313AC)
— Trans Mux circuit packs
– 48 Channel Trans Mux (Portless) circuit pack (NTK558DAE5)
— OC-n/STM-n circuit packs
– 1xOC-192/STM-64 circuit packs (NTK523BAE5, NTK523DAE5,
NTK523FAE5, NTK523FBE5, NTK524BAE5, NTK524DAE5,
NTK524FAE5, NTK524FBE5)
– 2xOC-48/STM-16 circuit packs (NTK516BAE5, NTK517BAE5,
NTK519BAE5, NTK520BAE5)
– 8xOC-3/12/STM-1/1 circuit packs (NTK513DAE5, NTK513MAE5)
– 16xOC-n/STM-n circuit packs (NTK512FAE5, NTK513FAE5,
NTK512GAE5, NTK513GAE5, NTK513GAE7
– 8xOC-3-n/STM-n circuit packs (NTK511AA, NTK513DAE5,
NTK513MAE5)
– (2+8)xOC-n/STM-n circuit packs (NTK521CAE5, NTK521DAE5,
NTK522CAE5, NTK522DAE5)
— OTSC and OTR circuit packs
– 10G OTSC circuit pack (NTK528AAE5)
– 10G OTR (NTK530MAE5)
– 2.5G MOTR (NTK530NAE5, NTK530NCE5)
— SuperMux circuit packs
– SuperMux with integrated DWDM circuit packs (NTK535EAE5,
NTK535EBE5)
– SuperMux with XFP circuit packs (NTK535FAE5)
— NGM WT circuit packs
– 10G OC-192/STM-64 WT circuit packs (NTK530AAE5,
NTK530BAE5, NTK530CAE5)
– 10GEL WT circuit packs (NTK530ABE5, NTK530BBE5,
NTK530CBE5)
– 10G OTU2 WT circuit packs (NTK530ACE5, NTK530BCE5,
NTK530CCE5)

New in this release and documentation roadmap xiii
— Data circuit packs

– GE circuit packs (NTK535LAE5, NTK535LBE5)
– 10GE circuit pack (NTK533AAE5)
– 24x10/100BT EPL circuit packs (NTK548BAE5, NTK548MAE5)
– FLEX MOTR circuit pack (NTK531YAE5)
— Layer 2 circuit packs
– L2SS circuit pack (NTK531BAE5, NTK531HAE5)
– PDH gateway circuit pack (NTK531MAE5)
– L2 MOTR circuit pack (NTK531VAE5)
• Protection schemes
– 1+1/MSP linear (including 1+1 linear SDH-J)
– 1+1 GE
– UPSR/SNCP
– 2-Fiber BLSR/MS-SPRing
– 4-Fiber BLSR/MS-SPRing
– RPR
– 1+1 (LAG)
6500 technical publications

The following roadmap identifies the technical publications that support the
6500 D-Series and S-Series for Release 12.7.

xiv New in this release and documentation roadmap
6500 D-Series and S-Series roadmap
Planning a Network Installing, Managing and Maintaining and Circuit Pack-Based

Commissioning and Provisioning Troubleshooting Documentation
Testing a Network a Network a Network
Documentation Installation - Administration Fault Management - Common Equipment

Roadmap General Information and Security Performance (323-1851-102.1)
(323-1851-090) (323-1851-201.0) (323-1851-301) Monitoring
(323-1851-520) WaveLogic, OCLD,
Planning - Installation - Configuration -
OCI, MUX,
Parts 1, 2, and 3 2-slot Shelves Provisioning &
Fault Management - and Submarine
(NTRN10FG) (323-1851-201.1) Operating Parts 1 & 2
Alarm Clearing (323-1851-102.4)
Data Comms (323-1851-310)
Planning & User Guide Installation - 7-slot & Parts 1 and 2
(323-1851-101) 6500-7 packet-optical Configuration - (323-1851-543) OTR and
Shelves Protection Switching OTN Flex MOTR
Ordering Information
(323-1851-201.2) (323-1851-315) Fault Management - (323-1851-102.5)
(323-1851-151)
Module
Manufacturing Installation - Configuration - Replacement
14-slot Shelves Photonics
Discontinued and Connections (323-1851-545)
(323-1851-201.3) Equipment
Unsupported Parts Management
(323-1851-102.6)
(323-1851-155) Installation - (323-1851-320)
Fault Management -
NBI Fundamentals 32-slot Shelves Configuration - SNMP eMOTR
(323-1851-165) (323-1851-201.4) Control Plane (323-1851-740) (323-1851-102.7)
(323-1851-330)
Latency Passive Chassis
Encryption and FIPS Fault Management - OTN I/F, PKT I/F, &
Specifications (2150 & Photonics),
Security Policy Customer Visible PKT/OTN I/F
(323-1851-170) Filters, and Modules
Overview and Logs (323-1851-102.8)
Pluggable (323-1851-201.5)
Procedures (323-1851-840)
Datasheets Licensing (323-1851-340)
and Reference (323-1851-210)
(323-1851-180) MyCryptoTool The following publications are not provided in this release;
Certificate Electrical (323-1851-102.2)
TL-1 Description Commissioning OC-n/STM-n (323-1851-102.3)
and Testing Management and
(323-1851-190) Configuration - Bandwidth & Data Services Parts 2,3 (323-1851-320)
(323-1851-221) Quick Start The following publications are renamed;
CLI Reference (323-1851-341) Configuration – Connections Management (323-1851-320)
(323-1851-193) 6500 AC Rectifier WaveLogic, OCLD, OCI, MUX, & Sub Circuit Packs (323-1851-102.4)
(323-1851-900) OTR and OTN Flex MOTR Circuit Packs (323-1851-102.5)
Site Manager
Fundamentals eMOTR Circuit Packs (323-1851-102.7)
(323-1851-195)
SAOS-based Command Fault and MIB

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

1-1
SLAT process overview 1-
This chapter contains the following topics:

• “Abbreviations used in this chapter” on page 1-1
• “How to use this document” on page 1-3
• “SLAT prerequisites” on page 1-6
Abbreviations used in this chapter

ARP address resolution protocol
CMD channel mux/demux
COLAN central office LAN
CS Coherent Select
CSA centralized security administration
DCN data communications network
DHCPv4 dynamic host configuration protocol version 4 (IPv4)
DISP dispersion
DOC domain optical controller
DSCM dispersion slope compensation module
EDP engineering documentation package
FEC forward error correction
GCC general communications channel
GNE gateway network element
IDP international documentation package
IISIS integrated ISIS
ILAN intershelf LAN

1-2 SLAT process overview
IPv4 Internet Protocol version 4
LAN local area network
LIM line interface module
LOFEF laser off far end failure
MOR multiwavelength optical repeater
NE network element
NAT network address translation
NDP topology neighbor discovery protocol - topology
ND Proxy (or NDP in ND Proxy protocol

Proxy context)
NRD network element release driver
NTP network timing protocol
OADM optical add-drop multiplexer
ODU optical data unit
OSC optical service channel
OSPFv2 open shortest path first - version 2
OTS optical transport sections
OTM optical transport module
OTN optical transport network
OTR optical transponder
OTU optical transport unit
RADIUS remote authentication dial-in user service
ROADM reconfigurable optical add/drop multiplexer
RNE remote network element
Rx receive
SAT SLAT Assistant Tool
SBS stimulated Brillouin scattering
SLAT system lineup and testing

SNMP simple network management protocol
SP shelf processor
TR transmit/receive
Tx transmit
TTI trail trace identifier
UDP user datagram protocol
WSS wavelength selective switch
How to use this document

Figure 1-1 on page 1-5 outlines the 6500 end-to-end SLAT process flow. Make
sure you review the “SLAT prerequisites” before starting the SLAT process.
Complete either:
• “Nodal SLAT procedures” at the first 6500 site. See “Node setup solutions”
on page 2-4 for the Node Setup simplification solution introduced in
release 10.0.
or
• Zero touch provisioning (ZTP). See “Appendix C: Zero touch provisioning”
on page 10-1
or
• script-based commissioning solution (if a commissioning script file exists).
See “Node setup solutions” on page 2-4.
or
• command line interface (CLI) for fixed-plan terminals. See “Fixed-band
plan thin terminals” on page 2-9.
If the site contains 6500 photonic layer circuit packs, perform the “Photonic
layer provisioning procedures” and “Photonic layer site testing procedures”
while you are at the site. If the site contains service circuit packs, perform the
“Service layer site testing procedures” while you are at the site (optional).
Then move on to the next 6500 site and repeat the same process until all 6500
sites have been visited.
If you are deploying a Passive 6500 photonic layer system, perform the
“Passive OTS network procedures” to turn up the Passive system. (For
information on Passive applications, refer to the 6500 Packet-Optical Platform
Photonic Layer Guide, NTRN15DA.)

If your network contains non-6500 amplifiers, perform nodal SLAT and site
testing at all amplifier sites according to amplifier SLAT documentation.
Once the site testing procedures are done, perform “Wavelength addition and
deletion”. If your network contains non-6500 amplifiers, perform amplifier
network SLAT according to amplifier SLAT documentation.
For Flexible Grid configurations, refer to Configuration - Control Plane,

323-1851-330. for information on wavelength addition or deletion.
After completion of the end-to-end SLAT process, you can perform final
system provisioning to customize your system. For 6500 provisioning
procedures, refer to Part 1 and Part 2 of Configuration - Provisioning and
Operating, 323-1851-310, Configuration - Connections Management,
323-1851-320, and Administration and Security, 323-1851-301.
For PKT/OTN transport and switched services, refer to OTN I/F, PKT I/F, and
PKT/OTN I/F Circuit Packs, 323-1851-102.8 for the provisioning procedures
required to bring the OTN I/F, PKT I/F, and PKT/OTN I/F circuit packs to a
ready to carry traffic state.

Figure 1-1
End-to-end SLAT process flowchart
6500 nodal SLAT or ZTP

“Nodal SLAT procedures” (Chapter 2) or “Appendix C: Zero touch provisioning”
To select the node setup solution for your configuration (Node Setup application or SLAT
Assistant Tool), see Figure 2-1, “Selecting the turning-up solution for a newly installed
system”.
Photonic layer Photonic Submarine POTS/

DOC-controlled layer (DOC or PKT
systems Passive Flexible
systems Grid)
“Photonic layer “Passive OTS See Configuration -

provisioning network procedures” Control Plane,
procedures” (Chapter 6) 323-1851-330, and
(Chapter 3) SAOS-based Packet
Services
Configuration,
323-1851-630.
See 6500
Packet-Optical
“Photonic layer site testing Platform Submarine
procedures” (Chapter 4) Networking
Application Guide,
NTRN72AA.
Flexible
Grid
Wavelength addition and deletion
(see Configuration - Control
Fixed Plane, 323-1851-330)
grid
“Wavelength addition and deletion”
(Chapter 7)

SLAT prerequisites
To start SLAT, engineering data specific to the deployment must be generated
in the planning stages in the form of an engineering documentation package
(EDP) or international documentation package (IDP) for each site. This
engineering data contains items such as provisioning information, fiber
connections, circuit pack placements, data communications strategy, and link
budget design information.
You must have the following information and equipment and meet the following
pre-requisites before 6500 SLAT can begin.
Commissioning script file

If you have selected the script-based commissioning solution, make sure you
have the commissioning script file (file format is .json).
Equipment requirements
You must have the 6500 equipment specific to the network element as
specified in the EDP or IDP. The circuit packs and their associated slot
numbers must be identified.
Supporting equipment requirements

You must have the following supporting equipment as listed in Table 1-1.
Table 1-1
Supporting equipment list
Item Check
Access to the 6500 load (if SP is not equipped with the correct load), see Note.
Craft computer that meets minimum system requirements—refer to the current

release of Site Manager for 6500 Packet-Optical Platform - Fundamentals,
323-1851-195, for details.
Current release Site Manager software installed on your craft computer—refer to

the current release of Site Manager for 6500 Packet-Optical Platform -
Fundamentals, 323-1851-195, for installation procedures.
Note 1: Advanced SAT and the Node Setup application support Java 1.7 and
higher.
Note 2: After Site Manager is installed, the Nodal SLAT Assistant Tool can be
launched directly from the Site Manager Tools menu for all previous releases
supported by the installer.
If you will be using OneControl: OneControl installed on the OneControl server—

refer to the OneControl documentation suite for more information
Optical fiber numbers or labels for each port to be connected

Table 1-1
Supporting equipment list (continued)
Item Check
Ethernet cables:
• 10Base-T RJ-45 crossover cable (network element to craft computer)
• 10/100Base-T DB-9 to RJ-45 cables (network element to DCN)
• RJ-45/DB-9 adapters
Voltmeter
Optical power meter

Fiber cleaning kit
Fiberscope with LC adapter (and SC adapter for optical layer equipment as
required)
Spare patch cords and adapters
Note: Starting with 6500 Release 12.1, neither a S/W DVD (NTK562xx) nor release-specific paper
certificates (NTK569xx) are available. Use your company's Ciena portal (portal.ciena.com) to access
6500 software releases and software licenses. Starting with 6500 Release 12.1, you must order a
release-specific software license (S74-LIC-NTK569xx) for each shelf that runs the release and use the
licensing portal to activate the software licenses generated by the order. The activated licenses must
be uploaded to your company's License Manager and each 6500 shelf configured to retrieve the
required license(s). For more information on software licenses, refer to ‘Licenses and ordering process’
in Planning - Ordering Information, 323-1851-151.
Provisioning parameters for node setup

Consult the engineering data sheet for your site and make sure you have the
information listed in the table(s) that apply to your node turning-up solution:
• For the SLAT Assistant Tool (SAT):
— for IPv4, see Table 1-2 on page 1-8 and Table 1-3 on page 1-27
— for IPv6, see Table 1-2 on page 1-8 and Table 1-4 on page 1-31
— In Table 1-2 on page 1-8:
– For the Commissioning Steps that specify IPv4 or IPv6 tabs, use
the information under the tab that applies to your system.
– The Commissioning Steps that do not contain IPv4 or IPv6 tabs
either apply to systems irrespective of the IP version, or apply to
IPv4 only, in which case it will be noted in Table 1-2 on page 1-8.
– Various SLAT Assistant Tool panels also include other parameters,
which are either read-only or not mandatory to provision at the
commissioning stage. For more information on parameters, see
Part 1 of Configuration - Provisioning and Operating,
323-1851-310.

For more information on parameters, see Administration and Security,

323-1851-301, and Fault Management - SNMP, 323-1851-740.
Also refer to the data communications planning in Data Communications
Planning and User Guide, 323-1851-101, for information on data
communication parameters, setting the interface IP addresses, and
external and internal routing protocol settings.
For the PECs of the circuit packs used in Table 1-2 on page 1-8, refer to
Planning - Ordering Information, 323-1851-151.
• For the Node Setup application, see Table 2-6 on page 2-47.
Table 1-2
Provisioning information for each network element—SLAT Assistant Tool
Parameter Value Description Mandatory
NE Identification (Note 1)
NE Type OBP, OCP, COP, CCA, Network element equipment type: read only
CNE OBP-Optical Broadband Platform
OCP-Optical Convergence Platform
COP-Consolidated Optical Platform
CCA-Consolidated Channel Access
CNE-Converged network element
Release RELxxxxx.xx Release of NE software running on shelf read only
processor, where xxxxx.xx represents an
alphanumeric value representing the
software version running on the shelf
processor.
NE Name 1 to 20 alphanumeric Can include any combination of upper and yes
characters lower case letters, numbers, or special
characters excluding the following
characters: backslash (\), space,
double-quote ("), colon (:), semicolon (;),
ampersand (&), greater than (>), less than
(<), percent (%), or comma (,).
OneControl supports the following special
characters _+@-^~/.$%*#!()=[]{}’?|‘ in the TID
for the 6500 Site Manager craft launch. Do
not use special characters not supported in
an NE TID if you want to launch the 6500 Site
Manager craft from OneControl.

Table 1-2
Provisioning information for each network element—SLAT Assistant Tool (continued)
Extended NE 1 to 64 alphanumeric Can include any combination of upper and no
Name characters lower case letters, numbers, or special
(<), percent (%), or comma (,).
CLLI Up to 11 11-character alphanumeric code in the form no
characters CCCCSSBBUUU where:
• CCCC denotes the city, town, or locality
code
• SS denotes the geographical area (for
example, state or province code)
• BB denotes the building code or network
site
• UUU denotes the network entity or unique
traffic unit identifier
The combination of these codes comprise a
unique place, a unique building, and a
specific entry.
The CLLI cannot include special characters
but can include spaces. Spaces are included
in the length of the CLLI.
NE Configuration - IPv4 tab (Note 1)
Shelf Number 1 to 254 Shelf identifier of the shelf. Must be unique yes
within a site.
Photonic shelves (6500 and/or CPL) at a
given site (with the same Site ID) must have
unique logical shelf numbers (also referred to
as Shelf ID), regardless of node name (TID).
Note: A Photonic shelf refers to a shelf with
an OTS provisioned on it.
IPv4 Shelf IP standard dot notation Also known as circuitless IP address. yes
Address

Table 1-2
Site ID 0 to 65535 Identifier of the site. Must be the same for all yes for
NEs within a site. photonic
For photonic network designs, as per One services
Planner guidance, the Site ID must be unique
across the network, meaning different sites
need to use unique Site IDs. Within a Site, for
service shelves connected to the photonic
shelves, all shelves should use the same Site
ID or use different Site IDs but be in the same
Site Group.
Note: The setting of the Site Group is not
available from the SLAT Assistant Tool. Refer
to the ‘Node information’ section in
Administration and Security, 323-1851-301
for more information.
In order for Visualization to work properly, the
Site ID on non-photonics shelves should be
set to match the Site ID of photonic shelves at
the same site.
Note: For SPLI, alarm correlation, and OTS
management to function, the Site ID must be
provisioned to a non-zero value.
Site Name up to 20 characters Unique text string assigned to the site. no
Location up to 64 alphanumeric The location (latitude and longitude) no
characters associated with the selected shelf. The
preferred format is as follows (note that there
is no space following the comma):
<latitude>,<longitude>
where
<latitude> = -90.000000 to +90.000000 ("+"
optional)
<longitude> = -180.000000 to +180.000000
(“+” optional)
TID DISABLE or ENABLE Enables/disables TID consolidation for the yes for
Consolidation NE. photonic
For Control Plane considerations, see Note services
14. (channel
access nodes
only)

Table 1-2
TID DISABLE or ENABLE Identifies if the NE is a TID consolidation yes for
Consolidation primary. photonic
Primary For Control Plane considerations, see Note services
14. (channel
access nodes
If you are commissioning the Primary shelf of only)
a TIDc that will be managed by OneControl, it
is preferable to enable the SNMP proxy, see
“SNMP Provisioning (Note 4)” on page 1-23.
NE Mode SONET, SDH, SDH-J Software mode of network element. yes
IPv4 ON, OFF You must enable either IPv4, or IPv6, or both. see the
If IPv4 is enabled (ON), you must provision Description
the IPv4 shelf IP address. If IPv4 is not
enabled (OFF), do not provision the IPv4
shelf IP address.
If IPv6 is enabled (ON), you must provision
shelf IP address.
IPv6 ON, OFF You must enable either IPv4, or IPv6, or both. see the
If IPv4 is enabled (ON), you must provision Description
shelf IP address.
If IPv6 is enabled (ON), you must provision
shelf IP address.
IPv6 Hop Limit 1 to 255 Sets the IPv6 hop limit. no
Default is 90.
IPv6 Capable YES, NO Indicates whether the NE is IPv6 capable or read only
not.
If the value is NO, IPv6 tabs are not be
displayed in the SLAT tool and the user
cannot perform any IPv6 related provisioning.
The SLAT tool allows IPv6 related
provisioning only if IPv6 Capable is YES.
GCC0 Mode DISABLED, IISIS, Controls the auto-provisioning behavior of no
OSPF the GCC0 comms channel. Default =
Disabled.

Table 1-2
NDP mode DISABLED (default), Controls the auto-provisioning behavior of no
ENABLED the NDP feature.
If the value is Disabled, there is no action
performed. If the value is enabled, the
NDPMODE is used to auto provision an NDP
link on a GCC0 channel (when a facility is
created). It also enables the NDP feature the
first time a facility is created.
Alarm ON (default), OFF Indicates whether the alarm correlation no
Correlation feature is enabled or disabled.
Bay number 0 (unprovisioned) to 25 Unique number assigned to the bay. no
Not supported.
Frame up to 21 alphanumeric Unique text string assigned to the equipment. no
identification characters
code
Subnet name up to 36 alphanumeric Unique text string assigned to each shelf. no
characters
Shelf Synch YES/NO Enables (YES) or disables (NO) shelf synch no
between the primary shelf and the member
shelves.
Air Filter ENABLE, Enable or disable the “Filter Replacement no
Replacement DISABLE (default) Timer Expired” alarm.
Alarm
Air Filter 0 to 1826 (default 731 Sets the number of days before the “Filter no
Replacement or 730) Replacement Timer Expired” alarm is raised.
Timer (in Days) See Note 13.
Provisioned shelf dependent value Determines the provisioned shelf amperage. no

Shelf Current
(in Amps)
Auto Delete on • YES This parameter is not supported in this no
LOS • NO (default) release, and must be left at the default of NO.
Auto Facility • OFF Determines whether facilities are no

Provisioning • ON automatically provisioned at the time when
the associated equipment is provisioned.
• ON: Facilities are automatically provisioned
if possible.
• OFF: No facilities are automatically
provisioned.
For an OSMINE-managed system, you must
set Auto Facility Provisioning to OFF.

Table 1-2
TCA • ENABLED Determines whether TCA suppression is no
Suppression • DISABLED (default) enabled or disabled.
CS Control • ENABLED Determines whether Coherent Select no

• DISABLED provisioning is enabled or disabled at a nodal
level.
Note: The CS Control value can be changed
on a primary or member shelf of a
consolidated node. However, if Shelf Synch is
enabled, the CS Control parameter cannot be
edited on a member shelf. If the CS Control
parameter is changed on a primary shelf, it
broadcasts the value to all member shelves.
Auto OSC/ • OSPF (default) Defines whether the OSC will be provisioned no
OSPF • DISABLED or not when the SFP on the 2xOSC or
Provisioning SPAP-2 w/2xOSC circuit pack is provisioned.
For more information, see the section on
Optical Service Channel (OSC) interface in
Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
Default Control Flexible Grid Capable, Sets the default control mode. Any newly no
Mode Fixed ITU (default) provisioned ROADM or COADM OTSs use
the provisioned value. Value for individual
OTSs can be edited using the OTS
management application, see Part 2 of
Configuration - Provisioning and Operating,
323-1851-310, for details.
Note: All TIDc nodes in the network must be
set to Flexible Grid Capable before Flexible
Grid can be implemented.
Default 0-4800, default is 6.250 Sets the default filer edge spacing each side no
Filter-edge of a media channel (MC). Any newly
Spacing (GHz) provisioned MCs use the provisioned value.
TL1 Gateway DISABLED (default), Specifies the TL-1 gateway function as no
GNE ENABLED enabled or disabled. If enabled, the node can
forward TL-1 commands to a remote node.
TL1 Gateway DISABLED (default), Indicates whether or not the node accepts no
RNE ENABLED TL-1 sessions from a TL-1 gateway. If
disabled, the node will not accept TL-1
gateway connections.

Table 1-2
ETH 10G • 10.7G - GFP/OPU2 Determines the system-wide default ETH10G no
Mapping (Standard/MAC mapping when an ETTP or Mapped ETTP
transparent) [default] facility (with a rate of ETH10G) is created.
• 10.7G - GFP/OPU2+7 When set, this parameter does not impact
(Preamble/Ordered existing ETTP and Mapped ETTP facilities.
Set/MAC transparent)
• 11.09G - OPU2e
(PCS transparent)
Line Flapping 30 to 600 Indicates how long (in seconds) the line must no
Alarm Clear (default is 600) be error free to clear the Line Flapping alarm.
Time (30-600 Note: This parameter is only editable if the
Secs)
Line Flapping Alarm parameter is set to
Disabled first. If it is enabled, then disable it,
change the Line Flapping Alarm Clear Time
value, and re-enable the alarm.
Line Flapping • DISABLED (default) Determines whether the Line Flapping alarm no
Alarm • ENABLED is enabled or disabled.
Line Flapping 30 to 600 Indicates the hold-off period (in seconds) no

Alarm Raise (default is 300) before the Line Flapping alarm is raised if the
Time (30-600 Line Flapping Alarm Threshold is met.
Secs) Note: This parameter is only editable if the
change the Line Flapping Alarm Raise Time
Line Flapping 2 to 10 (default is 3) Indicates the number of failure events that no
Alarm must occur within the Line Flapping Alarm
Threshold Raise Time period before the Line Flapping
alarm is raised.
Note: This parameter is only editable if the
change the Line Flapping Alarm Threshold
OTN Path Wait • 0 Determines the wait to restore time (in no
To Restore • 1 to 12 in 1-minute minutes) used by all ASNCP and SNCP
Time (in Mins) increments (default 5) Protection Groups (PG).
• 15 The value cannot be over-ridden on a per PG
basis.
• 30
• 60

Table 1-2
Alarm Info Checkboxes: Determines whether enhanced alarm no
• Disabled reporting is enabled or disabled. When
enabled, depending on the option(s)
• Card Type selected, additional details are displayed in
• Wavelength the corresponding columns in the information
• Frame Identification table, “Alarm details” field, and “Event details”
Code field of the Site Manager Active Alarms,
Historical Fault Browser and Consolidated
• Subnet Name Alarms applications.
• Physical Shelf ID • Disabled: disables enhanced alarm
• Bay Number reporting, and “-” is displayed in the
• Label columns/fields below:
• CLFI • Card Type: Populates “Card Type” column.
• Name • Wavelength: Populates “Wavelength”

column.
• Frame Identification Code: Populates
“Frame Identification Code” column.
• Subnet Name: Populates “Reporting
Subnet” column.
• Physical Shelf ID: Not supported in this
release.
• Bay Number: Not supported in this release.
• Label: Populates “CLFI” column with label
associated with TCM and PKT/OTN
transport and switched services facilities.
• CLFI (Common Language Facility
Identifier): Populates “CLFI” column.
• Name (SNC name): Populates “Additional
Information” column with optional SNC
Name for all OTN Control Plane
SNC-related alarms. For further information
on the SNC name parameter, refer to the
“SNC Name” section in the “L0 and L1
sub-network connections management”
chapter of Configuration - Control Plane,
323-1851-330.

Table 1-2
NE Configuration - IPv6 tab (Note 1)
Aid - Index Index: 1 to 254 Index-based AID for the IPv6 shelf address. yes - Only
Index can be
modified.
Type and
Shelf are
read-only.
Circuit SHELF-<1 to 255> Displays the shelf circuit identifier, which no (cannot be
includes the shelf number. changed)
IPv6 Shelf IP eight groups of four Also known as circuitless IP address. yes
Address hexadecimal digits
separated by colons, as
per RFC 4291
Prefix 128 The IPv6 prefix for the shelf interface. The no (cannot be
only valid value is 128 (this is a host changed)
interface).
GNE Configuration - IPv4 tab
GNE YES, NO Specifies whether the shelf is a GNE. no
Single Shelf IP YES, NO Defines whether shelf IP address should no
equal the COLAN IP address.
GNE Group integer (1-255) Specifies the redundancy group that the GNE yes only if
belongs to for master/backup negotiation. configuration
is
REDUNDANT
ARP
Primary YES, NO Defines whether the NE is the primary or yes only if
secondary communication gateway. configuration
is
REDUNDANT
ARP
GNE up to 36 alphanumeric A unique name identifies the GNE, for yes if to be
Subnetname characters standalone or redundant private IP managed by
configurations. OneControl

Table 1-2
GNE Standalone ARP, Based on the selected comms configuration, yes
configuration Redundant ARP, some GNE parameters are blocked.
radio button
Redundant NAT,
Standalone OSPF,
Redundant OSPF,
Standalone Static,
Standalone Private IP,
Redundant Private IP
GNE Configuration - IPv6 tab
GNE YES, NO Specifies whether the shelf is a GNE. yes
GNE Standalone OSPFv3, Specifies the GNE type. yes
configuration Redundant OSPFv3,
radio button
Standalone Static,
Standalone ND Proxy
Auto Equipping
Enabled slots slots 1, 2, and 15, 25, Slots equipped with 2x10G OTR and MOTR yes
27, 83-90 for 2-slot circuit packs must have auto-equipping
shelf enabled.
slots 1 to 7 and 15, 83 SONET and SDH-J NEs have all
to 90 for 7-slot shelf auto-equipping enabled by default.
slots 1 to 16, 83 to 90
for 14-slot shelf
slots 1 to 18, 21 to 28,
31 to 38, 41 and 42, 51
to 62 for 32-slot shelf
slots 1-8, 15, 16, and 83
to 86 for 6500-7
packet-optical shelf
select all, deselect all

Table 1-2
OSPF Router Provisioning - IPv4 tab and IISIS Router Provisioning (applies to IPv4 only)—see
Table 1-3 on page 1-27.
Before performing the provisioning steps, refer to the data communications planning in Data
Communications Planning and User Guide, 323-1851-101, in order to understand the specific DCN
configuration.
If you will be provisioning OSPF/IISIS router during the Shelf IP, COLAN, or DCC Provisioning SAT
steps, you do not have to provision the router at the OSPF Router Provisioning or IISIS Router
Provisioning step. The OSPF/IISIS router provisioning during the Shelf IP, COLAN, or DCC Provisioning
SAT steps overwrites the router provisioning performed at the OSPF Router Provisioning or IISIS Router
Provisioning step.
OSPF Router Provisioning - IPv6 tab—see Table 1-4 on page 1-31
ILAN Provisioning - IPv4 tab (Note 4 and Note 12)
Aid Index - 1 to 254 Instance-based AID. see Note 2
IP Address and standard dot notation ILAN IP address and subnet mask. and Note 10
Subnet Mask
Port Enabled YES, NO Enables or disables the port.
See Note 16.
Routing NONE, OSPF, IISIS, If OSPF, IISIS, or OSPF/IISIS is selected, see Note 8
Protocol OPSF/IISIS you must provision the corresponding circuit
parameters (see Table 1-3 on page 1-27).
ILAN Provisioning - IPv6 tab (Note 4 and Note 12)
Aid - Index Index: 1 to 254 Instance-based AID. yes
Circuit ILAN-shelf-port Specifies which ILAN port. no
IP Address Eight groups of four IPv6 address to assign to ILAN interface. yes
hexadecimal digits
per RFC 4291
IP network 1 to 128 The IPv6 prefix associated with the IPv6
prefix address of the ILAN interface.
Port Enabled NO (default), YES Specifies whether port is enabled or not. no
See Note 16.
Routing NONE, OSPFv3 If OSPFv3 is selected, you must provision the see Note 8
Protocol corresponding circuit parameters (see Table
1-4 on page 1-31).

Table 1-2
Shelf IP Provisioning - IPv4 tab
IP Address and standard dot notation Also known as circuitless IP address and see Note 2
Subnet Mask subnet mask.
Routing NONE, OSPF, IISIS, If OSPF, IISIS, or OSPF/IISIS is selected,
Protocol OSPF/IISIS you must provision the corresponding circuit
Shelf IP Provisioning - IPv6 tab
Aid - Index Index: 1 to 254 Instance-based AID. yes
Circuit NONE, OSPFV3 If OSPFV3 is selected, you must provision yes
the corresponding circuit parameters (see
Table 1-4 on page 1-31).
IPv6 Shelf eight groups of four IPv6 address to assign to shelf. yes
Address hexadecimal digits
per RFC 4291
Prefix 128 The IPv6 prefix for the shelf IP address is yes
always 128.
Routing None, OSPFv3 Specifies whether OSPFv3 is enabled on the
protocol interface.
IISIS Router Provisioning (applies to IPv4 only) (see Table 1-3 on page 1-27)
COLAN Provisioning - IPv4 tab (Note 4 and Note 5) (see Table 1-3 on page 1-27 for complete list
of parameters)
Access COLAN-shelf-port COLAN port access identifier. yes
Identifier (AID)
IP Address and standard dot notation COLAN IP address and subnet mask. see Note 2
Subnet Mask and Note 6
Proxy ARP ON, OFF Enables or disables the proxy ARP on the see Note 5
COLAN port. and Note 7
Port Enabled YES, NO Enables or disables the port. no
See Note 16.
Routing NONE, OSPF, IISIS, If OSPF, IISIS, or OSPF/IISIS is selected, see Note 2
Protocol OSPF/IISIS you must provision the corresponding circuit and Note 6
COLAN Provisioning - IPv6 tab (Note 4 and Note 5) (see Table 1-4 on page 1-31 for complete list
of OSPFv3 parameters.)
Aid (Access IPADDR-shelf-index, Index-based AID for the COLAN IP address. yes
Identifier) where index is 1 to 254
Circuit COLAN-shelf-port, COLAN circuit identifier. yes
where port is X or A

Table 1-2
IP Address eight groups of four COLAN IPv6 address. yes.
hexadecimal digits See Note 2
separated by colons, as and Note 6
per RFC 4291
IP network 1 to 128 The IPv6 prefix associated with the IPv6 yes
prefix address of the COLAN interface.
Port Enabled NO (default), YES Enables or disables the port. no
See Note 16.
Routing NONE, OSPFv3 If OSPFv3 is selected, you must provision the see Note 2
Protocol corresponding circuit parameters (see Table and Note 6
1-3 on page 1-27).
ARP/ND Proxy Provisioning - IPv4 tab
Start and End standard dot notation Proxy ARP IP address(es). see Note 2
proxy ARP IP and Note 7
addresses
ARP/ND Proxy Provisioning - IPv6 tab
Aid (Access NDPROXY-shelf-index, Index-based AID of the ND Proxy entry. yes
Identifier) where index is 1 to 150
Circuit COLAN-shelf-X COLAN-X port yes
IPv6 Address eight groups of four IPv6 address to add to ND Proxy table. yes. See Note
hexadecimal digits 2 and Note 6
per RFC 4291
Network address translation (NAT) Provisioning
DCN IP standard dot notation DCN IP address. see Note 2
Address
Remote NE IP standard dot notation Shelf IP address.
Address
Prime YES Indicates whether the shelf IP address is
used for mapping of incoming packets.
Dynamic NAT Provisioning
NAT Starting 1024 to 65535 Sets the base UDP/TCP port value no
Port dynamically allocated for connections flows
managed by NAT services. It applies to
Redundant NAT and Private IP GNEs.
Note: If not specified, the current value is not
changed. If never configured, the default is
50000.

Table 1-2
NAT Number 256 to 1024 Specifies the number of UDP/TCP port no
Of Entries values dynamically allocated for connections
flows managed by NAT services. It applies to
Redundant NAT and Private IP GNEs.
Note: If not specified, the current value is not
changed. If never configured, the default is
512.
Port Filtering Provisioning
Access COLAN-shelf-port COLAN port identifier. yes
Identifier (AID)
Action PERMIT, BLOCK The action to be taken when IP packets yes
match the filter rule.
Location REMFORWARDOUT, Sets the location of the filter rule for the yes
INGRESS provisioned port.
Protocol TCP, UDP Displays which type of the protocol is yes
applicable to the remote NE port.
Destination 1 to 65535 Sets the start of the blocked or permitted port yes
Start Port of the protocol type.
Destination 1 to 65535 Sets the end of the blocked or permitted port yes
End Port of the protocol type.
Reverse Port NAT provisioning
Access shelf-number Shelf access identifier. yes
Identifier (AID)
DCN Port 1 to 65535 Sets the external port which is being mapped. yes
RNE IP Standard dot notation Sets the Private IP of the remote NE. yes
Address
Remote NE HTTP, Secure HTTP, Sets the type of service that supports the yes
Service FTP, NNCLI (Telnet), remote NE.
NNCLI (SSH),
TL1 (Telnet),
TL1 (SSH), SNMP
RNE Port 1 to 65535 Displays the internal port which is being yes
mapped.
Protocol TCP, UDP Displays which type of the protocol is yes
applicable to the remote NE port.
NDP Provisioning
Aid shelf-number Shelf access identifier. yes
Admin State ENABLED, DISABLED Enables or disables the NDP feature at a yes
(default) shelf level.

Table 1-2
Static Routes Provisioning - IPv4 tab
IP Address and standard dot notation IP address and subnet mask of the static yes
Subnet Mask route. see Note 2
Next Hop standard dot notation IP address of the next hop. and Note 11
Circuit COLAN, ILAN ports Port used to get to the next hop.
Cost 1 to 65535 Cost of the link.
Carrier Section/RS, line/MS, Sets the DCC/GCC channel used, section/ yes
GCC0, GCC1 RS, line/MS, GCC0 or GCC1 (options
available depend on circuit pack type and
function).
Description 1 to 64 characters Label for the static route. no
Static Routes Provisioning - IPv6 tab
Aid STATICRT-shelf-index, Index-based AID of the static route. yes
where index is 1 to 80
IP Address eight groups of four IPv6 address of the static route. yes
hexadecimal digits see Note 2
separated by colons, as and Note 11
per RFC 4291
IP network 0 to 128 The IPv6 prefix associated with the IPv6 yes
prefix address of the static route.
Next Hop eight groups of four IPv6 address of the next hop. no
hexadecimal digits
per RFC 4291
Circuit COLAN, ILAN ports Port used to get to the next hop. yes
Cost 1 to 65535 Cost of the link. yes
Carrier Section/RS, line/MS, Sets the DCC/GCC channel used, section/ yes
GCC0, GCC1 RS, line/MS, GCC0 or GCC1 (options
available depend on circuit pack type and
function).
description 1 to 64 characters Optional description of the static route. no
redistribute OFF, OSPFV3 Specifies whether to redistribute the static no
route into OSPFv3.
rdtype INTERNAL, If redistributing into OSPFv3, specifies the no
EXTERNAL type of metric used. Internal uses Type-1
metric, External uses Type-2 metric.
OSPF - Routes Distribution / IISIS - Routes Distribution (applies to IPv4 only)—see Table 1-3 on
page 1-27

Table 1-2
SNMP Provisioning (Note 4)
Agent state ENABLED, DISABLED Enables or disables SNMP. yes
Version alphanumeric Indicates the version of the SNMP. no
characters
Alarm Masking On, Off Enables or disables alarm masking. no
Proxy On, Off Enables or disables SNMP proxy – option no
disabled for standalone NEs and member
shelves. Proxy can only be enabled when the
primary shelf is 6500.
If you are commissioning the Primary shelf of
is preferable to enable the SNMP proxy.
Request numeric value Timeout value for SNMP requests – option no
Timeout disabled for standalone NEs and member
shelves.
Destination alphanumeric Indicates the trap destination. no
characters
IP Address For IPv4, standard dot Trap destination IP address. no
notation.
For IPv6, eight groups
of four hexadecimal
digits separated by
colons, as per RFC
4291.
UDP port 1 to 65535 The user datagram protocol (UDP) port. no
Version V1, V2C, V3 Version of trap to be sent. no
For V3, see Note 15.
UAP PUBLIC, SYSADMIN, User access privilege of the V2 user to be no
OBSERVER, used to send traps.
CUSTOMER1,
CUSTOMER2,
OPERATOR
UID alphanumeric The SNMP V3 user if version is specified as no
characters a V3 trap. See Note 15.
The user information used to send traps.

Table 1-2
TRAP DISABLE, Disables or enables TL-1 traps and/or SAOS no
Configuration ENABLE_ALL, traps on a per receiver basis.
TL1_TRAPS_ONLY, For V1 or V2c version, only TL-1 traps are
SAOS_TRAPS_ONLY supported. Therefore, only
TL1_TRAPS_ONLY and DISABLE options
are valid.
For V3 version, both TL-1 and SAOS traps
are supported. Therefore, all options are
valid. Also see Note 15.
Security Provisioning
Password Standard, Complex, Sets the password creating rules to standard, no
Rules Custom complex, or custom.
ADMIN/ alphanumeric Sets the password for Admin user or Surveil no
SURVEIL characters user.
New Password
Confirm New
Password
SSH/TELNET and HTTP/HTTPS Server Provisioning
SSH Server ENABLED, DISABLED Set the status of the SSH server. no
Active State Note: An SSH server cannot be disabled
unless a telnet server is enabled.
Maximum SSH 1 to 18 (default 5) Indicates the maximum number of concurrent no
Active SSH sessions that are allowed to the network
Sessions element.
SSH Idle 0 to 99 (default 30) Sets the time (in minutes) before an idle SSH no
Timeout session is disconnected. A value of 0
(minutes) indicates infinite (no timeout).
Telnet Server ENABLED, DISABLED Set the status of the Telnet server. no
Active State Note: An SSH server cannot be disabled
unless a telnet server is enabled.
Maximum 1 to 18 (default 18) Sets the maximum number of concurrent no
Telnet Active Telnet sessions that are allowed to the
Sessions network element.
Note: If both SSH and telnet servers are
enabled, the total of maximum number of
SSH and telnet sessions must not exceed the
system maximum number of sessions (18).
Telnet Idle 0 to 99 (default 30) Sets the time (in minutes) before an idle no
Timeout Telnet session is disconnected. A value of 0
(minutes) indicates infinite (no timeout).

Table 1-2
HTTP Server ON, OFF Sets the status of the HTTP server. no
Active State
HTTPS Server ON, OFF Sets the status of the HTTPS server. no
Active State
Craft Access Provisioning—see Table 1-3 on page 1-27 for IPv4 and Table 1-4 on page 1-31 for
IPv6
Aid LAN-15/16/41/42 or as Craft port AID. yes
applicable for shelf
types
IP Address and standard dot notation Craft LAN port IP address and subnet mask. no
Subnet Mask See Note 2
and Note 3.
IPV4 Server ON (default), OFF Sets the IPV4 server on or off. no
State
IPV6 Server ON, OFF (default) Sets the IPV6 server on or off. no
State
Host Only ON, OFF (default) Sets the host only mode. The Host Only no
Mode Mode option is displayed in Site Manager, but
is not supported in this release.
Port Enabled YES, NO Indicates if the port is enabled. no
Craft OSPF/IISIS Provisioning—see Table 1-3 on page 1-27 for IPv4 and Table 1-4 on page 1-31
for IPv6

Table 1-2
Note 1: Various SAT panels also include other parameters, which are either read-only or not mandatory
to provision at the commissioning stage. For more information on parameters, see Part 1 of
Configuration - Provisioning and Operating, 323-1851-310.
Note 2: For more information about data communications engineering rules, refer to Data
Communications Planning and User Guide, 323-1851-101.
Note 3: Craft IP address is required only if you want the ability to access remote network elements using
the LAN-15 (or 41) port. Assign unique IP addresses to each LAN-15 (or 41) port in the system. Do not
use 10.0.0.1.
Note 4: The number immediately following OTM2, COLAN, ILAN, and DEST indicates the shelf number.
Note 5: If you want ARP Proxy enabled on the COLAN port, you must select ARP Proxy ON in the
COLAN Provisioning step.
Note 6: COLAN provisioning is required only if COLAN is connected directly to the DCN (The COLAN
Provisioning step becomes highlighted only if in the COLAN & GNE Configuration step you have
selected an option where COLAN is connected to the DCN.).
Note 7: Proxy ARP and ND Proxy are only supported on the COLAN-X port.
Note 8: ILAN provisioning is required only if you intend to use ILAN. There are two ILAN ports defined
on a 6500 NE, namely ILAN-IN and ILAN-OUT.
Note 9: If you select the OSPF or OSPF/IISIS (IPv4 only) routing protocol and the Shelf IP address is
not defined on the NE, a warning message will be displayed to first define the Shelf IP address and the
operation will be aborted.
Note 10: The NSAP is up to 40 characters depending on the first 2 characters (AFI). For example, for
an AFI of 49, the range is 20 characters (6 characters for area address, 12 characters for system id, and
2 characters for network selector). The network selector (NSEL, last 2 bytes of NSAP) of the provisioned
NSAP destination address must be set to ‘00’ (6500 internally automatically sets the NSEL to support
the required transport service).
Note 11: Static routes provisioning is required only if the network element is connected directly to DCN
and OSPF is not configured on the COLAN interface.
Note 12: An OSC channel can be used instead of ILAN to connect shelves that are located at a distance
greater than 100 m. For engineering rules, refer to Data Communications Planning and User Guide,
323-1851-101.
Note 13: The default value for the air filter replacement timer is not displayed [the field displays empty]
as long as the NE is not commissioned. The field can be provisioned only after the shelf IP is defined.
Note 14: In this release. there can only be a single Photonic OSRP instance within a TIDc. That is, for
each TIDc, there can only be a single SONET/SDH, OTN, or Photonic Control Plane OSRP instance.
L1 SONET/SDH or OTN Control Plane shelves can be either Primary or Member TIDc shelves. L0
Control Plane shelves must be Primary TIDc shelves only. Refer to the “TID consolidation (TIDc)” section
in the “Node information” chapter in Administration and Security, 323-1851-301, for details about Control
Plane considerations for TIDc.
Note 15: SNMPv3 on the current release of 6500 does not have any usable SNMPv3 USM users by
default. To access the node via SNMP v3, you must log into Site Manager via the Craft port after the
node is set up and create a USM user. For more information, see Fault Management - SNMP,
323-1851-740.
Note 16: If you are provisioning both IPv4 and IPv6 on the LAN ports (ILAN or COLAN), set the same
value for this parameter for both IPv4 and IPv6, that is, either YES (enabled) or NO (disabled).
Otherwise, the enabled/disabled provisioning of one protocol can overwrite the other.

Table 1-3
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4
Parameter Value Description
OSPF router parameters
OSPF Router ID standard dot notation Sets the router ID for the OSPF.
It is recommended that the SHELF IP address (if
provisioned) is used as the OSPF router ID.
Route On (default), Off Sets whether routes or route summaries (On) are
Summarization redistributed.
Autonomous On, Off (default) Sets the autonomous system border router (ASBR). ASBR
System Border identifies whether an OSPF router can accept input (route
Router redistribution) from another autonomous system such as
IISIS, or static routes.
Opaque Filter On, Off (default) Filters out OSPF Type-11 opaque LSAs (Address
Resolution [AR] and Topology Resolution [TR]) not required
by applications at a given site and within a given OSPF area,
in order to reduce memory consumption.
Shelf IP On, Off (default) Re-distributes a route to the local shelf IP into all OSPF
Re-distribution areas that the shelf participates in.
IISIS router parameters
Router Level Level1 (default) Sets the IISIS router level. Since level 2 is not supported in
Level 1 and 2 this release, “Level 2” is always disabled.
Level 1 Priority 0 to 127 (default 64) Sets the level 1 (L1) router priority. The L1 router with the
highest priority becomes the L1 designated router for that
LAN segment.
Level 2 Priority 0 to 127 (default 64) Sets the level 2 router priority. The L2 router assigned the
highest priority becomes the L2 designated router for that
LAN segment.
Not supported in this release, option is disabled.
Route ON (default), OFF Sets whether routes (OFF) or route summaries (ON) are
Summarization redistributed.

Table 1-3
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)
OSPF circuit parameters
Name COLAN-shelf-A, Displays the ports available for OSPF.

COLAN-shelf-X,
ILAN-shelf-IN,
ILAN-shelf-OUT,
LAN-shelf-15 (or 41),
SHELF-shelf,
OSC-shelf-slot-port,
OTMn ports,
OTUTTP/ ODUTTP/
ODUCTP AID
IP Address and standard dot notation When adding an OSPF router, sets the IP subnet address,
Subnet Mask and the subnet mask, respectively, for redistribution. Do not
use the default route of 0.0.0.0 (IP subnet 0.0.0.0 and subnet
mask 0.0.0.0). This route must not be statically provisioned,
and must not be learned through OSPF.
Routing Protocol NONE, OSPF, IISIS, Sets the routing defined for the network configuration.
or OSPF/IISIS
Carrier GCC0, GCC1 Sets the GCC on the OTMn/OTUTTP/ODUTTP/ODUCTP

port for the OSPF circuit.
Only applicable to OTMn/OTUTTP/ODUTTP/ODUCTP
ports.
Network area standard dot notation Sets the area (defaults to backbone area of 0.0.0.0).
Cost 1 to 65534 Sets the cost of the route (reflects speed of interface)
Defaults are as follows:
• SHELF: 0 (cannot be changed)
• LAN-shelf-15 (or 41), LAN-shelf-16 (or 42), COLAN, ILAN:
10
• GCC0/1 on OTM1: 303
• GCC0/1 on OTM2: 75
• GCC0/1 on OTM3: 19
• GCC0/1 on /OTUTTP/ODUTTP/ODUCTP: 75
Dead interval 1 to 65535 Sets the interval (in seconds) at which hello packets must
(default 40) not be seen before neighbors declare the router down
Hello interval 1 to 65535 Sets the interval (in seconds) between the hello packets that
(default 10) the router sends on the interface

Table 1-3
Retransmit 1 to 3600 (default 5) Sets the interval (in seconds) required between link state
interval advertisement retransmissions.
Note: It is not supported in this release
Transmit delay 1 to 3600 (default 1) Sets the estimated time (in seconds) to transmit a link state
update packet over this interface.
Priority 0 to 255 (default 1) Sets the router priority value used in multi-access networks
for the election of the designated router (0 indicates that
router is not eligible to become designated router)
Area Default Cost 1 to 16777215 Sets the cost of the route to the next area.
(default 1) Note: It is not supported in this release.
Area Off (default), NSSA, Sets whether the router is in a not so stubby area (NSSA) or
Stub stub area. NSSA and Stub are not supported in this release
Authentication Null, Simple Sets the type of password authentication performed on the
Type OSPF circuit.
Password Character string Sets the password if password authentication is selected.

(1 to 8 characters) Characters can be any combination of upper case, lower
case, numbers, or special characters.
Opaque Link State On, Off (default) Sets whether opaque link state advertisement performs on
Advertisement the OSPF circuit.

Table 1-3
IISIS circuit parameters
Name SHELF-shelf, Displays the available ports for an IISIS circuit.

LAN-shelf-15 (or 41), Only OTMn/OTUTTP/ODUTTP/ODUCTP ports with GCC0/
LAN-shelf-16 (or 42), GCC1 provisioned are available for selection.
COLAN-shelf-A,
COLAN-shelf-X, IISIS over the GRE interfaces is not supported in this
ILAN-shelf-IN, release.
ILAN-shelf-OUT,
GRE-shelf-IP-1 to 4,
OTMn ports,
OTUTTP/ ODUTTP/
ODUCTP AID
Carrier GCC0, GCC1 Displays the GCC used, GCC0 or GCC1 (options available
depend on circuit pack type and function).
Circuit Metric 1 to 63 Sets the circuit default metric used to calculate the best
route. Default depends on type of interface as follows:
• SHELF, LAN-shelf-15 (or 41), LAN-shelf-16 (or 42),
COLAN, ILAN, GRE-IP: 4
• OTMn ports with GCC0/GCC1 provisioned: 5
• OTUTTP/ODUTTP/ODUCTP: 5
Select a higher value for a slower circuit.
Level 2 Only On, Off (default) Sets the status of level 2 only routing on the IISIS circuit.
Not supported in this release, On option is always disabled
three way On, Off (default) Sets the status of 3-way handshaking on the IISIS circuit.
handshake Not supported in this release, On option is always disabled.
Neighbor Off (default), IP, OSI, Sets the protocols supported on neighbor routers (overrides
Protocols IP and OSI what the router advertises).
Supported (NPS) Must be set to OSI if the lower layer Protocol parameter is
Override set to LAPD.
The “IP” and “IP and OSI” options are not supported.

Table 1-3
OSPF—Routes Distribution
IP Address and standard dot notation When adding an OSPF router, sets the IP subnet address,
Subnet Mask and the subnet mask, respectively, for redistribution. Do not
use the default route of 0.0.0.0 (IP subnet 0.0.0.0 and subnet
mask 0.0.0.0). This route must not be statically provisioned,
and must not be learned through OSPF.
Metric 1 to 65535 When adding an OSPF router, sets the metric for
redistribution
Metric Type External (default), When adding an OSPF router, sets the metric type for
Internal redistribution
Distribution List Staticrdlist (default), When adding an OSPF router, sets the redistribution mode
Isisrdlist
IISIS—Routes Distribution
IP Address and standard dot notation Sets the IP subnet address and subnet mask, respectively,
Subnet Mask of the distribution list entry for the selected IISIS router. Do
not use the default route of 0.0.0.0 (IP subnet 0.0.0.0 and
subnet mask 0.0.0.0). This route must not be statically
provisioned, and must not be learned through OSPF.
Metric 1 to 63 Sets the metric (cost) of the distribution list entry for the
selected IISIS router.
Metric Type External (default), Sets the metric type of the distribution list entry for the
Internal selected IISIS router.
Distribution List Staticrdlist (default), Sets the IISIS router distribution list entries for the selected
Ospfrdlist IISIS router
Table 1-4
OSPFv3 parameters—SLAT Assistant Tool - IPv6
OSPFv3 router parameters
Router ID standard dot notation Sets the router ID for the OSPFv3 router.
The router ID must be unique within the OSPF network. If an
OSPFv2 router exists, the OSPFv3 defaults to the same
value as the OSPFv2 router ID.

Table 1-4
OSPFv3 parameters—SLAT Assistant Tool - IPv6 (continued)
OSPFv3 circuit parameters
OSPFv3 AID OSPFv3-shelf-index, index-based AID for the OSPFv3 circuit

where index is 1 to
256
Name COLAN-shelf-A, Displays the ports available for OSPFv3.

COLAN-shelf-X,
ILAN-shelf-IN,
ILAN-shelf-OUT,
SHELF-shelf
OSPFv3 Network standard dot notation Sets the area

area
Cost 1 to 65534 Sets the cost of the route (reflects speed of interface)
Defaults are as follows:
• SHELF: 0
• LAN-shelf-15 (or 41), LAN-shelf-16 (or 42), COLAN,
ILAN: 10
Dead interval 1 to 65535 Sets the interval (in seconds) at which hello packets must
(default 40) not be seen before neighbors declare the router down
Hello interval 1 to 65535 Sets the interval (in seconds) between the hello packets that
(default 10) the router sends on the interface
Retransmit interval 1 to 3600 (default 5) Sets the interval (in seconds) required between link state
advertisement retransmissions.
Transmit delay 1 to 3600 (default 1) Sets the estimated time (in seconds) to transmit a link state
update packet over this interface.
Priority 0 to 255 (default 1) Sets the router priority value used in multi-access networks
for the election of the designated router (0 indicates that
router is not eligible to become designated router)
Other customer provisioning information

If there are customer provisioning requirements, make sure that you have all
the necessary information.

2-1
Nodal SLAT procedures 2-
Nodal SLAT procedures describe how to bring a newly installed 6500 network
element to an in-service state ready to carry traffic. Make sure the SLAT
prerequisites listed in Chapter 1, “SLAT process overview” are met before
starting the Nodal SLAT procedures.
The 6500 also supports Zero Touch Provisioning (ZTP) which provides
automatic configuration for 6500 network elements (NE) once powered-up
and able to communicate on the network, thus removing the need for the user
to perform the nodal SLAT procedures. For more information, refer to Chapter
10, “Appendix C: Zero touch provisioning”.
This chapter also includes procedures to provision additional photonic

parameters and procedures to clone a golden database onto newly
commissioned network elements.

• “Abbreviations used in procedures” on page 2-1
• “Nodal SLAT procedures” on page 2-3
• “Fixed-band plan thin terminals” on page 2-9
• “Procedures” on page 2-26
Abbreviations used in procedures

BIP breaker interface panel
CS Coherent Select

2-2 Nodal SLAT procedures
DISP dispersion
DOC domain optical controller
EBER excessive bit error rate
eDCO electronic dynamically compensating optics
ID identifier
ILAN intershelf LAN
L2SS layer 2 service switch
LACP link aggregation control protocol
LED light emitting diode
NDP topology neighbor discovery protocol - topology
ND Proxy (or NDP in ND Proxy protocol

Proxy context)
NE network element
OCI optical channel interface
OCLD optical channel and laser detector

OTM optical transport module
PC personal computer
PDH plesiochronous digital hierarchy
PEC product engineering code
PM performance monitoring
Rx receive
SCMD serial channel mux/demux
SP shelf processor
TL-1 transaction language 1
TOADM thin optical add/drop multiplexer
Tx transmit
UPC user privilege code
WT wavelength translator
Nodal SLAT procedures

Table 2-5 on page 2-26 lists the procedures in this chapter. Refer to “Node
setup solutions” to select the solution for your configuration, then perform the
Preparation tasks, and finally perform the applicable turning-up procedure(s),
Quick-start turning-up - Node Setup procedure or Advanced SLAT Assistant
Tool (SAT) procedures (perform the Advanced SLAT procedures in the order
listed). Perform the Optional tasks in Procedure 2-29, “Post SLAT
commissioning”, as required.

Node setup solutions

6500 supports a high level of functional flexibility. This flexibility was
associated in previous releases with a high level of complexity surrounding the
commissioning of the 6500 into the network.
Two simplified solutions are supported:

• script-based commissioning solution—If a commissioning script file exists,
use this solution.
The script-based commissioning solution integrates with planning.
Planners can generate commissioning scripts, which can then be
distributed to the field technicians to apply to the shelf they are
commissioning. This process reduces significantly the possibility of data
entry errors when nodes are being commissioned, because the field
technician is now only selecting the appropriate script(s) for the shelf that
they are commissioning.
Note: Refer to the MCP User Guide for procedures on generating and
exporting commissioning scripts.
• Node Setup application or Advanced SLAT Assistant tool (see “Node

Setup application or Advanced SLAT Assistant tool” on page 2-4)
Node Setup application or Advanced SLAT Assistant tool

The Node Setup application is a simplified solution that enables setting up the
6500 network element in basic data communications (DCN) configurations in
a maximum of six easy steps. Based on the shelf type defined by the user, the
tool completes automatically the provisioning of several parameters.
Additional advanced NE Configuration options are also available, which can

be displayed by opening the Advanced Parameters panel where they can be
edited, if required.
ATTENTION
The Node Setup tool remembers the Advanced Parameter settings (NE
Configuration) and SNMP application settings. The tool automatically reuses
them when the next shelf is set up. The information is stored in the
slat_preferences.xml file at the following Site Manager installation location:
<user_home_dir>/.ciena_desktop/sitemanager/PREFERENCES/SM
If necessary, before you move on to setting up another network and/or

another TID, if the remembered values are not required, delete the
slat_preferences.xml file to restore the defaults. To share the preferences
with another user/computer, copy the xml file to the required computer.

The Node Setup application also uses the Single Public IP configuration. In
this configuration:
• The Shelf IP address must be DCN visible.
• The Shelf IP address and the COLAN-X IP address are normally the
same.
The Advanced SLAT Assistant Tool is available for users that require an
expanded set of parameters when commissioning network elements in more
complex configurations.
ATTENTION
The Advanced SLAT Assistant Tool remembers the NE Configuration system
parameter settings and SNMP application settings. The tool automatically
reuses them when the next shelf is set up. The information is stored in the

After the initial setup is complete using either the Node Setup application or
Advanced SLAT, more parameter provisioning can be applied by using Site
Manager menus. All the parameters are editable via Site Manager.
To select the turning-up solution for your configuration—script-based, Node

Setup, or Advanced SLAT—refer to Figure 2-1 on page 2-6.
For flowcharts of the quick-start Node Setup for each shelf type, see:
• Standalone shelf — Figure 2-2 on page 2-7
• Primary with Members shelf — Figure 2-3 on page 2-8
• Member shelf — Figure 2-4 on page 2-9
For examples of the solution provided by the Node Setup application for
network elements in various configurations, see “Appendix B: Quick-start
turning-up using the Node Setup application—examples” on page 9-1.

Figure 2-1
Selecting the turning-up solution for a newly installed system
Yes Is a commissioning script available?
Use the script-based commissioning solution No
Yes No
Is the DCN configuration one of the
following?
Direct Connect
DCN: 1.x.x.x
 Single shelf TIDs

 Dedicated DCN LAN drop per TID
 DCN routable IP address per shelf
COLAN X
1.2.2.2 NE1
RJ45-Ethernet
or
Gateway Connect
DCN: 1.x.x.x
 Dedicated DCN LAN drop per GNE
 DCN routable IP address per shelf
GNE
COLAN X
Shelf 1 1.3.3.2
TID A (Primary)
ILAN / OSPF GNE Proxy ARP GNE

Shelf 3
1.3.3.3 Shelf 2 1.3.3.4 (Member)
(Member)
TID A
TID A
Use the Node Setup application

For Standalone shelf, see Figure 2-2 on page 2-7.
Yes For Primary with Members shelf, see Figure 2-3 on page 2-8.
For Member shelf, see Figure 2-4 on page 2-9.
No
Use the Advanced SLAT Assistant Tool

Figure 2-2
Quick-start turning-up of a Standalone shelf using the Node Setup application (NE1 in Figure 2-1
on page 2-6)
Preparation “Powering up a new network element and

task connecting a craft computer” (Procedure 2-1)
Quick-start turning-up of a Standalone shelf using Node Setup (Procedure 2-4)
If the Node Setup application

Launch Site Manager.
did not open, go to
Procedure 2-2 “Checking the
current software release” to
No check your current software
Does the Node Setup application open? release, then restart
Procedure 2-4 “Quick-start
Yes (SP has the correct turning-up using the Node
software release) Setup application” as
instructed in Procedure 2-2
Node Setup
NE Identification “Checking the current
Steps
software release”.
In addition to the basic

NE Configuration parameters, Advanced
Proxy ARP GNE Parameters are available with
can also be set up, initial values, can be edited as
depending on future required, and are
development plans. COLAN Provisioning
automatically populated when
setting up the next shelf.
(optional)
SNMP Provisioning
(optional)
Note: After completing the basic

Basic setup complete. setup, more provisioning can be
done via Site Manager (optional).
To complete turning-up, seat required circuit packs and check for alarms.
(Procedure 2-4 “Quick-start turning-up using the Node Setup application” will instruct you
to use step 9 to step 20 in Procedure 2-2 “Checking the current software release”.)

Figure 2-3
Quick-start turning-up of a Primary with Members shelf using the Node Setup application
Preparation “Powering up a new network element and connecting a craft

task computer” (Procedure 2-1)
Quick-start turning-up of a Primary with Members shelf using Node Setup (Procedure 2-4)

Launch Site Manager. did not open, go to
Procedure 2-2 “Checking the
No check your current software
Does the Node Setup application open? release, then restart
Procedure 2-4 “Quick-start
turning-up using the Node
(SP has the correct
Yes Setup application” as
software release)
Node Setup
Steps NE Identification “Checking the current
software release”.
NE Configuration parameters, Advanced
Parameters are available with
initial values, can be edited as
required, and are
Proxy ARP GNE automatically populated when
COLAN Provisioning
(optional)
SNMP Provisioning
(optional)

Basic setup complete.
setup, more provisioning can be

Figure 2-4
Quick-start turning-up of a Member shelf using the Node Setup application
Preparation “Powering up a new network element and

task connecting a craft computer” (Procedure 2-1)
Quick-start turning-up of a Member shelf using Node Setup (Procedure 2-4)

did not open, go to
Launch Site Manager. Procedure 2-2 “Checking the
check your current software
release, then restart
No
Does the Node Setup application open? Procedure 2-4 “Quick-start
turning-up using the Node
Setup application” as
Yes (SP has the correct
software release.)
“Checking the current
Node Setup software release”.
Steps NE Identification

parameters, Advanced
Parameters are available with
NE Configuration initial values, can be edited as
required, and are
automatically populated when
Basic setup complete.
setup, more provisioning can be
Fixed-band plan thin terminals

Figure 2-5 illustrates the supported types of photonic line systems supported
by the fixed band plan thin terminals (also known as Channel access nodes).
Figure 5-1 on page 5-5 to Figure 5-21 on page 5-24 illustrate examples of the
fixed band plan thin terminal configurations.

Figure 2-5
6500 photonic line systems
Unprotected 6500 Photonic line systems

Span 1
Channel access node Channel access node
Span 1 Span 2
Channel access node Line amp node Channel access node
Span 1 Span 2 Span 3
Channel access node Line amp node Line amp node Channel access node
Protected 6500 Photonic line systems

Channel access node Channel access node
Working link (see Note)
Protection link (see Note)
Note: The Working link and the Protection link can consist of 1 span, 2 spans, or 3 spans.
For these configurations, you can commission the 6500 nodes as per
standard 6500 procedures and manually provision the equipment/slot
sequence or use CLI “install create” commands.
Note: The CLI “install create” commands are only supported on 2-slot or
7-slot compact shelves with SPAP2.
CLI “install create” commands are provided for each of the supported types of
configurations—except Line Amp configurations—that perform all or most of
the provisioning required for commissioning in just one step. Table 2-2 on
page 2-13 lists the “install create” commands. The Line Amp configurations
must be provisioned manually.
The CLI “install create” commands cannot be used for supported

configurations that include XLAs or SRAs. For these configurations, you must
commission the 6500 nodes as per standard 6500 procedures and manually
provision the equipment/slot sequence. Refer to Part 2 of Configuration -
Provisioning and Operating, 323-1851-310.2.

Note 1: For the SRA, the “FORCEDSHUTOFF” parameter value must be

set to “FALSE” in order to bring up the RAMAN pump lasers to ON.
Note 2: For CMD64 configurations with MLA3/ESAM, XLA/ESAM, or
XLA/SRA, the “Tx Power Reduction Control” parameter value for the LOC
facility must be set to “Always Off” so the transponders/Waveserver ports
associated with the CMD64 do not remain in reduced power state when
SPLI is established. Refer to Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.1, for details.
Note 3: For most configurations, the XLA mode should be left at the
default (High Gain). For XLA/SRA configurations, refer to “SRA calibration
- Gain range per fiber type” on page 5-43 for recommendations dependent
on span range. For XLA/ESAM configurations, contact Ciena.
After you complete the commissioning of the 6500 shelf, proceed to Chapter
5, “Fixed-plan terminal node procedures”.
Standard reach and Extended reach configurations

The configurations can have Standard reach or Extended reach. Standard
reach requires that all spans be lower than the maximum span loss indicated
in the link budget tables. If one or more spans exceed the indicated maximum
loss, it must be considered as Extended reach. This is also the case for
protected configurations. For example, if the working or the protection span
exceeds the indicated maximum loss, then both the working and the
protection span must be considered as Extended reach.
Multi-span Line Amp nodes consist of:

• For Standard reach: MLA3 and LIM
• For Extended reach: MLA3 pair with 10 dB pad
Minimum channel count requirement

Automatic switching in response to a fiber cut requires a minimum channel
count as shown in the following table.
If the network has one or more spans whose loss exceed(s) the limits in the
following table, then there are no generic rules. Minimum channel count is
customized based upon actual network particulars. For more information,
contact Ciena.

Table 2-1
Minimum channel count
Configurations Span count Minimum channel count

using and maximum span loss
Fixed-96 Fixed-88 Fixed-44 Fixed-64
band plan band plan band plan band plan
SLA 1 span, <10.2 dB span loss 8 6 8 N/A
MLA3 1 span, <24.7 dB span loss 3 5 3 3
MLA3 2 spans, <22.0 dB span loss 4 7 5 4
MLA2/MLA3 3 spans, <22.0 dB span loss 5 9 6 5
Assumptions for span reach

The following elements are assumed for span reach:
• Fiber type is NDSF.
• The fiber attenuation coefficient is 0.25 dB/km.
• Short spans are padded so that net span loss exceeds the minimum span
loss quoted in the link budget tables.
• Head-end and tail-end patch panels have 0.5 dB loss.
• If using Waveserver transponders, the Waveserver channels are
populated by member ID number as follows.
— Fixed-96 50GHz band plan: Member ID 1 to 48
— Flex-12 50GHz band plan: Member ID 1 to 6
For more information, see:

— Waveserver and 6500 Interworking, 323-4001-165
— Waveserver Ai and 6500 Interworking, 323-4002-165
6500 commissioning—provisioning information

6500 commissioning—provisioning information for Terminal nodes and
Line Amp nodes
Table 2-2 on page 2-13 lists the CLI install create commands used to
commission the Terminal node configurations. Table 2-3 on page 2-17
includes the descriptions for the parameters of the install create commands
used to commission the Terminal nodes (“Commissioning fixed-plan terminal
nodes using CLI” on page 2-103).

Table 2-4 on page 2-21 includes parameters for the CLI commands used to
commission manually the Line Amp configurations (“Commissioning
fixed-plan terminal nodes using CLI” on page 2-103).
Consult the engineering data sheet for your site and make sure you have the
information listed in the following tables as applicable to your Terminal or Line
Amp configuration. Mandatory parameters are in highlighted table cells.
• “6500 “install create” commissioning—provisioning information” on page
2-17 (Terminal nodes: Flex-12, Fixed-96, Fixed-88, Fixed-44, Fixed-64)
• “6500 Line Amp commissioning—provisioning information” on page 2-21
(Line Amps)
Table 2-2
“Install create” commands
Configuration “Install create” command

(Examples)
Unprotected configurations
Fixed-96 [50GHz] install create band-plan fixed96 group-id <Group Identifier> site-id <Site ID>
unprotected remote-site-id <Remote Site ID> site-name <Site name> ip <IP Address of the COLAN
(see Figure 5-2 on port> netmask <Netmask of the COLAN port> [def-gateway <Default gateway>] [otdr
page 5-5 and yes] [location <Location of the site>] [system-name <System ID>] [display <Display
Figure 5-3 on commands flag>]
page 5-6) Example (no OTDR):
install create band-plan fixed96 group-id 3 site-id 5 remote-site-id 10 site-name
"Site_1" ip 192.168.0.2 netmask 255.255.255.0 def-gateway 192.168.0.255
Example (OTDR):
"Site_1" ip 192.168.0.2 netmask 255.255.255.0 def-gateway 192.168.0.255 otdr yes

Table 2-2
“Install create” commands (continued)

(Examples)
(see Figure 5-6 on port> netmask <Netmask of the COLAN port> [def-gateway <Default gateway>] [otdr
page 5-9) yes] [location <Location of the site>] [system-name <System ID>] display <Display
commands flag>]
Example (no OTDR):
Example (OTDR):
Fixed-44 install create band-plan fixed44 group-id <Group Identifier> site-id <Site ID>
[100GHz] remote-site-id <Remote Site ID> site-name <Site name> ip <IP Address of the COLAN
unprotected port> netmask <Netmask of the COLAN port> [def-gateway <Default gateway>] [otdr
(see Figure 5-7 on yes] [location <Location of the site>] [system-name <System ID>] [display <Display
page 5-10 and commands flag>]
Figure 5-8 on Example (no OTDR):
page 5-11)
Example (OTDR):

Table 2-2

(Examples)
Flex-12 [50GHz] install create band-plan flex12 group-id <Group Identifier> site-id <Site ID>
(see Figure 5-10 remote-site-id <Remote Site ID> site-name <Site name> ip <IP Address of the COLAN
on page 5-13 and port> netmask <Netmask of the COLAN port> [def-gateway <Default gateway>] [otdr
Figure 5-11 on yes] [location <Location of the site>] [system-name <System ID>] [display <Display
page 5-14) commands flag>]
Example (no OTDR):
install create band-plan flex12 group-id 5 site-id 5 remote-site-id 10 site-name
Example (OTDR):
(see Figure 5-12 port> netmask <Netmask of the COLAN port> [def-gateway <Default gateway>] [otdr
on page 5-15 and yes] [location <Location of the site>] [system-name <System ID>] [display <Display
Figure 5-13 on commands flag>]
page 5-16) Example (no OTDR):
Example (OTDR):

Table 2-2

(Examples)
Protected configurations
Fixed-96 [50GHz] install create band-plan fixed96 group-id <Group Identifier> protected yes site-id
protected <Site ID> remote-site-id <Remote Site ID> site-name <Site name> ip <IP Address of
(see Figure 5-16 the COLAN port> netmask <Netmask of the COLAN port> [def-gateway <Default
on page 5-19) gateway>] [location <Location of the site>] [system-name <System ID>] [display
<Display commands flag>]
Example:
install create band-plan fixed96 group-id 3 protected yes site-id 5 remote-site-id 10
site-name "Site_1" ip 192.168.0.2 netmask 255.255.255.0 def-gateway 192.168.0.255
Example:
Fixed-44 install create band-plan fixed44 group-id <Group Identifier> protected yes site-id
[100GHz] <Site ID> remote-site-id <Remote Site ID> site-name <Site name> ip <IP Address of
protected the COLAN port> netmask <Netmask of the COLAN port> [def-gateway <Default
(see Figure 5-18 gateway>] [location <Location of the site>] [system-name <System ID>] [display
on page 5-21) <Display commands flag>]
Example:

Table 2-2

(Examples)
Example:
Table 2-3
6500 “install create” commissioning—provisioning information
Parameter and description Value “install Mandatory

create” to enter at
command commiss.
parameter stage
Band plan type • flex12 band-plan yes

Determines the provisioning of the • fixed96
equipment in the configuration and the • fixed88
channel-to-wavelength mappings. The
band-plan on 6500 and Waveserver (if • fixed44
applicable) must match. • fixed64
Not stored on the shelf.
Note: For more information on the fixed
band plans, refer to the wavelengths plans
in the Photonic equipment description
section of 6500 Photonic Equipment,
323-1851-102.6.
Default gateway Standard dot notation: def-gateway no

Used to provision a static route to the n.n.n.n
default gateway. Must be in the same
subnet as the IP address.
Display commands flag • yes display no

If this flag is set, the commands will be • no (default)
printed to the screen, but not executed.

Table 2-3
6500 “install create” commissioning—provisioning information (continued)

command commiss.
parameter stage
Group Identifier Integer value in the range group-id yes

This number must match the group-id of the 1 to 99
Waveserver modules if connected to the For more information,
line system. refer to the 400G
This group identifier is combined with the Waveserver User Guide,
site name to generate a node name. 323-4001-100. For
information on
This is stored in the shelf/baynum attribute Waveserver Ai, refer to
and is also included in the TID of the system the Waveserver Ai User
if the site-name is also provided. Guide, 323-4002-100.
IP Address of the COLAN port Standard dot notation: ip yes

Also used as the SHELF IP address. n.n.n.n
Note: COLAN (central office local area 0.0.0.0 indicates

"unnumbered".
network) is a facility on the network element
that allows the 6500 to communicate with
the customer data comms network (DCN).
Location of the site GPS coordinates of the location no

Stored in the shelf/location field. site (comma-separated
longitude,latitude.
For example,
"45.34940,-75.85461".)
Netmask of the COLAN port standard dot notation: netmask yes

n.n.n.n.
OPS Protection flag • no (default) protected no

If set to yes, it indicates that an OPS will be • yes
provisioned with two Mux/Demux groups.
OTDR flag • no (default) otdr no

If set to yes, it indicates that an ESAM will • yes
be provisioned for OTDR functionality.

Table 2-3

command commiss.
parameter stage
Remote Site ID Integer value in the range remote-site-id yes

This remote site ID is used to generate a 1 to 65535
unique optical system ID (OSID), if a
system-id is not provided. It is also used to
properly provision the Path ID for the OTS
equipment created.
This is not stored on the shelf, but it is used
to construct the following attributes
ots/osid
If a system-name is not provided, the OSID
is constructed of the hex forms of the site-id
and remote-site-id. If it is unprotected or a
working link, the smaller of the two site IDs
will come first. If it is a protection link, the
smaller of the two site IDs will come last.
Site ID Range is 1 to 65535 site-id yes

This number must be a unique ID within the
comms connected network. It is used to
associate all photonic equipment at the
same site together into logical groupings for
management interfaces.
Stored in the shelf/siteid attribute.
Also used in the ots/osid field if the
system-name is not provided.

Table 2-3

command commiss.
parameter stage
Site name Alphanumeric string site-name yes

The site name is a human readable name Maximum length of 17
common to the nodes at a site. If it is characters.
provided, it is combined with the provided The name can include
group ID to provision the node name of the any combination of
device also. uppercase and lowercase
Stored in the shelf/siteName field. letters, numbers, or
If it is supplied, it is combined with the special characters. The
group-id to construct a TID. name cannot include the
following characters:
If it is omitted, the default TID will be used. backslash(\), space,
double-quote ("), colon
(:), semicolon (;),
ampersand (&), greater
than (>), less than (<), or
comma (,).
System ID Alphanumeric string system-name no

The system-name is used to uniquely Up to seven characters
identify the links between sites in a network. for protected
If the system-name is not provided, it is configurations or eight
generated based on the local site ID and the characters for
remote site ID. If the system is a protected unprotected
system, the system ID is limited to seven configurations
characters (alphanumeric characters and
underscore “_”), so that a 'W' or 'P' can be
appended to indicate the working and
protection lines.
If supplied, this is used as the basis of the
OSID.
If the configuration is protected, a "W" or "P"
is added to the end of the OSID. In this
case, the system-name is limited to seven
characters.

Table 2-4
6500 Line Amp commissioning—provisioning information
Parameter description Value Command Mandatory

parameter to enter at
commiss.
stage
System parameters (command example: system config set)
Alarm info • DSBL alarm-info no

Parameter is listable: a set of parameters (No alarm information is
can be defined (for example, CRDTYP, reported in Autonomous
WVLNGTH). This parameter does not work Outputs [AO].)
in a cumulative manner, that is, to add/ • CRDTYP
remove flag from an existing set, the (Card Type is reported
desired new set must be fully specified as a in AOs.)
list. • WVLNGTH
(Wavelength is reported
in AOs.)
• FIC
(FIC is reported in AOs.)
• SBNTNM
(Subnet Name is
reported in AOs.)
• PHYSSHLF
(Physical Shelf ID is
reported in AOs.)
• BYNMBR
(Bay Number is
reported in AOs.)
• LABEL
(Label is reported in
AOs. This field is
supported only on SP2
and SPTX cards.)
• CLFI
(CLFI is reported in
AOs. This field is
and SPTX cards.)
• NM
(NAME is reported in
AOs. This field is
card.)

Table 2-4
6500 Line Amp commissioning—provisioning information (continued)

commiss.
stage
AutoRoute • DISABLE (default) autoroute-def yes

Sets the AutoRoute value in new channel • Set to DISABLE for Line Set to
access OTSs created in this node, unless Amp site. DISABLE
the user provides an explicit value in the • ENABLE for Line
create command. Amp site.
When AutoRoute is disabled,
cross-connects must be provisioned at all
channel access sites.
When AutoRoute is enabled,
cross-connects are automatically derived
as follows: passthrough cross-connects are
created at intra-domain channel access
sites and local add/drop cross-connects are
created for in-service CMD Tx/Rx
adjacencies.
Coherent Select (CS) control • Set to OFF. cs-ctrl yes
Group Identifier Integer value in the range group-id yes

For Line Amp, this refers to a physical bay 1 to 99
number.
It is stored in the shelf/baynum attribute and
is also included in the TID of the system
when the site-name is provided.
Location of the site GPS coordinates of the location no

Stored in the shelf/location field. site (comma-separated
longitude,latitude.
For example,
"45.34940,-75.85461".)
Minimum provisioned cooling requirements • LOWFLOW min-cooling no

of the shelf • HIGHFLOW (default)
NE mode • SONET ne-mode yes

Typically set to SONET • SDH
• SDHJ
• UNKNOWN
(default)

Table 2-4

commiss.
stage
OSC Mode • OSPF (default) osc-mode no

State value used to control OSPF circuits will be
auto-provisioning of comms circuit when an auto-created using
OSC facility is provisioned. default area 0.0.0.0.
• DISABLED (To
manually provision
OSPF circuits using
non-default areas, set to
DISABLED.)
Site ID Range is 1 to 65535 site-id yes

This number must be a unique ID within the
Site name Alphanumeric string site-name yes

If it omitted, the default TID will be used. backslash(\), space,
(:), semicolon (;),
comma (,).
Shelf parameters (command example: shelves shelf create)
Bay number Integer value. bay-num no

The bay number defines the bay ID where Range is 0 to 99.
the shelf is located. It is optionally reported
in AO messages.

Table 2-4

commiss.
stage
Primary Member Activation—TID • enable primary no

Consolidation • disable (default)
The parameter enables/disables the shelf
as primary.
Site ID Range is 0 to 65535. site-id yes

This number must be a unique ID within the 0 indicates not defined.
Stored in the shelf/siteid attribute.
Also used in the ots/osid field if the
system-name is not provided.
Name Alphanumeric string site-name yes

If it omitted, the default TID will be used. backslash(\), space,
(:), semicolon (;),
comma (,).
TID Consolidation • enable tidc no

• disable (default)

Table 2-4

commiss.
stage
OTS parameters (command example: topology ots create)
Configuration type • Set to AMP for Line Amp cfgtype yes

commissioning. Set to AMP
for Line
Amp site.
Optical System ID Alphanumeric string up to osid yes

7 characters for protected Must match
configurations or 8 the OSIDs
characters for provisioned
unprotected on the
configurations Terminal
nodes.
tx-path Integer value from 1 to tx-path yes

Parity must be the opposite of the tx-path for 254.
the far-end neighbor.
That is, if remote tx-path is an odd number,
then the local tx-path must be an even
number. Typically, only 1 and 2 are used
alternating across the network.

Procedures
Table 2-5
Procedures in this chapter
Procedure
Preparation tasks
Procedure 2-1, “Powering up a new network element and connecting a craft computer”
Procedure 2-2, “Checking the current software release”
Commissioning script procedures
Procedure 2-3, “Commissioning the network element using scripts”
Quick-start turning-up - Node Setup procedure
Procedure 2-4, “Quick-start turning-up using the Node Setup application”
Advanced SLAT Assistant Tool (SAT) procedures
Procedure 2-5, “Launching Advanced SLAT and logging in”
Procedure 2-6, “Commissioning a network element using Advanced SLAT”
Procedure 2-7, “Enabling or disabling auto-equipping”
Procedure 2-8, “Performing a lamp test”
Procedure 2-9, “Provisioning OSPF router parameters”
Procedure 2-10, “Provisioning ILAN”
Procedure 2-11, “Provisioning Shelf IP address”
Procedure 2-12, “Provisioning IISIS router parameters”
Procedure 2-13, “Provisioning COLAN”
Procedure 2-14, “Provisioning proxy ARP (IPv4)/ND Proxy Provisioning (IPv6)”
Procedure 2-15, “Provisioning NAT”
Procedure 2-16, “Provisioning Dynamic NAT”
Procedure 2-17, “Provisioning Port Filtering”
Procedure 2-18, “Provisioning Reverse Port NAT”
Procedure 2-19, “Provisioning Neighbor Discovery Protocol”
Procedure 2-20, “Provisioning static routes”
Procedure 2-21, “Provisioning OSPF routes distribution”
Procedure 2-22, “Provisioning IISIS routes distribution”

Table 2-5
Procedures in this chapter (continued)
Procedure
Procedure 2-23, “Provisioning SNMP”
Procedure 2-24, “Provisioning security”
Procedure 2-25, “Provisioning SSH/TELNET and HTTP/HTTPS Server”
Procedure 2-26, “Provisioning craft access”
Procedure 2-27, “Provisioning craft OSPF/IISIS”
Procedure 2-28, “Checking, clearing, and provisioning alarms”
Fixed band plan thin terminals CLI procedures
Procedure 2-30, “Commissioning fixed-plan terminal nodes using CLI”
Procedure 2-31, “Commissioning 6500 Line Amp nodes using the CLI”
Optional tasks
—in Procedure 2-29, “Post SLAT commissioning”:
• “Connecting the network element to the DCN” on page 2-99

• “Enabling the IPv6 DHCP server on the craft port” on page 2-100
• Database cloning tasks:
– “Saving the golden database” on page 2-100
– “Restoring the golden database onto newly commissioned network elements” on page 2-101

Procedure 2-1
Powering up a new network element and connecting a
craft computer
Use this procedure to power up the shelf and connect your craft computer to
the shelf processor.
If you want to connect a craft computer to an already commissioned network

element, refer to the procedure on logging in to a network element using a
direct network connection to the LAN port on the shelf processor, in
Administration and Security, 323-1851-301.
Note: For multi-shelf nodes, commission the member shelves first and the
Primary shelf last.
CAUTION
Risk of damage to equipment
Electrostatic discharge (ESD) can damage
electrostatic-sensitive devices. Always connect yourself to
ground before you handle an electrostatic-sensitive device.
DANGER
Risk of injury
Observe the safety guidelines in “Appendix A: Observing
product and personnel safety guidelines”, and those
recommended by your company at all times.
ATTENTION
Protect RJ45 and USB ports by not removing any dust caps until a cable is
connected to a port. If a cable is removed from a port that was originally
equipped with a dust cap, protect the port with the appropriate dust cap.
Prerequisites
To perform this procedure, you must directly connect your craft computer to
the shelf processor at the network element site, for each network element in
the system. For instructions, refer to the Installation technical publication
specific to the respective 6500 shelf type, the chapter on installing 6500
shelves.

Procedure 2-1 (continued)

Powering up a new network element and connecting a craft computer
Step Action
1 Ensure that installation of the network element is complete. Refer to the

procedures in the Installation technical publication specific to the respective
6500 shelf type.
2 Verify that all the network element equipment is present as specified in your
site engineering documentation package (EDP) or international
documentation package (IDP).
3 If the shelf is powered up, power down the shelf.
4 Unseat the shelf processor(s) and the circuit packs if they are seated.
5 Verify all ILAN to ILAN connectivity for multiple shelves within a site and
COLAN-X connectivity to the DCN on GNE shelves.
6 Seat the shelf processor (SP). For shelf types that support two SPs, the active
SP must be in slot 15 (for 6500-7 packet-optical, 2-slot, 7-slot, and 14-slot
shelves) or slot 41 (for 32-slot shelves). You will be instructed to seat the
second SP, if applicable, at the end of node setup/commissioning.
7 Make sure the fans, the fillers, the Power Input Cards, and the MIC if
applicable, are seated.
CAUTION
Filler circuit packs required
Equip all empty slots with filler circuit packs to ensure
the correct air flow and cooling. Otherwise, equipment
damage can occur within 3 minutes.
Powering up the shelf

8 Power up the shelf.
If the shelf is equipped with Then go to
a breakerless or fused Power Input Card, or DC step 9
power supplies for a 2-slot shelf
a breakered Power Input Card step 10
AC power supplies for a 2-slot shelf step 11
9 Turn on the circuit breakers at the BIP corresponding to Power Input Cards A
and B or the redundant DC power supplies for a 2-slot shelf (for breakerless
Power Input Cards, turn on the power at the source).
Go to step 12.


Step Action
10 Switch the power breakers on the Power Input Cards A and B to the “on”
position (indicated with a | sign on the panel).
Go to step 12.
11 Plug in the power cords corresponding to the redundant AC power supplies
for a 2-slot shelf.
12 Upon circuit pack power up, the red Fail, the green Ready, and the blue In Use
status LEDs go through the following sequence:
• The red LED turns on momentarily.
• After a few seconds, the red, green and blue LEDs turn on.
• After a few seconds, the red and blue LEDs turn off and the green LED
flashes to indicate the software is initializing.
• When software initialization is complete, the green status LED turns on
(does not flash).
• If the circuit pack is in-service, the blue LED turns on after the green LED
while the circuit pack is in use.
Wait until the green and blue LEDs on the shelf processor turn steadily on.
Connecting the computer to the shelf processor
13 Connect the computer to the RJ-45 connector (LAN-15 or LAN-41 port) on
the shelf processor with a cross-over or straight Ethernet cable.
14 Configure your computer to obtain an IP address automatically (the shelf
processor is a DHCP server and can assign an IP address) or provision the
computer to have an IP address of 10.0.0.2 with a subnet mask of
255.255.255.252, and a default gateway of 10.0.0.1.
It can take up to three minutes for the Ethernet link to establish.
Note: If the SP has been previously commissioned or a Transport Data
Recovery Failed alarm is raised, delete all shelf provisioned data. Refer to the
“Deleting all shelf provisioning information for a standalone shelf or all
shelves of a consolidated node” procedure in Administration and Security,
323-1851-301.
15 Select your next step.
If Then go to
you have configured the computer to obtain an IP step 16
address automatically and you are using a PC
you have configured the computer to obtain an IP step 18
address automatically and you are using a MAC
you have provisioned the IP address manually step 23


Step Action
If you are using a PC

16 At the command prompt on your craft computer, enter:
ipconfig /flushdns
ipconfig /release
ipconfig /renew
17 From the command output, verify that your computer is assigned an IP
address of 10.0.0.2, a subnet mask of 255.255.255.252, and a default
gateway of 10.0.0.1.
Then go to step 23.
If you are using a MAC
18 Open System Preferences.
19 Open Network settings
20 Click on the Ethernet interface from the list on the left-hand side of the
preferences.
If the Configure IPv4 field Then
is set to Using DHCP close the window. Then go to step 23.
is not set to Using DHCP go to step 22
22 Use the drop-down menu to change the Configure IPv4 field to Using DHCP.
Then click Apply and close the window.
23 You have completed this procedure. Depending on your turning-up solution,
select the procedure to go to next from the following table.
To select your turning-up solution, see “Node setup solutions” on page 2-4
and “Selecting the turning-up solution for a newly installed system” on page
2-6.
If you will be using Then go to
the Node Setup application “Quick-start turning-up using the Node
Setup application” on page 2-42
a commissioning script file or “Checking the current software release” on
Advanced SLAT page 2-32
—end—

Procedure 2-2
Checking the current software release
Use this procedure to check the current software release on the network
element from the Node Information window in Site Manager or the NE
Identification window in Advanced SLAT/SLAT Assistant Tool.
Prerequisites
To perform this procedure you must
• have Site Manager Release 12.7 software installed on your craft computer
• use an account with a UPC level of 4 or higher
Step Action
1 Select the application with which to check the software release.

If you will be using Then go to
Advanced SLAT step 2
a commissioning script file or Site Manager step 3
2 Launch Advanced SLAT (Procedure 2-5, “Launching Advanced SLAT and

logging in”) and verify the software release in the NE Identification panel of
the Advanced SLAT/SLAT Assistant Tool.
Go to step 6.
Note that when you log into an already provisioned shelf, a warning message
is displayed stating that provisioning data have been detected on the shelf
and providing instructions on the next step to perform:
For more information, see Procedure 2-5, “Launching Advanced SLAT and
logging in”.
3 Launch Site Manager and choose Connection type as Craft Ethernet. Log
into the network element by using the default IP address, which is 10.0.0.1.
The default user ID/password is ADMIN/ADMIN.
For detailed login procedures, refer to Administration and Security,
323-1851-301.
If the shelf is not commissioned, several warning dialogs may be displayed.
This behavior is expected and you must acknowledge to proceed. If a dialog
is displayed with the option of running a commissioning script or continuing
with Site Manager, click Site Manager. If a dialog is displayed that the Node
Setup Application will be launched, click Cancel.
4 Select the Node Information tab, then select the required shelf.
5 Under the General tab, check the current software release running on the
shelf processor (SP) in the Software version field.


Step Action

If the current software release Then go to
is the correct one step 8
is not the correct one step 7
7 Deliver the correct release to the shelf processor and then downgrade or
upgrade, as applicable, the software release on the shelf processor (Load,
first Invoke, second Invoke, Commit). Refer to release management and
upgrade management procedures in Administration and Security,
323-1851-301.
ATTENTION
Do not attempt to clear any alarms until the new shelf processor is upgraded.
ATTENTION
During the Invoke step, make sure the “Manually invoke circuit packs
requiring cold restart” check box is not selected.
ATTENTION
If you were directed to this procedure Procedure 2-2, “Checking the current
software release” from Procedure 2-4, “Quick-start turning-up using the
Node Setup application”, after you deliver the correct software release to the
SP, go back to Procedure 2-4, “Quick-start turning-up using the Node Setup
application”.
If the current software release is correct (Release 12.7)

If your turning-up solution is Then
using a commissioning script file you have completed the procedure.
Next go to Procedure 2-3,
“Commissioning the network element
using scripts”
Advanced SLAT or the Node go to step 9
Setup application


Step Action

If your shelf Then go to
is equipped with NTK615AA/NTK615BA or NTK616AA/ step 10
NTK616BA PKT/OTN cross-connect (XC) circuit packs
is not equipped with NTK615AA/NTK615BA or step 14
NTK616AA/NTK616BA PKT/OTN cross-connect (XC)
circuit packs

If your turning-up solution is Then go to
Advanced SLAT step 11
the Node Setup application step 12
11 Do not seat any circuit packs at this point. You will be instructed later during
Procedure 2-6, “Commissioning a network element using Advanced SLAT” to
seat the NTK615AA/NTK615BA or NTK616AA/NTK616BA PKT/OTN
cross-connect [XC] circuit pack and then the rest of the circuit packs after the
NE Configuration stage (which implicitly sets the date/time without user
intervention).
Go to step 19 in this procedure.
12 Seat one PKT/OTN XC circuit pack (NTK615AA/NTK615BA or NTK616AA/
NTK616BA) and wait until the green and the blue LEDs on the XC turn
steadily on (approximately 25 minutes).
Alarms may be raised during the interval, which should clear automatically
13 If there are other active alarms, determine if they are expected. Clear any
unexpected alarms by following the appropriate procedures in Part 1 and
Part 2 of Fault Management - Alarm Clearing, 323-1851-543.
CAUTION
Risk of damage to circuit packs
Ensure that any alarms associated with the fans are cleared
before proceeding (for example, fan failed, fan missing,
incompatible fan, or equipment configuration mismatch).
Installing the circuit packs with failed, missing, or wrong fans
may cause the circuit packs to be damaged by overheating.
14 Seat all remaining circuit packs that you must equip in the shelf.


Step Action
15 Wait until the green LEDs on all circuit packs turn steadily on. For the
cross-connect circuit pack, the blue LED should also be on.
If any of the circuit packs do not power up properly, first try to unseat and
reseat the circuit pack to make sure the circuit pack is inserted into the
backplane correctly. If the red LED on the circuit pack is lit, replace the circuit
pack. Refer to Fault Management - Module Replacement, 323-1851-545, for
the appropriate procedures.
16 Select Active Alarms from the Faults drop-down menu.
17 Make sure there are no “Software Auto-upgrade in Progress” alarms or wait
until these alarms clear before going to the next step.
The “Software Auto-upgrade in Progress” alarm indicates that a circuit pack
is in the process of being auto-upgraded/downgraded to the active release of
the network element. This alarm will clear on its own once the process is
complete.
19 Make sure you exit from the Site Manager session.
20 You have completed this procedure.
If your turning-up solution is Then
the Node Setup application The quick-start turning-up is complete.
Advanced SLAT Go to Procedure 2-5, “Launching Advanced
SLAT and logging in”.
—end—

Procedure 2-3
Commissioning the network element using scripts
Use this procedure to commission a new network element by using scripts.
Prerequisites
To perform this procedure
• make sure you have performed Procedure 2-1, “Powering up a new
network element and connecting a craft computer” and Procedure 2-2,
“Checking the current software release”
• make sure the active shelf processor (SP) is seated and all the other
circuit packs are unseated, and that the LAN cable is disconnected from
the FIM
• make sure the following cables are not connected:
— ILAN cables
— COLAN cables
• have the commissioning script file. The file type is .json.
Note: Refer to the MCP User Guide for procedures on generating and
exporting commissioning scripts.
• have a copy of Part 1 and Part 2 of Fault Management - Alarm Clearing,

323-1851-543
• have a copy of Fault Management - Module Replacement, 323-1851-545
CAUTION
CAUTION
Risk of injury
Observe the safety guidelines in Installation - General
Information, 323-1851-201, and those recommended by your
company at all times.


Step Action
1 If you are logged into the network element, log out and exit Site Manager.
2 Make sure the craft computer is physically connected to the Craft port on the
faceplate of the shelf processor.
3 Launch Site Manager and choose Connection type as Craft Ethernet. Log
into the network element by using the default IP address, which is 10.0.0.1,
and the ADMIN/ADMIN credentials.
(For detailed login procedures, refer to Administration and Security,
323-1851-301.)
4 If the shelf is not commissioned, several warning dialogs may be displayed.
This behavior is expected and you must acknowledge to proceed.
If a dialog is displayed with the option of running a commissioning script or
continuing with Site Manager, click Run Commissioning Script.
If a dialog is not displayed with the option of running a commissioning script,
choose the option to continue with Site Manager. Once the dialog closes,
launch the TL1 Command Builder tool, Tools/TL1 Command Builder.
Note: The TL1 Command Builder main window opens. (The window
opens automatically only if you click Run Commissioning Script. To
open the TL1 Command Builder application manually, go to the Site
Manager Tools menu.)
5 In the TL1 Command Builder main window, verify that “Halt on error” (at the
bottom of the window) is checked.
6 Import the commissioning file as follows:
a. Go to File --> Open.
b. In the Open window, navigate to the folder where the commissioning file
is located. From the Files of type drop-down list select “Text Files
(.json)”, then select the commissioning script file from the file structure.
c. Click the Load button.
Note: The file is parsed in the background, which builds the set of TIDs,
shelves for each TID, and scripts for each shelf.


Step Action
7 After the file has been parsed successfully, a chooser dialog opens, which
allows the user to make the following selections:
a. Use the TID Name drop-down list to select the network element name
that you want to commission.
b. Use the Shelf drop-down list to select the shelf you want to commission.
c. Record the list of values in the Shelf drop-down.
d. Record whether the ALL value is listed in the Shelf drop-down list.
Note: Every new shelf has a shelf specific script that must be applied first
to commission that new shelf. The Shelf: ALL script in the drop-down list
will have to be applied to the Primary shelf after all of the shelf specific
scripts have been applied.
e. In the Script Number drop-down list, “1” will be the only option listed and
is selected by default.
f. Click OK.
8 In the TL1 Command Builder main window, click Run Script.
9 Verify the information in the confirmation dialog.
If the information is Then click
correct, that is, the correct node, shelf, OK
and Release are listed
not correct Cancel. Correct the selections and
verify the information in the new
confirmation dialog. Click OK.
If the following dialog is displayed before the ED-IP command is sent, click
OK and wait 30 seconds, then close TL1 Command Builder and Site
Manager:
“The remaining operation in script 1 is changing the craft port IP address.
The session to the craft port will likely drop due to the IP address change
before a response is received. After clicking “OK” please wait 30 seconds
for the ED-IP command to execute then close the TL1 Command Builder
application, If this is the last shelf specific script 1 for this TIDc, please
connect your computer to the craft port of the primary. Reset/renew the
IP address on your computer and log back into the primary and execute
the Shelf All script.”
Note: If the shelf-specific script execution fails, in the TL1 Command
Builder main window, click Save Results to save the log of the
commands sent and the responses received during the script execution.
Contact your next level of support.


Step Action
10 Perform the following tasks:

a. Log out of Site Manager if you are still logged in.
b. Connect the COLAN cables as required.
c. Connect the ILAN cables as required.
d. Insert the circuit packs, including the second shelf processor if applicable.
Make sure that the FIM LAN cable is connected, if applicable to your
configuration (Degree #1 of ROADM if applicable).
11 Repeat the following on all of the remaining shelves recorded in step 7 c:
• Procedure 2-1, “Powering up a new network element and connecting a
craft computer”, then
• Procedure 2-2, “Checking the current software release”, then
• step 1 to step 10 in this procedure
When the shelf specific script has been applied on all the remaining shelves,
go to step 12.
12 Connect the craft computer to the Craft port on the Primary shelf.
13 If the deployment is configured to allow craft reach-through, have your
computer obtain a new IP address from the Primary craft port. If you are using
a PC, at the DOS command prompt on your craft computer, enter:
ipconfig /flushdns
ipconfig /release
ipconfig /renew
14 After your computer has obtained a new IP address, record the IP address.
You will be required to enter in the Site Manager login dialog the IP address
your computer has obtained from the craft port minus 1. For example, if your
computer obtains IP address 11.0.0.6, you must enter the IP address of
11.0.0.5 in the Site Manager login dialog.
If centralized Then
security
has not been use the customer specific credentials to log in.
enabled The default credentials are ADMIN/ADMIN.
has been enabled use the credentials from centralized security to log in
15 Open Site Manager and log into the Primary shelf.


Step Action
16 In the Navigate/Window management area (left-hand side pane) of the Site

Manager main window, click on the plus sign next to the “Member shelves” to
expand the list of shelves. Review the list to check that all the expected
Member shelves are seen from the Primary shelf correctly. If they are not
listed as expected, check for alarms and that the ILAN cables are connected
correctly.
17 Check whether the ALL value was recorded in step 7 d.
If Then
the ALL value was go to step 18
recorded
the ALL value was you have completed this procedure. Proceed to
not listed/recorded Chapter 3, “Photonic layer provisioning procedures”.
Note: It is recommended that the intra-site and
inter-site fibering be completed before the
craftsperson leaves the site to ensure any fiber-related
issues are resolved without requiring subsequent
visits to the site.
Applying the Shelf: ALL script

18 Apply script Shelf: ALL as follows:
a. In Site Manager, go to the Tools menu and open the TL1 Command
Builder application.
b. In the TL1 Command Builder main window, verify that “Halt on error” (at
the bottom of the window) is checked.
c. Import the commissioning file:
— Go to File --> Open.
— In the Open window, navigate to the folder where the commissioning
file is located. From the Files of type drop-down list select “Text Files
(.json)”, then select the commissioning script file from the file
structure.
— Click the Load button.
d. Use the TID Name drop-down list to select the network element name.
e. In the Shelf drop-down list, select ALL.
f. In the Script Number drop-down list, “1” will be the only option listed and
is selected by default. Click OK.
g. Click Run Script.
h. In the warning dialog checking that this is the correct shelf, click OK.


Step Action
19 After script Shelf: ALL completes executing, select your next step.
If the script Shelf: ALL Then
execution
was successful A confirmation dialog is displayed. Click OK.
You have completed this procedure. Proceed to
Chapter 3, “Photonic layer provisioning
procedures”.
Note: It is recommended that the intra-site and
inter-site fibering be completed before the
craftsperson leaves the site to ensure any
fiber-related issues are resolved without requiring
subsequent visits to the site.
failed In the TL1 Command Builder main window, click
Save Results to save the log of the commands
sent and the responses received during the script
execution. Contact your next level of support.
—end—

Procedure 2-4
Quick-start turning-up using the Node Setup
application
If you have selected the Node Setup application as your turning-up solution
(see “Node setup solutions” on page 2-4 and “Selecting the turning-up
solution for a newly installed system” on page 2-6), use this procedure to
launch the application and perform the basic setup steps.
The Node Setup application steps are used to turn up the network element in
a simple way. After the basic setup is complete, more parameter provisioning
can be applied by using Site Manager menus. All the parameters are editable
via Site Manager.
Note: The Node Setup application must only be used locally during the
initial nodal SLAT process (when your craft computer is connected directly
to the LAN-15 port on the SP in a 6500-7 packet-optical, 2-slot, 14-slot or
7-slot shelf or LAN-41 port in a 32-slot shelf).
In order to perform NE turning-up, you must complete all mandatory fields in

each application Step.
For Node Setup examples, see the following worksheets:

• Direct Connect with basic parameters, Standalone shelf — Table 9-1 on
page 9-3
• Gateway Connect with basic parameters, Member shelf — Table 9-2 on
page 9-7
• Gateway Connect with basic parameters, Primary with Members shelf —
Table 9-3 on page 9-10
Note: The Last Refresh field at the bottom of the Node Setup application
screen displays the NE time in GMT.


Quick-start turning-up using the Node Setup application
Prerequisites
To perform this procedure you must:
• use an ADMIN account (ADMIN/ADMIN by default)
• have Site Manager installed
Note: Java Web Start (JWS) is no longer supported.
• make sure that there are no other active login sessions to the NE (such as
monitoring from OneControl, open TL-1 sessions, open Site Manager
sessions)
Note: The SP and filler cards must be the only circuit packs seated in the
shelf. The active SP must be in slot 15 (for 6500-7 packet-optical, 2-slot,
7-slot, and 14-slot shelves) or slot 41 (for 32-slot shelves). Ensure fans,
power cards and access panels exist. Ensure that the maintenance
interface card (MIC) is present for MIC supported shelves.
Step Action
1 Launch Site Manager.

2 In the Login screen:
• Select Connection type as Craft Ethernet.
• Enter the IP address of the network element. The default IP address of
an NE is 10.0.0.1.
• Make sure the Use SSH checkbox is not checked.
3 Enter the User ID and Password (ADMIN/ADMIN by default).
4 Click Connect.
5 If the shelf is not commissioned, several warning dialogs may be displayed.
This behavior is expected and you must acknowledge to proceed.
You are logged out of Site Manager. The Node Setup application opens with
the NE Identification Step highlighted.
Note: The Node Setup application will be launched only if the node shelf
processor is running Release 10 or higher. If the Node Setup Application did
not launch, go to Procedure 2-2, “Checking the current software release” to
check your current software release, then restart this procedure
(Procedure 2-4, “Quick-start turning-up using the Node Setup application”) as
instructed in Procedure 2-2, “Checking the current software release”.


Step Action
6 Enter a network element name in the NE Name field. Refer to NE

Identification in Table 2-6 on page 2-47 for provisioning rules.
Information on valid TID characters is available by clicking the Help button.
Optional parameters (CLLI and Extended NE Name) can be provisioned also,
if required.
7 Click Apply to apply the identification changes to the network element.
The date and time are set based on the craft computer date and time
converted to GMT. Optionally, to change after Node Setup is complete, use
Site Manager->Node Information->Node Information tab.
8 Select the NE Configuration Step in the left-hand side panel of the application
window.
9 Select your Shelf Type (Standalone, Primary with Members, Member) in the
NE Configuration panel.
Note: 6500 supports single-shelf TIDs and multi-shelf TIDs. In a multi-shelf
TID, the Member shelves are connected with the Primary shelf through ILAN.
10 Enter the following mandatory NE Configuration parameters. Refer to NE
Configuration in Table 2-6 on page 2-47 for provisioning rules.
• Shelf Number
• Shelf IP Address (IPv4)
• OSPF Network Area
• Site ID is mandatory for photonic services.
Optional parameters (Site Name, Location) can be provisioned also, if

required.
11 Additional configuration parameters are provisioned automatically. Click on
the Advanced Parameters label to open the panel and view or edit the
parameters. Refer to Advanced Parameters in Table 2-6 on page 2-47 for
provisioning rules and initial defaults.
ATTENTION
The Node Setup tool remembers the Advanced Parameter settings (NE
Configuration) and SNMP application settings. The tool automatically reuses
them when the next shelf is set up. The information is stored in the



Step Action
12 Click Apply to apply the configuration changes to the network element.

Depending on your selection of Shelf Type, the tool provisions a set of
parameters automatically. When you press the Help button in the NE
Configuration panel, detailed NE Configuration instructions are displayed,
which include the parameters for each Shelf Type and the values with which
they are provisioned. If you require a parameter value change, use Site
Manager->Configuration->Comms Setting Management after you complete
the basic setup. For the list of parameters for each Shelf Type, see:
• Standalone shelf — Table 9-1 on page 9-3
• Member shelf — Table 9-2 on page 9-7
• Primary with Members shelf — Table 9-3 on page 9-10
If your Shelf Type is Then go to

Member step 22
Primary with Members step 13 to set up the Proxy ARP GNE
Configuration
Standalone step 15 to set up COLAN Provisioning
13 In the Proxy ARP GNE Configuration panel, enter the IP addresses of the
member shelves for this TIDc. Enter member shelf IP addresses as follows:
• Enter consecutive addresses by first address and last address of the
range.
• You can enter one non-consecutive address by setting the same address
in the Start IP Address and End IP Address. If you want to enter more
than one non-consecutive IP address, use Site Manager -> Configuration
->Comms Setting Management after you complete the basic setup.
If Member shelves already exist when this step is executed, you can display
their IP addresses, along with the Primary IP address, in the table by clicking
on the Refresh button.
14 Click Apply to apply the Proxy ARP GNE configuration changes to the
network element. Then go to step 15 to set up COLAN Provisioning.
15 In the COLAN Provisioning panel, the tool auto-populates the COLAN-X IP
address to match the Shelf IP address. You can change the address. Enter
the following mandatory parameters. Refer to COLAN Provisioning in Table
2-6 on page 2-47 for provisioning rules.
• IP Address
• Subnet Mask
16 Click Apply to apply the COLAN Provisioning changes to the network
element.


Step Action
17 The next step, Security Provisioning, is optional. If you are using this step,
enter the applicable parameters. To enable the Centralized Authentication
tab, select the Centralized Authentication Required checkbox. Refer to
Optional Step - Security Provisioning in Table 2-6 on page 2-47 for
provisioning rules.
18 Click Apply to apply the changes to the network element.
The application remembers all the changes made by the user and applies
them to the next shelf that is set up.
19 The next step, SNMP Provisioning, is optional. If you are using this step, enter
the applicable parameters. Refer to Optional Step - SNMP Provisioning in
Table 2-6 on page 2-47 for provisioning rules.
20 Click Edit Trap Destination, enter the destination SNMP trap viewer
information, then click OK. Click Apply SNMP Data to apply the changes to
the network element.
The application remembers all changes made by the user and applies them
to the next shelf that is set up.
21 Click the Confirm Completion button.
22 You have completed the basic setup of the network element.
After the basic setup is complete, more parameter provisioning can be
applied by using Site Manager menus. All the parameters are editable via Site
Manager.
23 To complete the turning-up, go to Procedure 2-2, “Checking the current
software release” and perform step 9 to step 20 to insert the required circuit
packs and check for alarms.
—end—

Table 2-6
Node Setup application parameters
For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.
NE Identification
NE Type OBP, OCP, COP, CCA, Network element equipment type: no

CNE OBP-Optical Broadband Platform (read only)
OCP-Optical Convergence Platform
COP-Consolidated Optical Platform
CCA-Consolidated Channel Access
CNE-Converged network element
Release RELxxxxx.xx Release of NE software running on shelf no

processor, where xxxxx.xx represents an (read only)
alphanumeric value representing the
software version running on the shelf
processor.
NE Name 1 to 20 alphanumeric Can include any combination of upper and yes

characters lower case letters, numbers, or special
(<), or comma (,).
See Note 1.
Extended NE 1 to 64 alphanumeric Can include any combination of upper and no

Name characters lower case letters, numbers, or special
(<), or comma (,).

Table 2-6
Node Setup application parameters (continued)
CLLI Up to 11 characters 11-character alphanumeric code in the form no

CCCCSSBBUUU where:
• CCCC denotes the city, town, or locality
code
• SS denotes the geographical area (for
example, state or province code)
• BB denotes the building code or network
site
• UUU denotes the network entity or unique
traffic unit identifier
The combination of these codes comprise a
unique place, a unique building, and a
specific entry.
The CLLI cannot include special characters
but can include spaces. Spaces are included
in the length of the CLLI.
NE Configuration
Shelf Type Standalone A shelf that does not belong to a consolidated yes
Primary with Members node is referred to as a Standalone shelf.
Member In a consolidated node, a single shelf is either

a Primary with Members shelf or a Member
shelf.
The Primary shelf represents the group of
shelves in a consolidated node.
Shelf Number 0 to 254 Shelf identifier of the shelf. Must be unique yes
within a site.
Photonic shelves (6500) at a given site (with
the same Site ID) must have unique logical
shelf numbers (also referred to as Shelf ID),
regardless of node name (TID).
Note: A Photonic shelf refers to a shelf with
an OTS provisioned on it.
Shelf IP Address standard dot notation Also known as circuitless IP address. yes
OSPF Network standard dot notation Sets the area. yes

Area

Table 2-6
Site ID 0 to 65535 Identifier of the site. Must be the same for all Site ID
NEs within a site. must be
For photonic network designs, as per One provisioned
Planner guidance, the Site ID must be unique before the
across the network, meaning different sites photonic
need to use unique Site IDs. Within a Site, for layer is
service shelves connected to the photonic defined.
shelves, all shelves should use the same Site Can be
ID or use different Site IDs but be in the same provisioned
Site Group. at this point
or after the
Note: The setting of the Site Group is not node setup
available from the SLAT Assistant Tool. Refer has
to the ‘Node information’ section in completed.
Administration and Security, 323-1851-301
for more information.
In order for Visualization to work properly, the
Site ID on non-photonics shelves should be
set to match the Site ID of photonic shelves at
the same site.
Note: For SPLI, alarm correlation, and OTS
management to function, the Site ID must be
provisioned to a non-zero value.
Site Name up to 20 characters Unique text string assigned to the site. no
Location up to 64 alphanumeric The location (latitude and longitude) no

characters associated with the selected shelf. The
preferred format is as follows (note that there
is no space following the comma):
<latitude>,<longitude>
where
<latitude> = -90.000000 to +90.000000 ("+"
optional)
<longitude> = -180.000000 to +180.000000
(“+” optional)

Table 2-6
Alarm Info Disabled (default), Determines whether enhanced alarm no

Card Type, reporting is enabled or disabled. When
Wavelength, Frame enabled, depending on the option(s)
Identification Code, selected, additional details are displayed in
Subnet Name, Physical the corresponding columns in the information
Shelf ID, Bay Number, table, “Alarm details” field, and “Event details”
Label, CLFI, Name field of the Site Manager Active Alarms,
Historical Fault Browser and Consolidated
Alarms applications.
• Disabled: disables enhanced alarm
reporting, and “-” is displayed in the
columns/fields below:
• Card Type: Populates “Card Type” column.
• Wavelength: Populates “Wavelength”
column.
• Frame Identification Code: Populates
“Frame Identification Code” column.
• Subnet Name: Populates “Reporting
Subnet” column.
• Physical Shelf ID: Not supported in this
release.
• Bay Number: Not supported in this release.
• Label: Populates “CLFI” column with label
associated with TCM and PKT/OTN
transport and switched services facilities.
• CLFI (Common Language Facility
Identifier): Populates “CLFI” column.
• Name (SNC name): Populates “Additional
Information” column with optional SNC
Name for all OTN Control Plane
SNC-related alarms. For further information
on the SNC name parameter, refer to the
“SNC Name” section in the “L0 and L1
sub-network connections management”
chapter of Configuration - Control Plane,
323-1851-330.

Table 2-6
Advanced Parameters
The Advanced Parameters are filled in automatically and can be edited as required. The tool remembers
the Advanced Parameter settings and automatically reuses them when the next shelf is set up.
NE Mode SONET (default), SDH, Software mode of network element. no

SDH-J
NDP Mode DISABLED, ENABLED Controls the auto-provisioning behavior of no

(default) the NDP feature.
If the value is Disabled, there is no action
performed. If the value is enabled, the
NDPMODE is used to auto provision an NDP
link on a GCC0 channel (when a facility is
created). It also enables the NDP feature the
first time a facility is created.
Alarm Correlation ON, OFF (default) Indicates whether the alarm correlation no
feature is enabled or disabled.
Shelf Synch YES (default), NO Enables or disables shelf synch between the no
primary shelf and the member shelves.
Air Filter ENABLE, DISABLE Enable or disable the “Filter Replacement no

Replacement (default) Timer Expired” alarm.
Alarm
Air Filter 0 to 1826 (default 731 Sets the number of days before the “Filter no
Replacement or 730) Replacement Timer Expired” alarm is raised.
Timer (in days)
Auto Delete on • YES Enables/disables the auto-squelch feature no

LOS • NO (default) (delete of channels with Ingress LOS alarm).
TCA Suppression ENABLED, DISABLED Enables or disables TCA suppression. no

(default)
Auto Facility OFF, ON (default) Enables or disables facilities no

Provisioning autoprovisioning.
For an OSMINE-managed system, you must
set Auto Facility Provisioning to OFF.

Table 2-6
Shelf DISABLED, ENABLED Disables or enables shelf auto-equipping. no

AutoEquipping If NE Mode selection is
SONET or SDH-J,
default is ENABLED.
If NE Mode selection is
SDH, default is
DISABLED.
CS Control DISABLED, ENABLED Enables or disables Coherent Select no

provisioning.
If you enable CS Control from the Node
Setup application, the Autoroute OTS
parameter is automatically disabled.
Determines whether Coherent Select
provisioning is enabled or disabled at a nodal
level.
Note: The CS Control value can be changed
on a primary or member shelf of a
consolidated node. However, if Shelf Synch is
enabled, the CS Control parameter cannot be
edited on a member shelf. If the CS Control
parameter is changed on a primary shelf, it
broadcasts the value to all member shelves.
Proxy ARP GNE
Start IP Address standard dot notation Proxy ARP IP address(es). yes

and
End IP Address
COLAN Provisioning
IP Address standard dot notation COLAN IP address. yes
Subnet Mask standard dot notation COLAN subnet mask. yes
Optional Step - Security Provisioning
Passwords tab
Password Rules Standard, Complex Sets the password creating rules to standard no
or complex.

Table 2-6
ADMIN/SURVEIL alphanumeric Sets the password for ADMIN user or no

New Password characters SURVEIL user.
Confirm New
Password
Centralized enabled, disabled When enabled, the Centralized no

Authentication Authentication tab is enabled to allow
Required authentication parameters to be entered.
Centralized Authentication tab
Server State Enable, disable Sets the status of the Primary and Secondary no
RADIUS servers.
IP Address Standard dot notation Sets the IP address of the Primary and no
Secondary RADIUS servers.
Port Number numeric Sets the port number of the Primary and no
Shared Secret alphanumeric Sets the shared secret of the Primary and no
Confirm Shared characters Secondary RADIUS servers.
Secret
Timeout (s) numeric Sets the timeout value for the Primary and no
Authentication Challenge, Local Can only be enabled if at least one RADIUS no

Alternative server is enabled.
Both RADIUS servers can only be disabled if
Centralized Authentication is disabled.
Intrusion On-User Based, Sets the detection of the intrusion attempts. no

Detection State On-Source Based, Off
Optional Step - SNMP Provisioning
Agent State enabled, disabled Enables or disables SNMP. no
Version alphanumeric Indicates the version of the SNMP. no

characters
Alarm Masking On, Off Enables or disables alarm masking. no

Table 2-6
Proxy On, Off Enables or disables SNMP proxy – option no

shelves. Proxy can only be enabled when the
primary shelf is 6500.
If you are commissioning the Primary shelf of
is preferable to enable the SNMP proxy.
Request Timeout numeric value Timeout value for SNMP requests – option no
shelves.
Destination alphanumeric Indicates the trap destination. no

characters
IP Address standard dot notation Trap destination IP address. no
UDP Port 1 to 65535 The user datagram protocol (UDP) port. no
Version V1, V2C, V3 Version of trap to be sent. no

For V3, see Note 2.
UAP PUBLIC, SYSADMIN, User access privilege of the V2 user to be no

OBSERVER, used to send traps.
CUSTOMER1,
CUSTOMER2,
OPERATOR

Table 2-6
UID alphanumeric The SNMP V3 user if version is specified as no

characters a V3 trap. See Note 2.
The user information used to send traps.
TRAP DISABLE, Disables or enables TL-1 traps and/or SAOS no

Configuration ENABLE_ALL, traps on a per receiver basis.
TL1_TRAPS_ONLY, For V1 or V2c version, only TL-1 traps are
SAOS_TRAPS_ONLY supported. Therefore, only
TL1_TRAPS_ONLY and DISABLE options
are valid.
For V3 version, both TL-1 and SAOS traps
are supported. Therefore, all options are
valid. Also see Note 2.
Note 1: OneControl supports the following special characters _ + @ - ^ ~ / . $ % * # ! ( ) = [ ] { } ’ ? | ‘ in

the TID for the 6500 Site Manager craft launch. Do not use special characters not supported in an NE
TID if you want to launch the 6500 Site Manager craft from OneControl.
Note 2: SNMPv3 on the current release of 6500 does not have any usable SNMPv3 USM users by
default. To access the node via SNMP v3, you must log into Site Manager via the Craft port after the
node is set up and create a USM user. For more information, see Fault Management - SNMP,
323-1851-740.

Procedure 2-5
Launching Advanced SLAT and logging in
If you have selected Advanced SLAT as your turning-up solution (see “Node
setup solutions” on page 2-4 and “Selecting the turning-up solution for a newly
installed system” on page 2-6), use this procedure to launch SAT and log into
the network element. You must have only one active SAT session for each
network element at a time.
Advanced SLAT contains the complete SLAT procedures that guide the user
through different SLAT steps. Advanced SLAT can be used remotely.
Note: SAT must only be used locally during the initial nodal SLAT process
(when your craft computer is connected directly to the LAN-15 port on the
SP in a 6500-7 packet-optical, 2-slot, 14-slot or 7-slot shelf or LAN-41 port
in a 32-slot shelf). Do not run SAT remotely over DCN.
Prerequisites
• have Site Manager installed
Note: Java Web Start (JWS) is no longer supported.

• ensure that photonic circuit packs are seated in the shelf
• ensure that all External Inventory equipment (for example, CMDs and
DSCMs) is connected to the shelf access panel via CAT5 cables as
indicated in the EDP/IDP.
Step Action
Clearing the Java cache on your craft computer (to ensure the correct SAT load is executed)
Note 1: You only need to execute step 1 to step 7 once before the first time
you launch SAT.
Note 2: The following steps are based on Windows 7. Equivalent steps
should be performed is using Windows 10, Mac OS, or Linux. Refer to the
platform related or Java documentation for details.
1 In the Windows Start menu, select Control Panel.


Step Action
2 In the Control Panel, select the Java entry.

3 In the General tab of the Java Control Panel, click Settings in the Temporary
Internet Files section.
4 Click Delete Files in the Temporary Files Settings dialog.
5 In the Delete Temporary Files confirmation dialog, make sure that only the
Applications and Applets check box is checked, then click OK.
6 Click OK in the Temporary Files Settings dialog.
7 Click OK in the Java Control Panel.
Launching Advanced SLAT
8 Launch Site Manager.
9 Make sure the Use SSH checkbox is not checked.
10 In the Login screen, select Connection type as Craft Ethernet and enter the
IP address of the network element. The default IPv4 address of an NE is
10.0.0.1.
IPv6 is disabled by default and not accessible through the craft port until
enabled (in the NE Configuration Commissioning Step).
11 Enter the User ID and Password (ADMIN/ADMIN by default).
12 Click Connect.
13 If the shelf is not commissioned, a dialog box is displayed containing a
message that Site Manager has detected the uncommissioned status. You
have the option to launch Advanced SLAT or Node Setup to commission the
shelf, or to continue with Site Manager. When you select one of the
commissioning tools, you are logged out of Site Manager.
If you select the following option Then
Site Manager go to step 15
Node Setup you will be logged out of Site Manager.
Advanced SLAT you will be logged out of Site Manager.
15 From the Tools menu, select 6500 -> Advanced SLAT.

A login screen appears.


Step Action
Logging into the SLAT Assistant Tool

16 In the Login screen, leave the Domain at the Default domain.
17 Enter the username and password (ADMIN/ADMIN by default).
18 Click Login.
19 Click OK in the security banner.
The SLAT Assistant Tool window opens with the first Commissioning Step
highlighted.
If the shelf is already provisioned, a warning message is displayed. Follow the
detailed instructions provided in the message on how to proceed (depending
on whether the provisioning data is expected, or the shelf is being
re-commissioned with, or without physical cards present on the shelf).
20 Go to Procedure 2-6, “Commissioning a network element using Advanced
SLAT” if you are logging in for the first time or Procedure 2-26, “Provisioning
craft access” if you are logging back in after setting the shelf IP address. If the
Apply button is disabled and provisioning is entered, you can hover over the
Apply button and the tooltip will display the information over the error blocking
the Apply button.
After you complete a task, click Next to advance to the next task in the task
list. A green check mark will appear next to the task just completed, except
the “Craft Access Provisioning” task.
Click Previous to return to the previous task in the task list. Click Refresh to
refresh the current screen.
Note: The Last Refresh field at the bottom of the SAT screen displays the NE
time in GMT.
After an Advanced SLAT session is closed, the step tracking information
(check mark) is lost, but all applied provisioning is maintained.
Advanced SLAT tasks that follow the NE Configuration task are enabled only
after you complete the NE Configuration task.
—end—

Procedure 2-6
Commissioning a network element using Advanced
SLAT
Use this procedure to enter the NE identification, NE configuration, and GNE
configuration data for the network element in Advanced SLAT. See Table 1-2
on page 1-8 for detailed information.
ATTENTION

In order to perform NE commissioning, you must complete all mandatory

fields in the NE Identification Commissioning Step, apply them to the NE and
click on the Next button to sequentially advance to the next Commissioning
Step on the Commissioning Step navigation list until you complete the GNE
Configuration Commissioning Step.
Commissioning Steps that require shelf number for their execution will be
blocked by Advanced SLAT if the shelf number is not defined. The only two
Commissioning Steps that will be enabled by Advanced SLAT when the shelf
number is not defined are NE Identification and NE Configuration.
Note: Provisioned shelf current should be set after the shelf number has
been provisioned and prior to provisioning any other shelf parameters. To
determine the Provisioned shelf current value, refer to Administration and
Security, 323-1851-301 for the engineering rules.
Prerequisites
• make sure that there are no other active login sessions to the NE (such as
monitoring from OneControl, open TL-1 sessions, open Site Manager
sessions)
• be logged into the network element
• have the SLAT Assistant Tool open with the NE Identification
Commissioning Step highlighted


Commissioning a network element using Advanced SLAT
Step Action
1 If Then go to
a message opens indicating that provisioning data has step 2
been detected on the shelf
otherwise step 3
2 If provisioning data has been detected on the shelf, follow the detailed
instructions provided in the message on how to proceed (depending on
whether the provisioning data is expected, or the shelf is being
re-commissioned with, or without physical cards present on the shelf).
If you click the Delete Shelf button:
• If no physical cards are present in the shelf, the SLAT tool will start the
process to delete the existing provisioning.
• If physical cards are present in the shelf, a message opens indicating
that:
— Physical cards have been detected in the shelf.
— To remove the existing provisioning data, you must remove all the
physical cards from the shelf, except the active shelf processor and
the filler cards. (See Fault Management - Module Replacement,
323-1851-545 for the steps to unseat and remove the equipment.)
The active SP must be in slot 15 (for 2-slot, 7-slot, 6500-7
packet-optical, and 14-slot shelves) or slot 41 (for 32-slot shelves).
Then click the OK button in the physical cards detected message.
Then click the Delete Shelf button in the provisioning data detected
message to proceed with the delete operation.
• After you have clicked the Delete Shelf button:
a. The shelf restarts and the connection to the network element is dropped.
b. Exit the Advanced SLAT by clicking the X button in the top right corner of
the window.
c. Log back in with Advanced SLAT using Procedure 2-5, “Launching
Advanced SLAT and logging in”.
3 In the NE Identification panel, enter a network element name in the NE Name
field. Refer to Table 1-2 on page 1-8 for provisioning rules.
4 Enter the CLLI value in the CLLI field.
5 Optionally, enter the extended NE name in the Extended NE Name field.
Refer to Table 1-2 on page 1-8 for provisioning rules.
This step can take up to 90 seconds to complete.


Step Action
7 Click Next.
The next Commissioning Step panel appears.
8 Enter the Shelf Number in the NE Configuration IPv4 panel.
10 Use Site Manager to set the Provisioned shelf current value. Refer to the
Editing the nodal system parameters procedure in Administration and
Security, 323-1851-301.
11 Enter the other parameters in the NE Configuration IPv4 panel (refer to Table
1-2 on page 1-8 for provisioning rules).
The IPv4 panel includes several shelf parameters that are independent of
IPv4/IPv6 addressing, therefore even if provisioning an IPv6-only shelf, make
sure to complete other provisioning on the IPv4 panel.
Either an IPv4 or an IPv6 shelf IP address, or both, must be provisioned on
the shelf.
If IPv4 is required, set IPv4 to ON and provision an IPv4 shelf IP address. If
IPv4 is not required, set IPv4 to OFF, leave the IPv4 shelf IP address blank
and ensure that GCC and OSC auto-provisioning are disabled.
If IPv6 is required, set IPv6 to ON in this step. If IPv6 is not required, set IPv6
to OFF. IPv6 tabs on this and subsequent steps are enabled only if IPv6 is set
to ON.
For more information on shelf parameters, refer to Administration and
Security, 323-1851-301.
It is recommended to enable TID consolidation on all shelves running 6500
release 5.0 or higher. If there are other 6500 network elements at the same
site as the TID consolidated node and they are interconnected to the TID
consolidated node using the ILAN ports, make sure that the other network
elements have a different NE Name (TID) from the TID consolidated node.
Otherwise, the other network elements will be auto-discovered by the primary
shelf of the TID consolidated node and the primary shelf will raise the
Member Shelf Unknown alarm.
Note: When provisioning a TIDc primary shelf, ensure the TID Consolidation
Primary field is set to ENABLE. When provisioning a TIDc member shelf,
ensure the TID Consolidation Primary field is set to DISABLE.


Step Action

If Then go to
you must provision the IPv6 panel also step 14
otherwise step 16
14 Provision the parameters in the IPv6 panel (refer to Table 1-2 on page 1-8 and
Table 1-4 on page 1-31). An asterisk (*) denotes mandatory parameters,
which must be entered, if enabled.
16 For a SONET or SDH-J network element, verify that the blue LED on each
circuit pack is on.
This step can take a few minutes to complete.
For an SDH network element, the blue LED will not be on until auto-equipping
is enabled in Procedure 2-7, “Enabling or disabling auto-equipping”.
17 Click Confirm Completion, then click Next.
If your shelf Then go to
is equipped with NTK615AA/NTK615BA or step 19
circuit packs
is not equipped with NTK615AA/NTK615BA or step 26
circuit packs
19 Seat one PKT/OTN XC circuit pack (NTK615AA/NTK615BA or NTK616AA/

NTK616BA) and wait until the green and the blue LEDs on the XC stop
blinking and remain solid (approximately 25 minutes).
Alarms may be raised during the interval, which should clear automatically.
CAUTION
Ensure that any alarms associated with the fans are cleared
before proceeding (for example, fan failed, fan missing,
incompatible fan, or equipment configuration mismatch).
Installing the circuit packs with failed, missing, or wrong fans
may cause the circuit packs to be damaged by overheating.


Step Action
21 Seat all remaining circuit packs that you must equip in the shelf.
22 Wait until the green LEDs on all circuit packs turn steadily on. For the
cross-connect circuit pack, the blue LED should also be on.
Note: The blue LEDs will also be on for other circuit packs that have
auto-equipping enabled and are in-service.
If any of the circuit packs do not power up properly, first try to unseat and
reseat the circuit pack to make sure the circuit pack is inserted into the
backplane correctly. If the red LED on the circuit pack is lit, replace the circuit
pack. Refer to Fault Management - Module Replacement, 323-1851-545, for
the appropriate procedures.
23 Select Active Alarms from the Faults drop-down menu.
24 Review the active alarms and ensure that all “Software Auto-upgrade in
Progress” alarms have cleared before proceeding to the next step.
The “Software Auto-upgrade in Progress” alarm indicates that a circuit pack
is in the process of being auto-upgraded/downgraded to the active release of
the network element. This alarm will clear on its own once the process is
complete. See Part 2 of Fault Management - Alarm Clearing, 323-1851-543,
for details of the “Software Auto-upgrade in Progress” alarm.
26 Select your next step. If you are using Dual Stack IPv4/IPv6, you must
provision the parameters in both the IPv4 tab and the IPv6 tab.
If you are provisioning the GNE Configuration panel for Then go to
IPv4 step 27
IPv6 step 32
27 If you select No in the GNE drop-down list, all GNE parameters are blocked.
28 If you select Yes in the GNE drop-down list, select the data communication
configuration from the displayed list. (Based on the selected comms
configuration, some GNE parameters are blocked.)
29 Enter the GNE parameters in the GNE Configuration panel (refer to Table 1-2
on page 1-8 for provisioning rules).
30 Click Confirm Completion to apply the changes to the network element.


Step Action

If Then go to
otherwise step 35
32 If you select No in the GNE drop-down list, all items in the displayed GNE list
are blocked.
33 If you select Yes in the GNE drop-down list, select the data communication
configuration from the displayed list. (Based on the selected comms
configuration, some GNE parameters are blocked.)
34 Click Confirm Selection to apply the changes to the network element.
35 Click Next.
Go to Procedure 2-7, “Enabling or disabling auto-equipping”.
—end—

Procedure 2-7
Enabling or disabling auto-equipping
Use this procedure to enable or disable the auto-equipping mode for each
individual slot or for all slots simultaneously.
By default, auto-equipping is enabled if the NE mode is SONET or SDH-J, and

disabled if the NE mode is SDH. Therefore, this procedure is mandatory for
SDH network elements, optional for SONET and SDH-J network elements.
Prerequisites
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted
Step Action
1 In the Auto Equipping panel, click on the Select All button or Deselect All
button to enable/disable auto-equipping for all slots. The following slots can
be provisioned:
• slot 1, 2, 15 and 25-27 for 2-slot shelf
• slot 1, 2, 15 and 83-90 for 2-slot optical Type 2 shelf with SPAP-2 w/
2xOSC
• slot 1 to 7, 15 and 83-86 for 7-slot shelf
• slot 1 to 7, 15 and 83-90 for 7-slot Optical Type 2 shelf
• slot 1 to 16, 83 to 90 for 14-slot shelf
• slot 1 to 18, 21 to 28, 31 to 38, 41, 42 and 51 to 62 for 32-slot shelf
• slot 1 to 8, 15, 16 and 83 to 86 for 6500-7 packet-optical shelf
2 Select individual check boxes to enable/disable auto-equipping for individual
slots.
You can cancel the changes by clicking Cancel.
Unselected slot indicates that when a circuit pack is inserted into the slot, it
does not automatically go in-service and generate alarms.
4 For an SDH network element, verify that the blue LED on each circuit pack is
on. This step can take a few minutes to complete.


Enabling or disabling auto-equipping
Step Action
5 Click Next.
Go to Procedure 2-8, “Performing a lamp test”.
—end—

Procedure 2-8
Performing a lamp test
Use this procedure to verify that all LEDs on the shelf are working properly.
Prerequisites
highlighted
Step Action
1 In the Lamp Test panel, click Apply to verify that all LEDs illuminate for
30 seconds.
If any of the LEDs does not illuminate, first check if there are any active
alarms against the unit the LED is located. Follow the appropriate procedures
in Part 1 and Part 2 of Fault Management - Alarm Clearing, 323-1851-543 to
clear the alarms. Otherwise, the LED is defective. Replace the unit by
following the appropriate procedures in Fault Management - Module
Replacement, 323-1851-545.
2 Click Next.
Go to Procedure 2-9, “Provisioning OSPF router parameters”.
—end—

Procedure 2-9
Provisioning OSPF router parameters
If OSPF routing is required, use this procedure to provision the OSPF router
ID (mandatory) and other OSPF router parameters.
Before performing the provisioning steps, refer to the data communications

planning in Data Communications Planning and User Guide, 323-1851-101,
in order to understand the specific configurations.
Note: If the OSC SFP equipment is auto created before the shelf IP is
entered, OSPFv2 routers and circuits are not created. For OSC OSPFv2
auto provisioning, shelf IP must be provisioned before ED-SYS command
is applied.
Prerequisites
highlighted
Step Action
If you are provisioning the OSPF Router Provisioning Then go to
panel for
IPv4 step 2
IPv6 step 6
2 In the OSPF Router Provisioning panel, enter the shelf IPv4 address in the
Router ID field (mandatory).


Provisioning OSPF router parameters
Step Action
3 Enter the other parameters in the rest of the fields, as applicable. Refer to
Table 1-3 on page 1-27 for provisioning rules.
A Delete button is available if you want to delete the entry.
If Then go to
otherwise step 8
6 Enter the OSPFv3 Router id in the Router ID field (mandatory). Follow the
recommendations displayed in the panel. Refer to Table 1-4 on page 1-31 for
provisioning rules.
If an OSPFv2 router ID has been provisioned, the SLAT tool will autopopulate
the OSPFv2 router id in the OSPFv3 Router id field. If the OSPFv3 ID is
autopopulated, it is not provisioned until the user selects Apply.
8 Click Next.
Go to Procedure 2-10, “Provisioning ILAN”.
—end—

Procedure 2-10
Provisioning ILAN
Use this procedure to provision the intershelf local area network (ILAN). This
procedure is required only if the network element must connect to other
network elements’ ILAN. Otherwise, click Confirm Completion. Then click
Next to go to the next procedure.
If you intend to use ILAN, make sure that the shelf IP address is also
provisioned.
Prerequisites
highlighted
Step Action
If you are provisioning for Then go to
IPv4 step 2
IPv6 step 7
2 In the ILAN Provisioning panel, click Add.


Provisioning ILAN
Step Action
3 In the Add ILAN port data dialog box:

a. Select an ILAN port.
b. Enter the IPv4 address.
If an IPv4 LAN interface address is unnumbered, the IPv6 LAN interface
address must be unnumbered, and vice versa. (If the rule is not met, you
will see an Operation failed error message.)
When you try to add or edit an IPv4 address on a LAN interface, the
system checks for the above rule only if IPv6 is supported by the NE or if
IPv6 is enabled on the NE. Otherwise, the system does not run the check.
c. Enter the subnet mask.
d. Select YES or NO to enable or disable the port.
IPv4 and IPv6 use the same port. For example, if port enabled is set to
NO on the IPv6 ILAN-IN provisioning, then the IPv4 ILAN-IN provisioning
port will be disabled also.
Port enabled cannot be set to NO if an IPv4 or IPv6 OPSF circuit exists
on that interface.
e. Select the routing protocol (NONE, OSPF, IISIS, or OSPF/IISIS).
f. Provision the circuit parameters (see Table 1-3 on page 1-27).
g. Click OK.
4 Repeat step 2 to step 3 for the other ILAN port, if applicable.
You can select one of the rows in the table and click Delete or Edit to delete
or edit that entry.
5 In the ILAN Provisioning panel, click Confirm Completion.
If Then go to
otherwise step 11
7 In the IPv6 panel, click Add.


Provisioning ILAN
Step Action
8 Enter the required information in the Add ILAN port data dialog box:
a. Select an ILAN port.
b. Enter the IPv6 address.
If an IPv4 LAN interface address is unnumbered, the IPv6 LAN interface
address must be unnumbered, and vice versa. (If the rule is not met, you
will see an Operation failed error message.)
When you try to add or edit an IPv4 address on a LAN interface, the
system checks for the above rule only if IPv6 is supported by the NE or if
IPv6 is enabled on the NE. Otherwise, the system does not run the check.
c. Enter the subnet mask.
d. Select YES or NO to enable or disable the port.
IPv4 and IPv6 use the same port. For example, if port enabled is set to
NO on the IPv6 ILAN-IN provisioning, then the IPv4 ILAN-IN provisioning
port will be disabled also.
Port enabled cannot be set to NO if an IPv4 or IPv6 OPSF circuit exists
on that interface.
e. Select the routing protocol (NONE or OSPF).
f. Provision the circuit parameters (see Table 1-4 on page 1-31).
g. Click OK.
9 Repeat step 7 and step 8 for the other ILAN port, if applicable.
You can select one of the rows in the table and click Delete or Edit to delete
or edit that entry.
10 In the IPv6 panel, click Confirm Completion.
11 Click Next.
Go to Procedure 2-11, “Provisioning Shelf IP address”.
—end—

Procedure 2-11
Provisioning Shelf IP address
Use this procedure to provision the shelf IP address for the shelf. You can also
define the OSPF circuit parameters for the Shelf port.
All shelves require either an IPv4 shelf address, an IPv6 shelf address, or
both.
Note: When reprovisioning a member shelf, the 6500 can lose TL-1
access and you cannot recover TIDc member following a SLAT. You can
restart the primary shelf so the new member will properly auto-enroll or
use a different shelf IP for the member when re-provisioning it.
Prerequisites
• have SLAT Assistant Tool open with the Commissioning Step highlighted
• ensure that the shelf IP address is not defined
Step Action
If you are provisioning the Shelf IP Provisioning panel for Then go to
IPv4 step 2
IPv6 step 8
2 In the Shelf IP Provisioning panel, select the IPv4 tab and enter the shelf IPv4
address.
3 Select the routing protocol for the port.


Provisioning Shelf IP address
Step Action
4 Provision the parameters for the routing protocol you selected.

If you select Then provision
OSPF the OSPFv2 circuit parameters (see Table 1-3 on page
1-27)
IISIS the IISIS circuit parameters (see Table 1-3 on page 1-27)
OSPF/IISIS both the OSPFv2 and IISIS circuit parameters (see Table
1-3 on page 1-27)
5 Click Apply to apply the changes to the shelf.

6 If a confirmation dialog appears, click Yes in the confirmation dialog.
If Then go to
you must provision the IPv6 tab also step 8
otherwise step 10
8 Select the IPv6 tab.

9 Provision the parameters in the IPv6 panel. An asterisk (*) denotes
mandatory parameters, which must be entered, if enabled. For OSPFv3
parameters, see Table 1-4 on page 1-31.
Then, click Confirm Completion and click Apply to apply the changes to the
shelf.
10 Click Next.
11 Test the provisioned IP addresses by performing a ping from the DCN to
ensure that comms are provisioned correctly to the network element being
commissioned. Refer to the “Using the ping and trace commands”
procedures in Data Communications Planning and User Guide,
323-1851-101.
If you are provisioning IPv6 only, go to Procedure 2-13, “Provisioning
COLAN”.
Go to Procedure 2-12, “Provisioning IISIS router parameters” if otherwise.
—end—

Procedure 2-12
Provisioning IISIS router parameters
If IISIS routing is required, use this procedure to provision IISIS router
parameters. This procedure applies to IPv4 only.

If you will be provisioning IISIS router parameters during the Shelf IP, COLAN,
or GCC Provisioning steps, you do not have to provision the router at the IISIS
Router Provisioning step. The IISIS router provisioning during the Shelf IP,
COLAN, or GCC Provisioning steps overwrites the router provisioning
performed at the IISIS Router Provisioning step.
Prerequisites
highlighted
Step Action
1 In the IISIS Router Provisioning panel, enter the parameters in the fields, as
applicable. See Table 1-3 on page 1-27 for parameter details.
3 Click Next.
Go to Procedure 2-13, “Provisioning COLAN”.
—end—

Procedure 2-13
Provisioning COLAN
Use this procedure to provision the central office local area network (COLAN).
This procedure is required only if the network element is connected directly to
the data communications network (DCN). Otherwise, skip this procedure.
The following COLAN ports are defined on a 6500 NE:

• COLAN-X port, automatically switch to provide Ethernet access to the
“active” SP
• COLAN-A port, provides Ethernet access to the SP in slot 15 (or 41) and
16 (or 42)
Prerequisites
highlighted
Step Action
IPv4 step 2
IPv6 step 7
2 In the COLAN Provisioning panel, click Add.

3 In the Add dialog box, enter the parameters in the fields, as applicable. Refer
to “COLAN Provisioning” section in Table 1-2 on page 1-8 for parameter
details. If you select OSPF, IISIS, or OSPF/IISIS for the routing protocol,
provision the OSPF, IISIS, or OSPF/IISIS circuit parameters, respectively
(see Table 1-3 on page 1-27).
IPv4 and IPv6 use the same port. For example, if port enabled is set to NO
on the IPv6 COLAN-X provisioning, then the IPv4 COLAN-X provisioning port
will be disabled also.
Port enabled cannot be set to NO if an IPv4 or IPv6 OPSF circuit exists on
that interface.


Provisioning COLAN
Step Action
4 Click OK in the Add dialog box.

A new row, with the entered values, is added to the table.
You can select one of the rows in the table and click Delete or Edit button to
delete or edit an entry.
5 In the COLAN Provisioning IPv4 panel, click Confirm Completion.
If Then go to
otherwise step 9
7 Provision the parameters in the IPv6 panel. An asterisk (*) denotes

mandatory parameters, which must be entered, if enabled. See Table 1-2 on
page 1-8.
IPv4 and IPv6 use the same port. For example, if port enabled is set to NO
on the IPv6 Colan-x provisioning, then the IPv4 COLAN-x provisioning port
will be disabled also.
Port enabled cannot be set to NO if an IPv4 or IPv6 OPSF circuit exists on
that interface.
8 After you finished provisioning all the required parameters, click Confirm
Completion.
9 Click Next.
Go to Procedure 2-14, “Provisioning proxy ARP (IPv4)/ND Proxy Provisioning
(IPv6)”.
—end—

Procedure 2-14
Provisioning proxy ARP (IPv4)/ND Proxy Provisioning
(IPv6)
Use this procedure to provision proxy ARP for IPv4 and perform ND Proxy
provisioning for IPv6. Proxy ARP and ND Proxy are supported on the COLAN
X port only.
Proxy ARP provisioning is required for IPv4 only if you require proxy ARP to
reply to ARP requests directed at other NEs. Otherwise, skip this procedure
for IPv4.
ND Proxy provisioning is required for IPv6 if you require this shelf to respond
to Neighbor Solicitation requests on behalf of subtending shelves.
To enable proxy ARP, the network element must be a GNE and have proxy
ARP enabled.
Prerequisites
highlighted
Step Action
IPv4 step 2
IPv6 step 7
2 In the IPv4 (Proxy ARP Provisioning) panel, click Add.

3 In the Add dialog box, enter a single ARP address in the Start Address field
or enter a range of ARP addresses in the Start Address and End Address
fields.


Provisioning proxy ARP (IPv4)/ND Proxy Provisioning (IPv6)
Step Action

The single ARP address defined by the start address or the range of ARP
addresses defined by the start and end addresses is now displayed in the IP
Address table.
You can select one of the rows in the table and click Delete to delete the entry.
5 In the Proxy ARP Provisioning panel, click Confirm Completion.
If Then go to
you must provision the IPv6 (NDP Provisioning) panel also step 7
otherwise step 11
7 In the IPv6 (NDP Provisioning) panel, click Add.

8 In the Add dialog box, enter a single ND Proxy IPv6 address in the IP Address
field.
10 Click Confirm Completion in the IPv6 (NDP Provisioning) panel to apply the
changes to the network element.
11 Click Next.
Go to Procedure 2-15, “Provisioning NAT”.
—end—

Procedure 2-15
Provisioning NAT
Use this procedure to provision the network address translation (NAT) table.
This table allows a GNE to map an allocated DCN IP address to the NE IP
address provisioned on the NE. This procedure applies to IPv4 only.
Prerequisites
highlighted
Step Action
1 In the NAT Provisioning panel, click Add.

2 In the Add dialog box:
• enter the DCN IP address
• enter the Remote NE IP address
• select the prime
• click OK
The entered value is displayed in the table.
3 Repeat step 1 and step 2 for all the entries.
4 In the NAT Provisioning panel, click Confirm Completion.
5 Click Next.
Go to Procedure 2-16, “Provisioning Dynamic NAT”.
—end—

Procedure 2-16
Provisioning Dynamic NAT
Use this procedure to provision the Dynamic network address translation
(NAT). This procedure applies to IPv4 only.
Prerequisites
highlighted
Step Action
1 In the Dynamic NAT Provisioning panel, enter the value for NAT Starting Port.
This value should be between 1024 and 65535.
2 Enter a value for Number of NAT Entries. This value should between 256 and
1024.
3 Click Apply.
Go to Procedure 2-17, “Provisioning Port Filtering”.
—end—

Procedure 2-17
Provisioning Port Filtering
Use this procedure to provision the Port filtering parameters.
There are two types of filters:

• ingress—Ingress port filters are supported in both IPv4 and IPv6, on all
6500-type shelves.
• egress—Egress port filters (REMFORWARDOUT) are only supported on
6500-type Private-IP GNE shelves.
Use the Add button to provision a new entry and the Delete button to delete
an existing entry.
Prerequisites
highlighted
Step Action
1 In the Port Filtering Provisioning panel, click on the Add button and enter the
parameters in the fields, as applicable. Refer to “Port Filtering Provisioning”
section in Table 1-2 on page 1-8 for provisioning values.
3 Click on the Confirm Completion button.
4 Click Next.
Go to Procedure 2-18, “Provisioning Reverse Port NAT”.
—end—

Procedure 2-18
Provisioning Reverse Port NAT
Use this procedure to provision the Reverse Port NAT parameters. This
procedure applies to IPv4 only.
Reverse Port NAT displays the information about mapping the TCP/UDP port
of external requests to other internal port numbers and use a single external
IP address to access service in the internal network.
The Reverse Port NAT entries can be added only in Standalone Private IP and
Redundant Private IP GNE configuration modes.
Use the Add button to provision a new entry and the Delete button to delete
an existing entry. The Add button is disabled when Static NAT entries exist.
Prerequisites
highlighted
Step Action
1 In the Reverse Port NAT Provisioning panel, click on the Add button and enter
the parameters in the fields, as applicable. Refer to “Reverse Port NAT
provisioning” section in Table 1-2 on page 1-8 for provisioning values.
3 Click on the Confirm Completion button.
4 Click Next.
Go to Procedure 2-19, “Provisioning Neighbor Discovery Protocol”.
—end—

Procedure 2-19
Provisioning Neighbor Discovery Protocol
Use this procedure to enable or disable the NDP (Neighbor Discovery
Protocol) feature on the shelf.
Prerequisites
• have the Advanced Nodal SLAT Assistant Tool open with the NDP
Provisioning Step highlighted
Step Action
1 In the NDP Provisioning panel, select Enabled or Disabled from the Admin
State drop-down list. Click Apply.
2 If no change is required, click Confirm Completion.
3 Click Next.
Go to Procedure 2-20, “Provisioning static routes”.
—end—

Procedure 2-20
Provisioning static routes
Use this procedure to provision static routes. One or more static routes are
required on non-OSPF GNE shelves, usually against the COLAN, to provide
reachability to external destinations. In most cases, these static routes must
be redistributed into the internal routing domain (OSPF or iISIS). For IPv4,
redistribution is done as a separate step. For IPv6, redistribution is specified
as part of the static route provisioning itself.
Depending on the specific requirements of the network, static routes may also
be required on other interfaces and shelves.
Prerequisites
highlighted
Step Action
IPv4 step 2
IPv6 step 8
2 In the IPv4 Static Routes Provisioning panel, click Add.

3 In the Add dialog box, enter the parameters for the static route. Refer to
“Static Routes Provisioning” section in Table 1-2 on page 1-8 for parameter
details. An asterisk (*) denotes mandatory parameters, which must be
entered, if enabled.


Provisioning static routes
Step Action

5 Repeat step 2 to step 4 for the other static routes, if applicable.
6 In the IPv4 Static Routes Provisioning panel, click Confirm Completion.
If Then go to
otherwise step 12
8 In the IPv6 Static Routes Provisioning panel, click Add. See Table 1-2 on
page 1-8 for parameter details.
9 In the Add dialog box, enter the parameters for the static route in the fields,
as applicable. Then, click OK. Note that redistribution of the static route into
OSPFv3 can be enabled in this step by setting Redistribute to OSPFv3, and
setting the RDTYPE (metric type) as either Internal (Type 1) or External
(Type 2).
10 Repeat step 8 and step 9 for the other static routes, if applicable.
11 Click Confirm Completion to apply the changes to the network element.
12 Click Next.
Go to Procedure 2-21, “Provisioning OSPF routes distribution”.
—end—

Procedure 2-21
Provisioning OSPF routes distribution
Use this procedure to provision route redistribution on the OSPF router.
Routes can be distributed into OSPFv2 from the following two sources:
• iISIS (ISISRDLIST)
• static routes (STATICRDLIST)

Prerequisites
highlighted
Step Action
1 In the OSPF - Routes Distribution panel, click Add.

2 In the Add Distributed Route dialog box, enter the parameters in the fields, as
applicable. Refer to Table 1-2 on page 1-8 “OSPF - Routes Distribution”
section in Table 1-3 on page 1-27 for parameter details.
• enter the IP address
• enter the subnet mask
• enter the metric
• select a metric type (internal or external)
• select a distribution list (IISISRDLIST or STATICRDLIST)
You can select one of the rows in the table and click Delete to delete an entry.
4 Repeat step 1 to step 3 for the other routes, if applicable.
5 In the OSPF - Routes Distribution panel, verify the route distribution data.
Then click Confirm Completion.
6 Click Next.
Go to Procedure 2-22, “Provisioning IISIS routes distribution”.
—end—

Procedure 2-22
Provisioning IISIS routes distribution
Use this procedure to provision routes distribution on the IISIS router. This
procedure applies to IPv4 only. Routes can be distributed into iISIS from the
following two sources:
• OSPF (OSPFRDLIST)
• static routes (STATICRDLIST)

Prerequisites
highlighted
Step Action
1 In the IISIS - Routes Distribution panel, click Add.

2 In the Add Distributed Route dialog box, enter the parameters in the fields, as
applicable. Refer to “IISIS - Routes Distribution” section in Table 1-3 on page
1-27 for parameter details.
You can select one of the rows in the table and click Delete to delete an entry.
4 Repeat step 1 to step 3 for the other routes, if applicable.
5 In the IISIS - Routes Distribution panel, click Confirm Completion.
6 Click Next.
Go to Procedure 2-23, “Provisioning SNMP”.
—end—

Procedure 2-23
Provisioning SNMP
Use this procedure to provision the SNMP for the network element.
ATTENTION

Prerequisites
highlighted
Step Action
1 In the SNMP Provisioning panel, set the SNMP state to Enabled or Disabled.
To set the SNMP State to Enabled, select Enabled and click Apply SNMP
Data.
2 In the SNMP provisioning panel, select the SNMP Version.
3 Enable or disable alarm masking.
4 Enable or disable SNMP proxy. If SNMP proxy is enabled, enter a proxy
timeout value.
5 Click Apply SNMP Data.
6 Select a destination ID from the SNMP Trap Destinations table and click Edit
Trap Destination.
7 In the Edit SNMP Trap Destinations dialog box, edit the IP address and UDP
port and the TRAP Configuration for that destination and click OK.


Provisioning SNMP
Step Action
8 Repeat step 6 and step 7 for the remaining destination IDs, if applicable.
9 In the SNMP provisioning panel, click Confirm Completion.
10 Click Next.
Go to Procedure 2-24, “Provisioning security”.
—end—

Procedure 2-24
Provisioning security
Use this procedure to provision the security attributes for the network element.
On a member shelf, only Intrusion detection status is provisionable. You can
leave the default settings, and change them at a later time.
Prerequisites
highlighted
Step Action
1 In the Security Provisioning panel, enter the parameters in the fields, as

applicable. Refer to “Security Provisioning” section in Table 1-2 on page 1-8
for parameter details.
2 In the Security provisioning panel, click Apply to apply the changes.
3 Click Next.
Go to Procedure 2-25, “Provisioning SSH/TELNET and HTTP/HTTPS
Server”.
—end—

Procedure 2-25
Provisioning SSH/TELNET and HTTP/HTTPS Server
Use this procedure to provision the Secure Shell (SSH), Telnet, and HTTP/
HTTPS server for the network element.
Prerequisites
highlighted
Step Action
1 In the SSH/TELNET and HTTP/HTTPS Server Provisioning panel, set the

SSH server active state to DISABLED or ENABLED.
2 If the SSH server active state is ENABLED, enter the values for Maximum
SSH active sessions and SSH server idle timeout.
If both SSH and telnet servers are enabled, the total maximum number of
SSH and telnet sessions must not exceed the system maximum number of
sessions (21).
IPv4 and IPv6 initiated sessions combine together for the total number of
sessions.
3 In the SSH/TELNET and HTTP/HTTPS Server Provisioning panel, set the
Telnet server active state to DISABLED or ENABLED.
4 If the Telnet server active state is ENABLED, enter the values for Maximum
telnet active sessions and Telnet server idle timeout.
If both SSH and telnet servers are enabled, the total maximum number of
SSH and telnet sessions must not exceed the system maximum number of
sessions (21).
IPv4 and IPv6 initiated sessions combine together for the total number of
sessions.
5 Set the HTTP server active state to ON or OFF.
6 Set the HTTPS server active state to ON or OFF.
7 In the provisioning panel, click Apply to apply the changes.
8 Click Next.
Go to Procedure 2-26, “Provisioning craft access”.
—end—

Procedure 2-26
Provisioning craft access
Use this procedure to provision the craft LAN-15 (or 41) and LAN-16 (or 42)
port IPv4 address. To access the IPv6 craft port IP, IPv6 must be turned on
through Site Manager access through IPv4, because IPv6 is disabled by
default.
This procedure is required only if you want the ability to access remote
network elements using the LAN-15 (or 41) or LAN-16 (or 42) port. Otherwise,
skip this procedure.

Prerequisites
highlighted
Step Action
1 Read the instructions displayed in the panel.

2 Select the required Craft LAN port in the LAN ports table.
3 In the Craft Provisioning panel, click Edit.
4 In the Edit dialog box, enter a unique IP address for the LAN port in the craft
IP Address field.
The default craft IP address is 10.0.0.1.
5 In the Edit dialog box, enter a subnet mask for the LAN port in the Subnet
Mask field.
The default craft subnet mask is 255.255.255.252.
6 In the Edit dialog box, enter the other required parameters in the fields, as
applicable. Refer to Table 1-2 on page 1-8 for parameter details.
7 Click OK in the dialog box.


Step Action
If you are connected through the craft port, the connection to the network
element is dropped. An “Operation Failed” error message appears because
the software is unable to refresh the screen. This is expected.
CAUTION
Loss of step tracking information
This step (step 7) causes a logout. You must log back
into the network element. The step tracking
information (check mark) is lost, but all applied
provisioning is maintained.
8 Exit the Advanced SLAT by clicking the X button in the top right corner of the
window.
If you are using a Then go to
PC step 10
MAC step 11
If you are using a PC

10 At the command prompt on your craft computer, enter:
ipconfig /flushdns
ipconfig /release
ipconfig /renew
Then go to step 12.
If you are using a MAC
11 Navigate to Applications --> Utilities --> Terminal.
12 From the command output, verify that your craft computer is assigned the IP
address you just entered + or - 1, a subnet mask of 255.255.255.252, and a
default gateway that is the IP address you just entered.
For example, if you entered 47.123.123.111, your craft computer IP address
is now 47.123.123.112 or 47.123.123.110, with a default gateway of
47.123.123.111.


Step Action
13 Log back in with Advanced SLAT using Procedure 2-5, “Launching Advanced
SLAT and logging in”. Use the new LAN port IP address you just entered,
instead of the default IP address.
A message appears indicating that you are reconnecting after setting the craft
IP address.
14 Click OK to close the message.
15 If you have finished editing the craft access, click Confirm Completion.
Go to Procedure 2-27, “Provisioning craft OSPF/IISIS”.
—end—

Procedure 2-27
Provisioning craft OSPF/IISIS
Use this procedure to provision Craft OSPF/IISIS circuits. This step is
optional. The data should be filled only if you require craft reach through
capability.
This procedure is required only if you want the ability to access remote
network elements using the LAN-15 (or 41) or LAN-16 (or 42) port. Otherwise,
skip this procedure.
Craft OSPF data can only be provisioned if the craft IP address does not have
the default (IPv4) value (10.0.0.1 or 10.0.0.5).

Prerequisites
highlighted
Step Action
1 Read the instructions displayed in the panel.

2 Select the required Craft LAN port in the LAN ports table.
3 In the Craft OSPF/IISIS Provisioning panel, click Edit.
4 Select your routing protocol (NONE, OSPF, IISIS, or OSPF/IISIS) and
provision the parameters. Refer to “OSPF and IISIS parameters—SLAT
Assistant Tool - IPv4” on page 1-27 or “OSPFv3 parameters—SLAT Assistant
Tool - IPv6” on page 1-31 for parameter details.
If NONE is selected as the routing protocol, all fields are grayed out.
5 Click OK in the dialog box.
6 If you have finished editing the craft OSPF/IISIS, click Confirm Completion.
You have completed the SAT procedures for this network element. Exit SLAT
Assistant Tool by clicking the X button at the top right corner of the window.
Go to Procedure 2-28, “Checking, clearing, and provisioning alarms”.
—end—

Procedure 2-28
Checking, clearing, and provisioning alarms
Use this procedure to check and clear the active alarms on the network
element, and to provision alarm points. You must clear any unexpected
alarms.
Prerequisites
Step Action
1 Make sure that there are no equipment class alarms. Certain facility class
alarms are expected until the network SLAT is complete.
2 Clear any unexpected alarms according to Part 1 and Part 2 of Fault
Management - Alarm Clearing, 323-1851-543.
3 If you want to change the alarm severity for any alarm points, in the Site
Manager Alarm Profiles application under Configuration->Alarms & Controls:
a. Select a user alarm profile (User 1, for example) for the appropriate alarm
class.
b. Edit the user alarm profile name if you want. Refer to the “Editing an
alarm profile” procedure in Part 1 of Fault Management - Alarm Clearing,
323-1851-543.
c. Edit the severity for each alarm point you want to change. Refer to the
“Editing an alarm profile” procedure in Part 1 of Fault Management -
Alarm Clearing, 323-1851-543.
d. Set the modified alarm profile as the default. Refer to the “Setting a
default profile” procedure in Part 1 of Fault Management - Alarm
Clearing, 323-1851-543.
e. Set the modified alarm profile as active for all instances of facilities or
equipment which are already provisioned. Refer to the “Setting a profile
as active” procedure in Part 1 of Fault Management - Alarm Clearing,
323-1851-543.
All existing alarms that have a different severity in the modified profile will
be cleared and raised with the new severity.
You have completed this procedure.
For more (optional) initial provisioning, go to Procedure 2-29, “Post SLAT
commissioning”.
—end—

Procedure 2-29
Post SLAT commissioning
Use this procedure to perform the following optional tasks, as applicable to
your system:
• enabling the DHCP server on the craft IPv6 port
• connecting the network element (NE) to the DCN
CAUTION
• saving the golden database to a remote host. Perform this task if you want
to clone a provisioning golden database onto a number of newly
commissioned NEs that are physical clones.
• cloning a provisioning golden database onto a number of newly
commissioned NEs that are physical clones
Prerequisites
• To enable the DHCP server on the craft IPv6 port, you must:
— use an account with a UPC level of 4 or higher.
— be logged into the network element
• To set up a golden database, you must
— use an account with a UPC level of 3 or higher
— have the user identifier and password you want to set for the golden
user profile
— have the URL of the remote host where you will back up the golden
database
— be logged into the golden NE
— make sure you have provisioned the golden NE with the provisioning
database that will serve as the golden database
— make sure that you have provisioned communications on the golden
NE to perform the file transfer of the golden database to the remote
host


Step Action
• To restore the golden database onto newly commissioned NEs that are
physical clones, you must
— use an account with a UPC level of 3 or higher
— make sure that you have provisioned communications on the newly
commissioned NEs to perform the file transfer of the golden database
from the remote host
— make sure the newly commissioned NEs are physical clones of the
golden NE
CAUTION
Risk of DCC/GCC communications loss
If the newly commissioned NE is not a physical clone of the
golden NE, the DCC/GCC communications may not be
preserved. Perform a local restore on the newly commissioned
network element to restore the DCC/GCC communications.
Step Action
1 Select the task you must perform.

If Then
you want to connect the network element to the go to step 2
DCN
you want to enable the IPv6 DHCP server on the go to step 6
craft port
you want to set up a golden database go to step 11
you want to clone a provisioning golden database go to step 17
onto a number of newly commissioned network
elements that are physical clones
you have completed all the tasks applicable to you have completed this
your system procedure.
Connecting the network element to the DCN

2 If the network element was configured to be connected to the data
communications network (DCN), connect the COLAN Ethernet port to the
customer DCN. For a gateway network element (GNE), this connection can
be through a gateway router.


Step Action
3 Using a computer connected to the DCN, open a Site Manager session.

4 Enter the IP address that you assigned for the network element and log in as
an admin level user.
5 If the network element uses simple network timing protocol (SNTP) or remote
authentication dial in user service (RADIUS), verify that all alarms related to
visibility to their related servers have cleared.
You have completed this task. Go to step 1.
Enabling the IPv6 DHCP server on the craft port
6 In Site Manager, go to Comms Setting Management and select the Services
tab.
7 Under Service Type, select DHCP.
8 From the list of ports, select the craft port and click Edit.
9 Under IPv6 Server, select the ON radio button.
10 Click OK.
Saving the golden database
11 Select Backup and Restore from the Configuration menu.
12 In the Backup and Restore panel, select the Backup tab.
13 In the URL field enter the path to the remote host.
14 Select the Do not backup or restore Comms Settings data check box.
15 Click Check to perform pre-checks on the network element.
These pre-checks include checking that the URL of the remote host is
reachable and if the user ID and password are valid. The results of the checks
are shown in the message area. These checks are also run when Save is
selected.
If any of the checks fail, investigate and correct the problem before you
proceed. If you cannot identify the problem, contact your next level of support.
16 Click Save to save the provisioning data to the remote host.


Step Action
Restoring the golden database onto newly commissioned network elements

Backing up the local database
17 Select and log into one of the NEs onto which you will be cloning the golden
database.
19 In the Backup and Restore panel, select the Backup tab.
20 In the URL field enter “file:”.
22 Click Save to save the provisioning data to the shelf processor.
Restoring the golden database onto the newly commissioned NEs
24 In the Backup and Restore panel, select the Restore tab.
25 In the URL field enter the path to the remote host.
26 Select the Do not backup or restore Comms Settings data check box.
This option is not supported when the network element is running the Control
Plane (all types). Control Plane related comms settings are still backed up
when this option is selected.
These pre-checks include checking that the URL of the remote host is
reachable and if the user ID and password are valid. The results of the checks
are shown in the message area. These checks are also run when Restore is
selected.
If any of the checks fail, investigate and correct the problem before you
proceed. If you cannot identify the problem, contact your next level of support.
28 Click Restore to restore provisioning data from the remote host.
29 Wait until a “Validating restore...complete” message is displayed in the
message area.
30 Click Commit.
31 Click Yes in the confirmation dialog box.
32 Click OK in the warning dialog box.
The connection to the network element will be lost.
33 Wait for five minutes before you log back into the network element.
The Database Restore in Progress alarm clears.


Step Action
34 Check that GCC communications have been preserved. If the GCC

communications have not been preserved because the newly commissioned
NE is not a physical clone of the golden NE, perform a local restore to restore
the GCC communications as follows:
• Select Backup and Restore from the Configuration menu.
• In the Backup and Restore panel, select the Restore tab.
• In the URL field enter “file:”.
• Click Check to perform pre-checks on the network element.
• Click Restore to save the provisioning data to the shelf processor.
• Wait until a “Validating restore...complete” message is displayed in the
message area.
• Click Commit.
• Click Yes in the confirmation dialog box.
• Click OK in the warning dialog box.
The connection to the network element will be lost.
• Wait for five minutes before you log back into the network element.
The Database Restore in Progress alarm clears.
35 Repeat step 23 to step 34 for all the other newly commissioned NEs onto
which you want to clone the golden database.
—end—

Procedure 2-30
Commissioning fixed-plan terminal nodes using CLI
Use this procedure to commission fixed plan terminal nodes (also referred to
as Channel access nodes) using the 6500 command line interface (CLI).
Note 1: The CLI “install create” commands are only supported on 2-slot
or 7-slot compact shelves with SPAP2.
Note 2: The “install create” commands cannot be used for supported
configurations that include XLAs or SRAs. For these configurations, you
must commission the 6500 nodes as per standard 6500 procedures and
manually provision the equipment/slot sequence as detailed elsewhere in
this document.
Note 3: For the SRA, the “Forced Shut Off” parameter value for the
RAMAN facility must be set to “False” in order to bring up the RAMAN
pump lasers to ON. Refer to Part 1 of Configuration - Provisioning and
Note 4: For CMD64 configurations with MLA3/ESAM, XLA/ESAM, or
XLA/SRA, the “Tx Power Reduction Control” parameter value for the LOC
facility must be set to “Always Off” so the transponders/Waveserver ports
associated with CMD64 do not remain in reduced power state when SPLI
is established. Refer to Part 1 of Configuration - Provisioning and
The configurations can have Standard reach or Extended reach. For more
information, refer to “Standard reach and Extended reach configurations” on
page 2-11.
This procedure refers to CLI commands. For more information on CLI

command syntax, refer to CLI Reference, 323-1851-193.
Prerequisites
• Have the engineering data sheet for each site with the commissioning
information specific to your configuration. See Table 2-3 on page 2-17 for
commissioning parameters.
• have accessed the shelf through CLI, refer to Administration and Security,
323-1851-301 for more information.


Step Action
1 Select your configuration (see the Configuration column in Table 2-2 on page
2-13)
If your configuration is Then go to
Flex-12 [50GHz] (see Figure 5-10 on page 5-13 and Figure step 2
5-11 on page 5-14)
One of the following: step 3
• Fixed-96 [50GHz] unprotected (see Figure 5-2 on page 5-5
and Figure 5-3 on page 5-6)
• Fixed-96 [50GHz] protected (see Figure 5-16 on page 5-19)
• Fixed-88 [50GHz] unprotected (see Figure 5-6 on page 5-9)


Step Action
Commissioning a Flex-12 [50 GHz] configuration

2 Enter the “install create” command for Flex-12 [50GHz] (see Figure 5-10 on
page 5-13 and Figure 5-11 on page 5-14), see Table 2-2 on page 2-13.
The system sets the following parameters automatically:
• CS Control is set to ON.
Note: To check, use the following CLI command:
system config show
and verify the value of the cs-ctrl parameter.
• For both amplifiers embedded within the CCMD12:

— Target Gain is set to 23 dB.
— LOS thresholds are left at default values as follows:
- Input LOS threshold = -29.0 dBm
- Output LOS threshold = -12.0 dBm
- Shut Off threshold = -35.0 dBm
Note: To check:
amps amp show amp-1-1-<25|26>
You have completed the commissioning of the Flex-12 [50GHz] (see Figure
5-10 on page 5-13 and Figure 5-11 on page 5-14) configuration. Next perform
Procedure 5-1, “Connecting intra-site fibers for the fixed-plan terminal nodes
and performing site testing”.


Step Action
Commissioning a Fixed-96 [50GHz], Fixed-88 [50GHz], Fixed-44 [100GHz], or Fixed-64 [75GHz]

configuration (protected or unprotected)
3 Enter the “install create” command as applicable to your configuration, see
The system sets the following parameters automatically:
• CS Control is set to ON.
system config show
and verify the value of the cs-ctrl parameter.
• If your configuration is equipped with MLA2 or MLA3, the “install create”
command sets parameter values as indicated below. For protected
configurations, the parameter values are set for both MLA2/MLA3
modules in the shelf.
— Line A (AMP port 8) Input LOS Threshold is left at default value of
-36 dBm.
amps amp show amp-1-<1|2>-8
— Line B (AMP port 6) Gain Offset is set to +5.0 dB (for Fixed-96,

Fixed-88, or Fixed-44 configurations) or 0.0 dB (for Fixed-64
configurations) and Input LOS Threshold is set to -28 dBm.
• If your configuration is equipped with SLA, the “install create” command
sets parameter values as indicated below. For protected configurations,
the parameter values are set for both SLA modules in the shelf.
— Line A (AMP port 8) Input LOS Threshold is set to -35 dBm.
— Line B (OPTMON port 6) LOS Threshold is set to -28 dBm.

optmons optmon show optmon-1-<1|2>-6


Step Action
• SLA/MLA2/MLA3 Line B (ADJ-LINE port 5) parameters are set as

follows. For protected configurations, the parameter values are set for
both SLA/MLA2/MLA3 modules in the shelf.
— fiber-type: NDSF. If your deployed fiber type is not NDSF, you can edit
the fiber-type parameter in step 4.
— min-span-loss for SLA: 0 dB
— min-span-loss for MLA2/MLA3: 16 dB
— span-loss-margin: 3 dB
— target-span-loss: 21.5 dB (see Note 2)
Note 1: To check, use the following CLI command:

adjacencies line show adj-1-<1|2>-5
Note 2: In Procedure 5-3, “Connecting the inter-site fibers for fixed-plan
terminal nodes, performing additional provisioning, and testing the
photonic link”, after you connect the far-end node, you will set the target
span loss of SLA/MLA2/MLA3 Line B (ADJ-LINE port 5) to the expected
span loss value.
4 If your deployed fiber type is not NDSF, edit the fiber-type parameter (of SLA/
MLA2/MLA3 Line B [ADJ-LINE port 5]) to match the actual fiber type
deployed, using the following CLI command:
adjacencies line set adj-1-<1|2>-5 fiber-type <fiber-type
Value>
• For protected configurations, edit the fiber-type parameter for both line
interface modules (that is, both SLA/MLA2/MLA3 modules in the shelf).


Step Action
5 Select your next step. (For more information on Standard and Extended
reach, see “Standard reach and Extended reach configurations” on page
2-11.)
If your configuration Then
is being provisioned
for Standard reach you have completed this procedure. Next perform
Procedure 5-1, “Connecting intra-site fibers for the
fixed-plan terminal nodes and performing site
testing”.
Note: If your configuration is protected, additional
manual provisioning is required to complete setting
up the protected Terminal nodes with Standard
reach. After the transponder wavelengths are
connected to the 6500 Photonic system, the
procedures will direct you to the required steps.
for Extended reach go to step 6 to perform additional provisioning for
Extended reach configurations
Performing additional provisioning at Terminal nodes for Extended reach configurations

6 Set CS Control to OFF by entering:
system config set cs-ctrl off
7 Set the following parameters for Line A (port 8)
• Target Gain Tilt to -3.0 dB
and
• Target Gain to 27.0 dB
by entering
amps amp set amp-1-<1|2>-8 targ-gain-tilt -3 targ-gain 27
• For protected configurations, set the Line A (port 8) Target Gain Tilt and
Target Gain for both line interface modules (that is, both MLA2/MLA3
modules in the shelf).


Step Action
8 Set Line B (port 6) Target Gain Tilt to -2.5 dB by entering:

amps amp set amp-1-<1|2>-6 targ-gain-tilt -2.5
• For protected configurations, set the Line B (port 6) Target Gain Tilt for
both line interface modules (that is, both MLA2/MLA3 modules in the
shelf).

Next perform Procedure 5-1, “Connecting intra-site fibers for the fixed-plan
terminal nodes and performing site testing”.
Note: Additional manual provisioning is required to complete setting up the
Terminal nodes with Extended reach (protected or unprotected). After the
transponder wavelengths are connected to the 6500 Photonic system, the
procedures will direct you to the required steps.
—end—

Procedure 2-31
Commissioning 6500 Line Amp nodes using the CLI
Use this procedure to commission 6500 Line Amp nodes using the CLI.
(Examples of Line Amp configurations are illustrated in Figure 5-20 on page
5-23 and Figure 5-21 on page 5-24.)
This procedure refers to CLI commands. For more information on CLI

Prerequisites
• Have the engineering data sheet with the commissioning information
specific to your configuration. See Table 2-4 on page 2-21 for Line Amp
commissioning parameters.
• have accessed the shelf through CLI, refer to Administration and Security,
323-1851-301 for more information.
Step Action
1 Enter the following CLI commands to commission the shelf:

system sid set name <Site name>-<group-id>
shelves shelf create shelf-1 site-id <Site ID> site-name
<Site name> bay-num <group-id> [location <Location of the
site>]
system config set ne-mode sonet autoroute-def disable
cs-ctrl <Value> [alarm-info <alarm-info Value>]
where cs-ctrl Value is
— on, if your configuration includes MLAx+LIM
— off, if your configuration includes MLAx+MLAx
where MLAx is MLA2 or MLA3.


Step Action
Provisioning comms
Note: If DCN is not available at the Line Amp site, contact Ciena.
comms ip create colan-1-x ip-addr <COLAN ipv4 address>
netmask <Value>
comms ip create shelf-1 ip-addr <COLAN ipv4 address>
netmask <Value>
comms ospf router create shelf-1 router-id <COLAN ipv4
address>
comms ospf circuit create shelf-1 net-area <n.n.n.n>
comms ospf circuit create osc-1-15-1 net-area <n.n.n.n>
comms ospf circuit create osc-1-15-2 net-area <n.n.n.n>
Note: <n.n.n.n> is used on the Terminal nodes, where n is the first octet of
the IP address.
comms lan create colan-1-x
comms ip-static-route create shelf-1 cost <value> ip-addr
0.0.0.0 circuit colan-1-x netmask 0.0.0.0 next-hop
<Default gateway(Gateway ipv4 address)>
Confirming that the equipment is provisioned
2 Confirm that the equipment is provisioned.
equipment config show ALL
Configuring the line-facing modules
Note: In Procedure 5-3, “Connecting the inter-site fibers for fixed-plan
terminal nodes, performing additional provisioning, and testing the photonic
link”, after you connect the far-end node, you will set the target span loss of
MLAx Line B (ADJ-LINE port 5) to the expected span loss value.
If your Line Amp node includes Then go to
MLAx+MLAx (see Figure 5-21 on page 5-24) step 4
MLAx+LIM (see Figure 5-20 on page 5-23) step 8
Setting amplifier parameters for MLA3+MLA3 configurations

4 Enter the following CLI commands to configure the amplifiers in the shelf:
amps amp set amp-1-1-6 input-los-thres -28
amps amp set amp-1-2-6 input-los-thres -28
5 Provision the pad loss for 10 dB pads at mid-stage:
adjacencies fiber set ADJ-1-<1|2>-7 pad-loss 10


Step Action
6 Set Line A (AMP port 8) Target Gain Tilt to 0 dB and Target Gain to 23.5 dB
on both MLAx:
amps amp set amp-1-<1|2>-8 targ-gain-tilt 0 targ-gain
23.5
7 Set Line B (AMP port 6) Target Gain Tilt to -2.5 dB on both MLAx:
amps amp set amp-1-<1|2>-6 targ-gain-tilt -2.5
Go to step 9 for OTS provisioning.
Note: After the transponder wavelengths are connected to the 6500 Photonic
system (in the Chapter 5, “Fixed-plan terminal node procedures”), you will set
the Line B (AMP port 6) Target Gain on both MLAx. The procedures will direct
you to the required step.
Setting line-facing module parameters for MLA3+LIM configurations
8 Enter the following CLI commands:
amps amp set amp-1-<MLAx slot number>-6 input-los-thres
-8
optmons optmon set optmon-1-<LIM slot number>-6 los-thres
-20
OTS provisioning
9 Enter the following CLI commands.
Note that:
• At the Line Amp site, the line amp in slot 1 should be facing the remote
site with the lowest site-id, and the line amp in slot 2 should be facing the
remote site with the highest site-id.
• The Optical System ID (OSID) must match the Os Ids of the Terminal
nodes. At Terminal nodes, OSID is provisioned/queried as system-name
(see Table 2-3 on page 2-17. For more information on OSID at Terminal
nodes, also see site-id and remote-site-id.)
topology ots create ots-1-1 osid <Value> tx-path
<parity_value> cfgtype amp amp-mate ots-1-2 osc
osc-1-15-<1|2>
topology ots set ots-1-2 osc osc-1-15-<1|2>
10 Verify that the OTS has been created:

topology ots show ALL
You have completed the commissioning of the Line Amp node.
Next perform Procedure 5-1, “Connecting intra-site fibers for the fixed-plan
terminal nodes and performing site testing”.
—end—

3-1
Photonic layer provisioning procedures 3-

• “Photonic layer provisioning procedures” on page 3-3

BS band splitter
CCMD colorless Channel Mux/Demux
CDC ROADM colorless directionless contentionless ROADM (configurations

with Flex WSS C-Band w/OPM 20x1 in the ROADM OTS)
CDA Colorless CMD Direct Attach
COADM colorless optical add/drop multiplexer
CS Coherent Select
DGFF dynamic gain flattening filter
DIA direction independent access
DOC domain optical control
ESAM enhanced service access module
FGA fixed gain amplifier

3-2 Photonic layer provisioning procedures
MINMUXPOUT minimum mux power output
MLAx MLA, MLA2, or MLA3 amplifiers
MMPO minimum mux power output

NE network element
OMDF optical mux/demux filter
OPM optical power monitor
ORL optical return loss
OSCF OSC filter
RLA ROADM with line amplifier
Rx receive
SAM service access module
SMD selective Mux/Demux
SP shelf processor
SRA single line Raman amplifier
TR transmit/receive
Tx transmit

WSSOPM wavelength selective switch with optical power monitor
XLA switchable line amplifier
Photonic layer provisioning procedures

In the current release, the legacy OTS Management application is no longer
supported. All configurations use the Photonic Configuration Management
application to define the OTS type and specify equipment connectivity.
For the benefits provided by Photonic Configuration Management OTS

provisioning model, refer to 6500 Packet-Optical Platform Photonic Layer
Guide, NTRN15DA.
To provision the OTS using the Photonic Configuration Management

application:
• Provision equipment that are part of the OTS.
• Perform the “Creating an OTS instance with basic parameters” procedure
in Part 2 of Configuration - Provisioning and Operating, 323-1851-310.
Note: At DGFF sites, two OTSs must be provisioned. When you are
creating the first ROADM OTS, the second ROADM OTS is not auto-
created. You must provision manually the second ROADM OTS with the
same OTS Optical System Identifier.
• Perform the “Editing OTS slot sequences” procedure in Part 2 of

Configuration - Provisioning and Operating, 323-1851-310. All intra-OTS
adjacencies are system derived once the slot sequences are defined.
• For non-MPO WSSs, for example, WSS Flex C-Band w/OPM 9x1,
provision the far end WSS or extra-OTS equipment in the OTS branch slot
sequences. Perform the “Editing OTS slot sequences” procedure in Part 2
of Configuration - Provisioning and Operating, 323-1851-310.
• If your system includes root equipment, such as FIM or GMD10, perform
the “Editing TID slot sequences” procedure in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310.
• Provision the necessary photonic parameters using Procedure 3-1,
“Provisioning photonic parameters”.
• Provision the inter-OTS WSS-WSS adjacencies and line adjacencies
using Procedure 3-2, “Provisioning adjacencies”. If the OTS was
provisioned using slot sequences, manual far-end address provisioning of
the WSS-WSS adjacencies is not required.
• For Flex grid systems, refer to Configuration - Control Plane, 323-1851-
330, for all Flex grid channel procedures.

To provision the OTS for Coherent Select configurations:

• Make sure that Coherent Select provisioning for the shelf is enabled (CS
Control parameter). Depending on the node setup solution you have
selected, see:
— Advanced SLAT Assistant Tool - Table 1-2
— Node Setup application - Table 2-6
• Perform the “Adding passive components” procedure in WaveLogic
Photonics Coherent Select, 323-1851-980 for the applicable components:
— 2150 chassis
— 2xOSC
— Amplifiers (MLA2, MLA2 w/ VOA, MLA3, LIM C-Band)
— OBBs (OBB 2x2x2 C-Band or OBB 2x4x1 C-Band)
— Mux/Demux (OBMD 1x8 C-Band, CMD44, BMD2)
• Perform the “Creating an OTS instance for TOADM and AMP types”
procedure in WaveLogic Photonics Coherent Select, 323-1851-980 as
applicable to your configuration.
• Perform the “Editing the OTS slot sequence” in WaveLogic Photonics
Coherent Select, 323-1851-980 as applicable to your configuration.
• Perform the “Editing the TID slot sequence” in WaveLogic Photonics
Coherent Select, 323-1851-980 as applicable to your configuration.
• For fiber types other than NDSF, perform the “Provisioning line
adjacencies for non-NDSF fiber types” procedure to provision the line
adjacencies for each passive OTS or passive configuration site.
For NDSF fiber spans, adjacencies are automatically provisioned.
• Provision line adjacencies.
For more information, refer to WaveLogic Photonics Coherent Select, 323-

1851-980.
For OTS instances provisioned using the Photonic Configuration

Management application, the Slot Configuration Mode parameter is
automatically set to a value of “Derived” once the basic OTS parameters are
provisioned.
Various configurations using Optical Protection Switch (OPS) protection

switching are supported, including path and span protection. For information
on provisioning these configurations, refer to Configuration - Protection
Switching, 323-1851-315.

OPS and the Adjacency Mismatch alarm

The Adjacency (ADJ) Mismatch alarm may be raised on the ADJ-TX facility
when the ADJ-TX Tuning Mode is provisioned to a value not supported by the
transponder circuit pack.
The Provisioned Tuning Mode on the ADJ-TX is set according to associated

CRS' parent MCTTP's Capacity Change Mode (CCMODE). If Capacity
Change Mode is Mode 1, Provisioned Tuning Mode will be set to Accelerated
Tuning. If Capacity Change Mode is Mode 2 or Mode 3, the Provisioned
Tuning Mode will be set to Fast Tuning.
If CRS-NMCs are created on the CMD TX ADJs associated with the same
OPS group, the associated MCTTPs must have same Capacity Change Mode
to correctly set Tuning Mode on transponder and get Discovered Tuning Mode
back on CMDs. Otherwise, “Adjacency Mismatch” alarm will be raised against
one of CMD TX ADJ and OPS Switch ports.
Refer to Part 1 of Configuration - Provisioning and Operating, 323-1851-310,

to determine which circuit packs and facilities support the Tuning Mode
options.
Refer to Part 1 of Fault Management - Alarm Clearing, 323-1851-543, for the

Adjacency Mismatch alarm-clearing procedures.
Procedures
The following table lists the procedures in this chapter. Perform the
procedures as applicable.
Procedures in this chapter do not cover the provisioning of the passive OTS
network. For the provisioning of the passive OTS network, see “Passive OTS
network procedures” on page 6-1.
Table 3-1
Procedure
Procedure 3-1, “Provisioning photonic parameters”
Procedure 3-2, “Provisioning adjacencies”
Procedure 3-3, “Changing amplifier provisioning targets and differential

provisioning settings on an existing network”
Procedure 3-4, “Updating SPLI entries”
Procedure 3-5, “Recalibrating the SRA circuit packs”

Procedure 3-1
Provisioning photonic parameters
Use this procedure to provision:
• photonic parameters for line facing amplifiers, XLA amplifiers, RLA
amplifiers, DIA amplifier, cascaded amplifiers, DSCMs and pads at a
network element
• the fiber type for SRA circuit packs
• RAMAN parameters (SRA circuit packs)
Note: If the Raman Gain is set to 0 dB, the Raman pumps are disabled
and the SRA provides the equivalent functionality as an ESAM.
• the excess loss parameter on the OSC (2xOSC or SPAP-2 [with OSC
SFP] circuit packs, SRA/ESAM/SAM circuit packs)
• the minimum mux power output (MMPO) in the mux direction for the
following configurations:
— SMD in a CDA configuration with line facing RLA.
— COADM OTS connected directly to the amplified ports of the
backbone WSS (no COADM amplifier).
The MMPO cannot be provisioned from Site Manager and must be
provisioned using TL1. See “Connecting intra-site fibers and testing a
Colorless Direct Attach configuration (COADM OTS connected to 1x9 or
1x2 WSS or RLA)” on page 4-191 for more information on this
configuration.
In this release, the MMPO must be set to:
— -12.0 dBm with a reference bandwidth of 12.5GHz for the COADM
OTS in a SMD in a CDA configuration with line facing RLA
configuration.
— -12.0 dBm with a reference bandwidth of 12.5GHz for the COADM
OTS in a COADM OTS connected directly to the amplified ports of the
backbone WSS (no COADM amplifier) configuration.
For passive OTS network provisioning, see “Passive OTS network

procedures” on page 6-1.


The target peak power and the target gain tilt must be provisioned for each line
facing and cascaded amplifier in the system. The target peak power and the
target gain tilt values, and the XLA/RLA gain mode and top offset are
provisioned as per the OnePlanner amplifier report. For Drop LIM, nothing
needs to be provisioned. For DIA amplifier, the target gain must be
provisioned as per the OnePlanner amplifier report.
DSCMs can be auto-provisioned or manually provisioned. Pads are manually

provisioned as DSCMs, except for channel pads that connect to a CMD Tx or
Rx port.
DSCM/Pad placed at the input or output port of a line facing amplifier must be
associated with an OTS, the position of DSCM/Pad is specified in the
equipment slot sequence.
CAUTION
Electrostatic discharge (ESD) can damage electrostatic-
sensitive devices. Always connect yourself to ground before
you handle an electrostatic-sensitive device.
DANGER
Risk of injury
CAUTION
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light can
severely damage your eyes.
For any patch panel losses or remote distance losses between the WSS
switch port and a filter Common/NTWK/EXPR port, refer to 6500
Packet-Optical Platform Photonic Layer Guide, NTRN15DA.
For differential provisioning information, refer to the “Differential Provisioning”

section in Part 2 of Configuration - Provisioning and Operating, 323-1851-310.


Prerequisites
• Ensure that the commissioning procedures (using Node Setup or
Advanced SLAT) have been completed.
• Ensure that photonic circuit packs (such as SCMD4, 2xOSC, SPAP-2 w/
2xOSC, SLA, MLA, MLA2, MLA2 w/VOA, MLA3, LIM, XLA, SRA, ESAM,
SAM, WSS, RLA, 2-port OPM), pluggables, and/or modules (such as
CMD44, CMD64, BMD2, or DSCM) have been provisioned. Refer to the
“Retrieving equipment and facility details” procedure in Part 1 of
• Use an account with a UPC level of 3 or higher.
Step Action
1 Log into the network element using Site Manager and launch the Equipment
& Facility Provisioning application from the Configuration menu.
2 Select your type of configuration.
If Then
you are provisioning a Coherent make sure that CS Control is enabled.
Select (CS) configuration See the “Enabling Coherent Select
provisioning mode” procedure in
WaveLogic Photonics Coherent Select,
323-1851-980. Then, go to step 3.
otherwise go to step 3
Provisioning line facing amplifier, XLA, or RLA

3 Verify that all amplifier facilities for the MLA, MLA2, MLA2 w/VOA, MLA3,
SLA, XLA, or RLA circuit packs have been created.
4 In the Equipment table, select the LIM equipment for a line facing amplifier,
the XLA equipment, or the RLA.
Note: AMP facility is not available for the LIM circuit pack.
5 Select AMP in the Facility Type drop down list.
XLA, MLA, MLA2, MLA2 w/VOA, MLA3, and RLA amplifiers have two
amplifier facilities (pre- and post-amplifiers), and SLAs have one amplifier
facility (pre-amplifier).
The AID of a post-amplifier is AMP-<shelf>-<slot>-6 (AMP-<shelf>-<slot>-5
for an RLA).
The AID of a pre-amplifier is AMP-<shelf>-<slot>-8.
6 Click Edit in the Facility area.


Step Action
7 In the Edit facility dialog box, edit AMP facility parameters. (Set the secondary
state, target gain tilt, target peak power, and reference bandwidth as indicated
in the EDP/IDP.)
Note: By default, the reference bandwidth parameter is ‘50GHZITU’. For Flex
Grid configurations, the reference bandwidth parameter must be set to
‘12.5GHZ’
.
If you are provisioning Then go to

an AMP facility on an XLA or an RLA step 8 to continue the facility
Note: For RLA, only applies to pre-amplifier provisioning
(AMP-<shelf>-<slot>-8).
otherwise step 12
8 For AMP facilities on an XLA or RLA, set the XLA/RLA top offset as per the
OnePlanner report, then click Apply in the Edit facility dialog box.
9 Set the AMP facility of the XLA/RLA out of service (OOS) and click Apply in
the Edit facility dialog box. Click Yes in the warning confirmation message.
10 Set the XLA/RLA gain mode as per the OnePlanner report.
11 Set the AMP facility of the XLA/RLA back to its initial service state.
12 Click OK in the Edit facility dialog box.
13 If the line facing amplifier is an MLA2 w/VOA, select VOA in the Facility Type
drop down list.
MLA2 w/VOA has one VOA facility per direction (ports 5 and 7).
15 In the Edit facility dialog box, edit VOA facility parameters (set the VOA Reset
Required and Target Pad as indicated in the EDP/IDP).
16 Click OK in the Edit facility dialog box. Click Yes in the warning confirmation
message.
17 Repeat step 4 to step 16 for each line facing amplifier, XLA, or RLA.
Provisioning RAMAN parameters
18 Verify that the RAMAN facility has been created.
19 In the Equipment table, select the SRA equipment.
20 Select RAMAN in the Facility Type drop down list.
22 In the Edit facility dialog box, edit RAMAN facility parameters as indicated in
the EDP/IDP.
23 When you are finished, click OK in the Edit facility dialog box. Click Yes in the
warning confirmation message.


Step Action
24 For parameters that cannot be edited in the Site Manager interface, log into
the TL-1 interface and use the ED-RAMAN command to edit the required
values.
Note: Once provisioned, the SRA will run an OTDR trace automatically.
(Note that the Optical Time Domain Reflectometer requires at least 20 km of
optical fiber to verify the fiber for reflection or loss. An OTDR trace run on
short fiber may fail due to loss or reflection.) If the software detects issues with
the fiber (high reflection or high loss), alarms will be raised to indicate the
condition:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”.
This is expected behavior when the SRA line fibers are not connected. If the
line fibers are connected, refer to the procedures on OTDR alarms in Fault
Management - Alarm Clearing, Part 2 of 2, 323-1851-543. For detailed
information on Optical Time Domain Reflectometer (OTDR), refer to:
- the 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA
- the chapter on OTDR trace in Configuration - Provisioning and Operating,
Part 2 of 2, 323-1851-310
Provisioning the fiber type on SRA circuit packs (OTDRCFG facility)
25 This step is not required, unless indicated in the EDP/IDP. To provision the
fiber type on the Telemetry facility of SRA circuit packs as indicated in the
EDP/IDP:
a. In the Equipment table, select the SRA equipment.
b. Select the SRA OTDRCFG facility.
c. Click Edit in the Facility area.
d. Set the Fiber Type as indicated in the EDP/IDP.
e. Click OK in the Edit facility dialog box. Click Yes in the warning
confirmation message.
Provisioning cascaded amplifier
26 In the Equipment table, select the LIM equipment for a cascaded SLA circuit
pack.
27 Select AMP from the Facility Type drop down list.
29 In the Edit facility dialog box, edit AMP facility parameters (set the target gain
tilt, target peak power as indicated in the EDP/IDP).
message.
31 Select OPTMON in the Facility Type drop down list.


Step Action
32 Select the OPTMON facility corresponding to the Line B In port (OPTMON-

<shelf>-<slot>-6) and click Edit in the Facility area.
33 In the Edit facility dialog box, set the Primary state to OOS and click OK. Click
Yes in the warning confirmation message. Verify that the OPTMON LOS
alarm corresponding to the cascaded SLA circuit pack clears.
34 Repeat step 26 to step 33 for each cascaded amplifier.
Provisioning DIA amplifier
35 In the Equipment table, select the LIM equipment for a DIA amplifier circuit
pack.
36 Select AMP from the Facility Type drop down list.
38 In the Edit facility dialog box, edit AMP facility parameters (set the target gain
as per the OnePlanner report).
message.
40 Repeat step 35 to step 39 for each DIA amplifier.
41 If a pad is required at the following location, provision required pad as Excess
Loss against the corresponding ADJ-FIBER facility:
• CMD44 Common Out port (port 90)
• BMD2 Common Out port (port 2)
For pads at DIA OTS WSS and backbone WSS Switch port 8/9 Output port
(port 18/20), no provisioning is required.
Provisioning DSCM/Pad/excess loss on OSC
Note: If the DSCM is connected by CAT5 cable to the External Inventory
Access Panel port of the shelf, it will auto-provision. Otherwise, you need to
provision the DSCM manually. The Pad must be provisioned as DSCM
manually if it is not connected to a CMD Tx or Rx. Channel pads that connect
to a CMD Tx and/or Rx must be provisioned as Pad Loss in the ADJ-FIBER
facility of the CMD Tx and/or Rx port.
42 If Then go to
you are provisioning a channel pad step 47
you are provisioning a DSCM or non-channel pad step 43
you are provisioning the excess loss on OSC step 49
(insertion of pad)
you have completed DSCM, pad, or excess loss you have completed
provisioning this procedure


Step Action
Provisioning DSCMs and non-channel pads

43 Auto-provision a DSCM by connecting a CAT5 cable between the DSCM and
the access panel external inventory port. Or manually provision a DSCM or
non-channel pad by performing step 44.
44 Provision a DSCM or non-channel pad manually.
a. In the Equipment & Facility Provisioning application, click Add in the
Equipment area to open the Add Equipment dialog box.
b. Select Display Only Empty Slots.
c. Select the slot number (external or virtual slot).
d. Select the appropriate PEC of the DSCM/pad from the Card PEC drop-
down list.
e. Click OK.
45 Repeat step 43 or step 44 for each DSCM and non-channel pad.
46 In the Photonic Configuration Management application, edit the appropriate
slot sequence to position the DSCMs/pads appropriately. Refer to the “Editing
slot sequences” procedure in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
Go to step 42.
Provisioning pads for channel Tx/Rx
47 Provision the required channel pad.
a. In the Equipment & Facility Provisioning application, select the channel
port of the channel mux/demux that the pad is connected to.
b. Select ADJ-FIBER in the Facility Type drop-down menu.
c. Select the ADJ-FIBER facility corresponds to the port where the pad is
connected in the Facility list and click Edit.
d. Enter the pad value in the Pad Loss field.
e. Click OK. Click Yes in the warning confirmation message.
48 Repeat step 47 for each channel pad.
Go to step 42.


Step Action
Provisioning the excess loss parameter on OSC (insertion of pad)

49 If 2xOSC or SPAP-2 (with OSC SFP) equipment is present:
a. Select the 2XOSC or SPAP-2 circuit pack in the Equipment area.
b. Select the P155M-SH-SL-Port (1 or 2) facility.
c. Select ADJ-FIBER in the Facility Type drop-down menu.
d. Select the ADJ-SH-SL-Port (1 or 2) facility (Adjacency Type LIM).
e. Click Edit.
f. Enter the parameter value in the Excess Loss field.
g. Click OK. Click Yes in the warning confirmation message.
50 If SRA/ESAM/SAM equipment is present:

a. Select the SRA/ESAM/SAM-SH-SL circuit pack in the Equipment area.
b. Select the associated P155M-SH-SL-2 equipment.
c. Select ADJ-FIBER in the Facility Type drop-down menu.
d. Select ADJ-SH-SL-2 (Adjacency Type LIM).
e. Click Edit.
f. Enter the parameter value in the Excess Loss field.
g. Click OK. Click Yes in the warning confirmation message.
Provisioning the minimum mux power output (MMPO)
51 Login to the network element TL-1 interface as an admin user. At the TL-1
prompt ''<'' type:
ACT-USER::ADMIN:1::<password>;
52 Enter the MMPO and RefBW parameters, at the TL1 prompt “<“ type:
ED-OTS:<tid>:<aid>:<ctag>:::,MINMUXPOUT=-
xx.yy,REFBW=12.5GHZ;
where:
• <aid> is the OTS identifier in the format ‘OTS-shelf-instance’.
• xx.yy is:
-12.00 dBm for CDA configuration with line facing RLA
configuration
-12.00 dBm for the COADM OTS in a COADM OTS connected
directly to the amplified ports of the backbone WSS (no
COADM amplifier) configuration
53 Repeat step 52 for all COADM OTSs in the configuration.
—end—

Procedure 3-2
Provisioning adjacencies
For OTS instances created using the Photonic Configuration Management
application, once the slot sequences are defined, all intra-OTS adjacencies
are system derived. Use this procedure to provision the inter-OTS WSS-WSS
(or RLA-RLA) adjacencies and line adjacencies. For configurations using
FIMs (except 1x20 CD with FIM4 configurations), all adjacencies are
automatically system derived.
For 1x20 CD with FIM4 configurations, the derived ROADM OTSs define the
SAM/ESAM/SRA, XLA and WSSOPM, or MLA3 and WSSOPM adjacencies.
However, manual provisioning of the expected far-end address (EFEA)
adjacency is required for the following locations:
• pass-through
— WSS to WSS FIM (FIM associated with the WSS)
— WSS FIM (FIM associated with the WSS) to WSS FIM (FIM associated
with the WSS)
— WSS FIM (FIM associated with the WSS) to WSS
• add/drop
— WSS to WSS FIM (FIM associated with the WSS)
— WSS FIM (FIM associated with the WSS) to SMD FIM (FIM associated
with the SMD)
— SMD FIM (FIM associated with the SMD) to SMD
— SMD to CCMD12
Note 1: Only one direction provisioning is required. The other direction is
derived automatically and is not allowed to be provisioned manually.
Note 2: For pass-throughs, EFEAs on the WSS to WSS sub-ports are
automatically derived when WSS to WSS FIM, WSS FIM to WSS FIM, and
WSS FIM to WSS adjacencies are provisioned correctly.
Note 3: For add/drops, EFEAs between the WSS and SMD sub-ports are
automatically derived when WSS to WSS FIM, WSS FIM to SMD FIM, and
SMD FIM to SMD adjacencies are provisioned correctly.


Figure 3-1 on page 3-16 shows an example of a 1x20 CD with FIM4

configuration with two degrees and an add/drop bank on each degree. For this
example, the following EFEAs need to be provisioned for degree #1 and for
connection to degree #2 (add/drop for degree #2 not detailed):
• Degree #1 add/drop
— FIM4 to WSS MPO port ADJ-1-90-1: EFEA=1-5-5, ADJTYPE=WSS
The WSS MPO port to FIM4 adjacency is automatically derived (ADJ-
1-5-5: EFEA=1-90-1, ADJTYPE=FIM.
— FIM4 to FIM4 LC port ADJ-1-90-48: EFEA=2-91-49, ADJTYPE=FIM
FIM4 to FIM4 LC port adjacency is automatically derived (ADJ-2-91-
48: EFEA=1-90-49, ADJTYPE=FIM
— FIM4 to SMD14x8 MPO port ADJ-2-91-4: EFEA=2-1-4,
ADJTYPE=SMD
SMD to FIM4 adjacency is automatically derived (ADJ-2-1-4: EFEA=2-
91-4 ADJTYPE =FIM)
— SMD14x8 to CCMD12: ADJ-2-1-20: EFEA=3-1-25, ADJTYPE=CMD
CCMD12 to SMD14x8 adjacency is automatically derived (ADJ-3-1-
26: EFEA=2-1-19, ADJTYPE =SMD)
When the WSS to FIM, FIM to FIM, and FIM-SMD adjacencies are
provisioned, the WSS to SMD sub-port EFEAs are automatically derived.
• Degree #1 <-> Degree #2 passthrough
— FIM4 to WSS MPO adjacency ADJ-1-90-4: EFEA=1-5-8,
ADJTYPE=WSS
WSS to FIM4 adjacency is automatically derived (ADJ-1-5-8:
EFEA=1-90-4, ADJTYPE=FIM)
— WSS to FIM4 MPO adjacency ADJ-5-5-5: EFEA=5-90-1,
ADJTYPE=FIM
FIM4 to WSS adjacency is automatically derived (ADJ-5-90-1,
EFEA=5-5-5, ADJTYPE=WSS)
— FIM4 to FIM4 LC Adjacency ADJ-5-90-10: EFEA=1-90-11,
ADJTYPE=FIM
FIM4 to FIM4 adjacency is automatically derived (ADJ-1-90-10:
EFEA=5-90-11 ADJTYPE=FIM)
When the WSS to FIM, FIM to FIM, and FIM-WSS adjacencies are
provisioned, the WSS to WSS sub-port EFEAs are automatically derived.


Figure 3-1
1x20 CD with FIM4 - example EFEA adjacencies
1-1 SRA SRA 5-1
XLA XLA
1-2 5-2
1-5 5-5
WSS 1x20 WSS 1x20
8 7 6 5 5 6 7 8
4 3 2 1 1 2 3 4
1-90 FIM4 FIM4 5-90
48 49 10 11 10 11 48 49
48 49 10 11 10 11 48 49
2-91 FIM4 FIM4 6-91
4 3 2 1 1 2 3 4
4 3 2 1 1 2 3 4
2-1 SMD14x8 SMD14x8 6-1
19 20 5 6 5 6 19 20
25 26 25 26
3-1 CCMD12 CCMD12 6-10
Derived during ROADM OTS creation

User manually provisioned
System derived (from user manual provisioning)


See Photonic Layer Guide, NTRN15DA, for details of the intra and inter
adjacencies.
For TOADM and DIA, inter-OTS adjacencies are provisioned after TOADM
and DIA are tested in Procedure 4-9, “Testing TOADM channel access
continuity” and Procedure 4-10, “Testing a DIA configuration”.
Note: When a BMD2 is provisioned in a ROADM or DIA OTS, CMD1

defaults to BMD2 pair port #1 (port 3,4), and CMD2 defaults to BMD2 pair
port #2 (port 5,6). If there is only one 50 GHz CMD44 (red or blue), it must
be provisioned to BMD2 pair port #1 (port 3, 4).
For a Colorless OADM configuration made up of a DIA OTS and a COADM

OTS, inter-OTS adjacencies are required between the COADM OTS and the
DIA OTS. Use this procedure to provision the COADM to DIA inter-OTS
adjacencies.
For Colorless OADM Direct Attach configurations (see “Colorless Direct

Attach configuration (COADM OTS with 1x9 WSS) example” on page 4-196),
inter-OTS adjacencies are required between the COADM OTS and the
ROADM OTS. Use this procedure to provision the COADM to ROADM inter-
OTS adjacencies.
For Colorless Direct Attach configurations using OPS, Tx and Rx adjacencies

are required at the OPS. Use this procedure to provision the Tx and Rx
adjacencies at the OPS for the following configuration types:
• Colorless Direct Attach configuration—COADM OTS connected to 1x9
WSS and using OPS (see “Colorless Direct Attach configuration (COADM
OTS connected to 1x9 WSS and using OPS) example” on page 4-198)
• Colorless Direct Attach configuration—CCMD12 connected to 1x20 WSS
and using OPS (see “Configuration example—CCMD12 connected to
1x20 WSS and using OPS” on page 4-226)


For Colorless Direct Attach configurations (CCMD12 connected to 1x20

WSS) with 11 to 15 degrees, manual provisioning of the expected far-end
address (EFEA) adjacency is required for the following locations as
appropriate:
— WSS to FIM4
— WSS to FIM5
— WSS to FIM6
Note 1: Only one direction provisioning is required. The other direction is
derived automatically and is not allowed to be provisioned manually.
Note 2: WSS to FIM sub-ports are automatically derived when WSS to
FIM adjacencies are provisioned correctly.
Note 3: None of the MPO ports are reserved – any port on the 1x20 WSS
may be used with any combination of FIM4, FIM5 or FIM6 for add/drop or
express traffic.
Note 4: If performing a brownfield upgrade of the CDA configuration, TL1
must be used to remove TID-SLOT-SEQ on one port and then manual
adjacency must be used to provision the FIM.
For Flex grid systems, refer to Configuration - Control Plane, 323-1851-330,

for all Flex grid channel procedures.
The 2-port OPM is not part of an OTS. For adjacencies to the 2-port OPM,
see:
• “CMD44-OPM adjacencies” on page 3-30 for the CMD-OPM adjacencies,
• “LIM-OPM adjacencies” on page 3-31 and “LIM-OPM adjacencies in XLA
case” on page 3-31 for the LIM-OPM adjacencies.
A single OPM can be fibered to two different LIM (or XLA, if present) circuit
packs that are in different OTSs. The OPM and LIM (or XLA, if present) circuit
packs must reside in the same shelf.
When one 2-port OPM circuit pack is equipped in the shelf where a line
amplifier OTS is provisioned, the following LIM to OPM adjacencies are auto-
provisioned:
• port 1 (Line B MON) of the LIM in lower numbered OTS points to OPM port
1
• port 1 (Line B MON) of the LIM in higher numbered OTS points to OPM
port 2


When two 2-port OPM circuit packs are equipped in the shelf where a line
amplifier OTS is provisioned, the following LIM to OPM adjacencies are auto-
provisioned:
• port 1 (Line B MON) of the LIM in lower numbered OTS points to port 1 of
the 2-port OPM in higher numbered slot
• port 1 (Line B MON) of the LIM in higher numbered OTS points to port 2
of the 2-port OPM in higher numbered slot
You can override the preceding auto-provisioned LIM to OPM adjacencies if

required.
When a 2-port OPM circuit pack is equipped in the shelf where a line amplifier
OTS is provisioned, the following XLA to OPM adjacencies (LIM type) are
auto-provisioned:
• port 1 (Line B MON) of the XLA points to OPM port 1
• port 2 (Line A MON) of the XLA points to OPM port 2
When two 2-port OPM circuit packs are equipped in the shelf where a line
amplifier OTS is provisioned, the following XLA to OPM adjacencies (LIM
type) are auto-provisioned:
• port 1 (Line B MON) of the XLA points to OPM port 1 in higher numbered
slot
• port 2 (Line A MON) of the XLA points to OPM port 2 in higher numbered
slot
You can override the preceding auto-provisioned XLA to OPM adjacencies if

required.
When two or more 2-port OPMs are provisioned in the shelf, the adjacencies
will be derived only for the 2-port OPM that was provisioned first.


Prerequisites
• Ensure that the commissioning procedures (using Node Setup or
Advanced SLAT) have been completed.
• Log into the network element using Site Manager and launch the
Equipment & Facility Provisioning application from the Configuration
menu.
Step Action
1 Select your first step.

If Then perform
the configuration type is Amplifier step 2 to step 17
configuration type is Channel Access ROADM step 2 to step 35
configuration type is DGFF step 9 to step 17,
then step 24 to
step 34
configuration type is Channel Access (COADM to DIA step 36 to step 45
inter-OTS)
configuration type is Colorless OADM Direct Attach step 46
the Colorless Direct Attach configuration is using OPS step 56
you want to use standalone OPM monitoring step 63
configuration type is 1x20 CD with FIM4 step 69
configuration type is 1x20 CD ROADM with FIM4/ step 71
FIM5/FIM6


Step Action
Provision adjacencies between the 2-port OPM and the LIM or XLA if applicable
Note 1: For ROADM, when the LIM (or XLA if present) and WSSOPM are
provisioned in the OTS, the LIM monitor port adjacencies point to the OPM
monitor ports of the WSSOPM by default. If required, you can override the
default adjacencies to point to the 2-port OPM by performing step 2 to step 6.
Then the far end address of the WSSOPM monitor port adjacencies will be
cleared.
Note 2: Perform step 2 to step 6 at a line amplifier site if you want to override
the auto-provisioned LIM (or XLA if present) to OPM adjacencies.
Note 3: The RLA has an internal OCM and does not need to be connected
to an OPM. RLA ports 1 and 2 can be used to connect an external customer
OPM if required.
2 In the Equipment table, select the LIM equipment, XLA, or RLA equipment
that is connected to the 2-port OPM.
3 Select ADJ in the Facility Type drop down list.
4 Select the LIM monitor port (port 1 or port 2) or XLA monitor port (port 1 or 2).
6 In the Edit facility dialog box:
• select OPM in the Adjacency type drop down list
• select the Expected far end address format (TID-SH-SL-PRT) and the
Expected far end address as indicated in the EDP/IDP. This address
should point to the 2-port OPM monitor port (port 1 or port 2).
• click OK
The corresponding adjacency at the OPM port will be auto-derived.
7 Repeat step 2 to step 6 for the other LIM monitor port or XLA monitor port that
is connected to the 2-port OPM.
8 Repeat step 2 to step 7 for all LIM equipment or XLA equipment monitor port.
Provision Line adjacencies
9 In the Equipment table, select the LIM, RLA, SRA, ESAM, SAM, or DSCM
equipment that connects to the line fiber in the transmit direction.
10 Select ADJ-LINE (for LIM, RLA, SRA, ESAM, SAM) or ADJ (for DSCM) from
the Facility Type drop down list.
11 Select the Line adjacency that corresponds to ADJ-<shelf>-<slot>-5 (Line B
Out) or ADJ-<shelf>-<slot>-1 (for DSCM Out) as indicated in the EDP/IDP.
13 In the Edit facility dialog box, modify the Fiber Type as indicated in the EDP/
IDP.


Step Action
14 Select the Expected far end address format (TID-SH-SL-PRT) and enter the
Expected far end address as indicated in the EDP/IDP.
The Expected far end address identifies the receive port of the line facing
module that is connected to the other end of the line, it should point to port 8
of LIM, RLA, SRA, ESAM, SAM, or port 2 of DSCM on the remote NE.
15 Enter the minimum span loss, span loss margin and target span loss as
16 Click OK in the Edit facility dialog box.
17 Repeat step 9 to step 16 for all line adjacencies. If this is a DGFF site, go to
step 24.
Provision adjacencies between the 2-port OPM and the enhanced CMD44 or CMD64 if applicable
18 In the Equipment table, select the enhanced CMD44 or CMD64 equipment
that is connected to the 2-port OPM.
20 Select the CMD44 monitor port (port 92) or CMD64 monitor port (port 129 or
port 130).
should point to the 2-port OPM monitor port (port 1 or port 2).
• click OK
The corresponding adjacency at the OPM port will be auto-derived.
23 Repeat step 18 to step 22 if there is another CMD44 or CMD64 connected to
the 2-port OPM (or if you want to connect the other monitor port of a CMD64).


Step Action
Provision WSS-WSS or RLA-RLA adjacencies

If Then
your configuration uses FIMs (not all WSS-WSS adjacencies are derived
applicable to RLAs) once the FIM is provisioned and the
respective WSS circuit packs are
added to the Add and Drop TID
Sequences. The WSS-WSS adjacency
provisioning is complete.
25 In the Equipment table, select the WSSOPM or RLA equipment for one end
of the WSS-WSS link.
27 Select the adjacency corresponding to the WSS or RLA output port.
• select WSS or RLA in the Adjacency type drop down list
should point to the connecting WSS’s or RLA’s input port AID.
• click OK
30 In the Equipment table, select the WSSOPM or RLA equipment for the other
end of the WSS-WSS or RLA-RLA link.
32 Select the adjacency corresponding to the WSS or RLA output port.
• select WSS or RLA in the Adjacency type drop down list
should point to the connecting WSS or RLA circuit pack’s input port AID.
• click OK
If this is a DGFF site, you have completed this procedure.


Step Action
35 Repeat step 24 to step 34 for all WSS-WSS or RLA-RLA adjacency types

listed in the EDP/IDP.
Provisioning SMD-LIM adjacencies between COADM SMD and DIA LIM
36 In the Equipment table, select the SMD equipment for the SMD-LIM link.
38 Select the adjacency corresponding to the SMD Common Out (port 10).
• select LIM in the Adjacency type drop down list
• select the Expected far end address format (TID-SH-SL-PRT) and enter
the Expected far end address as indicated in the EDP/IDP. This address
should point to the connecting MLA circuit pack Line A In (port 8).
• click OK
41 In the Equipment table, select the LIM equipment for the LIM-SMD link.
43 Select the adjacency corresponding to the MLA circuit pack Line B Out (port
5).
• select SMD in the Adjacency type drop down list
should point to the connecting SMD Common In (port 9).
• click OK
To provision OPM adjacencies when using standalone OPM monitoring, go

to step 63.
Provisioning WSS-LIM Adjacencies between Colorless OADM cascaded LIM and WSS for
Colorless OADM Direct Attach (see a configuration example in “Colorless Direct Attach
configuration (COADM OTS with 1x9 WSS) example” on page 4-196)
46 In the Equipment table, select the cascaded MLA3 equipment for the LIM-
WSS link.
48 Select the adjacency corresponding to the Line B Out (port 5).
49 Click Edit in the Facility area


Step Action

• select WSS in the Adjacency type drop down list
should point to the connecting WSS non-amplified Switch In (for instance,
port 13).
• click OK
51 In the Equipment table, select the WSS equipment for the LIM-WSS link.
53 Select the adjacency corresponding to the outgoing non-amplified Switch Out
port on the WSS connecting to the cascaded LIM, as indicated in the EDP/
IDP (for instance, port 14).
• select LIM in the Adjacency type drop down list
should point to the connecting MLA3 Line A In (port 8).
• click OK
If the Colorless Direct Attach configuration uses an OPS, go to step 56.
To provision OPM adjacencies when using standalone OPM monitoring, go
to step 63.
Provisioning Tx and Rx adjacencies at the OPS
56 In the Equipment table, select the OPS Equipment and then select ADJ in the
Facility Type drop down list.
Identify the OPS ports associated with the protection group.
57 For the OPS Common In port, provision the ADJ-TYPE to Tx.
58 For the OPS Common Out port, provision the ADJ-TYPE to Rx.
59 For the OPS SW1 Out port and the SW2 Out port, provision the ADJ-TYPE
to TXRX.
60 For the OPS Common In port, provision the ADJ-TX Expected Far End
Address to point to the transponder line port.
61 For the OTS1/path1 CMD Channel In port, provision the ADJ-TX Expected
Far End Address to point to OPS SW1 Out port.


Step Action
62 For the OTS2/path2 CMD Channel In port, provision the ADJ-TX Expected
Far End Address to point to OPS SW2 Out port.
Note: For OPS in colored configurations, if the wavelengths corresponding
to the Expected Far End Addresses of SW1 and SW2 differ, this fault is
reported via an “Adjacency Mismatch” alarm.
Provisioning OPM adjacencies when using standalone OPM monitoring
63 In the Equipment table, select the equipment that is connected to the 2-port
OPM.
65 Select the equipment monitor port (port 1 or port 2).
should point to the connecting OPM port.
• click OK
Provisioning the Excess Loss parameter
68 To scale the measured power from the tap point to the actual line power,
provision the Excess Loss parameter:
• select ADJ-FIBER in the Facility Type drop down list
• select the facility that is the tap point
• click Edit in the Facility area
• in the Edit facility dialog box, provision the Excess Loss parameter as
indicated in the EDP/IDP
• click OK


Step Action
Provisioning adjacencies for 1x20 CD ROADM with FIM4 configuration

Note: The FIM to FIM EFEA adjacencies should not be provisioned until the
FIM to FIM connections are made during testing (see Procedure 4-29, “Site
testing for 1x20 Colorless Directionless (CD) ROADM with FIM4”).
69 In the Equipment table, provision the far end address for the following physical
layer adjacencies:
• MPO ports of the FIMs associated with WSS or the WSS (for both pass-
through and add/drop)
• LC ports of the FIM associated with WSS or LC ports of the FIM
associated with the SMD14x8 (for add-drops)
• LC ports of the FIM associated with WSS or LC ports of the FIM
associated with another WSS (for pass-through)
• MPO ports of the FIM associated with SMD14x8 or the SMD14x8 (for
add-drops)
• LC ports of the SMD14x8 or LC level ports of the CCMD12 (for add-
drops)
For information on the adjacencies required, see the introduction to this
procedure and Figure 3-1 on page 3-16.
Note: You only need to, and can only, provision the far-end address
adjacency for one direction, the other direction is automatically derived and
cannot be manually provisioned. For example, between 1x20 WSS to the
associated FIM4, the far-end address adjacency can be provisioned either on
the physical layer adjacency of the WSS (MPO level port) or that of the FIM4,
but not both.
To provision the expected far-end address adjacency:
a. Select the required equipment.
b. Select ADJ in the Facility Type drop down list.
c. Select the adjacency corresponding to the required port.
d. Click Edit in the Facility area.
e. In the Edit facility dialog box:
— select the required equipment in the Adjacency type drop down list
— select the Expected far end address format (TID-SH-SL-PRT) and
enter the Expected far end address as indicated in the EDP/IDP.
f. Click OK
g. Repeat substep a to substep f for all the EFEA adjacencies that need to
be provisioned.


Step Action
Provisioning the Excess Loss parameter for additional FIM to FIM losses
Note: The following steps are required if there is additional fiber loss between
FIMs (for example, where this connection is across a building). The excess
loss cannot be greater than 3 dB (but must be validated by link engineering
for each deployment).
70 To allow for excess loss for FIM to FIM connections, provision the Excess
Loss parameter:
a. Select ADJ-FIBER in the Facility Type drop down list.
b. Select the facility for the excess loss. Depending where the excess losses
are located and the direction, excess losses may need to be provisioned:
— For pass-through, on WSSs (it could be either WSS or both)
— For add-drop, on SMDs and/or WSSs. If there is an excess loss in the
direction WSS -> SMD, it should be provisioned on the WSS. If there
is an excess loss in the direction SMD -> WSS, it should be
provisioned on the SMD.
c. Click Edit in the Facility area.
d. In the Edit facility dialog box, provision the Excess Loss parameter as
e. Click OK.
f. Repeat substep a to substep e for all excess losses.
Provisioning adjacencies for 1x20 CD ROADM with FIM4/FIM5/FIM6 configuration (11 to 15
degrees)
71 In the Equipment table, provision the far end address for the following physical
layer adjacencies:
• MPO ports of the FIM4s or the WSS
For information on the adjacencies required, see the introduction to this
procedure.
Note: You only need to, and can only, provision the far-end address
adjacency for one direction, the other direction is automatically derived and
cannot be manually provisioned. For example, between 1x20 WSS to the
associated FIM4, the far-end address adjacency can be provisioned either on
the physical layer adjacency of the WSS (MPO level port) or that of the FIM4,
but not both.


Step Action
To provision the expected far-end address adjacency:

a. Select the required equipment.
b. Select ADJ in the Facility Type drop down list.
c. Select the adjacency corresponding to the required port.
d. Click Edit in the Facility area.
e. In the Edit facility dialog box:
— select the required equipment in the Adjacency type drop down list
— select the Expected far end address format (TID-SH-SL-PRT) and
enter/select the Expected far end address as indicated in the EDP/
IDP.
— click OK
f. Repeat substep a to substep e for all the EFEA adjacencies that need to
be provisioned.
—end—

Figure 3-2
CMD44-OPM adjacencies
2-port OPM

Figure 3-3
LIM-OPM adjacencies
Figure 3-4
LIM-OPM adjacencies in XLA case

Procedure 3-3
Changing amplifier provisioning targets and
differential provisioning settings on an existing
network
Use this procedure to change amplifier peak power and gain tilt targets, as
well as differential provisioning settings, on an already deployed photonic
layer network. This procedure does not apply to the passive OTS network.
Changing the differential provisioning settings using this procedure only

applies to existing traffic carrying channels. If you are adding a new service,
for example, 100G, and there are no existing 100G channels on the system,
you can change the differential provisioning directly for that new service before
adding the channels, without having to perform this procedure.
Prerequisites
• Before you perform this procedure, contact Ciena to perform a link budget
analysis of the system to determine the amplifier peak power and gain tilt
targets, as well as differential provisioning settings, that must be applied.
• All active channels on the network must have an End-to-End Condition of
“Optimized”.
• The network must be alarm-free.
• Peak power and gain tilt targets must be available for all amplifiers in the
network.
• Differential provisioning targets must be available for all modulation types
for all domains.
Step Action
Preparing DOC network elements

1 When changing amplifier provisioning and differential provisioning bias in a
network with channels that cross DOC boundaries, all optical domains in
which the channels exist must be re-optimized as part of this procedure.
Identify all domains that will be affected by this procedure.


Changing amplifier provisioning targets and differential provisioning settings on an existing
network
Step Action
2 Disable the DOC gain clamp mode.

a. Open a DOS window and telnet to the network element identified as
Domain Optical Controllers (DOC) in step 1
C:\telnet <shelf IP> if connecting through the DCN
or log in directly to the shelf through the LAN-15 port on the SP
b. Login to the network element TL-1 interface as an admin user. At the TL-
1 prompt ''<'' type:
ACT-USER::ADMIN:1::<password>;
c. Disable the DOC gain clamp mode:
ED-DOC::DOC-<shelf>-<instance>:CTAG:::
DOCGAINCLAMP=DISABLE;
3 Repeat step 2 on both DOC network elements in each optical domain in the
network. Branched networks and networks with spurs contain more than one
optical domain.
4 Log into the network element identified as Domain Optical Controllers (DOC)
in step 1.
a. In Site Manager, select Configuration->Photonic Services->Domain
Optical Controller (DOC).
b. Click Start Monitoring.
c. Select the Settings tab.
d. Record the original Automation mode setting.
e. Click Edit. Change the Automation mode to Enhanced Auto Monitor Only.
Then click OK.
5 Repeat step 4 on both DOC network elements in each optical domain in the
network. Branched networks and networks with spurs contain more than one
optical domain.


network
Step Action
Updating the Target Gain Tilt

6 Update the Target Gain Tilt by no more than 1 dB for each amplifier in the
network.
a. In Site Manager, select Configuration->Equipment & Facility
Provisioning.
b. Select the first amplifier facility that requires a Target Gain Tilt change and
click Edit. Change the Target Gain Tilt to the new value. Click OK.
c. Perform step 9 to step 15 to re-optimize the network.
d. Repeat substep b and substep c for each amplifier facility at the site that
requires a Target Gain Tilt change.
e. Repeat substep a to substep d for each site in the network.
Updating Target Peak Power and Differential Provisioning Bias
7 Update the amplifier Target Peak Power by no more than 1 dB at each site in
the network.
a. In Site Manager, select Configuration->Equipment & Facility
Provisioning.
b. Select the first amplifier facility that requires a Target Peak Power change
and click Edit. Change the Target Peak Power by no more than 1 dB.
Click OK.
d. Repeat substep b and substep c for each amplifier facility at the site that
requires a target peak power change.
e. Repeat substep a to substep d for each site in the network.
8 Update the differential provisioning bias settings by no more than 1 dB at
each network element identified as a DOC site.
a. In Site Manager, select Configuration->Photonic Services-
>Differential Provisioning.
b. Select the first Modulation Class that requires a bias change and click
Edit. Change the bias by no more than 1 dB from the current setting in
the direction required (negative or positive). Click OK.
d. Repeat substep b and substep c for each modulation class that requires
a bias change.
e. Repeat substep a to substep d for each DOC site in the network.


network
Step Action
Re-optimizing the network

9 Log into the network elements identified as Domain Optical Controller (DOC)
in the network.
10 In Site Manager, select Configuration->Photonic Services->Domain
Optical Controller (DOC).
11 Click Re-optimize and wait for DOC to indicate that the optimization is
complete and the channels are optimized.
If the DOC status stays in the “Re-opt:Waiting” state for an extended period,
clear any “DOC Action: Fault Detected” alarms in downstream domains (see
Part 1 of Fault Management - Alarm Clearing, 323-1851-543). Resolving the
issue in the downstream domain and clearing the alarm will allow the
upstream domain to proceed with the channel re-optimization.
12 When the Re-Optimize is complete, click Reset TCA Baselines to adjust the
baselines for the amplifier change just completed.
If Then go to
the channels exit the domain step 14
otherwise step 16
14 Adjust the baselines (by using Reset TCA baselines) in the domains located
downstream from the domain just re-optimized.
15 Re-optimize the downstream domains for which you have adjusted the
baselines.
16 Repeat step 7 to step 15 to change the provisioning by no more than 1 dB
steps until the final targets have been achieved.
17 After you change the amplifier provisioning values in all domains and all
active channels on the network have an End-to-End Condition of “Optimized”,
log into the network elements identified as Domain Optical Controllers (DOC)
in step 1 and change the Automation mode back to its original setting
recorded in step 4.
18 Perform step 17 on both DOC NEs in each optical domain in the network.
Branched networks and networks with spurs contain more than one optical
domain.


network
Step Action
19 After you change the amplifier provisioning values in all domains and all
active channels on the network have an End-to-End Condition of “Optimized”,
enable the DOC gain clamp mode you disabled in step 2.
a. At the TL-1 command prompt, enter:
ED-DOC::DOC-<shelf>-<instance>:CTAG:::
DOCGAINCLAMP=ENABLE;
b. Log out of the TL-1 interface.
CANC-USER::ADMIN:1;
20 Perform step 19 on both DOC NEs in each optical domain in the network.
Branched networks and networks with spurs contain more than one optical
domain.
—end—

Procedure 3-4
Updating SPLI entries
Use this procedure to update Service and Photonic Layer Interoperability
(SPLI) entries on an already deployed photonic layer network.
Updating of SPLI entries is necessary when the TID of the corresponding

transponders has been changed. For example, when changing the name of
the transponder shelf, Waveserver, or Waveserver Ai.
Prerequisites
menu.
Step Action
1 On the CMD/OMD/OMX associated with the transponder where the TID is

being changed, select the ADJ-TX facility associated with the transponder
from the Facility Type drop-down list.
2 Click Edit and set the following parameters:
• Sync Provisioned: False
• Auto Discovered: Manual
• Expected Far End Address: empty
Note: You must expand the Optional Parameters to view all the parameters.
This causes the matches in the associated SPLI entry to go to ‘0’.
3 Repeat step 1 and step 2 for the CMD/OMD/OMX associated with
transponders where the TIDs are being changed.
4 Delete the SPLI entries associated with the transponders with the old TIDs.
See ‘Deleting unreliable SPLI entries’ procedure in Administration and
Security, 323-1851-301, for details.
Note: You must wait for the match to be ‘0’ before you can delete an SPLI
entry.
5 Add an SPLI entry to the SPLI database for each transponder with a changed
TID. See ‘Adding SPLI entries’ procedure in Administration and Security, 323-
1851-301, for details.
6 Provision the ADJ-TXs associated with the transponders with changed TIDs.
See ‘Editing facility parameters’ procedure in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310, for details.
—end—

Procedure 3-5
Recalibrating the SRA circuit packs
If the XLA gain mode is changed, the associated SRA must be re-calibrated
as the SRA calibration requires that the correct XLA Gain Mode is set prior to
being executed and the calibration results may change depending on the
provisioned XLA Gain Mode.
This procedure details the steps required to re-calibrate the SRA if the XLA
Gain Mode is changed.
Prerequisites
menu.
Step Action
1 Delete all channels going through the domain where the XLA Gain Mode is
being changed. For more information, refer to Chapter 7, “Wavelength
addition and deletion” and Configuration - Connections Management, 323-
1851-320.
Note: If the channels are provisioned as SNCs, the SNCs only need to be
changed to out-of-service (OOS) which will delete the underlying channels.
For more information, refer to Configuration - Control Plane, 323-1851-330.
2 Set the primary state of the DOC to OOS. For more information, refer to Part
2 of Configuration - Provisioning and Operating, 323-1851-310.
3 Change the XLA Gain Mode to the required mode. For more information, refer
to Part 1 of Configuration - Provisioning and Operating, 323-1851-310.
4 Using TL1, set the SRA calibrated mode to RECALIBRATIONREQUIRED:
ED_RAMAN:[tid}:RAMAN-shelf-slot-8
CALIBRATED=RECALIBRATIONREQUIRED
5 Set the primary state of the DOC to in-service (IS). For more information, refer
to Part 2 of Configuration - Provisioning and Operating, 323-1851-310.
6 Add back all the required channels going through the domain where the XLA
Gain Mode has been changed. For more information, refer to Chapter 7,
“Wavelength addition and deletion” and Configuration - Connections
Management, 323-1851-320.
Note: If the channels are provisioned as SNCs, the SNCs only need to be
changed to IS which will delete the underlying channels. For more
information, refer to Configuration - Control Plane, 323-1851-330.
—end—

4-1
Photonic layer site testing procedures 4-
Photonic layer site testing procedures describe how to test the photonic layer
in 6500 network element. Make sure the SLAT prerequisites listed in Chapter
1, “SLAT process overview” are met and Nodal SLAT procedures are
completed before starting the photonic layer site testing procedures.
Procedures in this chapter do not apply to the passive OTS network. For the
passive OTS network procedures, see “Passive OTS network procedures” on
page 6-1.
Procedures in this chapter do not apply to the fixed-12/44/64/88/96 band plan

thin terminal configurations. For the fixed band plan thin terminal
configurations, see Chapter 5, “Fixed-plan terminal node procedures”,
Waveserver and 6500 Interworking, 323-4001-165, or Waveserver Ai and
6500 Interworking, 323-4002-165.

• “Photonic layer site testing procedures” on page 4-3

BIP breaker interface panel
CCMD colorless channel mux/demux
CDA Colorless CMD Direct Attach
CDC ROADM colorless directionless contentionless ROADM (configurations with
Flex WSS C-Band w/OPM 20x1 in the ROADM OTS)
CHC channel control
COADM colorless optical add/drop multiplexer
CS Coherent Select
DGFF dynamic gain flattening filter

4-2 Photonic layer site testing procedures
DHCP dynamic host configuration protocol

DIA direction independent access
EBER excessive bit error rate
ID identifier
ILAN intershelf LAN
IP Internet protocol
LED light emitting diode
MLAx MLA, MLA2, or MLA3
MPO Multifiber Push-on
NE network element
OBB Optical Bridge and Broadcast
OBMD Optical Broadband Mux/Demux
OSPF open shortest path first
PC personal computer
PEC product engineering code
Rx receive
SMD selective mux/demux
SP shelf processor

SRA single line Raman amplifier

Tx transmit
UPC user privilege code
WT wavelength translator
Photonic layer site testing procedures

Table 4-1
Procedure
Procedure 4-1, “Connecting intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM sites”
Procedure 4-2, “Adding a new CMD44, CMD64, CMD16, CMD24, CMD96, or BMD2”
Procedure 4-3, “Adding a new OMD4 or OMX”
Procedure 4-4, “Adding a new SCMD4”
Procedure 4-5, “Adding a new CCMD12”
Procedure 4-6, “Adding a new CCMD8x16 or a CXM C-Band Type 1”
Procedure 4-7, “Testing ROADM channel access continuity”
Procedure 4-8, “Testing a CDC ROADM configuration”
Procedure 4-9, “Testing TOADM channel access continuity”
Procedure 4-10, “Testing a DIA configuration”
Procedure 4-11, “Testing a low channel count DIA configuration”
Procedure 4-12, “Testing a Colorless OADM configuration”
Procedure 4-13, “Connecting intra-site fibers and testing a Colorless Direct Attach configuration
(COADM OTS connected to 1x9 or 1x2 WSS or RLA)”
Procedure 4-14, “Connecting intra-site fibers for a Colorless Direct Attach configuration
(CCMD12/CMD44/CMD64 connected to 1x20 WSS)”
Procedure 4-15, “Testing Colorless Direct Attach with Direct Attach CMD44/CMD64 configurations
Procedure 4-16, “Testing a line amplifier node”

Table 4-1
Procedure
Procedure 4-17, “Testing DGFF nodes”
Procedure 4-18, “Connecting intra-site fibers for Coherent Select sites”
Procedure 4-19, “Testing a Coherent Select line amplifier node”
Procedure 4-20, “Testing a Coherent Select Terminal - Colored node”
Procedure 4-21, “Testing Coherent Select Directionless or Directional nodes”
Procedure 4-22, “Connecting inter-NE fibers and testing the photonic layer”
Procedure 4-23, “Configuring a single span 100 GHz CMD44 point-to-point terminal”
Procedure 4-24, “Configuring a single span 100 GHz CMD16/CMD24 point-to-point terminal”
Procedure 4-25, “Configuring a single span OMD4/CMD44 or OMX point-to-point terminal”
Procedure 4-26, “Equalizing a thin terminal system”
Procedure 4-27, “Configuring a remote CMD44 terminal”
Procedure 4-28, “Connecting intra-site fibers for 1x20 Colorless Directionless (CD) ROADM with
FIM4 sites”
Procedure 4-29, “Site testing for 1x20 Colorless Directionless (CD) ROADM with FIM4”
Procedure 4-30, “Connecting intra-site fibers for 1x20 Colorless Directionless (CD) ROADM with FIM
Type 3 sites”
Procedure 4-31, “Site testing for 1x20 Colorless Directionless (CD) ROADM with FIM Type 3”

Procedure 4-1
Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites
Use this procedure to perform intra-site fiber connections at a line amplifier
site or a TOADM/ROADM/DGFF/DIA/Colorless OADM site. In this procedure,
CMD44 refers to both the regular CMD44, the enhanced 100GHz CMD44 with
isolator (eCMD44), and the enhanced 50GHz CMD44 unless specified
otherwise.
The configurations shown in the following figures are also known as MuxAmp
configurations:
• “Intra-NE fiber connections at a ROADM site (CMD44 only)” on page 4-48
• “Intra-NE fiber connections at a ROADM site with interior SLA” on page
4-49
• “Intra-NE fiber connections at a ROADM site with single 2xOSC circuit
pack” on page 4-50
• “Intra-NE fiber connections at a ROADM site (example shows XLA and
SRA)” on page 4-51
• “Intra-NE fiber connections at a ROADM site (CMD44 and CMD64)” on
page 4-52
• “Intra-NE fiber connections at a ROADM site (CMD96)” on page 4-53
• “Intra-NE fiber connections at a ROADM site using RLA/CMD64” on page
4-54
• “Intra-NE fiber connections at a ROADM site using RLA/CMD44” on page
4-55
• “Intra-NE fiber connections at a ROADM site using RLA/CMD64 with
ESAM/SAM/SRA (SAM shown)” on page 4-56
• “Intra-NE fiber connections at a ROADM site using RLA/CMD44 with
ESAM/SAM/SRA (SRA shown)” on page 4-57
• “20-Degree Colorless Directional with FIM5 and FIM6” on page 4-58
• “Intra-NE fiber connections between a low channel count DIA and
backbone OTS (up to 4 degrees and 4 DIA banks)” on page 4-59
backbone OTS (up to 8 degrees)” on page 4-60
backbone OTS (with CMD44 connected to amplified ports of backbone
WSS)” on page 4-61


Connecting intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM sites

backbone OTS (with CMD44 connected to unamplified ports of backbone
WSS)” on page 4-62
backbone OTS using RLA” on page 4-63
• “Inter-NE fiber connections between a low channel count DIA and
backbone OTS with CMD44/CMD64 connected to amplified and
unamplified ports of backbone WSS” on page 4-64
• “Intra-NE fiber connections at a ROADM site with XLA and SRA - DSCM
placement” on page 4-65
• “Intra-NE fiber connections at a ROADM site with ESAM-MLAx (example
shows MLA)” on page 4-65
• “Intra-NE fiber connections (CMD44 to BMD2 to WSS)” on page 4-66
• “Intra-NE fiber connections (CMD44 to BMD2 to SLA to WSS)” on page
4-67
• “Intra-NE fiber connections (CMD44 to Drop LIM to WSS)” on page 4-68
• “Intra-NE fiber connections between a 100 GHz DIA and backbone OTS”
on page 4-69
• “Intra-NE fiber connections between a 50 GHz DIA (CMD44 only) and
backbone OTS” on page 4-70
• “Intra-NE fiber connections between a 50 GHz DIA (CMD44 and CMD64)
and backbone OTS” on page 4-71
• “Intra-NE fiber connections between a 50 GHz DIA (CMD44) and
backbone OTS with line facing RLA” on page 4-72
• “Intra-NE fiber connections at a Colorless OADM site” on page 4-73
• “Intra-NE fiber connections at a Colorless OADM site with CMD44 50GHz”
on page 4-74
• “Intra-NE fiber connections at a Colorless OADM site (up to 5 add/drop
banks and 5 degrees)” on page 4-75
• “Intra-NE fiber connections at a Colorless OADM site (with line facing
RLA)” on page 4-76
• “Intra-NE fiber connections at a ROADM site with a colorless OADM and
colored DIA (with CMD44/CMD64 connected to unamplified and amplified
ports of backbone WSS)” on page 4-77
• “Intra-NE fiber connections at a low channel count DIA site (non-OTS
equipment)” on page 4-78


• “Intra-NE fiber connections at a CDC ROADM site (CCMD8x16)” on page

4-79
• “Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and
CMD44 50 GHz)” on page 4-80
• “Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and
CMD44 100 GHz)” on page 4-81
The configurations shown in the following figures are also known as dynamic
gain flattening filter (DGFF) configurations:
• “Intra-NE fiber connections at a DGFF site” on page 4-82
• “Intra-NE fiber connections at a DGFF site (RLA)” on page 4-83
• “Intra-NE fiber connections at a DGFF site (RLA with SAM/ESAM/SRA)”
on page 4-84
This procedure does not cover a ROADM site using OMD4, OMDF4, OMDF8,
and/or BS. You must connect the intra-site fibers of such ROADM sites based
on the specific network configurations.
For a thin OADM site, fiber connections between the two OTSs are done after
the TOADM site is tested in Procedure 4-9, “Testing TOADM channel access
continuity”.
For a DIA or Colorless OADM configuration, fiber connections between the

DIA WSS and backbone WSSs are done after the DIA or Colorless OADM
configuration is tested in one of the following:
• Procedure 4-10, “Testing a DIA configuration”
• Procedure 4-11, “Testing a low channel count DIA configuration”
• Procedure 4-12, “Testing a Colorless OADM configuration”
To connect intra-site fibers for:

• COADM Direct Attach configurations (COADM [CCMD12 & Flex-SMD]
Direct Attach with WSS 1x9) see Procedure 4-13, “Connecting intra-site
fibers and testing a Colorless Direct Attach configuration (COADM OTS
connected to 1x9 or 1x2 WSS or RLA)”
• Colorless CMD Direct Attach sites, see Procedure 4-14, “Connecting
intra-site fibers for a Colorless Direct Attach configuration
• Coherent Select sites, see Procedure 4-18, “Connecting intra-site fibers
for Coherent Select sites”


• Colorless Directionless (CDA) sites, see Procedure 4-12, “Testing a

Colorless OADM configuration”
For configurations with colored CMDs (CMD44and CMD64):

• For configurations with a FIM, the colored CMDs must be added to a
degree using TID-SLOT-SEQ provisioning.
• For configurations without a FIM, the colored CMDs must be added to a
degree using OTS-SLOT-SEQ provisioning.
• The CMDs can be connected directly to the ROADM OTS amplified drop
ports (SW8 and SW9) or via an additional amplifier to the unamplified
ports.
• The add/drop amplifier gain values of the external/additional amplifier
associated with the colored CMD are set and forget (recommended values
(from planning tool) are manually provisioned).
• The Mux AMP automatic power reduction gets automatically disabled.
For configurations with colored CMDs (CMD96):
• The CMD96 must be added to a degree using OTS-SLOT-SEQ
provisioning.
• The CMD96 must be provisioned in the same shelf as the backbone WSS
degree.
• The CMD96 can be connected directly to the ROADM OTS amplified drop
ports (SW8 and SW9) or the ROADM OTS unamplified drop ports (SW1
and SW7) via a MLA3 or XLA.
• If the CMD96 is connected to the ROADM OTS unamplified drop ports via
a MLA3 or XLA, the add amplifier gain values associated with the CMD96
are set and forget (recommended values (from planning tool) are manually
provisioned). The drop amplifier gain values are automatically controlled.
The 20-degree ROADM provides a fully connected ROADM architecture

without any add/drop structure. ROADM groups 1-5, 6-10, 11-15, and 15-20
interconnect via a FIM5 for intra-group connections and via a FIM6 for
inter-group connections. For full connectivity the configuration requires four
FIM5 and six FIM6. The ROADM degree consists ROADM degree consists of
a 20x1 WSS, a SAM/ESAM/SRA, and either a XLA or MLA3.
For CDC configurations with colored CMDs (CMD44s):

• The colored CMDs must be connected into the WSS high isolation ports
(an additional AMP is required).


• The colored CMDs must be added to a degree using TID-SLOT-SEQ

provisioning.
• The following configuration limitations apply:
— CMD44 or CMD44/BMD2 must be provisioned in the same shelf as the
backbone WSS degree.
— The AMP associated with the CMD44 or CMD44/BMD2 must be on
the same shelf as the CMD44, CMD44/BMD2, or CMD64.
For information on the equipment supported in configurations, refer to

Photonics Equipment, 323-1851-102.6.
The Colorless OADM configuration can support up to 5 degrees and 5 DIA

banks with 100% add/drop from each DIA bank to each degree. Multiple
permutations of the number of degrees/add drop banks are supported. When
supporting multiple degrees and DIA banks, the following apply:
• It is recommended to use first available switch port (starting from switch
port 9 and then decrementing) to connect the DIA (add/drop bank).
port 1 and then incrementing) to connect other degrees.
• MLA3/XLA/MLA2/MLA are supported for the DIA AMP. Gain settings for
the DIA AMP are provided by the planning tool.
• The DIA can be connected to either the amplified ports or non amplified
ports of the backbone WSS. If connected to an amplified port of the
backbone WSS, the internal AMP of backbone WSS must be set with
Force Shutoff to Disabled and operating at Minimum Gain.
• TT-OPS is supported.
Note: For 96-channel support, use an MLA3 or XLA as COADM LIM and
NTK553GB SMD.
For Colorless OADM configurations with line facing RLA, multiple

permutations of the number of degrees/add drop banks are supported. For
example, 5 degrees with 1 DIA or 4 degrees with 2 DIAs.
• It is recommended to use:
— first available switch port (starting from RLA switch port 5 and then
decrementing) to connect the DIA/COADM (add/drop bank)
incrementing) to connect other degrees
• RLA paired with SAM/ESAM/SRA is supported.


• OPS-protected channels connected to CCMD12 (using internal or

external OPS) and TT-OPS protection supported.
For DIA configurations with colored CMDs (CMD44 and CMD64) co-existing
with a BMD2:
• The DIA can be connected to either the amplified ports or non-amplified
ports of the backbone WSS.
— Rx VOA should be disabled only if the DIA is connected to the
amplified ports.
— Non-DIA equipment cannot co-exist with DIA on the amplified ports.
— Internal AMP of backbone WSS must be set with Force Shutoff to
Disabled and operating at Minimum Gain.
• Domain must be operating in Flex control, the WSSs must be Flex
capable.
• MLA3/XLA are supported for the DIA AMP
— Gain settings for the DIA AMP are provided by the planning tool.
— If XLA used, XLA Line B is clamped at 23.6dBm output power to
ensure laser safety compliance.
— MLA2/MLA may be used with the known limitation that it has a limited
frequency range.
• TT-OPS is supported
For DIA configurations with colored CMDs (CMD44, CMD64, or CMD96) with
line facing RLA:
• multiple permutations of the number of degrees/add drop banks are
supported. For example, 5 degrees with 1 DIA or 4 degrees with 2 DIAs.
It is recommended to use:
decrementing) to connect the DIA (add/drop bank)
• RLA paired with SAM/ESAM/SRA is supported.


For low channel count DIA configurations:

• 4 degrees and 4 DIA banks are supported with 100% add/drop from each
DIA bank to each degree. Multiple permutations of the number of
degrees/add drop banks are supported. It is recommended to use:
— first available switch port (starting from switch port 7 and then
• 8 degrees is supported with 100% add/drop from each DIA bank to each
degree. Multiple permutations of the number of degrees/add drop banks
are supported. It is recommended to use:
ports of the backbone WSS.
— Rx VOA should be disabled only if the DIA is connected to the
amplified ports.
— Internal AMP of backbone WSS must be set with Force Shutoff to
• The CCMD12s and DIA WSS must be located in the same shelf.
• CMD44/CMD64 can be connected to the backbone WSS, either directly to
the amplified ports and via an amplifier (XLA/MLA3/MLA2/MLA) and a
BMD2 to the unamplified ports.
• CMD44/CMD64 is added to a degree using OTS-SLOT-SEQ. CMD44
must be located in the same shelf as the backbone WSS.
• The CMD44/CMD64 cannot co-exist with the DIA on the amplified ports.
• If CMD44/CMD64 is connected to amplified ports of the backbone WSS,
the internal AMP of the backbone WSS must be set with Force Shutoff to
• If connected to the backbone WSS unamplified ports, the add amplifier
gain values associated with the CMD44/CMD64 are set and forget
(recommended values (from planning tool) are manually provisioned). The
drop amplifier is automatically controlled.


• If CMD64 and CMD44 are co-located, to avoid the risk of contention due
to the overlapping frequencies of the CMD44 and CMD64, use a planning
tool to identify the frequencies to ensure no overlap.
For low channel count DIA with line facing RLAs:

• multiple permutations of the number of degrees/add drop banks are
supported. For example, 5 degrees with 1 DIA or 4 degrees with 2 DIAs.
It is recommended to use:
— recommended that amplified ports of DIA WSS (SW8 and SW9) are
not used
• RLA paired with a SAM/ESAM/SRA is also supported.
For configurations with combined add/drop configurations (for example,

“Intra-NE fiber connections at a ROADM site with a colorless OADM and
colored DIA (with CMD44/CMD64 connected to unamplified and amplified
ports of backbone WSS)” on page 4-77), apply the engineering rules for each
add/drop configuration. Test each add/drop configuration separately before
testing the ROADM channel access continuity (Procedure 4-7, “Testing
ROADM channel access continuity”).


Prerequisites
• Ensure that commissioning information has been entered.
• Ensure that cables are connected between the access panel and
subtending modules (CMD, BMD2, and DSCM).
• Use optical terminators on unused input faceplate connectors of installed
WSS circuit packs. If dust caps are used instead of optical terminators,
PMs can be reported against the port and the port may appear in-service.
• Ensure that the fibers have been cleaned and verified to be in working
condition, and the loss between fibers is not greater than 0.5 dB. The
fibers that are used in the following steps must be verified to be in good
working order prior to use. It is very important that fibers are cleaned and
scoped prior to being connected. Refer to the cleaning instructions in
Installation - General Information, 323-1851-201.0.
CAUTION
DANGER
Risk of injury
Step Action

If Then
you are connecting OSC to the make sure to read the Note
following equipment: messages that precede step 2, then
SLA, MLA, LIM, MLA2, MLA2 w/VOA, go to step 2
MLA3, or RLA
making OSC connections on go to step 9
SRA/ESAM/SAM circuit packs
you have finished making OSC go to step 16
connections


Step Action
Connecting OSC to SLA, MLA, LIM, MLA2, MLA2 w/VOA, MLA3, or RLA
Note: For the maximum number and slot equipping rules regarding 2xOSC
circuit packs, see the section on shelf equipping rules in the configuration
rules chapter of Planning - Ordering Information, 323-1851-151. The OSC
ports in this section (step 2 to step 8) could alternatively be on the SPAP-2
w/2xOSC circuit pack if applicable.
2 Connect the 2xOSC OSC-1 Out port to the OSC In (port 3) of the appropriate
line facing circuit pack (SLA, MLA, LIM, MLA2, MLA2 w/VOA, MLA3, or RLA).
Ensure that the OSC-1 is connected to the line facing circuit pack as indicated
in the EDP/IDP (in the correct slot).
3 Connect the 2xOSC OSC-1 In port to the OSC Out (port 4) of the appropriate
line facing circuit pack. Ensure that the OSC-1 is connected to the line facing
circuit pack as indicated in the EDP/IDP (in the correct slot).
If you need to fiber another OSC and are using a Then go to
single 2xOSC circuit pack configuration step 5
dual 2xOSC circuit packs configuration step 7
Go to step 16.
7 Connect the 2xOSC OSC-1 Out port of the second 2xOSC circuit pack to the
OSC In (port 3) of the appropriate line facing circuit pack. Ensure that the
OSC-1 is connected to the line facing circuit pack as indicated in the EDP/IDP
(in the correct slot).


Step Action
8 Connect the 2xOSC OSC-1 In port of the second 2xOSC circuit pack to the
OSC Out (port 4) of the appropriate line facing circuit pack. Ensure that the
Then go to step 1.
Making OSC connections on SRA/ESAM/SAM
9 Make sure to read and observe the following CAUTION and Note.
CAUTION
Risk of not detecting OSC Optical Line Failure alarms
Make sure to connect the OSC fibers as indicated in the
EDP/IDP. Otherwise, Optical Line Failure alarms may
not be detected correctly in single fiber cut scenarios.
(Double fiber cuts are not affected.)
The Optical Line Failure condition invokes “Automatic

Line ShutOff” (ALSO), which is a regulatory safety
requirement that automatically shuts down the amplifier
optically upstream of the cut/disconnect and in the
opposite direction.
Note: If you are making OSC connections for SRA/ESAM/SAM and if

SPAP-2 w/2xOSC circuit packs are also present in the shelf, make sure to use
the SRA/ESAM/SAM OSC ports for OSC connectivity. Do not use the OSC
ports of the SPAP-2 w/2xOSC.


Step Action
10 On the SRA/ESAM/SAM circuit pack, connect the OSC SFP Tx port to the
OSC In port (Port 3).
If Then go to
you are connecting an NTK504BA OSC Filter module step 13
you are not using and OSC Filter module and are step 12
completing the OSC connections on SRA/ESAM/SAM
12 Connect the OSC Out (Port 4) to the OSC SFP Rx port.

Then go to step 1.
13 Connect the OSC Filter In port to the OSC Out (Port 4) of the SRA.
14 Connect the OSC Filter Out port to the DWDM OSC SFP Rx (Port 2 Rx) of
the SRA.
15 Connect the DWDM OSC SFP Tx (Port 2 Tx) of the SRA to the OSC In
(Port 3) of the SRA.
Then go to step 1.
If you are performing intra-NE fibering at a Then go to
line amplifier site step 17
TOADM site step 58
ROADM site step 71
Connecting intra-NE fibers at a line amplifier site

If you are performing intra-NE fibering at a line amplifier Then go to
site equipped
with SRA/ESAM/SAM line facing circuit packs and XLA step 18
circuit packs
with ESAM-MLAx-ESAM step 26
with ESAM-MLAx-MLAx-ESAM step 32
with ESAM-MLAx-MLAx step 40
with ESAM/SAM-XLA-XLA-ESAM/SAM step 46
otherwise step 51


Step Action
Performing intra-NE fibering at a line amplifier site equipped with SRA/ESAM/SAM line facing circuit
packs and XLA circuit packs
18 See Figure 4-3 on page 4-42 for an example of intra-NE fibering at a line
amplifier site with XLA circuit packs. (The line facing circuit pack can be
ESAM, SAM, or SRA.)
The line amplifier site contains two OTSs. One OTS contains one of the line
facing circuit packs and the XLA (OTS 1 in Figure 4-3 on page 4-42). The
other OTS contains the second line facing circuit pack (OTS2 in Figure 4-3 on
page 4-42).
Make sure to fiber correctly. The system derives the adjacencies based on the
OTS slot sequence provisioning.
19 Connect the Line A Out (port 7) of the line facing circuit pack that is in the
same OTS as the XLA either to a DSCM In port or to the Line A In (port 8) of
the XLA circuit pack. When connecting to a DSCM, ensure that the
connection is made as indicated in the EDP/IDP (DSCM in the correct slot).
Ensure the correct fixed pad is inserted in the connection as indicated in the
EDP/IDP.
20 If applicable, connect the first DSCM to the second DSCM in the Line A
direction towards the XLA.
21 If not connected in step 19, connect the Line A In (port 8) of the XLA circuit
pack to the DSCM Out port. If only one DSCM, the DSCM you are connecting
to is the same as in step 19. If two DSCMs, you are connecting to the second
DSCM. Ensure the correct fixed pad is inserted in the connection as indicated
in the EDP/IDP.
22 Connect the Line A Out (port 7) of the XLA either to a DSCM In port or to the
Line B In (port 6) of the line facing circuit pack that is in the other OTS than
the XLA (OTS2 in Figure 4-3). When connecting to a DSCM, ensure that the
connection is made as indicated in the EDP/IDP (DSCM in the correct slot).
EDP/IDP.
23 If applicable, connect the first DSCM to the second DSCM in the Line A
direction towards the next line facing circuit pack.
24 If not connected in step 22, connect the Line B In (port 6) of the line facing
circuit pack to the DSCM Out port. If only one DSCM, the DSCM you are
connecting to is the same as in step 22. If two DSCMs, you are connecting to
the second DSCM. Ensure the correct fixed pad is inserted in the connection
as indicated in the EDP/IDP.


Step Action
25 Perform step 19 to step 24 in the opposite direction. The port numbers are as
follows:
• OTS2 line facing circuit pack Line A Out - port 7
• XLA Line B In - port 6
• XLA Line B Out - port 5
• line facing circuit pack that is in the same OTS as the XLA (OTS1) -
Line B In port 6
Go to step 56.
Performing intra-NE fibering at a line amplifier site equipped with ESAM +MLAx+ESAM
amplifier site with ESAM-MLAx-ESAM circuit pack configuration.
The line amplifier site contains two OTSs. One OTS contains one of the
ESAMs and the MLAx (OTS 1 in Figure 4-4 on page 4-43). The other OTS
contains the second ESAM (OTS2 in Figure 4-4 on page 4-43).
27 Connect the Line A Out (port 7) of the ESAM that is in the same OTS as the
MLAx either to a DSCM In port or to the Line A In (port 8) of the MLAx circuit
pack. When connecting to a DSCM, ensure that the connection is made as
indicated in the EDP/IDP (DSCM in the correct slot). Ensure the correct fixed
pad is inserted in the connection as indicated in the EDP/IDP.
28 If not connected in step 27, connect the Line A In (port 8) of the MLAx circuit
pack to the DSCM Out port. Ensure the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
29 Connect the Line A Out (port 7) of the MLAx either to a DSCM In port or to
the Line B In (port 6) of the ESAM circuit pack that is in the other OTS than
the MLAx (OTS2 in Figure 4-4 on page 4-43). When connecting to a DSCM,
ensure that the connection is made as indicated in the EDP/IDP (DSCM in
the correct slot). Ensure the correct fixed pad is inserted in the connection as
30 If not connected in step 29, connect the Line B In (port 6) of the ESAM to the
DSCM Out port. Ensure the correct fixed pad is inserted in the connection as


Step Action
31 Perform step 27 to step 30 for the opposite direction. The port numbers are
as follows:
• OTS2 ESAM circuit pack Line A Out - port 7
• MLAx Line B In - port 6
• MLAx Line B Out - port 5
• ESAM circuit pack that is in the same OTS as the MLAx (OTS1) -
Line B In port 6
Go to step 56.
Performing intra-NE fibering at a line amplifier site equipped with ESAM -MLAx-MLAx-ESAM
amplifier site with ESAM-MLAx-MLAx-ESAM circuit pack configuration.
The line amplifier site contains two OTSs. One OTS contains one of the
ESAMs and one MLAx (OTS 1 in Figure 4-5 on page 4-44). The other OTS
contains the second MLAx and the second ESAM (OTS2 in Figure 4-5 on
page 4-44).
33 Connect the Line A Out (port 7) of the first ESAM either to a DSCM In port or
to the Line A In (port 8) of the MLAx circuit pack that is in the same OTS as
the first ESAM. When connecting to a DSCM, ensure that the connection is
made as indicated in the EDP/IDP (DSCM in the correct slot). Ensure the
correct fixed pad is inserted in the connection as indicated in the EDP/IDP.
35 Connect the Line A Out (port 7) of the MLAx from OTS 1 either to a DSCM In
port or to the Line B In (port 6) of the MLAx circuit pack that is in the other
OTS (OTS2 in Figure 4-5 on page 4-44). When connecting to a DSCM,
ensure that the connection is made as indicated in the EDP/IDP (DSCM in
36 If not connected in step 35, connect the Line B In (port 6) of the OTS2 MLAx
circuit pack to the DSCM Out port. Ensure the correct fixed pad is inserted in
the connection as indicated in the EDP/IDP.


Step Action
37 Connect the Line B Out (port 5) of the OTS2 MLAx either to a DSCM In port
or to the Line B In (port 6) of the ESAM circuit pack that is in the same OTS
(OTS2 in Figure 4-5 on page 4-44). When connecting to a DSCM, ensure that
the connection is made as indicated in the EDP/IDP (DSCM in the correct
slot). Ensure the correct fixed pad is inserted in the connection as indicated
in the EDP/IDP.
38 If not connected in step 37, connect the Line B In (port 6) of the OTS2 ESAM
circuit pack to the DSCM Out port. Ensure the correct fixed pad is inserted in
the connection as indicated in the EDP/IDP.
as follows:
• OTS2 ESAM Line A Out - port 7
• OTS2 MLAx Line A In - port 8
• OTS2 MLAx Line A Out - port 7
• OTS1 MLAx Line B In - port 6
• OTS1 MLAx Line B Out - port 5
• OTS1 ESAM Line B In - port 6
Go to step 56.
Performing intra-NE fibering at a line amplifier site equipped with ESAM-MLAx-MLAx
amplifier site with ESAM-MLAx-MLAx circuit pack configuration.
The line amplifier site contains two OTSs. One OTS contains the ESAM and
one of the MLAx (OTS 1 in Figure 4-6 on page 4-45). The other OTS contains
the second MLAx (OTS2 in Figure 4-6 on page 4-45).
41 Connect the Line A Out (port 7) of the ESAM either to a DSCM In port or to
the Line A In (port 8) of the MLAx circuit pack that is in the same OTS as the
ESAM. When connecting to a DSCM, ensure that the connection is made as


Step Action
43 Connect the Line A Out (port 7) of the MLAx from OTS 1 either to a DSCM In
port or to the Line B In (port 6) of the MLAx circuit pack that is in the other
OTS than the ESAM (OTS2 in Figure 4-6 on page 4-45). When connecting to
a DSCM, ensure that the connection is made as indicated in the EDP/IDP
(DSCM in the correct slot). Ensure the correct fixed pad is inserted in the
44 If not connected in step 43, connect the Line B In (port 6) of the MLAx from
OTS2 to the DSCM Out port. Ensure the correct fixed pad is inserted in the
as follows:
• OTS2 MLAx circuit pack Line A Out - port 7
• OTS1 MLAx Line B In - port 6
• OTS1 MLAx Line B Out - port 5
• ESAM circuit pack Line B In - port 6
Go to step 56.
Performing intra-NE fibering at a line amplifier site equipped with ESAM/SAM-XLA-XLA-ESAM/SAM
amplifier site with SAM-XLA-XLA-SAM circuit pack configuration.
The line amplifier site contains two OTSs. Each OTS contains one
ESAM/SAM and one XLA.
47 Connect the Line A Out (port 7) of the first ESAM/SAM to the Line A In (port
8) of the XLA circuit pack that is in the same OTS as the first ESAM/SAM.
EDP/IDP.
48 Connect the Line A Out (port 7) of the XLA from OTS 1 to the Line B In (port
6) of the XLA circuit pack that is in the other OTS (OTS2 in Figure 4-7 on page
4-45). Ensure the correct fixed pad is inserted in the connection as indicated
in the EDP/IDP.


Step Action
49 Connect the Line B Out (port 5) of the OTS2 XLA to the Line B In (port 6) of
the ESAM/SAM circuit pack that is in the same OTS (OTS2 in Figure 4-7 on
page 4-45). Ensure the correct fixed pad is inserted in the connection as
as follows:
• OTS2 ESAM/SAM Line A Out - port 7
• OTS2 XLA Line A In - port 8
• OTS2 XLA Line A Out - port 7
• OTS1 XLA Line B In - port 6
• OTS1 XLA Line B Out - port 5
• OTS1 ESAM/SAM Line B In - port 6
Go to step 56.
Performing intra-NE fibering at a line amplifier site
51 See Figure 4-1 on page 4-40 or Figure 4-2 on page 4-41 for an example of
intra-NE fibering at a line amplifier site.
52 Connect the Line A Out (port 7) of the first line facing circuit pack either to a
DSCM IN port or to the Line B In (port 6) of the next adjacent line facing circuit
pack. When connecting to a DSCM, ensure that the connection is made as
53 If not connected in step 52, connect the Line B In (port 6) of the next adjacent
line facing circuit pack to the DSCM Out port. The DSCM you are connecting
to is the same as in step 52. Ensure the correct fixed pad is inserted in the
54 Connect the Line A Out (port 7) of the adjacent line facing circuit pack either
to a DSCM IN port or to the Line B In (port 6) of the first line facing circuit pack.
When connecting to a DSCM, ensure that the connection is made as
indicated in the EDP/IDP (DSCM in the correct slot). Make sure the correct
fixed pad is inserted in the connection as indicated in the EDP/IDP.
55 If not connected in step 54, connect the Line B In (port 6) of the first line facing
circuit pack to the DSCM Out port. The DSCM you are connecting to is the
same as in step 54. Ensure that the correct fixed pad is inserted in the
Go to step 56.


Step Action
Connecting LIM, or XLA if present, to 2-port OPM

If Then go to
you are connecting the XLA, or the line facing circuit step 57
pack if XLA is not present, to a 2-port OPM
otherwise You have completed
this procedure.
57 Connect the monitor ports (port 1 and port 2) of the LIM, or XLA if present, to
the monitor ports of the 2-port OPM (port 1 and port 2) as indicated in the
EDP/IDP.
Note: Connecting SRA/ESAM/SAM monitor ports (ports 9 and 10) to an
OPM is not supported.


Step Action
Connecting intra-NE fibers at a TOADM site

58 See Figure 4-8 on page 4-46 or Figure 4-9 on page 4-47 to perform the steps
for intra-NE fibering at a TOADM site.
59 Starting with the SCMD4 that is the farthest away from the line facing circuit
pack according to the EDP/IDP. Complete the SCMD4 cascade fibering by
performing step 60 to step 62.
60 Connect the Common Out (port 2) of the SCMD4 to the Upgrade In (port 11)
of the next SCMD4.
61 Connect the Common In (port 1) of the SCMD4 to the Upgrade Out (port 12)
of the next SCMD4.
62 Repeat from step 60 on the next circuit pack in the cascade until you reach
the last SCMD4 in the cascade (that is, the SCMD4 that is connected to the
line facing circuit pack).
63 Connect the Common Out (port 2) of the last SCMD4 in the cascade (that is,
the SCMD4 that is connected to the line facing circuit pack) to the Line B In
(port 6) of the line facing circuit pack.
64 Connect the Common In (port 1) of the last SCMD4 in the cascade (that is,
the SCMD4 that is connected to the line facing circuit pack) to the Line A Out
(port 7) of the line facing circuit pack.
65 If the configuration Then
does not include an ESAM go to step 68
includes an ESAM (see Figure 4-9 on page 4-47) go to step 66
66 Connect the Line A Out (port 7) of the ESAM to the Line A In (port 8) of the
MLAx circuit pack.
67 Connect the Line B Out (port 5) of the MLAx to the Line B In (port 6) of the
ESAM circuit pack.
If this is a Then
thin terminal site go to step 69
thin OADM site Repeat step 59 to step 64 for the OTS facing
the other direction. Then go to step 69.


Step Action
69 If Then go to
you want to connect the line facing circuit pack to a step 70
2-port OPM
otherwise You have completed
this procedure.
Connecting LIM to 2-port OPM at a TOADM site

70 Connect the monitor ports (port 1 and port 2) of the line facing circuit pack to
the monitor ports of the 2-port OPM (port 1 and port 2) as indicated in the
EDP/IDP.
Connecting intra-NE fibers at a ROADM or a DGFF site
Note: If duplex LC-LC patch cords are used for connections between the
WSSOPM monitor ports and amplifier circuit pack monitor ports, ensure the
fibers are traced properly for no crossed connections. If simplex LC-LC patch
cords are available, connecting them one at a time can reduce the risk of
misfibering.
If Then go to
this is a ROADM site that uses ESAM-MLAx step 97
this is a CDC ROADM site step 72
DGFF step 78
ROADM configuration (other than the above) step 78
72 See the following for examples of intra-NE fibering at a CDC ROADM site.
• Figure 4-42 on page 4-79


Step Action
73 CDC ROADM configurations include Fiber Interconnect Modules (FIM). Keep

in mind the following information regarding the FIMs. For more information,
see the Photonic passive modules table in Planning - Ordering Information,
323-1851-151.
FIM Type 1 is shipped with the following equipment pre-installed:
• dust caps on MPO ports 1 to 4 (WSS1)
• MPO Loopback (APC, SM, 12 Fiber) modules in all the other MPO port
positions
• Duplex LC Loopback (SM) modules in each of the duplex LC connector
positions
FIM Type 2 is shipped with the following equipment pre-installed:

• dust caps on MPO ports 1 to 4 (WSS1)
• MPO Loopback (APC, SM, 12 Fiber) modules in all the other MPO port
positions
In addition to providing the optical loopback operation required by

applications that use the FIM, the loopback modules act as dust caps for the
optical ports. Do not remove the loopback modules except as part of a fiber
installation procedure. The FIM tray assembly includes a bag of dust caps
that must be put on any loopback connector that is being removed and saved
for future use.
74 If your configuration contains CCMD8x16s, start with one CCMD8x16 and
connect it to the FIM as indicated in the EDP/IDP. Repeat for all applicable
CCMD8x16 modules as indicated in the EDP/IDP.
This equipment uses MPO cables and connectors. For steps to:
• connect MPO cables, see the Installation technical publication specific to
the respective 6500 shelf type (in the procedure on routing fiber-optic
cables and electrical cables to circuit packs in the 6500 shelf)
• inspect and clean MPO connectors, see Installation - General
Information, 323-1851-201.0
CAUTION
Risk of affecting performance
You must inspect and clean the MPO connectors after
removing the MPO cable from its original packaging or
if the MPO cable has been removed from the faceplate
for any reason.
Always inspect the MPO connectors before making a

connection.


Step Action
75 If your configuration contains 50 GHz CMD44s:

a. Connect the common Out (port 90) of the CMD44 to input port of BMD2
(either 3 or 5) as indicated in the EDP/IDP. If another CMD44 is present,
connect that to the other input port of BMD2. See Figure 4-30 on page
4-67.
b. Connect the common In (port 89) of the CMD44 to corresponding Output
port of BMD2 (either 4 or 6) as indicated in the EDP/IDP.
c. Connect the common Out of BMD2 (port 2) to the Line B In (port 6) of the
XLA or MLA3 circuit pack as indicated in the EDP/IDP.
d. Connect the common In of BMD2 (port 1) to the Line A Out (port 7) of the
XLA or MLA3 circuit pack as indicated in the EDP/IDP.
e. Connect the Line B Out (port 5) of the XLA or MLA3 circuit pack to the
one of the two FIM Upgrade In ports (A or B) for the degree as indicated
in the EDP/IDP.
Note: The FIM upgrade ports connect to one of the two WSS high
isolation ports.
f. Connect the Line B Out (port 5) of the XLA or MLA3 circuit pack to the
one of the two FIM Upgrade Out ports (A or B) for the degree as indicated
in the EDP/IDP.
isolation ports.
76 If your configuration contains 100 GHz CMD44s:
a. Connect the common Out (port 90) of the CMD44 to the Line B In (port
6) of the XLA or MLA3 circuit pack as indicated in the EDP/IDP.
b. Connect the common In (port 89) of the CMD44 to the Line A Out (port
7) of the XLA or MLA3 circuit pack as indicated in the EDP/IDP.
c. Connect the Line B Out (port 5) of the XLA or MLA3 circuit pack to the
one of the two FIM Upgrade In ports (A or B) for the degree as indicated
in the EDP/IDP.
isolation ports.
d. Connect the Line B Out (port 5) of the XLA or MLA3 circuit pack to the
one of the two FIM Upgrade Out ports (A or B) for the degree as indicated
in the EDP/IDP.
isolation ports.


Step Action
77 Connect the FIM to the WSSOPM for all applicable ROADM degrees as
This equipment uses MPO connectors. See step 74 for instructions on how
to handle MPO cables and connectors.
Then go to step 79.
78 See:
• the following figures for examples of intra-NE fibering at ROADM sites:
— Figure 4-10 on page 4-48 - CMD44, WSS 5x1, MLA, dual 2xOSC
— Figure 4-11 on page 4-49 - CMD44, WSS 5x1, MLA, interior SLA,
dual 2xOSC
— Figure 4-12 on page 4-50 - CMD44, WSS 5x1, MLA, interior SLA,
single 2xOSC
— Figure 4-13 on page 4-51 - CMD44, WSS 1x9, XLA, SRA
— Figure 4-14 on page 4-52 - CMD44, CMD64/XLA or MLA3, WSS 1x9,
amp
— Figure 4-15 on page 4-53 - CMD96, CMD96/XLA, WSS 1x9, MLA
— Figure 4-16 on page 4-54 - CMD64, RLA
— Figure 4-17 on page 4-55 - CMD44, RLA
— Figure 4-18 on page 4-56 - CMD64, RLA, SAM
— Figure 4-19 on page 4-57 - CMD64, RLA, SRA
— Figure 4-20 on page 4-58 - WSS 20x1, XLA, SAM. FIM5, FIM6
— Figure 4-21 on page 4-59 - low channel count DIA (WSS/CCMD12)
and backbone OTS (WSS and MLA3) - 4 DIA and 4 degrees
and backbone OTS (WSS and MLA3) - 8 degrees
and backbone OTS (WSS and MLA3) - with CMD44
and backbone OTS (WSS and MLA3) - with CMD44/MLA/SLA
and backbone OTS (RLA)
and backbone OTS (WSS and MLA3) with CMD44/CMD64
connected to amplified and unamplified ports of backbone WSS
• the following figures for examples for examples of intra-NE fibering at a
DGFF site
— Figure 4-45 on page 4-82 - WSS 5x1, MLA, dual 2xOSC
— Figure 4-46 on page 4-83 - RLA, dual 2xOSC
— Figure 4-47 on page 4-84 - RLA, SAM


Step Action
At sites equipped with XLA, the line facing circuit pack can be ESAM, SAM,
or SRA.
If Then go to
the site uses SRA/ESAM/SAM and XLA/RLA circuit step 80
packs
otherwise step 89

If a DSCM module is Then go to
present between SRA/ESAM/SAM and XLA step 81
not present step 87
81 Connect the Line A Out (port 7) of the SRA/ESAM/SAM circuit pack to the
DSCM In port. Ensure that the connection is made as indicated in the
EDP/IDP (DSCM in the correct slot). Ensure the correct fixed pad is inserted
in the connection as indicated in the EDP/IDP.
82 If applicable, connect the first DSCM to the second DSCM.
83 Connect the DSCM Out port to the Line A In (port 8) of the XLA/RLA. If only
one DSCM, the DSCM you are connecting is the same as in step 81. If two
DSCMs, you are connecting the second DSCM. Ensure the correct fixed pad
is inserted in the connection as indicated in the EDP/IDP.
84 Connect Line B In (port 6) of the line facing circuit pack to the DSCM Out port.
Ensure that the connection is made as indicated in the EDP/IDP (DSCM in
86 Connect Line B Out (port 5) of the XLA/RLA to the DSCM In port. If only one
DSCM, the DSCM you are connecting is the same as in step 84. If two
Go to step 81.
87 Connect Line A Out (port 7) of the line facing circuit pack to the Line A In (port
8) of the XLA/RLA.
88 Connect the Line B In (port 6) of the line facing circuit pack to the Line B Out
(port 5) of the XLA/RLA.


Step Action

present step 90
not present step 95

If the DSCM module is located Then go to
between the output of the pre-amplifier and the step 91
input of the cascaded SLA line port (as per Figure
4-11 on page 4-49 or Figure 4-12 on page 4-50).
This branch also applies to XLA configurations.
at the end of span (before pre-amplifier) (as per step 94
Figure 4-10 on page 4-48). This branch does not
apply to XLA configurations.
91 Connect the Line A Out (port 7) of the line facing circuit pack, or XLA if
present, to the DSCM In port. Ensure that the connection is made as
92 Connect the DSCM Out port to the Line A In (port 8) of the line circuit pack
(cascaded SLA). The DSCM you are connecting to is the same as in step 91.
93 Connect the Line A Out (port 7) of the line circuit pack (cascaded SLA) to the
Common IN port of the WSS. Ensure the correct fixed pad is inserted in the
Go to step 96.
94 Connect the Line A In (port 8) of the line circuit pack (pre-amplifier) or RLA to
the DSCM Out port. Ensure that the connection is made as indicated in the
EDP/IDP (DSCM in the correct slot). Ensure the correct fixed pad is inserted
in the connection as indicated in the EDP/IDP.
95 Connect the Common In (port number depends on the WSS) of the WSS or
RLA (port 8) to the Line A Out (port 7) of the line facing circuit pack.
96 Connect the Common Out (port number depends on the WSS) of the WSS
or RLA (port 5) to the Line B In (port 6) of the line facing circuit pack.
Go to step 109.
97 See Figure 4-28 on page 4-65 for an example of intra-NE fibering at a
ROADM site with MLAx-ESAM configuration.


Step Action

present between the ESAM and the MLAx step 99
not present step 105
99 Connect the Line A Out (port 7) of the ESAM circuit pack to the DSCM In port.
Ensure that the connection is made as indicated in the EDP/IDP (DSCM in
101 Connect the DSCM Out port to the Line A In (port 8) of the MLAx. If only one
102 Connect Line B In (port 6) of the ESAM to the DSCM Out port. Ensure that
the connection is made as indicated in the EDP/IDP (DSCM in the correct
slot). Ensure the correct fixed pad is inserted in the connection as indicated
in the EDP/IDP.
104 Connect Line B Out (port 5) of the MLAx to the DSCM In port. If only one
Go to step 81.
105 Connect Line A Out (port 7) of the ESAM to the Line A In (port 8) of the MLAx.
106 Connect the Line B In (port 6) of the ESAM to the Line B Out (port 5) of the
MLAx.
107 Connect the Common In (port number depends on the WSS) of the WSS to
the Line A Out (port 7) of the MLAx.
108 Connect the Common Out (port number depends on the WSS) of the WSS to
the Line B In (port 6) of the MLAx.
Connecting WSS OPM or 2-port OPM to LIM, or to XLA if present, or to MLAx in ESAM-MLAx ROADM
configurations
If you are connecting to Then go to
WSS OPM step 110
2-port OPM step 111


Step Action
110 Connect the Line B MON and Line A MON ports of:
• the line facing circuit pack, or
• the XLA if present, or
• the MLAx in ESAM-MLAx ROADM configurations
to the correct WSS OPM ports as follows:

• Line B MON (port 1) to OPM Monitor 1 (port 1)
• Line A MON (port 2) to OPM Monitor 2 (port 2)
To avoid misfibering, ensure that the patch cords are correctly labeled.
Go to step 112.
111 Connect Line B MON and Line A MON ports of:
• the line facing circuit pack, or
• the XLA if present, or
• the RLA, or
• the MLAx in ESAM-MLAx ROADM configurations
to the monitor ports of the 2-port OPM (port 1 and port 2) as indicated in the
EDP/IDP.
112 Repeat step 79 to step 111 for all ROADM/DGFF OTSs at the site.
Connecting WSS to WSS
113 Connect the Switch In port of the WSS or RLA at one end of the fiber
connection for the pass-through channel to the Switch Out port of the WSS
or Demux Out port of the RLA at the other end of the fiber connection, as
114 Connect the Switch Out port of the WSS or Demux Out port of the RLA at one
end of the fiber connection for the pass-through channel to the Switch In port
of the WSS or RLA at the other end of the fiber connection, as indicated in
the EDP/IDP.
115 Repeat step 113 and step 114 for all the fiber connections required for
pass-through channels at the same site.


Step Action

If the site Then
has no channel access (DGFF site) you have completed
this procedure
is a 20-degree ROADM with no channel access go to step 118
using FIM5 and FIM6
is a ROADM site with CMD44 access go to step 117
is a ROADM site with CCMD12 access go to step 158
is a ROADM with a low channel count DIA go to step 171

If you want to connect a CMD44/CMD64 module to Then go to
2-port OPM step 119
otherwise step 120
Connecting FIM5, FIM6, and WSS

118 Connect the FIM5, FIM6 and WSS for all applicable ROADM degrees as
indicated in the EDP/IDP (see Figure 4-20 on page 4-58 for an example).
This equipment uses MPO cables and connectors. For steps to:
CAUTION
for any reason.

connection.
You have completed the procedure.


Step Action
Connecting CMD44/CMD64 to 2-port OPM

119 Connect the following monitor ports to the monitor port of the 2-port OPM
(either 1or 2) as indicated in the EDP/IDP:
• CMD44 - Monitor out port (port 92)
• CMD64 - Monitor out port (port 132) and/or monitor in port (port 131)
Connecting CMD44
If you want to connect a CMD44 module to Then go to
BMD2 module to WSS or RLA circuit pack step 121
BMD2 module to SLA circuit pack (DropLIM) to WSS step 125
circuit pack
WSS or RLA circuit pack step 131
SLA circuit pack (Drop LIM) to WSS circuit pack step 133
BMD2 module to amplifier in DIA configuration step 137
amplifier in DIA configuration step 141
have only CMD64 modules step 145
Note: It is recommended to connect the CMD44 ports (89/90) to the WSS

100 GHz w/OPM 5x1 Switch ports 11/12 (SW5).
For WSS 50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM 9x1:
- CMD1 defaults to SW8 (port 17,18)
For WSS 50 GHz w/OPM 2x1 with BMD2 (which defaults to SW2 – port 5,6):
- CMD1 defaults to BMD2 pairport #1 (port 3,4)
- CMD2 defaults to BMD2 pairport #2 (port 5,6)
For WSS 50 GHz w/OPM 2x1 without a BMD2
- CMD2 is not auto-provisioned


Step Action
Connecting CMD44 to BMD2 to WSS (WSS 50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM 9x1 not
supported with BMD2) or RLA
121 Connect the common Out (port 90) of the CMD44 to input port of BMD2
connect that to the other input port of BMD2. See Figure 4-29 on page 4-66.
122 Connect the common In (port 89) of the CMD44 to corresponding Output port
of BMD2 (either 4 or 6) as indicated in the EDP/IDP.
123 Connect the common Out of BMD2 (port 2) to Switch In port (or Add In port
for NTK553KA) of WSS or RLA as indicated in the EDP/IDP. For RLA, SW5
(Switch 5 In, port 29) is recommended.
124 Connect the common In of BMD2 (port 1) to Switch Out port (or Drop Out port
for NTK553KA) of WSS or RLA as indicated in the EDP/IDP. For RLA, SW5
(Switch 5 Out, port 30) is recommended.
Go to step 143.
Connecting CMD44 to BMD2 to SLA (Drop LIM) to WSS (WSS 50 GHz w/OPM 9x1/WSS Flex C-Band
w/OPM 9x1 not supported with Drop LIM or BMD2)
125 Connect the common Out (port 90) of the CMD44 to input port of BMD2
connect that to the other input port of BMD2. See Figure 4-30 on page 4-67.
126 Connect the common In (port 89) of the CMD44 to corresponding Output port
of BMD2 (either 4 or 6) as indicated in the EDP/IDP.
127 Connect the common Out of BMD2 (port 2) to the Line B In (port 6) of the SLA
circuit pack.
128 Connect the common In of BMD2 (port 1) to the Line A Out (port 7) of the SLA
circuit pack.
129 Connect the Line B Out (port 5) of the SLA circuit pack to the Switch In port
(or Add In port for NTK553KA) of WSS as indicated in the EDP/IDP.
130 Connect the Line A In (port 8) of the SLA circuit pack to the Switch Out port
(or Drop Out port for NTK553KA) of WSS as indicated in the EDP/IDP.
Go to step 143.


Step Action
Connecting CMD44 to WSS or RLA

131 Connect the Common Out (port 90) of the CMD44 to the Switch In port (or
Add In port for NTK553KA) of the WSS or RLA as indicated in the EDP/IDP.
See Figure 4-10 on page 4-48 (WSS) or Figure 4-17 on page 4-55 (RLA). For
RLA, SW5 (Switch 5 In, port 29) is recommended.
132 Connect the Common In (port 89) of the CMD44 to the Switch Out port (or
Drop Out port for NTK553KA) of the WSS or RLA as indicated in the
EDP/IDP. For RLA, SW5 (Switch 5 Out, port 30) is recommended.
Note: The internal fibering between a 50 GHz CMD44 and WSS 50 GHz
w/OPM 9x1/WSS Flex C-Band w/OPM 9x1 can be done in the following
manner. The common In and Out of the 50 GHz CMD44 card can be
connected to the switch port 8 or switch port 9, that is, port numbers 17,18 or
port numbers 19, 20. Specifically for 50 GHz CMD44, the intra fibering from
50 GHz CMD44 to WSS 50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM 9x1
is done on the corresponding ports. Pass through configuration is not allowed
on the switch ports 8 and 9 (that is, port numbers 17,18,19 and 20 for a WSS
50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM 9x1).
Go to step 143.
Connecting CMD44 to SLA (Drop LIM) to WSS (WSS 50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM
9x1 not supported with Drop LIM)
133 Connect the Common Out (port 90) of the CMD44 to the Line B In (port 6) of
the SLA circuit pack. See Figure 4-31 on page 4-68 for an example.
134 Connect the Common In (port 89) of the CMD44 to the Line A Out (port 7) of
the SLA circuit pack.
135 Connect the Line B Out (port 5) of the SLA circuit pack to the Switch In port
(or Add In port for NTK553KA) of the WSS as indicated in the EDP/IDP.
136 Connect the Line A In (port 8) of the SLA circuit pack to the Switch Out port
(or Drop Out port for NTK553KA) of the WSS as indicated in the EDP/IDP.
Go to step 143.
Connecting CMD44 to BMD2 to amplifier in DIA configuration
137 Connect the Common Out (port 90) of the CMD44 50 GHz to the Input of
BMD2 (either 3 or 5) as indicated in the EDP/IDP. If a second CMD44 50 GHz
is present, connect the second CMD44 50 GHz to the other input port of
BMD2. See Figure 4-33 on page 4-70 for an example.
138 Connect the Common In (port 89) of the CMD44 50 GHz module(s) to the
corresponding Output of BMD2 (either 4 or 6) as indicated in the EDP/IDP.
139 Connect the Common Out (port 2) of the BMD2 to Line A In (port 8) of the
amplifier circuit pack.


Step Action
140 Connect the Common In (port 1) of BMD2 to Line B Out (port 5) of the
Go to step 143.
Connecting CMD44 to amplifier in DIA configuration
141 Connect the Common Out (port 90) of the CMD44 100 GHz to Line A In
(port 8) of the amplifier circuit pack. See Figure 4-32 on page 4-69 for an
example.
142 Connect the Common In (port 89) of the CMD44 100 GHz to Line B Out
(port 5) of the amplifier circuit pack.
143 If required, repeat from step 117 for each CMD44 to be connected at the site.
144 For DIA, go to step 157. For CMD64s or CMD96s, go to step 145. Otherwise,
you have completed this procedure.
Connecting CMD64 or CMD96
If you want to connect a CMD64 or CMD96 module to Then go to
amplified ports of WSS circuit pack or ports of RLA step 146
unamplified ports of WSS circuit pack with an amplifier step 148
BMD2 module to amplifier in DIA configuration (CMD64 step 152
only)
Connecting CMD64 or CMD96 to amplified WSS ports or to unamplified RLA ports

Note: Connecting a CMD96 directly to the RLA is not supported.
146 Connect the Common Out (port 130) of the CMD64 or the CMD96 (port 194)
to the Switch In port (or Add In port for NTK553KA) of the WSS or RLA as
indicated in the EDP/IDP. See Figure 4-14 on page 4-52, Figure 4-15 on page
4-53, Figure 4-16 on page 4-54, Figure 4-26 on page 4-64, and Figure 4-40
on page 4-77.
147 Connect the Common In (port 129) of the CMD64 or the CMD96 (port 193)
to the Switch Out port (or Drop Out port for NTK553KA) of the WSS or RLA
as indicated in the EDP/IDP.
Connecting CMD64 or CMD96 to amplifier and then unamplified WSS ports
148 Connect the Common Out (port 130) of the CMD64 or the CMD96 (port 194)
to Line A In (port 8) of the amplifier circuit pack. See Figure 4-32 on page
4-69, Figure 4-26 on page 4-64, and Figure 4-40 on page 4-77 for an
example.
149 Connect the Common In (port 129) of the CMD64 or the CMD96 (port 193)
to Line B Out (port 5) of the amplifier circuit pack.


Step Action
150 Connect the Line A In (port 8) of the amplifier circuit pack to the Switch Out
port (or Drop Out port for NTK553KA) of the WSS as indicated in the
EDP/IDP.
151 Connect the Line B Out (port 5) of the amplifier circuit pack to the Switch In
port (or Add In port for NTK553KA) of the WSS as indicated in the EDP/IDP.
Connecting CMD64 to BMD2 to amplifier in DIA configuration
152 Connect the Common Out (port 130) of the CMD64 module to the Input of
BMD2 (either 3 or 5) as indicated in the EDP/IDP. See Figure 4-33 on page
4-70 and Figure 4-40 on page 4-77 for an example.
153 Connect the Common In (port 129) of the CMD64 module to the
154 If the BMD2 Then go to
is already connected to the amplifier (has a CMD44 step 157
connected)
is not already connected to the amplifier (has a step 155
CMD44 connected)
155 Connect the Common Out (port 2) of the BMD2 to Line A In (port 8) of the
156 Connect the Common In (port 1) of BMD2 to Line B Out (port 5) of the
Go to step 157.
Connecting intra-NE fibers for a DIA OTS
157 See Figure 4-32 on page 4-69, Figure 4-33 on page 4-70, Figure 4-34 on
page 4-71, Figure 4-35 on page 4-72, and Figure 4-40 on page 4-77 to
perform the steps for intra-NE fibering for a DIA OTS.
158 Connect the DIA amplifier Line B MON and Line A MON ports to the correct
DIA WSS OPM port as follows:
• Line B MON (port 1) to OPM Monitor 1 (port 1)
• Line A MON (port 2) to OPM Monitor 2 (port 2)
159 Connect the Common Out port of the DIA WSS to the DIA amplifier Line B In
(port 6).
160 Connect the Common In port of the DIA WSS to the DIA amplifier Line A Out
(port 7).
161 If required, repeat step 158 to step 160 for all DIA OTSs at the site.


Step Action

If the DIA OTS is Then
part of a Colorless OADM configuration go to step 163
otherwise you have completed this
procedure
Connecting intra-NE fibers for a COADM OTS

page 4-75, and Figure 4-39 on page 4-76 to perform the steps for intra-NE
fibering for a COADM OTS.
164 Connect the Common Out (port 26) of the CCMD12 to the Switch In port of
the SMD as indicated in the EDP/IDP.
165 Connect the Common In (port 25) of the CCMD12 to the corresponding
Switch Out port of the SMD as indicated in the EDP/IDP.
166 Connect the Monitor Out (port 27) of the CCMD12 to the corresponding
Monitor port of the SMD as indicated in the EDP/IDP.
167 Repeat step 164 and step 166 for each connected CCMD12.
168 Connect the Common Out (port 10) of the SMD to Line A In (port 8) of the
amplifier circuit pack in the DIA OTS.
169 Connect the Common In (port 9) of the SMD to Line B Out (port 5) of the
amplifier circuit pack in the DIA OTS.
170 Repeat step 164 to step 169 for all COADM OTSs at the site.
Connecting intra-NE fibers for a low channel count DIA
page 4-61, Figure 4-24 on page 4-62, Figure 4-25 on page 4-63, Figure 4-40
on page 4-77, and Figure 4-41 on page 4-78, to perform the steps for intra-NE
fibering for a low channel count DIA.
172 Connect the Common Out (port 26) of the CCMD12 to the Common In (port
21) of the WSS as indicated in the EDP/IDP.
173 Connect the Common In (port 25) of the CCMD12 to the Common Out (port
22) of the WSS as indicated in the EDP/IDP.
174 Connect the Monitor Out (port 27) of the CCMD12 to the Monitor 1 (port 1) of
the WSS as indicated in the EDP/IDP.
175 Repeat step 171 to step 174 for all low channel count DIA at the site.
—end—

Figure 4-1
Intra-NE fiber connections at a Line amplifier site (single 2xOSC configuration)

Figure 4-2
Intra-NE fiber connections at a Line amplifier site (dual 2xOSC configuration)

Figure 4-3
Intra-NE fiber connections at a line amplifier site—example shows SRA – XLA – SRA (with and
without DSCMs)
Can be SRA/ESAM/SAM
Note: A 2-port OPM can be connected at the Mon 1 and Mon 2 ports of the XLA.
circuit pack
OTS2
With DSCMs
OTS1
Can be SRA/ESAM/SAM
circuit pack

Figure 4-4
Intra-NE fiber connections at a line amplifier site—ESAM - MLAx - ESAM (example shows MLA2)

Figure 4-5
Intra-NE fiber connections at a line amplifier site—ESAM - MLAx - MLAx - ESAM (example shows
MLA)

Figure 4-6
Intra-NE fiber connections at a line amplifier site—ESAM - MLAx - MLAx (example shows MLA)
Figure 4-7
Intra-NE fiber connections at a line amplifier site—ESAM/SAM - XLA - XLA - ESAM/SAM (example
shows SAM)

Figure 4-8
Intra-NE fiber connections at a TOADM site
8
Line B Out
Line A In
MLA
Slot 13
A
B
Mon2(A Out)
Mon1(B Out)
OSC A Out
Line A Out
OSC B In
Line B In
Note 3: A 2-port OPM can be connected at the Mon 1 and Mon 2 ports of the line facing circuit pack.
4
6
B
3
7
2
1
2x OSC
OSC1 Out
WSC
1
OSC
3
1
OSC1 In SCMD4 Ch1 Out
4
OSC2 Out 3
2
WSC
OSC
Ch1 In
2
4
MUX / DEMUX
Ch2 Out
Note 2: Dual 2xOSC configuration shown. Single 2xOSC configuration is also supported.
OSC2 In
6
Common In
Slot 14 1 Ch2 In
5
2 Ch3 Out
Common Out 8
11
Upg In Ch3 In 7
12
Slot 12
Upg Out Ch4 Out
10
9
Ch4 In
Ch1 Out
SCMD4 4
3
Ch1 In
Note 1: The diagram within the dotted square represents a thin terminal.
MUX / DEMUX
Ch2 Out
6
Common In
5
1 Ch2 In
2 Ch3 Out
Common Out 8
11 7
Upg In Ch3 In
Slot 11
12
Upg Out Ch4 Out
10
9
Ch4 In
OTS
2
Ch4 Out
Slot 4
10
Upg In 9
Ch4 In
11
Upg Out Ch3 Out
12 8
Common In 7
1 Ch3 In
2 Ch2 Out
Common Out 6
5
Ch2 In
Ch1 Out
4
SCMD4 3
Ch1 In
Ch4 Out
Slot 3
10
Upg In 9
Ch4 In
11
Upg Out
MUX / DEMUX
Ch3 Out
12 8
Common In 7
1 Ch3 In
2 Ch2 Out
Common Out 6
5
2x OSC Ch2 In
Ch1 Out
OSC1 Out 4
1 SCMD4
WSC
OSC
3
3
1 Ch1 In
OSC1 In
OSC2 Out
2
WSC
OSC
4
2
OSC2 In
Slot 1
7
2
6
3
4
1
Mon1(B Out)
Mon2(A Out)
OSC A Out
OSC B In
Line A Out
Line B In
B
Slot 2
A
Line B Out
Line A In
MLA
OTS
1
5
8

Figure 4-9
Intra-NE fiber connections at a TOADM site (sCMD4+MLAx+ESAM

WSC WSC WSC WSC
2 1 2 1
Figure 4-10
Release 12.7
OSC OSC OSC OSC
2 1 2 1
2 x OSC PEC: NTK554BA

OSC1 In
OSC1 In
OSC2 Out
OSC2 Out
OSC1 Out
OSC1 Out
OSC2 In
OSC2 In
2
2
1
1
2
2
1
1

MLA WSS WSS MLA
PEC: NTK552BA PEC: NTK553EA PEC: NTK553EA PEC: NTK552BA
Line B Mon 1 Monitor 1 Monitor 1 1 Line B Mon
1 1
Line A Mon OPM OPM Line A Mon
2 2 2 2
Monitor 2 Monitor 2
OSC B In Switch 1 In Switch 1 In OSC B In
3 3
3 3
4 4
OSC A Out 4 4 OSC A Out
Common In Common In
Switch 1 Out Switch 1 Out
17 17
Copyright© 2010-2020 Ciena® Corporation

Line A In Line A Out Line B In Line B Out
8 A 7 Switch 2 In Switch 2 In 6 B 5
5 5
6 6
5 B 6 Switch 2 Out Switch 2 Out 7 A 8
Line B Out Line B In Line A Out Line A In
7 7 9:1
Switch 3 In Switch 3 In
8
Switch 4 In 8
9 Switch 4 In
Switch 5 In 9
10 Switch 5 In
1:5 Switch 6 In
1:5
10
Σ 11
Σ
Switch 6 In
Switch 7 In
11
18 12 18
Intra-NE fiber connections at a ROADM site (CMD44 only)
Switch 7 In
Common Out Switch 8 In Common Out
12
13 Switch 8 In
Switch 9 In
13
Switch 9 In
LC LC
Ch 1 In CMD44 CMD44 Ch 1 In
PEC: NTT862AA PEC: NTT862AA
Ch 1 Out Ch 1 Out
LC LC
Ch 2 In LC LC Ch 2 In
Common Out 90 90 Common Out
Ch 2 Out Ch 2 Out
89 89
Common In Common In
LC LC
Ch 43 In Ch 43 In
Legend
Ch 43 Out Ch 43 Out
44 Channel MUX/DEMUX
LC LC
= DSCM Ch 44 In Ch 44 In
= Attenuator Ch 44 Out Ch 44 Out
May 2020
323-1851-221 Standard Issue 1
Figure 4-11
Release 12.7
WSC WSC WSC WSC
2 1 2 1
OSC OSC OSC OSC

2 1 2 1

OSC1 In
OSC1 In
OSC2 Out
OSC2 Out
OSC1 Out
OSC1 Out
OSC2 In
OSC2 In

2
2
1
1
2
2
1
1
MLA SLA WSS WSS MLA

PEC: NTK552BA PEC: NTK552AA PEC: NTK553EA PEC: NTK553EA PEC: NTK552BA
Line B Mon Line B Mon 1 Monitor 1 Monitor 1 1 Line B Mon
1 1 1
Line A Mon Line A Mon OPM OPM Line A Mon
2 2 2 2 2
Monitor 2 Monitor 2

OSC B In OSC B In Switch 1 In Switch 1 In OSC B In
3 3 3
3 3
4 4 4
OSC A Out OSC A Out 4 4 OSC A Out
Common In
Common In Switch 1 Out Switch 1 Out
Line A In Line A Out Line A In Line A Out 17
A 7 7 17 Switch 2 In Switch 2 In Line B In Line B Out
8 8 A 6 B 5
5 5
6 6
5 B 6 5 6 Switch 2 Out Switch 2 Out 7 A 8
Line B Out Line B In Line B Out Line B In Line A Out Line A In
7 7 9:1
9:1
8 8
9 9
10 10
1:5 1:5
Σ Switch 5 In Switch 5 In Σ
11 11
12 12
18 Switch 5 Out Switch 5 Out 18
Common Out Common Out
13 13
14 14
Intra-NE fiber connections at a ROADM site with interior SLA
15 15
16 16
LC LC
Ch 1 Out Ch 1 Out
LC LC
Ch 2 Out Ch 2 Out
89 89
Common In Common In
LC LC
Ch 43 In Ch 43 In
Legend Ch 43 Out Ch 43 Out
LC LC
Ch 44 Out Ch 44 Out
= Attenuator
May 2020

Figure 4-12
Release 12.7
WSC WSC
4 3
OSC OSC
2 1
OSC1 In
OSC2 Out
OSC1 Out
OSC2 In

2
2
1
1
MLA SLA WSS WSS MLA
PEC: NTK552BA PEC: NTK552AA PEC: NTK553EA PEC: NTK553EA PEC: NTK552BA
Line B Mon Line B Mon 1 Monitor 1 Monitor 1 1 Line B Mon
1 1 1
Line A Mon Line A Mon OPM OPM Line A Mon
2 2 2 2 2
Monitor 2 Monitor 2

OSC B In OSC B In Switch 1 In Switch 1 In OSC B In
3 3 3
3 3
4 4 4
OSC A Out OSC A Out 4 4 OSC A Out
Common In
Common In Switch 1 Out Switch 1 Out
Line A In Line A Out Line A In Line A Out 17
7 7 17 Switch 2 In Switch 2 In Line B In Line B Out
8 A 8 A 6 B 5
5 5
6 6
5 B 6 5 6 Switch 2 Out Switch 2 Out 7 A 8
Line B Out Line B In Line B Out Line B In Line A Out Line A In
7 7 9:1
9:1
8 8
9 9
10 10
1:5 1:5
Σ Switch 5 In Switch 5 In Σ
11 11
12 12
18 Switch 5 Out Switch 5 Out 18
Common Out Common Out
13 13
14 14
15 15
16 16
LC LC
Ch 1 Out Ch 1 Out
LC LC
Ch 2 Out Ch 2 Out
89 89
Common In Common In
Intra-NE fiber connections at a ROADM site with single 2xOSC circuit pack
LC LC
Ch 43 In Ch 43 In
Legend Ch 43 Out Ch 43 Out
LC LC
Ch 44 Out Ch 44 Out
= Attenuator
May 2020
Figure 4-13
Intra-NE fiber connections at a ROADM site (example shows XLA and SRA)
Note : An interior SLA is supported between the WSS and the XLA.

Figure 4-14
Intra-NE fiber connections at a ROADM site (CMD44 and CMD64)

Figure 4-15
Intra-NE fiber connections at a ROADM site (CMD96)

Figure 4-16
Intra-NE fiber connections at a ROADM site using RLA/CMD64

Figure 4-17
Intra-NE fiber connections at a ROADM site using RLA/CMD44

Figure 4-18
Intra-NE fiber connections at a ROADM site using RLA/CMD64 with ESAM/SAM/SRA (SAM shown)

Figure 4-19
Intra-NE fiber connections at a ROADM site using RLA/CMD44 with ESAM/SAM/SRA (SRA shown)

Figure 4-20
20-Degree Colorless Directional with FIM5 and FIM6

Figure 4-21
Intra-NE fiber connections between a low channel count DIA and backbone OTS (up to 4 degrees
and 4 DIA banks)

Figure 4-22
Intra-NE fiber connections between a low channel count DIA and backbone OTS (up to 8 degrees)

Figure 4-23
Intra-NE fiber connections between a low channel count DIA and backbone OTS (with CMD44
connected to amplified ports of backbone WSS)

Figure 4-24
Intra-NE fiber connections between a low channel count DIA and backbone OTS (with CMD44
connected to unamplified ports of backbone WSS)

Figure 4-25
Intra-NE fiber connections between a low channel count DIA and backbone OTS using RLA

Figure 4-26
Inter-NE fiber connections between a low channel count DIA and backbone OTS with
CMD44/CMD64 connected to amplified and unamplified ports of backbone WSS

Figure 4-27
Intra-NE fiber connections at a ROADM site with XLA and SRA - DSCM placement
Figure 4-28
Intra-NE fiber connections at a ROADM site with ESAM-MLAx (example shows MLA)

Figure 4-29
Intra-NE fiber connections (CMD44 to BMD2 to WSS)

Figure 4-30
Intra-NE fiber connections (CMD44 to BMD2 to SLA to WSS)

Figure 4-31
Intra-NE fiber connections (CMD44 to Drop LIM to WSS)

Figure 4-32
Intra-NE fiber connections between a 100 GHz DIA and backbone OTS

Figure 4-33
Intra-NE fiber connections between a 50 GHz DIA (CMD44 only) and backbone OTS

Figure 4-34
Intra-NE fiber connections between a 50 GHz DIA (CMD44 and CMD64) and backbone OTS

Figure 4-35
Intra-NE fiber connections between a 50 GHz DIA (CMD44) and backbone OTS with line facing
RLA

Figure 4-36
Release 12.7
6500
Ch 01 Out
2
Ch 01 In
1
Ch 02 Out
4
Ch 02 In
Σ 12:1
3
COADM OTS
Ch 03 Out
6 Monitor Out
Ch 03 In 27
5
DIA OADM OTS
Ch 04 Out
8
Ch 04 In
7

Ch 05 Out
10
Ch 05 In
9
Ch 06 Out
12 Common In
Ch 06 In 25 WSS 50 GHz
11
Ch 07 Out
PEC: NTK553FA/FC/LA
Common Out
14 26
CCMD12
13 Ch 07 In
Monitor 1
Ch 08 Out 1
16 Monitor 2 OPM
Ch 08 In 2
15 MLA
Ch 09 Out Switch1 Out
18 PEC: NTK552BA 4
Switch1 In
CCMD12
Ch 09 In Mon 1 (B Out) 3
17 1

Switch2 Out
LB In
Ch 10 Out 25 2 Common In 6
20 Switch8 In Mon 2 (A Out) 21 Switch2 In
Ch 10 In 5
PEC: NTK508FA
26
19 Switch8 Out OSC B In
3
50 GHz SMD
8
2:8
23
22 4
9x1
Switch7 In
OSC A Out Switch3 In
Common In
7
LB Out
Ch 11 In 24
21
PEC: NTK553GA
Switch7 Out 9 Line A In Line A Out
Ch 12 Out 8 A 7 Switch4 Out
10
WSS 50 GHz
21
24 Switch6 In
Switch4 In
Σ 1:12
Ch 12 In 22 9
23 10
Colorless Channel Mux Demux

Switch6 Out
5 B 6 Switch5 Out
19
Switch5 In Line B Out Line B In 12
Switch5 In
20
Switch5 Out 11
Switch6 Out
OPM
17 14
Common Out
Switch4 In
Switch6 In
Intra-NE fiber connections at a Colorless OADM site
18 13
Switch4 Out
Dual-WSS
Σ 1:9
50 GHz 1x8
Common Out Switch7 Out
8 16
15 22
Up to 8 CCMD12s
Switch3 In Monitor 8
Ch 01 Out Switch7 In
2 16 7 15
Switch3 Out Monitor 7
Ch 01 In 6
1 Monitor 6
13
Ch 02 Out
Switch2 In 5 9:1
4 Monitor 5
14 Switch8 Out (Drop1)
Ch 02 In
Switch2 Out 18
Σ 12:1
4
3 Monitor 4
8:2
11 Switch8 In (Add1)
Ch 03 Out Switch1 In 3 17
6 Monitor Out 12
Monitor 3
Ch 03 In 27 Switch1 Out 2 Switch9 Out (Drop2)
5
Monitor 2 20
Ch 04 Out
1 Switch9 In (Add2)
Monitor 1 19
8
Ch 04 In
7
Ch 05 Out
10
Ch 05 In
9
Ch 06 Out
12 Common In
Ch 06 In 25
11
Ch 07 Out Common Out
14 26
CCMD12
13 Ch 07 In
MLA3 is 96-channel capable).
Ch 08 Out
16
Ch 08 In
15
Ch 09 Out
18
CCMD12
Ch 09 In
17
Note: Amplifier can be MLA, MLA2, or MLA3
Ch 10 Out
(MLA and MLA2 are only 88-channel capable,
20
Ch 10 In
PEC: NTK508FA
19
Ch 11 Out
22
Ch 11 In
21
Ch 12 Out
24
Σ 1:12
Ch 12 In
23
May 2020

Figure 4-37
Intra-NE fiber connections at a Colorless OADM site with CMD44 50GHz

Figure 4-38
Intra-NE fiber connections at a Colorless OADM site (up to 5 add/drop banks and 5 degrees)

Figure 4-39
Intra-NE fiber connections at a Colorless OADM site (with line facing RLA)

Figure 4-40
Intra-NE fiber connections at a ROADM site with a colorless OADM and colored DIA (with
CMD44/CMD64 connected to unamplified and amplified ports of backbone WSS)

Figure 4-41
Intra-NE fiber connections at a low channel count DIA site (non-OTS equipment)

Figure 4-42
Intra-NE fiber connections at a CDC ROADM site (CCMD8x16)

Figure 4-43
Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and CMD44 50 GHz)

Figure 4-44
Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and CMD44 100 GHz)

WSC WSC WSC WSC
2 1 2 1
Figure 4-45
Release 12.7
OSC OSC OSC OSC
2 1 2 1

OSC1 In
OSC1 In
OSC2 Out
OSC2 Out
OSC1 Out
OSC1 Out
OSC2 In
OSC2 In
2
2
1
1
2
2
1
1

MLA WSS WSS MLA
PEC: NTK552BA PEC: NTK553EA PEC: NTK553EA PEC: NTK552BA
Line B Mon 1 Monitor 1 Monitor 1 1 Line B Mon
1 1
Line A Mon OPM OPM Line A Mon
2 2 2 2
Monitor 2 Monitor 2
OSC B In Switch 1 In Switch 1 In OSC B In
3 3
3 3
4 4
OSC A Out 4 4 OSC A Out
Common In Common In

Line A In Line A Out 17 17
7 Switch 2 In Switch 2 In Line B In Line B Out
8 A 6 B 5
Intra-NE fiber connections at a DGFF site
5 5
6 6
5 B 6 Switch 2 Out Switch 2 Out 7 A 8
Line B Out Line B In Line A Out Line A In
7 7 9:1
8
Switch 4 In 8
9 Switch 4 In
Switch 5 In 9
10 Switch 5 In
1:5 Switch 6 In
1:5
10
Σ 11
Σ
Switch 6 In
Switch 7 In
11
18 12 18
Switch 7 In
Common Out Switch 8 In Common Out
12
13 Switch 8 In
Switch 9 In
13
Switch 9 In
Legend
= DSCM
= Attenuator
May 2020
Figure 4-46
Intra-NE fiber connections at a DGFF site (RLA)

Figure 4-47
Intra-NE fiber connections at a DGFF site (RLA with SAM/ESAM/SRA)

Procedure 4-2
Adding a new CMD44, CMD64, CMD16, CMD24,
CMD96, or BMD2
Use this procedure to add a new 100GHz CMD44/eCMD44, 50GHz CMD44,
CMD64, CMD16, CMD24, CMD96, or Broadband Mux/Demux (BMD2). For
more information about the modules, refer to Photonic Equipment,
323-1851-102.6.
Note: In the current release, software support for the CMD16 and CMD24
modules is limited to Inventory only (no Equipment/facility, topology, or
control support).
If a shelf is equipped with an access panel that supports external slots and a
shelf processor that supports interfacing with external slots, a CMD44,
CMD64, CMD16, CMD24, CMD96, or BMD2 module is automatically
provisioned to the external slot when physically connected to the access
panel. The external slot numbers depend on the shelf type and SP type. Refer
to Common Equipment, 323-1851-102.1. Otherwise, you must manually
provision the CMD44, CMD64, CMD16, CMD24, CMD96, or BMD2 module to
one of the virtual slots. The virtual slots are: slots 91 to 99 on a 2-slot
(NTK503LA variant), 6500-7 packet-optical, 7-slot, or 14-slot shelf, and slots
63 to 82 on a 32-slot shelf. The virtual slots are always available whether the
access panel supports external slots or not.
This procedure also applies to remote CMD44 modules considering the

following:
• The remote CMD44 is manually provisioned at the local site but is
physically located at a remote site.
• CMD44 Tx and Rx adjacencies must be provisioned (just as in the case
where the CMD44 is local).
• Each direction can have the CMD44 physically located either at the local
site or at the remote site but not at both sites.
• Data communications to the remote 6500 service shelf can be achieved
using a direct DCN connection to the shelf’s COLAN port or using a
channel’s GCC0/DCC.
For more information on Remote CMD44, refer to 6500 Packet-Optical

Platform Photonic Layer Guide, NTRN15DA.


Adding a new CMD44, CMD64, CMD16, CMD24, CMD96, or BMD2
CAUTION
DANGER
Risk of injury
CAUTION
Prerequisites
• You require an optical power meter.
• You require an LC to LC patch cord.
• You require RJ-45 straight-through cables NTTC09BME6 (to connect
CMD44, CMD64, CMD16, CMD24, CMD96, or BMD2 modules to the
access panel)
• You require a user account with a UPC level of 3 or higher.
• Make sure that the power and wavelength have been provisioned on the
transmitter that you are testing with.
Step Action
1 Install the 100GHz CMD44/eCMD44, 50GHz CMD44/eCMD44, CMD64,

CMD16, CMD24, CMD96, or BMD2 module as indicated in the Installation
technical publication specific to the respective 6500 shelf type.
The CMD44 and CMD64 are 2U rack modules. The CMD16, CMD24, and
BMD2 are a 1U rack modules. The CMD96 is a 3U rack module. All are
external modules.


Step Action

If the shelf Then
is equipped with an access Using a straight-through RJ-45 cable, connect
panel that supports the CMD44, CMD64, CMD16, CMD24,
external slots and a shelf CMD96, or BMD2 to an external slot (located
processor that supports on the top left corner of the access panel). The
interfacing with external CMD44, CMD64, CMD16, CMD24, CMD96, or
slots BMD2 auto-provisions. Go to step 7.
otherwise if the module is a CMD44, CMD64, CMD96, or
BMD2, go to step 3
if the module is a CMD16 or CMD24, go to
step 7 (manual provisioning of these modules
is not supported)
Provisioning CMD44, CMD64, CMD96, or BMD2 manually

3 In Site Manager, select Configuration -> Equipment & Facility
Provisioning.
4 Click on the Add button.
5 In the Add Equipment dialog box, enter the following data as indicated in the
EDP/IDP:
• Type
• Provisioned PEC
• Slot
• State (IS/OOS)
6 Click on the OK button.
Testing the CMD44, CMD64, CMD16, CMD24, CMD96, or BMD2
7 Select one of the transmitters to be connected to the CMD44, CMD16,
CMD24, CMD96, or CMD64. Use a power meter or the power monitoring
function (if available) on the subtending transmitting equipment to determine
the transmitter power (record the transmitter power).
8 Connect the transmitter of the subtending transmitting equipment to the
channel input port of the CMD44, CMD16, CMD24, CMD96, or CMD64
corresponding to the transmitter center frequency.
9 Ensure that this is the only transmitter connected to the CMD44, CMD16,
CMD24, CMD96, or CMD64. All other transmitters must be disconnected
from the CMD44, CMD16, CMD24, CMD96, or CMD64.
10 Use a power meter and measure the power level at the Common Out port of
the CMD44 (port 90), CMD16, CMD24, CMD96 (port 194), or the CMD64
(port 130). Record this value.


Step Action
11 Calculate the loss between the Channel In port and the Common Out port
using the values recorded in step 7 and in step 10. If the loss is greater than
6 dB (for 100GHz CMD44/eCMD44), 7 dB (for 50GHz CMD44), 7.5 dB (for
50GHz eCMD44), 4.9 dB (CMD16), 5.2 dB (CMD24), 7 dB (CMD96), or
6.5 dB (for CMD64), clean and verify all optical patch fibers and connectors.
If you are unable to increase the power, contact your next level of support to
determine if any components require replacement.
If Then go to
BMD2 present step 13
otherwise step 16
13 Use a power meter and measure the power level at the Common Out port of
the BMD2 (port 2).
Record this value.
14 Calculate the loss between the Channel In port and the Common Out port of
the BMD2 using the values recorded in step 10 and in step 13. If the loss is
greater than 10.8 dB (with 50GHz CMD44), clean and verify all optical patch
fibers and connectors. If you are unable to increase the power, contact your
next level of support to determine if any components require replacement.
15 Place a loopback between Common Out (port 2) and the Common In (port 1)
of the BMD2 using an LC to LC patch cord. Go to step 17.
16 Place a loopback between the:
• Common Out (port 90) and the Common In (port 89) of the CMD44
or
or
• Common Out port and the Common In port of the CMD16
or
• Common Out port and the Common In port of the CMD24
or
17 Using a power meter, measure the power present on the CMD44, CMD16,
CMD24, CMD96, CMD64, or BMD2 output port that corresponds to the
wavelength being tested.


Step Action

If Then go to
BMD2 present step 19
otherwise step 21
19 Calculate the loss between the BMD2 common input and the BMD2 output
port.
20 If the measured loss is higher than 3.8 dB, try to fix the problem by cleaning
and inspecting the optical connectors. If this is not sufficient, replace the
BMD2. Refer to the appropriate procedure in Fault Management - Module
21 Calculate the loss between the common input of the CMD44, CMD16,
CMD24, CMD96, CMD64, or BMD2 and the CMD44, CMD16, CMD24,
CMD96, or CMD64 channel output port.
22 If the loss is greater than 6 dB (for 100GHz CMD44 only), or 6.6 dB (for
100GHz eCMD44), 7 dB (for 50GHz CMD44 only), 7.5 dB (for 50GHz
eCMD44 only), 4.9 dB (CMD16), 5.2 dB (CMD24), 7.6 dB (CMD96), 7.1 dB
(for CMD64 only), 10.5dB (for 50GHz CMD44 and BMD2), or 11 dB (for
50GHz eCMD44 and BMD2), try to fix the problem by cleaning and inspecting
the optical connectors. If this is not sufficient, replace the module. Refer to the
appropriate procedure in Fault Management - Module Replacement,
323-1851-545.
23 Remove the optical patch cord between the Common Out and the Common
In ports.
24 Disconnect the transmitter from the CMD44, CMD16, CMD24, CMD96, or
CMD64 port.
—end—

Procedure 4-3
Adding a new OMD4 or OMX
Use this procedure to add a new OMD4 or OMX. For more information about
the OMD4 and OMX modules, refer to Common Equipment, 323-1851-102.1.
If a shelf is equipped with an access panel that supports external slots and a
shelf processor that supports interfacing with external slots, an OMD4 or OMX
module is automatically provisioned to the external slot when physically
connected to the access panel. The external slot numbers depend on the shelf
type and SP type. Refer to Common Equipment, 323-1851-102.1. Otherwise,
you must manually provision the OMD4 or OMX module to one of the virtual
slots. The virtual slots are: slots 91 to 99 on a 2-slot (NTK503LA variant),
6500-7 packet-optical, 7-slot, or 14-slot shelf, and slots 63 to 82 on a 32-slot
shelf. The virtual slots are always available whether the access panel supports
external slots or not.
CAUTION
DANGER
Risk of injury
CAUTION
Prerequisites
• You require an LC to LC patch cord for OMD4, or an SC to SC or LC to SC
patch cord for OMX.


• You require RJ-45 straight-through cables NTTC09BME6 (to connect

OMD4 or OMX modules to the access panel)
• Make sure that the power and wavelength have been provisioned on the
transmitter that you are testing with.
Step Action
1 Install the OMD4 or OMX module as indicated in the Installation technical

publication specific to the respective 6500 shelf type.
If the shelf Then
is equipped with an access panel Using a straight-through RJ-45 cable,
that supports external slots and a connect the CMD44 or BMD2 to an
shelf processor that supports external slot (located on the top left
interfacing with external slots corner of the access panel). The OMD4
or OMX auto-provisions. Go to step 7.
Provisioning OMD4 or OMX manually

3 In Site Manager, select Configuration -> Equipment & Facility
Provisioning.
4 Click on the Add button.
5 In the Add Equipment dialog box, enter the following data as indicated in the
EDP/IDP:
• Type
• Provisioned PEC
• Slot
• State (IS/OOS)
Testing the OMD4 or OMX
7 Select one of the transmitters to be connected to the OMD4/OMX. Use a
power meter or the power monitoring function (if available) on the subtending
transmitting equipment to determine the transmitter power (record the
transmitter power).
8 Connect the transmitter to the appropriate OMD4/OMX channel input port.
9 Ensure that this is the only transmitter connected to the OMD4/OMX. All other
transmitters must be disconnected from the OMD4/OMX.
10 Use a power meter and measure the power level at the Common Out/OTS
Out (port 2) of the OMD4/OMX. Record this value.


Step Action
11 Calculate the loss between the Channel In port and the Common Out/OTS
Out port using the values recorded in step 7 and in step 10. If the loss is
greater than 2.5 dB for OMD4 or the Max Mux loss in Table 4-2 on page 4-93
for OMX, clean and verify all optical patch fibers and connectors. If you are
unable to increase the power, contact your next level of support to determine
if any components require replacement.
12 Place a loopback between the Common Out/OTS Out (port 2) and the
Common In/OTS In (port 1) of the OMD4/OMX using an LC to LC patch cord
for OMD4 or an SC to SC patch cord for OMX.
13 Using a power meter, measure the power present on the OMD4/OMX output
port that corresponds to the wavelength being tested.
14 Calculate the loss between the common input and the OMD4/OMX channel
output port.
15 If the loss is greater than 2.5 dB for OMD4 or the Max Demux loss in Table
4-2 on page 4-93 for OMX, try to fix the problem by cleaning and inspecting
the optical connectors. If this is not sufficient, replace the module. Refer to the
323-1851-545.
16 Remove the optical patch cord between port 2 and port 1.
17 Disconnect the transmitter from the OMD4/OMX.
18 Select one of the transmitters to be connected to the Upgrade/THRU port of
the OMD4/OMX. Use a power meter or the power monitoring function (if
available) on the subtending transmitting equipment to determine the
transmitter power (record the transmitter power).
19 Connect the transmitter to the Upgrade/THRU In port of the OMD4/OMX
(port 11 on OMD4 and 4-channel OMX, port 35 on 16-channel OMX).
20 Ensure that this is the only transmitter connected to the OMD4/OMX. All other
transmitters must be disconnected from the OMD4/OMX.
21 Use a power meter and measure the power level at the Common Out/OTS
Out (port 2) of the OMD4/OMX. Record this value.
22 Calculate the loss between the Upgrade/THRU In port and the Common Out
port using the values recorded in step 18 and in step 21. If the loss is greater
than 1.1 dB for OMD4 or the Max Pass-through/upgrade loss in Table 4-2 on
page 4-93 for OMX, clean and verify all optical patch fibers and connectors.
If you are unable to increase the power, contact your next level of support to
23 Place a loopback between the Common Out/OTS Out (port 2) and the
Common In/OTS In (port 1) of the OMD4/OMX using an LC to LC patch cord
for OMD4 or an SC to SC patch cord for OMX.


Step Action
24 Using a power meter, measure the power present on the OMD4/OMX

Upgrade/THRU Out port (port 12 on OMD4 and 4-channel OMX, port 36 on
16-channel OMX).
25 Calculate the loss between the common input and the OMD4/OMX
Upgrade/THRU Out port.
26 If the loss is greater than 0.75 dB for OMD4 or the Max Pass-through/upgrade
loss in Table 4-2 on page 4-93 for OMX, try to fix the problem by cleaning and
inspecting the optical connectors. If this is not sufficient, replace the module.
Refer to the appropriate procedure in Fault Management - Module
27 Remove the optical patch cord between port 2 and port 1.
28 Disconnect the transmitter from the OMD4/OMX.
—end—
Table 4-2
OMX maximum dB loss
Module Max Mux Max Demux Max

loss (dB) loss (dB) Pass-through/upgrade
loss (dB)
4 CH + Fiber Manager 4.5 4.9 1.2
4 CH Enhanced 2.8 3.1 1.0
4 CH 100 GHz 3.3 3.6 1.1
16 CH DWDM C-band 4.5 4.5 1.1
16 CH DWDM L-band 4.1 4.1 NA
16 CH DWDM 100 GHz C-band 5.1 5.1 1.2

Procedure 4-4
Adding a new SCMD4
Use this procedure to add and test a new SCMD4 to an existing 6500
Packet-Optical Platform network.
CAUTION
Risk of service interruption
When a new SCMD4 is added to a thin OADM site, traffic
passing through the thin OADM site will be lost when the
upgrade ports are rerouted.
Prerequisites
CAUTION
DANGER
Risk of injury
CAUTION
Step Action
1 Insert the new SCMD4 into the shelf. Equipment and facilities will
auto-provision if auto-equipping is enabled.


Adding a new SCMD4
Step Action
Testing the new SCMD4

2 Select one of the transmitters to be connected to the new SCMD4. Make sure
the wavelength of the transmitter matches the wavelength of the SCMD4 port
it is to be connected to.
3 Use a power meter set correctly for the wavelength or the power monitoring
function (if available) on the subtending transmitting equipment to determine
the transmitter power. Record the transmitter power.
4 Connect the transmitter to the appropriate SCMD4 channel input port.
5 Ensure that this is the only transmitter connected to the SCMD4. All other
transmitters must be disconnected from the SCMD4.
6 In the Site Manager interface, select Configuration −> Equipment & Facility
Provisioning.
7 Select the VOA facility that corresponds to the SCMD4 channel you are
testing.
The SCMD4 ingress VOA AID used in the Site Manager interface is:
VOA-<shelf>-<SCMD4 slot>-<port>.
8 Click Edit.
9 Set the Target Loss for the VOA to 0 dB.
10 Click OK.
11 Use a power meter and measure the power level at the Common Out (port 2)
of the SCMD4. Record this value.
12 Calculate the loss between the Channel In port and the Common Out port
using the values recorded in step 3 and in step 11. If the loss is greater than
4.6 dB, clean and verify all optical patch fibers and connectors. If you are
unable to increase the power, contact your next level of support to determine
if any components require replacement.
13 Place a loopback between the Common Out and the Common In ports of the
SCMD4 using an LC-to-LC patch cord.
14 Set the demux VOA on the SCMD4 to 0 dB. The demux VOA is located on
port 1.
15 Using a power meter, measure the power present on the SCMD4 channel
output port that corresponds to the wavelength being tested.


Adding a new SCMD4
Step Action
16 Calculate the loss between the common input and the SCMD4 channel
output port.
17 If the measured loss is higher than 5.4 dB, try to fix the problem by cleaning
and inspecting the optical connectors and optical patch fibers. If this is not
sufficient, replace the SCMD4. Refer to the appropriate procedure in Fault
Management - Module Replacement, 323-1851-545.
18 Remove the optical patch cord between the Common Out and the Common
In ports.
19 Disconnect the transmitter from the SCMD4 port.
20 Reset the Target Loss of the ingress VOA of the tested wavelength to 15 dB.
21 Reset the Target Loss of the demux VOA back to 15 dB. The demux VOA is
located on port 1.
Connecting the new SCMD4 to other equipment
22 Optically connect the SCMD4 to other equipment as indicated in the
EDP/IDP.
CAUTION
Risk of service interruption
If the SCMD4 is being added at a Thin OADM node,
traffic passing through the node will be lost when the
upgrade ports are rerouted. If the SCMD4 is being
added at a Thin Terminal or a Thin OADM node, traffic
dropping at the node may be lost when the upgrade
ports are rerouted.
23 Edit the OTS to include the new SCMD4. Refer to the “Editing an OTS
instance” procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310. For a Thin OADM node, edit both OTSs.
24 Provision the SCMD4 Cascading Order according to the EDP/IDP. For
details, see the “Provisioning the SCMD cascading order” procedure in Part 2
of Configuration - Provisioning and Operating, 323-1851-310.


Adding a new SCMD4
Step Action
25 For a thin OADM node, edit the inter-OTS adjacencies for the pass-through
traffic if the configuration has changed.
• Select Configuration -> Equipment & Facility Provisioning.
• In the Equipment table, select the innermost SCMD4 (the one furthest
from the line facing circuit pack), or the line-facing circuit pack if the
SCMD4 cascade is empty (no SCMD4).
• Select ADJ in the Facility Type drop down list.
• Select the adjacency that corresponds to the port where the
pass-through traffic is handed off to the other OTS.
This port is the Upgrade Out (port 12) of the innermost SCMD4 or Line A
OUT (port 7) of the line-facing circuit pack if the SCMD4 cascade is
empty (no SCMD4).
Note: Adjacency format = ADJ-<shelf>-<slot>-<port>
• Click Edit in the Facility area.
• Set the Adjacency type to CMD (if the other OTS SCMD4 cascade is not
empty) or LIM (if the other OTS SCMD4 cascade is empty).
• Enter the Expected Far End Address and the Expected Far End Address
Format as described in the EDP/IDP.
The Expected Far End Address must point to the input port of the
innermost SCMD4 of the other OTS (port 11) or to the Line B In (port 6)
of the line-facing circuit pack of the other OTS if its SCMD4 cascade is
empty (no SCMD4).
• Click OK.
• Repeat the above substeps for the other OTS.
26 At each of the 2 DOC nodes controlling the channels passing through or
add/drop at the node where the SCMD4 was added, perform a DOC
re-optimization followed by a DOC reset TCA baseline operation. Refer to the
“Re-optimizing channels” and “Resetting TCA baselines” procedures in
Part 2 of Configuration - Provisioning and Operating, 323-1851-310.
—end—

Procedure 4-5
Adding a new CCMD12
Use this procedure to add and test a new CCMD12 to an existing 6500
Packet-Optical Platform network.
Note: This procedure does not apply to low channel count DIA ROADM
configurations (only one CCMD12 is supported per DIA).
Prerequisites
• You must know how to retrieve performance monitoring data. Refer to the
“Retrieving performance monitoring data” procedure in Fault Management
- Performance Monitoring, 323-1851-520.
CAUTION
DANGER
Risk of injury
CAUTION
Step Action
1 Insert the new CCMD12 into the shelf. Equipment and facilities will
auto-provision if auto-equipping is enabled.
Testing the new CCMD12
2 Select one of the transmitters to be connected to the new CCMD12. Edit the
OTMn facility of the transmitter to set the Tx power to maximum and Tx
wavelength to 1550.12 nm.


Adding a new CCMD12
Step Action
3 Connect the transmitter to the appropriate CCMD12 Ch In port. Connect the

receiver to the appropriate CCMD12 Ch Out port.
Ensure that this is the only transmitter and receiver connected to the
CCMD12. All other transmitters and receivers must be disconnected from the
CCMD12.
4 Place a loopback between the CCMD12 Common In (port 25) and Common
Out (port 26) using an LC-to-LC patch cord with a 20 dB pad.
5 Retrieve the untimed OPT-OCH PM value for the OTMn facility of the
transmitter, in the transmit direction.
6 Retrieve the untimed OPR-OTS PM value for the OPTMON facility of the
CCMD12 Ch In port.
The fiber loss = step 5 value - step 6 value, which must be less than 1 dB. If
it is not, clean the connectors and verify the optical patch fiber between the
transmitter and the CCMD12 Ch In.
7 Retrieve the untimed OPIN-OTS PM value for the AMP facility of the CCMD12
Common In (port 25).
The loss = step 6 value - step 7 value, which must be less than 14.4 dB. If it
is not, clean the connectors and verify the loopback patch cord. If you are
unable to reduce the loss, contact your next level of support to determine if
any components require replacement.
8 With an optical power meter, measure the power level at the CCMD12
Monitor Out (port 27). This value must be greater than or equal to step 7 value
+ 9 dB.
9 Retrieve the untimed OPR-OCH PM value for the OTMn facility of the receiver
connected to the CCMD12 Ch Out, in the Receive direction.
The gain = step 9 value - step 7 value, which must be greater than 5.6 dB. If
CCMD12 Ch Out and the receiver. If you are unable to increase the gain,
contact your next level of support to determine if any components require
replacement.
10 Remove the optical patch cord between the CCMD12 Common Out and the
Common In ports.
Connecting the new CCMD12 to the SMD
11 Connect the Common Out port of the CCMD12 to the Switch In port of the
SMD as indicated in the EDP/IDP.
SMD Switch In port.
The gain = step 12 value - step 5 value, which must be greater than 5.6 dB.
If it is not, clean the connectors and verify the optical patch fiber between the
SMD Switch In port and the CCMD12 Common Out port.


Adding a new CCMD12
Step Action
13 Connect the CCMD12 Common In port to the corresponding Switch Out port
of the SMD as indicated in the EDP/IDP.
14 Connect the CCMD12 Monitor Out port to the corresponding Monitor port of
the SMD as indicated in the EDP/IDP.
15 Edit the OTS to include the new CCMD12. Refer to the “Editing an OTS
instance” procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310.
16 Disconnect the transmitter and receiver from the CCMD12 Ch In and Ch Out
ports.
17 Edit the OTMn facility of the transmitter to set the Tx power to its default value
and Tx wavelength to 0 nm.
—end—

Procedure 4-6
Adding a new CCMD8x16 or a CXM C-Band Type 1
Use this procedure to add and test a new CCMD8x16 or a CXM to an existing
6500 Packet-Optical Platform network. For more information about the
CCMD8x16 and the CXM C-Band Type 1, refer to Photonics Equipment,
323-1851-102.6.
The CCMD8x16 and the CXM are connected to Fiber Interconnect Modules
(FIM). Keep in mind the following information regarding the FIMs. For more
information, see the Photonic passive modules table in Planning - Ordering
Information, 323-1851-151.
• FIM Type 1 is shipped with the following equipment pre-installed:
— dust caps on MPO ports 1 to 4 (WSS1)
— MPO Loopback (APC, SM, 12 Fiber) modules in all the other MPO port
positions
— Duplex LC Loopback (SM) modules in each of the duplex LC
connector positions

positions
• In addition to providing the optical loopback operation required by

applications that use the FIM, the loopback modules act as dust caps for
the optical ports. Do not remove the loopback modules except as part of
a fiber installation procedure. The FIM tray assembly includes a bag of
dust caps that must be put on any loopback connector that is being
removed and saved for future use.
Prerequisites
If you are adding a CXM C-Band Type 1 and want to test the MPO cable
between the CCMD8x16 UPG CXM port and the CXM C-Band Type 1 UPG
CCMD port, you must use a transponder.


CAUTION
DANGER
Risk of injury
CAUTION
Step Action
1 Make sure there are no Cable Trace Compromised alarms, Adjacency Far
End Not Discovered alarms or Adjacency Mismatch alarms in the TID where
you are installing the new CCMD8x16 or the CXM C-Band Type 1. See Fault
Management - Alarm Clearing, 323-1851-543 for the procedures on how to
clear the respective alarms.
2 Insert the new equipment:
• CCMD8x16 into the shelf (see the procedure on inserting or removing
circuit packs in the Installation technical publication specific to the
respective 6500 shelf type)
• CXM C-Band Type 1 into the host CCMD8x16 circuit pack (see the
procedure on installing and removing pluggable modules in the
Installation technical publication specific to the respective 6500 shelf
type)
Equipment and facilities will auto-provision if auto-equipping is enabled.

3 Make sure that the TID slot sequence provisioning is complete. For details,
see the procedure on editing TID slot sequences in Part 2 of Configuration -


Step Action
4 Connect the equipment to the FIM per the EDP/IDP:

• The Common A port of the CCMD8x16 should be connected to a CMD
port labeled with an A on the FIM.
• The Common B port of the CXM C-Band Type 1 should be connected to
a CMD port labeled with a B on the FIM.
The CDC equipment uses MPO cables and connectors. For steps to:
CAUTION
for any reason.

connection.
5 If you are adding a CXM C-Band Type 1, connect the jumper cable between
the UPG CXM port on the CCMD8x16 and the UPG CCMD port on the CXM.
6 Make sure there are no Adjacency Far End Not Discovered alarms or
Adjacency Mismatch alarms. See Fault Management - Alarm Clearing,
323-1851-543 for the procedures on how to clear the respective alarms.
7 After the last fibering has been completed and the TID slot sequence has
been completed, if the Dark Fiber Loss Management system parameter is
enabled in the Node Information tab of Site Manager, the network element
starts verifying all the subfibers within the MPO ports automatically. (For
details on setting the parameter, see the procedure on editing the nodal
system parameters in Administration and Security, 323-1851-301.)
Make sure that you wait for approximately 5 minutes after the last fibering was
completed.
8 In Site Manager, display the connection validation results under the Validation
Summary tab.


Step Action
9 If any of the subfibers within the MPO cables is dirty or bent, a High Fiber
Loss error is displayed. Disconnect the cable, clean and inspect the
connectors, then reconnect the cable. Replace the cable, if necessary. Note
that the root cause of the High Fiber Loss alarm on a given adjacency port
can include the near end fiber, far end fiber, loopback connector, or the FIM.
For details, see Fault Management - Alarm Clearing, 323-1851-543.
10 If there is a problem with a loopback connector, in Site Manager select
Configuration, then Shelf Level View, then right-click on the MPO port and
select Show Fiber Topology to determine which loopback connector.
Disconnect the loopback, clean and inspect the connectors, then reconnect
the loopback.
If you have added Then
a new CCMD8x16 you have completed this
procedure
a CXM C-Band Type 1 and you want to go to step 12
test the jumper MPO subfibers between
ports 34 and 35 of the CCMD8x16
12 If the configuration is set up with ROADM OTSs and you want to test the
jumper MPO subfibers between ports 34 and 35 of the CCMD8x16, you will
use a transponder. Select one of the transponders to be connected to the new
CCMD8x16.
13 Connect the transmitter to the appropriate CCMD8x16 In port per the
EDP/IDP and connect the receiver to the appropriate CCMD8x16 Out port
per the EDP/IDP.
Ensure that this is the only transmitter and receiver pair connected to the
CCMD8x16. All other transmitters and receivers must be disconnected from
the CCMD8x16.
14 Perform a manual loopback test to exercise the jumper subfibers. See the
procedure on performing optical loopback testing in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310. If the test fails, disconnect the
cable, clean and inspect the connectors, then reconnect the cable. Replace
the cable, if necessary.
—end—

Procedure 4-7
Testing ROADM channel access continuity
Use this procedure to test channel access continuity on a WSS based node
where light from transmitting subtending equipment is available. This test
verifies the optical continuity and checks for reflection-related problems. This
procedure does not optimize the channels for traffic.
In this procedure, CMD refers to the OMDF4, OMDF8, OMD4, CMD44,

CMD64, or the CCMD12 unless specified otherwise. The OMDF4 and
OMDF8 may be connected to the BS5.
See “Testing a CDC ROADM configuration” on page 4-133 for CDC ROADM
sites and “Testing DGFF nodes” on page 4-286 for DGFF site testing.
Prerequisites
• This procedure allows you to perform optical continuity testing through all
the equipment associated with one ROADM OTS. Full traffic continuity
testing can proceed only after the system is complete. It is recommended
that you perform the continuity test with at least one service layer source
for each installed CMD.
Note: The ROADM OTS must be defined before performing this
procedure.
• If no transmitter is available, you cannot perform this procedure.

• Perform this procedure only after you have completed Procedure 2-1,
“Powering up a new network element and connecting a craft computer”
through Procedure 4-1, “Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. You must first
complete the NE commissioning and fibering before performing this
procedure.


Step Action
• The fibers that are used in the following steps to connect to subtending
client equipment must be verified to be in good working order prior to use.
It is very important that client fibers are cleaned and scoped prior to being
connected. See Installation - General Information, 323-1851-201.0, for the
cleaning and inspection procedures.
CAUTION
DANGER
Risk of injury
CAUTION



Figure 4-48
Overview of ROADM channel access continuity testing and fibering steps (configuration uses
LIM)
Dir. 1 OPM connections

17 20
24
B 28 A
12
A 33 B
32
18 Dir. 2
2 40
29
37
BMD2 OR BS5 DIA OR DIA
COADM
Power 10 36
meter
Tx Rx Tx Rx
Tx Rx
Figure 4-49
SRA/ESAM/SAM+XLA)
Dir. 1
OPM connections
19 20
24
B B 28 A B
12
A A 33 A
32 B
19
40
2
29
37 Dir. 2
COADM
Power 10 36
meter
Tx Rx Tx Rx
Tx Rx


Figure 4-50
ESAM+MLAx)
Dir. 1
OPM connections
17 20
24
B B 28 A B
12
A A 33 A
32 B
18
40
2
29
37 Dir. 2
COADM
Power 10 36
meter
Tx Rx Tx Rx
Tx Rx
Figure 4-51
RLA)
Dir. 1
20
OPM
19 connections
24
B 28 A
12
A 33 B
19
2
29
37 Dir. 2
Power 10 36
meter
Tx Rx


Figure 4-52
RLA and ESAM/SAM/SRA)
Dir. 1
19
B B 28 A B
12
A A 33 A
B
19
2
29
37 Dir. 2
Power 10 36
meter
Tx Rx
Step Action
1 Launch Site Manager and log in as an admin level user.

Testing OSC connectivity
Note: The OSC ports in this procedure could be on the SPAP-2 w/2xOSC
circuit pack, on the 2xOSC circuit pack, or the SRA, ESAM, or SAM circuit
packs as applicable.
2 Using patch cords that are known to be in good condition, put an optical
loopback with no padding (see Note) between Line B Out (port 5) and Line A
In (port 8) of the line facing circuit pack connected to the OSC-1 you are
testing.
Note: If using high power OSC SFPs (NT592NR or NTK592NV), it is
recommended to use a 5 dB pad between Line B Out (port 5) and Line A In
(port 8) of the line facing circuit pack to prevent erroneous readings.
3 In the Equipment & Facility Provisioning window, select the P155M
equipment associated with the OSC-1, then the OSC facility. Record the Tx
Power parameter.


Step Action
4 In the Performance Monitoring window, select the OPTMON type and the
facility for OSC Out (port 4) on the line facing circuit pack connected to the
OSC-1 you are testing (OPTMON-<shelf>-<slot>-4). Record the OPR-OTS
Untimed parameter.
5 Calculate the coupler loss for the line facing circuit pack:
Coupler loss = <OSC output power (dBm) read in step 3> - <OSC Out power
(dBm) read in step 4>
The calculated coupler loss should be less than 5 dB (SRA) or 3.5 dB (other
line facing circuit packs).
If the OSC or loopback fibers are dirty, crossed or pinched, the calculated
coupler loss will be much greater than 5 dB (SRA) or 3.5 dB (other line facing
circuit packs). You must rectify the situation before you continue.
6 Using an optical power meter, measure the power going to the OSC In port
from the OSC Out (port 4). This value should be roughly the same as the
power read in step 4.
7 Remove the loopback you put in step 2.
8 Repeat step 2 to step 7 for the other OSC-1 (dual 2xOSC configuration) or
the OSC-2 (single 2xOSC configuration).
Setting up for the testing
9 See the following figures for examples of ROADM node testing. Labeled
numbers in these figures identify the steps to follow.
• Figure 4-48 on page 4-107 - configuration uses LIM
• Figure 4-49 on page 4-107 - configuration uses SRA/ESAM/SAM+XLA
• Figure 4-50 on page 4-108 - configuration uses ESAM+MLAx
• Figure 4-51 on page 4-108 - configuration uses RLA
• Figure 4-52 on page 4-109 - configuration uses RLA + SRA/ESAM/SAM


Step Action
10 Select the CMD you want to test:

• Select one of the transmitters to be connected to the selected CMD.
• For the ADJ-TX facility of the CMD port to be connected, set the
transmitter type to match the transmitter you are turning up.
• If you can adjust the output power of the transmitter, set it to maximum.
• Set a power meter to measure the transmitter output power and connect
the transmitter to the appropriate CMD port.
The transmitter wavelength should match the CMD port you are using
(that is, the transmitter must be tuned to correct wavelength).
Note: No other transmitter should be connected to the network element at
this point. Make sure the receiver of the testing wavelength is not connected
to the circuit pack so as not to overload receiver port while testing.
11 If you are testing with DIA or Colorless OADM:
• Verify that fibering at this site is in place. See Procedure 4-1, “Connecting
intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM sites”.
• Make sure the DIA or Colorless OADM configuration is tested. See
Procedure 4-10, “Testing a DIA configuration”, Procedure 4-11, “Testing
a low channel count DIA configuration”, or Procedure 4-12, “Testing a
Colorless OADM configuration”.
• Create an optical cross-connect for the channel from the DIA or Colorless
OADM to the line facing circuit pack you are testing. See the “Adding a
Photonic cross-connect” procedure in Configuration - Connections
loopback with the appropriate padding between the line facing circuit pack
Line B Out (port 5) and the line facing circuit pack Line A In (port 8).
The amount of padding depends on the type of the line facing circuit pack.
13 Select the amount of padding based on circuit pack type.
If the line facing circuit pack is Then use
LIM 0 dB
SLA 10 dB
MLA, MLA2, MLA2 w/VOA, or MLA3 20 dB
SRA/ESAM/SAM 20 dB
RLA 20 dB


Step Action
14 Select Configuration -> Equipment & Facility Provisioning. Select the

appropriate photonic shelf from the Shelf drop-down list and select the
ROADM WSSOPM or RLA in the equipment table.
• Create a CHC facility:
— Set the Minimum Frequency and the Maximum Frequency to those
corresponding to the wavelength that you are testing (step 10).
— Set the Opaque state to “No”.
— Set the Switch selector to the port to which the Drop LIM, CMD,
BMD2, or DIA is connected.
— Ensure that the CHC mode is Open Loop Loss.
For details, see the procedure on adding a CHC facility in Part 1 of
• Create a NMCC facility:
— Set the Center Frequency to that corresponding to the wavelength
that you are testing.
— Set the Spectral Width to “37.5 GHz” (or “59.0 GHz” for WaveLogic
Ai transponders in 56 GBaud mode).
— Set the Target Loss to “0 dB”.
For details, see the procedure on adding a NMCC facility in Part 1 of
15 If you are testing with DIA, select the DIA WSSOPM in the equipment table.
• Select the CHC in the Facility drop down list.
• Select the wavelength of the transmitter chosen in step 10.
• Set the Opaque state to “No”.
• Set the Switch selector to the port to which the ROADM WSS is
connected.
• Set the Target Loss to 0 dB.
16 If you are testing with DIA and COADM, select the SMD in the equipment
table.
• Select the required CHC facility in the mux direction and for the
wavelength that you are testing.
• Set the Primary state to “OOS”.
• Set the Opaque state to “No”.
• Set the Switch selector to the port to which the CCMD12 Common Out is
connected.
• Set the Target Loss to 0 dB.


Step Action
17 If the line facing circuit pack is an MLA, MLA2, MLA2 w/VOA, or MLA3,
perform this step on the line facing circuit pack.
If your configuration uses ESAM-MLAx, perform this step on the MLAx.
a. Edit the Line B AMP facility (AMP-<shelf>-<slot>-6) to set the target gain
to 17 dB:
— In the Equipment & Facility Provisioning application, select the
appropriate photonic shelf from the Shelf drop-down list and select
the LIM in the equipment table.
— Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-6 in the facility table.
— Click Edit.
— In the Edit AMP facility dialog, enter 17.00 in the Target Gain field
then click OK.
b. Verify the ORL at Line B output:
— In the Performance Monitoring application, select the appropriate
photonic shelf from the Shelf drop-down list.
— For non-MLA2 w/VOA, select the AMP Type and the facility
AMP-<shelf>-<slot>-6 from the Facility drop down list.
— For MLA2 w/VOA, select the VOA Type and the facility
VOA-<shelf>-<slot>-5 from the Facility drop down list.
— Click Start Monitoring.
— In the PM table, read the Untimed ORL-OTS value.
— If the value is lower than 28 dB, clean all the optical connections from
the Line B output port to the input of the pad. When DSCMs are used
and the DSCM location is at the head end of the span (collocated with
the amplifier being commissioned), the minimum ORL threshold to
meet or exceed is 24 dB.


Step Action
18 If the line facing circuit pack is an MLA, MLA2, MLA2 w/VOA, MLA3, or an
SLA, perform this step on the line facing circuit pack.
If your configuration uses ESAM-MLAx, perform this step on the MLAx.
a. Edit the Line A AMP facility (AMP-<shelf>-<slot>-8) to set the target gain
to 20 dB:
— Click Edit.
then click OK.
b. Verify the ORL at Line A output:
— If the value is lower than 28 dB (24 dB when a DSCM is placed after
the amplifier output), clean all the optical connections from the Line
A output port to the input of the CMD.
19 If an XLA or RLA is present, perform the following on the XLA or RLA:

a. Edit the Line B AMP facility (AMP-<shelf>-<slot>-6 for XLA,
AMP-<shelf>-<slot>-5 for RLA) to set the target gain to 20 dB and the
Gain Mode to HIGH (XLA only) (You will be instructed to set the XLA AMP
facility OOS to modify the Gain Mode.):
the XLA or RLA in the equipment table.
AMP-<shelf>-<slot>-6 for XLA or AMP-<shelf>-<slot>-5 for RLA in
the facility table.
— Click Edit.
— Make a note of the Line B AMP facility Gain Mode value.
— Set the AMP facility of the XLA or RLA out of service (OOS) and click
Apply in the Edit facility dialog box.


Step Action
— In the Edit AMP facility dialog:

•Set the Gain Mode to HIGH (XLA only).
•Enter 20.00 in the Target Gain field.
•Click OK.
— Set the AMP facility of the XLA or RLA back to its initial service state.
— Select the AMP Type and the facility AMP-<shelf>-<slot>-6 for XLA
or AMP-<shelf>-<slot>-5 for RLA from the Facility drop down list.
c. At the end of testing, set the XLA or RLA AMP facility OOS and set the
Gain Mode back to the initial value (noted in substep a), then set the
facility back in-service.
d. Edit the Line A AMP facility (AMP-<shelf>-<slot>-8) to set the target gain
to 20 dB and the Gain Mode to HIGH:
the XLA in the equipment table.
— Click Edit.
— Make a note of the Line A AMP facility Gain Mode value.
— Set the AMP facility of the XLA out of service (OOS) and click Apply
in the Edit facility dialog box.
•Set the Gain Mode to HIGH.
•Click OK.
— Set the AMP facility of the XLA back to its initial service state.
For RLA, go to substep f, otherwise go to substep e.


Step Action
e. Verify the ORL at Line A output:

— Select the AMP Type and the facility AMP-<shelf>-<slot>-8 from the
Facility drop down list.
A output port to the input of the CMD.
f. At the end of testing, set the Gain Mode back to the initial value (noted in
substep d).
Validating the fibering to the OPM
20 Read the total power going to the WSS OPM Monitor 1 port (port 1) by
retrieving the untimed OPR-OTS PM value for the WSSOPM OPTMON
facility:
a. Select Performance -> Performance Monitoring.
b. Select the WSSOPM type and the facility OPTMON-<shelf>-<WSS
slot>-1. Click Start Monitoring. Read the Untimed OPR-OTS value.
21 Use the PM feature as follows to verify that the power going to the OPM is
approximately 17 dB (for an MLA, MLA2, MLA2 w/VOA, MLA3, or XLA),
10 dB (for a SLA or LIM), or 19 dB to 23 dB (for a RLA) lower than the power
at the Line B out (port 5).
If Then use the PM feature on the
an XLA is present XLA
an RLA is present RLA
your configuration uses ESAM+MLAx MLAx
otherwise line facing circuit pack

b. Select your next step.
If Then go to
the line facing circuit pack is an MLA, substep c
MLA2, MLA2 w/VOA, or MLA3
the line facing circuit pack is a SLA or LIM substep e
an XLA is present substep c
an RLA is present substep c
your configuration uses ESAM+MLAx substep c


Step Action
c. Select the AMP type and the facility AMP-<shelf>-<AMP slot>-6

(AMP-<shelf>-<slot>-5 for RLA). Click Start Monitoring. Read the
Untimed OPOUT-OTS value.
d. Calculate the difference of the power read in substep c and the power
recorded in step 20. The difference should be approximately 17 dB.
Go to substep g.
e. Select the OPTMON type and the facility OPTMON-<shelf>-<AMP
slot>-6 (AMP-<shelf>-<slot>-5 for RLA). Click Start Monitoring. Read
the Untimed OPR-OTS value.
f. Calculate the difference of the power read in substep e and the power
g. If the power difference is 19 dB or higher (for an MLA, MLA2, MLA2
w/VOA, MLA3, XLA, or RLA) or 12 dB or higher (for a SLA or LIM), clean
and verify the patch cord and the connectors between the Line B Mon
port (port 1) and the OPM Monitor 1 port.
h. If you cannot correct the loss, contact your next level of support.
22 If testing a RLA configuration, go to step 24.
23 To verify that the fiber connections are correct and the power from the correct
port is being measured, temporarily disconnect the fiber between AMP
monitor port 1 to WSS OPM monitor port 1.
If the reading on the WSSOPM Then the fibers are
OPTMON facility indicates
no power connected correctly. Reconnect
the removed fiber and go to the
next step.
there is still power connected incorrectly. Swap the
fiber connections and repeat
from step 20.
retrieving the untimed OPR-OTS PM value for the WSSOPM OPTMON
facility:


Step Action
approximately 17 dB (for an SLA, MLA, MLA2, MLA2 w/VOA, MLA3, XLA, or
RLA) or 10 dB (for a LIM) lower than the power at the Line A Out (port 7).

b. Select your next step.
If Then go to
the line facing circuit pack is an SLA, MLA, substep c
MLA2, MLA2 w/VOA, or MLA3
the line facing circuit pack is a LIM substep e
an XLA is present substep c
an RLA is present substep c
your configuration uses ESAM+MLAx substep c
c. Select the AMP type and the facility AMP-<shelf>-<AMP slot>-8. Click
Start Monitoring. Read the Untimed OPOUT-OTS value.
Go to substep g.
e. Select the OPTMON type and the facility OPTMON-<shelf>-<AMP
f. Calculate the difference of the power read in substep e and the power
g. If the power difference is 19 dB or higher (for an SLA, MLA, MLA2, MLA2
w/VOA, MLA3, XLA, or RLA) or 12 dB or higher (for a LIM), clean and
verify the patch cord and the connectors between the Line A Mon (port 2)
and the OPM Monitor 2 port.
h. If you cannot correct the loss, contact your next level of support.


Step Action
next step.
from step 24.
27 Ensure that all LOS alarms on the WSS OPM are cleared.


Step Action
Calculating loss in the Mux direction

28 Using the PM features, measure the power present at the Line B input (port 6)
as follows.
If Then you are measuring on
Line B input (port 6) of the
If Then go to
the line facing circuit pack is MLA, MLA2, MLA2 w/VOA, substep a
or MLA3
the line facing circuit pack is SLA or LIM substep c
an XLA is present substep a
an RLA is present substep a
your configuration uses ESAM+MLAx substep a
a. Select the AMP type and the facility AMP-<shelf>-<AMP slot>-6

(AMP-<shelf>-<slot>-5 for RLA). Click Start Monitoring.
b. Read the Untimed OPIN-OTS value.
Go to step 29.
c. Select the OPTMON type and the facility
OPTMON-<shelf>-<AMP slot>-6 (AMP-<shelf>-<slot>-5 for RLA). Click
Start Monitoring.
d. Read the Untimed OPR-OTS value.
29 Calculate the loss between the CMD input and the Line B input (port 6):
<power measured in step 10 (dBm)> - <power measured in step 28 (dBm)>
30 Considering all the components present (including fixed pads and DSCM),
calculate the maximum expected loss between the CMD input port and the
Line B input (port 6) of the line facing circuit pack (use the maximum expected
loss data provided in Table 4-3 on page 4-129 to Table 4-5 on page 4-131).


Step Action
The following list is provided as a job aid to calculate the expected loss.
• Identify the equipment present in your configuration and enter the values
for the associated loss or gain, as applicable, after the = (equal sign) on
the respective equipment line.
• Add the values preceded by + (plus sign).
• Subtract the values preceded by - (minus sign).
• The result is the maximum expected loss for your configuration.
+ max CCMD12 (if using Colorless OADM) combiner loss =

- CCMD12 (if using Colorless OADM) add amplifier gain =
+ SMD (if using Colorless OADM) WSS mux loss =
+ max OMDF4 (if present) mux loss =
+ max OMD4 (if present) mux loss =
+ max OMDF4 (if cascaded OMDF4s are used) add-direction passthrough
(EXPR In to NTWK Out) loss =
+ max OMD4 (if cascaded OMD4s are used) add-direction passthrough
(Upgrade In to Common Out) loss =
+ max OMDF8 (if present) mux loss =
+ max BS5 (if present) mux loss =
+ max CMD44 (if present) mux loss =
+ max BMD2 (if present) mux loss =
+ max external/additional drop SLA (associated with colored CMD) Line B tap
loss (if present) = 1.8 dB
- external/additional drop MLA/XLA (associated with colored CMD) Line B
gain (if present) =
- DIA (if present) amplifier gain =
+ DIA (if present) WSS demux loss =
+ max WSS mux loss =
+ Fixed pad loss (if present) =
- XLA gain (if present) =
+ max DSCM loss (if present) =
+ N x 0.5 dB for each patch cord =
= max expected loss =


Step Action
31 If the measured loss (calculated in step 29) is higher than the maximum
expected loss (calculated in step 30), identify the source of the excessive loss
and to make the appropriate corrections:
• Starting with the transmitter and going toward the line facing circuit pack,
measure the input and the output of each component with a power meter.
Always clean both male connectors before closing a connection.
• Compare the loss through each component and patch cord with the
maximum expected loss as indicated in Table 4-3 on page 4-129 to Table
4-5 on page 4-131.
• When the source of the excessive loss is identified, clean and inspect the
optical connectors. If the problem persists, replace the faulty component.
32 If present, verify the ORL at Line B output of the external/additional drop
MLA/XLA (associated with colored CMD):
• In the Performance Monitoring application, select the appropriate
• Select the AMP Type and the facility AMP-<shelf>-<slot>-6 from the
• Click Start Monitoring.
• In the PM table, read the Untimed ORL-OTS value.
• If the value is lower than 28 dB, clean all the optical connections from the
Line B output port to the input of the CMD.


Step Action
Calculating loss in the Demux direction

33 Using the PM features, read the power present at the Line A output (port 7)
as follows.
If Then you are measuring on
Line A output (port 7) of the
If Then go to
the line facing circuit pack is SLA, MLA, MLA2, or MLA3 substep a
the line facing circuit pack is MLA2 w/VOA substep c
the line facing circuit pack is LIM substep e
an XLA is present substep a
an RLA is present substep a
your configuration uses ESAM+MLAx substep a
a. Select the AMP type and the facility AMP-<shelf>-<AMP slot>-8. Click
Start Monitoring.
b. Read the Untimed OPOUT-OTS value.
Go to step 34.
c. Select the VOA type and the facility VOA-<shelf>-<AMP slot>-7. Click
Start Monitoring.
d. Read the Untimed OPOUT-OTS value.
Go to step 34.
e. Select the OPTMON type and the facility
OPTMON-<shelf>-<AMP slot>-8. Click Start Monitoring.
f. Read the Untimed OPR-OTS value.
34 Disable the Forced Shutoff on the DropLIM or WSS 50 GHz w/OPM 9x1 or
WSS Flex C-Band w/OPM 9x1:
a. In the Equipment & Facility Provisioning application, select the
LIM or WSSOPM in the equipment table.
b. Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-8 for LIM or AMP-<shelf>-<slot>-21 for WSSOPM in
the facility table.


Step Action
c. Click Edit.
d. In the Edit AMP facility dialog, select Disabled in the Forced Shutoff
dropdown list then click OK.
table.
• Select the required CHC facility in the demux direction and for the
wavelength that you are testing
— Set the Primary state to “OOS”
— Set the Opaque state to “No”
— Set the Switch selector to the port to which the CCMD12 Common In
is connected
• Select the NMCC in the Facility drop down list.
— Set the Target Loss to 0 dB.
36 With a power meter, measure the power present on the CMD output port that
corresponds to the wavelength being tested.
37 Calculate the loss between the line facing circuit pack Line A out and the CMD
channel output port:
calculate the maximum expected loss between the Line A output and the
CMD channel output (use the data provided in Table 4-3 on page 4-129 to
Table 4-5 on page 4-131). Gain values can be retrieved by querying the
appropriate AMP facilities.
The following list is provided as a job aid to calculate the expected loss.
• Identify the equipment present in your configuration and enter the values
for the associated loss or gain, as applicable, after the = (equal sign) on
the respective equipment line.
• Add the values preceded by + (plus sign).
• Subtract the values preceded by - (minus sign).
• The result is the maximum expected loss for your configuration.
Fixed pad loss (if present) =

- XLA gain (if present) =
+ max WSS demux loss =
+ max BMD2 (if present) demux loss =


Step Action
+ max CMD44 (if present) demux loss =

+ max OMDF4 (if present) demux loss =
+ max OMD4 (if present) demux loss =
+ max OMDF4 (if cascaded OMDF4s are used) drop-direction passthrough
(EXPR Out to NTWK In) loss =
+ max OMD4 (if cascaded OMD4s are used) drop-direction passthrough
(Common In to Upgrade Out) loss =
+ max OMDF8 (if present) demux loss =
+ max BS5 (if present) demux loss =
+ max CCMD12 (if using Colorless OADM) splitter loss =
- CCMD12 (if using Colorless OADM) drop amplifier gain =
+ SMD (if using Colorless OADM) WSS demux loss =
- WSS 50 GHz w/OPM 9x1/WSS Flex C-Band w/OPM 9x1 (if present)
SW8/SW9 amp gain =
- cascaded LIM gain (if present) =
- external/additional drop SLA (associated with colored CMD) Line A gain (if
present) =
- external/additional drop MLA/XLA (associated with colored CMD) Line A
gain (if present) =
+ DIA (if present) WSS mux loss =
- DIA (if present) amplifier gain =
39 If the measured loss (calculated in step 37) is higher than the maximum
expected loss (calculated in step 38), identify the source of the excessive loss
and make the appropriate corrections:
• Starting with the Line A output and going toward the CMD, measure the
input and the output of each component with a power meter.
• Compare the loss through each component and patch cord with the
maximum expected loss as indicated in Table 4-3 on page 4-129 to Table
4-5 on page 4-131.
optical connectors.
• If the excessive loss persists, replace the faulty component. Refer to the
323-1851-545.


Step Action
40 If present, verify the ORL at Line A output of the external/additional drop

SLA/MLA/XLA (associated with colored CMD):
• In the Performance Monitoring application, select the appropriate
• In the PM table, read the Untimed ORL-OTS value.
• If the value is lower than 28 dB, clean all the optical connections from the
Line A output port to the input of the CMD.
41 On the WSSOPM, select the required CHC facility and for the wavelength that
you are testing:
— Set the Opaque state to “Yes”.
— Set the Switch selector to the default (usually the first switch on the
WSS).
— Set the Target Loss to its default value (18 dB).
42 If you are testing with DIA, select the DIA WSSOPM in the equipment table.
• Select the CHC in the Facility drop down list.
— Select the wavelength of the transmitter chosen in step 10.
WSS).
table.
• Select the required CHC facility in the mux direction and for the
wavelength that you are testing
— Set the Primary state to “IS”.
— Set the Switch selector to the default mux port (port 11).


Step Action
table.
• Select the required CHC facility in the demux direction and for the
wavelength that you are testing.
— Set the Primary state to “IS”.
— Set the Switch selector to the default demux port (port 12).
45 Enable the Forced Shutoff on the DropLIM or WSS 50 GHz w/OPM 9x1 or
WSS Flex C-Band w/OPM 9x1:
a. In the Equipment & Facility Provisioning application, select the
LIM or WSSOPM in the equipment table.
b. Select AMP from the Facility Type drop-down list and select
AMP-<shelf>-<slot>-8 for LIM or AMP-<shelf>-<slot>-21 for WSSOPM in
the facility table.
c. Click Edit.
d. In the Edit AMP facility dialog, select Enabled in the Forced Shutoff
dropdown list then click OK.
46 Remove the loopback put in step 12.
47 Repeat from step 9 on the other OTS if the node is not a terminal.
Testing express port cabling for all channels
48 Select the WSSOPM or RLA you want to test. Start with one direction. Ensure
that Line A In (port 8) port on the circuit pack associated with the WSS or the
Line A In (port 8) port on the RLA is disconnected as follows.
If Then you are ensuring that the Line
A In (port 8) is disconnected on the
following circuit pack associated
with the WSS or on the RLA
• In the Equipment & Facility Provisioning application, retrieve the facility

information of the Line A AMP facility (port 8).
• Ensure the primary state of the Line A AMP facility (port 8) is not
OOS-AUMA.


Step Action
• Place the pre-amplifier in no shutoff mode by setting the AMP facility

parameter ALSO Disabled to True.
The “Automatic Shutoff Disabled” alarm is raised. If alarm correlation is
enabled, this alarm could be masked. Check the active disabled alarms.
In the no shutoff mode, the amplifier will produce broadband noise. In this
mode, the amplifier output power may be different from 9.5 dBm.
49 Use the PM function to verify the OPOUT-OTS at the pre-amplifier output by
performing the following:
• Select Performance->Performance Monitoring-> New to open the PM
screen.
• For non-MLA2 w/VOA, select the AMP Type and the facility
• For MLA2 w/VOA, select the VOA Type and the facility
• Record the OPOUT-OTS Untimed parameter.
50 Select the OPTMON or RLA from the Type drop down list and the facility of
the WSSOPM or RLA Common In port in the Facility drop down list.
• Verify that the OPR-OTS Untimed parameter reading is similar to the one
recorded in step 49.
51 Select the first adjacent (remote) WSSOPM or RLA switch In port for the
pass-through channel as indicated in the EDP/IDP in the Facility drop down
list.
• Record the OPR-OTS untimed parameter. The value obtained should not
be more than 1 dB more than the Max Demux Loss indicated in Table 4-3
on page 4-129.
52 Repeat step 51 for all the adjacent (remote) WSSOPM or RLA switch In ports
for the pass-through channels that are connected to the WSSOPM or RLA
you are testing as indicated in the EDP/IDP.
53 Place the pre-amplifier back to shutoff mode by setting the AMP facility
parameter ALSO Disabled to False.
The “Automatic Shutoff Disabled” alarm is cleared.
54 Repeat step 48 to step 53 for all the other WSSOPMs or RLAs at that site.
55 Return the transmitter power to its default value if you have adjusted the
output power in step 10.
—end—

Table 4-3
CCMD12, SMD, CMD44, CMD64, CMD42, CMD96, BMD2, OMD4, and WSS maximum dB loss
Unit PEC Max Mux loss (dB) Max Demux loss (dB)
100 GHz CMD44 NTT862AA 6.0 6.0
100 GHz CMD44 with isolator NTT862FA 6.0 6.6
50 GHz CMD44 Blue NTT862BA 7.0 7.0
50 GHz CMD44 Red NTT862BB 7.0 7.0
50 GHz enhanced CMD44 Blue NTT862BC 7.5 7.5
50 GHz enhanced CMD44 Red NTT862BD 7.5 7.5
75 GHz CMD64 NTT862JA 6.5 7.1
112.5 GHz CMD42 NTT862NA 6.5 7.1
50 GHz CMD96 NTT862EA 7.0 7.6
SCMD4 100 GHz NTK508AAE5/ 4.6 Ch In to Common 5.4 Common In to Ch
NTK508ABE5/ Out Out
NTK508ACE5/ 1.1 Upgrade In to 0.75 Common In to
NTK508ADE5/ Common Out Upgrade Out
NTK508AEE5/
NTK508AFE5/
NTK508AGE5/
NTK508AHE5/
NTK508AJE5
WSS 100 GHz w/OPM 5x1 NTK553EA 7.0 8.7
WSS 100 GHz w/OPM 4x1 NTK553HA 11.4 8.5
WSS 100 GHz w/OPM 2x1 (2-slot) NTK553JA 7.0 4.4
WSS 100 GHz w/OPM 2x1 (1-slot) NTK553JB 8.8 5.3
WSS 50 GHz w/OPM 2x1 (3-slot) NTK553KC 7.0 4.4
WSS 50 GHz w/OPM 2x1 (1-slot) NTK553KA 8.4 12.4 Common In to
Demux Out
2.0 Common In to Drop
Out
WSS 50 GHz w/OPM 9x1 NTK553FA 7.0 11.2
NTK553FC 6.8 11.7
WSS Flex C-Band w/OPM 9x1 NTK553LA 6.8 11.7
RLA 5x1 NTK553RA 6.5 8.0
BMD2 NTT862DA 3.8 3.8

Table 4-3
CCMD12, SMD, CMD44, CMD64, CMD42, CMD96, BMD2, OMD4, and WSS maximum dB loss
CCMD12 NTK508FA 13.4 13.4
SMD NTK553GA 7.3 7.3
SMD NTK553GB 7.1 7.1
OMD4 NTK504AA/ 2.5 Ch In to Common 3.3 Common In to Ch
NTK504AB/ Out Out
NTK504AC/ 1.1 Upgrade In to 0.75 Common In to
NTK504AD/ Common Out Upgrade Out
NTK504AE/
NTK504AF/
NTK504AG/
NTK504AH/
NTK504AJ
Table 4-4
OMDF4, OMDF8, and BS5 maximum dB loss
Mux/Add direction Demux/Drop direction Maximum Mux loss Maximum

(dB) Demux loss (dB)
OMDF4
Ch 1 In - NTWK OUT NTWK IN - Ch 1 Out 1.7 2.8
EXPR IN - NTWK OUT NTWK IN - EXPR OUT 2.0 2.7
OMDF8

Table 4-4
OMDF4, OMDF8, and BS5 maximum dB loss
Mux/Add direction Demux/Drop direction Maximum Mux loss Maximum

(dB) Demux loss (dB)
BS5
Group A In - NTWK OUT NTWK IN - Group A Out 2.0 3.2
Group B In - NTWK OUT NTWK IN - Group B Out 2.2 3.0
Group C In - NTWK OUT NTWK IN - Group C Out 2.5 2.7
Group D In - NTWK OUT NTWK IN - Group D Out 2.8 2.4
Group E In - NTWK OUT NTWK IN - Group E Out 3.1 2.1
Table 4-5
Dispersion Slope Compensation Modules (DSCM) maximum dB loss
Description Order Equivalent fiber PEC Maximum insertion

length (km) loss (dB)
DSCM-5 Type 1 C-band SC 5 NTT870AA 2.0
DSCM-10 Type 1 C-band SC 10 NTT870AB 2.3
DSCM-20 Type 1 C-band SC 20 NTT870AC 2.9
DSCM-30 Type 1 C-band SC 30 NTT870AD 3.5
DSCM-40 Type 1 C-band SC 40 NTT870AE 4.1
DSCM-50 Type 1 C-band SC 50 NTT870AF 4.7
DSCM-60 Type 1 C-band SC 60 NTT870AG 5.4
DSCM-70 Type 1 C-band SC 70 NTT870AH 6.0
DSCM-80 Type 1 C-band SC 80 NTT870AJ 6.6
DSCM-90 Type 1 C-band SC 90 NTT870AK 7.2
DSCM-100 Type 1 C-band SC 100 NTT870AL 7.8
DSCM-110 Type 1 C-band SC 110 NTT870AM 9.5
DSCM-120 Type 1 C-band SC 120 NTT870AN 10.1
DSCM-130 Type 1 C-band SC 130 NTT870AP 10.9
DSCM-140 Type 1 C-band SC 140 NTT870AQ 11.5
DSCM-20 Type 2 C-band SC 20 NTT870CA 2.5
DSCM-40 Type 2 C-band SC 40 NTT870CB 2.9

Table 4-5
Dispersion Slope Compensation Modules (DSCM) maximum dB loss (continued)
Description Order Equivalent fiber PEC Maximum insertion

length (km) loss (dB)
DSCM-80 Type 2 C-band SC 80 NTT870CC 3.9
DSCM-120 Type 2 C-band SC 120 NTT870CD 5.0
DSCM-160 Type 2 C-band SC 160 NTT870CE 6.1
DSCM-200 Type 2 C-band SC 200 NTT870CF 7.1
DSCM-240 Type 2 C-band SC 240 NTT870CG 8.2
DSCM-280 Type 2 C-band SC 280 NTT870CH 9.3
DSCM-320 Type 2 C-band SC 320 NTT870CJ 10.3
DSCM-20 Type 3 C-band SC 20 NTT870EA 4.1
DSCM-40 Type 3 C-band SC 40 NTT870EB 5.1
DSCM-80 Type 3 C-band SC 80 NTT870EC 6.9
DSCM-120 Type 3 C-band SC 120 NTT870ED 8.2
DSCM-12.5 Type 5 C-band SC 12.5 NTT870GA 3.7
DSCM-25 Type 5 C-band SC 25 NTT870GB 4.3
DSCM-50 Type 5 C-band SC 50 NTT870GC 5.5
DSCM-75 Type 5 C-band SC 75 NTT870GD 7.0
DSCM-100 Type 5 C-band SC 100 NTT870GE 8.2
DSCM-125 Type 5 C-band SC 125 NTT870GF 8.8
DSCM-150 Type 5 C-band SC 150 NTT870GG 10.0

Procedure 4-8
Testing a CDC ROADM configuration
Use this procedure to test channel access continuity on a CDC ROADM where
light from transmitting subtending equipment is available. This test verifies the
optical continuity and checks for reflection-related problems. This procedure
does not optimize the channels for traffic.
Refer to 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA, for

detailed information on photonic concepts, applications, and engineering
rules.
CDC ROADM configurations include Fiber Interconnect Modules (FIM), either

FIM Type 1 or FIM Type 2. Keep in mind the following information regarding
the FIMs. For more information, see the Photonic passive modules table in
Planning - Ordering Information, 323-1851-151.
positions
connector positions

positions
• In addition to providing the optical loopback operation required by

removed and saved for future use.


Prerequisites
the equipment associated with CDC ROADM equipment at the site. Full
traffic continuity testing can proceed only after the system is complete. It
is recommended (while not mandatory) that you perform an Optical
Loopback test with at least one service layer source for each installed
CCMD8x16. See the procedure on performing optical loopback testing in
• Perform this procedure only after you have completed Procedure 2-1,
“Powering up a new network element and connecting a craft computer”
complete the NE commissioning, photonic layer provisioning including TID
slot sequence provisioning (see “Photonic layer provisioning procedures”
on page 3-3), and fibering before performing this procedure.
• The fibers and the MPO cables that are used in the following steps to
connect the equipment must be verified to be in good working order prior
to use. It is very important that fibers are cleaned and scoped prior to
being connected. See Installation - General Information, 323-1851-201.0,
for the cleaning and inspection procedure.
• Use optical terminators on applicable unused input faceplate connectors
of installed WSS circuit packs. If dust caps are used instead of optical
terminators, PMs can be reported against the port and the port may
appear in-service.
This requirement does not apply to the WSS Flex C-Band w/OPM 20x1
circuit packs.


CAUTION
DANGER
Risk of injury
CAUTION
Step Action

testing.
Power parameter.
Untimed parameter.


Step Action
8 Repeat step 2 to step 7 for all other ROADM OTSs at the site.
Testing the interconnects using the Connection Validation application: WSSOPM-to-WSSOPM,
WSSOPM-to-MPO loopback module, WSSOPM-to-LC loopback module, WSSOPM-to-CCMD8x16,
CCMD8x16-to-MPO loopback module
9 See the following figures for examples of the interconnects tested by the
Connection Validation application:
• Figure 4-53 on page 4-138—testing the WSSOPM-to-WSSOPM
interconnect
• Figure 4-54 on page 4-139—testing the WSSOPM-to-MPO loopback
module interconnect
• Figure 4-55 on page 4-140—testing the WSSOPM-to-LC loopback
module interconnect
• Figure 4-56 on page 4-141—testing the WSSOPM-to-CCMD8x16
interconnect
• Figure 4-57 on page 4-142—testing the CCMD8x16-to-MPO loopback
module interconnect
End Not Discovered alarms or Adjacency Mismatch alarms. If alarms are
raised, see Fault Management - Alarm Clearing, 323-1851-543 for the
procedures on how to clear the respective alarms.
11 Make sure that the Dark Fiber Loss Management system parameter is
enabled in the Node Information tab of Site Manager. (For details, see the
procedure on editing the nodal system parameters in Administration and
Security, 323-1851-301.)
12 Make sure that you wait for approximately 5 minutes after the last fibering was
completed.


Step Action
13 In Site Manager, go to Configuration -> Photonic Services ->Connection

Validation and display the connection validation results under the Validation
Summary tab. If the cables are not connected as provisioned, disconnect,
clean and inspect the connectors and reconnect to the correct location. For
High Fiber Loss alarms, see the procedure in Fault Management - Alarm
Clearing, 323-1851-543.
The CDC equipment uses MPO cables and connectors. For steps to:
• connect MPO cables (in the procedure on routing fiber-optic cables and
electrical cables to circuit packs in the 6500 shelf), see the Installation
technical publication specific to the respective 6500 shelf type
CAUTION
for any reason.

connection.
14 If alarms are raised, see Fault Management - Alarm Clearing, 323-1851-543

for the procedures on how to clear the respective alarms.
High Fiber Loss detection is performed between the following locations:
• WSSOPM − WSSOPM
• WSSOPM − MPO loopback connector
• WSSOPM − LC loopback connector
• WSSOPM − CCMD8x16
• WSSOPM − CXM
• CCMD8x16 - MPO loopback connector
• CXM - MPO loopback connector


Figure 4-53
CDC ROADM—testing the WSSOPM-to-WSSOPM interconnect


Figure 4-54
CDC ROADM—testing the WSSOPM-to-MPO loopback module interconnect


Figure 4-55
CDC ROADM—testing the WSSOPM-to-LC loopback module interconnect


Figure 4-56
CDC ROADM—testing the WSSOPM-to-CCMD8x16 interconnect


Figure 4-57
CDC ROADM—testing the CCMD8x16-to-MPO loopback module interconnect


Step Action
Testing with transponder loopback (CCMD8x16 only)

15 Perform an Optical Loopback test on the CCMD8x16 and degree you are
preparing to turn up. (For details, see the procedure on performing
connection validation in Part 2 of Configuration - Provisioning and Operating,
323-1851-310.)
• See Figure 4-58 on page 4-144 for an example of testing with
transponder loopback at a CDC ROADM node.
• See Figure 4-59 on page 4-145 for an example of testing the jumper cable
interconnect on CCMD8x16 using transponder loopback. If a CXM is
present, the jumper cable is automatically tested during the Optical
Loopback test (in step 18). Only the path that goes through an MPO
loopback connector on the FIM will be verified. If there is a WSSOPM on
the far end, that particular subfiber will not be verified through the jumper.
16 Make sure a transponder is connected to the CCMD8x16 with which you are
testing. The transponder should have a valid SPLI and no CRS on the
respective CCMD8x16 ADJ-TX.
17 Provision the Far End Address on the ADJ-TX of the appropriate port of the
CCMD8x16 to which the transponder is connected.
18 Perform optical loopback testing through CCMD8x16 ADJ-TX. See the
procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310.
19 Select the Validation Summary tab to display the connection validation
results. If the test has failed, refer to the ‘Reason’ column in the Validation
Summary table and take further action based on the information provided.
For High Fiber Loss alarms, see the procedure in Fault Management - Alarm
Clearing, 323-1851-543. If required, disconnect the MPO cable, clean and
inspect the connectors and reconnect. For steps to:
CAUTION
for any reason.

connection.


Figure 4-58
CDC ROADM—testing with transponder loopback


Figure 4-59
CDC ROADM—testing the jumper cable interconnect on CCMD8x16 using transponder loopback


Step Action
20 If excessive losses are detected, clean and inspect the optical connectors.
(See Table 4-6 on page 4-146 for maximum CCMD8x16 and WSS Flex
C-Band w/OPM 20x1 loss values and Table 4-7 on page 4-146 for maximum
FIM loss values.)
Table 4-6
CCMD8x16 and WSS Flex C-Band w/OPM 20x1 maximum loss
WSS Flex C-Band w/OPM 20x1 NTK553MA 8.2 8.2
CCMD8x16 NTK508HA 17 17
Table 4-7
Fiber Interconnect Modules (FIM) maximum loss
Module PEC Maximum insertion loss (dB)

FIM Type 1 NTK504CA 2 dB
FIM Type 2 NTK504CB 2 dB
21 If the problem persists, replace the faulty component. Refer to the appropriate
procedure in Fault Management - Module Replacement, 323-1851-545.
Validating CMD44 to WSS connectivity
23 Ensure that the CMD44/BMD2 and MLA3/XLA are added to the slot
sequence. See the procedure on editing a slot sequence in Part 2 of
24 For the CMD you are testing:
a. Select one of the transmitters to be connected to the selected CMD.
b. For the ADJ-TX facility of the CMD port to be connected, set the
c. If you can adjust the output power of the transmitter, set it to correct power
level.


Step Action
d. Connect the transmitter to the appropriate CMD port. The transmitter

wavelength should match the CMD port you are using (that is, the
transmitter must be tuned to correct wavelength).
If SPLI managed, the transmitter will be tuned automatically to the center
frequency with proper power level.
Note: No other transmitter should be connected to the CMD at this point.
Make sure the receiver of the testing wavelength is not connected to the
circuit pack so as not to overload receiver port while testing.
25 Retrieve the transmitter power (OPT-OCH from the OTM/PTP facility) and the
power into amplifier Line B input port (AMP OPTMON PM).
The delta should be less than:
• CMD44/BMD2: 9 dB +/- 1 dB
• eCMD44/BMD2: 9 dB +/- 1 dB
• CMD44: 6 dB +/- 1 dB
• eCMD44: 6 dB +/- 1 dB
26 Retrieve the amplifier Line B output port (AMP OPUT-OTS) and the power
into WSS switch port input (WSS OPTMON PM). The expected fiber loss
should be less than 2 dB (as in Table 4-7 for FIM1).
27 Repeat step 23 to step 25 for each CMD44/BMD2.
Validating the fibering to the output of the line facing circuit pack
28 Select one degree for the following sequence of testing steps. (You will repeat
the steps for each degree.)
29 On the transponder connected to the CCMD8x16/CMD44 with which you are
testing:
the transmitter to the appropriate CCMD8x16/CMD44 port.
30 Provision a photonic connection (you can select any wavelength for
CCMD8x16 or the appropriate wavelength for CMD44) from the CCMD8x16
or CMD44 input port where the transponder is connected to the output port
of the line facing circuit pack. See the procedure on adding a photonic
connection in Configuration - Connections Management, 323-1851-320.


Step Action

MLA3 20 dB
SRA/ESAM/SAM 20 dB

appropriate photonic shelf from the Shelf drop-down list and select the CDC
ROADM WSSOPM in the equipment table.
• Select CHC in the Facility drop down list and select the CHC with the
index associated with the wavelength in the Mux direction of the
transmitter chosen in step 30, that is ‘CHC-<shelf>-<slot>-10-<index>’.
34 Select the next step.
If Then go to
the line facing circuit pack is an MLA3 step 35
an XLA is present step 37


Step Action
35 If the line facing circuit pack is an MLA3, perform this step on the line facing
circuit pack (MLA3).
to 17 dB:
— Click Edit.
— Record the current Target Gain value. (You will revert to it at the end
of this procedure.)
then click OK.


Step Action
to 20 dB:
— Click Edit.
— Record the current Target Gain value. (You will revert to it later in this
procedure.)
then click OK.
A output port to the input of the CCMD8x16/CMD44.
Go to step 38.
37 If an XLA is present, perform the following on the XLA:

to 20 dB and the Gain Mode to HIGH (You will be instructed to set the XLA
AMP facility OOS to modify the Gain Mode.):
— Click Edit.
— Record the Line B AMP facility Gain Mode value and the Target Gain
value. (You will revert to them at the end of this procedure.)


Step Action

•Set the primary state to out of service (OOS).
•Click Apply.
•Set the primary state back to in service (IS).
•Click OK.
c. Edit the Line A AMP facility (AMP-<shelf>-<slot>-8) to set the target gain
— Click Edit.
— Record the Line A AMP facility Gain Mode value and the Target Gain
•Click Apply.
•Click OK.


Step Action
d. Verify the ORL at Line A output:

A output port to the input of the CCMD8x16/CMD44.
retrieving the untimed OPR-OTS PM value the WSSOPM OPTMON facility:
approximately 17 dB (for an MLA3 or XLA) lower than the power at the Line
A Out (port 7).

b. Select the AMP type and the facility AMP-<shelf>-<AMP slot>-8. Click
c. Calculate the difference of the power read in substep b and the power
d. If the power difference is 19 dB or higher (for an MLA3 or XLA), clean and
e. If you cannot correct the loss, contact your next level of support.


Step Action
next step.
from step 38.
B out (port 5).

verify the patch cord and the connectors between the Line B Mon port
(port 1) and the OPM Monitor 1 port.


Step Action
next step.
from step 41.
Restoring the settings on the degree after testing
45 Select your step.
If Then
the line facing circuit set the respective MLA3 Target Gain values back to
pack is an MLA3 the values you recorded in step 35 (MLA3 Line B) and
step 36 (MLA3 Line A)
an XLA is present set the XLA AMP facilities to OOS, then set the XLA
Gain Mode and Target Gain back to the values you
recorded in step 37 for the XLA Line B and Line A,
respectively. Set the facilities back to IS.
46 On the WSSOPM:
• Select CHC in the Facility drop down list and select the CHC facility with
the index associated with the wavelength in the Mux direction of the
47 Delete the photonic connection you provisioned in step 30.
48 Remove the far-end adjacency provisioning if it was added in step 17 for the
purpose of this testing only.
49 Remove the loopback you added in step 31.
50 Remove the padding you added in step 32.
51 Repeat step 29 to step 50 for each of the remaining degrees.
—end—

Procedure 4-9
Testing TOADM channel access continuity
Use this procedure to test channel access continuity at TOADM sites where
light from transmitting subtending equipment is available. This test verifies the
optical continuity and checks for reflection-related problems. This procedure
does not optimize the channels for traffic.
See Figure 4-60 on page 4-156 and Figure 4-61 on page 4-157 for an example
of TOADM node testing. Labeled numbers in this figure identify the steps in
this procedure. You can use Table 4-9 on page 4-163 to record information
and test results.
Prerequisites
• Have an optical power meter.
• Make sure that you have a copy of the EDP/IDP.
• This procedure allows you to perform optical continuity testing through the
OTS. Full traffic continuity testing can proceed only after the system is
complete. It is recommended that you perform the continuity test with at
least one service layer source for each installed SCMD4.
• Perform this procedure only after you have completed all procedures
procedure.
It is very important that client fibers are cleaned and inspected prior to
being connected. See Installation - General Information, 323-1851-201.0
for the cleaning and inspection procedures.
CAUTION
DANGER
Risk of injury


CAUTION
Figure 4-60
Overview of TOADM channel access continuity testing
10
16 17
A
B
12 18
19
11
Power 9 20
meter
Tx Rx


Figure 4-61
Overview of TOADM channel access continuity testing (with ESAM)
Step Action
Note: Perform this procedure for each OTS.

circuit pack if applicable.
testing.
Power parameter.


Step Action
Untimed parameter.
The calculated coupler loss should be less than 3.5 dB.
coupler loss will be much greater than 3.5 dB. You must rectify the situation
before you continue.
9 Select the SCMD4 you want to test:
• Choose the SCMD4 that is the furthest from the line-facing circuit pack.
• Choose one of the transmitters to be connected to the selected SCMD4.
Make sure the wavelength of the transmitter matches the wavelength of
the SCMD4 port it is connected to.
• If you can adjust the output power of transmitter, set it to maximum.
• Using a power meter set correctly for the wavelength, measure the
transmitter output power and connect the transmitter to the appropriate
SCMD4 port.

loopback with the appropriate padding between the line-facing circuit pack
Line B OUT port and the line-facing circuit pack Line A IN port.


Step Action
The amount of padding depends on the type of the line-facing circuit pack.
Circuit pack Padding
LIM 0 dB
SLA 10 dB
MLA, MLA2, or MLA3 20 dB
ESAM 20 dB
11 On the SCMD4 where the transmitter is connected, set the target loss of the
corresponding ingress VOA facility to 0 dB by editing the Target Loss
parameter of the VOA facility in the Equipment and Facility Provisioning
application.
12 Using the PM features, measure the power present at the Line B input of the
line-facing circuit pack:
If the line-facing circuit Then select
pack is
MLA, MLA2, or MLA3 Line B AMP facility (port 6) and record the
OPIN-OTS Untimed value
SLA and LIM OPTMON facility (port 6) and record the
OPR-OTS Untimed value
Note: If your configuration uses ESAM, perform this step on the MLAx.
13 Calculate the loss between the SCMD4 input and the Line B input port:
calculate the maximum expected loss between the SCMD4 input channel
port and the Line B input port (use the information in Table 4-8 on page 4-163
and Table 4-5 on page 4-131).
max SCMD4 mux loss (Ch-In to Common Out) =

+ N x SCMD4 Group mux loss (Upgrade In to Common Out) =
+ Fixed pad loss (if present) =


Step Action
15 If the measured loss is higher than the maximum expected loss, identify the
source of the excessive loss and make the appropriate corrections:
• Starting with the transmitter and going toward the line-facing circuit pack,
• Compare the loss through each component and patch cord to the
maximum expected loss as indicated in Table 4-8 on page 4-163 and
16 If the line-facing amplifier circuit pack is an MLA, MLA2, or MLA3:
• Adjust the target gain of the Line B amplifier facility to 17 dB.
• Verify the ORL at the Line B output. If the value is lower than 28 dB, clean
all the optical connections from the Line B output port to the input of the
pad. When DSCMs are used and the DSCM location is at the head end
of the span (collocated with the amplifier being commissioned), the
minimum ORL threshold to meet or exceed is 24 dB.
17 If the line-facing amplifier circuit pack is an MLA, MLA2, MLA3, or an SLA:
• Adjust the target gain of the Line A amplifier facility to 20 dB.
• Verify the ORL at the Line A output. If the value is lower than 28 dB (24 dB
when a DSCM is placed after the amplifier output), clean all the optical
connections from the Line A output port to the input of the SCMD4.
18 Using the PM features, measure the power present at the Line A output of the
line facing circuit pack:
If the line-facing circuit pack Then use the Line A facility (port 8)
is
MLA, MLA2, MLA3, or SLA AMP facility OPOUT-OTS Untimed value
LIM OPTMON facility OPR-OTS Untimed value
Note: If your configuration uses ESAM, perform this step on the MLAx.
19 Set the target loss of the demux VOA facility on the SCMD4 Common In
(port 1) to 0 dB.
20 With a power meter, measure the power present on the SCMD4 output port
that corresponds to the wavelength you are testing.
21 Calculate the loss between the line-facing circuit pack Line A Out and the
SCMD4 channel output port.


Step Action
compute the maximum expected loss between the Line A output and the
SCMD4 channel output (use the information in Table 4-8 on page 4-163 and
Table 4-5 on page 4-131).
Fixed pad loss (if present) =

+ N x SCMD4 group demux loss (Common In to Upgrade Out) =
+ max SCMD4 demux loss (Common In to Ch-Out) =
a. Starting with the Line A output and going toward the SCMD4, measure
the input and the output of each component with a power meter.
b. Compare the loss through each component and patch cord with the
maximum expected loss as indicated in Table 4-8 on page 4-163 and
c. When the source of the excessive loss is identified, clean and inspect the
24 When you have completed all testing, return the SCMD4 VOAs to 15 dB of
attenuation and disconnect the test transmitter.
25 Remove the loopback at the amplifier and reconnect the fibers as per
EDP/IDP.
If this is a Then
thin OADM site repeat from step 9 on the other line-facing OTS. Then
go to step 27.
thin terminal site you have completed this procedure


Step Action
27 Using fibers that are known to be in good condition, complete the connection
between the two innermost SCMD4 in each direction for the pass-through
traffic. See Figure 4-8 on page 4-46 for an example.
a. Connect the Upgrade Out (port 12) of the innermost SCMD4 (or Line A
Out [port 7] of the line-facing circuit pack if SCMD4 cascade is empty) in
OTS1 to the Upgrade In (port 11) of the innermost SCMD4 (or Line B In
[port 6] of the line-facing circuit pack if SCMD4 cascade is empty) in
OTS2.
b. Connect the Upgrade In (port 11) of the innermost SCMD4 (or Line B In
[port 6] of the line-facing circuit pack if SCMD4 cascade is empty) in
OTS1 to the Upgrade Out (port 12) of the innermost SCMD4 (or Line A
Out [port 7] of the line-facing circuit pack if SCMD4 cascade is empty) in
OTS2.
Note: The innermost SCMD4 is the one that is the furthest from the
line-facing circuit pack in each OTS.
28 Provision the inter-OTS adjacency for the pass-through traffic.
• Select Configuration -> Equipment & Facility Provisioning.
• In the Equipment table, select the innermost SCMD4 (the one furthest
from the line facing circuit pack), or the line-facing circuit pack if the
SCMD4 cascade is empty (no SCMD4).
• Select ADJ in the Facility Type drop down list.
• Select the adjacency that corresponds to the port where the
pass-through traffic is handed off to the other OTS.
This port is the Upgrade Out (port 12) of the innermost SCMD4 or Line A
OUT (port 7) of the line-facing circuit pack if the SCMD4 cascade is
empty (no SCMD4).
Note: Adjacency format = ADJ-<shelf>-<slot>-<port>
• Click Edit in the Facility area.
• Set the Adjacency type to CMD (if the other OTS SCMD4 cascade is not
empty) or LIM (if the other OTS SCMD4 cascade is empty).
• Enter the Expected Far End Address and the Expected Far End Address
Format as described in the EDP/IDP.
The Expected Far End Address must point to the input port of the
innermost SCMD4 of the other OTS (Port 11) or to the Line B In (port 6)
of the line-facing circuit pack of the other OTS if its SCMD4 cascade is
empty (no SCMD4).


Step Action
• Click OK.
• Repeat the above substeps for the other OTS.
—end—
Table 4-8
SCMD4 Maximum dB loss
Circuit PEC Max Mux loss (dB) Max Demux loss (dB)
pack
SCMD4 NTK508AAE5/ • Ch-In to Common Out: 4.6 dB • Common In to Ch-Out: 5.4 dB

100 GHz NTK508ABE5/ • Upgrade In to Common Out: 1.1 dB • Common In to Upgrade Out: 0.75
NTK508ACE5/ dB
NTK508ADE5/
NTK508AEE5/
NTK508AFE5/
NTK508AGE5/
NTK508AHE5/
NTK508AJE5
Table 4-9
Worksheet: Testing Thin OADM channel access continuity
Procedure Site Name:________________ Grp Grp Grp Grp Grp Grp Grp Grp Grp
step Site ID:___________________ Ch Ch Ch Ch Ch Ch Ch Ch Ch
Shelf:____________________
step 9 Transmitter power (dBm)
step 12 Power at Line B input (dBm)
step 13 Measured loss (dB)
step 14 Expected loss (dB)
step 18 Power at Line A output (dBm)
step 20 Power at SCMD4 demux output

(dBm)
step 21 Measured loss (dB)
step 22 Expected loss (dB)

Procedure 4-10
Testing a DIA configuration
Use this procedure to test a direction independent access (DIA) configuration
that is not part of a Colorless COADM configuration. Figure 4-62 on page
4-165 illustrates an example of DIA configuration.
To test a low channel count DIA configuration, see Procedure 4-11, “Testing a
low channel count DIA configuration”.
Prerequisites
• Have a power meter.
network element. Full traffic continuity testing can proceed only after the
system is complete. It is recommended that you perform the continuity test
with at least one service layer source for each installed CMD44, CMD96,
or CMD64.
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. Connect all optical
fibers within the DIA configuration. You must first complete the NE
commissioning and fibering before performing this procedure.
client equipment must be verified to be in good working order before use.
It is very important that client fibers are cleaned and inspected before
CAUTION
DANGER
Risk of injury


CAUTION
Figure 4-62
DIA configuration testing overview
19
18 21
OPM
25 17
14
13 26 14c 22
MON
B
A
10 26c
8 28
BMD2
7 29
4 30
Power 3 31
meter
Tx Rx Rx Tx
Step Action

2 Make sure that you have connected all optical fibers within the DIA
configuration. Do not connect fibers between the DIA configuration and other
WSS circuit packs.
3 Select the CMD44, CMD96, or CMD64 you want to test:
• Select one of the transmitters to be connected to the selected CMD44,
CMD96, or CMD64.
the transmitter to the appropriate CMD44, CMD96, or CMD64 port.


Step Action
The transmitter wavelength should match the CMD44, CMD96, or CMD64

port you are using (that is, the transmitter must be tuned to correct
wavelength).
4 Check power at the Common Out of the CMD44 (port 90), CMD96 (port 194),
or the CMD64 (port 130) with a power meter to validate insertion loss. If the
loss is higher than:
• 8 dB for a CMD44 50 GHz
• 7 dB for an eCMD44 100 GHz
• 8.5 dB for an eCMD44 50 GHz
• 7.0 dB for a CMD96 50 GHz
clean and inspect the optical connectors. Repeat the measurement and if the
loss is still higher than the values above, replace the CMD44, CMD96, or
CMD64 module. Refer to the appropriate procedure in Fault Management -
Module Replacement, 323-1851-545.
5 Reconnect the fiber of CMD44, CMD96, or CMD64 Common Out as per
EDP/IDP.
If your DIA configuration Then go to
includes a BMD2 module step 7
does not include a BMD2 module step 10
7 If your configuration includes a BMD2 module, check power into the BMD2
Mux port (port 3 or port 5, depending on which BMD2 port you have
connected the CMD44 50 GHz, CMD96, or CMD64 to) with a power meter.
The measured power into the BMD2 must be within 1 dB of the CMD44,
CMD96, or CMD64 Common Out.
8 Measure the power at the Common Out (port2) of the BMD2. If the loss is
higher than 4 dB, clean and inspect the optical connectors. Repeat the
measurement and if the loss is still higher than 4 dB, replace the BMD2
module. Refer to the appropriate procedure in Fault Management - Module
9 Reconnect the fiber of BMD2 Common Out as per EDP/IDP.


Step Action
10 Using the PM features, measure the power present at the Line A Input (port 8)
of the amplifier circuit pack. Check that the input power is within 2 dB of the
power measured at the output of the CMD44, CMD96, CMD64, or BMD2 if
applicable.
11 Set the target gain for AMP-<shelf>-<AMP slot>-8 facility to 7 dB.
12 Verify the ORL at Line A Out (port 7) on the amplifier (PMs for Line A Out are
available as part of AMP port 8 PMs). If the value is lower than 28 dB, clean
all the optical connections from the Line A Out port.
Validating the fibering to the OPM in the Mux direction
a. Open a new PM Counts tab, select Performance -> Performance
Monitoring.
14 Use the PM feature on the amplifier circuit pack to verify that the power going
to the OPM is at least 17 dB lower than the power at the Line A out (port 7).
a. Select the already opened Performance Monitoring application from step
13, and open a new PM Counts tab.
b. Select the shelf.
e. If the power difference is more than 2 dB off of the expected value, clean
and verify the patch cord and the connectors between the Line A Mon
f. If you cannot correct the loss, contact your next level of support.


Step Action
next step.
from step 13.
17 Check power into the WSS Common In using OPTMON performance
monitoring measurements. The power into the WSS should be within 2 dB of
the power out of the amplifier.
18 Check power out of WSS with a power meter. Check that wavelength exists
on all switch ports.
The measured power must be within 2 dB of
(Power in - maximum WSS demux loss as per Table 4-3 on page 4-129)
loopback on one switch port of the WSS (between In SW<port x> and Out
SW<port x>). Make sure no other switch ports have fiber connected to them.
20 On the WSSOPM, for the wavelength you are testing:
— Set the Opaque state to “No”
— Set the Switch selector to the port which has the fiber loopback
— Set the Minimum Frequency and the Maximum Frequency to those
corresponding to the wavelength that you are testing.
— Set the Spectral Width to “37.5 GHz” (“59.0 GHz” if using an WLAi
transmitter for the test)
— Set the Target Loss to “0 dB”


Step Action
21 Check power into WSS switch port input using OPTMON PMs. The power
value must be within 1 dB of the measurement in step 18.
22 Check power into amplifier B using amplifier PMs. The power value must be
within 2 dB of
(Switch port input - expected WSS Mux port loss as per Table 4-3 on page
4-129)
23 Set the target gain for AMP-<shelf>-<AMP slot>-6 facility to 15 dB.
24 Verify the ORL at port 5 (Line B Out) on the amplifier (PMs for Line B Out are
available as part of AMP port 6 PMs).
If the value is lower than 28 dB, clean all the optical connections from the Line
B Out port.
Validating the fibering to the OPM in the DeMux direction
26 Use the PM feature on the amplifier circuit pack to verify that the power going
to the OPM is approximately 17 dB lower than the power at the Line B out
(port 5).
b. Select the shelf.
e. If the power difference is more than 2 dB off of the expected value, clean
and verify the patch cord and the connectors between the Line B Mon
port (port 1) and the OPM Monitor 1 port.
f. If you cannot correct the loss, contact your next level of support.


Step Action
next step.
from step 25.
28 If your configuration includes a BMD2 module, check power into the BMD2
Common In (port 1) with a power meter. The measured power into the BMD2
Common In must be within 1 dB of the amplifier output power. Reconnect the
fiber as per EDP/IDP.
29 Measure the power at the BMD2 Demux Out (port 4 or 6). If the measured
loss is higher than 4.5 dB, clean and inspect the optical connectors. Repeat
the measurement and if the loss is still higher than 4.5 dB, replace the BMD2
module. Refer to the appropriate procedure in Fault Management - Module
30 Check power into the CMD44 Common In (port 89), CMD96 Common In (port
193), or CMD64 Common In (port 129) with a power meter. The measured
power into the CMD44 or CMD64 Common In must be within 1 dB of the
amplifier or BMD2 output power.
31 Check power out of the CMD44, CMD96, or CMD64 Demux port of the test
wavelength with a power meter. If the measured loss is higher than:
• 8 dB for a CMD44 50 GHz
• 8.5 dB for an eCMD44 50GHz
• 7.6 dB for an eCMD44 100 GHz
• 7.6 dB for an CMD96 50 GHz
clean and inspect the optical connectors. Repeat the measurement and if the
loss is still higher than the values above, replace the CMD44, CMD96, or
CMD64 module. Refer to the appropriate procedure in Fault Management -
Module Replacement, 323-1661-545.


Step Action
32 On the WSSOPM, for the wavelength that you are testing:

• Select the required CHC facility:
— Set the Opaque state to “Yes”
WSS)
• Select the NMCC facility:
— Set the Target Loss to its default value (15 dB for WSS 50GHz 2x1 or
18 dB for all other WSS)
33 Remove the loopback on the WSS, put the CHC out-of-service (OOS), and
delete the CHC and NMCC facilities created in step 20.
Checking fibering between DIA and backbone WSS
34 Fiber the DIA WSS circuit pack to the other WSS circuit packs at the site in
accordance with the EDP/IDP. See Figure 4-32 on page 4-69 and Figure 4-33
on page 4-70 for examples.
35 Provision the inter-OTS WSS-WSS adjacencies to indicate to the 6500
software how the WSSs in the node are physically connected to one another.
Provision an adjacency on each WSS output port that is connected to another
WSS. To do so, log into each shelf and perform step 35 to step 42.
36 Select Configuration->Equipment & Facility Provisioning.
37 Select the adjacency that corresponds to one of the WSS output port
connected to another WSS
(ADJ-<shelf>-<slot>-<port> where port = 4, 6, 8,10, 12, 14, or 16)
Note: Port numbers shown are for WSSOPM 1x9.
38 Click on the Edit button.
The dialog box opens.
39 Set the Adjacency type to WSS.
40 Enter the Expected Far End Address and the Expected Far End Address
Format as per EDP/IDP (the Expected Far End Address must point at the
input port of the other WSS).
42 Repeat from step 37 if other WSS adjacencies must be provisioned on the
DIA WSS and backbone WSS circuit packs.
In a branching node with N directions, each DIA WSS should get N
adjacencies, one to each of the N directions. Each ROADM WSS should get
one adjacency to each DIA WSS.
43 Check power into the backbone WSS circuit pack(s) connected to the DIA
using OPTMON PMs. The measured power should be within 2 dB of the
power measured in step 18.


Step Action
44 Disconnect the TX.

45 Check power into the backbone WSS/RLA circuit pack(s) connected to the
DIA using OPTMON PMs. The ports should now be in LOS. If any one is not,
verify the physical fibering.
46 If there are Loss of Signal alarms present, clear the alarms by changing the
secondary state of the affected facilities to AINS.
47 If your configuration includes two CMD44 modules or a CMD44 with a
CMD96 or CMD64 module, repeat step 3 to step 12, step 17 to step 24, step
28 to step 33, and step 43 to step 46 to verify the second CMD44 module.
48 If the ROADM has no local CMD44 add/drop, then after the DIA testing is
complete, leave the TX connected to the DIA and test the ROADM using the
input to the WSS/RLA from the DIA. See Procedure 4-7, “Testing ROADM
channel access continuity”.
49 Set the AMP target gain for both AMP facilities to the value as per EDP/IDP.
—end—

Procedure 4-11
Testing a low channel count DIA configuration
Use this procedure to test a low channel count direction independent access
(DIA) configuration.
Figure 4-63 on page 4-174 illustrates an example of a low channel count DIA
configuration.
Prerequisites
• Have an optical power meter.
with at least one service layer source for the CCMD12.
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. Connect all optical
fibers within the low channel count DIA configuration. You must first
procedure.
CAUTION
DANGER
Risk of injury


CAUTION
Figure 4-63
Low channel count DIA configuration testing overview


Step Action

2 Using a patch cord that is known to be in good condition, put an optical
loopback between the DIA WSS Switch1 In (port 3) and Switch1 Out (port 4).
Make sure no other switch ports have fiber connected to them.
3 Select one of the transmitters to be connected to the new CCMD12. Edit the
OTMn facility of the transmitter to set the Tx power to maximum and Tx
wavelength to 1550.12 nm.
4 Connect the transmitter to the appropriate CCMD12 Ch In port. Connect the
receiver to the appropriate CCMD12 Ch Out port.
Ensure that this is the only transmitter and receiver connected to the
CCMD12. All other transmitters and receivers must be disconnected from the
CCMD12.
5 Make sure that the High Fiber Loss alarm is not present.
6 Retrieve the untimed OPT-OCH PM value for the OTMn facility of the
transmitter, in the Transmit direction.
CCMD12 Ch In port.
The fiber loss = step 6 value - step 7 value, which must be less than 1 dB. If
transmitter and the CCMD12 Ch In.
8 Retrieve the untimed OPR-OTS PM value for the OPTMON facility of the DIA
WSS Common In (port 21).
The gain = step 7 value - step 8 value, which must be greater than 5.6 dB. If
CCMD12 Common Out and the DIA WSS Common In. If the connectors and
optical patch fiber are in good condition, contact your next level of support to
WSS Switch1 In (port 3).
The loss = step 8 value - step 9 value, which must be less than 12 dB. If it is
not, clean the connectors and verify the loopback patch cord. If you are
10 Create a CHC facility on the DIA WSSOPM for the wavelength that you are
testing:
• Set the Opaque state to “No”
• Set the Switch selector to the port which has the fiber loopback
• Set the Minimum Frequency to “193.375 THz” and the Maximum
Frequency to “193.425 THz”.


Step Action

11 Create a NMCC facility on the DIA WSSOPM for the wavelength that you are
testing:
• Set the Center Frequency to “193.4 THz”
— Set the Spectral Width to “37.5 GHz” (or “59.0 GHz” for WaveLogic
Ai transponders in 56 GBaud mode)
• Set the Target Loss to “0 dB”
12 Retrieve the untimed OPIN-OTS PM value for the AMP facility of the CCMD12
Common In (port 25).
The loss = step 9 value - step 12 value, which must be less than 8.3 dB. If it
is not, clean the connectors and verify the optical patch fiber between the
WSS Common Out and the CCMD12 Common In. If you are unable to reduce
the loss, contact your next level of support to determine if any components
require replacement.
13 With an optical power meter, measure the power level at the WSS Monitor 1
port (port 1) for the CCMD12 under test. This value must be greater than or
equal to step 12 value + 9 dB.
14 Retrieve the untimed OPR-OCH PM value for the OTMn facility of the receiver
connected to the CCMD12 Ch Out, in the Receive direction.
The gain = step 12 value - step 13 value, which must be greater than 5.6 dB.
CCMD12 Ch Out and the receiver. If the connectors and optical patch fiber
are in good condition, contact your next level of support to determine if any
components require replacement.
15 Disconnect the transmitter and receiver from the CCMD12 Ch In and Ch Out
ports.
16 Edit the OTMn facility of the transmitter to set the Tx power to its default value
and Tx wavelength to 0 nm.
17 Delete the CHC and NMCC facilities created in step 10 and step 11.
18 Remove the optical patch cord between the DIA WSS Switch1 In (port 3) and
Switch1 Out (port 4).
accordance with the EDP/IDP.


Step Action

32 Repeat step 1 to step 31 for any other low channel count DIA.
33 If the ROADM has no local CMD44 add/drop, then after the DIA testing is
complete, leave the TX connected to the DIA and test the ROADM using the
input to the WSS/RLA from the DIA. See Procedure 4-7, “Testing ROADM
channel access continuity”.
—end—

Procedure 4-12
Testing a Colorless OADM configuration
Use this procedure to test a Colorless OADM configuration. A Colorless
OADM configuration is made up of the DIA OTS and the COADM OTS.
See the following figures for examples of the Colorless OADM configuration:
• “Intra-NE fiber connections at a Colorless OADM site” on page 4-73
• “Intra-NE fiber connections at a Colorless OADM site with CMD44 50GHz”
on page 4-74
• “Intra-NE fiber connections at a Colorless OADM site (up to 5 add/drop
banks and 5 degrees)” on page 4-75
• “Intra-NE fiber connections at a Colorless OADM site (with line facing
RLA)” on page 4-76
To test a Colorless OADM Direct Attach configuration (COADM [CCMD12 &

Flex-SMD] Direct Attach with WSS 1x9), see Procedure 4-13, “Connecting
intra-site fibers and testing a Colorless Direct Attach configuration (COADM
OTS connected to 1x9 or 1x2 WSS or RLA)”. To test a Colorless CMD Direct
Attach configuration, see Procedure 4-15, “Testing Colorless Direct Attach
with Direct Attach CMD44/CMD64 configurations (CCMD12/CMD44/CMD64
connected to 1x20 WSS)”.

The Colorless OADM configuration can support up to 5 degrees and 5 DIA

banks with 100% add/drop from each DIA bank to each degree. Multiple
permutations of the number of degrees/add drop banks are supported. When
supporting multiple degrees and DIA banks, the following apply:
port 9 and then decrementing) to connect the DIA (add/drop bank).
port 1 and then incrementing) to connect other degrees.
• MLA3/XLA/MLA2/MLA are supported for the DIA AMP. Gain settings for
the DIA AMP are provided by the planning tool.


ports of the backbone WSS. If connected to an amplified port of the
backbone WSS, the internal AMP of backbone WSS must be set with
Force Shutoff to Disabled and operating at Minimum Gain (which is 6 dB).
Note: For 96-channel support, use an MLA3 or XLA as DIA LIM and
NTK553GB SMD.
Prerequisites
“Retrieving performance monitoring data” procedure in Fault Management
- Performance Monitoring, 323-1851-520.
• You require an LC to LC patch cord (for testing steps that use a fiber
loopback).
with at least one service layer source for each installed CCMD12.
• You must first complete the NE commissioning and fibering before
performing this procedure. Perform this procedure only after you have
completed the intra-site fibers as detailed in Procedure 4-1, “Connecting
intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM sites”.
Connect all optical fibers within the Colorless OADM configuration.
Specifically:
— The COADM OTS and the DIA OTS must be provisioned. See Chapter
3, “Photonic layer provisioning procedures”.
— The High Fiber Loss Detection Alarm parameter in the Site Manager
Node Information application (System tab) must be set to Enabled for
the shelf containing a COADM OTS.
— The DIA LIM-SMD adjacencies for the Colorless OADM are
provisioned. See Procedure 3-2, “Provisioning adjacencies”.


CAUTION
Electrostatic discharge (ESD) can damage electrostatic-sensi-
tive devices. Always connect yourself to ground before you
handle an electrostatic-sensitive device.
DANGER
Risk of injury
Information, 323-1851-201.0, and those recommended by
your company at all times.
DANGER
Do not look directly into the optical beam. Invisible light can se-
verely damage your eyes.

• Ensure that the COADM shelf is either:
— TID consolidated with the backbone ROADM shelf
— temporarily provisioned as a primary shelf (for standalone testing)
Optical loopback tests can only be performed from a Primary shelf. In
addition, Photonic connections can only be added if the COADM and the
ROADM shelves are TID consolidated. The COADM shelf must be TID
consolidated with the ROADM shelf before full traffic continuity can be
tested.

Figure 4-64
Release 12.7
6500
Ch 01 Out
2
Ch 01 In
7
1
Ch 02 Out
4
Ch 02 In
Σ 12:1
3
COADM OTS
Ch 03 Out
6 Monitor Out
Ch 03 In 27
5
DIA OADM OTS

Ch 04 Out
8
Ch 04 In
7
Ch 05 Out
10
Ch 05 In

9
Ch 06 Out
12 Common In
Ch 06 In 25
11 WSS 50 GHz
PEC: NTK553FA/FC/LA
14 26
CCMD12
13 Ch 07 In
Monitor 1
Ch 08 Out 1
Colorless OADM testing overview
16 Monitor 2 OPM
Ch 08 In 2
15
MLA
18 PEC: NTK552BA 4
CCMD12
Ch 09 In Mon 1 (B Out) Switch1 In
17 3
1
Switch2 Out
LB In
Ch 10 Out 25
2 Common In 6
20 Switch8 In
Mon 2 (A Out) 21

Switch2 In
Ch 10 In 5
PEC: NTK508FA
26
19 Switch8 Out OSC B In
3
50 GHz SMD
2:8
23 8
22
9x1
4
Switch7 In
OSC A Out Switch3 In
Common In
LB Out
Ch 11 In 7
PEC: NTK553GA
24
21
Switch7 Out 9
Line A In Line A Out
Ch 12 Out 8 A 7 Switch4 Out
WSS 50 GHz
21 10
24 Switch6 In
Switch4 In
Σ 1:12
Ch 12 In 22 10 9
23

Switch6 Out
5 B 6 Switch5 Out
19
Switch5 In Line B Out Line B In 12
Switch5 In
20
Switch5 Out 11
OPM
Switch6 Out
17 14
Common Out
Switch4 In
Switch6 In
18
Switch4 Out 13
Dual-WSS
Σ 1:9
50 GHz 1x8
Common Out Switch7 Out
15 8 16
22
Up to 8 CCMD12s
Switch3 In Monitor 8
Ch 01 Out Switch7 In
2
16
Switch3 Out Monitor 7
7 15
Ch 01 In 6
1 13 Monitor 6
Ch 02 Out
Switch2 In 5 9:1
4 14 Monitor 5
Switch2 Out Switch8 Out (Drop1)
Ch 02 In 18
Σ 12:1
4
3
Monitor 4
8:2
11 Switch8 In (Add1)
Ch 03 Out
Switch1 In
Monitor 3
3 17
6 Monitor Out 12
Switch9 Out (Drop2)
2
Ch 03 In 27
Switch1 Out
5
Monitor 2 20
Ch 04 Out
1 Switch9 In (Add2)
Monitor 1 19
8
Ch 04 In
7
Ch 05 Out
10
Ch 05 In
9
Ch 06 Out
12 Common In
Ch 06 In 25
11
14 26
CCMD12
13 Ch 07 In
Ch 08 Out
16
Ch 08 In
15
Ch 09 Out
18
CCMD12
Ch 09 In
17
Ch 10 Out
20
Ch 10 In
PEC: NTK508FA
19
Ch 11 Out
22
Ch 11 In
21
Ch 12 Out
24
Σ 1:12
Ch 12 In
23

May 2020

Step Action
1 Ensure that the COADM shelf is either:

• TID consolidated with the backbone ROADM shelf
• temporarily provisioned as a primary shelf (for standalone testing)
Optical loopback tests can only be performed from a Primary shelf. In
addition, Photonic connections can only be added if the COADM and the
ROADM shelves are TID consolidated.
Testing Transponder and COADM OTS Connectivity
2 Select one add/drop bank for the following sequence of steps.
Note that you must perform the testing steps on all the add/drop banks as
follows:
• Perform the transponder loopback test on all the ports where
transponders are connected as part of your system.
• For add/drop banks where transponders are not connected as part of
your system, you will use the spare transponder on one port of the
respective CCMD12. After the test is completed on the CCMD12 port,
move the spare transponder to the next add/drop bank and repeat the
testing steps.
3 For the transponder you will be using for the tests, make sure the transmitter
is connected to the CCMD12 In port and the receiver is connected to the
CCMD12 Out port.
4 On the ADJ-TX of the CCMD12 port to which the transponder is connected,
make sure:
• the Far End Address is provisioned
• there is no cross-connection provisioned
5 Perform optical loopback testing through CCMD12 ADJ-TX. See the
323-1851-310. You can select multiple Transponders from different
CCMD12s for the optical loopback testing which are then tested sequentially.
The optical loopback testing checks:
• connectivity and fiber loss for the following:
— Transponder Tx to CCMD12
— CCMD12 to SMD
— SMD to CCMD12
— CCMD12 to Transponder Rx
• Target Trace Identifier (TTI) (if the Tx/Rx is capable of transmitting and
receiving TTI traces)
After the optical loopback testing is complete, pass/fail results are provided
against the ADJ-Tx port.


Step Action
6 If excessive losses are detected as part of the loopback test, clean and
inspect the optical connectors. See Table 4-10 for maximum loss values.
Table 4-10
CCMD12 and SMD maximum loss
Equipment PEC Max Mux loss (dB) Max Demux loss (dB)
CCMD12 NTK508FAE5 13.4 13.4
SMD 50 GHz 8x1 NTK553GA 2.2 dB to 7.3 dB 2.5 dB to 7.1 dB
SMD Flex 8x1 NTK553GB 2.5 dB to 7.1 dB 2.5 dB to 7.1 dB
9 Repeat step 2 to step 8 for all the other transponders that are connected to
CCMD12 In ports in the add/drop bank as part of your configuration.
Then perform the testing on the next add/drop bank where transponders are
connected.
If there are add/drop banks where transponders are not connected, use the
spare transponder to perform the testing on one of the ports of the add/drop
bank. Then move on to the next add/drop bank where transponders are not
connected.
Make sure that you have tested for each add/drop bank at least once.
Testing the COADM and DIA OTSs
10 Select one add/drop bank and one degree and perform step 11 to step 56 on
that branch.
loopback between the DIA WSS Switch1 In (port 3) and Switch1 Out (port 4).
Make sure no other switch ports have fiber connected to them.
Note: The high/low gain mode settings on an XLA must be verified with
link budget design or as planned by the network planning tool.


Step Action
12 If the COADM shelf Then go to

has been TID consolidated with the backbone ROADM step 13
has not been TID consolidated with the backbone step 15
ROADM (is temporarily a standalone Primary shelf)
13 Provision a photonic connection (you can select any wavelength) from any
CCMD12 input port where a transponder is connected, to the output port of
the line facing circuit pack. See the procedure on adding a photonic
• If SPLI is active, the selected wavelength is automatically pushed to the
Tx for tuning. A ‘Tx tuning in progress’ alarm will be raised for the OTMn
facility. This is expected. Wait until the alarm clears.
• If SPLI is not active, the Tx OTMn facility must be manually tuned to the
selected wavelength, and the Tx power must be manually adjusted to the
same power level as indicated by the “Actual Tx Power” field in the
CCMD12 Ch In port ADJ-Tx facility.
14 Under Performance->Performance Monitoring, PM Graph tab, plot the
graph for SMD port 10 (Common Out). Under the CHMON tab, for Graph
Type select “Channel powers per port” and check that the wavelength chosen
for the cross-connect is showing and is within +/-1 dB of -14 dBm.
If the value is not within the range, there may be an issue with the SMD.
Go to step 18.
15 Set up the transponder that is connected to the CCMD12 input port:
a. Set the center frequency (to match the NMCC center frequency that will
be set up in subsequent steps).
b. Set the transmit total power to -5 dBm.
c. Set the spectrum width for 35GBaud signal (effective bandwidth
<50GHz).


Step Action
16 On the SMD, in the mux and demux directions and for the wavelength that you
are testing:
— Set the Primary state to “OOS”.
— For the mux direction, set the Switch selector to the port to which the
CCMD12 Common Out is connected.
— For the demux direction, set the Switch selector to the port the
CCMD12 Common In is connected.
— Set the Channel Width to 50.00 GHz (ITU Grid)
— Set the Center Frequency to the center frequency set on the
transponder. The minimum and maximum frequency are
automatically derived.
— Click OK.
— Set the Spectral Width to “37.5 GHz”.
— Click OK.
17 On the DIA WSSOPM, for the wavelength you are testing:
— Set the Switch selector to the port which has the fiber loopback
— Set the Channel Width to 50.00 GHz (ITU Grid)
— Set the Center Frequency to the center frequency set on the
transponder. The minimum and maximum frequency are
automatically derived.
— Click OK.


Step Action

— Set the Spectral Width to “37.5 GHz”.
— Click OK.
18 Verify the loss between the SMD and the DIA amplifier:
• Select the ADJ-FIBER facility for SMD port 10 (Common Out).
• If the loss is more than 2 dB, check the fibering.
19 Retrieve the untimed ORL-OTS PM value for the AMP facility of the DIA
amplifier Line A Output (AMP-<shelf>-<slot>-8).
ORL value must be greater than 28 dB. If the value is lower than 28 dB, clean
all the optical connections from the Line A Out port.
20 Use the PM application to check that power is present at DIA WSSOPM port
2.
21 Put the AMP facility of DIA amplifier Line A Out (port 8) OOS and check that
there is no power at DIA WSSOPM port 2. If otherwise, check the fibering
from the DIA amplifier Monitor port 2 to the DIA WSSOPM port 2.
22 Put DIA amplifier Line A back IS.
23 Verify the loss between DIA amplifier Monitor port 2 and DIA WSSOPM port
2:
a. On the DIA amplifier, select the ADJ-FIBER facility, then select port 2
(Monitor 2 [A]), and check the fiber loss that is reported.
b. If the loss is more than 1 dB, check the fibering.
24 Select the AMP type and the facility AMP-<shelf>-<DIA AMP slot>-8. Click
25 Check ADJ-FIBER on port 7 of the DIA amplifier. If the loss is more than 2 dB,
check the fibering.
WSS Monitor port 2.
The loss = step 24 value - step 26 value, which must be less than 20 dB. If it
is not, make sure the fiber is connected to the correct ports. Clean the
connectors and verify the optical patch fiber between the DIA amplifier Mon
2 (port 2) and the DIA WSS Monitor port 2. If you are unable to reduce the
loss, contact your next level of support to determine if any components


Step Action
WSS Switch1 In (port 3).
is not, clean the connectors and verify the loopback patch cord. If you are
has been TID consolidated into the backbone ROADM step 29
has not been TID consolidated into the backbone ROADM step 30
(is temporarily a standalone Primary shelf)
29 On the DIA WSSOPM, open pixel for the CHC-shelf-slot-index:

a. Select the CHC in the Facility drop-down list and select the CHC with the
index associated with the wavelength being tested.
b. Set the Opaque state to “No”.
c. Set the Switch selector to the port which has the fiber loopback. Click OK.
d. Select the NMCC facility in the Facility drop-down list.
e. Set the Target Loss to 0 dB. Click OK.
30 Retrieve the untimed OPIN-OTS PM value for the AMP facility of the DIA
amplifier Line B In (port 6).
The loss = step 27 value - step 30 value, which must be less than 8 dB. If it is
not, clean the connectors and verify the optical patch fiber between the DIA
WSS Common Out and the DIA amplifier Line B In. If you are unable to
reduce the loss, contact your next level of support to determine if any
components require replacement.
31 Retrieve the untimed OPOUT-OTS PM value for the AMP facility of the DIA
amplifier Line B Output (AMP-<shelf>-<slot>-6).
WSS Monitor port 1.
is not, make sure the fiber is connected to the correct ports. Clean the
connectors and verify the optical patch fiber between the DIA amplifier
Mon 1 (port 1) and the DIA WSS Monitor port 1. If you are unable to reduce
the loss, contact your next level of support to determine if any components


Step Action
33 Retrieve the untimed ORL-OTS PM value for the AMP facility of the DIA
amplifier Line B Output (AMP-<shelf>-<slot>-6).
ORL value must be greater than 28 dB. If the value is lower than 28 dB, clean
all the optical connections from the Line B Out port.
SMD Common In (port 9).
The fiber loss = step 31 value - step 34 value, which must be less than 1 dB.
DIA amplifier Line B Out and the SMD Common In.
35 Remove the fiber loopback you added in step 11.
has been TID consolidated into the backbone ROADM step 37
has not been TID consolidated into the backbone ROADM step 52
(is temporarily a standalone Primary shelf)
accordance with the EDP/IDP.


Step Action

50 On the DIA WSSOPM:
a. Select the CHC in the Facility drop-down list and select the CHC with the
index associated with the wavelength being tested.
b. Set the Opaque state to “Yes”.
c. Select the NMCC facility in the Facility drop-down list.
d. Set the Target Loss to its default value (18 dB). Click OK.
51 Delete the photonic connection you provisioned in step 13. Go to step 56.
52 Restore the transponder set up in step 15 to the required settings.
53 On the SMD, in the mux and demux directions and for the wavelength that you
are testing:
— Set the Primary state to “IS”
— Set the Switch selector to the port to the default mux port (port 11)
(Mux direction) or the default demux port (port 12) (Demux direction i
— Click OK.
For details, see the procedure on editing a CHC facility in Part 1 of
• Select the required NMCC facility:
— Click OK.
For details, see the procedure on editing a NMCC facility in Part 1 of


Step Action
54 On the DIA WSSOPM, for the wavelength you are testing:

— Set the Switch selector to the port to the default (port 3)
— Click OK.
• Select the required NMCC facility:
— Click OK.
55 Delete the CHC and NMCC facilities created in step 16 and step 17.
56 Repeat step 11 to step 55 for the next untested add/drop bank and ROADM
pair. If there are no more untested add/drop banks, for the next untested
ROADM, use the last add/drop bank used for testing.
Note: If the COADM shelf is not TID consolidated with the ROADM shelf
(was temporarily a Primary shelf), the shelf must be TID consolidated with the
ROADM shelf before full traffic continuity can be tested.
57 If the ROADM has no local CMD add/drop, then after the Colorless OADM
testing is complete, leave the TX connected to the Colorless OADM and test
the ROADM using the input to the WSS/RLA from the DIA OTS. See “Testing
ROADM channel access continuity” on page 4-105.
Note: Do not perform “Testing ROADM channel access continuity” on page
4-105 if an Colorless OADM is being added to an existing deployed degree.
The ROADM has already been tested and you will not be able to loopback the
line ports without impacting traffic.
—end—

Procedure 4-13
Connecting intra-site fibers and testing a Colorless
Direct Attach configuration (COADM OTS connected
to 1x9 or 1x2 WSS or RLA)
Use this procedure to connect intra-site fibers for a Colorless Direct Attach
configuration (COADM OTS connected to 1x9 or 1x2 50 GHz WSS or RLA)
and to test the configuration. Figure 4-65 on page 4-196 illustrates a
configuration example with a 1x9 WSS. Figure 4-66 on page 4-197 illustrates
a configuration example with a 1x2 50 GHz WSS. Figure 4-67 on page 4-198
illustrates a configuration example with a 1x9 WSS and an OPS. Figure 4-68
on page 4-199 illustrates a configuration example with a 1x9 WSS and an
CMD44 50 GHz. Figure 4-69 on page 4-200 illustrates a configuration
example with a 1x9 WSS and amplified/unamplified CMD44 50 GHz. Figure
4-70 on page 4-201 illustrates a configuration example with a 1x9 WSS
without a COADM amplifier. Figure 4-71 on page 4-202 illustrates a
configuration example with a 1x9 WSS with a line facing RLA.
To connect intra-site fibers for a Colorless OADM configuration (made up of a

DIA OTS and a COADM OTS), see Procedure 4-1, “Connecting intra-site
fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. To test the
configuration, see Procedure 4-12, “Testing a Colorless OADM configuration”.
To connect intra-site fibers for a Colorless Direct Attach configuration

(CCMD12 connected to 1x20 WSS), see Procedure 4-14, “Connecting
intra-site fibers for a Colorless Direct Attach configuration
(CCMD12/CMD44/CMD64 connected to 1x20 WSS)”. To test the
configuration, see Procedure 4-15, “Testing Colorless Direct Attach with
Direct Attach CMD44/CMD64 configurations (CCMD12/CMD44/CMD64
connected to 1x20 WSS)”.



Connecting intra-site fibers and testing a Colorless Direct Attach configuration (COADM OTS
connected to 1x9 or 1x2 WSS or RLA)
Note that:
• The Colorless OADM Direct Attach configuration:
— is connected to:
– NTK553LA or NTK553LB (1x9 WSSOPM). These units can be
used in fixed-grid 50 GHz configurations or flexible grid.
– NTK553FA or NTK553FC (1x9 WSSOPM) in fixed-grid 50 GHz
configurations
– NTK553KA (1x2 WSSOPM) in fixed-grid 50 GHz configurations
— works with the following units for 96 channels:
– XLA and MLA3
– NTK553LA/LB
The following units support up to 88 channels:
– MLA and MLA2
– NTK553KA, NTK553FA/FC
— supports up to 96 channels in 50 GHz fixed grid mode
— is not supported on amplified drop ports of the 1x9 WSSOPM (Switch
8 and 9)
• The COADM OTS should have MLA3/XLA as LIM type (if required), along
with Flex SMD. The Flex SMD can operate in 50 GHz fixed grid mode and
flexible grid mode. Access AMP is not mandatory for COADM OTS (see
subsequent bullet).
Note: During initial system commissioning, Tx/Rx loopback is used to test
the fiber connectivity between Tx/Rx <-> CCMD12 <-> SMD. The “Testing
the COADM amplifier” part of the procedure is used only for testing the
connectivity between SMD <-> COADM amplifier.
• The COADM OTS can be connected directly to the amplified ports of the
backbone WSS (no COADM amplifier):
— In the mux direction, a custom minimum mux power output (MMPO)
must be manually provisioned on the COADM SMD to
-12dBm/12.5GHz using TL1. See “Provisioning photonic parameters”
on page 3-6 for details
— The backbone drop EDFA gain on the backbone WSS needs to be set
at Min Gain (to avoid power saturation on that AMP).


For configurations with colored CMDs (CMD44):

• The colored CMDs must be added to a degree using OTS-SLOT-SEQ
provisioning against the backbone WSS.
• The CMD44 must be provisioned in the same shelf as the backbone WSS
degree.
• The CMD44 50 GHz Blue and CMD44 50 GHz Red must be connected to
the ROADM OTS amplified drop ports (SW8 and SW9).
For configurations using a line facing RLA:

• up to 5 degrees are supported
• it is recommended to use:
decrementing) to connect the COADM (add/drop bank)
• a custom minimum mux power output (MMPO) must be manually
provisioned on the SMD using TL1 (ProvMMPO = -12.0 dBm, RBW =
12.5 GHz), see “Provisioning photonic parameters” on page 3-6 for
details. This provisioning must be done regardless of the ROADM OTS
control mode (fixed or flex).
• RLA paired with a SAM/ESAM/SRA is also supported.
For engineering rules, refer to 6500 Packet-Optical Platform Photonic Layer

Guide, NTRN15DA.
Note: This procedure assumes that the CCMDs are connected and
tested before any colored CMD44s are connected and tested. If the
colored CMD44s are connected first in a greenfield scenario, use
Procedure 4-7, “Testing ROADM channel access continuity” to test the
colored CMD44s.


Prerequisites
procedure on retrieving performance monitoring data in Fault
Management - Performance Monitoring, 323-1851-520.
• You must first complete the NE commissioning before performing this
procedure. Perform this procedure only after you have completed all
applicable procedures in this document up to, but not including, Procedure
4-1, “Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”. Specifically:
— Ensure that commissioning information has been entered.
— The COADM OTS and the ROADM OTS must be provisioned.
Note: The COADM amplifier, if required, must be explicitly provisioned as
part of the COADM OTS.
— The High Fiber Loss Detection Alarm parameter in the Site Manager
Node Information application (System tab) must be set to Enabled for
the shelf containing a COADM OTS.
— The MLA-SMD adjacencies for the Colorless OADM Direct Attach are
provisioned. See Procedure 3-2, “Provisioning adjacencies”.
with at least one service layer source for each installed CCMD12.


CAUTION
DANGER
Risk of injury
CAUTION



Figure 4-65
Colorless Direct Attach configuration (COADM OTS with 1x9 WSS) example


Figure 4-66
Colorless Direct Attach configuration (COADM OTS connected to 1x2 50 GHz WSS) example—
testing with transponder loopback


Figure 4-67
Colorless Direct Attach configuration (COADM OTS connected to 1x9 WSS and using OPS)
example


Figure 4-68
Colorless Direct Attach configuration (COADM OTS connected to 1x9 WSS with CMD44 and using
OPS) example


Figure 4-69
Colorless Direct Attach configuration (COADM OTS connected to 1x9 WSS with unamplified and
amplified CMD44s and using OPS) example


Figure 4-70
Colorless Direct Attach configuration (COADM OTS connected directly to amplified ports of
backbone WSS, no COADM amplifier) example


Figure 4-71
Colorless Direct Attach configuration (COADM OTS connected to RLA) example


Step Action
Connecting intra-site fibers for the configuration

1 Connect the intra-site fibers. See examples in the following illustrations:
• “Colorless Direct Attach configuration (COADM OTS with 1x9 WSS)
example” on page 4-196
• “Colorless Direct Attach configuration (COADM OTS connected to 1x2 50
GHz WSS) example—testing with transponder loopback” on page 4-197
• “Colorless Direct Attach configuration (COADM OTS connected to 1x9
WSS and using OPS) example” on page 4-198
WSS with CMD44 and using OPS) example” on page 4-199
WSS with unamplified and amplified CMD44s and using OPS) example”
on page 4-200
• “Colorless Direct Attach configuration (COADM OTS connected directly
to amplified ports of backbone WSS, no COADM amplifier) example” on
page 4-201
• “Colorless Direct Attach configuration (COADM OTS connected to RLA)
example” on page 4-202
Do not connect the COADM OTS amplifier Line B Out and Line A In fibers to
the ROADM OTS WSS at this point. You will provision for the
ROADM-to-COADM inter-OTS connection when you perform the optical
loopback testing steps later in this procedure (starting in step 2). You will
connect the respective fibers after you finish testing the COADM OTS and
then use the COADM OTS to test the ROADM OTS.
Testing the COADM configuration
Testing with transponder loopback to verify the CCMD12 - SMD fiber connectivity
2 Perform an Optical Loopback test on the CCMD12 and degree you are
323-1851-310.) See Figure 4-66 on page 4-197 for an example of testing with
transponder loopback at a Colorless Direct Attach node.
3 Make sure a transponder is connected to the CCMD12(s) with which you are
testing.
If the configuration is COADM OTS connected to 1x9 WSS and using OPS,
the transponder is connected to two CCMD12s through an OPS.
The transponder must have a valid SPLI and no CRS on the respective
CCMD12 ADJ-TX.


Step Action
CCMD12 to which the transponder is connected.
If the configuration is Then go to
using an OPS step 6
Note: These steps are not supported for Waveserver
Tx/Rx. For more details, see Waveserver User Guide,
323-4001-100.
not using an OPS step 10
6 In Site Manager, using the Protection Status screen, select the appropriate
Shelf and OPTMON OPS Facility and then operate a Lockout on the
protection member to make the OPS SW1 active.
This allows the optical manual loopback test to be performed between the
transmitter/receiver, through the OPS, to the CCMD12 connected on the OPS
SW1 path.
7 Perform step 10 to step 12, then release the Lockout on the Protection path.
Shelf and OPTMON OPS Facility, then operate a Forced switch on the
working member to make the OPS SW2 active.
SW2 path.
9 Perform step 10 to step 12, then release the Forced switch on the Working
path. Then go to step 15.
323-1851-310.
results. If the test has failed, disconnect the cable, clean and inspect the
connectors and reconnect.
For steps to inspect and clean connectors, see Installation - General
Information, 323-1851-201.0.
Clearing, 323-1851-543.


Step Action
13 If the COADM Then go to

includes an amplifier step 15
does not include an amplifier step 14
14 Connect the COADM OTS SMD Common Out and Common In fibers to the
amplified ports of the ROADM OTS WSS, where the inter-OTS adjacencies
are already provisioned in Procedure 3-2, “Provisioning adjacencies”.
Go to step 25.
Testing with COADM amplifier
loopback between the following ports. Make sure no other switch ports have
fiber connected to them.
• COADM OTS LIM Line B out (port 5) and Line A In (Port 8). As part of the
loopback, a pad is required (for example, for MLA/MLA2/MLA3/XLA, a
15 dB pad).
Note: The high/low gain mode settings on an XLA must be verified with
link budget design or as planned by the network planning tool.
16 Connect the selected transmitter to the CCMD12 (transmitter (Tx) goes to the
CCMD12 Ch In port, and receiver (Rx) to the adjacent Ch Out port).
17 Provision the Far End Address (FEA) between CCMD12 ADJ-Tx facility of the
Ch In port and the Tx OTMn ADJ facility
18 Provision a photonic connection for a wavelength available on the ROADM
degree (for example, 1550.12 nm) from the CCMD12 input port where the
transponder is connected to the output port of the line facing circuit pack. See
the procedure on adding a photonic connection in Configuration -
Connections Management, 323-1851-320.
• If SPLI is active, the selected wavelength is automatically pushed to the
Tx for tuning. A Tx tuning in progress alarm will be raised be raised for
the OTMn facility.
• If SPLI is not active, the Tx OTMn facility must be manually tuned to the
selected wavelength, and the Tx power must be manually adjusted to the
same power level as indicated by the “Actual Tx Power” field in the
CCMD12 Ch In port ADJ-Tx facility.


Step Action
19 For the MLA/MLA2/MLA3/XLA COADM amplifier circuit pack:

to 15 dB:
— Click Edit.
of this procedure.)
then click OK. Click Yes in the warning/confirmation message.
b. Verify the connectivity between SMD common-out and Line B input:
— Read the Line B input power value:
—In the Performance Monitoring application, select the appropriate
—Select the AMP Type and the facility AMP-<shelf>-<slot>-6 from
the Facility drop down list.
—Click Start Monitoring.
—In the PM table, read the Untimed OPIN-OTS value.
—Click Stop Monitoring.
— Read the SMD common-out power value:
—Select the OPTMON Type and the facility
OPTMON-<shelf>-<SMD slot>-10 from the Facility drop down
list.
—In the PM table, read the Untimed OPT-OTS value.
— Compare AMP Line B Untimed OPIN-OTS value with the SMD
OPTMON Untimed OPT-OTS value. The difference must be less than
1 dB. If the value is more than 1 dB, clean all the optical connections
from the Line B output port to the input of the pad.
Note: ORL detection is automatically disabled for an amplifier when facing a
WSS switch port.


Step Action
20 For the MLA/MLA2/MLA3/XLA COADM amplifier circuit pack:

to 15 dB:
— Click Edit.
procedure.)
then click OK. Click Yes in the warning/confirmation message.
the Line A output port to the input of the CCMD12.
c. Verify the connectivity between Line A output and SMD common-in:
— Read the Line A output power value:
—Select the AMP Type and the facility AMP-<shelf>-<slot>-8 from
the Facility drop down list.
—In the PM table, read the Untimed OPOUT-OTS value.


Step Action
— Read the SMD common-in power value:

—Select the OPTMON Type and the facility
OPTMON-<shelf>-<SMD slot>-9 from the Facility drop down list.
—In the PM table, read the Untimed OPR-OTS value.
— Compare AMP Line A Untimed OPOUT-OTS value with the SMD
OPTMON Untimed OPR-OTS value. The difference must be less
than 1 dB. If the value is more than 1 dB, clean all the optical
connections from the Line A output port to the input of the SMD.
21 Set the respective MLA/MLA2/MLA3/XLA Target Gain values back to the
values you recorded in step 19 (MLA3 Line B) and step 20 (MLA3 Line A).
22 Remove the optical patch cord between the COADM OTS LIM (Line B Out
(port 5) to Line A In (port 8) or the SMD/Flex SMD common output (port 26)
to common input (port 25).
24 Connect the COADM OTS amplifier Line B Out and Line A In fibers to the
ROADM OTS WSS/RLA, where the inter-OTS adjacencies are already
provisioned in Procedure 3-2, “Provisioning adjacencies”.
Validating CMD44 to WSS connectivity
Note: This procedure assumes that the CCMDs are connected and tested
before any colored CMD44s are connected and tested. If the colored
CMD44s are connected first in a greenfield scenario, use Procedure 4-7,
“Testing ROADM channel access continuity” to test the colored CMD44s.
25 Ensure that the CMD44/BMD2 and MLA/MLA2 (if required) are added to the
slot sequence. See the procedure on editing a slot sequence in Part 2 of
level.


Step Action

transmitter must be tuned to correct wavelength).
27 If there is Then go to
an amplifier between the CMD and the WSS step 28
no amplifier between the CMD and the WSS step 30
power into amplifier Line B input port (AMP OPIN-OTS).
The typical delta in measured power levels should be less than:
• CMD44/BMD2: 9 dB +/- 1 dB
• eCMD44/BMD2: 9 dB +/- 1 dB
• CMD44: 6 dB +/- 1 dB
• eCMD44: 6 dB +/- 1 dB
29 Retrieve the amplifier Line B output port (AMP OPOUT-OTS) and the power
into WSS switch port input (WSS OPTMON PM).
The expected fiber loss should be less than the high fiber loss threshold
(default 1.5 dB).
Go to step 31.
power into WSS switch port input (WSS OPTMON PM).
The expected fiber loss should be less than the high fiber loss threshold
(default 1.5 dB).
31 Repeat step 25 to step 30 for each CMD44.


Step Action

32 If the ROADM OTS degree is not yet tested for channel access continuity and
is currently not carrying any traffic, then after the testing is complete, leave
the transmitter connected to the Colorless Direct Attach and test the ROADM
using the input to the WSS/RLA from the COADM OTS or CMD44. See
Procedure 4-7, “Testing ROADM channel access continuity”.
Note: Do not perform Procedure 4-7, “Testing ROADM channel access
continuity” if an COADM or CMD44 is being added to an existing deployed
degree. The ROADM has already been tested and you will not be able to
loopback the line ports without impacting traffic.
—end—

Procedure 4-14
Connecting intra-site fibers for a Colorless Direct
Attach configuration (CCMD12/CMD44/CMD64
connected to 1x20 WSS)
Use this procedure to perform intra-site fiber connections for a Colorless
Direct Attach configuration (CCMD12/CMD44/CMD64 connected to 1x20
WSS, with or without an OPS).
Various configurations using different CMDs are supported as follows:

• CCMD12 - provides colorless directional configuration. Can operate in
fixed grid or flexible grid mode.
• CCMD12 and CMD64 - provides colorless directional configuration (when
using CCMD12). XLA or MLA3 used between CMD64 and FIM4. Can
operate in fixed grid or flexible grid mode (only flexible grid mode when
using CMD64).
• CCMD12 and CMD44 - provides colored directional configuration. Can
operate in fixed grid or flexible grid mode. BMD2 and a XLA or MLA3 used
between CMD44s and FIM4.
For configurations with colored CMDs (CMD44 or CMD64):

• The colored CMDs must be connected into the WSS high isolation ports
(an additional AMP is required).
• The colored CMDs must be added to a degree using TID-SLOT-SEQ
provisioning.
• The following configuration limitations apply:
— CMD44, CMD44/BMD2, or CMD64 must be provisioned in the same
shelf as the backbone WSS degree.
— The AMP associated with the CMD44, CMD44/BMD2, or CMD64 must
be on the same shelf as the CMD44, CMD44/BMD2, or CMD64.
• The add/drop amplifier gain values associated with colored CMD are set
and forget (recommended values (from planning tool) are manually
provisioned).
• The Mux AMP automatic power reduction gets automatically disabled.


Connecting intra-site fibers for a Colorless Direct Attach configuration (CCMD12/CMD44/CMD64
To connect intra-site fibers for:

• Colorless OADM configurations (made up of a DIA OTS and a COADM
OTS), see Procedure 4-1, “Connecting intra-site fibers for
TOADM/ROADM/DGFF/DIA/Colorless OADM sites”
• a Colorless Direct Attach configuration (COADM OTS connected to 1x9 or
1x2 WSS), see Procedure 4-13, “Connecting intra-site fibers and testing a
1x2 WSS or RLA)”
Prerequisites
subtending modules (for example, CMD, FIM).
CAUTION
DANGER
Risk of injury
• These configurations use MPO cables and connectors. For steps to:
— connect MPO cables, see the Installation technical publication specific
to the respective 6500 shelf type (in the procedure on routing
fiber-optic cables and electrical cables to circuit packs in the 6500
shelf)
— inspect and clean MPO connectors, see Installation - General


CAUTION
for any reason.

connection.
DANGER
Risk of injury
For a FIM Type 4 module and to respect the 1M laser
safety limit on the aggregate MPO output, the individual
input powers to the LC ports must be <=13 dBm.
• These configurations include Fiber Interconnect Modules (FIM). FIMs are

shipped with the following equipment pre-installed, including different
loopback modules. In addition to providing the optical loopback operation
required by applications that use the FIM, the loopback modules act as
dust caps for the optical ports. Do not remove the loopback modules
except as part of a fiber installation procedure. The FIM tray assembly
includes a bag of dust caps that must be put on any loopback connector
that is being removed and saved for future use. For more information, see
the Photonic passive modules table in Planning - Ordering Information,
323-1851-151.
— FIM Type 4 is shipped with the following equipment pre-installed:
– Duplex LC Loopback (SM) modules in each of the duplex LC
connector positions
– four MPO Loopback (APC, SM, 12 Fiber) modules pre-installed in
four of the FIM’s five MPO connectors
– Duplex LC Loopback (SM) modules in each of the duplex LC
connector positions
– dust caps on the rest of the FIM optical connectors
– MPO Loopback (APC, SM, 12 Fiber) modules in each of the MPO
connectors


Step Action
1 Identify your configuration type and connect the equipment as indicated in the
EDP/IDP.
For port numbers on FIMs, refer to the procedure on connecting fiber-optic
cables to circuit packs in the Installation technical publication specific to the
respective 6500 shelf type.
• Basic ROADM configuration with possible expansion—see:
— Figure 4-72 on page 4-217 (CCMD12s only)
— Figure 4-72 on page 4-217 (CMD64 and CCMD12s)
— Figure 4-74 on page 4-219 (CMD44s and CCMD12s)
and note the following:
— ROADM OTS contains WSS 1x20, MLA3/XLA-SRA/ESAM/SAM.
— CMDs (CCMD12s, CMD64/XLA/MLA3, or
CMD44/BMD2/XLA/MLA3) are not part of an OTS.
— CMDs (CCMD12s, CMD64/XLA/MLA3, or
CMD44/BMD2/XLA/MLA3) are connected via FIM Type 4.
— For configurations with up to 10 degrees, manual adjacency
provisioning or TID-SLOT-SEQ can be used on the Twin 1x20 WSS.
If using TID-SLOT-SEQ, MPO ports C and D must be dedicated for
local add/drop channels only and MPO ports A and B must be
dedicated for express traffic only. If using manual adjacencies, the
Twin 1x20 WSS, MPO ports A and B and MPO ports C and D can be
used for either local add/drop channels or express traffic.
— For configurations with between 10 degrees and 15 degrees, the
Twin 1x20 WSS, MPO ports A and B and MPO ports C and D can be
used for either local add/drop channels or express traffic.
— Each add/drop port can accommodate up to 5x CCMD12s (5x12
channels) and 1 x CMD64 (64 channels) or 2xCMD44 (2x44
channels) up to 128 channels (120 channels for CCMD12 only).
— Use FIM Type 5 only if the degree expands to more than one.
— Use FIM Type 6 only if the degree expands to more than five.
• Two-degree ROADM configuration—see Figure 4-75 on page 4-220 and
note the following:
— A single FIM Type 4 can be used for 2x degrees to have fulfill
add/drop channels per degree
— Use FIM Type 5 to interconnect degree 1 and 2.
— Figure 4-75 on page 4-220 shows configuration using CCMD12s
only. Configurations using CMD64s or CMD44s use same FIM
configurations.


Step Action
• Two-degree ROADM configuration with possible future expansion—see

Figure 4-76 on page 4-221 and note the following:
— A single FIM Type 4 can be used for two degrees to have full fill
add/drop channels per degree.
— Use FIM Type 5 to interconnect degree 1 and 2.
— Use FIM Type 6 only if the degree expands to more than five.
configurations.
• 4-degree ROADM configuration with full fill per degree with two FIM Type
4 and one FIM Type 5—see Figure 4-77 on page 4-222. Figure 4-77 on
page 4-222 shows configuration using CCMD12s only. Configurations
using CMD64s or CMD44s use same FIM configurations.
• For five to ten degree expansions, see Figure 4-78 on page 4-223 and
note the following:
— Degrees 1 to 5 are interconnected through the first FIM Type 5.
— Degrees 6 to 10 are interconnected through a second FIM Type 5.
— Degrees 1 to 5 and degrees 6 to10 are interconnected through the
FIM Type 6 (5x5 MPO).
configurations.
• For a full-filled ten-degree ROADM node, see Figure 4-79 on page 4-224.
Figure 4-79 on page 4-224 shows configuration using CCMD12s only.
Configurations using CMD64s or CMD44s use same FIM configurations.
• For eleven to fifteen degree expansions, see Figure 4-80 on page 4-225
and note the following:
— Degrees 1 to 5 are interconnected through the first FIM Type 5.
— Degrees 6 to 10 are interconnected through a second FIM Type 5.
— Degrees 11 to 15 are interconnected through a third FIM Type 5.
— Degrees 1 to 5 and degrees 6 to10 are interconnected through the
first FIM Type 6 (5x5 MPO).
— Degrees 1 to 5 and degrees 11 to15 are interconnected through a
second FIM Type 6 (5x5 MPO).
— Degrees 6 to 10 and degrees 11 to15 are interconnected through a
third FIM Type 6 (5x5 MPO).
— interconnection of degrees without any local add/drops is allowed.


Step Action
— you must manually provision the EFEA on the physical adjacencies

of the WSS 1x20 and the FIMs, see “Provisioning adjacencies” on
page 3-14.
— shows configuration using CCMD12s only. Configurations using
CMD64s or CMD44s use same FIM configurations.
• For an example of a configuration using OPS, see Figure 4-81 on page
4-226.
—end—

Figure 4-72
Configuration example—basic ROADM configuration with possible expansion (CCMD12)

Figure 4-73
Configuration example—basic ROADM configuration with possible expansion (CCMD12 and
CMD64 75 GHz)

Figure 4-74
Configuration example—basic ROADM configuration with possible expansion (CCMD12 and
CMD44)

Figure 4-75
Configuration example—two-degree ROADM

Figure 4-76
Configuration example—two-degree ROADM with possible future expansion

Figure 4-77
Configuration example—four-degree ROADM with full-fill per degree with two FIM Type 4 and one
FIM Type 5

Figure 4-78
Configuration example—five to ten-degree expansion

Figure 4-79
Configuration example—full-filled ten-degree ROADM

Figure 4-80
Configuration example—eleven to fifteen-degree expansion

Figure 4-81
Configuration example—CCMD12 connected to 1x20 WSS and using OPS

Procedure 4-15
Testing Colorless Direct Attach with Direct Attach
CMD44/CMD64 configurations
(CCMD12/CMD44/CMD64 connected to 1x20 WSS)
Use this procedure to test Direct Attach configurations
(CCMD12/CMD44/CMD64 connected to 1x20 WSS), where light from
transmitting subtending equipment is available. The procedure applies for
configurations with and without OPS between the transponder and the CMD.
This test verifies the optical continuity and checks for reflection-related
problems. This procedure does not optimize the channels for traffic.
To test:
• Colorless OADM configurations (made up of a DIA OTS and a COADM
OTS), see Procedure 4-12, “Testing a Colorless OADM configuration”
• Colorless Direct Attach configurations (COADM OTS connected to 1x9 or
1x2 WSS), see Procedure 4-13, “Connecting intra-site fibers and testing a
1x2 WSS or RLA)”
These configurations use MPO cables and connectors. For steps to:
• inspect and clean MPO connectors, see Installation - General Information,
323-1851-201.0
CAUTION
removing the MPO cable from its original packaging or if the
MPO cable has been removed from the faceplate for any
reason.

connection.


Testing Colorless Direct Attach with Direct Attach CMD44/CMD64 configurations
These configurations include Fiber Interconnect Modules (FIM). FIMs are

required by applications that use the FIM, the loopback modules act as dust
caps for the optical ports. Do not remove the loopback modules except as part
of a fiber installation procedure. The FIM tray assembly includes a bag of dust
caps that must be put on any loopback connector that is being removed and
saved for future use. For more information, see the Photonic passive modules
table in Planning - Ordering Information, 323-1851-151.
• FIM Type 4:
connector positions
• FIM Type 5:
— four MPO Loopback (APC, SM, 12 Fiber) modules pre-installed in four
of the FIM’s five MPO connectors
connector positions
— dust caps on the rest of the FIM optical connectors
• FIM Type 6:
— MPO Loopback (APC, SM, 12 Fiber) modules in each of the MPO
connectors
— dust caps on the rest of the FIM optical connectors
Note: This procedure assumes that the CCMDs are connected and
tested before any colored CMD44/CMD64s are connected and tested. If
the colored CMD44/CMD64s are connected first in a greenfield scenario,
use Procedure 4-7, “Testing ROADM channel access continuity” to test
the colored CMD44/CMD64s.
Prerequisites
the equipment associated with one OTS. Full traffic continuity testing can
proceed only after the system is complete. It is recommended that you
perform the continuity test with at least one service layer source for each
installed CMD.


• You must first complete the NE commissioning, photonic layer

provisioning including TID slot sequence provisioning, and fibering before
performing this procedure. Refer to:
— Chapter 2, “Nodal SLAT procedures”
— Chapter 3, “Photonic layer provisioning procedures”
— Procedure 4-14, “Connecting intra-site fibers for a Colorless Direct
Attach configuration (CCMD12/CMD44/CMD64 connected to 1x20
WSS)”
CAUTION
DANGER
Risk of injury
CAUTION
DANGER
Risk of injury
For a FIM Type 4 module and to respect the 1M laser safety
limit on the aggregate MPO output, the individual input
powers to the LC ports must be <=13 dBm.
Step Action


Step Action

testing.
Power parameter.
Untimed parameter.
Testing the interconnects using the Connection Validation application
9 For a configuration with 11 to 15 ROADM degrees, ensure that the expected
far end addresses (EFEAs) are provisioned for the WSS to FIM connections
(see Procedure 3-2, “Provisioning adjacencies”).


Step Action
11 Make sure that the Dark Fiber Loss Management system parameter is
Security, 323-1851-301.)
completed.
Clearing, 323-1851-543.
The Colorless CMD Direct Attach equipment uses MPO cables and
connectors. For steps to:
CAUTION
for any reason.

connection.

• WSSOPM − MPO loopback connector
• CCMD12 − MPO loopback connector


Step Action
Testing with transponder loopback (CCMD12 only)

15 Perform an Optical Loopback test on the CCMD12 and degree you are
323-1851-310.)
See Figure 4-82 on page 4-233 for an example of testing with transponder
loopback at a CDA node. For an example of a configuration using OPS, see
Figure 4-81 on page 4-226.
16 Make sure a transponder is connected to the CCMD12 with which you are
testing. The transponder must have a valid SPLI and no CRS on the
respective CCMD12 ADJ-TX.
If the configuration is using OPS, the transponder is connected to two
CCMD12s through an OPS.
CCMD12 to which the transponder is connected.
If the configuration is Then go to
using an OPS step 19
Note: These steps are not supported for Waveserver
Tx/Rx. For more details, see Waveserver User Guide,
323-4001-100.
not using an OPS step 23
Shelf and OPTMON OPS Facility and then operate a Lockout on the
protection member to make the OPS SW1 active.
SW1 path.
20 Perform step 23 to step 27, then release the Lockout on the Protection path.
Shelf and OPTMON OPS Facility, then operate a Forced switch on the
working member to make the OPS SW2 active.
SW2 path.
22 Perform step 23 to step 27, then release the Forced switch on the Working
path. Then go to step 33.


Figure 4-82
CDA—testing with transponder loopback (example not using OPS)


Step Action

323-1851-310.
results. If the test has failed, refer to the ‘Reason’ column in the Validation
Summary table and take further action based on the information provided.
Clearing, 323-1851-543. If required, disconnect the MPO cable, clean and
inspect the connectors and reconnect. For steps to:
CAUTION
for any reason.

connection.
(See Table 4-11 on page 4-234 for maximum CCMD12 and WSS Flex
C-Band w/OPM 20x1 loss values and Table 4-12 on page 4-235 for maximum
FIM loss values.)
Table 4-11
CCMD12 and WSS Flex C-Band w/OPM 20x1 maximum loss
WSS Flex C-Band w/OPM 20x1 NTK553MA 8.2 8.2
CCMD12 NTK508FAE5 17 17


Step Action
Table 4-12
Fiber Interconnect Modules (FIM) maximum loss
Module PEC Maximum insertion loss Maximum insertion loss
Add or Drop: Add or Drop:
MPO-MPO connections MPO-LC connections
FIM Type 4 NTK504CD not applicable 1.1 dB
FIM Type 5 NTK504CE 1.4 dB 1.1 dB
FIM Type 6 NTK504CF 1.4 dB not applicable
Validating CMD44/CMD64 to WSS connectivity

Note: This procedure assumes that the CCMDs are connected and tested
before any colored CMD44/CMD64s are connected and tested. If the colored
CMD44/CMD64s are connected first in a greenfield scenario, use
Procedure 4-7, “Testing ROADM channel access continuity” to test the
colored CMD44/CMD64s.
28 Ensure that the CMD44/BMD2 or CMD64 and MLA3/XLA are added to the
TID slot sequence or have EFEA ADJs provisioned. See the procedure on
editing a slot sequence in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
level.
transmitter must be tuned to correct wavelength/frequency).


Step Action
power into amplifier Line B input port (AMP OPIN-OTS).
The typical delta in measured power levels should be less than:
• CMD64: 5 dB +/- 1 dB
• CMD44/BMD2: 9 dB +/- 1 dB
• eCMD44/BMD2: 9 dB +/- 1 dB
• CMD44: 6 dB +/- 1 dB
• eCMD44: 6 dB +/- 1 dB
31 Retrieve the amplifier Line B output port (AMP OPUT-OTS) and the power
into WSS switch port input (WSS OPTMON PM). The expected fiber loss
should be less than 1.1 dB (as in Table 4-12 for FIM4).
32 Repeat step 28 to step 31 for each CMD44/CMD64.
34 On the transponder connected to the CCMD12/CMD44/CMD64 with which
you are testing:
the transmitter to the appropriate CCMD12/CMD44/CMD64 port.
35 Provision a photonic connection (you can select any wavelength for CCMD12
or the appropriate wavelength for CMD44/CMD64) from the
CCMD12/CMD44/CMD64 input port where the transponder is connected to
the output port of the line facing circuit pack. See the procedure on adding a
photonic connection in Configuration - Connections Management,
323-1851-320.
MLA3 20 dB
SRA/ESAM/SAM 20 dB


Step Action

appropriate photonic shelf from the Shelf drop-down list and select the CDA
ROADM WSSOPM in the equipment table.
• Select CHC in the Facility drop down list and select the CHC with the
If Then go to
to 17 dB:
— Click Edit.
of this procedure.)
then click OK.


Step Action
to 20 dB:
— Click Edit.
procedure.)
then click OK.
the amplifier output), clean all the optical connections from the Line A
output port to the input of the CCMD12/CMD44/CMD64.
Go to step 44.
42 If an XLA is present, perform the following on the XLA:
to 20 dB and the Gain Mode to HIGH (You will be instructed to set the XLA
AMP facility OOS to modify the Gain Mode.):


Step Action
— Click Edit.
•Click Apply.
•Click OK.
c. Edit the Line A AMP facility (AMP-<shelf>-<slot>-8) to set the target gain
— Click Edit.
•Click Apply.


Step Action

•Click OK.
d. Verify the ORL at Line A output:
A output port to the input of the CCMD12/CMD44/CMD64.
approximately 17 dB (for an MLA3 or XLA) lower than the power at the Line A
Out (port 7).
If an OSC Filter (NTK504BA) is present, you must also factor in its insertion
loss of 1.2 dB.



Step Action
next step.
from step 44.
B out (port 5).



Step Action
next step.
from step 44.
If Then
respectively. Set the facilities back to IS.

purpose of this testing only.
53 Remove the loopback you added in step 36.
54 Remove the padding you added in step 37.
—end—

Procedure 4-16
Testing a line amplifier node
Use this procedure to test a Line Amplifier node.
With no input connected, the pre-amplifier is set to the no shutoff mode (by
setting the ALSO Disabled parameter to True). In the no shutoff mode the
amplifier transmits an amplified spontaneous emission (ASE) broadband
noise that can be used to measure the reflectance and the loss of the
mid-stage connections.
CAUTION
DANGER
Risk of injury
CAUTION
Prerequisites
There should be no line fibers connected. The only fibers connected are the
intra-NE fibers.


Figure 4-83
Overview of Line Amplifier node testing for configurations using SLA/MLAx and LIM circuit packs


Figure 4-84
Overview of Line Amplifier node testing for configurations using
SRA/ESAM/SAM+XLA+SRA/ESAM/SAM circuit packs
Dir. 2
B B A
SRA/ SRA/
ESAM/ ESAM/
XLA
SAM SAM
1 2
A A B
Dir. 1
Legend
= Attenuator
= DSCM
Figure 4-85
Overview of Line Amplifier node testing for configurations using ESAM+MLAx+ESAM circuit
packs


Figure 4-86
Overview of Line Amplifier node testing for configurations using ESAM+MLAx+MLAx+ESAM
circuit packs
Figure 4-87
Overview of Line Amplifier node testing for configurations using ESAM+MLAx+MLAx circuit
packs


Figure 4-88
Overview of Line Amplifier node testing for configurations using
ESAM/SAM+XLA+XLA+ESAM/SAM circuit packs


Step Action

circuit pack, on the 2xOSC circuit pack, or the SRA/ESAM/SAM circuit packs
as applicable.
testing.
Power parameter.
Untimed parameter.
(dBm) read in step 4> + 5 (if 5 dB pad fitted in step 2)
8 Repeat step 2 to step 7 for the other OSC-1 (dual 2xOSC configuration), the
OSC-2 (single 2xOSC configuration, ESAM+MLAx, or
SRA/ESAM/SAM+XLA configuration).


Step Action

If you are testing a line amplifier configuration Then go to
equipped with SLA/MLAx+LIM circuit packs step 10
equipped with SRA/ESAM/SAM and XLA circuit packs step 36
equipped with ESAM+MLAx+ESAM circuit packs step 62
equipped with ESAM+MLAx+MLAx+ESAM circuit packs step 88
equipped with ESAM+MLAx+MLAx circuit packs step 116
equipped with ESAM/SAM+XLA+XLA+ESAM/SAM circuit step 139
packs
Testing mid-stage loss in direction 1

10 Start with the line facing circuit pack with the Line A amplifier (SLA, MLA,
MLA2, MLA2 w/VOA, or MLA3). For convenience, call it line facing circuit
pack 1. See Figure 4-83 on page 4-244 for examples of line amplifier node
testing.
11 If line facing circuit pack 2 is an SLA or LIM, put an optical loopback with
10 dB padding between Line B Out (port 5) and Line A In (port 8) of line facing
circuit pack 2. If line facing circuit pack 2 is an MLA/MLA2/MLA2
w/VOA/MLA3, no loopback is required.
12 Put the Line A amplifier facility of line facing circuit pack 1 in no shutoff mode
as follows.
OOS-AUMA.
• Set the AMP facility parameter ALSO Disabled to True.


Step Action
13 Using PM, observe the ORL at the output of the Line A amplifier facility of line
facing circuit pack 1.
• Select Performance->Performance Monitoring to open the PM screen.
• Review the ORL-OTS Untimed parameter. The measurement in the
Untimed bin should be greater than 28 dB. When DSCMs are placed after
the amplifier output, the ORL value should be greater than 24 dB.
If the reading is less than the minimum ORL required, clean all fiber
connections at the amplifier output (including connections to a DSCM)
and verify that the patch fiber and attenuator are clean and in good
working order.
• If cleaning fiber connections does not correct reflectance problems,
contact your next level of support.
14 In the Performance Monitoring window:
If line facing circuit pack 2 is Then go to
MLA, MLA2, MLA2 w/VOA, or MLA3 step 16
SLA or LIM step 17


Step Action
16 In Site Manager, select the appropriate LIM from the Equipment and Facilities
Provisioning window.
• Ensure the Primary State of the Line B amplifier of line facing circuit pack
2 is not OOS-AUMA.
• Select Performance -> Performance Monitoring.
• Select the MLA/MLA2/MLA2 w/VOA/MLA3 Line B AMP facility of line
facing circuit pack 2 (AMP-<shelf>-<slot>-6) from the Facility drop down
list.
• Record the OPIN-OTS Untimed parameter.
• Calculate the mid-stage loss:
Mid-stage loss = <Line A output power (dBm) read in step 14> - <adjacent
Line B input power (dBm) read in this step>
• Compare the mid-stage loss with the expected range by adding up the
pad and DSCM loss as indicated in Table 4-5 on page 4-131. If the loss
falls below this range, increase the pad attenuation. If the loss exceeds
this range, clean and inspect all connectors and patch cords in the
mid-stage access, then go to step 23.
17 In the Performance Monitoring window,
• Select the OPTMON facility associated with port 6 of line facing circuit
pack 2 (OPTMON-<shelf>-<slot>-6).
• Record the OPR-OTS Untimed parameter.
Line B input power (dBm) read in this step>.
mid-stage access.
SLA, MLA, MLA2, MLA2 w/VOA, or MLA3 step 23
LIM step 19


Step Action
Testing mid-stage loss in direction 2 if line facing circuit pack 2 is a LIM circuit pack
19 In the Performance Monitoring window, select the OPTMON Type and the
facility for the LIM of line facing circuit pack 2 (OPTMON-<shelf>-<slot>-8)
from the Facility drop down list. Record the OPR-OTS Untimed parameter.
SLA step 22
1 is not OOS-AUMA.
list.


Step Action

mid-stage access.
23 Put the Line A amplifier of line facing circuit pack 1 back in normal mode by
setting the AMP facility parameter ALSO Disabled to False.
24 If line facing circuit pack 2 is a LIM or SLA, remove the loopback between Line
B Out (port 5) and the Line A In (port 8) of line facing circuit pack 2.
If line facing circuit pack 2 is Then
SLA, MLA, MLA2, MLA2 w/VOA, or go to step 26
MLA3
LIM you have completed this procedure
Testing mid-stage loss in direction 2 if line facing circuit pack 2 is not a LIM circuit pack
26 If line facing circuit pack 1 is an SLA, put an optical loopback with 10-dB
padding between Line B Out (port 5) and Line A In (port 8) of line facing circuit
pack 1. If line facing circuit pack 1 is an MLA/MLA2/MLA2 w/VOA/MLA3, no
loopback is required.


Step Action
as follows:
OOS-AUMA.
• Select Performance->Performance to open the PM screen.
working order.


Step Action

SLA step 32
1 is not OOS-AUMA.
list.
mid-stage access.
The “Automatic Shutoff Disabled” alarm clears.


Step Action
34 If line facing circuit pack 1 is an SLA, remove the loopback between Line B
Out (port 5) and the Line A In (port 8) of line facing circuit pack 1.
35 Connect all the line fibers as per EDP/IDP.
Testing a line amplifier node equipped with SRA/ESAM/SAM and XLA circuit packs
See Figure 4-84 on page 4-245 for an example of node testing of this
configuration. Testing starts with direction 1 by putting a loopback on
SRA/ESAM/SAM 2 and putting the XLA Line A amplifier in the no shutoff
mode. Testing completes with direction 2 by putting a loopback on
SRA/ESAM/SAM 1 and putting the XLA Line B amplifier in the no shutoff
mode.
Note: DSCMs are not supported when using SRA line facing circuit packs.
Direction 1 (Loopback on SRA/ESAM/SAM 2)
36 Put an optical loopback with 20 dB padding between Line B Out (port 5) and
Line A In (port 8) of SRA/ESAM/SAM 2.
37 Put the Line A amplifier facility of the XLA in no shutoff mode as follows:
OOS-AUMA.
In the case of SRA and ESAM, the following alarms are raised:
• “Line A Input OTDR Trace High Reflection Detected”
• “Line A Input OTDR Trace High Loss Detected”
• “OTDR Trace In Progress”
This is expected behavior when the SRA/ESAM line fibers are not connected.
For detailed information on Optical Time Domain Reflectometry (OTDR),
refer to:
• the 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA
• the chapter on OTDR trace in Configuration - Provisioning and Operating,
Part 2 of 2, 323-1851-310
• the procedures on OTDR alarms in Fault Management - Alarm Clearing,
Part 2 of 2, 323-1851-543


Step Action
Note that OTDR requires at least 20 km of optical fiber to verify the fiber for
reflection or loss. An OTDR trace run on short fiber may fail due to loss or
reflection.
The following steps require readings on the XLA. Note that the XLA power is
squelched when the OTDR trace is running. The OTDR trace must complete
before you can get a reading on the XLA.
38 Record the following XLA AMP facility parameters (you will be instructed in
step 46 to put them back to the values you are recording in this step):
• AMP Mode
• Target Power
39 After the OTDR trace has completed:
a. Put the XLA AMP facility out-of-service.
b. Set the XLA AMP facility AMP Mode to Power.
c. Set the Target Power to 9.5 dBm. (In the no shutoff mode, the amplifier
will produce broadband noise. In this mode, the amplifier output power
may be different from 9.5 dBm.)
d. Put the XLA AMP facility back in-service.
40 Using PM, observe the ORL at the output of the Line A amplifier facility of the
XLA:
working order.


Step Action

• Select the OPTMON facility associated with port 6 of SRA/ESAM/SAM 2
(OPTMON-<shelf>-<slot>-6).
mid-stage access.
43 In the Performance Monitoring window, select the OPTMON Type
(ESAM/SAM) or RAMAN Type (SRA) and the facility for the SRA/ESAM/SAM
2 (OPTMON-<shelf>-<slot>-8 or RAMAN-<shelf>-<slot>-8) from the Facility
drop down list. Record the OPR-OTS Untimed parameter.
• Select the OPTMON facility associated with port 6 of the XLA
XLA B input power (dBm) read in this step>.
mid-stage access.
45 Put the Line A amplifier of the XLA back in normal mode by setting the AMP
facility parameter ALSO Disabled to False.
46 Put the XLA AMP facility parameters back to the values you recorded in step
38, as follows:
a. Put the facility out-of-service.
b. Put the AMP Mode and the Target Power of the facility back to the values
you recorded in step 38.
c. Put the facility back in-service.


Step Action
47 Remove the loopback between Line B Out (port 5) and the Line A In (port 8)
of SRA/ESAM/SAM 2.
In the case of SRA and ESAM, the following alarms clear:
Direction 2 (Loopback on SRA/ESAM/SAM 1)
Line A In (port 8) of SRA/ESAM/SAM 1.
50 Put the Line B amplifier facility of the XLA in no shutoff mode as follows.
information of the Line B AMP facility (port 6).
• Ensure the primary state of the Line B AMP facility (port 6) is not
OOS-AUMA.
In the case of SRA and ESAM, the following alarms are raised:
This is expected behavior when the SRA/ESAM line fibers are not connected.
For detailed information on Optical Time Domain Reflectometry (OTDR),
refer to:
Part 2 of 2, 323-1851-310
Part 2 of 2, 323-1851-543


Step Action
reflection.
The following steps require readings on the XLA. Note that the XLA power is
squelched when the OTDR trace is running. The OTDR trace must complete
before you can get a reading on the XLA.
51 Record the following XLA AMP facility parameters (you will be instructed in
step 59 to put them back to the values you are recording in this step):
• AMP Mode
• Target Power
a. Put the XLA AMP facility out-of-service.
b. Set the XLA AMP facility AMP Mode to Power.
d. Put the XLA AMP facility back in-service.
53 Using PM, observe the ORL at the output of the Line B amplifier facility of the
XLA:
working order.


Step Action

• Select the OPTMON facility associated with port 6 of SRA/ESAM/SAM 1
Mid-stage loss = <Line B output power (dBm) read in step 54> - <adjacent
mid-stage access.
56 In the Performance Monitoring window, select the OPTMON Type
(ESAM/SAM) or RAMAN Type (SRA) and the facility for the SRA/ESAM/SAM
1 (OPTMON-<shelf>-<slot>-8 or RAMAN-<shelf>-<slot>-8) from the Facility
drop down list. Record the OPR-OTS Untimed parameter.
• Select the OPTMON facility associated with port 8 of the XLA
XLA A input power (dBm) read in this step>.
mid-stage access.
58 Put the Line A amplifier of the XLA back in normal mode by setting the AMP
59 Put the XLA AMP facility parameters back to the values you recorded in step
51, as follows:


Step Action
of SRA/ESAM/SAM 1.
In the case of SRA and ESAM, the following alarms clear:
Testing a line amplifier node equipped with ESAM+MLAx+ESAM circuit packs
configuration. Testing starts with direction 1 by putting a loopback on ESAM 2
and putting the MLAx Line A amplifier in the no shutoff mode. Testing
completes with direction 2 by putting a loopback on ESAM 1 and putting the
MLAx Line B amplifier in the no shutoff mode.
Direction 1 (Loopback on ESAM 2)
Line A In (port 8) of ESAM 2.
63 Put the Line A amplifier facility of MLAx in no shutoff mode as follows:
OOS-AUMA.
For ESAM, the following alarms are raised:
This is expected behavior when the ESAM line fibers are not connected. For
detailed information on Optical Time Domain Reflectometer (OTDR), refer to:
Part 2 of 2, 323-1851-310
Part 2 of 2, 323-1851-543


Step Action
reflection.
The following steps require readings on the MLAx. Note that the MLAx power
is squelched when the OTDR trace is running. The OTDR trace must
complete before you can get a reading on the MLAx.
64 Record the following MLAx Line A AMP facility parameters (you will be
instructed in step 72 to put them back to the values you are recording in this
step):
• AMP Mode
• Target Power
a. Put the MLAx AMP facility out-of-service.
b. Set the MLAx AMP facility AMP Mode to Power.
d. Put the MLAx AMP facility back in-service.
66 Using PM, observe the ORL at the output of the Line A amplifier facility of the
MLAx:
• Select the AMP Type and the facility AMP<shelf>-<slot>-8 from the
working order.


Step Action

• Select the OPTMON facility associated with port 6 of ESAM 2
(OPTMON<shelf>-<slot>-6).
mid-stage access.
facility for ESAM 2 (OPTMON<shelf>-<slot>-8) from the Facility drop down
list. Record the OPR-OTS Untimed parameter.
• Select the OPTMON facility associated with port 6 of MLAx.
mid-stage access.
71 Put the Line A amplifier of the MLAx back in normal mode by setting the AMP


Step Action
72 Put the MLAx AMP facility parameters back to the values you recorded in step
64, as follows:
of ESAM 2.
For ESAM, the following alarms clear:
- “Line A Input OTDR Trace High Reflection Detected”
- “Line A Input OTDR Trace High Loss Detected”
- “OTDR Trace In Progress”
Line A In (port 8) of ESAM 1.
76 Put the Line B amplifier facility of MLAx in no shutoff mode as follows:
OOS-AUMA.
Part 2 of 2, 323-1851-310
Part 2 of 2, 323-1851-543


Step Action
reflection.
step):
• AMP Mode
• Target Power
79 Using PM, observe the ORL at the output of the Line B amplifier facility of the
MLAx:
working order.


Step Action

Mid-stage loss = <Line B output power (dBm) read in step 80> - <adjacent
mid-stage access.
• Select the OPTMON facility associated with port 8 of MLAx.
Line A input power (dBm) read in this step>.
mid-stage access.
84 Put the Line B amplifier of the MLAx back in normal mode by setting the AMP


Step Action
77, as follows:
of ESAM 1.
Testing a line amplifier node equipped with ESAM+MLAx+MLAx+ESAM circuit packs
configuration. Testing starts with direction 1 by putting a loopback on ESAM 2
and putting the MLAx 1 Line A and MLAx 2 Line B amplifiers in the no shutoff
mode. Testing completes with direction 2 by putting a loopback on ESAM 1
and putting the MLAx 2 Line A and MLAx 1 Line B amplifiers in the no shutoff
mode.
Line A In (port 8) of the line facing circuit pack 2 (ESAM 2).


Step Action
89 Put the Line A amplifier facility of MLAx 1 and the Line B amplifier facility of
MLAx 2 in no shutoff mode as follows:
a. In the Equipment & Facility Provisioning application, retrieve the facility
b. Ensure the primary state of the Line A AMP facility (port 8) is not
OOS-AUMA.
c. Set the AMP facility parameter ALSO Disabled to True for the Line A
amplifier facility of MLA 1.
d. Repeat substep a to substep c for the Line B amplifier facility of MLAx 2
(port 6).

Part 2 of 2, 323-1851-310
Part 2 of 2, 323-1851-543
reflection.


Step Action
step):
• AMP Mode
• Target Power
92 Using PM, observe the ORL at the output of the Line A amplifier facility of
MLA 1:
working order.


Step Action
93 Using PM, observe the ORL at the output of the Line B amplifier facility of
MLA 2:
Untimed bin should be greater than 28 dB. When DSCMs are used and
the DSCM location is at the head end of the span (collocated with the
amplifier being commissioned), the minimum ORL threshold to meet or
exceed is 24 dB.
working order.
• Calculate the loss:
Loss = <Line A output power (dBm) read in step 94> - <adjacent Line B input
power (dBm) read in this step>.
• Compare the loss with the expected range by adding up the pad and
DSCM loss as indicated in Table 4-5 on page 4-131. If the loss falls below
this range, increase the pad attenuation. If the loss exceeds this range,
clean and inspect all connectors and patch cords in the mid-stage
access.


Step Action

mid-stage access.
98 Put the Line A amplifier of MLA 1 and Line B of MLA 2 back in normal mode
by setting the AMP facility parameter ALSO Disabled to False.
90, as follows:
of ESAM 2.
Line A In (port 8) of the line facing circuit pack 1 (ESAM 1).


Step Action
103 Put the Line A amplifier facility of MLAx 2 and the Line B amplifier facility of
MLAx 1 in no shutoff mode as follows:
b. Ensure the primary state of the Line A AMP facility (port 8) is not
OOS-AUMA.
c. Set the AMP facility parameter ALSO Disabled to True for Line A amplifier
facility of MLAx 2.
d. Repeat substep a to substep c for the Line B amplifier facility of MLAx 1
(port 6).

Part 2 of 2, 323-1851-310
Part 2 of 2, 323-1851-543
reflection.


Step Action
step):
• AMP Mode
• Target Power
MLA 2:
working order.


Step Action
MLA 1:
exceed is 24 dB.
working order.
access.


Step Action

mid-stage access.
112 Put the Line A amplifier of MLA 2 and Line B of MLA 1 back in normal mode
by setting the AMP facility parameter ALSO Disabled to False.
104, as follows:
of ESAM 1.
Testing a line amplifier node equipped with ESAM+MLAx+MLAx circuit packs
configuration. Testing starts with direction 1 by putting a loopback on the
ESAM and putting the MLAx 1 Line B and MLAx 2 Line A amplifiers in the no
shutoff mode. Testing completes with direction 2 by putting the MLAx 1 Line
A amplifier in the no shutoff mode.


Step Action
Direction 1 (MLAx -> MLAx - ESAM)

116 See Figure 4-87 on page 4-246 for an example of node testing for this type of
configuration.
Line A In (port 8) of the ESAM circuit pack.
118 Put the Line B amplifier facility of MLAx 1 in no shutoff mode as follows:
information of the Line B AMP facility (port 5).
• Ensure the primary state of the Line B AMP facility (port 5) is not
OOS-AUMA.
Part 2 of 2, 323-1851-310
Part 2 of 2, 323-1851-543
reflection.
119 Put the Line A amplifier facility of MLAx 2 in no shutoff mode.
120 Record the following MLAx 2 Line A AMP facility parameters and the MLAx 1
Line B AMP facility parameters (you will be instructed in step 128 to put them
back to the values you are recording in this step):
• AMP Mode
• Target Power


Step Action

a. Put the MLAx AMP facilities from step 120 out-of-service.
b. On the MLAx AMP facilities from step 120, set the AMP Mode to Power.
c. On the MLAx AMP facilities from step 120, set the Target Power to
9.5 dBm. (In the no shutoff mode, the amplifier will produce broadband
noise. In this mode, the amplifier output power may be different from
9.5 dBm.)
d. Put the MLAx AMP facilities from step 120 back in-service.
MLAx 2.
working order.
123 In the Performance Monitoring window, record the output power of the Line A
amplifier facility of MLAx 2:
• Select the MLAx 2 Line A AMP facility AMP-<shelf>-<slot>-8 from the


Step Action
124 In the Performance Monitoring window, record the input power of the Line B
amplifier facility of MLAx 1 and calculate the loss at this stage.
• Select the MLAx 1 Line B AMP facility AMP-<shelf>-<slot>-6 from the
Loss = <MLAx 2 Line A output power (dBm) read in step 123> - <MLAx 1
access, then go to step 125.
MLAx 1.
exceed is 24 dB.
working order.
126 In the Performance Monitoring window, record the output power of the Line B
amplifier facility of MLAx 1:
• Select the MLAx 1 Line B AMP facility AMP-<shelf>-<slot>-5 from the


Step Action
127 In the Performance Monitoring window, record the input power of the Line B
ESAM facility and calculate the loss at this stage.
• Select the OPTMON facility associated with port 6 of the ESAM circuit
pack (OPTMON-<shelf>-<slot>-6).
access.
128 For each of the MLAx AMP facilities from step 120, put the facility parameters
back to the values you recorded in step 120, as follows:
129 Remove the loopback fiber you placed (in step 117) between Line B Out
(port 5) and Line A In (port 8) of the ESAM circuit pack.
130 On the MLAx 1 Line B AMP facility:
• Put the facility back in normal mode by setting the facility parameter
ALSO Disabled to False (was set to True in step 118).
• Set the AMP Mode to Gain.
131 On the MLAx 2 Line A AMP facility:
• Put the facility back in normal mode by setting the facility parameter
ALSO Disabled to False (was set to True in step 119).
• Set the AMP Mode to Gain.


Step Action

Direction 2 (ESAM -> MLAx -> MLAx)
as follows:
OOS-AUMA.
working order.


Step Action
135 Using PM, observe the output power of the Line A amplifier facility of line
facing circuit pack 1:
136 In Site Manager, select the appropriate AMP from the Equipment and
Facilities Provisioning window.
2 is not OOS-AUMA.
• Select the MLAx Line B AMP facility of line facing circuit pack 2
(AMP-<shelf>-<slot>-6) from the Facility drop down list.
mid-stage access.


Step Action
Testing a line amplifier node equipped with ESAM/SAM+XLA+XLA+ESAM/SAM circuit packs

configuration. Testing starts with direction 1 by putting a loopback on
ESAM/SAM 2 and putting the XLA 1 Line A amplifier in the no shutoff mode.
Testing completes with direction 2 by putting a loopback on ESAM/SAM 1 and
putting the XLA 2 Line A amplifier in the no shutoff mode.
Note: DSCMs are not supported when using SRA line facing circuit packs.
Direction 1 (Loopback on ESAM/SAM 2)
Line A In (port 8) of the line facing circuit 2 (ESAM/SAM 2).
139 Put the Line A In (port 8) AMP facility of the XLA 1 in no shutoff mode (the
XLA adjacent to the line circuit pack 1 [ESAM/SAM 1]) as follows:
a. In the Equipment & Facility Provisioning application, record the current
settings of the Line A AMP facility (port 8).
b. Put the AMP facility out-of-service.
c. Change the AMP facility mode to Power.
d. Change the Target Power to -1.5 dBm.
e. Set the AMP facility parameter ALSO Disabled to True.
f. Put the AMP facility back in-service.
In the no shutoff mode, the amplifier will produce broadband noise.
140 Check the ORL reported on XLA 1 port 8 (Line A In).
a. Review the ORL-OTS Untimed parameter. The measurement in the
working order.
b. If cleaning fiber connections does not correct reflectance problems,
141 Select the ADJ-FIBER facility for port 7 of XLA 1 (Line A Out) and check the
fiber loss that is reported.
If the loss is more than 1 dB, check the fibering.
142 Check the ORL reported on XLA 2 port 6 (Line B In).


Step Action
143 If the optional OPM is present:

a. Check for total power present on port 2 of the OPM.
b. Put the XLA 2 Line B In (port 6) AMP facility out-of-service and check that
there is no power at port 2 of the OPM.
c. Put the XLA 2 Line B In (port 6) AMP facility back in-service.
144 Select the ADJ-FIBER facility for port 5 of XLA 2 (Line B Out) and check the
145 Select the ADJ-FIBER facility for port 7 of ESAM/SAM 2 (Line A Out) and
check the fiber loss that is reported.
146 On port 8 of the XLA 1 (Line A In), return the AMP facility to its initial settings
147 Remove the optical loopback you put in step 138 on the line facing circuit 2
(ESAM/SAM 2).
Direction 2 (Loopback on ESAM/SAM 1)
148 Put the optical loopback with 20 dB padding between Line B Out (port 5) and
Line A In (port 8) of the line facing circuit 1 (ESAM/SAM 1).
149 Put the Line A In (port 8) AMP facility of the XLA 2 in no shutoff mode as
follows:
a. In the Equipment & Facility Provisioning application, record the current
settings of the Line A AMP facility (port 8).
b. Put the AMP facility out-of-service.
c. Change the AMP facility mode to Power.
d. Change the Target Power to -1.5 dBm.
e. Set the AMP facility parameter ALSO Disabled to True.
f. Put the AMP facility back in-service.
150 Check the ORL reported on XLA 2 port 8 (Line A In).
working order.


Step Action
151 Select the ADJ-FIBER facility for port 7 (Line A Out) of XLA 2 and check the
152 Check the ORL reported on port 6 of XLA1 (Line B In).
working order.
153 If the optional OPM is present, select the ADJ-FIBER facility for port 1 of
XLA 1 and check the fiber loss that is reported.
154 Select the ADJ-FIBER facility for port 5 of XLA 1 (Line B Out) and check the
155 Select the ADJ-FIBER facility for port 7 of ESAM/SAM 1 (Line A Out) and
check the fiber loss that is reported.
156 On Line A In (port 8) of the XLA 2, return the AMP facility to its initial settings
157 Remove the loopback you put in step 148 on the line facing circuit 1
(ESAM/SAM 1).
158 Connect all the line fibers as per engineering data sheet.
—end—

Procedure 4-17
Testing DGFF nodes
Use this procedure to test a DGFF node. DGFF nodes contain two ROADM
OTS subtypes without local add/drop channels. A DGFF node can be:
• at a DOC domain boundary, or
• not at a DOC domain boundary. In this case, the DGFF node demarcates
two sections within a single DOC domain.
For more information, refer to 6500 Packet-Optical Platform Photonic Layer

Guide, NTRN15DA.
CAUTION
DANGER
Risk of injury
CAUTION
Prerequisites
• There should be no line fibers connected. The only fibers connected are
the intra-NE fibers.


Testing DGFF nodes
Figure 4-89
Test setup example—OSC connectivity
Loopback Loopback


Testing DGFF nodes
Figure 4-90
Test setup example—node continuity
Direction 1
Line B Out
fiber
Line B Out
fiber Direction 2
Step Action

2 Make sure that all the amplifiers associated with the DGFF OTSs are set at
default Gain mode. For each amplifier:
a. In the Equipment & Facility Provisioning application, select the amplifier
in the Equipment panel.
b. From the Facility Type drop down list, select AMP, then select the facility,
click Edit, check the AMP Mode value, and make sure that it is set at Gain.
c. Repeat substep a and substep b for all the amplifiers associated with the
DGFF OTSs.


Testing DGFF nodes
Step Action
Testing OSC connectivity (see Figure 4-89 on page 4-287)

circuit pack, on the 2xOSC circuit pack, or the SRA/ESAM/SAM circuit packs,
as applicable.
testing.
Power parameter.
Untimed parameter.
Coupler loss = <OSC pluggable module output power (dBm) read in step 4>
- <amplifier OSC Out power (dBm) read in step 5>
of the OSC pluggable module from the OSC Out (port 4) of the line facing
circuit pack. This value should be approximately the same as the power read
in step 5.
8 Remove the loopback you placed in step 3.
the OSC-2 (single 2xOSC configuration or SRA/ESAM/SAM+XLA
configuration).
Testing site continuity (see Figure 4-90 on page 4-288)
10 Connect line fibers at port 5 (Line B Out) of the amplifiers/line facing circuit
packs. Line fibers must remain disconnected at port 8 (Line A In).
11 Start with one direction. For example, in Figure 4-90 on page 4-288 start in
direction 1.


Testing DGFF nodes
Step Action
12 Put the Line A AMP facility (port 8) of the first amplifier (amplifier 1 in Figure
4-90 on page 4-288) in no shutoff mode as follows:
information.
b. Ensure the primary state of the facility is not OOS-AUMA.
c. Put the Line A AMP facility in no shutoff mode by setting the AMP facility
13 On the Line A AMP (port 8) facility of amplifier 1:
a. Set the AMP Target Power value at its default maximum.
b. Change the AMP Mode to Power.
14 Select Performance->Performance Monitoring to open the PM screen.

15 Select the facility for amplifier 1:
16 Click Start Monitoring.
17 Record the OPOUT-OTS Untimed parameter (total Optical Power Output at
amplifier 1).
18 Select the OPTMON Type and the facility for the WSS Common In port of the
WSS from the Facility drop down list. Record the OPR-OTS Untimed
parameter.
The difference between the power values recorded in step 17 and step 18
should be less than 0.5 dB.


Testing DGFF nodes
Step Action
19 Select the OPTMON Type and the facility for the WSS OPM Port 2 from the
Facility drop down list. Record the OPR-OTS Untimed parameter (optical
power received).
should be less than 18 dB.
20 Select Performance->PM Graphing. From the Graph Type drop down list,
select the Channel powers per port option. Select
CHMON-<sh>-<ampSlot>-7 from the Facility drop down list.
Channel powers should be visible in the PM Graphing window if the OPM is
connected correctly to the amplifier monitor port and if the OPM device is
capable of monitoring the channel optical powers.
21 On the next WSS in Direction 1:
a. Select the OPTMON Type and the facility for the WSS Switch In (Mux In)
port from the Facility drop down list (for example, select port 3 if ports 3
and 4 are connected to set up the DGFF site, as in Figure 4-90 on page
4-288).
b. Record the OPR-OTS Untimed parameter. The difference between the
power values recorded in this step (step 21) and step 18 should be less
than 12 dB.
22 Check for High Fiber Loss (HFL) alarms reported against ADJ-FIBER
facilities at the following interconnections:
• amplifier 1 port 7 to WSS 1 Common In
• WSS 1 to WSS 2
If an HFL alarm is raised, go to Equipment & Facility Provisioning, select the

amplifier or the WSS in the equipment list, select the alarmed ADJ-FIBER
facility and check the Fiber Loss. If the value of the fiber loss is higher than
the Fiber Loss Minor Threshold (default is 3 dB), clean the fiber connections
at both ends of the interconnection. If cleaning the fiber does not clear the
alarm, replace the fiber patch cord. If replacing the fiber patch cord does not
clear the alarm, contact your next level of support.
23 See Figure 4-90 on page 4-288. On the Line B AMP facility of amplifier 2,
make sure the AMP Mode is set to Gain and the Target Gain is set to 15 dB.
24 Open the pixel for a channel at the WSS Mux:
a. Select the CHC facility and click Edit.
b. In the Edit Facility CHC window, set the Opaque parameter to No.
c. Set the Switch Selector to 3.
d. Set the Target Loss to 0.


Testing DGFF nodes
Step Action
25 Make sure all alarms against the AMP facility on port 6 or AMPMON on port 5
have cleared on amplifier 2 (for example, Input Loss of Signal, Shutoff
Threshold Crossed, Automatic Power Reduction). If the alarms have not
cleared, see the respective alarm clearing procedures in Fault Management
- Alarm Clearing, 323-1851-543.
26 Select Performance->PM Graphing. From the Graph Type drop down list,
select the Channel powers per port option. Select
CHMON-<sh>-<ampSlot>-5 from the Facility drop down list.
Channel powers should be visible in the PM Graphing window if the OPM is
connected correctly to the amplifier monitor port and if the OPM device is
capable of monitoring the channel optical powers.
Restoring settings after testing
27 On the Line B AMP facility of amplifier 2, make sure the Target Gain is set
back to minimum gain.
28 Close down the pixel you opened in step 24:
a. Select the CHC facility and click Edit.
b. In the Edit Facility CHC window, set the Opaque parameter to Yes.
c. Set the Switch Selector to 3.
d. Set the Target Loss to 18.
29 Put amplifier 1 back in auto shutoff mode by setting the Line A AMP facility
parameter ALSO Disabled to False.
30 On the Line A AMP facility of amplifier 1, change the AMP Mode to Gain.
31 Repeat step 12 to step 30 for the other direction (see Figure 4-90 on page
4-288—Direction 2, amplifiers 3 and 4, respectively).
—end—

Procedure 4-18
Connecting intra-site fibers for Coherent Select sites
Use this procedure to perform intra-site fiber connections for Coherent Select
(CS) sites. In this procedure, CMD44 refers to both the regular CMD44, the
enhanced 100GHz CMD44 with isolator (eCMD44), and the enhanced
50 GHz CMD44 unless specified otherwise.
Note: Contact your Ciena representative for availability of CMD42 module

(NTT862NA).
To connect intra-site fibers for configurations other than Coherent Select, see
“Connecting intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM
sites” on page 4-5.
Prerequisites
subtending modules (CMD, BMD2, OBB, OBMD).
CAUTION
DANGER
Risk of injury


Step Action

If Then go to
you are connecting an OSC to the following equipment: step 2
LIM (line-amp only), MLA2, MLA2 w/VOA, or MLA3
you have finished making OSC connections step 10
Connecting OSC to LIM, MLA2, MLA2 w/VOA, or MLA3

2 For the maximum number and slot equipping rules regarding 2xOSC circuit
packs, see the section on shelf equipping rules in the configuration rules
chapter of Planning - Ordering Information, 323-1851-151. The OSC ports in
this section (step 2 to step 9) could alternatively be on the SPAP-2 w/2xOSC
circuit pack if applicable.
Review the illustration that applies to your configuration:
• Figure 4-91 on page 4-301—CS line amplifier site
• Figure 4-92 on page 4-302—CS Terminal - Colored site (also known as
Terminal with 88-channel colored Mux/Demux) - using CMD44 50 GHz
• Figure 4-96 on page 4-306 and Figure 4-97 on page 4-306 —CS
Terminal - Colored site (also known as Terminal with 42-channel colored
Mux/Demux) - using CMD42 112.5 GHz
• Figure 4-98 on page 4-307—CS Terminal - Directionless site (also known
as single-ended OADM 16-channel colorless and directionless
Mux/Demux)
• Figure 4-99 on page 4-308—CS OADM - Directionless site (also known
as OADM 16-channel colorless and directionless Mux/Demux)
• Figure 4-100 on page 4-309—CS Terminal - Directional (also known as
single-ended OADM, 16+16 channel colorless and directional
Mux/Demux)
• Figure 4-101 on page 4-310—CS OADM - Directional (also known as
single-ended OADM, 16+16 channel colorless and directional
Mux/Demux


Step Action
line facing circuit pack (LIM [line-amp only], MLA2, MLA2 w/VOA, or MLA3).
Ensure that the OSC-1 is connected to the line facing circuit pack as indicated
in the EDP/IDP (in the correct slot).
If you need to fiber another OSC and are using a Then go to
single 2xOSC circuit pack configuration step 6
dual 2xOSC circuit packs configuration step 8
Go to step 10.
8 Connect the 2xOSC OSC-1 Out port of the second 2xOSC circuit pack to the
OSC In (port 3) of the appropriate line facing circuit pack. Ensure that the
9 Connect the 2xOSC OSC-1 In port of the second 2xOSC circuit pack to the
OSC Out (port 4) of the appropriate line facing circuit pack. Ensure that the


Step Action

If you are performing intra-NE fibering at a Then go to
CS line amplifier site step 11
CS Terminal - Colored site (also known as Terminal with step 14
88-channel colored Mux/Demux) - using CMD44 50 GHz
CS Terminal - Colored site (also known as Terminal with step 23
44/64/96-channel colored Mux/Demux) - using CMD42
112.5 GHz, CMD44 100 GHz, CMD64 75 GHz, or CMD96
50 GHz
CS Terminal - Directionless site (also known as step 30
single-ended OADM 16-channel colorless and
directionless Mux/Demux)
CS OADM - Directionless site (also known as OADM step 30
16-channel colorless and directionless Mux/Demux)
CS Terminal - Directional (also known as single-ended step 39
OADM, 16+16 channel colorless and directional
Mux/Demux)
CS OADM - Directional site (also known as OADM 16+16 step 39
channel colorless and directional Mux/Demux)
Connecting intra-NE fibers at a CS line amplifier site

11 See Figure 4-91 on page 4-301 for an example of intra-NE fibering at a CS
line amplifier site.
12 Connect the Line A Out (port 7) of the first line facing circuit pack to the
Line B In (port 6) of the next adjacent line facing circuit pack.
13 Connect the Line A Out (port 7) of the adjacent line facing circuit pack to the
Line B In (port 6) of the first line facing circuit pack.
You have completed connecting intra-NE fibers at a CS line amplifier site.
Connecting intra-NE fibers at a CS Terminal - Colored site (88-channel using CMD44 50 GHz)
14 See Figure 4-92 on page 4-302 to perform the steps for intra-NE fibering at a
CS Terminal - Colored site (also known as terminal with 88-channel colored
Mux/Demux site).
If you want to connect a CMD44 module to Then go to
2-port OPM step 16
otherwise step 18


Step Action
Connecting CMD44s to 2-port OPM

16 Connect the monitor port (port 92) of one of the CMD44s to the monitor port
of the 2-port OPM as indicated in the EDP/IDP.
17 Perform step 16 for the other CMD44 and the other monitor port of the 2-port
OPM.
Connecting CMD44s to BMD2 to amplifier
18 Connect the Common Out (port 90) of the CMD44 50 GHz to the Input of
BMD2 (either 3 or 5) as indicated in the EDP/IDP.
19 Connect the second CMD44 50 GHz to the other input port of BMD2.
20 Connect the Common In (port 89) of the CMD44 50 GHz module(s) to the
21 Connect the Common Out (port 2) of the BMD2 to Line B In (port 6) of the
22 Connect the Common In (port 1) of BMD2 to Line A Out (port 7) of the
Connecting intra-NE fibers at a CS Terminal - Colored site (44-channel using CMD44 100GHz,
64-channel using CMD64 75 GHz, or 96-channel using CMD96 100 GHz)
23 See the following figures to perform the steps for intra-NE fibering at a CS
Terminal - Colored site:
• Figure 4-96 on page 4-306 and Figure 4-97 on page 4-306 for terminal
with 42-channel colored Mux/Demux site using CMD42 112 GHz.
• Figure 4-93 on page 4-303 for terminal with 44-channel colored
Mux/Demux site using CMD44 100GHz.
Mux/Demux site using CMD64 75 GHz.
Mux/Demux site using CMD96 50GHz.
If you want to connect Then go to
a CMD42 module to a 2-port OPM step 25
otherwise step 28
Note: The CMD44 100 GHz does not contain monitor ports.


Step Action
Connecting CMD42 to 2-port OPM

25 Connect the monitor ports (port 87 [common in mon] and port 88 [common
out mon]) of the CMD42 to the monitor ports of the 2-port OPM as indicated
in the EDP/IDP.
Go to step 28.
in the EDP/IDP.
Go to step 28.
in the EDP/IDP.
Connecting CMDs to amplifier
28 Connect the Common Out of the CMD42 (port 86), CMD44 100 GHz (port
90), CMD64 (port 130), or CMD96 (port 194) to the Line B In (port 6) of the
amplifier circuit pack as indicated in the EDP/IDP.
29 Connect the Common In of the CMD42 (port 85), CMD44 100 GHz (port 89),
CMD64 (port 129), or CMD96 (port 193) to Line A Out (port 7) of the amplifier
circuit pack as indicated in the EDP/IDP.
Connecting intra-NE fibers at a CS Terminal - Directionless site or CS OADM - Directionless site
30 See the following illustrations, then go to step 31.
• Figure 4-98 on page 4-307 to perform the steps for intra-NE fibering at a
CS Terminal - Directionless site (also known as single-ended OADM
16-channel colorless and directionless Mux/Demux).
• Figure 4-99 on page 4-308 to perform the steps for intra-NE fibering at a
CS OADM - Directionless site (also known as OADM 16-channel
colorless and directionless Mux/Demux).
Connecting OBMDs to OBB (CS Terminal - Directionless site or CS OADM - Directionless site)
31 Connect the CMD1 In port (port 1) of the Optical Bridge and Broadcast (OBB)
to the Common Out port (port 18) of the Optical Broadband Mux/Demux
(OBMD) as indicated in the EDP/IDP.
32 Connect the CMD1 Out port (port 2) of the Optical Bridge and Broadcast
(OBB) to the Common In port (port 17) of the Optical Broadband Mux/Demux


Step Action
to the Common Out port (port 18) of the other Optical Broadband Mux/Demux
(OBB) to the Common In port (port 17) of the other Optical Broadband
Mux/Demux (OBMD) as indicated in the EDP/IDP.
Connecting OBB to amplifier (CS Terminal - Directionless site or CS OADM - Directionless site)
35 Connect the Line 2 Out port (port 8) of the OBB to Line B In port (port 6) of
the amplifier.
36 Connect the Line 2 In port (port 7) of the OBB to Line A Out port (port 7) of
the amplifier.
If this is a Then
CS Terminal - Directionless site You have completed this procedure.
CS OADM - Directionless site Go to step 37 to connect the other
amplifier.
the amplifier.
the amplifier.
Connecting intra-NE fibers at a CS Terminal - Directional site or CS OADM - Directional site
39 See the following illustrations, then go to step 40.
• Figure 4-100 on page 4-309 to perform the steps for intra-NE fibering at
a CS Terminal - Directional (also known as single-ended OADM, 16+16
channel colorless and directional Mux/Demux).
• Figure 4-101 on page 4-310 to perform the steps for intra-NE fibering at
a CS OADM - Directional site (also known as OADM 16+16 channel
colorless and directional Mux/Demux)
Connecting OBMDs to OBB (CS Terminal - Directional site or CS OADM - Directional site)


Step Action
Connecting OBB to amplifier (CS Terminal - Directional site or CS OADM - Directional site)
the amplifier.
the amplifier.
If this is a Then
CS Terminal - Directional site You have completed this procedure.
CS OADM - Directional site Go to step 50 to connect the other
amplifier.
the amplifier.
the amplifier.
—end—

Figure 4-91
Intra-NE fiber connections—Coherent Select line amplifier site (example shows MLA2)

Figure 4-92
Intra-NE fiber connections—Coherent Select Terminal (88-channel) - Colored site (example shows
MLA2)

Figure 4-93
Intra-NE fiber connections—Coherent Select Terminal (44 channel) - Colored site (example shows
MLA3)

Figure 4-94
MLA3)

Figure 4-95
MLA3)

Figure 4-96
MLA3)
Figure 4-97
MLA3XLA+ESAM)

Figure 4-98
Intra-NE fiber connections—Coherent Select Terminal - Directionless (example shows MLA2)

Figure 4-99
Intra-NE fiber connections—Coherent Select OADM - Directionless site (example shows MLA2)

Figure 4-100
Intra-NE fiber connections—Coherent Select Terminal - Directional (example shows MLA2)

Figure 4-101
Intra-NE fiber connections—Coherent Select OADM - Directional site (example shows MLA2)

Procedure 4-19
Testing a Coherent Select line amplifier node
Use this procedure to test a Coherent Select (CS) line amplifier node. Figure
4-102 on page 4-312 illustrates an example of testing.
With no input connected, the pre-amplifier is set to the no shutoff mode. In the
no shutoff mode the amplifier transmits an amplified spontaneous emission
(ASE) broadband noise that can be used to measure the reflectance and the
loss of the mid-stage connections.
CAUTION
DANGER
Risk of injury
CAUTION
Prerequisites
There should be no line fibers connected. The only fibers connected are the
intra-NE fibers.


Figure 4-102
Overview of Coherent Select Amplifier node testing
Step Action
1 See Figure 4-102 on page 4-312 for an example of CS line amplifier node
testing. For convenience, in this procedure the circuit packs are called as
follows:
• The line facing circuit pack with the Line A amplifier (MLA2,
MLA2 w/VOA, or MLA3) is called line facing circuit pack 1.
• The LIM is called line facing circuit pack 2.


Step Action

circuit pack or on the 2xOSC circuit pack.
testing.
Power parameter.
Untimed parameter.
Testing the mid-stage loss in direction 1
Line A In (port 8) of line facing circuit pack 2.


Step Action
11 Put the Line A amplifier facility of line facing circuit pack 1 in no shutoff mode.
OOS-AUMA.
• Put the Line A amplifier facility of line facing circuit pack 1 in no shutoff
mode by setting the AMP facility parameter ALSO Disabled to True.
• For MLA2/MLA3, select the AMP Type and the facility
working order.
• For MLA2/MLA3, select the AMP Type and the facility


Step Action

mid-stage access.
Testing the mid-stage loss in direction 2
facility for line facing circuit pack 2 (OPTMON-<shelf>-<slot>-8) from the
Facility drop down list. Record the OPR-OTS Untimed parameter.
16 In Site Manager, select line facing circuit pack 1 from the Equipment and
Facilities Provisioning window.
• Ensure the Primary State of the Line B amplifier facility of line facing
circuit pack 1 is not OOS-AUMA.
• Select the MLA2/MLA2 w/VOA/MLA3 Line B AMP facility of line facing
circuit pack 1 (AMP-<shelf>-<slot>-6) from the Facility drop down list.


Step Action
of line facing circuit pack 2.
—end—

Procedure 4-20
Testing a Coherent Select Terminal - Colored node
Use this procedure to test a Coherent Select Terminal - Colored node (see
Figure 4-92 on page 4-302), where light from transmitting subtending
equipment is available. This test verifies the optical continuity and checks for
reflection-related problems. This procedure does not optimize the channels
for traffic.
Note: Contact your Ciena representative for availability of CMD42 module

(NTT862NA).
Prerequisites
installed CMD.
– Chapter 2, “Nodal SLAT procedures”
– Chapter 3, “Photonic layer provisioning procedures”
– Procedure 4-18, “Connecting intra-site fibers for Coherent Select
sites”
CAUTION
DANGER
Risk of injury


CAUTION
Step Action

testing.
Power parameter.
Untimed parameter.


Step Action

8 If the configuration is 88-channel terminal using CMD44 50 GHz modules, go
to step 9. Otherwise, go to step 10.
9 Start with the Blue CMD44:
a. Choose one of the transmitters to be connected to the selected Blue
CMD44. Make sure the wavelength of the transmitter matches the
wavelength of the CMD44 port it is connected to.
b. If you can adjust the output power of transmitter, set it to maximum.
c. Using a power meter set correctly for the wavelength, measure the
CMD44 port.
Go to step 11.
10 For the CMD42, CMD44 100 GHz, CMD64, or CMD96:
a. Choose one of the transmitters to be connected to the selected CMD.
Make sure the wavelength of the transmitter matches the wavelength of
the CMD port it is connected to.
b. If you can adjust the output power of transmitter, set it to maximum.
c. Using a power meter set correctly for the wavelength, measure the
CMD port.
Line B Out port and the line facing circuit pack Line A In port. The amount of
padding shall be 20 dB (MLA2/MLA3/MLA2 w/ VOA).
line facing circuit pack.
13 Calculate the loss between the CMD input and the Line B input port:


Step Action
14 Considering all the components present (including fixed pads and BMD2),
calculate the maximum expected loss between the CMD input channel port
and the Line B input port. Select the LINE B AMP facility (port 6) and record
the OPIN-OTS Untimed value.
max CMD mux loss (Ch<x>-In to Common Out) (see Table 4-3 on page
4-129)
+ max BMD2 mux loss (88-channel CMD44 50 GHz configurations only)
(see Table 4-3 on page 4-129)
+ Fixed pad loss (if present)
+ N x 0.5 dB for each patch cord
a. Starting with the transmitter and going toward the line facing circuit pack,
b. Compare the loss through each component and patch cord to the
maximum expected loss
Refer to the appropriate procedure in Fault Management – Module
16 Adjust the target gain of the Line B amplifier facility to 17 dB. Verify the ORL
at the Line B output. If the value is lower than 28 dB, clean all the optical
connections from the Line B output port to the input of the pad.
17 Adjust the target gain of the Line A amplifier facility to 20 dB. Verify the ORL
at the Line A output. If the value is lower than 28 dB, clean all the optical
connections from the Line A output port to the input of the CMD.
19 With a power meter, measure the power present on the CMD output port that
corresponds to the wavelength you are testing.
20 Calculate the loss between the line facing circuit pack Line A Out and the
CMD channel output port. Line A facility (port 8) AMP facility OPOUT-OTS
Untimed value:
21 Considering all the components present (including fixed pads), compute the
maximum expected loss between the Line A output and the CMD channel
output.


Step Action
a. Starting with the Line A output and going toward the CMD, measure the
input and the output of each component with a power meter. Always clean
both male connectors before closing a connection.
maximum expected loss for each component.
23 When you have completed all testing, disconnect the test transmitter.
24 If the configuration is 88-channel terminal using CMD44 50 GHz modules,
repeat step 9 to step 23 with the Red CMD44.
25 When all testing is complete, remove the loopback at the amplifier and
reconnect the fibers as per the EDP/IDP.
—end—

Procedure 4-21
Testing Coherent Select Directionless or Directional
nodes
Use this procedure to test the following types of Coherent Select (CS) nodes:
• Terminal - Directionless node (see Figure 4-98 on page 4-307)
• OADM - Directionless node (see Figure 4-99 on page 4-308)
• Terminal - Directional node (see Figure 4-100 on page 4-309)
• OADM - Directional node (see Figure 4-101 on page 4-310)
where light from transmitting subtending equipment is available.
This test verifies the optical continuity and checks for reflection-related
problems. This procedure does not optimize the channels for traffic.
Prerequisites
installed Optical Broadband Mux/Demux (OBMD).
— Chapter 2, “Nodal SLAT procedures”
— Chapter 3, “Photonic layer provisioning procedures”
— Procedure 4-18, “Connecting intra-site fibers for Coherent Select
sites”


Testing Coherent Select Directionless or Directional nodes
Step Action
CAUTION
DANGER
Risk of injury
CAUTION
Step Action

testing.
Power parameter.


Step Action
Untimed parameter.
8 Select the OBMD8 you want to test:
a. Start with the leftmost OBMD8.
b. Select one of the transmitters to be connected to the selected OBMD8.
Provision the transmitter to a valid wavelength.
c. If you can adjust the output power of the transmitter, set it to maximum.
d. Using a power meter set correctly for the wavelength, measure the
transmitter output power, and connect the transmitter to the appropriate
OBMD8 port.
Note 1: For Terminal - Directional or OADM - Directional nodes, perform the
following testing steps with OBB CMD1 and CMD2 ports for Line 1 and OBB
CMD3 and CMD4 ports for Line 2.
Note 2: If you are testing an OADM node, from this step on select one of the
line facing circuit packs and perform the steps using that circuit pack.


Step Action
Line B Out port and the line facing circuit pack Line A In port.
The amount of padding must be 20 dB (MLA2/MLA3/MLA2 w/VOA).
line facing circuit pack.
11 Calculate the loss between the OBMD8 input and the Line B input port:
12 Considering all the components present (including fixed pads), calculate the
maximum expected loss between the OBMD8 input channel port and the Line
B input port. Select the LINE B AMP facility (port 6) and record the OPIN-OTS
Untimed value.
max OBMD8 mux loss (Ch<x>-In to Common Out) (see Table 4-13 on
page 4-328)
+ max OBB mux loss (see Table 4-14 on page 4-328 or Table 4-15 on page
4-328, as applicable)
+ N x 0.5 dB for each patch cord
• Starting with the transmitter and going toward the line facing circuit pack,
• Compare the loss through each component and patch cord to the
maximum expected loss
14 Adjust the target gain of the Line B amplifier facility to 17 dB. Verify the ORL
at the Line B output. If the value is lower than 28 dB, clean all the optical
connections from the Line B output port to the input of the pad.
15 Adjust the target gain of the Line A amplifier facility to 20 dB. Verify the ORL
at the Line A output. If the value is lower than 28 dB, clean all the optical
connections from the Line A output port to the input of the OBMD8.


Step Action
17 With a power meter, measure the power present on the OBMD8 output port
that corresponds to the wavelength you are testing.
18 Calculate the loss between the line facing circuit pack Line A Out and the
OBMD8 channel output port. Line A facility (port 8) AMP facility OPOUT-OTS
Untimed value:
19 Considering all the components present (including fixed pads), compute the
maximum expected loss between the Line A output and the OBMD8 channel
output.
a. Starting with the Line A output and going toward the OBMD8, measure
the input and the output of each component with a power meter. Always
clean both male connectors before closing a connection.
maximum expected loss for each component.
21 When you have completed all testing, disconnect the test transmitter.
22 Repeat step 8 to step 21 with the other OBMD module(s).
23 Remove the loopback at the amplifier and reconnect the fibers as per the
EDP/IDP.
If you are testing Then
a Terminal node return the transmitter power to its
default value if you have adjusted the
output power in step 8 (substep c).
an OADM node (non-Terminal) go to step 25


Step Action
25 Repeat step 8 to step 23 for the second OTS. Then go to step 26.
26 In the Equipment & Facility Provisioning application:
a. Display the facility information of the Line A AMP facility (port 8) of MLA
west.
b. Place the west side MLA in no shutoff mode by setting the AMP facility
c. Set the Output power to 10 dBm.
27 Use the PM function to verify the OPOUT-OTS at the Line A output by
performing the following:
a. Select Performance->Performance Monitoring to open the PM screen.
b. For non-MLA2 w/VOA, select the AMP Type and the facility
For MLA2 w/VOA, select the VOA Type and the facility
c. Click Start Monitoring.
d. Record the OPOUT-OTS Untimed parameter.
28 Read the OPIN-OTS value at Line B In of the east side MLA2 and compare
with the value read in step 27.
Delta = Line A Out – OBB Insertion Loss (see Table 4-14 on page 4-328 or
Table 4-15 on page 4-328, as applicable) – 2x 0.5 dB (patch cord)
29 If the delta calculated in step 28 is higher than 2 dB, clean fibers and check
power at each component, starting with Line A Out connection until Line B In
of the east side MLA.
30 Place the amplifier back to shutoff mode by setting the AMP facility parameter
ALSO Disabled to False.
31 Repeat step 26 to step 30 for the other direction.
32 Return the transmitter power to its default value if you have adjusted the
output power in step 8 (substep c).
—end—

Table 4-13
Optical Broadband Mux/Demux (OBMD 1x8 C-Band) module insertion loss
optical specifications
From To Maximum insertion loss (dB)
Common In Demux Out 11
Mux In Common Out 11.3
Table 4-14
Optical Bridge and Broadcast (OBB 2x2x2 C-Band) module insertion loss
Line 1 In Line 2 Out 21.3
CMD1 Out 5.4

CMD2 Out
CMD1 Out 5.4

CMD2 Out
CMD 1 In Line 1 Out 6.4

Line 2 Out

Line 2 Out
Table 4-15
Optical Bridge and Broadcast (OBB 2x4x1 C-Band) module insertion loss
CMD1 Out 5.4

CMD2 Out
CMD3 Out 5.4

CMD4 Out

Procedure 4-22
Connecting inter-NE fibers and testing the photonic
layer
Use this procedure to connect the OTS to the optical line and to perform
photonic layer testing.
To log on to remote nodes from an amplifier node, shelf IP of the remote nodes
are needed.
The fibers used in the following steps to make optical connections to the line
must be verified to be in good working order prior to use. It is very important
that the optical connectors be cleaned and scoped prior to being connected.
See Installation - General Information, 323-1851-201.0 for instructions on
inspecting and cleaning fibers.
If you need to provision the amplifiers manually to test the optical continuity
and ORL, the default gain could be too low. If the default gain is too low, set
the Pre Amp Gain Target to 20 dB. If the span loss is significantly less than
20 dB, then the Pre Amp Gain Target can be provisioned to the span loss.
CAUTION
DANGER
Risk of injury
CAUTION


Connecting inter-NE fibers and testing the photonic layer
Step Action
Logging into the Craft

Connecting the inter-NE fiber
2 Select a direction (for example, direction 1) and start with the first line facing
circuit pack.
You can perform the following steps simultaneously for all line facing circuit
packs. Alternatively, you can perform the following steps on each line facing
circuit pack one by one.
At a terminal site, there is only one line facing circuit pack present so you only
need to perform the following steps once.
3 Connect the line fibers to either the amplifier Line A input port (receive path)
or the DSCM IN port (DSCM at the end of a span) and the Line B output port
(transmit path).
Checking the downstream OSC Rx connection
4 Place in OOS-MA state the OSC facility connected to the line facing circuit
pack.
5 Coordinate with personnel at the other end of the span to determine that the
OSC Rx LOS alarm is raised on the correct SFP equipment (according to the
EDP/IDP).
6 If the alarm is raised on the correct SFP, place the OSC facility back in service
and go to step 7. Otherwise, correct the OSC fibering.
Verifying the far end addresses for line adjacencies
7 Verify the Actual far end address for the line adjacencies by performing the
following:
• Select the line AID of the line facing circuit pack that you are connecting
to the line, that is, Line B Out or DSCM Out as indicated in the EDP/IDP
(ADJ-<shelf>-<AMP slot>-5 for LIM or ADJ-<shelf>-<DSCM slot>-1 for
DSCM or ADJ-<shelf>-<SRA/ESAM/SAM slot>-5 for SRA/ESAM/SAM)
(that is, the transmit port of the line facing circuit pack).
• In the Configuration-> Equipment & Facility Provisioning application,
select the LIM or DSCM or SRA/ESAM/SAM equipment that is connected
to the line.
• In the Facility type drop down menu, select: ADJ-LINE for LIM or for
SRA/ESAM/SAM, or ADJ for DSCM
• Verify that the Actual far end address matches the Expected far end
address as indicated in the EDP/IDP.


Step Action
• Verify that the fiber type is correct for the line adjacency as specified in
the EDP/IDP.
• Verify that the ADJ status is “RELIABLE”.
Note: An “Adjacency Mismatch” alarm is raised in case of a mismatch
between the Actual far end address and the Expected far end address.
8 Repeat step 7 for all NEs in the network, then go to step 9.
Checking for unexpected alarms
9 In the Active Alarms application, verify that there are no unexpected alarms
raised against the remote authentication dial in user service (RADIUS) server
visibility, if applicable.
10 If applicable, verify the status of both network timing protocol (NTP) servers,
and verify that there are no unexpected alarms raised against the NTP server
visibility.
11 Ensure that the Primary State of every AMP facility is IS (in the Edit Facility
dialog). However, when there is no light, the primary state displayed in the
facility table should be OOS-AU.
12 Verify that there are no unexpected communication, Optical Line Fail, OSC
related or Adjacency Mismatch alarms.
The system can have amplifier shutoff alarms until you add the first optical
channel.
13 Verify that there are no alarms that indicate incorrect provisioning of domain
optical control (DOC) OTSs.
The DOC Invalid Photonic Domain alarm should be cleared at this point.
14 Clear any unexpected alarms by referring to Fault Management - Alarm
Clearing, 323-1851-543 for troubleshooting.
15 Repeat step 9 to step 14 for all the NEs in the network.


Step Action
Verifying span loss

16 At the next network element of the first line facing direction, retrieve the OSC
span loss measurement by performing the following.
• In the Equipment & Facility Provisioning application, select the
ADJ-LINE facility of the line-facing circuit pack.
• Read the Span Loss values in the facility display. This is the span loss
calculated by the associated OSC. For SRA, the span loss is calculated
by the associated Telemetry Gain (TG) signal.
• Verify the span loss against the expected loss as indicated in the
EDP/IDP. The Span Loss Margin, Target Span Loss, and Minimum Span
Loss are provisioned in the respective ADJ-LINE facility fields. The
values should be non-zero to enable span loss detection.
The span loss represents the loss of the OSC/TG signal from the far end Line
B output port to the near end Line A input port. The loss is measured in the
receive direction and includes the loss from the transmitter on the other side
of the line to the drop port on the local line facing circuit pack.
• The OSC/TG span loss is measured at the low wavelength edge of the
C band. The expected span loss is typically quoted at the middle of the
C band. To account for the wavelength dependent loss (WDL), subtract
0.01 dB/km (for example, for a 100 km span, subtract 1 dB) from the
reported span loss before comparing with the expected loss.
— Compare the reported loss after correcting for WDL against the
expected value from the EDP/IDP.
— Clean the fibers for the Line A input port under the following
conditions:
— If the span loss source from “OSC” is 3 dB higher than expected.
— If the span loss source from “TG” is 2 dB higher than expected.
• If the span loss measurement from either source is lower than the
expected span loss, then no further action is required.
• If the loss is still greater than expected, you may need to verify the
connections on the next network element at the other end of the line or
test the optical line to find the source of the additional attenuation.
The Rx path loss is a provisionable value that corresponds to the total loss
from the Tx to the span input and the loss from the span output to the drop
port. The relation between the actual measurement and the displayed span
loss is:
Displayed span loss = Measured loss - Rx path loss


Step Action
Verifying fiber loss

17 If the line circuit pack is an SRA/ESAM/SAM, verify that there are no High
Fiber Loss alarms raised between the amplifier (XLA or MLAx) and the
SRA/ESAM/SAM. The fiber loss thresholds are provisioned in the respective
ADJ-FIBER facility fields. When the fiber loss exceeds the provisioned excess
loss for that fiber by more than the provisioned threshold, the “High Fiber
Loss” alarm is raised if the High Fiber Loss Detection Alarm system
parameter is enabled (default value is enabled). For more information, see
Verifying OSC BER
18 Ensure that the OSC Bit Error Rate is acceptable. In the Equipment and
Facility Provisioning application, check the OSC facility table. Verify that the
value displayed in the “Estimated Bit Error Rate” column is better than
1.0E-11 or as indicated in the EDP/IDP.
Verifying ORL
19 If the line facing circuit pack is an ESAM, MLA, MLA2, MLA2 w/VOA, or
MLA3, or if an XLA is present, put the post-amplifier in no shutoff mode. In the
Equipment & Facility Provisioning application:
• Retrieve the facility information of the Line B AMP facility (port 6).
• If present, also retrieve the facility information of the ESAM/SAM
OPTMON facility (port 6).
• Set the SRA/ESAM/SAM OPTMON facility parameter ALSO Disabled to
True.


Step Action
MLA3, or if an XLA is present, use the PM function to measure the optical
return loss (ORL) at the post-amplifier output by performing the following.
• Select Performance->Performance Monitoring to open the PM
window.
• Review the untimed ORL-OTS reading in the Performance Count(s) list.
For the post-amplifier (AMP-<shelf>-<slot>-6 for non-MLA2 w/VOA or
VOA-<shelf>-<slot>-5 for MLA2 w/VOA), the measurement in the
Untimed bin should be stable and greater than 28 dB. When DSCMs are
used and the DSCM location is at the head end of the span (collocated
with the amplifier being commissioned), the minimum ORL threshold to
• If the reading is stable, but less than the required threshold, clean all fiber
connections at the amplifier output and verify that any patch fibers used
are clean and have no pinches or bends.
• If the ORL reading is OOR, check if the amplifier is provisioned to IS.
MLA3, or if an XLA is present, put the post-amplifier back to shutoff mode:
• Set the AMP facility parameter ALSO Disabled to False.
• If present, also set the ESAM/SAM OPTMON facility parameter ALSO
Disabled to False.
Running OTDR trace (if required)
Note: OTDR traces are supported on the ESAM and SRA circuit packs.
22 Run a manual short OTDR trace, see ‘OTDR trace’ chapter in Part 2 of
Configuration - Provisioning and Operating, 323-1851-310, for details.
23 Check that the single/total losses for any events are below the thresholds.
Refer to Photonic Layer Guide, NTRN15DA, for details on the types of events
and how to interpret the OTDR traces.
Note: If the single/total losses for any events are above the thresholds, if
necessary clean the optical interface connector sleeve inside the circuit pack
and the connectors and adapters on the patch cords. Refer to the ‘Cleaning
connectors’ section in Installation - General Information, 323-1851-201.0, for
detailed cleaning procedures.
Repeat for other line facing directions
24 If necessary, repeat this procedure from step 3 onwards for the other line
facing directions.
—end—

Procedure 4-23
Configuring a single span 100 GHz CMD44
point-to-point terminal
Use this procedure to configure a single span CMD44 Terminal or in an
amplified or unamplified configuration. See Figure 4-103 on page 4-337 and
For more information on supported single span configurations and

engineering rules, refer to 6500 Packet-Optical Platform Photonic Layer
Guide, NTRN15DA.
Only 100GHz CMD44 type is supported. 50 GHz CMD44 is not supported.
Step Action
1 Add the CMD44 module. See Procedure 4-2, “Adding a new CMD44,
CMD64, CMD16, CMD24, CMD96, or BMD2”.
2 If you are configuring Then
an amplified configuration go to step 3
3 Insert an SLA in the slot as indicated in the EDP/IDP.

4 If a 2xOSC or SPAP-2 w/2xOSC circuit pack is required, insert it in the slot as
5 Connect the Common Out (port 90) of the CMD44 to the Line B In (port 6) of
the SLA.
6 Connect the Common In (port 89) of the CMD44 to the Line A Out (port 7) of
the SLA.
7 If applicable, connect the 2xOSC OSC-1 Out port to the OSC In (port 3) of the
SLA. Connect the 2xOSC OSC-1 In port to the OSC Out (port 4) of the SLA.
8 In Site Manager connected to the shelf, select Configuration -> Equipment
& Facility Provisioning. Select the amp facility associated with the SLA, in
the form of AMP-<shelf>-<AMP slot>-8. Click Edit and enter 20 dB of Target
Gain.
9 Check that the equipment inventory has been updated to include the module
you have just connected. If the equipment inventory does not include the new
module, the module may still be being upgraded. Wait until the active LED on
the module is lit and not blinking, then click on the Refresh button.


Configuring a single span 100 GHz CMD44 point-to-point terminal
Step Action
Connecting DWDM services

10 Connect Tx to appropriate CMD44 input ports and Rx to appropriate CMD44
output ports.
Note: Connect the Tx only to CMD44 input ports. Mis-connecting the Tx to
a non-enhanced CMD44 output port can generate APR in the amp. The
100GHz eCMD44 has an embedded isolator after the Common In port, which
prevents the amp from entering the APR state.
11 Repeat step 1 to step 10 at the other end of the span.
(transmit path).
13 Repeat step 12 at the other end of the span.
Provisioning and verifying DWDM services
14 Provision the Tx/Rx to the values prescribed in the link budget for both
directions (if bidirectional link).
15 Verify that the DWDM is operating properly by checking the alarms and the
BER monitor.
—end—

Figure 4-103
Release 12.7
LC
LC
TX LC Ch 1 In 100GHz CMD44 100GHz CMD44 LC TX
Unprotected Ch 1 In
1 1
2 2
Ch 1 Out Ch 1 Out
RX LC Ch 2 In Ch 2 In LC RX
LC 3 3 LC
4 4
Ch 2 Out LC Ch 2 Out
Common Out LC Common In

90 Inter-office fiber 89
89 90
Common In Common Out
LC Ch 43 In Ch 43 In LC
85 85
86 86
Ch 43 Out Ch 43 Out
LC Ch 44 In LC
Ch 44 In
87 87
88 88
Ch 44 Out Ch 44 Out
Legend
CMD44 single span point-to-point unamplified configuration
= DSCM (optional)
= Pad (optional)

May 2020
Figure 4-104
CMD44 single span point-to-point amplified configuration

Procedure 4-24
Configuring a single span 100 GHz CMD16/CMD24
Use this procedure to configure a single span CMD16/CMD24 Terminal or in
an amplified or unamplified configuration. See:
• “CMD16 or CMD 24 single span point-to-point unamplified configuration
(CMD16 shown)” on page 4-341
• “CMD16 or CMD24 single span point-to-point amplified configuration
(CMD16 shown)” on page 4-341
• “Cascaded CMD16/CMD 24 single span point-to-point amplified
configuration” on page 4-342.
Note 1: Adding a CMD24 to a CMD16 upgrade port (or vice versa) is

traffic affecting since the terminator needs to be unplugged from the
Upgrade Out port causing the pre-amp to go in APR.
Note 2: An unamplified cascaded CMD16/CMD24 single span
configuration is not supported.
Note 3: In the current release, software support for the CMD16 and
CMD24 modules is limited to Inventory only (no Equipment/facility,
topology, or control support).
Guide, NTRN15DA.
Step Action
1 Add the CMD16 and/or CMD24 modules. See Procedure 4-2, “Adding a new
CMD44, CMD64, CMD16, CMD24, CMD96, or BMD2”.
2 If you are connecting Then
a cascaded CMD16/CMD24 or go to step 3
CMD24/CMD16
Connecting the CMD16/CMD24 cascade

3 If CMD16/CMD24 or CMD24/CMD16 cascading is required:
a. Starting with the CMD16 or CMD24 that is to be connected to line fiber or
the line facing module according to the EDP/IDP.
b. Connect the Upgrade In of the CMD16/CMD24 to the Common Out of the
other CMD16/CMD24.


Configuring a single span 100 GHz CMD16/CMD24 point-to-point terminal
Step Action
c. Connect the Upgrade Out of the CMD16/CMD24 to the Common In of the

other CMD16/CMD24.
d. Ensure that low reflection terminator is connected on the Upgrade Out
port if unused on the CMD16/CMD24.
Connecting the amplifier

5 Insert an MLAx in the slot as indicated in the EDP/IDP.
7 Connect the Common Out of the CMD16 or CMD24 to the Line B In (port 6)
of the MLAx.
8 Connect the Common In of the CMD16 or CMD24 to the Line A Out (port 7)
of the MLAx.
SLA. Connect the 2xOSC OSC-1 In port to the OSC Out (port 4) of the MLAx.
& Facility Provisioning. Select the amp facility associated with the MLAx, in
Gain.
11 Check that the equipment inventory has been updated to include the module
module, the module may still be being upgraded. Wait until the active LED on
the module is lit and not blinking, then click on the Refresh button.
12 Connect Tx to appropriate CMD16/CMD24 input ports and Rx to appropriate
CMD16/CMD24 output ports.
Note: Connect the Tx only to CMD16/CMD24 input ports. Mis-connecting the
Tx to a CMD16/CMD24 can generate APR in the amp.
(transmit path).


Configuring a single span 100 GHz CMD16/CMD24 point-to-point terminal
Step Action
15 Repeat step 14 at the other end of the span.

BER monitor.
—end—
Figure 4-105
CMD16 or CMD 24 single span point-to-point unamplified configuration (CMD16 shown)
Figure 4-106
CMD16 or CMD24 single span point-to-point amplified configuration (CMD16 shown)

Figure 4-107
Cascaded CMD16/CMD 24 single span point-to-point amplified configuration

Procedure 4-25
Configuring a single span OMD4/CMD44 or OMX
Use this procedure to configure a single span OMD4/CMD44 terminal in an
amplified or unamplified configuration, or to configure a single span OMX
terminal in an unamplified configuration. See Figure 4-108 on page 4-346 to

Guide, NTRN15DA.
Step Action
1 Add the required OMD4/CMD44 or OMX modules as indicated in the

EDP/IDP. See Procedure 4-3, “Adding a new OMD4 or OMX” and
Procedure 4-2, “Adding a new CMD44, CMD64, CMD16, CMD24, CMD96, or
BMD2”.
Connecting the OMD4/CMD44 or OMX cascade
2 If OMD4/CMD44 cascading is required:
a. Starting with the OMD4 that is to be connected to line fiber or the line
facing module according to the EDP/IDP.
b. Connect the Upgrade In (port 11) of the OMD4 to the Common Out
(port 2) of the next OMD4.
c. Connect the Upgrade Out (port 12) of the OMD4 to the Common In
(port 1) of the next OMD4.
d. Repeat from substep a on the next OMD4 to connect another OMD4 if
applicable.
e. If the last module in the cascade is a CMD44, connect the Upgrade In
(port 11) of the OMD4 to the Common Out (port 90) of the CMD44.
Connect the Upgrade Out (port 12) of the OMD4 to the Common In
(port 89) of the CMD44.
f. If the last module in the cascade is an OMD4, terminate its upgrade port
with a terminator pad.


Configuring a single span OMD4/CMD44 or OMX point-to-point terminal
Step Action
3 If OMX cascading is required:

a. Starting with the OMX that is to be connected to line fiber according to
the EDP/IDP.
b. Connect the THRU In (port 11 on 4-channel OMX or port 35 on
16-channel OMX) of the OMX to the OTS Out (port 2) of the next OMX.
c. Connect the THRU Out (port 12 on 4-channel OMX or port 36 on
16-channel OMX) of the OMX to the OTS In (port 1) of the next OMX.
d. Repeat from substep a on the next OMX to connect another OMX.
5 Insert an SLA in the slot as indicated in the EDP/IDP.

7 Connect the Common Out (port 2) of the OMD4 that is to be connected to the
SLA to the Line B In (port 6) of the SLA.
8 Connect the Common In (port 1) of the OMD4 that is to be connected to the
SLA to the Line A Out (port 7) of the SLA.
SLA. Connect the 2xOSC OSC-1 In port to the OSC Out (port 4) of the SLA.
& Facility Provisioning. Select the amp facility associated with the SLA, in
Gain.
11 Check that the equipment inventory has been updated to include the modules
modules, the modules may still be being upgraded. Wait until the active LED
on the modules is lit and not blinking, then click on the Refresh button.
12 Connect Tx to appropriate OMD4/CMD44 or OMX input ports and Rx to
appropriate OMD4/CMD44 or OMX output ports.
Note: Connect the Tx only to OMD4 and CMD44 input ports. Mis-connecting
the Tx to a non-enhanced CMD44 output port can generate APR in the amp.
The 100GHz eCMD44 and OMD4 have an embedded isolator after the
Common In port, which prevents the amp from entering the APR state.


Configuring a single span OMD4/CMD44 or OMX point-to-point terminal
Step Action

14 For OMD4/CMD44 unamplified single span, connect the line fibers to the
OMD4 Common In port (receive path) and the OMD4 Common Out port
(transmit path).
15 For OMD4/CMD44 amplified single span, connect the line fibers to the
amplifier Line A input port (receive path) and the Line B output port (transmit
path).
16 For OMX unamplified single span, connect the line fibers to the OMX OTS In
port (receive path) and the OMX OTS Out port (transmit path).
17 Repeat step 14, step 15 or step 16 at the other end of the span.
BER monitor.
—end—

Figure 4-108
OMD4/CMD44 single span point-to-point unamplified configuration

Figure 4-109
OMD4/CMD44 single span point-to-point amplified configuration

Figure 4-110
OMX single span point-to-point unamplified configuration (4 CH OMX shown)

Procedure 4-26
Equalizing a thin terminal system
The thin terminal refers to any cascades of OMDF4/CMD44, OMDF8/BS,
CMD16/CMD24, or CMD44 connected to any LIM variants (LIM, SLA, and
MLAx). MLAx means MLA, MLA2, MLA2 w/VOA, or MLA3. The thin terminal
is defined using the TOADM OTS type in the OTS provisioning model. The
TOADM OTS is used to enable a topology view of channels whose Tx/Rx
adjacencies are subsequently provisioned on channel In/Out ports.
The thin terminals are used in a standalone point to point system. Up to two
line amplifier sites are supported depending on the link budget.
CAUTION
Risk of traffic loss
The OTS provisioning for a thin terminal system includes
setting DOC to TRUE for the OTS. However, the DOC must be
put OOS and channels must be equalized manually. Refer to
6500 Packet-Optical Platform Photonic Layer Guide,
NTRN15DA, for detailed information on photonic concepts,
applications, and engineering rules.
A view of all channels in topology (built via Tx/Rx adjacency provisioning at

both ends of the link) is presented to the user in the Site Manager DOC screen
but no operations are performed using DOC, since DOC is OOS and not used.
Use this procedure to equalize a thin terminal point to point system. Typical
thin terminal systems are shown in Figure 4-111 on page 4-350. The target
power into line fiber is 0 dBm/ch.


Figure 4-111
Typical thin terminal systems
You must provision the amplifier target gain (AMP A and AMP B) to their
design flat gain (DFG) values as indicated in Table 4-16. The target gain tilt
should be left at the default value of 0 dB.
Table 4-16
Amplifier design flat gains
Circuit pack AMP A AMP B
SLA 20 dB N/A
MLA 20 dB 17 dB
MLA2, MLA2 w/VOA, MLA3 23.5 dB 23.5 dB
For MLA2 w/VOA, set the VOA reset required parameter of the VOA facility to
False and set the Target Loss parameter based on the calculated value for:
• downstream Z (SPAN) at Terminal and Line amplifier
• downstream Z (MID) at Line amplifier


The following is a description of the pad placement at a thin terminal site (see
Figure 4-112):
• Channel Add Pads Z(add,n) – Placed at the channel input of a channel
Mux/Demux module to provide target output power at Line B OUT. See
Table 4-17 on page 4-352 for the Line B target output power.
• SPAN Pads Z(SPAN) – Sized to set the loss between upstream Line B
OUT and local Line A In equal to the local AMP A design flat gain. See
• Channel Drop Pads Z(drop,n) – Placed before the receive port of a
transponder's DWDM interface to set the channel RX power below its
overload threshold. Refer to the Technical specifications section in Part 3
of Planning, NTRN10FG, for overload threshold values of each OTR,
OCLD or pluggable module.
• 3 dB pad between Line A Out and CMD Common In – This pad is to
prevent the pre-amplifier from being triggered into APR due to back
reflections from unterminated CMD ports. The 3 dB pad is not required
with LIM circuit pack (NTK552DAE5) or if the CMD connecting to
SLA/MLAx is eCMD44 (NTT862FAE5).
Figure 4-112
Pad placement at a thin terminal site


Table 4-17
Terminal line B target output power (up to 40 channels)
Channel Count Output Power (dBm) Channel Count Output Power (dBm)
1 0.1 21 13.2
2 3.1 22 13.4
3 4.8 23 13.6
4 6.1 24 13.8
5 7.0 25 14.0
6 7.8 26 14.2
7 8.5 27 14.3
8 9.0 28 14.5
9 9.6 29 14.6
10 10 30 14.8
11 10.4 31 14.9
12 10.8 32 15.1
13 11.2 33 15.2
14 11.5 34 15.3
15 11.8 35 15.4
16 12.1 36 15.6
17 12.3 37 15.7
18 12.6 38 15.8
19 12.8 39 15.9
20 13.0 40 16.0
The following is a description of the pad placement at a line amplifier site (see
Figure 4-113 on page 4-353):
• SPAN Pads Z(SPAN) – Sized to set the loss between upstream Line B
OUT and local Line A In equal to the local AMP A design flat gain. See
Table 4-16 on page 4-350. If there is no local AMP A (LIM circuit pack),
Z(SPAN) = 0 dB (no pad).
• Midstage Pads Z(MID) – Sized to set the loss between local Line A OUT
and local Line B In equal the local AMP B design flat gain. See Table 4-16
on page 4-350.
— If there is no local AMP B (LIM or SLA circuit pack), Z(MID) = 0 dB (no
pad) with no DSCM1 or Z(MID) = 8 dB with DSCM1
— If there is no local AMP A (LIM circuit pack), Z(MID) is sized to set the
loss between the upstream Line B Out and local Line B In equal to the
local AMP B design flat gain.


Figure 4-113
Pad placement at a line amplifier site
Figure 4-114 shows a simplified thin terminal network. Only key elements
involved in the equalization process are shown.
Figure 4-114
Simplified thin terminal network for equalization purposes
Prerequisites
All actions contained in this procedure are to be executed on an OTS that was
previously created and defined.
All the equipment that are part of the OTS being worked on have all been
installed and provisioned properly.
All fibers connecting the equipment that are part of the OTS being worked on
have all been installed properly (labeled, routed, cleaned, inspected and
connected).


Fibers between the DWDM transmitters and the appropriate MUX ports have
all been labeled, routed, cleaned, inspected and connected at both ends.
Fibers that are to connect the DWDM receivers to the DEMUX port have been
labeled, routed, cleaned, inspected and connected to the DEMUX ports but
not to the receivers. Instead the ends that are to be connected to the DWDM
receivers should be protected by dust caps.
Refer to the Attenuators table in Planning - Ordering Information,

323-1851-151 for pad values and pad numbers.
All transponder line interfaces in the design must be present with transmit
ports enabled and outputting proper optical power levels.
To perform this procedure, you require:

• an optical power meter (OPM)
• a variety of fixed pads, fiber-optic connectors, inspection & cleaning tools
• an account of UPC level 3 or higher
This procedure provides high level steps with respect to using the Site
Manager Equipment & Facility Provisioning application and the Performance
Monitoring application. Refer to Part 1 of Configuration - Provisioning and
Operating, 323-1851-310 and Fault Management - Performance Monitoring,
323-1851-520 for detailed procedures.
Step Action
Equalizing the thin terminal system initially

1 Start with one direction, either from west to east terminal, or east to west
terminal. See Figure 4-114 on page 4-353.
2 At the near end thin terminal site, if the line facing amplifier is a LIM or SLA
circuit pack, go to step 6.
3 In the Equipment & Facility Provisioning application, select the LIM
equipment for the line facing amplifier.
4 Provision the AMP-<shelf>-<slot>-6 facility.
• set the target gain to the design flat gain of the AMP as indicated in Table
4-16 on page 4-350
• set target gain tilt to 0 dB


Step Action
5 If the line facing amplifier is an MLA2 w/VOA, set the VOA-<shelf>-<slot>-5

facility VOA Reset Required to False. Otherwise, go to step 6.
6 For each channel, calculate the total insertion loss from the channel input to
Line B In, including all passive filter insertion losses in between. See Table
4-18 on page 4-361 for the typical insertion loss of the equipment used in your
configuration.
The initial pad for the channel = transponder Tx power (dBm) - total insertion
loss (dB) + design flat gain of AMP B as indicated in Table 4-16 on page 4-350
(or 0 dB gain if no AMP B)
7 Select the appropriate pad to place at the CMD channel input so that the
target output power at Line B OUT will be as indicated in Table 4-17 on page
4-352. This is Z(add, n).
• connect the first channel with the initial pad, make sure all other channels
are disconnected
• check Line B OUT power with the untimed OPOUT-OTS value for
AMP-<shelf>-<slot>-6 (with AMP B) or the untimed OPR-OTS value for
OPTMON-<shelf>-<slot>-6 (no AMP B) in the PM application
• adjust the pad value, 1 dB at a time, until Line B OUT power is as
indicated in Table 4-17 on page 4-352 for one channel
• connect the second channel with its initial pad
• check Line B OUT power
• adjust the pad value until Line B OUT power is as indicated in Table 4-17
on page 4-352 for two channels
• repeat this process for each subsequent channel until all Z(add, n) pads
are selected
8 If the downstream site is not a line amplifier site, go to step 22.
9 At the line amplifier site, if the first line facing amplifier is a LIM circuit pack,
go to step 15.


Step Action
10 At the line amplifier site, calculate the Z(SPAN) pad connected to the first line
facing amplifier.
• measure the upstream Line B OUT output power, that is, the untimed
OPOUT-OTS value for the upstream AMP-<shelf>-<slot>-6 (with AMP B)
or the untimed OPR-OTS value for the upstream
• measure the power at the local Line A In, that is, the untimed OPIN-OTS
value for the local AMP-<shelf>-<slot>-8 (with AMP A) or the untimed
OPR-OTS value for the local OPTMON-<shelf>-<slot>-8 (no AMP A) in
the PM application
• upstream span loss (dB) = upstream Line B OUT power (dBm) - local
Line A In power (dBm)
• Z(SPAN) (dB) = DFG of the first line facing amplifier (from Table 4-16 on
page 4-350) - upstream span loss (dB)
11 If the upstream amplifier is an MLA2 w/VOA, set the VOA-<shelf>-<slot>-5
facility Target Loss to Z(SPAN). Otherwise, place a fixed attenuator with a
value of Z(SPAN) at the Line A In (port 8) of the first line facing amplifier.
equipment for the first line facing amplifier.
4-16 on page 4-350
14 If the first line facing amplifier is an MLA2 w/VOA, set the
VOA-<shelf>-<slot>-7 facility VOA Reset Required to False. Otherwise, go to
step 15.


Step Action
15 Calculate the Z(MID) pad from the first line facing amplifier to the second line
facing amplifier.
• measure the Line A OUT power, that is, the untimed OPOUT-OTS value
for the local AMP-<shelf>-<slot>-8 (with AMP A) in the PM application
If there is no local AMP A, use the upstream Line B OUT power, that is,
the untimed OPOUT-OTS value for the upstream AMP-<shelf>-<slot>-6
(with AMP B) or the untimed OPR-OTS value for the upstream
OPTMON-<shelf>-<slot>-6 (no AMP B) in the PM application.
• measure the power at the Line B In of the second line facing amplifier,
that is, the untimed OPIN-OTS value for the local AMP-<shelf>-<slot>-6
(with AMP B) in the PM application
• Midstage loss (dB) = Line A OUT power (dBm) - Line B In power (dBm)
(with local AMP A)
or
Midstage loss (dB) = upstream Line B OUT power (dBm) - local Line B In
power (dBm) (no local AMP A)
• Z(MID) (dB) = DFG of the second line facing amplifier (from Table 4-16
on page 4-350) - Midstage loss (dB)
If there is no local AMP B, Z(MID) = 0 dB (no pad) with no DSCM1 or Z(MID)
= 8 dB with DSCM1.
16 If the first line facing amplifier is an MLA2 w/VOA, provision the
VOA-<shelf>-<slot>-7 facility Target Loss to Z(MID). Otherwise, place a fixed
attenuator with a value of Z(MID) at the Line B In (port 6) of the second line
facing amplifier.
17 If the second line facing amplifier is a LIM or SLA circuit pack, go to step 21.
equipment for the second line facing amplifier.
4-16 on page 4-350
20 If the second line facing amplifier is an MLA2 w/VOA, provision the
VOA-<shelf>-<slot>-5 facility VOA Reset Required to False. Otherwise, go to
step 21.
21 If the downstream site is another line amplifier site, repeat from step 9 for the
next line amplifier site.
22 At the far end thin terminal, if the line facing amplifier is a LIM circuit pack, go
to step 28.


Step Action
23 At the far end thin terminal site, calculate the Z(SPAN) pad.
• measure the upstream Line B OUT output power, that is, the untimed
OPOUT-OTS value for the upstream AMP-<shelf>-<slot>-6 (with AMP B)
or the untimed OPR-OTS value for the upstream
• measure the power at the local Line A In, that is, the untimed OPIN-OTS
value for the local AMP-<shelf>-<slot>-8 (with AMP A) or the untimed
OPR-OTS value for the local OPTMON-<shelf>-<slot>-8 (no AMP A) in
the PM application
• upstream span loss (dB) = upstream Line B OUT power (dBm) - local
Line A In power (dBm)
• Z(SPAN) (dB) = DFG of the line facing amplifier (from Table 4-16 on page
4-350) - upstream span loss (dB)
24 If the upstream amplifier is an MLA2 w/VOA, set the VOA-<shelf>-<slot>-5
facility Target Loss to Z(SPAN). Otherwise, place a fixed attenuator with a
value of Z(SPAN) at the Line A In (port 8) of the line facing amplifier.
equipment for the line facing amplifier.
4-16 on page 4-350
27 If the CMD module connecting to the line facing amplifier is not an eCMD44
(NTT862FAE5), connect a 3 dB pad between Line A Out and CMD Common
In.
28 Select the appropriate pad to place at the input of each receiver. This is
Z(drop,n).
• for each channel being dropped, connect an OPM on the CMD channel
output port and measure the dropped channel power
• determine the pad required to set the power below the receiver overload
level
• repeat this step until all Z(drop, n) pads are selected
29 Repeat from step 2 for the opposite direction.


Step Action
30 Reset the PM baseline for both Line A (AMP-<shelf>-<slot>-8 with AMP A or

OPTMON-<shelf>-<slot>-8 with no AMP A) and Line B
(AMP-<shelf>-<slot>-6 with AMP B or OPTMON-<shelf>-<slot>-6 with no
AMP B) at both West and East terminal sites.
Refer to the “Resetting the PM physical baseline power level” procedure in
Fault Management - Performance Monitoring, 323-1851-520.
You have completed the initial system equalization.
Adding or removing a channel to/from an existing thin terminal network
Adding a channel
31 At the near end thin terminal, calculate the total insertion loss from the
channel input to Line B In, including all passive filter insertion losses in
between. See Table 4-18 on page 4-361 for the typical insertion loss of the
equipment used in your configuration.
The initial pad for the channel = transponder Tx power (dBm) - total insertion
loss (dB) + design flat gain of AMP B as indicated in Table 4-16 on page 4-350
(or 0 dB gain if no AMP B)
32 Select the appropriate Z(add, n) pad for the new channel at the CMD channel
input so that the target output power at Line B OUT will be as indicated in
• connect the channel with the initial pad
• check Line B OUT power with the untimed OPOUT-OTS value for
AMP-<shelf>-<slot>-6 (with AMP B) or the untimed OPR-OTS value for
• adjust the pad value, 1 dB at a time, until Line B OUT power is as
indicated in Table 4-17 on page 4-352 for the channel count value of
(current channel count + 1)
33 At the far end thin terminal, select the appropriate Z(drop,n) pad to place at
the input of each receiver for the new channel.
• for the channel being dropped, connect an OPM on the CMD channel
output port and measure the dropped channel power
• determine the pad required to set the power below the receiver overload
level
34 Repeat step 31 and step 33 for the opposite direction.


Step Action

You have completed adding a new channel to an existing system.
Removing a channel
36 At the near end thin terminal, disconnect the channel to be removed from the
CMD channel input. Remove the Z(add,n) pad associated with the deleted
channel.
37 At the far end thin terminal, disconnect the channel to be removed from the
CMD channel output. Remove the Z(drop,n) pad associated with the deleted
channel.
38 Repeat step 36 and step 37 for the opposite direction.
You have completed removing a channel from an existing system.
—end—

Table 4-18
OMDF4, OMDF8, BS5, CMD44, CMD16, and CMD24 typical insertion loss in the
Mux direction
Input port Output port Typical loss (dB)

OMDF4
Ch 1 In NTWK OUT 1.0
EXPR IN NTWK OUT 1.2
OMDF8
BS5
Group A In NTWK OUT 1.2
Group B In NTWK OUT 1.3
Group C In NTWK OUT 1.5
Group D In NTWK OUT 1.7
Group E In NTWK OUT 1.9
CMD44
Ch n In Common Out 4.0 (minimum loss)
CMD16
Ch n In Common Out 4.8 (maximum loss)
Upgrade In Common Out 1.2 (maximum loss)
CMD24
Ch n In Common Out 5.1 (maximum loss)
Upgrade In Common Out 1.4 (maximum loss)

Procedure 4-27
Configuring a remote CMD44 terminal
Use this procedure to configure a remote CMD44 terminal. For supported
configurations, refer to 6500 Packet-Optical Platform Photonic Layer Guide,
NTRN15DA.
Step Action
Fibering the remote CMD44 to the optical line

1 Fiber the remote CMD44 to the optical line ensuring that the loss is as per link
budget calculations.
2 In Site Manager connected to the shelf, click on Configuration ->
Equipment & Facility Provisioning.
Provisioning the CMD44
3 Provision the CMD44 as follows:
• Click on the Add button in the equipment area.
• Select the right type of CMD44 (50GHz Red or Blue or 100GHz).
• Select a slot between 91-99.
• Click OK to confirm the changes.
Note: Choosing a slot between 83-90 will trigger the remote equipment not
supported alarm.
Provisioning the Excess Loss parameter
4 In the Equipment table, select the WSS by clicking on it once. In the Facility
table, select ADJ-Fiber. Select the WSS demux port associated with the
remote CMD44 demux input.
5 Click Edit and provision the Excess Loss parameter with the measured loss
of the fiber between the WSS demux out and the remote CMD44 demux in.
6 Click OK to confirm the changes.
7 In the Equipment table, select the remote CMD44 by clicking on it once. In the
Facility menu, select ADJ-Fiber. Select the CMD44 Mux out (port 90).
8 Click Edit and provision the Excess Loss parameter with the measured loss
of the fiber between the remote CMD44 Mux out and the WSS Mux in.
9 Click OK to confirm the changes.
—end—

Procedure 4-28
Connecting intra-site fibers for 1x20 Colorless
Directionless (CD) ROADM with FIM4 sites
Use this procedure to perform intra-site fiber connections at a 1x20 CD
ROADM with FIM4 site.
The following figures show examples of the CD ROADM with split FIM
configurations:
• “Intra-NE fiber connections at a 1x20 CD with FIM4 site (15x15
configuration with add/drops)” on page 4-368
• “Intra-NE fiber connections at a 1x20 CD with FIM4 site (20 degree
configuration without add/drops)” on page 4-369
This procedure does not cover any other ROADM site configurations. You
must connect the intra-site fibers of such ROADM sites based on the specific
network configurations.
Do not make the FIM to FIM connections during this procedure. For a 1x20
CD ROADM with FIM4 configuration, fiber connections between the FIMs are
done during 1x20 CD ROADM with FIM4 testing in Procedure 4-29, “Site
testing for 1x20 Colorless Directionless (CD) ROADM with FIM4”.
The following shelf slotting requirements apply:

• For the Degree/OTS equipment:
— All the equipment forming the degree must be equipped in the same
shelf.
• For the Add/drop structure equipment:
— The FIM4 must be equipped in the same shelf as the SMD.
— The CCMD12 and SMD can be in the same shelf or in different
shelves.
• The transponder equipment can be in the same shelf as the degree/OTS
equipment or in the same shelf as the add/drop structure equipment or in
a different shelf.
• All shelves at the node containing the degree/OTS equipment, the
add/drop structure equipment and the transponder equipment must be
TID consolidated.


Connecting intra-site fibers for 1x20 Colorless Directionless (CD) ROADM with FIM4 sites
• The maximum number of supported shelves at a TIDc node:

— 36 if primary shelf is equipped with SP2
— 16 if primary shelf is equipped with SPAP-2

Prerequisites
subtending modules (FIM).
CAUTION
DANGER
Risk of injury


shelf)
CAUTION
for any reason.

connection.
DANGER
Risk of injury
For a FIM Type 4 module and to respect the 1M laser
safety limit on the aggregate MPO output, the individual
input powers to the LC ports must be <=13 dBm.
• These configurations include Fiber Interconnect Modules (FIM). FIMs are

required by applications that use the FIM, the loopback modules act as
dust caps for the optical ports. Do not remove the loopback modules
except as part of a fiber installation procedure. The FIM tray assembly
includes a bag of dust caps that must be put on any loopback connector
that is being removed and saved for future use. For more information, see
the Photonic passive modules table in Planning - Ordering Information,
323-1851-151.
FIM Type 4 is shipped with the Duplex LC Loopback (SM) modules in each
of the duplex LC connector positions pre-installed.


Step Action
EDP/IDP.
cables to circuit packs in the Installation technical publication specific to the
respective 6500 shelf type.
Connect the intra-site fibers. See examples in the following illustrations:
• 15 degrees x15 add/drops with full express connectivity and up to 5
add/drops for each degree - Figure 4-115 on page 4-368
• 20 degree with full express connectivity and no add/drops - Figure 4-116
on page 4-369
Do not connect the FIM to FIM connections at this point. These connections
will be done as part of the 1x20 CD ROADM with FIM4 testing
(Procedure 4-29, “Site testing for 1x20 Colorless Directionless (CD) ROADM
with FIM4”).
Each ROADM OTS contains a WSS 1x20, XLA, and SRA/ESAM/SAM or a
WSS 1x20 and a MLA3.
For the 15x15 configuration with add/drops:
• Recommended WSS port usage
— WSS-WSS interconnections start at port 5, then 6 and 7.
— Port 8 used for WSS-SMD interconnection and can support up to 5
selective add/drop banks (any 5 out of the 15 add/drop banks).
• Recommended FIM4 (connected to WSS) port usage
— Ports 38/39 are used for future channel expansion.
— Ports that connect to WSS ports 5, 6, and 7 are used for WSS-WSS
interconnections.
— Ports that connect to WSS port 8 are used for WSS-SMD
interconnection and can support up to 5 selective add/drop banks
(any 5 out of the 15 add/drop banks).
• Recommended FIM4 (connected to SMD) port usage
— 6 pairs of ports marked in red in Figure 4-115 on page 4-368 on the
FIM are unusable ports as they are not physically connected to any
SMD port.
— Each FIM4 can connect up to 14 degrees as add/drops.
Note: While this port usage is recommended, other port usage is allowed.
The flexibility of fiber connections is everywhere that includes the locations
between WSS and FIM, FIM and FIM, FIM and SMD, as well as SMD and
CCMD12(s), under the condition that provisioning is correct.


Step Action
For the 20 degree configuration without add/drops:

• Recommended FIM port usage
— Ports 48/49 are used for future channel expansion.
— All the other 19 pairs of fibers are used for full 20 degree
interconnection.
— Passthrough fibers start from the ones corresponding to WSS port 5
and then moving to higher # ports.
Note: While this port usage is recommended, other port usage is
allowed. The flexibility of fiber connections is everywhere that includes
the locations between WSS and FIM as well as between FIM and FIM,
under the condition that provisioning is correct.
—end—

Figure 4-115
Intra-NE fiber connections at a 1x20 CD with FIM4 site (15x15 configuration with add/drops)

Figure 4-116
Intra-NE fiber connections at a 1x20 CD with FIM4 site (20 degree configuration without
add/drops)

Procedure 4-29
Site testing for 1x20 Colorless Directionless (CD)
ROADM with FIM4
Use this procedure to test 1x20 Colorless Directionless (CD) ROADM with
FIM4 configurations. See examples in:
• “Intra-NE fiber connections at a 1x20 CD with FIM4 site (15x15
configuration with add/drops)” on page 4-368
• “Intra-NE fiber connections at a 1x20 CD with FIM4 site (20 degree
configuration without add/drops)” on page 4-369
1x20 Colorless Directionless (CD) ROADM with FIM4 configurations include

Fiber Interconnect Modules (FIM) Type 4. FIM Type 4 is shipped with the
Duplex LC Loopback (SM) modules in each of the duplex LC connector
positions pre-installed.
In addition to providing the optical loopback operation required by applications

that use the FIM, the loopback modules act as dust caps for the optical ports.
Do not remove the loopback modules except as part of a fiber installation
procedure. The FIM tray assembly includes a bag of dust caps that must be
put on any loopback connector that is being removed and saved for future use.
For more information, see the Photonic passive modules table in Planning -
Ordering Information, 323-1851-151.
Prerequisites
• Make sure that you have a copy of the engineering data sheet.
• Have a user account with a UPC level of 3 or higher.
• Have the following equipment:
— 20 dB optical attenuator
— an LC to LC patch cord (for testing steps that use an optical fiber
loopback)
— an optical power meter
system is complete. The testing steps in this procedure cycle through all
ports on add/drop banks. If you have transponders installed as part of your
system, use them for the testing steps.
For add/drop bank ports where transponders are not connected as part of
your system, use a spare transponder for the testing steps. After testing is
complete on a port, move the spare transponder to the next port you will
be testing that does not have a transponder connected.


Site testing for 1x20 Colorless Directionless (CD) ROADM with FIM4

performing this procedure. Connect all optical fibers within the
configuration.
ATTENTION
The FIM to FIM connections should not be made before starting this
procedure. Ensure that the Duplex LC Loopback (SM) modules are fitted in
each of the duplex LC connector positions.
• The ROADM OTSs must be defined.

shelf)
CAUTION
reason.

connection.
CAUTION


DANGER
Risk of injury
DANGER
Step Action
1 Ensure that the FIM to FIM connections are not installed and that the Duplex
LC Loopback (SM) modules are fitted in each of the duplex LC connector
positions on all FIMs.
2 Ensure that no expected far end addresses (EFEAs) are provisioned for the
FIM to FIM connections (see Procedure 3-2, “Provisioning adjacencies”).
Attention: The OSC ports in this procedure could be on the SPAP-2

w/2xOSC circuit pack, on the 2xOSC circuit pack, or the line facing circuit
testing.
Power parameter.
5 In the Performance Monitoring window, PM Counts tab, select the Shelf and
the Slot from the respective lists, then click Start Monitoring. Under the
OPTMON tab, select the OPTMON facility for OSC Out (port 4) on the line
facing circuit pack connected to the OSC-1 you are testing
(OPTMON-<shelf>-<slot>-4). Record the OPR-OTS Untimed parameter.


Step Action
Testing the MPO interconnects using the Connection Validation application
WSSOPM − MPO loopback connector, WSSOPM − LC loopback connector, SMD14x8 − MPO loopback
connector (if add/drop configuration), SMD14x8 − LC loopback connector (if add/drop configuration)
10 Log into the network element using Site Manager. Select the appropriate
shelf from the Shelf drop-down list.
12 Make sure that the Dark Fiber Loss Measurement system parameter is
Security, 323-1851-301.)
completed.
Clearing, 323-1851-543.


The site equipment uses MPO cables and connectors. For steps to:
CAUTION
for any reason.

connection.

• WSSOPM loopback to itself via FIM4 LC loopback connector
• SMD14x8 loopback to itself via FIM4 LC loopback connector (if add/drop
configuration)
WSSOPM − WSSOPM, WSSOPM − SMD 14x8
16 Connect the FIM to FIM fibers as identified in the EDP/IDP.
17 Provision the far end addresses for the FIM to FIM connections (see
Procedure 3-2, “Provisioning adjacencies”).
Clearing, 323-1851-543.
• WSSOPM − WSSOPM (WSSs from the 2 different degrees)
• WSSOPM − SMD 14x8
20 If the degree being tested Then go to
includes add/drops step 21
does not include add/drops step 37


Step Action
Connecting the transponder and testing with transponder loopback

follows:
testing steps.
22 Make sure the transponder you will be using for the tests is connected to the
CCMD12 In port.
make sure:
323-1851-310.
See Table 4-19 for CCMD12 and SMD maximum loss values and Table 4-20
for maximum FIM loss values.
Table 4-19
CCMD12 NTK508FAE5 13.4 13.4
SMD Flex 14x8 NTK553GC 7.1 7.1
Table 4-20
Fiber Interconnect Module (FIM Type 4) maximum loss
Equipment PEC Maximum insertion loss (dB)
FIM Type 4 NTK504CD Add or Drop, MPO-LC connections: 1.1


Step Action
28 Repeat step 21 to step 27 for all the other CCMD12 In ports in the add/drop
bank, then on all the other add/drop banks.
Validating the fibering to the output of the line facing circuit pack (degrees with add/drops)
The “TX Tuning In Progress” alarm is raised. This is expected. Wait until the
alarm clears.
31 Using patch cords that are known to be in good condition, put a fiber loopback
with the appropriate padding between the line facing circuit pack Line B Out
(port 5) and the line facing circuit pack Line A In (port 8) of the degree being
tested.
MLA3 20 dB
SRA/ESAM/SAM 20 dB
32 On the WSS, open pixel for the CHC-shelf-slot-index:

a. Select Configuration -> Equipment & Facility Provisioning. Select the
CD ROADM WSSOPM in the equipment table.
b. Select the CHC in the Facility drop-down list and select the CHC with the
transmitter chosen in step 30, that is
‘CHC-<shelf>-<slot>-<port>-<index>
c. Set the Opaque state to “No”.
e. Set the Target Loss to 0 dB.


Step Action

If Then go to
to 17 dB:
— Click Edit.
of this procedure.)
then click OK.
Facility drop-down list.
the Line B output port to the input of the pad.


Step Action
to 20 dB:
— Click Edit.
procedure.)
then click OK.
A output port to the input of the CCMD12 (add/drop degrees) or other
line facing circuit pack (degrees with no add/drops).
Go to step 62.


Step Action
36 If an XLA is present, perform the following tasks:

a. On the XLA, edit the Line B AMP facility (AMP-<shelf>-<slot>-6) to set
the target gain to 20 dB and the Gain Mode to HIGH (You will be
instructed to set the XLA AMP facility OOS to modify the Gain Mode.):
— Click Edit.
•Set the primary state to out-of-service (OOS).
•Click Apply.
•Set the primary state back to in-service (IS).
•Click OK.
b. On the XLA, verify the ORL at Line B output:
c. Verify the loss between the Line B Out port of the XLA and the Line B In
port of the line facing circuit pack:
— On the XLA, select port 5 (Line B Out), then select the ADJ-FIBER
facility and check the fiber loss that is reported.
— If the loss is more than 1 dB, check the fibering.


Step Action
d. Verify the loss between the line facing circuit pack and the XLA in the
Demux direction (using Line A):
— On the line facing circuit pack, select port 7 (Line A Out) then select
the ADJ-FIBER facility and check the fiber loss that is reported.
e. On the XLA, edit the Line A AMP facility (AMP-<shelf>-<slot>-8) to set
the target gain to 20 dB and the Gain Mode to HIGH:
— Click Edit.
•Click Apply.
•Click OK.
f. Verify the ORL at Line A output:
the Line A output port to the input of the CCMD12 (add/drop degrees)
or other line facing circuit pack (degrees with no add/drops).
Go to step 62.


Step Action
Validating the fibering to the output of the line facing circuit pack (degrees without add/drops)
The following figure shows an example test setup and is referenced during
the following steps to clarify the locations.
Figure 4-117
Test setup example - 1x20 CD with FIM4 with no add/drops
38 Put the Line A AMP facility (port 8) of the amplifier of the degree under test
(Amp 2 in Figure 4-117) in no shutoff mode as follows:
information.
39 On the Line A AMP (port 8) facility of amplifier of the degree under test (Amp
2 in Figure 4-117):


Step Action

41 Select the facility (AMP-<shelf>-<slot>-8) for amplifier of the degree under
test (Amp 2 in Figure 4-117) from the Facility drop down list.
43 Record the OPOUT-OTS Untimed parameter (total Optical Power Output at
amplifier of the degree under test, Amp 2 in Figure 4-117).
44 Select the OPTMON Type and the facility for the WSS Common In port (port
9) of the WSS of the degree under test from the Facility drop down list. Record
the OPR-OTS Untimed parameter.
45 Put the amplifier of the degree under test (Amp 2 in Figure 4-117) back in the
auto shutoff mode by setting the Line A AMP facility ALSO Disabled to False.
46 On the Line A AMP (port 8) facility of amplifier of the degree under test (Amp
2 in Figure 4-117), change the AMP Mode back to Gain.
tested (Amp 2 in Figure 4-117).
MLA3 20 dB
SRA/ESAM/SAM 20 dB
connected degree line facing circuit pack (Amp 1 in Figure 4-117) to the
output port of the line facing circuit pack of the degree being tested (Amp 2 in
Figure 4-117). See the procedure on adding a photonic connection in
Configuration - Connections Management, 323-1851-320.
49 Put the Line A AMP facility (port 8) of the amplifier on the degree not being
tested (Amp 1 in Figure 4-117) in no shutoff mode as follows:
information.


Step Action
50 On the Line A AMP (port 8) facility of the amplifier on the degree not being
tested (Amp 1 in Figure 4-117):
51 On the WSS on the degree not being tested (WSS1 in Figure 4-117), open
pixel for the CHC-shelf-slot-index:
index associated with the wavelength in the DeMux direction of the
transmitter chosen in step 38, that is ‘CHC-<shelf>-<slot>-9-<index>.
52 On the WSS on the degree being tested (WSS2 in Figure 4-117), open pixel
for the CHC-shelf-slot-index:
transmitter chosen in step 38, that is ‘CHC-<shelf>-<slot>-10-<index>
54 Select the OPTMON Type and the facility for the WSS Common Out port (port
10) of the WSS on the degree being tested (WSS2 in Figure 4-117) from the
Facility drop down list. Record the OPT-OTS Untimed parameter.
55 Select the facility (AMP-<shelf>-<slot>-6) for amplifier of the degree under
test (Amp 2 in Figure 4-117) from the Facility drop down list.


Step Action
57 Record the OPIN-OTS Untimed parameter (total Optical Power Input at Amp1
in Figure 4-117).
If Then go to
to 17 dB:
— Click Edit.
of this procedure.)
then click OK.


Step Action
to 20 dB:
— Click Edit.
procedure.)
then click OK.
Go to step 62.


Step Action

— Click Edit.
•Click Apply.
•Click OK.
— On the XLA, select port 5 (Line B Out), then select the ADJ-FIBER
facility and check the fiber loss that is reported.


Step Action
— On the line facing circuit pack, select port 7 (Line A Out) then select
the ADJ-FIBER facility and check the fiber loss that is reported.
— Click Edit.
•Click Apply.
•Click OK.
the amplifier output), clean all the optical connections from the Line A
output port to the input of the CCMD12 (add/drop degrees) or other


Step Action

A Out (port 7).

next step.
from step 62.


Step Action
B out (port 5).

next step.
from step 65.


Step Action

If Then
pack is an MLA3 the values you recorded in:
- step 34 (MLA3 Line B) and step 35 (MLA3 Line A)
for degrees with add/drops
- step 59 (MLA3 Line B) and step 60 (MLA3 Line A)
for degrees without add/drops
recorded in:
step 36 for the XLA Line B and Line A, respectively,
for degrees with add/drops.
step 61 for the XLA Line B and Line A, respectively,
for degrees without add/drops.
Set the facilities back to IS.
70 On the WSSOPM, close down the pixel that you opened in step 32 (degrees
with add/drops) or step 51 and step 52 (degrees without add/drops):
a. Select CHC in the Facility drop down list and select the CHC facility with
transmitter chosen in step 30 (degrees with add/drops) or step 38
(degrees without add/drops), that is
CHC-<shelf>-<slot>-<port>-<index>
b. Set the Opaque state to “Yes”.
c. Select the NMCC in the Facility drop-down list:
d. Set the Target Loss to its default value (18 dB).
71 For degrees without add/drops, put the amplifier on the degree not being
tested (Amp 1 in Figure 4-117) back in the auto shutoff mode by setting the
Line A AMP facility ALSO Disabled to False.
72 For degrees without add/drops, change the AMP mode to Gain for the
amplifier on the degree not being tested (Amp 1 in Figure 4-117).
73 Delete the photonic connection you provisioned in step 30 (degrees with
add/drops) or step 38 (degrees with add/drops).
74 Remove the fiber loopback and the padding you added in step 31 (degrees
with add/drops) or step 49 (degrees with add/drops).


Step Action
Repeat for all degrees

purpose of this testing only (that is, for spare transponder used for testing
purposes only).
—end—

Procedure 4-30
Connecting intra-site fibers for 1x20 Colorless
Directionless (CD) ROADM with FIM Type 3 sites
Use this procedure to perform intra-site fiber connections at a 1x20 CD
ROADM with FIM Type 3 site.
The following figures show examples of the CD ROADM with FIM3

configurations:
• “Intra-NE fiber connections at a 1x20 CD ROADM with FIM Type 3 site
(100% add/drop with up to 10 degrees)” on page 4-397
(partial fill with up to 11-14 degrees)” on page 4-398
The figures show configurations using XLA-SAM for line-facing circuit packs.
The following line-facing circuit pack configurations are also supported:
• MLA3
• MLA3-SAM/ESAM
• XLA-ESAM
• XLA-SRA
This procedure does not cover any other ROADM site configurations. You
must connect the intra-site fibers of such ROADM sites based on the specific
network configurations.
The topology is provisioned using the OTS slot and TID slot sequences as
follows:
• OTS slot sequence is used to define the ROADM OTS(s), including OSC,
involving SAM/ESAM/SRA, MLA3/XLA, and WSSOPM.
• TID slot sequence is used to define following adjacencies:
— FIM MPO to WSS1x20 MPO
— FIM MPO to SMD14x8 MPO
— SMD14x8 LC to CCMD12(s)
Refer to Part 2 of Configuration - Provisioning and Operating,
323-1851-310, for procedures on creating/editing OTS and TID slot
sequences.


Connecting intra-site fibers for 1x20 Colorless Directionless (CD) ROADM with FIM Type 3 sites
The following shelf slotting requirements apply:

• For the Degree/OTS equipment:
— All the equipment forming the degree must be equipped in the same
shelf.
• For the Add/drop structure equipment:
— The FIM3 must be equipped in the same shelf as the SMD.
— The CCMD12 and SMD can be in the same shelf or in different
shelves.
• The transponder equipment can be in the same shelf as the degree/OTS
equipment or in the same shelf as the add/drop structure equipment or in
a different shelf.
• All shelves at the node containing the degree/OTS equipment, the
add/drop structure equipment and the transponder equipment must be
TID consolidated.
• The maximum number of supported shelves at a TIDc node:
— 36 if primary shelf is equipped with SP2
— 16 if primary shelf is equipped with SPAP-2

Prerequisites
subtending modules (FIM).


CAUTION
DANGER
Risk of injury
CAUTION
for any reason.

connection.
— connect MPO cables, see the Installation, 323-1851-201.x, technical

publication specific to the respective 6500 shelf type (in the procedure
on routing fiber-optic cables and electrical cables to circuit packs in the
6500 shelf)
These configurations include Fiber Interconnect Modules (FIM).
FIM Type 3 (NTK504CC) is shipped with:

• dust caps pre-installed on Fiber Group 1 ports (4 items)
• MPO loopback connectors pre-installed on Fiber Group 2-20 ports
(76 items)
• dust caps for MPO loopback connectors (not installed, 76 items)
• LC duplex loopback connectors pre-installed on UPG ports 1-20
(20 items)
• dust caps for LC loopback connectors (not installed, 20 items)


In addition to providing the optical loopback operation required by

removed and saved for future use. For more information, see the Photonic
passive modules table in Planning - Ordering Information, 323-1851-151.


Step Action
EDP/IDP.
cables to circuit packs in the Installation, 323-1851-201.x, technical
Connect the intra-site fibers. See examples in the following illustrations:
• 10 degrees x10 add/drops with 100% add/drop - Figure 4-118 on page
4-397
• 14 degree with partial add/drop - Figure 4-119 on page 4-398
Each ROADM OTS contains either:

• WSS 1x20, XLA, and ESAM/SAM/SRA
• WSS 1x20 and MLA3
• WSS 1x20, MLA3, and ESAM/SAM
Port usage:
• WSS port usage, for an n-degree site:
— (n-1) ports used for WSS interconnectivity
— (20-n) ports used for SMD14x8 interconnectivity
• recommended FIM Type 3 port usage
— Degrees (connections to WSS) are populated starting at port group
1 and then incrementing.
— Add/drop banks ((connections to SMD 14x8) are populated starting
at port group 20 and then decrementing.
— LC Upgrade ports reserved for future use.
Note: While this port usage is recommended, other port usage is allowed.
The flexibility of fiber connections is everywhere that includes the locations
between WSS and FIM, FIM and SMD, as well as SMD and CCMD12(s),
under the condition that provisioning is correct.
—end—

Figure 4-118
Intra-NE fiber connections at a 1x20 CD ROADM with FIM Type 3 site (100% add/drop with up to
10 degrees)

Figure 4-119
Intra-NE fiber connections at a 1x20 CD ROADM with FIM Type 3 site (partial fill with up to 11-14
degrees)

Procedure 4-31
Site testing for 1x20 Colorless Directionless (CD)
ROADM with FIM Type 3
Use this procedure to test large Colorless Directionless (CD) ROADM
configurations. See examples in:
(100% add/drop with up to 10 degrees)” on page 4-397
(partial fill with up to 11-14 degrees)” on page 4-398
Colorless Directionless (CD) ROADM with FIM Type 3 configurations include

Fiber Interconnect Modules (FIM).
FIM Type 3 (NTK504CC) is shipped with:

• dust caps pre-installed on Fiber Group 1 ports (4 items)
• MPO loopback connectors pre-installed on Fiber Group 2-20 ports
(76 items)
• dust caps for MPO loopback connectors (not installed, 76 items)
• LC duplex loopback connectors pre-installed on UPG ports 1-20
(20 items)
• dust caps for LC loopback connectors (not installed, 20 items)
In addition to providing the optical loopback operation required by applications

that use the FIM, the loopback modules act as dust caps for the optical ports.
Do not remove the loopback modules except as part of a fiber installation
procedure. The FIM tray assembly includes a bag of dust caps that must be
put on any loopback connector that is being removed and saved for future use.
For more information, see the Photonic passive modules table in Planning -
Ordering Information, 323-1851-151.


Site testing for 1x20 Colorless Directionless (CD) ROADM with FIM Type 3
Prerequisites
• Make sure that you have a copy of the engineering data sheet.
• Have a user account with a UPC level of 3 or higher.
• Have the following equipment:
— 20 dB optical attenuator
— an LC to LC patch cord (for testing steps that use an optical fiber
loopback)
— an optical power meter
system is complete. The testing steps in this procedure cycle through all
ports on add/drop banks. If you have transponders installed as part of your
system, use them for the testing steps.
For add/drop bank ports where transponders are not connected as part of
your system, use a spare transponder for the testing steps. After testing is
complete on a port, move the spare transponder to the next port you will
be testing that does not have a transponder connected.
performing this procedure. Connect all optical fibers within the
configuration.


CAUTION
reason.
connection.
CAUTION
DANGER
Risk of injury
DANGER
— connect MPO cables, see the Installation, 323-1851-201.x, technical

publication specific to the respective 6500 shelf type (in the procedure
on routing fiber-optic cables and electrical cables to circuit packs in the
6500 shelf)


Step Action
Attention: The OSC ports in this procedure could be on the SPAP-2

w/2xOSC circuit pack, on the 2xOSC circuit pack, or the line facing circuit
testing.
Power parameter.
3 In the Performance Monitoring window, PM Counts tab, select the Shelf and
the Slot from the respective lists, then click Start Monitoring. Under the
OPTMON tab, select the OPTMON facility for OSC Out (port 4) on the line
facing circuit pack connected to the OSC-1 you are testing
(OPTMON-<shelf>-<slot>-4). Record the OPR-OTS Untimed parameter.


Step Action
Testing the MPO interconnects using the Connection Validation application

Note: If MPO loopback modules are not fitted to the FIM Type 3 MPO
connectors, High Fiber Loss alarms will be raised due to the Dark Fiber Loss
Management feature for every subfiber within the MPO connector that does
not have the loopback module on it.
8 Log into the network element using Site Manager. Select the appropriate
shelf from the Shelf drop-down list.
10 Make sure that the Dark Fiber Loss Measurement system parameter is
Security, 323-1851-301.)
completed.
Clearing, 323-1851-543.
The site equipment uses MPO cables and connectors. For steps to:
CAUTION
for any reason.

connection.
electrical cables to circuit packs in the 6500 shelf), see the Installation,
323-1851-201.x, technical publication specific to the respective 6500
shelf type


Step Action

• WSSOPM − FIM MPO loopback connector
• WSSOPM − CCMD12
• WSSOPM − SMD Flex 14x8
• SMD14x8 − FIM MPO loopback connector
• SMD14x8 − LC loopback connector
Connecting the transponder and testing with transponder loopback
follows:
testing steps.
15 Make sure the transponder you will be using for the tests is connected to the
CCMD12 In port.
make sure:
323-1851-310.


Step Action
See Table 4-21 for CCMD12 and SMD maximum loss values and Table 4-22
for maximum FIM loss values.
Table 4-21
CCMD12 NTK508FAE5 13.4 13.4
SMD Flex 14x8 NTK553GC 7.1 7.1
Table 4-22
Fiber Interconnect Module (FIM Type 3) maximum loss
Equipment PEC Maximum insertion loss (dB)
FIM Type 3 NTK504CC Add or Drop, MPO-MPO connections: 1.4

Add or Drop, MPO-LC connections: 1.1
21 Repeat step 14 to step 20 for all the other CCMD12 In ports in the add/drop
bank, then on all the other add/drop banks.
The “TX Tuning In Progress” alarm is raised. This is expected. Wait until the
alarm clears.


Step Action
tested.
MLA3 20 dB
SRA/ESAM/SAM 20 dB
25 On the WSS, open pixel for the CHC-shelf-slot-index:

‘CHC-<shelf>-<slot>-<port>-<index>
If Then go to
to 17 dB:
— Click Edit.
of this procedure.)
then click OK. Click Yes in the warning confirmation message.


Step Action

28 Perform this step on the line facing circuit pack (MLA3).
to 20 dB:
— Click Edit.
procedure.)
then click OK. Click Yes in the warning confirmation message.
Go to step 30.


Step Action

— Click Edit.
•Click Apply. Click Yes in the warning confirmation message.
•Click OK.
— On the XLA, select the ADJ-FIBER facility and then select port 5
(Line B Out), check the fiber loss that is reported.


Step Action
— On the line facing circuit pack, select the ADJ-FIBER facility and then
select port 7 (Line A Out), check the fiber loss that is reported.
— Click Edit.
•Click Apply. Click Yes in the warning confirmation message.
•Click OK.
the Line A output port to the input of the CCMD12 (add/drop degrees)
or other line facing circuit pack (degrees with no add/drops).
Go to step 30.


Step Action

A Out (port 7).

next step.
from step 30.


Step Action
B out (port 5).

next step.
from step 33.


Step Action

If Then
respectively
Set the facilities back to IS.
38 On the WSSOPM, close down the pixel that you opened in step 25:
a. Select CHC in the Facility drop down list and select the CHC facility with
CHC-<shelf>-<slot>-<port>-<index>
b. Set the Opaque state to Yes”. Click Yes in the warning confirmation
message.
c. Select the NMCC in the Facility drop-down list:
d. Set the Target Loss to its default value (18 dB). Click Apply. Click Yes in
the warning confirmation message.
40 Remove the fiber loopback and the padding you added in step 24.
Repeat for all degrees
purpose of this testing only (that is, for spare transponder used for testing
purposes only).
—end—

5-1
Fixed-plan terminal node procedures 5-
This section describes the configuration and connections for the fixed-plan
terminal node configurations.
Note: For more information on using the fixed-plan terminals with

Waveserver transponders, refer to Waveserver and 6500 Interworking.
323-4001-165, and Waveserver Ai and 6500 Interworking, 323-4002-165.
Coherent Select thin terminal connections

If the thin terminal is configured as Coherent Select, connections are
provisioned similar to Layer 0 Control Plane using sub-network connections
(SNC): the user specifies the originating point and the destination point at the
originating node, without the need for further provisioning at intermediate
nodes or the destination node. Using Site Manager, connections are created
and managed through the Sub-Network Connection application.
To manage Coherent Select connections through the Sub-Network

Connection application, an OSRP instance must be created with the Control
Plane type set to “L0 Provisioning” mode. In this mode, the user specifies the
local endpoint and the remote endpoint on the originating node and the cross-
connections are created in all required nodes.
For information regarding making connections in Coherent Select thin

terminal configurations, refer to WaveLogic Photonics Coherent Select, 323-
1851-980.

5-2 Fixed-plan terminal node procedures
List of procedures
The following table provides references to the procedures covered in this
chapter.
Table 5-1
Fixed-plan terminals connection and testing procedures
Procedure
Procedure 5-1, “Connecting intra-site fibers for the fixed-plan terminal nodes and performing site
testing”
Procedure 5-2, “Adding transponder information for SPLI and adding adjacencies”
Procedure 5-3, “Connecting the inter-site fibers for fixed-plan terminal nodes, performing additional
provisioning, and testing the photonic link”
Procedure 5-4, “Creating 6500 and transponder fiber connections for a Fixed-96, Fixed-88, Fixed-
44, Fixed-64, or Flex-12 configuration”
Procedure 5-5, “Verifying 6500 threshold and power level settings for protected configurations”
Procedure 5-6, “Setting Line B target gain for Extended Reach and line-amp configurations”
Procedure 5-7, “Resetting the TCA baselines”
Procedure 5-8, “Calibrating the SRA circuit packs”
Procedure 5-9, “Verifying traffic continuity for unprotected Fixed-96, Fixed-88, Fixed-44, Fixed-64,
and Flex-12 configurations”
Procedure 5-10, “Verifying traffic continuity for Fixed-96, Fixed-88, Fixed-44, and Fixed-64 OPS
protected configurations”

Procedure 5-1
Connecting intra-site fibers for the fixed-plan terminal
nodes and performing site testing
Use this procedure to perform intra-site fiber connections for fixed-plan
terminal nodes (also known a Channel access nodes) and to perform intra-site
testing for the 6500.

Prerequisites
• Ensure that you have the engineering data sheet for your node.
subtending modules (CMD, BMD2).
condition, and the loss between fibers is not greater than 0.5 dB. It is very
important that fibers are cleaned and scoped prior to being connected.
Refer to the cleaning instructions in Installation - General Information,
323-1851-201.0.
CAUTION
CAUTION
Risk of injury


Connecting intra-site fibers for the fixed-plan terminal nodes and performing site testing
Step Action
1 Review the following figures and the engineering data sheet to identify the
example for your node configuration type:
• Two wavelength (BMD2) - Figure 5-1 on page 5-5
• Fixed-96 50 GHz unprotected - Figure 5-2 on page 5-5
• Fixed-96 50 GHz unprotected with ESAM - Figure 5-3 on page 5-6
• Fixed-96 50 GHz unprotected with XLA/ESAM - Figure 5-4 on page 5-7
• Fixed-96 50 GHz unprotected with XLA/SRA - Figure 5-5 on page 5-8
• Flex-12 50 GHz unprotected - Figure 5-10 on page 5-13
• Flex-12 50 GHz unprotected with ESAM - Figure 5-11 on page 5-14
• Fixed-64 75 GHz unprotected with XLA/ESAM - Figure 5-15 on page
5-18
• Fixed-96 50 GHz protected - Figure 5-16 on page 5-19
• Line amp node - standard reach - Figure 5-20 on page 5-23
• Line amp node - extended reach - Figure 5-21 on page 5-24
2 Connect the 6500 equipment as illustrated in the respective example.
3 Verify that there are no unexpected alarms. To clear alarms, see Fault
You have completed the connecting of the intra-site fibers for the 6500 at this
site.
Next perform Procedure 5-2, “Adding transponder information for SPLI and
adding adjacencies”.
—end—

Figure 5-1
Example of 2-channel with BMD2 node
Figure 5-2
Example of CMD96 50GHz unprotected Channel access node (also known as Fixed-96 [50GHz]
configuration—unprotected)

Figure 5-3
Example of CMD96 50GHz unprotected (with ESAM) Channel access node (also known as
Fixed-96 [50GHz] configuration—unprotected)

Figure 5-4
Example of CMD96 50GHz unprotected (with XLA and ESAM) Channel access node (also known
as Fixed-96 [50GHz] configuration—unprotected)

Figure 5-5
Example of CMD96 50GHz unprotected (with XLA and SRA) Channel access node (also known as

Figure 5-6
Example of 2xeCMD44 50GHz unprotected Channel access node (also known as Fixed-88 [50GHz]

Figure 5-7
Example of eCMD44 100GHz unprotected Channel access node (also known as Fixed-44 [100GHz]

Figure 5-8

Figure 5-9
Example of CMD44 100GHz unprotected (with XLA and SRA) Channel access node (also known
as Fixed-44 [100GHz] configuration—unprotected

Figure 5-10
Example of CCMD12 50GHz unprotected Channel access node (also known as Flex-12 [50GHz]

Figure 5-11
Example of CCMD12 50GHz unprotected (with ESAM) Channel access node (also known as
Flex-12 [50GHz] configuration—unprotected)

Figure 5-12
Example of CMD64 75GHz unprotected Channel access node (also known as Fixed-64 [75GHz]

Figure 5-13

Figure 5-14
Example of CMD64 75GHz unprotected (with XLA and SRA) Channel access node (also known as

Figure 5-15
Example of CMD64 75GHz unprotected (with XLA and ESAM) Channel access node (also known
as Fixed-64 [75GHz] configuration—unprotected)

Figure 5-16
Example of CMD96 50GHz protected Channel access node (also known as Fixed-96 [50GHz]
configuration—protected)

Figure 5-17
Example of 2xeCMD44 50GHz protected Channel access node (also known as Fixed-88 [50GHz]

Figure 5-18
Example of eCMD44 100GHz protected Channel access node (also known as Fixed-44 [100GHz]

Figure 5-19
Example of CMD64 75GHz protected Channel access node (also known as Fixed-64 [75GHz]

Figure 5-20
Example of Line Amp node—Standard reach
OSC SFP 0-34dB Low Tx Out

PEC: NTK592NG In
Loc: Shelf:1 Slot:15-1
6500 MLA3
PEC: NTK552GA LC
Line B Mon
1
2
Line A Mon
LC
OSC B In
3
4
OSC A Out
8 A 7
LC LC
5 B 6
Line B Out Line B In
Loc: Shelf: 1 Slot: 1
6500 LIM
PEC: NTK552DA LC
Line B Mon
1
2
Line A Mon
LC
OSC B In
3
4
OSC A Out
8 7
LC LC
5 6

PEC: NTK592NG In

Figure 5-21
Example of Line Amp node—Extended reach

PEC: NTK592NG In
6500 MLA3
PEC: NTK552GA LC
Line B Mon
1
2
Line A Mon
LC
OSC B In
3
4
OSC A Out
8 A 7 1 10 dB 2
LC LC
5 B 6
6500 MLA3
PEC: NTK552GA LC
Line B Mon
1
2
Line A Mon
LC
OSC B In
3
4
OSC A Out
8 A 7 1 10 dB 2
LC LC
5 B 6

PEC: NTK592NG In

Procedure 5-2
Adding transponder information for SPLI and adding
adjacencies
Use this procedure to:
• add a transponder node name to the 6500 SPLI list if they support SPLI
• provision the transponder line port as Far End Address in 6500's ADJ
facility
Prerequisites
• Have the IPv4 address(es) of the transponder node(s).
• If you are using Site Manager, have Site Manager software installed on
your craft computer for this 6500 software load release.
• For more information on SPLI information sharing, see Administration and
Security, 323-1851-301.
• This procedure refers to CLI commands. For more information on CLI
Note: The transponder node name will be added on the 6500 NE to which
the transponder line port is connected. That is, in a TIDc configuration, if
the transponder node is connected to the CMD on the member shelf, the
transponder node name will be added to the member shelf instead of the
primary shelf.
Step Action
1 Log in using Site Manager or use the CLI, as applicable.

2 Add the IPv4 address(es) of the transponder node name(s) to the SPLI list of
the 6500 node as follows:
• If you are using Site Manager, refer to the procedure on adding SPLI
entries in Administration and Security, 323-1851-301.
• If you are using the CLI, enter:
adjacencies spli create SHELF-<shelf number> fend-ip-
addr <FEIPADD> spli-id <TID>
where
— FEIPADD is the IPv4 address of the transponder node being added
to the 6500 SPLI list. Surround the IP address with double-quotes.


Adding transponder information for SPLI and adding adjacencies
Step Action
— TID is a string defined by the user to represent the transponder node.

Surround the string with double-quotes. It is recommended that the
transponder's member-name string be used as TID.
Note: DHCP is not recommended to be used on transponder when SPLI is
used as the transponder could get assigned a different IPv4 address through
DHCP. When that occurs, the user would have to return to this step to
manually update the IPv4 address provisioned in the 6500 SPLI table.
3 Provision the transponder line port as Far End Address in 6500's ADJ facility
as follows.
• If you are using Site Manager, refer to Chapter 3, “Photonic layer
provisioning procedures”, and Configuration - Provisioning and Operating
Part 1, 323-1851-310 for more information.
adjacencies adjacency set <AID> prov-addr-form <prov-
addr-form> prov-fe-addr <prov-fe-addr>
where
— <AID> is the CMD adjacency in the form ADJ-SH-SL-PORT for the
CMD port connected to the transponder.
— <prov-addr-form> defines the format of the far end address. For
example, ‘NODENAME-SL-PRT’ for transponder node name-Slot-
Port.
— <prov-fe-addr> is a string defined by the user to represent the far end
address of the transponder in the form TID-Slot-Port.
If following recommendations, the TID is the transponder's member-
name string. Surround the string with double-quotes.
4 If you have more sites to commission, proceed to the next 6500 site.
If you have finished performing all the tasks up to this procedure on all the
6500 sites, go to Procedure 5-3, “Connecting the inter-site fibers for fixed-
plan terminal nodes, performing additional provisioning, and testing the
photonic link”.
—end—

Procedure 5-3
Connecting the inter-site fibers for fixed-plan terminal
nodes, performing additional provisioning, and
testing the photonic link
Use this procedure to connect the inter-site fibers for the fixed-plan terminal
configurations and test the photonic link.
Note: The CLI commands in this procedure assume that the “install
create” commands have been used (only supported on 2-slot or 7-slot
compact shelves with SPAP2) which provision circuit packs in particular
shelf slots. If the CLI “install create” commands have not been used, shelf/
slot numbers in the commands should be adjusted as necessary.
Prerequisites
Step Action
1 Connect the inter-site fibers between the local 6500 site and the remote 6500
site.
2 Wait for five minutes and make sure there are no alarms indicating that the
line ports were not connected correctly. DOC invalid photonic domain alarms
should clear.
Provisioning the target span loss for Terminal nodes
3 For Terminal nodes, after you connect the remote node, you can set the target
span loss of SLA/MLA2/MLA3 Line B (ADJ-LINE port 5) to the expected span
loss value as follows:
adjacencies line set adj-1-<1|2>-5 targ-span-loss
<targ-span-loss Value>
For protected configurations, set the target span loss value for both line
interface modules (that is, both SLA/MLA2/MLA3 modules in the shelf).
For spans using MLA2/MLA3, if the actual span loss is 16 dB, set the Target
Span Loss to 16.1 dB (because it must exceed Minimum Span Loss = 16 dB).


Connecting the inter-site fibers for fixed-plan terminal nodes, performing additional provisioning,
and testing the photonic link
Step Action
View the reported span loss as follows:

and verify the value of the osc-span-loss parameter.
Although the value is reported against port 5, the reported span loss is in the
direction from the remote node to this node.
Provisioning the target span loss for Line Amp nodes
4 For Line Amp nodes (equipped with MLAx-MLAx or MLAx-LIM), after you
connect the remote nodes, you can set the target span loss of MLAx Line B
(ADJ-LINE port 5) to the expected span loss value as follows:
adjacencies line set adj-1-<1|2>-5 targ-span-loss
<targ-span-loss Value>
If the actual span loss is 16 dB, set the Target Span Loss to 16.1 dB (because
it must exceed Minimum Span Loss = 16 dB).
View the reported span loss as follows:

and verify the value of the osc-span-loss parameter.
Although the value is reported against port 5, the reported span loss is in the
direction from the remote node to this node.


Connecting the inter-site fibers for fixed-plan terminal nodes, performing additional provisioning,
and testing the photonic link
Step Action
Provisioning the fiber type for Line Amp nodes

5 For Line Amp nodes, edit the fiber-type parameter of both line facing circuit
packs to match the actual fiber type deployed, as follows:
adjacencies line set adj-1-<1|2>-5 fiber-type
<fiber-type Value>
Testing the 6500 photonic link
6 Verify discovered far end addresses and span loss OSC as follows:
• If you are using the CLI, for fixed44, fixed88, fixed96, and fixed64
configurations, enter:
adjacencies adjacency show adj-1-1-5
adjacencies line show adj-1-1-5
In addition, for protected configurations, enter:
adjacencies adjacency show adj-1-2-5
adjacencies line show adj-1-2-5
Note: Additional testing (pm amp counts) will be performed after the
transponder wavelengths are connected to the 6500 Photonic system (later
in this chapter). The procedures will direct you to the required steps.
7 Verify that there are no unexpected alarms. To clear alarms, see Fault
Management - Alarm Clearing, 323-1851-543. Note that Shutoff Threshold
Crossed alarms raised against all the amplifiers are expected (because the
transponder equipment is not connected yet).
Then go to Procedure 5-4, “Creating 6500 and transponder fiber connections
for a Fixed-96, Fixed-88, Fixed-44, Fixed-64, or Flex-12 configuration”.
—end—

Procedure 5-4
Creating 6500 and transponder fiber connections for a
Fixed-96, Fixed-88, Fixed-44, Fixed-64, or Flex-12
configuration
Use this procedure to connect fibers between the 6500 and transponder for a
fixed channel configuration.
Prerequisites
To perform this procedure, you must:
• have installed all 6500 and transponder nodes in the solution
• have completed Procedure 5-3 and verified that all 6500 and transponder
nodes are configured correctly
Step Action
6500 CMD ports

1 If you are Then go to
connecting transponder to a 6500 Fixed-96/88/44/64 step 2
configuration
connecting transponder to a 6500 Flex-12 configuration step 3
2 Use the front-plate of the CMD you are connecting to in order to verify the
ports specified by transponder. The front-plate has a schematic, listing the
wavelengths, and which set of Tx/Rx ports match up with that particular
wavelength. See Figure 5-22 on page 5-30.
Figure 5-22
Wavelengths and Tx/Rx ports on front plate of CMD
Go to step 4


Creating 6500 and transponder fiber connections for a Fixed-96, Fixed-88, Fixed-44, Fixed-64, or
Flex-12 configuration
Step Action
3 Use Table 5-2 to match the physical connections between the transponder
line-port with the 6500 CCMD12 port.
Table 5-2
Flex-12 wavelengths and CCMD12 line-port assignments
Wavelength (nm) 6500 CMD port (In) 6500 CMD port (Out)
1560.61 1 2
1561.01 3 4
1561.41 5 6
1561.83 7 8
1562.23 9 10
1562.64 11 12
1563.05 13 14
1563.45 15 16
1563.86 17 18
1564.27 19 20
1564.68 21 22
1565.09 23 24
Note: For CCMD12 thin terminal configuration, frequency assignments are manual and no additional
validation is done. Other frequencies/wavelengths can be assigned but users should not reuse already
used wavelengths on the ports while using the SPLI application for frequency assignments.


Creating 6500 and transponder fiber connections for a Fixed-96, Fixed-88, Fixed-44, Fixed-64, or
Flex-12 configuration
Step Action
Connecting fibers
DANGER
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.
4 The fiber connections between the 6500 CMD and the transponder line-ports
require single-mode fiber with LC-LC connectors. After the port connections
have been identified, refer to the Inspecting and cleaning optical interface
connectors procedure, found in the Installation-General Information, 323-
1851-201.0 before cleaning the connectors.
5 Using a power meter, verify the Tx power being transmitted from transponder
Tx port is as specified in the engineering documentation.
6 Connect the Tx from the transponder to the odd-numbered port of the
identified pair on the CMD and connect the Rx from the transponder to the
even-numbered port on the CMD.
7 Repeat step 1 to step 6 on the far-end 6500 and transponder.
8 If you have Then go to
a protected configuration Procedure 5-5, “Verifying 6500
threshold and power level settings
for protected configurations”
an Extended Reach or line-amp Procedure 5-6, “Setting Line B
configuration target gain for Extended Reach
and line-amp configurations”
an unprotected Standard Reach Procedure 5-7, “Resetting the
configuration TCA baselines”
—end—

Procedure 5-5
Verifying 6500 threshold and power level settings for
protected configurations
Use this procedure to complete the configuration for 6500 terminal nodes that
are in protected configurations.
Note 1: To set the OPTMON LOS thresholds in ROADM networks where
the OPS is located between the transponder TxRx and the CMD44, and
where the channel count is higher than the minimum channel count
required, the OPS LOS threshold for SW1/SW2 IN OPTMON facility is
provisioned 6 dB below the SW1/SW2 IN OPTMON facility OPR-OTS PM
value.
Note 2: The CLI commands in this procedure assume that the “install
Prerequisites
To complete this procedure, make sure you have:
• performed the commissioning procedures for terminal nodes as described
in the Commissioning chapter of this technical publication
• connected the transponder wavelengths to the 6500 photonic system and
have the minimum number of channels as required in Table 5-3 on page
5-35. If this procedure is attempted with fewer than the number of required
channels, there will not be enough optical power in the photonic system to
clear the OPS LOS alarm.
• logged into the 6500 CLI or Site Manager



Verifying 6500 threshold and power level settings for protected configurations
Step Action
Configuring OPS power levels and LOS Thresholds

1 For protected configurations, the Input power level to OPS SW1 In and SW2
In ports must be within 2 dB of each other. To view the OPS SW1 In and OPS
SW2 port power levels:
• If you are using Site Manager, refer to Fault management - Performance
Monitoring, 323-1851-520 for more information.
pm optmon counts show optmon-1-3-13 montype opr-ots
and
pm optmon counts show optmon-1-3-15 montype opr-ots
If the power differs by more than 2 dB, insert a pad on the SW with higher
input power, so that its input power is within ± 2 dB of the other SW.
Note: This operational consideration exists to ensure that the modem
receiver does not see a dramatic change in power level when the OPS
switches. The modem receiver may take longer time to re-acquire a
signal if the new signal has a different power level leading to higher than
expected protection switch times.
2 For all protected configurations, the OPS LOS Thresholds that were set by
the “install create” command for the OPS SW1 In and OPS SW2 In ports must
be manually configured. The new OPS LOS Threshold will depend on the
type of amplifier used, the span count of the photonic system, and the power
loss for each span. Refer to the following table to calculate the value that
applies to your configuration.
Note: If your network has one or more spans with losses greater than listed
in the table, it is considered to be an Extended Reach configuration. For
Extended Reach configurations, the OPS LOS thresholds must be calculated
by Ciena. Contact your Ciena support team.


Step Action
Table 5-3
LOS Thresholds for OPS SW1 In and OPS SW2 In ports for protected
configurations
Amp Span Maximum span Minimum OPS LOS

type count loss (per span) transponder channels Threshold (dBm)
required
SLA 1 < 10.2 dB for Fixed-96: 8 -1.0 – Pad value at
for Fixed-88: 6 SW input
for Fixed-44: 8
for Fixed-64: N/A
MLA3 1 < 24.7 dB for Fixed-96: 3 0 – Pad value at
for Fixed-44: 3
for Fixed-64: 3
MLA3 2 < 22 dB for Fixed-96: 4 +4.0 – Pad value at
for Fixed-44: 5
for Fixed-64: 4
MLA2/ 3 < 22.0 dB for Fixed-96: 5 +3.0 – Pad value at
MLA3 for Fixed-88: 9 SW input
for Fixed-44: 6
for Fixed-64: 5
3 Set the LOS Threshold from step 2:

• If you are using Site Manager, refer to Configuration - Provisioning and
Operating, 323-1851-310 for more information.
— Set the LOS Threshold for the OPS SW1 In port:
optmons optmon set optmon-1-3-13 los-thres <los-thres
Value>
— Set the LOS Threshold for the OPS SW2 In port:
optmons optmon set optmon-1-3-15 los-thres <value>


Step Action
4 As an example, for a protected photonic system using SLAs, with 1 span

count, 8 channels on a Fixed-96 configuration, and a 3dB pad at OPS SW1,
the calculation would be: -1-3 = -4.
To set the OPS LOS SW1 Threshold for this example using CLI, enter
optmons optmon set optmon-1-3-15 los-thres 4
If you have Then go to
an Extended Reach Procedure 5-6, “Setting Line B target
configuration or 6500 line-amp gain for Extended Reach and line-amp
configurations”
a Standard Reach configuration Procedure 5-7, “Resetting the TCA
baselines”
—end—

Procedure 5-6
Setting Line B target gain for Extended Reach and
line-amp configurations
Use this procedure to set the Line B target gain for Extended Reach 6500
terminal nodes and 6500 line-amp nodes. For more information on Standard
and Extended Reach configurations, see “Standard reach and Extended
reach configurations” on page 2-11.
Prerequisites
To complete this procedure, make sure you have:
• the engineering data plan for the 6500 Extended Reach and line-amp
shelves
• connected the transponder wavelengths to the 6500 photonic system

Step Action
Setting Line B target gain for Extended Reach terminal configurations (protected or unprotected)
1 For Extended Reach configurations (protected or unprotected), you must set
the Line B (port 6) Target Gain on the 6500 terminal nodes. Adjust the value
so that Line B output power matches Table 5-4 on page 5-39 for all amplifier
cards in the shelf (the Target Gain value will be ~23 dB).
To set the Line B Target Gain:
amps amp set amp-1-<1|2>-6 targ-gain <targ-gain Value>


Setting Line B target gain for Extended Reach and line-amp configurations
Step Action
To view the Line B output power:

pm amp counts show amp-1-<1|2>-6 montype opout-ots
2 Repeat step 1 for the far-end 6500 node.
Setting Line B target gain for line-amps
3 For configurations with line-amps, you must set the Line B (port 6) Target
Gain for each amplifier card. Adjust the value so that Line B output power
matches Table 5-4 on page 5-39 for all amplifier cards in the shelf (the Target
Gain value will be ~23 dB).
To set the Line B Target Gain:
amps amp set amp-1-<1|2>-6 targ-gain <targ-gain Value>
To view the Line B output power:
pm amp counts show amp-1-<1|2>-6 montype opout-ots
4 Repeat step 3 for each line-amp shelf in the photonic system.
5 Once this procedure is completed, go to Procedure 5-7, “Resetting the TCA
baselines”.
—end—

Table 5-4
Target Power at Line B (dBm)
Band plan and amplifier type

fixed96 fixed88 fixed44 fixed 64 fixed96 fixed88 fixed 64
Channel MLA3 MLA3 MLA3 MLA3/ MLA3 Channel MLA3 MLA3 MLA3
count MLA2 count
1, 2, or 1, 2, or 1 2 3 1, 2, or 3 1, 2, or 1, 2, or 1, 2, or 3
3 spans 3 spans span spans spans spans 3 spans 3 spans spans
1 3.2 3.6 6.6 4.4 3.4 4.9 49 20.1 20.5 21.8
2 6.2 6.6 9.6 7.4 6.4 7.9 50 20.2 20.5 21.9
3 7.9 8.3 11.3 9.1 8.1 9.7 51 20.3 20.6 22.0
4 9.2 9.6 12.6 10.4 9.4 10.9 52 20.3 20.7 22.0
5 10.2 10.5 13.6 11.4 10.4 11.9 53 20.4 20.8 22.1
6 11.0 11.3 14.3 12.1 11.1 12.7 54 20.5 20.9 22.2
7 11.6 12.0 15.0 12.8 11.8 13.4 55 20.6 21.0 22.3
8 12.2 12.6 15.6 13.4 12.4 13.9 56 20.7 21.0 22.4
9 12.7 13.1 16.1 13.9 12.9 14.4 57 20.7 21.1 22.5
10 13.2 13.6 16.6 14.4 13.4 14.9 58 20.8 21.2 22.5
11 13.6 14.0 17.0 14.8 13.8 15.3 59 20.9 21.3 22.6
12 14.0 14.3 17.4 15.2 14.2 15.7 60 21.0 21.3 22.7
13 14.3 14.7 17.7 15.5 14.5 16.0 61 21.0 21.4 22.7
14 14.6 15.0 18.0 15.8 14.8 16.4 62 21.1 21.5 22.8
15 14.9 15.3 18.3 16.1 15.1 16.7 63 21.2 21.5 22.9
16 15.2 15.6 18.6 16.4 15.4 16.9 64 21.2 21.6 23.0
17 15.5 15.9 18.9 16.7 15.7 17.2 65 21.3 21.7 -
18 15.7 16.1 19.1 16.9 15.9 17.5 66 21.4 21.8 -
19 16.0 16.3 19.4 17.2 16.2 17.7 67 21.4 21.8 -
20 16.2 16.6 19.6 17.4 16.4 17.9 68 21.5 21.9 -
21 16.4 16.8 19.8 17.6 16.6 18.0 69 21.6 21.9 -
22 16.6 17.0 20.0 17.8 16.8 18.2 70 21.6 22.0 -
23 16.8 17.2 20.2 18.0 17.0 18.4 71 21.7 22.1 -
24 17.0 17.4 20.4 18.2 17.2 18.6 72 21.8 22.1 -

Table 5-4
Target Power at Line B (dBm) (continued)
Band plan and amplifier type

fixed96 fixed88 fixed44 fixed 64 fixed96 fixed88 fixed 64
Channel MLA3 MLA3 MLA3 MLA3/ MLA3 Channel MLA3 MLA3 MLA3
count MLA2 count
1, 2, or 1, 2, or 1 2 3 1, 2, or 3 1, 2, or 1, 2, or 1, 2, or 3
3 spans 3 spans span spans spans spans 3 spans 3 spans spans
25 17.2 17.5 20.5 18.3 17.3 18.8 73 21.8 22.2 -
26 17.3 17.7 20.7 18.5 17.5 19.0 74 21.9 22.2 -
27 17.5 17.9 20.9 18.7 17.7 19.2 75 21.9 22.3 -
28 17.6 18.0 21.0 18.8 17.8 19.3 76 22.0 22.4 -
29 17.8 18.2 21.2 19.0 18.0 19.5 77 22.0 22.4 -
30 17.9 18.3 21.3 19.1 18.1 19.6 78 22.1 22.5 -
31 18.1 18.5 21.5 19.3 18.3 19.8 79 22.2 22.5 -
32 18.2 18.6 21.6 19.4 18.4 19.9 80 22.2 22.6 -
33 18.4 18.7 21.8 19.6 18.6 20.0 81 22.3 22.6 -
34 18.5 18.9 21.9 19.7 18.7 20.2 82 22.3 22.7 -
35 18.6 19.0 22.0 19.8 18.8 20.3 83 22.4 22.7 -
36 18.7 19.1 22.1 19.9 18.9 20.4 84 22.4 22.8 -
37 18.9 19.2 22.2 20.0 19.0 20.6 85 22.5 22.8 -
38 19.0 19.4 22.4 20.2 19.2 20.7 86 22.5 22.9 -
39 19.1 19.5 22.5 20.3 19.3 20.8 87 22.6 23.0 -
40 19.2 19.6 22.6 20.4 19.4 20.9 88 22.6 23.0 -
41 19.3 19.7 22.7 20.5 19.5 21.0 89 22.7 - -
42 19.4 19.8 22.8 20.6 19.6 21.1 90 22.7 - -
43 19.5 19.9 22.9 20.7 19.7 21.2 91 22.8 - -
44 19.6 20.0 23.0 20.8 19.8 21.3 92 22.8 - -
45 19.7 20.1 - - - 21.4 93 22.9 - -
46 19.8 20.2 - - - 21.5 94 22.9 - -
47 19.9 20.3 - - - 21.6 95 23.0 - -
48 20.0 20.4 - - - 21.7 96 23.0 - -

Procedure 5-7
Resetting the TCA baselines
Use this procedure to set the Threshold Crossing Alert (TCA) baseline power
levels on the 6500 amplifier and OPS cards. Completing this procedure allows
the optical power baseline to be set correctly. In the event of a change in the
power profile, Gauge TCA alarms will be raised which allows for better fault
isolation.
This procedure must be completed on all 6500 nodes in the photonic system,
once all of the transponders have been connected to the 6500 terminal nodes.
Note 1: If any additional transponder channels are added to the photonic

system, this procedure should be repeated.
Note 2: The CLI commands in this procedure assume that the “install
Prerequisites
• have connected all transponder channels to the 6500 CMDs
• be logged into the 6500 CLI

Step Action

1 To view the current TCA baseline settings for each 6500 circuit pack:
Monitoring, 323-1851-520 for more information
pm amp counts show shelf-1-all tmper basln
and
pm optmon counts show shelf-1-all tmper basln
The mon value indicates the current TCA baseline for a specific port.


Step Action
2 To reset the min/max values and the TCA baselines on the near-end 6500
shelf:
• If you are using the CLI, enter the following four commands:
pm optmon reset shelf-1-all
pm optmon reset optmon-1-all tmper basln
pm amp reset shelf-1-all
pm amp reset amp-1-all tmper basln
3 Repeat step 1 to step 2 for:
• the far-end 6500 terminal shelf
• any line-amp 6500 shelves located between the terminal shelves
• if you have a protected configuration, any line-amp 6500 shelves on both
the working and protected path.
4 Once the TCA baselines have been reset, you can verify the new baseline
settings:
pm optmon counts show shelf-1-all tmper basln
and
pm amp counts show shelf-1-all tmper basln
5 If you have Then
an unprotected Fixed-96, Procedure 5-9, “Verifying traffic continuity
Fixed-88, Fixed-44, Fixed-64, for unprotected Fixed-96, Fixed-88, Fixed-
or a Flex-12 configuration 44, Fixed-64, and Flex-12 configurations”
a protected Fixed-96, Fixed- Procedure 5-10, “Verifying traffic continuity
88, Fixed-44, or Fixed-64 for Fixed-96, Fixed-88, Fixed-44, and
configuration Fixed-64 OPS protected configurations”
—end—

Procedure 5-8
Calibrating the SRA circuit packs
If a SRA is used in the thin terminal configuration, the SRA circuit pack at each
end must be manually calibrated before adding channels using this procedure.
CAUTION
Possible damage to equipment
During this procedure, there must not be any input power to the
XLA circuit pack otherwise the equipment may be damaged.
“SRA calibration - Gain range per fiber type” shows the gain range per fiber
type for the SRA calibration.
Table 5-5
SRA calibration - Gain range per fiber type
Fiber Type Min Gain Max Gain Min Span Max Gain Min Span Max Span
(dB) (dB) Low Gain Low Gain High Gain (dB)
(dB) (dB) (dB)
NDSF 6 15 14 23 21
eLEAF (LEAF) 8 20 16 28 23
TWRS 10 24 18 32 25
TWC 10 23 18 31 25
TWP 10 23 18 31 25 43
LS 10 24 18 32 25
DSF 10 24 18 32 25
TWreach 10 24 18 32 25
Teralight 8 20 16 28 23
NDSF Low Water Peak 7 19 15 27 22
Unknown 6 15 14 23 21
Note: When commissioning the SRA, the “FORCEDSHUTOFF”

parameter value must be set to “FALSE” in order to bring up the RAMAN
pump lasers to ON.


Prerequisites
• have the engineering documentation package (EDP) or installation
documentation package (IDP) or equivalent site/network engineering
plans
• be logged into the 6500
• have set the SRA “FORCEDSHUTOFF” parameter value to “FALSE” in
order to bring up the RAMAN pump lasers to ON.
Step Action
1 Verify there is no input power to the XLA circuit pack.

CAUTION
Possible damage to equipment
Not performing this action could result in damaging the
equipment.
2 Set the XLA post-amplifier (facility port 6) AMP Mode to the Power:
a. Set the AMP facility to out-of-service (OOS).
b. Set the ALSO Disabled parameter to True.
c. Set the AMP Mode to Power.
d. Record the current power and set the Target Power to 20 dBm.
e. Record the current switch mode and set the Gain Mode to High.
f. Set the AMP facility to in-service (IS).
Note: The “Automatic Shutoff Disabled” alarm will be raised. The alarm will
clear after step 7 is completed.
3 At downstream site, set XLA pre-amplifier (facility port 8) to OOS.
4 Before sending the calibration command, check the following conditions are
met:
• No Optical Line Fail alarm
• No OTDR alarm
• No transmitter sending power into the CMD (that is, there must no input
power to the XLA circuit pack)


Step Action
5 Send the calibration request to SRA:

• If you are using TL1 command, enter the following command:
OPR-RAMAN-CALIBRATION:[tid]:RAMAN-shelf-slot-8:CTAG
Note: There is no Site Manager support for this command.
ramans calibration operate RAMAN-shelf-slot-8
If calibration is successful, the “Calibration Required” alarm is cleared and the
SRA RAMAN facility “Calibrated Flag” is set.
If calibration fails, the “Calibration Required” alarm does not clear, the SRA
RAMAN facility “Calibrated Flag” is not set.
If calibration fails on multiple attempts, contact your next level of support.
6 After the calibration request completes, record the recommended gain on the
SRA RAMAN facility:
a. Set the Raman gain mode to “Provisioned”.
b. Set the provisioned Gain to the recommended gain + 1 dB.
c. Re-run the calibration process at step 5.
d. Once set, the gain should not be reverted back to recommended.
Note: If calibration fails after performing step 6 for multiple times, contact
your next level of support.
7 Set the XLA post-amplifier (facility port 6) AMP Mode to Gain:
a. Set the AMP facility to out-of-service (OOS).
b. Set the ALSO Disabled parameter to False.
c. Set the AMP Mode to Gain.
d. Set the Target Power to the value recorded in step 2 substep d.
e. Record the Gain Mode to the value recorded in step 2 substep e.
f. Set the AMP facility to in-service (IS).
8 At downstream site, set XLA pre-amplifier (facility port 8) to IS.
—end—

Procedure 5-9
Verifying traffic continuity for unprotected Fixed-96,
Fixed-88, Fixed-44, Fixed-64, and Flex-12
configurations
Use this procedure to verify that the 6500 and transponder nodes are carrying
traffic correctly once the shelves have been fibered together.
Prerequisites
To complete this procedure, you must:
• be logged into all applicable 6500 CLI sessions
• have connected all fibers between transponder and the 6500 CMD
• have verified the configuration of the 6500 and transponder nodes
Step Action
LED status
1 If you are Then go to
verifying traffic on a Fixed 96, Fixed-88, Fixed-44, or Fixed- step 2
64 configuration
verifying traffic on a Flex-12 configuration step 3
2 On the 6500 amplifiers, verify that the following LEDs are dark:
• OSC 3/4
• Ln B 5/6
• Ln A 7/8
Continue to step 4.
3 On the 6500 CCMD12 cards, verify that the Common In Port 25 LEDs are
dark.
4 On the 6500 SPAP-2s, verify that the OSC1 LEDs are dark.
Note: If an LED is yellow, it indicates that an alarm is raised against that port.


Verifying traffic continuity for unprotected Fixed-96, Fixed-88, Fixed-44, Fixed-64, and Flex-12
configurations
Step Action
Verifying power levels and alarms

5 Verify that the Rx power on the transponder line ports are within the specified
range.
6 To verify the presence of any threshold crossing, power level, or other
unexpected alarms on the 6500 nodes:
• If you are using Site Manager, refer to Fault Management - Alarm
Clearing, 323-1851-543 for more information
• If you are using the CLI, enters:
alarms alarm show
7 Follow the alarm clearing procedures in Fault Management - Alarm Clearing,
323-1851-543, to clear any unexpected alarms.
8 Check for the presence of any unexpected alarms on the transponder nodes,
use the appropriate alarm clearing procedures to clear any unexpected
alarms.
—end—

Procedure 5-10
Verifying traffic continuity for Fixed-96, Fixed-88,
Fixed-44, and Fixed-64 OPS protected configurations
Use this procedure to verify that the 6500 and transponder nodes are carrying
traffic correctly and that the protection switching on 6500 is working as
expected.
Prerequisites
To complete this procedure, you must:
• be logged into all applicable 6500 CLI sessions
• have connected all fibers between transponder and the 6500 CMD
• have verified the configuration of the 6500 and transponder nodes
• have the minimum number of transponder channels as listed in “Minimum
channel count” on page 2-12.
Step Action
LED status
1 On the 6500 amplifiers, verify that the following LEDs are dark:
• OSC 3/4
• Ln B 5/6
• Ln A 7/8
2 On the OPS circuit pack, verify that the following LEDs are dark:
• Sw1 13
• Sw2 15
3 On the 6500 SPAP-2s, verify that the OSC1 LEDs are dark.
Note: A yellow LED on the 6500 or Waveserver indicates that an alarm is
raised against that port.


Verifying traffic continuity for Fixed-96, Fixed-88, Fixed-44, and Fixed-64 OPS protected
configurations
Step Action
Verifying power levels and alarms

4 Verify that the Rx power on the transponder line ports are within the specified
range.
5 To verify the presence of any threshold crossing, power level, or other
unexpected alarms on the 6500 nodes:
• If you are using Site Manager, refer to Fault Management - Alarm
Clearing, 323-1851-543 for more information
alarms alarm show
6 Follow the alarm clearing procedures in Fault Management - Alarm Clearing,
323-1851-543, to clear any unexpected alarms.
7 Check for the presence of any unexpected alarms on the transponder nodes,
use the appropriate alarm clearing procedures to clear any unexpected
alarms.
Verifying 6500 protection status
8 To verify the protection configuration of the 6500 nodes, enter
• If you are using Site Manager, refer to Configuration - Protection
Switching, 323-1851-315 for more information
optmons prot-group show all
and verify that the prot-scheme is set to 1plus1.


configurations
Step Action
Testing manual protection switching

9 To verify the working and protection path of the 6500 nodes:
Operating, 323-1851-310 for more information
optmons optmon show optmon-1-3-all
For example:
Ciena_Toronto-17# optmons optmon show optmon-1-3-all
----------------------------------------------------
aid | OPTMON-1-3-13
los-thres | -20.00
port-label | "OPS3 SW1 In"
also-disabled | FALSE
pst | IS
sst | WRKRX
----------------------------------------------------
aid | OPTMON-1-3-15
los-thres | -20.00
pst | IS
sst | STBYH
In the above example, the working path is on OPTMON-1-3-13 (indicated by

sst | WRKRX) and the protection path is on OPTMON-1-3-15 (indicated by
sst | STBYH).
Note: The default configuration is the working path on OPTMON-1-3-13 and
the protection path on OPTMON-1-3-15.


configurations
Step Action
10 To operate a protection switch to the protect path,:

optmons prot-switch operate optmons-1-3-13 sc man
on the near-end and far-end 6500 nodes.
11 To confirm that the traffic has switched to the protect path:
> optmons optmon show optmon-1-3-all
For example:
-----------------------------------------------------
aid | OPTMON-1-3-13
los-thres | -20.00
pst | OOS-AU
sst | FAF,STBYH
-----------------------------------------------------
aid | OPTMON-1-3-15
los-thres | -20.00
pst | IS
sst | WRKRX
12 Verify that the traffic is on the alternate path on both 6500 nodes. In the above
example, the working path is now on OPTMON-1-3-15 (indicated by sst |
WRKRX) and the protection path is on OPTMON-1-3-13 (indicated by sst |
FAF, STBYH).
Verifying traffic on the 6500 protection path
13 Verify the traffic on the transponder client ports is working as expected using
a test set or the client traffic source.


configurations
Step Action
Moving traffic back to the working path

14 To move traffic back to the working path:
on the near-end and far-end 6500 nodes.
For example:
----------------------------------------------------
aid | OPTMON-1-3-13
los-thres | -20.00
pst | IS
sst | WRKRX
-----------------------------------------------------
aid | OPTMON-1-3-15
los-thres | -20.00
pst | IS
sst | STBYH
In the example, the working path is back on OPTMON-1-3-13 (indicated by
sst | WRKRX) and the protection path is back on OPTMON-1-3-15
(indicated by sst | STBYH).


configurations
Step Action
Testing automatic protection switching
DANGER
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.
16 On the working path, pull the Rx fiber (port 8) of the amplifier circuit pack on
one of the 6500 nodes. This will cause a switch to the protection path for the
near-end and far-end 6500 nodes.


configurations
Step Action
17 To confirm that the traffic has switched to the protect path:

For example:
aid | OPTMON-1-3-13
los-thres | -20.00
pst | OOS-AU
sst | FAF,STBYH
-----------------------------------------------------
aid | OPTMON-1-3-15
los-thres | -20.00
pst | IS
sst | WRKRX
and verify that the traffic is on the alternate path on both 6500 nodes.
Verifying traffic on the 6500 protection path
18 Verify the traffic on the transponder client ports is working as expected using
a test set or the client traffic source.


configurations
Step Action
Moving traffic back to the protection path

19 Reconnect the fiber into the Rx port of the 6500 amplifier.
20 To move traffic back to the working path:
on the near-end and far-end 6500 nodes
For example:
-----------------------------------------------------
aid | OPTMON-1-3-13
los-thres | -20.00
pst | IS
sst | WRKRX
-----------------------------------------------------
aid | OPTMON-1-3-15
los-thres | -20.00
pst | IS
sst | STBYH
In the above example, the working path is back on OPTMON-1-3-13
(indicated by sst | WRKRX) and the protection path is back on OPTMON-1-
3-15 (indicated by sst | STBYH).
—end—


323-1851-221
6-1
Passive OTS network procedures 6-
This chapter contains all the necessary procedures to turn up a passive OTS
network.
Before performing the procedures in this chapter, it is assumed that the proper
planning and engineering work has been completed. OnePlanner is a network
design and link engineering tools that support the passive OTS networks. Use
either one of these tools to complete the engineering of such network.
OnePlanner can generate reports and Visio schematics that will be used in
the execution of these procedures.
As indicated in some procedures, it is expected that the user mark up printed

versions of the Visio diagrams to record required pad adjustments. The user
is also expected to record the actual adjusted per channel power values at the
various measurement points used for pad adjustments. In the case of the CND
tool, you can use the Power Levels worksheet to record the power of each
wavelength at various locations where adjustments are being made.

• “Passive OTS network procedures” on page 6-2

BR Back reflection
BS Band splitter
CMD Channel Mux/Demux
CND Ciena Network Designer
DSCM Dispersion slope compensation module
DWDM Dense wavelength division multiplexing
EDP Engineering documentation package
FGA Fixed gain amplifier
ID Identifier
IDP International documentation package
LED Light emitting diode

6-2 Passive OTS network procedures
NE Network element
OADM Optical add/drop multiplexer
OMDF Optical mux/demux filter
OPM Optical power monitor
Optical power meter
OSA Optical spectrum analyzer
OSC Optical service channel
OSCF OSC filter
OSP Outside plant
OSPF Open shortest path first
OTDR Optical time domain reflectometer
OTN Optical transport network
OTS Optical transport sections
PEC Product engineering code
PPC6 6-slot passive photonics chassis
RX Receive
SFP Small form-factor pluggable
TX Transmit
UPC User privilege code
XFP Large form-factor pluggable
ZPT Zero pass through
Passive OTS network procedures

Table 6-1
Procedure
Procedure 6-1, “Adding passive components”
Procedure 6-2, “Creating a passive OTS and defining its configuration”
Procedure 6-3, “Provisioning line adjacencies”
Procedure 6-4, “Equalizing a passive layer network”
Procedure 6-5, “Equalizing the OTS TX at a ZPT node”
Procedure 6-6, “Equalizing OTS RX and OTS TX at an express node”
Procedure 6-7, “Equalizing the OTS RX at a ZPT node”
Procedure 6-8, “Equalizing a line amplifier node with one FGA”

Table 6-1
Procedure
Procedure 6-9, “Equalizing a line amplifier node with two FGA”
Procedure 6-10, “Adding a new channel over a passive OTS network”
Procedure 6-11, “Inserting a new add/drop filter”
Procedure 6-12, “Turning up channels over a Passive Bridge to ROADM configuration”
Procedure 6-13, “Turning up channels over a Passive Bridge to ROADM—one passive tail
configuration”

Procedure 6-1
Adding passive components
Use this procedure to provision passive components that are involved in the
passive OTS.
OMDF8 is a double-width module. It can be installed in either slot 1 (occupying

slots 1 and 2) or slot 4 (occupying slots 4 and 5) of the 2150 (6-slot) chassis
and the 6-slot passive photonics chassis (PPC6), and in slot 1 (occupying
slots 1 and 2) of the 2150 (3-slot) chassis. Make sure the partition between
slots 1 and 2 or between slots 4 and 5 is removed by removing the retainer
screw(s) and pulling out the partition.
The DSCM modules that are not part of Ciena’s portfolio or have no I2C
external Ethernet connectors and the 2150 (6-slot) and 2150 (3-slot) chassis
should be provisioned to one of the virtual slots. The virtual slots are: slots 29
to 32 on a 2-slot shelf (NTK503MAE5/NAE5 variants), slots 91 to 99 on a
2-slot (NTK503LA variant), 6500-7 packet-optical, 7-slot, or 14-slot shelf, and
slots 63 to 82 on a 32-slot shelf.
In the passive OTS network, pads are not provisioned using the DSCM
equipment type (and hence not part of an OTS). Pads are provisioned using
the pad loss parameter value within the ADJ-FIBER facility of a given port as
indicated in step 42 of this procedure.
Note that in this procedure, the 2xOSC circuit pack could be the SPAP-2
w/2xOSC circuit pack if applicable.
Prerequisites
• be logged into the network element and have the Site Manager interface
open
Step Action
1 Select the required network element in the navigation tree.

2 Select Equipment & Facility Provisioning from the Configuration
drop-down menu to open the Equipment & Facility Provisioning application.
3 Select the required shelf from the Shelf drop-down list.


Step Action

If your configuration requires Then go to
OSCF, OMDF4, OMDF8, and/or BS modules step 5
otherwise step 18

2150 (6-slot) chassis or 2150 (3-slot) chassis step 6
6-slot passive photonics chassis (PPC6) in a shelf with step 6
auto-equipping disabled or with no external slot support
6-slot passive photonics chassis (PPC6) in a shelf that step 9
supports external slots and with auto-equipping enabled
6 First, add the 2150 (6-slot) chassis, 2150 (3-slot) chassis or 6-slot passive
photonics chassis (PPC6) needed to house the passive components. The
2150 (6-slot) chassis, 2150 (3-slot) chassis or 6-slot passive photonics
chassis (PPC6) is required only if the passive configuration contains the
OSCF, OMDF4, OMDF8, or BS modules. Click Add in the Equipment area to
open the Add Equipment dialog box. In the Add Equipment dialog box, enter
the required information (as per EDPs):
• select PPC6 in the Type drop-down menu
• select the chassis type in the Provisioned PEC drop-down menu
• select the required slot number
• the State is IS by default
• click OK
7 Verify that the 2150 (6-slot) chassis, 2150 (3-slot) chassis or 6-slot passive
photonics chassis (PPC6) appears in the Equipment list.
8 Repeat from step 6 to add all the necessary 2150 (6-slot) chassis, 2150
(3-slot) chassis or 6-slot passive photonics chassis (PPC6).
Go to step 11.
9 Connect the 6-slot passive photonics chassis (PPC6) to the external slots on
the access panel using straight-through RJ-45 cables. The 6-slot passive
photonics chassis (PPC6) auto-provision.
10 Verify that the 6-slot passive photonics chassis (PPC6) appear in the
Equipment list.


Step Action

If the passive filters are equipped in a Then go to
2150 (6-slot) chassis or 2150 (3-slot) chassis step 12
6-slot passive photonics chassis (PPC6) in a shelf with step 12
auto-equipping disabled or with no external slot support
6-slot passive photonics chassis (PPC6) in a shelf that step 16
supports external slots and with auto-equipping enabled
12 Add the OSC filters, the optical mux/demux filters and the band splitters
needed in your configuration (as per EDPs). Click Add in the Equipment area
to open the Add Equipment dialog box. In the Add Equipment dialog box,
enter the required information (as per EDPs):
• select in the Type drop-down menu
— OSCF for an OSC filter
— OMDF4 for a 4-channel optical mux/demux filter
— OMDF8 for an 8-channel optical mux/demux filter
— BS for a band splitter
• select the proper module in the Provisioned PEC drop-down menu
• select the required slot-subslot in the Slot drop-down menu
• click OK
13 Verify that the filter module appears in the Equipment list.
14 Repeat from step 12 to add all the necessary filter modules.
15 Insert the filter modules in the appropriate slots of the 2150 (6-slot) chassis
or 2150 (3-slot) chassis or the 6-slot passive photonics chassis (PPC6) (as
per EDPs).
Go to step 18.
16 Insert the OSC filters, the optical mux/demux filters and the band splitters in
the appropriate slots of the 6-slot passive photonics chassis (PPC6) (as per
EDP). The passive filters auto-provision.
17 Verify that the filter modules appear in the Equipment list.


Step Action

4200 DCM modules step 19
6500 DSCM modules in a shelf with auto-equipping step 19
disabled or with no external slot support
6500 DSCM modules in a shelf that supports external step 22
slots and with auto-equipping enabled
no DSCM modules step 24
19 Add the DSCM needed in your configuration (as per EDPs). Click Add in the
Equipment area to open the Add Equipment dialog box. In the Add Equipment
dialog box, enter the required information (as per EDPs):
• select DSCM in the Type drop-down menu
• select the proper DSCM in the Provisioned PEC drop-down menu
• click OK
20 Verify that the DSCM appears in the Equipment list.
21 Repeat from step 19 to add all the necessary DSCMs.
Go to step 24.
22 Connect the 6500 DSCM modules to the external slots on the access panel
using straight-through RJ-45 cables. The 6500 DSCM modules
auto-provision.
23 Verify that the 6500 DSCM modules appear in the Equipment list.
L-band MLA/LIM, FGA, and/or 2xOSC circuit packs in a step 25
shelf with auto-equipping enabled
L-band MLA/LIM, FGA, and/or 2xOSC circuit packs in a step 28
shelf with auto-equipping disabled
no L-band MLA/LIM, FGA, or 2xOSC circuit packs step 36
25 Insert the L-band MLA/LIM, FGA, and/or 2xOSC circuit packs in the
appropriate slots (as per EDP). The L-band MLA/LIM, FGA, and/or 2xOSC
circuit packs auto-provision.
26 Once the blue LED and green LED on the L-band MLA/LIM, FGA, and/or
2xOSC circuit packs turn steadily on, verify that the L-band MLA/LIM, FGA,
and/or 2xOSC circuit packs appear in the Equipment list.


Step Action
27 For the 2xOSC circuit packs, insert the required SFP modules in the
appropriate ports (as per EDP). The SFP modules auto-provision. Verify that
the SFP modules appear in the Equipment list.
Go to step 36.
28 Add the L-band MLA/LIM, FGA, and/or 2xOSC circuit packs needed in your
configuration (as per EDPs). Click Add in the Equipment area to open the
Add Equipment dialog box. In the Add Equipment dialog box, enter the
required information (as per EDPs):
• select in the Type drop-down menu
— LIM for an L-band MLA or LIM circuit pack
— FGA for an FGA circuit pack
— 2xOSC for a 2xOSC circuit pack
— SP for an SPAP-2 w/2xOSC circuit pack
• select the required slot in the Slot drop-down menu
• click OK
29 Verify that the L-band MLA/LIM, FGA, or 2xOSC circuit pack appears in the
Equipment list.
30 Repeat from step 28 to add all the necessary L-band MLA/LIM, FGA, and/or
2xOSC circuit packs.
31 Insert the L-band MLA/LIM, FGA, and/or 2xOSC circuit packs in the
appropriate slots (as per EDP).
32 For the 2xOSC circuit packs, add the required SFP modules (as per EDPs).
Click Add in the Equipment area to open the Add Equipment dialog box. In
the Add Equipment dialog box, enter the required information (as per EDPs):
• select P155M in the Type drop-down menu
• select the proper PEC in the Provisioned PEC drop-down menu
• select the required slot-port in the Slot drop-down menu
• click OK
33 Verify that the SFP module appears in the Equipment list.
34 Repeat from step 32 to add all the necessary SFP modules.
35 Insert the required SFP modules in the appropriate ports (as per EDP).


Step Action

OMX or CMD44 modules in a shelf that supports external step 37
slots and with auto-equipping enabled
OMX or CMD44 modules in a shelf with auto-equipping step 39
disabled or with no external slot support
no OMX or CMD44 modules step 42
37 Connect the OMX or CMD44 modules to the external slots on the access
panel using straight-through RJ-45 cables. The OMX or CMD44 modules
auto-provision.
38 Verify that the OMX or CMD44 modules appear in the Equipment list.
Go to step 42.
39 Add the OMX or CMD44 modules needed in your configuration (as per
EDPs). Click Add in the Equipment area to open the Add Equipment dialog
box. In the Add Equipment dialog box, enter the required information (as per
EDPs):
• select OMX or CMD44 in the Type drop-down menu
• select the proper OMX or CMD44 in the Provisioned PEC drop-down
menu
• click OK
40 Verify that the OMX or CMD44 module appears in the Equipment list.
41 Repeat from step 39 to add all the necessary OMX or CMD44 modules.
42 Provision the required pad.
• Select the equipment that the pad is connected to in the Equipment list.
For a pad at the line port of a transponder, select the channel port of the
channel mux/demux that the line port is connected to.
• Select the ADJ-FIBER in the Facility Type drop-down menu.
• Select the ADJ-FIBER facility corresponds to the port where the pad is
connected in the Facility list and click Edit.
• Enter the pad value in the Pad Loss field.
• Click OK.
43 Repeat step 42 for all the required pads.
—end—

Procedure 6-2
Creating a passive OTS and defining its configuration
Use this procedure to create a passive OTS and define the position of each
component within the OTS.
Prerequisites
• be logged into the network element and have the Site Manager interface
open
• make sure the passive components have been provisioned according to
Procedure 6-1, “Adding passive components”
• review the new OTS provisioning model concept in the overview section of
the “OTS Slot Sequencing” chapter in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310
Step Action
1 Perform the “Creating an OTS instance with basic parameters” procedure in

2 Perform the “Editing slot sequences” procedure in Part 2 of Configuration -
3 If defining a passive amplifier OTS, repeat step 2 to edit the slot sequence for
the amplifier mate OTS.
4 Provision the line adjacencies using Procedure 6-3, “Provisioning line
adjacencies”.
—end—

Procedure 6-3
Provisioning line adjacencies
Use this procedure to provision the line adjacencies for each passive OTS or
passive configuration site. The Actual Far End Address field will not be
populated.
Note: The line in and line out adjacencies must be provisioned in order
for links to be populated in OneControl.
Prerequisites
• have the Site Manager interface open
• be logged into each network element
• make sure the passive OTS or configuration has been defined according
to Procedure 6-2, “Creating a passive OTS and defining its configuration”
Step Action
1 Select Equipment & Facility Provisioning from the Configuration

drop-down menu to open the Equipment & Facility Provisioning application.
3 Select the line facing equipment in the configuration as per EDPs in the
Equipment list.
4 Select ADJ from the Facility Type drop-down menu.
5 Select the required ADJ facility corresponding to the port you are provisioning
and click Edit to open the Edit ADJ Facility dialog box.
6 In the Edit ADJ Facility dialog box, enter the required information (as per
EDPs):
• select LINE in the Adjacency type drop-down menu
• select the required Expected far end address format
• select or enter the required Expected far end address that points to the
line port at the next site
• enter the required Customer defined facility identifier
• click OK
7 Repeat from step 3 for the other line facing equipment if applicable.
—end—

Procedure 6-4
Equalizing a passive layer network
This procedure provides an example for equalizing (or pad tuning) a passive
layer network, using the example network shown in Figure 6-1 on page 6-22.
Before deploying and turning-up any 6500 passive layer network, the output
from either the Ciena Network Designer (CND) or the OnePlanner tool must
be used to design and build the network. The Ciena account team uses the
tool to generate the equipment requirement for the network based on the
customer network requirements (that is, facility, wavelength, capacity, and
service requirements). A graphical output (in Visio format) from the tool is
used to build the network.
The tool output provides the following information that is necessary to turn-up
a 6500 passive layer network:
• Network View diagram (CND) / screen capture of the OnePlanner tool
view or Visio report (OnePlanner) – indicates the number of nodes and the
fiber type/loss specifications for the optical network interconnections
between the nodes. Figure 6-1 on page 6-22 is an example of the CND
network view for a 5-node network. OnePlanner provides a similar network
view.
• Node View diagrams (CND) / NE OTS diagrams and Fiber Run List Report
(OnePlanner) – indicate the optical interconnections for each node. The
diagrams and the report identify the fiber interconnections and potential
pad placements at each node and between nodes. These diagrams and
reports indicate all connections between the interface module ports and
the network fiber plant. Figure 6-2 on page 6-23 is an example of the CND
node view diagram for an OTS of a node. Figure 6-3 on page 6-24 is a
OnePlanner example of the NE OTS diagram. Figure 6-4 and Figure 6-5
on page 6-25 illustrate an excerpt from the OnePlanner Fiber Run List
Report for the example in Figure 6-3 on page 6-24.
• Power Level reports (CND) / Passive Provisioning grid and DWDM
Adjacencies grid (OnePlanner) – indicate the optical channel power
values for the DWDM ports within each node. This tool output identifies the
channel and/or network power levels that should be achieved. The power
levels are achieved in a passive layer network by manual pad placement.
Figure 6-6 on page 6-26 is an example of the tabular power report for a
node. In OnePlanner, the information can be exported from the Passive
Provisioning and DWDM Adjacencies grids (see Passive Provisioning
example in Figure 6-7 and Figure 6-8 on page 6-27, and DWDM
Adjacencies example in Figure 6-9 on page 6-28, Figure 6-10 on page
6-29, Figure 6-11 on page 6-29, and Figure 6-12 on page 6-30).


• Rack View diagrams (CND only) – indicate how the 2150 (6-slot), 2150
(3-slot) or PPC6 shelves and other ancillary equipment (filters, DSCMs,
and so on) are populated at each node. These diagrams also identify the
SFP/XFP requirements for each node.
The CND and OnePlanner Visio output examples provided in Figure 6-1 on
page 6-22, Figure 6-2 on page 6-23, and Figure 6-3 on page 6-24 are for
network-level turn-up and test explanation purposes only. The example
network is intended to capture some of the standard network configuration
concepts present in actual deployments. Understanding the concepts
contained in these network-level diagrams and in the subsequent
network-level turn-up description allows this information to be adapted for any
network configuration. For special network-level configurations not described
in this section, contact the Ciena account team for additional information.
In Figure 6-1 on page 6-22 (CND) (the OnePlanner network view is similar),
five 6500 nodes are connected in an end-to-end configuration. Included in this
diagram are the span fiber characteristics and the open or closed type of
node, where an open (or Zero Pass Through, ZPT) node contains all add/drop
traffic with no pass-through (express) traffic, and a closed node may contain
add/drop traffic but always contains pass-through (express) traffic. The step
number marked up in the diagram refers to the step number in this procedure.
The OTS TX and OTS RX terminology is explained in Figure 6-13 on page
6-31.
The Node View diagram, provided by CND as shown in Figure 6-2 on page
6-23, indicates the optical connections that are made between the different
chassis, ancillary equipment (that is, the FGAs, DSCMs, filters, and band
splitters), and span fiber at each node. The connection detail is provided to the
port level. The suggested need and recommended location of optical
attenuators is also shown on the diagram, if applicable. This information is
provided by OnePlanner as shown in Figure 6-3 on page 6-24, Figure 6-4 on
page 6-25, and Figure 6-5 on page 6-25.
The optical attenuator values included on the interconnection diagrams are

based on the network design, and may not reflect the final operational field
values. Therefore, in the field, padding values can be different, indicated pads
may not be needed, or additional pads (not indicated in the pad list) may be
required. Suggested pads values are included in the OnePlanner Visio report
(detailed site view tabs). Rx Overload protection suggested pad values are
available in the OnePlanner DWDM Adjacencies grid.


The CND Power Level report, as shown in Figure 6-6 on page 6-26, contains
target channel power levels (average, maximum and minimum) for the
following points within a 6500 passive layer node:
• FGA input
• Network Fiber Launch output
• Transponder Receiver input
OnePlanner provides channel power targets (average, maximum and

minimum) in the Passive Provisioning grid, as follows:
• FGA output
• Network Fiber Launch output
Transponder Receiver Input targets and suggested starting pad values are
provided in the OnePlanner DWDM Adjacencies grid.
The target channel power levels called out in the CND Power Level report or
the OnePlanner grids are realized at installation time by the channel
equalization procedure (this procedure as an example), which is a process for
installing pads and manual adjustment (that is, “tuning”) of the pad values with
appropriate test equipment and test points. Therefore, equalizing sometimes
is also called pad tuning.
6500 passive layer networks use generic pad placements for the channel
equalization procedure. The following is a description of these pad
placements (refer to Figure 6-14 on page 6-32):
• FGA Overload Pads Z(FGA) – Placed at a FGA-RX (pre-amplifier) input to
ensure the FGA output does not saturate before full channel count
loading. When a DSCM precedes the FGA, then the pad is placed before
the DSCM.


• Launch Pads Z(LAUNCH) – Placed on the express path of an OADM or

Line Amplifier to set the express channels' fiber launch power to the target
design value. Launch pads are present only at nodes with an express path
(that is, not at ZPT nodes). At an OADM node, a Z(LAUNCH) pad is
normally placed between the last drop filter and the first add filter in the
direction of interest. However, in some specific OADM node configurations
(see the diagram 4 in Figure 6-14 on page 6-32), there may be more than
one Z(LAUNCH) pad. In this case, the equalization procedure asks that
the Z(LAUNCH) pad be adjusted at each interconnection of the receiving
OTS and the transmitting OTS. At a Line Amplifier node, the Z(LAUNCH)
pad placement varies. If the Line Amplifier has a single FGA in the
direction of interest, the Z(LAUNCH) pad is placed at that FGA's input. If
the Line Amplifier has two cascaded FGAs in the direction of interest, an
FGA pad is placed at the first amplifier's input and a Z(LAUNCH) pad is
installed at the second amplifier's input. In both the single FGA and dual
FGA configurations, when a DSCM precedes the FGA, then the pad is
placed before the DSCM.
• Receiver Overload Pads Z(drop,n) – Placed before the receive port of a
transponder's DWDM interface to set the channel RX power to the target
design value.
• Channel Equalization Pads Z(add,n) – Placed at the channel input of a
channel Mux/Demux module to set each added channel's fiber launch
power to the target design value.
• FGA Output Pad – Placed at the output of the FGA to ensure that the
power in the fiber plant will meet target power.
Within a node, pad values are installed and “tuned” starting upstream and
progressing downstream in the signal direction. Each pad value is chosen so
that all channel powers measurements at the reference point indicated in
Table 6-2 on page 6-17 are as close to the average design value as possible,
while ensuring that they are within the maximum and minimum thresholds
defined in the CND Power Level report or the OnePlanner grids.
Pads should always be placed at the receive port of an interconnection.

Adopting this standard practice facilitates network maintenance activities. If
two pads must be concatenated, and there is insufficient space to
accommodate the cascaded pads (such as interference of a shelf cover), one
pad can be placed at the transmit port and a second pad at the receive port.


The 6500 OTS and topology software allows almost any placement of the
different components (for example, DSCM, pads, etc.) in a passive photonic
system. However, the CND and OnePlanner design tools determine the
placement of the different components (for example, DSCM, pads, etc.) in a
passive photonic system that is a smaller subset of what the 6500 software
allows. See Figure 6-14 on page 6-32 for CND or OnePlanner tool possible
component placement. This equalization procedure is designed to support the
configurations defined by the CND or OnePlanner tool, not all possible
configurations supported by the 6500 software. Therefore, to use this
procedure, the 6500 passive layer network must be modeled using CND or
OnePlanner. If the system was not modeled using CND or OnePlanner, this
procedure may not be used.


Table 6-2
Summary of external pad IDs, placement rules, test points and verification criteria
Pad ID Associated Measurement and set point details

with power
into Physical Reference Measure- Criteria
placement point ment
type
Z(FGA) FGA FGA Line FGA Line Out OSA Pad that sets all Pch as close to
Input (see PFGA,avg as possible, while
Note) guaranteeing that
PFGA,min<Pch<PFGA,max
Z(FGA Tx) Node FGA Tx Node egress OSA Pad that sets all Pch as close to
egress PLAUNCH,avg as possible, while
guaranteeing that
PLAUNCH,min<Pch<PLAUNCH,max
Z(LAUNCH) Node Varies with Node egress OSA Pad that sets all Pch as close to
egress configuration PLAUNCH,avg as possible, while
guaranteeing that
Z(drop,n) Channel RX Channel Rx Channel OPM Pad that sets Pdrop,in as close to
Input Demux Out Pdrop,n,avg as possible, while
guaranteeing that
Pdrop,n,min<Pch<Pdrop,n,max
OnePlanner considerations: The DWDM Adjacencies grid provides a threshold value (Max
Rx Power Required) and the Rx Nominal Level value. If the measured power is above the
threshold, you must install a pad to bring the power level between the threshold and Rx
Nominal Level. The power level should be as close to the Rx Nominal Level as possible.
Z(add,n) Channel Channel Mux At installation: OSA Pad that sets Padd,n as close to
Mux Input Node egress PLAUNCH,avg as possible, while
guaranteeing that
PLAUNCH,min<Padd,n<PLAUNCH,max
After OSA, Pad that sets Pch as close to

installation: OPM PLAUNCH,avg as possible, while
Node egress guaranteeing that
Monitor
Note: When a DSCM precedes the FGA, then the pad is placed before the DSCM.
OSA: Optical Spectrum Analyzer
OPM: Optical Power Meter


Prerequisites
All actions contained in this procedure are to be executed on an OTS that was
previously created and defined as per the previous procedures.
All the passive components that are part of the OTS being worked on have all
been installed and provisioned properly.
All fibers connecting the passive components that are part of the OTS being
worked on have all been installed properly (labeled, routed, cleaned,
inspected and connected).
Fibers between the DWDM transmitters and the appropriate MUX ports have
all been labeled, routed, cleaned, inspected and connected at both ends. The
pads that are present in this connection should be as specified in the EDPs
(as per the CND or OnePlanner tool).
Fibers that are to connect the DWDM receivers to the DEMUX port have been
labeled, routed, cleaned, inspected and connected to the DEMUX ports but
not to the receivers. Instead the ends that are to be connected to the DWDM
receivers should be protected by dust caps.
All other padding indicated in the EDPs should also be present.
Refer to the Attenuators table in Planning - Ordering Information,

323-1851-151 for pad values and pad numbers.
All transponder line interfaces in the design must be present with transmit
ports enabled and outputting proper optical power levels.
The network must have at least one pass-through wavelength at each express
or line amp node. This is a prerequisite since it is important to set the
Z(LAUNCH) pad correctly during the initial install. Having to add or change it
afterwards on an existing system will be traffic affecting.
The following outside fiber plant pre-checks must be performed:

• Verify the end-to-end fiber spans using an optical time domain
reflectometer (OTDR) and a fixed C-Band (that is, 1550nm) light source to
measure actual end-to-end losses.
Note: End-to-end is defined as all the components (OSP fiber span,
distribution frames, patch cords, and so on) that make up the end-to-end
optical connectivity between 6500 nodes.


• Verify the actual fiber span characteristics to ensure they match the fiber
type, length, and loss in the to-build network design.
• Unidirectional span losses may differ, but higher loss span should be
equivalent to the loss in the to-build network design.
• Measure back reflection (BR) at the input and outputs of the fiber spans
(and any associated patch panels) to ensure no single event has a BR of
greater than -40 dB.
• Fiber dispersion measurements are recommended if the fiber
characteristics are uncertain.
CAUTION
Do not attempt to optically turn up the network if the fiber span
data does not match the values in the network design. Contact
the Ciena account team to re-validate the design with the
updated fiber span data.
To perform this procedure, you require:

• an optical spectrum analyzer (OSA)
• an optical power meter (OPM)
• a variety of fixed pads, fiber-optic connectors, inspection & cleaning tools
• CND or OnePlanner reports as part of the EDPs
Notes about the OSA:

• To avoid damaging the instrument, read the user manual to understand
the maximum tolerable input power of the OSA. Determine if a calibrated
pad is required or if a particular setting must be applied to activate the
internal attenuator. As a reminder, the FGA maximum output power is
17 dBm.
• Adjust the OSA resolution bandwidth or use integrated power to measure
the complete signal power for each traffic carrying wavelength. You need
to consider the type of modulation being used. A resolution bandwidth of
0.2 nm is adequate for 2.5G, 10G, and 40G interfaces, and 0.5 nm for
100G interfaces.


Step Action
1 Start at ZPT Node 1 (clockwise). See Figure 6-1 on page 6-22.

• Tune pads where wavelengths are muxed (clockwise) or the OTS TX
direction.
• Do not tune pads in demux (counter clockwise) or OTS RX direction as
no padding has occurred upstream.
• Follow Procedure 6-5, “Equalizing the OTS TX at a ZPT node”.
2 Progress to Express Node 2 which has 2 OTSs, one for each facing direction.
OTS1 faces Node 1 and OTS2 faces Node 3.
• Tune pads where wavelengths are demuxed (clockwise) or the OTS1 RX
direction.
• Then tune pads where wavelengths are muxed (clockwise) or the OTS2
TX direction.
• Follow Procedure 6-6, “Equalizing OTS RX and OTS TX at an express
node”.
3 Progress to Line Amplifier Node 3 which has 2 OTSs, one for each facing
direction. OTS1 faces Node 2 and OTS2 faces Node 4.
• Tune pads in the clockwise direction.
• Follow Procedure 6-8, “Equalizing a line amplifier node with one FGA” or
Procedure 6-9, “Equalizing a line amplifier node with two FGA”.
• Tune pads where wavelengths are demuxed (clockwise) or the OTS1 RX
direction.
• Then tune pads where wavelengths are muxed (clockwise) or the OTS2
TX direction.
node”.
5 Progress to ZPT Node 5.
• Tune pads where wavelengths are demuxed (clockwise) or the OTS RX
direction.
• Follow Procedure 6-7, “Equalizing the OTS RX at a ZPT node”.
• This concludes the equalization procedure for the clockwise (CW)
direction.


Step Action
6 Start at ZPT Node 5 (counterclockwise).

• Tune pads where wavelengths are muxed (counterclockwise) or the OTS
TX direction.
• Follow Procedure 6-5, “Equalizing the OTS TX at a ZPT node”.
• Tune pads where wavelengths are demuxed (counterclockwise) or the
OTS2 RX direction.
• Then tune pads where wavelengths are muxed (counterclockwise) or the
OTS1 TX direction.
node”.
8 Progress to Line Amplifier Node 3 which has 2 OTSs, one for each facing
direction. OTS1 faces Node 2 and OTS2 faces Node 4.
• Tune pads in the counterclockwise direction.
• Follow Procedure 6-8, “Equalizing a line amplifier node with one FGA” or
Procedure 6-9, “Equalizing a line amplifier node with two FGA”.
OTS2 RX direction.
• Then tune pads where wavelengths are muxed (counterclockwise) or the
OTS1 TX direction.
node”.
10 Progress to ZPT Node 1.
OTS RX direction.
• Follow Procedure 6-7, “Equalizing the OTS RX at a ZPT node”.
• This concludes the equalization procedure for the counterclockwise
(CCW) direction.
—end—

Figure 6-1
Example Network View diagram for a 5-node 6500 passive layer network

Figure 6-2
Example Node View diagram (CND) for an OTS of a 6500 passive layer node

Figure 6-3
Example NE OTS diagram (OnePlanner) for an OTS of a 6500 passive layer node

Figure 6-4
Excerpt from Fiber Run List Report (OnePlanner) for the network example in Figure 6-3 (columns
up to Source Conn)
Figure 6-5
Excerpt from Fiber Run List Report (OnePlanner) for the network example in Figure 6-3 (columns
from Source Slot on)

Figure 6-6
Example Power Level report (CND) for a 6500 passive layer node

Figure 6-7
Excerpt from Passive Provisioning grid report (OnePlanner) for the network example in Figure 6-3
(columns up to Equipment Group [OTS])
Figure 6-8
Excerpt from Passive Provisioning grid report (OnePlanner) for the network example in Figure 6-3
(columns from Equipment Group [OTS] on)

Figure 6-9
Excerpt from DWDM Adjacencies Report (OnePlanner) for the network example in Figure 6-3
(columns up to Provisioned PEC)

Figure 6-10
(columns from Derived PEC to Tx Typ. Launch Power)
Figure 6-11
(columns from Tx Max. Launch Power to PADDRFORM)

Figure 6-12
(columns from Estimated Rx Pad on)

Figure 6-13
OTS TX and OTS RX terminology illustration
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Z(FGA Tx)
Note: Equipment and placement within the OTS can be different from what is shown in this figure.
For example, at an express node, all the equipment in OTS2 can be in OTS1 or there can be only
one OTS provisioned. For the purposes of this equalization procedure, assume the equipment is
placed in the OTSs as shown.

Figure 6-14
Generic pad placement illustration
Z(FGA Tx)
1. Channel Access Node
Z(FGA Tx)
2. Line Amplifier with one FGA
Z(FGA Tx)
3. Line Amplifier with two FGAs
4. Interconnection points between the receiving OTS and the transmitting OTS
Note: Unidirectional traffic only is shown for simplicity. Not all equipment may be present in a particular node.

Procedure 6-5
Equalizing the OTS TX at a ZPT node
This procedure provides detailed steps to equalize the OTS TX at a ZPT node.
This procedure must be executed in conjunction with Procedure 6-4,
“Equalizing a passive layer network”.
Step Action
1 Connect an OSA to the appropriate location as indicated below.

• If an OSC filter is present in the OTS TX, disconnect the input of that OSC
filter and connect it to the OSA.
• If no OSC filter is present in the OTS TX, connect the OSA to the Out port
of the last component in that OTS TX. The Out port of the last component
in the OTS TX should have the fiber that connects to the fiber plant so you
will need to disconnect this fiber before connecting the OSA.
If an FGA Then go to
is present on the OTS Tx path step 3
is not present on the OTS Tx path step 4

If the FGA Tx target power is Then go to
equal to the Equipment Group Power/Channel target step 4
different than the Equipment Group Power/Channel target step 7
4 Locate the per channel target power expected at the point the OSA is
connected in the Power Levels tab of the detailed design report. This value is
located in the “P/ch avg (dBm)” column of the Power Levels table in the Visio
schematics produced by the CND tool (attached to the EDPs). OnePlanner
provides this information in the Passive Provisioning grid.
For each wavelength corresponding to a transmitter connected to the OTS
you are working on, compute the required power adjustment at the filter input.
This is Z(add,n) in diagram 2 of Figure 6-13 on page 6-31.
Adjustment (dB) = Power of λn on the OSA (dBm) - per channel Target Power
(dBm)


Equalizing the OTS TX at a ZPT node
Step Action
5 For each wavelength corresponding to a transmitter connected to the OTS

you are working on, make the adjustment.
• If the corresponding transmitter has an adjustable output power, make
the adjustment via software.
• If the corresponding transmitter has a fixed output power, round the
adjustment to the nearest integer value and apply it to the value of the
current pad. Replace with the appropriate pad. Mark up the schematics
to record the pad adjustments.
• Before proceeding to the next wavelength, make sure the adjusted power
of the current wavelength is within ±1.0 dB of the target value. Repeat the
adjustment if required (replace the pad if it does not provide the expected
loss). Add a column to the power levels table and record the adjusted
power of the wavelength.
Note: If all wavelengths powers are lower than the target value by a large
amount, look for an excessive loss point at the output of the MUX chain. If only
one group of wavelength is showing a power level much lower than expected,
look for the excess loss point at the output of the corresponding MUX module.
If only one wavelength has a power much lower than expected, look for the
excessive loss point at the input of the MUX. In all cases, fix the problem
immediately before continuing to the next step.
6 Ensure that all wavelengths power are within the maximum and minimum
power indicated in the Power Levels report (P/ch max and P/ch min). Store
an OSA trace showing all channels power levels and archive it. Archive and
name the file so that the data can be easily associated to the site and the
precise location of the OSA test point (Bay/shelf/slot/port) and the date.
7 Once the FGA Tx target power level is achieved, measure the FGA output
power and compare it against the Equipment Group Power/Channel target to
determine if an additional pad is required at the output of the FGA.
8 Disconnect the OSA and reconnect the fiber you disconnected in step 1.
9 Return to the step in Procedure 6-4, “Equalizing a passive layer network” that
called this procedure.
—end—

Procedure 6-6
Equalizing OTS RX and OTS TX at an express node
This procedure provides detailed steps to equalize the OTS RX and OTS TX
at an express node. This procedure must be executed in conjunction with
Procedure 6-4, “Equalizing a passive layer network”.
Step Action
1 If an FGA-RX (pre-amplifier) is present in the OTS RX, go to step 2.

Otherwise go to step 6.
2 Disconnect the fiber connected to the FGA-RX output. Then connect an OSA
to the FGA-RX output.
Compute the required power adjustment for the pad. This is Z(FGA) in
diagram 1 of Figure 6-13 on page 6-31.
Adjustment (dB) = (Pmax + Pmin)/2 - per channel Target Power (dBm)
where Pmax (dBm) and Pmin (dBm) are the highest and lowest channel power
measurements made on the OSA, respectively.
4 Make the adjustment. Round the adjustment to the nearest integer value and
apply it to the value of the current pad. Replace with the appropriate pad.
Mark up the schematics to record the pad adjustments.
• Make sure the adjusted power of all wavelengths falls within the max per
channel power and the min per channel power values as indicated in the
CND Power Levels table (under column “P/ch max” and column “P/ch
min”). OnePlanner provides this information in the Passive Provisioning
grid.
• Repeat the adjustment if required (replace the pad if it does not provide
the expected loss).
• Add a column to the Power Levels table and record the adjusted power of
the wavelength. Also mark up the Visio schematics accordingly.
Note: If you cannot get all the wavelengths within the minimum per
wavelength power and the maximum per wavelength power, it indicates that
the equalization may not have been correctly done upstream.


Step Action
Z(drop,n) in diagram 1 of Figure 6-13 on page 6-31. For each wavelength
being dropped, connect a power meter on the demux output port and
measure the dropped channel power. Determine the pad required to set the
power in the range indicated by the Power Levels table.
If you are using OnePlanner, the DWDM Adjacencies grid provides a
threshold value (Max Rx Power Required) and the Rx Nominal Level value.
If the measured power is above the threshold, you must install a pad to bring
the power level between the threshold and Rx Nominal Level. The power
level should be as close to the Rx Nominal Level as possible.
Make sure the adjusted power of the current wavelength is within the required
range. Repeat the adjustment if required (replace the pad if it does not
provide the expected loss). Add a column to the power levels table and record
the adjusted power of the Rx wavelength.
Connect the fiber from the demux output port to each receiver through the
pad.
8 Considering only the pass-through wavelengths (not the channels being
added at this OTS), compute the required pad adjustment needed at each
interconnection of the receiving OTS and the transmitting OTS. Locate the
per channel target power expected at the point the OSA is connected. This
value is located in the “P/ch avg (dBm)” column of the Power Levels table in
the Visio schematics produced by the CND tool (attached to the EDPs).
Compute the required power adjustment for the pad at each interconnection
of the receiving OTS and the transmitting OTS. This is Z(LAUNCH) in diagram
1 of Figure 6-13 on page 6-31.
If an FGA is present on the OTS Tx path, you must use the FGA target power.
OnePlanner provides the FGA target output power in the Estimated Average
Power per Channel column of the Passive Provisioning grid.


Step Action
apply it to the value of the current pad at each interconnection of the receiving
OTS and the transmitting OTS. Replace with the appropriate pad. Mark up the
schematics to record the pad adjustments.
• Make sure the adjusted power of all pass-through wavelengths falls within
the max per channel power and the min per channel power values as
indicated in the Power Levels table (under column “P/ch max” and column
“P/ch min”).
the expected loss).
10 Considering only the add wavelengths (the channels being added at this
OTS), locate the per channel target power expected at the point the OSA is
schematics produced by the CND tool (attached to the EDPs). For each
wavelength corresponding to a transmitter connected to the OTS you are
working on, compute the required power adjustment at the filter input. This is
Z(add,n) in diagram 1 of Figure 6-13 on page 6-31.
Adjustment (dB) = Power of λn on the OSA (dBm) - per channel Target Power
(dBm)
If an FGA is present on the OTS Tx path, you must use the FGA target power.
OnePlanner provides the FGA target output power in the Estimated Average
Power per Channel column of the Passive Provisioning grid.


Step Action
11 For each wavelength corresponding to a transmitter connected to the OTS

you are working on, make the adjustment.
• If the corresponding transmitter has an adjustable output power, make
the adjustment via software.
current pad. Replace with the appropriate pad. Mark up the schematics
to record the pad adjustments.
• Before proceeding to the next wavelength, make sure the adjusted power
of the current wavelength is within ±1.0 dB of the target value. Repeat the
adjustment if required (replace the pad if it does not provide the expected
loss). Add a column to the power levels table and record the adjusted
power of the wavelength.
Note: If all wavelengths powers are lower than the target value by a large
amount, look for an excessive loss point at the output of the MUX chain. If only
one group of wavelength is showing a power level much lower than expected,
look for the excess loss point at the output of the corresponding MUX module.
If only one wavelength has a power much lower than expected, look for the
excessive loss point at the input of the MUX. In all cases, fix the problem
immediately before continuing to the next step.
12 Ensure that all wavelengths power are within the maximum and minimum
power indicated in the Power Levels report (P/ch max and P/ch min). Store
an OSA trace showing all channels power levels and archive it. Archive and
name the file so that the data can be easily associated to the site and the
precise location of the OSA test point (Bay/shelf/slot/port) and the date.
If an FGA Then go to
is present on the OTS Tx path step 14
is not present on the OTS Tx path step 16

15 Once the FGA Tx target power level is achieved, measure the FGA output
power and compare it against the Equipment Group Power/Channel target to
determine if an additional pad is required at the output of the FGA.


Step Action
—end—

Procedure 6-7
Equalizing the OTS RX at a ZPT node
This procedure provides detailed steps to equalize the OTS RX at a ZPT
node. This procedure must be executed in conjunction with Procedure 6-4,
Step Action
1 If an FGA-RX (pre-amplifier) is present in the OTS RX, go to step 2.

Otherwise go to step 6.
2 Disconnect the fiber connected to the FGA-RX output. Then connect an OSA
to the FGA-RX output.
diagram 2 of Figure 6-13 on page 6-31.
Power Levels table (under column “P/ch max” and column “P/ch min”).
the expected loss).


Equalizing the OTS RX at a ZPT node
Step Action
Z(drop,n) in diagram 2 of Figure 6-13 on page 6-31. For each wavelength
being dropped, connect a power meter on the demux output port and
measure the dropped channel power. Determine the pad required to set the
power in the range indicated by the Power Levels table.
Make sure the adjusted power of the current wavelength is within the required
range. Repeat the adjustment if required (replace the pad if it does not
provide the expected loss). Add a column to the power levels table and record
the adjusted power of the Rx wavelength.
Connect the fiber from the demux output port to each receiver through the
pad.
If you are using OnePlanner, the DWDM Adjacencies grid provides a
threshold value (Max Rx Power Required) and the Rx Nominal Level value.
If the measured power is above the threshold, you must install a pad to bring
the power level between the threshold and Rx Nominal Level. The power
level should be as close to the Rx Nominal Level as possible.
—end—

Procedure 6-8
Equalizing a line amplifier node with one FGA
This procedure provides detailed steps to equalize a line amplifier node with
one FGA. This procedure must be executed in conjunction with
Procedure 6-4, “Equalizing a passive layer network”.
Step Action

provides the FGA target output power in the Estimated Average Power per
Channel column of the Passive Provisioning grid.
Compute the required power adjustment for the pad. This is Z(LAUNCH) in
diagram 3 of Figure 6-13 on page 6-31. The pad is at the FGA input if no
DSCM precedes the FGA or the pad is at the DSCM input if a DSCM
precedes the FGA.


Equalizing a line amplifier node with one FGA
Step Action
the expected loss).
• Store an OSA trace showing all channels power levels and archive it.
Archive and name the file so that the data can be easily associated to the
site and the precise location of the OSA test point (Bay/shelf/slot/port)
and the date.
5 Once the FGA Tx target power is achieved, measure FGA output power and
compare against the Equipment Group Power/Channel target to determine if
an additional pad is required at the output of the FGA.
—end—

Procedure 6-9
Equalizing a line amplifier node with two FGA
This procedure provides detailed steps to equalize a line amplifier node with
two FGA. This procedure must be executed in conjunction with Procedure 6-4,
Step Action
1 Disconnect the fiber connected to the FGA-RX output and then connect an
OSA to the FGA-RX output.
precedes the FGA.
the expected loss).


Step Action

Compute the required power adjustment for the pad. This is Z(LAUNCH) in
precedes the FGA.
the expected loss).
• Store an OSA trace showing all channels power levels and archive it.
Archive and name the file so that the data can be easily associated to the
site and the precise location of the OSA test point (Bay/shelf/slot/port)
and the date.


Step Action

9 Once FGA Tx target is achieved, measure FGA output power and compare
against the Equipment Group Power/Channel target to determine if an
additional pad is required at the output of the FGA.
—end—

Procedure 6-10
Adding a new channel over a passive OTS network
Use this procedure to add a new channel over an existing passive OTS
network. This procedure is not traffic impacting.
If no DWDM mux/demux ports are available to support the new wavelength,

you must first add the necessary mux/demux filter. If the necessary group
output/input ports are available from a band splitter module already connected
in line, then the new channel can be simply connected to these ports with no
impact to traffic. If this is not the case, you need to proceed with the insertion
of a new add/drop filter (Procedure 6-11, “Inserting a new add/drop filter”),
which will be traffic impacting.
Step Action
1 Make sure the new receivers are not connected.

2 In both locations where the new channel terminates, put a 20 dB pad at the
output of the new transmitter and connect them to the proper MUX port.
3 Connect an OSA on the monitor port as close as possible to the connection
to the transmit line fiber. If an FGA occupies a post amplifier position in the
OTS, connect the OSA to the output monitor port. If there is no FGA in a post
amplifier position, connect the OSA to a monitor port downstream from the
point where all wavelengths are multiplexed.
4 Determine the pad value that sets the added channel power within ±1.0 dB of
(Pmax + Pmin)/2, where Pmax (dBm) and Pmin (dBm) are the highest and lowest
channel power measurements made on the OSA.
5 Make the adjustment:
• If the new transmitter has an adjustable output power, make the
adjustment via software assuming the 20 dB pad is removed. Remove
the 20 dB pad and reconnect the new transmitter to the MUX port.
current pad. Replace with the appropriate pad.
• Before proceeding to the next step, make sure the adjusted power of the
new wavelength falls within ±1.0 dB of (Pmax + Pmin)/2, where Pmax (dBm)
and Pmin (dBm) are the highest and lowest channel power measurements
of the existing wavelengths. Repeat the adjustment if required (replace
the pad if it does not provide the expected loss).


Adding a new channel over a passive OTS network
Step Action
6 In both locations where the new channel terminates, connect a power meter
on the demux output port and measure the power. Determine the pad
required to set the power in the range indicated by the Power Levels table in
the Visio schematics produced by the CND tool (attached to the EDPs). Make
sure the adjusted power at the new wavelength receiver input is within the
required range. Repeat the adjustment if required (replace the pad if it does
not provide the expected loss).
7 Take a screen capture of the OSA launch spectrum with all added channels
and archive it.
—end—

Procedure 6-11
Inserting a new add/drop filter
Use this procedure to insert a new add/drop filter to an existing passive OTS
network.
It occasionally becomes necessary to deviate from the original network design

because traffic demands evolve differently from what was planned for. A
revised design, to be validated by the CND or the OnePlanner tool, may result
in additional filters being placed at an OADM. The insertion of these filters will
not affect the traffic on wavelengths added or dropped at the OADM site.
However, traffic passing through this node will be impacted.
With correct planning, the expansion of the node's add/drop capacity can be
managed with minimal impacts to channel equalization. If the new add/drop
filters are inserted after the last drop filter and before the first add filter, the
only pad that needs to be changed is the pad located between the two OTSs.
Previously deployed FGA, DSCM, receiver overload and channel equalization
pads will remain unchanged if the expansion filters are added as described.
See Figure 6-15 on page 6-51 for an illustration of add/drop filter insertion
procedure. Labeled numbers in this figure identify the steps to follow.
Step Action
1 For wavelengths that are supporting protected channels, use the proper
manual switch and lockout to move the traffic away from the path that will be
interrupted.
2 Select the first direction you want to work on and connect an OSA on the
monitor port as close as possible to the connection to the transmit line fiber.
• If an FGA occupies a post amplifier position in the OTS, connect the OSA
to the output monitor port.
• If there is no FGA in a post amplifier position, connect the OSA to a
monitor port downstream from the point where all wavelengths are
multiplexed.
• Record the trace and the total spectrum power.


Inserting a new add/drop filter
Step Action
3 Disconnect the fiber at the input of the PAD in the connection between the two
OTSs. Clean, inspect, label and connect a fiber between the EXPR output
port of the new DROP filter and the input of the PAD in the connection
between the two OTSs. In a similar manner, disconnect the fiber at the output
of the PAD in the connection between the two OTS. Clean, inspect, label and
connect a fiber between the EXPR input port of the new ADD filter and the
output of the PAD in the connection between the two OTSs.
4 Disconnect the fiber at the EXPR output port of the last existing drop filter.
Clean, inspect, label and connect a fiber between the EXPR output port of the
last existing DROP filter and the NTWK input port of the new DROP filter.
5 Disconnect the fiber at the EXPR input port of the first existing ADD filter.
Clean, inspect, label and connect a fiber between the EXPR input port of the
first existing ADD filter and the NTWK output port of the new DROP filter.
6 With the OSA still connected at the same location as in step 2, take another
trace of the spectrum and compute the adjustment needed on the PAD in the
connection between the two OTSs.
Adjustment (dB) = New total spectrum power (dBm) - Initial total spectrum
power (dBm)
7 Make the adjustment: Round the adjustment to the nearest integer value and
Before proceeding to the next step, make sure the adjusted spectrum power
falls within ±1.0 dB of initial spectrum power.
Note: If the pad adjustment in the connection between the two OTSs is not
done properly, the power balancing between express wavelengths and added
wavelength at this node will be altered leading to possible performance and
system margin degradation.
8 Capture and label the adjusted OSA trace and archive as a proof of correct
installation. Mark up the Visio schematics to indicate the revised pad value.
9 If the new add/drop filter have not been inserted in the other direction, repeat
from step 2 in the other direction. Otherwise, go to the next step.
10 Release the manual or lockout switches that were done in step 1.
11 Perform Procedure 6-10, “Adding a new channel over a passive OTS
network” to bring up channels at the newly inserted add/drop filters.
—end—

Figure 6-15
Generic view of a passive OTS

Procedure 6-12
Turning up channels over a Passive Bridge to ROADM
configuration
This procedure provides steps for turning up channels over Passive Bridge to
ROADM configurations, using the example shown in Figure 6-16 on page
6-55. Labeled numbers in the figure identify the steps to follow. For the
procedure on turning up channels over Passive Bridge to ROADM—one
passive tail configurations, see Procedure 6-13, “Turning up channels over a
Passive Bridge to ROADM—one passive tail configuration”.
For details on Passive Bridge applications and engineering rules, see the
6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA.
For special network-level configurations not described in this section, contact

the Ciena account team for additional information.
Step Action
1 Turn up the ROADM network. Refer to the SLAT process description and
flowchart in Chapter 1, “SLAT process overview”.
2 Provision the inventory, OTS, and adjacencies for the passive equipment at
Sites A, 1, 2, and B (see Figure 6-16 on page 6-55).
Refer to the following procedures in this chapter:
• Procedure 6-1, “Adding passive components”
• Procedure 6-2, “Creating a passive OTS and defining its configuration”
• Procedure 6-3, “Provisioning line adjacencies”
After you complete the provisioning, select your next step.

If you are turning up channels Then go to
in the Site A to Site B direction step 3
in the Site B to Site A direction step 10
Note: Each direction can be turned up independently.
Turning up channels in the Site A to Site B direction

3 Equalize the channels transmitted from Site A to Site 1. Refer to the
equalizing procedures in this chapter.
4 Equalize the channels received at Site 1 from Site A. Refer to the equalizing
procedures in this chapter.


Turning up channels over a Passive Bridge to ROADM configuration
Step Action
5 At Site 1, stitch channels from the passive OTS to the ROADM OTS.
Note: The network design output of either the Ciena Network Designer
(CND) or OnePlanner tool will show overload pads placed at Site 1/OTS4
CMD CH outputs (demux). Do not deploy these pads.
a. Connect the passive demux outputs directly to the ROADM mux inputs.
b. For each stitched channel at ROADM OTS CMD Channel In, set the Max/
typical launch power of the ADJ-TX facility to the power level measured
at ROADM OTS CMD Channel In.
The target powers for stitched channels at ROADM OTS mux are:
- approximately -6 dBm if ROADM OTS is equipped with MLA2
- approximately -1 dBm if ROADM OTS is equipped with MLA
6 Turn up the stitched channels over the ROADM network between Site 1 and
Site 2.
7 At Site 2, stitch the channels from the ROADM OTS to the passive OTS.
8 Equalize the channels transmitted from Site 2 to Site B. Refer to the
9 Equalize the channels received at Site B from Site 2. Refer to the equalizing
You have completed turning up the channels in the A to B direction.
Turning up channels in the Site B to Site A direction
10 Equalize the channels transmitted from Site B to Site 2. Refer to the
11 Equalize the channels received at Site 2 from Site B. Refer to the equalizing
procedures in chapter.
Note: The network design output of the either the Ciena Network Designer


Turning up channels over a Passive Bridge to ROADM configuration
Step Action
Site 1.
14 At Site 1, stitch the channels from the ROADM OTS to the passive OTS.
15 Equalize the channels transmitted from Site 1 to Site A. Refer to the
16 Equalize the channels received at Site A from Site 1. Refer to the equalizing
You have completed turning up the channels in the B to A direction.
—end—

Figure 6-16
Example of Passive Bridge to ROADM configuration
4 15 16 3
5 14
1
2
6 13
7 12
8 11 10 9

Procedure 6-13
Turning up channels over a Passive Bridge to
ROADM—one passive tail configuration
This procedure provides steps for turning up channels over Passive Bridge to
ROADM—one passive tail configurations, using the example shown in
Figure 6-17 on page 6-58. Labeled numbers in the figure identify the steps to
follow. For the procedure on turning up channels over Passive Bridge to
ROADM configurations, see Procedure 6-12, “Turning up channels over a
Passive Bridge to ROADM configuration”.
For details on Passive Bridge applications and engineering rules, see the
6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA.
For special network-level configurations not described in this section, contact

the Ciena account team for additional information.
Step Action
1 Turn up the ROADM network. Refer to the SLAT process description and
flowchart in Chapter 1, “SLAT process overview”.
2 Provision the inventory, OTS, and adjacencies for the passive equipment at
Sites A and 1 (see Figure 6-17 on page 6-58).
Refer to the following procedures in this chapter:
• Procedure 6-1, “Adding passive components”
• Procedure 6-2, “Creating a passive OTS and defining its configuration”
• Procedure 6-3, “Provisioning line adjacencies”
After you complete the provisioning, select your next step.
If you are turning up channels Then go to

in the Site A to Site 2 direction step 3
in the Site 2 to Site A direction step 7
Note: Each direction can be turned up independently.
Turning up channels in the Site A to Site 2 direction

3 Equalize the channels transmitted from Site A to Site 1. Refer to the
4 Equalize the channels received at Site 1 from Site A. Refer to the equalizing


Turning up channels over a Passive Bridge to ROADM—one passive tail configuration
Step Action
Note: The network design output of either the Ciena Network Designer
Site 2.
You have completed turning up the channels from Site A to Site 2.
To turn up the channels from Site 2 to Site A, go to step 7.
Turning up channels in the Site 2 to Site A direction
7 Turn up the channels over the ROADM network between Site 2 and Site 1.
8 At Site 1, stitch channels from the ROADM OTS to the passive OTS. Connect
the ROADM demux outputs to the Passive mux inputs via equalization pads.
9 Equalize the channels transmitted from Site 1 to Site A. Refer to the
10 Equalize the channels received at Site A from Site 1. Refer to the equalizing
You have completed turning up the channels from Site 2 to Site A.
To turn up the channels from Site A to Site 2, go to step 3.
—end—

Figure 6-17
Example of Passive Bridge to ROADM—one passive tail configuration
4 3
9 10
5 8
6 7

323-1851-221
7-1
Wavelength addition and deletion 7-

• “Guidelines for provisioning the Expected far end address (EFEA)
between a CMD and a transponder” on page 7-2
• “Wavelength addition and deletion procedures” on page 7-2

ASE amplified spontaneous emission
CCMD colorless channel mux/demux
CDC ROADM colorless directionless contentionless ROADM (configurations
with Flex WSS C-Band w/OPM 20x1 in the ROADM OTS)
DOC domain optical control
NE network element
Rx receive

7-2 Wavelength addition and deletion

SP shelf processor
TR transmit/receive
Tx transmit
Guidelines for provisioning the Expected far end address (EFEA)

between a CMD and a transponder
Keep in mind the following guidelines:
• Provisioning of the EFEA is required on both the ADJ-TX and ADJ-RX of
the CMD pointing to the transponder.
• Provisioning of the EFEA on the transponder ADJ pointing to the CMD is
optional. If the transponder must be disassociated from the CMD port and
this EFEA is provisioned, you must explicitly remove the EFEA
provisioning from the transponder.
• It is recommended that the provisioning be done on the ADJ-TX first. After
the actual far end address (FEA) is populated, provisioning in any other
location should be done by using the “Use actual Rx address and format”
checkbox in Site Manager. If there is no comms path between the
transponder and the photonic line, the checkbox cannot be used and you
must enter the ADJ information manually.
Wavelength addition and deletion procedures

For submarine applications, refer to 6500 Packet-Optical Platform Submarine

Networking Application Guide, NTRN72AA.
For Flex grid configurations, refer to 6500 Packet-Optical Platform

Configuration - Control Plane, 323-1851-330.

Table 7-1
Procedure
Procedure 7-1, “Adding bidirectional optical channels”
Procedure 7-2, “Adding unidirectional optical channels”
Procedure 7-3, “Deleting bidirectional optical channels”
Procedure 7-4, “Deleting unidirectional optical channels”
Procedure 7-5, “Force deleting optical channels”
Procedure 7-6, “Express deleting optical channels”
Procedure 7-7, “Adding the first optical channel to a Stretched Span”

Procedure 7-1
Adding bidirectional optical channels
Use this procedure to add bidirectional channels that originate or terminate at:
• a SCMD4 at a Thin OADM (TOADM)
• a CMD44 at a ROADM
• a CMD44 at a DIA OADM
• a CCMD12 at a Colorless OADM
• a CCMD12 at a low channel count DIA ROADM
• a CMD44, OMD4, OMDF4, or OMDF8 at a Metro ROADM
• a CCMD8x16 at a CDC ROADM
For instructions on how to add channels using the Control Plane for 6500
photonic systems that have the L0 Control Plane application enabled (that is,
OTS parameters Autoroute set to Disabled and CPS set to Enabled), refer to
the Layer 0 Control Plane Activation and Service Provisioning Overview in
Part 2 of the Control Plane Application Guide - Layer 0 (Photonic),
NTRN71AA.
In this procedure, CMD refers to the OMD4, OMDF4, OMDF8, SCMD4,

CMD44, CCMD8x16, or CCMD12 unless specified otherwise.
Adding optical channels includes the following:

• connecting the service layer DWDM transmitter and receiver to the CMD
port
• creating the logical definition of the channel, that is:
— adding cross connections for a multidomain channel
— provisioning Tx/Rx adjacencies. Follow the “Guidelines for
provisioning the Expected far end address (EFEA) between a CMD
and a transponder” on page 7-2.
If the OTS parameter Autoroute is enabled in the network, the steps to
create the logical definition of the channel must be performed in the order
above.
If Autoroute is disabled in the network, there is no required order for these
steps.
— provisioning the cross connections on the CMD Tx/Rx ports—applies
only if Autoroute is disabled in the network
• repeat the above for other channels
• adding newly defined channels to the system using DOC


• If the OTS parameter Autoroute is disabled in the network:

— All photonic connections must be provisioned at all channel access
sites. CMD Tx and Rx adjacencies can be put in-service once they are
connected to transponders and the system will not automatically
create channels until the appropriate cross connections are
provisioned.
— The Active value, which controls whether the channel is managed by
DOC, is not automatically propagated by the system and is
provisioned on each cross connection.
You can begin adding channels for optimization once the network topology is
created and is visible.
In field deployments, channels are typically added in an incremental fashion

(for example, one at a time or several at a time) to provide transport services
upon demand. In certain scenarios such as field reconfigurations (during a
maintenance window), there may be a requirement to initiate via the craft
interface a channel add of a large number of channels at one time. As a rule
of thumb, if there is a requirement to initiate via the craft interface a channel
add of a large number of channels (>35) at a time, then the operation will
usually need to be performed in two or three steps.
When Autoroute is enabled, DOC supports automatic channel additions.

When the DOC Auto Add Channels parameter is enabled for all optical
domains (different OSIDs) that the channel being added is crossing, adding
this channel to an upstream domain will automatically add it to all downstream
domains. This procedure implements this strategy. If Auto Add Channels is
disabled, channels crossing multiple optical domains must be sequentially
added to each domain being crossed, starting with the upstream domain first.
When Autoroute is disabled, if the cross connections are provisioned with the
Active parameter set to True, the channels will be automatically added in all
domains. If the Active parameter is set to False, you must add the channels in
every domain even if DOC Auto Add is enabled.
It is recommended to perform the first channel add in one direction at a time

(to allow for mis-fibering to be detected through the alarms raised at this stage
and thus to prevent future issues). Once the addition and optimization have
been performed in the first direction, perform the channel add in the opposite
direction using DOC. This procedure recommends this strategy when
performing the first channel add.


Prerequisites
If new 6500 hardware is required to support a new channel at add/drop point,
you must first perform the new hardware installation before performing this
procedure (see Procedure 4-2, “Adding a new CMD44, CMD64, CMD16,
CMD24, CMD96, or BMD2”, Procedure 4-3, “Adding a new OMD4 or OMX”,
Procedure 4-4, “Adding a new SCMD4”, Procedure 4-5, “Adding a new
CCMD12”, or Procedure 6-1, “Adding passive components”).

• be logged into each network element to be traversed by channels to be
added and/or dropped
• ensure service layer circuit packs are already installed and provisioned.
For 6500 service layer circuit pack OTMn provisioning (that is, parameters
such as Tx wavelength, Tx power, Tx mode, Tx SBS dither, Tx AM
Format), refer to the “Editing facility parameters” procedure in Part 1 of
The service layer circuit pack OTMn Tx power and Tx wavelength do not
have to be provisioned if using SPLI Tx power and Tx wavelength
autoprovisioning, which is supported on some service layer circuit packs.
For more information, refer to the “Supporting circuit packs/facilities for
CMD Tx/Rx type discovery, Tx power & Tx wavelength autoprovisioning,
network & site alarm correlation” section in Part 1 of Planning,
NTRN10FG. For SPLI engineering rules, refer to the SPLI section in the
Data Communications Planning and User Guide, 323-1851-101, and the
Photonic Layer Guide, NTRN15DA.
If the service interface does not support SPLI Tx power autoprovisioning
and has an adjustable transmitter, the output power must be set to its
Min./Max./Actual launch power (dBm) of the corresponding CMD Tx
adjacency, unless stated otherwise in the OnePlanner Report/Custom
Link Engineering Report.
If the service interface does not support SPLI Tx wavelength
autoprovisioning, make sure the transmitter wavelength is provisioned and
set to the correct Tx power required.


• review the “Guidelines for provisioning the Expected far end address
(EFEA) between a CMD and a transponder” on page 7-2
• for 40G or 100G services, ensure the transponder connection between the
40G or 100G mate circuit packs has been provisioned. Refer to the
procedure on adding a transponder connection in Configuration -
• ensure that the differential provisioning is already provisioned. Refer to the
“Differential Provisioning” chapter in Part 2 of Configuration - Provisioning
and Operating, 323-1851-310.
CAUTION
DANGER
Risk of injury
CAUTION
CAUTION
Backup and restore after a channel reconfiguration
When any channel reconfiguration (adding or deleting of
channels) is performed, it is recommended that you back up
the provisioning data for all network elements that the channels
traverse. This includes a backup on all shelves in any
consolidated TID site where the channel reconfiguration was
performed. If a restore is performed using an old database
backup (pre-channel reconfiguration), problems may occur on
any channel that was added, dropped, or passed through that
network element. When restoring data on a consolidated TID
site, you must restore the provisioning data for all the shelves
in the consolidated TID site.


Step Action
1 If applicable, ensure the Modulation Class bias (differential provisioning) is

properly set at all DOC OTSs, as per the OnePlanner Report.
Connecting the DWDM transmitter and receiver to the CMD port or the OPS, as applicable to your
configuration
2 For every new channel, connect the DWDM transmitter and the receiver of the
service layer equipment to the correct CMD port at both ends of the selected
channel.
If the configuration uses an OPS, connect the transponder to the OPS and
the OPS to the CCMDs on each of the two OPS paths.
If the EDP/IDP or OnePlanner Report/Custom Link Engineering Report
indicates that padding is required before the receiver, make sure to add the
appropriate fixed pad at the receiver input. Such padding usually requires that
the Rx adjacency parameters be edited, which will be done in later steps.
You must connect a transmitter and a receiver at both ends.
Creating the logical definition of the channel
If Then go to
the channel crosses optical domains (different Optical step 4
System Identifiers [OSID])
otherwise step 6
4 Provision a 2WAY photonic connection at each branch site (site where the
channel changes domains) for the selected channel. Refer to the procedure
on adding a photonic connection in Configuration - Connections
Note that if the OTS parameter Autoroute is disabled, the photonic
connections at domain boundaries can alternatively be provisioned after
provisioning CMD ADJ-TX adjacencies (after step 55).
(Note that for CDC configurations with existing WSS 50 GHz w/OPM C-Band
9x1 [NTK553FA/NTK553FC] and WSS Flex C-Band w/OPM 9x1 [NTK553LA]
circuit packs. when the cross connect is created, regardless of the ACTIVE
flag status, the Tx will tune to the wavelength and the channel will be added
and controlled by the Twin 1x20 WSSOPM controller, but will not be added
onto the line until either a DOC add or ACTIVE flag is set to TRUE. Contact
Ciena for information on deploying CDC configurations with
NTK553FA/NTK553FC/NTK553LA circuit packs.)
5 If the configuration uses an OPS, for the same selected channel provision the
associated 2WAY photonic connection on the second OPS path.


Step Action

If the OTS parameter Then
Autoroute is
enabled At ROADM sites where the channel stays within
the same Photonic domain (that is, both
directions are in the same Photonic domain), the
photonic connections are system-derived. Go to
step 7.
disabled You must provision the photonic connections
within the optical domain.
If the configuration uses an OPS, for the same
selected channel provision the associated
2WAY photonic connection on the second OPS
path.
Then go to step 7.
CMD ADJ-TX provisioning

7 Log in to the site where the selected channel originates and open the
Equipment and Facility provisioning application. Select the CMD to which the
service layer DWDM transmitter for this channel is connected.
If the CMD is Then go to
CCMD12 or CCMD8x16 step 32
not a CCMD12 or CCMD8x16 step 9
Provisioning ADJ-TX and ADJ-RX on CMD other than CCMD12 or CCMD8x16

9 Select “ADJ-TX” from the Facility Type drop down menu.
10 Select the ADJ-TX (with a primary state of OOS-MA) that matches the
wavelength you want to assign to the channel.
The Edit ADJ-TX dialog box opens.


Step Action

If the service interface Then go to
supports SPLI Tx/Rx Type autodiscovery step 13
does not support SPLI Tx/Rx Type autodiscovery step 22
Note: Refer to the “Supporting circuit packs/facilities for CMD Tx/Rx type
discovery, Tx power & Tx wavelength autoprovisioning, network & site alarm
correlation” section in Part 1 of Planning, NTRN10FG, for service interfaces
that support SPLI Tx/Rx type autodiscovery.
Provisioning for a service interface that supports SPLI Tx/Rx Type autodiscovery
13 In the Edit ADJ-TX dialog box, ensure that Paired Rx is set to Yes and Auto
Discovered is set to Auto.
14 If using SPLI to autoprovision the Tx power and Tx wavelength, ensure that
Sync Provisioned is set to True. Ensure SPLI Management is set to True on
transponder facility.
15 Edit the “Expected far end address format” to “TID-SH-SL-PRT”.
16 Enter the “Expected far end address” to be the OTMn facility of the service
layer circuit pack that was connected to the CMD in step 2.
The format must be <TID>-<shelf>-<slot>-<port> of the OTMn facility.
17 If required, provision additional ADJ-TX parameters:
• Customer defined facility identifier
• Circuit Identifier
• Active—This is an ADJ-TX parameter if Autoroute is enabled only. (When
Autoroute is disabled, Active is a cross connection parameter and can be
edited when provisioning the cross connection.)
• Expected Far End PEC
18 Click OK in the Edit ADJ-TX dialog box.
19 Ensure the CMD ADJ-TX facility primary state becomes “IS”.
20 If the OnePlanner Report specifies values for the Launch Power Overwrite
parameters that are different from the default values corresponding to the
transmitter type, you must edit the following CMD ADJ-TX fields:
• Min. Launch Power (dBm)
• Max. Launch Power (dBm)
• Actual Tx Power (dBm)


Step Action
21 If the OnePlanner Report specifies values for the Receive Power Overwrite
receiver type, you must edit the following CMD ADJ-RX fields:
• Sensitivity level (dBm)
• Overload level (dBm)
• Nominal level (dBm)
Go to step 28.
Provisioning for a service interface that does not support SPLI Tx/Rx Type autodiscovery
Discovered is set to Manual.
23 Select the Transmitter Type as indicated in the EDP/IDP.
The Transmitter Type should match the service layer equipment (as Colored)
or be set to “Foreign” or “Foreign Coherent” for other types of transmitters.
a. If the OnePlanner Report specifies values for the Launch Power
Overwrite parameters that are different from the default values
corresponding to the transmitter type, you must edit the following CMD
ADJ-TX fields:
— Minimum launch power (dBm)
— Maximum launch power (dBm)
— Actual Tx Power (dBm)
b. If you selected the “Foreign” transmitter type, you can use the default
values or edit the following CMD ADJ-TX fields:
— Modulation Class (Custom1 to Custom6)
— Tx Minimum Spectral Width (GHz)
— Tx Signal Bandwidth 3dB (GHz)—cannot be less than 12.5 GHz
— Tx Signal Bandwidth 10dB (GHz)
— Min. Launch Power (dBm)
— Max. Launch Power (dBm)


Step Action
c. If you selected the “Foreign Coherent” transmitter type, you can use the
default values or edit the following CMD ADJ-TX fields:
You must edit the ‘Tx Signal Bandwidth 3dB (GHz)’ and ‘Tx Signal
Bandwidth 10dB (GHz)’ values to match the spectral characteristics of
the actual signal. Refer to the Photonic Layer Guide, NTRN15DA, for
information on setting these values.
24 If required, provision other ADJ-TX parameters:
• Expected far end address format
• Expected far end address
26 Ensure the CMD ADJ-TX primary state becomes “IS”.
27 If the “Foreign” or “Foreign Coherent” transmitter type is selected or if the
OnePlanner Report specifies values for the Receive Power Overwrite
If Then go to
the channel originates through a DIA step 29
otherwise step 30
autoroute is disabled For local add/drop, provision a
2WAY photonic connection from
the CMD Tx port to LIM port 5,
and from LIM port 8 to the CMD
Rx port.


Step Action
29 Provision a 2WAY photonic connection between the DIA CMD44 Ch In port

and the Backbone amplifier Line B Out port for the selected channel. Refer to
30 If SPLI is not being used or a “Foreign” or “Foreign Coherent” transmitter type
has been selected, provision the wavelength and the Tx Power at the
transponder that is connected to the CMD port.
The Tx power default value for the “Foreign Coherent” type is -5 dBm.
Refer to the OnePlanner Report for more details on the expected Tx powers.
31 Repeat from step 7 for the site where the selected channel is terminating.
Go to step 55.
Provisioning ADJ-TX and ADJ-RX on a CCMD12 or CCMD8x16
32 Select ADJ-TX from the Facility Type drop down menu.
33 Select the ADJ-TX for the channel you want to add.
34 Click Edit.
Discovered is set to Auto.
37 Ensure that Sync Provisioned is set to True.
layer circuit pack.


Step Action

ADJ-TX fields:
b. If the OnePlanner Report specifies values for the Receive Power
corresponding to the receiver type, you must edit the following CMD
ADJ-RX fields:
— Sensitivity level (dBm)
— Overload level (dBm)
— Nominal level (dBm)
Go to step 52.


Step Action
44 Select the transmitter type as indicated in the EDP/IDP. It should match the
service layer equipment (as Colorless) or be set to “Foreign” or “Foreign
Coherent” for other types of transmitters.
ADJ-TX fields:
— Min. launch power (dBm)
— Max. launch power (dBm)


Step Action

46 Click Apply, then OK in the Edit ADJ-TX dialog box.
47 Record the “Target Input Power at CMD (dBm)” for the ADJ-TX. You will have
to provision the transponder Tx power to this value.
49 If the “Foreign” or “Foreign Coherent” transmitter type is selected or if the
OnePlanner Report specifies values for the Receive Power Overwrite
50 If SPLI is not being used or a “Foreign” or “Foreign Coherent” transmitter type
has been selected, provision at the transponder the wavelength and the Tx
Power (recorded in step 47).
52 Provision a 2WAY photonic connection between the CCMD12 or CCMD8x16
Ch In port and the Backbone amplifier Line B Out for the selected channel.
Refer to the procedure on adding a photonic connection in Configuration -
53 For SPLI supported transponders, perform the optical loopback test to verify
the fiber connectivity. Refer to the “Performing optical loopback testing”
323-1851-310.
This step is optional.
54 If the configuration includes an OPS, make sure that the Tx and Rx
adjacencies are provisioned at the OPS on both OPS paths. See
Procedure 3-2, “Provisioning adjacencies”.
55 Repeat from step 3 for every new channel. If all the required channels have
been provisioned, go to “Checking new channels in DOC” and step 56.


Step Action
Checking new channels in DOC

Note: If your configuration includes SRA and XLA equipment, an Automatic
Shutoff Disabled alarm is raised temporarily when adding the first channels
or running the manual power audit. The alarm is raised because DOC
performs a power audit, during which it disables the automatic laser shutoff
feature on the XLA, so that the XLA can generate amplifier noise (ASE) for
the SRA calibration. At the end of the power audit, DOC re-enables the
automatic laser shutoff feature and the alarm clears.
56 Log in to the site(s) where the two DOC entities reside (one for each
direction), in the domain where the channels ingress the optical network (that
is, where the service layer DWDM transmitter is connected to the CMD).
Perform the following:
• In the Configuration -> Photonic Services -> Domain Optical
Controller (DOC), click on either the Start Monitoring or the Refresh
button.
• Select the DOC entity that is to control the channels just provisioned.
Ensure that the newly created channels appear under DOC control. They
should have a Channel Condition as Inactive and DOC Trail Status of
COMPLETE.
• If this is not the case, verify that you have correctly completed steps from
step 3 for the missing channels.
57 If Autoroute is enabled, go to step 58 to review the DOC settings. Otherwise,

go to step 64.


Step Action
Reviewing DOC settings

58 Open the DOC Settings tab for each optical domain being crossed by the
channel(s) being added.
If you are adding Then go to
branched channel(s) (channels crossing different step 60
domains)
otherwise step 64
60 In the DOC settings tab, make sure the Auto add channels is Enabled. If not,
then do the following:
• In the Settings tab, click on Edit button.
• In the Edit dialog box, set ''Auto add channels'' to Enabled.
• Click on the OK button to confirm your selection.
61 Repeat step 60 for all Photonic domains crossed by channel(s) being added.
62 Make sure all Photonic domains crossed by channel(s) being added are set
to the same automation mode. Refer to the “Editing the DOC Settings”
323-1851-310 for details on how to edit DOC settings.
63 Repeat step 58 to step 62 in the opposite direction.
Setting OTDR baselines and calibrating SRA circuit packs
64 Before adding the first channels on the domain, identify whether SRA or
ESAM circuit packs are present in the domain. If there are SRA or ESAM
circuit packs in the domain:
• Run a Long (40000ns/120000m) OTDR trace and a Short
(1000ns/20000m) OTDR trace manually.
• Set the traces as baselines.
For OTDR procedures, see the chapter on OTDR trace in Part 2 of

Note that the Optical Time Domain Reflectometer requires at least 20 km of
short fiber may fail due to loss or reflection.


Step Action
65 If SRA circuit packs are present in the domain:

• It is recommended to perform a manual power audit before adding
channels (see the manual power audit procedure in Part 2 of
Configuration - Provisioning and Operating, 323-1851-310).
The manual power audit will validate and calibrate all SRA circuit packs
before adding a channel in the system. A channel must be provisioned
through every SRA circuit pack in the domain for the power audit to
function properly.
If the manual power audit is not performed, make sure there is at least
one inactive channel provisioned that goes through each SRA in the
domain.
Note: If there are any channels managed in the domain, the Manual Power
Audit cannot be performed at a later time.
• Verify that all SRA circuit packs have cleared the Calibration Required
alarm and that the Calibration Flag parameter in the Raman facility is set
to either Calibration Not required (for spans greater than 35 dB) or
Calibrated (for spans less than 35 dB). Perform for every domain
independently if the channel traverses multiple domains.
66 Repeat step 64 and step 65 in the opposite direction.
Adding newly defined channels to DOC
67 From the DOC application of the domain where the channels ingress the
optical network, multi select all newly created channels and click on
Pre-check.
If the pre-check fails, investigate the problem using the DOC logs and take the
appropriate actions.
Note: Pre-checks may fail on a channel in a section without managed
channels. In this case, try to add the channel anyway and it will likely pass.
68 Select all the new channels and click on the Add button.
Note: If the added channel is declared to be Optimized and a receiver alarm
is raised, verify the connectivity, padding and receiver adjacency provisioning
against the network design.


Step Action
69 Repeat step 67 and step 68 in the opposite direction once the new channels
have been added and optimized in the first direction. (After the first channel
add, you can perform step 67 and step 68 on both directions simultaneously.)
When Autoroute is enabled, if the channels being added span multiple
domains, because Auto Add Channels is enabled in the DOC settings
throughout the network, addition of the channel to the upstream domain will
trigger the addition of the channel in all domains, starting from the upstream
domain and ending with the domain where the channel is received.
Active parameter set to True, the channels will be added automatically in all
domains. If the Active parameter is set to False, you must add the channels
in every domain even if DOC Auto Add is enabled. To add the channels, you
can either use the DOC application or edit the cross connection Active
parameter value to True.
If “Partially Added” or “Partially Deleted” DOC status appears when
performing the Add/Delete channels procedures, refer to the “DOC Action
Failed: Add” and “DOC Action Failed: Delete” alarm clearing procedures in
For Raman spans over 35 dB, if the “Target Unachievable” alarm is raised on
Raman facilities, refer to the alarm clearing procedure in Part 2 of Fault
If “Inactive:waiting for power” channel status appears when performing the
Add procedures, check the transmitter input power, and follow the alarm
clearing procedures to clear any Circuit Pack Missing, LOS, High Fiber Loss,
Adjacency Far End Not Discovered, Adjacency Discovery Unreliable, and
Adjacency Mismatch alarms at the site.
Once the channels are added, the Overall Status field displays a value of
Optimal. The Channel Condition and End-to-End Condition for the added
channels displays a value of Optimized.
—end—

Procedure 7-2
Adding unidirectional optical channels
Use this procedure to add unidirectional channels that originate or terminate
at:
For instructions on how to add channels using the Control Plane for 6500
photonic systems that have the L0 Control Plane application enabled (that is,
OTS parameters Autoroute set to Disabled and CPS set to Enabled), refer to
the Layer 0 Control Plane Activation and Service Provisioning Overview in
Part 2 of the Control Plane Application Guide - Layer 0 (Photonic),
NTRN71AA.
In this procedure, CMD refers to the OMD4, OMDF4, OMDF8, SCMD4, or

CMD44 unless specified otherwise.
Adding optical channels includes the following:

• connecting the service layer DWDM transmitter and receiver to the CMD
port
• creating the logical definition of the channel, that is:
— adding cross connections for a multidomain channel
— provisioning Tx/Rx adjacencies. Follow the “Guidelines for
provisioning the Expected far end address (EFEA) between a CMD
and a transponder” on page 7-2.
If the OTS parameter Autoroute is enabled in the network, the steps to

create the logical definition of the channel must be performed in the order
above.
If Autoroute is disabled in the network, there is no required order for these
steps.
— provisioning the cross connections on the CMD Tx/Rx ports—applies
only if Autoroute is disabled in the network
• repeat the above for other channels
• adding newly defined channels to the system using DOC


If the OTS parameter Autoroute is disabled in the network:

• All photonic connections must be provisioned at all channel access sites.
CMD Tx and Rx adjacencies can be put in-service once they are
connected to transponders and the system will not automatically create
channels until the appropriate connections are provisioned.
• The Active value, which controls whether the channel is managed by
DOC. is not automatically propagated by the system and is provisioned on
each connection.
You can begin adding channels for optimization once the network topology is
created and is visible.
In field deployments, channels are typically added in an incremental fashion

interface a channel add of a large number of channels at one time. As a rule
add of a large number of channels (>35) at a time, then the operation will
usually need to be performed in two or three steps.
When Autoroute is enabled, DOC supports automatic channel additions.

When the DOC Auto Add Channels parameter is enabled for all optical
domains (different Optical System Identifiers) that the channel being added is
crossing, adding this channel to an upstream domain will automatically add it
to all downstream domains. This procedure implements this strategy. If Auto
Add Channels is disabled, channels crossing multiple optical domains must
be sequentially added to each domain being crossed, starting with the
upstream domain first.
Active parameter set to True, the channels will be automatically added in all
domains. If the Active parameter is set to False, you must add the channels in
every domain even if DOC Auto Add is enabled.
Optical Drop and Continue (OD&C) channels are uni-directional and can be
dropped at any intermediate site between far-end Rx target and Tx source.


ATTENTION
If the channel is unidirectional, the TX and RX adjacencies at both end points
must be un-paired.
In Optical Drop & Continue (OD&C), the RX adjacency facility at intermediate

drop points must be un-paired.
Prerequisites
If new 6500 hardware is required to support a new channel at add/drop point,
you must first perform the new hardware installation before performing this
procedure (see Procedure 4-2, “Adding a new CMD44, CMD64, CMD16,
CMD24, CMD96, or BMD2”, Procedure 4-3, “Adding a new OMD4 or OMX”,
Procedure 4-4, “Adding a new SCMD4”, Procedure 4-5, “Adding a new
CCMD12”, or Procedure 6-1, “Adding passive components”).

added and/or dropped
• ensure service layer circuit packs are already installed and provisioned.
For 6500 service layer circuit pack OTMn provisioning (that is, parameters
such as Tx wavelength, Tx power, Tx mode, Tx SBS dither, Tx AM
Format), refer to the “Editing facility parameters” procedure in Part 1 of
The service layer circuit pack OTMn Tx power and Tx wavelength do not
have to be provisioned if using SPLI Tx power and Tx wavelength
autoprovisioning, which is supported on some service layer circuit packs.
For more information, refer to the “Supporting circuit packs/facilities for
CMD Tx/Rx type discovery, Tx power & Tx wavelength autoprovisioning,
network & site alarm correlation” section in Part 1 of Planning,
NTRN10FG. For SPLI engineering rules, refer to the SPLI section in the
Data Communications Planning and User Guide, 323-1851-101, and the
Photonic Layer Guide, NTRN15DA.
If the service interface does not support SPLI Tx power autoprovisioning
and has an adjustable transmitter, the output power must be set to its
Min./Max./Actual launch power (dBm) of the corresponding CMD Tx
adjacency, unless stated otherwise in the OnePlanner Report/Custom
Link Engineering Report.


Make sure the transmitter wavelength is provisioned and set to the correct
Tx power required.
• for 40G or 100G services, ensure the transponder connection between the
40G or 100G mate circuit packs has been provisioned. Refer to the
procedure on adding a transponder connection in Configuration -
• ensure that the differential provisioning is already provisioned. Refer to the
“Differential Provisioning” chapter in Part 1 of Configuration - Provisioning
and Operating, 323-1851-310.
CAUTION
DANGER
Risk of injury
CAUTION
CAUTION
Backup and restore after a channel reconfiguration
When any channel reconfiguration (adding or deleting of
channels) is performed, it is recommended that you back up
the provisioning data for all network elements that the channels
traverse. This includes a backup on all shelves in any
consolidated TID site where the channel reconfiguration was
performed. If a restore is performed using an old database
backup (pre-channel reconfiguration), problems may occur on
any channel that was added, dropped, or passed through that
network element. When restoring data on a consolidated TID
site, you must restore the provisioning data for all the shelves
in the consolidated TID site.


Step Action
1 If applicable, ensure the Modulation Class bias (differential provisioning) is

properly set at all DOC OTSs, as per the OnePlanner Report.
Connecting the DWDM transmitter and receiver to the CMD port or the OPS, as applicable to your
configuration
2 For every new channel, connect the DWDM transmitter and the receiver of the
service layer equipment to the correct CMD port at both ends of the selected
channel.
If the configuration uses an OPS, connect the transponder to the OPS and
the OPS to the CCMDs on each of the two OPS paths.
If the EDP/IDP or OnePlanner Report/Custom Link Engineering Report
indicates that padding is required before the receiver, make sure to add the
appropriate fixed pad at the receiver input. Such padding will usually require
that the Rx adjacency parameters be edited. This will be done in later steps.
You must connect a transmitter at one end and a receiver at the other end.
Creating the logical definition of the channel
If Then go to
the channel crosses optical domains (different Optical step 4
System Identifiers [OSID])
the channel does not cross optical domains step 6
4 Provision a 1WAY photonic connection at each branch site (site where the
channel changes domains) for the selected channel. Refer to the procedure
on adding a photonic connection in Configuration - Connections
Note that if the OTS parameter Autoroute is disabled, the photonic
connections at domain boundaries can alternatively be provisioned after
provisioning CMD ADJ-TX adjacencies (after step 43).
5 If the configuration uses an OPS, for the same selected channel provision the
associated 1WAY photonic connection on the second OPS path.


Step Action

If the OTS parameter Then
Autoroute is
enabled At ROADM sites where the channel stays within
the same Photonic domain (that is, both
directions are in the same Photonic domain), the
photonic connections are system-derived. Go to
step 7.
disabled You must provision the photonic connections
within the optical domain.
If the configuration uses an OPS, for the same
selected channel provision the associated
1WAY photonic connection on the second OPS
path.
Then go to step 7.
CMD ADJ-TX provisioning

7 Log in to the site where the selected channel originates and open the
Equipment and Facility provisioning application. Select the CMD to which the
service layer DWDM transmitter for this channel is connected.
8 Select “ADJ-TX” from the Facility Type drop down menu.
9 Select the ADJ-TX (with a primary state of OOS-MA) that matches the
wavelength you want to assign to the channel.


Step Action
12 In the Edit ADJ-TX dialog box, set Paired Rx to No, Auto Discovered to Auto,
and Sync Provisioned to True for the ADJ-TX facility.
13 If using SPLI to autoprovision the Tx power and Tx wavelength, ensure that
Sync Provisioned is set to True. Ensure SPLI Management is set to True on
transponder facility.
layer circuit pack that was connected to the CMD in step 2.
18 Ensure the CMD ADJ-TX facility primary state becomes “IS”.
19 If the OnePlanner Report specifies values for the Launch Power Overwrite
transmitter type, you must edit the following CMD ADJ-TX fields:
• Min. Launch Power (dBm)
• Max. Launch Power (dBm)
• Actual Tx Power (dBm)
20 If the channel is an optical drop and continue (OD&C) channel, set the
ADJ-TX routing rule to the Longest path using the TL-1 command:
ED-ADJ-TX::ADJ-<CMD shelf#>-<CMD slot#>-<CMD
port#>:CTAG:::ROUTINGRULE=LONGESTPATH;
Go to step 26.


Step Action
22 Select the Transmitter Type as indicated in the EDP/IDP.
The Transmitter Type should match the service layer equipment (as Colored)
or be set to “Foreign” or “Foreign Coherent” for other types of transmitters.
ADJ-TX fields:
— Min. launch power (dBm)
— Max. launch power (dBm)


Step Action

If Then go to
the channel originates step 27
through a DIA
otherwise step 28
autoroute is disabled For local add/drop, provision a 2WAY photonic
connection from the CMD Tx port to LIM port 5,
and from LIM port 8 to the CMD Rx port.
27 Provision a 1WAY photonic connection between the DIA CMD44 Ch In port

CMD ADJ-RX provisioning
28 Log in to the site where the selected channel terminates and open the
Equipment and Facility provisioning application. For OD&C applications,
select the last drop site.
29 Select the CMD to which the service layer DWDM receiver for this channel is
connected to.
30 Select “ADJ-RX” from the Facility Type drop down menu.
31 Select the ADJ-RX (primary state OOS-MA) that matches the wavelength you
want to assign to the channel and click on the Edit button.
The Edit ADJ-RX dialog box opens.
32 In the Edit ADJ-RX dialog box, set Paired Tx to No, Auto Discovered to
Manual, and Sync Provisioned to False for the ADJ-RX facility.


Step Action
33 Select the type of receiver as indicated in the EDP/IDP: it should match the
service layer equipment or be set to “Foreign” for other types of receivers.
If you select a foreign receiver, you must enter the following parameters
manually:
34 You can also provision other ADJ-RX parameters:
35 Click OK in the Edit ADJ-RX dialog box.
36 Ensure the CMD ADJ RX facility primary state becomes “IS”.
37 If the OnePlanner Report specifies values for the Receive Power Overwrite
38 If the configuration includes an OPS, make sure that the Tx and Rx
adjacencies are provisioned at the OPS on both OPS paths. See
Procedure 3-2, “Provisioning adjacencies”.
If Then go to
the channel terminates through a DIA step 40
otherwise step 41
autoroute is disabled (drop) For local add/drop,
provision a 2WAY
photonic
connection from
the CMD Tx port to
LIM port 5, and
from LIM port 8 to
the CMD Rx port.


Step Action
40 Provision a 1WAY photonic connection between the Backbone amplifier Line

A In port to the DIA CMD44 Ch Out port for the selected channel. Refer to the
procedure on adding a photonic connection in Configuration - Connections
optical drop and continue step 42
otherwise step 43
42 Repeat step 28 to step 39 to add intermediate drop Rx adjacencies for all

optical drop and continue points, if applicable.
43 Repeat from step 3 for every new channel.
Checking new channels in DOC
Note: If your configuration includes SRA and XLA equipment, an Automatic
Shutoff Disabled alarm is raised temporarily when adding the first channels.
The alarm is raised because DOC performs a power audit, during which it
disables the automatic laser shutoff feature on the XLA, so that the XLA can
generate amplifier noise (ASE) for the SRA calibration. At the end of the
power audit, DOC re-enables the automatic laser shutoff feature and the
alarm clears.
44 Log in to the site where the DOC entity resides, in the domain where the
channels ingress the optical network (that is, where the service layer DWDM
transmitter is connected to the CMD). Perform the following:
button.
• Select the DOC entity that is to control the channels just provisioned.
Ensure that the newly created channels appear under DOC control. They
should have a Channel Condition as Inactive and DOC Trail Status of
COMPLETE.
• If this is not the case, verify that you have correctly completed from step
3 for the missing channels.
45 If Autoroute enabled, go to step 46 to review the DOC settings. Otherwise, go
to step 51.
Reviewing DOC settings
46 Open the DOC Settings tab for each optical domain being crossed by the
channel(s) being added.


Step Action

branched channel(s) (channels crossing different step 48
domains)
otherwise step 51
48 In the DOC settings tab, make sure the Auto add channels is Enabled. If not,
• In the Edit dialog box, set ''Auto add channels'' to Enabled
49 Repeat step 48 for all Photonic domains crossed by channel(s) being added.
50 Make sure all Photonic domains crossed by channel(s) being added are set
Setting OTDR baselines and calibrating SRA circuit packs
51 Before adding the first channels on the domain, identify whether SRA or
ESAM circuit packs are present in the domain. If there are SRA or ESAM
circuit packs in the domain:
• Run a Long (40000ns/120000m) OTDR trace and a Short
(1000ns/20000m) OTDR trace manually.
• Set the traces as baselines.
For OTDR procedures, see the chapter on OTDR trace in Part 2 of

Note that the Optical Time Domain Reflectometer requires at least 20 km of
short fiber may fail due to loss or reflection.


Step Action
52 If SRA circuit packs are present in the domain:

• It is recommended to perform a manual power audit before adding
channels (see the manual power audit procedure in Part 2 of
Configuration - Provisioning and Operating, 323-1851-310).
The manual power audit will validate and calibrate all SRA circuit packs
before adding a channel in the system. A channel must be provisioned
through every SRA circuit pack in the domain for the power audit to
function properly.
If the manual power audit is not performed, make sure there is at least
one inactive channel provisioned that goes through each SRA in the
domain.
Note: If there are any channels managed in the domain, the Manual Power
Audit cannot be performed at a later time.
• Verify that all SRA circuit packs have cleared the Calibration Required
alarm and that the Calibration Flag parameter in the Raman facility is set
to either Calibration Not required (for spans greater than 35 dB) or
Calibrated (for spans less than 35 dB). Perform for every domain
independently if the channel traverses multiple domains.
53 Repeat step 51 and step 52 in the opposite direction.
Adding newly defined channels to DOC
54 From the DOC application of the domain where the channels ingress the
optical network, multi select all newly created channels and click on
Pre-check.
If the pre-check fails, investigate the problem using the DOC logs and take the
appropriate actions.
Note: Pre-checks may fail on a channel in a section without managed
channels. In this case, try to add the channel anyway and it will likely pass.


Step Action
55 Select all the new channels and click on the Add button.
Note: If the added channel is declared to be Optimized and a receiver alarm
is raised, verify the connectivity, padding and receiver adjacency provisioning
against the network design.
When Autoroute is enabled, if the channels being added span multiple
domains, because Auto Add Channels is enabled in the DOC settings
throughout the network, addition of the channel to the upstream domain will
trigger the addition of the channel in all domains, starting from the upstream
domain and ending with the domain where the channel is received.
Active parameter set to True, the channels will be added automatically in all
domains. If the Active parameter is set to False, you must add the channels
in every domain even if DOC Auto Add is enabled. To add the channels, you
can either use the DOC application or edit the cross connection Active
parameter value to True.
To guarantee that the addition of OD&C channels is non-service affecting
(NSA), OD&C channels must be added to DOC one at a time.
If “Partially Added” or “Partially Deleted” DOC status appears when
performing the Add/Delete channels procedures, refer to the “DOC Action
Failed: Add” and “DOC Action Failed: Delete” alarm clearing procedures in
For Raman spans over 35 dB, if the “Target Unachievable” alarm is raised on
Raman facilities, refer to the alarm clearing procedure in Part 2 of Fault
Once the channels are added, the Overall Status field displays a value of
Optimal. The Channel Condition and End-to-End Condition for the added
channels displays a value of Optimized.
—end—

Procedure 7-3
Deleting bidirectional optical channels
Use this procedure to delete bidirectional channels that originate or terminate
at:
• a CCMD12 at a Colorless OADM
• a CCMD12 at a low channel count DIA ROADM
• a CCMD8x16 at a CDC ROADM
In this procedure, CMD refers to the OMD4, OMDF4, OMDF8, SCMD4,

CMD44, CCMD8x16, or CCMD12 unless specified otherwise.
This procedure does not apply to channels managed by Layer 0 Control

Plane. To delete channels managed by Layer 0 Control Plane, you must delete
the respective Control Plane sub-network connection. Refer to Configuration
- Control Plane, 323-1851-330. (For detailed information on Control Plane
concepts, applications, and engineering rules, refer to 6500 Packet-Optical
Platform Control Plane Application Guide, NTRN71AA.)
In field deployments, channels are typically deleted in an incremental fashion

interface a channel delete of a large number of channels at one time. As a rule
delete of a large number of channels (>35) at a time, then the operation will
usually have to be performed in two or three steps.
You can delete any number of channels in the same operation; however, DOC
will sequence the deletion such that channels will be deleted in limited-size
bundles during the same operation to guarantee non-service affecting (NSA)
operation.
When Autoroute is enabled, DOC supports automatic channel deletions.

When the DOC auto delete channels parameter is enabled for all optical
domains (different Optical System Identifiers) that a channel is crossing, then
deleting this channel from an upstream domain will automatically delete it from
all downstream domains. This procedure implements this strategy.


Auto Delete parameter set to True, the cross connections will be automatically
deleted from all optical domains when the channel is deleted from DOC. If the
connection Auto Delete parameter is set to False, you must delete the cross
connections from each node, even if DOC Auto Delete is enabled.
Note: For TOADM configurations, line amplifiers connected to SCMD4s

may not go into shutoff mode when all channels are deleted due to the
limited range of the internal VOAs coupled with the fact that the
transponders stay tuned and outputting power in this colored
configuration. To avoid this, disconnect all transponders connected to the
affected SCMD4s after the last channel is deleted.
Prerequisites
deleted
• do not disconnect any service layer transmitters from the system
CAUTION
DANGER
Risk of injury
CAUTION


Step Action
Deleting channels
If the OTS parameter Autoroute Then
is
enabled go to step 2
disabled and the channel(s) you go to step 7
want to delete are not managed
by Layer 0 Control Plane
disabled and the channel(s) you This procedure does not apply to
want to delete are managed by channels managed by Layer 0 Control
Layer 0 Control Plane Plane. To delete channels managed by
Layer 0 Control Plane, you must delete
the respective Control Plane
sub-network connection. Refer to
Configuration - Control Plane,
323-1851-330. (For detailed
information on Control Plane concepts,
applications, and engineering rules,
refer to 6500 Packet-Optical Platform
Control Plane Application Guide,
NTRN71AA.)

If you are deleting Then go to
branched channel(s) (channels crossing different domains) step 3
otherwise step 8
3 Log in to the site where the DOC entity resides for each optical domain being
crossed by the channel(s) being deleted and open the Domain Optical
Controller (DOC) application.
4 In the DOC settings tab, make sure “Auto delete channels” is Enabled. If not,
• In the Edit dialog box, set ''Auto delete channels'' to Enabled.
5 Repeat step 4 for all Photonic domains crossed by channel(s) being deleted.


Step Action
6 Make sure all Photonic domains crossed by channel(s) being deleted are set
Then go to step 8.
7 If Autoroute is disabled, log into each network element along the channel path
and use the Photonic Connections application to set the Active parameter of
the cross connection to False and the Auto Delete parameter to True.
button.
• Select the DOC entity that is controlling the channel to be deleted.
• Select the channels to be deleted.
• Click on the Delete button.
• Click on the Yes button in the confirmation dialog that appears.
If the delete command fails or if the “Partially Deleted” DOC status appears
when performing the Delete channels procedure, refer to the “DOC
Command Failed: Delete” alarm clearing procedure in Part 1 of Fault
Once the channels are deleted, the Overall Status field displays a value of
Optimal, and the value displayed in the Channel Condition and in the
End-to-End Condition columns for each remaining channel entity is
Optimized. The Channel Condition and the End-to-End Condition of the
deleted channels is Inactive.
When Autoroute is enabled, if the DOC Auto delete channels parameter is
enabled in all optical domains (different Optical System Identifiers) that the
selected channel is crossing, then deleting this channel from an upstream
domain will automatically delete it from all downstream domains, starting with
the receiving domain and going back towards the source domain.
Auto Delete parameter set to True (step 7), the cross connections will be
automatically deleted from all optical domains when the channel is deleted
from DOC. (If the connection Auto Delete parameter is set to False, you must
delete the cross connections from each node, even if DOC Auto Delete is
enabled.)
9 Repeat step 8 for the other direction. You can perform step 8 on both
directions simultaneously.


Step Action
10 For the selected channel, delete the 2WAY photonic connection at each
branch site (site where the channel changes domain) if the deleted channel
crosses optical domains. Refer to the “Deleting Photonic connections”
procedure in Configuration - Connections Management, 323-1851-320.
At ROADM sites where the channel stays within the same Photonic domain
(that is, both directions are in the same Photonic domain), if Autoroute is
enabled, the photonic connections are system-derived and will be
auto-deleted when the CMD ADJ-TX is deprovisioned.
11 If the configuration uses an OPS, for the same deleted channel delete the
associated photonic connection on the second OPS path.
Deprovisioning the CMD ADJ-TX/ADJ-RX
12 Log in to the site where the selected channel originates.
If the channel you are deleting Then go to
originates through a DIA step 14
otherwise step 15
14 Delete the 2WAY photonic connection between the DIA CMD44 Ch In port
the “Deleting Photonic connections” procedure in Configuration -
Connections Management, 323-1851-320. If autoroute is disabled, delete the
photonic connection for the CMD to LIM manually.
originates through a Colorless OADM step 16
otherwise step 17
16 Delete the 2WAY photonic connection between the CCMD12 Ch In port and
the Backbone amplifier Line B Out port for the selected channel. Refer to the
“Deleting Photonic connections” procedure in Configuration - Connections
17 Open the Equipment and Facility Provisioning application. Select the CMD
equipment corresponding to the channel to be deleted.
18 Select “ADJ-TX” from the Facility Type drop down list.
19 Select the ADJ-TX that corresponds to the wavelength to be deleted and click
on the Edit button.


Step Action

If Then go to
you are using SPLI step 21
otherwise step 22
21 In the Edit ADJ-TX dialog box, change the Expected far end address to Null.
Go to step 23.
22 In the Edit ADJ-TX dialog box, change the Transmitter type to Unknown.
24 Click OK in the confirmation message if it appears.
26 Repeat from step 10 for each deleted channel.
After you delete a channel, some ports on photonic circuit packs that
originally had light may no longer have light, and will raise a Loss of signal
alarm. This is an expected behavior. To clear the alarm, change the
secondary state of the affected facility to AINS.
27 If the transponder must be disassociated from the CMD port, remove the
EFEA provisioning on the transponder ADJ pointing to the CMD, if present:
• In the Equipment and Facility Provisioning application, select the
transponder equipment.
• Select “ADJ” from the Facility Type drop down list.
• In the Edit ADJ dialog box, remove the EFEA provisioning.
• Click OK in the Edit ADJ dialog box.
• Click OK in the confirmation message if it appears.
Note: For TOADM configurations, line amplifiers connected to SCMD4s may
not go into shutoff mode when all channels are deleted due to the limited
range of the internal VOAs coupled with the fact that the transponders stay
tuned and outputting power in this colored configuration. To avoid this,
disconnect all transponders connected to the affected SCMD4s after the last
channel is deleted.
—end—

Procedure 7-4
Deleting unidirectional optical channels
Use this procedure to delete unidirectional channels that originate or
terminate at:
In this procedure, CMD refers to the OMD4, OMDF4, OMDF8, SCMD4, or

CMD44 unless specified otherwise.
In field deployments, channels are typically deleted in an incremental fashion

interface a channel delete of a large number of channels at one time. As a rule
delete of a large number of channels (>35) at a time, then the operation will
usually have to be performed in two or three steps.
You can delete any number of channels in the same operation; however, DOC
will sequence the deletion such that channels will be deleted in limited-size
bundles during the same operation to guarantee non-service affecting (NSA)
operation.
When Autoroute is enabled, DOC supports automatic channel deletions.

When the DOC auto delete channels parameter is enabled for all optical
domains (different Optical System Identifiers) that a channel is crossing, then
deleting this channel from an upstream domain will automatically delete it from
all downstream domains. This procedure implements this strategy.
Auto Delete parameter set to True, the cross connections will be automatically
deleted from all optical domains when the channel is deleted from DOC. If the
connection Auto Delete parameter is set to False, you must delete the cross
connections from each node, even if DOC Auto Delete is enabled.
Note: For TOADM configurations, line amplifiers connected to SCMD4s
may not go into shutoff mode when all channels are deleted due to the
limited range of the internal VOAs coupled with the fact that the
transponders stay tuned and outputting power in this colored
configuration. To avoid this, disconnect all transponders connected to the
affected SCMD4s after the last channel is deleted.


Prerequisites
deleted
• do not disconnect any service layer transmitters from the system
CAUTION
DANGER
Risk of injury
CAUTION
Step Action

If the OTS parameter Autoroute is Then go to
enabled step 2
disabled step 7
Deleting channels
2 Log in to the site where the DOC entity resides for each optical domain being
crossed by the channel(s) being deleted and open the Domain Optical
Controller (DOC) application.


Step Action

If you are deleting Then go to
branched channel(s) (channels crossing different domains) step 4
otherwise step 8
4 In the DOC settings tab, make sure the Auto delete channels is Enabled. If
not, then do the following:
• In the Edit dialog box, set ''Auto delete channels'' to Enabled
5 Repeat step 4 for all Photonic domains crossed by channel(s) being deleted.
6 Make sure all Photonic domains crossed by channel(s) being deleted are set
Then go to step 8.
7 If Autoroute is disabled, log into each network element along the channel path
and use the Photonic Connections application to set the Active parameter of
the cross connection to False and the Auto Delete parameter to True.
button
• Select the DOC entity that is controlling the channel to be deleted.
• Select the channels to be deleted.
• Click on the Delete button.
• Click on the Yes button in the confirmation dialog that appears.
If the delete command fails or if the “Partially Deleted” DOC status appears
when performing the Delete channels procedure, refer to “DOC Command
Failed: Delete” alarm clearing procedure in Part 1 of Fault Management -
Alarm Clearing, 323-1851-543.
After the channels are deleted, the Overall Status field displays a value of
Optimal, and the value displayed in the Channel Condition and in the
End-to-End Condition columns for each remaining channel entity is
Optimized. The Channel Condition and the End-to-End Condition of the
deleted channels is Inactive.


Step Action
When Autoroute is enabled, if the DOC Auto delete channels parameter is

enabled in all optical domains (different Optical System Identifiers) that the
selected channel is crossing, then deleting this channel from an upstream
domain will automatically delete it from all downstream domains, starting with
the receiving domain and going back towards the source domain.
Note: If DOC Auto delete is disabled, manually delete the channels at each
DOC site from tail-end to head-end by performing step 8.
Auto Delete parameter set to True (step 7), the cross connections will be
automatically deleted from all optical domains when the channel is deleted
from DOC. (If the connection Auto Delete parameter is set to False, you must
delete the cross connections from each node, even if DOC Auto Delete is
enabled.)
9 For the selected channel, delete the 1WAY photonic connection at each
branch site (site where the channel changes domain) if the deleted channel
crosses optical domains. Refer to the “Deleting Photonic connections”
procedure in Configuration - Connections Management, 323-1851-320.
At ROADM sites where the channel stays within the same Photonic domain
(that is, both directions are in the same Photonic domain), if Autoroute is
enabled, the photonic connections are system-derived and will be
auto-deleted when the CMD ADJ-TX is deprovisioned.
10 If the configuration uses an OPS, for the same deleted channel delete the
associated photonic connection on the second OPS path.
Deprovisioning the CMD ADJ-TX/ADJ-RX
Note: Intermediate OD&C adjacencies need to be removed first.
11 Log in to the site where the selected channel originates.
originates through a DIA step 13
otherwise step 14
13 Delete the 1WAY photonic connection between the DIA CMD44 Ch In port
the “Deleting Photonic connections” procedure in Configuration -
Connections Management, 323-1851-320. If autoroute is disabled, delete the
photonic connection for the CMD to LIM manually.


Step Action
14 Open the Equipment and Facility Provisioning application. Select the CMD
equipment corresponding to the channel to be deleted.
15 Select “ADJ-TX” from the Facility Type drop down list
16 Select the ADJ-TX that corresponds to the wavelength to be deleted and click
on the Edit button.
17 In the Edit ADJ-TX dialog box, change the Transmitter type to Unknown.
18 It is recommended to set the Paired Rx parameter to Yes.
20 For an OD&C channel, set the ADJ-TX routing rule to the Shortest path using
the TL-1 command:
ED-ADJ-TX::ADJ-<CMD shelf#>-<CMD slot#>-<CMD
port#>:CTAG:::ROUTINGRULE=SHORTESTPATH;
21 Log in to the site where the selected channel terminates and open the
Equipment and Facility Provisioning application. Select the CMD equipment
corresponding to the channel to be deleted.
terminates through a DIA step 23
otherwise step 24
23 Delete the 1WAY photonic connection between the Backbone amplifier Line
A In port to the DIA CMD44 Ch Out port for the selected channel. Refer to the
“Deleting Photonic connections” procedure in Configuration - Connections
Management, 323-1851-320. If autoroute is disabled, delete the photonic
connection for the CMD to LIM manually.
24 Select “ADJ-RX” from the Facility Type drop down list.
25 Select the ADJ-RX that corresponds to the wavelength to be deleted and click
on the Edit button.
The Edit ADJ-RX dialog box opens.
26 In the Edit ADJ-RX dialog box, change the Receiver type to Unknown.
27 Click OK in the Edit ADJ-RX dialog box.
28 Click OK in the confirmation message.


Step Action
29 If applicable, repeat step 21 to step 27 for all OD&C intermediate drop Rx Adj,
including branch domain drops for the channel that was deleted.
30 Repeat from step 9 for each deleted channel.
After you delete a channel, some ports on photonic circuit packs that
originally had light may no longer have light, and will raise a Loss of signal
alarm. This is expected. To clear the alarm, change the secondary state of the
affected facility to AINS.
31 If the transponder must be disassociated from the CMD port, remove the
EFEA provisioning on the transponder ADJ pointing to the CMD, if present:
• In the Equipment and Facility Provisioning application, select the
transponder equipment.
• Select “ADJ” from the Facility Type drop down list.
• In the Edit ADJ dialog box, remove the EFEA provisioning.
• Click OK in the Edit ADJ dialog box.
• Click OK in the confirmation message if it appears.
Note: For TOADM configurations, line amplifiers connected to SCMD4s may
not go into shutoff mode when all channels are deleted due to the limited
range of the internal VOAs coupled with the fact that the transponders stay
tuned and outputting power in this colored configuration. To avoid this,
disconnect all transponders connected to the affected SCMD4s after the last
channel is deleted.
—end—

Procedure 7-5
Force deleting optical channels
Note: Perform this procedure when channel deleting using
Procedure 7-3, “Deleting bidirectional optical channels” or Procedure 7-4,
“Deleting unidirectional optical channels” has failed. This procedure must
be performed in conjunction with Procedure 7-3, “Deleting bidirectional
optical channels” or Procedure 7-4, “Deleting unidirectional optical
channels”, and not as a stand-alone procedure.
Use this procedure to delete optical channels in any of the following

circumstances:
• The CMD or BMD2 (for WSS 50GHz w/OPM 2x1) that is associated with
the channels to be deleted has been removed from the system.
• Channel deletion using the Delete button has failed.

CAUTION
Risk of traffic interruption
Channel deletion using the Force Delete button can impact
existing channels that are not force deleted.
CAUTION
DANGER
Risk of injury


CAUTION
Step Action
1 Use a PC with visibility to the network elements where the channels to be

deleted are added and/or dropped, and to the DOC network elements for the
two directions.
Deleting the optical channel
Note: To guarantee a non-service affecting (NSA) delete, deleting OD&C
must be performed through DOC.
For bidirectional channels, perform step 2 to step 9 on the DOC OTS for both
optical paths. You can perform these steps at the two DOC OTSs (that is, the
DOC OTS for each direction) simultaneously, or perform these steps one
direction at a time.
2 Identify the OTS that is serving as the DOC for the applicable direction.
3 From the navigation tree, select Configuration -> Photonic Services ->
Domain Optical Controller (DOC).
The Domain Optical Controller (DOC) window appears.
4 Make note of the current Automation Mode setting and set the Automation
Mode to Enhanced Auto Monitor Only. To reset the Automation Mode,
perform the following:
• Select the Settings tab.
• Click on the Edit button.
The Edit DOC dialog box appears.
• Select the Enhanced Auto Monitor Only from the Automation mode
pull-down list.
• Click on the OK button.
The Automation mode field now displays Enhanced Auto Monitor Only.
5 In the Channels tab, select the channels to delete, and click on the Force
Delete button.
A confirmation dialog opens.


Step Action
6 Click on the Yes button.

Once the channels are deleted, the Overall Status field displays a value of
Non-Optimal, and the value displayed in the Channel Condition column for
each remaining channel entity is Not Optimal. The status of the deleted
channels is Inactive.
7 Click the Re-optimize button in the DOC screen.
A confirmation dialog opens.
8 Click on the Yes button and wait for the Overall Status to become Optimal.
After the re-optimization completes, the Overall Status field displays a value
of Optimal, and the value displayed in the Channel Condition column for each
remaining channel entity is Optimized. The status of the deleted channels is
Inactive.
Note: If you stop a manual deletion of optical channels before all the selected
optical channels become “Inactive”, some of the optical channels will be
shown as “Partially Deleted” and some will be shown as “Non-Optimal”. If the
Partially Deleted optical channels are deleted and re-added, after
re-optimizing all the optical channels will be shown as Optimal. However, the
Active parameter (if Autoroute is enabled, Equipment and Facility
Provisioning window, ADJ-TX panel; if Autoroute is disabled, Photonic
Connections window) for the deleted/added optical channels will be TRUE but
will be FALSE for the optical channels that were originally selected for
deletion but were not deleted. You must manually change the Active
parameter of these optical channels to TRUE (see the “Editing facility
parameters” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310).
Note: If the DOC status stays in the “Re-opt:Waiting” state for an extended
period, clear any “DOC Action: Fault Detected” alarms in downstream
domains. Resolving the issue in the downstream domain and clearing the
alarm will allow the upstream domain to proceed with the channel
re-optimization.
9 Set the Automation Mode to its original setting, which you noted in step 4.
10 Repeat step 2 to step 9 for the other direction, if necessary.
11 Return to Procedure 7-3, “Deleting bidirectional optical channels” or
Procedure 7-4, “Deleting unidirectional optical channels” to delete the Tx/Rx
adjacency.
—end—

Procedure 7-6
Express deleting optical channels
Use this procedure to express delete optical channels from a 6500
Packet-Optical Platform system when a major outage has occurred on the
optical line fibers that prevents delete (Procedure 7-3, “Deleting bidirectional
optical channels” or Procedure 7-4, “Deleting unidirectional optical channels”)
and force delete (Procedure 7-5, “Force deleting optical channels”) operations
from being successful. This procedure applies only to DOC Enhanced
Automation mode.

Prerequisites
• For every section of the optical line, check the line adjacencies (ADJ-LINE)
of the line-facing amplifier and make sure that the following information is
provisioned:
— Actual Far End Address
— Expected Far End Address
and that the Status is Reliable.
• Before you disconnect any service layer transmitters from the system, you
must delete the optical channel from the DOC.
CAUTION
DANGER
Risk of injury


CAUTION
Step Action
1 From the navigation tree, select Configuration -> Photonic Services ->
Domain Optical Controller (DOC).
2 Identify and select the channel you want to express delete.
3 From the DOC Trail, identify the upstream DOC.
4 From the NE Trail, identify the network element and the shelf where the
channel originates.
5 If you have not already done so, open a Site Manager session to the selected
network element and log into the Site Manager interface as an admin level
user.
6 Select Configuration -> Equipment & Facility Provisioning.
7 Select the shelf you identified in step 4.
8 Select the CMD and ADJ-TX for the channel you want to delete.
9 Click the Edit button and in the Edit facility ADJ-TX dialog window, set the
Active parameter to False. Then set the Express delete parameter to True.
10 Repeat step 1 to step 9 for all channels you want to delete.
11 Log into the upstream DOC network elements that control the channels.
12 Select Configuration -> Photonic Services -> Domain Optical Controller
(DOC) and click the Start Monitoring button. Monitor the status of all the
channels you are deleting.


Step Action
13 After all the channels report an End-to-End Condition of Inactive, select your
next step.
If you performed the express Then
delete to
move the channels to another Re-add the channels to the new path.
path See Procedure 7-1, “Adding
bidirectional optical channels”.
completely remove the channels Go to Procedure 7-3, “Deleting
(that is, remove all the information bidirectional optical channels” or
associated with the channels, Procedure 7-4, “Deleting unidirectional
remove/disconnect TX/RX optical channels” to delete the Tx/Rx
equipment) adjacency.
—end—

Procedure 7-7
Adding the first optical channel to a Stretched Span
Use this procedure to manage traffic on a Stretched Span configuration,
specifically to manually add a wavelength used to carry OSC traffic over a
span exceeding the OSC link budget. Figure 7-1 on page 7-55 illustrates a
configuration example. The ROADM in the Stretched Span does not support
the DIA or Colorless OADM configuration.
This procedure applies to systems with the OTS parameter Autoroute set to
Enabled. For instructions on how to add channels using the Control Plane for
6500 photonic systems that have the L0 Control Plane application enabled
(that is, OTS parameters Autoroute set to Disabled and CPS set to Enabled),
refer to the Layer 0 Control Plane Activation and Service Provisioning
Overview in Part 2 of the Control Plane Application Guide - Layer 0 (Photonic),
NTRN71AA.
This procedure does not apply for Raman spans, but can be used for spans
equipped with line facing equipment such as MLA2, MLA2 w/ VOA, MLA3.
After you complete this procedure, you can add other traffic wavelengths using
DOC (see Procedure 7-1, “Adding bidirectional optical channels”).
CAUTION
During this procedure the fiber plant does not have to be
disrupted and the system remains a Class 1(IEC)/Class I
(FDA) product.
If the fiber downstream of the MLA2/MLA3 Line A output

connector becomes disconnected accidentally while the Amp
Auto Shutoff Disabled feature is active, the radiation at the
exposed fiber can be at hazard level 1M (IEC 60825-2). In this
situation, you must take all safety precautions appropriate to
hazard level 1M (IEC 60825-2).
The ORL based APR safety mechanism remains active.


Prerequisites
• The installation of terminal (6500/5000) equipment is completed and
terminal equipment is fibered.
If 5000 equipment is used as a data communications route, an MOTR
circuit pack is required for communications. One of the optical mux ports
is connected to a switch (which acts as a media converter) to which an
Ethernet cable can be connected, thus extending the ILAN connection
between sites.
• Network element and nodal commissioning is complete.
• Amplifier peak power provisioning is complete.
• Communications are available to the 6500 network elements on either
side of the Stretched Span.
• Resources are deployed on both sides of each Stretched Span that exists
in the network, at the sites where the 6500 data communications are
bridged to a terminal shelf. Resources can communicate to coordinate
their actions.
• The site EDPs (engineering design packages)/IDPs (international
documentation packages) and the terminal (6500/5000 Technical
Publications) are available.
• Have an optical power meter available.
• The transmitters and the receivers of the terminal cards carrying the OSC
traffic are fibered but not connected to the CMD44.
• There are no wavelengths present on the system.


Figure 7-1
Example of adding the first optical channel to a Stretched Span (using 6500 terminal equipment)
Stretched Span
••• ROADM ROADM •••
ILAN Line Line ILAN

Amp Amp
6500 6500
Note: For clarity, only amplifiers are shown.
Step Action

If you are using Then go to
6500 GCC0 in a different shelf from photonic equipment step 2
6500 GCC0 in the same shelf as photonic equipment step 6
5000 as the data communications route step 7
2 Set an OSPF router on the 6500 shelves over which the data communications
will be bridged.
3 Provision an OSPF circuit on the ILAN IN or ILAN OUT facility of the 6500
shelves over which the data communications will be bridged.
4 On the 6500 photonic shelf, provision an OSPF circuit on the ILAN (IN or
OUT) facilities that are handing off the data communication traffic to the 6500
shelf with the GCC0 carrying cards.
This procedure assumes that the necessary ILAN port has been correctly
provisioned when the shelf was commissioned.
5 Where the data communications are bridged over to a 6500 shelf, connect a
straight-through Ethernet cable between the ILAN IN or ILAN OUT port of the
6500 shelf with the GCC0 carrying cards and the ILAN (IN or OUT) of the
6500 photonic shelf.
6 On each 6500 shelf over which the data communications are bridged,
provision an OSPF circuit on the GCC0 facility that will carry the traffic.
Go to step 12.


Step Action
Using 5000 as the data communications route

7 Provision the switch acting as the media converter.
8 Place the client facility of the connected 5000 MOTR In-service.
9 Use an Ethernet cable to connect the 6500 ILAN to the switch.
10 Use the correct fiber type for the MOTR interface to connect the switch and
the 5000 MOTR.
11 Provision an OSPF circuit on the ILAN (IN or OUT) facility of the 6500 shelves
that are handing off the 6500 data communication traffic to 5000 (that is, the
shelves that have an ILAN connected to the media converter switch). This
procedure assumes that the necessary ILAN port has been correctly
provisioned when the shelf was commissioned
12 Log into the shelves that connect to the Stretched Span and make sure that
there is no OSPF circuit provisioned on the OSC facility going towards the
Stretched Span. Delete the OSPF circuit on the OSC if it exists.
13 Put the following facilities OOS to mask alarms:
• OPTMON-<shelf>-<slot>-4 on the LIM equipment connected to the
Stretched Span may have an LOS alarm. Placing this facility OOS will
have no impact on the operation of the stretched span.
Manually adding the wavelength that will carry the OSC traffic
Note: The following steps are executed in parallel by two teams on either side
of a Stretched Span. These steps are repeated for each Stretched Span in
the network.
14 Connect the 6500/5000 terminal Tx and Rx to the appropriate CMD44 ports.
15 On the shelves connected to the 6500/5000 terminal equipment, provision
the topology for the channel, including the following, as applicable to the
multiplexing/demultiplexing structure of your configuration:
• ADJ-TX
• ADJ-RX
• photonic cross-connects
16 Log into the shelf that is running DOC. Put DOC OOS and apply the following
settings:
• Automation mode: Enhanced Auto Monitor Only
• Auto Add channels: Disabled
• Auto Delete channels: Disabled


Step Action
17 At the channel Ingress NE, set the channel access loss to minimum by setting
the parameters of the corresponding channel control (CHC) facility on the
WSS as follows:
• Opaque state set to No
• Switch Selector as per EDP/IDP (ROADM channel access)
• Target Loss set to 0 dB
18 Select the Line B (transmit) facility (port 6 of MLA/MLA2/MLA3) that comes
after the multiplexing in the wavelength path. Using an optical power meter,
verify that the loss between the terminal transmitter and the Line B input is
within specifications (use the values in Table 4-3 on page 4-129 and calculate
the maximum loss that applies to your configuration, then enter in Table 7-2).
If the loss is higher than expected, locate the source of the excessive loss and
take the appropriate corrective actions.
Table 7-2
Maximum multiplexing loss
Site configuration Maximum loss (dB)
CMD44 100GHz + WSS/OPM
CMD44 50GHz + WSS/OPM
CMD44 50GHz + BMD2 + WSS/OPM

If Then go to
the output of the Line B amplifier connects to a Stretched step 21
Span
otherwise step 20
20 Perform the following:

a. Set the gain of the LINE B amplifier so that the total output power is equal
to the provisioned target peak power.
b. Ensure that there are no Input or Output LOS alarms against the Line B
amplifier (AMP-<shelf>-<slot>-6).
This procedure assumes that at this stage the peak power targets of all the
amplifiers in the Stretched Span network have been provisioned as specified
in the EDP/IDP. Take the appropriate actions if this is not the case.
Go to step 26.


Step Action
21 The LINE B amplifier facing the Stretched Span will be in automatic shutoff.
You must disable ALSO to add the wavelength. This is done by putting the
Line A AMP facility (port 8) into shutoff disabled mode as follows:
Edit the amplifier facility to set the ALSO Disabled value to True.
22 A few seconds after completing step 21, the following alarms should clear:
• the Automatic Shutoff alarm against the LINE B AMP facility (port 6)
amplifier facing into the Stretched Span
• the Optical Line Fail alarm against the downstream Line A AMP facility
(port 8)
23 Set the gain of the LINE B amplifier facing the Stretched Span so that the total
output power is equal to the provisioned target peak power.
This procedure assumes that at this stage, the peak power targets of all the
amplifiers in the Stretched Span network have been provisioned as indicated
in the EDP/IDP. Take the appropriate actions if this is not the case.
24 Communicate with the team on the other side of the Stretched Span to
indicate that the wavelength is now present over the Stretched Span.
25 From this point on, the resource on the other side of the Stretched Span takes
the relay to complete the amplifier gain adjustments until they reach the
demux. Vice-versa, the team on the other side will ask you to take the relay
in the other direction.
26 Set the amplifier gain of the downstream Line A amplifier as follows:
a. Use the Site Manager Performance Monitoring application to measure
the input power of the LINE A IN port and compare it with the output
power from the previous amplifier (Line B OUT [port 5]). If the span loss
is not as expected, take the appropriate actions.
b. Select the type of site.
If the site is Then
a ROADM site Use the CHMON PMs to measure the output power of
the channel being added at the LINE A OUT port of the
amplifier (CHMON-<shelf>-<slot>-7).
a Line Amp site Use the AMP PMs to measure the output power of the
LINE A OUT port of the amplifier.
Set the gain of the LINE A amplifier so that the total
output power is equal to the provisioned target peak
power.


Step Action
c. Ensure that there are no Input or Output LOS alarms against the Line A
amplifier (AMP-<shelf>-<slot>-8). If this amplifier is connected to the
stretched span, the input LOS threshold should be set to -40 and the
output LOS threshold should be set to at least 3 dB lower than the current
output power.
This procedure assumes that at this stage the peak power targets of all the
amplifiers in the network have been provisioned as indicated in the EDP/IDP.
Take the appropriate actions if this is not the case.
The output power may be higher than expected due to minimum gain.
If Then
you are at the terminal site go to step 28
otherwise return to step 19 and repeat until you
reach the terminal site

If the site Then
uses an interior SLA in set and set the amplifier gain for the interior
forget mode SLA as per the EDP/IDP, then go to
step 31
uses an interior SLA that is go to step 29 to set the gain of the
managed by DOC interior SLA
does not use an interior SLA go to step 31
29 If the site uses an interior SLA that is managed by DOC, set the gain of the
interior SLA as follows:
a. Use the Site Manager Performance Monitoring application to measure
the input power of the LINE A IN port and compare it with the output
power from the previous amplifier. If the span loss is not as expected, take
the appropriate actions. (The loss between the MLA and the interior SLA
could be due to a DSCM or other form of pad.)
b. Use the Site Manager Performance Monitoring application to measure
the output power of the LINE A OUT port of the amplifier.
c. Set the gain of the amplifier so that the total power at the Line A Out is
equal to the provisioned target peak power.
30 If the site uses a 9x1 50GHz WSS, you must take the demux amplifier out of
forced shutoff. In the Site Manager interface, select the WSS AMP facility and
edit FORCEDSHUTOFF=DISABLED.


Step Action
31 At the demux, adjust the Receiver power as close as possible to the nominal
power of the receiver adjacency. Use an optical power meter to measure the
receiver power. Make adjustments by changing the gain of the WSS demux
EDFA if applicable.
32 When step 31 is completed in both directions, allow a few minutes for the
terminal cards to settle. Retrieve the OTU layer performance monitoring
parameters for the terminal cards in both directions. Confirm that the OTU
layer defects are not incrementing (CV, ES, SES, SEFS).
If OTU layer PMs Then go to
are incrementing for a given direction step 34
are not incrementing in either direction step 36
34 Starting from the receiving end, increase the pre-amplifier (Line A [port 8]
AMP facility of the MLA) gain by 1 dB, wait for one minute, then refresh the
PM data to see if OTU layer defects are still incrementing.
35 Repeat step 34 as necessary until the OTU layer defects are no longer
detected. If the amplifier is already at its maximum gain (see gain ranges
below), leave it as is and move to the next amplifier.
Amplifier Gain range (dB)
MLA Line A 7 - 20
MLA Line B 6-17
MLA2 Line A, 11-23.5

MLA2 Line B,
MLA3 Line A,
MLA3 Line B
36 When communication is established through the routed link, allow the system
a few minutes to provide complete visibility of the domain from both sides of
the Stretched Span. To verify data communication continuity, log into the
network element on the other side of the Stretched Span.
37 If the network contains another Stretched Span that requires a manual
channel addition, go to step 14. After a channel has been manually added to
all Stretched Spans to provide communications to the entire network, go to
step 38.
38 Clear all the alarms as indicated in Fault Management - Alarm Clearing,
323-1851-543. Make sure all amplifier facilities are in-service (set input LOS
threshold 3 dB below current power and secondary state to AINS, if need be).


Step Action
39 If the OTS parameter Autoroute is disabled, create photonic cross

connections for the channel to be added between the CMD port and LIM port
on each terminal site. Refer to the procedure on adding a photonic connection
in Configuration - Connections Management, 323-1851-320.
40 In each direction, log into the shelf running DOC. Open the DOC facility
screen and wait for the channel information to populate (the current Channel
Condition is “Inactive”). It can take a few minutes after adding the channel for
this information to appear. Record the access identifier of the channel when
it appears.
41 Set the channel state to “Not Optimal” by using TL-1 Command Builder or,
alternatively, by opening a telnet session on the shelf running DOC, as
follows. Note that when using TL-1 Command Builder, substeps a and e are
not required.
a. Use the following command to log into the TL-1 interface:
ACT-USER::<ADMIN Level User>:<CTAG>::<ADMIN Level
password>:;
b. Use the following command to change the Channel Condition from
“Inactive” to “Not Optimal’’:
ED-DOC-CH::<access
identifier>:<CTAG>:::CHACTION=ADD,EDITCOSONLY=Y;
where <access identifier> format is
NC-Shelf-SiteId-RemShelf-RemPath-Wavelength
c. In the DOC screen click on the Refresh button to check that the Channel
Condition is now set to “Not Optimal”.
If Then go to
a channel that has not yet been manually added to the substep d
system is set to “Not Optimal” using this procedure
otherwise substep e
d. If a channel that has not yet been manually added to the system is
unintentionally set to “Not Optimal” using this procedure, repeat step 41
substep a, substep b, and substep c to set the channel that has been
manually added to the system to “Not Optimal”.
e. Log out of the TL-1 interface using the following command:
CANC-USER::<ADMIN Level User>:<CTAG>;
42 Repeat step 41 for all channels manually added to the system.


Step Action
43 Take the Line A AMP facilities out of Auto Shutoff Disabled mode to re-enable
normal response to ALSO Automatic Shutoff requests to Line A Amps on the
Stretched Span(s):
Edit the Line A AMP facilities to set the ALSO Disabled value to False.
44 For normal operation of Stretched Span applications with valid optical safety
feature operation, the Shutoff Thresholds for the Line A AMP facilities must
be provisioned to -40 dBm, which is below their defaults. (MLA Line A default
is -35 dBm; MLA2 Line A default is -39 dBm; MLA3 Line A default is -39 dBm.)
Do not provision this threshold below -40 dBm during normal operation. All
optical safety testing and accreditation is suspect if this threshold is
provisioned below -40 dBm.
Check that the Shutoff Thresholds for the Line A AMP facilities are
provisioned correctly.
45 If the OTS parameter Autoroute is enabled, open the Facilities -> Adjacency
screen and select the TX Adjacency for the channel added to the system. Edit
the Ingress Active Flag in the TX Adjacency to be TRUE.
If Autoroute is disabled, go to step 46.
46 Repeat step 45 for all channels manually added to the system.
47 Change the DOC settings in both directions to put the DOC facilities
in-service.
48 If a channel that has not yet been manually added to the system was
unintentionally set to “Not Optimal” in step 41, set the channel to “Inactive” by
selecting the channel in the DOC facility screen and clicking the Force Delete
button.
49 Click on the Reset TCA Baselines button in the DOC facility screen.
50 When the DOC facilities in both directions are in-service and the Ingress
Active Flag is updated, click on the Re-optimize button and wait until the
Channel Condition is “Optimal” before proceeding.
51 When the Channel Condition is “Optimal”, click on the Reset TCA Baselines
button in the DOC facility screen.
52 Change the DOC settings in each direction as indicated in the EDP/IDP.
53 Use DOC to add the remaining channels (see Procedure 7-1, “Adding
bidirectional optical channels”).


Step Action
54 Put the following facilities OOS based on link budget and/or to mask alarms:
• OSC-<shelf>-<slot>-<port> for the OSC facility facing the stretched span
If the span loss of the stretched span is greater than 37 dB, the OSC
facility must be put OOS in order for the Automatic Laser Shut Off feature
to function properly. All optical safety testing and accreditation is suspect
if the OSC is kept IS on stretched spans with span loss greater than 37
dB. Putting the OSC facility OOS means that the manual workaround will
have to be performed for recovery from fiber cut, and that Optical Line Fail
alarms will be raised against both sides of the stretched span, regardless
of whether a fiber is cut in one or both directions along the stretched
span.
If the span loss of the stretched span is 37 dB or less, the OSC facility can
be kept IS. The signal degrade threshold must be set to 1E-4 for the OSC
facility. Depending on the span loss of the stretched span, the signal
degrade alarm may still be present after increasing the signal degrade
threshold. In order to avoid a standing alarm on the system, the facility
can be put OOS. Putting the OSC facility OOS means that the manual
workaround will have to be performed for recovery from fiber cut, and that
Optical Line Fail alarms will be raised against both sides of the stretched
span, regardless of whether a fiber is cut in one or both directions along
the stretched span.
—end—


8-1
Appendix A: Observing product and

personnel safety guidelines 8-
This section contains safety guidelines that you must follow for personal safety
and to operate the equipment correctly.
Ciena documentation contains precautionary messages and safety

procedures that refer to specific tasks or conditions. You must read and follow
all precautionary messages before you start to work on the equipment.
This section contains the following topics:

• “Audience” on page 8-2
• “Precautionary messages” on page 8-2
• “Safety standards” on page 8-3
• “Grounding standards” on page 8-4
• “Laser radiation—optical transmission systems” on page 8-4
• “Labeling” on page 8-6
• “Hazard level 3B labeling on the 2-slot optical module chassis (OMC2)” on
page 8-29
• “Using optical fibers” on page 8-32
• “Working with systems cooled by forced air” on page 8-34
• “Working with power” on page 8-35
• “Dissipating static electricity” on page 8-43
• “Preventing circuit pack damage and pluggable module damage” on page
8-48
• “Controlling equipment access” on page 8-50
• “Controlling equipment environment” on page 8-50
• “Applying a 1M Hazard Level Caution label on NTK552AAE5,
NTK552BAE5, NTK552FAE5, NTK552FB, and NTK552GAE5 circuit
packs” on page 8-56

8-2 Appendix A: Observing product and personnel safety guidelines
• “Applying Hazard Level 3B and/or 1M laser safety labels on OMC2” on

page 8-65
Audience
Personnel working directly on equipment must be
• trained, authorized, and qualified to carry out the tasks required
• able to follow safety guidelines specific to the product and all local
customer-specific safety procedures
Precautionary messages
To prevent personal injury, equipment damage, and service interruptions,
follow all precautionary messages in Ciena documentation and all local safety
standards required by your company.
The following precautionary messages appear in Ciena documentation.
DANGER
Risk of personal injury
A precautionary message with this symbol indicates a risk of
personal injury.
DANGER
Risk of electrical shock
personal injury caused by an electrical hazard.
CAUTION
personal injury caused by exposure to a laser beam.
WARNING
Risk of burn
personal injury caused by a hot surface.
CAUTION
Risk of interruption to service
service interruption or equipment damage.

Appendix A: Observing product and personnel safety guidelines 8-3
CAUTION
static damage to circuit packs. Use antistatic protection.
WARNING
Hazardous moving parts
Keep fingers and other body parts away.
WARNING
Parties mobiles dangereuses
Tenir les doigts et les autres parties du corps éloignés.
CAUTION
Risk of electric shock
Disconnect all power sources before servicing to avoid shock
hazard.
CAUTION
Risque de choc électrique
Débranchez toutes les sources d'alimentation avant l'entretien
afin d'éviter tout risque de choc.
Safety standards
Ciena network elements conform to all relevant safety standards. The 6500
complies with the following safety standards:
• IEC 60950-1:2005+A1:2009+A2:2013—Information technology
equipment - Safety, Part 1: General requirements
• IEC 60825-1:2014 and IEC 60825-2:2004+A1:2006+A2:2010—Safety of
Laser Products
• FDA 21 CFR 1040—Performance Standards for Light-Emitting Products.
This product complies with FDA performance standards for laser products
except for deviations pursuant to laser notice No.50, date June 24, 2007.

Grounding standards
Ciena network elements support grounding connections to the following
electrical standards:
• ITU-T K.27, Bonding Configurations and Earthing Inside a
Telecommunication Building
• GR-295-CORE, Telcordia Technologies System Documentation, Mesh
and Isolated Bonding Networks: Definition and Application to Telephone
Central Offices
• Telcordia Technologies GR-1089-CORE Issue 6, Electromagnetic
Compatibility (EMC) and Electrical Safety
• ETSI ETS 300 253, Environmental Engineering (EE); Earthing and
bonding configuration inside telecommunications centres
• RUS Telecom Engineering and Construction Manual, section 810
• NFPA70, (US National Electrical Code)
• CSA 22.1, (Canadian Electrical Code)
For details related to grounding, see “Grounding requirements” on page 8-36.
Laser radiation—optical transmission systems

Ciena optical products use laser or light-emitting diode (LED) sources that
emit light energy into optical fibers. This energy is within the red (visible) and
infrared (not visible) areas of the electromagnetic spectrum.
International standards
The IEC 60825 series of international standards cover the safety of laser and
LED products. The following list provides examples from the International
Electrotechnical Commission (IEC), Code of Federal Register (CFR), and
European Norm (EN) series of standards:
• IEC 60825-1 Safety of Laser Products—Part 1: Equipment Classification,
Requirements and User’s Guide (Part 1 of a series of publications under
the general title of: Safety of Laser Products). This standard provides
information about equipment classification and on limit values for the
safety of laser products. In Europe, the EN 60825 series of standards for
CE marking purposes evaluate the safety of laser and LED products. The
EN 60825 series is technically equivalent to IEC 60825.
• IEC 60825-2, Safety of Laser Products—Part 2: Safety of Optical Fibre
Communication Systems. This standard provides information about the
safety of optical fiber communication systems.
• Regional standards such as the EN 60825 series: for example, British
Standard BS EN 60825-1, Safety of Laser Products, Equipment
Classification, Requirements and User’s Guide. These standards are

based on the IEC 60825 series. In Europe, the EN 60825 series of

standards for CE marking purposes evaluate the safety of laser and LED
products. The EN 60825 series is technically equivalent to IEC 60825.
• In the United States, the Food and Drug Administration (FDA), publishes
regulations 21 CFR 1010, Performance Standards for Electronics
Products: General, and 21 CFR 1040 in the Code of Federal Register
(CFR). Regulations 21 CFR 1010 and 21 CFR 1040 contain laser safety
requirements equivalent to the European standards. FDA Laser Notice 50,
issued by the US Department of Health and Human Services (FDS) on
June 24, 2007, now states that there is no objection to the FDA conforming
with IEC labels as specified in IEC 60825-1. This is in an effort on the part
of the FDA to align its standards for laser products with international
standard IEC 60825-1.
Although the FDA classifications (I, IIIb, IV) are similar to IEC classification
(1, 3B, 4), the classifications are not equivalent. Ciena ensures that all its
products are compliant with either or both FDA and IEC requirements, as
required.
Laser radiation hazards

When operating the product normally, with all optical connectors in position
and correctly terminated, the optical radiation is completely enclosed. The
system is a Class 1(IEC)/Class I (FDA) product, regardless of the power
transmitted within the optical fiber.
If you have unterminated optical cables (breaks in the fiber-optic cable or

disconnected connectors) the output from circuit packs containing optical
transmitters can be greater than Class 1 (IEC)/Class I (FDA).
When used and operated as per the procedures described herein, the
maximum radiation level encountered does not exceed the accessible
emission limit (AEL) for Class 1 (IEC) or Class I (FDA). The worst case hazard
level that may be encountered (as defined by IEC 60825-2) is Hazard Level
1M, and defined by ANSI Z136.2 as a Service Group 1. Because the system
is intended to be installed in a restricted access location, no additional
engineering design features are required to prevent exposure to the laser
radiation.
CAUTION
Risk of injury
For a FIM Type 4 module and to respect the 1M laser safety
limit on the aggregate MPO output, the individual input powers
to the LC ports must be <=13 dBm.

The following statement (English and French versions shown) refers to all
6500 cards and components bearing an IEC 60825-2 Hazard Level 1M label.
For further details on optical power and wavelength for each instance, refer to
Table 8-1 on page 8-15 and Table 8-2 on page 8-22.
Labeling
The 6500 system and circuit packs have been labeled in accordance with
IEC 60825-1, IEC 60825-2, and FDA Laser Notice 50 (Dated June 24, 2007).
Circuit pack labels

The elements of a typical circuit pack explanatory label are as follows:
• laser warning symbol
• warning text explaining the risk associated with the hazard from exposed
optical fiber ends and unterminated connectors. This warning text
indicates a hazard can exist on either the fixed or free end of a connector
depending on the direction of transmission.
• a laser hazard level statement in accordance with
IEC 60825-2:2004+A1:2006+A2:2010

For laser hazard labels found on the 6500 system, refer to the following
illustrations.
• “(1) Laser hazard level 1 label” on page 8-8—applies to equipment as
specified in:
— “Additional information for optical pluggable modules (see Note 1 and
Note 2)” on page 8-15
— “Additional information for circuit packs and lasers on fixed ports of
circuit packs” on page 8-22
• “(2) Laser hazard level 1M label” on page 8-9—applies to equipment as
specified in “Additional information for circuit packs and lasers on fixed
ports of circuit packs” on page 8-22


specified in “Additional information for optical pluggable modules (see
Note 1 and Note 2)” on page 8-15
specified in “Hazard level labeling on NTK552AAE5, NTK552BAE5,
NTK552FAE5, NTK552FB, and NTK552GAE5 circuit packs” on page 8-27
• “(19) Laser hazard level 3B label” on page 8-13—applies to equipment as
specified in “Hazard level 3B labeling on the 2-slot optical module chassis
(OMC2)” on page 8-29
• “(20) Laser hazard level 3B label” on page 8-13—applies to equipment as
specified in “Hazard level 3B labeling on the 2-slot optical module chassis
(OMC2)” on page 8-29
Figure 8-1
(1) Laser hazard level 1 label

Figure 8-2
(2) Laser hazard level 1M label
Figure 8-3
Figure 8-4
Figure 8-5

Figure 8-6
Figure 8-7
Figure 8-8
Figure 8-9

Figure 8-10
Figure 8-11
Figure 8-12
Figure 8-13
Figure 8-14

Figure 8-15
Figure 8-16
Figure 8-17
Figure 8-18

Figure 8-19
(19) Laser hazard level 3B label
Figure 8-20
(20) Laser hazard level 3B label

The 6500 circuit packs use lasers that may exceed the AEL for Class 1, and
therefore require wavelength and optical power information at the aperture.
Additionally, the information in the following list is provided in this section for
every optical circuit pack and optical pluggable transceiver—refer to specific
information in Table 8-1 on page 8-15 and Table 8-2 on page 8-22:
• wavelength, shown as a nominal value or dense wavelength division
multiplexing (DWDM) range of values, such as in the following examples:
— 1310 nm nominal indicates a single wavelength in the range of
1260 nm to 1380 nm
— 1550 nm nominal indicates a single wavelength in the range 1525 nm
to 1625 nm
— 1510 nm to1625 nm indicates a range of multiple discrete DWDM
wavelengths
— 1471- 1611 nm indicates a range of multiple discrete CWDM
wavelengths
• wavelength, shown as a nominal value to represent 4 or more discrete

wavelengths for the CFP portfolio of products per:
— (for a 4x10G, 40G, CFP) 1310 nm nominal indicates 4 discrete
wavelengths at nominal wavelengths of 1271 nm (1264.5 to 1277.5
nm), 1291 nm (1284.5 to 1297.5 nm), 1311 nm (1304.5 to 1317.5 nm)
and 1331 nm (1324.5 to 1337.5 nm)
wavelengths at nominal wavelengths of 1295.56 nm (1294.53 to
1296.59 nm), 1300.05 nm (1299.02 to 1301.09 nm), 1304.58 nm
(1303.54 to 1305.63 nm) and 1309.14 nm (1308.09 to 1310.19 nm)
wavelengths at nominal wavelengths of 1523 nm (1521 to 1525 nm),
1531 nm (1529 to 1533 nm), 1539 nm (1537 to 1541 nm), 1547 nm
(1545 to 1549 nm), 1555 nm (1553 to 1557 nm), 1563 nm (1561 to
1565 nm), 1571 nm (1569 to 1573 nm), 1579 nm (1577 to 1581 nm),
1587 nm (1585 to 1589 nm), 1595 nm (1593 to 1597 nm)
• the maximum accessible optical output power at the faceplate/aperture,
after a fiber break (that is, in consideration of IEC 60825-1 classification
and the impact of embedded laser safety features as an Optical Fiber
Communications System per IEC 60825-2).
• the name and the publication date of the standards used to assess the
product

ATTENTION
The Transmit Output Power (max and min), Receiver Sensitivity, and
Receiver Overload data in the Optical Specifications table for each pluggable
(SFP, SFP+, SFP28, QSFP28, QSFP-DD, QSFP+, XFP, CFP, CFP2, and
CFP2-DCO) are performance specifications for the device. Alarm and
warning thresholds may differ based on monitor accuracy of the specific
pluggable device.
The standards for the equipment listed in the following tables are:
• IEC 60825-1:2014
• FDA 21CFR 1040.10
• IEC 60825-2:2004/A1:2006/A2:2010
Table 8-1
Additional information for optical pluggable modules (see Note 1 and Note 2)
Optical Wavelength Maximum output power Hazard level

pluggable
modules
160-9013-900 850 nm < 0.75 mW (-1.25 dBm) 1/Figure 8-1 on page 8-8 (see Note
3)
160-9014-900 1310 nm < 10 mW (10 dBm) 1/Figure 8-1 on page 8-8
160-9108-900 1270/1330 nm < 10 mW (10 dBm) 1/Figure 8-1 on page 8-8
160-9109-900 1330/1270 nm < 10 mW (10 dBm) 1/Figure 8-1 on page 8-8
160-9111-900 850 nm < 0.5 mW (-3 dBm) 1/Figure 8-1 on page 8-8

Table 8-1
Additional information for optical pluggable modules (see Note 1 and Note 2) (continued)

pluggable
modules
160-9201-900 1528.38-1565.50 < 10 mW (10 dBm) 1/Figure 8-1 on page 8-8

nm
160-9400-900 850 nm < 2.31mW (3.6 dBm) 1/Figure 8-1 on page 8-8
160-9402-900 1310 nm <10 mW (10 dBm) 1/Figure 8-1 on page 8-8
160-9404-900 1310 nm < 4.46 mW (6.5 dBm) 1/Figure 8-1 on page 8-8
(see Note 7)
160-9406-900 1310 nm <10 mW (10 dBm) 1/Figure 8-1 on page 8-8

Table 8-1

pluggable
modules
160-9506-900 1290 nm - 1330 nm < 100 mW (20 dBm) 1/Figure 8-1 on page 8-8
160-9600-900 1271 nm, 1291 nm, < 10 mW (10 dBm) 1/Figure 8-1 on page 8-8
1311 nm, 1331 nm
180-2110-900 1528.77 nm - < 50 mW (17 dBm) 1/Figure 8-1 on page 8-8

1567.54 nm

1567.54 nm

(see Note 7) 1567.54 nm

1567.54 nm
NTK583AAE6 1528.38 - 1568.77 <= 2.51 mW (4 dBm) 1/Figure 8-1 on page 8-8
nm
NTK583ABE6 1528.38 -1568.77 <= 2.51 mW (4 dBm) 1/Figure 8-1 on page 8-8
nm
NTK585<xy> 1528.77 nm - <= 10 mW (10 dBm) 1/Figure 8-1 on page 8-8

1564.68 nm
NTK586xxE5 1528.77 -1605.74 <= 2.6 mW (4.2 dBm) 1/Figure 8-1 on page 8-8
nm
NTK587AAE5- 1528.77 -1564.68 <= 7.1 mW (8.5 dBm) 1/Figure 8-1 on page 8-8
NTK587DUE5 nm
NTK587EAE6- 1528.77 nm - <= 2 mW (3 dBm) 1/Figure 8-1 on page 8-8

NTK587HUE6 1563.86 nm in 100
GHz spacing
NTK588xxE5 1530.33 nm - <= 5.4 mW (7.3 dBm) 1/Figure 8-1 on page 8-8
1564.68 nm

Table 8-1

pluggable
modules
NTK589xxE6 1530.33 nm - <=11.2 mW (10.5 dBm) 1/Figure 8-1 on page 8-8

1565.09 nm for C-
Band
1570.42 nm -
1605.74 nm for L-
Band
NTK590<xy> 1471 nm -1611 nm <= 3.16 mW (5 dBm) 1/Figure 8-1 on page 8-8
NTK590LH 1471 nm -1611 nm <= 3.16 mW (5 dBm) 1/Figure 8-1 on page 8-8
NTK590MH
NTK590NH
NTK590PH
NTK590QH
NTK590RH
NTK590SH
NTK590TH
NTK591<xy> 1471 nm -1611 nm <= 3.16 mW (5 dBm) 1/Figure 8-1 on page 8-8
NTK592NBE6 1511 nm <= 3.16 mW (5 dBm) 1/Figure 8-1 on page 8-8
NTK592NHE6 1511 nm <= 3.16 mW (5 dBm) 1/Figure 8-1 on page 8-8
NTK592NPE6 1511 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTK592NGE5 1511 nm <= 0.399 mW (-4 dBm) 1/Figure 8-1 on page 8-8
NTK592NR 1516.9 nm <= 10 mW (10 dBm) 1/Figure 8-1 on page 8-8
NTK592NS 1610.06 nm <= 4 dBm 1/Figure 8-1 on page 8-8
NTK592NVE5 1511 nm <= 3.16 mW (5 dBm) 1/Figure 8-1 on page 8-8
NTK596xH 1471 nm - 1611 nm <= 6.9 mW (8.4 dBm) 1/Figure 8-1 on page 8-8
NTTA01BJE6 1310 nm <= 2.8 mW (4.5 dBm) 1/Figure 8-1 on page 8-8 (see Note
3)
NTTA01FJE6 1310 nm <= 2.8 mW (4.5 dBm) 1/Figure 8-1 on page 8-8 (see Note
3)
NTTA03AA 850 nm < 6.72 mW (8.27 dBm) 1/Figure 8-1 on page 8-8 (see Note
3)

Table 8-1

pluggable
modules
NTTA03BJE6 1310 nm (see Note <= 10 mW (10 dBm) 1/Figure 8-1 on page 8-8 (see Note
5) 3)
NTTA03GJ 1550 nm (see Note < 50 mW (17 dBm) 1M/Figure 8-15 on page 8-12
5 and Note 6)
NTTA03HE 1550 nm (see Note < 50 mW (17 dBm) 1M/Figure 8-15 on page 8-12
5 and Note 6)
NTTA11AA 850 nm <= 2.35 mW (3.7 dBm) 1/Figure 8-1 on page 8-8 (see Note
3)
NTTA11BAE6 1310 nm <= 10 mW (10 dBm) 1/Figure 8-1 on page 8-8 (see Note
3)
NTTA12BAE6 1310 nm <= 10 mW (10 dBm) 1/Figure 8-1 on page 8-8 (see Note
3)
NTTA13EEE6 1550 nm 7.19 mW (8.6 dBm) 1/Figure 8-1 on page 8-8 (see Note
3)
NTTP01AF 850 nm <= 0.5 mW (-3 dBm) 1/Figure 8-1 on page 8-8
NTTP01CD 1310 nm <= 11.3 mW (10.5 dBm) 1/Figure 8-1 on page 8-8
NTTP01CF 1310 nm <= 0.5 mW (-3 dBm) 1/Figure 8-1 on page 8-8
NTTP02AD 1310 nm <= 0.5 mW (-3 dBm) 1/Figure 8-1 on page 8-8
NTTP02BF 1310 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP02CDE6 1310 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP02ED 1310 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP02FF 1550 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP03BD 1310 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP03CF 1310 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP03EF 1310 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP03FF 1550 nm <= 2 mW (3 dBm) 1/Figure 8-1 on page 8-8
NTTP04CDE6 1310 nm <= 5.9 mW (7.7 dBm) 1/Figure 8-1 on page 8-8

Table 8-1

pluggable
modules
NTTP05EF 1310 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP05FF 1550 nm <= 1.58 mW (2 dBm) 1/Figure 8-1 on page 8-8
NTTP06AD 850 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP06AF 850 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP06CD 1310 nm <= 0.5 mW (-3 dBm) 1/Figure 8-1 on page 8-8
NTTP07FF 1550 nm <= 3.16 mW (5 dBm) 1/Figure 8-1 on page 8-8
NTTP08AC 1310 nm <= 1.0 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP08SD 1310 nm <= 1.0 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP09BD 1310 nm <= 1.0 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP10BD 1530 nm <= 1.0 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP11AF 850 nm <= 0.56 mW (-2.5 dBm) 1/Figure 8-1 on page 8-8
NTTP11BF 1310 nm <= 14.7 mW (11.6 dBm) 1/Figure 8-1 on page 8-8
NTTP11CF 1310 nm <= 14.7 mW (11.6 dBm) 1/Figure 8-1 on page 8-8
NTTP12ACE6 1310 nm 0.16 mW (-8 dBm) 1/Figure 8-1 on page 8-8
NTTP12BCE6 1310 nm 0.04 mW (-14 dBm) 1/Figure 8-1 on page 8-8
NTTP13CFE6 1310 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
NTTP30CFE6 1310 nm <=2.7 mW (4.3 dBm) 1/Figure 8-1 on page 8-8
NTTP80BA 1310 nm <= 2.3 mW (3.6 dBm) 1/Figure 8-1 on page 8-8
NTTP80DA 1550 nm <= 2.0 mW (3 dBm) 1/Figure 8-1 on page 8-8
NTTP81AA 850 nm < 0.5 mW (-3 dBm) 1/Figure 8-1 on page 8-8

Table 8-1

pluggable
modules
NTTP81DA 1550 nm < 4 mW (6 dBm) 1/Figure 8-1 on page 8-8
NTTP81KAE6 1550 nm <= 2.51 mW (4 dBm) 1/Figure 8-1 on page 8-8

(see Note 4)
NTTP84BA 1310 nm <=10 mW (10 dBm) 1/Figure 8-1 on page 8-8
NTTP84CA 1310 nm <=10 mW (10 dBm) 1/Figure 8-1 on page 8-8
NTTP84AAE6 1550 nm <= 1.58 mW (2 dBm) 1/Figure 8-1 on page 8-8
NTTP84HA - 1471 nm - 1611 nm <=10 mW (10 dBm) 1/Figure 8-1 on page 8-8
NTTP84HH
NTTP84JA - 1471 nm - 1611 nm <=10 mW (10 dBm) 1/Figure 8-1 on page 8-8
NTTP84JH
NTTP86BAE6 1310 nm <=10 mW (10 dBm) 1/Figure 8-1 on page 8-8
XCVR-080U49 1490 nm < 10 mW (10 dBm) 1/Figure 8-1 on page 8-8
XCVR-080U55 1550 nm < 10 mW (10 dBm) 1/Figure 8-1 on page 8-8
Note 1: The Transmit Output Power (max and min), Receiver Sensitivity, and Receiver Overload data
in the Optical Specifications table for each pluggable (SFP, SFP+, SFP28, QSFP+, QSFP28,
QSFP-DD, XFP, CFP, CFP2, or CFP2-DCO) are performance specifications for the device. Alarm and
warning thresholds may differ based on monitor accuracy of the specific pluggable device.
Note 2: For a complete list of circuit packs that support each pluggable module, refer to the section on
supported pluggable modules in each circuit pack, in Part 3 of Planning, NTRN10FG.
Note 3: The hazard level label may or may not appear on the related circuit pack. For these optical
pluggables, the reference to Figure 8-1 on page 8-8 is provided for information only.
Note 4: The LR-2 spec for Telcordia GR-253-CORE indicates a C-Band wavelength range of 1530 nm
to 1565 nm. The LR2 XFP ordered will have a wavelength operating anywhere within this range.
Note 5: For a 4x25G, 100G, CFP, 1310 nm nominal indicates 4 discrete wavelengths at nominal
wavelengths of 1295.56 nm (1294.53 to 1296.59 nm), 1300.05 nm (1299.02 to 1301.09 nm), 1304.58
nm (1303.54 to 1305.63 nm) and 1309.14 nm (1308.09 to 1310.19 nm).
Note 6: For a 10x10G, 100G, CFP, 1550 nm nominal indicates 10 discrete wavelengths at nominal
wavelengths of 1523 nm (1521 to 1525 nm), 1531 nm (1529 to 1533 nm), 1539 nm (1537 to 1541 nm),
1547 nm (1545 to 1549 nm), 1555 nm (1553 to 1557 nm), 1563 nm (1561 to 1565 nm), 1571 nm (1569
to 1573 nm), 1579 nm (1577 to 1581 nm), 1587 nm (1585 to 1589 nm), 1595 nm (1593 to 1597 nm).
Note 7: Contact your Ciena representative for availability.

Table 8-2
Additional information for circuit packs and lasers on fixed ports of circuit packs
Circuit packs/ Wavelength Maximum output power Hazard level/

lasers on fixed Laser hazard label on circuit
ports pack
B-730-0003-001 850 nm <= 1 mW (0 dBm) 1/Figure 8-1 on page 8-8
B-700-1036-001 1310 nm <= 7.3 mW (8.83 dBm) 1/Figure 8-1 on page 8-8
NTK504BA 1516.9 nm <= 10 mW (10 dBm) 1M/ Figure 8-2 on page 8-9
(see Note 1)
NTK504PA 1504.5 nm - 1565.3 nm Terrestrial: 1M/Figure 8-2 on page 8-9

(see Note 1) 1569.8 nm - 1610.5 nm < 100 mW (20 dBm)
Submarine isolator output: 3B/Figure 8-19 on page 8-13

23 dBm 3B/Figure 8-20 on page 8-13
Submarine common
output: 24.5 dBm
NTK504PL 1504.5 nm - 1565.3 nm Submarine isolator output: 3B/Figure 8-19 on page 8-13
(see Note 1) 1569.8 nm - 1610.5 nm 23 dBm 3B/Figure 8-20 on page 8-13
Submarine common 1M/Figure 8-2 on page 8-9

output: 19.5 dBm
NTK504PN 1528 nm - 1570 nm < 250 mW (24 dBm) 1M/ Figure 8-2 on page 8-9
NTK505CA 1528.77 nm - 1566.72 < 100 mW (20 dBm) 1M/ Figure 8-2 on page 8-9
nm
NTK508AAE5 1530 nm - 1565 nm < 100 mW (20 dBm) 1M/Figure 8-3 on page 8-9
NTK508ABE5
NTK508ACE5
NTK508ADE5
NTK508AEE5
NTK508AFE5
NTK508AGE5
NTK508AHE5
NTK508AJE5
NTK508FAE5 1527 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK508HA 1310 nm + 1528.77 nm < 10 mW (10 dBm) @ 1M/Figure 8-16 on page 8-12
- 1566.72 nm 1310 nm
< 100 mW (20dBm) @
1528-1567 nm
NTK528XAE5 1528 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9

Table 8-2
Additional information for circuit packs and lasers on fixed ports of circuit packs (continued)

ports pack
NTK529SAE5 1550 nm 3.98 mW (+6 dBm) 1/Figure 8-1 on page 8-8

NTK529SDE5
NTK532GN 1528 nm - 1612 nm <= 100 mW (20 dBm) 1/Figure 8-1 on page 8-8
NTK538EJ 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-18 on page 8-12
NTK538EK nm (C-Band)
NTK538EL
NTK538EM
NTK538UJ 1310 nm (Client), Client: < 10mW (10 dBm) 1M/Figure 8-17 on page 8-12
NTK538UK 1528.77 nm - 1566.72 Line: < 100mW (20 dBm)
nm (Line)
NTK538UL
NTK538UM
NTK538UN
NTK539BB 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
NTK539BE nm (C-Band)
NTK539BH
NTK539BN
NTK539FJ 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
NTK539FN nm (C-Band)
NTK539PAE5 1527 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK539PBE5 (C-Band)
NTK539PCE5
NTK539PDE5
NTK539PEE5
NTK539PFE5
NTK539PUE5 1568 nm - 1609 nm <= 100 mW (20 dBm) 1M/Figure 8-9 on page 8-10
(L-Band)

Table 8-2

ports pack
NTK539QJ 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
NTK539QK nm (C-Band)
NTK539QL
NTK539QM
NTK539QN
NTK539QS
NTK539QV
NTK539RAE5 1528 nm -1566 nm <= 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9
NTK539RBE5 1528.77 -1566.72 nm <= 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9
NTK539RCE5 1528.77 - 1566.72 nm <= 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9
NTK539RDE5 1528.77 - 1566.72 nm <= 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9
NTK539REE5 1528.77 - 1566.72 nm <= 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9
NTK539TAE5 1527 nm - 1566 nm <= 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9
NTK539TBE5 (C-Band)
NTK539TCE5
NTK539TDE5
NTK539TEE5
NTK539UA 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
nm (C-Band)
NTK539UB 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
nm (C-Band)
NTK539UC 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
nm (C-Band)
NTK539UD 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
nm (C-Band)
NTK539UE 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
nm (C-Band)
NTK539UH 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
nm (C-Band)

Table 8-2

ports pack
NTK538BK 1528.77 nm -1566.72 <= 100 mW (20 dBm) 1M/Figure 8-8 on page 8-10
NTK538BL nm (C-Band)
NTK538BM
NTK538BR
(Contact Ciena
for availability of
NTK538BR.)
NTK539XAE5 1528 nm - 1565 nm <= 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9
NTK539XEE5
NTK552AAE5 1528 nm - 1566 nm <= 10 mW (10 dBm) See “Hazard level labeling on
(see Note 1) NTK552AAE5, NTK552BAE5,
NTK552FAE5, NTK552FB, and
NTK552GAE5 circuit packs” on
page 8-27.
NTK552AB 1528 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9
NTK552BAE5 1528 nm - 1566 nm <= 10 mW (10 dBm) See “Hazard level labeling on
page 8-27.
NTK552BL 1528 nm -1566 nm < 10 mW (10 dBm) 1M/Figure 8-14 on page 8-11
(L-Band)
NTK552DAE5 1528 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-14 on page 8-11
NTK552DL 1570 nm - 1606 nm < 100 mW (20 dBm) 1M/Figure 8-14 on page 8-11
(L-Band)
NTK552FAE5 1528 nm - 1566 nm <= 10 mW (10 dBm) See “Hazard level labeling on
page 8-27.
NTK552FB 1528 nm - 1566 nm < 100 mW (20 dBm) See “Hazard level labeling on
NTK552AAE5, NTK552BAE5,
page 8-27.

Table 8-2

ports pack
NTK552GAE5 1528 nm - 1566 nm <= 10 mW (10 dBm) See “Hazard level labeling on
page 8-27.
NTK552JA 1421 nm - 1566.72 nm < 100 mW (20 dBm) 1M/Figure 8-11 on page 8-11
NTK552JN 1516.9 nm - 1566.72 < 100 mW (20 dBm) 1M/Figure 8-12 on page 8-11
nm
NTK552JT 1516.9 nm - 1566.72 < 100 mW (20 dBm) 1M/Figure 8-12 on page 8-11
nm
NTK552KA 1527 nm - 1567 nm < 100 mW (20 dBm) 1M/Figure 8-13 on page 8-11
NTK553EAE5 1528 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-3 on page 8-9
NTK553FAE5 1528 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-3 on page 8-9
NTK553GAE5 1528 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK553GB 1528 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK553GC 1528 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK553FC 1528 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-4 on page 8-9
NTK553HA 1527 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK553JAE5 1527 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK553JB 1527 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK553KAE5 1527 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK553KCE5 1527 nm - 1566 nm < 100 mW (20 dBm) 1M/Figure 8-5 on page 8-9
NTK553LA 1527 nm - 1567 nm < 100 mW (20 dBm) 1M/Figure 8-6 on page 8-10
NTK553LB
NTK553MA 1310 nm + 1528.77 nm < 10 mW (10 dBm) @ 1M/Figure 8-16 on page 8-12
- 1566.72 nm 1310 nm
< 100 mW (20 dBm) @
1528-1567 nm
NTK553PAE5 1528 nm - 1567 nm < 14.79 mW (11.7 dBm) 1M/Figure 8-3 on page 8-9
NTK554HA 1529 nm - 1566 nm < 128 mW (21.072 dBm) 1M/Figure 8-7 on page 8-10

Table 8-2

ports pack
NTK538CT 1528.77 nm - 1566.72 <= 100 mW (20 dBm) 1M/Figure 8-18 on page 8-12
NTK538DT nm
NTK554TA 1527 nm - 1566 nm < = 100 mW (20 dBm) 1M/Figure 8-13 on page 8-11
NTK538DR 1528.77 nm - 1566.72 <= 100 mW (20 dBm) 1M/Figure 8-18 on page 8-12
NTK538DS nm
NTK538DZ
NTK540AC/BC 1528.77 nm - 1566.72 <= 100 mW (20 dBm) 1M/Figure 8-18 on page 8-12
NTK540AD/BD nm
NTK540AE/BE
Note 1: The current IEC 60825-2 label artwork for the NTK504BA overstates the threat actually posed by
a disconnection or break at the output. The optical power emitted at the output of the NTK504BA, when
used in conjunction with the NTK592NR DWDM OSC Transceiver, will not exceed the level indicated in
this table.
Note 2: The maximum output power level on these amplifier cards is the power level after engagement of
laser safety mechanisms (see the section on optical power safety mechanisms in 6500 Photonic Layer
Guide, NTRN15DA). These levels are not the maximum operational levels achievable for each amplifier.
For this information, see the technical specifications in Part 3 of Planning, NTRN10FG. For further details,
refer to Hazard level 3B labeling on the 2-slot optical module chassis (OMC2).
Hazard level labeling on NTK552AAE5, NTK552BAE5, NTK552FAE5,

NTK552FB, and NTK552GAE5 circuit packs
As of Release 10.2, a MuxAmp configuration is supported using the amplifier
circuit packs listed in Table 8-3 on page 8-28. The MuxAmp is used in some
networks where lower power interfaces (like the WL3n source) are used. This
configuration requires that Automatic Power Reduction (APR) be disabled,
otherwise it may be triggered during normal operation and hence the
amplifiers had to be reclassified as Class 1M from IEC 60825-1.
Note: Only the shelf processor software can disable APR at Mux sites.
Users cannot disable APR. When APR is disabled, clamping is added
automatically to ensure safety.
The amplifiers used in this application are required to have a Hazard Level 1M
warning label as illustrated in Figure 8-17 on page 8-12. Consequently, the
latest circuit pack release will be labeled for use in Class 1M applications.

The circuit packs and hardware releases in Table 8-3 were originally
manufactured with a Hazard Level 1 warning label as illustrated in Figure 8-1
on page 8-8 and can be re-labeled with the Level 1M label kit (Figure 8-21 on
page 8-29) as described in Procedure 8-1, “Applying a 1M Hazard Level
Caution label on NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB,
and NTK552GAE5 circuit packs”.
Table 8-3
List of circuit packs within the scope of “Applying a 1M Hazard Level Caution
label on NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB, and
NTK552GAE5 circuit packs”
Product Engineering Circuit pack name and hardware release

Code (PEC)
NTK552AAE5 Single Line Amplifier (SLA C-Band), Release 19 and lower
NTK552BAE5 Midstage Line Amplifier (MLA C-Band), Release 19 and

lower
NTK552FAE5 Midstage Line Amplifier 2 (MLA2 C-Band), Release 17

and lower
NTK552FB Midstage Line Amplifier 2 (MLA2 C-Band) with variable

optical attenuator (VOA), Release 05 and lower
NTK552GAE5 Midstage Line Amplifier 3 (MLA3 C-Band), Release 06

and lower
The new (higher) hazard level is consistent with certain existing amplifier
circuit packs and OCLD circuit packs (for example, WL3 circuit packs), so
there is no effective change to the overall system-level laser safety risk for the
6500.

Figure 8-21
Laser Hazard Level 1M Caution label with self adhesive backing
(415-2818-001 rev B)
Hazard level 3B labeling on the 2-slot optical module chassis (OMC2)

Using the upgrade coupler/splitter module (UCS) and/or the C/L-band mux/
demux module (CLMD) in applications that require using the isolator port of
the respective module for wet plant deployments of Submarine Line Terminal
Equipment (SLTE) will necessarily defeat the laser safety features of the
line-facing amplifiers for operational reasons.

Accordingly, the laser safety labels, which appear on the front and back
surfaces of the OMC2 door, must be modified to reflect the new laser safety
hazard concurrent with the SLTE application of the UCS module and/or the
C/L-band mux/demux module (CLMD).
To ensure personnel are adequately warned of the laser safety threat for these
applications, choose the language appropriate labels from the Hazard Level
3B label kits included with each module and apply to the OMC2 door as
described in Procedure 8-2, “Applying Hazard Level 3B and/or 1M laser safety
labels on OMC2”. Refer to the insert included in each kit for additional details.
ATTENTION
Users of the equipment and service personnel should have appropriate laser safety
training.
Figure 8-22
Laser hazard level 3B label (415-2998-001 rev A; to be applied on the front of the
OMC2 door; language variants)

Figure 8-23
Laser hazard level 3B label (415-2999-001 rev A; to be applied on the back of the
OMC2 door; language variants)
Circuit pack explanatory label—Passive subassembly labels

A passive optical subassembly supplied and installed as part of a complete
Ciena optical communication system has the appropriate hazard level
assigned and labels attached. If Ciena does not supply and install the
subassembly, you must determine the maximum accessible optical output
level and assign the appropriate hazard level and labels.
Passive subassemblies (for example, optical patch panels, couplers and

splitters, and optical switches) can carry optical signals of any power
depending on the source optical fibers. These subassemblies require the
appropriate laser warning and explanatory labels that you normally place in
close proximity to the connectors or to the access panel.
You are responsible for ensuring the following requirements are met:
• be aware of the optical powers at the inputs and outputs of the
subassemblies
• place the appropriate labels on subassemblies
• only qualified personnel, trained in optical safety, and who understand the
optical safety issues associated with the subassemblies, work on the
equipment

Product-level regulatory label

All products containing optical circuit packs include product-level regulatory
labels. Ciena applies the regulatory label at the factory. This label includes
information about equipment compliance to safety standards and does not
have to be visible after installation of the equipment. This label also includes
all necessary approval marks. It is located on the side of the 6500 shelf.
Using optical fibers

Optical fibers are either single mode or multiple mode. The information in the
following paragraphs applies to all optical fibers.
Handling optical fibers

When you work with optical fibers, you must take the following precautions:
• Wear eye protection such as safety goggles or safety glasses with side
guards when you install optical fibers.
WARNING
severely damage your eyes. Keep all optical connectors
capped.
• Do not look into the opening of an optical fiber, or the opening of an optical
fiber connector, if the optical fiber is active or the unit has the power turned
on.
• Avoid direct exposure to optical fiber ends or optical connector ends where
you can access the laser signal directly.
• Clean your hands after you handle optical fibers. Small pieces of glass are
not always visible and can damage your eyes.
DANGER
Risk of eye injury
If you have a piece of a glass in your eye, get medical
assistance immediately.
• Do not handle pieces of optical fiber with your fingers. Use tweezers or
adhesive tape to lift and discard any loose optical fiber ends.
• Wear rubber gloves when you clean optical connectors. The gloves
prevent direct contact with the isopropyl alcohol and prevent
contamination of the ferrules with skin oils.
• Place all optical fiber clippings in a plastic container provided for that
purpose.
• Handle optical fibers with caution. Place the optical fibers in a safe location
during installation.

• Protect all optical fiber connectors with clean dust caps at all times.
Use optical terminators on unused input faceplate connectors of installed
• Follow the manufacturer instructions when you use an optical test set.
Incorrect calibration or control settings can create hazardous levels of
radiation.
Splicing optical fibers

When you must look at a spliced optical fiber with a small magnifier, take the
following precautions:
• Power off all laser sources to the optical fiber or disconnect the remote
optical fiber end from the laser sources before you start splicing. Make
sure that all laser sources remain disconnected or have the power turned
off. The laser sources can be in a central office, on subscriber premises,
or in a remote location.
• Disconnect all optical test sets from the optical fiber before you start
splicing. The connections can be local or remote.
• Use only the optical instruments approved by your company.

Repairing optical fibers

When an accidental break occurs in the optical fiber, do the following:
• Report the location of the damaged optical fiber to both the central office
and the field repair personnel.
• Power down all laser sources to the optical fiber or disconnect the remote
optical fiber end from the laser sources. The laser sources can be in a
central office, on subscriber premises, or in a remote location.
Working with systems cooled by forced air

When you work with systems cooled by forced air, you must take the following
precautions:
• Wear eye protection such as safety goggles or safety glasses with side
guards when you work near the shelf air exhaust or when you inspect or
replace a cooling fan module or shelf air filter as you may dislodge debris
including glass fiber particles.
DANGER
Risk of eye injury
Wear eye protection such as safety goggles or safety glasses
with side guards when you work with fan modules, air filters, or
in proximity to the shelf air exhaust.
• If you remove a cooling fan module from a 6500 shelf to inspect or replace
it, you must replace it within 30 to 60 seconds depending on the shelf type.
Make sure that you have a replacement cooling fan module ready before
removing the cooling fan module.
CAUTION
Risk of personal injury
The fan blades on cooling fan modules rotate at high speed
while operating. If you are removing an active fan module from
a shelf, partially remove it then wait a few seconds for the fan
blades to stop rotating before handling it. Do not hold or carry
a fan module in a manner that could cause detrimental contact
to the fan blades or any backflow louvers.
All 6500 shelves are cooled by forced air pulled through the system by one or
more cooling fan modules. The circuit packs and modules in the system
depend on a constant flow of air in order to operate efficiently and reliably. The
following guidelines apply:
• Do not allow a shelf equipped with active circuit packs to operate without
any working cooling fan modules for more than 30 seconds as some circuit
packs or modules may overheat and malfunction or fail.
• Do not block the air exhaust or operate the system in a fully enclosed
cabinet or room that will re-circulate exhaust air back into the system.

• Do not operate a shelf with empty slots, empty subslots, or empty

pluggable transceiver ports/ cages as it affects shelf cooling. You must
equip unused slots and subslots with appropriate filler cards or panels and
protect all unequipped transceiver ports/cages with appropriate dust
covers.
• Do not operate a shelf indefinitely without periodically inspecting and
replacing the air filter. In controlled operating environments that are below
the airborne contaminant levels listed in Telcordia GR-63-CORE (NEBS)
and maintain an ambient temperature of 30°C or less, it is recommended
that you inspect the air filter after 12 months of use and that you replace it
if it has accumulated a layer of dust.
You must discard and replace the air filter after 18 to 24 months of use.
The recommended air filter replacement interval is six months when
operating in environments with higher ambient temperatures, with an
unknown concentration of airborne contaminants or when the
concentration is known to be in excess of Telcordia GR-63-CORE (NEBS)
levels.
Working with power
This section includes information on grounding requirements, working with AC
power, and working with DC power.

Grounding requirements
Follow this precaution.
CAUTION
Risk of electrical shock and equipment damage
Grounding is mandatory to satisfy local electrical codes/
regulations for the safe use of the equipment.
Ground the rack/cabinet to the common building network

(CBN), isolated bonding network (IBN) or ETSI Mesh Bonding
Network ground/protective earth. See the procedure on
connecting the rack ground to the office ground in Installation -
General Information, 323-1851-201, for details.
Correct grounding of the equipment rack/cabinet is mandatory

in accordance to electrical safety standards and mitigates the
electrostatic discharge (ESD) and operational concerns
described in “Consequences of incorrect grounding” on page
8-38.
Also, ground every 6500 shelf and peripheral tray as described

in the related procedure. Refer to the Installation technical
Marked locations on the rack and/or shelf bearing the Protective Earthing
Conductor are appropriate locations for attaching grounding hardware (for
example, approved cables, lugs)—see Figure 8-24 on page 8-36.
Figure 8-24
Protective Earthing Conductor (IEC 60417-5019)
Bonding topologies
Bonding is a complementary feature to, but should not be confused with,
Protective Grounding and is intended to create equipotential nodes
throughout the office installation. Marked locations bearing the symbol
illustrated in Figure 8-24 identify sites that can be used to bond equipment but
are not intended for safety grounding. The Protective Earthing Conductor can
be connected using either of these topologies to satisfy the mandatory
(safety) grounding dependencies for the 6500.

The 6500 supports connection to and installation in the following equipment

bonding topologies (additional detail on these topologies and their
relationships is covered in Telcordia GR-295-CORE):
• CBN—Common Bonding Network – This is the principal means for
effecting bonding and earthing inside a telecommunication building. It is
the set of metallic components that are intentionally or incidentally
interconnected to form the principal BN in a building. These components
include: structural steel or reinforcing rods, metallic plumbing, ac power
conduit, ACEG conductors, cable racks, and bonding conductors. The
CBN always has a mesh topology and is connected to the grounding
electrode system.
• IBN—Isolated Bonding Network – A bonding network that has a single
point of connection (SPC) from the network element (for example, shelf or
rack) to either the common bonding network or another isolated bonding
network. All IBNs will have a connection to earth through the SPC.
• Mesh—BN – A bonding network in which all associated equipment
frames, racks, and cabinets, and usually, the dc power return conductor,
are intentionally bonded together as well as at multiple points to the CBN.
Consequently, the mesh-BN augments the CBN.
• There are multiple additional variations of these topologies, for example,
Mesh-IBN, Star-IBN.

Figure 8-25 on page 8-38 illustrates the key differences and relationships
among the bonding topologies.
Figure 8-25
Bonding topologies—CBN, IBN, MESH
• There are two supported DC Return implementations supported within the

Bonding Network topologies (in Figure 8-25):
— Common DC Return (DC-C) – An implementation where the battery
return is bonded to the surrounding BN, either in a Mesh or Isolated
topology. This is often implemented as a bond to the local framework
or bonding hardware.
— Isolated DC Return (DC-I) – An implementation of the battery return
where the network element has a separate DC return, isolated from
other BNs until a single connection point, often at the power source,
where connection to the CBN is implemented.
Consequences of incorrect grounding
The Protective Earthing Conductor is a key dependency of the mandatory
safety requirements in most countries. The 6500 is independently certified as
safe with the dependency that the equipment (rack, shelf) is grounded at one
or more of the approved bonding sites noted in the preceding section as a
Protective Earthing Conductor. If not connected or incorrectly connected,
there is a risk of shock or damage due to high energy fault currents (should
these arise). Local electrical codes/regulations typically require strict
adherence to all safety instructions during installation—the equipment must
be grounded for safe use.
Additionally, grounding the 6500 will ensure that all external surfaces
(including the ESD jack locations) are of sufficiently low impedance to
non-intrusively reduce static charge build-up that may occur when operating,

repairing or installing new equipment in the 6500. When correctly grounded,

the ESD jack locations work effectively in coordination with good ESD
mitigation practices (see “Dissipating static electricity” on page 8-43) to
mitigate the risk of damage to the equipment. For the list of related standards,
see “Grounding standards” on page 8-4.
Working with AC power

DANGER
Read and understand the power procedures you are
performing. Take necessary precautions and use the
appropriate insulated tools when working with power.
AC-powered 6500 shelves must be grounded. When you install AC power

cables/feeds to the product’s power input connectors, or if you perform routine
power maintenance, make sure that you:
• Read and understand the power procedures that you are performing.
• Take the necessary precautions.
A continuously lit green "Power OK" LED at the faceplate of an AC power input
card Type 2 (NTK505RA, NTK505RN, and NTK505SB) indicates that the AC
power input circuit is functioning correctly. If the green “Power OK” LED is lit,
there is voltage detected on the associated AC feeder.
If the green “Power OK” LED on a power input card is not lit, the possible
causes can include, but are not limited to:
• the AC power cord may be unplugged or damaged.
• the AC source breaker tripped or turned off or the fuse in the source panel
may be blown or missing.
• AC feeder low voltage or power failure
• damaged or non-functional power input card

Working with DC power

DANGER
The battery feeds can be at a high enough potential to
constitute a shock hazard. Read and understand the power
procedures you are performing. Take necessary precautions
and use the appropriate insulated tools when working with
power.
WARNING
Risk of personal injury, energy hazard
The battery feeds are capable of supplying very high current
which, during an unintentional short, can cause burns. Read
and understand the power procedures you are performing.
Take necessary precautions and use the appropriate insulated
tools when working with power.
ATTENTION
NTK505CAE5 60A Power Input Card (breakered) and NTK505DAE5 60A
Power Input Card (breakerless) can only be equipped in specific 6500
shelves rated for 60A or greater. These power cards do not have agency
(CSA/UL) approval for use in the NTK503xA (except NTK503SA),
NTK503xB and NTK503xC 14-slot shelf assemblies. Therefore, these
combinations are not supported.
ATTENTION
The 60A Power Input Cards (NTK505CAE5/NTK505DAE5/NTK505EAE5),
2x50A Power Input Card (NTK505DS) and 3x60A Power Input Cards
(NTK605CAE5/NTK605EAE5/NTK605FA/NTK605FE), and 4x60A Power
Input Cards (NTK605GA/NTK605GE) use protective covers to prevent
access to powered terminals and are required when the equipment is
powered. Ensure the covers are securely in place before applying power and
remain in place at all times when powered.
When you install power feeds to the product input terminals or if you perform
routine power maintenance, make sure that you do the following:
• Read and understand the power procedures you are performing.
• Take the necessary precautions and use the appropriate insulated tools to
perform any tasks.
A continuously lit green "Power OK" (“Pwr OK” or “Power”) LED at the
faceplate of a field-replaceable power input card indicates that the power input
circuit is functioning correctly. If the green “Power OK” LED is lit, there is
voltage detected on the associated feeder in the correct polarity and the power
is passing through the power input breaker or fuse (if applicable to the power

card type) to the backplane. Except for the NTK605CAE5/NTK605EAE5

variants of the 3x60A power input cards, all power input cards with more than
one power feed (for example, L1, L2) have one green “Pwr OK” LED per feed.
The NTK605CAE5/NTK605EAE6 variants of the 3x60A power input cards
have one green “Power” LED that is lit when all three feeds are present and
working and one yellow “Low Voltage” LED that is lit when one or more feeds
are not working (and at least one of three feeds has sufficient voltage to
illuminate the yellow LED).
If the green “Power OK” LED on a power input card is not lit, the possible
causes can include, but are not limited to:
• the power cable assembly or a feed/return wire is not correctly connected
to the power card or the power source
• the breaker is in the “off” or “tripped” position (applies to breakered power
input card types)
• the main fuse is blown or not equipped in the fuse cartridge (applies to
fused power input card types)
• a bus bar required to bridge power from a shared feed/return to multiple L-
/L+ input terminals is missing (applies to 3x60A/4x60A power input cards
being configured for power sharing)
• feeder low voltage or source power failure
• an over-current fail (power input card circuit breaker trip or fuse blown)
• the fuse in the source panel may be blown, defective or missing, the
source breaker tripped or turned off, or the main fuse (and optional alarm
indicator fuse if equipped) of a fused power input card is blown, defective
or missing
• a reverse polarity condition at the input terminals has caused a circuit
breaker trip or a fuse to blow
• damaged or non-functional power input card
Before you replace a blown fuse, you must:

• Determine if there are any obvious causes of the trip occurring in the
affected parts and associated wiring. For example, signs or odors
associated with an overheated component.
• Verify that the configuration of the power distribution elements complies
with the installation instructions.
If the 6500 is directly powered without protection by a fuse panel or breaker

panel, then breakered power input cards (rated for the lesser of the shelf or
feeder rating) or fused power input cards (equipped with a main fuse rated for
the lesser of the shelf or feeder rating) must be used.

Fused power input card NTK505EEE5 (for the 7-slot optical shelf
[NTK503PAE5] and 14-slot shelf variants) is rated and certified for a maximum
fuse of 40A. Fused power input card NTK505QE (for the 7-slot optical Type 2
shelf [NTK503KA]) is rated and certified for a maximum fuse of 50A. Fused
power input card NTK505EC (for the 6500-7 packet-optical shelf
[NTK503RA]) is rated and certified for a maximum of 50A. Fused power input
cards NTK505EAE5 (for the 14-slot converged and packet-optical shelves)
and NTK605DAE5 and NTK605FE (for the 32-slot packet-optical shelf) are
rated and certified for a maximum fuse of 60A.
20A, 40A, 50A, and 60A fuses are available (see Planning - Ordering
Information, 323-1851-151). Other fuse ratings may be supported in specific
applications. Contact your Ciena representative for Cooper Bussman type
TPS or Littelfuse type TLS part numbers. Use of a fuse rated for more than
the power card or shelf rating or use of a different brand of fuses can result in
equipment damage and voids all warranties.
If the 6500 is powered and protected by an external fuse or breaker panel

(with appropriately sized fuses or breakers), then use of unprotected
(breakerless) power input cards is permitted. Failure to provide acceptable
external over-current protection and supply disconnection can result in
equipment damage and voids all warranties.
The 2-slot optical Type 2 shelf (NTK503LA) when equipped with 24 Vdc
breakered power input cards (NTK505TR) is rated for a maximum of 17 A at
20 Vdc to 30 Vdc. The 24 Vdc power input card has a breaker rated for 25 A
so it may be connected directly to a 24 Vdc power source as long as the
supplied current rating does not exceed the lesser of the power cable rating or
the power input card breaker rating of 25 A.
If the 7-slot optical shelf (NTK503PAE5) is to be installed without using a

4x10A, 4x20A or 4x40A BIP (NTK599BH, NTK599BGE5 or NTK599BA) or a
1U BIP/FIP (NTK599DA/NTK599EA) equipped with 10 A, 20 A or 40 A circuit
breakers, then a breakered or fused power input card must be used.
For the 7-slot optical Type 2 shelf (NTK503KA), DC power input cards are only
available in breakered and fused variants so use of the 4x10A, 4x20A, 4x40A
or 4x50A BIP (NTK599BH, NTK599BGE5, NTK599BA or NTK599BK) or the
1U BIP/FIP (NTK599DA/NTK599EA) equipped with 10 A, 20 A or 40 A circuit
breakers is optional.
The 6500-7 packet-optical (NTK503RA) supports breakered and fused power

input cards rated for 50 A and 60 A so use of the 4x20A, 4x40A or 4x50A BIP
(NTK599BGE5, NTK599BA, NTK599BK) or a 1U BIP/FIP (NTK599DA/
NTK599EA) equipped with 20 A or 40 A circuit breakers is optional. If the shelf
is equipped with 60 A breakerless power input cards, an external fuse or

breaker panel (such as a BIP) must be used to limit the feed to 60 A or less. If
the shelf is equipped with 60 A power input cards (breakered, breakerless or
fused), 1 rack unit (1U) of space above the shelf must be reserved for routing
the cables to the power card lug terminals. (The 6500-7 packet-optical
[NTK503RA] shelf occupies 8U of rack space [instead of 7U] when it is
equipped with the 60A breakered or fused power input cards).
If the 14-slot shelf is to be installed without using a 4x20A, 4x40A or 4x50A

BIP (NTK599BGE5, NTK599BA, NTK599BK) or a 1U BIP/FIP (NTK599DA/
NTK599EA) equipped with 20 A or 40 A circuit breakers, then a breakered or
fused power input card must be used.
If the 14-slot packet-optical shelf (NTK503SA) is equipped with 2x50A

breakerless power input cards, the feeds must be protected by an external
fuse or breaker panel such as a 4x40A or 4x50A BIP (NTK599BA or
NTK599BK).
Use of the 4x20A, 4x40A or 4x50A BIP (NTK599BGE5, NTK599BA,

NTK599BK) and 1U BIP/FIP (NTK599DA/NTK599EA) is not supported with
32-slot packet-optical shelf variants. Each power feed to a 3x60A or 4x60A
breakered or fused power input card is rated for 60 A max. However, when
sharing power across two or more feed or return terminals using a supported
bus bar, the shared feed must be limited to 100 A or less with a breaker or fuse
at the power source.
Dissipating static electricity

The level of static electricity increases on your body when you move around
or come into contact with other charged surfaces. Excessive levels of static
electricity can damage equipment. You must wear a properly functioning heel
grounder (that attaches to your leg and foot) and/or an antistatic wrist-strap,
or another personal grounding device when you work on any of the following:
• network element shelves (including the metal frame and cover)
• cables connected to circuit packs
• circuit packs
CAUTION
Risk of equipment damage
Heel grounders or similar worn footwear attachments work
when the floor is designed to dissipate static electricity. If the
properties of the floor are unknown or in doubt, use a
wrist-strap and make sure it is connected to a piece of
electrostatic discharge (ESD) grounding equipment before
proceeding with any maintenance or installation activity.

Any one of the previously mentioned grounding devices dissipate electrostatic

charges to the ground quickly and safely. Use grounding devices correctly to
eliminate the ESD threat you pose to the equipment.
When you wear an antistatic wrist-strap or a heel grounder, you must make
sure the grounding straps are in contact with a moist part of your skin.
Connect the grounding cord to the grounding plug on a grounded fixture of the
product you are working on, such as the shelf ESD jack or rack mounted ESD
jack. Grounded fixtures are accessible on most Ciena products. See the ESD
ground jacks shown in:
• “Example of ESD jack location—6500 7-slot optical shelf (NTK503PAE5)”
on page 8-44
• “Example of ESD jack location—6500-7 packet-optical shelf (NTK503RA)”
on page 8-45
• “Example of ESD jack locations—6500 14-slot optical shelf” on page 8-45
• “Example of ESD jack locations—6500 14-slot packet-optical shelf
(NTK503SA)” on page 8-46
• “Example of ESD jack locations—6500 32-slot packet optical shelf
(NTK603AAE5)” on page 8-47
Figure 8-26
Example of ESD jack location—6500 7-slot optical shelf (NTK503PAE5)
ESD
Ground

Figure 8-27
Example of ESD jack location—6500-7 packet-optical shelf (NTK503RA)
Figure 8-28
Example of ESD jack locations—6500 14-slot optical shelf

Figure 8-29
Example of ESD jack locations—6500 14-slot packet-optical shelf (NTK503SA)

Figure 8-30
Example of ESD jack locations—6500 32-slot packet optical shelf (NTK603AAE5)
The following guidelines provide optimal electrostatic discharge protection:

• Install bays on conductive floor coverings.
• Provide conductive shoes, antistatic wrist-straps, and heel grounders to all
personnel working on the equipment.
• Maintain local environmental conditions so that relative humidity around
equipment to be serviced is in excess of 20% (preferably higher than
40%). This lowers the threat of developing damaging electrostatic levels.
• You can implement an ESD training and control program that educates
personnel on the hazards of ESD and simple mitigation procedures that
can easily be applied.

Preventing circuit pack damage and pluggable module damage

In this section, the generic term “module” is used to refer to circuit packs or
pluggable modules as applicable.
All modules are subject to damage by rough handling or by electrostatic

discharges. Review the following sections for more information on how to
prevent damage to modules.
If Ciena ships modules separately from the network element shelf, then these
circuit packs can come in shielded containers marked with the following
symbol:
ATTENTION ATTENTION
OBSERVER LES FOLLOW PRECAUTIONS
PRÉCAUTIONS. MANIPULER FOR HANDLING
LE MATERIEL SENSIBLE A ELECTROSTATIC SENSITIVE
L’ELECTROSTATIQUE EN DEVICES
SUIVANT LES MESURES DE
SECURITE
Handling, installing, storing, or replacing circuit packs and pluggable

modules
When you handle, install, or replace modules, you must take the following
precautions:
• Wear an antistatic wrist strap, a heel grounder, or another personal
grounding device before you remove a module from its package or from
the shelf.
• Follow installation and removal procedures for each module. Make sure to
understand and perform each precautionary message in these
procedures (for example, opening/closing the latches of the circuit pack
simultaneously).

CAUTION
Do not touch any solder points, pins, connectors or
components including any integrated electrical cables or
optical fibers when handling a circuit pack or module. Contact
with surfaces other than handles, faceplates, latches/ejectors,
thumbscrews, card guides or module outer shells may result in
contamination that will increase the risk of early failure.
Touching pins, connectors, integrated cables or fibers may
degrade performance or cause permanent damage. When
handling a circuit pack or module, hold it only by the faceplate,
pull handle, card guide or outer shell as directed. During
unpacking or packing of a circuit pack, handle by the card
guide or outer edges only if absolutely necessary. Manipulate
latches, ejectors and thumbscrews only as described in the
applicable procedure.
• Inspect all pin connectors on each module for damage before use.
• Inspect each module for damage before you insert the component into the
shelf.
• Store un-installed modules separately in a shielded box.
• Do not stack modules on or against each other.
• Do not force modules into their packaging material.
• Do not store several modules in the same container.
• Allow each module to reach room temperature before you insert the
module into the shelf.
• Protect all optical connectors of the transmit (Tx) and receive (Rx) optical
modules with clean dust caps at all times.
Use optical terminators on unused input faceplate connectors of installed
PMs can be reported against the port and the port may appear in-service
• Protect circuit pack pluggable transceiver ports/cages by leaving all dust
covers in place until immediately before a transceiver is installed into a
circuit pack. If you will not be immediately replacing a pluggable
transceiver, ensure that the empty port/cage in the circuit pack is protected
by the appropriate dust cover.
• Protect RJ45 and USB ports by leaving dust caps in place until a cable is
connected to a port. If a cable is removed from a port that was originally
equipped with a dust cap, ensure that you replace the appropriate dust
cap on the empty port.
• Store pluggable modules in their protective static-dissipative containers
(when not in use) to prevent damage to the exposed connector terminals.

Leave spare modules in the original shielded containers until you need the
modules. To prevent damage to modules in storage, follow procedures that
prevent:
• accumulation of dirt or dust on the pin connectors
• damage to the printed-circuit board or its components
• warpage (of printed-circuit boards stored in areas where the humidity can
exceed 95% and the temperature can exceed 70°C)
Transporting circuit packs and pluggable modules

When you transport modules, pack each module in its original shielded
container and padding, or in an electrostatically shielded bag. If you lose the
original material, place the module in a shielded bag and use another
container with sufficient padding.
Controlling equipment access

The 6500 system is intended to be installed in a restricted access location. In
North America, location restriction must be in accordance with articles 110-
16, 110-17, and 110-18 of the National Electrical Code, ANSI/NFPA No. 70.
Outside North America, the location restriction must be in accordance with the
international safety standard IEC 60950-1:2005+A11:2009. In the context of
these requirements, a restricted access location is further defined as a
location:
• where access is restricted to only trained personnel
• to which unsupervised members of the general public are not admitted
Controlling equipment environment

The environmental attributes of the system location must be within the ranges
specified in Part 3 of 6500 Planning, NTRN10FG, "Operating environmental
specifications for 6500 system" table.
Some of the equipment is supported in an extended operating temperature

environment (-40C to 65C/-40F to 149F). The extended operating
temperature specification applies only to the following equipment and only in
the conditions specified in the section "Extended temperature solution
overview and description" in Part 1 of 6500 Planning, NTRN10FG. For more
information on the supported equipment, see the tables in the section
"Extended temperature solution overview and description".

The following tables list the supported equipment in an extended temperature

environment (-40C to 65C/-40F to 149F):
• Table 8-4 lists the supported 6500 shelves, common equipment, and
circuit packs.
• Table 8-5 on page 8-52 lists the supported pluggables.
• Table 8-6 on page 8-53 lists the supported power and electrical interface
cables and optical fiber patch cords.
Table 8-4
Supported 6500 shelves, common equipment, and circuit packs that operate in an extended
temperature environment
Component Description Order code

type
Shelf 6500 2-slot optical Type 2 shelf assembly NTK503LA
Bracket kit Bracket and air baffle kit, 6500 2-slot Type 2, front or NTK509NEE6
rear exhaust 567 mm center-to-center mounting holes,
100/127 mm setback, EIA hole pitch
Shelf Shelf processor w/access panel (SPAP-2) w/2xOSC NTZF14xx (kit includes the
processor 2xSFP circuit pack NTK555NA circuit pack)
NTZF15xx (kit includes the
NTK555NB circuit pack)
Power input Power Input Card (breakerless) - 2-Wire D-Sub Input, NTK505TA
cards Max 10A
24 Vdc Power Input Card (breakered) - 2-Wire D-Sub NTK505TR

Input
AC Power Input Card (100 - 240 Vac) NTK505SB
Cooling fan Cooling Fan Module for 2-slot shelf NTK507NA

module
Front covers 6500 Shelf Front Cover (2-slot shelf) NTK509CNE6
6500 2-slot Shelf Front Cover Kit w/Extended Depth NTK509CM
Air filter Air Filter for 2-slot shelf NTK509ENE6
Service OTN Flex MOTR 1xXFP/8xSFP circuit pack NTK532DE

circuit pack
eMOTR Edge 4xXFP/2xSFP+/8xSFP NTK536BE
4x10G OTR 8xXFP circuit pack NTK530QP
100G MOTR WaveLogic 3n Basic C-Band 10xSFP+ NTK538BR
Filler card Interface Filler Card NTK505YAE5

Table 8-5
Supported pluggable optics that operate in an extended temperature environment
Pluggable module description Order code Reference
Note: For support in an extended temperature environment, the pluggable must be used in a circuit
pack and shelf configuration that also supports operation in an extended temperature environment
(Table 8-4 on page 8-51). Dust caps that ship with the pluggables must be left in place until an optical
patch cord is connected.
OC-48/STM-16 SR1/I16.1 1310 nm XCT Enhanced SFP NTTP03BD • Pluggable

Datasheets and
GE SX/FC100/FC200 850nm SFP NTTP06AD Reference,
GE/FC100/FC200 1000-BaseLX 1310 nm XCT Enhanced SFP NTTP06CD 323-1851-180 for
more information
OC-3/12/STM-1/4 IR1/S1.1_S4.1 1310 nm XCT Enhanced SFP NTTP04CDE6 about supported
rates and
Multirate 1310 nm, SMF, 15 km SFP NTTP13BFE6 protocols.
10G, 1270/1330nm Tx/Rx Bidirectional, 40km, SFP+ 160-9108-900 • Part 3 of 6500
Planning,
10G, 1330/1270nm Tx/Rx Bidirectional, 40km, SFP+ 160-9109-900 NTRN10FG
9.95G-11.09G Multirate, 1550 nm, SMF, 40 km SFP+ 160-9204-900 (Technical
specifications)
Multirate LongHaul 14xx/15xx/16xx ITU CWDM SFP+ 160-921x900
10/100/1000BASE-T RJ45 SFP NTTP61CA
Multirate 1471 nm LongHaul ITU CWDM XFP NTTP84JA
Multirate 1491 nm LongHaul ITU CWDM XFP NTTP84JB
Multirate 1511 nm LongHaul ITU CWDM XFP NTTP84JC
Multirate 1531 nm LongHaul ITU CWDM XFP NTTP84JD
Multirate 1551 nm LongHaul ITU CWDM XFP NTTP84JE
Multirate 1571 nm LongHaul ITU CWDM XFP NTTP84JF
Multirate 1591 nm LongHaul ITU CWDM XFP NTTP84JG
Multirate 1611 nm LongHaul ITU CWDM XFP NTTP84JH
9.95G-11.09G Multirate XFP, 1310nm, SMF, 10km NTTP84CA
9.95G-11.09G Multirate,1310nm, SMF, 10km SFP+ 160-9203-900
WaveLogic 5n 100G Type 1.1 CFP2-DCO 180-2111-900

Table 8-6
Supported power and electrical interface cables and optical fiber patch cords that operate in an
extended temperature environment
Cables and Description Order code

patch cords
DC power Cable Assembly, Power, 8AWG, HiFlex, Right Routed 2W2, 2.5 m, NTTC01CHE6
cables Connectorized at one end only
Cable Assembly, Power, 8AWG, 150°C, Red/Black, Right Routed, NTTC01FF

2W2, 2.5 m Connectorized at one end only
Cable Assembly, Power, 8AWG, 150°C, Black/Red, Right Routed, NTTC01FL

Cable Assembly, Power, 8AWG, HiFlex Blue/Gray, Right Routed 2W2, NTTC01CKE6
2.5 m, Connectorized at one end only
Cable Assembly, Power, 8AWG, 150°C, Blue/Gray, Right Routed, NTTC01FH

Cable Assembly, Power, 8AWG, 150°C, Black/Blue, Right Routed, NTTC01FN

Cable Assembly, Power, 12AWG, Black/Black, Right Routed, 2W2, 4.0 NTTC01EF
m, Connectorized at one end only
Cable Assembly, Power, 8AWG, 150C, Red(L+)/Blue(L-), Left Routed, NTTC01FP

2W2, 5.0m Connectorized at one end only
Cable Assembly, Power, 8AWG, 150C, Red(L+)/Blue(L-), Right NTTC01FQ

Routed, 2W2, 5.0m Connectorized at one end only
AC power AC Power Cord - North America, right-angle IEC 60320 C13 (F) to NT0H49ADE6
cables standard plug (NEMA 5-15); 10A/125VAC; 3 m (10 ft)
AC Power Cord - North America, right-angle IEC 60320 C13 (F) to twist- NT0H49ACE6
lock plug (NEMA L5-15P); 10A/125VAC; 3 m (10 ft)
AC Power Cord - European, right-angle IEC 60320 C13 (F) to 2-pin plug NT0H49AEE6
(CEE 7/7); 16A/250VAC; 3 m (10 ft)
AC Power Cord - U.K./Ireland, right-angled IEC 60320 C13 to Fused BS 431-1136-001

1363/A (M); 10A/250VAC; 2.5 m (7.8 ft)
AC Power Cord, right-angle IEC 60320 C13 to C14; 10A 125/250VAC; 441-0096-001
2.5 m (8.2 ft)

Table 8-6
extended temperature environment (continued)

patch cords
DCN and Cable Assembly, Cat 5E, RJ45, TIA568B, Crossover, Single (different NTTC09AxE6
craft access lengths) (Note)
cables
Cable Assembly, Cat 5E, RJ45, TIA568B, Straight, Single (different NTTC09BxE6
lengths) (Note)
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Crossover, Single NTTC09CxE6
(different lengths) (Note)
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single NTTC09Dx,
(different lengths) (Note) NTTC09DxE6
Alarm and Alarm cable, DB9M angled to open, solid wire (30 m) NTTC08ATE6
telemetry
cables Environmental alarm cable kit (3 m) NT6Q59ABE6
(kit contains
two
NT6Q71ABE6
cables)
Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 3 m NTTC09DM
used for Alarm/Telemetry (Note)
Optical fiber Optical patchcord, FPC, LC-LC, 1.6D, 1F, SM, riser, bend insensitive, NTTC52xx
patch cords 42.5 MM LC boot end to ferrule tip, field removable trigger, anti-snag
(bend device (different lengths)
insensitive)
Optical fiber Optical patchcord, SM, Simplex (different lengths) NTTC50xxE6

patch cords
(25mm bend Optical patchcord, SM, Duplex (different lengths) NTTC53xxE6
radius) Optical patchcord, MM 50 micron, Simplex (different lengths) NTTC56xxE6
Optical patchcord, MM 50 micron, Duplex (different lengths) NTTC59xxE6
Optical patchcord, MM 62.5 micron, Simplex (different lengths) NTTC62xxE6
Optical patchcord, MM 62.5 micron, Duplex (different lengths) NTTC65xxE6
Optical patchcord, LC-LC, SM, Simplex, 16 inch (40.64 cm.) NTT899EAE6

Table 8-6
extended temperature environment (continued)

patch cords
Console Cyclades RJ45 Female to EIA/TIA-561 Standard RJ45 Male Serial NTTC09EA
adapter Console Port Adapter Cable, 6 in
cables
EIA/TIA-561 Standard RJ45 Male to Cisco RJ45 Female Serial Console 170-0062-900
Port Adapter, 6 in
DB9 Female to EIA/TIA-561 Standard RJ45 Male Serial Console Port 170-0063-900
Adapter Cable, 6 ft
DB9 Male to EIA/TIA-561 Standard RJ45 Male Serial Console Port 170-0064-900
Adapter Cable, 6 in
Note: The NTTC09AxE6, NTTC09BxE6, NTTC09CxE6, andNTTC09Dx[E6] cables are not rated for
the entire extended temperature range defined by GR- 3108 OSP Class 2. These cables must only be
used in an extended temperature environment that is -20oC to +65oC.

Procedure 8-1
Applying a 1M Hazard Level Caution label on
NTK552AAE5, NTK552BAE5, NTK552FAE5,
Use this procedure to apply a 1M Hazard Level Caution label on
NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB, and NTK552GAE5
circuit packs. To determine whether the 1M Hazard Level Caution label
applies to your equipment and application, see “Hazard level labeling on
NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB, and NTK552GAE5
circuit packs” on page 8-27.
Note: The layout of the product identification labels may not look exactly
as illustrated.
Prerequisites
Before you start, ensure you have the following materials:
• the amplifier circuit pack(s) with Hazard Level 1 label. See “Hazard level
labeling on NTK552AAE5, NTK552BAE5, NTK552FAE5, NTK552FB, and
NTK552GAE5 circuit packs” on page 8-27 and Figure 8-1 on page 8-8 for
an illustration of the Hazard Level 1 label.
• Laser Hazard Level 1M Caution label with self adhesive backing
(415-2818-001 rev B) for each Hazard Level 1 labeled circuit pack. New
labels must contain the following wording: “Hazard level 1M” and
“λ=1528-1567 nm; <100 mW”. See Figure 8-21 on page 8-29.
• an appropriate antistatic surface to work on. It is advisable to perform this
procedure outside of the shelf. The fibering/functioning of the in-service
circuit packs present in the shelf may be disturbed when performing this
procedure.
• an appropriate antistatic or grounding strap
• general purpose rubbing alcohol
• lint free tissue
• a pair of tweezers
The ideal application temperature range for the label adhesive is from 21°C to
38°C. Application is not recommended if the surface temperature is below
10°C.


Applying a 1M Hazard Level Caution label on NTK552AAE5, NTK552BAE5, NTK552FAE5,
Precautions
CAUTION
Electrostatic discharge (ESD) can damage electrostatic
sensitive devices. Use antistatic protection to avoid damaging
circuit packs.
CAUTION
Risk of damaging equipment
Extreme caution is required when manipulating the circuit
packs to avoid damaging the components on the circuit pack.
Make sure that you do not drop the circuit pack.
Step Action
1 Wear an appropriate ESD personal grounding device to dissipate

electrostatic charges.
2 If you are applying the label on:
• a circuit pack that is not installed in the shelf, go to step 3
• a circuit pack that is installed in the shelf, keep in mind that it is advisable
to perform this procedure outside of the shelf. The fibering/functioning of
the in-service circuit packs present in the shelf may be disturbed when
performing this procedure.
If the circuit pack is in-service and you will perform this procedure outside
of the shelf, follow the instructions in the procedure on replacing an
amplifier module in Fault Management - Module Replacement,
323-1851-545, to remove the circuit pack from the shelf.
If the circuit pack is not in-service and you will perform this procedure
outside of the shelf, follow the instructions in the procedure on inserting
or removing circuit packs, in the Installation technical publication specific
to your shelf type to remove the circuit pack from the shelf.
Go to step 3.


Step Action
3 Confirm you have the correct circuit pack by looking at the name on the top
latch label (Figure 8-31). See Table 8-3 on page 8-28 for target circuit pack
names.
Figure 8-31
Confirming the circuit pack name


Step Action
4 Confirm the target circuit pack by the PEC printed on the barcode label on the
lower latch label (Figure 8-32). See Table 8-3 on page 8-28 for target circuit
pack PECs.
Figure 8-32
Confirming the circuit pack PEC


Step Action
5 Confirm you have the correct circuit pack by looking at the Hazard Level 1
label (Figure 8-33).
Figure 8-33
Confirming the existing label


Step Action
6 Gently clean any dirt or oil from the target surface (that is, the yellow portion)
with rubbing alcohol and a lint free tissue. See Figure 8-34. Avoid damaging
existing label material and its adhesive from over use of rubbing alcohol.
Figure 8-34
Cleaning the target surface


Step Action
7 Carefully remove the patch label from its backing liner. It is recommended to
use a pair of tweezers for ease of handling and to avoid touching the adhesive
surface. See Figure 8-35.
Figure 8-35
Removing the label from the backing liner


Step Action
8 Position the new label so that it covers the current laser label area. See Figure
8-36.
CAUTION
Risk of label misalignment
Do not apply pressure at this point.
Figure 8-36
Positioning the new label


Step Action
9 Apply pressure evenly to finalize the bonding process, taking care to avoid
any sliding motion (which could cause some misalignment). See Figure 8-37.
Allow two to three days for the adhesive to cure completely.
Figure 8-37
Finalizing the label bonding
10 If the circuit pack was in-service and you performed this procedure outside of
the shelf, follow the instructions in the procedure on replacing an amplifier
module in Fault Management - Module Replacement, 323-1851-545, to install
the circuit pack back in the shelf.
If the circuit pack was not in-service and you performed this procedure
outside of the shelf, follow the instructions in the procedure on inserting or
removing circuit packs, in the Installation technical publication specific to your
shelf type to insert the circuit pack back in the shelf.

Procedure 8-2
Applying Hazard Level 3B and/or 1M laser safety
labels on OMC2
Use this procedure to apply Hazard Level 3B laser safety labels on the OMC2
door for the applications described in “Hazard level 3B labeling on the 2-slot
optical module chassis (OMC2)” on page 8-29.
You can also use this procedure to apply Hazard Level 1M safety labels for
UCS, CLMD, and MonCS modules on the back of the OMC2 door.
Prerequisites
Before you start:
• confirm that your application requires the labels (see “Hazard level 3B
labeling on the 2-slot optical module chassis (OMC2)” on page 8-29)
• ensure that you have the following label kits (shipped with the UCS module
and/or the C/L-band mux/demux module (CLMD):
— 415-2998-001 Hazard Level 3B Label Kit (for the front of the OMC2
door)
— 415-2999-001 Hazard Level 3B Label Kit (for the back of the OMC2
door)
• ensure that you have the following label kit (shipped with the UCS, CLMD,
and MonCS modules):
— 415-3007-001 Hazard Level 1M Label, (for the back of the OMC2
door)
Step Action

If you are Then go to
applying a Hazard Level 3B label step 2
applying a Hazard Level 1M label step 7
Applying a Hazard Level 3B label

2 Ensure that the surface where you will apply the label is clear of debris and
clean (see “Applying the Hazard Level 3B label from kit 415-2998-001 to the
front of the OMC2 door”).
3 Remove the required language variant of the Hazard Level 3B label from kit
415-2998-001 and apply it to the front of the OMC2 door as illustrated below.
Apply pressure over the surface of the label to ensure adequate adhesion.


Applying Hazard Level 3B and/or 1M laser safety labels on OMC2
Step Action
Figure 8-38
Applying the Hazard Level 3B label from kit 415-2998-001 to the front of the
OMC2 door
4 Open the OMC2 door to reveal the inside of the door.

clean (see “Applying the Hazard Level 3B label from kit 415-2999-001 to the
inside of the OMC2 door”).
6 Remove the required language variant of the Hazard Level 3B label from kit
415-2999-001 and apply it to the inside of the OMC2 door as illustrated below.
Apply pressure over the surface of the label to ensure adequate adhesion.

Figure 8-39
Applying the Hazard Level 3B label from kit 415-2999-001 to the inside of the
OMC2 door
The OMC2 with UCS module and/or the C/L-band mux/demux module
(CLMD) is now labeled in accordance with IEC 60825-2 Edition 3.2 for a
Controlled Access Location.
ATTENTION
Users of the equipment and service personnel should have appropriate laser safety
training.
Applying a Hazard Level 1M label

Note: Do not apply the Hazard Level 1M label if a Hazard Level 3B label is
required or is already present.
7 Open the OMC2 door to reveal the inside of the door.
clean.
9 Remove the Hazard Level 1M label from kit 415-3007-001.
10 Apply the label to the back of the OMC2 door, aligned with the edge of the
hinge and centered between the marks on the inside of the door. Apply
pressure over the surface of the label to ensure adequate adhesion.
—end—


323-1851-221
9-1
Appendix B: Quick-start turning-up

using the Node Setup application—
examples 9-
The following configuration types are supported by the Node Setup

application:
• “Direct Connect—configuration example” on page 9-2
• “Gateway Connect—configuration example” on page 9-6
Note: The configuration data examples are guidelines and are not to be
copied in a field system. Each company has a different class IP address
range assigned. It is a requirement to cross-check with the appropriate
Ciena customer engineering documentation package (EDP/IDP) and
customer IT/IS department before performing datacomms and NE
provisioning.
Note: For other configuration types, use the Advanced SLAT Assistant Tool.
See “Node setup solutions” on page 2-4 and “Selecting the turning-up solution
for a newly installed system” on page 2-6.

9-2 Appendix B: Quick-start turning-up using the Node Setup application—examples
Direct Connect—configuration example

For the Direct Connect configuration type, see:
• an example of a 6500 shelf in a Direct Connect scenario — Figure 9-1
• a Node Setup data example (Standalone shelf) — Table 9-1 on page 9-3.
For more information on parameter descriptions and possible values, click
on the parameter and be directed to “Node Setup application parameters”
on page 2-47.
A flowchart of the quick-start turning-up of a Standalone shelf using the Node

Setup application is illustrated in Figure 2-2 on page 2-7.
For Node Setup procedure steps, see Procedure 2-4, “Quick-start turning-up
using the Node Setup application”.
Figure 9-1
Direct Connect configuration example (Standalone shelf)
DCN 1.x.x.x
Single
Sing
g shelf TIDs
Dedicated
Dedd DCN LAN drop per TID
DCN routable IP address per shelf
COLAN-X
1.2.2.2 NE1 RJ-45-Ethernet

Appendix B: Quick-start turning-up using the Node Setup application—examples 9-3
Table 9-1
Direct Connect with basic Node Setup parameters—Standalone data example (NE1 in Figure 9-1)
Task Parameter NE1 values Procedure 2-4,

“Quick-start
turning-up using
the Node Setup
application”
step reference
NE NE Name NE1 step 6

Identification (Must be entered by user.)
The Date and Time are provisioned automatically to the date and time of
the user’s PC, converted to GMT.
Optional step for the Date and Time parameters: To change after Node Setup is
complete, use Site Manager->Node Information->Node Information tab.
NE Configuration Shelf Type Standalone step 10
Shelf Number (Must be entered by user.)
Shelf IP Address 1.2.2.2

(Default is blank.)
OSPF Network Area (Default is blank.)
The following Advanced Parameters are provisioned automatically.

Optional steps for these parameters:
• To view or change during Node Setup, open the NE Configuration Advanced
Parameters panel.
• To change after Node Setup is complete, use Site Manager.
Attention: The tool remembers the Advanced Parameter settings and
automatically reuses them when the next shelf is set up. The information is
stored in the slat_preferences.xml file at the following Site Manager installation
location:
If necessary, before you move on to setting up another network and/or another
TID, delete the slat_preferences.xml file to restore the defaults.
NE Mode Default is SONET. step 11
NDP Mode Default is ENABLED.
Alarm Correlation Default is OFF.
Shelf Synch Default is YES.
(continued)

Table 9-1

“Quick-start
turning-up using
the Node Setup
application”
step reference
NE Configuration Air Filter Replacement Alarm Default is DISABLE. step 11

(continued)
Air Filter Replacement Timer Default is 731 or 730.

(in days)
Auto Delete on LOS Default is NO.
TCA Suppression Default is DISABLED (No).
Alarm Info Default is Disabled.
Auto Facility Provisioning Default is ON.
Shelf AutoEquipping If NE Mode selection is

SONET or SDH-J, default
is ENABLED.
SDH, default is DISABLED.
CS Control Default is DISABLED.
The following NE Configuration details are provisioned automatically.

Optional step for these parameters:
• To change, use Site Manager->Configuration->Comms Setting Management
after Node Setup is complete.
OSPF Router with Off not applicable

Autonomous System Border
Router (ASBR)
TID Consolidation Enabled
TID Consolidation Primary Enabled
(continued)

Table 9-1

“Quick-start
turning-up using
the Node Setup
application”
step reference

• To change, use Site Manager->Configuration->Node Information -> System
after Node Setup is complete.
Control Mode Default Default is Fixed ITU not applicable
Default Filter-edge Spacing Default is 6.250

(GHz)
COLAN-X IP Address 1.2.2.2 step 15

Provisioning
Subnet Mask 255.0.0.0
- Basic Node Setup complete -

Gateway Connect—configuration example

For the Gateway Connect configuration type, see:
• an example of 6500 shelves in a Gateway Connect scenario — Figure 9-2
• a Node Setup data example for a Member shelf — Table 9-2 on page 9-7
• a Node Setup data example for a Primary with Members shelf — Table 9-3
on page 9-10
For more information on parameter descriptions and possible values, click
on the parameter and be directed to “Node Setup application parameters”
on page 2-47.
Flowcharts of the quick-start turning-up of the shelves using the Node Setup
application are illustrated in:
• Figure 2-3 on page 2-8 — Primary with Members shelf
• Figure 2-4 on page 2-9 — Member shelf
For Node Setup procedure steps, see Procedure 2-4, “Quick-start turning-up
using the Node Setup application”.
Figure 9-2
Gateway Connect configuration example (Primary with Members shelf and Member shelves)
DCN 1.x.x.x
Dedicated DCN LAN drop per TID

Ded
DCN routable IP address per shelf
COLAN-X
GNE
Shelf 1 1.3.3.2
(Primary)
TID A GNE Proxy ARP GNE
1.3.3.4 Shelf 3
1.3.3.3 Shelf 2 (Member)
(Member) TID A
TID A

Table 9-2
Gateway Connect with basic Node Setup parameters—Member data example (Shelf 2 in Figure
9-2 on page 9-6)
Task Parameter Shelf 2 Procedure 2-4, “Quick-start

turning-up using the Node Setup
application” step reference
NE NE Name Shelf 2 step 6

Identification (Must be entered by
user.)
The Date and Time are provisioned automatically to the date and time of the
user’s PC, converted to GMT.
NE Configuration Shelf Type Member step 10
Shelf Number (Must be entered by

user.)

(Default is blank.)

Parameters panel.
Attention: The tool remembers the Advanced Parameter settings and automatically
If necessary, before you move on to setting up another network and/or another TID,
delete the slat_preferences.xml file to restore the defaults.
NDP Mode Default is ENABLED

(ON).
(continued)

Table 9-2
9-2 on page 9-6) (continued)

NE Configuration The following Advanced Parameters are provisioned automatically.

(continued) (continued)
Air Filter Replacement Default is DISABLE. step 11

Alarm
Air Filter Replacement Default is 731 or 730.

Timer (in days)
TCA Suppression Default is DISABLED

(No).
Auto Facility Default is ON.

Provisioning

SONET or SDH-J,
default is ENABLED.
SDH, default is
DISABLED.
(continued)

Table 9-2
9-2 on page 9-6) (continued)

NE Configuration The following NE Configuration details are provisioned automatically.

(continued) Optional step for these parameters:
• To change, use Site Manager->Configuration->Comms Setting Management after
Node Setup is complete.
OSPF Router with Off not applicable

Autonomous System
Border Router (ASBR)
TID Consolidation Disabled

Primary
ILAN-IN and ILAN-OUT ports are created with

un-numbered IPs and OSPF circuits using the
OSPF Network Area entered.

• To change, use Site Manager->Configuration->Node Information -> System after
Default Filter-edge Default is 6.250

Spacing (GHz)

Table 9-3
Gateway Connect with basic Node Setup parameters—Primary with Members data example
(Shelf 1 in Figure 9-2 on page 9-6)

NE NE Name Shelf 1 step 6

Identification (Must be entered by
user.)
The Date and Time are provisioned automatically to the date and time of the
user’s PC, converted to GMT.
NE Configuration Shelf Type Primary with Members step 10
Shelf Number (Must be entered by

user.)

(Default is blank.)
OSPF Network Area (Default is blank.)

Parameters panel.
Attention: The tool remembers the Advanced Parameter settings and automatically
If necessary, before you move on to setting up another network and/or another TID,
delete the slat_preferences.xml file to restore the defaults.
NDP Mode Default is ENABLED

(ON).
(continued)

Table 9-3
(Shelf 1 in Figure 9-2 on page 9-6) (continued)

Air Filter Replacement Default is DISABLE. step 11

Alarm
Air Filter Replacement Default is 731 or 730.

Timer (in days)
TCA Suppression Default is DISABLED

(No).
Auto Facility Default is ON.

Provisioning

SONET or SDH-J,
default is ENABLED.
SDH, default is
DISABLED.

• To change, use Site Manager->Configuration->Comms Setting Management after
OSPF Router with On not applicable

Autonomous System
Border Router (ASBR)

Primary
ILAN-IN and ILAN-OUT ports are created with

un-numbered IPs and OSPF circuits using the
OSPF Network Area entered.
(continued)

Table 9-3
(Shelf 1 in Figure 9-2 on page 9-6) (continued)

NE Configuration The following NE Configuration details are provisioned automatically.

(continued) Optional step for these parameters:
• To change, use Site Manager->Configuration->Node Information -> System after
Default Filter-edge Default is 6.250

Spacing (GHz)
Proxy ARP GNE Start IP Address (Must be entered by step 13

user.)
End IP Address (Must be entered by

user.)
COLAN-X IP Address 1.3.3.2 step 15

Provisioning
Subnet Mask 255.0.0.0

10-1
Appendix C: Zero touch provisioning 10-

• “Overview” on page 10-2
• “Support details” on page 10-6
• “Operational considerations” on page 10-7
• “Prerequisites” on page 10-7
• “Triggering ZTP out-of-the-box” on page 10-7
• “ZTP details” on page 10-8
• “DHCP options” on page 10-10
• “ZTP sequence diagrams” on page 10-11
• “ZTP files” on page 10-13
• “6500 DHCP relay agent provisioning” on page 10-18
• “Security” on page 10-19
• “ZTP completion” on page 10-20
• “ZTP error handling” on page 10-21
• “Configuration examples” on page 10-30

COLAN Central office local area network
DCC Data communication channel
DCN Data communications network
DHCP Dynamic host configuration protocol
ESAM Enhanced service access module
FTP File transfer protocol
GCC General communications channel

10-2 Appendix C: Zero touch provisioning
GNE Gateway network element

HTTP Hypertext transfer protocol
ILA Integrated line amplifier
ILAN Intershelf local area network
ID Identifier
IP Internet protocol
IPv4 Internet protocol version 4
IPv6 Internet protocol version 6
LAN Local area network
NE Network element
NOC Network operator center
OSC Optical service channel
RNE Remote network element
ROADM Reconfigurable optical add/drop multiplexer
SAM Service access module
SFTP Secure file transfer protocol
SP Shelf processor
SRA Single line Raman amplifier
SZTP Secure zero touch provisioning
TID Target identifier
UPC User privilege code
XML Extensible Markup Language
ZTP Zero touch provisioning
Overview
Zero touch provisioning (ZTP) is a feature that simplifies the initial
commissioning of a shelf from the perspective of the installer by allowing the
shelf to retrieve its provisioning information and subsequently provision itself
automatically. Depending on the requirements of a given customer’s
operations, the provisioning information could range from the minimal amount
required to make the shelf visible on the network (for example, basic shelf and
data comms provisioning) to a larger set of commands including equipment
and services provisioning. If the shelf receives the minimal amount of
provisioning information, the remainder of the provisioning can be performed
remotely via Site Manager or the network management system (NMS).

ZTP makes use of standard protocols, such as dynamic host configuration

protocol (DHCP), to acquire a temporary address and pointers to external
servers and files, and file transfer protocols to retrieve the appropriate
provisioning files.
Resources required by ZTP, such as DHCP and TFTP/FTP/SFTP servers, are

located in the external DCN. An uncommissioned 6500 acts as a DHCP client.
A commissioned 6500 can act as a DHCP relay agent for subtending
uncommissioned 6500s. In this way, a network build-out using ZTP happens
in a 'lily pad' manner. 6500 can also act as a DHCP relay agent for non-6500
devices in a 'plain relay agent' mode. To become a DHCP relay agent, a 6500
must be provisioned as one, either through ZTP itself (when initially
commissioned) or subsequent to the initial ZTP provisioning.
Figure 10-1 shows the ZTP components. The DHCP server shown could be
an actual server existing on the same L2 network as the 6500s, or could
represent a DHCP relay agent, in which case the actual DHCP server could
be located deeper inside the customer’s external DCN. The DHCP and ZTP
configuration server functions can exist on the same physical machine or
separate machines (shown as separate machines in Figure 10-1).
Figure 10-1
ZTP components

Figure 10-1 shows directly-connected 6500s as DHCP clients. Figure 10-2

shows directly-connected 6500 shelves which are fully provisioned and acting
as DHCP relay agents for uncommissioned line amplifiers subtending over
OSC. In this case, the line amplifiers are the DHCP clients.
Figure 10-2
6500 DHCP relays and clients
Figure 10-3 shows the steps involved in using ZTP. At a high level, those steps
are:
• Preparation of the external infrastructure to support ZTP.
— Configuration of the DHCP server and, if applicable, DHCP relay
agent(s).
— Creation of boot and CLI configuration files for each shelf. Refer to
“ZTP files” on page 10-13 for details of these files.
— Storage of the boot and configuration files on external
TFTP/FTP/SFTP servers.
• Physical installation of the hardware.
• A DHCP transaction between the hardware and a DHCP server. This may
also involve a DHCP relay agent.
• Retrieval of boot and configuration files to allow the shelf to provision itself.

Figure 10-3
High-level ZTP steps
Terminology
For the 6500 feature, the term Zero Touch Provisioning (ZTP) is used in a
generic sense to be consistent with other Ciena products and the industry in
general. The term ‘touch’ is from the installers perspective, and refers to the
steps, other than the physical installation, required to allow a new shelf to
provision automatically.
6500 supports standard DHCP options that allow flexibility in how a given
customer uses ZTP, and the number of touches required is a factor of how
these options are used to support the customer's work flow.
To achieve true ‘zero touch’, a topology-based ZTP flow can be used where
provisioning information is supplied to a new shelf based on its location in the
network (where it is connected). True ‘zero touch’ does not depend on the
physical shelf installed in that location, the location determines its
provisioning.
A ‘one touch’ flow does not use topology but instead identifies a new shelf
based on its serial number. In this case the ‘touch’ is the correlation of the
serial number with the appropriate provisioning information for that shelf. ‘One

touch’ does not depend on where the shelf is connected in the network, the
serial number determines its provisioning. The correlation of serial number to
provisioning information can be done before or after the shelf is physically
installed. In the case where the serial number correlation is done before the
installation, it is necessary to ensure the shelf with the given serial number is
installed in the correct location in the network. In the case where the serial
number correlation is done after the installation, any shelf can be installed but
it is subsequently necessary to take that serial number and link it to the correct
DHCP provisioning and configuration files for that serial number.
Refer to “DHCP options” on page 10-10 for more detail on the DHCP options.
Support details
The following list details the support considerations for 6500 ZTP:
• Supported on SP2 and SPAP2 w/2xOSC.
• Supported on all shelf variants, subject to the supported SPs previously
mentioned.
• Supported regardless of intended shelf function (for example, transponder
or Photonic).
• Supported on shelves directly connected to the external DCN via
COLAN-X (for example, shelves that will become GNEs).
• Supported on shelves not directly connected to the external DCN (shelves
connected via unnumbered ILAN or OSC to an already-commissioned
6500). In terms of OSC, ZTP is supported over the following OSC cards:
— 2xOSC
— SPAP2 w/2xOSC
— SRA
— SAM
— ESAM
• When enabled, ZTP is active on the COLAN-X, ILAN-IN, ILAN-OUT, and
OSC interfaces
• The 6500 DHCP relay agent can be enabled on COLAN-X, COLAN-A,
ILAN, and OSC interfaces.
• Supported in TIDc configurations and non-TIDc configurations.
• Supported in both DCN-routable and non-DCN-routable (Private-IP)
configurations.

Operational considerations
The following should be considered regarding ZTP:
• Not supported on 6500 T-series.
• Not supported over GCC.
• ZTP is supported for IPv4 only.
• Configuration files are supported in CLI format only.
• Generally, ‘create’ and ‘set’ CLI commands are supported.
• Interactive commands are not supported.
• When using the CLI ‘topology slot-seq set’ and ‘topology tid-slot-seq set’
commands, set the VALIDATION parameter to OFF. The create OTS
commands need time to complete and the ‘topology slot-seq set’ and
‘topology tid-slot-seq set’ CLI commands will fail if run when the
equipment creation is not completed and VALIDATION is ON.
• HTTP/HTTPS are not supported for file transfer.
• Upgrades are not supported over ZTP.
• For shelves that will become TID-consolidated after ZTP completes, refer
to “TIDc and Shelf-Sync” on page 10-17 for more information.
Prerequisites
To use ZTP, you require:
• Detailed network design information as input to the following items.
• A DHCP server configured to support ZTP, including the DHCP options
described in this chapter.
• Optionally, one or more DHCP relay agents in the external DCN
configured to reach the actual DHCP server(s).
• One or more file servers supporting TFTP, FTP, and/or SFTP where the
boot and configuration files can be accessed.
• Boot and configuration files for each shelf.
• An Ethernet Loopback Plug inserted in the craft port of the SP2/SPAP2.
See “Triggering ZTP out-of-the-box” on page 10-7.
Triggering ZTP out-of-the-box

6500 supports two commissioning modes 'out-of-the-box':
• Non-ZTP - this is the pre-Release 12.3 manual mode and is the default
behavior.
• ZTP - the ZTP mode is triggered on an uncommissioned shelf by the
presence of an RJ45 Ethernet Loopback Plug (ELP), NTTC09FA, in the
RJ45 craft port of the SP2/SPAP2 when the SP2/SPAP2 is powered up.

ZTP can also be triggered on an uncommissioned shelf post-power-up by

restarting the SP2/SPAP2 with an RJ45 ELP in the RJ45 craft port. If there
are dual SP2s, a RJ45 ELP should be inserted in both SP2s.
Additional information on RJ45 ELP:

• The RJ45 ELP can be left in the craft port indefinitely. It is only referenced
during restart on an uncommissioned shelf.
• The RJ45 ELP can be removed after ZTP is complete, for example if a
craft PC needs to be connected to the craft port.
ZTP details
ZTP flow - topology based
Figure 10-4 shows the sequence of steps in the ZTP process using a
topology-based work flow. In this case, the network plan determines where
and how each shelf will be connected (for example, shelf-A ILAN-OUT
connected to shelf-B ILAN-IN). The DHCP server is configured to incorporate
DHCP option 82 information that is provided by a DHCP relay agent so that
the appropriate information can be assigned to each shelf.
Figure 10-4
ZTP topology-based flow

The sequence is as follows:

1 The boot and configuration files are prepared for each shelf according to
network plan.
2 By incorporating DHCP option 82 criteria which identify where a shelf is
connected in the network, the DHCP server is configured to assign
appropriate addresses and provide pointers to the boot files for each shelf.
The boot and configuration files are stored on external file servers.
3 The installer completes the physical installation of the shelf, connecting it
according to the plan.
4 The uncommissioned shelf interacts with the DHCP server, possibly via a
DHCP relay agent, to acquire a temporary address and pointer to a boot
file.
5 The shelf retrieves its boot file. The shelf retrieves the configuration file
and processes the CLI commands to provision itself.
ZTP flow - client-ID based
Figure 10-5 shows the sequence of steps in the ZTP process using a client-ID
based flow. In this case, the serial number that is provided in DHCP option 61
(client-ID) is used by the DHCP server to associate the correct address and
provisioning information to provide to a shelf. The flow shown assumes the
serial number of the shelf is known before the physical installation, and
therefore the specific shelf with that serial number must be installed in the
correct location in the network.
Figure 10-5
ZTP client-id based flow

It is also possible that the physical installation may occur first. In this case, the
serial number of the installed shelf must be fed back to the planning and/or
operations organizations to correlate with the appropriate provisioning
information.
The sequence is as follows:

1 The boot and configuration files are prepared for each shelf according to
network plan. The serial number for each shelf is known.
2 The DHCP server is configured to assign appropriate addresses and
provide pointers to the boot files for each shelf based on DHCP option 61
(client-ID) that each 6500 client includes in its DHCP discover and request
messages. The boot and configuration files are stored on external file
servers.
3 The installer completes the physical installation of the shelf.
4 The uncommissioned shelf interacts with the DHCP server, possibly via a
DHCP relay agent, to acquire a temporary address and pointer to a boot
file.
5 The shelf retrieves its boot file. The shelf retrieves the configuration file
and processes the CLI commands to provision itself.
DHCP options
The following DHCP options are used for 6500 ZTP.
Option 66
This is a standard DHCP option that is used to specify the location of an
external file server. More details on how it may be used are given in “ZTP files”
on page 10-13.
Option 67
This is a standard DHCP option that is used to specify the boot file name.
More details on how it may be used are given in “ZTP files” on page 10-13.
Option 60
This is a standard DHCP option that is used to identify the vendor class. The
vendor class can be used in conjunction with other options (for example, 61 or
82) to target the boot and configuration files to a specific shelf. The format
used on 6500 is:
[vendor code]-[product type]-[shelf type]
where:
— Ciena vendor code = 1271
— Product type is:
– 00011600, for 6500-S
– 00011D00, for 6500-T

— Shelf type is:

– 000, for 14-slot
– 001, for 32-slot
– 002, for 7-slot
– 004, for 2-slot Type-2
– 005, for 7-slot Type-2
– 006, for 7-slot packet optical
– 016, for 6500-T 12-slot
– 017, for 6500-T 6-slot
– 018, for 6500-T 24-slot
Note: 6500 T-series is not supported in this release.
Option 61
This is a standard DHCP option that is used to specify the client identifier. On
6500, the client identifier is the serial number of the shelf.
Option 77
This option is sent by the 6500 DHCP client to indicate the software release
running on the client. The format contains type/value pairs where type ‘0’
denotes software release and the release value is ‘xx.xx’, for example:
‘0/12.40’.
Option 82
This is a standard DHCP option that is added by a DHCP relay agent to
identify the relay agent name and port the DHCP request was received on.
The format is:
• Agent Circuit ID sub-option (sub-option 1): ILAN-IN, ILAN-OUT,
COLAN-X, COLAN-A, or OSC-slot-port
• Agent Remote ID sub-option (sub-option 2): TID-shelf.circuit-id
Note: The circuit-id is contained in both sub-option 1 and sub-option 2, as
this can be helpful with some DHCP server implementations when parsing
option 82 information.
ZTP sequence diagrams

This section provides details of the DHCP interactions and file transfers for two
6500 scenarios:
• 6500 shelf directly connected to the external DCN via COLAN-X
• 6500 shelf not connected to the external DCN

Directly connected 6500

ZTP is supported for a 6500 shelf directly connected to the external DCN
using COLAN-X. It is assumed the COLAN-X will become a numbered
interface. Only COLAN-X is supported as a numbered interface for ZTP.
In this scenario, DHCP operates as it would for any typical host, with DHCP
discover, offer, request, and acknowledgment packets exchanged with a
DHCP server, possibly with a DHCP relay agent in between. The IP
address/mask received via DHCP is applied to the COLAN-X interface along
with a default gateway so that the shelf can retrieve the boot file and
configuration file to configure itself. Figure 10-6 shows this scenario.
Figure 10-6
Directly-connected 6500
Non-directly connected 6500

ZTP is supported for 6500 shelves not directly connected to the external DCN,
such as those connected via an unnumbered ILAN or OSC to a commissioned
shelf.
In this scenario, special handing is required as the interface is unnumbered.

The special handling is performed by the 6500 relay agent, which acts on
behalf of the 6500 client as shown in Figure 10-7. Following the DHCP
acknowledgment from the DHCP server, the 6500 relay agent:
• retrieves the boot and configuration files for the client
• extracts a subset of information required to provision basic data
communications on the client

• inserts the basic data communications information in the DHCP

acknowledgment sent to the client using DHCP options 43 and 231 to 235.
This is referred to as ‘option conversion’ in Figure 10-7.
Once the client provisions this basic information, it can then retrieve the boot
file and configuration file itself to provision itself.
Figure 10-7
Non-directly connected 6500
ZTP files
A boot file and CLI configuration file are required for each shelf. These files
must be located on a file server supporting either TFTP, FTP, and/or SFTP.
Boot file
The boot file is an XML file containing control information which guides the
ZTP process, including:
• a pointer to the configuration file
• instructions on what action to take if errors are encountered
• optional instructions on how to transfer files

The following is an example of a boot file with detailed descriptions of the

fields.
<XmlCienaCommandFile>
<XmlCmdPlatformClass
name="6500"
version="12.60"
configFilePath="6500_ztp/65_0020_cmd"
configFileRule="retryOnFailure"
ztpTimeout="60">
</XmlCmdPlatformClass>
</XmlCienaCommandFile>
Fields:
• name: must be ‘6500’
• version: both the 6500 relay agent and 6500 client check that the version
specified in the boot file matches the software version they are running.
The match must be exact, but a trailing wild card ‘*’ is allowed in the boot
file. The following table shows examples on how matching works:
Version Shelf release Result
12.0 12.0 Match
12. 12.0 Mismatch
12.* 12.0 Match
12.0 12.1 Mismatch
12.*1 12.1 Not supported - mismatch
• configFilePath: location of the configuration file. This can be a URL or a

relative path used along with DHCP option 66.
• configFileRule: specifies the behavior if an error is encountered while
processing the configuration file. The possible values and behaviors are:
— retryOnFailure: the shelf decommissions itself and restarts the ZTP
process if any commands fail to execute.
— ignoreOnFailure (default): the shelf completes the ZTP process even
if some commands failed to execute.
— stopOnFailure: the shelf stops the ZTP process at the first failed
command.
• ztpTimeout (optional) specifies the time (in minutes) between retries. The
default is 60. The range is 30-1440. After 3 retries, the interval
automatically moves to 1440.

Configuration file
The configuration file contains the CLI commands used to provision the shelf.
The file can include:
• only a minimal set of commands just to provision basic shelf parameters
and data comms to make the shelf visible on the network
or
• a larger set of commands including equipment and facility provisioning
and services, depending on the requirements for a given customer.
The format of the file is one CLI command per line. Comment lines are
indicated using a leading hash character ('#'). The following is an example of
a minimal set of commands:
system sid set name “SITEZTP-3103”
shelves shelf create SHELF-1 bay-num 1 location “” primary
enable tidc enable site-id 1 site-name “SITELTP”
system config set ne-mode sonet osc-mode disabled min-cooling
highflow
comms ip create shelf-1 ip-addr 10.1.1.133 netmask
255.255.255.255
comms lan create ilan-1-in
comms ip create ilan-1-in ip-addr 0.0.0.0 netmask
255.255.255.255
comms ospf router create shelf-1 router-id 10.1.1.133
comms ospf circuit create shelf-1 net-area 1.1.1.1
comms ospf circuit create ilan-1-in net-area 1.1.1.1
# OSC provisioning
equipment config create 2XOSC-1-2 prov-pec NTK554BA
equipment config create P155M-1-2-1 prov-pec NTK592NB
equipment config create P155M-1-2-2 prov-pec NTK592NB
oscs osc create OSC-1-2-1
comms ospf circuit create osc-1-2-1 net-area 1.1.1.1
# ESAM provisioning
equipment config create esam-1-6 prov-pec NTK552JT
equipment config create esam-1-6 prov-pec NTK552JT
comms ospf circuit create OSC-1-6-2 net-area 1.1.1.1
Rules:
• In this release, only CLI format is supported for these commands.
• The name of the configuration file is limited to a maximum of
128 characters.
• The commands are case insensitive.

• A hash ('#') character at the beginning of a line can be used to indicate that
the line contains comments.
• The shelf can process the CLI commands in an arbitrary order, but for
performance reasons, it is recommended to adhere to a logical ordering.
For example, provision basic shelf parameters before equipment,
equipment before facilities, services after supporting equipment and
facilities.
• Basic shelf provisioning information should be ordered as follows:
— Set the system identifier: system sid set name …
— Create shelf object: shelves shelf create …
— Edit system object: system config set ne-mode …
— Create shelf IP: comms ip create shelf-x …
— Other comms provisioning, such as LAN ports, IP addresses, and
routing.
• In general, it is recommended that auto-provisioning is not used in
conjunction with ZTP.
Boot file transfer

The boot file can be transferred using TFTP, FTP, or SFTP and is located by
concatenating DHCP options 66 and 67.
Table 10-1 shows examples on how options 66 and 67 can be used. URL
format is supported as per RFC 3986, for example:
ftp://[<userID>[:<password>]]@<host>[:<port>]/<directory_path>
[/prefix]
Note: If the URL format is not used for option 66, the transfer protocol will
be TFTP, as in the first example in Table 10-1.
Table 10-1
Boot file - option 66 and 67 examples
Option 66 Option 67
10.100.17.44 6500_ztp/NNTM01NZ003V_boot
tftp://10.100.17.44/6500_ztp NNTM01NZ003V_boot
ftp://ZtpUser:[email protected]/6500_ztp NNTM01NZ003V_boot
ftp://ZtpUser:[email protected] 6500_ztp/NNTM01NZ003V_boot
sftp://ZtpUser:[email protected] 6500_ztp/NNTM01NZ003V_boot

Configuration file transfer

The configuration file can be transferred using TFTP, FTP, or SFTP and is
located based on the value in configFilePath and possibly option 66:
• if configFilePath is a full URL, option 66 is ignored.
• if configFilePath is only a path, option 66 and configFilePath are
concatenated.
As per the boot file, the URL format is supported for the configuration file.
Table 10-2 shows examples of the use of option 66 and/or configFilePath. The
first two rows show cases where, since configFilePath specifies a complete
URL, the option 66 is ignored.
Table 10-2
Configuration file - option 66 and configFilePath examples
Option 66 configFilePath
ftp://ZtpUser:[email protected] ftp://ZtpUser:[email protected]/
(ignored) 6500_ztp/65_0020_cmd
sftp://ZtpUser:[email protected] sftp://ZtpUser:[email protected]
(ignored) /6500_ztp/65_0020_cmd
ftp://ZtpUser:[email protected] 6500_ztp/65_0020_cmd
sftp://ZtpUser:[email protected] 6500_ztp/65_0020_cmd
TIDc and Shelf-Sync

Shelf-sync is a feature which synchronizes certain data within a consolidated
TID. As such, some provisioning applied at the primary shelf is synchronized
with the member shelves, overwriting any provisioning that may already have
been applied at the member shelf. With shelf-sync enabled, it is
recommended that this provisioning is done only on the primary shelf when
using ZTP.
The following outlines data that is synchronized using shelf-sync.

System
system config-system set
system config-alm set
system config-l0 set
TACACS+
security tacacs-server set
security authmode set
tacacs config set

PODS (Photonic Optical Data Synchronization)

topology tid-slot-seq set
Alarm Profiles
almprofile default set
almprofile attribute set-profile
almprofile name set
PM profiles
PM threshold synchronization is triggered by setting the threshold level for any
facility for a given Profile ID. As an example, the cli command below sets the
ES-OTU (NEND, RCV, 15-min) to 6 on PROFILE4. This can be executed with
respect to any facility and montype to trigger the sync.
pm otuttp threshold set SHELF-1 dest-profile-id PROFILE4 dirn
RCV locn NEND mon-type ES-OTU thlev 6 tmper 15-MIN
6500 DHCP relay agent provisioning

In order to act as a DHCP relay for subtending devices, the DHCP relay agent
needs to be provisioned on a given 6500. This provisioning can occur during
the initial commissioning of the shelf, using ZTP, or could occur subsequent to
the ZTP process.
Enabling the DHCP relay agent involves two basic steps, with a possible third
step depending on the mode chosen. Refer to “Procedures” on page 10-42 for
command details.
• Provisioning an external DHCP server. In Release 12.3, only one external
server is supported. The server must be provisioned before enabling the
DHCP relay agent.
• Enabling the DHCP relay agent and specifying the mode. There are two
supported modes:
— AUTO: in this mode, the DHCP relay agent is enabled on all inter-shelf
interfaces (except COLAN-X), which include COLAN-A, ILAN-IN,
ILAN-OUT, and OSC.
— MANUAL: in this mode, the user must manage which interfaces the
relay is enabled on (see next item).
• If the mode is MANUAL, you must provision the interfaces on which to
enable the DHCP relay agent. This step is required if setting an interface
to PLAINRA mode.
The default behavior for a 6500 DHCP relay agent supports ZTP for other
6500 shelves which, because they are supported over unnumbered
interfaces, require special handling. However, 6500 can also act as a DHCP
relay agent for non-6500 devices, such as CESD and
Waveserver/WaveserverAi. This is referred to as 'PLAINRA', or plain relay

agent. In the PLAINRA mode, the relay agent behaves in a generic way which
assumes that the subtending client is connected over a numbered interface.
PLAINRA defaults to OFF, but can be enabled using the DHCP RA (relay
agent) interfaces command.
The following rules apply to DHCP relay agent provisioning:

• To manually specify DHCP relay agent interfaces, the DHCP relay mode
must be manual.
• To manually add a DHCP relay agent interface, the interface must have IP
provisioning (numbered or unnumbered).
• PLAINRA is only allowed on numbered interfaces.
• If an interface has a manually provisioned DHCP relay agent,
modifications of the IP or Layer-2 provisioning are not allowed.
Modifications are allowed if the DHCP relay agent mode is AUTO.
• For a network that will use a Private-IP GNE configuration, the following
DHCP relay agent provisioning rules apply:
— The Private-IP GNE(s) relay agent(s) must be provisioned to use the
external DHCP server.
— Non-GNE relay agent shelves must be provisioned to use the shelf-IP
address of a Private-IP GNE as the DHCP server.
The following is an example of DHCP relay agent provisioning using CLI

commands:
comms dhcp rasrvrinfo create dhcprasrvr-1-1 srvrip 10.1.99.170
comms dhcp relay set shelf-1 mode manual
comms dhcp raif create dhcpra-1-1 circuit ilan-1-in
Security
A commissioned 6500 shelf is considered to be trusted since it can use secure
protocols, such as SFTP, for file transfers and RADIUS/TACACS+ for
authentication. An uncommissioned 6500 client is considered untrusted.
Included in the handling for remote shelves over unnumbered interfaces (see
“Non-directly connected 6500” on page 10-12), the 6500 relay agent
implements security features to protect from untrusted clients. These include
removing any references to the external ZTP infrastructure (for example,
options 66/67) in messages sent to the client, encrypting the configuration
data contained in option 43, and ensuring only the specific 6500 shelf that the
configuration data is intended for can decode it.

Figure 10-8
ZTP security
The following security commands are not supported by ZTP:

• User provisioning (changing of passwords, adding new users, editing
passwords for users)
• RAMAN password provisioning
• Release server provisioning
• OSPF password/MD5 password provisioning
• URL with suppressed passwords (if a user id is supplied and no password
is supplied, CLI prompts for the password after the command has been
entered). URL could be used to upload a server certificate for the
REST/gRPC servers during ZTP.
6500 provides the ability to encrypt RADIUS, TACACS+, or

challenge/response shared secrets which then can be entered in CLI or
included in the ZTP configuration file (see “Encrypting and provisioning
shared secrets” on page 10-52).
ZTP completion
ZTP generates an event to indicate successful completion or partial
completion.

Successful completion indicates the ZTP process is complete and no errors

were encountered. For example:
"SHELF-1:SYSPROV_C,TC,01-01,00-07-24,NEND,NA,,,:\"System
Provisioning Complete\",NONE:0100000000-0000-2115,:YEAR=201
8,MODE=NONE,ADDITIONALINFO=\"Zero Touch Provisioning\""
Partial completion indicates that ZTP has encountered errors. For example:
"SHELF-1:SYSPROV_PART_C,TC,01-01,00-07-49,NEND,NA,,,:\"Syst
em Provisioning Partially Complete\",NONE:0100000000-6125-2
116,:YEAR=2018,MODE=NONE,ADDITIONALINFO=\"Zero Touch
Provisioning\""
Note: If the ‘configFileRule' in the boot file indicates 'retryOnFailure', a

partial completion event may be generated each time a retry occurs.
ZTP error handling

6500 provides detailed information on both DHCP client and DHCP relay
agent to troubleshoot problems encountered with the ZTP process. This
section describes the commands that can be used and the associated output.
If ZTP encounters errors, it may be necessary to connect to the craft port
directly to retrieve this information, as the shelf may not be accessible
remotely.
6500 DHCP client

Commands
The command is supported through TL-1 and CLI.
TL1:
RTRV-STATS-ZTP:::CTAG;
CLI:
comms ztpstats show shelf-x
Response
The response contains three types of information:
• Status: Possible values are Running, Completed, and Not Run. This
information is always displayed. Not Run indicates one of the following
conditions:
— ZTP disabled
— ZTP not used
• Counters for various types of conditions. Only those with non-zero counts
are displayed.
• For any failed commands, the line numbers in the configuration file
associated with the failures. This allows the failed commands to be
identified and corrected.

The following is an example of the output. For illustrative purposes, all the
fields are shown, even though only non-zero fields are normally displayed.
ZTP Status Completed
0 Lease Acquired
0 Lease Released
0 Lease error: no parameters received
0 Lease error: netmask missing or 0
0 Lease error: IP is 0
0 Lease error: IP is broadcast
0 Lease error: gateway missing or 0
0 Lease error: IP is multicast
0 Lease error: gateway is not unicast
0 Lease error: subnet overlapping
0 Internal Protocol Error
0 DHCP Client reboot
0 No option 66 in the DHCP Offer
0 No option 67 in the DHCP Offer
0 Bootfile: config file name exceeds max length
0 Bootfile name exceeds max length
0 DHCP Option 66 exceeds 255 characters
0 Internal Error
0 DHCP option 67 exceeds 128 characters
0 DHCP option 66 plus 67 exceed 128 characters
0 DHCP option 66 plus 67 URL exceed 247 characters
0 Username exceeds maximum length
0 Password exceeds maximum length
0 No username or password provided
0 DHCP option 66 URL invalid file transfer mode
0 Config file invalid file transfer mode
0 Bootfile invalid file transfer mode
0 FTP/SFTP/TFTP failed to get the bootfile
0 Bootfile syntax error
0 Bootfile name mismatch
0 Bootfile name missing
0 Bootfile release mismatch
0 Bootfile release missing
0 Bootfile parse URL Fail
0 FTP/SFTP/TFTP Failed to get the configuration file
0 FTP Parse URL Fail
0 SFTP Parse URL Fail
0 The configurations file is empty
0 DCHP messages dropped due to invalid length or checksum
The number of unexecuted CLI commands is 20.
The line number for each unexecuted command is shown below.
8 50 51 54 55 56 57 58 63 64
65 66 67 68 69 70 71 72 73 74

A description of the counter fields is given in Table 10-3.
Table 10-3
6500 DHCP client - error counter field descriptions
Field Description
Lease Acquired DHCP lease has been acquired.
Lease Released DHCP lease has been released.
Lease error: no parameters received No parameters were present in the lease.
Lease error: netmask missing or 0 The subnet mask in the DHCP offer was missing or zero.
Lease error: IP is 0 The IP address in the DHCP offer had a value of zero.
Lease error: IP is broadcast The IP address in the DHCP offer was a broadcast address.
Lease error: gateway missing or 0 The gateway IP in the DHCP offer was missing or zero.
Lease error: IP is multicast The IP address in the DHCP offer was a multicast address
rather than unicast.
Lease error: gateway is not unicast The gateway IP provided in the DHCP offer was not
unicast.
Lease error: subnet overlapping The lease subnet overlaps with a numbered interface.
Internal Protocol Error Contact Ciena for assistance.
DHCP Client reboot The DHCP client has restarted sending request messages
on a particular interface.
No option 66 in the DHCP offer Option 66 was not found in the DHCP offer.
Bootfile: config file name exceeds max The maximum length for the configuration file is 128
length characters.
Bootfile name exceeds max length The maximum length for the boot file name is 128
characters.
DHCP Option 66 exceeds 255 characters The maximum length for option 66 is 255 characters.
Internal Error Contact Ciena for assistance.
DHCP option 67 exceeds 128 characters The maximum length for option 67 is 128 characters.
DHCP option 66 plus 67 exceed 128 The maximum length for option 66 and 67 combined is 128
characters characters.
DHCP option 66 plus 67 URL exceed 247 The maximum length for the URL built with options 66 and
characters 67 is 247 characters.
Username exceeds maximum length The maximum length is 40 characters.
Password exceeds maximum length The maximum length is 128 characters.
No username or password provided The transfer protocol is either FTP or SFTP and user or
password is missing.

Table 10-3
6500 DHCP client - error counter field descriptions (continued)
Field Description
DHCP option 66 URL invalid file transfer The supported file transfer modes for the boot file are
mode TFTP, FTP, and SFTP.
Config file invalid file transfer mode The supported file transfer modes for the configuration file
are TFTP, FTP, and SFTP.
Boot file invalid file transfer mode The supported file transfer modes for the boot file are
TFTP, FTP, and SFTP.
FTP/SFTP/TFTP failed to get the boot file Possible reasons include:
• no IP connectivity to the server
• file not present
• incorrect permissions to read the file
Bootfile syntax error Unable to parse the boot file due to XML syntax error(s).
Bootfile name mismatch The name field in the boot file does not match the product
type on the shelf. The name must be '6500'.
Bootfile name missing Then name field in the boot file is missing.
Bootfile release mismatch The software release specified in the boot file does not
match the release running on the DHCP client or the DHCP
relay (if applicable).
Bootfile release missing The release is a mandatory field in the boot file.
Bootfile parse URL Fail The URL used to get the boot file has a syntax error.
FTP/SFTP/TFTP Failed to get the Possible reasons include:
configuration file • no IP connectivity to the server
• incorrect permissions to read the file.
FTP Parse URL Fail The URL used to get the configuration file has a syntax
error.
SFTP Parse URL Fail The URL used to get the configuration file has a syntax
error.
The configurations file is empty The configuration file contains no commands.
DCHP messages dropped due to invalid Length or checksum invalid (UDP or IP layer).
length or checksum

6500 DHCP relay

Commands
The relay agent statistics command is supported through TL-1 and CLI.
TL1:
RTRV-RASTATS-DHCP:::T;
CLI:
comms dhcp rastats show shelf-x
The command indicates the status and statistics for the DHCP relay agent.
The stats are shown only for the provisioned interfaces and only if there has
been a DHCP transaction on an interface in the last 15 minutes, as
transactions are deleted automatically after that time.
Response
The following is an example of the response to the RTRV-RASTATS-DHCP
TL1 command:
"SHELF-1:\"Circuit=ECC-1-15-2 ClientId=NNTMHQCH0135
Release=12.60 TXID=0xfbfaa96d RxfromClient=3 TxtoServer=3
RxfromServer=3 TxtoClient=2 Status=Completed\""
"SHELF-1:\"Circuit=ILAN-1-IN ClientId=NNTMHQCH0073
Release=12.60 TXID=0xad7f97b0 RxfromClient=3 TxtoServer=3
RxfromServer=3 TxtoClient=0 Status=CLI file syntax error on
line 4\""
The response contains the following information:

• Circuit: the interface on which a DHCP transaction is/was active
• ClientId: shows option 61 information from the DHCP client, which for
6500 is the serial number
• Release: shows the software release of the DHCP client
• TXID: this is the transaction ID in the DHCP messages, established by the
client in the DHCP discover message.
• RxfromClient: the number of DHCP packets received from the client
• TxtoServer: the number of DHCP packets sent to the DHCP server
• RxfromServer: the number of DHCP packets received from the DHCP
server
• TxtoClient: the number of DHCP packets sent to the client
• Status: provides more detail on the state of DHCP transactions (see Table
10-4 for details).

Table 10-4
6500 DHCP agent - status field descriptions
Field Description
Completed DHCP acknowledgment was sent to client
In Progress DHCP acknowledgment not yet sent to client. Either not
received by the relay agent, or file transfers are still in
progress.
Configuration File prepare for client failed Contact Ciena for assistance.
Configuration File extract commands failed Contact Ciena for assistance.
Configuration File extracted commands list Confirm that the command file contains at the least the
empty basic shelf provisioning commands (refer to
“Configuration file” on page 10-15). If the problem
persists, contact Ciena for assistance.
IP Send Internal Error Contact Ciena for assistance.
IP Send Failed - Link was down Could not send towards DHCP client because link is
down. Check link and retry. If the problem persists,
contact Ciena for assistance.
ACK has Option 43 The DHCP acknowledgment from the server already
has option 43 information.
ACK has no Option 66 The DHCP acknowledgment from the server is missing
option 66.
ACK has no Option 67 The DHCP acknowledgment from the server is missing
option 67.
Configuration file has zero size The configuration file has zero size.
Configuration file syntax error on line x The configuration file has a syntax error on line x.
Bootfile: config file name exceeds max length The maximum length for the configuration file is 128
characters.
Bootfile name exceeds max length The maximum length for the boot file name is 128
characters.
DHCP Option 66 exceeds 255 characters The maximum length for option 66 is 255 characters.
DHCP option 67 exceeds 128 characters The maximum length for option 67 is 128 characters.
DHCP option 66 plus 67 exceed 128 The maximum length for option 66 and 67 combined is
characters 128 characters.

Table 10-4
6500 DHCP agent - status field descriptions (continued)
Field Description
DHCP option 66 plus 67 URL exceed 247 The maximum length for the URL built with options 66
characters and 67 is 247 characters.
Username exceeds maximum length The maximum length is 40 characters.
Password exceeds maximum length The maximum length is 128 characters.
No username or password provided The transfer protocol is either FTP or SFTP and user or
password is missing.
DHCP option 66 URL invalid file transfer mode The supported file transfer modes for the boot file are
Config file invalid file transfer mode The supported file transfer modes for the configuration
file are TFTP, FTP, and SFTP.
Bootfile invalid file transfer mode The supported file transfer modes for the boot file are
FTP/SFTP/TFTP failed to get the bootfile Possible reasons include:
• no IP connectivity to the server
• incorrect permissions to read the file.
Bootfile syntax error Unable to parse the boot file due to XML syntax error(s).
Bootfile name mismatch The name field in the boot file does not match the
product type on the shelf. The name must be '6500'.
Bootfile name missing Then name field in the boot file is missing.
Bootfile release mismatch The software release specified in the boot file does not
match the release running on the DHCP client or the
DHCP relay (if applicable).
Bootfile release missing The release is a mandatory field in the boot file.
Bootfile parse URL Fail The URL used to get the boot file has a syntax error.
FTP/SFTP/TFTP Failed to get the Possible reasons include:
configurations file • no IP connectivity to the server
• incorrect permissions to read the file
FTP Parse URL Fail The URL used to get the configuration file has a syntax
error.
SFTP Parse URL Fail The URL used to get the configuration file has a syntax
error.
The configuration file is empty The configuration file contains no commands.

Troubleshooting other ZTP scenarios

This section highlights some other possible ZTP scenarios to assist in
troubleshooting.
DHCP lease acquired, shelf uncommissioned

This scenario applies to a shelf that is connected via COLAN-X, which in a
ZTP context is considered a numbered interface.
ZTP supports a range of commissioning scenarios, including one where only

the DHCP client functionality is used to provide an address/mask and default
gateway to the COLAN-X to make the shelf visible on the network so that the
commissioning can be ‘pushed down’ from a remote location. In this scenario,
DHCP options 66 and 67 are intentionally not provided in the DHCP response.
Therefore, if DHCP options 66 and 67 are unintentionally not provided in the

DHCP response, such as if the DHCP server is not configured properly, a shelf
that is supposed to retrieve its boot and command files will behave the same
way, accepting the DHCP lease on COLAN-X and waiting for further
commissioning. The ZTP status will appear as follows:
< RTRV-STATS-ZTP:OME-00238A33B305::1;
OME-00238A33B305 01-01-09 07:11:45
M 1 COMPLD
"SHELF-0:\"ZTP Status Running\""
"SHELF-0:\" 1 Lease Acquired\""
;
If this is unintentional, it is recommended to investigate and correct the DHCP
server configuration, so that it provides the correct DHCP options 66 and 67,
and then re-initiate the ZTP sequence by doing DLT-SHELF with a FORCE
option, which causes a restart of the shelf processor.
Note: This does not apply to shelves connected over unnumbered

interfaces (ILAN and OSC).
ZTP status stays at 'running'

This scenario is where the ZTP process does not complete and the ZTP
statistics (TL1: RTRV-STATS-ZTP:::CTAG; or CLI: comms ztpstats show
shelf-x) show a status of 'running' for an extended period of time, perhaps
even indefinitely.
This scenario could be encountered on a ZTP client if there is a failure

executing the 'shelves shelf create' command (for example, due to a syntax
error). A shelf is only considered commissioned once the 'shelves shelf create'
command executes successfully and as such ZTP is still considered active, or
running, until such time.

Since ZTP has not completed, the ZTP statistics show limited information but
the scenario can be confirmed through other means. The CLI command
'shelves shelf show all' will indicate that the shelf entity does not exist,
and attempts to retrieve other shelf provisioning will indicate that the shelf is
not yet commissioned as per the following examples:
OME-7487BBAE3005# shelves shelf show ALL
Failed: Input, Entity does Not Exist
OME-7487BBAE3005# system config show SHELF-1

Failed: Status, Requested Command Inhibited (Shelf is not
commissioned.)
The behavior and recommended action depend on the configFileRule value in

the bootfile as follows:
• if configFileRule = stopOnFailure or ignoreOnFailure, the ZTP process
stops indefinitely. Check and correct the 'shelves shelf create'
command syntax, then issue the 'shelves shelf delete shelf-n
force yes' to restart the ZTP process.
• if configFileRule = retryOnFailure, the ZTP process will automatically
restart after the ztpTimeout interval. Check and correct the 'shelves
shelf create' command syntax and wait for the ztpTimeout interval, or
manually restart the ZTP process using the 'shelves shelf delete
shelf-n force yes' command.

Configuration examples
Redundant OSPF GNE with TIDc
This example includes redundant OSPF GNEs and a consolidated TID. The
DHCP server is located on the same subnet as the two GNEs. The xFTP
server is a separate machine located on a different subnet. Figure 10-9 shows
the high-level configuration. The boot files, configuration files, and Linux
DHCP server configuration file (dhcpd.conf) are given in subsequent sections.
Figure 10-9
ZTP configuration example - Redundant OSPF GNE with TIDc

Boot files
SITE A Shelf 1
File name: SITEA-SHELF1_xml
name="6500"
version="12.60"
configFilePath="6500_ztp/SITEA-SHELFl_cli"
configFileRule="ignoreOnFailure"
ztpTimeout="60">
SITE A Shelf 2
File name: SITEA-SHELF2_xml
name="6500"
version="12.60"
configFilePath="6500_ztp/SITEA-SHELF2_cli"
ztpTimeout="60">
SITE B Shelf 1
File name: SITEB-SHELF1_xml
name="6500"
version="12.60"
configFilePath="6500_ztp/SITEB-SHELFl_cli"
ztpTimeout="60">

Configuration files
SITE A Shelf 1
File name: SITEA-SHELF1 cli
system sid set name SITEA
shelves shelf create SHELF-1 site-id 1 site-name “SITEA” primary ENABLE tidc ENABLE
bay-num 1 location ""
comms ip create SHELF-1 ip-addr 10.132.241.121 netmask 255.255.255.255
system config set SHELF-1 ne-mode SONET osc-mode DISABLED min-cooling HIGHFLOW
autoroute-def DISABLE cs-ctrl ON alarm-info FIC&SBNTNM&BYMBR
servers http set SHELF-1 rest ON
comms ospf router create SHELF-1 router-id 10.132.241.121
comms ospf circuit create SHELF-1 net-area 0.0.0.0
comms lan create COLAN-1-X
comms ip create COLAN-1-X ip-addr 10.132.241.79 netmask 255.255.255.0
comms gne create SHELF-1 config REDUNDANT access OSPF
comms ospf circuit create COLAN-1-X area OFF retrans-invl 5 cost 1000 trans-delay 1
passive OFF net-area 0.0.0.0 opaque OFF auth-type NULL area-def-cost 1 dead-invl 40
priority 1 hello-invl 10
topology ots create OTS-1-1 osid DOM1 tx-path 1 subtype TOADM cfgtype CHA doc-ind Y
osc OSC-1-15-1 cs-ind Y auto-route DISABLE
comms lan create ILAN-1-IN config AUTO
comms lan create ILAN-1-OUT config AUTO
comms ip create ILAN-1-IN ip-addr 0.0.0.0 def-ttl 90 netmask 255.255.255.255
non-routing OFF
comms ip create ILAN-1-OUT ip-addr 0.0.0.0 def-ttl 90 netmask 255.255.255.255
non-routing OFF
comms ospf circuit create ILAN-1-IN area OFF retrans-invl 5 cost 10 trans-delay 1
passive OFF net-area 0.0.0.0 opaque ON auth-type NULL area-def-cost 1 dead-invl 40
comms ospf circuit create ILAN-1-OUT area OFF retrans-invl 5 cost 10 trans-delay 1
topology slot-seq set SLOTSEQ-1-1-1 drop-seq 1-1 add-seq 1-1 validation OFF
amps amp set AMP-1-1-6 input-los-thres -28
amps amp set AMP-1-1-8 targ-gain 18.8 targ-gain-tilt 0
system date set current-date 18-02-19 current-time 15-00-00
adjacencies line set ADJ-1-1-5 min-span-loss 16 targ-span-loss 20 fiber-type NDSF
comms dhcp relay set shelf-1 mode auto

SITE A Shelf 2
File name: SITEA-SHELF2_cli
system sid set name SITEA
shelves shelf create SHELF-2 site-id 1 site-name "SITEA" primary DISABLE tidc ENABLE
autoroute-def DISABLE cs-ctrl ON alarm-info FIC&SBNTNM&BYNMBR
comms lan create ILAN-2-IN config AUTO
comms lan create ILAN-2-OUT config AUTO
comms ip create ILAN-2-IN ip-addr 0.0.0.0 def-ttl 90 netmask 255.255.255.255
non-routing OFF
comms ip create ILAN-2-OUT ip-addr 0.0.0.0 def-ttl 90 netmask 255.255.255.255
non-routing OFF
comms ospf circuit create ILAN-2-IN area OFF retrans-invl 5 cost 10 trans-delay 1
comms ospf circuit create ILAN-2-OUT area OFF retrans-invl 5 cost 10 trans-delay 1
comms dhcp relay set SHELF-2 mode auto
SITE B Shelf 1
File name: SITEB-SHELF1_cli
system sid set name SITEB
shelves shelf create SHELF-1 site-id 2 site-name "SITEB" primary ENABLE tidc ENABLE
autoroute-def DISABLE cs-ctrl ON alarm-info FIC&SBNTNM&BYNMBR
comms lan create COLAN-1-X
comms ip create COLAN-1-X ip-addr 10.132.241.140 netmask 255.255.255.0
comms gne create SHELF-1 config REDUNDANT access OSPF
comms ospf circuit create COLAN-1-X area OFF retrans-invl 5 cost 1000 trans-delay 1
passive OFF net-area 0.0.0.0 opaque OFF auth-type NULL area-def-cost 1 dead-invl 40
topology ots create OTS-1-1 osid DOM1 tx-path 2 subtype TOADM cfgtype CHA doc-ind Y
osc OSC-1-15-1 cs-ind Y auto-route DISABLE
topology slot-seq set SLOTSEQ-1-1-1 drop-seq 1-1 add-seq 1-1 validation OFF
amps amp set AMP-1-1-6 input-los-thres -28
amps amp set AMP-1-1-8 targ-gain 18.8 targ-gain-tilt 0
system date set current-date 18-02-19 current-time 15-00-00
adjacencies line set ADJ-1-1-5 min-span-loss 16 targ-span-loss 20 fiber-type NDSF

Linux DHCP configuration (dhcpd.conf) file

This DHCP configuration file shows various ways of using the DHCP options
to provide the appropriate information to a given shelf:
• Site-A shelf 1 uses both options 60 and 61
• Site-A shelf 2 uses option 82
• Site-B shelf 1 uses options 60 and 82
The following is an example of the Linux DHCP configuration file.

#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
# see 'man 5 dhcpd.conf'
#
authoritative;
option time-offset 14400;
default-lease-time 600;
max-lease-time 7200;
# Linux server
option tftp-server-name "ftp://ZtpuserID:[email protected]";
# subnet of the linux DHCP server
subnet 10.132.241.0 netmask 255.255.255.0 {
option routers 10.132.241.1;
option subnet-mask 255.255.255.0;
# Define Class for SITEA-SHELF1 options 60 and 61
class "SITEA-SHELF1" {
match if option dhcp-client-identifier = "NNTM01N20003V" and option
vendor-class-identifier = "1271-00011600-004";
log (info, "matched on client ID and vendor ID for SITEA-SHELF1");
}
pool {
log (info, "using pool options for SITEA-SHELF1");
allow members of "SITEA-SHELF1";
range 10.132.241.79;
option bootfile-name "6500_ztp/SITEA-SHELF1_xml";
allow known-clients;
}
# Define Class for SITEA-SHELF2 option 82
class "SITEA-SHELF2" {
match if option agent.circuit-id = "SITEA-1.ILAN-OUT";
log (info, "matched on circuit-id for SITEA-SHELF2");
}
pool {
log (info, "using pool options for SITEA-SHELF2");
allow members of "SITEA-SHELF2";
range 10.132.241.139;
option bootfile-name "6500_ztp/SITEA-SHELF2_xml";
}
# Define Class for SITEB-SHELF1 option 82 and 60
class "SITEB-SHELF1" {
match if option agent.circuit-id = "SITEA-1.OSC-15-1" and option
vendor-class-identifier = "1271-00011600-005";
log (info, "matched on circuit-id and vendor ID for SITEB-SHELF1");
}
pool {
log (info, "using pool options for SITEB-SHELF1");
allow members of "SITEB-SHELF1";
range 10.132.241.140;
option bootfile-name "6500_ztp/SITEB-SHELF1_xml";
}
}

Private-IP GNE
This example includes redundant Private-IP GNEs and a consolidated TID.
The DHCP/FTP server is located on a different subnet from the two GNEs.
Figure 10-10 shows the high-level configuration. The boot files, configuration
files, and Linux DHCP server configuration file (dhcpd.conf) are given in
subsequent sections. These configuration files include only the basic shelf
provisioning, assuming the balance of the provisioning information will be
pushed down once the shelves are visible on the network.
Figure 10-10
ZTP configuration example - Redundant Private-IP
The two GNE shelves become relay agents for the subtending shelves,
pointing to the external DHCP server. In this example, shelf SITEZTP-3130 is
also configured as a relay agent for any future subtending shelves (not shown)
and is therefore configured to point to the GNE shelf SITEZTP-0415 as its
DHCP server.

The notable differences in a Private-IP configuration versus a routable IP

configuration are:
• only the GNE shelves point to the external DHCP server
• the internal (RNE) relay agents point to the shelf-IP of one of the GNE
shelves.
Boot files
GNE SITE ZTP-3149
File name: 3149_1_xml_JE_PIP
name="6500"
version="12.60"
configFilePath="6500_ltp/3149_1_cli_JE_PIP"
configFileRule="stopOnFailure">
GNE SITE ZTP-0415

File name: 0415_xml_JE_PIP
name="6500"
version="12.60"
configFilePath="6500_ltp/0415_cli_JE_PIP"
RNE SITE ZTP-3149

File name: 3149_2_xml_JE_PIP
name="6500"
version="12.60"
configFilePath="6500_ltp/3149_2_cli_JE_PIP"

RNE SITE ZTP-3130

File name: 3130_xml_JE_PIP
name="6500"
version="12.60"
configFilePath="6500_ltp/3130_cli_JE_PIP"
Configuration files
GNE SITE ZTP-3149
File name: 3149_1_cli_JE_PIP
system sid set name "SITEZTP-3149"
shelves shelf create SHELF-1 bay-num 1 location "" primary enable tidc enable site-id
1 site-name "SITEZTP-1"
system config set ne-mode sonet osc-mode disabled min-cooling highflow
comms ip create shelf-1 ip-addr 10.199.199.1 netmask 255.255.255.255
comms gne create SHELF-1 config REDUNDANT access PRIVATEIP subnet-name ""
comms tl1gw config set SHELF-1 gne ENABLED rne ENABLED
comms ne-list create SHELF-1 gne YES gne-ip-addr 10.184.17.82 rne-tid SITEZTP-0415
comms ne-list create SHELF-1 gne NO rne-tid SITEZTP-3130
comms ip create colan-1-x ip-addr 10.184.17.19 netmask 255.255.255.240
comms lan create colan-1-a
comms ip create colan-1-a ip-addr 0.0.0.0 netmask 255.255.255.255
equipment config create P155622M-1-15-1 prov-pec NTTP04CF
comms ospf router create SHELF-1 router-id 10.199.199.1 asbr ON
comms ospf circuit create COLAN-1-A net-area 1.1.1.1 cost 10 area-def-cost 1
dead-invl 40 hello-invl 10 retrans-invl 5 trans-delay 1 priority 1 area OFF auth-type
NULL opaque ON passive OFF
comms ip-static-route create SHELF-1 ip-addr 0.0.0.0 netmask 0.0.0.0 circuit
COLAN-1-X next-hop 10.184.17.17 cost 100
comms ospf rdentry create SHELF-1 ip-addr 0.0.0.0 netmask 0.0.0.0 metric 100
metric-type INTERNAL leak-list-id STATICRDLIST

GNE SITE ZTP-0415

File name: 0415_cli_JE_PIP
comms gne create SHELF-1 config REDUNDANT access PRIVATEIP subnet-name ""
comms tl1gw config set SHELF-1 gne ENABLED rne ENABLED
comms ne-list create SHELF-1 gne NO rne-tid SITEZTP-3130
comms ne-list create SHELF-1 gne YES gne-ip-addr 10.184.17.19 rne-tid SITEZTP-3149
comms ip create colan-1-x ip-addr 10.184.17.82 netmask 255.255.255.248
comms lan create ilan-1-out
comms ip create ilan-1-out ip-addr 0.0.0.0 netmask 255.255.255.255
#equipment config create P155622M-1-15-2 prov-pec NTTP04CF
#oscs osc create OSC-1-15-2
comms ospf router create SHELF-1 router-id 10.199.199.3 asbr ON
comms ospf circuit create ILAN-1-OUT net-area 1.1.1.1 cost 10 area-def-cost
1 dead-invl 40 hello-invl 10 retrans-invl 5 trans-delay 1 priority 1 area OFF
auth-type NULL opaque ON passive OFF
#comms ospf circuit create OSC-1-15-2 net-area 1.1.1.1
comms ip-static-route create SHELF-1 ip-addr 0.0.0.0 netmask 0.0.0.0 circuit
COLAN-1-X next-hop 10.184.17.81 cost 100
comms ospf rdentry create SHELF-1 ip-addr 0.0.0.0 netmask 0.0.0.0 metric 100
metric-type INTERNAL leak-list-id STATICRDLIST
RNE SITE ZTP-3149

File name: 3149_2_cli_JE_PIP
shelves shelf create SHELF-2 bay-num 1 location "" primary DISABLE tidc ENABLE
site-id 1 site-name "SITEZTP-1"
system config set ne-mode SONET osc-mode DISABLED min-cooling HIGHFLOW
comms tl1gw config set SHELF-2 rne ENABLED
comms ip create ilan-2-in ip-addr 0.0.0.0 netmask 255.255.255.255
comms lan create ilan-2-out
comms ip create ilan-2-out ip-addr 0.0.0.0 netmask 255.255.255.255
#equipment config create P155622M-2-15-1 prov-pec NTTP04CF
#oscs osc create OSC-2-15-1
comms ospf circuit create ilan-2-out net-area 1.1.1.1
#comms ospf circuit create osc-2-15-1 net-area 1.1.1.1

RNE SITE ZTP-3130

File name: 3130_cli_JE_PIP
comms tl1gw config set SHELF-2 rne ENABLED
comms ip create ilan-2-in ip-addr 0.0.0.0 netmask 255.255.255.255
equipment config create P155622M-2-15-2 prov-pec NTTP04CF
comms dhcp rasrvrinfo create DHCPRASRVR-2-1 srvrip 10.199.199.3
comms dhcp relay set SHELF-2 mode AUTO
Linux DHCP configuration (dhcpd.conf) file

This DHCP configuration file shows the use of DHCP options 61 (client ID) to
assign the appropriate information to a given shelf.
The following is an example of the Linux DHCP configuration file.

#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
# see 'man 5 dhcpd.conf'
#
authoritative;
option time-offset 14400;
default-lease-time 600;
max-lease-time 7200;
# Linux server
option tftp-server-name "ftp://6500_ZTP:[email protected]";
option ntp-servers 10.134.145.24;
# subnet of the linux DHCP server
subnet 10.184.17.160 netmask 255.255.255.248 {
range 10.184.17.164 10.184.17.164;
}
# subnet of the Windows DHCP server
subnet 10.184.17.168 netmask 255.255.255.248 {
range 10.184.17.171 10.184.17.174;
}
# subnet of vlan 10 sub-tending Cisco 3560-1
subnet 10.184.17.16 netmask 255.255.255.240 {
range 10.184.17.24 10.184.17.26;
}
subnet 10.184.17.80 netmask 255.255.255.248 {
range 10.184.17.84 10.184.17.86;
}
# subnet used for shelf-IPs of RNEs in Private-IP config
subnet 10.199.199.0 netmask 255.255.255.0 {
range 10.199.199.100 10.199.199.150;
}
subnet 10.184.17.32 netmask 255.255.255.240 {
range 10.184.17.40 10.184.17.42;
}
group {
host 65_4053 {
option dhcp-client-identifier "NNTMHQPR0070";
option bootfile-name "6500_ltp/3149_2_xml_JE_PIP";
}
host 65_3149 {
option dhcp-client-identifier "NNTMRT0517GP";
option bootfile-name "6500_ltp/3149_1_xml_JE_PIP";
}
host 65_0415 {
option dhcp-client-identifier "NNTMHQCH0095";
option bootfile-name "6500_ltp/0415_xml_JE_PIP";
}
host 65_3130 {
option dhcp-client-identifier "NNTMRT052D29";
option bootfile-name "6500_ltp/3130_xml_JE_PIP";
}
}

Procedures
The following table lists the procedures for the provisioning of the DHCP relay
agent associated with the ZTP feature.
Table 10-5
Procedure
Zero touch provisioning
Procedure 10-1, “Retrieving and editing the ZTP settings”
DCHP relay agent
Procedure 10-2, “Retrieving and editing the DHCP relay agent parameters”
Procedure 10-3, “Adding a DHCP relay agent server”
Procedure 10-4, “Deleting a DHCP relay agent server”
Procedure 10-5, “Retrieving DHCP relay agent statistics”
DHCP relay agent interface
Procedure 10-6, “Retrieving DHCP relay agent interface parameters”
Procedure 10-7, “Adding a DHCP relay agent interface”
Procedure 10-8, “Deleting a DHCP relay agent interface”
Zero touch provisioning security
Procedure 10-9, “Encrypting and provisioning shared secrets”
All procedures assume that the user is logged in to the network element (see
Administration and Security, 323-1851-301).

Site Manager navigation

The following figure provides an overview of the Site Manager navigation
associated with communications management for the 6500 which includes
DHCP RA provisioning. The figure shows the path from the Site Manager
menu bar.

Procedure 10-1
Retrieving and editing the ZTP settings
Use this procedure to retrieve or edit the ZTP settings.
Prerequisites
To perform this procedure, you must use an account with a level 1 UPC or
higher (retrieve) or level 3 UPC or higher (edit).
Step Action

2 Select Comms Setting Management from the Configuration drop-down
menu to open the Comms Setting Management application. The Comms
Setting Management application contains three tabs which provide access to
associated parameters.
3 Select the Services tab.
5 Select Zero Touch Provisioning from the Service Type drop-down list.
The information about zero touch provisioning is displayed. See “Zero Touch
Provisioning parameters” on page 10-54 for information about the options
available.
6 To edit ZTP admin state mode, click Edit.
The Edit ZTP Admin State dialog box is displayed.
7 Select the required admin state from the Admin State drop-down list. See
“Zero Touch Provisioning parameters” on page 10-54 for editable parameters.
8 Click OK.
—end—

Procedure 10-2
Retrieving and editing the DHCP relay agent
parameters
Use this procedure to retrieve or edit the DHCP relay agent parameters
associated with the ZTP feature.
Note: You must delete all DHCP relay agent interfaces before changing
the DHCP relay agent mode from MANUAL to AUTO or OFF to AUTO (see
Procedure 10-8, “Deleting a DHCP relay agent interface”).
Prerequisites
Step Action

5 Select DHCP Relay Agent from the Service Type drop-down list.
Information about the provisioned DHCP Relay Agents is displayed.
6 To edit DHCP relay agent mode, click Edit.
The Edit DHCP RA Mode dialog box is displayed.
7 Select the required mode from the Mode drop-down list. See “DHCP Relay
Agent parameters” on page 10-54 for editable parameters.
8 Click OK.
—end—

Procedure 10-3
Adding a DHCP relay agent server
Use this procedure to add a DHCP relay agent server associated with the
ZTP feature.
Note: Only one DHCP RA server is supported in this release.
Prerequisites
higher.
Step Action

menu to open the Comms Setting Management application.
6 Click Add.
The Add DHCP RA Server dialog box is displayed.
7 Enter the IP Address of the DHCP server in the IP address field.
8 Click OK.
—end—

Procedure 10-4
Deleting a DHCP relay agent server
Use this procedure to delete a DHCP relay agent server associated with the
ZTP feature.
Note: Only one DHCP RA server is supported in this release.
Prerequisites
higher.
Step Action

6 Select the required DHCP RA server entry in the table.
7 Click Delete.
8 Click Yes to close the warning box.
—end—

Procedure 10-5
Retrieving DHCP relay agent statistics
Use this procedure to retrieve DHCP relay agent statistics associated with the
ZTP feature.
Prerequisites
Step Action

6 Select the required DHCP RA server entry in the table.
7 Click DHCP RA Stats.
The DHCP RA Stats window is displayed with the statistics of the provisioned
interfaces.
Note 1: The Stats for the interface are shown only if there has been a DHCP
transaction for that interface.
Note 2: DHCP transactions are deleted after 15 minutes.
Example output:
"SHELF-1:\"Circuit=ILAN-1-OUT ClientId=NNTMHQBL0950
TXID=0x1dde1a1d RxfromClient=2 TxtoServer=2 RxfromServer=4
TxtoClient=4 Status=Completed\""
—end—

Procedure 10-6
Retrieving DHCP relay agent interface parameters
Use this procedure to retrieve the DHCP relay agent interface parameters
associated with the ZTP feature.
Prerequisites
Step Action

5 Select DHCP RA Interfaces from the Service Type drop-down list.
The information about the DHCP relay agent interfaces is displayed. See
“DHCP Relay Agent Interface parameters” on page 10-55 for information
about the options available.
—end—

Procedure 10-7
Adding a DHCP relay agent interface
Use this procedure to add a DHCP relay agent interface associated with the
ZTP feature. DHCP relay agent interfaces can only be added when the DHCP
Relay Agent mode is MANUAL.
DHCP RA interfaces are supported with the following ports:

• COLAN (COLAN-X or COLAN-A [not applicable for 2-slot Shelf Type 1])
• ILAN (ILAN-IN [not applicable for 2-slot Shelf Type 1] or ILAN-OUT
• OSC
Prerequisites
higher.
Step Action

5 Select DHCP RA Interfaces from the Service Type drop-down list.
6 Click Add.
The Add DHCP RA Interfaces Parameters dialog box is displayed.
Note: If all the available circuits are already added, an information dialog box
is displayed with the message ‘No Circuit is available for provisioning’.
7 Select the required AID from the Aid drop-down list.
8 Select the required circuit from the Circuit drop-down list.
9 Select OFF or ON from the Plain RA drop-down list.
Note: The default is OFF and is the required setting when it is to service
DHCP client from a 6500 shelf for ZTP. When connecting a non-6500 Ciena
equipment to the 6500 DHCP relay agent, set Plain RA to ON.
10 Click OK.
11 Repeat step 6 to step 10 as necessary for additional DHCP RA interfaces.
—end—

Procedure 10-8
Deleting a DHCP relay agent interface
Use this procedure to delete a DHCP relay agent interface associated with the
ZTP feature.
Prerequisites
higher.
Step Action

6 Select the required DHCP RA interface entry in the table.
7 Click Delete.
8 Click Yes to close the warning box.
9 Repeat step 6 to step 8 as necessary to delete additional DHCP RA servers.
—end—

Procedure 10-9
Encrypting and provisioning shared secrets
Use this procedure to encrypt and provision a shared secret for a RADIUS
server, a TACACS+ server, or challenge/response.
The encryption of the secret (step 2 and step 3) must be run on any
commissioned NE as it requires user prompting for the secret. The
provisioning of the encrypted secret (step 4 to step 7) is intended for the ZTP
configuration file (but can also be run from the CLI).
Prerequisites
higher.
Step Action
1 Start a 6500 CLI session. See Administration and Security, 323-1851-301, for
details.
Encrypting the secret
2 Encrypt the shared secret by entering the following CLI command:
security encrypt-string operate input-string
3 At the prompt, enter the secret string:
Enter value for "input-string" :
The encrypted secret is displayed, for example:
-----------------------------------------------------
-----------------------------------------
encrypted-string |
"ARUA2IgCwTUJ4PDoO5Qrwj50Ms7cAGal"
-----------------------------------------------------
-----------------------------------------
Entering the encrypted secret
4 If you are using Then go to
RADIUS authentication step 5
TACACS+ authentication step 6
Challenge/response authentication step 7


Encrypting and provisioning shared secrets
Step Action
Provisioning the encrypted shared secret on a RADIUS server

5 To provision a RADIUS server with the encrypted shared secret, enter the
following in the CLI or add as a command in the ZTP configuration file (uses
encrypted string generated in step 2 as an example):
radius auth set server PRIMARY encrypted-pid
The procedure is complete.
Provisioning the encrypted shared secret on a TACACS+ server
6 To provision a TACACS+ server with the encrypted shared secret, enter the
following in the CLI or add as a command in the ZTP configuration file (uses
encrypted string generated in step 2 as an example):
security tacacs-server set SERVER-1-1 encrypted-secret
Provisioning the encrypted secret for Challenge/response authentication
7 To provision the challenge/response secret, enter the following in the CLI or
add as a command in the ZTP configuration file (uses encrypted string
generated in step 2 as an example):
security challenge-secret set encrypted-secret
—end—

Table 10-6
Zero Touch Provisioning parameters
Parameter Options Description Addable/

Editable
Admin State • Off Sets ZTP mode for the shelf: Yes
• On • Off - ZTP is disabled
• Auto (default) • On - ZTP is enabled
• Auto - the ZTP admin state is
automatically determined by the
presence of RJ45 Ethernet Loopback
Plug on craft port of SP.
Table 10-7
DHCP Relay Agent parameters

Editable
Mode • Off (default) Sets DHCP RA mode for the shelf: Yes
• Manual • Off - RA is disabled
• Auto • Manual - the user must manually
provision the RA interfaces
• Auto - the DHCP RA is automatically
applied to all shelf interfaces except
COLAN-X (COLAN-A, ILAN-IN,
ILAN-OUT, and OSC as applicable)
Aid DHCPRASRVR-<shelf>-1 Specifies the index-based AID of the No

DHCP RA server.
Note: Only one DHCP RA server is
supported in this release.
IP Address Standard dot notation Sets the IP address of the DHCP Yes
server.

Table 10-8
DHCP Relay Agent Interface parameters

Editable
Aid DHCPRA-<shelf>-1 to 20 Specifies the index-based AID of the Yes

DHCP RA interface.
Circuit • COLAN-<shelf>-A Specifies the DHCP RA interface. Yes

• COLAN-<shelf>-X
• LAN-<shelf>-IN
• LAN-<shelf>-OUT
• OSC-<shelf>-<slot>-<port>
Plain RA • OFF (default) Disables (ON) or enables (OFF) the Yes

• ON DHCP option 43 conversion on the
specified interface. If the interface is a
numbered interface, the value of the
field can be either ON or OFF. If the
interface is an unnumbered interface,
the value of the field must be OFF.


Copyright© 2010-2020 Ciena® Corporation. All rights reserved.
Release 12.7
Publication: 323-1851-221
Document status: Standard
Issue 1
Document release date: May 2020
CONTACT CIENA
For additional information, office locations, and phone numbers, please visit the Ciena
web site at www.ciena.com

6500 Packet-Optical Platform Commissioning and Testing

Uploaded by

Copyright:

Available Formats

6500 Packet-Optical Platform Commissioning and Testing

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

6500 Packet-Optical Platform Commissioning and Testing

Uploaded by

Copyright:

Available Formats

What is the document about?

What is the document about?

What information is included in appendices A, B, and C?

What information is included in appendices A, B, and C?

6500 Packet-Optical Platform

Commissioning and Testing

323-1851-221 - Standard Issue 1