Вы находитесь на странице: 1из 804

6500 Packet-Optical Platform

Commissioning and Testing


Release 13.0

What’s inside...
SLAT process overview
Nodal SLAT procedures
Photonic layer provisioning procedures
Photonic layer site testing procedures
Passive OTS network procedures
Service layer site testing procedures
Wavelength addition and deletion
MSPP network SLAT procedures
Broadband network SLAT procedures
Appendix A: Observing product and personnel safety guidelines
Appendix B: Quick-start turning-up using the Node Setup application—examples

323-1851-221 - Standard Issue 3


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

For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
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
Interworking with 6500—SLAT considerations 1-6
CPL or 6500 photonic 1-6
Optical Line System 1600 (1600G) 1-6
MOR/MOR+ 1-8
565, 5100 and 5200 DWDM optical multiplexer (OMX) 1-8
SLAT prerequisites 1-11
Commissioning script file 1-11
Equipment requirements 1-11
Supporting equipment requirements 1-11
Provisioning parameters for node setup 1-12
Other customer provisioning information 1-38

Nodal SLAT procedures 2-1


Abbreviations used in procedures 2-1
Nodal SLAT procedures 2-3
Node setup solutions 2-3
List of procedures
2-1 Powering up a new network element and connecting a craft computer 2-12
2-2 Checking the current software release 2-16
2-3 Commissioning the network element using scripts 2-20
2-4 Quick-start turning-up using the Node Setup application 2-26
2-5 Launching Advanced SLAT and logging in 2-40
2-6 Commissioning a network element using Advanced SLAT 2-43
2-7 Enabling or disabling auto-equipping 2-50
2-8 Performing a lamp test 2-52
2-9 Provisioning OSPF router parameters 2-53
2-10 Provisioning ILAN 2-55
2-11 Provisioning Shelf IP address 2-58
2-12 Provisioning IISIS router parameters 2-60
2-13 Provisioning COLAN 2-61
2-14 Provisioning proxy ARP (IPv4)/ND Proxy Provisioning (IPv6) 2-63
2-15 Provisioning NAT 2-65

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
vi Contents

2-16 Provisioning Dynamic NAT 2-66


2-17 Provisioning Port Filtering 2-67
2-18 Provisioning Reverse Port NAT 2-68
2-19 Provisioning Neighbor Discovery Protocol 2-69
2-20 Provisioning static routes 2-70
2-21 Provisioning OSPF routes distribution 2-72
2-22 Provisioning IISIS routes distribution 2-74
2-23 Provisioning SNMP 2-75
2-24 Provisioning security 2-77
2-25 Provisioning SSH/TELNET and HTTP/HTTPS Server 2-78
2-26 Provisioning craft access 2-79
2-27 Provisioning craft OSPF/IISIS 2-82
2-28 Checking, clearing, and provisioning alarms 2-83
2-29 Post SLAT commissioning 2-84

Photonic layer provisioning procedures 3-1


Abbreviations used in this chapter 3-1
Photonic layer provisioning procedures 3-3
List of procedures
3-1 Provisioning photonic parameters 3-6
3-2 Provisioning adjacencies 3-13
3-3 Changing amplifier provisioning targets and differential provisioning settings
on an existing network 3-25
3-4 Updating SPLI entries 3-30

Photonic layer site testing procedures 4-1


Abbreviations used in procedures 4-1
Photonic layer site testing procedures 4-3
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, or BMD2 4-64
4-3 Adding a new OMD4 or OMX 4-68
4-4 Adding a new SCMD4 4-72
4-5 Adding a new CCMD12 4-76
4-6 Adding a new CCMD8x16 or a CXM C-Band Type 1 4-79
4-7 Testing ROADM channel access continuity 4-83
4-8 Testing a CDC ROADM configuration 4-111
4-9 Testing TOADM channel access continuity 4-133
4-10 Testing a DIA configuration 4-141
4-11 Testing a low channel count DIA configuration 4-149
4-12 Testing a Colorless OADM configuration 4-153
4-13 Connecting intra-site fibers and testing a Colorless Direct Attach configuration
(COADM OTS connected to 1x9 or 1x2 WSS) 4-161
4-14 Connecting intra-site fibers for a Colorless Direct Attach configuration
(CCMD12/CMD44/CMD64 connected to 1x20 WSS) 4-178
4-15 Testing Colorless Direct Attach configurations (CCMD12/CMD44/CMD64
connected to 1x20 WSS) 4-192

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Contents vii

4-16 Testing a line amplifier node 4-208


4-17 Testing DGFF nodes 4-247
4-18 Connecting intra-site fibers for Coherent Select sites 4-254
4-19 Testing a Coherent Select line amplifier node 4-267
4-20 Testing a Coherent Select Terminal - Colored node 4-273
4-21 Testing Coherent Select Directionless or Directional nodes 4-278
4-22 Connecting inter-NE fibers and testing the photonic layer 4-285
4-23 Configuring a single span 100 GHz CMD44 point-to-point terminal 4-291
4-24 Configuring a single span OMD4/CMD44 or OMX point-to-point
terminal 4-295
4-25 Equalizing a thin terminal system 4-301
4-26 Configuring a remote CMD44 terminal 4-314

Passive OTS network procedures 5-1


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

Service layer site testing procedures 6-1


Abbreviations used in procedures 6-1
Service layer site testing procedures 6-2
List of procedures
6-1 Testing the power at the optical interface Tx port 6-3
6-2 Testing the power at the optical interface Rx port 6-8
6-3 Testing optical signal continuity in the network element 6-10
6-4 Testing DS1 service modules 6-12
6-5 Testing E1 circuit packs 6-16
6-6 Testing DS3/EC-1 circuit packs and DS3/E3 circuit packs 6-20
6-7 Testing 16xSTM-1e circuit packs 6-24
6-8 Testing Trans Mux (TMUX) circuit packs 6-28
6-9 Testing 4xGE EPL circuit packs and testing GE protection 6-32
6-10 Testing 24x10/100BT circuit packs 6-39
6-11 Testing L2SS or 20G L2SS circuit packs 6-46
6-12 Testing L2SS DS1/E1/DS3/E3 4XGE (PDH) circuit packs 6-54

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
viii Contents

6-13 Testing L2SS, 20G L2SS, and PDH gateway equipment protection 6-58
6-14 Testing RPR circuit packs 6-63
6-15 Testing 1x10GE EPL circuit packs 6-67
6-16 Testing SuperMux circuit packs 6-70
6-17 Setting a hardware terminal loopback for a network element 6-78
6-18 Restoring a network element to its initial state 6-81

Wavelength addition and deletion 7-1


Abbreviations used in this chapter 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

MSPP network SLAT procedures 8-1


Abbreviations used in procedures 8-1
MSPP network SLAT procedures 8-2
List of procedures
8-1 Testing signal continuity and protection switching in a basic network
configuration 8-3
8-2 Testing a Resilient Packet Ring 8-13
8-3 Testing L2SS or PDH Gateway 8-19

Broadband network SLAT procedures 9-1


Abbreviations used in procedures 9-1
Network SLAT procedures 9-2
List of procedures
9-1 Validating connections with TTI or TR control 9-3
9-2 Performing system acceptance testing 9-9
LOFEF description 9-9

Appendix A: Observing product and personnel safety guidelines


10-1
Audience 10-2
Precautionary messages 10-2
Safety standards 10-3
Grounding standards 10-4
Laser radiation—optical transmission systems 10-4
International standards 10-4
Laser radiation hazards 10-5

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Contents ix

Labeling 10-6
Circuit pack labels 10-6
Using optical fibers 10-30
Handling optical fibers 10-30
Splicing optical fibers 10-31
Repairing optical fibers 10-31
Working with systems cooled by forced air 10-32
Working with power 10-33
Grounding requirements 10-33
Working with AC power 10-36
Working with DC power 10-36
Dissipating static electricity 10-40
Preventing circuit pack damage and pluggable module damage 10-46
Handling, installing, storing, or replacing circuit packs and pluggable
modules 10-46
Transporting circuit packs and pluggable modules 10-48
Controlling equipment access 10-48
Controlling equipment environment 10-48
List of procedures
10-1 Applying a 1M Hazard Level Caution label on NTK552AAE5, NTK552BAE5,
NTK552FAE5, NTK552FB, and NTK552GAE5 circuit packs 10-53

Appendix B: Quick-start turning-up using the Node Setup


application—examples 11-1
Direct Connect—configuration example 11-2
Gateway Connect—configuration example 11-6

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
x Contents

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
xi

New in this release and documentation


roadmap 0

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


Release 13.0 software and subsequent maintenance releases for
Release 13.0.
For interworking with Waveserver, refer to the CLI, REST, gRPC &
Waveserver-6500 Interworking, 323-1851-165.

Issue 3
The Attention box listing the applications where this software release can be
used has been removed. If you have 6500 Release 13.0 software, refer to the
Planning Guide, Part 1, NTRN10EG, for supported applications. For
information specific to other 6500 13.0x releases, refer to the Planning Guide
Part 1, or the Addendum for that release.

Issue 2
This document was up-issued to include changes to the Attention box to
indicate the applications where this software release can be used.

Note: The Attention was removed in Issue 3.

Issue 1
The following new/enhanced features are covered in this document:
• Packet Transport System (PTS)

6500 technical publications


The following two roadmaps identify the technical publications that support the
6500 D-Series and S-Series and the technical publications that support the
6500 T-Series platform for Release 13.0.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
xii 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
Planning - (323-1851-520) Electrical
Installation - Configuration - (323-1851-102.2)
Parts 1, 2, and 3 2-slot Shelves Provisioning
(NTRN10EG) (323-1851-201.1) Fault Management - OC-n/STM-n
and Operating
Data Comms Alarm Clearing (323-1851-102.3)
Planning & User Guide
Parts 1 and 2
Installation - 7-slot & Parts 1 and 2
(323-1851-101) (323-1851-310) WaveLogic Ai, Flex,
7 packet-optical (323-1851-543)
Ordering Information Shelves Configuration - 100G+, 40G,
(323-1851-151) (323-1851-201.2) Bandwidth & Data Fault Management - OSIC ISS, & SLIC10
Services Parts 1,2,3 Module (323-1851-102.4)
Manufacturing DiscD Installation -
(323-1851-320) Replacement Broadband/SMUX
(323-1851-155) 14-slot Shelves (323-1851-545) OTN FLEX MOTR
CLI, REST, gRPC & (323-1851-201.3) Configuration -
Waveserver-6500 (323-1851-102.5)
Installation - Control Plane Fault Management -
Interworking 32-slot Shelves (323-1851-330) SNMP Photonics
(323-1851-165) (323-1851-201.4) (323-1851-740) Equipment
Latency Encryption and FIPS (323-1851-102.6)
Specifications Passive Chassis Security Policy
Overview and Fault Management - Data and Layer 2
(323-1851-170) (2150 & Photonics),
Procedures Customer Visible (323-1851-102.7)
Pluggable Filters, and Modules
(323-1851-340) Logs
Datasheets (323-1851-201.5)
(323-1851-840) OTN I/F, PKT I/F, &
and Reference MyCryptoTool PKT/OTN I/F
(323-1851-180) Commissioning Certificate (323-1851-102.8)
TL-1 Description and Testing Management and
(323-1851-190) (323-1851-221) Quick Start PTS Circuit Packs
(323-1851-341) and Modules
CLI Reference (323-1851-102.9)
(323-1851-193)
Site Manager
Fundamentals
(323-1851-195)

SAOS-based Command Fault and MIB


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

Supporting WaveLogic Photonics 6500 Data 6500 Control Plane Submarine Networking
Documentation Coherent Select Application Guide Application Guide Application Guide
(323-1851-980) (NTRN15BA) (NTRN71AA) (NTRN72AA)
6500 Photonic Common 6500 - 5400 / 8700 Fiber Node Return Universal AC Rectifier
Layer Guide Photonic Layer Interworking Solution Configuration Application Note
(NTRN15DA) Technical Publications (323-1851-160) (323-1851-985) (009-2012-900)

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
New in this release and documentation roadmap xiii

6500 T-Series roadmap

Planning a Network Installing, Managing and Maintaining and


Commissioning and Provisioning Troubleshooting
Testing a Network a Network a Network

Administration Fault Management -


T-Series Installation -
and Security Performance
Shelf Guide T-Series Shelves
(323-1851-301) Monitoring
(323-1851-103) (323-1851-201.6) (323-1851-520)
Data Communications Configuration -
T-Series Shelf Provisioning and
Planning and Fault Management -
Guide Operating Parts 1 & 2
User Guide Alarm Clearing
(323-1851-103) for T-Series
(323-1851-101) Parts 1 and 2
(323-1851-311) for T-Series
TL-1 Description
for T-Series Configuration - (323-1851-544)
(323-1851-191) Bandwidth
Fault Management -
for T-Series
Site Manager Module
(323-1851-321)
Fundamentals Replacement
(323-1851-195) Configuration - for T-Series
Control Plane (323-1851-546)
(323-1851-330) Fault Management -
SNMP
(323-1851-740)

Fault Management -
Customer Visible
Logs
(323-1851-840)

SAOS-based Command Fault and MIB


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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
xiv New in this release and documentation roadmap

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
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
• “Interworking with 6500—SLAT considerations” on page 1-6
• “SLAT prerequisites” on page 1-11

Abbreviations used in this chapter


ARP address resolution protocol

BB broadband

CMD channel mux/demux

COLAN central office LAN

CPL common photonic layer

CS Coherent Select

CSA centralized security administration

DCN data communications network

DHCPv4 dynamic host configuration protocol version 4 (IPv4)

DHCPv6 dynamic host configuration protocol version 6 (IPv6)

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-2 SLAT process overview

IDP international documentation package

IISIS integrated ISIS

ILAN intershelf LAN

IPv4 Internet Protocol version 4

IPv6 Internet Protocol version 6

LAN local area network

LIM line interface module

LOFEF laser off far end failure

MOR multiwavelength optical repeater

MSPP multi-service provisioning platform

NE network element

NAT network address translation

NDP topology neighbor discovery protocol - topology

ND Proxy (or NDP in ND Proxy protocol


Proxy context)

NGM next generation modulation

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

OSPFv3 open shortest path first - version 3

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-3

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

WT wavelength translator

How to use this document


The 6500 systems interwork with the Common Photonic Layer (CPL), Optical
Line System 1600 (1600G), and MOR/MOR+ amplifiers. The 6500 also has
its own photonic layer.

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-3 for the Node Setup simplification solution introduced in
release 10.0.
• script-based commissioning solution (if a commissioning script file exists).
See “Node setup solutions” on page 2-3.

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-4 SLAT process overview

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.

Finally, perform “MSPP network SLAT procedures” or “Broadband network


SLAT procedures” as applicable.

Refer to “Interworking with 6500—SLAT considerations” for an overview of


SLAT considerations for systems that include 6500, CPL, 1600G, or MOR/
MOR+.

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, Part 1 to Part 3 of Configuration - Bandwidth and
Data Services, 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.

For PTS services, refer to PTS Circuit Packs and Modules, 323-1851-102.9
for the provisioning procedures required to bring the PTS circuit packs to a
ready to carry traffic state.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-5

Figure 1-1
End-to-end SLAT process flowchart

6500 nodal SLAT


“Nodal SLAT procedures” (Chapter 2)
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”.

MSPP Photonic layer Photonic Submarine POTS/


& DOC-controlled layer (DOC or PKT/PTS
SuperMux systems Passive Flexible
systems Grid)

Optional (see “Service “Photonic layer “Passive OTS See Configuration -


layer site testing provisioning network procedures” Control Plane,
procedures”) procedures” (Chapter 5) 323-1851-330, and
(Chapter 6) (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)

MSPP Broadband
“MSPP network SLAT “Broadband network SLAT
procedures” procedures”
(Chapter 8) (Chapter 9)

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-6 SLAT process overview

Interworking with 6500—SLAT considerations


The 6500 OC-48/STM-16 and OC-192/STM-64 DWDM wavelengths
interwork with the CPL equipment, 6500 Photonic layers, 1600G systems,
MOR/MOR+ amplifier systems, and 565, 5100 and 5200 DWDM optical
multiplexer (OMX) products through the OC-192/STM-64 AM1/AM2 DWDM
tunable optical interfaces. The AM1/AM2 dithering support is required when
interworking with Long Haul 1600 systems and MOR+ systems.

The following sub-sections include SLAT considerations for 6500 interworking


with CPL, 6500 Photonic layers, 1600G, MOR/MOR+, and 565, 5100 and
5200 systems.

CPL or 6500 photonic


For each network element:
• Perform SAT procedures.
• Determine whether photonic equipment is present in the network element.
Refer to Table 1-1.
Table 1-1
SLAT procedures overview

If photonic equipment is present in the network element If photonic equipment is not present in
the network element

• provision photonic equipment • provision circuit packs


• provision photonic layer (OTS) • perform site testing for each circuit pack
• provision adjacencies • perform system acceptance testing
• test photonic layer (NE based): connect intra-NE fibers and • complete system provisioning
perform NE based photonic testing
• verify network wide visibility: connect inter-NE fibers
• provision DWDM circuit packs
• perform site testing for each circuit pack
• perform network optimization: add optical channels
• perform system acceptance testing
• complete system provisioning

Refer to the CPL Technical Publication Library for details on CPL nodal SLAT
and network SLAT.

Optical Line System 1600 (1600G)


Refer to Figure 1-2 on page 1-9 and Figure 1-3 on page 1-10 for an overview
of network SLAT for a system that includes 6500 and 1600G.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-7

The following are the 6500 AM2-capable circuit packs:


• Broadband circuit packs: NGM WTs (LAN PHY, SONET/SDH, OTU2),
10G OTR, 10G OTSC.
• MSPP circuit packs: 1xOC192/STM64 DWDM C-Band Tunable HO and
LO.

When adding 6500 AM2-capable wavelengths to 1600G:


• Use the 1600G procedures with or without protection switching, as
applicable.
• Use channel autodiscovery and power optimization as before.
• Revert to manual transmitter-power adjustments if requested by the
Push-Button Equalization (PBE) client (for example, loss of comms
scenario). PBE allows automatic adjustments to the transmitters when
invoked on the 1600G AMP NE housing the link post-amplifier.
• The PBE server feature extends PBE coverage to 6500 AM-2 capable
circuit packs:
— NGM WT 1xOC192/STM64 (NTK530AA/BA)
— NGM WT 10GE LAN (NTK530AB/BB)
— NGM WT OTU2 (NTK530AC/BC)
— 10G OTR (NTK530MA)
— 10G OTSC (NTK528AA)
— 1xOC192/STM64 AM1/AM2 DWDM Tunable HO/LO (NTK526JA/
NTK527JA)

1600G Demux VOAs can be set to minimum attenuation when 6500 circuit
packs are deployed, because they have their own, built-in VOA.

When performing the 1600G optical link testing, refer to 6500 Procedure 9-2,
“Performing system acceptance testing” for HCCSREF values and
considerations, and eight-hour system soaking.

Refer to the 1600G Technical Publication Library for details on 1600G nodal
SLAT and network SLAT. Refer to the 1600G Supporting Documentation
Library for details on the implementation of unrepeatered DWDM links with
6500 network elements.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-8 SLAT process overview

MOR/MOR+
Refer to Figure 1-2 on page 1-9 and Figure 1-3 on page 1-10 for an overview
of network SLAT for a system that includes 6500 and MOR/MOR+.

The following are the 6500 AM1-capable circuit packs:


• Broadband circuit packs: 10G OTR, 10G OTSC.
• MSPP circuit packs: 1xOC192/STM64 DWDM C-Band Tunable HO and
LO.

When adding AM1-capable 6500 wavelengths to MOR/MOR+:


• Use MOR/MOR+ procedures with or without protection switching, as
applicable.
• You can use channel autodiscovery and power optimizer.
• 6500 wavelengths will appear as an “OC192 DWDMTx” source in the
MOR/MOR+ channel inventory.
• You must adjust all Tx powers manually.

MOR/MOR+ Demux VOAs can be set to minimum attenuation when 6500


circuit packs are deployed, because they have their own, built-in VOA.

When performing the MOR/MOR+ optical link testing, refer to 6500


Procedure 9-2, “Performing system acceptance testing” for HCCSREF values
and considerations, and eight-hour system soaking.

Refer to the 1600G Technical Publication Library for details on MOR/MOR+


nodal SLAT and network SLAT.

565, 5100 and 5200 DWDM optical multiplexer (OMX)


When interworking with the OMX product, to avoid link budget problems, you
must set the Tx FEC Format of the OC-192/STM-64 AM1/AM2 DWDM tunable
optical interface to super concatenated FEC. The Rx Equalization firmware
must be also running on the OMX side.

If the 6500 at one end uses OC-192/STM-64 DWDM optical interfaces and at
the other end uses OC-192/STM-64 AM1/AM2 DWDM tunable optical
interfaces, you must contact your Ciena representative for link budget
validation.

6500 supports 16 wavelengths in the OMX C-Band 200GHz grid, 32


wavelengths in the OMX C-Band 100GHz grid, and 16 wavelengths for the
OMX L-band for interworking with the OMX.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-9

Figure 1-2
Overview of 6500 network SLAT with 1600G or MOR+ (Broadband functions)

Follow up until the 1600G/MOR + SLAT complete


channel add portion (minus Channel Add)
(amplifiers are provisioned)

Tx wavelength set 6500 BB Nodal


SLAT complete 6500 6500 6500
Before NGM WTs
equalization invoked, 6500 6500
Connect Line Tx/Rx of
Rx OSNR may be below
6500 BB to Mux/Demux 6500 6500
limits for Dispersion Scan

Adjust Tx powers to
equalize system Autodiscover 6500 wavelengths
Tx dispersion value set
Tx/Rx pairs optimized
by TR control
Line Txs of 6500 BB
circuit packs that do Validate 6500 BB Validate 6500 BB WT TR Control and
not support TR Control OTU connections OTU connections

Dispersion Scan
(Search for CD value to
achieve Tx/Rx continuity)
TR Control
Init Alarm
OOS Optimization
(Coarse adjustment of
optical parameters to
achieve best BER)

After completion, Tx/Rx pairs are


ready for systems acceptance IS Optimization
testing (BER test) (ready for traffic, TR Control IS Opt
still optimizing) in progress Alarm

SS Optimization No TR Control
(fully optimized) Alarm

Soak ( 8 Hours)
FEC counts match System acceptance testing
expected BER for (Validate that all Line Rxs at all 6500 BB NEs meet
SLAT expected pre-FEC BER)

Final system provisioning

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-10 SLAT process overview

Figure 1-3
Overview of 6500 network SLAT with 1600G or MOR+ (MSPP functions)

Follow up until the 1600G/MOR + SLAT complete


channel add portion (minus Channel Add)
(amplifiers are provisioned)

Tx wavelength set 6500 Nodal SLAT


complete 6500 6500 6500

Connect Line Tx of 6500 6500


6500 to Mux 6500 6500

Autodiscover 6500 wavelengths

Adjust Tx powers to
equalize system 1600G/MOR+ link equalization

1600G/MOR+ Demux
VOAs adjustments

After completion, Tx/Rx pairs Connect Line Rx of 6500


are ready for systems to Demux
acceptance testing (BER test)

Soak ( 8 Hours) System acceptance testing


FEC counts match (Validate that all Line Rxs at all 6500 NEs meet
expected BER for expected pre-FEC BER)
SLAT

Final system provisioning

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-11

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-2.

Table 1-2
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 Site
Manager for 6500 and CPL Fundamentals for this release, 323-1851-195,
for details
Current release Site Manager software installed on your craft computer—
refer to Site Manager for 6500 and CPL Fundamentals for this release,
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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-12 SLAT process overview

Table 1-2
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-3 on page 1-13 and Table 1-4 on page 1-32
— for IPv6, see Table 1-3 on page 1-13 and Table 1-5 on page 1-37
— In Table 1-3 on page 1-13:
– 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-3 on page 1-13.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-13

– 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-3 on page 1-13, refer to
Planning - Ordering Information, 323-1851-151.
• For the Node Setup application, see Table 2-2 on page 2-31.
Table 1-3
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-14 SLAT process overview

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
Extended NE 1 to 64 alphanumeric Can include any combination of upper and no
Name 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 (,).
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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-15

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
Site ID 0 to 65535 identifier of the site. Must be the same for all yes for
NEs within a site. photonic
In order for Visualization to work properly, the services
Site ID on non-photonics shelves should be
set to match the Site ID of photonic shelves at
the same site.
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
15. (channel
access nodes
only)
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
15. (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 5)” on page 1-28.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-16 SLAT process overview

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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
the IPv6 shelf IP address. If IPv6 is not
enabled (OFF), do not provision the IPv6
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
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
the IPv6 shelf IP address. If IPv6 is not
enabled (OFF), do not provision the IPv6
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 the no
OSPF GCC0 comms channel. Default = Disabled
NDP mode DISABLED (default), controls the auto-provisioning behavior of the no
ENABLED 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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-17

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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 (default) 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 1 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 15.

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 N

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.
TCA • ENABLED Determines whether TCA suppression is no
Suppression • DISABLED (default) enabled or disabled.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-18 SLAT process overview

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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
Configuration - Provisioning and Operating,
Part 1 of 2, 323-1851-310.1.
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, Configuration -
Provisioning and Operating, Part 1 of 2,
323-1851-310.2 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-19

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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
Line Flapping Alarm parameter is set to
Disabled first. If it is enabled, then disable it,
change the Line Flapping Alarm Raise Time
value, and re-enable the alarm.
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
Line Flapping Alarm parameter is set to
Disabled first. If it is enabled, then disable it,
change the Line Flapping Alarm Threshold
value, and re-enable the alarm.
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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-20 SLAT process overview

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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 columns/
• Label 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-21

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-22 SLAT process overview

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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 WT, OTR, 2x10G OTR, yes
27, 83-90 for 2-slot OTSC, and MOTR circuit packs must have
shelf auto-equipping 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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-23

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
OSPF Router Provisioning - IPv4 tab and IISIS Router Provisioning (applies to IPv4 only)—see
Table 1-4 on page 1-32.
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-5 on page 1-37
ILAN Provisioning - IPv4 tab (Note 5 and Note 13)
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 11
Subnet Mask
Port Enabled YES, NO enables or disables the port
See Note 17.
Routing NONE, OSPF, IISIS, If OSPF, IISIS, or OSPF/IISIS is selected, see Note 9
Protocol OPSF/IISIS you must provision the corresponding circuit
parameters (see Table 1-4 on page 1-32).
ILAN Provisioning - IPv6 tab (Note 5 and Note 13)
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
separated by colons, as
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 17.
Routing NONE/OSPFv3 If OSPFv3 is selected, you must provision the see Note 9
Protocol corresponding circuit parameters (see Table
1-5 on page 1-37).

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-24 SLAT process overview

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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
parameters (see Table 1-4 on page 1-32).
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-5 on page 1-37).
IPv6 Shelf eight groups of four IPv6 address to assign to shelf yes
Address hexadecimal digits
separated by colons, as
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-4 on page 1-32)
COLAN Provisioning - IPv4 tab (Note 5 and Note 6) (See Table 1-4 on page 1-32 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 7
Proxy ARP ON, OFF enables or disables the proxy ARP on the see Note 6
COLAN port and Note 8
Port Enabled YES, NO enables or disables the port no
See Note 17.
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 7
parameters (see Table 1-4 on page 1-32).
COLAN Provisioning - IPv6 tab (Note 5 and Note 6) (See Table 1-5 on page 1-37 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-25

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
IP Address eight groups of four COLAN IPv6 address yes. See Note
hexadecimal digits 2 and Note 7
separated by colons, as
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 17.
Routing NONE, OSPFv3 If OSPFv3 is selected, you must provision the see Note 2
Protocol corresponding circuit parameters (see Table and Note 7
1-4 on page 1-32).
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 8
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 7
separated by colons, as
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-26 SLAT process overview

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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 match yes
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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-27

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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 12
Circuit COLAN, ILAN ports port used to get to the next hop
Cost 1 to 65535 cost of the link
Carrier Section/RS, sets the DCC/GCC channel used, section/ yes
line/MS, 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 12
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
separated by colons, as
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-4 on
page 1-32

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-28 SLAT process overview

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
SNMP Provisioning (Note 5)
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
a TIDc that will be managed by OneControl, it
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 16.
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 16.
the user information used to send traps

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-29

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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 16.
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).

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-30 SLAT process overview

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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-4 on page 1-32 for IPv4 and Table 1-5 on page 1-37 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. When On, the no
Mode interface only accepts packets that terminate
at its IP address and routing updates and
packets to be forwarded through other
circuits are dropped.
Port Enabled YES, NO indicates if the port is enabled no
Craft OSPF/IISIS Provisioning—see Table 1-4 on page 1-32 for IPv4 and Table 1-5 on page 1-37
for IPv6

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-31

Table 1-3
Provisioning information for each network element—SLAT Assistant Tool (continued)
Parameter Value Description Mandatory
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: OTM2 TR control applies only to NGM ports and is expected to be always ON (default) during
SLAT. 10G OTR Port 1, MOTR Port 1 and 2x10G OTR Ports 1 and 3 do not support TR Control.
Note 5: The number immediately following OTM2, COLAN, ILAN, and DEST indicates the shelf number.
Note 6: If you want ARP Proxy enabled on the COLAN port, you must select ARP Proxy ON in the
COLAN Provisioning step.
Note 7: 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 8: Proxy ARP and ND Proxy are only supported on the COLAN-X port.
Note 9: 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 10: 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 11: 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 12: 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 13: 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 14: 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 15: 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 16: 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 17: 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-32 SLAT process overview

Table 1-4
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.

Link State external (default), Sets the type of link state announcement used.
Announcement router, summary This parameter is not used and can be left at the default
Type value (External).

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-33

Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)

Parameter Value Description

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),
LAN-shelf-16 (or 42),
SHELF-shelf,
OSC-shelf-slot-port,
OC-n/ STM-n/
STM0J/ STM1J/
STM4J/ OTMn/
OTUTTP/ ODUTTP/
ODUCTP ports

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 Section/RS (default) Sets the DCC/GCC on the OCn/STMn/OTMn/OTUTTP/


line/MS, GCC0, ODUTTP/ODUCTP port for the OSPF circuit.
GCC1 Only applicable to OCn/STMn/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, 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
• section/RS DCC: 520
• line/MS DCC: 174

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-34 SLAT process overview

Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)

Parameter Value Description

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.
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.
Note: It is not supported in this release

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 Virtual Link Standard dot Sets the IP address of the OSPF router id designated as a
notation virtual interface. Area Virtual Link 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-35

Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)

Parameter Value Description

IISIS circuit parameters

Name SHELF-shelf, Displays the available ports for an IISIS circuit.


LAN-shelf-15 (or 41), Only OC-n/STM-n/STM0J/STM1J/STM4J/OTMn/OTUTTP/
LAN-shelf-16 (or 42), ODUTTP/ODUCTP ports with lower layer DCC/GCC0/
COLAN-shelf-A, GCC1 provisioned are available for selection.
COLAN-shelf-X,
ILAN-shelf-IN, IISIS over the GRE interfaces is not supported in this
ILAN-shelf-OUT, release.
GRE-shelf-IP-1 to 4,
OC-n/ STM-n/
STM0J/ STM1J/
STM4J/ OTMn/
OTUTTP/ ODUTTP/
ODUCTP ports

Carrier Section/RS (default), Displays the DCC channel used, section/RS, line/MS, GCC
line/MS, GCC0, used, GCC0 or GCC1 (options available depend on circuit
GCC1 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
• OC-n/STM-n/STM0J/STM1J/STM4J/OTMn ports with line/
MS DCC/GCC0/GCC1 provisioned: 5
• /OTUTTP/ODUTTP/ODUCTP: 5
• OC-n/EC1/STM-n/STM0J/STM1J/STM4J ports with
section/RS DCC provisioned: 6
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-36 SLAT process overview

Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)

Parameter Value Description

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 DCC Protocol parameter
Override is set to LAPD.
When provisioning an IISIS circuit:
• on an optical DCC port connected to OSI managed
network elements (for example, Optical Metro 3000 and
Optical Metro 4000), you must ensure that neighbour
protocol supported override parameter is set to OSI.
• on an optical port connected to another 6500 network
element, it is strongly recommended that the lower layer
DCC Protocol parameter be set to PPP and the neighbour
protocol supported override parameter be set to Off.
The “IP” and “IP and OSI” options are not supported.

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
SLAT process overview 1-37

Table 1-4
OSPF and IISIS parameters—SLAT Assistant Tool - IPv4 (continued)

Parameter Value Description

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-5
OSPFv3 parameters—SLAT Assistant Tool - IPv6

Parameter Value Description

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.

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,
LAN-shelf-15 (or 41),
LAN-shelf-16 (or 42),
SHELF-shelf

OSPFv3 Network standard dot notation Sets the area


area

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
1-38 SLAT process overview

Table 1-5
OSPFv3 parameters—SLAT Assistant Tool - IPv6 (continued)

Parameter Value Description

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.
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.
Note: It is not supported in this release

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
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.

This chapter also includes procedures to provision additional photonic


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

This chapter contains the following topics:


• “Abbreviations used in procedures” on page 2-1
• “Nodal SLAT procedures” on page 2-3
• “Procedures” on page 2-10

Abbreviations used in procedures


ARP address resolution protocol

BIP breaker interface panel

COLAN central office LAN

CMD channel mux/demux

CPL common photonic layer

CS Coherent Select

DCN data communications network

DHCPv4 dynamic host configuration protocol version 4 (IPv4)

DHCPv6 dynamic host configuration protocol version 6 (IPv6)

DISP dispersion

DOC domain optical controller

DSCM dispersion slope compensation module

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-2 Nodal SLAT procedures

EBER excessive bit error rate

eDCO electronic dynamically compensating optics

EDP engineering documentation package

GCC general communications channel

GNE gateway network element

ID identifier

IDP international documentation package

IISIS integrated ISIS

ILAN intershelf LAN

IPv4 Internet Protocol version 4

IPv6 Internet Protocol version 6

L2SS layer 2 service switch

LACP link aggregation control protocol

LAN local area network

LED light emitting diode

LIM line interface module

NAT network address translation

NDP topology neighbor discovery protocol - topology

ND Proxy (or NDP in ND Proxy protocol


Proxy context)

NE network element

NTP network timing protocol

OCI optical channel interface

OCLD optical channel and laser detector

OSC optical service channel

OSPFv2 open shortest path first - version 2

OSPFv3 open shortest path first - version 3

OTM optical transport module

OTS optical transport sections

PC personal computer

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-3

PDH plesiochronous digital hierarchy

PEC product engineering code

PM performance monitoring

ROADM reconfigurable optical add/drop multiplexer

Rx receive

SAT SLAT Assistant Tool

SBS stimulated Brillouin scattering

SCMD serial channel mux/demux

SLAT system lineup and testing

SNMP simple network management protocol

SP shelf processor

SPAP shelf processor with access panel

TL-1 transaction language 1

TOADM thin optical add/drop multiplexer

Tx transmit

UDP user datagram protocol

UPC user privilege code

WSS wavelength selective switch

WT wavelength translator

Nodal SLAT procedures


Table 2-1 on page 2-10 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-4 Nodal SLAT procedures

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 Blue Planet 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-5

The Advanced SLAT Assistant Tool continues to be 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
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.

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 11-1.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-6 Nodal SLAT procedures

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-7

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.

Security Provisioning
(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 8 to step 22 in Procedure 2-2 “Checking the current software release”.)

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-8 Nodal SLAT procedures

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)

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
turning-up using the Node
(SP has the correct
Yes Setup application” as
software release)
instructed in Procedure 2-2
Node Setup
Steps NE Identification “Checking the current
software release”.
In addition to the basic
NE Configuration parameters, Advanced
Parameters are available with
initial values, can be edited as
required, and are
Proxy ARP GNE automatically populated when
setting up the next shelf.

COLAN Provisioning

Security Provisioning
(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 8 to step 22 in Procedure 2-2 “Checking the current software release”.)

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-9

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)


If the Node Setup application
did not open, go to
Launch Site Manager. Procedure 2-2 “Checking the
current software release” to
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
instructed in Procedure 2-2
software release.)
“Checking the current
Node Setup software release”.
Steps NE Identification

In addition to the basic


parameters, Advanced
Parameters are available with
NE Configuration initial values, can be edited as
required, and are
automatically populated when
setting up the next shelf.
Basic setup complete.
Note: After completing the basic
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 8 to step 22 in Procedure 2-2 “Checking the current software release”.)

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-10 Nodal SLAT procedures

Procedures
Table 2-1
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”

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-11

Table 2-1
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”

Optional tasks
—in Procedure 2-29, “Post SLAT commissioning”:

• “Connecting the network element to the DCN” on page 2-85


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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-12 Nodal SLAT procedures

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.

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.

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).

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-13

Procedure 2-1 (continued)


Powering up a new network element and connecting a craft computer

Step Action

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.
Note: The 2-slot shelf (NTK503MAE5/NAE5 variants) has the shelf
processor built into the chassis.
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.
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-14 Nodal SLAT procedures

Procedure 2-1 (continued)


Powering up a new network element and connecting a craft computer

Step Action

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-15

Procedure 2-1 (continued)


Powering up a new network element and connecting a craft computer

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.
21 Select your next step.
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-3
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-26
a commissioning script file or “Checking the current software release” on
Advanced SLAT page 2-16
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-16 Nodal SLAT procedures

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 13.0software 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-17

Procedure 2-2 (continued)


Checking the current software release

Step Action

6 Select your next step.


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 13.0)


8 Select your next step.
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 8
Setup application

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-18 Nodal SLAT procedures

Procedure 2-2 (continued)


Checking the current software release

Step Action

9 Select your next step.


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

10 Select your next step.


If your turning-up solution is Then go to
Advanced SLAT step 11
the Node Setup application step 14

11 Select your next step.


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

12 Select your next step.


If your turning-up solution is Then go to
Advanced SLAT step 11
the Node Setup application step 14

13 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/BA or NTK616AA/BA 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 21 in this procedure.
14 Seat one PKT/OTN XC circuit pack (NTK615AA/BA or NTK616AA/BA) 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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-19

Procedure 2-2 (continued)


Checking the current software release

Step Action

15 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.

16 Seat all remaining circuit packs that you must equip in the shelf.
17 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.
18 Select Active Alarms from the Faults drop-down menu.
19 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.
20 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.
21 Make sure you exit from the Site Manager session.
22 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—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-20 Nodal SLAT procedures

Procedure 2-3
Commissioning the network element using scripts
Use this procedure to commission a new Release 12.3 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 Blue Planet 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
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.

CAUTION
Risk of injury
Observe the safety guidelines in Installation - General
Information, 323-1851-201.0, and those recommended by
your company at all times.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-21

Procedure 2-3 (continued)


Commissioning the network element using scripts

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-22 Nodal SLAT procedures

Procedure 2-3 (continued)


Commissioning the network element using scripts

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-23

Procedure 2-3 (continued)


Commissioning the network element using scripts

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-24 Nodal SLAT procedures

Procedure 2-3 (continued)


Commissioning the network element using scripts

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-25

Procedure 2-3 (continued)


Commissioning the network element using scripts

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—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-26 Nodal SLAT procedures

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-3 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 11-1 on
page 11-3
• Gateway Connect with basic parameters, Member shelf — Table 11-2 on
page 11-7
• Gateway Connect with basic parameters, Primary with Members shelf —
Table 11-3 on page 11-10

Note: The Last Refresh field at the bottom of the Node Setup application
screen displays the NE time in GMT.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-27

Procedure 2-4 (continued)


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. Alternatively, If you are using the web launch
of Site Manager off the shelf processor, Java 1.7 (or higher) must be
installed. Java Web Start (JWS) is not supported on SPAP processor
circuit packs (NTK503MAE5, NTK503NAE5, NTK555LA, NTK555NA or
NTK555NB).
• 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”.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-28 Nodal SLAT procedures

Procedure 2-4 (continued)


Quick-start turning-up using the Node Setup application

Step Action

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


Identification in Table 2-2 on page 2-31 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-2 on page 2-31 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-2 on page 2-31 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
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-29

Procedure 2-4 (continued)


Quick-start turning-up using the Node Setup application

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 11-1 on page 11-3
• Member shelf — Table 11-2 on page 11-7
• Primary with Members shelf — Table 11-3 on page 11-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-2 on page 2-31 for provisioning rules.
• IP Address
• Subnet Mask
16 Click Apply to apply the COLAN Provisioning changes to the network
element.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-30 Nodal SLAT procedures

Procedure 2-4 (continued)


Quick-start turning-up using the Node Setup application

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-2 on page 2-31 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-2 on page 2-31 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 8 to step 22 to insert the required circuit
packs and check for alarms.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-31

Table 2-2
Node Setup application parameters

Parameter Value Description Mandatory

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
characters excluding the following
characters: backslash (\), space,
double-quote ("), colon (:), semicolon (;),
ampersand (&), greater than (>), less than
(<), 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
characters excluding the following
characters: backslash (\), space,
double-quote ("), colon (:), semicolon (;),
ampersand (&), greater than (>), less than
(<), or comma (,)

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-32 Nodal SLAT procedures

Table 2-2
Node Setup application parameters (continued)

Parameter Value Description Mandatory

For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.

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

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 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.

Shelf IP Address standard dot notation also known as circuitless IP address yes

OSPF Network standard dot notation sets the area yes


Area

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-33

Table 2-2
Node Setup application parameters (continued)

Parameter Value Description Mandatory

For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.

Site ID 0 to 65535 identifier of the site. Must be the same for all Site ID
NEs within a site. must be
In order for Visualization to work properly, the provisioned
Site ID on non-photonics shelves should be before the
set to match the Site ID of photonic shelves at photonic
the same site. layer is
defined.
For SPLI, alarm correlation, and OTS Can be
management to function, the Site ID must be provisioned
provisioned to a non-zero value. at this point
or after the
node setup
has
completed.

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)

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-34 Nodal SLAT procedures

Table 2-2
Node Setup application parameters (continued)

Parameter Value Description Mandatory

For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-35

Table 2-2
Node Setup application parameters (continued)

Parameter Value Description Mandatory

For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.

NE Configuration (continued)
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 the no


(default) 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 1 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 autoprovisioning no


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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-36 Nodal SLAT procedures

Table 2-2
Node Setup application parameters (continued)

Parameter Value Description Mandatory

For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-37

Table 2-2
Node Setup application parameters (continued)

Parameter Value Description Mandatory

For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.

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
Secondary RADIUS servers

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
Secondary RADIUS servers

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-38 Nodal SLAT procedures

Table 2-2
Node Setup application parameters (continued)

Parameter Value Description Mandatory

For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.

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
a TIDc that will be managed by OneControl, it
is preferable to enable the SNMP proxy.

Request Timeout numeric value timeout value for SNMP requests – option no
disabled for standalone NEs and member
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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-39

Table 2-2
Node Setup application parameters (continued)

Parameter Value Description Mandatory

For more information on parameters, see Administration and Security, 323-1851-301, and Fault
Management - SNMP, 323-1851-740.

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-40 Nodal SLAT procedures

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-3 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
To perform this procedure you must:
• have Java 1.7 (or higher) software installed on your craft computer if you
are using a web browser to launch SAT. Java Web Start (JWS) is not
supported on SPAP processor circuit packs (NTK503MAE5,
NTK503NAE5, NTK555LA, NTK555NA or NTK555NB).
• If you are launching SAT from the installed version of Site Manager, you
do not have to install Java. (In this case, SAT uses the Java software
included in the Site Manager installation.)
• use an account with a UPC level of 4 or higher
• 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-41

Procedure 2-5 (continued)


Launching Advanced SLAT and logging in

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 If you wish to launch the Nodal SLAT Assistant Tool Then go to
within Site Manager step 9
without Site Manager step 16

9 Launch Site Manager.


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.
14 Select your next step.
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. Go to step 20.
16 Launch a web browser, Internet Explorer, for example.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-42 Nodal SLAT procedures

Procedure 2-5 (continued)


Launching Advanced SLAT and logging in

Step Action

17 Enter the IP address of the network element in the URL field, and press
Enter. The default IP address of an NE is 10.0.0.1.
18 In the web page, click the Launch Nodal SLAT Assistant Tool link.
19 On the next web page, click Launch Advanced SAT. If a security warning
dialog appears, click Continue. If any pop up dialogs appear, accept them if
you agree. You must accept them in order for the Advanced SLAT to run. Then
run the tool. If the required Java version is not installed, a warning dialog
appears, select Run with the latest version.
A Login screen appears.
Logging into the SLAT Assistant Tool
20 In the Login screen, leave the Domain at the Default domain.
21 Enter the username and password (ADMIN/ADMIN by default).
22 Click Login.
23 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).
24 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—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-43

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-3
on page 1-13 for detailed information.

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
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.

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-44 Nodal SLAT procedures

Procedure 2-6 (continued)


Commissioning a network element using Advanced SLAT

Note: SuperMux, FLEX MOTR, and L2 MOTR circuit packs can be shelf
timed or self timed after the commissioning depending on whether the
circuit pack gets autoprovisioned before or after the XC. If you want all
SuperMux, FLEX MOTR, or L2 MOTR circuit packs to be shelf timed, you
can commission the shelf without these circuit packs equipped in the shelf
and equip them after the commissioning has been completed. If you want
all these circuit packs to be self timed, you can leave these circuit packs
equipped in the shelf during the commissioning procedure. After the
commissioning has been completed, you can use the “Provisioning an
independent timing group” procedure in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310, to change the timing to self
timed.

Prerequisites
To perform this procedure you must
• 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)
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the NE Identification
Commissioning Step highlighted

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-45

Procedure 2-6 (continued)


Commissioning a network element using Advanced SLAT

Step Action

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-3 on page 1-13 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-3 on page 1-13 for provisioning rules.
6 Click Apply to apply the changes to the network element.
This step can take up to 90 seconds to complete.
7 Click Next.
The next Commissioning Step panel appears.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-46 Nodal SLAT procedures

Procedure 2-6 (continued)


Commissioning a network element using Advanced SLAT

Step Action

8 Enter the Shelf Number in the NE Configuration IPv4 panel.


9 Click Apply to apply the changes to the network element.
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-3 on page 1-13 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.
12 Click Apply to apply the changes to the network element.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-47

Procedure 2-6 (continued)


Commissioning a network element using Advanced SLAT

Step Action

13 Select your next step.


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-3 on page 1-13
and Table 1-5 on page 1-37). An asterisk (*) denotes mandatory parameters,
which must be entered, if enabled.
15 Click Apply to apply the changes to the network element.
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.
The next Commissioning Step panel appears.
18 Select your next step.
If your shelf Then go to
is equipped with NTK615AA/BA or NTK616AA/BA step 19
PKT/OTN cross-connect (XC) circuit packs
is not equipped with NTK615AA/BA or NTK616AA/BA step 26
PKT/OTN cross-connect (XC) circuit packs

19 Seat one PKT/OTN XC circuit pack (NTK615AA/BA or NTK616AA/BA) 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.
20 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-48 Nodal SLAT procedures

Procedure 2-6 (continued)


Commissioning a network element using Advanced SLAT

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.
25 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.
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-3
on page 1-13 for provisioning rules).
30 Click Confirm Completion to apply the changes to the network element.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-49

Procedure 2-6 (continued)


Commissioning a network element using Advanced SLAT

Step Action

31 Select your next step.


If Then go to
you must provision the IPv6 panel also step 32
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.
The next Commissioning Step panel appears.
Go to Procedure 2-7, “Enabling or disabling auto-equipping”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-50 Nodal SLAT procedures

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• 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-85 for 2-slot optical Type 2 shelf with SPAP
• 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.
3 Click Apply to apply the changes to the network element.
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-51

Procedure 2-7 (continued)


Enabling or disabling auto-equipping

Step Action

5 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-8, “Performing a lamp test”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-52 Nodal SLAT procedures

Procedure 2-8
Performing a lamp test
Use this procedure to verify that all LEDs on the shelf are working properly.

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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.
Note: NTK503MAE5/NAE5 2-slot shelf integrated Access Panel lamps on
the PWR OK A will not light during a lamp test if there is no power on feed A
and PWR OK B will not light during a lamp test if there is no power B on feed
B.
2 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-9, “Provisioning OSPF router parameters”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-53

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted

Step Action

1 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 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).

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-54 Nodal SLAT procedures

Procedure 2-9 (continued)


Provisioning OSPF router parameters

Step Action

3 Enter the other parameters in the rest of the fields, as applicable. Refer to
Table 1-4 on page 1-32 for provisioning rules.
A Delete button is available if you want to delete the entry.
4 Click Apply to apply the changes to the network element.
5 Select your next step.
If Then go to
you must provision the IPv6 panel also step 6
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-5 on page 1-37 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.
7 Click Apply to apply the changes to the network element.
8 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-10, “Provisioning ILAN”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-55

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted

Step Action

1 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 for Then go to
IPv4 step 2
IPv6 step 7

2 In the ILAN Provisioning panel, Click Add.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-56 Nodal SLAT procedures

Procedure 2-10 (continued)


Provisioning ILAN

Step Action

3 In the Add ILAN port data dialog box:


• select an ILAN port
• 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.
• enter the subnet mask
• 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.
• select the routing protocol (NONE, OSPF, IISIS, or OSPF/IISIS)
• provision the circuit parameters (see Table 1-4 on page 1-32)
• 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.
6 Select your next step.
If Then go to
you must provision the IPv6 panel also step 7
otherwise step 11

7 In the IPv6 panel, click Add.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-57

Procedure 2-10 (continued)


Provisioning ILAN

Step Action

8 Enter the required information in the Add ILAN port data dialog box:
• select an ILAN port
• 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.
• enter the subnet mask
• 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.
• select the routing protocol (NONE or OSPF)
• provision the circuit parameters (see Table 1-5 on page 1-37)
• 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.
The next Commissioning Step panel appears.
Go to Procedure 2-11, “Provisioning Shelf IP address”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-58 Nodal SLAT procedures

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have SLAT Assistant Tool open with the Commissioning Step highlighted
• ensure that the shelf IP address is not defined

Step Action

1 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 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-59

Procedure 2-11 (continued)


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-4 on page
1-32)
IISIS the IISIS circuit parameters (see Table 1-4 on page 1-32)
OSPF/IISIS both the OSPFv2 and IISIS circuit parameters (see Table
1-4 on page 1-32)

5 Click Apply to apply the changes to the shelf.


6 If a confirmation dialog appears, click Yes in the confirmation dialog.
7 Select your next step.
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-5 on page 1-37.
Then, click Confirm Completion and click Apply to apply the changes to the
shelf.
10 Click Next.
The next Commissioning Step panel appears.
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—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-60 Nodal SLAT procedures

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.

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.

If you will be provisioning IISIS router parameters during the Shelf IP, COLAN,
or DCC 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 DCC Provisioning steps overwrites the router provisioning
performed at the IISIS Router Provisioning step.

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted

Step Action

1 In the IISIS Router Provisioning panel, enter the parameters in the fields, as
applicable. See Table 1-4 on page 1-32 for parameter details.
A Delete button is available if you want to delete the entry.
2 Click Apply to apply the changes to the network element.
3 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-13, “Provisioning COLAN”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-61

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 (not available on a 2-slot shelf with integrated SP or SPAP),
provides Ethernet access to the SP in slot 15 (or 41) and 16 (or 42)

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted

Step Action

1 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 for Then go to
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-3 on page 1-13 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-4 on page 1-32).
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-62 Nodal SLAT procedures

Procedure 2-13 (continued)


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.
6 Select your next step.
If Then go to
you must provision the IPv6 panel also step 7
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-3 on
page 1-13.
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.
The next Commissioning Step panel appears.
Go to Procedure 2-14, “Provisioning proxy ARP (IPv4)/ND Proxy Provisioning
(IPv6)”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-63

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted

Step Action

1 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 for Then go to
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-64 Nodal SLAT procedures

Procedure 2-14 (continued)


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

Step Action

4 Click OK in the Add dialog box.


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.
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 to delete the entry.
5 In the Proxy ARP Provisioning panel, click Confirm Completion.
6 Select your next step.
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.
9 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 to delete the entry.
10 Click Confirm Completion in the IPv6 (NDP Provisioning) panel to apply the
changes to the network element.
11 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-15, “Provisioning NAT”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-65

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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.
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 to delete the entry.
4 In the NAT Provisioning panel, click Confirm Completion.
5 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-16, “Provisioning Dynamic NAT”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-66 Nodal SLAT procedures

Procedure 2-16
Provisioning Dynamic NAT
Use this procedure to provision the Dynamic network address translation
(NAT). This procedure applies to IPv4 only.

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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.
The next Commissioning Step panel appears.
Go to Procedure 2-17, “Provisioning Port Filtering”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-67

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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-3 on page 1-13 for provisioning values.
2 Click OK in the Add dialog box.
A new row, with the entered values, is added to the table.
A Delete button is available if you want to delete the entry.
3 Click on the Confirm Completion button.
4 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-18, “Provisioning Reverse Port NAT”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-68 Nodal SLAT procedures

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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-3 on page 1-13 for provisioning values.
2 Click OK in the Add dialog box.
A new row, with the entered values, is added to the table.
A Delete button is available if you want to delete the entry.
3 Click on the Confirm Completion button.
4 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-19, “Provisioning Neighbor Discovery Protocol”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-69

Procedure 2-19
Provisioning Neighbor Discovery Protocol
Use this procedure to enable or disable the NDP (Neighbor Discovery
Protocol) feature on the shelf.

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• 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.
The next Commissioning Step panel appears.
Go to Procedure 2-20, “Provisioning static routes”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-70 Nodal SLAT procedures

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
highlighted

Step Action

1 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 for Then go to
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-3 on page 1-13 for parameter
details. An asterisk (*) denotes mandatory parameters, which must be
entered, if enabled.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-71

Procedure 2-20 (continued)


Provisioning static routes

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 Repeat step 2 to step 4 for the other static routes, if applicable.
6 In the IPv4 Static Routes Provisioning panel, click Confirm Completion.
7 Select your next step.
If Then go to
you must provision the IPv6 panel also step 8
otherwise step 12

8 In the IPv6 Static Routes Provisioning panel, click Add. See Table 1-3 on
page 1-13 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).
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.
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.
The next Commissioning Step panel appears.
Go to Procedure 2-21, “Provisioning OSPF routes distribution”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-72 Nodal SLAT procedures

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)

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.

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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-3 on page 1-13 “OSPF - Routes Distribution”
section in Table 1-4 on page 1-32 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)
3 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 to delete an entry.
4 Repeat step 1 to step 3 for the other routes, if applicable.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-73

Procedure 2-21 (continued)


Provisioning OSPF routes distribution

Step Action

5 In the OSPF - Routes Distribution panel, verify the route distribution data.
Then click Confirm Completion.
6 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-22, “Provisioning IISIS routes distribution”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-74 Nodal SLAT procedures

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)

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.

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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-4 on page
1-32 for parameter details.
3 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 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.
The next Commissioning Step panel appears.
Go to Procedure 2-23, “Provisioning SNMP”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-75

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

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
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.

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-76 Nodal SLAT procedures

Procedure 2-23 (continued)


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.
The next Commissioning Step panel appears.
Go to Procedure 2-24, “Provisioning security”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-77

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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-3 on page 1-13
for parameter details.
2 In the Security provisioning panel, click Apply to apply the changes.
3 Click Next.
The next Commissioning Step panel appears.
Go to Procedure 2-25, “Provisioning SSH/TELNET and HTTP/HTTPS
Server”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-78 Nodal SLAT procedures

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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.
The next Commissioning Step panel appears.
Go to Procedure 2-26, “Provisioning craft access”.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-79

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.

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.

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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-3 on page 1-13 for parameter details.
7 Click OK in the dialog box.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-80 Nodal SLAT procedures

Procedure 2-26 (continued)


Provisioning craft access

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.
9 Select your next step.
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-81

Procedure 2-26 (continued)


Provisioning craft access

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—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-82 Nodal SLAT procedures

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).

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.

Prerequisites
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element
• have the SLAT Assistant Tool open with the Commissioning Step
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-32 or “OSPFv3 parameters—SLAT Assistant
Tool - IPv6” on page 1-37 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—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-83

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
To perform this procedure you must
• use an account with a UPC level of 4 or higher
• be logged into the network element

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—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-84 Nodal SLAT procedures

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
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.

• 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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-85

Procedure 2-29 (continued)


Post SLAT commissioning

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-86 Nodal SLAT procedures

Procedure 2-29 (continued)


Post SLAT commissioning

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.
You have completed this task. Go to step 1.
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.
You have completed this task. Go to step 1.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Nodal SLAT procedures 2-87

Procedure 2-29 (continued)


Post SLAT commissioning

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.
18 Select Backup and Restore from the Configuration menu.
19 In the Backup and Restore panel, select the Backup tab.
20 In the URL field enter “file:”.
21 Click Check to perform pre-checks on the network element.
22 Click Save to save the provisioning data to the shelf processor.
Restoring the golden database onto the newly commissioned NEs
23 Select Backup and Restore from the Configuration menu.
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.
27 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 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2-88 Nodal SLAT procedures

Procedure 2-29 (continued)


Post SLAT commissioning

Step Action

34 Check that DCC/GCC communications have been preserved. If the DCC/


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 DCC/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.
You have completed this task. Go to step 1.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-1

Photonic layer provisioning procedures 3-

This chapter contains the following topics:


• “Abbreviations used in this chapter” on page 3-1
• “Photonic layer provisioning procedures” on page 3-3
• “Procedures” on page 3-4

Abbreviations used in this chapter


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

CMD channel mux/demux

COADM colorless optical add/drop multiplexer

CS Coherent Select

DGFF dynamic gain flattening filter

DIA direction independent access

DOC domain optical control

DSCM dispersion slope compensation module

EDP engineering documentation package

ESAM enhanced service access module

FEC forward error correction

FGA fixed gain amplifier

IDP international documentation package

LAN local area network

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-2 Photonic layer provisioning procedures

LIM line interface module

MLAx MLA, MLA2, or MLA3 amplifiers

NE network element

NTP network timing protocol

OMDF optical mux/demux filter

OPM optical power monitor

ORL optical return loss

OSC optical service channel

OSCF OSC filter

OTS optical transport sections

RLA ROADM with line amplifier

ROADM reconfigurable optical add/drop multiplexer

Rx receive

SAM service access module

SAT SLAT Assistant Tool

SBS stimulated Brillouin scattering

SCMD serial channel mux/demux

SLAT system lineup and testing

SMD selective Mux/Demux

SP shelf processor

SRA single line Raman amplifier

TL-1 transaction language 1

TOADM thin optical add/drop multiplexer

TR transmit/receive

TTI trail trace identifier

Tx transmit

WSS wavelength selective switch

WSSOPM wavelength selective switch with optical power monitor

XLA switchable line amplifier

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-3

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:

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-4 Photonic layer provisioning procedures

— Advanced SLAT Assistant Tool - Table 1-3


— Node Setup application - Table 2-2
• 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.

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 5-1.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-5

Table 3-1
Procedures in this chapter
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”

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-6 Photonic layer provisioning procedures

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)
• the excess loss parameter on the OSC (2xOSC or SPAP-2 [with OSC
SFP] circuit packs, SRA/ESAM/SAM circuit packs)

For passive OTS network provisioning, see “Passive OTS network


procedures” on page 5-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
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-7

Procedure 3-1 (continued)


Provisioning photonic parameters

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.

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 1 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
Configuration - Provisioning and Operating, 323-1851-310.
• 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-8 Photonic layer provisioning procedures

Procedure 3-1 (continued)


Provisioning photonic parameters

Step Action

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 or
the XLA equipment.
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, and MLA3 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).
6 The AID of a pre-amplifier is AMP-<shelf>-<slot>-8.
7 Click Edit in the Facility area.
8 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 9 to continue the facility
Note: For RLA, only applies to pre-amplifier provisioning
(AMP-<shelf>-<slot>-8).
otherwise step 13
9 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.
10 Set the AMP facility of the XLA/RLA out of service (OOS) and click Apply in
the Edit facility dialog box.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-9

Procedure 3-1 (continued)


Provisioning photonic parameters

Step Action

11 Set the XLA/RLA gain mode as per the OnePlanner report.


12 Set the AMP facility of the XLA/RLA back to its initial service state.
13 Click OK in the Edit facility dialog box.
14 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 Click Edit in the Facility area.
16 In the Edit facility dialog box, edit VOA facility parameters (set the VOA Reset
Required and Target Pad as indicated in the EDP/IDP).
17 Click OK in the Edit facility dialog box.
18 Repeat step 4 to step 17 for each line facing amplifier, XLA, or RLA.
Provisioning RAMAN parameters
19 Verify that the RAMAN facility has been created.
20 In the Equipment table, select the SRA equipment.
21 Select RAMAN in the Facility Type drop down list.
22 Click Edit in the Facility area.
23 In the Edit facility dialog box, edit RAMAN facility parameters as indicated in
the EDP/IDP.
24 When you are finished, click OK in the Edit facility dialog box.
25 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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-10 Photonic layer provisioning procedures

Procedure 3-1 (continued)


Provisioning photonic parameters

Step Action

Provisioning the fiber type on SRA circuit packs (TELEMETRY facility)


26 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 TELEMETRY 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.
Provisioning cascaded amplifier
27 In the Equipment table, select the LIM equipment for a cascaded SLA circuit
pack.
28 Select AMP from the Facility Type drop down list.
29 Click Edit in the Facility area.
30 In the Edit facility dialog box, edit AMP facility parameters (set the target gain
tilt, target peak power as indicated in the EDP/IDP).
31 Click OK in the Edit facility dialog box.
32 Select OPTMON in the Facility Type drop down list.
33 Select the OPTMON facility corresponding to the Line B In port (OPTMON-
<shelf>-<slot>-6) and click Edit in the Facility area.
34 In the Edit facility dialog box, set the Primary state to OOS and click OK.
Verify that the OPTMON LOS alarm corresponding to the cascaded SLA
circuit pack clears.
35 Repeat step 27 to step 34 for each cascaded amplifier.
Provisioning DIA amplifier
36 In the Equipment table, select the LIM equipment for a DIA amplifier circuit
pack.
37 Select AMP from the Facility Type drop down list.
38 Click Edit in the Facility area.
39 In the Edit facility dialog box, edit AMP facility parameters (set the target gain
as per the OnePlanner report).
40 Click OK in the Edit facility dialog box.
41 Repeat step 36 to step 40 for each DIA amplifier.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-11

Procedure 3-1 (continued)


Provisioning photonic parameters

Step Action

42 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.
43 If Then go to
you are provisioning a channel pad step 48
you are provisioning a DSCM or non-channel pad step 44
you are provisioning the excess loss on OSC step 50
(insertion of pad)
you have completed DSCM, pad, or excess loss you have completed
provisioning this procedure

Provisioning DSCMs and non-channel pads


44 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 45.
45 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 DSCM from the Type drop-down list.
c. Select the appropriate PEC of the DSCM/pad from the Provisioned PEC
drop-down list.
d. Select the slot number (external or virtual slot).
e. Click OK.
46 Repeat step 44 or step 45 for each DSCM and non-channel pad.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-12 Photonic layer provisioning procedures

Procedure 3-1 (continued)


Provisioning photonic parameters

Step Action

47 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 43.
Provisioning pads for channel Tx/Rx
48 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.
49 Repeat step 48 for each channel pad.
Go to step 43.
Provisioning the excess loss parameter on OSC (insertion of pad)
50 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.

51 If SRA/ESAM/SAM equipment is present:


a. Select the SRA/ESAM/SAM-SH-SL circuit pack in the Equipment area.
b. Select ADJ-FIBER in the Facility Type drop-down menu.
c. Select ADJ-SH-SL-2 (Adjacency Type LIM).
d. Click Edit.
e. Enter the parameter value in the Excess Loss field.
f. Click OK.
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-13

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, all adjacencies are automatically system derived.

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-165),
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-167)
• 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-191)

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-14 Photonic layer provisioning procedures

Procedure 3-2 (continued)


Provisioning adjacencies

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-23 for the CMD-OPM adjacencies,
• “LIM-OPM adjacencies” on page 3-24 and “LIM-OPM adjacencies in XLA
case” on page 3-24 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-15

Procedure 3-2 (continued)


Provisioning adjacencies

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-16 Photonic layer provisioning procedures

Procedure 3-2 (continued)


Provisioning adjacencies

Prerequisites
• Ensure that the commissioning procedures (using Node Setup or
Advanced SLAT) have been completed.
• Use an account with a UPC level of 3 or higher.
• 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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-17

Procedure 3-2 (continued)


Provisioning adjacencies

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).
5 Click Edit in the Facility area.
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.
12 Click Edit in the Facility area.
13 In the Edit facility dialog box, modify the Fiber Type as indicated in the EDP/
IDP.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-18 Photonic layer provisioning procedures

Procedure 3-2 (continued)


Provisioning adjacencies

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
indicated in the EDP/IDP.
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.
19 Select ADJ in the Facility Type drop down list.
20 Select the CMD44 monitor port (port 92) or CMD64 monitor port (port 129 or
port 130).
21 Click Edit in the Facility area.
22 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.
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).

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-19

Procedure 3-2 (continued)


Provisioning adjacencies

Step Action

Provision WSS-WSS or RLA-RLA adjacencies


24 Select your next step.
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.
otherwise go to step 25

25 In the Equipment table, select the WSSOPM or RLA equipment for one end
of the WSS-WSS link.
26 Select ADJ in the Facility Type drop down list.
27 Select the adjacency corresponding to the WSS or RLA output port.
28 Click Edit in the Facility area.
29 In the Edit facility dialog box:
• select WSS or RLA 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 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.
31 Select ADJ in the Facility Type drop down list.
32 Select the adjacency corresponding to the WSS or RLA output port.
33 Click Edit in the Facility area.
34 In the Edit facility dialog box:
• select WSS or RLA 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 connecting WSS or RLA circuit pack’s input port AID.
• click OK
If this is a DGFF site, you have completed this procedure.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-20 Photonic layer provisioning procedures

Procedure 3-2 (continued)


Provisioning adjacencies

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.
37 Select ADJ in the Facility Type drop down list.
38 Select the adjacency corresponding to the SMD Common Out (port 10).
39 Click Edit in the Facility area.
40 In the Edit facility dialog box:
• 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.
42 Select ADJ in the Facility Type drop down list.
43 Select the adjacency corresponding to the MLA circuit pack Line B Out (port
5).
44 Click Edit in the Facility area.
45 In the Edit facility dialog box:
• select SMD 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 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-165)
46 In the Equipment table, select the cascaded MLA3 equipment for the LIM-
WSS link.
47 Select ADJ in the Facility Type drop down list.
48 Select the adjacency corresponding to the Line B Out (port 5).
49 Click Edit in the Facility area

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-21

Procedure 3-2 (continued)


Provisioning adjacencies

Step Action

50 In the Edit facility dialog box:


• select WSS 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 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.
52 Select ADJ in the Facility Type drop down list.
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).
54 Click Edit in the Facility area.
55 In the Edit facility dialog box:
• 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 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-22 Photonic layer provisioning procedures

Procedure 3-2 (continued)


Provisioning adjacencies

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.
64 Select ADJ in the Facility Type drop down list.
65 Select the equipment monitor port (port 1 or port 2).
66 Click Edit in the Facility area.
67 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 enter
the Expected far end address as indicated in the EDP/IDP. This address
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
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-23

Figure 3-1
CMD44-OPM adjacencies

2-port OPM

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-24 Photonic layer provisioning procedures

Figure 3-2
LIM-OPM adjacencies

Figure 3-3
LIM-OPM adjacencies in XLA case

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-25

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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-26 Photonic layer provisioning procedures

Procedure 3-3 (continued)


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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-27

Procedure 3-3 (continued)


Changing amplifier provisioning targets and differential provisioning settings on an existing
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.
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 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.
c. Perform step 9 to step 15 to re-optimize the network.
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-28 Photonic layer provisioning procedures

Procedure 3-3 (continued)


Changing amplifier provisioning targets and differential provisioning settings on an existing
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.
13 Select your next step.
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer provisioning procedures 3-29

Procedure 3-3 (continued)


Changing amplifier provisioning targets and differential provisioning settings on an existing
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—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
3-30 Photonic layer provisioning procedures

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
• Use an account with a UPC level of 3 or higher.
• Log into the network element using Site Manager and launch the
Equipment & Facility Provisioning application from the Configuration
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—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
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 5-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 CLI, REST API, gRPC and Waveserver-6500
Interworking, 323-1851-165.

This chapter contains the following topics:


• “Abbreviations used in procedures” on page 4-1
• “Photonic layer site testing procedures” on page 4-3

Abbreviations used in procedures


ARP address resolution protocol
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
CMD channel mux/demux
COADM colorless optical add/drop multiplexer
COLAN central office LAN
CS Coherent Select
DCN data communications network
DGFF dynamic gain flattening filter

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-2 Photonic layer site testing procedures

DHCP dynamic host configuration protocol


DIA direction independent access
DSCM dispersion slope compensation module
EBER excessive bit error rate
EDP engineering documentation package
ESAM enhanced service access module
GCC general communications channel
GNE gateway network element
ID identifier
IDP international documentation package
IISIS integrated ISIS
ILAN intershelf LAN
IP Internet protocol
LAN local area network
LED light emitting diode
LIM line interface module
MLAx MLA, MLA2, or MLA3
MPO Multifiber Push-on
NAT network address translation
NE network element
NTP network timing protocol
OBB Optical Bridge and Broadcast
OBMD Optical Broadband Mux/Demux
OPM optical power monitor
ORL optical return loss
OSC optical service channel
OSPF open shortest path first
OTS optical transport sections
PC personal computer
PEC product engineering code
ROADM reconfigurable optical add/drop multiplexer
Rx receive
SAM service access module
SAT SLAT Assistant Tool
SBS stimulated Brillouin scattering
SCMD serial channel mux/demux
SLAT system lineup and testing
SMD selective mux/demux
SNMP simple network management protocol
SP shelf processor

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-3

SRA single line Raman amplifier


TL-1 transaction language 1
TOADM thin optical add/drop multiplexer
Tx transmit
UDP user datagram protocol
UPC user privilege code
WSS wavelength selective switch
WSSOPM wavelength selective switch with optical power monitor
WT wavelength translator
XLA switchable line amplifier

Photonic layer site testing procedures


The following table lists the procedures in this chapter. Perform the
procedures as applicable.

Table 4-1
Procedures in this chapter

Procedure
Procedure 4-1, “Connecting intra-site fibers for TOADM/ROADM/DGFF/DIA/Colorless OADM sites”
Procedure 4-2, “Adding a new CMD44, CMD64, 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)”
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 configurations (CCMD12/CMD44/CMD64
connected to 1x20 WSS)”
Procedure 4-16, “Testing a line amplifier node”

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-4 Photonic layer site testing procedures

Table 4-1
Procedures in this chapter (continued)

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 OMD4/CMD44 or OMX point-to-point terminal”
Procedure 4-25, “Equalizing a thin terminal system”
Procedure 4-26, “Configuring a remote CMD44 terminal”

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-5

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-39
• “Intra-NE fiber connections at a ROADM site with interior SLA” on page
4-40
• “Intra-NE fiber connections at a ROADM site with single 2xOSC circuit
pack” on page 4-41
• “Intra-NE fiber connections at a ROADM site (example shows XLA and
SRA)” on page 4-42
• “Intra-NE fiber connections at a ROADM site (CMD44 and CMD64)” on
page 4-43
• “Intra-NE fiber connections at a ROADM site using RLA/CMD64” on page
4-44
• “Intra-NE fiber connections at a ROADM site using RLA/CMD44” on page
4-45
• “Intra-NE fiber connections at a ROADM site using RLA/CMD64 with
ESAM/SAM/SRA (SAM shown)” on page 4-46
• “Intra-NE fiber connections at a ROADM site using RLA/CMD44 with
ESAM/SAM/SRA (SRA shown)” on page 4-47
• “Intra-NE fiber connections between a low channel count DIA and
backbone OTS” on page 4-48
• “Intra-NE fiber connections at a ROADM site with XLA and SRA - DSCM
placement” on page 4-49
• “Intra-NE fiber connections at a ROADM site with ESAM-MLAx (example
shows MLA)” on page 4-49
• “Intra-NE fiber connections (CMD44 to BMD2 to WSS)” on page 4-50
• “Intra-NE fiber connections (CMD44 to BMD2 to SLA to WSS)” on page
4-51
• “Intra-NE fiber connections (CMD44 to Drop LIM to WSS)” on page 4-52

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-6 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

• “Intra-NE fiber connections between a 100 GHz DIA and backbone OTS”
on page 4-53
• “Intra-NE fiber connections between a 50 GHz DIA and backbone OTS”
on page 4-54
• “Intra-NE fiber connections at a Colorless OADM site” on page 4-55
• “Intra-NE fiber connections at a Colorless OADM site with CMD44 50GHz”
on page 4-56
• “Intra-NE fiber connections at a low channel count DIA site (non-OTS
equipment)” on page 4-57
• “Intra-NE fiber connections at a CDC ROADM site (CCMD8x16)” on page
4-58
• “Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and
CMD44 50 GHz)” on page 4-59
• “Intra-NE fiber connections at a CDC ROADM site (CCMD8x16 and
CMD44 100 GHz)” on page 4-60

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-61
• “Intra-NE fiber connections at a DGFF site (RLA)” on page 4-62
• “Intra-NE fiber connections at a DGFF site (RLA with SAM/ESAM/SRA)”
on page 4-63

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”

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-7

Procedure 4-1 (continued)


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

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)”
• Colorless CMD Direct Attach sites, see Procedure 4-14, “Connecting
intra-site fibers for a Colorless Direct Attach configuration
(CCMD12/CMD44/CMD64 connected to 1x20 WSS)”
• Coherent Select sites, see Procedure 4-18, “Connecting intra-site fibers
for Coherent Select sites”

For configurations with colored CMDs (CMD44and CMD64):


• The colored CMDs must be added to a degree using TID-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 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-8 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

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
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.

Step Action

1 Select your first step.


If Then
you are connecting OSC to the make sure to read the Attention
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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-9

Procedure 4-1 (continued)


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

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).
4 Select your next step.
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

5 Connect the 2xOSC OSC-2 Out port to the OSC In (port 3) of the appropriate
line facing circuit pack. Ensure that the OSC-2 is connected to the line facing
circuit pack as indicated in the EDP/IDP (in the correct slot).
6 Connect the 2xOSC OSC-2 In port to the OSC Out (port 4) of the appropriate
line facing circuit pack. Ensure that the OSC-2 is connected to the line facing
circuit pack as indicated in the EDP/IDP (in the correct slot).
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).

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-10 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

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
OSC-1 is connected to the line facing circuit pack as indicated in the EDP/IDP
(in the correct slot).
Then go to step 1.
Making OSC connections on SRA/ESAM/SAM
9 Make sure to read and observe the following CAUTION and Attention.
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-11

Procedure 4-1 (continued)


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

Step Action

10 On the SRA/ESAM/SAM circuit pack, connect the OSC SFP Tx port to the
OSC In port (Port 3).
11 Select your next step.
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.
16 Select your next step.
If you are performing intra-NE fibering at a Then go to
line amplifier site step 17
TOADM site step 53
ROADM site step 63

Connecting intra-NE fibers at a line amplifier site


17 Select your next step.
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
otherwise step 46

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-12 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

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-34 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-34). The
other OTS contains the second line facing circuit pack (OTS2 in Figure 4-3 on
page 4-34).
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).
Ensure the correct fixed pad is inserted in the connection as indicated in the
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-13

Procedure 4-1 (continued)


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

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 51.
Performing intra-NE fibering at a line amplifier site equipped with ESAM +MLAx+ESAM
26 See Figure 4-4 on page 4-35 for an example of intra-NE fibering at a line
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-35). The other OTS
contains the second ESAM (OTS2 in Figure 4-4 on page 4-35).
Make sure to fiber correctly. The system derives the adjacencies based on the
OTS slot sequence provisioning.
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-35). 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.
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
indicated in the EDP/IDP.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-14 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

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 51.
Performing intra-NE fibering at a line amplifier site equipped with ESAM -MLAx-MLAx-ESAM
32 See Figure 4-5 on page 4-36 for an example of intra-NE fibering at a line
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-36). The other OTS
contains the second MLAx and the second ESAM (OTS2 in Figure 4-5 on
page 4-36).
Make sure to fiber correctly. The system derives the adjacencies based on the
OTS slot sequence provisioning.
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.
34 If not connected in step 33, 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.
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-36). 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.
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-15

Procedure 4-1 (continued)


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

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-36). 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.
39 Perform step 33 to step 38 for the opposite direction. The port numbers are
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 51.
Performing intra-NE fibering at a line amplifier site equipped with ESAM-MLAx-MLAx
40 See Figure 4-6 on page 4-37 for an example of intra-NE fibering at a line
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-37). The other OTS contains
the second MLAx (OTS2 in Figure 4-6 on page 4-37).
Make sure to fiber correctly. The system derives the adjacencies based on the
OTS slot sequence provisioning.
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
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.
42 If not connected in step 41, 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-16 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

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-37). 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.
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
connection as indicated in the EDP/IDP.
45 Perform step 41 to step 44 for the opposite direction. The port numbers are
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 51.
46 See Figure 4-1 on page 4-32 or Figure 4-2 on page 4-33 for an example of
intra-NE fibering at a line amplifier site.
47 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
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.
48 If not connected in step 47, 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 47. Ensure the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.
49 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.
50 If not connected in step 49, 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 49. Ensure that the correct fixed pad is inserted in the
connection as indicated in the EDP/IDP.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-17

Procedure 4-1 (continued)


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

Step Action

51 Select your next step.


If Then go to
you are connecting the XLA, or the line facing circuit step 52
pack if XLA is not present, to a 2-port OPM
otherwise You have completed
this procedure.

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


52 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.
You have completed this procedure.
Connecting intra-NE fibers at a TOADM site
53 See Figure 4-7 on page 4-38 to perform the steps for intra-NE fibering at a
TOADM site.
54 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 55 to step 57.
55 Connect the Common Out (port 2) of the SCMD4 to the Upgrade In (port 11)
of the next SCMD4.
56 Connect the Common In (port 1) of the SCMD4 to the Upgrade Out (port 12)
of the next SCMD4.
57 Repeat from step 55 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).
58 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.
59 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-18 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

Step Action

60 Select your next step.


If this is a Then
thin terminal site go to step 61
thin OADM site Repeat step 54 to step 59 for the OTS facing
the other direction. Then go to step 61.

61 If you are using the SCMD4, provision the SCMD4 cascade order according
to the EDP/IDP. Under Configuration -> Photonic Services -> SCMD
Cascading Order, select the line facing circuit pack and identify the SCMD4
in each position (position 1 is the one closest to the line facing circuit pack).
Select your next step.
If Then go to
you want to connect the line facing circuit pack to a step 62
2-port OPM
otherwise You have completed
this procedure.

Connecting LIM to 2-port OPM at a TOADM site


62 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.
You have completed this procedure.
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.
63 Select your next step.
If Then go to
this is a ROADM site that uses ESAM-MLAx step 89
this is a CDC ROADM site step 64
DGFF step 70
ROADM configuration (other than the above) step 70

64 See the following for examples of intra-NE fibering at a CDC ROADM site.
• Figure 4-28 on page 4-58
• Figure 4-29 on page 4-59
• Figure 4-30 on page 4-60

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-19

Procedure 4-1 (continued)


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

Step Action

65 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.
66 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-20 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

Step Action

67 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-21 on page
4-51.
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.
Note: The FIM upgrade ports connect to one of the two WSS high
isolation ports.
68 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.
Note: The FIM upgrade ports connect to one of the two WSS high
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.
Note: The FIM upgrade ports connect to one of the two WSS high
isolation ports.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-21

Procedure 4-1 (continued)


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

Step Action

69 Connect the FIM to the WSSOPM for all applicable ROADM degrees as
indicated in the EDP/IDP.
This equipment uses MPO connectors. See step 66 for instructions on how
to handle MPO cables and connectors.
Then go to step 71.
70 See:
• the following figures for examples of intra-NE fibering at ROADM sites:
— Figure 4-8 on page 4-39 - CMD44, WSS 1x5, MLA, dual 2xOSC
— Figure 4-9 on page 4-40 - CMD44, WSS 1x5, MLA, interior SLA, dual
2xOSC
— Figure 4-10 on page 4-41 - CMD44, WSS 1x5, MLA, interior SLA,
single 2xOSC
— Figure 4-11 on page 4-42 - CMD44, WSS 1x9, XLA, SRA
— Figure 4-12 on page 4-43 - CMD44, CMD64/XLA or MLA3, WSS 1x9,
amp
— Figure 4-13 on page 4-44 - CMD64, RLA
— Figure 4-14 on page 4-45 - CMD44, RLA
— Figure 4-15 on page 4-46 - CMD64, RLA, SAM
— Figure 4-16 on page 4-47 - CMD64, RLA, SRA
— Figure 4-17 on page 4-48 - low channel count DIA (WSS/CCMD12)
and backbone OTS (WSS and MLA3)
• the following figures for examples for examples of intra-NE fibering at a
DGFF site
— Figure 4-31 on page 4-61 - WSS 1x5, MLA, dual 2xOSC
— Figure 4-32 on page 4-62 - RLA, dual 2xOSC
— Figure 4-33 on page 4-63 - RLA, SAM
At sites equipped with XLA, the line facing circuit pack can be ESAM, SAM,
or SRA.
71 Select your next step.
If Then go to
the site uses SRA/ESAM/SAM and XLA/RLA circuit step 72
packs
otherwise step 81

72 Select your next step.


If a DSCM module is Then go to
present between SRA/ESAM/SAM and XLA step 73
not present step 79

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-22 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

Step Action

73 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.
74 If applicable, connect the first DSCM to the second DSCM.
75 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 73. 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.
76 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
the correct slot). Ensure the correct fixed pad is inserted in the connection as
indicated in the EDP/IDP.
77 If applicable, connect the first DSCM to the second DSCM.
78 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 76. 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.
Go to step 81.
79 Connect Line A Out (port 7) of the line facing circuit pack to the Line A In (port
8) of the XLA/RLA.
80 Connect the Line B In (port 6) of the line facing circuit pack to the Line B Out
(port 5) of the XLA/RLA.
81 Select your next step.
If a DSCM module is Then go to
present step 82
not present step 87

82 Select your next step.


If the DSCM module is located Then go to
between the output of the pre-amplifier and the step 83
input of the cascaded SLA line port (as per Figure
4-9 on page 4-40 or Figure 4-10 on page 4-41).
This branch also applies to XLA configurations.
at the end of span (before pre-amplifier) (as per step 86
Figure 4-8 on page 4-39). This branch does not
apply to XLA configurations.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-23

Procedure 4-1 (continued)


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

Step Action

83 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
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.
84 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 83.
85 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
connection as indicated in the EDP/IDP.
Go to step 88.
86 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.
87 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.
88 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 101.
89 See Figure 4-19 on page 4-49 for an example of intra-NE fibering at a
ROADM site with MLAx-ESAM configuration.
90 Select your next step.
If a DSCM module is Then go to
present between the ESAM and the MLAx step 91
not present step 97

91 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
the correct slot). Ensure the correct fixed pad is inserted in the connection as
indicated in the EDP/IDP.
92 If applicable, connect the first DSCM to the second DSCM.
93 Connect the DSCM Out port to the Line A In (port 8) of the MLAx. If only one
DSCM, the DSCM you are connecting is the same as in step 91. 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.
94 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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-24 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

Step Action

95 If applicable, connect the first DSCM to the second DSCM.


96 Connect Line B Out (port 5) of the MLAx to the DSCM In port. If only one
DSCM, the DSCM you are connecting is the same as in step 94. 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.
Go to step 81.
97 Connect Line A Out (port 7) of the ESAM to the Line A In (port 8) of the MLAx.
98 Connect the Line B In (port 6) of the ESAM to the Line B Out (port 5) of the
MLAx.
99 Connect the Common In (port number depends on the WSS) of the WSS to
the Line A Out (port 7) of the MLAx.
100 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
101 Select your next step.
If you are connecting to Then go to
WSS OPM step 102
2-port OPM step 103

102 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 104.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-25

Procedure 4-1 (continued)


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

Step Action

103 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.
To avoid misfibering, ensure that the patch cords are correctly labeled.
104 Repeat step 71 to step 103 for all ROADM/DGFF OTSs at the site.
Connecting WSS to WSS
105 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
indicated in the EDP/IDP.
106 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.
107 Repeat step 105 and step 106 for all the fiber connections required for
pass-through channels at the same site.
108 Select your next step.
If the site Then
has no channel access (DGFF site) you have completed
this procedure
is a ROADM site with CMD44 access go to step 109
is a ROADM site with CCMD12 access go to step 144
is a ROADM with a low channel count DIA go to step 157

109 Select your next step.


If you want to connect a CMD44/CMD64 module to Then go to
2-port OPM step 110
otherwise step 111

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-26 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

Step Action

Connecting CMD44/CMD64 to 2-port OPM


110 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
111 Select your next step.
If you want to connect a CMD44 module to Then go to
BMD2 module to WSS or RLA circuit pack step 112
BMD2 module to SLA circuit pack (DropLIM) to WSS step 116
circuit pack
WSS or RLA circuit pack step 122
SLA circuit pack (Drop LIM) to WSS circuit pack step 124
BMD2 module to amplifier in DIA configuration step 128
amplifier in DIA configuration step 132
have only CMD64 modules step 136

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)
- CMD2 defaults to SW9 (port 19,20)
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
- CMD1 defaults to SW2 (port 5,6)
- CMD2 is not auto-provisioned

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-27

Procedure 4-1 (continued)


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

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
112 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-20 on page 4-50.
113 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.
114 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.
115 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 134.
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)
116 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-21 on page 4-51.
117 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.
118 Connect the common Out of BMD2 (port 2) to the Line B In (port 6) of the SLA
circuit pack.
119 Connect the common In of BMD2 (port 1) to the Line A Out (port 7) of the SLA
circuit pack.
120 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.
121 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 134.
Connecting CMD44 to WSS or RLA
122 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-8 on page 4-39. For RLA, SW5 (Switch 5 In, port 29) is
recommended.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-28 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

Step Action

123 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 134.
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)
124 Connect the Common Out (port 90) of the CMD44 to the Line B In (port 6) of
the SLA circuit pack. See Figure 4-22 on page 4-52 for an example.
125 Connect the Common In (port 89) of the CMD44 to the Line A Out (port 7) of
the SLA circuit pack.
126 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.
127 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 134.
Connecting CMD44 to BMD2 to amplifier in DIA configuration
128 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-24 on page 4-54 for an example.
129 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.
130 Connect the Common Out (port 2) of the BMD2 to Line A In (port 8) of the
amplifier circuit pack.
131 Connect the Common In (port 1) of BMD2 to Line B Out (port 5) of the
amplifier circuit pack.
Go to step 134.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-29

Procedure 4-1 (continued)


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

Step Action

Connecting CMD44 to amplifier in DIA configuration


132 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-23 on page 4-53 for an
example.
133 Connect the Common In (port 89) of the CMD44 100 GHz to Line B Out
(port 5) of the amplifier circuit pack.
134 If required, repeat from step 109 for each CMD44 to be connected at the site.
135 For DIA, go to step 143. For CMD64s, go to step 136. Otherwise, you have
completed this procedure.
Connecting CMD64
136 Select your next step.
If you want to connect a CMD64 module to Then go to
amplified ports of WSS circuit pack or ports of RLA step 137
unamplified ports of WSS circuit pack with an amplifier step 139

Connecting CMD64 to amplified WSS ports or to unamplified RLA ports


137 Connect the Common Out (port 130) of the CMD64 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-12 on page 4-43 and Figure 4-13 on page 4-44.
138 Connect the Common In (port 129) of the CMD64 to the Switch Out port (or
Drop Out port for NTK553KA) of the WSS or RLA as indicated in the
EDP/IDP.
You have completed this procedure.
Connecting CMD64 to amplifier and then unamplified WSS ports
139 Connect the Common Out (port 130) of the CMD64 to Line A In (port 8) of the
amplifier circuit pack. See Figure 4-23 on page 4-53 for an example.
140 Connect the Common In (port 89) of the CMD44 100 GHz to Line B Out (port
5) of the amplifier circuit pack.
141 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.
142 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.
You have completed this procedure.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-30 Photonic layer site testing procedures

Procedure 4-1 (continued)


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

Step Action

Connecting intra-NE fibers for a DIA OTS


143 See Figure 4-23 on page 4-53 and Figure 4-24 on page 4-54 to perform the
steps for intra-NE fibering for a DIA OTS. See Figure 4-24 on page 4-54 to
perform
144 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)
To avoid misfibering, ensure that the patch cords are correctly labeled.
145 Connect the Common Out port of the DIA WSS to the DIA amplifier Line B In
(port 6).
146 Connect the Common In port of the DIA WSS to the DIA amplifier Line A Out
(port 7).
147 If required, repeat step 144 to step 146 for all DIA OTSs at the site.
148 Select your next step.
If the DIA OTS is Then
part of a Colorless OADM configuration go to step 149
otherwise you have completed this
procedure

Connecting intra-NE fibers for a COADM OTS


149 See Figure 4-25 on page 4-55 to perform the steps for intra-NE fibering for a
COADM OTS.
150 Connect the Common Out (port 26) of the CCMD12 to the Switch In port of
the SMD as indicated in the EDP/IDP.
151 Connect the Common In (port 25) of the CCMD12 to the corresponding
Switch Out port of the SMD as indicated in the EDP/IDP.
152 Connect the Monitor Out (port 27) of the CCMD12 to the corresponding
Monitor port of the SMD as indicated in the EDP/IDP.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-31

Procedure 4-1 (continued)


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

Step Action

153 Repeat step 150 and step 152 for each connected CCMD12.
154 Connect the Common Out (port 10) of the SMD to Line A In (port 8) of the
amplifier circuit pack in the DIA OTS.
155 Connect the Common In (port 9) of the SMD to Line B Out (port 5) of the
amplifier circuit pack in the DIA OTS.
156 Repeat step 150 to step 155 for all COADM OTSs at the site.
Connecting intra-NE fibers for a low channel count DIA
157 See Figure 4-27 on page 4-57 to perform the steps for intra-NE fibering for a
low channel count DIA.
158 Connect the Common Out (port 26) of the CCMD12 to the Common In (port
21) of the WSS as indicated in the EDP/IDP.
159 Connect the Common In (port 25) of the CCMD12 to the Common Out (port
22) of the WSS as indicated in the EDP/IDP.
160 Connect the Monitor Out (port 27) of the CCMD12 to the Monitor 1 (port 1) of
the WSS as indicated in the EDP/IDP.
161 Repeat step 157 to step 160 for all low channel count DIA at the site
(maximum of two low channel count DIAs per site).
—end—

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-32 Photonic layer site testing procedures

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

WSC WSC

2 x OSC PEC: NTK554BA


2 1

OSC OSC
2 1

OSC2 Out

OSC1 Out
OSC2 In

OSC1 In
2
2

1
1
MLA MLA
PEC: NTK552BA PEC: NTK552BA
Line B Mon Line B Mon
1 1
Line A Mon Line A Mon
2 2
OSC B In OSC B In
3 3
4 4
OSC A Out OSC A Out
Line A In Line A Out Line B In Line B Out
8 A 7 6 B 5

5 B Line B In
6 7 A 8
Line B Out Line A Out Line A In

Legend
= DSCM
= Attenuator

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-33

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

WSC WSC WSC WSC

2 x OSC

2 x OSC
2 1 2 1

PEC: NTK554BA

PEC: NTK554BA
OSC OSC OSC OSC
2 1 2 1

OSC2 Out

OSC1 Out

OSC2 Out

OSC1 Out
OSC2 In

OSC1 In

OSC2 In

OSC1 In
2
2

1
1

2
2

1
1
SLA SLA
PEC: NTK552AA PEC: NTK552AA
Line B Mon Line B Mon
1 1
Line A Mon Line A Mon
2 2
OSC B In OSC B In
3 3
4 4
OSC A Out OSC A Out
Line A In Line A Out Line B In Line B Out
8 A 7 6 5

5
Line B In
6 7 A 8
Line B Out Line A Out Line A In

Loc: AA Shelf: X Slot: Y

Legend
= DSCM
= Attenuator

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-34 Photonic layer site testing procedures

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-35

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-36 Photonic layer site testing procedures

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-37

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-38 Photonic layer site testing procedures

Figure 4-7
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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
WSC WSC WSC WSC
Figure 4-8

2 1 2 1

Release 13.0
OSC OSC OSC OSC
2 1 2 1

2 x OSC PEC: NTK554BA


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

6500 Packet-Optical Platform


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-2019 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
44 Channel MUX/DEMUX

LC LC
= DSCM Ch 44 In Ch 44 In

= Attenuator Ch 44 Out Ch 44 Out

June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-39

323-1851-221 Standard Issue 3


Figure 4-9

Release 13.0
WSC WSC WSC WSC
2 1 2 1

OSC OSC OSC OSC


2 1 2 1

2 x OSC PEC: NTK554BA


2 x OSC PEC: NTK554BA

OSC1 In
OSC1 In

OSC2 Out
OSC2 Out

OSC1 Out
OSC1 Out

OSC2 In
OSC2 In

6500 Packet-Optical Platform


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

Copyright© 2010-2019 Ciena® Corporation


OSC B In OSC B In Switch 1 In Switch 1 In OSC B In
3 3 3
4-40 Photonic layer site testing procedures

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
Switch 3 In Switch 3 In
7 7 9:1
9:1
8 8
Switch 3 Out Switch 3 Out
Switch 4 In Switch 4 In
9 9
10 10
Switch 4 Out Switch 4 Out
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
Switch 6 In Switch 6 In
14 14
Intra-NE fiber connections at a ROADM site with interior SLA

Switch 7 In Switch 7 In
15 15
Switch 8 In Switch 8 In
16 16
Switch 9 In 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
44 Channel MUX/DEMUX

LC LC
= DSCM Ch 44 In Ch 44 In

Ch 44 Out Ch 44 Out
= Attenuator

June 2019
Commissioning and Testing
323-1851-221 Standard Issue 3
Figure 4-10

Release 13.0
WSC WSC
4 3

OSC OSC
2 1

2 x OSC PEC: NTK554BA

OSC1 In
OSC2 Out
OSC1 Out

OSC2 In

6500 Packet-Optical Platform


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

Copyright© 2010-2019 Ciena® Corporation


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
Switch 3 In Switch 3 In
7 7 9:1
9:1
8 8
Switch 3 Out Switch 3 Out
Switch 4 In Switch 4 In
9 9
10 10
Switch 4 Out Switch 4 Out
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
Switch 6 In Switch 6 In
14 14
Switch 7 In Switch 7 In
15 15
Switch 8 In Switch 8 In
16 16
Switch 9 In 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
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
44 Channel MUX/DEMUX
44 Channel MUX/DEMUX

LC LC
= DSCM Ch 44 In Ch 44 In

Ch 44 Out Ch 44 Out
= Attenuator

June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-41

323-1851-221 Standard Issue 3


4-42 Photonic layer site testing procedures

Figure 4-11
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.

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-43

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-44 Photonic layer site testing procedures

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-45

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-46 Photonic layer site testing procedures

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-47

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-48 Photonic layer site testing procedures

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-49

Figure 4-18
Intra-NE fiber connections at a ROADM site with XLA and SRA - DSCM placement

Figure 4-19
Intra-NE fiber connections at a ROADM site with ESAM-MLAx (example shows MLA)

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
4-50 Photonic layer site testing procedures

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

CMD44 50GHz Blue


PEC: NTT862BA

1 Ch1 In

2
1530.33nm
LC
2xOSC PEC: NTK554BAE5
LC
Ch1 Out OSC1 Out OSC2 Out
Ch2 In 1 OSC OSC 2
44 Channel MUX / DEMUX

3
4
1530.72nm 1 1 2 2
Ch2 Out OSC1 In OSC2 In
Loc: Shelf: Slot:
Common Out
90

Common In 89
WSS 50 GHz
PEC: NTK553KC
85 Ch43 In
1546.92nm
MLA
86
Ch43 Out
PEC: NTK552BA
Ch44 In Monitor 1 Line B Mon
87 1 1
1547.32nm OPM
88
Ch44 Out BMD2 Monitor 2
2 2
Line A Mon
PEC: NTT862DA
3
Switch1 In Σ 1:2 Common Out
8
3
4
OSC B In

Input 1 Switch1 Out OSC A Out


4
CMD44 50GHz Red 3
Common
2 Line B In Line B Out
PEC: NTT862BB Output 1 Out 6 B 5
4 Switch2 In
5
1
2
Ch1 In
1547.72nm
Ch1 Out 5
Input 2
Σ 6
Switch2 Out
2:1
Common In
7 7
Line A Out
A
Line A In
8
Common
Ch2 In 1
44 Channel MUX / DEMUX

3 In
1548.11nm Output 2
4 6
Ch2 Out

Common Out
90
Note: NTK553KC shown. For NTK553KA,
ports 3 and 4 are Switch In/Demux Out, and
Common In 89 ports 5 and 6 are Add In/Drop Out.

85 Ch43 In
1564.68nm
86
Ch43 Out
87 Ch44 In
1565.09nm
88
Ch44 Out

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
Photonic layer site testing procedures 4-51

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

6500 Packet-Optical Platform Commissioning and Testing


Release 13.0 323-1851-221 Standard Issue 3
Copyright© 2010-2019 Ciena® Corporation June 2019
2xOSC
Figure 4-22

1 OSC1 Out OSC OSC OSC2 Out 2

Release 13.0
1 OSC1 In 1 2 OSC2 In 2 MLA
Line B Mon
1
2
WSS 100 GHz 5x1 Line A Mon
OSC B In
Monitor 1 3
1
OPM Monitor 2 4
2 OSC A Out

6500 Packet-Optical Platform


Switch1 In Line B In Line B Out
3 6 B 5

4 Switch1 Out

Common Out Cascaded LIM 7 A 8


18 Line A Out Line A In
Mon 1 (B Out)
∑ 1: 5 1 SLA

Copyright© 2010-2019 Ciena® Corporation


2
4-52 Photonic layer site testing procedures

Mon 2 (A Out)
OSC B In
3

Switch5 In 4
11 5:1 OSC A Out
Common In
12 Switch5 Out 17 Line B In Line B Out
6 5

7 8
Intra-NE fiber connections (CMD44 to Drop LIM to WSS)

A
Line A Out Line A In

Drop LIM SLA


Mon 1 (B Out)
1
2
eCMD44 100 GHz
Mon 2 (A Out) Ch1 In 1
OSC B In
3 Ch1 Out 2
4 Common In
OSC A Out 89
Line A In Line A Out
8 A 7
90 Common Out

Ch44 In 87
5 6
Line B Out Line B In
Ch44 Out 88

June 2019
Commissioning and Testing
323-1851-221 Standard Issue 3
Figure 4-23

Release 13.0
Backbone OTS 1 Backbone OTS 2
WSC WSC
WSC WSC 4 3
4 3

2x OSC

2x OSC
OSC OSC
OSC OSC 2 1
2 1

6500 Packet-Optical Platform


PEC: NTK554BA

OSC2 In
OSC1 In

OSC2 Out
OSC1 Out

PEC: NTK554BA

OSC2 In
OSC1 In

OSC2 Out
OSC1 Out
1
1

2
2

1
1

2
2
WSS 100 GHz WSS 100 GHz
PEC: NTK553JA
PEC: NTK553JA
MLA
PEC: NTK552BA 6500 Monitor 1 MLA
Monitor 1 1
Mon 1 (B Out) 1 OPM Monitor 2 6500 PEC: NTK552BA

Copyright© 2010-2019 Ciena® Corporation


1 2
Monitor 2 OPM Mon 1 (B Out)
2 1
2
Mon 2 (A Out)
Switch1 In Common Out 2
OSC B In Switch1 Out 3 18 Mon 2 (A Out)
3 Common In 4
 1: 2
17  1: 2 Switch1 Out
Switch1 In 4 OSC B In
4 3 3
OSC A Out
4
Line A In Line A Out Switch2 In OSC A Out
8 A 7 5
Switch2 Out 6 Switch2 Out Common In Line B In Line B Out
Common Out 6 17 6 B 5
18 Switch2 In
5
2:1
2:1
5 B 6
Line B Out Line B In
7 A 8
Line A Out Line A In

Can also be NTK553EA/HA or


Can also be NTK553EA/HA or NTK553JB
NTK553JB

DIA OTS

LC Ch1 In eCMD44 MLA WSS 100 GHz


1 6500
PEC: NTT862FA PEC: NTK552BA PEC: NTK553JA
2 Mon 1 (B Out)
Ch1 Out 1
LC 2 Monitor 1
Ch2 In 1
3 Mon 2 (A Out)
Monitor 2 OPM
OSC B In 2
4 3
Ch2 Out
Common Out LC 4 Switch1 Out
OSC A Out Common In 4
90 Pad 17  1: 2
Line A In Line A Out Switch1 In
89 8 3
A 7
Intra-NE fiber connections between a 100 GHz DIA and backbone OTS

Common In
LC Ch 43 In Switch2 Out 6
85 5 B 6 Common Out
Line B Out Line B In 18 Switch2 In
2:1 5
86

44 Channel MUX / DEMUX


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

This pad may be required for high


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

June 2019
Commissioning and Testing
Photonic layer site testing procedures 4-53

323-1851-221 Standard Issue 3


Backbone OTS 1 Backbone OTS 2

WSC WSC WSC WSC


4 3 4 3

2x OSC
Figure 4-24

2x OSC

Release 13.0
OSC OSC OSC OSC
2 1 2 1

PEC: NTK554BA
PEC: NTK554BA

OSC2 In
OSC1 In
OSC2 In
OSC1 In

OSC2 Out
OSC1 Out
OSC2 Out
OSC1 Out

1
1

2
2
WSS 50 GHz

1
1

2
2
WSS 50 GHz
PEC: NTK553FA/FC/LA PEC: NTK553FA/FC/LA
MLA MLA
6500 Monitor 1 Monitor 1 6500
PEC: NTK552BA 1 1 PEC: NTK552BA
Mon 1 (B Out) Monitor 2 OPM OPM Monitor 2 Mon 1 (B Out)
1 2 2 1
2 2
Mon 2 (A Out) Switch1 Out 4 Switch1 In Mon 2 (A Out)
3
OSC B In Switch1 In 3 Switch1 Out OSC B In
3 4 3
4 Switch2 Out 6 Switch2 In 4
Common In 5 Common Out OSC A Out
OSC A Out 21 Switch2 In Switch2 Out 22
5 6
Line A In Line A Out Line B In Line B Out
8 A 7 6 B 5

6500 Packet-Optical Platform


Switch3 Out 8 Switch3 In
7

9x1
9x1
Switch3 In 7 Switch3 Out
8
5 B 6 7 A 8
Line B Out Line B In Switch4 Out Switch4 In Line A Out Line A In
10 9

WSS 50 GHz
WSS 50 GHz
Switch4 In 9 Switch4 Out
10
Switch5 Out 12 Switch5 In
11
Switch5 In 11 Switch5 Out
12
Switch6 Out 14 Switch6 In
13
 1: 9 Switch6 In 13 14 Switch6 Out  1: 9
Common Out Switch7 Out 16 Switch7 In Common In
22 15
21
Switch7 In 15 Switch7 Out
16

9:1 9:1

Copyright© 2010-2019 Ciena® Corporation


Switch8 Out (Drop1) 18 The Upgrade Ports are either used
17 Switch8 In (Add1)
Switch8 In (Add1) 17
18 Switch8 Out (Drop1)
4-54 Photonic layer site testing procedures

for DIA configurations or Local


Switch9 Out (Drop2) 20
19 Switch9 In (Add2) CMD44 50GHz Add/Drop
Switch9 In (Add2) 19
20 Switch9 Out (Drop2)

Can also be NTK553KC


Can also be NTK553KC

Pad Optical Modeler determines whether


Pad these pads are required and the pad
Pad value.
Pad

DIA OTS
CMD44 50GHz Blue Can also be NTK553KC
PEC: NTT862BA
Slot: 84
1 Ch1 In
1530.33nm
2
Ch1 Out WSS 50 GHz
3 Ch2 In
1530.72nm
PEC: NTK553FA/FC/LA
4
Ch2 Out
MLA Monitor 1
Common Out 90 1
PEC: NTK552BA 6500 Monitor 2 OPM
Intra-NE fiber connections between a 50 GHz DIA and backbone OTS

2
Mon 1 (B Out)
Common In 89 1
BMD2 Switch1 Out 4
2
PEC: NTT862DA Mon 2 (A Out) Switch1 In 3
85 Ch43 In OSC B In
1546.92nm 3 Switch2 Out
Common In 6
86 3 Input 1
21

44 Channel MUX / DEMUX


Ch43 Out 4 Switch2 In
Common OSC A Out 5
87 Ch44 In 2
1547.32nm Output 1 Out
4 Line A In Line A Out Switch3 Out
88 Pad 8 A 7 8
Ch44 Out
9x1

Switch3 In 7
5
Input 2

Common 5 B 6 Switch4 Out 10
WSS 50 GHz

1 Line B Out Line B In


CMD44 50GHz Red In Switch4 In
Output 2 9
6
PEC: NTT862BB These 5 Other switches can be
Switch5 Out 12
Slot: 85
1 Ch1 In Switch5 In fibered to other OTS with 9x1 50GHz
11
1547.72nm
2
Ch1 Out Switch6 Out 14 WSS terminals.
3 Ch2 In 1: 9 Switch6 In 13
1548.11nm 
4 This pad may be required for high
Ch2 Out Switch7 Out
Common Out 16
Can also be NTK552FA or 22
Common Out 90 power Service circuit pack Switch7 In 15
transmitters, such as OM5K. Optical NTK552GA
Common In 89
Modeler determines whether pad is 9:1
Switch8 Out (Drop1) 18

85 Ch43 In required and pad value. Switch8 In (Add1) 17


1564.68nm
86

44 Channel MUX / DEMUX


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

June 2019
Commissioning and Testing
323-1851-221 Standard Issue 3
Figure 4-25

Release 13.0
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

6500 Packet-Optical Platform


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

Copyright© 2010-2019 Ciena® Corporation


1
Switch2 Out

LB In
Ch 10 Out 2 Common In 6
20
25
Switch8 In Mon 2 (A Out) 21 Switch2 In
Ch 10 In