009-2011-160 (CND R5.2 User Manual) RevA

Ciena Network Designer
CND
User Manual
Software Release 5.2
009-2011-160 - Revision A
October, 2011
Copyright© 2011 Ciena® Corporation
Ciena® Confidential and Proprietary
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.

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
1-800-CIENA24 (243-6224)
In North America E-mail:CIENA24@ciena.com
410-865-4961
In Europe, Middle East, 800-CIENA-24-7 (800-2436-2247)
E-mail:CIENA24@ciena.com
and Africa +44-207-012-5508
800-CIENA-24-7 (800-2436-2247)
In Asia-Pacific +81-3-6367-3989 E-mail:CIENA24@ciena.com
+91-124-4340-600
In Caribbean and Latin 800-CIENA-24-7 (800-2436-2247)
E-mail:CIENA24@ciena.com
America 410-865-4944 (USA)
Sales and General Information 410-694-5700 E-mail:sales@ciena.com
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-124-434-0500 E-mail:sales@ciena.com
In Latin America 011-5255-1719-0220 (Mexico City) E-mail:sales@ciena.com
877-CIENA-TD (243-6283)
Training E-mail: techtng@ciena.com
or 410-865-8996
For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.
Ciena Network Designer (CND) 009-2011-160 - Revision A

Copyright© 2011 Ciena® Corporation October, 2011
IMPORTANT: PLEASE READ THIS LICENSE AGREEMENT ("AGREEMENT") CAREFULLY BEFORE
INSTALLING OR USING CIENA CORPORATION ("Ciena") SOFTWARE, HARDWARE OR DOCUMENTATION
(COLLECTIVELY, THE "EQUIPMENT").
BY INSTALLING OR USING THE EQUIPMENT, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS
AGREEMENT AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS.
1. Right to Use License; Restrictions. Subject to these terms, and the payment of all applicable license fees, Ciena
grants to you, as end user, a non-exclusive license to use the Ciena software (the "Software") in object code form
solely in connection with, and as embedded within, the Equipment,. You shall have the right to use the Software solely
for your own internal use and benefit. You may make one copy of the Software and documentation solely for backup
and archival purpose, however you must reproduce and affix all copyright and other proprietary rights notices that
appear in or on the original. You may not, without Ciena's prior written consent, (i) sublicense, assign, sell, rent, lend,
lease, transfer or otherwise distribute the Software; (ii) grant any rights in the Software or documentation not expressly
authorized herein; (iii) modify the Software nor provide any third person the means to do the same; (iv) create
derivative works, translate, disassemble, recompile, reverse engineer or attempt to obtain the source code of the
Software in any way; or (v) alter, destroy, or otherwise remove any proprietary notices or labels on or embedded within
the Software or documentation. You acknowledge that this license is subject to Section 365 of the U.S. Bankruptcy
Code and requires Ciena's consent to any assignment related to a bankruptcy proceeding. Sole title to the Software
and documentation, to any derivative works, and to any associated patents and copyrights, remains with Ciena or its
licensors. Ciena reserves to itself and its licensors all rights in the Software and documentation not expressly granted
to you. You shall preserve intact any notice of copyright, trademark, logo, legend or other notice of ownership from any
original or copies of the Software or documentation.
2. Audit: Upon Ciena's reasonable request, but not more frequently than annually without reasonable cause, you
shall permit Ciena to audit the use of the Software at such times as may be mutually agreed upon to ensure
compliance with this Agreement.
3. Confidentiality. You agree that you will receive confidential or proprietary information ("Confidential Information")
in connection with the purchase, deployment and use of the Equipment. You will not disclose Confidential Information
to any third party without prior written consent of Ciena, will use it only for purposes for which it was disclosed, use your
best efforts to prevent and protect the contents of the Software from unauthorized disclosure or use, and must treat it
with the same degree of care as you do your own similar information, but with no less than reasonable care. You
acknowledge that the design and structure of the Software constitute trade secrets and/or copyrighted materials of
Ciena and agree that the Equipment is Confidential Information for purposes of this Agreement.
4. 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 Equipment and any accompanying technical
data (collectively "Materials") are commercial within the meaning of applicable Federal acquisition regulations. These
Materials were developed fully at private expense. U.S. Government use of the Materials is restricted by this
Agreement, and all other U.S. Government use is prohibited. In accordance with FAR 12.212 and DFAR Supplement
227.7202, software delivered to you is commercial computer software and the use of that software is further restricted
by this Agreement.
5. Term of License. This license is effective until terminated. Customer may terminate this license at any time by
giving written notice to Ciena [or] and destroying or erasing all copies of Software including any documentation. Ciena
may terminate this Agreement and your license to the Software immediately by giving you written notice of termination
in the event that either (i) you breach any term or condition of this Agreement or (ii) you are wound up other than
voluntarily for the purposes of amalgamation or reorganization, have a receiver appointed or enter into liquidation or
bankruptcy or analogous process in your home country. Termination shall be without prejudice to any other rights or
remedies Ciena may have. In the event of any termination you will have no right to keep or use the Software or any
copy of the Software for any purpose and you shall destroy and erase all copies of such Software in its possession or
control, and forward written certification to Ciena that all such copies of Software have been destroyed or erased.

6. Compliance with laws. You agree to comply with all applicable laws, including all import regulations, and to obtain
all required licenses and permits related to installation and use of Equipment. Software, including technical data, is
subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and
may be subject to export or import regulations in other countries. Customer agrees to comply strictly with all such
regulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, or import Software.
7. Limitation of Liability. ANY LIABILITY OF Ciena SHALL BE LIMITED IN THE AGGREGATE TO THE AMOUNTS
PAID BY YOU 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 THIRD-PARTY SUPPLIER OF Ciena. NEITHER Ciena NOR ANY OF ITS THIRD-PARTY
SUPPLIERS 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
8. General. Ciena may assign this Agreement to any Ciena affiliate or to a purchaser of the intellectual property rights
in the Software, but otherwise neither this Agreement nor any rights hereunder may be assigned nor duties delegated
by either party, and any attempt to do so will be void. This Agreement shall be governed by the laws of the State of
Maryland (without regard to the conflict of laws provisions) and shall be enforceable in the courts of Maryland. The
U.N. Convention on Contracts for the International Sale of Goods shall not apply hereto. This Agreement constitutes
the complete and exclusive statement of 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.

Preface
Overview
This guide is intended to be used by internal sales engineers to facilitate the design of 4200 (formerly
known as CN 4200) and CoreStream networks.
Disclaimer
While every effort has been made to ensure that this document is complete and accurate at the time
of printing, the information that it contains is subject to change. Ciena® is not responsible for any
additions to or alterations of the original document. Networks vary widely in their configurations,
topologies, and traffic conditions. This document is intended as a general guide only. It has not been
tested for all possible applications, and it may not be complete or accurate for some situations.
Trademark Acknowledgements
• Ciena® is a registered trademark of Ciena Corporation.
• CoreStream® Agility Optical Transport System is a registered trademark of Ciena
Corporation.
• CoreDirector® FS Multiservice Optical Switch and CoreDirector® FSCI Multiservice
Optical Switch are registered trademarks of Ciena Corporation.
• Windows® 95/98/2000/XP and Windows NT® are registered trademarks of the Microsoft
Corporation.
• Microsoft is either a registered trademark or trademark of Microsoft Corporation in the
United States and/or other countries.
• UNIX® is a registered trademark licensed exclusively through X/Open Company, Ltd.
• Sun, Sun Microsystems, JAVA, Java Secure Socket Extension, and JAVAX are
trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. or other
countries. This product includes code licensed from RSA Data Security.
Intended Audience
This document is intended for sales engineers responsible for designing 4200 and CoreStream
networks. All personnel are required to read, understand, and observe the safety precautions
described in the appropriate product manuals.
Release Notes and Document Updates

The hard copy and Compact Disc Read Only Memory (CD-ROM) versions of this document are
revised only at major releases and, therefore, may not always contain the latest product information.
As needed, Software Release Documents (SRDs) will be provided between major releases to
describe any new information or document changes.
The latest online version of this document and all release notes can be accessed by way of the Ciena
web site at http://www.ciena.com.

ii
Release History
The following information lists the release history of this document.
Table 1. Printing History
Issue/Revision Release Date Content Description

009-2006-191, Revision 001 July 2006 Document describing Ciena Network Designer
Release 2.0 operation.
009-2006-292, Revision 001 January 2007 Document describing Ciena Network Designer
009-2006-292, Revision A March 2007 Document describing Ciena Network Designer
Release 3.0 operation, incorporating 10G network
module option changes.
009-2006-292, Revision B June 2007 Document describing Ciena Network Designer
Release 3.0 operation, incorporating changes up
to R3.0.2.
009-2007-381, Revision 001 October 2007 Document describing Ciena Network Designer
009-2007-381, Revision A February 2008 Document describing Ciena Network Designer
Release 3.1.x operation.
009-2008-300, Revision 001 July 2008 Document describing Ciena Network Designer
009-2008-300, Revision A August 2008 Document describing Ciena Network Designer
Release 4.0 operation with input from CI and SEs.
009-2008-300, Revision B November 2008 Document describing Ciena Network Designer
Release 4.0 operation, covering maintenance
release R4.0.1.
009-2009-011, Revision A April 2009 Document describing Ciena Network Designer
009-2009-011, Revision B August 2009 Document describing Ciena Network Designer
Release 4.1 operation, covering maintenance
release R4.1.1.
009-2009-589, Revision A December 2009 Document describing Ciena Network Designer
009-2010-355, Revision A October 2010 Document describing Ciena Network Designer
009-2011-060, Revision A March 2011 Document describing Ciena Network Designer
009-2011-160, Revision A October 2011 Drafts describing Ciena Network Designer Release
5.2 operation.

iii
Related Documentation
Documentation is available on CD-ROM and online at http://www.ciena.com. The following is a list
of the related documents. Additional supporting documentation is available through the Ciena web
site at http://www.ciena.com.
4200 Advanced Services Platform (formerly known as ActivSpan

4200 and CN4200) Customer Documents
• 4200 Advanced Services Platform, Release 8.0.1, System Description Manual (009-2011-
450)
• 4200 Advanced Services Platform, Release 8.0.1, Hardware Installation Manual (009-
2011-451)
• 4200 Advanced Services Platform, Release 8.0.1, Turn-up and Test Manual
(009-2011-452)
• 4200 Advanced Services Platform, Release 8.0.1, Alarm and Trouble Clearing Manual
(009-2011-453)
• 4200 Advanced Services Platform, Release 8.0.1, Service Manual - Hardware
Replacement Procedures Part 1 (009-2011-454.1)
• 4200 Advanced Services Platform, Release 8.0.1, Service Manual - Maintenance
Procedures Part 2 (009-2011-454.2)
• 4200 Advanced Services Platform, Release 8.0.1, CLI Reference Manual
(009-2011-455)
• 4200 Advanced Services Platform, Release 8.0.1, TL1 Command Reference (009-2011-
456)
• 4200 Advanced Services Platform, Release 8.0.1, Configuration Guide, Volume 1: System
CLI (009-2011-457)
• 4200 Advanced Services Platform, Release 8.0.1, Configuration Guide, Volume 2: System
HTTP (009-2011-458)
• 4200 Advanced Services Platform, Release 8.0.1, Configuration Guide, Volume 3: G10/
G10X (009-2011-459)
• 4200 Advanced Services Platform, Release 8.0.1, Configuration Guide, Volume 4: EM6/
ESOM (009-2011-460)
• 4200 Advanced Services Platform, Release 8.0.1, Configuration Guide, Volume 5: X4 and
X4 Modules (009-2011-461)
• 4200 Advanced Services Platform, Release 8.0.1, SNMP Reference Manual (009-2011-
462)
CoreStream Regional Customer Documents

• CoreStream Transport System, Release 7.3, System Description Manual (009-2007-260)
• CoreStream Transport System, Release 7.3, Hardware Installation Manual
(009-2007-261)
• CoreStream Transport System, Release 7.3, Turn-up and Test Manual
(009-2007-262)
• CoreStream Transport System, Release 7.3, Alarm and Trouble Clearing Manual
• (009-2007-263)

iv
• CoreStream Transport System, Release 7.3, Maintenance and Upgrade Manual

(009-2007-264)
• CoreStream Transport System, Release 7.3, Software Release Documents (SRD)
(009-2007-266)
• CoreStream Transport System, Release 7.3, TL1 Reference Manual (009-2007-256)
CoreStream ULH (Agility) Documents

• CoreStream Transport System, Release 9.0, System Description Manual (009-2009-050)
• CoreStream Transport System, Release 9.0, Hardware Installation Manual
(009-2009-051)
• CoreStream Transport System, Release 9.0, Turn-up and Test Manual (009-2009-052)
• CoreStream Transport System, Release 9.0, Alarm and Trouble Clearing Manual
(009-2009-053)
• CoreStream Transport System, Release 9.0, Maintenance and Upgrade Manual
(009-2009-054)
• CoreStream Transport System, Release 9.0, Software Release Documents (SRD)
(009-2009-055)
• CoreStream Transport System, Release 9.0, TL1 Reference Manual (009-2009-056)
Other Documents
• Ciena Standard Cleaning and Equipment Safety Practices, Revision C (009-2003-121)
• Ciena Installation Workmanship Standards, Revision D (009-7B03-000)
Document Ordering Information

To order additional documentation, the user can contact the local sales representative.
Document Comments
Ciena appreciates all comments that will help us to improve our documentation quality. The user can
submit comments through the Ciena web site (http://www.ciena.com) or with the Documentation
Improvement Request form included with this document.
Additional Product Information

• Additional product information can be obtained by contacting the local sales representative.

Table of Contents
CHAPTER 1:
OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Features and Enhancements in CND Release 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Features and Enhancements Specific to 4200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Other Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
CoreStream Reference Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4200 Reference Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Platform Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Ciena Network Designer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
CHAPTER 2:
CND CONCEPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
General introduction to Ciena Network Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
CHAPTER 3:
GRAPHICAL USER INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Begin Using the Ciena Network Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
GUI/Canvas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Message Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Resizing Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
File Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Edit Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
View Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Tools Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Locking Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

vi Table of Contents
Reports Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Layout Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Preference Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Window Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Help Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Menu Bar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Formatting Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Global Design Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
CHAPTER 4:
EXCEL INPUT TEMPLATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
General Information About Excel Input Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Error Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Error Correcting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
CoreStream Input Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
AllSpansPhysical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
SpansPhysical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Unprotected_Traffic/Protected_Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4200 Input Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
AllSpansPhysical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
SpansPhysical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Demand and Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
CHAPTER 5:
CREATE 4200 NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Network Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Create a 4200 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Flow Chart Blocks: Detailed Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Block A. Add Nodes to Canvas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Block B. Create and Configure Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Block C. Create and Configure Lightpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Table of Contents vii
Block D. Configure 4200 Network Design Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Block E. Run 4200 Chassis and Service Card Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Block F. Lock Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Block G. Run Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
CHAPTER 6:
CREATE CORESTREAM NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Network Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Create a CoreStream Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
Flow Chart Blocks: Detailed Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Block A. Add Nodes to Canvas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Block B. Create and Configure Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Block C. Create and Configure Lightpaths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Block E. Configure CoreStream Network Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Block F. Lock Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Block G. Run Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240
CHAPTER 7:
ERROR MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Viewing GUI Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Viewing Kernel Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
APPENDIX A:
PRODUCT REFERENCE TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
CoreStream Product Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
4200, CN 2110, and CN 2150 Product Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

SFP Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
XFP Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Modules for 4200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Card Slot Rules for 4200 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Module Locations within the 4200 RS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Rules for Visio Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

viii Table of Contents

1
Chapter 1:
Overview
This manual provides information about the Ciena Network Designer (CND) supporting the design
of customer solutions based on the Ciena CoreStream Agility Optical Transport System, CN 2110,
CN 2150, and 4200 FlexSelect Advanced Services Platform products. The manual guides the user
through various features and functions of the software tool, and the processes that automate the
network planning functions, validate the results, export configuration files, and troubleshoot
problems.
This document contains procedural information describing installation and initial configuration of the
Ciena Network Designer. Each procedure is written in a task-oriented format consisting of numbered
step-by-step instructions for performing a series of actions to accomplish a stated objective. All
procedures should be performed in the order they appear in this document.
The Ciena Network Designer is a GUI-based network-planning tool intended primarily to facilitate
the sales process for networks built with either CoreStream or 4200, CN 2110, and CN 2150
products. The intended users of this software package are sales engineers from Ciena and from
other distributors and sales partners who are familiar with the functionality of the CoreStream and/
or 4200, CN 2110, and CN 2150 product lines. The CND creates networks supporting CoreStream
OR 4200, CN 2110, and CN 2150 products; it is not designed to incorporate the two networks.
The product line context (CoreStream or 4200) is defined by the following:
• User performs kernel design using Tools menu and selects either Design CoreStream
networks or Design CN4200 networks.
• Any node, lightpath, or link defined as either CoreStream or 4200 defines the entire network.
• User adds fiber Optical Protection Switching (OPS) protection to any link by right-clicking on
the link while in the Link View to define it as 4200.
Defining any single node, link, or lightpath as CoreStream or 4200 will immediately define the
context of the entire network design, since mixed CoreStream and 4200 designs are not allowed. In
addition, there is a separate Excel Input Template for CoreStream and 4200 that uniquely defines
the network type.

2 Chapter 1 - Overview
Features and Enhancements in CND Release 5.2

Features and Enhancements Specific to 4200
Coherent 40G Support in 4200 Designs
CND 5.2 supports the design and validation of Coherent 40G channels in 4200 managed power
designs (VMUX, ROADM, Mixed ROADM). 40G is not supported on fixed filter networks and is only
supported in designs with OTU1 (2.5G) if the data rates are not mixed on the same links.
40G lightpaths in the network can be validated with the “40G Non-Linear Validation” design option.
This design option can also be deselected by the user to provide only a linear analysis to allow the
user to quickly evaluate 40G OSNR and signal power levels and refine them with design changes.
The mandatory 40G non-linear validation can then be run once satisfactory signal power and OSNR
levels are achieved. The design option “40G Non-Linear Validation” is available for both CoreStream
and 4200 designs.
The supported 40G network modules are listed in Table 1-1. Support for in-skin 40G modules and
eDC40G variants via a 6500 optical shelf is included in the link design analysis, the graphical user
interface (including service type selections, Network Modules selection, Channel Properties editing)
and reports (Visio diagrams and BOM). However, CND 5.2 does not support the in-skin 40G
muxceivers at the Rack View Level, that is, the Visio and BOM do not reserve rack space for the RS-
F40M, nor does it ensure sufficient electrical power budget for it. There is no support for RS-F40M
XFPs in the Channel Card and Port Info GUI, Visio, and BOM.
Table 1-1. Supported 40G modules
PMD Residual
Distance
40G XCVR variant (ps) Dispersion
(km) Limit
Limit Limit (ps)
eDC40G with Enh PMD Compensation (NTK539PAE5) 30 - 50000
eDC40G C-Band (NTK539PBE5) 10 - 50000
eDC40G C-Band Regional (NTK539PCE5) 8 600 50000
eDC40G C-Band Metro (NTK539PDE5) 8 300 50000
RS-F40M (Standard) 8 600 50000
RS-F40M (Premium) 25 - 50000
10G and 40G Non-Linear Launch Power Levels

CND 5.2 allows for provisioning of different launch power levels for 10G and 40G channels in a
network design.
Recommended 40G launch power values per fiber type for compensated and uncompensated
networks are shown in Table 1-2. For networks with 10G and 40G, the recommended bias to apply
to 10G launch power levels relative to 40G launch power levels is given in Table 1-3.

Chapter 1 - Overview 3
Table 1-2. Recommended power per channel into fiber for pure 40G, with and without DCM
ELEAF TWRS TWC TWREACH TeraLight LS DSF
NDSF NDSF
uncomp/ uncomp/ uncomp/ uncomp/ uncomp/ uncom uncomp/
Spans uncomp comp
comp comp comp comp comp p/comp comp
(dBm) (dBm)
(dBm) (dBm) (dBm) (dBm) (dBm) (dBm) (dBm)
1 2 1 1.1 0 -0.5 0.5 1.1 -2 -3

2 2 1 1.1 -0.5 -0.7 0.5 1.1 -2.1 -3.8
3 2 1 1.1 -0.5 -0.9 0.5 1.1 -2.3 -4.5
4 2 1 1 -0.5 -1.1 0.4 1 -2.4 -5.3
5 2 0 0.8 -0.6 -1.3 0.2 0.8 -2.5 -6
6 2 -1 0.4 -1 -1.7 -0.2 0.4 -2.9 -6.6
7 2 -1 0 -1.4 -2 -0.6 0 -3.4 -7.2
8 2 -1 -0.3 -1.7 -2.4 -0.9 -0.3 -3.8 -7.7
9 2 -1 -0.7 -2.1 -2.7 -1.3 -0.7 -4.1 -8.1
10 2 -1 -1 -2.4 -3 -1.6 -1 -4.5 -8.5
11 1.8 -1 -1.3 -2.7 -3.3 -1.9 -1.3 -4.8 -8.8
12 1.6 -1 -1.7 -3 -3.6 -2.3 -1.7 -5.2 -9.1
13 1.6 -1 -2 -3.3 -3.8 -2.6 -2 -5.5 -9.3
14 1.5 -1 -2.2 -3.6 -4.1 -2.8 -2.2 -5.7 -9.4
15 1.2 -1 -2.5 -3.9 -4.3 -3.1 -2.5 -6 -9.5
16 1 -1 -2.8 -4.1 -4.5 -3.4 -2.8 -6.1 -9.6
17 0.8 -1.2 -3 -4.4 -4.7 -3.6 -3 -6.3 -9.7
18 0.6 -1.4 -3.3 -4.6 -4.9 -3.9 -3.3 -6.5 -9.8
19 0.4 -1.6 -3.5 -4.8 -5.1 -4.1 -3.5 -6.6 -9.9
20 0.2 -1.8 -3.7 -5 -5.3 -4.3 -3.7 -6.7 -10
21 0 -2 -3.9 -5.2 -5.5 -4.5 -3.9 -6.8 -10
22 -0.2 -2.2 -4.1 -5.4 -5.6 -4.7 -4.1 -6.9 -10
23 -0.4 -2.4 -4.3 -5.6 -5.8 -4.9 -4.3 -7 -10
24 -0.5 -2.5 -4.4 -5.7 -5.9 -5 -4.4 -7 -10
25 -0.7 -2.7 -4.6 -5.9 -6 -5.2 -4.6 -7 -10

Table 1-3. Recommended launch bias levels for 10G channels, with and without DCM, at gap 4 and
no gap, 100 GHz grid
NDSF NDSF NDSF NDSF NDSF NDSF NZDSF NZDSF NZDSF NZDSF NZDSF NZDSF
comp comp comp uncomp uncomp uncomp comp comp comp uncomp uncomp uncomp
Spans Pure 40G Gap 4 no Gap Pure 40G Gap 4 no Gap Pure 40G Gap 4 no Gap Pure 40G Gap 4 no Gap
Tx Bias Tx Bias Tx Bias Tx Bias Tx Bias Tx Bias Tx Bias Tx Bias Tx Bias Tx Bias Tx Bias Tx Bias
(dB) (dB) (dB) (dB) (dB) (dB) (dB) (dB) (dB) (dB) (dB) (dB)
1 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2

2 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
3 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
4 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
5 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
6 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
7 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
8 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
9 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
10 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
11 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
12 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
13 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2
14 0 0.5 -3 0 -0.5 -2 0 -1 -2.5 0 -1.5 -2.5
15 0 0.5 -3 0 -0.5 -2 0 -1 -2.5 0 -1.5 -2.5
Support for R8.0 OSC and OAV Cards

R8.0 OSC and OAV cards are supported in 4200 designs, see list below. These cards implement an
integrated fixed pad on the OSC transmit to reduce OSC penalty on 40G wavelengths, where the
version with 8 dB pad has the least penalty but has a reduced OSC link budgets. Both auto
placement and manual forcing of these cards are supported. CND provides the user with the ability
to select or deselect each version of the OAV and OSC in the Design Options GUI in order to limit
which cards are used. They can also be manually forced on a per card basis from the Link View GUI.
• MAN-OS-CP-2 (R8.0)
• OAV-VS-U-CP-2 (R8.0)
• OAV-VS-HP-2 (R8.0)
When multiple OSC pad variants are selected in the Design Options GUI, CND places the variant
with the largest OSC pad such that the sum of the span loss, span margin, and OSC pad are 35 dB
or less. A warning message is output if an OSC pad variant is forced or auto placed that results in
the sum of the span loss, span margin, and OSC pad being more than 35 dB.

OSC Link Budget Considerations

The worst case OSC pad values are in excess of the marked value, so the supportable usage is as
listed in Table 1-4.
Table 1-4. OSC link budget considerations
Supported span loss + span
Card
margin
MAN-0S-CP-2 (R8.0) 32.5 dB or less
OAV-VS-U-CP-2 (R8.0)
OAV-VS-HP-2 (R8.0)

OAV-VS-HP-4 (R8.0)

OAV-VS-HP-8 (R8.0)
Default Placement of VMUX8 Selection

Default placement of VMUX-8 filters at VMUX/ Mixed ROADM nodes is supported via the Use
VMUX8 Only design option. VMUX-4 filters are Manufacturing Discontinued (MD) by the end of
2011, so this option allows networks to be designed with VMUX-8 filters only rather than placing
VMUX-4 filters when only half of a band is in use.
Other Features and Enhancements

Licensing
A license is required to use CND 5.2. CND generates an email request for a license (or update),
which the user then sends to tools@ciena.com.
Launching CND without a license opens a registration form. The user must input the license key in
the form.
The product license information is updated in the About Ciena Network Designer window.
The user will be informed if the expiry date is less than or equal to 30 days. After the updated license
key has been entered, the current license expiry date will be updated automatically to the new expiry
date.
The user can install any updated version of CND without having to enter the existing license key
again or a new one, as long as the existing license key is valid.

40G Non-Linear Report Generation

CND 5.2 provides the ability to generate a 40G Non-Linear Report for advanced analysis of 40G
lightpaths since all 40G design results must be reviewed by OPNET. The reports contain 40G data
on various aspects of the design, including fiber and DCM launch powers and cumulative residual
dispersion across the various links.
A "Generate 40G Non-Linear Log Files" selection is implemented in the Design Option GUI and is
not selected by default. Once the user has a 40G design result ready for analysis, this option should
be enabled and the design rerun. Additional data is logged to the C:\Temp directory on a per design
run basis and the user can then subsequently generate a 40G Non-Linear Report. Please note that
this logging function will result in an approximate 25% increase in CND run time and should normally
be left disabled.
Fiber Types Supported in 40G Non-Linear Validation

The fiber types supported in 40G non-linear validation for CoreStream and 4200 designs are as
follows:
• NDSF
• E-LEAF
• TWc
• TW-RS
• TW reach
• DSF
• TeraLight
• Leaf
CND5.2 does not support 40G non-linear validation for lightpaths over fiber types TW+ and oldLS.
TWC and LS fiber types, respectively, are recommended as alternative fiber types.
Input Power to DCM

CND5.2 computes the input power to DCM for both Corestream and 4200 designs, which is used
during the non-linear validation of 40G.
Enhanced Reporting for 40G Channels

Reporting for 40G channels has been enhanced for CoreStream network designs as follows.
Two additional parameters are reported for 40G channels in the Lightpaths sheet of the Design
Summary Report: Polarization Dependent Loss (PDL) and Net System Margin (NSM). CND 5.2 also
supports the computation of Polarization Mode Dispersion (PMD) for 40G channels and this is also
reported in the Lightpaths sheet of the Design Summary Report. The pass/fail status of 40G
channels can be derived from the three possible categories of NSM values: Pass, Tentative Pass,
or Fail. The legend shown for the NSM can be used to correlate the color of the NSM value to the
corresponding pass/fail category. In addition, a short failure reason message is appended to the
NSM value of the failing 40G channels. For more details, see Table 7-9.
These elements are also supported for 4200 network designs.

Prerequisites
Prerequisites
• .Net Framework 4.0 must be installed on the machine to run CND 5.2 due to the migration from
Visual Studio 2008 to 2010 (implemented in CND 5.2).
CoreStream Reference Documentation

Reference documentation for products supported by the Ciena Network Designer can be found on
myCiena > Customer/Service Related Sites > Product Documentation. Look for the CoreStream
document suite under CoreStream Optical Transport System. Suggestions for product
information are:
• CoreStream Optical Transmission System (Agility) System Description Manual (general
product overview and specific information)
• CoreStream Optical Transmission System (Regional) System Description Manual
(general product overview and specific information)
• CoreStream Optical Transmission System (Agility) Turn-up and Test Manual (product
descriptions)
• CoreStream Optical Transmission System (Regional) Turn-up and Test Manual (product
descriptions)
4200 Reference Documentation

Reference documentation for products supported by the Ciena Network Designer can be found on
myCiena > Customer/Service Related Sites > Product Documentation. Look for the 4200
document suite under 4200 Advanced Services Platform.
For product information it is suggested to consult 4200 System Description Manual (description of
4200 Platform, network design, product specs, ordering info).
Platform Requirements
• Ciena Network Designer software operates on Windows 2000 and XP platforms. The platform
hardware and software requirements are:
• Windows 2000® or Windows XP®
• Microsoft® Visio 2003 or later
• Processor: 2.0 GHz dual core recommended
• Memory: 2 GB
• Hard disk: 30 MB available disk space
• Compact Disc Read Only Memory (CD-ROM) drive
Ciena Network Designer Release 5.2 software requires the following software and hardware to
configure a server:
• Windows XP® (SP 2)
• Microsoft® Visio 2003 or later
• Processor: 2.33 GHz Xeon CPU recommended
• Memory: 2 GB
• Hard disk: 30 MB available disk space

Ciena Network Designer Installation
Ciena Network Designer Installation

Installation instructions and procedures for initializing the software are provided in the Ciena
Network Designer Software Release Document (SRD), shipped with the Ciena Network Designer
software.
Licensing
See Licensing on Page 5.
Backward Compatibility
CND 5.2 supports backward compatibility only for 4200 designs, though direct import of older XML
design files into CND 5.2 should only be performed on files designed in CND 4.1.1 or later. Design
files from CND 3.0.x, 3.1.x, 4.0.x, or 4.1.0 should first be imported into CND 4.1.1 and saved. The
saved file can then be directly imported into CND 5.2.
XML design files can be edited with a text editor to view the version of the file, which is shown in the
second line of the file.
For CoreStream designs, backward compatibility is supported for designs (Excel input or XML files)
made in CND5.0.0 or later.
The OTU3 and OTU3e DQPSK network modules implemented in CND 4.2 are not supported (as the
product was cancelled). Any design files from CND 4.2, 5.0, or 5.1 containing 40G DQPSK lightpaths
should be modified in that earlier release of CND to remove the 40G channels before importing the
file into CND 5.2.
Similarly, 50GHz ROADM is a cancelled product and any design file with 50 GHz ROADM should
be redesigned as a 100 GHz network before importing the file into CND 5.2.
Document Organization
Table 1-5. Document Organization
Chapter Description
1 - Overview Provides an overview of the Ciena Network Designer User
Manual and prerequisites for the Ciena Network Designer.
2 - Concepts Provides an overview of the Ciena Network Designer.
3 - Graphical User Interface Gives a tour of the GUI as it can be used for either network.
4 - Excel Input Template Explains use of the Excel input template, for either network, as
a method to create a network with CND.
5 - Create 4200 Network Provides in-depth steps for designing a 4200 network with
CND.
6 -Create CoreStream Network Provides in-depth steps for designing a CoreStream network
with CND.
7- Error Messages Describes the error messages or prompts that may be
generated by the GUI and kernel while using Ciena Network
Designer.

2
Chapter 2:
CND Concepts
General introduction to Ciena Network Designer

Ciena Network Designer allows the user to configure various network topologies. The GUI allows
the user to navigate among the various components of a network design. Components may be
added, deleted, or edited to configure the desired attributes. Then the network design can be
validated to ensure that it meets the minimum design requirements for implementation. Additionally,
Ciena Network Designer has reporting functions that simplify both the analysis of design and the
ordering process; and in addition aid in comparing multiple scenarios, generating proposals,
deployment diagrams, and installation expectations (such as expected optical power levels).
Definitions
• Network
A network is a collection of nodes.
• Node
A node is a collection of equipment at a particular location. CND R5.2 supports up to degree 4
nodes.
• Lightpath
A lightpath is the route of traffic flow, a collection of data-carrying channels that traverses
between a common starting and ending node. A lightpath can be composed of several diverse
routes and/or protection paths with different intermediate nodes.
• Link
A link is the length of optical fiber connecting two nodes. A link may contain two or more spans
separated by amp sites, referred to as a multi-span link.
• Degree
A degree consists of all the equipment that is connected to one fiber pair at a node in a 4200
network.
• 2.5G wave (CoreStream)
A 2.5G wave is a high speed bulk service that is the underlying mechanism on which a
customer’s service can be created. A 2.5G wave can carry two GbE services. Note that 2.5G is
not supported in CND release 5.2.
• 10G wave (CoreStream)
A 10G wave is a high speed bulk service that is the underlying mechanism on which a
customer’s service can be created. A 10G wave can carry eight GbE services.
• OTU wave (4200)
An OTU wave is a high-speed DWDM service.
The OTU1 wave is supported on the EM6, M3S, M6S, FSLM-20, and G6S modules, with a line
rate of 2.67 Gbps.

10 Chapter 2 - CND Concepts
Definitions
The OTU2 wave is supported on the F10-T, F10-A, extended reach F10-T/A (XR-F10-T, XR-
F10-A), FSLM-2(-TN), and Quad-10T cards with a line rate of 10.709225 Gbps.
The OTU2e (10GbE) wave is supported on the F10-T, XR-F10-T, and Quad-10T modules. Line
rate is 11.05 Gbps.
The OTU2es wave is supported in the Quad-10T module. Line rate is 11.095 Gbps
The OTU2e (FC200/400) wave is supported on the FC4-T module. Client rates are 2 Gbps for
FC200 and 4 Gbps for FC400.
The FC1200 wave is supported on the F10-T and XR-F10-T modules. The line rate is
11.3 Gbps.
The OTU3P wave is supported on the RS-F40M muxceiver module. The line rate is
44.569 Gbps.
The 4200 uses the ITU-T G.709 OTUk (OTU1 and OTU2) Digital Wrapper protocol as the
primary transport medium for conveying client services. The OTUk transport signal is a
stratified transport model consisting of one or more of the following layers:
• OPVC layer: consists of one or more OPVC timeslots designed to carry time-slotted
services such as Gigabit Ethernet (GbE), ESCON, Fibre Channel, and others. Each timeslot
represents 155Mb/s bandwidth. Sixteen OPVC timeslots comprise an ODU1 frame payload.
• ODU1 layer: used to carry directly mapped 2.5G services such as STM-16 and OC-48, or
aggregated, time-slotted services. Because a 2.5G service consumes the entire ODU1
payload (2.48Gbps), an ODU1 cannot carry 2.5G and time-slotted services simultaneously.
• ODU2 layer: used to carry directly mapped 10G services like STM-64 and OC-192 or
aggregated directly mapped 2.5G and/or time-slotted services. Because a 10G service
consumes the entire ODU2 payload (9.95Gbps), an ODU2 cannot carry a 10G and any
other service simultaneously; however, it can carry multiple 2.5G and/or time-slotted
services.
• OTUk layer: the transport signal (OTU1 or OTU2) transmitted by and received at the
hardware interface (the port), essentially adding the OTU overhead and FEC to the
corresponding ODUk layer.

3
Chapter 3:
Graphical User Interface
Familiarity with the standard Windows environment is useful when using Ciena Network Designer.
The main drop-down menus appear across the top of the window and are accessible by clicking on
the menu heading. Under the menu headings are icons that can be clicked for quick access to
frequently used functions. The user right-clicks with the mouse to access pop-up menus.The
minimize, maximize, and close buttons are located in the upper right corner of the window. These
features and others are standard and help make the Ciena Network Designer user-friendly.
The following topics are covered in this chapter:
• “Begin Using the Ciena Network Designer” on page 11
• “Menu Options” on page 13
• “File Menu Options” on page 13
• “Edit Menu Options” on page 16
• “View Menu Options” on page 17
• “Tools Menu Options” on page 24
• “Locking Menu Options” on page 27
• “Reports Menu Options” on page 28
• “Layout Options” on page 42
• “Preference Menu Options” on page 42
• “Window Menu Options” on page 57
• “Help Menu Options” on page 58
• “Menu Bar Icons” on page 58
• “Show Tree Icon” on page 63
• “CoreStream Enable/Disable SOADM as DGE” on page 66
• “CoreStream Force/Clear Shelf Amp (USA6)” on page 67
• “Generate 40G Non-Linear Report” on page 67
• “Legend” on page 67
Begin Using the Ciena Network Designer

CND Release 5.2 accepts network data that is input in one of the following three formats:
• An Excel file containing network information, which is subject to input template restrictions and
error checking. Network designs are commonly entered into the CND by first entering
information about the network into an Excel spreadsheet, and then importing it into CND. After
a network appears on canvas, it can be modified further and will always be saved in XML. Edits
to the network are not rewritten to the Excel file, even if the network data was originally loaded
using Excel. The XML files are used as the design files for subsequent network design. Most of
the design time is spent inputting data properly in the input template. The Excel Input Template
is described in “Excel Input Template” on page 69.

12 Chapter 3 - Graphical User Interface
Begin Using the Ciena Network Designer
• An XML (Extensible Markup Language) file that has been saved using CND. Backward
compatibility will be maintained, allowing the user to load XML files saved with previous CND
versions.
• A CND canvas, on which the user can draw the desired network using drag-and-drop for nodes
and links. The user can also drag-and-drop new nodes and links for existing networks loaded
from Excel and XML. Once a network appears on the CND canvas, it will always be saved in
XML format. Any edits to the network will not be rewritten to the Excel file, even if the network
data was first loaded using Excel. The user is expected to use the XML files as the design file
for subsequent network designs.
The network data is displayed in the default CND Network View. There is no visual distinction made
between CoreStream and 4200 nodes prior to designing the network for the first time.
The user double-clicks the icon that was created on the desktop during software installation to begin
using the Ciena Network Designer. The main window appears (Figure 3-1).
Figure 3-1. Main Window
Menu bar
Tree View (if a file Graphical User Interface (GUI) - canvas

is loaded and Tree
View is enabled)
Resizing bars
Message area
Menu bar
The menu bar provides the main software menu and icons representing shortcuts to various
activities.
GUI/Canvas
The GUI canvas provides a graphical view of the network. It displays different views of networks and
nodes.

Chapter 3 - Graphical User Interface 13
Menu Options
Tree View
When a file is loaded, users can open a Tree View of the network in focus. A drop-down list at the
top provides options for expanding the entire network, nodes, links, or lightpaths.
Message Area
The message area displays error messages.
Resizing Bars
Resizing bars allow the user to expand or shrink displayed areas on the screen.
Menu Options
File Menu Options
The File menu offers the standard Windows file options (Figure 3-2). New networks can be created
and saved. A saved network design can be opened or closed for later retrieval. Any network
elements displayed in the graphical element pane can be printed for hard copy viewing by selecting
the print function.
Figure 3-2. File Menu Options
File > New

Select File > New to create a new network. The GUI will display a blank canvas as in Figure 3-1 on
Page 12.

Menu Options
File > Open

Select File > Open to open an existing network file. Use the standard Windows Open dialog box
(Figure 3-3).
Figure 3-3. Open Existing Network File
File > Close

Select File > Close to close the current view. If focus is on the Network View, the tool prompts to
save the file if desired (Figure 3-4). If focus is on any other view, such as the Node View, that view
closes but the file remains open.
Figure 3-4. Save Network Design

Menu Options
File > Save

Select File > Save or File > Save As to save the network file, with the current or a new name, in the
working directory of the current version of CND. Selection of File > Save saves the file with a version
number appended. Up to six versions will be saved. When the file is saved a seventh time, the oldest
version drops off. Files are numbered 1-6, with 6 being the oldest version (Figure 3-5).
Figure 3-5. Save Network Design
File > Print

Select File > Print to open the standard Windows print menu, or File > Print Preview to see a view
of the file to be printed.
File > Exit

Select Exit to close the CND tool. If a file is open, an information box asks for confirmation to save
it before the tool is closed, and another box opens to ask for confirmation to close the program.

Menu Options
Edit Menu Options

Edit > Delete
Click the Delete key or select Edit > Delete to delete the highlighted node or link. Before the
operation is carried out, a confirmation box such as the one in Figure 3-6 may display. Click OK to
delete the node or link, or Cancel to exit the operation.
Figure 3-6. Edit > Delete
A locked node or link, or a node or link connected to a locked node or link, cannot be deleted. The
Delete option is grayed out.
Edit > Lightpath

Select Edit > Lightpath to force all auto assigned channels to manual assigned channels or vice
versa at the network level.
Figure 3-7. Edit > Lightpath

Menu Options
View Menu Options

The View menu provides access to the elements of the network: the network, a node, a link, and a
lightpath. It also provides the option to Show Ports without Links or Hide Ports without Links. In
addition, it has the standard Windows zoom options.
Figure 3-8. View Menu
View > Network

Select View > Network to return the GUI view to the Network View. Figure 3-9 shows a 4200
Network View. Nodes are identified by color and shape as follows:
• Fixed Filter — gray boxes
• ROADM — yellow circles
• Mixed ROADM — dark orange circles
• VMUX nodes — green circles

Menu Options
• Regeneration site (an amplifier site converted to regen site) — small node icon
Figure 3-9. Network View
The user can mouse over a port to see a list of the amplifiers and DCMs at the port (Figure 3-10).
Figure 3-10. List of Tx and Rx Components in Network View
In the Network View, the user can right-click on a node to open a menu with the choices shown in
Figure 3-11.
• Select Convert Node to Amp Site to convert a node, if appropriate.

Menu Options
• Select Remove Node to delete the node. The channels remain, and the span that is left has
the characteristics of both spans before the node was removed. Consult “Autorouting” on
page 108 and “Autorouting” on page 209 for discussions of autorouting specific to either 4200
or CoreStream.
• Select Forbid Regen to prevent regen placement at a node or amp site. The option shown
depends on the force/forbid status.
• Select Lock or Unlock to lock/unlock the entire selection; all lightpaths, amps, or DCMs in the
selection
• Select OCM to auto place OCM or to Force Shared/Degree based OCM. There will be a check
mark by the currently selected option. Shared OCM selection will place a single OCM which will
be shared between all 4 degrees of the node while degree based OCM will use a single OCM
for one or more specific degrees while allowing sharing of another OCM between remaining
degrees. Forcing OCM is allowed even before a kernel run. Forced OCMs are cleared when
switching between 50GHz and 100GHz OADM settings.
The BOM will report one OCM for each node degree in case of degree based OCM. An option
is also available in the Design Options GUI to globally place an OCM at each node degree.
Figure 3-11. Network Menu
View > Node

Select View > Node to expand the view of the desired node. The user will be prompted to select the
desired node to expand from a drop-down list (Figure 3-12). The nodes, including back-to-back
regen sites, are displayed in alphabetical order. The corresponding Link View can be opened if a
regen site is selected from the drop-down list. The corresponding Node View can be opened if a
node is selected from the drop-down list and OK is clicked.
Figure 3-12. Select Desired Node

Menu Options
Figure 3-13 shows an example of an expanded Node View in a 4200 network. The node architecture
is shown graphically, and degree and lightpath information is presented in tables. The degrees are
numbered beginning at the bottom (Degree 0) and moving clockwise; thus, the bottom degree is
Degree 0, Degree 1 is on the left, Degree 2 is at the top, and Degree 3 is on the right.
Figure 3-13. Node View

Menu Options
Figure 3-14 shows an example of a node with degree based OCMs in the Node View.
Figure 3-14. Degree Based OCM
View > Link

Select View > Link to expand the view of the desired link. The user is prompted to select the link to
expand from a drop-down list (Figure 3-15). If View > Link is selected from the Node View, the drop-
down list contains the links from that node. If View > Link is selected from the Network View, all links
in the network will be available from the drop-down list. Highlight the desired link in the list and click
OK to make a selection.
Figure 3-15. Select Desired Link

Menu Options
Figure 3-16 shows the expanded link view for 4200 networks.
Figure 3-16. View Link (4200)

Menu Options
For CoreStream networks, the Link View is shown in Figure 3-17. Raman, amplifier, and DGE can
be selected for the chosen link and forced for the link, so these settings are different from the global
settings selected in Design CoreStream Networks in the Tools menu (“Tools > Design
CoreStream/CN 4200 Network” on page 25).
Figure 3-17. View Link (CoreStream)
View > Lightpath

Lightpaths can be viewed and instructions are provided for adding lightpaths.
View Lightpath
To view an existing lightpath, select View > Lightpath > View Lightpath to open the View
Lightpath GUI. See “View Lightpath” on page 119 for additional details.

Menu Options
Add Lightpath
To view instructions for adding a lightpath, select View > Lightpath > Add Lightpath. To add a
lightpath, CTRL-left-click the start node and CTRL-left-double-click the end node in the Network
View to start the Lightpath Wizard. For steps specific to 4200, see “Block C. Create and Configure
Lightpath” on page 112, and for CoreStream see “Block C. Create and Configure Lightpaths” on
page 211.
View > Show/Hide Ports Without Links

Select View > Show Ports without links to display all of the ports on the nodes in the network view.
Select View > Hide Ports without links to remove ports that do not have links from the network
view.
View > Zoom

Select View > Zoom to change the size of the objects in the canvas. First be sure the canvas has
focus, and then select Zoom In, Zoom Out, Zoom Normal, or Zoom To Fit as desired.
Tools Menu Options

The Tools menu has options to create either a CoreStream or 4200 network.

Menu Options
Tools > Design CoreStream/CN 4200 Network

After the general design of the network is established by adding the nodes and links, select Tools >
Design CoreStream or Design CN 4200 Network to set the network parameters as desired. Only
the option appropriate for the network type is available. Figure 3-18 shows the parameters available
when designing a CoreStream network and Figure 3-19 shows the dialog box for designing a
4200 network.
Figure 3-18. Design CoreStream Network Dialog Box

Menu Options
Figure 3-19. CN 4200 Network Design Dialog Box
These menu options cannot be used to switch designs. If a network is designated as a CoreStream
network, the option to design as a 4200 network will be grayed out, and vice versa.
When OK is clicked, a kernel run is initiated and will run for a variable amount of time depending on
network design size and complexity.
During the kernel run, a button appears on the menu bar to abort the run (Figure 3-20). When the
Abort Run button is selected, a confirmation message appears at the middle of the screen. The
kernel run is not aborted until the user confirms the abort request, so a design result can still occur
if the abort is not confirmed. Upon abort, the design file is reverted to its prior state, but a kernel run
must be successfully completed before reports can be generated.
Figure 3-20. Abort Run

Menu Options
Upon completion of the kernel run, the tool displays the summary of the network optimization. Each
iteration of the network design is shown (Figure 3-21 and Figure 3-22). Click the Clear History
button to delete the Design Summary information.
Figure 3-21. CoreStream Network Optimization Summary
Figure 3-22. CN 4200 Network Optimization Summary
Locking Menu Options

Network locking can be applied to 4200 networks as well as to CoreStream networks. When
equipment is locked, that equipment does not get changed or removed either in subsequent network
design operations (even if the design fails due to the locked equipment) and/or in the subsequent
force operations. Network locking keeps already-designed networks unchanged while adding
additional sites or capacity, thus enabling the user to analyze the effects of edits to existing designs.
Network locking provides the effect of bulk forcing while maintaining the integrity of the original
design. Locking cannot be initiated if changes have been made to any associated part of the network
until a design run is successfully completed.
The sub-menu options of the Locking menu vary based on the active CND view and/or the GUI items
that have been selected. “Locking Menu Options” on page 324 provides the actions associated with
the choices.

Menu Options
Reports Menu Options

The Ciena Network Designer enables Excel and Visio reports. Design Summary provides technical
information about network design. Generate BOM provides Bill of Materials (BOM) information
about the network design. Generate Incremental BOM gives an itemized listing of differential BOM
quantities for two different network designs. Optical Service Report (4200) gives information about
the unidirectional optical properties of each lightpath as it traverses the network on a per OCH group
basis. 40G Non-Linear Report provides reports for advanced analysis of 40G lightpaths. The
reports contain 40G data on various aspects of the design, including fiber and DCM launch powers
and cumulative residual dispersion across the various links. These reports are all generated in
Excel.
For 4200, three Visio report subsets can be generated: Visio Network View provides network-level
Visio drawings of the network design, Visio Node View provides drawings of the intra-node
connections and fiber diagrams for the facing links along with Power Level sheets containing
information for optical deployment and validation, and Visio Rack View provides Visio drawings of
all the chassis along with the various cards and SFP/XFP locations for a specific node.
The user can generate complete or partial Visio reports using the Reports > Visio Reports menu
option. A kernel run, followed by a CN 4200 Chassis Configuration run (selections of chassis type
and service card parameters), is required before generating BOM and Visio reports. BOM output is
entered into the Bid Formatting Tool (BFT) to create a quote.
Table 3-1 shows the reports that can be generated.
Table 3-1. CND Reports
Report Name Format Sheet Name Contents
4200 Chassis Excel See Visio See Visio Report (4200)

Configuration Report (4200)
Design Summary Excel Network Network level summary
Summary
Nodes Node level summary
Links Link level summary
Lightpaths Lightpath level summary
Pads Information about pads
Power Levels Power level information
Design Information about design constraints
Constraints
Optical Service Report Excel Optical Service OCH group summary
(4200) Report
40G Non-Linear Report Excel Results Details 40G data on various aspects of the
design, including fiber and DCM launch
powers and cumulative residual
dispersion across the various links

Menu Options
Table 3-1. CND Reports (Continued)

Report Name Format Sheet Name Contents
Visio Report (4200) Visio Network View Network View diagram for each node/site
Node View Node View diagrams for each node/site
Rack View Rack View diagrams for each node/site
Power Levels Power level information
BOM Report Excel Configuration Itemized bill of material
Incremental BOM Excel Baseline XML Itemized bill of material for design1
BOM
Modified XML Itemized bill of material for design1
BOM
Incremental Itemized bill of material containing the
BOM differential qualities between design 1
and design2
Reports >4200 Chassis Configuration

Select Reports > 4200 Chassis Configuration to define the parameters for CN4200 Chassis
Group (Figure 3-23) and Service Card Group (Figure 3-30) before generating BOM and Visio
reports. Select a node from the drop-down list and click Edit to configure chassis attributes.
Maintain Slot Assignment: This option can be set from the Chassis Group tab by selecting the
appropriate selection(s) from the Select Network/Node/Amp pulldown and checking the Maintain
Slot Assignment box as appropriate.
PSM/PDU Optimization: This option is applied to the selected entry in the 'Select Network / Node /
Amp' pick list. When checked, CND will automatically update the PSM size for MC/CL chassis and
the PDU size for racks containing RS chassis if they require more power than provided by the
existing default selections in the Chassis Group tab. This allows more efficient chassis usage as
CND otherwise enforces the power limits of the selected PSM/PDU option, which can result in

Menu Options
unused chassis slots. Note that PSM/PDU optimization will properly be prevented on a site that has
Maintain Slot Assignment enabled. PSM/PDU Optimization is selected by default for new designs,
and not selected when importing an existing design.
Figure 3-23. Chassis Configuration

Menu Options
The user can select service card type for various services using the Service Card Group tab. In
addition, the user can select network/client SFPs/XFPs, share ports among valid service cards for
service aggregation through backplane connectivity, and add child cards for a parent card through
the Channel Card And Port Info GUI (Figure 5-70).
Figure 3-24. Service Card Configuration
Click here or change the card type in Card

Type column to open Channel Card and
Port Info window
The Chassis Group tab provides radio button selection options for most of the hardware at nodes
and network level. New software license version numbers (up to R8.1) are supported. Multiple
Classic/Micro chassis are not allowed in an R5.0/6.0 amp site without an RS chassis. To ensure this,
Classic Only and Micro Only chassis options at amp sites are grayed out for VMUX/ROADM/Mixed-
ROADM designs and fixed OADM designs with OAV-VS-U-C (R5.0) or OAV-VS-HP (R6.0) Rx amp
options.
Reports > Design Summary

CND generates the appropriate Design Summary report (that is, CoreStream or 4200) based on
context as determined by the kernel run. The 4200 and CoreStream design summary reports each
have seven sheets: Network Summary, Nodes, Links, Lightpaths, Pads, Power Levels, and
Design Constraints. The Design Constraints sheet lists design constraint messages (if any).

Menu Options
Click the icon circled below or select Design Summary from the menu (Figure 3-25).
Figure 3-25. Design Summary Menu Option

Menu Options
The tool creates an Excel summary report such as the one shown in Figure 3-26.
Figure 3-26. Design Summary (4200)

Menu Options
Reports > Optical Service Report (4200)

The Optical Service Report gives information about the unidirectional optical properties of a lightpath
on a per OCH group basis as it traverses through the network. The report, in Excel format, provides
information about the channel and total power, OSNR, amp gain, insertion loss, ASE, and residual
dispersion.
Figure 3-27. Optical Service Report
The table is sorted to show all the forward direction node degree rows together first (from start to
end) and then the reverse direction node degree rows together (from end to start) (Figure 3-28).
Figure 3-28. Optical Service Report

Menu Options
Reports > 40G Non-Linear Report

Clicking the Generate 40G Non-Linear Report icon in the menu bar opens the Generate 40G Non-
Linear Report window, from which the report can be generated. The report contains 40G data on
various aspects of the design, including fiber and DCM launch powers and cumulative residual
dispersion across the various links
Figure 3-29. 40G Non-Linear Report
Reports > Visio Reports (4200)

The Visio Reports feature, available on 4200 designs, generates a Visual Basic script (.bas) that
contains all information required to build a schematic drawing of the network design. The NE
schematics are generated and viewed in Visio, and can be used for design planning and
informational purposes (Figure 3-30).
For CoreStream designs, this menu option is grayed out. See “Visio Reports” on page 182 for a
complete discussion of generating Visio reports for 4200 designs.
Figure 3-30. Visio Reports

Menu Options
When the Visio Reports menu option is selected, a GUI window opens, allowing the desired
contents to be chosen for entry into a Visio report (Figure 3-31).
Figure 3-31. Select Contents of Visio Reports

Menu Options
Reports > Generate BOM

Select Reports > Generate BOM to generate and view the descriptions, and part numbers of the
elements of the network. A 4200 or a CoreStream BOM is generated, depending on which network
design has focus on the canvas (Figure 3-32).
Figure 3-32. Generate BOM

Menu Options
For 4200 networks, a Y1 or a Y1 + YN report can be created (Figure 3-33). For CoreStream
networks, prices are included in the BOM (Figure 3-34).
Figure 3-33. Sample Section of BOM Report (4200)

Menu Options
Figure 3-34. Sample Section of BOM Report (CoreStream)

Menu Options
Reports > Generate Incremental BOM

Select Reports > Generate Incremental BOM to generate an incremental BOM, which gives an
itemized listing of differential BOM quantities for two different network designs (Figure 3-35). The
incremental BOM can be created from two valid XML files or already-generated configuration (BOM)
Excel files, or a mix of the two. The incremental BOM can be generated between two 4200 designs
or between two CoreStream designs.
Figure 3-35. Generate Incremental BOM
Using the combo list box, an XML that is currently open in CND can be chosen either for Design #1
or Design #2 when Choose from Open files is checked (Figure 3-36). Checking this button
disables the Browse button. Alternatively, a network design XML or BOM xls file can selected using
the Browse button. Click the Is BaseLine radio button next to either Design #1 or Design #2 to be
the baseline file against which the incremental BOM quantities are calculated and reported.
Figure 3-36. Generate Incremental BOM
Typical use cases are:

• For a brownfield locked network, the incremental BOM reports the itemized listing of
incremental BOM quantities for any future additions into the locked network.
• The incremental BOM helps in reporting the incremental BOM quantities that are needed to
reach to Yn traffic from Y1 traffic in the same network.
• For network validation, the incremental BOM can report the differential BOM quantities of the
same network but with varied design parameters.

Menu Options
Figure 3-37 is a section of the incremental BOM, showing the difference in parts between the
baseline and the incremental designs.
Figure 3-37. Section of Incremental BOM Report (CoreStream)
Reports > Load Price Information (CoreStream Networks Only)

Use the Load price Information menu option to upload a price worksheet to generate a pricing
guide for a CoreStream network (Figure 3-38).
Figure 3-38. Load Price Information Menu Option

Menu Options
Layout Options
The Layout menu (Figure 3-39) offers design choices for smoothing and editing the network layout
on the canvas. Select either Layered Layout or Force Directed Layout and try different settings.
Figure 3-39. Layout Menu Options
Preference Menu Options

CND allows the user to create custom settings for Preferences and save them as global preferences
to be used in subsequent designs. Any new design drawn on canvas or imported using the Excel
Input Template will use preferences from Global Preferences, and will save them as current design
preferences. However, the Link/Span Length units in Excel Input Template supersede the Length
Units in Global Preferences, but will not overwrite the Length Units in Global Preferences.
Select Preference > Edit Preferences to display the Load Preferences dialog box (Figure 3-40).
The user can load preferences from the current design, global preferences, or default preferences.
The user can overwrite Current Design preferences to Global Preferences, Global Preferences to
Current Design preferences, and Default Preferences (with or without modifications) to either Global
Preferences or Current Design preferences, or both. This can be done by selecting the check boxes
at the bottom of the Edit Preferences window. The user can also reset the Global Preferences to
Default Preferences any time by using the Preferences > Reset Global Preferences to Default
option.
Figure 3-40. Load Preferences

Menu Options
Select OK to open a dialog box with tabs to set preferences for the following:
• Design Parameters
• Design Options
• Non-linear Launch Powers
• CS Tx PAF (CoreStream only)
• Color
• Add/Drop Capacity
• Default Client SFP/XFP
• TXCVR Default
• Save Options
• VMUX OADM Settings
• Service Card Defaults
• Regen Card
• Design Constants
• Display Options
The preference set in use is shown in parentheses in the title bar of the Preferences window (Figure
3-49). The Global Preferences apply to all new designs created on the canvas or by import of an
Excel Input Template.

Menu Options
Design Parameters
EOL BER is set at IE-15 (Figure 3-41). Invoke Channel Power Equalization for Fixed OADM
Networks is enabled by default and should normally remain checked. It may be unchecked when
working with a Fixed OADM design that does not contain amplifiers to avoid unnecessarily pad
equalizing add traffic with express traffic. For small, low loss Fixed OADM network designs,
unchecking this option may help avoid amplifier placement. However, this option must be checked
for any Fixed OADM designs containing amplifiers or the subsequent optical deployment of the
network design will not be valid.
Figure 3-41. Design Parameters
Design Options
Select the Design Options tab (Figure 3-42 and Figure 3-43). In the Network Module Preference
area, select either CS or CN4200, and for 4200 network designs, select the Service Type.
Subsequent choices displayed are based on CS or CN4200 selection. In the Network Modules
area, check the module(s) that will be offered as a selection in the Lightpath Wizard. In the
Wavelength Band Priority area, select a band for 100 GHz OADM and re-order the list by using
the up- and down-arrows. One priority level can be assigned to any one half band, with the highest

Menu Options
priority at the top position and lowest priority at the bottom position. A check box option, Default
Band Priority, resets the order of the lists to default priority. This dictates the order in which CND
auto assigns wavelengths during lightpath creation, or channel additions to existing lightpaths.
Figure 3-42. Design Options, CN4200

Menu Options
Figure 3-43. Design Options, CoreStream
Non-linear Launch Powers

The Non-linear Launch Power tab allows the user to modify the default non-linear launch power
level for 10G and 40G wavelengths on a per fiber type basis.
Non-linear launch power values are the maximum channel power limits enforced during the linear
optimization of a network (with or without non-linear validation) but are not used by non-linear
optimization. The user can decrease the non-linear launch powers if the design fails non-linear
validation, or increase non-linear launch powers to attempt to increase optical reach (for 10G only),
though non-linear validation must subsequently pass.
For 10G and 40G channels, the launch power range is -15dBm to +7dBm regardless of the fiber
type. The per fiber type 40G launch power values are by default the same as 10G launch power
values. Specific guidance for 10G and 40G launch power levels for 40G or 10G + 40G designs are
given in Table 1-2 and Table 1-3.
The window (Figure 3-44) lists the fiber types supported by CND, along with a field for entering the
launch powers and an accompanying display of the default launch power for each fiber type. The
default launch power values are for display only; they cannot be edited. Non-linear launch power
values may be entered with one decimal place accuracy. If an invalid value is entered in any of the
cells, then CND will issue an error message. Click Restore Default to change all entered values to
the defaults. CND allows the user to adjust the 10G and/or 40G non-linear launch powers manually
on a uni-direction per link basis from the Link View GUI. If the check box "Apply Modified Non-linear

Menu Options
Launch Power Values to forced span launch powers in current design" is checked, then CND will
update all user forced as well as unforced non-linear launch powers in the design. If this box is not
checked, then CND will only update the unforced non-linear launch powers.
Figure 3-44. Non-linear Launch Powers

Menu Options
CS Tx PAF (CoreStream only)

Set PAF Power Adjustment Factor (dB) Values as shown in Figure 3-45.
The Default Power Adjustment Factor (dB) value is greyed out and shown to the right. A PAF value
in the uniform range of -8 to 9dB irrespective of fiber type can be entered.
Click Restore defaults to over write user entered values with the fiber based default PAF values.
'Check Apply Modified PAF Values to Forced PAF values in Current Design' to over write the user
forced PAF values in existing spans in the network with the ones entered in the preferences. If this
option is not checked, the updated preferences values will be applied only to the spans in network
where user has not manually specified PAF values.
Check Persist the preference values as Global Preferences also to persist the current
preferences modifications as Global Preferences.
Click OK to save the modified preferences.
Click Cancel to abandon the modified preferences settings.
Figure 3-45. CS Tx PAF

Menu Options
Color
If desired, select the Color tab to select a color for locked links. Left-click Locked link color... to
open a color chart and select a new color. When a link is locked using the Network Locking options
it can be difficult to distinguish in the Network View if the network is large. This option gives the user
the ability to select a highlight color that stands out in the network design.
Figure 3-46. Color
Add/Drop Capacity
Select the Add/Drop Capacity tab to configure add/drop capacity for 4200 ROADM designs
(Figure 3-47), to be applied as the global default setting to all nodes. Select from capacity driven,
16, or 40 channels. The settings made here apply to the entire network. If the design includes a part
of the network with a less aggressive configuration, place a component, for example a low-power
transmitter, into the spur.
The user can also select any or all of the Options applicable to Guaranteed Growth to 16/40
Channel Add/Drop which, as the title indicates, are specific to nodes with 16 or 40 Channel Add/
Drop Capacity settings. The first option considers integrated port OPS for future growth channels
when only tunable transponders are in use; therefore, the kernel considers additional OPS loss in
the add/drop direction while processing the current channels. The second option considers low Tx
power (0dBm) for future growth channels when only tunable transponders are in use; therefore, the
kernel considers an additional 5dB loss in the add direction for current high power channels. The
third option considers discrete port OPS for future growth channels; therefore, the kernel considers
an additional 5dB + OPS loss in add, and OPS loss in drop, direction while processing the current
channels.

Menu Options
Figure 3-47. Add/Drop Capacity
Default Client SFP/XFP

Select the default client SFP/XFP modules to be auto-populated in the Service Card Configuration
window for various service card types (Figure 3-48). For EM6 and M6 (all varieties), M3, and G6,
selections at port 1 are applicable only for any child cards added for aggregation purposes, because
the OTU1 DWDM SFP is populated in port 1 by default, while selections at other ports are applicable
for parent as well as child cards. The preferences set here are applied to subsequently created
lightpaths, not those already created.
CND only allows the SR1, IR1, CWDM, and DWDM SFPs in port 1 of the G10 card and not in other
ports. This is due to G10 thermal requirements.

Menu Options
Note the Quad-10T allows a different XFP setting for each of the four client ports. It is normally
recommended that all four ports be set with the same XFP, as CND will consolidate all channels at
a node onto the fewest Quad-10T cards, making it difficult for the user to predict which client/network
port pair is assigned to which physical port pair position or specific Quad-10T card. The user can edit
the XFP assignments as appropriate from the Channel Card and Port Info GUI (Figure 5-70).
Figure 3-48. Default Client SFP/XFP

Menu Options
TXCVR Default
For F10/FC4-T cards, select the default network transponder type to be auto-populated at the A and
Z nodes when the OTU2 network module selection allows for tunable sparing (Figure 3-49). The
default is a fixed frequency transponder, which normally is the desired choice.
Select the transceiver to be used as the default at the 4200 node with an FSLM-2 card with a DWDM
XFP (FSLM-2), and the default to be used with an FSLM-2-TN card with an LT-EXFP (in an RS
chassis). The selections made here will be auto-populated in the Service Card Configuration
window. For a specific group of channels, the user can make a different choice during lightpath
creation, using the Lightpath Wizard.
Figure 3-49. TXCVR Default

Menu Options
Save Options
Select the Save Options tab to choose a location to save file backups. CND always performs a
backup function, saving the current and prior five versions of a file with “copy1” (current) through
“copy6” (oldest) appended. The path shown in Figure 3-50 is the default save location. When
checked, Autosave implements a periodic autosave of the current design file based on the specified
time interval, which is adjustable using the up and down arrows.
Figure 3-50. Save Options
VMUX OADM Settings

Select the VMUX OADM Settings tab to choose between Lowest Total Cost and Lowest Y1 Cost.
Lowest Total Cost will use VMUX8 as much as possible rather than a pair of VMUX4s within the
same band. Lowest Y1 Cost will replace a VMUX8 with a pair of VMUX4s if it allows only one VMUX4
to be populated at Y1. The user can choose between BS5 Preferred and Concatenated VMUX
Preferred (Figure 3-51) as the VMUX Terminal option. The BS5 is a 5-group band splitter that
muxes/demuxes all five 100 GHz DWDM wavelength groups into and from an aggregated DWDM
signal. Concatenated VMUX Preferred will use daisy chained VMUX cards when there are four or
fewer VMUX cards at a terminal node. BS5 Preferred will force a BS5 band splitter for cases where

Menu Options
a VMUX terminal node has four or fewer VMUX cards. The BS5 is used any time more than four
VMUX cards are present at a VMUX Terminal node, regardless of the setting, as only up to four
VMUX cards can be concatenated.
Figure 3-51. VMUX OADM Settings

Menu Options
Service Card Defaults

Select the default service cards to be auto-populated for OTU2, Enhanced OETUNE OTU2, OTU1,
ETR, and CLO wavelengths (Figure 3-52).
Figure 3-52. Service Card Defaults

Menu Options
Regen Card
Select the regen card type to be used as the default based on network module. Note that the choices
offered are based on interoperability due to chirped or unchirped transponder design. (Figure 3-53).
Figure 3-53. Regen Card
Design Constants
Set the loss and PMD coefficient for the spans (Figure 3-54), with any change applied to all spans
in the network design.
For the loss coefficient, select either dB/km or dB/Mile from the drop-down list, and enter any positive
number with up to two decimal digits. The default value is 0.25 for dB/km and 0.40 for dB/Mile.
For the PMD coefficient, enter any value between 0 and 1.0 ps/sqrt(km). The default value is 0.1 ps/
sqrt(km).
Figure 3-54. Design Constants

Menu Options
Display Options
Select the Display Options tab to choose between kilometers and miles. Select the desired wave
units for the Specify Wave window for both 4200 and CoreStream: Wave Id, Frequency, or
Wavelength (Figure 3-55).
Figure 3-55. Display Options
Window Menu Options

The Window menu options are the standard Windows choices as shown in Figure 3-56. If more than
one network design is open, highlight the desired design to give it focus in the CND tool view.
Figure 3-56. Window Menu Options

Menu Options
Help Menu Options

The Help menu options allow the user to check the version of CND that is running, to access the
CND User Guide, and to renew the CND license (Figure 3-57).
Figure 3-57. Help Menu Options
Menu Bar Icons

The menu bar icons provide shortcuts to various activities (Figure 3-58). Icons have focus or are
grayed out depending on the function displayed in the GUI pane. If a button is selected to perform a
function at an inappropriate time, such as prior to running a network design, an error message
displays. The user can mouse over a button to see its purpose.
Figure 3-58. Menu Bar Icons
Formatting Icons
The formatting icons provide shortcuts to standard Windows functions new, open, save, undo last
move, and redo (Figure 3-59).
Figure 3-59. Formatting Icons
Global Design Icons

The global design icons include buttons for demand settings, CoreStream design, and 4200 design
(Figure 3-60).
Figure 3-60. Global Design Icons

Menu Options
The demand settings button is a toggle; if Y1 demands are to be considered in the reports, click the
button once. The view changes to . To generate reports for the Y1+Yn demands, click the
button again to toggle it back to . Both buttons are disabled when a CoreStream design
has focus on the canvas.
: Performs a 4200 network design, disabled when a CoreStream design has focus on the
canvas.
: Performs a CoreStream network design, disabled when a 4200 design has focus on the
canvas.
Reports Icons
The reports icons include buttons for CN 4200 Chassis and Service Card Configuration (4200 only),
Generate Design Summary Report, Optical Service Report (4200 only), Generate Visio Report
(4200 only), Generate BOM Report, Generate Incremental BOM Report, and Generate 40G
Non-Linear Report (Figure 3-61).
Figure 3-61. Reports Icons
Force Option Icons (4200)

The force option icons include buttons for split VMUX8, force VMUX, force ROADM, force Mixed-
ROADM, and force not selected, which undoes the force action (Figure 3-62). Split VMUX8 can only
be performed after a kernel run, but the Force NE Type buttons can be used prior to the first kernel
run. These buttons are available only for 4200 non-fixed-OADM designs.
Force Option Icons
Globally Split VMUX8 Filters will split VMUX8s into pairs of VMUX4s as applicable for the
selected nodes, observing the limit of four concatenated VMUX cards per degree. It is disabled when
a CoreStream design or 4200 non-VMUX filter design has focus on the CND canvas.
Force NE as VMUX can be applied to single or multiple nodes. This button is disabled when a
CoreStream design has focus on the CND canvas.
Force NE as ROADM can be applied to single or multiple nodes. This button is disabled when
a CoreStream design has focus on the CND canvas.
Force NE as MixROADM can be applied to single or multiple nodes. This button is disabled
when a CoreStream design has focus on the CND canvas.

Menu Options
Clear Force NE can be applied to single or multiple nodes. This button is disabled when a
CoreStream design has focus on the CND canvas.
: Force No Equipment can be applied at amp sites for both CoreStream and 4200 networks and
is only active when a Link View GUI is open. When the user clicks on this icon, a window opens with
a list of all the site locations in the link. A checkbox is provided to select or deselect the Force No
Equipment option at any site (Figure 3-62). If the user has previously forced equipment at the amp
site, a confirmation window will state that all forced edits will be cleared from the site, and give the
user the option to continue or cancel. Once Force No Equipment is done, the amp site is considered
to be a fiber connection point and no equipment is placed there.
Figure 3-62. Force No Equipment Locations
Regen Icons
The forbid regen icon forbids regen placement for the selected object, and the clear forbid regen icon
reverses that setting and allows regen placement (Figure 3-63). The user can select the entire
network or one or more nodes from the Network View, or one or more amp sites from the Link View
GUI.
Figure 3-63. Forbid/Clear Forbid Regen Icons
Lock/Unlock Icons
The lock/unlock icons lock and unlock the network, a link, a lightpath, amps, and/or DCMs
(Figure 3-64). The equipment affected by clicking a lock/unlock icon varies based on the active CND
view and/or the GUI items that have been selected. “Locking Menu Options” on page 324 provides
the actions associated with the choices.
Figure 3-64. Lock/Unlock Icons

Menu Options
Lightpath Icons
The lightpath icons provide buttons to view, add a channel, delete, add protection/diverse routing,
and/or force a regen (Figure 3-65).
Figure 3-65. Lightpath Icons
: Open View Lightpath window, enabled for both CoreStream and 4200 network design views.
: Add channels to lightpath, enabled for both CoreStream and 4200 lightpath views.
: Delete lightpath, enabled for both CoreStream and 4200 lightpath views.
: Add protection/diverse routing to lightpath, enabled for both CoreStream and 4200 lightpath
views.
: Force regen, select to open the Force Regen Locations GUI, which lists all intermediate amp
and node sights along the optical path of the selected lightpath. This GUI allows the user to force
regens at specific amp or node locations by checking the status box associated with the desired
location(s). Similarly, the GUI provides a “Forbid Regen” checkbox in the lower left corner, which
prevents regen from being placed on a lightpath. If force regen is performed on a lightpath, then the
user is responsible for placing all required regen to get a valid network design result. CND will
provide informative error messages if a lightpath with force or forbid regen does not pass the network
design.
Global Edit Icon

The global edit icon (Figure 3-66) opens the Global Edit Options window (Figure 3-67) where the
user can modify the Service Type, Year Type, Protection Type, and/or Network Module at the
network level by using the Same and Any wild card settings. For example, this can allow the user

Menu Options
to modify Y1 OTU2 service types with any protection type or network module to be YN by selecting
OTU2/Y1/Any/Any for the From column and OTU2/YN/Same/Same for the To column and then
clicking Apply. Note that selections are applied globally on eligible unlocked channels only.
Figure 3-66. Global Edit Icon
Figure 3-67. Global Edit Window
Manual/Auto Assign Icons

The Auto Assignment button is selected to convert all manual channel assignments to auto
assigned, which allows CND to auto assign the channel IDs on the subsequent design run. The
Manual Assignment is the converse, and will force all channels to be manually assigned to their
existing channel ID values (Figure 3-68). These buttons are context sensitive, where the selection
is applied to the entire network if selected while the Network View is open. The selection is lightpath
specific if the Lightpath View is open.
Figure 3-68. Manual/Auto Assign Icons
Force T3 DCMs to LL Equivalents Icon

The Force T3 DCMs to LL Equivalents icon converts unforced or unlocked Type 3 DCMs to their
corresponding low loss variants as CND does not auto place low loss Type 3 DCM unless the 40G
Unchirped Dispersion Map is selected. (Figure 3-69). When executed in the Link view, only Type 3
DCMs in that link are converted. A subsequent design run is required to revalidate the network with
the low loss Type 3 DCMs.
Figure 3-69. Force T3 DCMs to LL Equivalents Icon

Menu Options
Zoom Icons
The zoom icons zoom the network graphic display in or out incrementally (Figure 3-70).
Figure 3-70. Zoom Icons
Show Tree Icon

The show tree icon opens a Tree View of the network on the left-hand side of the CND window
(Figure 3-71).
Figure 3-71. Show Tree Icon
Users can open a Tree View of the network (Figure 3-73). A drop-down list at the top is used to
select expansion of the entire network, nodes, links, or lightpaths. Regardless of which view is
chosen, the other elements can be expanded by clicking the + next to the desired element.
Several GUI operations can be performed by right-clicking from the Tree View, as shown in
Figure 3-72. The options that are available depend on the object selected and the network design
options. Left-clicking opens the view specific to the selected group.
Figure 3-72. Tree View Options for 4200

Menu Options
To close the Tree View, click the icon again, which is renamed the Hide Tree icon when the Tree
View is opened.
Figure 3-73. Show Tree View
Tree icon
Editing Multiple Lightpaths/Channels

From the Tree View, right-click a lightpath and select Edit Lightpath, as shown in Figure 3-74.
Figure 3-74. Edit Lightpath

Menu Options
To select multiple lightpaths/channels in Edit Channel Properties for Lightpath window, press <Shift>
+ left-click to select a range of channels or <Ctrl> + left-click to select single or multiple non-
contiguous items. The Edit Traffic Properties Figure 3-75 or Edit Wave Properties Figure 3-76 data
is updated based on the selections.
Figure 3-75. Edit Traffic Properties

Menu Options
Figure 3-76. Edit Wave Properties
Pressing 'Apply' applies the data selections to all selected Lightpaths/Channels.
CoreStream Enable/Disable SOADM as DGE

These icons can be used to enable or disable SOADM as DGE. SOADM will not be considered as
DGE in nodes where Disable SOADM as DGE is forced. SOADM will be used as DGE as needed
in nodes where Disable SOADM as DGE is forced. (Figure 3-77).
Figure 3-77. SOADM as DGE Icons

Menu Options
CoreStream Force/Clear Shelf Amp (USA6)

These icons (Figure 3-78) can be used to force/clear USA6 shelf amp on a per-node basis. These
will not work for ILA Regen sites and ILA regen site must be converted to a node in order to place
the USA6 shelf amp.
Figure 3-78. Shelf Amp (USA6) Icons
Generate 40G Non-Linear Report

The icon (Figure 3-79) can be used to open the Generate 40G Non-Linear Report window, where
the path to the network design/run log folder can be selected/entered.
Figure 3-79. Generate 40G Non-Linear Report Icon
Legend
The legend (Figure 3-80) provides definitions (Table 3-2) for the icons displayed in the Node View.
Figure 3-80. Icon Legend
4200 CoreStream
Table 3-2. Icon Legend Definitions

Legend Definition
OOO Port All-optical pass-through OADM port (CoreStream networks)

OEO Port Optical-electrical-optical port, used to regenerate the optical signal
at a terminal port (CoreStream networks)

Menu Options
Table 3-2. Icon Legend Definitions (Continued)

Legend Definition
Optically Expressed Wavelengths expressed through two ports within an NE optically

without OEO regeneration
Electronically Regenerated A wavelength that has been electrically regenerated
Fiber OPS Protected Link Link is pink colored to distinguish from non Fiber OPS link
(4200 networks)
Non Fiber OPS Link Link is green colored to distinguish from Fiber OPS link
(4200 networks)
Node Port with Edit Filter Flag True A node port (degree) at which user has performed an edit filter
operation to modify the filter configuration placed by a kernel run
(4200 networks)
Single data rate lightpath traffic A group of wavelengths carrying one type of data traffic
Two data rate lightpath traffic A group of wavelengths carrying two types of data traffic.
Optically Expressed via Cross Over Wavelengths expressed through WSS-2 in multi-degree SOADM
node comprised of WD S Term and WD SOADM NEs.

4
Chapter 4:
Excel Input Template
Network designs are commonly entered into the CND by first entering information about the network
into an Excel spreadsheet and then importing it into CND. After a network appears on canvas, it can
be modified further and will always be saved in XML. Edits to the network are not rewritten to the
Excel file, even if the network data was originally loaded using Excel. The XML files are used as the
design files for subsequent network design.
Once the Excel template has been filled in satisfactorily, it can be opened by selecting File > Open
in CND and choosing the.xls template file. If there are errors in the template, they will display in the
message area of the CND GUI. If the template is error-free, the design will open on the CND canvas,
and will be saved as an xml file.
General Information About Excel Input Templates

The Excel Input Templates are specific to either 4200 or CoreStream and are located as shown in
Figure 4-1. CND also creates desktop short cuts for both the 4200 and CoreStream version of the
Excel Input Template.
Figure 4-1. Location of Excel Input Templates
Most of the design time is spent inputting data properly in the input template. Note the following
points when creating the Excel input file as the starting point for a CND network:
• Do not password protect workbook or worksheets.
• Use all UPPER case for node and link names to avoid possible capitalization errors.
• Use only alphanumeric characters in node and link names. Do not use special characters; note
that spaces are considered special characters. Allowed characters allowed are A-Z, a-z, 0-9,
hyphen (-), and underscore (_).
Note: Both templates contain an Instructions tab. It is strongly recommended that these
instructions be reviewed prior to beginning work with the Excel Input Template.
Ciena Network Designer® CND 009-2011-160 - Revision A

70 Chapter 4 - Excel Input Template
General Information About Excel Input Templates
Macros
The following points apply to the macros embedded in the template.
• Enter links details in the Links sheet and traffic details in the routing sheets
• Node names and degree in the Nodes sheet are automatically filled from inputs in the Links
sheet
• The SpansPhysical sheet is also automatically filled from inputs in the Links sheet
• In the AllSpansPhysical sheet, user can change the default values for the network design.
• The SpansPhysical sheet is filled in based on values in the Links sheet and defaults in the
AllSpansPhysical sheet - but can be modified.
• The drop-down list content in routing sheets is automatically created when they are activated
• Length units can be modified by selecting the Link_Length drop-down in the C2 cell in the Links
sheet. Default units are Km. Note that toggling this value does not convert length values
between kilometers and miles. Changing the units tells CND which base the length units are in.
Error Checking
The list below describes the error checking provided by the macros.
• Error checking of Links sheet is done and reported in the Links sheet when user tries to move
to any other sheet.
• Errors on Links sheet prohibit movement to other sheets until the errors are corrected.
• If there are no errors in the Links sheet, the Nodes sheet and SpansPhysical sheets are
updated automatically from the Links sheet.

Chapter 4 - Excel Input Template 71
CoreStream Input Template
Error Correcting
If there are errors in the template file, the CND reports those errors, as explained below.
• The message area of the CND main window displays reports of errors in the input template
when opened.
• The errors on individual sheets are reported as they are made (Figure 4-2). Once all the errors
on one sheet are corrected, the errors on another sheet can be reported.
Figure 4-2. Error Message

The following figures show an example of the CoreStream template pages needed to enter data for
network creation.
Nodes
Figure 4-3 shows the information that must be entered regarding node identification.
• The entries in the NODE_NAME column become the nodes in the network when the Excel
template is opened using CND.
• The NODE_NAME and DEG columns are locked. The user is not required to enter the values
manually, as both these columns are filled automatically from the user entries made in the
Links sheet.
• The entries in the NODE_LOC_X and NODE_LOC_Y column signify the X and Y coordinates
of the nodes on CND canvas when the excel template is opened using CND.
• Values for the NODE_LOC_X and NODE_LOC_Y columns may be entered, but CND
automatically assigns X and Y values for the nodes even if the entries in these columns are
blank.
• Entries in the DEG column signify the number of connected links for a corresponding node.

Table 4-1. Excel Template Data Ranges for Nodes

Column Name Data Range User Editing
NODE_NAME A-Z, a-z, 0-9, hyphen and “_” underscore Excel macro fills automatically
character
NODE_LOC_X 1 - 2147483647
NODE_LOC_Y 1 - 2147483647
DEG 1-4 Excel macro fills automatically
Figure 4-3. Sample Input Template, Nodes (CoreStream)
Links
Figure 4-4 shows the information that must be filled in regarding links. All fields on the links page
must be filled in. The Links sheet is used to define the node-to-node links in the network. Each row
entry in the Links sheet corresponds to one node-to-node link. Note the following points while
entering values in the Links sheet rows:
• FiberNodeA and FiberNodeB correspond to the node names between which the link exists.
• Entry for the Link_length corresponds to the total link length.
• Choose the units for length as Km or miles by selecting the drop-down list at the C1 cell.
• When the selection in the C1 cell is Links_length_Km, CND updates the selection for the
Length units in the Preferences menu to Km. Similarly, when the selection in the C1 cell is
Links_length_mi, CND automatically updates the selection for the Length units in the
Preferences menu to miles.
• From the selection in the C1 cell in the Links sheet, the corresponding headings in the
AllSpansPhysical and SpansPhysical sheets are modified by the Excel macro automatically,
avoiding user modification of the headings in the template (which can lead to errors).
• The entry for the Spans column in the Links sheet signifies the number of spans in that link.
From the entry made in the Spans column, a corresponding number of row entries is made
automatically in the SpansPhysical sheet.
• The entry for the Link_Name column in the Links sheet signifies the name of that link. The
default name is <FiberNodeA>_<FiberNodeB>. This default value can be modified by typing
manually into the cell.

• Based on the entries made in the Links sheet, the Nodes sheet and the SpansPhysical sheet
are updated. The macro that does the updates only runs when the Links sheet is deactivated. If
there are errors in the links sheet, these are reported in the links sheet for the user to correct
(Figure 4-5). A listing of these errors can be found in Chapter 7.
• The entry for the Link_Type column in the Links sheet signifies the link as either Agility or
Regional. The entry ILA2 defines the link as Regional. Otherwise, the link type is defined as
Agility.
Table 4-2. Excel Template Data Ranges for Links

FiberNodeA A-Z, a-z, 0-9, hyphen and “_” underscore character User to enter values
FiberNodeB A-Z, a-z, 0-9, hyphen and “_” underscore character User to enter values
Link_Length_Km 1 - 9999 Km or 1 - 6214 mi depending on selection User to enter values
made by user in C1 cell in Links sheet
Spans 1 - 32 User to enter values
Link_Name A-Z, a-z, 0-9, hyphen and “_” underscore character Excel macro fills automatically;
user can modify
Link_Type Specify Agility (Default) and Regional (ILA2) links. Use the pull-down menu to
specify link type.
Figure 4-4. Sample Input Template, Links (CoreStream)
Figure 4-5. Sample Error Messages, Links (CoreStream)
AllSpansPhysical
Figure 4-6 shows the AllSpansPhysical page, which provides for high-level network design without
detail by span. Entered parameters will be applied to newly added spans, and default values are
defined for the All_Span_Fiber_Type, All_Span_Distance_Km, All_Span_Loss, All_Span_Margin,
All_Span_Dispersion, and All_Span_Dispersion_Slope, Version, Network_Type, and
Loss_Coefficient_dBperKm. Regardless of the entry in the C1 cell in the Links sheet, the loss
coefficient value to be entered is in dB/km.

Table 4-3. Excel Template Data Ranges for AllSpansPhysical

Column Name Data Range User Editing Remarks
All_Span_Fiber_Type NDSF, LS, OldLS, Default values When

TWPlus, TWC, filled All_span_fiber_type is
TWRS, Leaf, ELEAF, automatically by changed,
DSF, Teralight, or Excel macro All_span_dispersion and
TWReach All_span_dispersion slope
values are automatically
changed to that fiber’s
default values.
All_Span_Distance_Km 1 - 300 Km or 1 - 186 Default values
mi depending on filled
selection made by automatically by
user in C1 cell in Links Excel macro
sheet
All_Span_Loss 0.1 - 55 Default values
filled
automatically by
Excel macro
All_Span_Margin 0-9 Default values
filled
automatically by
Excel macro
All_Span_Dispersion (-5) - 25 Default values Protected cell. User
filled cannot edit. When
automatically by All_span_fiber_type is
Excel macro changed, default
dispersion value is
changed automatically.
All_Span_Dispersion_ Slope 0 - 0.3 Default values Protected cell. User
filled cannot edit. When
automatically by All_span_fiber_type is
Excel macro changed, default
dispersion slope value is
changed automatically.
Version CND5.2 Fixed value
Network_Type CoreStream Fixed value

Table 4-3. Excel Template Data Ranges for AllSpansPhysical (Continued)

Loss_Coefficient_dBperKm 0 - 0.5 dB/Km or Default values

0 - 0.8 dB/mi filled
depending on automatically by
selection made by Excel macro
user in C1 cell in Links
sheet
PMD_Coefficient_psPerSqrtKm 0 - 1.00 ps/sqrt(km) Default value Fiber Polarization Mode
filled Dispersion coefficient
automatically by
Excel macro
Figure 4-6. Sample Input Template, AllSpansPhysical (CoreStream)
SpansPhysical
Figure 4-7 shows where to enter the physical information about the spans. All the entries are
generated automatically from the entries made in the Links sheet. Note the following points:
• There is the option to edit span parameters (Bi-directional)
• There is the option to force No Equipment
• There is the option to specify Tx/Rx PAFs (Uni-directional)
• Tx PAF is applicable to ILA degrees as well as end node degrees
• Rx PAF is applicable to end node degrees

Table 4-4. Excel Template Data Ranges for SpansPhysical

Span_Dispersion (-5) - 25 Excel macro fills When All_Span_Fiber_Type is changed, default
automatically dispersion value is changed automatically.
“0” is not a valid value for non-DSF fibers.

“blank cell” is not a valid value in all cases.
For all such instances, CND parser considers default

value based on fiber type. Common message, “Zero or
blank dispersion and dispersion slope values have been
replaced with the specified fiber type's default values.” is
shown.
In all other cases, if entered dispersion value is beyond+/

-25% value of default value based on fiber type, separate
messages are shown referring to each of those cells,
“Dispersion value is beyond +/- 25% of default Dispersion
value of <value> for <FiberType> fibre type in Span
worksheet for span row <rowNo>.”
Span_Dispersion_ 0 - 0.3 Excel macro fills When All_Span_Fiber_Type is changed, the default
Slope automatically dispersion slope value is changed automatically.
“0” and “blank cell” are not valid values in all cases.

value based on fiber type. Message “Zero or blank
dispersion and dispersion slope values have been
replaced with the specified fiber type's default values.” is
shown.
In all other cases, if entered dispersion slope value is

beyond+/-25% value of default value based on fiber type,
separate messages are shown referring to each of those
cells, “Dispersion Slope value is beyond +/- 25% of
default Dispersion Slope value of <value> for
<FiberType> fibre type in Span worksheet for span row
<rowNo>.”
Force_No_ True/False Defaults to Available at amp sites. User sets to "True" to model amp
Equipment False; user can site as fiber connection point with no equipment placed.
modify
Tx PAF W to E(dB) -8 to 9dB User can Transmit PAF West to East, applicable to ILA and end
modify. node degrees.
Tx PAF E to W(dB) -8 to 9dB User can modify Transmit PAF East to West, applicable to ILA and end
node degrees.
Rx PAF E to W(dB) -8 to 9dB User can modify Receive PAF East to West, applicable to end node
degrees.
Rx PAF W to E(dB) -8 to 9dB User can modify Receive PAF West to East, applicable to end node
degrees.

Table 4-4. Excel Template Data Ranges for SpansPhysical (Continued)

PMD Coefficient (W displayed with User can
to E) default values modify.
from
AllSpanPhysical
sheet
PMD Coefficient (E displayed with User can
to W) default values modify.
from
AllSpanPhysical
sheet
Figure 4-7. Sample Input Template, SpansPhysical (CoreStream) (sections of the spreadsheet
shown vertically)
Unprotected_Traffic/Protected_Traffic
Figure 4-8 (unprotected) and Figure 4-9 (protected) show where to place the information that
creates the routes, using the node - link - node concept. Note the following points:
• Unprotected_Traffic sheet defines the unprotected Y1 traffic.
• Protected_Traffic sheet defines the protected Y1 traffic.
• Columns Protection_Type and Path_Type are hidden on the Unprotected_Traffic sheet
because they are not applicable for unprotected traffic. These columns define the protection
and path type of the traffic, respectively.
• The demand name cannot be repeated for different traffic on the Unprotected_Traffic sheet.
• The demand name cannot be repeated for different traffic on the Protected_Traffic sheet. But
the demand name must be same for the primary and protected paths of the same traffic.
• NodeA and NodeB are the starting and ending nodes of the traffic.
• Entry for the Channels column defines the number of channels in the traffic.
• Entry for the Data Rate column defines the type of the channels in the traffic. If there are
channels with different data rates, there will be a separate entry for each data rate.

• Entry for the Network_Module column defines the network module type for that data rate in the
traffic.
• In the Specify_Wave_IDs column, wave ids can be specified for the channels in the traffic by
entering values of format: Wave_id, Wave_id2...Wave_idN.
• The value in the Power_Offset_(dB) column should be used as power offset for 40G channels
for both west to east and east to west directions. This offset value will be applicable for all the
channels specified in the “Channels” column and “Specify_Wave_Ids”. If different 40G
channels have to have different channel power offset values, they should be entered in
different rows with the required channel power offset in each corresponding row. While parsing,
for channels where no specific value is entered for the Power Offset, 0.0dB will be considered
as default value.
• The traffic path can be defined by selecting the enroute node names from the drop-down lists in
the columns with headings Node, Node2…Node50.
• Columns with headings Link, Link2…Link49 are filled with default link names such as
Node_Node. The user can enter other link names in these columns manually that match the
entries in the Links sheet. In addition, the user can select link names from the drop-down lists in
these columns.
• The entry for the Hops column equals the number of the links in the defined path for that traffic.
• There will be a parser error if any of the following conditions is not valid:
• If there is at least one 40G channel via a span having fiber type other than NDSF, LS, TWC
or ELEAF.
• If there is at least one 40G channel via a span having fiber type as NDSF, LS, TWC or
ELEAF, but the dispersion and/or slope are non-default values.

Table 4-5. Excel Template Data Ranges for Unprotected_Traffic/Protected_Traffic

Column
Data Range User Editing Remarks
Name
Demand 1 - 2147483647 User enters value Demand name is same for primary
and protected traffic rows
NodeA A-Z, a-z, 0-9, hyphen and “_” User can select from drop-
underscore character down list or type in manually
NodeB A-Z, a-z, 0-9, hyphen and “_” User can select from drop-
Channels 1-96 in Agility links User enters value No of channels in any node to
1-80 in Regional links. node link cannot exceed the limit.
Data_Rate 10G, 40G
Hops 1 - 49 User enters value Hops must match hops defined in
path by selecting intermediate
nodes and intermediate links
Network_ 10G C-BAND G.709 User can select from drop- Transceiver/network module
Module 10G RB G.709 down list or type in manually options. Should be the same for
10G G.709 SWAP (C BAND-RB) primary and secondary paths.
10G G.709 SWAP (RB-C BAND)
eDC40G with Enh PMD
Compensation (NTK539PAE5)
eDC40G C Band
(NTK539PBE5)
eDC40G C Band Regional
(NTK539PCE5)
eDC40G C Band Metro
(NTK539PDE5)
Protection_ OPS PORT PROTECTED User can select from drop- To be used on routing sheets for
Type down list or type in manually protected traffic. Only OPS is
(Protected_ supported.
Traffic only)
Path_Type Primary, Secondary User can select from drop- Used on routing sheets for
down list or type in manually protected traffic. Both rows for
Primary and Secondary paths
shall be one after the other, row for
primary path being first
Specify_ 1-96 User to enter values in the Should be the same for primary
Wave_ IDs format : Wave_id1, wave_id2, and secondary paths.
..., Wave_idN
Power Offset If data rate is 10G, 0.0. If data rate is 10G, non- Should be used for both west to
(dB) If data rate is 40G, 4 to +6. editable. east and east to west directions.
If data rate is 40G, user to Should be the same for primary
enter value. and secondary paths.
Node1 A-Z, a-z, 0-9, hyphen and “_” User can select from drop-
Link1 A-Z, a-z, 0-9, hyphen and “_” User can select from drop-

4200 Input Template
Figure 4-8. Sample Input Template, Unprotected_Traffic (CoreStream)
Figure 4-9. Sample (blank) Input Template, Protected_Traffic (CoreStream) - Left side
Figure 4-10. Sample (blank) Input Template, Protected_Traffic (CoreStream) - Right side
4200 Input Template

The following figures show an example of the 4200 template pages needed to input data for network
creation.
Nodes
Note: Although the Nodes page is first in the template, fill in the Links page first.
Figure 4-11 shows the information on the Nodes page.

• The NODE_NAME and DEG columns are locked. The user is not required to enter the values
manually, as both these columns are filled automatically from the user entries made in the
Links sheet. Entries in the DEG column signify the number of connected links for a
corresponding node.
• Values for the NODE_LOC_X and NODE_LOC_Y columns may be entered to signify the X and
Y coordinates of the nodes on CND canvas when the Excel template is opened using CND.
Note that entries in these columns are not mandatory as CND automatically assigns X and Y
values for the nodes even if the entries in these columns are blank.

4200 Input Template
Table 4-6. Excel Template Data Ranges for Nodes

NODE_NAME A-Z, a-z, 0-9, hyphen and “_” Excel macro fills automatically based
underscore character on user entries in the FiberNodeA and
FiberNodeB values on the Links page.
NODE_LOC_X 1 - 2147483647 Location 1 is on the left of the canvas,
with increasing values to the right
NODE_LOC_Y 1 - 2147483647 Location 1 is at the top of the canvas,
with increasing values beneath
Figure 4-11. Sample Input Template, Nodes (4200)
Links
Note: Although the Nodes page is first in the template, fill in the Links page first.
Figure 4-12 shows the information that must be filled in regarding links. All fields on the links page
must be filled in. The Links sheet is used to define the node-to-node links in the network. Each row
entry in the Links sheet corresponds to one node-to-node link. Note the following points while
entering values in the Links sheet rows:
• FiberNodeA and FiberNodeB correspond to the node names between which the link exists.
• Entry for the Link_length corresponds to the total link length.
• Choose the units for length as Km or miles by selecting the drop-down list at the C1 cell.
• When the selection in the C1 cell is Links_length_Km, CND will force the selection for the
Length units in the Current Preferences menu to Km. Similarly, when the selection in the C1
cell is Links_length_mi, CND will force the selection for the Length units in the Current
Preferences menu to miles.
• The entry for the Spans column in the Links sheet signifies the number of spans in that link.
From the entry made in the Spans column, a corresponding number of row entries is made
automatically in the SpansPhysical sheet.

4200 Input Template
• The entry for the Link_Name column in the Links sheet signifies the name of that link. The
default name is filled automatically as <FiberNodeA>_<FiberNodeB>. This default value can be
modified by typing manually into the cell.
• The entry for the Fiber_OPS_Protected column in the Links sheet signifies whether the link is
Fiber OPS protected or not. Select Yes or No from the drop-down list. Selecting Yes adds
another row below the existing one for a secondary link. This row will contain the exact same
parameters as those for the primary link, but the length and span count values can be modified
for the secondary path. A blank cell in this column for the primary link is a valid entry, equivalent
to No. The Fiber OPS-protected cell for the secondary link is intentionally kept empty and the
user is restricted from modifying this cell. Upon clearing this cell for primary link, or selecting
No, the secondary link information will be deleted.
• In the Link_Type column, the type of link is displayed for the primary and secondary links. The
user is restricted from modifying this column for either the primary or secondary link.
• Based on the entries made in the Links sheet, the Nodes sheet and the SpansPhysical sheet
are updated. The macro that does the updates only runs when the Links sheet is deactivated. If
there are errors in the links sheet, these are reported in the links sheet for the user to correct
(Figure 4-13). A listing of these errors can be found in Chapter 7.

4200 Input Template
Table 4-7. Excel Template Data Ranges for Links

FiberNodeA* A-Z, a-z, 0-9, hyphen and “_” underscore character User to enter values
except for secondary
Fiber OPS link, where
node on secondary link
emulates primary
FiberNodeB* A-Z, a-z, 0-9, hyphen and “_” underscore character User to enter values
Link_Length_Km 1 - 9999 Km or 1 - 6214 mi depending on selection User to enter values
made by user in C1 cell in Links sheet
Spans 1 - 32 User to enter values
Link_Name A-Z, a-z, 0-9, hyphen and “_” underscore character Value filled automatically
Fiber_OPS_Protected Yes, No User can select from
drop-down list or type in
manually
Link_Type Primary/secondary Protected cell. User
cannot edit; value filled
automatically with
“PRIMARY” and
“SECONDARY” in
successive rows
* The supported length of the node name string is max 100 characters.
Figure 4-12. Sample Input Template, Links
Figure 4-13. Sample Error Messages, Links

4200 Input Template
AllSpansPhysical
Figure 4-14 shows the AllSpansPhysical page, which provides for high-level network design without
detail by span. Default values are defined for the All_Span_Fiber_Type, All_Span_Distance_Km,
All_Span_Loss, All_Span_Margin, All_Span_Dispersion, All_Span_Dispersion_Slope, Version,
Network_type, Loss_Coefficient_dBperKm, PMD_Coefficient_psPerSqrtKm, and Chanel_Plan
rows. These fields do not require modification, but dictate the default values populated on the
Spansphysical sheet for blank values. The Loss_Coefficient_dBperKm entry defines the fiber loss
coefficient. The PMD_Coefficient_psPerSqrtKm is the default PMD coefficient for all fibers in the
design and should only be updated if a different specific value is globally desired in the design.
Regardless of the entry in the C1 cell in the Links sheet, the loss coefficient value to be entered is
in dB/Km.

4200 Input Template
Table 4-8. Excel Template Data Ranges for AllSpansPhysical

All_Span_Fiber_ NDSF, LS, OldLS, Default values filled When All_span_fiber_type is
Type TWPlus, TWC, TWRS, automatically by changed, All_span_dispersion
Leaf, ELEAF, DSF, Excel macro and All_span_dispersion slope
Teralight, or TWReach values are automatically changed
to that fiber’s default values.
All_Span_Distance_ 1 - 300 Km or 1 - 186 mi Default values filled The Link_Length values on the
Km depending on selection automatically by Links sheet supersede this value
made by user in C1 cell in Excel macro on the SpansPhysical sheet.
Links sheet
All_Span_Loss 0.1 - 55 Default values filled The Link_Length values on the
automatically by Links sheet multiplied by the
Excel macro Loss_Coefficient supercede this
value on the SpansPhysical
sheet.
All_Span_Margin 0-9 Default values filled
automatically by
Excel macro
All_Span_Dispersion (-5) - 25 Default values filled Protected cell. User cannot edit.
automatically by When All_span_fiber_type is
Excel macro changed, default dispersion value
is changed automatically.
All_Span_Dispersion 0 - 0.3 Default values filled Protected cell. User cannot edit.
_Slope automatically by When All_span_fiber_type is
Excel macro changed, default dispersion slope
value is changed automatically.
Version CND5.2 Fixed value
Network_Type 4200 Fixed value
Loss_Coefficient_dB 0 - 0.5 dB/Km or Default values filled
perKm 0 - 0.8 dB/mi depending automatically by
on selection made by Excel macro
user in C1 cell in Links
sheet
PMD_Coefficient_ps 0 - 1.00 ps/sqrt(km) Default value filled Fiber Polarization Mode
PerSqrtKm automatically by Dispersion coefficient
Excel macro

4200 Input Template
Figure 4-14. Sample Input Template, AllSpansPhysical (4200)
SpansPhysical
Figure 4-15 shows where to enter the physical information about the spans. All the entries are
generated automatically from the entries made in the Links sheet. Note the following points:
• All cells are updated automatically by the Excel macro with the corresponding default values
defined in the Links and AllSpansPhysical sheets.
• Modifying the node names is not allowed on the SpansPhysical sheet. Cells corresponding to
the node names are locked.
• In each link, the default names given to the amp sites are Site1, Site2 … SiteN. However, it is
recommended that the amplifier site names be modified to meaningful site names by typing in
the values in the corresponding cells in the FiberNodeB column. The corresponding update is
made automatically in the FiberNodeA column. The user is restricted from modifying the values
in the FiberNodeA column.
• Specific values for the Span_Fiber_Type, Span_Distance, Span_Loss, Span_Margin,
Span_Dispersion, Span_Dispersion_Slope, and PMD_Coefficient can be modified for each row
entry. Note that updating the Span_Distance value will update the Span_Loss value with the
distance value multiplied by the loss coefficient. The user may have to update the Span_Loss
value subsequently if it is a known, measured value. It is not recommended that the
Span_Dispersion and Span_Dispersion_Slope values be modified. The PMD_Coefficient value
can be updated on a per span basis if necessary, though this is typically only done if there is a
span-specific calculated coefficient based on measured PMD.

4200 Input Template
Table 4-9. Excel Template Data Ranges for SpansPhysical

FiberNodeA A-Z, a-z, 0-9, hyphen Excel macro fills
and “_” underscore automatically
character
FiberNodeB A-Z, a-z, 0-9, hyphen Excel macro fills
and “_” underscore automatically
character
Span_Fiber_Type NDSF, LS, OldLS, Excel macro fills When span fiber type is changed, the dispersion and
TWPlus, TWC, automatically dispersion slope values are automatically changed to
TWRS, Leaf, ELEAF, that fiber’s default values.
DSF, Teralight, or
TWReach
Span_Distance_mi/ 1 - 300 Km or 1 - 186 Excel macro fills However, leaving any SpanLength cell empty would
_Km mi depending on automatically raise an error, reported in Spansphysical sheet
selection made by column “I.” Unless all spans have valid span lengths,
user in C1 cell in transitioning to any other sheet is disabled.
Links sheet
Span_Loss 0.1 - 55 Excel macro fills Default value entered by macro equals product of per
automatically span length and loss coefficient.
Span_Margin 0-9 Excel macro fills
automatically
Span_Dispersion (-5) - 25 Excel macro fills Modification not recommended.
automatically When All_Span_Fiber_Type is changed, the default
dispersion slope value is changed automatically.
“0” is not a valid value for non-DSF fibers. “blank cell”
is not a valid value in all cases.
replaced with the specified fiber type's default values.”
is shown.
beyond+/-25% value of default value based on fiber
type, separate messages are shown referring to each
of those cells, “Dispersion value is beyond +/- 25% of
default Dispersion value of <value> for <FiberType>
fibre type in Span worksheet for span row <rowNo>.”

4200 Input Template

Span_Dispersion_ 0 - 0.3 Excel macro fills Modification not recommended.
Slope automatically When All_Span_Fiber_Type is changed, the default
dispersion slope value is changed automatically.
“0” and “blank cell” are not valid values in all cases.
replaced with the specified fiber type's default values.”
is shown.
beyond+/-25% value of default value based on fiber
type, separate messages are shown referring to each
of those cells, “Dispersion Slope value is beyond +/-
25% of default Dispersion Slope value of <value> for
<FiberType> fibre type in Span worksheet for span
row <rowNo>.”
Force_No_ True/False Defaults to Available at specific amp sites. User sets to "True" to
Equipment False; can be model amp site as fiber connection point with no
modified by user equipment placed.
PMD_Coefficient 0 - 5.00 ps/sqrt(km) Excel macro fills
automatically
Link_Type PRIMARY or Excel macro fills This cell cannot be modified by the user and is auto
SECONDARY automatically populated as "PRIMARY" or "SECONDARY" if the link
is OPS protected.
Add_DGE_Site True Select from An amp site can be specified as a DGE in the
False drop-down Spansphysical sheet of the Excel input template.
menu Adding a DGE site will be allowed only if the Amp site
is not a no-equipment site as shown in Figure 4-16.
In the template these two options are mutually
exclusive, therefore, both options cannot be Yes.
10G Launch Power -15dBm to +7dBm User to enter This cell is used to enter a limit for the non-linear
W to E(dBm/ch) values launch power used for Linear optimization with or
without Non-linear Validation in the West to East
direction for 10G channels. If a value outside the
range is entered, CND will raise an error and the
design will not load. If the amp site has been forced as
No-Equipment then this cell cannot be modified.
40G Launch Power -15dBm to +7dBm User to enter This is used to enter a limit for the non-linear launch
W to E(dBm/ch) values power used for Linear optimization with or without
Non-linear Validation in the East to West direction for
40G channels. If a value outside the range is entered,
CND will raise an error and the design will not load. If
the amp site has been forced as No-Equipment then
this cell cannot be modified.
10G Launch Power -15dBm to +7dBm User to enter This cell is used to enter a limit for the non-linear
E to W(dBm/ch) values launch power used for Linear optimization with or
without Non-linear Validation in the East to West
direction for 10G channels. If a value outside the
range is entered, CND will raise an error and the
design will not load. If the amp site has been forced as
No-Equipment then this cell cannot be modified.

4200 Input Template

40G Launch Power -15dBm to +7dBm User to enter This is used to enter a limit for the non-linear launch
E to W(dBm/ch) values power used for Linear optimization with or without
Non-linear Validation in the West to East direction for
40G channels. If a value outside the range is entered,
CND will raise an error and the design will not load. If
the amp site has been forced as No-Equipment then
this cell cannot be modified.
Figure 4-15. Sample Input Template, SpansPhysical (4200)
Demand and Routing

Figure 4-16 shows where to place the information to create routes. Note the following points:
• R-OTUN-Y1-UnProt sheet defines the unprotected Y1 traffic.
• R-OTUN-YN-UnProt sheet defines the unprotected YN traffic.
• R-OTUN-Y1-Prot sheet defines the protected Y1 traffic.
• R-OTUN-YN-Prot sheet defines the protected YN traffic.
• Columns Protection_Type and Path_Type are hidden on the R-OTUN-Y1-UnProt and
R-OTUN-YN-UnProt sheets because they are not applicable for unprotected traffic. These
columns define the protection and path type of the traffic, respectively.
• The demand name cannot be repeated for different traffic on the R-OTUN-Y1-UnProt and
R-OTUN-YN-UnProt sheets.
• The demand name cannot be repeated for different traffic on the R-OTUN-Y1-Prot and
R-OTUN-YN-Prot sheets. But the demand name must be same for the primary and secondary
paths of the same traffic.
• NodeA and NodeB are the starting and ending nodes of the traffic.
• Entry for the Channels column defines the number of channels in the traffic.
• Entry for the Data Rate column defines the type of the channels in the traffic. If there are
channels with different data rates, there will be a separate entry for each data rate.
• Entry for the Network_Module column defines the network module type for that data rate in the
traffic.
• In the Specify_Wave_IDs column, wave ids can be specified for the channels in the traffic by
entering values of format: Wave_id, Wave_id2...Wave_idN. This is an optional field, where
blank entries allow CND to auto assign wavelength IDs based on Preferences > Design
Options > Wavelength Band Priority.
• The traffic path can be defined by selecting the enroute node names from the drop-down lists in
the columns with headings Node, Node2…Node50.

4200 Input Template
• Columns with headings Link, Link2…Link49 are filled with default link names such as
Node_Node. The user can enter other link names in these columns, but this is not
recommended, as any edits should be done in the Links sheet.
• The entry for the Hops column equals the number of the links in the defined path for that traffic.

4200 Input Template
Table 4-10. Excel Template Data Ranges for Demand and Routing
Column
Name
Demand_name 1 - 2147483647 User enters value Demand name is same for primary
and protected traffic rows
NodeA A-Z, a-z, 0-9, hyphen and “_” User can select from drop-
NodeB A-Z, a-z, 0-9, hyphen and “_” User can select from drop-
Channels 1 - 40 User enters value Number of channels in any node to
node link cannot exceed the limit
Data_Rate OTU1, OTU2, OTU2es, ETR, User can select from drop-
CLO, OTU1(ISC2/ISC3c), down list or type in manually
OTU2e(10GbE), OTU3P,
OTU2e(FC200/400), FC1200
Hops 1 - 49 User enters value Hops must match hops defined in
path
Network_ OPT-XX-D-U User can select from drop-
Module OPT-XX-D-UL down list or type in manually
F10-A/T-90-noDT
F10-A/T-90-DT
F10-A/T-90-TN-DT
F10-A/T-90-XX-DT
F10-T-90-noDT
F10-T-90-DT
F10-T-90-TN-DT
F10-T-90-XX-DT
F40-T/M
FC4-T-90-TN-DT
FC4-T-90-noDT
FC4-T-90-DT
FC4-T-90-XX-DT
XR-F10-A/T-90-TN-DT
XR-F10-T-90-TN-DT
LT-EXFP(Quad-10T)
OPT-XX-D-U (FSLM-20)
OPT-XX-D-UL (FSLM-20)
DWDM XFP (FSLM-2)
LT-EXFP (FSLM-2-TN)
RS-F40M (Standard)
RS-F40M (Premium)
eDC40G Metro (O-Shelf)
eDC40G Regional (O-Shelf)
eDC40G (O-Shelf)
eDC40G E-PMD (O-Shelf)
Protection_ OPS PORT PROTECTED, User can select from drop- To be used on routing sheets for
Type 1+1 PORT PROTECTED, 1+1 down list or type in manually protected traffic
CARD PROTECTED, 1+1
CHASSIS PROTECTED

4200 Input Template
Table 4-10. Excel Template Data Ranges for Demand and Routing (Continued)
Column
Name
Path_Type Primary, Secondary User can select from drop- To be used on routing sheets for
down list or type in manually protected traffic. Both rows belonging
to Primary and Secondary paths
shall be one after the other, row for
primary path being first
Specify_Wave_ 16-23, 25-32, 34-41, 43-50, User to enter values in the Optional field; if not filled in by user,
IDs 52-59 format : Wave_id1, Wave_id2, assigned automatically
..., Wave_idN
Node1 A-Z, a-z, 0-9, hyphen and “_” User can select from drop-
Link1 A-Z, a-z, 0-9, hyphen and “_” Auto populated
underscore character

4200 Input Template
Figure 4-16. Sample Input Template, Demand and Routing (4200) Year 1 Unprotected
Figure 4-17. Sample Input Template, Demand and Routing (4200) Year 1 Protected

4200 Input Template

5
Chapter 5:
Create 4200 Network
Overview
This chapter provides information about getting started creating a 4200 network using the
Release 5.2 Ciena Network Designer. The process is outlined with network design guidelines and
then presented in a flow chart highlighting each function through defined steps.
This chapter covers the following sections:
• “Network Design Guidelines” on page 96
• “Create a 4200 Network” on page 96
• “Flow Chart Blocks: Detailed Procedures” on page 99
• “Block A. Add Nodes to Canvas” on page 99
• “Configure Nodes” on page 99
• “Block B. Create and Configure Links” on page 100
• “Autorouting” on page 108
• “Add Protection” on page 110
• “Block C. Create and Configure Lightpath” on page 112
• “Add Channels to Lightpath” on page 115
• “Delete Lightpath” on page 116
• “Add Protection/Diverse Routing to Lightpath” on page 116
• “Force Regen” on page 116
• “Edit/Delete Channels” on page 116
• “View Lightpath” on page 119
• “Create Lightpath with ETR or CLO Channels” on page 120
• “Protection Behaviors” on page 122
• “Block D. Configure 4200 Network Design Options” on page 124
• “Degree View” on page 134
• “Amps/DCMs/OSCs” on page 137
• “DWDM” on page 144
• “Edit Filters” on page 145
• “Split VMUX8 Filters Globally” on page 154
• “Force NE Type” on page 132
• “Force Add/Drop Capacity” on page 133
• “Block E. Run 4200 Chassis and Service Card Configuration” on page 156
• “Configure 4200 Chassis” on page 157
• “Configure Service Cards” on page 159

96 Chapter 5 - Create 4200 Network
Network Design Guidelines
• “Merging OTU1s into a Common M6S Card” on page 168

• “Consolidating Channels on Quad-10T Cards” on page 171
• “Block F. Lock Network Elements” on page 172
• “Block G. Run Reports” on page 175
• “Design Summary” on page 175
• “Generate BOM” on page 180
• “Generate Incremental BOM” on page 181
• “Visio Reports” on page 182

This section describes the general process flow that users should follow to design networks with the
Ciena Network Designer.
The Ciena Network Designer accepts network design information from the Excel Input Template, or
the user can create a network using the drag-and-drop feature on the CND canvas.
Create a 4200 Network

The Excel template, which provides error checking and automatic input of several parameter values,
is the preferred method for network design. Chapter 4, Excel Input Template describes the
necessary steps.
Following is a high-level overview of the steps to design a 4200 network manually, on the CND
canvas.
Step 1: Press the Insert Node icon button and left-click in the canvas to add the desired
number of nodes to the canvas. Press the Insert Node icon button again to stop adding
nodes and disable the button.
Step 2: Draw links by holding down the left mouse button and moving the cursor from the
originating port to the terminating port.
Edit individual links by either double-clicking the desired link in the Network View or
selecting View > Link from the main menu and highlighting the desired link in the drop-
down list. In the Link View window, the user can
• Change fiber type, loss, margin, length, dispersion, dispersion slope, and PMD
coefficient
• Clear West to East and East to West Forced DCM (grey buttons at top of graphic
icon)
- - Insert or delete spans
- - Insert a node
- - Add or remove Fiber OPS protection
• Specify non-linear launch powers for 10G and 40G channels for linear
optimization with or without non-linear validation.
• Force Raman
• Force amp and/or DCM selections
- Convert an amp site to DGE or DGE to amp site
- Force or clear no equipment at amp site

Chapter 5 - Create 4200 Network 97
- Forbid or clear forbid regen at amp/DGE site

Step 3: Create a lightpath by holding the CTRL key, left-clicking on the starting node and left-
double-clicking on the ending node. Select protection if desired. Select the intermediate
nodes using CTRL-left-click. The network must have more than two nodes to configure
a protected lightpath (two links between the same node is not supported).
Step 4: Select Tools > Design CN4200 Network from the main menu. Choose settings from
the following design options in the CN 4200 Network Design Options window, and
perform the network design by clicking OK after selecting the following:
• OADM Settings
• DCM, Amplifier, Raman and OSC Settings
• Force Edits
• Regen Placement Options
• Design Threshold
• 10G Optimization Type
• 40G validation and logging settings
• Advanced Features
• Planned Fiber Capacity
• R5/R6 OAV Channel Output Power Limits
• Globally Place OCM at each node degree
• Globally Forbid Regen on Amp Sites
• PDL Settings
If the design result is not what is desired, then the Design CN4200 Network options should be
modified and the design rerun. Node attributes can be set within the Node view and forced edits to
amps, DCM, and OSC can be performed from the Degree view tabs within the Node view.
Step 5: When a satisfactory design has been achieved, run 4200 Chassis Configuration. Click
the CN4200 Chassis and Service Card Configuration icon or select Reports > 4200
Chassis Configuration from the main menu. The Chassis Group can be edited or left
at the default settings. The Service Card Group should be edited as needed for each
lightpath in the list.
Step 6: Run reports. Select Reports > Generate BOM from the main menu to create an Excel
spreadsheet suitable for entering into the Bid Formatting Tool (BFT). Edit the
spreadsheet (or Bill of Materials, BOM) for any parts to be added or removed specific
to any bids. Remove rows with zero quantities. Import the BOM output into the BFT for
pricing the designed network.
Select Reports > Visio Reports to open a GUI and set up Visio drawings of the entire
network or selected sections.

The flow chart in Figure 5-1 presents the recommended high-level procedures to design a network.
Figure 5-1. Ciena Network Designer Flow Chart (4200)
START
Optionally,
open degree view,
A. Add nodes add DCMs,
to canvas amplifiers, filters,
Fill in Excel rerun Design
input CN4200 network
template
B. Create links E. Run 4200

Chassis Configuration
F. Lock
network elements
C. Create,
configure lightpath
G. Run
reports
Configure Configure
D. Design 4200 service
4200 chassis cards
networks
Run final reports

(BOM, Visio, Rack Views)
Complete link
configuration
END

Flow Chart Blocks: Detailed Procedures

Block A. Add Nodes to Canvas
The CND canvas, with a 4200 network, is shown in Figure 5-2, with the results of Design CN4200
Network runs shown in the message pane. The user creates a network model by adding the desired
number of nodes to the CND canvas.
Note: Alternatively, create the network model by filling in the Excel Input Template. Chapter 4,
Excel Input Template, provides details.
Figure 5-2. Insert Node, Design Summary in Message Area
Set/unset node button Force NE/Clear Force NE toolbar buttons
Configure Nodes
Force NE Type and Clear Force NE Type options are available through the Network View. The user
can select a node or portion of the network and press the appropriate Force NE Type button to force
the NE type of a node or group of nodes. Similarly, the user can select a node or portion of the
network and press the Clear Force NE Type button to clear a forced NE for a node or group of
nodes. The following validations are performed while forcing NE:
• More than degree 2 node can be forced as VMUX provided no degree has a pass-through
connection to more than one other degree. Similarly, nodes with degrees with more than 32

channels or add/drop in more than 4 bands can be forced as VMUX if these degrees are
terminal degrees with no express traffic to other degrees.
• Nodes with add/drop and pass-through connection in more than 4 bands or having more than
32 channels on any of its degrees will be designed as Mixed-ROADM if forced as VMUX.
• Nodes with forced 16/40 channel add/drop capacity on any of its degrees will be designed as
Mix-ROADM if forced as VMUX.
Once a node has been forced to VMUX, the user can place OCM even before the network is defined,
by clicking the Place OCM button in the upper left corner of the Node View for degree 1 and 2 nodes.
If the node is undefined, clicking Place OCM forces the NE type to VMUX. If Remove OCM is clicked
subsequently, OCM is removed but the NE type remains forced to VMUX.
Force edits on nodes are cleared while forcing the NE, as listed below.
• Clear Edit Filter and force Tx amp operations when the NE is changed from VMUX to ROADM/
Mixed-ROADM
• Edit Filter operations are cleared when the NE is changed from Mixed-ROADM to VMUX/
ROADM
• Edit Filter operations are cleared when the add/drop capacity is changed
• Force NE Type and Add/Drop Capacity edits are cleared when a new link is added on a node
Step 1: Select File > New from the main menu or use the shortcut, Ctrl-N (Figure 5-3).
Figure 5-3. Create New File
Step 2: Click the button and click in the canvas to add the desired number of nodes. Name the
nodes by clicking in the name bar and entering the desired name in the highlighted
area. Unclick the node button when finished.
Step 3: To remove a node, highlight it and press the Delete key, or select Edit > Delete from
the main menu.
Block B. Create and Configure Links

Linking the nodes defines their degrees and creates a network. To create and configure links, the
following steps are performed.

Step 1: Left-click the desired port in a node and drag the cursor to the desired terminating port
(Figure 5-4).
Figure 5-4. Create Link
Step 2: Continue linking the nodes (Figure 5-5).
Figure 5-5. Link Nodes
Step 3: Double-click on the desired link in the graphic view. Alternatively, double-click on the
link instance in the Tree View to open a dialog box with a drop-down list containing the
available links (Figure 5-6). Links are named automatically, using the Tx and Rx node
names.
Figure 5-6. Select Link

Step 4: Link parameters can be edited in the tables either by entering data manually or
selecting from a drop-down list (Figure 5-7).
Figure 5-7. Change Link Parameters in Unidentified Network
To modify DCM, Amplifier, Raman, and OSC selections, the network design must have been run at
least once using Tools > Design CN4200 Network. In Figure 5-8, the brown highlights indicate the
forced edits to amps and DCMs on the link.
Figure 5-8. Link View
Forced edits
Step 5: Fiber type, loss, margin, length, dispersion, dispersion slope, PMD coefficient, and 10G
and 40G non-linear launch powers can be modified. Use the drop-down list for Fiber
Type or highlight the current value and enter the desired value. Be sure to set the length
before setting the loss for a span. If this is attempted in reverse order (setting loss first),

CND will calculate a new loss based on length multiplied by the loss coefficient,
changing the loss to a value different than the one specified.
The Reset Fiber Params button in the Link View can be used to reset the dispersion
and slope values of the individual spans to their default values. (See Figure 5-15.)
Changes to link parameters are accommodated, if possible, and the appropriate adjustments are
made to other parameters. Thus when the fiber type is changed, the dispersion and dispersion slope
of the associated span are changed to the default values for that fiber type. Similarly, the non-linear
launch powers for 10G and 40G channels are updated to the default values depending upon the fiber
type. The user can modify these values; however, this is neither recommended, nor typically done,
especially in the case of the default dispersion and dispersion slope values.
Step 6: The user can specify a Raman, OSC, DCM, or Amp for a site by clicking the appropriate
hyperlink and opening the associated dialog window (Figure 5-9 through Figure 5-14).

The options that are available depend on the network design. Refer to “Amps/DCMs/
OSCs” on page 137 for more information.
Figure 5-9. Force Raman Options
Figure 5-10. Force OSC Options (fixed filter networks)
Figure 5-11. Force OSC Options (managed power networks)

In managed power designs, the MAN-0S-CP pad variant can be explicitly forced only when the
RXAmp selection is forced as No Amp. If the forced RXAmp is cleared due to the Clear Forced
Amp design option, the forced OSC is ignored and the OAV or MAN-0S-CP is autoplaced per the
selected amp and OSC design options..
Figure 5-12. Force DCM Options

Figure 5-13. Force Amp Option (fixed filter networks)
Figure 5-14. Force Amp Option (managed power networks)
The following considerations apply when forcing a Raman:

• If No OSC has been applied to the link, the user will not be able to force Raman at any of the
sites in that link and/or at either of the connected nodes/ports. A message will display, “Raman
cannot be forced in this span as No OSC is forced in this link.”
• Raman cannot be forced at any site in the link and/or either of the connected nodes/ports,
unless the Rx amp is either OAV-VS-U-C (R5.0) or OAV-VS-HP (R6.0).
• Raman can only be forced if the facing span loss is up to 35 dB in 100 GHz designs when an
OAV receive amp is used.
• A warning will be raised if a Raman amp is forced on a span having a span loss coefficient of
more than 0.25 dB/km, indicating that Raman performance may not be adequate. Raman
usage is not recommended in this scenario.

The user can specify the limit for the non-linear launch power which will be used when the network
is designed with linear optimization with or without non-linear validation. It can be specified on a per-
span basis and separately for 10G and 40G channels for both East to West and West to East
directions. The range for 10G and 40G channels is -15 dBm to +7 dBm. The default values are
specified in Preferences > Non-Linear Launch Powers.
If the amp site is forced as a No-Equipment site, then the cells cannot be modified, as shown in
Figure 5-15.
Figure 5-15. Link View Details
Reset Fiber Params

button
The user can right-click on the amp site and select Force No Equipment, or click the Force No
Equipment icon button in the menu bar to forbid equipment at all amp sites. If equipment is forced
at the amp site, then CND will inform the user that the Force No Equipment action will clear the
forced edits.
Step 7: Click OK to enable the changes and return to the Link View.
Step 8: To insert or delete individual spans, right-click the desired span in the Link View to open
the pop-up menu and select Insert Span (Figure 5-16).
Figure 5-16. Insert Span Menu

All inserted and deleted spans are applied bi-directionally. When a span is inserted, the loss and
length of the original span are halved to accommodate the new span. An amplifier site is
automatically added to the inserted span (Figure 5-17). The new amplifier site will not be visible on
the drawing canvas unless it contains regens.
When a span is deleted, the loss and length of the deleted span are added to the span that is left,
and an amplifier site is automatically deleted.
Figure 5-17. Inserted Span
Autorouting
The autorouting feature allows the user to
• add nodes,
• convert an amp site to a node,
• convert a 2-degree pass-through node to an amp site, or
• remove a 2-degree pass-through node
without deleting the adjoining links or the lightpaths traversing it, provided the link, amps, DCMs,
associated lightpaths, connected node degree, connected degree amps, or connected degree
DCMs are not locked or Fiber OPS protected.
When an autorouting function is performed, forced edits are maintained from the original link(s), and
the non-linear launch powers for the span are updated. Routing and equipment information is
updated in the GUI. Design Summary reports are updated after Design CN4200 Network is run.
Autorouting is implemented with Convert Amp Site to Node, Convert Node to Amp Site, or
Remove Node in the Network View (Figure 5-18 and Figure 5-19), or Insert Node in the Link View
(Figure 5-20).
Convert Amp Site to Node: Right-click on an amp site in the Link View and select this option. The
amp site will be converted into a two degree node with the same name and the Link View GUIs will
be opened for the two adjacent spans created to allow for further modifications if desired.

Convert Node to Amp Site: Right-click on a 2-degree node with only pass-through channels to open
a pop-up menu. Adjoining links are combined into a single link; force amp/DCM edits are not cleared.
Figure 5-18. Convert Node to Amp Site While Preserving Traffic (Network View)
Remove Node: Right-click on a 2-degree node with only pass-through channels to open a pop-up
menu. Adjoining spans are combined to form a single span if the spans’ parameters are the same;
otherwise; the deleted node is converted into an amp site with “Force No Equipment” set.
Figure 5-19. Remove Node While Preserving Traffic (Network View)
Insert Node: Right-click on a span to open a pop-up menu. The link is split into two links and the span
in which node is inserted is equally divided into the newly formed links. These new links inherit user
forced edits from the original link.
Figure 5-20. Insert Node While Preserving Traffic (Link View)

Add Protection
When Add Protection is selected to implement Fiber OPS, the Link View displays the fiber primary
and secondary links, in different colors (Figure 5-21). In the data grid view, two new tabs are added
for primary and secondary links, where selecting the Primary Link or Secondary Link tab opens
the data grid view for that link.
Figure 5-21. Add Protection
Primary (working)
and secondary
(protection) tabs

The primary and secondary links are independent of each other, so the user can add or delete spans
in either link without affecting the other. In Figure 5-22, an amp site is added only to the secondary
link.
Figure 5-22. Amp Site on Link
The Degree View displays separate views of the hardware placed for the primary and secondary
links. The secondary link hardware block is outlined in a different color than the primary link.
Figure 5-23. Primary and Secondary Links

If the OPS protection is removed, the secondary fiber link is removed from the Link View and the
data grid. The edits in the primary link are retained, however.
OPS protection cannot be added if the link has forced regens. An error message displays with a list
of the lightpaths for which regens have been forced. If one or more lightpaths are traversing an OPS
protected link and continuing to other parts of the network, then regens are forced at both the ends
of the OPS link. Fiber OPS is intended as a point-to-point application, and allowing lightpaths to
optically continue into other parts of the network raises optical concerns that would restrict the
network design and limit its optical viability.
Block C. Create and Configure Lightpath

A lightpath is a collection of data carrying channels that traverse between two end nodes. The
combination of start and end nodes uniquely defines a lightpath. If the start and end nodes are the
same, but the intermediate nodes are different, it is considered a diverse route within the lightpath.
A lightpath can have one or more channels of data carrying traffic, which can be modulated at one
or more data rates (for example, OTU1 and OTU2).
Note: The user can add channels that share the same start and end nodes as an existing
lightpath, but use a different set of intermediate nodes.
Step 1: To configure a lightpath, CTRL+left-click the start node and CTRL+double-left-click the
end node in the Network View to start the Lightpath Wizard.
Step 2: In the Choose Lightpath Type window, select CN4200 Lightpath and click Next
(Figure 5-24).
If a lightpath already exists with those start and end nodes, then it will be shown in the
GUI. If more than one diverse or protected path exists with the same start and end
nodes, all paths will be shown, each in a separate window.
Figure 5-24. Add Lightpath; Select CN4200

Step 3: Select the desired protection type and click Next (Figure 5-25). The network must have
more than two nodes to configure a protected lightpath. Consult “Protection Behaviors”
on page 122 for notes about setting up protection.
Figure 5-25. Add Lightpath: Select Protection
Step 4: To select intermediate nodes of the lightpath, CTRL+left-click on each intermediate

node, and CTRL+double-left-click on the last node. For protected lightpaths, perform
this function on both the primary and secondary paths. No overlapping links are
allowed on the secondary path.
Step 5: For convenience, the user can specify a block of waves to be assigned by using the
drop-down lists and selecting the start and end wave numbers. In addition, the Y1/YN
designation can be assigned by toggling the buttons. Click OK after making the desired
selections. If the block includes a band(s) already assigned, an error message
displays. The channel count is updated as waves are added.
Toggle the button to select the desired year for the lightpath; Y1 or YN and click Next
(Figure 5-26). Y1 represents the initial deployment of services, and YN is the same
network with growth over intervening years. The optical design of the Y1 network
reflects all the equipment required both for Year 1 installation, and also any equipment
(such as amps and filters) necessary for non-service affecting growth to the YN
configuration. The BOM produced for the YN configuration is cumulative, not
incremental, for all equipment added from Y1 to YN.
Step 6: The user can also auto-assign waves by Y1 and YN, by entering the desired quantities
in the fields at the right of the window. CND first scans for forced channels (selected at
the top of the window) and assigns them waves as directed, thus ensuring that the
forced waves have the maximum opportunity to be forced successfully. In the event of
a collision (misallocation by the user, where the same wave id is forced on the same
port for different lightpaths), an error is raised to the GUI and processing stops. After
the forced assignments are completed, the current, automatic wave assignment
algorithm runs, drawing information from the data in the fields as well as the
wavelength band priorities set in Preferences > Design Options (refer to “Design
Options” on page 44).
Note that OTU3P is only supported for managed power designs. Also, there is no
support for auto assigned OTU3P channels - all OTU3P channels must have their
wavelength IDs manually assigned.

Figure 5-26. Specify Lightpath
Step 7: Click Close to exit the wizard without saving, Clear to clear the data and start over,
Save to save the information for the next kernel run, and Next to go to the next window.
Step 8: If no protection or other protection options were chosen, select the desired network-
side cards from the drop-down list and click Next (Figure 5-27). The selections offered
are based on the selections chosen in Preferences > Design Options > Network
Module Preference. (Refer to “Design Options” on page 44.)
Figure 5-27. Add Lightpath; Select Transport Cards

Step 9: If the network module selected was DWDM XFP (FSLM), LT-EXFP (FSLM), OPT-xx-
D-U (FSLM), or OPT-xx-D-UL (FSLM), then choose the cards to be placed at the
starting and ending nodes to model CoreDirector-CoreDirector or CoreDirector-4200
lightpaths as appropriate (Figure 5-28).
Figure 5-28. Add Lightpath; Select Start and End Node Cards
Note that the FSLM can be changed to an F10 card at either the start or end node in the
CN4200 Chassis and Service Card Configuration drop-down list (consult “Configure
Service Cards” on page 159).
Step 10: Click Next.
Step 11: Click Finish to add the lightpath. The finished view is shown in Figure 5-29. The
number of channels and type of transport is shown in the GUI and detailed below.
Figure 5-29. Lightpath Added
Add Channels to Lightpath

Click the button to open a window with protection choices. An information box opens, asking if you
want to use the already-routed secondary lightpath to protect the channels. If No is clicked, a window
opens to choose the secondary path. CTRL+left-click on the intermediate nodes and CTRL+double-
left-click on the last node to define the path. Follow Steps 5 - 11 above to complete the process. The
maximum allowed channels equals the system capacity minus the maximum number of channels on
any intermediate link. The GUI displays the available number of channels. An error message
displays if the user tries to add more channels than are available.

Delete Lightpath
To delete the lightpath, click the Delete Lightpath button. Click Yes in the information box asking
for confirmation to delete this lightpath and all other lightpaths with the same start and end nodes.
Add Protection/Diverse Routing to Lightpath
To add a protected channel or diverse route to an existing lightpath, click the Add Protection/
Diverse Routing to Lightpath button and refer to Step 3 and Figure 5-25 on Page 113.
Force Regen
Click the Force Regen button to open the Force Regen Locations window and check the Status
box to place a regen at an amp site or node (Figure 5-30) for all channels in the lightpath. Once a
forced regen location is specified, the user is responsible for placing sufficient regen to allow the
design to pass. CND will not autoplace any additional regen on a lightpath if one or more regens are
forced. Alternatively, Forbid Regen can be selected to forbid CND from placing regen on the
lightpath. As with Force Regen, CND may not be able to provide a valid design result if regen is
required on the lightpath. Therefore, Forbid Regen does not allow the user to avoid regen; rather, it
is a way for the user to notify CND that it should not continue to design the network if a regen is
required on the selected lightpaths.
Informative error messages are provided by CND if the network cannot be designed successfully
due to Force Regen or Forbid Regen settings.
Figure 5-30. Force Regen
Clear Force Regen

Click the Clear Force Regen button to clear all the forced regens for the lightpath shown in the
Lightpath View GUI. CND will prompt the user to confirm the clear action before proceeding.
Edit/Delete Channels
In the Lightpath View, click the Edit link in the Edit Lightpath column to open the Edit Channel
Properties for Lightpath window (Figure 5-31) for an unlocked lightpath. Alternatively, select Edit
Lightpath from the drop-down list associated with the desired lightpath icon in the Tree View.

If the lightpath is locked, the window opens but only the Year Type field can be altered.
To delete a specific channel, highlight the channel in the tree on the left side of the window and select
Delete Channel. If the channel is protected, a confirmation box opens, and the user can opt to delete
the channel in both the working and protected paths. If Yes is chosen, the protected channel is
converted to an unprotected channel.
To delete channels in bulk, select the branch label in the tree and click Delete Channel(s). If the
lightpath is protected then click Yes to delete all channels in both the primary and secondary paths,
No to delete all channels in the primary path only, or Cancel to quit.
Channels can be modified individually or in bulk by modifying the various property selections and
selecting Apply. Changes are saved each time Apply is clicked, so multiple edits can be performed
in sequence.
Note: Multiple channels can be selected by using <Ctrl> + left-click or <Shift> + left-click on
any tree branches and/or individual channels.
To modify a channel or selection:

• Select the desired service from the drop-down list.
• Select the desired year from the drop-down list.
• Select the desired protection from the drop-down list, noting the following considerations:
Changing protection type does not apply to ETR and CLO channels. If channels are unpro-
tected, the protection type cannot be changed, nor can 1+1 port, 1+1 chassis, or 1+1 card pro-
tection be changed to OPS port protection. Therefore, the user should take care when
modifying the protection type from “OPS Port Protected” or to “Unprotected,” as it cannot be
reversed. The affected channels will have to be deleted and re-added if the user wishes to
restore a prior protection type.
Changing protection type is applied to both the working and protected channels.
• Select the desired network module type from the drop-down list.

Figure 5-31. Edit Channel Properties
• Select from the available wave IDs. Only wave IDs that are available across the entire lightpath
can be selected. Check Auto Assign to have CND auto-assign the wave ID. The user may
select that or any other specific wavelength to assign the wavelength manually, as any auto-
assigned wavelength can potentially be reassigned to another channel during a subsequent
network design run. Similarly, any manually assigned wavelength can be selected as “Auto
Assign” to allow CND to auto-assign during subsequent design runs.
A channel cannot be edited if it is locked or regen locations traversed by the channel are locked.
Click Apply to update the channel plan. This is not Lightpath specific as it updates for the entire
network.
When the wave ID is changed for the primary path of an OPS port protected channel, the wave
ID is also changed on the secondary path (or vice versa). In all other cases, the wave ID is
updated only for the current channel.

If the channel type is changed from a 1+1 port protected OTU1 channel to OTU2, then the
default network module will be LT-EXFP (FSLM-2-TN), as that is the only network module
selection that supports that protection type.
Click Apply after modifying a single wave or a selection. Modifications are only saved when the
Apply button is clicked. If Close is clicked before Apply, then any edits that have not been followed
by clicking Apply are canceled, and the window closes without saving those edits.
All channels within the lightpath can be modified to share a common set of properties by selecting
the root of the GUI's tree view. The selected properties will be those of the prior branch or channel
selected, but these properties can be altered.
Additionally, Force All Manually Assigned Channels to Auto Assigned Channels or Force All
Auto Assigned Channels to Manually Assigned Channels can be applied from the root or branch
of the GUI's tree view by right-clicking either option.
A network design is required after editing channels.
View Lightpath
To view or modify the lightpath, select the view lightpaths icon in the toolbar, or View > Lightpath >
View Lightpath from the main menu to open the View Lightpath window (Figure 5-32).
The following tasks can be carried out from this window:
• Left-click on the hyperlink path name or check View and click Apply to open the Lightpath
View GUI to see the desired lightpath, or click View All and Apply to open separate GUIs for
all lightpaths. For larger networks, the user has the option to filter the search, using the Add
Condition and Find Now buttons. Each time the Add Condition button is clicked, another
qualifying field opens.
• Check or uncheck the Locked box and click Apply to lock/unlock the desired lightpath(s). In
addition, there is a Lock All or Unlock All button (depending on current status) to lock/unlock
all lightpaths. Note that the Lock All or Unlock All button only applies to the lightpaths
currently shown if qualifying conditions are applied.
When locking actions are applied to lightpaths, the path hyperlinks are colored per the color
key shown in the bottom left of the window. A partially locked lightpath occurs when a lightpath
is locked and additional channels are subsequently added and remain unlocked.
• Edit Lightpath allows the channels in the selected lightpath to be edited as described on
Page 116.
• Force Regen allows the user to force or forbid regen on a per lightpath basis as described on
Page 116.

• Delete Lightpaths allows the user to delete the selected lightpath.
Figure 5-32. View Lightpath Window
Create Lightpath with ETR or CLO Channels

Lightpaths using ETR/CLO channels must use fixed OADM and a total lightpath length of no more
than 40 km.
Step 1: To configure the lightpath, CTRL+left-click the start node and CTRL+double-left-click
the end node in the Network View to start the Lightpath Wizard.
Step 2: Click Next in the Create New Lightpath Wizard window.
Step 3: Select 1+1 Card Protection and click Next (Figure 5-33). The network must have
more than two nodes to configure a protected lightpath.
Figure 5-33. 1+1 Card Protected

Step 4: CTRL+left-click on the intermediate nodes and CTRL+double-left-click on the end

node and click Next for both the primary and secondary paths (Figure 5-34 and Figure
5-35).
Figure 5-34. Select Intermediate Nodes, Primary Path
Figure 5-35. Select Intermediate Nodes, Secondary Path
Step 5: Specify waves for the primary and secondary paths in the Specify Waves window (see
Figure 5-26).
Step 6: Select the desired network module from the drop-down list (Figure 5-36).
Figure 5-36. Select Network Modules
Step 7: Click Finish to finish adding the lightpath.

The lightpath is shown in the Lightpath View (Figure 5-37).
Figure 5-37. Completed Lightpath
Protection Behaviors
The user must consider the following points when configuring a protection type.
• 1+1 Port Protection
• Available for OTU1 and OTU1(ISC2/ISC3c) protocols, and OTU2 channels with DWDM
XFP (FSLM-2) and LT-EXFP (FSLM-2-TN) network modules
• Network SFP modules are duplicated for each channel
• Wave IDs/wavelengths of normal and protected channel may be same or different
• Network SFP modules are selected in same service card by default (Port 1 and Port 2 of
parent card) but can be selected in different service cards through Channel Card Port Info
window of Service Card Configuration
• No OPS cards are associated for client interfaces
• 1+1 OPS Port Protection
• Available for all protocols except ETR and CLO
• F10P-A/T or XR-F10P-A/T cards are used for network/line side interfaces for OTU2, OTU2e
(10GbE), and FC1200 protocols
• OPS1/2 cards are calculated on node degree basis and are placed on a node degree that
corresponds to the primary path

• An OPS2 card cannot be shared between two OPS port protected channels whose primary
path corresponds to different node degrees
• Wave IDs/ wavelengths of normal and protected channels have to be the same
• No OPS cards are associated for client interfaces
• 1+1 Card Protection
• Available for all protocols including ETR and CLO
• Service cards are duplicated for each 1+1 card protected channel
• OPS1/2 cards are associated with client interfaces for all protocols except ETR and CLO
• OPS1/2 cards for client interfaces are calculated on node degree basis on the basis of client
SFP/ XFPs selected through Channel Card Port Info window of Service Card
Configuration
• An OPS2 card cannot be shared between two client interfaces belonging to two different
1+1 card protected channels whose primary paths corresponds to different node degrees
• OPS1/2 cards are not calculated if no client SFP/XFPs are selected through Channel Card
Port Info window of Service Card Configuration
• Wave IDs/ wavelengths of normal and protected channel may be the same or different
• Since an ESOM card is configured as an optical child of a parent service card, it optically
subtends the OPS module provided for 1+1 card protection. OPS qualities are not provided
for ESOM client ports, whether directly off the ESOM card or off a port electrically
crossconnected from an EM6 card
• 1+1 Chassis Protection
• Available for all protocols except ETR and CLO
• Service cards are duplicated for each 1+1 chassis protected channel
• Processing engine ensures that cards (including service cards, amplifier cards, MAN-0S-C,
and filter cards) on node degrees corresponding to primary and secondary path of 1+1
chassis protected lightpaths have to be placed in different chassis
• OPS1/2 cards are associated with client interfaces for all protocols
• OPS1/2 cards are calculated on node degree basis on the basis of client SFP/XFPs
selected through Channel Card Port Info window of Service Card Configuration
• An OPS2 card cannot be shared between two client interfaces belonging to two different
1+1 card protected channels whose primary paths correspond to different node degrees
• OPS cards are not calculated if no client SFP/XFPs are selected through Channel Card
Port Info window of Service Card Configuration
• Wave IDs/ wavelengths of normal and protected channel may be the same or different
• Since an ESOM card is configured as an optical child of a parent service card, it optically
subtends the OPS module provided for 1+1 chassis protection. OPS qualities are not
provided for ESOM client ports, whether directly off the ESOM card or off a port electrically
crossconnected from an EM6 card
• Link OPS Protection
• Link based protection scheme applicable to fixed filter designs only
• OPS must be between two nodes with full regeneration
• CND provides separate link properties for the primary and secondary path of a link with
OPS fiber protection. The secondary link is treated as an independent link, so the user can
add or delete spans on the secondary link independently of the primary link. Note that CND
R4.0 had a limitation of considering the fiber characteristics of the primary and secondary

paths to be identical, and did not give the user the ability to specify separate characteristics
for each path.
• OPS1 card is placed on a node degree with OPS protected link
• OPS1 card is calculated on node degree basis rather than node basis. Multiple OPS1 cards
are placed in a node if there are multiple degrees with OPS protected link
Block D. Configure 4200 Network Design Options

After the nodes have been linked, the network can be defined as either 4200 or CoreStream. Before
beginning the design, the user selects View > Network from the main menu.
Step 1: In the main menu, select Tools > Design CN4200 Network (Figure 5-38).
Figure 5-38. Configure 4200 Network
Step 2: In the CN 4200 Network Design Options window, supply the information appropriate
for this network. The options that are available depend on the OADM and Channel Plan
settings, and based on these selections some options will be grayed out.
• OADM Settings: For nodes greater than two degrees, CND will by replace VMUX with Mixed-
ROADM by default. However, a three or four degree node can be forced as VMUX and will
design as VMUX if the node meets the Multi-Degree VMUX criteria of being a combination of
terminal degrees and/or two degree OADMs
CND supports ROADM and Mixed ROADM nodes up to four degrees.
Note the following points for Managed Power nodes:

• Degree 3 or 4 VMUX will upgrade to Mixed-ROADM.

• VMUX Terminal nodes (degree 1) and Mixed-ROADM support add/drop up to 40 channels.

Degree 2 VMUX nodes support up to a maximum of 32 channels with VMUX8, and fewer
with a combination of VMUX4 and VMUX8.
• Tx side DCM is not allowed; Tx amplifier for ROADM and Mixed-ROADM nodes is OAF-BC-
B; OAF-BC-HP amp is available as the transmit amplifier in nodes that require higher output
power as a result of high add/drop channel counts and/or high span loss topographies.
• Amplifier configuration is fixed at ROADM node (but not at line amplifier sites).
To reduce the cost associated with high add/drop channel count ROADM nodes that would normally
require two or more DWR modules for each degree, the user can select a Mixed-ROADM node,
which consists of one DWR module per degree and VMUX modules that can accommodate up to
40 add/drop channels per degree. A Mixed-ROADM node can be configured for nodes of any
degree: 1, 2, 3, or 4. VMUX modules are supported in the RS chassis only.
VMUX nodes can be degree 1 and 2 only, with a maximum of 32 channels dropped at any port (if all
VMUX8s are used). For degree 2 nodes, a maximum of one level of filters (8-channel filters, with
four cascades allowed to get to 32 channels) is allowed per port. For degree 1 nodes, two filter
choices are available either by default in Preferences > VMUX OADM Settings or via manual filter
edit, depending on minimizing filter loss:
• BS5 band splitter with VMUX filters attached to BS5 ports
• Up to four cascades of VMUX4 and VMUX8 filters in one level
The following points apply to VMUX nodes:
• No Tx side DCM is allowed at VMUX nodes
• Amplifier placement rules remain, except R5.0 and above OAVs and MAN-0S-CPs must be
used
• Power conditioning (ripple correction) is allowed at VMUX nodes when MAN-OCM is
manually placed, and pre-emphasis (R6.0) is enabled as a design option
The Use VMUX8 Only option can be selected for managed power designs and does not apply to
fixed filter designs.
• 10G Optimization Type:
• Linear Optimization: Linear optimization is used to find a cost optimal amp and DCM
solution without consideration of non-linear penalties. Note that fiber launch powers are
limited by the entries in Preferences > Non-Linear Launch Powers.
• Linear Optimization with Non-Linear Validation: Linear optimization is run and non-linear
penalties are computed for ripple and dispersion if the non-linear Q value is worse than the
linear Q value. Fiber launch powers are limited by the entries in Preferences > Non-Linear
Launch Powers (refer to “Non-linear Launch Powers” on page 46). The worst-case
computed penalties and non-linear Q, along with design pass/fail for non-linear validation
are reported.
• Non-Linear Optimization (Regional Solution): First, non-linear validation is performed on
all lightpaths. Non-linear penalties are assessed, based on the design created by a linear
optimization run. The default launch powers are initially started at lower channel power
levels but are incremented, as linear OSNR and nonlinear penalties are calculated and all
variables are balanced. The default launch powers considered by amp/DCM placement are
shown below.

Table 5-1. Non-linear Optimization Fiber Launch Powers
Default
Fiber Type Launch
Power (dBm)
NDSF 0
LS -3
oldLS -4
TW+ -1
TWC -2
TWRS -1
LEAF -1
eLEAF -1
DSF -5
Teralight -1
TWReach -1
If non-linear validation passes, results are reported for a design with Current Capacity
selected for Planned Fiber Capacity. For a 10G design with 40 Channels selected for
Planned Fiber Capacity, further checks are run to evaluate how all 40 channels will per-
form if the selected Channel Type is 10G. Every link is checked to ensure that any future
10G wavelength assignment will pass non-linear validation. As a result, CND may place
regens at amp sites if the link cannot be traversed optically by all 40 channels (creating
additional cost when there is no actual failure); however, the user can perform further design
actions, possibly including forced edits, to attempt to minimize cost.
If non-linear validation fails during the non-linear optimization process, the launch powers of
any failed lightpath are increased in steps until they reach a value where the maximum num-
ber of channels is passing, and non-linear validation is run again.
If non-linear validation still does not pass, regens are placed as needed, and the results are
reported as the worst-case penalties and worst-case non-linear Q.
The Non-Linear Validation (NLV) status is reported in the CND message area and in the
Design Summary Report based on whether the NLV is chosen in the design options for 10G
and/or 40G. For more details, refer to Table 7-7.
• 40G Settings
• 40G Non-Linear Validation: This option is selected to perform full 40G non-linear
validation of all 40G lightpaths within the design. Due to the potentially significant run time of
the non-linear analysis, this option can be deselected so that only a linear analysis is
performed on the 40G lightpaths. This allows the user to evaluate signal power levels and
OSNR to ensure they achieve reasonable levels for 40G to be viable. When only the 40G
linear analysis is run, a warning message is generated stating that 40G non-linear validation
must subsequently be run to properly validate the design.
• Generate 40G Non-Linear Log Files: Select this option in order to generate the log data
required for the 40G Non-Linear Report. All 40G design results must be evaluated by
OPNET even if all results are passing, with the 40G Non-Linear Report being required input.
40G design runs can take approximately 25% longer to run when this logging function is
enabled so it is normally left disabled. Once a desired 40G non-linear design result is

achieved, the design should be rerun with this option enabled, with a 40G Non-Linear
Report subsequently generated.
• DCM, Amplifier, Raman and OSC settings: Click the Edit Selection button to open the
settings window (Figure 5-39).
Figure 5-39. Edit DCM, Amplifier, Raman, and OSC
• DCM Settings: Select either Default DCM, Type 0 DCM, or Disable Low Loss DCM. DCM
selection is made based on fiber type at the port. Type 0 is optimized for NDSF, but it can be
used for other fibers, though amp/DCM placement may cause CND to fail the design if it
requires Type 3 DCM due to significant amounts of Leaf, eLeaf, TW Classic, or TW+ fiber.
Disable Low Loss DCM disables low loss type 0 fiber, which is used on longer spans. Refer to
Table A-15 in Appendix A for the list of DCM types for default and type 0 selections. Low loss
DCMs are used for dispersion compensation and DCF loss borrowing, which provides more
margin for higher span losses and potentially avoids the need for regional (high power)
amplifiers and/or Raman.
• Non Linear Dispersion Map Optimization: Select Unchirped Transceivers (Extended
Reach 10G) to implement the non-linear dispersion map optimal for the 10G XR-F10-F10-A/T
or the LT-EXFP used on both the Quad-10T and FSLM-2. The non-linear dispersion map is a
link-based dispersion map, where the residual dispersion is brought to near 0 ps/nm on link
basis.
Select Chirped Transceivers (Standard 10G) to implement the non-linear dispersion map
optimal for standard 10G chirped transceivers such as the existing F10-A, F10-T, FC4-T, or

FSLM-2 (with DWDM-XFP) modules. These transponders perform better with positive residual
dispersion. The non-linear dispersion map is a link-based dispersion map, where the residual
dispersion is under-compensated by about 300 ps/nm for every 1000km of dispersion
compensation at the mean wavelength.
The 10G unchirped non-linear dispersion maps can be detrimental to use of 10G chirped trans-
ceivers as they prefer a positive residual dispersion. CND will validate both unchirped and
chirped transceivers as appropriate with the use of any of the non-linear dispersion maps so
the use of any non-linear dispersion map with any transceiver is potentially viable and is purely
based on successful design results.
• Raman Settings: Check the Allow Raman box. Enter the margin for which Raman should be
placed in the associated Raman Threshold field. Raman amplifiers are placed at the output of
the fiber span, before the Rx (EDFA) amplifier. The Raman amplifier couples 14xx nm light into
the fiber plant, thereby providing gain to the signal in the fiber. The amount of fiber gain that can
be obtained from the Raman amplifier depends on the fiber type and the fiber loss.
• Fixed Filter Networks Preferred Amplifiers: For the Rx and Tx Amplifier sections, check the
preferred amplifier choices. The OAV-VS-HP and OAF-BC-HP are high-powered amplifiers
more ideal for regional networks with high loss spans. CND will cost optimize based on the
selected amplifier preferences, so selecting an amplifier does not mean that it will be placed in
the design unless it is the only Rx or Tx amplifier choice.
The following points apply for fixed filter networks.

• Default amplifier selections are shown in Table 5-2.
• The user can enable multiple amplifier selections at a time.
• The user is allowed to choose between OAV-0S-U-C or OAV-VS-U-C and OAV-VS-HP
combinations for a fixed filter network. The OSC signaling format is different for the OAV-0S-
U-C versus the OAV-VS-U-C and OAV-VS-HP and is therefore a mutually exclusive choice.
• OAF-00-1 can be selected with any combination, as it does not contain OSC functionality.
• Raman can be enabled only with OAV-VS-U-C or OAV-VS-HP amplifiers.
• Raman requires the OAV-VS-U-C or OAV-VS-HP and is not an option if the OAV-0S-U-C is
selected.
• When a high power amplifier (-HP option) is selected on the Rx side, it is also selected on
the Tx side (and vice versa).
• When a high power amplifier is deselected in the Rx side, it is also disabled in the Tx side
(and vice versa).
• Auto Place MAN-0S-C is disabled by default.
The following points apply for managed power networks.
• Default amplifier selections are shown in Table 5-2.
• The user is allowed to select one or both of the OAV-VS-U-C and OAV-VS-HP in the Rx
direction. It is recommended to select both amps, as CND will make the most cost-efficient
choice
• Raman is disabled as a default setting.
• In the Tx direction on an OLA or VMUX node, the user can select from OAF-00-1 or OAF-
BC-B. It is recommended to leave both selected and allow CND to cost optimize.
• There should be at least one box checked in both Rx and Tx directions at all times.
• If high power is selected in one direction/option (Rx or Tx), it is automatically selected in the
other direction.
• If high power is deselected in one direction/option, it is disabled in all directions/options.

Table 5-2 lists the amplifiers for the preferred amplifier selections.
Table 5-2. Preferred Amplifier Selections
R5.0/6.0 Network OLA R5.0/6.0 ROADM/

Direction Fixed Filter Nodes R5.0/6.0 VMUX Nodes Mixed-ROADM Nodes
Rx OAF-00-1-C OAV-VS-U-C OAV-VS-U-C OAV-VS-U-CP (R5.0)
OAV-0S-U-C OAV-VS-HP OAV-VS-HP OAV-VS-U-CP-2 (R8.0)
OAV-VS-U-C (R5.0) OAV-VS-U-CP-2 (R8.0) OAV-VS-U-CP-2 (R8.0) OAV-VS-U-CP-4 (R8.0)
OAV-VS-HP (R6.0) OAV-VS-U-CP-4 (R8.0) OAV-VS-U-CP-4 (R8.0) OAV-VS-U-CP-8 (R8.0)
OAV-VS-U-CP-8 (R8.0) OAV-VS-U-CP-8 (R8.0) OAV-VS-HP (R6.0)
OAV-VS-HP-2 (R8.0) OAV-VS-HP-2 (R8.0) OAV-VS-HP-2 (R8.0)
Tx OAF-00-1-C OAF-BC-B (R5.0) OAF-BC-B (R5.0) OAF-BC-B (R5.0)

OAF-BC-HP (R6.0) OAF-00-1-C OAF-00-1-C OAF-BC-HP (R6.0)
OAF-BC-HP (R6.0) OAF-BC-HP (R6.0)
• OSC Settings: Check Auto Place Man-0S-C to ensure OSC is present at all degrees of all
nodes for fixed filter designs. This tends to result in OAV being placed as the receive OA on all
spans, because the OAV contains OSC functionality. Receive OAF may offer a more optimal
design, so this option can be left unchecked and Place MAN-0S-CP on Link (from the Link
View) can be used to ensure OSC communications to amp sites and nodes where the user
cannot rely on in-band communications. For ROADM/Mixed ROADM/VMUX nodes, select the
applicable MAN-OS-CP (R5.0), MAN-OS-CP-2 (R8.0), MAN-OS-CP-4 (R8.0), and/or MAN-
OS-CP-8 (R8.0).
• Advanced Features: Check the box next to the desired feature. These options are for regional
systems where non-linear optimization is required.
• Pre-Emphasis (R6.0): Select for designs containing 100 GHz VMUX, ROADM, and Mixed-
ROADM nodes to limit the growth of system gain ripple, thus improving performance without
additional cost (potentially avoiding regens). Pre-emphasis does not correct ripple at amp
sites, only sites containing add/drop. OCM must be added manually to VMUX nodes for
channels added/dropped at a VMUX node to benefit from pre-emphasis. Pre-Emphasis
must be checked if one or more 40G channels are present in the network.
• OAV Mid-Stage Loss Borrowing: Can provide up to 9 dB of additional gain for an
OAV-VS-U-C or OAV-VS-HP, up to 6 dB for an OAV-15, and up to 7 dB for an OAV-22 by
reducing attenuation at mid-stage, thus potentially avoiding need for Raman and high-
powered amps, improving performance at no additional cost. Option is available only if
OAV-VS-U-C (R5.0) or OAV-VS-HP (R6.0) is selected as the Rx amp option.
• Optimize Non-Linear Dispersion Map: Select for a link-based placement of DCMs, which
can force link residual dispersion to be close to zero, thus increasing transmission distance
by reducing non-linear effects. Additionally, it is beneficial to zero compensate links when
the network is intended to support unknown any to any traffic in the future so that these
unknown lightpaths will not accumulate significant dispersion as they traverse the network.
For total link dispersion < 500ps/nm, dispersion is pre-compensated at the start of the link
and reduced toward zero at the end of the link.

For NDSF fiber, residual dispersion is pre-compensated to -500ps/nm at the beginning of the
link, and allowed to recover to 0ps/nm at the end of the link.
For NZDSF fiber, links may be broken into sub-links of 1200ps/nm total dispersion. Residual
dispersion is then pre-compensated to -600ps/nm at the beginning of the sub-link, and
allowed to recover to 0ps/nm at the end.
The user must consider the following points when using the non-linear dispersion map.
• The non-linear dispersion map option will place the optimal DCM to achieve the desired
dispersion compensation result. Thus larger DCMs are placed than would be by the
standard DCM placement algorithm. Since larger DCM has more insertion loss, this
option can limit the amount of mid-stage loss available for borrowing, which may require
more amplifiers or even regen within a design. If the non-linear dispersion map is not
required for 40G readiness, an alternative is to manually force larger DCM values on an
as-needed basis to help pass non-linear validation.
• The non-linear dispersion map zero compensates on a link basis. For it to be optimal, all
amp sites should be modeled as amp sites within a multi-span link. The non-linear
dispersion map result will not be optimal if an amp site is modeled as a node, and no
add/drop traffic is intended there.
• DCM is generally detrimental to 40G and will typically result in additional penalty against
40G lightpaths. If a network contains 10G and 40G, it can be better to avoid placing
more DCM into the network design by implementing an non-linear dispersion map.
• PMD Margin: This option is checked by default and computes the PMD for the lightpaths
under consideration. CND will always perform PMD analysis and provide calculated PMD
on a per lightpath basis in the Lightpaths tab of the Design Summary Report. This option
ensures an appropriate amount of margin to accommodate PMD penalty for all line rates
and enforce upper limits for PMD. PMD Margin should always remain selected to ensure
that the design properly tolerates the calculated levels of PMD, but can be deselected for
backward compatibility so that deployed designs failing PMD margin analysis can
temporarily be allowed to pass so that reports can be generated if needed prior to
addressing the PMD concern.
Chirped transponders (for example, F10-A, F10-T, FC4-T) have a maximum PMD tolerance
of 17 ps and unchirped transponders (XR-F10-A, XR-F10-T, LT-EXFP/Quad-10T) have a
maximum PMD tolerance of almost 24 ps. OTU1 tolerance of PMD is much higher, about
four times that of 10G rates. However, a PMD penalty must be accommodated by the
design at PMD levels well below the upper bound. Regeneration will be placed if sufficient
OSNR margin is not available for the PMD penalty.
• Regen Placement Options: Select either OSNR Based or Distance Based.
• OSNR Based: This selection is default for all designs created in CND. It will place regens
where needed, for optimal bidirectional OSNR. OSNR Based regen placement is
recommended for new designs, as it can result in faster run time and fewer regen
placements.
• Distance Based (Pre-CND 4.1 design compatibility): This option is selected by default
when importing design files from earlier version of CND. Select Distance Based regen
placement for networks designed in previous versions of CND (prior to R4.1) to achieve the
same design result, especially when working with deployed networks. In some cases, the
Distance Based regen placement option can run faster and/or provide fewer regens, though
this is not a commonly expected result.

• Design Threshold: Select Budgetary, Deployment, or Mean Deployment. Use Budgetary if

the design is intended only for RFX response, or if the customer has already provided
excessive additional margins in the loss budget. Use Mean Deployment for a network
intended for deployment. Mean Deployment provides a statistical approach to estimate
insertion losses based on filter measurements (mean and standard deviation). Use
Deployment for networks that require backward compatibility with CND R3.0 designs.
• Checking the Force Edits: Clear Forced Edits options clears all manual node and link related
edits. If the Force Edits check box is selected, the Clear Forced Edits hyperlink can then be
used to select specific types of edits to clear (Figure 5-40). Note that clearing forced edits will
not clear any locked components in the network.
Figure 5-40. Clear Forced Edits
• Planned Fiber Capacity: Select either Current Capacity or 40 Channels.

• Current Capacity: This option is the only option for fixed OADM networks, and is available
as an option for VMUX/ROADM/Mixed-ROADM managed power networks. If the Y1+YN
channel count on a given span is fewer than 40 channels, selecting this will potentially
enable higher channel powers, up to the per fiber type set in Non-Linear Launch Powers
in the Preferences menu or per span in the Link View GUI. This may allow the design to
have lower amp and DCM costs, and potentially reduce or avoid regen placement. When
non-linear analysis is performed, it will only consider the configured Y1+YN channels.
• 40 Channels: This option is only available for managed power networks and can be
selected to ensure that amplifier channel output power levels are set to allow 40 channels
through the amplifier while observing the total output power limits of the amplifier.
The Channel Type option allows the user to select 10G or 40G to indicate if the unspecified
growth channels will be 10G or 40G as these channel types can have different launch
power limits, which can affect the maximum channel output power levels allowed for 10G
and 40G.
It is very important to note that this option only affects amplifier channel output power. It in
no way guarantees that the design will continue to pass if unspecified 10G or 40G
wavelengths are added. 10G wavelength interfere with 40G, so unspecified growth can

result in larger penalty to 40G channels, which can potentially require further design actions,
such as lower 10G and/or 40G launch powers or changes to amplifiers.
• R5/R6 OAV Channel Output Power Limits

• Warn: This is the default selection that will continue to provide the same warning
mechanism implemented in prior releases of CND. This option is beneficial if the network is
being deployed in 4200 software release 7.2 or above as it allows CND to design the
network without observing a output channel power limit. The subsequent warning provides
the maximum channel output power each amp must observe as it is variable per amplifier
instance. The given limits can then be manually verified against the "P/Ch Avg" values for
amplifier output in the Power Levels sheet of the Design Summary Report, and the network
can be deployed as designed if the warning levels are observed. If not observed, further
design action is required.
• Enforce Pre-R7.2 Limits: This selection enables CND to automatically design to the +2.3
dBm/ch output channel power limit of the R5 OAV-VS-U-C and the +5.3 dBm/ch output
channel power limit of the R6 OAV-VS-HP. This option should commonly be selected for any
network deployed with 4200 software release 7.1 or earlier and avoids the need for
complicated workarounds to observe the limits.
• Global Design Options
• Globally Place OCM at Each Node Degree: Some customers require full equipment
redundancy in conjunction with protected traffic demands so this option will globally place a
separate OCM for each node degree when selected. It is disabled by default.
• Globally Forbid Regen on Amp Sites: Select this option to forbid regen placement at any
amp site within the design. This option has been moved to the Design Options GUI as it was
located in the Preferences GUI in CND 4.1.
• PDL Settings: This option is specific to 40G analysis and is set to "Per Lightpath System PDL"
by default. The "Force System PDL" allows the user to force a generic value between 0 and 10
dB for all 40G lightpaths but should only be used when given specific guidance to do so.
Step 3: Click OK to design the network or Cancel to quit.
Force NE Type
From the Node Properties tab in the Node View, the user can force the NE type as shown in Figure
5-41. In addition, the user can force the NE type by selecting a node or nodes in the Network View
and clicking the desired Force NE Type icon on the toolbar, or by selecting the node in the Tree View
and right-clicking to select from the pop-up menu.
Figure 5-41. Force NE Type Options

The following validations are performed when forcing the NE type:

• Multi-degree VMUX can only apply to nodes that have no more than one express path from any
one degree to another. That is, a node with more than two degrees can be forced as VMUX
provided none of the degrees have pass-through connections to more than one degree. For
example, if a three degree node with one OADM degree pair and one terminal degree is forced
as VMUX, then CND can design the node as multi-degree VMUX. Similarly, if a four degree
node is forced as VMUX as follows: two OADM degree pairs, one OADM degree pair and two
terminal degrees, or four terminal degrees, then CND will honor the forcing operation and
design the node as multi-degree VMUX.
• Nodes with add/drop and pass-through channels in more than four bands or having more than
32 channels on any non-terminal degrees (this express traffic) will be designed as Mixed-
ROADM if forced as VMUX
• Nodes with a forced 16 or 40 Channel Add/Drop Capacity setting will still be designed as Mix-
ROADM if forced as VMUX
Degree three and degree four non-fixed filter nodes can be forced as VMUX nodes. CND will honor
the force NE operation by allowing a combination of OADM pairs and terminal degrees. Forcing NE
on degree three and degree four non-fixed filter nodes is only allowed if no degree has a
passthrough connection to more than one degree. Also forcing NE as VMUX is not allowed if the
total number of add/drop and pass-through channels on a node degree are more than 32 or are in
more than four bands. Also if the force add/drop capacity is 16/40 channel then force NE type as
VMUX is not allowed.
Forced edits on nodes are cleared while forcing the NE as listed below:
• Clear Edit Filter and force Tx amp operations when the NE is changed from VMUX to ROADM/
Mixed-ROADM
• Edit Filter operations are cleared when the NE is changed from Mixed-ROADM to VMUX/
ROADM
• Edit Filter operations are cleared when the add/drop capacity is changed
• Force NE Type and add/drop capacity edits are cleared when a new link is added to a node
Force Add/Drop Capacity
The user can force the add/drop capacity on 100 GHz VMUX, ROADM, and Mixed-ROADM nodes
as shown in Figure 5-42. When 16 or 40 Channel Add/Drop is selected, CND will design the node
with a filter structure that will support any 16 channels or all 40 channels on all degrees of the node.
As a result, a degree 2 VMUX node will be converted to Mixed-ROADM if the user selects the 16-
or 40-channel option. When selected at the node level, this option supersedes the default global
value in the Preferences > Add/Drop Capacity tab.
Figure 5-42. Force Add/Drop Capacity

Degree View
Ciena Network Designer completely automates the placement of DCMs, amplifiers, and filters. To
configure any of these elements manually, the user can use the Degree View. Note that equivalent
amplifier and DCM forcing options are also available from the Link View.
Step 1: Double-click the desired port in the Node View to open the Degree window (Figure 5-
43 and Figure 5-44). Click the associated tab to view Node Properties or the desired
node degree. Use the scroll bar to view the DWDM group at the bottom of the Degree
window.

Figure 5-43. Degree View, Top

Figure 5-44. Degree View, Bottom
The yellow symbol in the upper left of each section of the Degree View indicates the
availability and status of the associated group (Figure 5-45).
Figure 5-45. Expanded View
= populated, unexpanded section
= expanded section

Amps/DCMs/OSCs
Step 2: Right click the Auto Place Raman icon to add or delete a Raman amp (Figure 5-46).
Figure 5-46. Raman Options
Step 3: Right click the amplifier icon to open the Force Amp Options window, and select the
desired amplifier (Figure 5-48). The available choices for Tx and Rx amplifiers are
dependent on the options selected in the Network Design Options window (“Block D.
Configure 4200 Network Design Options” on page 124). Converting an OAF amp to an
OAV moves the DCMs that were with the OAF to mid-stage. The OSC should toggle
from the respective OAV-0S-C (or OAV-VS-C if applicable) to MAN-0S-C or MAN-0S-
CP, depending on OADM and amplifier settings.
Table 5-3 lists the options for forcing amplifiers at Nodes/Regen Sites/DGE Sites, and Table 5-4 lists
the options for forcing amplifiers at Amp sites.

.
Table 5-3. Options for Forcing Amplifiers at Nodes/Regen Sites/DGE Sites
OADM Type RX Amp TX Amp

Fixed Filter No Amp No Amp
OAF-00-1-C OAF-00-1-C
OAV-0S-U-C OAF-BC-B
OAV-VS-U-C (R5.0) OAF-BC-HP (R6.0)
OAV-VS-HP (R6.0)
VMUX No Amp No Amp

OAV-VS-U-CP (R5.0) OAF-BC-B (R5.0)
OAV-VS-U-CP-2 (R8.0) OAF-00-1-C
OAV-VS-U-CP-4 (R8.0) OAF-BC-HP (R6.0)
OAV-VS-HP (R6.0)
OAV-VS-HP-2 (R8.0)
OAV-VS-HP-4 (R8.0)
OAV-VS-HP-8 (R8.0)
ROADM No Amp OAF-BC-B (R5.0)

OAV-VS-U-CP (R5.0) OAF-BC-HP (R6.0)
OAV-VS-HP (R6.0)
OAV-VS-HP-2 (R8.0)
OAV-VS-HP-4 (R8.0)
OAV-VS-HP-8 (R8.0)
Mixed ROADM No Amp OAF-BC-B (R5.0)

OAV-VS-U-CP (R5.0) OAF-BC-HP (R6.0)
OAV-VS-HP (R6.0)
OAV-VS-HP-2 (R8.0)
OAV-VS-HP-4 (R8.0)
OAV-VS-HP-8 (R8.0)

.
Table 5-4. Options for Forcing Amplifiers at Amp Sites
RX Amp TX Amp
Amp Sites in No Amp No Amp
Fixed Filter OAF-00-1-C OAF-00-1-C
Designs OAV-0S-U-C OAF-BC-HP (R6.0)
OAV-VS-U-C (R5.0)
OAV-VS-HP (R6.0)
Amp Sites in No Amp No Amp

VMUX/ OAV-VS-U-CP (R5.0) OAF-BC-B (R5.0)
ROADM/Mixed OAV-VS-U-CP-2 (R8.0) OAF-00-1-C
ROADM Designs OAV-VS-U-CP-4 (R8.0) OAF-BC-HP (R6.0)
OAV-VS-HP (R6.0)
OAV-VS-HP-2 (R8.0)
OAV-VS-HP-4 (R8.0)
OAV-VS-HP-8 (R8.0)
In a fixed filter network, if the user attempts to force an OAV-0S-U-C at any degree and
an OAV-VS-U-C or OAV-VS-HP has already been forced in at least one other degree
in the network, the following error message is shown. A similar message displays if an
attempt is made to force an OAV-VS-U-C or OAV-VS-HP and an OAV-0S-U-C has
already been placed.
Figure 5-47. Force AMP Warning

Figure 5-48. Amplifier Options
Step 4: Right-click the DCM icon to open the Force DCM Options window, and select the
desired DCM type (Figure 5-49). Depending on the selection, another section opens
at the bottom of the window to select the DCM Size for the type chosen. Consider the
following points when adding DCMs:
For fixed filter designs
• DCM can be placed at the input of a transmit OAF
• DCM can be placed at the mid-stage of a receive OAV
• DCM can be placed at the input of a receive OAF
• For VMUX/ROADM/Mixed-ROADM designs, DCM is always placed on the mid-
stage of the Rx OAV.
Figure 5-49. DCM Options

Step 5: Click OK to add the DCM or Cancel to quit.

Step 6: For fixed OADM networks, right-click the Auto Place OSC icon to open the Force OSC
Options window (Figure 5-50). Select Place MAN-0S-C on Link to place MAN-0S-C
at the selected degree, the connected degree at the facing node, and both degrees of
all amp sites in between. Remove MAN-0S-C on Link removes the MAN-0S-C from
the selected degree, the connected degree on the facing node, and both degrees of all
amp sites in between.
A link containing Raman must have an OSC. If the user attempts to force No OSC on the link, an
error message displays.
Figure 5-50. OSC Options

Figure 5-51 shows a degree for a node with amplifiers, DCMs, and OSCs added.
Figure 5-51. Amplifiers, DCMs, and OSCs Added

If a link on the node is Fiber OPS protected, then the OPS card is also shown in the Degree View.
As of CND 4.1, the primary and secondary (OPS) paths are independent of each other, the Degree
View displays the actual hardware placed corresponding to the primary and secondary links, as
shown in Figure 5-52. The protected link is outlined in pink.
Figure 5-52. Fiber OPS Protection

DWDM
Step 7: The DWDM Level 1 and Level 2 filter icons are shown in Figure 5-53. If a node has two
or more degrees and lightpaths are specified that pass through the node as express
traffic, the channel type and the links that they pass through are shown.
Figure 5-53. DWDM: Add Level 1, Level 2 Filter
Figure 5-54. DWDM: Channels

Edit Filters
The edit filter option can be applied to fixed filters, VMUX, and Mixed-ROADM designs, and is
available only after a kernel run. The user clicks Edit Filter in the DWDM window (Figure 5-55) and
selects from Reorder filters, Split a filter, Combine two filters, Use 5 band filter, or Change
VMUX Terminal (VMUX only). The Edit Filter view opens in a new window for ease of viewing. Edit
filter changes will not persist if lightpath changes are made subsequently. The color of the edited
filters will change in the GUI.
Figure 5-55. Edit Filter
When a node is forced as VMUX a pop-up message is displayed (Figure 5-56), and depending upon
the number of terminal degrees present in the node either a concatenated terminal or BS-5 terminal
can be forced. Any pass-through pairs will be converted to OADM pairs.
Figure 5-56. VMUX Terminal Options
The default option will be taken from the preferences. If the terminal node degree has add/drop in
more than 32 channels or more than 4 bands then even though user forces it as concatenated
VMUX, CND will design it as a BS-5 terminal.
If a lightpath passing through a forced VMUX node is added/deleted/edited, then the forced node
operation is cleared. Also if a link is added/deleted from a forced VMUX node then the force node
operation is cleared.
Locking Considerations:
Adding a link to locked VMUX node is allowed. The Force NE type operation is allowed on locked
nodes only if the existing NE type and force NE type is same. While adding a lightpath through a
locked VMUX node validation will be done such that the locked VMUX configuration of the node does
not change. An error message is displayed if the lightpath is not allowed.

After an Edit Filter operation has been completed, the user can click the Revert Current Changes
button to ignore all changes made in the current GUI session. This action is equivalent to exiting
without saving changes. To undo all forced edits at the degree and allow the kernel subsequently to
auto-place filters, the user can click Clear All Edit Filter Operations (Figure 5-57). This action is
equivalent to a Clear Forced Edits function local to the filter edits at a given degree. Note that the
filter structures displayed in the GUI will not update until after the kernel run.
Figure 5-57. Edit Filter Options
Reorder Filters
Step 1: Select Reorder filters to perform a simple swap of pairs (Figure 5-58). Look for filter
pairs connected from the express port of the parent filter to the network (common) port
of the child; that is, filters on the same level (all L1 or all L2) with a parent-child
relationship. If two filters are on the same level (L1 or L2) and have a parent-child
relationship, and if the child filter has an express port, then parent and child can be
switched. Applying Edit Filter will clear any Force Add/Drop Capacity options. In
addition, changes do not persist if the user makes lightpath changes. The user can
revert current changes or clear the Edit Filter operations if desired.
Reorder filters must follow the rules below for fixed filters.
• Neighboring CN-BS2-AB and CN-BS1-D are the only filters that can be switched.
• The original child filter inherits the input connectivity of the original parent filter.
• The express port of the original child filter is set to “in use” since it is now a parent filter.
• The original parent filter inherits the express connectivity of the original child filter.
• The input connectivity of the original parent filter is set to the original child filter, since the parent
and child have switched places.
Reorder filters follows the rules below for Mixed-ROADM.
• Only two VMUX filters may be reordered in a single step.
• A cascade of up to two VMUX8 filters is allowed in the add direction, while only one VMUX8 is
allowed in the drop direction.

• From a drop side point of view, pairs of VMUX4 in the same band can be substituted for the
VMUX8 module.
Figure 5-58. Reorder Filters
Split a filter
Step 1: Select Split a filter to split filters and place them on the same level as the original filter.
Highlight the desired filter combination to split (Figure 5-59).
Split a filter must follow the rules below for fixed filters.
• 8-channel filters can be split into a pair of 4-channel filters following these rules:
• CN-100-x80 -> CN-100-x4H + CN-100-x4L where x is the Band A through E.
• CN-100-x4H has the same level (L1 or L2) and input connectivity as the original
CN-100-x80. The express port is used (for the x4L filter).
• CN-100-x4L has the CN-100-x4H as the parent filter, and the same level as the original
filter. The express port is not used.
• Multiband filters can be split into lower order band filters following these rules. All replacement
filters are on the same level as the original filter.
• The first filter has the input connectivity of the original filter. The express port is used (for the
second filter).
• The second filter has the same first filter as the parent.

• When the 2-band filters are split into a pair of single band filters, the express port status of
the second filter is inherited from the original 2-band filter.
• The express port is not used when the 3-band filter is split.
• There is no express port assigned when the 5-band filter is split.
• Band drop for each filter is inherited from the original filter, whether there is a child filter or
some form of Band Pass-through (BPT). Similarly, any filter that refers to the original filter as
its parent needs to have its parent status updated appropriately.
• Following are the required options:
- CN-BS2-AB -> CN-BS1-A + CN-BS1-B
- CN-BS2-CD -> CN-BS1-C + CN-BS1-D
- CN-BS3-ABE -> CN-BS2-AB + CN-BS1-E (User can split the BS2-AB filter in a
subsequent step, if desired)
- CN-BS5 -> CN-BS2-CD + CN-BS3-ABE (User can split the 2- and 3-band filters in a
subsequent step, if desired)
Split a filter must follow the rule below for Mixed-ROADM.
• VMUX8 filters are split into two VMUX4 filters. After the operation, the filter remains the same
as the parent filter. New filters are the same level (L2) as the original filter. A YN VMUX4 filter
(created by splitting) will be placed after the Y1 VMUX4 filter so that it does not have to be
populated at Y1. The channel population for each VMUX4 follows from the channel population
of the original VMUX8.

Figure 5-59. Split Filters (Fixed Filter)

Step 2: Click the Apply button (which gets focus when a combination is highlighted). The filters
are split and displayed in the GUI. VMUX8 filters can also be split globally by clicking
the icon button in the menu bar (consult “Split VMUX8 Filters Globally” on page 154).
Combine two filters
Step 1: Select Combine two filters. The choices are displayed in the side window (Figure 5-
60). The filters to be combined should all be on the same level (L1 or L2) and have a
strict parent-child relationship without an intervening filter in the sequence. Combine
two filters must follow the rules below for fixed filters:
• A pair of adjacent 4-channel filters can be combined into an 8-channel filter by following these
rules:
• If two filters x4L and x4H exist at the same level (L1 or L2) with a parent-child relationship,
and if the child filter’s express port is NOT in use, then the two filters may be replaced with
an x80 filter.
• Channel status (add/drop/CPT) of the x80 filter is inherited from channel use of the original
4-channel filters.
• The input for the x80 filter (parent filter data or top level L1 filter) should be inherited from
the parent 4-channel filter.
• Two single-band filters can be combined into a 2-channel filter by following the rules below. If a
pair of eligible single-band filters exists at the same level (L1 or L2) with a parent-child
relationship, then the two filters may be replaced with a 2-band filter (CN-BS1-A + CN-BS1-B -
> CN-BS2-AB or CN-BS1-C + CN-BS1-D -> CN-BS2-CD).
• Band add/drop (or BPT) for the drop ports of the 2-band filter is inherited from the
appropriate single band filter. Similarly, any child filters will have their parent filter updated.
• The input for the BS2 filter (parent filter data or top level L1 filter) is inherited from the parent
single-band filter.
• The express port use for the BS2 filter is inherited from the child BS1 filter.
• A pair of 2-band filters can be combined into a 5-band filter (no express). A pair of 2-band filters
and the E band filter can be combined into a 5-band filter (no express). If a pair of 2-band filters
exists at the same level with a parent-child relationship, and if the express port of the child filter
is not in use, then the two filters may be replaced with a 5-band filter (CN-BS2-AB + CN-BS2-
CD -> CN-BS5 or CN-BS2-AB + CN-BS2-CD + CN-BS1-E -> CN-BS5).
• Band add/drop/BPT for the drop ports of the 5-band filter are inherited from the 2-band
filters. Similarly, any child filters will have their parent filter updated.
• The input for the BS5 filter will be inherited from the input for the parent filter being replaced.
• A pair of 4-channel filters in which the child filter express port is used can be combined into a
band filter and an 8-channel filter. If two filters x4L and x4H exist at L1 with a parent-child
relationship, and the child filter’s express port IS in use, then the two filters may be replaced by
a CN-BS1-x band filter with a child CN-100-x80 8-channel filter.
• Channel add/drop/CPT for the x80 filter will be inherited from the appropriate 4-channel
filter.
• The band filter input is inherited from the parent 4-channel filter.
• The band filter express is inherited from the child 4-channel filter express.
• The band filter will be placed at L1 and the 8-channel filter at L2.
• A single 4-channel filter (no express use) can be replaced with an 8-channel filter. If a 4-
channel filter x4L or x4H does NOT have its express port in use, then the filter may be replaced
with an x80 filter. This is more of an “expand” than a “combine” operation.

• Channel status (add/drop/CPT) of the x80 filter will be inherited from channel use of the
original 4-channel filter.
• The input for the x80 filter (parent filter data or top level L1 filter) will be inherited from the 4-
channel filter.
• One 4-channel filter in which the express port is used can be combined into a band filter and an
8-channel filter. If a filter x4L or x4H exists at L1, and the child filter’s express port IS in use,
then the filter may be replaced by a CN-BS1-x band filter with a child CN-100-x80 8-channel
filter.
• Channel add/drop/CPT for the x80 filter will be inherited from the 4-channel filter.
• The band filter input will be inherited from the 4-channel filter.
• The band filter express will be inherited from the 4-channel filter.
• The band filter will be placed at L1 and the 8-channel filter at L2.
Step 2: Highlight the desired combination and click Apply. The new filter is displayed in the
GUI.
Combine two filters must follow the rules below for Mixed-ROADM.
• The operation is allowed on the same level of filters.
• If two filters x4L and x4H exist at the same level with a parent-child relationship, then the two
filters can be replaced with an x80 filter provided they are in the same band. If the various
VMUX4 filters are all in different bands, then the VMUX4s cannot be combined into VMUX8s.

• A VMUX4 filter can be converted to an VMUX8 filter if that is the only filter subtended from a
DWR port. If two VMUX4 filters are subtended from a DWR port, neither can be converted,
unless they are in the same band.
Figure 5-60. Combine Two Filters (Fixed Filter)

Use 5-band filter

Step 1: Select Use 5-band filter (Figure 5-61).
Figure 5-61. Use 5-band Filter (Fixed Filter)

Split VMUX8 Filters Globally

In VMUX and Mixed-ROADM designs, the user can choose to split all VMUX8 filters into VMUX4
pairs by clicking the Split VMUX8 button on the menu bar (Figure 5-62). This operation is applied
across the entire network.
The maximum limit of VMUX filters in a filter chain on the drop side is four for a VMUX node port,
and two for a Mixed-ROADM node port.
Figure 5-62. Force VMUX8 Filter Split
Step 2: Select Change VMUX Terminal Configuration (Figure 5-63). This option is available
for VMUX only. The configuration can be changed from a BS5 VMUX terminal to a
concatenated VMUX terminal, and vice-versa. No option is provided if the user selects

this option to change the configuration from VMUX BS5 terminal to concatenated
VMUX terminal if the channels cover more than four bands.
Figure 5-63. Change VMUX Terminal Configuration

Figure 5-64. VMUX Terminal Change
Block E. Run 4200 Chassis and Service Card Configuration

The 4200 Chassis and Service Card Configuration GUI allows the user to perform post-
processing on the optical design to configure chassis options and service card options such as
modifying SFPs and XFPs and adding child cards to model electrical cross-connect relationships
between service cards. The user must finish configuring the network by specifying the chassis and
service card parameters before the BOM can be generated and subsequently loaded into the Bid
Formatting Tool (BFT) to create a quote with pricing.

Step 1: Click the CN4200 Chassis and Service Card icon in the toolbar (Figure 5-65).
Alternatively, from the main menu, select Reports > 4200 Chassis Configuration.
Figure 5-65. 4200 Chassis Configuration Icon
Step 2: Follow the steps in the next two sections,”Configure 4200 Chassis” and “Configure
Service Cards”, to finalize the network design for report creation. The user can accept
the default configuration for the chassis but the service cards and associated SFP/
XFPs must be defined for each node in the network.
Configure 4200 Chassis
Click the Edit button to bring the window into focus, and click on the Chassis Group tab (Figure 5-
66) to specify the desired chassis type.
Step 1: Select a device from the drop-down Select Network/Node/Amp list.
Step 2: Select the chassis style: Optimized, RS Only (nodes only), Classic Only, or Micro
Only.
Note: For 4200 networks using R5.0/R6.0 amps, amp sites cannot have two Micro or Classic
chassis unless an RS chassis is included.
Step 3: Select filter card placement:

• 4200 Managed: Filters are always placed within the 4200 Micro, Classic, or RS
chassis.
• 2150 Unmanaged: Filters will be placed in the 4200 Micro, Classic, or RS chassis
if there is room for them, but in a 2150 chassis otherwise.
• 2150 Only: Filters are only placed in a 2150 chassis, and never in the 4200
chassis.
Step 4: Select chassis size for Micro, Classic, or RS.
Step 5: Select power units for Micro and Classic.
Step 6: Select the alarm card for Micro and Classic chassis.
Step 7: Select miscellaneous equipment for Micro and Classic.
Step 8: Select exhaust ducts/power entry.
Note that the number of feeds on a PDU-NG1 cannot be upgraded in the field, so the
3-feed version of the PDU-NG1 is provided in the BOM, regardless of the number of
RS chassis in any given rack. This is done to protect against unplanned future growth.
Step 9: Select the appropriate version of 4200 software from the drop-down list.
Step 10: Select the demand setting: Y1 or Y1+YN.
Step 11: Check Maintain Slot Assignments to preserve chassis slot locations for existing
cards. This check box option applies to the selection shown in the adjacent Select

Network/Node/Amp list and can be applied to "All Nodes" or one or more individual
nodes. The Edit and Save buttons for the Chassis Group options are not used for
implementing the Maintain Slot Assignments selections.
The following rules apply to the Maintain Slot Assignments setting:
(a) The Maintain Slot Assignment setting is disabled for a node when:
• OADM setting changes from 100GHz Managed design to/from Fixed Filter
• OADM setting changes from 100GHz Managed design to/from 50GHz
• OADM setting changes from Fixed Filter to/from 50GHz design
• Filter Placement Option Changes from UnManaged to Managed
• Filter Placement Option Changes from 2150 Only to UnManaged
• Filter Placement Option Changes from 2150 Only to Managed
(b) The Maintain Slot Assignment setting is disabled for specific chassis due to
changes to the Chassis Style option. For example, changing from Optimized to RS
Only will keep the setting on existing RS chassis.
(c) When Maintain Slot Assignment is selected, cards are populated into designated
chassis/slot depending on the following criteria:
• If a card was previously present, then the card's slot position is unchanged
• If a previously present card type was changed, then the card gets populated into
its previous slot/new slot based on matching criterion
• Previously present card was deleted, then the corresponding slot position is
available for the new cards, if any, to occupy
• If a card is newly placed, then the card gets populated in the first available slot
(d) While populating the cards into the chassis, cards and the slot positions are
matched at different levels to place the same/relevant card into a slot. The following is
an example for different levels of matching a filter card to a slot:
• A filter card is populated in a slot if that slot was previously occupied by the same
filter card name from the same degree
• If the above is not possible, then a filter card is populated in a slot previously
occupied by a different filter card name from the same degree
• If the above two criteria cannot be met then a filter card is populated in a slot
previously occupied by a different filter card name from a different degree
• If none of the above criteria can be met then the filter card is populated in any slot
in any chassis
Step 12: Click Save or Cancel in the upper right side of the window. If Save And Exit is clicked,
the window will close.

Note that the user can also click the Service Card Group tab and move to that window without
saving or canceling the edits in the Chassis Group window. Upon attempting to save the edits in
the Service Card Group window, the user will be prompted to either save or cancel the edits in the
Chassis Group.
Figure 5-66. Chassis Configuration
Configure Service Cards

Step 1: Click the Service Card Group tab to display information about the service card group
and configure service cards and SFPs/XFPs.

Step 2: Highlight the desired node in the List Of Nodes and List of Lightpaths (to display
channels in a specific lightpath) panes (Figure 5-67, Figure 5-68).
Figure 5-67. Service Card Group (left side)
Figure 5-68. Service Card Group (right side)
Step 3: Click in the Node A Card column to select the cards available for the channel type if
modifications are desired (Figure 5-69).
Figure 5-69. Select Card Type
Step 4: Double-left-click Click Here in the Channel Card column to open the Channel Card
and Port Info GUI for the selected channel (Figure 5-70). This GUI allows the user to
configure network- and client-side ports for both the A and B endpoint nodes.

A list of SFPs or XFPs available for the card type can be selected from the drop-down list for each
port in the window that opens. The ports displayed in gray are cards within the lightpath that are
available to form cross-connect relationships.
Figure 5-70. Select SFP/XFP
Step 5: If desired, select a child card (a service card with no network-side ports that
electrically cross-connects traffic onto a parent card; that is, a child M6 off a parent
F10-A). Click Add in the Add Child Card column to open a drop-down list of cards to
add (Figure 5-71). The child card will be displayed beneath the original card in the
window (Figure 5-72).

Figure 5-71. Add Child Card
Figure 5-72. Child Card Added
The 4200 backplane allows for parent/child cross-connect relationships within a 4-slot group.
Therefore, a parent card can have a maximum of three child cards. Certain restrictions apply for
some cards, however:
• G10/G10X service cards are allowed as child card options off M3/M6, EM6, F10-A cards.
• G10/G10x service cards are not allowed as parent cards for any service cards.
• G6S service cards are allowed as child card options off the F10-A card if the lightpath length is
less than 100km.
• G6S service cards are allowed as parent or child card options for an OTU1 channel if the
lightpath length is less than 100km.
• G6S service cards have a limitation on ISC protocols of 100km or less.
• When an ESOM (ESOM/ESOM-IP) is added as a child card, a new window opens
(Figure 5-75) so the user can create a patch cord connection with the parent card. From the
drop-down lists, select the card and port that will connect with Port3 of the ESOM that is being
added as the child card. Click OK. The cards and SFP pairs valid for creating a patch cord
connectivity are shown in Table 5-5 on page 5-166, and a completed view with ESOM added as
a child card is shown in Figure 5-78 on page 5-167.

An ESOM card can use an EM6 card for additional client port aggregation via electrical backplane
connection. This is modeled either by adding a child EM6 card to a parent ESOM card, or by forming
a card group between an ESOM card and an existing EM6 card, and is limited by what is shared on
a common lightpath.
Following are substeps and options for creating/deleting card groups between an ESOM and/or
existing EM6 cards:
Creating a card group
• In the Channel Card and Port Info window, use CTRL + left-click to select a row with an EM6
and another row of a module with which the EM6 can make a card group, and click the Create
Group with ESOM or EM6 button to link the modules (Figure 5-73). (The Create Group with
ESOM or EM6 button is valid for EM6 and ESOM modules only. To support this grouping, an
ESOM interop license will be listed in the BOM.)
Creating a card group models an electrical backplane connection between the cards, and they
must be located in the same RS chassis quadrant or CL chassis. Once a card group is formed,
the cards in that group have the same GroupID value (other than “-1”), as shown in
Figure 5-74.
Figure 5-73. Create Card Group (Share Group ID - Left Side)

Figure 5-74. Create Card Group (Share Group ID - Right Side)
Card group shares GroupID
Deleting a card group

• Select a row in the data grid that is an ESOM or EM6 and click the Remove ESOM/EM6 from
Group button to free it from the previously associated card group. Be careful not to delete a
parent ESOM, which can orphan the former child EM6, leaving it unassociated with any other
service card for cross connect modeling.
Licensing Services on an EM6-Base card
• To support interoperability between an EM6-Base and the ESOM (ESOM or ESOM-IP), an
EM6-ESOM Interop License is required. The EM6-ESOM Interop License is required for an
EM6-Base module only when the EM6-Base is added as a child card to an ESOM, or a card
group is created between that EM6-Base and the ESOM using the Create Group with ESOM
or EM6 button.
• An LIC-VIDEO is provided in the BOM if an ELT-VID SFP is selected on an EM6-Base card.
• An LIC-SONET-SDH is provided in the BOM if the SDH License box is manually checked for an
EM6-Base in the Channel Card and Port Info GUI. This license is required in order to support
SONET/SDH services on the EM6-Base card.
• An LIC-GDPS is provided in the BOM when an EM6-Base card contains one or more OPT-ISC
SFPs in support of OTU1(ISC2/ISC3c) based client services.
Figure 5-75. Set Up Patch Cord Connectivity

To configure the optical or electrical port connectivity, the SFPs at the connecting ports of the cards
must be compatible. The SFPs that are displayed reflect the choices made in the default SFP
window in Preferences, and may not be compatible for this operation.
Clicking OK (if the SFPs are not compatible) opens an error message window (Figure 5-76).
Figure 5-76. Incompatible SFPs
Click OK to close the window and return to the Select Child Card window. Select matching SFPs
from the drop-down lists and click OK to implement the change and close the window.
The ESOM Connection Dialog window (Figure 5-77) is opened if the user attempts to change the
SFP on network Port 3 of the ESOM or on the associated port on the parent service card. Click
Validate SFP to confirm the compatibility of the change. An error message displays if the user tries
to place an incompatible SFP; otherwise, the change is accepted. Click Match SFP at Parent Card
to keep the new SFP in Port 3 of the ESOM and place a matching SFP in the parent card. Click
Accept SFP and Delete ESOM to place the desired SFP on the parent card and delete the ESOM,
or click Cancel to maintain the original selection of SFPs. Note that the Accept SFP and Delete
ESOM button has focus only if the user has tried to change the client SFP on the parent service card;
it is grayed out otherwise.
Figure 5-77. ESOM Connection Dialog

Table 5-5. Valid Modules and SFPs

ESOM
Module ESOM
(IP)
EM6-Base OPT-SX <--> OPT-SX
M6-GEFC-F OPT-SXET <--> OPT-SXET
G10 OPT-SX <--> OPT-SXET
M3S
OPT-SR-1 <--> OPT-SR-1
EM6-Flex
OPT-SR-1 <--> OPT-IR-1
F10-A OPT-SR-1 <--> OPT-12IR
F10-PA OPT-SR-1 <--> OPT-LX
M6S-F OPT-SR-1 <--> OPT-LX1G
OPT-IR-1 <--> OPT-IR-1
OPT-IR-1 <--> OPT-12IR
OPT-IR-1 <--> OPT-LX
OPT-IR-1 <--> OPT-LX1G
OPT-12IR <--> OPT-12IR
OPT-12IR <--> OPT-LX
OPT-12IR <--> OPT-LX1G
OPT-LX <--> OPT-LX
OPT-LX <--> OPT-LX1G
OPT-LX1G <--> OPT-LX1G
OPT-ZXET <--> OPT-ZXET

OPT-ZXET <--> OPT-nn
OPT-ZXET <--> OPT-nn-U
OPT-nn <--> OPT-nn
OPT-nn <--> OPT-nn-U
OPT-nn-U <--> OPT-nn-U
ELT-BT <--> ELT-BT

M6S-TDM-F No OPT-SR-1 <--> OPT-SR-1
OPT-SR-1 <--> OPT-IR-1
OPT-SR-1 <--> OPT-12IR
OPT-IR-1 <--> OPT-IR-1
OPT-IR-1 <--> OPT-12IR
OPT-12IR <--> OPT-12IR
M6-ESCON-F No No
G6S No No

Figure 5-78. ESOM Added as Child Card
Step 6: Configure each port as desired for each node. After specifying values for a node, click
Save to return to the Service Card Group window.
Step 7: Repeat Step 2 through Step 6 as needed for each channel in the network.
Step 8: When all nodes have been configured, click Save and Exit, to cause CND to calculate
the BOM for the network. This allows the user to generate BOM and Visio reports such
as the BOM report shown in Figure 5-79.
Note that clicking Save and Exit opens the Node Controller Warning window if there is no
controller card in slot MAIN of a Micro or Classic chassis (refer to Step 9 on Page 192).
Note: Recalculating the BOM will overwrite any manual chassis slot assignment edits
performed from the Rack View Interface GUI.
Each part in the network design is listed by its tool identifier, P-code, and Agile description. The
amount of a given part is totaled both by node and by network.
The BOM report can be edited as desired and imported into the Bid Formatting Tool (BFT) for pricing
the designed network.

While it is highly desirable to configure the transponder cards and all SFPs and XFPs to get an
accurate BOM, the tool will still generate a BOM and other reports even without that step. This can
be useful for a quick, optics-only quote, or one that will be edited manually later.
Figure 5-79. Design Configuration
Merging OTU1s into a Common M6S Card

CND allows the user to consolidate one or more OTU1s within the same lightpath onto a common
M6 card rather than using the default of one M6 card per OTU1 service. The client SFPs can also
be configured on the common M6.
Step 1: Select CN4200 Chassis and Service Card Configuration (Figure 5-80).
Figure 5-80. Design and Configuration Icons
CN4200 Chassis
and Service Card
Configuration

Step 2: On the Service Card Group tab, choose Not Selected from the drop-down list for the
OTU1 service to be shared onto a common M6 card (Figure 5-81).
Figure 5-81. Choose Not Selected
Step 3: Click Yes in the Service Card Configuration warning box.

Step 4: In the Channel Card column, select Click Here, then Config for the same OTU1
service.
Step 5: In the Channel Card and Port Info window that opens, select the desired DWDM SFP
to populate on an open port on the M6 card for Node A. Note that the corresponding
port for Node B does not populate; select the desired DWDM SFP for that port also.

Client SFPs may also be configured at this time. Click Save when finished (Figure 5-
82).
Figure 5-82. Select SFPs
Step 6: On the Service Card Group, click Save and Exit.

Step 7: Run a Visio report (see “Visio Reports” on page 182) to see the OTU1s on a common
M6 card (Figure 5-84).
Figure 5-84. Visio: OTU1s Shared on a Common M6 Card

Consolidating Channels on Quad-10T Cards

Ciena recommends the default placement of channels on Quad-10T cards by CND, which are
ordered by Y1/YN, degree, and ascending wavelength ID.
However, the user can reorder channels manually by following these steps.
Step 1: In the CN4200 Chassis and Service Card Configuration window, open the drop-
down list of a “Not-Selected” Node A or Node B card and select Quad-10T.
Step 2: Click Yes in the Service Card Configuration warning window.
Step 3: Click Config in the Channel Card column to open the Channel Card and Port Info
window.
Step 4: Size the window vertically to see the added card.
Step 5: Click an open odd port and select the network XFP (LT-EXFP for the Quad-10T). The
next even port will be populated with the client XFP (Figure 5-85). This XFP can be
changed using the drop-down list; changes are propagated to the new port.
Figure 5-85. Order of Channels in Channel Card and Port Info Window
Step 6: Click Save and apply the changes and close the window, or Cancel to close without
saving.
The Channel Card and Port Info window can be opened for other channels so they can be moved to
open port pairs. Any Quad-10T cards with all ports vacated will be removed, and any open ports on
used Quad-10Ts will be populated by any subsequently added channels. This also applies when
reopening the CN4200 Chassis and Service Card Configuration window, as any existing
placement due to manual edits is maintained, while any channel additions fill any open ports first,
before adding more Quad-10T cards.

Step 7: Click Save and Exit to close the CN4200 Chassis and Service Card Configuration
window, or Exit to close without saving.
Note that reopening the CN4200 Chassis and Service Card Configuration window displays a
confirmation window. The message in Figure 5-86 is displayed if there are edits to the Quad-10T
port assignments. Click Yes to open and preserve the manual changes to the port pair placement,
or No to allow CND to reconsolidate the Quad-10T port assignments per its year/degree/wavelength
ID ordering scheme. Note that all changes to the client XFP type are maintained regardless of
response, as this confirmation relates only to port assignment edits. The dialog box show in Figure
5-87 is shown if there are edited Quad-10T port assignments and Maintain Slot Assignment is set
for at least the A or Z node of one or more Quad-10T cards within the design.
Figure 5-86. Quad-10T Port Assignment Confirmation
Figure 5-87. Quad-10T Port Assignment Confirmation
Block F. Lock Network Elements

CND provides the ability to create and save incremental designs without changing already deployed
field configurations. In one tier, the user can lock an entire network design. In a second tier, the user
can lock nodes, links, and lightpaths. Thus, the user can freeze an iteration of a design and then add
to it without changing the original, or the user can do a kernel run and no physical alterations will be
made to the locked portion of the design by the optimization function of the CND.
Note: The following points apply when locking/unlocking.

• Nodes: A node degree cannot be locked or unlocked separately. When a node is
(un)locked, all the currently connected degrees are (un)locked as well.
• Links: Amp sites cannot be locked or unlocked separately. When a link is (un)locked,
all the amp sites in that link are (un)locked.
• Lightpaths: Channels cannot be locked or unlocked separately. When a lightpath is
(un)locked, all the channels in that lightpath are (un)locked.

To design a network incrementally and save each iteration, the entire network, a link, or a network
subset of the lightpaths, amps, or DCMs can be locked by right-clicking in the GUI window to open
the pop-up menu (Figure 5-88), by clicking Locking > Lock (or Unlock) in the main menu, or by
clicking the appropriate icon in the menu bar.
Figure 5-88. Lock Network from Pop-up Menu
Performing a locking action on the entire network opens a confirmation window (Figure 5-89).
Figure 5-89. Network Locking Confirmation Window
Click OK to open the Windows Save As menu. If the <givenName>.xml already exists in the
directory, when Save is pressed in the Save As window, a prompt appears to overwrite the existing
file, and if the user agrees, the <givenName>.xml is overwritten and the <givenName_baseline>.xml
(the original file) is saved as read-only. In the instance of multiple network locking operations on the
same design, read-only copies are saved with sequential numbers appended to the design file name
(Figure 5-90).
Figure 5-90. Save Locked File

The BASELINE file is read-only. If opened, the network is displayed locked, and all other views are
locked and grayed out (Figure 5-91).
Figure 5-91. Read-only BASELINE File
If the network, link, or lightpaths, or amps or DCMs subset is unlocked, it cannot be locked if the
node/link name and/or node NE type is modified, new links are added to the node, span parameter
is changed, channels are added to any one of the lightpaths terminated on the node, or any force
operation is performed in any of the links connected to the node. After a successful kernel run has
been done, the network, nodes, links, lightpaths, or any subset can be locked.
The user can also select a part of a network and lock/unlock that selection only by pressing SHIFT
+ left-click to select the desired nodes and links. The user can then lock or unlock the selection, using
either the icon option, the main menu option, or the right-click option.
Nodes can also be locked/unlocked in the Lightpath View, using either the icon option, the main
menu option, or the right-click option.
In the Node View, the user can lock/unlock the entire node, node amps, and/or node DCMs using
either the icon option, the main menu option, or the right-click option. The appearance of the Node
View changes based on the selection. The change is reflected in the Network View.
In the Link View, the user can lock/unlock the entire link, link amps, and/or link DCMs using either
the icon option, the main menu option, or the right-click option. The appearance of the Link View
changes based on the selection. The change is reflected in the Network View.
Locking/unlocking actions can also be performed on the network, or on nodes, links, or lightpaths;
either in bulk or individually from the Tree View.

Block G. Run Reports

The Ciena Network Designer enables Excel and Visio reports. Two Excel report styles are available:
Generate BOM provides Bill of Materials (BOM) information about the network design, and Design
Summary provides technical information about network design.
Three Visio report styles are available: Visio Network View provides network-level Visio drawings
of the network design, Visio Node View provides drawings of the intra-node connections and fiber
diagrams for the facing links, and Visio Rack View provides Visio drawings of all the chassis along
with the various cards at a specific node.
Design Summary
The Design Summary menu option to allows the user to create an Excel report summarizing the
network. Click the icon in the toolbar shown below, or from the main menu, select Reports > Design
Summary (Figure 5-92).
Toolbar icon
Main menu choice
If Fiber OPS links are part of the network, secondary links are reported separately in the Design
Summary. Since the hardware on primary and secondary links can differ, the network summary
sheet incorporates the actual hardware on these links. The secondary link is reported separately in
the Links, Lightpath, Pads, and Power Levels sheets. Any error messages pertaining to the
secondary link are reported in the Design Constraints and the Network Summary sheets.

The tool creates an Excel summary report broken out by network summary, nodes, links, and
lightpaths. Locked entities are colored yellow. Figure 5-93 gives an example of the network
summary. Specific information is broken out as shown in Figure 5-94 through Figure 5-99.
Figure 5-93. Design Summary, Network

Figure 5-94. Design Summary, Nodes

*“Pass-through Definitions” on page 320 provides definitions of pass-through types.
Figure 5-95. Design Summary, Links
Figure 5-96. Design Summary, Lightpath

Figure 5-97. Design Summary, Pads
Figure 5-98. Design Summary, Power Levels
Figure 5-99. Design Summary, Design Constraints

Generate BOM
The generated BOM report contains all hardware required for the network design, along with the
corresponding quantities at each node and at each amp site in the network. Before the BOM can be
generated, the 4200 Chassis and Service Card Configuration must be completed. If the
configuration has not been done, then the window will open when Generate BOM is selected from
the Reports menu. When the configuration is saved, the BOM is generated and opened as an Excel
file (Figure 5-101). Click the Generate BOM Report icon in the toolbar to generate the report (Figure
5-100). Depending upon the user selection for Y1 or Y1+YN, the name of the BOM report will be
appended by Y1 or Y1+YN.
Figure 5-100. BOM Icon
Figure 5-101. BOM

Generate Incremental BOM

The incremental BOM generates two reports, so the user can compare a baseline network with the
changes in a later version. Select Reports > Incremental BOM from the main menu, or click the
icon in the menu bar. Both Design CN4200 Network and CN4200 Chassis and Service
Card Configuration must be run before an incremental BOM can be generated.
In the information window that opens (Figure 5-102), select which file will be design #1 in the BOM
and which will be design #2. The files can be either.xml or.xls. Browse for the desired files, or choose
from the files currently open in CND. If Choose from Open files is checked, select the desired file
from a drop-down list. Finally, check Open in CND to open a file selected by way of browsing.
Note that 4200 and CoreStream design files cannot be mixed. Also, for designs with Fiber OPS
protection, incremental BOMs are not generated if one design is from CND R4.1+ and the other is
from CND R4.0.
Figure 5-102. Incremental BOM Setup
Click OK to create the Excel file (Figure 5-103). The Excel file contains the BOM for the original
(<filename>.baseline), the modified, and the incremental report. The incremental BOM displays the
difference in hardware between the original file (baseline) and the modified file selected by the user.
Thus, if a cell displays a zero for a piece of hardware, there is no change between the original and

the modified files, and no new equipment of that type is needed for the modified design. If a cell
displays a “2,” then 2 more pieces of that type of hardware are needed to support the modified
design. A “-2” indicates that two fewer pieces are needed.
Figure 5-103. Incremental BOM
Visio Reports
The Visio Reports feature generates a Visual Basic script (.bas) that contains all information
required to build a schematic drawing of the network design. The NE schematics are generated and
viewed in Visio, and can be used for design planning and informational purposes.

Note: The Visio software is a third-party drawing tool that is not supplied with the Ciena
Network Design Tool but must be installed to use this feature. Verify that a current
version of Visio is installed. CND Release 5.2 supports Visio 2003 and later. Also, this
feature assumes a working knowledge of the Visio software application.
For more information about or instructions on using Visio, refer to the Visio Standard
Edition User Guide, typically supplied with the Visio software package.
Before attempting to write a Visio file, run Tools > Design CN4200 Network. To write the file, the
following steps are performed.
For Visio 2003, follow Step 1 through Step 6 and continue with Step 12. For Visio 2007, follow
Step 7 through Step 11 and continue with Step 12.
Step 1: Verify that a current version of Visio is installed. CND Release 5.2 supports Visio 2003
and later.
Step 2: For the first use of Visio with CND, open the Visio application.
Step 3: From the main menu, select Tools > Macro > Security to open the Security dialog
box (Figure 5-104).
Step 4: Under the Security Level tab, select Medium.
Figure 5-104. Set Security Level

Step 5: Under the Trusted Publishers tab, select Trust Access to Visual Basic Project
(Figure 5-105).
Figure 5-105. Set Trusted Publishers
Step 6: Click OK and skip to Step 12.

Step 7: From the main menu of Visio 2007, select Tools > Trust Center to open the Trust
Center GUI.

Step 8: Check Trust access to the VBA project object model under Developer Macro
Settings, as shown in Figure 5-106.
Figure 5-106. Trust Center Macro Settings

Step 9: Select 'Trusted Locations' then Add new location..., as shown in Figure 5-107.
Figure 5-107. Add New Location

Step 10: Browse to C:\Program Files\Ciena Corporation, check Subfolders of this location are
also trusted and click OK, as shown in Figure 5-108.
Figure 5-108. Add New Location
This will enable all current and future installations of CND as they are subfolders of this path.

Step 11: Click OK on the 'Trust Center' window to close, as shown in Figure 5-109.
Figure 5-109. Visio Configuration Complete
Step 12: Select Report > Visio Reports to open the Visio Reports dialog box (Figure 5-110).
Alternatively, click the Generate Visio Report icon in the toolbar.
Step 13: Select Generate Complete or Generate Partial Visio Report as desired. A complete
Visio report contains the Network View diagram, Node View diagrams for all the nodes
in the network including regen sites and amp sites, the Power Levels sheets for all node
and amp sites, and the Rack View diagrams for all the nodes in the network including
regen sites and amp sites. If a partial report is chosen, the rest of the window gains
focus.
Generate Partial Visio Report
Step 1: If Generate Partial Visio Report is desired, then check the associated box.
Step 2: If desired, select the Node View Diagram tab. Links are displayed if an amp site was
configured.

Step 3: Highlight the nodes and amp sites to be drawn or click Select All for each as desired.
The Power Levels sheets are also generated for every node or amp site selected.
Figure 5-110. Visio Reports, Node View Diagram
Step 4: Click the Rack View Diagram tab (Figure 5-111). The Rack View also lists amp sites.

Step 5: Highlight the nodes to be drawn in the Rack View or click Select All.
Figure 5-111. Visio Reports, Rack View Diagram
Step 6: For individual nodes, click Configure to perform modifications to the card and chassis
configuration.
Note: All changes performed through the Rack View Interface and Swap Card Interface GUIs
will be lost if the BOM is subsequently regenerated by selecting Save and Exit in the
Chassis and Service Card Configuration GUI. The user must ensure all changes are
complete in the Chassis and Service Card Configuration GUI prior to making changes
within the Rack View Interface.
Step 7: In the Rack View Interface window that opens (Figure 5-112), click on a card to open
the Swap Card Interface GUI, which allows the user to swap the current chassis/slot
location with any other valid chassis/slot location. Note that slots represented with
green text links indicate that Maintain Slot Assignment is set for that chassis. CND will
maintain the slot assignments but the user can still perform manual swaps. The rack
display is dependent on the types of chassis selected (MC, CL, RS, CN2150, and
CN2110). The rack diagram shows the front views for all types of chassis that are
populated with cards. Cards can be moved within the same chassis and among various
chassis according to slot engineering rules and power consumption limits.

The user can view the power consumption of an individual chassis in every rack/bay. The Rack View
Interface is updated to show the RS chassis total power consumption and power consumption on a
half-chassis basis, with separate values for slots 2-9 and 10-17. In addition, the power supplies can
be swapped (according to power consumption requirements). If an inappropriate power supply is
selected, an error message displays.
Alarm cards and other common equipment that does not affect optical design validation can be
modified.
Refer to the tables in Appendix A, Product Reference Tables, for the rules applied by CND to create
the Visio drawings and populate the cards into chassis at each node and/or site.
Figure 5-112. Configure Rack View
Step 8: If desired, click Add Rack/Chassis (Figure 5-113).

a. Highlight the desired chassis in the drop-down list and click Add New Chassis.
b. Click OK in the Chassis Added message window.
Figure 5-113. Add Rack/Chassis

Step 9: Click Finish Add Chassis to add the chassis and return to the Rack View Interface.
The added chassis is displayed, with unfilled slots. Once Save Configuration is
clicked, the new configuration will be saved into the XML file.
If slot MAIN of the Micro and/or Classic chassis has a full blank card (i.e., no card available to serve
as node controller), then a warning message displays after Save Configuration is clicked. The
warning message contains the rack name, chassis name and chassis number as shown in Figure
5-114. All chassis without a node controller in slot MAIN are listed. Clicking OK returns the user to
the main Visio Reports window. Clicking Cancel gives the user the option of filling the empty slot
MAIN.
Figure 5-114. Added Chassis, Blank Slot MAIN
Step 10: To delete a chassis or rack, click Delete Rack/Chassis. Only empty chassis or racks
can be deleted. If the object is populated, an error message displays.
Step 11: If desired, click on a card in a slot to display the relevant information in the Swap Card
Interface window (Figure 5-115).
Step 12: To swap a card, select the rack and chassis from the drop-down lists, which display all
chassis in the selected rack that can accept the selected card. The available full-slot
and half-slot counts are shown after the chassis type, separated by a /. For example,

in Figure 5-115, chassis 100 is an RSFull17 chassis with five available full slots and no
available half-slots.
Figure 5-115. View Info on Selected Cards
A single service or filter card or card group may be swapped within one chassis or between chassis,
subject to existing slot engineering and power consumption rules. Card movement is allowed for
DCM modules in the CN 2110 chassis.
Step 13: Click the desired chassis slot (other than ALM and PSU for Classic and Micro chassis)
to open the Swap Card Interface window. One slot and card are displayed if the
selected slot contains a card that is not a member of a card group or does not occupy
more than one slot. If the card is a member of a group, all cards are shown. The
selected card is displayed in red.
Step 14: Click Save and Exit to save and return to the Rack View Interface or Cancel to return
to the previous screen with no changes. The Save and Exit button does not gain focus
until all cards in a selected group are swapped.
Note: The power supply of a Micro or Classic chassis cannot be changed from an AC-600 or
DC-600 if that chassis contains at least one CN ESOM.
If an ESOM is being moved to a Micro or Classic chassis and the PSM of that chassis is
not 600 watts, that card movement will be allowed, and the PSM value of that Micro
chassis will be changed to AC- or DC-600, as appropriate.
A Micro or Classic chassis with an ESOM must have a high-flow fan for sufficient
cooling, which requires a 600-watt power supply. If the node/network level Micro or
Classic chassis PSM option chosen is NOT already higher than AC- or DC-600, CND
will automatically place an AC- or DC-600 PSM.

Note: Refer to Appendix A for a list of cards and associated slots by chassis type.
Step 15: When the configuration for a given node is satisfactory, click Save Configuration to
save changes and exit the Rack View Interface. If the window is closed without
choosing Save Configuration, then all changes are lost. Steps 6 - 14 should be
performed for each node as desired. Click Generate Report to generate a Visio report.
Select Cancel to exit the Visio Reports GUI without generating a Visio. Any saved Rack
View Interface edits will persist if Cancel is selected. If a Visio is generated, the report
will open.
Figure 5-116 shows the Visio Network View, Figure 5-117 shows the Visio Node View,
Figure 5-118 shows the Rack Views, Figure 5-119 and Figure 5-120 show the Power View.
For designs with Fiber OPS links, secondary links are reported separately in the Network View, span
details, and links sheet. Since the hardware on these links can differ from primary links, the Node
View sheet contains the actual hardware on such links. Rack View diagrams for the amp sites on
secondary links are generated separately. Power levels for primary and secondary links are reported
separately in the Power Levels: Node sheet and Power Levels: amp sites sheet.
Amp sites with Force No Equipment are represented in the Visio as follows:
• Shown in Span Details, as they may be a physical site
• Shown in the span sheet that is the Node View Diagram equivalent for amp sites, as it may be
a physical site

• Shown in the Power Levels sheet, as the optical power level information can be useful if it is a
physical location where optical measurements can be made
Figure 5-116. Network View


Figure 5-118. Rack View

Figure 5-119. Power Levels View (left side)
Figure 5-120. Power Levels View (right side)


The 40G Non-Linear Report must be generated for all 40G designs and provided as input for the
required OPNET review.
Step 1: Make sure you have run the network in CND with the "Generate 40G Non-Linear Log
Files" option enabled to generate the raw data required for the 40G Non-Linear Report.
A completed run will generate log files in the "C:\TEMP" folder, with the file name based
on the current file name and time/date stamp.
The 40G Non-Linear Report will be located in the target folder of the CND design. If the
design is not saved, it is suggested to save it to the desired folder location before
generating the 40G Non-Linear Report. The target folder will also contain a current
copy of the CND design to provide a design reference consistent with the report.
Step 2: Do one of the following:
• Click the Generate 40G Non-Linear Report icon in the Menu bar (see “Reports
Icons” on page 59 and “Generate 40G Non-Linear Report” on page 67).
• From the main menu, select Reports > 40G Non-Linear Report.
The Generate 40G Non-Linear Report window opens (Figure 5-121). When the
window opens, the Log Folder Name field displays the path to the logs of the last CND
network design that was run.
In the Log Folder Name field, the user can select the folder of the CND design run for
which to generate the report if a 40G Non-Linear Report is needed for a prior design
run.
Figure 5-121. Generate 40G Non-Linear Report window
Step 3: Press the Generate Report button.

When the report generation run is complete, the 40G Non-Linear Report Excel file
opens (Figure 5-122). The report file name format is:
<design_name>_40GNLVReport_<month>_<date>_<year>_<time>.xls
In the generated 40G Non-Linear Report Excel file:
• The Results Details sheet is a single sheet that contains the values for the list of
parameters read from the PT1.log files for all the test channels (Forward HIGH,
Forward LOW, Reverse HIGH and Reverse LOW) in different columns.
• The Power sheets are generated for each test channel and report the fiber and
DCM launch powers across the path of the test channel.

Figure 5-122. Example of 40G NLV Report Excel file

6
Chapter 6:
Create CoreStream Network
Overview
This chapter provides information about getting started creating a CoreStream network using
Release 5.2 Ciena Network Designer. The process is outlined with network design guidelines and
then presented in a flow chart highlighting each function through defined steps.
This chapter covers the following sections:
• “Network Design Guidelines” on page 201
• “Create a CoreStream Network” on page 201
• “Flow Chart Blocks: Detailed Procedures” on page 204
• “Block A. Add Nodes to Canvas” on page 204
• “Block B. Create and Configure Links” on page 205
• “Block C. Create and Configure Lightpaths” on page 211
• “Block E. Configure CoreStream Network Options” on page 222
• “Configure Nodes” on page 226
• “Configure Links” on page 230
• “Block F. Lock Network Elements” on page 237
• “Block G. Run Reports” on page 240
• “Design Summary” on page 240
• “Generate BOM” on page 243
• “Generate Incremental BOM” on page 244

This section describes the general process that users should follow to design networks with the
Ciena Network Designer. The Ciena Network Designer accepts network design information from the
Excel Input Template, or the user can create a network using the drag-and-drop feature on the CND
canvas.
Create a CoreStream Network

The Excel template, which provides error checking and automatic input of several parameter values,
is the preferred method for network design. Chapter 4, Excel Input Template on Page 69 provides
the necessary steps.
The following steps are performed to design a CoreStream network manually, on the CND canvas.
A corresponding flow chart is shown in Figure 6-1.

202 Chapter 6 - Create CoreStream Network
Step 1: Press the Insert Node icon button and left-click in the canvas to add the desired
number of nodes to the canvas. These nodes are add drop sites only. To create OLA
sites, insert spans between the add drop nodes by adding spans as described in
Step 2.
Step 2: Create and configure links by holding down the left mouse button and moving the
cursor from the originating port to the terminating port. Edit individual links by either
double-clicking the desired link in the Network View or selecting View > Link from the
main menu and highlighting the desired link in the drop-down list.
In the link parameters window, the user can:
• Change design parameters for the link
• Insert/delete spans
• Change fiber type, loss, length, and dispersion
On amp sites, the user can
• Force No Equipment
• Convert Amp Site to Node
Step 3: Create and configure a lightpath by holding the CTRL key and left-clicking on the
starting node and left-double-clicking on the ending node. Select protection if desired.
Select the intermediate nodes using CTRL-left-click.
The following operations can be performed from the lightpath view:
• Add more channels to a lightpath
• Delete a lightpath
• Edit channel properties in the lightpath
• Force regen/ Clear Force Regen and forbid regen in the lightpath
• Add protection/Diverse route to the lightpath
• Force Router Band DCMs on end add/drop nodes, regen locations and OBP
locations
Step 4: Select Tools > Design CoreStream Networks from the main menu to select network
design options.
Step 5: Open the Node View by double-clicking on the desired node in the Network View or
selecting View > Node from the main menu and highlighting the desired node in the
drop-down list to then change node properties, forbid regen, force Shelf Amp (USA6),
Disable SOADM as DGE and force lightpath-based OBP.
Step 6: Complete link configuration by selecting View > Link from the main menu and
highlighting the desired link in the drop-down list (or double-left-click on the desired
link) to then change span parameters, add/delete spans, convert amp site to node,
force Raman, ILA2, DCMs, OPM-DGE, Tx and Rx PAFs, PMD Coefficient, and forbid
regen and force no equipment on amp sites.
Step 7: Run reports.

Chapter 6 - Create CoreStream Network 203
Figure 6-1. Ciena Network Designer Flow Chart (CoreStream)


Block A. Add Nodes to Canvas
The user creates a network model by adding the desired number of nodes to the CND canvas.
Step 1: Select File > New from the main menu or use the shortcut, Ctrl-N (Figure 6-2).
Figure 6-2. Create New File
Step 2: Click the Set/unset node button and click in the canvas to add the desired number of
nodes (Figure 6-3). Unclick the Set/unset node button when finished to avoid adding
unwanted nodes.
Figure 6-3. Add Nodes

Step 3: Name the nodes by clicking in the name bar and entering the desired name in the
highlighted area.
Step 4: To remove a node, highlight it and select Edit > Delete from the main menu.
Block B. Create and Configure Links

Linking the nodes defines their degrees and creates a template that can be refined into a network.
To create links, the following steps are performed.
Step 1: Left-click the desired port in a node and drag the cursor to the desired terminating port
(Figure 6-4). Links are named by the CND, using the Tx and Rx node names.
Figure 6-4. Create Link

Step 2: Continue linking the nodes (Figure 6-5).
Figure 6-5. Link Nodes

Step 3: Rename the nodes by left-clicking on the node name and entering the desired name.
Click OK in the information boxes asking if the links should be renamed to capture the
new node name (Figure 6-6).
Figure 6-6. Rename Node
Step 4: Double-click on the link instance in the Tree View to open a dialog box with a drop-
down list containing the available links (Figure 6-7). Alternatively, double-left-click on
the desired link in the graphic view.
Before the Tools > Design CoreStream Network task is run, the link is undefined for
any network and the user can change fiber type, loss, margin, length, dispersion,
dispersion slope, and PMD Coefficient. After the task is run, DCM, NE Type, Raman,
OPM, DGE and PAF will be available. (Figure 6-8).

The Reset Fiber Params button in the Link View can be used to reset the dispersion
and slope values of the individual spans to their default values. (See Figure 6-12.)
Figure 6-8. Change Link Parameters in Unidentified Network
Step 5: To insert or delete individual spans, right-click the desired span in the Link View to open
the pop-up menu and select Insert Span (Figure 6-9).
Figure 6-9. Insert Span Menu
All inserted and deleted spans are applied bi-directionally. When a span is inserted, the loss and
length of the original span are halved to accommodate the new span. An amp site is automatically
added to the inserted span (Figure 6-10).

When a span is deleted, the loss and length of the deleted span are added to the span that is left,
and an amplifier site is automatically deleted.
Figure 6-10. Inserted Span
Step 6: Click Save to enable the changes and return to the Link View.
Autorouting
The autorouting feature allows the user to
• add nodes,
• convert an amp site to a node,
• convert a 2-degree pass-through node to an amp site, or
• delete a 2-degree pass-through node to an amp site
without deleting the adjoining links or the lightpaths traversing it, provided the link, amps, DCMs,
associated lightpaths, connected node degree, connected degree amps, or connected degree
DCMs are not locked.
When an autorouting function is performed, forced edits are maintained from the original link(s).
Routing and equipment information is updated in the GUI. Design Summary reports are updated
after Design CoreStream Network is run.
Autorouting is implemented with Convert Node to Amp Site or Remove Node in the Network View
(Figure 6-11). The Link View options are shown in Figure 6-12.
Convert Node to Amp Site: Right-click to open a pop-up menu on a 2-degree node with only pass-
through channels. Adjoining links are combined into a single link; force amp/DCM edits are not
cleared.
OCMs are always placed on DGE sites and cannot be removed manually. DGE sites are preferred
as Regen locations compared to normal Amp Sites. Transmit DCMs are not auto placed on 50GHz
DGE sites, but manual forcing is allowed. OAF-50 is auto placed as transmit amplifier in 50GHz DGE
sites, but users can force ULH OAV amplifiers as transmit Amps.

Remove Node: Right-click to open a pop-up menu on a 2-degree node with only pass-through
channels. Adjoining spans are combined to form a single span if the spans’ optical parameters are
the same; otherwise; the deleted node is converted into a “No Equipment” site.
Figure 6-11. Convert Node to Amp Site While Preserving Traffic (Network View)
Insert Node: Right-click on a span, or double-left-click on a span after enabling the insert node
button. The link is split into two links and the span in which node is inserted is equally divided
into the newly formed links. Link-based forced edits such as OPM/DGE and DCMs are cleared.
Note: DCM modules are configurable only by selecting them from the link view as shown.
DCM can not be changed in the matrix below the diagram as is done with 4200.
Figure 6-12. Link View Options

Block C. Create and Configure Lightpaths

A lightpath is a collection of data carrying channels that traverse between two end nodes and one
or more intermediate nodes. The combination of start, end, and intermediate nodes uniquely defines
a lightpath. If the start and end nodes are the same, but the intermediate nodes are different, another
lightpath is defined. A lightpath can have one or more channels of data carrying traffic, which can be
modulated at one or more data rates (such as 2.5G and 10G); however, 2.5G is not supported in
CND Release 5.2.
Step 1: To configure a lightpath, CTRL-left-click the start and end nodes in the Network View
to start the Lightpath Wizard.
Step 2: In the Choose Lightpath Type window, select CoreStream Lightpath and click Next
(Figure 6-13). Alternatively, select View > Lightpath > Add Lightpath from the main
menu and the wizard will provide instruction to CTRL-left-click the start and end nodes,
or simply CTRL-left-click the start and end nodes.
If a lightpath already exists with those start and end nodes, then it will be shown in the GUI. If more
than one lightpath exists with the same start and end nodes, then all lightpaths will be shown in
separate windows.
To add a different unprotected lightpath that shares the same start and end nodes as an existing
lightpath but uses a different set of intermediate nodes, use the same steps as above but select the
diverse path option in the wizard. See “Add Protection/Diverse Routing to Lightpath” on page 217.
Figure 6-13. Add Lightpath; Select CoreStream
Step 3: To select intermediate nodes of the lightpath, CTRL-left-click on each intermediate

node, and CTRL-double-left-click on the last node. For protected lightpaths, perform
this function on both the primary and secondary paths. No overlapping links are
allowed on the secondary path.
Step 4: Check the desired number of channels for the lightpath.
For convenience, the user can specify a block of waves to be assigned by using the drop-down lists
and selecting the start and end wave numbers. The available channel count includes channels that
require wave conversion. Click OK after making the desired selections. If the block includes a
band(s) already assigned, an error message displays.
40G and 10G channels cannot be selected in the same band.
If the length is beyond the distance limit, an error is displayed and the user is not allowed to complete
the lightpath creation (Regional – 600 km, Metro – 300 km). A similar check is performed in span
length modification.

A static message is displayed on Specify wave to warn the user that the difference between the
frequencies of the selected 10G/40G channel to the nearest 40G/10G channel respectively is less
than or equal to 450 GHz.
40G power offset values are editable for both primary and secondary paths of a protected lightpath
in individual instances, but changing either path is reflected in both paths.
Figure 6-14. Add Lightpath; Select Channels
The channel count is updated as waves are added (see Channel Count fields at the bottom of the
Specify_waves screen, Figure 6-14).
Step 5: Click Close to exit the wizard without saving, Clear to keep the window open and start
over, Save to save the information for the next kernel run, and Next to go to the next
window. If Next is clicked, the user is queried about saving the settings.

Step 6: Select the desired network-side cards from the drop-down list and click Next (Figure
6-15).
Figure 6-15. Add Lightpath; Network Modules
Step 7: The finished view is shown in Figure 6-16. The number of channels and type of
transport is shown in the GUI and detailed in the table below.
Figure 6-16. Lightpath Added

Step 8: To force Router Band DCMs, select the Force Router Band DCMs tab in the lightpath
view (Figure 6-17).
Figure 6-17. Router Band DCMs
• Candidate Locations for Router Band DCMs (RBDCM): Start node/ End Node/
Regen Nodes/ Regen Site/ OBP Node/ OBP Site in the lightpath.
• RBDCMs are allowed in regen sites, regen nodes, add/drop nodes, OBP Sites
and OBP nodes
• RBDCM for a band at a degree is shared by all add-drop and regen channels of
that band at that degree.
• Forced-Unused-RBDCMs are cleared in subsequent kernel runs.

Step 9: Shelf AMP USA6 can be manually forced/cleared at specific nodes in the design either
from the node view/ network view (Figure 6-18). Right click menu options and tool bar
buttons are provided to facilitate manual forcing/clearing.
Figure 6-18. Force Shelf AMP
• USA6 forced at a node applies to all add-drop and regen bands at all degrees of
that node (including the newly added degree/bands).
• CND Release 5.2 does not support USA6 and USA3T simultaneously at a node.
• Each Band containing OBP channels at a degree requires a USA-3T. Therefore,
forcing Optical By Pass (OBP) means forcing USA-3T.
• Shelf Amplifier status cannot be changed at Brownfield nodes.
• USA6 is not supported at Regen Sites.
Step 10: To view or modify the lightpath, select View > Lightpath > View Lightpath from the
main menu to open the View Lightpath window (Figure 6-19).

Step 11: Check the box by the desired lightpath. In addition, the user can add conditions to the
description of the lightpath, to distinguish it in a large network.
Figure 6-19. Search for Lightpath
Step 12: Click Apply to open the lightpath GUI, and Close to close the View Lightpath window.
Add Channels to Lightpath
To add channels, click the icon in the menu bar shown in Figure 6-20 or the option button in the
lightpath window. Select the desired number of channels to add.
The maximum allowed channels equals the system capacity minus the maximum number of
channels on any intermediate link. The GUI displays the available number of channels. An error
message displays if the user tries to add more channels than are available.
Figure 6-20. Lightpath Commands in Icon Toolbar

Add channel to lightpath
View lightpaths
Force regen
Delete lightpath Add protection/diverse routing

Delete Lightpath
To delete the lightpath, click the menu bar button shown in Figure 6-20. Click Yes in the information
box asking for confirmation to delete this lightpath and all other lightpaths with the same start and
end nodes.
Add Protection/Diverse Routing to Lightpath
Step 1: To add protection or diverse routing, click the icon in the menu bar (Figure 6-20) or the
option button in the lightpath window to open the Add Protection/Diverse Routing
window in the Lightpath Wizard (Figure 6-21).
Figure 6-21. Add Protection/Diverse Routing
Step 2: Click Add Protection and click Next. A confirmation message displays (Figure 6-22).
Figure 6-22. Confirmation Message
Step 3: Follow the steps to create the secondary path for the lightpath.

Step 4: For diverse routing, click Diverse Routing and click Next (Figure 6-21). Follow the
steps to create another path. The View > Lightpath window shows both the primary
and secondary paths of the lightpath, and the path with the diverse routing (Figure 6-
23).
Figure 6-23. View Lightpaths

Force Regen
To force a regen, click the icon in the menu bar (Figure 6-20) or the option button in the lightpath
window to open the Select Force Regen Locations window (Figure 6-24).
Figure 6-24. Force Regen
Step 1: Check the desired box. If appropriate, a warning message displays to tell the user that
all forced OPM/DGEs on the link will be cleared (Figure 6-25). Click Yes to continue or
No to cancel.
Figure 6-25. Force Regen Warning

To remove the regen, right-click on the node in the lightpath view. The pop-up menu now has an
option to Clear Force Regen (Figure 6-26).
Figure 6-26. Clear Force Regen
Edit/Delete Channels
• In the Lightpath view, click the Edit/Delete Channels button to open the Edit Channel
Properties for Lightpath window (Figure 6-27) for an unlocked lightpath. If the lightpath is
locked, the window opens but the properties do not have focus. This window can also be
opened by clicking Edit in the Edit Lightpath column of the View Lightpath window (refer to
Figure 6-19 on page 6-216).
• Click Delete Channel. Click Yes to delete the channel in both the primary and secondary
paths, No to delete the channel in the primary path only, or Cancel to quit. If the channel is
protected, a confirmation box opens where the user can opt to delete the channel in both
the working and protected paths. If Yes is chosen, the protected channel is converted to an
unprotected channel.
• Click Delete All Channels in Selection.Click Yes to delete all channels in both the primary
and secondary paths, No to delete all channels in the primary path only, or Cancel to quit.
• Select the desired service from the drop-down list.
• Select the desired protection from the drop-down list. Changing protection type is applied to
both the working and protected channels.
• Select the desired network module type from the drop-down list.
• Select the wave to be edited. Alternatively, check the Auto Assign box to have the system
select the wave ID.
Either the entire selection or a single wave or combination of waves can be highlighted and modified.
In addition, there is a check box to apply the changes to all the channels in the selection.

Apply and Close buttons save the changes and close the window.
Figure 6-27. Edit Channel Properties
A channel cannot be edited if it is locked or regen locations traversed by the channel are locked.
The network design of the parent channel is retained after the edit, so long as it is a valid option for
the edited channel type; otherwise, it is updated based on the Preferences setting for the edited
channel.
Perform a network design after editing channels.

Block E. Configure CoreStream Network Options

Once the nodes have been linked, the network can be defined as either 4200 or CoreStream. Before
beginning the design, select View > Network from the main menu.
Step 1: In the main menu, select Tools > Design CoreStream Networks (Figure 6-29).
Step 2: In the CoreStream Network Design Options window, supply the information
appropriate for this network.
• Default Terminal Settings: select either Terminal or S-Terminal. This setting will be applied
to break cycle nodes, regen site or for auto-placing legacy terminals.
• Planned Fiber Capacity: Select one of the following options:
• Capacity Driven: This option is the default. Selecting this will potentially enable higher
channel powers, up to the per fiber type set in Non-Linear Launch Powers in the
Preferences menu. It represents the actual channel loading.
• Growth: This option may be selected to ensure that channel power levels are set at
amplifier outputs to guarantee channel growth on all spans. It represents 96 channel loading
for Agility or 80 channel loading for Regional.
• Wave Assignment Settings: Select one of the following options:
• Center Out—starts filling from the central band
• Lowest to Highest—starts from the lowest wavelength band (Band12)
• Highest to Lowest—starts from the highest wavelength band (Band1)
• DCM Settings: Select either Default DCM or Type 0 DCM. DCM selection is made based on
fiber type at the port. Type 0 is optimized for NDSF.
Check the Disable Low Loss DCM checkbox to disable low loss type 0 fiber, which is used on
longer spans.
Warning: Increased Run Time

Using the Optimize or Minimize Router Band DCM options will increase the run time
substantially.Using Router Band DCM option is recommended as the final step or when
Router Band DCM is absolutely required.
• Router Band DCM Settings: Select one of the following options:

• Optimize Router Band DCM—Auto places RBDCMs to achieve best Q.
• Minimize Router Band DCMs—Auto places RBDCMs for passing Q, and no RBDCMs if Q
passes without RBDCM.
• No Router Band DCMs—Does not auto place RBDCMs.
• Advanced Features: Enable or disable using the check boxes.
• Place OPM-DGE—only for Agility systems.
• Enable SOADM as DGE—enables SOADM (RBF) as DGE for the entire network.
• Place OPMs at All Nodes—enables RBF as DGE in all nodes where RBF as DGE has not
been disabled. This option is available only when Enable SOADM as DGE is selected.
• Disable Pre-Emphasis for Regional—no ripple correction will be applied.
• OSNR Pass Threshold: The pass threshold defines the OSNR level below which CND will
place regenerators in a network. Setting thresholds lower than the default gives an aggressive
network design with reduced regeneration, with the added risk that design may fail BER.
Setting thresholds higher than the default gives a conservative network design with increased
regeneration, but with a lower risk that the design might fail BER during validation. Select from
the following:

- 10G C Band G.709: recommended OSNR is 14dB

- 10G RB G.709: recommended OSNR is 14dB
- 10G G.709 Swap: recommended OSNR is 14dB
If the user checks the Use Default box, any values that were changed will be returned to
the default values in the list above.
• Raman Settings: Check or uncheck the box to enable or disable automatic Raman
amplifier placement in the network. CND will automatically place Raman amps in spans with
span loss greater than threshold value.
• Force Edits: Checking the Force Edits: Clear Force Edits options clears all unlocked
manual node and link related edits. If the Force Edits check box is selected, the Clear Force
Edits hyperlink can then be used to select specific types of edits to clear as shown in Figure
6-28. Note that clearing forced edits will not clear any locked components in the network.
• PDL Settings: Check the box if you want to set the value for System PDL. To accurately
model high/low power range for the 40G channels, the Polarization Dependent Loss (PDL)
is computed for 40G channels alone. No specific limits are applied for the PDL value. The
PDL contribution from various components in the transmission path (Fiber, DCM modules,
Amplifiers, Filters etc) have been accounted for. The existing ripple model for 10G channels
is unchanged and hence PDL is not computed for the 10G channels.
Figure 6-28. Clear Force Edits
• 40G Settings
• 40G Non-Linear Validation: This option is selected to perform full 40G non-linear
validation of all 40G lightpaths within the design. Due to the potentially significant run
time of the non-linear analysis, this option can be deselected so that only a linear
analysis is performed on the 40G lightpaths. This allows the user to evaluate signal
power levels and OSNR to ensure they achieve reasonable levels for 40G to be viable.
When 40G validation is run, a warning message is generated stating that 40G non-linear
validation must subsequently be run to properly validate the design.
• Generate 40G Non-Linear Log Files: Select this option in order to generate the log
data required for the 40G Non-Linear Report. All 40G design results must be evaluated

by OPNET even if all results are passing, with the 40G Non-Linear Report being
required input. 40G design runs can take approximately 25% longer to run when this
logging function is enabled so it is normally left disabled. Once a desired 40G non-linear
design result is achieved, the design should be rerun with this option enabled, with a
40G Non-Linear Report subsequently generated.
Step 3: When Enable XPM sampling is checked, XPM is computed for only worst case
channel in a band and the same value is considered for all channels in the band. When
the checkbox is not selected, XPM is computed for all channels in a band. Selecting
this option can reduce the kernel run times but the XPM penalty may not be optimized,
while de-selecting this option leads to longer kernel run times but the XPM computation
is more accurate.
Step 4: Click OK to create the network or Cancel to quit. The CND does error checking and
supplies validation error messages such as that shown in Figure 6-30 if design choices
do not match. Clicking OK implies acceptance of the message and the tool fixes the
error. CND also displays a summary of the design in the message window. Any
warnings are highlighted in red (Figure 6-31).

Figure 6-29. Configure CoreStream Network Design Options
Figure 6-30. Design Choice Error Message

Figure 6-31. CoreStream Network Summary
Configure Nodes
Optionally, the user can configure an individual node.
Step 1: Double-click on the node instance in the Tree View
Step 2: Select the desired node from the drop-down list (Figure 6-32). Alternatively, double-
left-click on the desired node to open the Node View. The Node View is shown in
Figure 6-33.
Figure 6-32. Select Node

Step 3: Change the NE type by selecting from the drop-down list under the Force NE Type
heading (Figure 6-34). The options offered are dependent on the number of ports in
the node.

All node edits have priority over global network design options. For example, the entire network can
be designed with partitioning IV, and then Force NE Type can be chosen to change certain nodes
to be COADM(ADC1).
Figure 6-34. Force NE Type
If COADM(ADC1), SOADM, COADM(ADC2), GD-SOADM, or WD SOADM is selected, the Group

Optical Ports dialog box offers a list of ports to add to the selected group if the choice is appropriate.
Depending on the degree of optical transparency of the NE selected, the user is offered the option
to group the associated ports (Figure 6-35).
Figure 6-35. Group Optical Ports
• Forcing/Clearing OBP is supported at Nodes only (not Regen Sites).

• OBP can be forced between any two node degrees of the node except with/within
COADM degrees.
• The OBP forced between an SOADM/ WD-SOADM/ GD-SOADM degree pair is
ignored and channels are expressed through RBF/WSS as applicable.

OBP States:
• Enable - Enable OBP for specific degree pair(s)/ specific light path(s); Candidate
for autoplacement of OBP
• Disable - OBP is strictly disabled for autoplacement
Auto OBP at nodes:
• To break optical cycle.
Auto OBP at Regen Sites:
• As NE type applicable at Regen Sites is either Terminal/ Select Terminal, the
applicable optical pass through is OBP.
Step 4: To force Optical Bypass (OBP), click the Force OBP button in the upper left corner of
the Node View (Figure 6-36).
Forced OBP is applicable for channels passing through node degrees with
incompatible NE types that cannot support regular optical express in GD SOADM,
SOADM, COADM(ADC1), COADM(ADC2) or optical cross over connections through
WSS-2 in WD S Term and WD SOADM. CND will not place any OBP automatically
except in break cycle nodes and ILA regen sites. OBP can only be forced at the
lightpath level. Forced OBP is supported between any degree pairs through the GUI
but the kernel will consider it wherever applicable. Channels passing through regular
OADM degree pairs will be optically expressed even though OBP is enabled between
those degrees.
Forced OBP is supported between the following NE types:
• Terminal or S Term to Terminal or S Term and vice versa
• S Term to S Term
• S term or Term to WD S Term and vice versa
• Term, S Term or WD S term to SOADM or GD SOADM
• SOADM or GD SOADM to Terminal S Term or WD S Term and vice versa
• Terminal-SOADM
• SOADM-SOADM (non paired)
Note that the SOADM can be a regular SOADM or a GD-SOADM.
OBP is not supported in a node where the originating or terminating port is COADM.
There is no limit to the number of bypasses a wavelength traverses between its source
and destination.
After enabling OBP between node degree pairs, a GUI window listing all light paths
traversing through the selected node degrees pops up and OPB can be enabled/
disabled for specific lightpaths.
Forbid Regen option is available as a right click option in either the Node View or at the
node level in the Network View. Note that the node level forbid regen is applicable to
OSNR threshold-based regen placement and regens can be placed in Forbid Regen
Nodes due to incompatible partitioning for the node degrees through which the

lightpath passes. OBP has to be specifically forced to avoid these regens and truly
forbid regen on the node.
Figure 6-36. Force OBP
Step 5: In the Group OBP Ports window that opens (Figure 6-37), select Enable from the
drop-down list to group the desired port(s). All ports on the node will be displayed.
Figure 6-37. Group OBP Ports
Configure Links
Optionally, the user can configure a link or links.
Step 1: Double-click on the link instance in the Tree View or left-double-click on the link.

Step 2: Select the desired link from the drop-down list (Figure 6-38). The Link View is shown in
Figure 6-39.
Figure 6-39. Link View
Step 3: Click the Force ILA2 button on the right side of the window to set the NE Type to CS
regional (ILA2).
Step 4: Click the Auto Place Raman link to place Raman if span loss exceeds the Raman
threshold.
Step 5: Select OPM, OPM Forced, DGE, and DGE Forced from the corresponding check
boxes.
The following guidelines apply when forcing or removing OPMs and DGEs.
• Force OPM/DGE is supported only in ILA1 Agility links.
• Place DGE cannot be forced at regen with NE as Terminals and terminal nodes, but DGEs can
be forced at SOADM, S Term nodes and S Term regen sites, WD S Term, WD SOADM and
COADM(ADC1).

• Force OPM is allowed at every location.

• On any uni-directional link, the number of OPMs must equal or exceed the number of DGEs.
• DGEs can be forced by direction, but OPMs are always bi-directional. For example, if DGE is
forced in the Rx direction, it applies to that site only as a Rx (not Tx). If OPM is forced, it can
apply in both directions.
• When a DGE is forced, an OPM must be forced correspondingly on the downstream side.
• If a regen is forced on a site/node on a link with forced OPM/DGE, all the forced OPM/DGEs at
sites/node on the link will be cleared, and a warning message "forcing this regen will clear all
force OPM/DGEs on the link" will be displayed. The forced regen can then be canceled. If the
regen is forced, a kernel run must be done and OPM/DGE forced again on the link.
Step 6: In the PAF W->E(dB) and PAF E->W(db) columns, leave the default setting or enter a
new value. The PAF defaults are based on fiber type for ILA sites (see Table 6-1) and
NE type at node degrees (see Table 6-2).
• A range of -8 to 9dB is supported for Tx/Rx PAF.
• Forced PAF values are validated against PAF ranges in the NE based default PAF table.
• Forcing Rx/Tx PAF is not available in COADM(ADC1)/COADM(ADC2) degrees.
The following guidelines apply when forcing DCMs (Figure 6-40):
• Low Loss DCMs and SR-DCM are not supported CoreStream designs in CND Release 5.2. It
is assumed that there would not be any legacy CoreStream designs using the Low Loss Type0
and Low Loss Type3 designs. Legacy designs using these DCMs cannot be supported in CND
Release 5.2 (may result in errors or exceptions).
• Tx DCM cannot be forced at Regen Sites unless they are converted to nodes.
• Tx DCMs can be forced at Terminal degrees only.
Figure 6-40. Forcing DCMs

Table 6-1. Fiber Type Based Default PAFs
Table 6-2. NE Based Default PAFs
Recommended span launch powers for 40G channels

While designing networks with 40G channels, the launch powers into the fibers should be carefully
configured within CND. Traditionally, the default 10G powers (depending on the PAF) vary based on
the fiber type alone. As mentioned in earlier sections of this document, the 40G powers would be
configured at predefined 'Power Offset' with respect to 10G powers. CND Release 5.2 continues to
honor the default NE based 10G PAFs (as per Table 6-2) and further validates the 40G powers to
be within the powers limits supported by different NE types as per Table 6-3.

Table 6-3. NE-based 40G power limits
Ideally, the default launch power would be determined based on the fiber type(s), span count, DCM
presence (or absence) and mixed versus pure 40G datarates. If mixed 10G and 40G channels are
present in the network, it is often helpful to use differential launch powers and reduce the 10G
powers as much as possible. To deal with such scenarios, the following tables—Table 6-4 (Note that
some unsupported fiber types are included for future reference.), Table 6-5, Table 6-6—should be
considered as reference to configure the 40G powers into the fiber.

Table 6-4. Recommended power per channel into fiber for pure 40G, no DCM
Table 6-5. Recommended power per channel into fiber for pure 40G, with DCM

Table 6-6. Recommended power per channel into fiber for mixed 10G / 40G, with DCM
Step 7: Forbid Regen on amp sites as appropriate. The Forbid Regen option is available as a
right click option on amp sites.
Step 8: Click the Save button.
Changes to link parameters are accommodated, if possible, and the appropriate adjustments are
made to other parameters. If invalid changes are made in fiber parameters, appropriate error
messages are displayed stating the range of values permitted.

Block F. Lock Network Elements

CND provides the ability to create and save incremental designs without changing already deployed
field configurations. In one tier, the user can lock an entire network design. In a second tier, the user
can lock nodes, links, and lightpaths. In a third tier, the user can lock the amps, filters, DCMs, or
regens in a node or amp site. Thus, the user can freeze an iteration of a design and then add to it
without changing the original, or the user can do a kernel run and no alterations will be made to the
design by the optimization function of the CND.
Note: The following points apply when locking/unlocking.

• Nodes: A node degree cannot be locked or unlocked separately. When a node is
(un)locked, all the currently connected degrees are (un)locked as well.
• Links: Amp sites cannot be locked or unlocked separately. When a link is (un)locked,
all the amp sites in that link are (un)locked.
• Lightpaths: Channels cannot be locked or unlocked separately. When a lightpath is
(un)locked, all the channels in that lightpath are (un)locked.
To design a network incrementally and save each iteration, the entire network, a link, or a network
subset of the lightpaths, amps, or DCMs can be locked by clicking Locking > Lock (or Unlock) in
the main menu, or clicking the appropriate icon in the menu bar. Locking/unlocking actions can also
be performed on the network, or on nodes, links, or lightpaths either in bulk or individually from the
Tree View.
Figure 6-41. Lock Network from Pop-up Menu

Performing a locking action on the entire network opens a confirmation window (Figure 6-42).
Figure 6-42. Network Locking Confirmation Window
Click OK to open the Windows Save As menu. If the <givenName>.xml already exists in the
directory, when Save is pressed in the Save As window, a prompt appears to overwrite the existing
file, and if the user agrees, the <givenName>.xml is overwritten and the <givenName_baseline>.xml
(the original file) is saved as read-only. In the instance of multiple network locking operations on the
same design, read-only copies are saved with sequential numbers appended to the design file name
(Figure 6-43).
Figure 6-43. Save Locked File

The BASELINE file is read-only. If opened, the network is displayed locked, and all other views are
locked and grayed out (Figure 6-44).
Figure 6-44. Read-only BASELINE File
If the network, link, or lightpaths, or amps or DCMs subset is unlocked, it cannot be locked if the
node/link name and/or node NE type is modified, new links are added to the node, span parameter
is changed, channels are added to any one of the lightpaths terminated on the node, or any force
operation is performed in any of the links connected to the node. After a successful kernel run has
been done, the network, nodes, links, lightpaths, or any subset can be locked.
The user can also select a part of a network and lock/unlock that selection only by pressing SHIFT
+ left-click to select the desired nodes and links. The user can then lock or unlock the selection, using
either the icon option, the main menu option, or the right-click option.
Nodes can also be locked/unlocked in the Lightpath view, using either the icon option, the main
menu option, or the right-click option.
In the Node View, the user can lock/unlock the entire node, node amps, and/or node DCMs using
either the icon option, the main menu option, or the right-click option. The appearance of the Node
View changes based on the selection. The change is reflected in the Network View.
In the Link View, the user can lock/unlock the entire link, link amps, and/or link DCMs using either
the icon option, the main menu option, or the right-click option. The appearance of the Link View
changes based on the selection. The change is reflected in the Network View.

Block G. Run Reports

The Ciena Network Designer enables Excel output reports. Two report styles are available: the
Design Summary provides technical information about network design, and Generate BOM/
Incremental BOM provides Bill of Materials (BOM) information about network design. Access to the
current price workbook is necessary to run the Generate BOM report with accurate results.
Design Summary
Use the Design Summary menu option to create an Excel report summarizing the network. Click
the icon in the toolbar shown below, or from the main menu, select Reports > Design Summary
(Figure 6-45).
The tool creates an Excel summary report broken out by network summary, nodes, links, and
lightpaths. Figure 6-46 gives an example of the network summary, which provides the number of
nodes, links, and amplifiers in general, and broken out by Agility and Regional designation. Specific
information is broken out as shown in Figure 6-47 through Figure 6-53.

Note that two additional columns have been added at the end of the Link sheet, for WE PMD
Coefficient and EW PMD Coefficient, respectively.
Figure 6-46. Design Summary, Network Breakout
Figure 6-47. Design Summary, Nodes Breakout

The channel plan is made up of the terminated and other channels, which correspond to the
terminated bands (Figure 6-48).
Figure 6-48. Design Summary, Links Breakout - Left Side
Figure 6-49. Design Summary, Links Breakout - Right
Figure 6-50. Design Summary, Lightpath Breakout - Left Side
Figure 6-51. Design Summary, Lightpath Breakout - Middle
Figure 6-52. Design Summary, Lightpath Breakout - Right Side
Regen locations in Column G, Regen Locations, is filled in only if the lightpath has a regen. If it does
not, then NA (Not Applicable) is entered in the cell. For the cell to be filled in correctly, the site names
MUST match exactly the names in columns I and J.

The value for Q in Column P is NA until the network design is run and the results are saved.
Figure 6-53. Warnings and Design Constraints
Generate BOM
Before generating the BOM, select Reports > Load Price Information so the design configuration
will be populated with accurate prices.
Select Reports > Generate BOM to create the Excel file with prices per element (Figure 6-54).
Note the following assumptions for the completed BOM:
• Check with CoreStream configuration guidelines for any potential discrepancy in configuration.
• The computation is for an ETSI rack only.
• Some universal connector part numbers have a wild character (note the x: 130-6500-9x0).
Replace this with the specific customer connector type.
• Band tunable cards also use a wild character.
• No CoreStream starter kit is used. Convert the configuration manually.
• 2.5G XCVR configuration is not taken into consideration for the current release.

• Depending upon the user selection for Y1 or Y1+YN, the name of the BOM report will be
appended by Y1 or Y1+YN.
Figure 6-54. Generate BOM
Generate Incremental BOM

The incremental BOM generates two price reports, so the user can compare a baseline network with
the changes in a later version. The user selects Reports > Incremental BOM from the main menu,
or clicks the icon in the menu bar.
In the information window that opens (Figure 6-55), select which file will be design #1 in the BOM
and which will be design #2. The files can be either .xml or .xls. Browse for the desired files, or
choose from the files currently open in CND. If Choose from Open files is checked, a drop-down
list is available. Also, check Open in CND to open a file by browsing. Click OK to generate the
incremental BOM.
Figure 6-55. Incremental BOM Setup

Click OK to create the Excel file with prices per element (Figure 6-56). The Excel file contains the
BOM for the original (<filename>.baseline), the modified, and the incremental report. The
incremental BOM displays the difference in hardware between the original file (baseline) and the
modified file selected by the user. Thus, if a cell displays a zero for a piece of hardware, there is no
change between the original and the modified files, and no new equipment of that type is needed for
the modified design. If a cell displays a 2, then 2 more pieces of that type of hardware are needed
to support the modified design. A -2 indicates that two fewer pieces are needed.

Figure 6-56. Incremental BOM


The 40G Non-Linear Report must be generated for all 40G designs and provided as input for the
required OPNET review.
Step 1: Make sure you have run the network in CND with the "Generate 40G Non-Linear Log
Files" option enabled to generate the raw data required for the 40G Non-Linear Report.
A completed run will generate log files in the "C:\TEMP" folder, with the file name based
on the current file name and time/date stamp.
The 40G Non-Linear Report will be located in the target folder of the CND design. If the
design is not saved, it is suggested to save it to the desired folder location before
generating the 40G Non-Linear Report. The target folder will also contain a current
copy of the CND design to provide a design reference consistent with the report.
Step 2: Do one of the following:
• Click the Generate 40G Non-Linear Report icon in the Menu bar (see “Reports
Icons” on page 59 and “Generate 40G Non-Linear Report” on page 67).
• From the main menu, select Reports > 40G Non-Linear Report.
The Generate 40G Non-Linear Report window opens (Figure 6-57). When the window
opens, the Log Folder Name field displays the path to the logs of the last CND network
design that was run.
In the Log Folder Name field, the user can select the folder of the CND design run for
which to generate the report if a 40G Non-Linear Report is needed for a prior design
run.
Figure 6-57. Generate 40G Non-Linear Report window
Step 3: Press the Generate Report button.

When the report generation run is complete, the 40G Non-Linear Report Excel file
opens (Figure 6-58). The report file name format is:
<design_name>_40GNLVReport_<month>_<date>_<year>_<time>.xls
In the generated 40G Non-Linear Report Excel file:
• The Results Details sheet is a single sheet that contains the values for the list of
parameters read from the PT1.log files for all the test channels (Forward HIGH,
Forward LOW, Reverse HIGH and Reverse LOW) in different columns.
• The Power sheets are generated for each test channel and report the fiber and
DCM launch powers across the path of the test channel.
• The Dispersion Map is a single sheet that contains the cumulative residual
dispersion across different links (Forward and Reverse directions).

Figure 6-58. Example of 40G NLV Report Excel file

7
Chapter 7:
Error Messages
The tables in this chapter present questions and error, warning, and information messages that are
generated by the Ciena Network Designer.
Viewing GUI Error Messages

To view and analyze error and warning messages generated by the GUI, observe the message area
on the main window. Common error messages are found in Table 7-1, 4200 specific error messages
are found in Table 7-2, and CoreStream specific error messages are found in Table 7-3.
Table 7-1. Common GUI Messages

CND Tool Message
Message Description
Area Type
XML parser Cannot save to XML. Invalid link: error
<<link.Name>>
XML parser AddLinks: Could not find node name warning
referenced by link: <<NodeName>>
XML parser Unable to create link <"+np.FacingLinkName + warning
">. No available ports found for node:
<<NodeName>>
Network design Cannot design empty document error
Network Design 40G Non-Linear Validation must be performed warning
Summary
Network view Design document has been modified. Save question
modified design?
Network view Closing Modified Network Design information
Network view Error saving network design as a file error
Network view Error saving graph as a file error
Network view Error reading graph from a file error
Network view Error re-reading graph from a file error
Network view Alignment failure: Primary Selection is empty error
or a link instead of a node
Network view Cannot save Empty Design warning
Network view Document is already opened, Can not warning
overwrite the file
Network view Invalid lightpath: No link exists between this warning
and previously selected node
Network view Node with identical name found warning
Network view Sizing failure: Primary Selection is empty or a warning
link instead of a node

250 Chapter 7 - Error Messages
Table 7-1. Common GUI Messages (Continued)

CND Tool Message
Message Description
Area Type
Network view Design document has been modified. Save question
modified design?
Network view Closing Modified Network Design Information
Network view Primary Selection is null or not a node warning
Link view No links found in document error
Link view Should not change a Link connecting a Node error
to another Node
Link view Alignment failure: Primary Selection is empty error
or a link instead of a node
Link view Primary Selection is null or not a node error
Link view Sizing failure: Primary Selection is empty or a error
link instead of a node
Link view Application Error: Link not found in XML error
document
Link view Could not locate right Ola Node: (NodeName). error
Unable to process input data
Link view No links found in document error
Link view Span Loss must be in between 0.1-55 dB error
Link view Span margin must be in between 0-9 dB error
Link view Span Length must be in between 1-186 mi error
Link view Span Length must be in between 1-300 km error
Link view Span dispersion must be in between -5 to 25 error
ps/nm/(km/mi)
Link view Span dispersion slope must be in between 0- error
0.3 ps/nm2/(km/mi)
Link view Could not load Link View Edit. Null Xml link error
node
Link view Should keep one span between Nodes. error
Link view Could not delete regen sections and nodes error
Link view Link with identical name found warning
Link view Link already exists between selected nodes! warning
Link view Cannot save xml document : Exception exception
message
Link view Do you want to change link name to … question
Link view This will convert entire network to CoreStream question
Network/CN4200 Network. Are you sure you
want to convert?
Link view The sum of span loss and margin can’t be error If the user tries to save when Raman is forced
>35dB as Raman is forced on this span in the span and the sum of Span Loss and
Span Margin is greater than 35db, this
message displays.
Link view Invalid Span Length: The length of the error If the user tries to save when the sum of the
lightpath containing G6S card as child card span length of a lightpath is greater than
and passing through this link should be less 100km and that lightpath contains a G6S card
than 100km as child card, this message displays.

Chapter 7 - Error Messages 251

CND Tool Message
Message Description
Area Type
Link view The dispersion value for this fiber type cannot error If the user tries to enter data in another cell
be zero after entering zero as the dispersion value for
non-DSF fiber type, this message displays.
Link view Span dispersion must be in between -5 and 25 error If the user tries to enter data in another cell
ps/nm/km and the dispersion is >25 or < -5, this message
displays.
Link view The dispersion slope value for this fiber type error If the user tries to enter data in another cell
cannot be zero after entering zero for the dispersion slope,
this message displays.
Link view Span dispersion slope must be in between 0 error If the user tries to enter data in another cell
and 0.3 ps/nm^2/km and the dispersion slope value > 0.3 or <= 0,
this message displays.
Link view Raman Threshold must be 21 dB or greater if error If the “Raman Present” checkbox is checked,
using ILA-2 type amplifiers CS-ILA-1 is selected as amp, and the Raman
threshold is < 21db, this message displays.
Link view All the forced { DCMs and/or OPM/DGE and/or warning If any DCMs and/or OPM/DGE and/or Regen
Regen Sites } in all the light paths passing Sites are forced in the link while saving, this
through the link will be reset. Do you want to message displays to remove all the forced
continue? items.
Link view Do you want the update the dispersion and warning This message displays if the user selects a
dispersion slope to default for the selected new fiber type after changing the dispersion or
fiber type dispersion slope manually for the old fiber
type.
Node view Could not load Node View Edit. Null Xml node error
Node view You should perform Network Design before error
edit force NE type.
Node view Could not able to add a link! error
Node view Node with identical name found error
Node view No nodes found in document error
Node view This will convert entire network to CoreStream question
Network/CN4200 Network. Are you sure you
want to convert?
Light Path view/ Select all intermediate nodes while creating error
wizard lightpath between Nodes.
Light Path view/ No alternative path Available error
wizard
Light Path view/ Secondary Path Selected has overlapping error
wizard links to that of Primary Path
Light Path view/ Not selected all intermediate Nodes error
wizard
Light Path view/ Already routed alternative path is not available error
wizard
Light Path view/ Please select alternative route different from error
wizard the existing route
Light Path view/ Please select all the intermediate nodes error
wizard
Light Path view/ All the Channels in the Lightpath are Protected error
wizard


CND Tool Message
Message Description
Area Type
Light Path view/ Number of channels exceeds maximum error
wizard
Light Path view/ Invalid lightpath: No link exists between this error
wizard and previously selected node
Light Path view/ You did not choose any channels error
wizard
Light Path view/ The range of specified-waves is invalid error
wizard because it contains a wave-id that has already
been assigned (wave-id xxx, yyy …)
Light Path view/ The range of specified-waves is invalid error
wizard because the start and end wave-ids are
identical.
Light Path view/ Any previous filter edit operation on all the warning When light path, passing through a node
wizard unlocked nodes will be lost and force node which is VMUX forced and node on which edit
type operations on all the unlocked VMUX filter operation was done, is added or deleted.
nodes traversed by this lightpath will be lost.
Do you wish to continue?
Light Path view/ Force node type operations on all the unlocked warning When light path, passing through a node
wizard VMUX nodes traversed by this lightpath will be which is VMUX forced, is added or deleted.
lost. Do you wish to continue?
Light Path view/ Lightpath cannot be added between selected warning When light path is added/created, this
wizard nodes as following node degrees are forced message appears if any node in the lightpath
and locked as BS-5 preferred VMUX terminals: has at least one port as forced and locked BS5
NodeA DegreeX terminal.
NodeB DegreeY
wizard nodes as following node degrees are part of message appears if any node degree in the
forced and locked VMUX OADM pairs: lightpath is a part of forced and locked OADM
NodeA DegreeX pair and the other node degree is not a part of
NodeB DegreeY a forced and locked OADM pair that passes
through the Locked OADM Pair node.
wizard nodes as following node degrees are forced message appears if any node in the lightpath
and locked concatenated terminals: is a forced and locked concatenated terminal.
NodeA DegreeX
NodeB DegreeY
Specify Lightpath All the manually specified even/odd channels warning Displayed when switching the channel plan
will be changed to auto assigned channels in from 40 to 44.
the entire network and all the manually
specified even/odd channels in this window will
be cleared. Do you want to continue - Yes /No
Specify Lightpath This operation is not allowed as number of error Displayed when switching the channel plan
auto/manual assigned channels is more than from 44 to 40.
40 in some of the links in the network. Change
the channel plan after deleting the excess
channels from the links listed below
Specify Lightpath All the manually specified 100 Ghz guard band warning Dipslayed when the number of auto/manually
channels will be changed to auto assigned assigned channels is less than or equal to 40
channels in the entire network. Do you want to channels but there are some manually
continue - Yes /No assigned channels falling on guard band wave
ids (24, 33, 42, and 51) when switching from
44 to 40 channel plan.


CND Tool Message
Message Description
Area Type
Preferences menu Design Constants: Loss Coefficient must be error
numeric.
Preferences menu EditPreference: Unable to save preferences in error
XML file
Preferences menu You must select at least one network module error
from the Design Options tab
Preferences menu All span losses will be modified with new loss warning
coefficient
Chassis Config - Select channel type first warning
Service Cards
Chassis Config - Select card type warning
Service Cards
Chassis Config - Card type mismatch with the channel type warning
Service Cards
Chassis Config - Card Type is mandatory warning
Service Cards
Chassis Config - Card Type incorrect for given Channel Type warning
Service Cards
Chassis Config - You are about to change Card which contains warning
Service Cards network module for the other channel. Assign
the network module for "+ id +"
<Traffic,Channel> Id pair on some other cards.
Chassis Config - Available ports on 2RS card of channel warning
Service Cards ‘"+drTemp[0] ["tid"]+", "+drTemp[0]["cid"]+"'
have been used for this channel.
Chassis Config - channelType value corrupted for warning
Service Cards tid=["+trafficID+"] and cid=["+cid+"]
Chassis Config - protectionType value corrupted for warning
Service Cards tid=["+trafficID+"] and cid=["+cid+"]
Chassis Config - cardType value corrupted for tid=["+trafficID+"] warning
Service Cards and cid=["+cid+"]
Chassis Config - Card Type incorrect for given Channel Type warning
Service Cards
Chassis Config - One Network port is already assigned to this warning
Service Cards - card. Select other card for another Network
MoreInfo Port
Chassis Config - You cannot add more Network Ports for this warning
Service Cards - channel
MoreInfo
Chassis Config - This port is defaulted to Network Port warning
Service Cards -
MoreInfo
Chassis Config - There cannot be two Network Ports warning
Service Cards -
MoreInfo
Chassis Config - Network port can be assigned to F10-A cards warning
Service Cards - only
MoreInfo


CND Tool Message
Message Description
Area Type
Chassis Config - This port is disabled for Card F10-A warning
Service Cards -
MoreInfo
Chassis Config - No more than 3 cards can be added to a warning
Service Cards - channel
MoreInfo
Chassis Config - Not Possible for current row warning
Service Cards -
MoreInfo
Chassis Config - At least 1 card must be present in a channel warning
Service Cards -
MoreInfo
Chassis Config - At least 2 cards must be present for this warning
Service Cards - protection type
MoreInfo
Chassis Config - Number of Network Ports is less than required warning
Service Cards -
MoreInfo
Chassis Config - Number of Network Ports is more than warning
Service Cards - required
MoreInfo
Help menu Unable to load CND User Guide, as the file error
CNDUserGuide.pdf is not available
Help menu Unable to load CND User Guide, Acrobat error
Reader is not installed
Excel Template Excel document cannot contain two routing error For old Excel templates, only one routing
Parser worksheets for CN4200 Network. sheet should be present in the input Excel file.
Excel Template "Node name: '"+strArray[0]+"'"+ "contain an error Node names entered in Excel input template
Parser invalid character. \nOnly alphanumeric contain special characters other than A-Z, a-z,
characters , underscore '_', spaces and dash '- 0-9, hyphen, and underscore.
' allowed.\r";
Excel Template "Link is broken at row number: " + i.ToString() error No end node value supplied for link in Links
Parser + " in Links worksheet!\r"; sheet.
Excel Template "Node " + strArray[0] + " found in Links error Node name entered in FiberNodeA column in
Parser worksheet A column is not defined in Nodes Links sheet is not listed in Nodes sheet.
worksheet!\r";
Excel Template "Node " + strArray[1] + " found in Links error Node name entered in FiberNodeB column in
Parser worksheet B column is not defined in Nodes Links sheet is not listed in Nodes sheet.
worksheet!\r";
Excel Template "Same Node name entered for FiberNodeA error Message is reported if in Links sheet, in a row
Parser and FiberNodeB at row number: " + entry for a link, values entered for FiberNodeA
i.ToString() + " in Links worksheet!\r"; and FiberNodeB are the same.
Excel Template "Length has to be provided for link row error Link_length cell value is blank for a link.
Parser number: " + i.ToString() + " in Links worksheet
C column\r";
Excel Template "Either span field or SpanPhysical worksheet error For old Excel template, either SpansPhysical
Parser needs to be provided!\r"; or AllSpansPhysical sheet should be present.
Excel Template "The number of spans in one more rows is not error Number of spans entered in Spans column in
Parser in the range Not a number or <1 or >33!\r"; Links sheet is not in range 1-32 (inclusive of
bounds).


CND Tool Message
Message Description
Area Type
Excel Template "Link name is missing in the links error Link_name cell value is blank for a link in Links
Parser worksheet!\r"; sheet.
Excel Template "Invalid fibre ops protection name is missing in error Fiber_OPS_Protection cell value for a link in
Parser the links worksheet!\r"; Links sheet is neither "Yes" nor "No."
Excel Template "Invalid Start and end node combination for error A specific link row entry of "n" number of
Parser spans in row:" + errorRows[k].ToString()+" of spans has corresponding span row entries
"+ "span physical worksheet"+".\r"; (n+1 number of rows) in SpansPhysical sheet,
but start and end node names do not match
with corresponding entries in Links sheet.
Excel Template "Invalid link for spans in row:" + error Link name in SpansPhysical sheet is not a
Parser linkerrorRows[j].ToString()+" of "+ "span valid link for set of site-node pairs.
physical worksheet"+".\r";
Excel Template "Invalid demand name: " + error Value entered for the demand name column in
Parser strArray[0].Trim()+"on row any routing sheet is not in range 1-
'"+rowNumber.ToString() +"' in "+ 2147483647 (inclusive of bounds).
worksheetName +" routing sheet"+".The value
should be an integer between 1 and
2147483647\r";
Excel Template "Same name entered for NodeA and NodeB in error Node names entered in NodeA and NodeB
Parser one or more light paths in the routing sheet on columns in routing sheet are the same.
row number: " +rowNumber.ToString() +" of "+
worksheetName +" routing sheet"+".\r";
Excel Template "Channel number '" + strArray[3] + "' is invalid error Entered value for the Channels column is
Parser in Routing worksheet on row number: " 1) Not a number or <1 or >40 in case of 4200
+rowNumber.ToString() +" of "+ Excel template
worksheetName +" routing sheet"+".\r"; 2) Not a number or <1 or >96 in case of CS
Excel template
Excel Template "Wave id number is invalid in Routing error Entered value for Specify_WaveID column is
Parser worksheet on row number: " not in defined wave id data range:
+rowNumber.ToString() +" of "+ 1) in case of 4200 Excel template the defined
worksheetName +" routing sheet"+".\r"; wave id data range is: 16-23, 25-32, 34-41,
43-50, 52-59
2) in case of CS Excel template the defined
wave id data range is: 1-96
Excel Template "No Fiber Type provided in All Span Physical error Fiber_Type cell value is blank in
Parser worksheet"+".\r"; AllSpansPhysical sheet.
Excel Template "No Span Distance provided in All Span error Span_Distance cell value is blank in
Parser Physical"+".\r"; AllSpansPhysical sheet.
Excel Template "Invalid span distance provided in All Span error Span_Distance cell value is incorrect as
Parser Physical"+".\r"; defined for AllSpansPhysical sheet:
1) 1-300Km (inclusive of bounds)
2) 1-186 miles (inclusive of bounds)
Excel Template "No Span Loss provided in All Span Physical error Span_Loss cell value is blank in
Parser worksheet"+".\r"; AllSpansPhysical sheet.
Excel Template "Invalid span loss value provided in All Span error Span_Loss cell value is not in the required
Parser Physical worksheet"+".\r"; data range: 0.1-55 (inclusive of bounds) in the
AllSpansPhysical sheet.
Excel Template "No Span Margin value provided in All Span error Span_Margin cell value is blank in
Parser Physical worksheet"+".\r"; AllSpansPhysical sheet.


CND Tool Message
Message Description
Area Type
Excel Template "Invalid Span Margin value provided in All error Span_Margin cell value is not in required data
Parser Span Physical worksheet"+".\r"; range: 0-9 (inclusive of bounds) in
Excel Template "Invalid Span Dispersion value provided in All error Span_Dispersion cell value is not in required
Parser Span Physical worksheet"+".\r"; data range: (-5)-25 (inclusive of bounds) in
Excel Template "No Span Dispersion Slope value provided in error Span_Dispersion_Slope cell value is blank in
Parser All Span Physical worksheet"+".\r"; AllSpansPhysical sheet.
Excel Template "Invalid Span Dispersion Slope value provided error Span_Dispersion cell value is not in required
Parser in All Span Physical worksheet"+".\r"; data range: 0-0.3 (inclusive of bounds) in
Excel Template "No Span Loss Coefficient value provided in error Loss_Coefficient cell value is blank in
Parser All Span Physical worksheet"+".\r"; AllSpansPhysical sheet.
Excel Template "Invalid Span Loss Coefficient value provided error Loss_Coefficient cell value is not in required
Parser in All Span Physical worksheet"+".\r"; data range: 0-0.5 (inclusive of bounds) in
Excel Template "A valid fiber type for span row " + i.ToString() error Entered value for Fiber_Type column in
Parser + " is needed in SpanPhysical SpansPhysical sheet is other than "NDSF, LS,
worksheet"+".\r"; Old LS, TWPlus, TWC, TWRS, Leaf, ELEAF,
DSF, Teralight, or TW Reach."
Excel Template "A valid span loss 1-55 dB for span row " + error Entered value for Span_Loss column in
Parser i.ToString() + " is needed in SpanPhysical SpansPhysical sheet is not in valid range: 0.1-
worksheet"+".\r"; 55.
Excel Template "Span margin must be a value between 0-9 dB error Entered value for Span_Margin column in
Parser for span row " + i.ToString() + " is needed in SpansPhysical sheet is not in valid range: 0-9.
SpanPhysical worksheet"+".\r";
Excel Template "Duplicate span link found for row " + error Link name in SpansPhysical sheet is not the
Parser i.ToString() + " is needed in SpanPhysical same for the set of site-node pair that has
worksheet"+".\r"; been previously used for span information
between a node-node pair.
Excel Template "Number of spans in link sheet for Link<" + error Value entered for number of spans in Links
Parser linkList[i].Attributes["nodeA"].Value + "," + sheet and corresponding number of rows in
linkList[i].Attributes["nodeB"].Value + "> does SpansPhysical sheet do not match.
not match with number of spans entered in the
Span Physical sheet.";
Excel Template Incorrect network module entered for "+ error Entered value for Network_Module column is
Parser enumChannelType.ToString() +" channel type other than:
in the routing sheet"; 1) OPT-XX-D-U,OPT-XX-D-UL,F10-A/T-90-
noDT,F10-A/T-90-TN,F10-A/T-90-XX,F10-A/T-
90-DT,F10-A/T-90-TN-DT,F10-A/T-90-XX-
DT,F10-A/T-90-DT-noDT,F10-T-90-noDT,F10-
T-90-DT,F10-T-90-TN-DT,F10-T-90-XX-
DT,FC4-T-90-TN-DT,FC4-T-90-noDT,FC4-T-
90-DT or FC4-T-90-XX-DT in any routing
sheet of 4200 Excel template.
2) 10G UFEC, G.709 C BAND Tunable, G.709
BAND Tunable, C BAND Tunable + BAND
Tunable, BAND Tunable + C BAND Tunable in
any routing sheet of CS Excel template.
Excel Template Nodes worksheet not found. error Nodes sheet not present in Excel template file.
Parser


CND Tool Message
Message Description
Area Type
Excel Template Links worksheet not found. error Links sheet not present in Excel template file.
Parser
Excel Template Excel document cannot contain routing error 4200 Excel template contains CS routing
Parser worksheets for both CN4200 and Corestream sheets or CS template contains 4200 routing
Network. sheets.
Excel Template Node name: " + nodeName + " mentioned in error Node name mentioned in Links sheet not
Parser link sheet not found in the nodes sheet of input found in Nodes sheet of input file.
file. Unable to create network.
Excel Template "Unknown channel type in error For old Excel template, channel type entered
Parser "+worksheetName+" routing sheet.\r"; is incorrect.
Excel Template Error processing span physical sheet. error Exception occurs in reading sheet.
Parser
Excel Template Could not process All Spans Physical Tab. error No span information found for a link.
Parser
Excel Template Could not process Spans Physical Worksheet. error Either AllSpansPhysical sheet not present in
Parser It is either not present or misformatted. Excel template file or not in required format.
Excel Template "Nodes not found!\r"; error Either an unfilled template file is opened in
Parser CND or Nodes sheet not filled.
Excel Template "There should be at least 2 nodes in the error Nodes sheet contains only one node name
Parser network defined in nodes worksheet!\r"; listed.
Excel Template "A node with name Node found at row number error Cell value entered for node name in Nodes
Parser "+ i +". Node name cannot be Node.\r"; sheet is "Node."
Excel Template "Links not found.\r"; error Either an unfilled template file is opened in
Parser CND or Links sheet not filled.
Excel Template "Link name: '"+strArray[4]+"'"+"contain an error Entered cell value for link name contains
Parser invalid character. \nOnly alphanumeric special characters other than A-Z, 0-9,
characters ,underscore '_', spaces and dash '-' hyphen, and underscore.
allowed.\r";
Excel Template Excel document must contain at least one error No routing sheet present.
Parser routings worksheet.
Excel Template Excel Input file does not contain the required error All required sheets are not present in template
Parser sheets. file.
Excel Template The NODES sheet could not be found. error Nodes sheet not present in template.
Parser
Excel Template The NODES sheet shall contain the column error Nodes sheet does not contain column
Parser headings NODE_NAME, NODE_LOC_X, headings NODE_NAME, NODE_LOC_X,
NODE_LOC_Y, and DEG in row number 1 of NODE_LOC_Y, and DEG in row number 1 of
the columns A to D strictly in the same order. columns A to D in same order.
Excel Template The LINKS sheet could not be found. error Links sheet not present in template.
Parser
Excel Template The LINKS sheet shall contain the column error Links sheet does not contain column headings
Parser headings FiberNodeA, FiberNodeB, FiberNodeA, FiberNodeB, LinkLength (km),
LinkLength (km), Spans, Link Name and the Spans, Link Name and FiberOPSprotection in
FiberOPSprotection in row number 1 of the row number 1 of columns A to F in same order.
columns A to F strictly in the same order.
Excel Template The Spansphysical sheet could not be found. error SpansPhysical sheet not present in template.
Parser


CND Tool Message
Message Description
Area Type
Excel Template The Spansphysical sheet shall contain the error SpansPhysical sheet does not contain column
Parser column headings FiberNodeA, FiberNodeB, headings: FiberNodeA, FiberNodeB,
Span_Fiber_Type, Span_Distance, Span_Fiber_Type, Span_Distance,
Span_Loss, Span_Margin,Span_Dispersion Span_Loss, Span_Margin,Span_Dispersion
and Span_dispersion_Slope in row number 1 and Span_dispersion_Slope in row number 1
of the columns A to H strictly in the same order of columns A to H in same order.
Excel Template The AllSpansphysical sheet could not be error AllSpansPhysical sheet not present in
Parser found. template.
Excel Template The AllSpansphysical sheet shall contain the error AllSpansPhysical sheet does not contain
Parser column headings column headings: All_Span_Fiber_Type,
All_Span_Fiber_Type,All_Span_Distance,All_ All_Span_Distance, All_Span_Loss,
Span_Loss,All_Span_Margin,All_Span_Disper All_Span_Margin, All_Span_Dispersion,
sion, All_Span_Dispersion_Slope,Version and All_Span_Dispersion_Slope, Version, and
Network_Type strictly in the same order from Network_Type in same order from row 1 to 8
row 1 to row 8 for column A. for column A.
Excel Template The invalid network type in AllSpansphysical error Network_Type cell value is neither "CN4200"
Parser sheet. nor "CoreStream."
Excel Template "The last channel"+" of "+ worksheetName +" error Channels cell value not empty in primary path
Parser routing sheet"+" does not contain row but empty in secondary path row for same
corresponding secondary channel.\r"; demand name.
Excel Template All Span Physical worksheet is missing row error Row headers in AllSpansPhysical sheet
Parser headers missing.
Excel Template "Non continuous path specified for span row " error No link/span exists between pair of NodeA -
Parser + i.ToString() + " in SpanPhysical Node B values.
worksheet."+".\r";
Excel Template "Link<" + linkList[i].Attributes["nodeA"].Value + error For a specific link in Links sheet,
Parser "," + linkList[i].Attributes["nodeB"].Value + "> corresponding span row entries in
has no details present in the Span Physical SpansPhysical sheet missing.
sheet.";
Excel Template Could not process All Spans Physical Tab. error Link entered in SpansPhysical sheet not valid
Parser Link<" + linkList[i].Attributes["nodeB"].Value + link as entered in Links sheet.
"_" + linkList[i].Attributes["nodeA"].Value + ">
referenced in Span Physical tab not found.
Excel Template "Duplicate Node Names found: " + strArray[0] error Node name repeats in Nodes sheet.
Parser + ".\r";
Excel Template "Node degree for node: " + error Degree cell value for node in Nodes sheet
Parser strArray[0].ToString() + " greater than 4.\r"; greater than 4.
Excel Template "A link already exists in links worksheet error More than one row entry present in Links
Parser between nodes: " + strArray[0]+" and "+ sheet with identical cell value entries for
strArray[1] + ".\r"; FiberNodeA and FiberNodeB. (Between any
given set of nodes there can exist only one
link.)
Excel Template "No hop number provided in Routing error Hops cell value for valid row entry empty in
Parser worksheet for traffic row: " + any routing sheet.
rowNumber.ToString()+" of "+ worksheetName
+" routing sheet"+".\r";
Excel Template "A valid distance 1-300 km for span row " + error Span length cell value in SpansPhysical sheet
Parser i.ToString() + " is needed in SpanPhysical not in valid data range: 1-300 Km (inclusive of
worksheet"+".\r"; bounds).
Excel Template "A valid distance 1-186 miles for span row " + error Span length cell value in the SpansPhysical
Parser i.ToString() + " is needed in SpanPhysical sheet not in valid data range: 1-186 miles
worksheet"+".\r"; (inclusive of bounds).


CND Tool Message
Message Description
Area Type
Excel Template "Error in intermediate/ola site name in error Mismatch in number of sites entered in
Parser spanphysical sheet for Link:" + SpansPhysical sheet due to name.
linkList[i].Attributes["name"].Value + ".";
Excel Template Network module not entered for a row error Network module cell value blank in any routing
Parser sheet.
Excel Template "The distance for link row number: " + error Link length cell value in Links sheet not in valid
Parser i.ToString() + " is out of bounds: 1 to 9999 km data range: 1-9999 Km (inclusive of bounds).
in Links worksheet\r";
Excel Template "The distance for link row number: " + error Link length cell value in Links sheet not in valid
Parser i.ToString() + " is out of bounds: 1 to 6214 data range: 1-6214 miles (inclusive of
miles in Links worksheet\r"; bounds).
Excel Template "No duplicate link names allowed in links error Link name entered in row in Links sheet
Parser worksheet: " + strArray[4] + " repeated in another row in Links sheet.
Excel Template "Hop count '" + strArray[5] + "' is invalid in error Hops cell value not in valid data rage: 1-50
Parser Routing worksheet on row number: " (inclusive of bounds).
+rowNumber.ToString() +" of "+
Excel Template "Invalid protection in Routing worksheet: " + error Protection type not valid for routing sheet
Parser strArray[7] + " is not a valid protection type "+" based on protected or unprotected status.
in "+ worksheetName +" routing sheet"+".\r";
Excel Template "Number of wave ids entered are more than error Number of wave ids mentioned in
Parser the number of channels for traffic row: " + Specify_WaveIDs cell greater than value
rowNumber.ToString()+" in "+ worksheetName entered for Channels cell.
Excel Template "The starting node name in NodeA column, error Starting node name in NodeA column, ending
Parser ending node name in NodeB column ,Channel node name in NodeB column, Channel count
count and Protection Type entered should be and Protection Type entered are not equal for
same for both Primary and Secondary paths of both Primary and Secondary paths for same
the same Demand name: " + Demand name.
strArray[0].Trim()+" in "+ worksheetName +"
routing sheet"+".\r";
Excel Template "The Demand name entered should be same error Demand name entered not same for both
Parser for both Primary and Secondary paths, row Primary and Secondary paths, row number.
number: " + rowNumber.ToString()+" in "+
Excel Template "Number of hops for traffic row: " + error Cell value for Hops not in defined data range:
Parser rowNumber.ToString() + " is out of range 1-50" 1-50 for any routing sheet.
+" of "+ worksheetName +" routing
sheet"+".\r";
Excel Template "The last node name entered for defining the error Last node name entered for defining the path
Parser path is not same as node name entered in is not equal to node name entered in NodeB
NodeB column for row column.
number:"+rowNumber.ToString()+" of "+
Excel Template "Channel count for link:"+strArray[j].Trim()+" error Total number of channels in link greater than
Parser exceeding the max limit"+" on "+ 40.
Excel Template "WaveIds repeating in demands for error WaveIDs entered in row in any routing sheet
Parser link:"+strArray[j].Trim()+" on "+ not unique.


CND Tool Message
Message Description
Area Type
Excel Template "Channel count exceeding and WaveIds error Specify_WaveIDs cell value has repeated
Parser repeating for demands in a wave id numbers so that cell contains more
link:"+strArray[j].Trim()+" on "+ wave ids than value entered for number of
worksheetName +" routing sheet"+".\r"; channels.
Excel Template "Invalid link "+strArray[j]+" for row number:"+ error Link name entered in LinkX column on any
Parser rowNumber.ToString()+" in column routing sheet not found in Link_name column
number:"+j.ToString()+" on "+ worksheetName in Links sheet.
Excel Template "Link Names cannot repeat for the same error Link name entered in LinkX column is
Parser demand, row:" + rowNumber.ToString()+" of "+ repeated for a given traffic in any routing
worksheetName +" routing sheet"+".\r"; sheet.
Excel Template "Primary and Protection paths shall have to be error Primary and Protection paths are not diverse
Parser diverse for the same for same demand although sharing common
demand:"+strArray[0].ToString()+""+" in "+ link.
Excel Template "No valid link exists between the set of nodes error No valid link exists between set of nodes in
Parser "+strArray[j-1].Trim()+" and adjacent NodeX columns in any routing sheet.
"+strArray[j+1].Trim()+" specified in demand
row:" + rowNumber.ToString()+" of "+
Excel Template "Invalid link name specified between the set of error Invalid link name entered between set of
Parser nodes "+strArray[j-1].Trim()+" and nodes in adjacent NodeX columns in any
"+strArray[j+1].Trim()+" specified in demand routing sheet.
Excel Template "Node '" + strArray[j] + "' referenced in routing error Node Name entered in the NodeX column not
Parser worksheet is not found in the Nodes worksheet found in the Nodes sheet in any routing sheet.
on row number: " +rowNumber.ToString() +" of
"+ worksheetName +" routing sheet"+".\r";
Excel Template "Node Names cannot repeat for the same error Node name entered in any NodeX column
Parser demand, row:" + rowNumber.ToString()+" of "+ repeated in same row in any routing sheet.
Excel Template "The first node name entered for defining the error Node name entered in any Node1 column
Parser path is not same as node name entered in does not match cell value of NodeA in same
NodeA column for row row in any routing sheet.
number:"+rowNumber.ToString()+" of "+
Excel Template "Number of hops is incorrect for traffic row: " + error Cell value for Hops not in defined data range:
Parser rowNumber.ToString()+" of "+ worksheetName 1-50 for any routing sheet.
Excel Template "Incorrect Path Type entered in the routing error Path type cell value is neither "primary" nor
Parser sheet for traffic row: " + "secondary" in any routing sheet.
rowNumber.ToString()+" in "+ worksheetName
Excel Template "The CLO - ETR channel type combination is error Missing ETR for CLO channel or vice versa.
Parser missing in the routing sheet for traffic row: " +
Excel Template "Wave id '"+tempWaveIDs[idCount].Trim()+"' error WaveID entered in row in any routing sheet is
Parser found repeating for traffic row: " + not unique.


CND Tool Message
Message Description
Area Type
Excel Template "Unknown wave id error Entered value for Specify_WaveID column not
Parser '"+tempWaveIDs[idCount].Trim()+"' found for in defined wave id data range:
traffic row: " + rowNumber.ToString()+" in "+ 1) for 4200 Excel template, defined wave id
worksheetName +" routing sheet"+".\r"; data range: 16-23, 25-32, 34-41, 43-50, 52-59.
2) For CS Excel template, defined wave id
data range: 1-9ng
Excel Template "Primary and Protection Paths cannot be same error Path type is same for rows having same
Parser for the same demand name.
demand:"+strArray[0].ToString()+""+" in "+
Excel Template "Invalid link name specified between the set of error Invalid link name entered between set of
Parser nodes "+strArray[j-1].Trim()+" and nodes in adjacent NodeX columns in any
"+strArray[j+1].Trim()+" specified in demand routing sheet.
Other This file is already opened by other error
application.
Other Excel file having incorrect format error
Other Not a valid File error
Other Document is already opened warning
Other No Document present to design warning
Other Network was previously designed as a warning
CN4200 network and cannot be converted to a
CoreStream network. Please select the Design
CN 4200 networks option.
Other No Document present warning
Other Can not validate Empty Document warning
Other Lightpaths can only be added from Network warning
View.\n Would you like go to Network View?
Other You need to load a valid excel price workbook warning
Other No network design found. Please open or warning
create a network.
Other Cannot design empty document warning
Other Network was previously designed as a warning
CoreStream network and cannot be converted
to a 4200 network. Please select the Design
CoreStream network option.
Other Unable to load CND User Guide, as the file warning
CNDUserGuide.pdf is not available
Other Unable to load CND User Guide, Acrobat warning
Reader is not installed
Other Could not find "+templateFileWithAbsPath+", warning
Please contact your Application administrator
for the correct Settings.
Other Could not initialize application: warning
Other Document is already opened, Can not warning
overwrite the file.
Other File " + path + " already exists.\n Do you want warning
to replace it


CND Tool Message
Message Description
Area Type
Other Cannot save Empty Design. warning
Other Kernel error: " + e.Message + " " + warning
e.StackTrace
Other No network design found. Please open or question
create a network
Other To add a new lightpath, hold down the control information
key and click on the starting and ending nodes.
Then follow the instructions. \nIf the nodes you
selected are already the endpoints of a
lightpath, the lightpath will be displayed.
Other Lightpaths can only be added from Network warning
View.\n Would you like go to Network View?
Other You need to load a valid excel price workbook. warning
Other No network design found. Please open or warning
create a network.
Other Cannot design empty document warning
Other Unable to load CND User Guide, as the file warning
CNDUserGuide.pdf is not available.
Other Unable to load CND User Guide, Acrobat warning
Reader is not installed.
Other Could not find "+templateFileWithAbsPath+", warning
Please contact your Application administrator
for the correct Settings.
Other Could not initialize application: warning
Other Document is already opened, Can not warning
overwrite the file.
Other File " + path + " already exists.\n Do you want warning
to replace it
Other Cannot save Empty Design. warning
Other Kernel error: " + e.Message + " " + warning
e.StackTrace
Other Are you sure want to exit? warning Displays when user closes application.
Table 7-2. 4200 GUI Messages

Message
CND Tool Area Message Description
Type
Network design This network was designed using an older error
CoreStream network template and cannot be
converted to a 4200 network. Please select the
Design CoreStream network option
Network design No Document present to design error

Table 7-2. 4200 GUI Messages (Continued)

Message
Type
Network design This network was designed as Fixed OADM, error
“Changing the OADM Type will remove all the
force edits.” Click “OK”:: If you still want to continue
and remove all forced edits, else Click “Cancel”::
To Revert and save this file with some other name.
To remove all force edits then press “Continue”
Network design This network was not designed as Fixed OADM, error
“Changing the OADM Type will remove all the
force edits.” Click “OK”:: If you still want to continue
and remove all forced edits, else Click “Cancel”::
To Revert and save this file with some other name.
To remove all force edits then press “Continue”
Network design At least one setting in Amplifier must be selected error
Network design Network cannot be designed as VMUX or error
ROADM, since Tx DCM has been forced
Network design At most two setting in Amplifier can be selected error
Network design At least one setting in Wavelength must be error
selected
Network design At most two setting in Wavelength can be selected error
Network design You cannot select both 200 Ghz and 100 Ghz error
DWDM
Network design At least one setting in Design Threshold must be error
selected
Network design At most one setting in Design Threshold can be error
selected
Network design 'Clear Forced Edits' is selected. Do you wish to warning
clear this option?
Network design ‘ETR/CLO’ services are supported by Fixed Filter error
Designs only’
Network design ‘Fiber OPS protected links are supported by Fixed error
Filter Designs only’
Network design This network contains LS or Old LS or DSF fiber warning
links.
Network design The working and protect fibers in the link must warning
have matching fiber loss and fiber total dispersion.
Dissimilar fiber links (for fiber type, length, loss,
dispersion) are not supported.
Network design Amplifier selection does not match with OADM error
selection
Network design All previous VMUX node configuration operations error Message displays when user modifies any
and edit filter operations will be lost light path in a network in which user had
previously done edit filter as well as VMUX
node configurations.
Network design This configuration is invalid as one of the degrees error Message displays when user tries to force
have add/drop in more than 4 bands a 2 degree node as VMUX OADM and any
of the degrees have add/drop in more than
4 bands.


Message
Type
Network design All previous force VMUX operations done on the warning Message displays when user had
nodes traversed by this light path will be lost performed force VMUX operations on any
of the nodes traversed by the light path.
‘force_port_type’ and
‘force_node_port_type’ flags at all such
nodes will be cleared by GUI.
Network design Node X can not be forced as VMUX as the node error Message displays when user forces a
add/drop capacity option is growth multi degree node with ’16 channel add/
drop maximum’ or ‘40 channel add/drop
maximum’ add/drop capacity option as
VMUX. This message shall be thrown by
GUI instead of displaying in message area
if user forces the NE type through node
view.
Network design This node can not be forced as VMUX as one of error Message displays when user forces
the node degree have multiple pass through VMUX as NE type for a 3 or 4 degree node
connections with one of the ports having multiple pass
through connections.
Network design This node can not be forced as VMUX as one of error Message displays when user forces
the OADM node degree has add/drop channels in VMUX as NE type for a degree 3 or 4 node
more than 4 bands whose one of the ports with pass through
connection has add/drop in more than 4
bands.
Network design VMUX terminal can’t be forced at non VMUX error Message displays when user clicks on a
nodes non VMUX node.
Network design VMUX terminal can’t be forced as there are no error Message displays when user clicks on a
VMUX terminal degrees on the selected VMUX VMUX node without VMUX terminal
node degrees.
Network design Please check at least one option "Save warning Message displays when user selects
Preferences in Current Design" or "Save "Default Preferences" in Load Preferences
Preferences Globally" and does not persist the values. Check at
least one option.
Network design Either Raman, OAV-VS-U-C (R5.0) or OAV-VS-HP warning Message displays when pressing OK on
(R6.0) is forced. Please select OAV-VS-U-C (R5.0) design screen.
or/and OAV-VS-HP (R6.0) from Amp Selection
Network design OAV-0S-U-C is forced. Please De-select OAV-VS- warning Message displays when pressing OK on
U-C (R5.0) and OAV-VS-HP (R6.0) from Amp design screen.
Selection
Network design Please select at least one Tx/Rx Amp option in warning Message displays when pressing OK on
DCM, Amplifier, Raman and OSC settings design screen.
Network design Mid Stage Loss Borrowing can only be selected if warning Message displays when selecting Mid
OAV-VS-U-C (R5.0) or OAV-VS-HP (6.0) is stage Loss Borrowing.
selected
Network design Changing the OADM setting to ROADM will clear error Message displays when changing the
all Tx force Amplifier Edits and Edit Filter options OADM selection to ROADM.
on all unforced VMUX and Mix-ROADM nodes and
Regen sites.
Network design Changing the OADM setting to VMUX will clear all error Message displays when changing the
Tx force Amplifier Edits and Edit Filter options on OADM selection to VMUX.
all unforced MixROADM nodes and Regen sites.


Message
Type
Network design Changing the OADM setting to MixROADM will error Message displays when changing the
clear all Tx force Amplifier Edits and Edit Filter OADM selection to Mixed-ROADM.
options on all unforced VMUX and Regen sites.
Network design This option can be selected only if OAV-VS-U-C error Message displays when selecting Mid
(R5.0) or OAV-VS-HP (6.0) is selected stage Loss Borrowing.
Network design Please Select one Amps in Rx Fixed Filter error Message displays when pressing OK on
design screen.
Network design Please Select one Amps in Tx Fixed Filter error Message displays when pressing OK on
Edit amps screen.
Network design OAV-0S-U-C is forced. Please De-select OAV-VS- error Message displays when selecting R5 or
U-C (R5.0) and OAV-VS-HP (R6.0) R6 amps.
Network design Please Select one Amps in Rx VMUX/ROADM error Message displays when pressing OK on
Edit amps screen.
Network design Please Select one Amps in Tx OLA/VMUX error Message displays when pressing OK on
Edit amps screen.
Network design Please Select one Amps in Tx ROADM error Message displays when pressing OK on
Edit amps screen.
Network design Please Enter value of Raman Threshold between error Message displays when entering value for
17 to 35 Raman threshold.
Network design Please Enter Numeric value of Raman Threshold error Message displays when entering value for
between 17 to 35 Raman threshold.
Network design OAV-0S-U-C is forced, Do you want to clear these error Message displays when selecting OAV-
force flags to use OAV-VS-HP? 0S-U-C.
Network design Either Raman, OAV-VS-U-C (R5.0) or OAV-VS-HP error Message displays when selecting OAV-
(R6.0) is forced, do you want to clear these force 0S-U-C.
flags to use OAV-0S-U-C?
force flags to use OAV-VS-U-C? 0S-U-C.
force flags to use Raman? 0S-U-C.
Network design Channel Q values on DSF fiber are sensitive to warning
fiber dispersion values. Best results will be
obtained using actual measured dispersion.The
affected links are :
Network design The fiber dispersion parameters of some of spans warning Message displays if the Dispersion or
in the following links have been manually modified Dispersion Slope of any fiber type is out of
to more than +-25% of normal value :{link names +/-25% of its default value.
separated by comma}
Network design This design is exposed to performance issues as warning Message displays if the lightpath is
lightpaths traverse more than three contiguous passing through the 4 consecutive VMUX
VMUX nodes. Further action is required. It is nodes.
recommended that OCM be added to VMUX
nodes as appropriate in order to clear this
warning.The affected lightpaths are: {light path
names separated by comma}
Network design One or more OCM cards have been manually warning Message displays if any lightpath is
placed in this design to avoid performance issues passing though the 4 consecutive VMUX
on lightpaths traversing more than three node but due to OCM the VMUX node
contiguous VMUX nodes. This design must also counter is resetting.
be deployed with system software release 6.1.1 or
above for the solution to be functional.


Message
Type
Network design Channel Q values on DSF fiber are sensitive to warning Message displays if the network has been
fiber dispersion values. Best results will be designed with NL validation or NL
obtained using actual measured dispersion.The optimization option and contains DSF fiber
affected links are:{link names separated by span with non zero dispersion coefficient.
comma}
Network design User needs to perform Non-Linear Validation/ warning Message displays if the network is
Optimization before deployment designed with “Linear Optimization” as
network type and “Deployment or Mean
Deployment” design threshold.
Network design Exception thrown while showing network design error Message displays while showing the
report in info panel. Error :{ Run Time Error Msg} summary information in message area, if
any run time exception occurred.
Network design This fixed filter design contains release 5.0 or warning Message displays if fixed filter design
above amps and OSCs hence it is strongly contains R5.0 or above amps and OSCs
recommended that either the 'Optimized' or 'RS then it is strongly recommended that either
Only' chassis style is used.If 'Classic Only' is the “Optimized” or “RS Only” chassis style
selected then please ensure that all amps and is used. If “Classic Only” is selected then
OSCs in interconnected degrees are placed within please ensure that all amps and OSCs in
the same Classic chassis. interconnected degrees are placed within
the same Classic chassis. De-select
release 5 and 6 amps for design option
window.
Network design The OPT-EXET SFP is not supported until System warning If OPT-EXET is selected in Service card
Software Release 7.0. config.
Network design Please remove the OTU1 and/or OTU1(ISC2/ error
ISC3c) channels traversing the following links as
OTU3P channels are present: (Link names 1 in
each line)
Network Design The '40 Channels' option for Planned Fiber warning
Summary Capacity only guarantees amplifier power levels
that will allow for 40 channels per span. This option
does not guarantee that existing 10G and/or 40G
lightpaths will continue to pass if additional
channels are added due to increased interference
between 10G and 40G and the potential need for
lower launch power levels.
Network Design The OSC function in link : (link names) will not warning
Summary work as the span loss exceeds the OSC link
budget of 35 dB for R5 MAN-0S-CP and OAV-VS-
U-C/OAV-VS-HP. For the OSC to work normally,
use MAN-OS-CP-4/OAV-VS-U-C-4/OAV-VS-HP-4
or lower PAD variants.
budget of 35 dB for R5 MAN-OS-CP and OAV-VS-
use MAN-OS-CP-2/OAV-VS-U-C-2/OAV-VS-HP-2
or lower PAD variants.
budget of 35 dB for R5 MAN-OS-CP and OAV-VS-
use MAN-OS-CP/OAV-VS-U-C/OAV-VS-HP PAD
variants.


Message
Type
Network Design All 4200 designs containing 40G wavelengths warning
Summary must be reviewed by OPNET prior to bid
submission or network deployment. Please rerun
the design with the "Generate 40G Non-Linear Log
Files" design option enabled, then generate a 40G
Non-Linear Report for OPNET analysis.
Network Design 10G and 40G Non-Linear Validation/Optimization warning
Summary must be performed
Network Design 10G Non-Linear Validation/Optimization must be warning
Summary performed
Link view Invalid Distance: The length of the lightpath error

containing ETR AND CLO channels should be less
than 40km.
Link view Invalid Loss: The total loss of the lightpath error
containing ETR AND CLO should be less than
10dB/Km.
Link view Invalid Distance: The length of the lightpath error
containing OTU1(ISC2/ISC3) should be less than
40km.
Link view Invalid Loss: The total loss of the lightpath error
containing OTU1(ISC2/ISC3) should be less than
10dB/Km.
Link view Cannot insert span. Matching Site not found. error
Link view With this increase in link length, the total length of warning
the lightpath is >100 for the lightpaths: LP1,
LP2...For the lightpaths with OTU1 (ISC2/ISC3c)
services, total length of the lightpath cannot be
>100.
Link view Span loss for a span having the RAMAN cannot warning
exceed the OSC budget.
Link view An amp site on link [name] has been upgraded to a warning
regen site in order to enable future growth to 40
channels.
Link view Raman can’t be forced as OSC function is not error Message displays when trying to force
available with >35dB span loss Raman through Link View when loss is >
35dB.
Link view Raman cannot be forced in this span as No OSC is error Message displays when trying to force
forced in this link Raman when No OSC is forced in the link.
Remove Force No OSC.
Link view Raman can’t be forced as OAF-00-1-C or No Amp error Message displays when trying to force
has been forced in the receive uniport Raman when OAF/No Amp has been
forced in the uniport. Remove Force OAF/
No Amp from the uniport.
Link view OAV-VS-U-C(R5.0)/OAV-VS-HP(R6.0) or Raman error Message displays when trying to force
can’t be forced as OAV-0S-U-C has been forced in OAV-VS-U-C(R5.0)/OAV-VS-HP(R6.0) or
the network. Do you want to clear forced OAV-0S- Raman when OAV-0S-U-C has been
U-C in the network? forced in the network. Click Yes to
proceed.


Message
Type
Link view OAF-00-1-C or No Amp can’t be forced as Raman error Message displays when trying to force
has been forced in this uniport OAF-00-1-C or No Amp when Raman has
been forced in this uniport. Remove Force
Raman.
Link view Warning: The Raman performance may not be warning Message displays when trying to force
adequate as the span length is less than 40Km Raman if span length is < 40Km.
Link view Warning: Raman amplification should not be used warning Message displays when trying to force
on this span as the loss coefficient is greater than Raman if the span loss per length is less
0.25 dB/Km. than 0.25db/Km.
Link view Warning: If Raman is forced on spans < 20 dB warning Message displays when trying to force
then the performance will not improve with the Raman if the span loss is less than 20dB.
Raman amplifier
Link view OAV-0S-U-C can’t be forced as OAV-VS-U- error Message displays when trying to force
C(R5.0)/OAV-VS-HP(R6.0) or Raman has been OAV-0S-U-C when OAV-VS-U-C(R5.0)/
forced in the network.Do you want to clear OAV- OAV-VS-HP(R6.0) or Raman has been
VS-U-C(R5.0)/OAV-VS-HP(R6.0) and Raman forced in the network. Click Yes to
amps forced operations in the network? proceed.
Link view No OSC can’t be forced as Raman is present in error Message displays when trying to force No
this link OSC when Raman is present in this link.
Force No Raman.
Link view OCM cannot be placed as this is an amp site with error Message displays when trying to force
no add/drop. OCM on amp sites.
Link view Please select DCM size error DCM type is selected but DCM size is not
selected. Select DCM size.
Link view "OAV-VS-U-C (R5.0)/OAV-VS-HP (R6.0) or warning
Raman (R6.1) can’t be forced as OAV-0S-U-C has
been forced in the network.
Do you want to clear forced OAV-0S-U-C in the
network?"
Link view "OAV-0S-U-C can’t be forced as OAV-VS-U-C warning
(R5.0)/OAV-VS-HP (R6.0) or Raman (R6.1) has
been forced in the network.
Do you want to clear OAV-VS-U-C (R5.0)/OAV-VS-
HP (R6.0) and Raman (R6.1) amps forced
operations in the network?"
Link view OAF-00-1-C/No Amp is not valid as Raman is error Message displays when user tries to force
forced. OAF-00-1-C or No Amp when Raman has
been forced in this uniport. Remove Force
Raman.
Link view No OSC can’t be forced as Raman has been error Message displays when user tries to force
forced in the receive uniport on the link. No OSC when Raman is present in this
link. Force No Raman
Link view Raman (R6.1) can’t be forced as OAF-00-1-C or error Message displays when user tries to force
No Amp has been forced in the receive uniport. Raman when OAF/No Amp has been
forced in the uniport. Remove Force OAF/
No Amp from the uniport
Link view Raman (R6.1) can’t be forced as No OSC has error Message displays when user tries to force
been forced on the link. Raman when No OSC is forced in the link.
Remove Force No OSC
Link view Warning: Raman can’t be forced as OSC function warning Message displays when user tries to force
is not available with > 35dB span loss. Raman through link view when loss is
greater than 35dB.


Message
Type
Link view Warning: Raman performance may not be warning Message displays when user tries to force
adequate with span length less than 40 km Raman if span length is less than 40 Km.
Link view "Raman (R6.1) can’t be forced as OAV-0S-U-C warning Message displays when user tries to force
has been forced in the network. Raman when OAV-0S-U-C has been
Do you want to clear forced OAV-0S-U-C in the forced in the network.
network?"
Link view allowed value for one or more 40G lightpaths error
passing through this link:{0}
- 300Km for the 40G network module 'eDC40G
Metro (O-Shelf)'{1}
Regional (O-Shelf)/ RS-F40M (Standard)'{2}
Either adjust the span lengths or force a Regen for
the impacted 40G lightpaths given below:
Node view You can not edit force NE type to VMUX for more error
than 2 node degree
Node view OSC can not be forced before a kernel run error
Node view User is not allowed to force an amplifier at a node error
port supporting ETR or CLO channels.
Node view DCM modules are not allowed at node ports error
supporting ETR or CLO services.
Node view You should perform Network Design before forcing error
Add Drop Capacity.
Node view This change will not persist if there are lightpath error
changes later.
Node view This port is already having 5-band filter. error
Node view Use 5-band filter configuration is not allowed. error
Node view Please select any edit filter options error
Node view Node X can not be forced as VMUX as the node error If user forces a multi degree node with “16
add/drop capacity option is growth channel add/drop maximum” or “40
channel add/drop maximum” add/drop
capacity option as VMUX
Node view Changes will not persist if there are light-path error User uses “VMUX Edit Filter” for the first
changes later time
Node view Any previous VMUX filter edit operations will be error User adds or deletes channels to the
lost existing lightpath
Node view This option is valid for VMUX Terminal Port only error If the node port type is not VMUX terminal
and user selects change configuration
option
Node view This option is valid up to 4 VMUX filters error After splitting the VMUX8, the cascaded
filter crosses beyond the 4 VMUX filters
Node view Concatenated VMUX terminal is not allowed at this error If user tries to change the configuration
node port as the add/drop channels occupy more from VMUX terminal BS5 to Concatenated
than 4 bands VMUX terminal and the added channels
cover more than 4 bands.
Node view The force NE options are available only for error The force NE options are available only for
CN4200 Non fixed OADM designs. 4200 non fixed filter designs. Choose a
non-fixed filter network.


Message
Type
Node view This will convert entire network to CN4200 warning If the network type has not been defined,
network. Are you sure you want to convert? then this will convert the network into a
4200 network.
Node view No document present error Force NE cannot be performed with an
empty document. Open any existing
document or create a new document with
at least 1 node.
Node view All Edit Filter and Force Amp operations will be warning All Edit Filter operations and/or Force Amp
cleared on ["NodeName"]. Do you want to operations for the given node will be
continue? cleared.
Node view Node: "NodeName" cannot be forced as VMUX as error A node provisioned with Add/Drop
the node add/drop capacity option is forced as 16/ capacity as 16/40 channel growth cannot
40 channel growth. be a VMUX node. Force this node as
some other OADM type or change the
add/drop capacity.
Node view Node: "NodeName" cannot be forced as VMUX as error Node with degree more than 2 cannot be a
the node degree is more than 2. VMUX node. Force this node as some
other OADM type or change the degree of
the node.
Node view Cannot perform edit filter operation as NE Type warning
has been modified for at least one the degree
belonging this node.
Node view The Edit Filter Operations on all node degrees will warning On changing the NE types, the Edit Filter
be cleared. Do you want to continue? operations may be lost.
Node view Node :"NodeName" cannot be forced as VMUX as error A node with an add/drop channel in more
one of the OADM node degree has add/drop than 4 bands cannot be a VMUX node.
channels in more than 4 bands. Force this node as some other OADM
type.
Node view This will clear all edit filter operations in current warning Message displays when user clicks on
session for this port <port number>. Do you want "Revert Current Changes" button. If user
to continue? clicks "OK," the changes made for the
session will be undone.
Node view This will clear all previous edit filter operations on warning Message displays when user clicks on
both the transparent ports. Do you want to "Clear All Edit Filter Operations" button. If
continue? user clicks "OK," the edit filter flags will
clear. After a kernel run, the kernel will
place the original filters.
Node view This degree is already having 5-band filter. error Message displays when the filter
placement is a BS5 configuration, and
user selects BS5 configuration. Do not
select the “Use BS5” option when the
configuration is BS5.
Node view This operation is not allowed because it will error Message displays when the user selects
convert all MPT channels into CPT. "Change VMUX Terminal Configuration"
and the degree has MPT pass-through. Do
not select "Change VMUX Terminal
Configuration" when there is an MPT
pass-through.
Node view Concatenated VMUX terminal is not allowed at this error Message displays when the user wants to
node degree as the add/drop channels occupy change BS5 preferred VMUX Terminal to
more than 4 bands. Concatenated VMUX Terminal, and the
number of VMUX filters exceeds four.


Message
Type
Light Path view/ Not a CN4200 Network error
wizard
Light Path view/ Can not Add 1+1 port protection or OPS port error
wizard protection to OTU2 channels
Light Path view/ Specify wave selection mismatch between primary error
wizard and secondary path: Number of YN-channels for
service xxx differ
wizard and secondary path: Number of Y1-channels for
service xxx differ
Light Path view/ The unequal number of channels that are entered information
wizard for ETR and CLO services will be auto assigned
by the kernel
Light Path view/ Equal number of channels should be selected for warning
wizard CLO service and YearType
Light Path view/ Invalid OPS port protection : No channels with error
wizard same waveID are available in primary and
secondary paths.
Light Path view/ Invalid Protection type:OPS Port Protection will not error
wizard support Fiber OPS.
Light Path view/ For OPS port protection both primary and error
wizard secondary path Wave Ids should be the same.
Light Path view/ Equal number of channels should be selected for warning
wizard ETR service and YearType
wizard and secondary path: Number of YN-channels for
service xxx differ
wizard and secondary path: Number of Y1-channels for
service xxx differ
Light Path view/ G6S is not allowed as the light path length error When user selects G6S as parent or child
wizard exceeds maximum allowed limit (100km) for ISC2/ card for OTU1 channel and the light path
ISC3c service length is more than 100km
Light Path view/ G6S is not allowed as the light path length error When user selects G6S as parent or child
wizard exceeds maximum allowed limit (100km) for ISC2/ card for OTU1 channel and the light path
ISC3c service length is more than 100km
Light Path view/ Operation was not performed on locked/OTU3P warning
wizard channels
Light Path view/ Operation was not performed because the error
wizard selected group contains two or more channels with
same wave ID's.
Chassis Config - Cannot configure an empty document warning
Chassis
Chassis Config - Network Design should be done before running warning
Chassis 4200 Chassis Configuration.
Chassis Config - This is not appropriate Exhaust Type for the warning
Chassis selected Chassis Size
Chassis Config - Exhaust ducts option must match the Mounting warning
Chassis options


Message
Type
Chassis Config - Error in xml, network node not found. warning
Chassis
Chassis Config - Please save or cancel the editing of record in warning
Chassis Chassis Group tab.
Chassis Config - You are about to change card type, all the service warning
Chassis card configuration for this channel will be lost
Chassis Config - Managed power Amp sites can’t have multiple error
Chassis Micro/Classic chassis without having RS chassis.
Please add an RS chassis before adding Micro/
Classic chassis.
Excel input Links To/From a node cannot be greater than 4. error Pop-up messages posted if more than 4
Verify the Links! links connected to a node. A node can
have a maximum of 4 connected links.
Excel input Same Name entered in FiberNodeA and error Message posted as cell value in Links
FiberNodeB in row(s) : sheet in Errors column when node names
for starting and ending nodes of a link are
the same. This error message also
identifies all row numbers having the same
error.
Excel input FiberNodeA not entered in Row(s) : error Message posted as cell value in Links
sheet in Errors column when starting node
name of link is not entered. This error
message also identifies all row numbers
having the same error.
Excel input FiberNodeB not entered in Row(s) : error Message posted as cell value in Links
sheet in Errors column when ending node
name of link is not entered. This error
message also identifies all row numbers
having the same error.
Excel input Link Length not entered in Row(s) : ; Valid Range error Message posted as cell value in Links
is 1 to 9999 (Inclusive of Bounds) sheet in Errors column when link length of
link is not entered. This error message
also identifies all row numbers having the
same error.
Excel input Invalid Link Length in Row(s) : ; Valid Range is 1 to error Message posted as cell value in Links
9999 Km (Inclusive of Bounds) sheet in Errors column when incorrect link
length of link (in Km) is not entered. This
error message also identifies all row
numbers having the same error.
Excel input Invalid Link Length in Row(s) : ; Valid Range is 1 to error Message posted as cell value in Links
6214 Miles (Inclusive of Bounds) sheet in Errors column when incorrect link
length of link (in mi) is not entered. This
Excel input Number of Spans not entered in Row(s) : ; Valid error Message posted as cell value in Links
Range is 1 to 32 (Inclusive of Bounds) sheet in Errors column when value for
number of spans in link is not entered. This


Message
Type
Excel input Link Name not entered in Row(s) : error Message posted as cell value in Links
sheet in Errors column when link name of
link is not entered. This error message
also identifies all row numbers having the
same error.
Excel input Enter Valid value in C2 Cell : 'Link_Length_Km' or error Message posted as pop-up when value
'Link_Length_mi' entered in cell C2 of Links sheet is neither
“Link_Length_Km” nor “Link_Length_mi.”
Excel input Entered Link length would result in span length error Message posted as cell value in Links
more than 300Km in Row(s) : sheet in Errors column when entered
LinkLength and number of spans would
result in any of the average span length
being greater than the limit of single span
length (in Km). This error message also
error.
Excel input Entered Link length would result in span length error Message posted as cell value in Links
more than 186miles in Row(s) : sheet in Errors column when entered
LinkLength and number of spans would
result in any of the average span length
being greater than the limit of single span
length (in mi). This error message also
error
Excel input Valid Data Range is : OTU1, OTU2, OTU1(ISC2/ error Message posted as pop-up when entered
ISC3), OTU2e(10GbE), OTU2e(FC200/400) OR value for Data_Rate column is other than
FC1200 OTU1, OTU2, OTU1(ISC2/ISC3),
OTU2e(10GbE), OTU2e(FC200/400) OR
FC1200 in any routing sheet.
Excel input Incorrect N/W Module error Message posted as pop-up when entered
value for Network_Module column is other
than OPT-XX-D-U,OPT-XX-D-UL,F10-A/T-
90-noDT,F10-A/T-90-TN,F10-A/T-90-
XX,F10-A/T-90-DT,F10-A/T-90-TN-
DT,F10-A/T-90-XX-DT,F10-A/T-90-DT-
noDT,F10-T-90-noDT,F10-T-90-DT,F10-T-
90-TN-DT,F10-T-90-XX-DT,FC4-T-90-TN-
DT,FC4-T-90-noDT,FC4-T-90-DT or FC4-
T-90-XX-DT in any routing sheet.
Excel input Please select Node Name from the Drop Down List error Message posted as pop-up when entered
value for NodeX columns is not a valid
node name in any routing sheet.
Excel input Valid Data range is in the NodeList array form! error Message posted as pop-up when entered
value for NodeA and NodeB columns is
not a valid node name in any routing
sheet.
Excel input Valid Data Range is : OPS PORT PROTECTED, error Message posted as pop-up when entered
OPS FIBER PROTECTED, 1+1 PORT value for Protection_Type column is other
PROTECTED, 1+1 CARD PROTECTED OR 1+1 than OPS PORT PROTECTED, OPS
CHASSIS PROTECTED FIBER PROTECTED, 1+1 PORT
PROTECTED, 1+1 CARD PROTECTED
OR 1+1 CHASSIS PROTECTED in any
protection routing sheet.


Message
Type
Excel input Valid Data Range is : Primary or Secondary error Message posted as pop-up when entered
value for Path_Type column is other than
Primary or Secondary in any protection
routing sheet.
Excel input Data Range for Link Length is 1-9999 Km error Message posted as pop-up when entered
(Inclusive of Bounds) value for Link_Length column in Links
sheet is not in range of 1-9999Km when
length units are set to Km in C2 cell of
Links sheet.
Excel input Data Range for Link Length is 16214 miles error Message posted as pop-up when entered
(Inclusive of Bounds) value for Link_Length column in Links
sheet is not in range of 1-6214miles when
length units are set to miles in C2 cell of
Links sheet.
Excel input Data Range for Number of Spans is 1-32(Inclusive error Message posted as pop-up when entered
of Bounds) value for Spans column in Links sheet is
not in range of 1-32.
Excel input Data Range for Fiber OPS Protection is : Yes/No error Message posted as pop-up when entered
(A Blank Cell is considered as 'No') value for Spans column in Links sheet is
neither "Yes" nor "No."
Excel input Valid Data range for Span Distance : 1-300 Km error Message posted as pop-up when entered
(Inclusive of bounds) value for Span_Length column in
Spansphysical or AllSpansphysical sheet
is not in range of 1-300Km when length
units are set to Km in C2 cell of Links
sheet.
Excel input Valid Data range for Span Distance : 1-186 Miles error Message posted as pop-up when entered
(Inclusive of bounds) value for Span_Length column in
Spansphysical or AllSpansphysical sheet
is not in range of 1-186miles when length
units are set to Km in C2 cell of Links
sheet.
Excel input Fiber Type cannot be other than : NDSF, LS, error Message posted as pop-up when entered
OldLS, TWPlus, TWC, TWRS, Leaf, ELEAF, DSF, value for Fiber_Type column in
Teralight or TWReach Allspansphysical sheet is other than
"NDSF, LS, OldLS, TWPlus, TWC, TWRS,
Leaf, ELEAF, DSF, Teralight or TWReach."
Excel input Valid Data range for Span Loss : 0.1-55(Inclusive error Message posted as pop-up when entered
of bounds) value for Span_Loss column in
AllSpansphysical sheet is not in range of
0.1-55.
Excel input Valid Data range for Span Margin : 0-9(Inclusive of error Message posted as pop-up when entered
bounds) value for the Span_Margin column in the
AllSpansphysical sheet is not in the range
of 0-9.
Excel input Valid Data range for Span Dispersion : (-5)- error Message posted as pop-up when entered
25(Inclusive of bounds) value for the Span_Dispersion column in
the AllSpansphysical sheet is not in the
range of (-5)-25.
Excel input Valid Data range for Span Dispersion Slope : 0- error Message posted as pop-up when entered
0.3(Inclusive of bounds) value for the Span_Dispersion_Slope
column in the AllSpansphysical sheet is
not in the range of 0-0.3.


Message
Type
Excel input Please Enter 'CND5.2' in this cell error Message posted as pop-up when entered
value for Version column in
AllSpansphysical sheet is not CND5.2.
Excel input Please Network Type as CN4200 in this Cell error Message posted as pop-up when entered
value for Version column in
AllSpansphysical sheet is not CN4200.
Excel input Zero or blank dispersion and dispersion slope warning Zero or blank dispersion and dispersion
values have been replaced with the specified fiber slope values are replaced with the
type's default values specified fiber type's default values.
Excel input Dispersion value is beyond +/- 25% of default warning A warning is raised if the values go out of +
Dispersion value of {default} defaultDispersion for / - 25% of default value.
{X} fibre type in Span worksheet for span row {i}
Excel input Dispersion Slope value is beyond +/- 25% of warning A warning is raised if the values go out of +
default Dispersion Slope value of {default} / - 25% of default value.
defaultDispersion Slope for {X} fibre type in Span
worksheet for span row {i}
Excel Template "Node '" + strArray[1] + "' referenced in routing error Value entered for Node name in routing
Parser worksheet is not found in the Nodes worksheet on sheet does not match any entered node
row number: " +rowNumber.ToString() +" of "+ names in Nodes sheet.
Excel Template "Invalid data rate in Routing worksheet: " + error Entered value for Data_Rate column is
Parser strArray[4] + " is not a valid rate on row number: " other than:
+rowNumber.ToString() +" of "+ worksheetName 1) OTU1, OTU2, OTU1(ISC2/ISC3),
+" routing sheet"+".\r"; OTU2e(10GbE), OTU2e(FC200/400) OR
FC1200 in any routing sheet
2) 10G in any routing sheet
Excel Template "The ETR channel type is entered but not the CLO error CLO channel details missing when ETR
Parser channel type on row number: " channel details are present. (Traffic
+rowNumber.ToString() +" of "+ worksheetName entered in protected routing sheets should
+" routing sheet"+".\r"; have equal number of ETR and CLO
channels.)
Excel Template "The CLO channel type is entered but not the ETR error ETR channel details missing when CLO
Parser channel type on row number: " channel details are present. (Traffic
+rowNumber.ToString() +" of "+ worksheetName entered in protected routing sheets should
+" routing sheet"+".\r"; have equal number of ETR and CLO
channels.)
Excel Template The LINKS sheet shall contain the column error Links sheet does not contain column
Parser headings FiberNodeA, FiberNodeB, LinkLength headings FiberNodeA, FiberNodeB,
(km), Spans, Link Name and the LinkLength (km), Spans, Link Name, and
FiberOPSprotection in row number 1 of the FiberOPSprotection in row number 1 of
columns A to F strictly in the same order."; columns A to F in same order.
Excel Template "Invalid protection in Routing worksheet: " + error Protection_Type cell value for valid row
Parser strArray[7] + " is not a valid protection type "+" in "+ entry not in valid data range:
worksheetName +" routing sheet"+".\r"; OPS PORT PROTECTED, OPS FIBER
PROTECTED, 1+1 PORT PROTECTED,
1+1 CARD PROTECTED OR 1+1
CHASSIS PROTECTED
Excel Template "Incorrect Path Type entered in the routing sheet error Path_Type cell value for valid row entry
Parser for traffic row: " + rowNumber.ToString()+" in "+ not in valid data range: Primary,
worksheetName +" routing sheet"+". It should be Secondary
Primary for this row.\r";


Message
Type
Excel Template "ETR or CLO data rate are not supported on error Data rate either ETR/CLO in any
Parser unprotected lightpaths.Routing sheet:"+ unprotected routing sheet.
worksheetName +" routing sheet"+",error row
number:"+ rowNumber.ToString()+".\r";
Excel Template "Only 1+1 Card Protection is supported for ETR error Protection type cell value for row entry with
Parser and CLO data rate in the routing sheet for traffic ETR/CLO data rate is other than 1+1 card
row: " + rowNumber.ToString()+" in "+ protection.
Excel Template "The total length for ETR and CLO data rate is error Total link length of all links in defined path
Parser more than 40 km in the routing sheet for traffic row: is greater than 40Km and corresponding
" + rowNumber.ToString()+" in "+ worksheetName data rate cell value is either ETR or CLO.
+" routing sheet "+".\r";
Excel Template The R_OTUN_Y1_UnProt sheet could not be error R_OTUN_Y1_UnProt sheet not present.
Parser found.
Excel Template The R_OTUN_Y1_UnPrott sheet does not contain error R_OTUN_Y1_UnProt sheet does not
Parser required headers. contain required headers.
Excel Template The R_OTUN_Y1_Prot sheet could not be found. error R_OTUN_Y1_Prot sheet not present.
Parser
Excel Template The R_OTUN_Y1_Prot sheet does not contain error R_OTUN_Y1_Prot sheet does not contain
Parser required headers. required headers.
Excel Template The R_OTUN_YN_UnProt sheet could not be error R_OTUN_YN_UnProt sheet not present.
Parser found.
Excel Template The R_OTUN_YN_UnProt sheet does not contain error R_OTUN_YN_UnProt sheet does not
Parser required headers. contain required headers.
Excel Template The R_OTUN_YN_Prot sheet could not be found. error R_OTUN_YN_Prot sheet not present.
Parser
Excel Template The R_OTUN_YN_Prot sheet does not contain error R_OTUN_YN_Prot sheet does not contain
Parser required headers. required headers.
Excel Template "Channel number must be between 0 and 40. '" + error Channels cell value is not in valid data
Parser strArray[3] + "' is invalid in Routing worksheet on range: 1-40 (inclusive of bounds).
row number: " +rowNumber.ToString() +" of "+
Excel Template "OPS Fibre protected link :"+ error Link in defined propagation path for ETR/
Parser processedDemandLinks[i].ToString()+" cannot CLO channel type is
support ETR and CLO data rate in the routing Fiber_OPS_Protection.
sheet for traffic row: " + rowNumber.ToString()+" in
"+ worksheetName +" routing sheet"+".\r";
Excel Template Design Constants: PMD Coefficient value must be error
Parser between 0 and 5.
Excel Template allowed value for one or more 40G lightpaths error
Parser passing through this link:{0}
Metro (O-Shelf)'{1}
Regional (O-Shelf)/ RS-F40M (Standard)'{2}
Either adjust the span lengths or force a Regen for
the impacted 40G lightpaths given below:
BOM You must perform a Network Design before error
running Configuration Report.


Message
Type
BOM Incremental BOM Generation Error: Invalid error
NETWORK TYPE: The network type of the
BaseLine file and the Modified file are different
BOM Power consumption of the service card group at error Power consumption of cards exceeds the
following locations exceeds PSM option: limit supported by the chassis.
Please select a higher power PSM Power Unit for
the involved nodes.
Visio You must perform a Network Design before error User has tried to generate Visio report
generating Visio Reports before designing network.
Visio Network was previously designed as a Corestream error User has tried to generate Visio report for
network and cannot be converted to a 4200 CoreStream network.
network. Please select the Design Corestream
network option
Visio CND cannot open the Visio report as the Microsoft warning Visio is not installed, so report cannot be
Visio software is not found on this computer. displayed, but *.bas file would be saved
Alternatively, the Visio report has been generated into system.
in the *.bas file format and saved at location: -----
Visio Please select either Network View Option or error If Network View diagram check box is
Nodes for visio node view. unchecked, NONE is selected in node
view diagram list box, and NONE is
selected in Rack View diagram list box,
error message guides user to make
appropriate choice for partial Visio report.
Visio Visio Report generated successfully! information Displayed after successful generation of
Visio reports.
Visio This node doesn’t have any racks information Displayed if user clicks Configure Link of
node but there are no racks in that node.
Visio CND cannot display the Visio report as the error User tries to generate Visio reports but MS
Microsoft Visio software is not found on this Visio not installed or properly configured
computer. on machine.
Visio You cannot select nodes since the option information Nodes cannot be selected if complete
'Complete Visio View' is selected Report option selected.
Visio This is a DWR Card, Swap the first part of the information If user tries to swap DWR card, both parts
card, second part would be swapped automatically will be swapped simultaneously.
with the next slot
Visio This slot cannot be selected for DWR card swap error Slot selected not compatible to DWR card
swap.
Visio For a half width card both the source and error User tries to swap half-width card to slot
destination needs to be half width that is not half-width.
Not possible to swap these cards, try again with
different combination
Visio Not possible to swap these cards, try again with error User tries to swap card to incompatible
different combination slot.
Visio Rack removed information Empty rack deleted by user.
Visio No of Chassis is not 0 for this Rack, remove the error User tries to delete rack with 1 or more
chassis first chassis.
Visio Chassis removed and Chassis number reassigned information Chassis deleted by user.
Visio Rack Added information New rack added by user.
Visio Chassis Added information New chassis added by user.


Message
Type
Visio Chassis cannot be added error User tries to add chassis to rack that does
not have free space to accommodate type
of chassis added.
Visio Problem occurred while generating Power Info error Generic exception occurred due to
Table for [“NodeName”]. corrupted XML or missing attribute for a
particular card. Rerun the kernel to catch
the missing attribute in XML.
Visio Problem occurred while generating Channel Info error Generic exception occurred due to
Table for [“NodeName”]. corrupted XML or missing attribute for a
particular card. Rerun the kernel to catch
the missing attribute in XML.
Visio Managed power Amp sites can’t have multiple error Trying to add multiple Micro/Classic
Micro/Classic chassis without having RS chassis. chassis if no RS chassis is present. To add
Please add an RS chassis before adding Micro/ other chassis, first add an RS chassis.
Classic chassis
Visio Total Power available for the PSU selected is error Message displays when PSM selected is
[psuVal] whereas chassis power is [power] changed and the total power of that
Therefore, this PSU cannot be selected chassis exceeds the available power for
the PSU selected. Select appropriate
PSU.
Visio This node doesn’t have any racks error When user tries to open Rack view for
node that has no rack.
Table 7-3. CoreStream GUI Messages

CND Tool Message
Message Description
Area Type
Network design Network was previously designed as a error
CN4200 network and cannot be converted
to a CoreStream network. Please select
the Design CN 4200 networks option.
Network design Raman Threshold must be 21 dB or error
greater if using ILA-2 type amplifiers
Network design At least one Partitioning type must be error
selected
Network design This network contains LS or Old LS or warning
DSF fiber links. Please confirm with
Lightwave Systems Engineering or
Product Line Management on the design.
Network design No Document present to design error
Network design OSNR Pass threshold value for 10G, not error
in correct format
Network design OSNR Pass threshold value for G709 error
Band Tunable, not in correct format
Network design OSNR Pass threshold value for G709C error
Band Tunable, not in correct format

Table 7-3. CoreStream GUI Messages (Continued)

CND Tool Message
Message Description
Area Type
Network design Cannot change this value since OSNR error
pass threshold is set to \"Use Default\"
Network design Amplifier 1 Type must be \"CS-ILA-1\" error
only, since the system capacity value is set
to \"96Ch@50Ghz\" in Edit Preferences
Network design Amplifier 2 Type must be \"CS-ILA-1\" warning
only, since the system capacity value is set
to \"96Ch@50Ghz\" in Edit Preferences
Network design Forcing this Regen will clear all Forced warning
OPM/DGEs on the link
Network design OPM / DGE can be forced on this link only error
after execution of <Design CoreStream
Networks> because a regen has been
forced on this link
Network design Forced DGE has been removed at Node warning During execution of <Design Corestream Networks>,
port(portID) due to Forcing of NE type to at Node ports with forced place_DGE, changing NE
Terminal type of node port to Terminal will clear forced DGEs at
the node ports. The forced DGE flag at other sites/
nodes on the link will remain unchanged and ‘force
OPMDGE’ flag at link level will be updated based on
flag status at other amp sites/start-end Nodes on the
link.
Network design Forced DGE at Node port(portID) has warning During execution of <Design Corestream Networks>, if
been removed due to partitioning change kernel has to change the setting of a node port with a
in Network Design Option forced DGE to type Terminal (from OADM or S-
Terminal). However, the forced OPM/DGE status of all
other sites/nodes on that link will remain unchanged.
Network design The OSNR does not pass even with regen warning If a section fails OSNR check and does not have any
site everywhere in link OLA site which can be converted to regen site
Network design Network cannot be designed warning If user tries to force a regen at a COADM site (which is
not allowed), s/he will be asked if s/he wants to
convert COADM to SOADM. If user answers “no,”
warning message displays.
Network Design All Corestream designs containing 40G warning
Summary wavelengths must be reviewed by OPNET
prior to bid submission or network
deployment. Please rerun the design with
the "Generate 40G Non-Linear Log Files"
design option enabled, then generate a
40G Non-Linear Report for OPNET
analysis.
Network locking Please perform kernel run first. error Kernel run must be done before network or network
subset can be locked.
Network locking Lock operation is performed on lockable warning Kernel run must be done before network or network
item(s) only. To Lock the rest of the subset can be locked.
selected items, please perform a kernel
Run
Network locking Lock operation is performed on lockable warning Kernel run must be done before network or network
item(s) only subset can be locked.
Network locking Network is already in locked/unlocked warning
state


CND Tool Message
Message Description
Area Type
Network locking The file name shall not end with error Save As window will reopen for new name.
“__Baseline.” Please re-enter the file
name.
Network locking Could not lock the lightpath completely as error
there are channels with isM=T.
Network locking File already exists at: "+loc+". Do you wish error Message displays if either baseline or FFA version of
to replace it? file already exists.
Network locking Locking the network will result in two error Locking the network creates two files:
saved files: '<givenName>.xml' which will <givenName>.xml, which will be the locked network,
be the locked network, saved and left open saved and left open in CND, and
in CND, and '<givenName>_baseline.xml' <givenName>_baseline.xml, which will be the locked
which will be the locked network saved as network saved as Read Only.
'Read Only' . Do you wish to continue?
Network locking All the elements in the network would get error This is the confirmation message box when network
unlocked, Do you wish to continue? lock operation is requested.
Network locking Cannot save xml document : Access to error When baseline file is opened and then is being saved,
path [X] is denied this message displays because the read-only file
cannot be overwritten.
Network locking Network {name} cannot be locked error An element or any other dependent element/ sub-
because its in modified state element is locked and cannot be modified. Unlock
element, using right-click menu.
Link view Raman Threshold must be 21 dB or error
greater if using ILA-2 type amplifiers
Link view Cannot insert span. Matching Ola not error
found
Link view Only sites with NE type ILA1 will be information Message displays if there are no sites with NE type
available for forced OPM/DGE ILA1.
Link view This will clear all forced OPM and DGEs warning Message displays when Clear Force OPM/DGE button
on the link. Do you want to continue? is clicked.
Link view Please select a partner OPM for forced error Message displays when OPM and DGE are not
DGE. selected in pairs while forcing OPM/DGE. Select
OPM/DGE in pairs.
Link view Please design the network while you error Message displays if network is not kernel designed.
perform Force DCM Operation. Before forcing a DCM at a location in the link, the
network should be designed by the kernel.
Link view CAN NOT FORCE A LOCKED DCM error Message displays if the link or DCMs in the link got
MODULE. locked. If the link is locked, unlock it, or unlock the
DCMs on the link and then force the DCM at a
particular location in the link.
Link view All the forced DCMs in the link will be warning Message displays if the user wants DCM placement to
reset. Do you want to continue? be done by the kernel, instead of manually forcing the
DCMs in the link. The kernel will remove the forced
DCMs, and then auto-place the DCMs.
Link view Please enter a valid non-linear launch error This error is thrown if the user makes the launch
power value. power of 10G/40G blank in the link view data grids
Link view The valid range for the non-linear launch error This error is thrown if the user enters a launch power
power is : "+ minRangeValue + " to " + value that is ouside the given maximum and minimum
maxRangeValue + " dBm/Ch. ranges of launch powers.
Link view Please enter a numeric value for non- error This error is thrown if the launch power value entered
linear launch power. in 10G/40G is not a numeric value.


CND Tool Message
Message Description
Area Type
Link view Operation not valid as the Link/Amps/ error Message displays while trying to insert/delete span if
locking DCMs are locked! Link/Amp/DCMs are locked. Unlock Link/Amp/DCM
Link view All Amps on link: [linkName] cannot be error Message displays while trying to unlock amps when
locking unlocked because link is locked the link is locked. Unlock Link/Amp/DCM.
Link view All Dcms on link: NODE_NODE1 cannot error Message displays while trying to unlock DCMs when
locking be unlocked because link is locked the link is locked. Unlock Link/Amp/DCM.
Link view All Dcms on link: [linkName] cannot be error Message displays while trying to lock DCMs in a link
locking locked because one or more dcms are in when it is in modified state. Run kernel.
modified state
Link view All Amps on link[linkName] cannot be error Message displays while trying to lock amps in a link
locking locked because one or more amps are in when it is in modified state. Run kernel.
modified state
Link view Link [linkName] Cannot be locked error Message displays while trying to lock link when it is in
locking Because Link is in modified state modified state. Run kernel.
Link view Ola on link {name} cannot be locked error An element or a sub-element has been modified by
locking because ola is in modified state the user. The modification has to be validated by the
kernel for a valid design.
Link view Ola: {site} on link: {.name} cannot be error An element or a sub-element has been modified by
locking locked because ola is in modified state the user. The modification has to be validated by the
Link view link: {.name} cannot be locked because error An element or a sub-element has been modified by
locking link is in modified state" the user. The modification has to be validated by the
Link view DCM on ola: {.site} on link: {name} cannot error An element or a sub-element has been modified by
locking be locked because DCM is in modified the user. The modification has to be validated by the
state kernel for a valid design.
Link view Raman on ola: {site} on link: {name} error An element or a sub-element has been modified by
locking cannot be locked because raman is in the user. The modification has to be validated by the
modified state kernel for a valid design.
Link view All Amps on link: {name} cannot be locked error An element or a sub-element has been modified by
locking because one or more amps are in modified the user. The modification has to be validated by the
Link view Link amps cannot be locked because error An element or a sub-element has been modified by
locking amps are already locked the user. The modification has to be validated by the
Link view All Dcms on link: {name} cannot be locked error An element or a sub-element has been modified by
locking because one or more dcms are in modified the user. The modification has to be validated by the
Link view All Amps on link: {name} cannot be error An element or any other dependent element/ sub-
locking unlocked because link is locked element is locked and cannot be modified. Unlock
Link view All dcms on link: {name} cannot be error An element or any other dependent element/ sub-
locking unlocked because link is locked element is locked and cannot be modified. Unlock
Link view Cannot delete , link is in locked state error An element or any other dependent element/ sub-
locking element is locked and cannot be modified. Unlock
Link view Cannot delete , link amps are in locked error An element or any other dependent element/ sub-
locking state element is locked and cannot be modified. Unlock


CND Tool Message
Message Description
Area Type
Link view Cannot delete , link dcms are in locked error An element or any other dependent element/ sub-
locking state element is locked and cannot be modified. Unlock
Link view Cannot delete , the lightpaths on error An element or any other dependent element/ sub-
locking connected links are is in locked state element is locked and cannot be modified. Unlock
Link view Link Name Modify:: Link is in locked state error An element or any other dependent element/ sub-
Link view Link Name Modify :: Link sites are in error An element or any other dependent element/ sub-
locking locked state element is locked and cannot be modified. Unlock
Link view Link Name Modify :: Connected node ports error An element or any other dependent element/ sub-
locking are in locked state element is locked and cannot be modified. Unlock
Link view Link Name Modify :: One or more error An element or any other dependent element/ sub-
locking lightpaths passing through the link are in element is locked and cannot be modified. Unlock
locked state element, using right-click menu.
Link view Modify operation: Link could not be added error An element or any other dependent element/ sub-
locking as node ports or dependencies are in element is locked and cannot be modified. Unlock
locked state. element, using right-click menu.
Node view User can group only one port to existing error
selection for COADM and SOADM
Node view User has to group minimum two ports to error
existing selection for WSS-N
Node view Xml document is null. Cannot group ports error
Node view Grouping of OBP is not possible error
Node view Node {NODE_NET_XML_NODE.name} error The changes done by the user are not validated, so
locking cannot be locked because its in modified the network is not in a validated state. Locking is not
state allowed for portions of the network that are not
validated. Validate by performing the network design.
Node view Node Name Cannot be modified as node error User changes are not allowed, as the node is locked.
locking is in locked state To modify the node name, unlock the node.
Node view Port <portID> of NODE cannot be locked error An element or a sub-element has been modified by
locking because its in modified state the user. The modification has to be validated by the
Node view Site {name} on link {.name} cannot be error An element or a sub-element has been modified by
locking locked because its in modified state the user. The modification has to be validated by the
Node view Unilink Cannot be locked Because Unilink error An element or a sub-element has been modified by
locking is in modified state the user. The modification has to be validated by the
Node view Node Name Cannot be modified as node error An element or any other dependent element/ sub-
locking is in locked state element is locked and cannot be modified. Unlock
Node view Node Name Cannot be modified as one or error An element or any other dependent element/ sub-
locking more links connected to node are in locked element is locked and cannot be modified. Unlock
state element, using right-click menu.


CND Tool Message
Message Description
Area Type
locking more ola on the link connected to node element is locked and cannot be modified. Unlock
are in locked state element, using right-click menu.
locking more dcm on the link connected to node element is locked and cannot be modified. Unlock
are in locked state element, using right-click menu.
Node view Cannot delete , node port is in locked state error An element or any other dependent element/ sub-
Node view Cannot delete , connected node port is in error An element or any other dependent element/ sub-
Node view Cannot delete , connected node port is in error An element or any other dependent element/ sub-
Light Path view/ Not a corestream Network error
wizard
Light Path view/ Lightpath [name] cannot be locked error Message displays when user tries to lock a lightpath.
wizard because its in modified state
Light Path view/ Channel: [Cid] of lightPath [name] cannot error Message displays when user tries to lock a lightpath.
wizard be locked because channel is in modified
state
Light Path view/ Regen on Link [name] cannot be forced/ error Message displays when user tries to force regen when
wizard unforced because link is in locked state. the link is locked.
wizard unforced because link's OLAs are in the link's ola is locked.
locked state.
wizard unforced because link's DCMs are in the link's DCM is locked.
locked state.
wizard unforced because connected port degree the connected ports degrees are locked.
types are in locked state and therefore
cannot be changed.
Light Path view/ Regen on Node cannot be forced/unforced error Message displays when user tries to force regen on a
wizard because its ports [pid] is in locked state node when the port is locked.
Light Path view/ Lightpath [name] cannot be deleted error Message displays when user tries to lock the lightpath
wizard because its in locked state. when the lightpath is already locked.
Light Path view/ Forcing regen on [portname] will clear all warning Message displays when user is forcing regen on node.
wizard force port node type on node. Do you want
to continue?
Light Path view/ Forcing regen on [regenlocationname] will warning Message displays when user is forcing regen on link.
wizard clear all force OPM/DGEs on the link. Do
you want to continue?
Light Path view/ Forcing regen on [regenlocationname] will warning Message displays when user is forcing regen on link.
wizard clear all force DCM on the link. Do you
want to continue?
Light Path view/ UnForcing regen on [regenlocationname] warning Message displays when user is forcing regen on link.
wizard will clear all force OPM/DGEs on the link.
Do you want to continue?


CND Tool Message
Message Description
Area Type
Light Path view/ UnForcing regen on [regenlocationname] warning Message displays when user is forcing regen on link.
wizard will clear all force DCM on the link. Do you
want to continue?
Light Path view/ Adding Channels will clear all the force warning Message displays when user adds channels to
wizard Regens. lightpath.
Light Path view/ Could not assign channels for Lightpath error
wizard N1_N2. The number of available
wavelengths is not enough. This requires
Wavelength conversion which is not
supported for Corestream.
Excel input Links To/From a node cannot be greater error Pop-up message displays when more than 4 links are
than 4. Verify the Links! connected to a node in Links sheet. (Node can have
max 4 connected links.)
Excel input Same Name entered in FiberNodeA and error Node name for starting and ending nodes of link are
FiberNodeB in row(s) : the same. Displayed in Error column in Links sheet.
Excel input FiberNodeA not entered in Row(s) : error Starting node name of link not entered. Displayed in
Error column in Links sheet.
Excel input FiberNodeB not entered in Row(s) : error Ending node name of link not entered. Displayed in
Error column in Links sheet.
Excel input Link Length not entered in Row(s) : ; Valid error Link length not entered. Displayed in Error column in
Range is 1 to 9999 (Inclusive of Bounds) Links sheet.
Excel input Invalid Link Length in Row(s) : ; Valid error Incorrect link length (Km). Displayed in Error column in
Range is 1 to 9999 Km (Inclusive of Links sheet.
Bounds)
Excel input Invalid Link Length in Row(s) : ; Valid error Incorrect link length (miles). Displayed in Error column
Range is 1 to 6214 Miles (Inclusive of in Links sheet.
Bounds)
Excel input Number of Spans not entered in Row(s) : ; error Value for number of spans in link not entered.
Valid Range is 1 to 32 (Inclusive of Displayed in Error column in Links sheet.
Bounds)
Excel input Invalid Number of Spans in Row(s) : ; Valid error Incorrect value for number of spans in the link.
Range is 1 to 32 (Inclusive of Bounds) Displayed in Error column in Links sheet.
Excel input Link Name not entered in Row(s) : error Link name not entered. Displayed in Error column in
Links sheet.
Excel input Enter Valid value in C2 Cell : error Pop-up message displays when value entered in cell
'Link_Length_Km' or 'Link_Length_mi' C2 of Links sheet is neither “Link_Length_Km” nor
“Link_Length_mi.”
Excel input Entered Link length would result in span error Link length and number of spans add up to averaged
length more than 300Km in Row(s) : span length being more than the limit of single span
length (in Km). Displayed in Error column in Links
sheet.
Excel input Entered Link length would result in span error Link length and number of spans add up to averaged
length more than 186miles in Row(s) : span length being more than the limit of single span
length (in miles). Displayed in Error column in Links
sheet.
Excel input Valid Data Range is :10G error Pop-up message displays when value for Data_Rate
column is other than "10G" in any routing sheet.


CND Tool Message
Message Description
Area Type
Excel input Valid Data Range is : 10G UFEC, G.709 C error Pop-up message displays when value for
BAND Tunable, G.709 BAND Tunable, C Network_Module column is other than "10G UFEC,
BAND Tunable + BAND Tunable, BAND G.709 C BAND Tunable, G.709 BAND Tunable, C
Tunable + C BAND Tunable BAND Tunable + BAND Tunable, BAND Tunable + C
BAND Tunable" in any routing sheet.
Excel input Please select Node Name from the Drop error Pop-up message displays when value for the NodeX
Down List columns is other than is not a valid node name in any
routing sheet.
Excel input Valid Data range is in the NodeList array error Pop-up message displays when value for NodeA and
form! NodeB columns not valid node name in any routing
sheet.
Excel input Valid Data Range is : OPS PORT error Pop-up message displays when value for
PROTECTED Protection_Type column other than "OPS PORT
PROTECTED" in any protection routing sheet.
Excel input Valid Data Range is : Primary or error Pop-up message displays when value for Path_Type
Secondary column other than "Primary or Secondary" in any
protection routing sheet.
Excel input Data Range for Link Length is 1-9999Km error Pop-up message displays when value for Link_Length
(Inclusive of Bounds) column in Links sheet not in range of 1-9999Km when
length units are set to Km in C2 cell of Links sheet.
Excel input Data Range for Link Length is 1-6214miles error Pop-up message displays when value for Link_Length
(Inclusive of Bounds) column in Links sheet not in range of 1-6214 miles.
Excel input Data Range for Number of Spans is 1-32 error Pop-up message displays when value for Spans
(Inclusive of Bounds) column in Links sheet not in range of 1-32.
Excel input Data Range for Fiber OPS Protection is : error Pop-up message displays when value for the Spans
Yes/No (A Blank Cell is considered as column in the Links sheet is neither "yes" nor "No."
'No')
Excel input Valid Data range for Span Distance : 1- error Pop-up message displays when value for
300 Km (Inclusive of bounds) Span_Length column in SpansPhysical or
AllSpansPhysical sheet not in range of 1-300 Km.
Excel input Valid Data range for Span Distance : 1- error Pop-up message displays when value for
186 Miles (Inclusive of bounds) Span_Length column in SpansPhysical or
AllSpansPhysical sheet not in range of 1-186 miles.
Excel input Fiber Type cannot be other than : NDSF, error Pop-up message displays when value for Fiber_Type
LS, OldLS, TWPlus, TWC, TWRS, Leaf, column in AllSpansPhysical sheet is other than
ELEAF, DSF, Teralight or TWReach "NDSF, LS, OldLS, TWPlus, TWC, TWRS, Leaf,
ELEAF, DSF, Teralight, or TWReach."
Excel input Valid Data range for Span Loss : 0.1-55 error Pop-up message displays when value for Span_Loss
(Inclusive of bounds) column in the AllSpansPhysical sheet not in range 0.1-
55.
Excel input Valid Data range for Span Margin : 0-9 error Pop-up message displays when value for
(Inclusive of bounds) Span_Margin column in AllSpansPhysical sheet not in
range 0-9.
Excel input Valid Data range for Span Dispersion : (- error Pop-up message displays when value for
5)-25 (Inclusive of bounds) Span_Dispersion column in AllSpansPhysical sheet
not in range (-5)-25.
Excel input Valid Data range for Span Dispersion error Pop-up message displays when value for
Slope : 0-0.3 (Inclusive of bounds) Span_Dispersion_Slope column in AllSpansPhysical
sheet not in range 0-0.3.
Excel input Please Enter "CND5.2" in this cell error Pop-up message displays when value for Version
column in AllSpansPhysical sheet not CND5.2.


CND Tool Message
Message Description
Area Type
Excel input Please Network Type as CoreStream in error Pop-up message displays when value for Version
this Cell column in AllSpansPhysical sheet not CoreStream.
Excel input Error in row " + row number+" and column error This error is thrown if the launch power value entered
" + column number+" of the SpanPhysical in 10G/40G is not a numeric value.
sheet: Non-numeric value entered for non-
linear launch power.
Excel input Error in row " + row number+" and column error This error is thrown if the user enters a non-linear
" + column number+" of the SpanPhysical launch power value that is outside the given maximum
sheet: Entered value for the non-linear and minimum range.
launch power is not in the valid range of "+
minRangeValue + " to " + maxRangeValue
+ " dBm/Ch.
Excel Template "Invalid x or y coordinate specified for error Value entered for LOC_X or LOC_Y columns (x and y
Parser node: " + strArray[0] + ". The value should coordinates of nodes) are not between 1 and
be an integer between 1 and 2147483647 (inclusive of bounds).
2147483647.\r";
Excel Template "Node '" + strArray[2] + "' referenced in error Value entered for node name in routing sheet does not
Parser routing worksheet is not found in the match with any entered node name in Nodes sheet.
Nodes worksheet on row number: "
Excel Template "Incorrect Path Type entered in the routing error Path_Type cell value for valid row entry not in valid
Parser sheet for traffic row: " + data range: "Primary, Secondary."
rowNumber.ToString()+" in "+
worksheetName +" routing sheet"+". It
should be Secondary for this row.\r";
Excel Template The R-OC192-Y1-Prot sheet could not be error R-OC192-Y1-Prot sheet not present.
Parser found.";
Excel Template The R-OC192-Y1-Prot sheet does not error R-OC192-Y1-Prot sheet does not contain required
Parser contain required headers."; headers in the CS Excel template.
Excel Template The R-OC192-Y1-UnProt sheet could not error R-OC192-Y1-UnProt sheet not present.
Parser be found.";
Excel Template The R-OC192-Y1-UnProt sheet does not error R-OC192-Y1-UnProt sheet does not contain required
Parser contain required headers."; headers in the CS Excel template.
Excel Template "Channel number must be between 0 and error Channels cell value not in valid data range: 1-96
Parser 96. '" + strArray[3] + "' is invalid in Routing (inclusive of bounds).
worksheet on row number: "
BOM Configuration worksheet does not contain error
part number <" + key + "> referenced in
engineering rules. Loading of configuration
worksheet aborted.
BOM RegionalTerm: No rule defined for error
partnumber: <<RegionalTermPartnums>>
BOM RegionalSOADM: No rule defined for error
partnumber:
BOM RegionalSelect: No rule defined for error
partnumber:
BOM AgilitySOADM: No rule defined for error
partnumber:


CND Tool Message
Message Description
Area Type
BOM AgilityCOADM: No rule defined for error
partnumber:
BOM AgilityTerm: No rule defined for error
partnumber:
BOM AgilitySelect: No rule defined for error
partnumber:
BOM AgilityWSS3: No rule defined for error
partnumber:
BOM AgilityWSS4: No rule defined for error
partnumber:
BOM RegionalCOADM: No rule defined for error
partnumber:
BOM RegionalOla: No rule defined for error
partnumber:
BOM AgilityOla: No rule defined for partnumber: error
BOM You must perform a Network Design error
before running Configuration Report
BOM The following part number are not updated error
due to the invalid part number:
<<part_Number>>
due to the invalid price:
<<price_Number>>
due to the invalid discount:
<<discount_error>>
BOM The upload action is terminated due to the error
error:
BOM Please select a CND generated Core error When choosing files for incremental BOM, user
Stream BOM xls file or a CND generated selects an xls file that was not generated by CND as a
Core Stream xml file CoreStream network.
BOM The Node/Site names are not unique error Changing a node/site name in one of the files being
across the network compared by the incremental BOM is not allowed.

Viewing Kernel Error Messages

Table 7-4 presents the kernel error and warning messages displayed in the message area and pop-
ups for 4200, and Table 7-5 displays the messages for CoreStream.
Table 7-4. 4200 Kernel Error Messages
Kernel
Message Notes
Module
Wave CN_WaveConvert: Too many channels at non- More than 16 channels are added/dropped at a port.
assignment Fixed port User needs to find the port and reduce the channels to make the
number of add/drop channels at a port <= 16.
Wave CN_AssignConvertedWave: Too may More than 16 channels are added/dropped or regened at a port.
assignment channels at non-fixed port User needs to find the port and reduce the channels to reduce the
number of add/drop channels at a port.
Wave The required channel number in link is too The number of required channels exceeds the capacity of the
assignment high. Please remove some traffic over the link. system.
User should reduce the required channels. CoreStream Agility <=
96, CoreStream RLS <= 80; 4200 <= 40.
Wave Duplicate forced wavelength X on Port Y, Node This error occurs when assigning user-forced waves, if the user has
assignment Z Traffics A and Traffic B inadvertently forced the same wave on the same port for two
distinct traffics.
Wave PORT OPS protected lightpath from Node x to This error occurs if both the work and protect routes of an OPS
assignment Node y cannot be supported, because it channel cannot be assigned identical wavelengths. The kernel run
required regeneration. Reconfigure light-path will abort. This will occur if wave conversion is required on one/both
as unprotected light-path or as 1+1 line of the routes.
protected lightpath
Partitioning CN_Port_Node_Type_Assignment: The ports in a node have different port node types. In this version,
Mismatched port node types all ports should have the same port node type in a node.
User should avoid forcing different port node type in a node.
Partitioning CN_Port_Node_Type_Assignment: Forced Degree 1 ROADM node forced to MixROADM
Degree 1 node cannot be MixROADM Replace ROADM node with VMUX node if mixROADM functionality
is desired
Partitioning CN_Port_Node_Type_Assignment: FORCED VMUX Node can have maximum degree of 2
VMUX node must be less than degree 3 Replace VMUX Node with ROADM Node
Partitioning CN_Port_Node_Type_Assignment: Forced Fixed Filter port/node forced in a VMUX ROADM design
port node type cannot be fixed filter Deselect Force/Node type or use Global undo/force Edit button
Partitioning CN_Port_Node_Type_Assignment: Network Fixed Filter port/node forced in a VMUX ROADM design or vice
contains fixed and non-fixed filters versa
Deselect Force/Node type or use Global undo/force Edit button
Partitioning CN_Port_Node_Type_Assignment: Too many Number of channels Added or Dropped exceed 16 in a VMUX or
add/drop or regen chans at non-fixed filter port ROADM node or Regen node
Reduce traffic through the failing node and re-route traffic through
other paths if available
Filter Regeneration is required at Node (N) for Regeneration is prohibited for traffic with Protection type "Port
placement Traffic (X) because CPT is not allowed at OPS."
VMUX, but is not allowed for OPS Port
Protected Channels.
Filter Regeneration is required at Node (N) for Regeneration is prohibited for traffic with Service type "FC1200."
placement Traffic (X) because CPT is not allowed at
VMUX, but is not allowed for FC1200 services
or OPS Port Protected Channels.
Filter Regeneration is required at Node (N) for Regeneration is prohibited for traffic with Service type "FC1200" or
placement Traffic (X) because CPT is not allowed at Protection type "Port OPS."
VMUX, but is not allowed for FC1200 services.

Table 7-4. 4200 Kernel Error Messages (Continued)

Kernel
Message Notes
Module
Filter Regeneration is required at Node ( N ) for Regeneration is prohibited for traffic with Protection type "Port
placement Traffic ( X ) because CPT limitation on XX OPS."
Transceiver channels in fixed OADM design,
but is not allowed for OPS Port Protected
Channels.
Filter Regeneration is required at Node ( N ) for Regeneration is prohibited for traffic with Service type "FC1200" or
placement Traffic ( X ) because CPT limitation on XX Protection type "Port OPS."
but is not allowed for FC1200 services or OPS
Port Protected Channels.
Filter Regeneration is required at Node ( N ) for Regeneration is prohibited for traffic with Service type "FC1200."
placement Traffic ( X ) because CPT limitation on XX
but is not allowed for FC1200 services.
Filter The following two degree VMUX nodes should Displays the list of Nodes which can be potentially converted to
placement be converted to amp sites and the design Amp site to avoid pads
rerun to ensure proper optical modeling and
related calculations:
<Node_Name>
Break cycle No breakable nodes in VMUX cycle. All nodes A node need to be converted to back-to-back terminals in a cycle of
have over 16 channels VMUX nodes, but the channels at all VMUX nodes are over 16,
which is higher than the add/drop capacity of a VMUX node.
User needs to force a VMUX node to ROADM or MixROADM node
in the cycle, or to reduce the traffic in the cycle to make sure the
number of channels is <= 16 in at least one node.
Break cycle Regeneration is required at Node ( N ) for Regeneration is prohibited for traffic with Protection type "Port
Traffic ( X ) because of break cycle, but is not OPS."
allowed for OPS Port Protected Channels.
Break cycle Regeneration is required at Node ( N ) for Regeneration is prohibited for traffic with Service type "FC1200" or
Traffic ( X ) because of Break Cycle, but is not Protection type "Port OPS."
allowed for FC1200 services or OPS Port
Protected Channels.
Break cycle Regeneration is required at Node ( N ) for Regeneration is prohibited for traffic with Service type "FC1200."
Traffic ( X ) because of Break Cycle, but is not
allowed for FC1200 services.
DCM DCM placement: Solution is not feasible No valid DCM solution is available for the network
placement
Amp Only OAF can be forced at tx ports in fixed OAF forced in the transmit direction on a VMUX or ROADM
placement filter networks. network
Remove the “force OAF” setting from the node
Amp Only OAF-BCB can be forced at tx ports in OAF-BCB forced in the transmit direction on a fixed filter or OLA
placement nodes in ROADM networks. node
Remove the “force OAF-BCB” setting from the node
Amp Only OAF or OAF-BCB can be forced at tx OAF-BCB forced in the transmit direction on a fixed filter or OLA
placement ports in nodes in VMUX networks. node
Remove the “forced OAF-BCB” setting from the node
Amp Only OAF can be forced at tx ports in ola sites OAF forced in the transmit direction on a ROADM network
placement in non-fixed filter networks. Remove the “force OAF” setting from the node.
Amp Only OAF or OAV-0S-UC can be forced at rx OAV-VS-UC forced in the Receive direction on a ROADM network
placement ports in fixed filter networks. Remove the “force OAV” setting the Rx node.


Kernel
Message Notes
Module
Amp Only OAV-VS-UC can be forced at rx ports in OAV-0S-UC forced in the Receive direction on a ROADM network
placement non-fixed filter networks. Remove the “force OAV” setting the Rx node.
Amp Amp placement: Solution is not feasible No valid Amplifier solution is available for the network
placement Error caused by high span loss or a combination of high span loss
and high demux loss in the network. VMUX and ROADM networks
are more prone to see this error message, since they can potentially
have high demux loss.
If you encounter this problem reduce the high span loss values in
the network until it works. Some of the high loss spans may have to
be broken into two spans.
Amp The gain offset value calculated for one or If the gain offset value calculated at any degree exceeds the -7.0
placement more amps in this design exceeds the -7.0 dB and +7.0 range, then kernel reports this warning message.
to +7.0 dB range currently allowed by R7.2 Correct the gain offset by adjusting the launch powers at mentioned
and R7.3 CN 4200 system software. node degrees.
If the network is implementing gain offset with
a system software release at or above R7.2
then please use system software release
R7.2.1 or R8.0 and above.
<Node_Name> Degree: <PortID>
Amp The following spans are terminated by R3 If the spans are terminated by R3 MAN-OS-C and/or R3 OAV-OS-
placement MAN-0S-C and/or R3 OAV-0S-U-C and must U-C, then span loss must be greater than 5dB to avoid OSC
have a span loss plus span margin of at least 5 overload.
dB to avoid OSC overload: User need to increase the span loss greater than 5 dB at the
<Span_Name> mentioned spans.
Amp The maximum lightpath distance for 40G 40G transceivers has distance limitations for eDC40G Metro (O-
placement network modules are: Shelf), eDC40G Regional (O-Shelf) and RS-F40M (Standard) as
- 300 km for the 'eDC40G Metro (O- mentioned in the error message.
Shelf) Reduce the span length to reduce the distance of the mentioned
- 600 km for the 'eDC40G Regional lightpaths.
(O-Shelf)' / RS-F40M (Standard)
Either adjust the span lengths or force regen

for the impacted 40G lightpaths given below:
<Lightpath_Name>
Margin Regeneration is required at Node (N) for Regeneration is prohibited for traffic with Protection type "Port
analysis Traffic (X) because of insufficient Q or OSNR, OPS."
but is not allowed for OPS Port Protected
Channels.
Margin Regeneration is required at Node (N) for Regeneration is prohibited for traffic with Service type "FC1200."
analysis Traffic (X) because of insufficient Q or OSNR,
but is not allowed for FC1200 services or OPS
Port Protected Channels.
Margin Regeneration is required at Node (N) for Regeneration is prohibited for traffic with Service type "FC1200" or
analysis Traffic (X) because of insufficient Q or OSNR, Protection type "Port OPS."
but is not allowed for FC1200 services.
Margin Receiver power is too low-increase Rx power If the Rx Max power is greater than -7.0 dBm, then apply the pad to
analysis at site location: make it less than -7.0 dBm.
After placing the PAD, if the min Rx power is less than -17.0 dBm,
then this error message will be reported to the user.
User need to reduce the Rx Max power to make it less than -7.0
dBm.


Kernel
Message Notes
Module
Regen There is no solution after 10 iterations for Regen Placement times out after placing 10 regens in the lightpath
placement regen placement. User can break up the lightpath into smaller lightpaths.
Regen Previous user changes via edit-filters have Regeneration is prohibited on Nodes where filters have been
placement changed the loss profile on previously passed edited.
channels for link LINK NAME which now fails
Q. Regeneration at ports with filter-edits is
prohibited. To get the design to pass, filter-
edits at one or more intermediate ports should
be reverted and re-run the design.
General The OPS traffic can not pass without A port OPS traffic can not pass without regeneration.
kernel regeneration. User should convert the port OPS to client OPS to allow
regeneration
Dlight The power into the transmission fiber is Reduce the launch power to span for the mentioned lightpaths.
integration crossing the max allowed fiber power limit for
the following lightpaths
<Lightpath_Name> - Frequencies <Freq>
Dlight The Rx input power is crossing the over load If the Rx power (Low, Mean and Max) is greater than 7.5 dBm, then
integration limit for the following lightpaths. report this warning message.
<Lightpath_Name> - Frequencies <Freq> User need to reduce Rx power.
Dlight The OSNR is below the minimum required If OSNR values (Low, Mean and Max) are less than 10.4 dB, then
integration OSNR-limit for the following lightpaths. report this warning message.
<Lightpath_Name> - Frequencies <Freq> Need to increase the Rx power to make OSNR better.

Table 7-5. CoreStream Kernel Error Messages

Kernel
Message Notes Corrective Action
Module
Amp Excessive Amp output power is required at following location(s). If the required output power is greater than Reduce the number of channels at the specified
Placement Either reduce the number of channels or force a lower PAF. actual amplifier output power, then it is locations or force a lower PAF. The max allowed
<Node_Name> Degree <Degree_ID> Max PAF allowed with given failure case. PAF for given channels is displayed in the
channels: <x>dB message.
Amp Tx PAF forced at following location(s) is above the maximum If the forced Tx PAF is greater than Reduce the PAF at the specified locations. So
Placement allowed PAF for the NE configuration. maximum PAF allowed based on NE that forced PAF remains within range of allowed
<Node_Name> Degree <Degree_ID> Max Allowed Tx PAF: <x>dB configuration at the degree, then it is a PAF at that degree.
failure case.
Amp Rx PAF forced at following location(s) is above the maximum If the forced Rx PAF is greater than Reduce the PAF at the specified locations. So
Placement allowed PAF for the NE configuration. maximum PAF allowed based on NE that forced PAF remains within range of allowed
<Node_Name> Degree <Degree_ID> Max Allowed Rx PAF: <x>dB configuration at the degree, then it is a PAF at that degree.
failure case.
Amp Tx PAF at following location(s) is set below the minimum allowed If the PAF at any location is less than Increase the PAF at the specified location so
Placement PAF for the NE configuration. minimum PAF allowed based on NE that PAF remains within range.
<Node_Name> Degree <Degree_ID> Min Allowed Tx PAF: <x>dB configuration at that degree, then it is a
failure case.
Amp Rx PAF at following location(s) is set below the minimum allowed If the PAF at any location is less than Increase the PAF at the specified location so
Placement PAF for the NE configuration. minimum PAF allowed based on NE that PAF remains within range.
<Node_Name> Degree <Degree_ID> Min Allowed Rx PAF: <x>dB configuration at that degree, then it is a
failure case.
Amp Required gain at following amp locations is above the maximum If the required gain at any location is Reduce the span loss or PAF offset to reduce
Placement allowed gain. Reduce the span loss, force a lower PAF or force greater than maximum gain allowed from an the required gain. Or Force a Raman if raman is
Raman amplifier as appropriate. amplifier, then it is a failure case. not present at the specified locations.
<Node_Name> Degree <Degree_ID> Max allowed gain: <x>dB
Amp Amplifier gain has been increased to support desired output PAF at If the desired output PAF at an Agility node Increase the PAF according to the required
Placement following locations. is less than the PAF supported by the ILA gain.
<Node_Name> Degree <Degree_ID> gain, in this case we need to maintain the
desired PAF at the node, We adjust
Comments [kaptan]: I don’t think we need this warning in first place. MinGain rather than simply setting a VOA
CND doesn’t refer to Amp Gains in any of the reports. here
Amp PAF based on fiber type at following locations is above the If the PAF at any location is greater than Reduce the PAF at the specified locations within
Placement maximum allowed PAF for the NE configuration. PAF is reduced to maximum PAF allowed, PAF will be reduced the range.
maximum allowed value. to maximum allowed PAF. This case is valid
<Node_Name> Degree <Degree_ID> Max Allowed Tx PAF: <x>dB only for auto configured PAFs.
Amp Rx PAF in following nodes is not compatible with forced Tx PAFs in Validation of forced Rx PAF with respect to User should force Rx PAF greater than all
Placement downstream express degrees. Either force a higher Rx PAF or downstream Tx PAF. If the Rx PAF is less express Tx PAFs.
force lower Tx PAFs in downstream express degrees as than downstream Tx PAF, then report an
appropriate. warning message that forced Rx PAF is not
<Node_Name> Degree <Degree_ID> Max Allowed Tx PAF: <x> compatible with express powers.
Amp Raman at following locations is turned off. Therefore there is an In case low loss spans, if raman is forced Remove the forced Raman in case of low loss
Placement extra 2.5dB insertion loss associated with the Raman module. It's and raman is not required. Turn off the spans.
advisable not to use Raman in small spans. raman and inform the user.
<Node_Name> Degree <Degree_ID>
Amp Required gain at following amp locations is allowed but is above the If the required gain is greater than flat gain reduce the losses (Span loss, PAF offset) or
Placement normal flat gain operating range. Either reduce the span loss or of an amplifier, then report an warning force a Raman to increase the gain.
force a lower PAF. message. There is a margin of 10 dB gain
<Node_Name> Degree <Degree_ID> Max gain for normal flat gain for ILA amplifiers. If that extra margin is
operation: <x>dB required to se the gain, report this warning.
Amp Fiber type based PAF at following locations could not be achieved If the PAF is greater then the actual Reduce the PAF according the number of
Placement due to maximum Amp output power limit. The PAF was reduced to amplifier output power per channel, then the channels present at that location.
the maximum allowed value. PAF will be reduced to the actual amplifier
<Node_Name> Degree <Degree_ID> output power per channel.
Amp PAF at following locations has been reduced because the gain is In case of ILA amplifiers, if the ILA amplifier NA
Placement insufficient to support the desired output power. works on gain less than minimum gain, the
<Node_Name> Degree <Degree_ID> required PAF can not be achieved. In this
case the PAF will be reduced based on gain
of ILA
Network Following nodes form unbreakable optical ring possibly due to Displayed when kernel fails to break optical Break the cycle manually or unforce NE types
Partitioning force/locked NE operations. Clear the force/locked NE operation cycles in the Network because of forced few of the nodes in the
on at least one node in order to break the optical ring: Nodes
<Node_Name1>
<Node_Name2>
Network The number of add/drop channels is higher than the COADM COADM constaint check when the add/drop We need to remove some channels passing
Partitioning add/drop capacity at the following location. capacity at COADM exceeds the limit being terminated at the COADM node ports
<Node_Name> Degree <Degree_ID>

Table 7-5. CoreStream Kernel Error Messages (Continued)

Amp The maximum lightpath distance for 40G network 40G transceivers has distance Reduce the span length to reduce the
Placement modules are: limitations for eDC40G C Band distance of the mentioned lightpaths.
- 300 km for the 'eDC40G C Band Metro Metro and eDC40G C Band
(NTK539PDE5) Regional as mentioned in the error
message.
- 600 km for the 'eDC40G C Band Regional
(NTK539PCE5)
Either adjust the span lengths or force regen for the
impacted 40G lightpaths given below:
<Lightpath_Name>

Table 7-6. New Corestream Kernel Error Messages in CND Release 5.1

Table 7-7. 4200 validation messages in CND Release 5.2 (10G/40G non-linear validation)

Table 7-8. CoreStream validation messages in CND Release 5.2 (10G/40G non-linear validation)
Table 7-9. 40G failure messages and the respective corrective actions

A
Appendix A:
Product Reference Tables
CoreStream Product Reference

Please consult the Ordering Guides chapters in the CoreStream System Description Manual
(Regional), Release 7.1, 009-2005-510, and the CoreStream System Description Manual (Agility),
Release 7.1, 009-2005-300 for descriptions and product numbers for CoreStream equipment
referred to in this document.
4200, CN 2110, and CN 2150 Product Reference

The following tables provide the properties of the CN 2110, CN 2150, and 4200 products for
reference when using the Ciena Network Designer.
• Table A-1, SFP Types on Page 298
• Table A-2, XFP Types on Page 300
• Table A-3, Modules for 4200 on Page 301
• Table A-4, Module Locations, 4200 Classic and 4200 MC on Page 307
• Table A-5, Module Locations, 4200 RS Chassis on Page 308
• Table A-6, Y1/YN Attribute on Page 310
• Table A-7, Card Groups on Page 311
• Table A-8, CN 2110 Chassis Population Rules on Page 312
• Table A-9, Micro, Classic, RS, and CN 2150 Chassis Population Rules on Page 313
• Table , Note: WSS-ROADM card occupies two slots in the RS chassis. on Page 314
• Table A-10, Dispersion Windows Used by CND for Different Transceivers on Page 315
• Table A-11, CN 2110 DCMs on Page 315
• Table A-12, Power Consumption for 4200 Cards on Page 315
• Table A-13, Protection Options by Wave on Page 317
• Table A-14, Available Amplifiers on Page 318
• Table A-15, DCMs by Fiber Type on Page 319
• Table A-16, Affected Parts List with Minimum Revision for AutoDT Capability on Page
319
• Table A-17, Locking Menu Options on Page 324

298 Appendix A -
SFP Types
Table A-1. SFP Types
SFP Type
Data Format Description
(Name in Tool)
OPT-SR GbE 850nm SR, interfaces to multimode mode fiber only, has
(OPT_SX) FC100, FC200 limited reach, used to interface nearby devices (up to 500 m),
1G, 2G FICON client-side
Available for client ports on M6 cards
OPT-SR1 GbE 1310nm, single-mode, client/network
(OPT_SR1) FC100, FC200 Available for client ports on M6 cards
1G, 2G FICON On G10 cards, restricted to Port 1 ONLY
STM-1/4/16
OC-3/12/48
OTU1
D1 Video (4200 only)
OPT-SX GbE 850nm SR, interfaces to single-mode fiber (SMF) only and can
(OPT_SX) FC100, FC200 reach devices ranging up to 20 km
1G, 2G FICON Available for client ports on M6 cards
OPT-LX-M GbE 1310nm SR, interfaces to single-mode fiber (SMF) only and
(OPT_LX-M) FC100, FC200 can reach devices ranging up to 20 km
OPT-IR1 GbE 1310nm, interfaces to SMF only and can reach devices
(OPT_IR1_H) FC100, FC200 ranging up to 45 km, client/network
STM-1/4/16 On G10 cards, restricted to Port 1 ONLY
OC-3/12/48
OTU1
OPT-xx GbE CWDM long reach < 110 km
FC100, FC200 On G10 cards, restricted to Port 1 ONLY
STM-1/4, OC-3/12
STM-16/OC-48, OTU1
OPT-xxD-U GbE ITU DWDM transceivers, 191.5-196.0 THz, 28 dB budget at
OPT-xxD-UL FC100, FC200 OC-48/STM-16, 80 km dispersion limit, client/network,
1G, 2G FICON channels 15-60
STM-1/4/16 Available for client and network side ports on M6 cards
OC-3/12/48 On G10 cards, restricted to Port 1 ONLY
OTU1 Dispersion window -800 to +1600 ps/nm (-U)
Dispersion window -1020 to +2040 ps/nm (-UL)
OPT-ESC 200 Mbps ESCON 1310nm LED over 62.5μ or 50μ multimode, client-side
(OPT_ESC) Available for client ports on M6 cards
OPT IR-1 OC3/12 IR-1 1310nm SM, 10Km, -5-+85C
(OPT-12IR or
OC3/12 IR-1)

Appendix A - 299
Table A-1. SFP Types (Continued)

SFP Type
Data Format Description
(Name in Tool)
ELT-BT 10/100/1000 BaseT Electrical interface that accepts RJ45 connector on shielded
CAT5 cable, transmission reach up to 100 m, client-side,
copper/electrical
Available for client ports on M6 cards
OPT-4G-SX FC200 For FC4-T and EM6 modules ONLY, 850nm
FC400
OPT-4G-LX5 FC100, FC200, FC400 For FC4-T and EM6 modules ONLY, 1310nm
OPT-ISC GbE For G6S module ONLY, 1310nm
1G, 2G FICON
OPT-100B-FX GbE, 100-BaseT For G10 module ONLY, 1310nm, SM
Note: The OPT-ISC (R10.0) SFP supported on the EM6 is the same as the OPT-ISC SFP.
This SFP is supported on the EM6 as a part of the R10.0 HW release.

300 Appendix A -
XFP Types
Table A-2. XFP Types
XFP Type Data Format Platform Description
XFP-OPT-SR 10GbE 4200 10G pluggable transceiver, 850nm
up to 300 m, short reach
XFP-OPT-LR OTU2 4200 10G pluggable transceiver, 1310nm
OC-192 up to 10 km
STM-64
FC1200
10GbE
10GbE LAN/WAN
XFP-OPT-ER STM-64/OC192 4200 10G pluggable transceiver, 1550nm
10GbE LAN for 40 km
10GbE WAN
OTU2 (G.709)
OTU2E (Transparent Mapping)
10GFC/FC1200
XFP-OPT-UR STM-64/OC192 4200 10G pluggable transceiver, 1550nm
10GbE LAN for 80 km
10GbE WAN
OTU2 (G.709)
10GFC/FC1200
XFP-OPT-xxU STM-64/OC192 4200 DWDM transceiver
(DWDM) 10GbE LAN
10GbE WAN
OTU2 (G.709)
10GFC/FC1200
LT-EXFP STM-64/OC-192 4200 OE XFP with band-tunable LR
OTU2 (G.709) optics for Quad-10T ONLY
OTU2 LANPHY (10GbE)
OTU2 (Wrapped FC1200)
XFP-EXT-LR OC192 4200 Ext temp (-5 TO 85C) transceiver,
10GbE-LR OPT, 1310nm for Quad-10T ONLY
XFP-EXT-ER OC192 4200 Ext temp (-5 TO 85C) transceiver,
10GbE-ER OPT, 1550nm for Quad-10T ONLY
XFP-EXT-UR 10GbE-UR 4200 Dual-slot 1-port module, 1550nm
SMF for Quad-10T ONLY
XFP-EXT-SR 10GbE-SR 4200 Ext temp (-5 TO 85C) transceiver,
OPT, 850nm MM for Quad-10T
ONLY

Appendix A - 301
Modules for 4200

Table A-3. Modules for 4200
Module Description
Interface
M6S Module Six SFP ports that support 850 nm, 1310 nm, CWDM, DWDM wavelengths,
or electrical RJ-45.
Two RJ-45 10/100Base-T management (MGMT) ports.
One RJ-45 RS-232 console (CNSL) port.
SFP supported interface rates:
• OC-3 - 155Mbps
• OC-12 - 622Mbps
• OC-48 - 2.49Gbps
• OTU1 - 2.67Gbps
• ESCON - 200Mbps
• GbE - 1Gbps
• FC100 -1Gbps
• FC200 - 2Gbps
• STM-1 -155Mbps
• STM-4 - 622Mbps
• STM-16 - 2.49Gbps
• 10Base-T - 10Mbit/s
• 100Base-T - 100Mbit
• 1000Base-T - 1000Mbit/s
M3S Three SFP ports that support 850 nm, 1310 nm, CWDM, DWDM wavelengths,
or electrical RJ-45.
• OC-3 - 155Mbps, OC-12 - 622Mbps, OC-48 - 2.49Gbps
• OTU1 - 2.67Gbps
• ESCON - 200Mbps
• GbE - 1Gbps
• FC100 -1Gbps, FC200 - 2Gbps
• STM-1 -155Mbps, STM-4 - 622Mbps, STM-16 - 2.49Gbps
• 10Base-T - 10Mbit/s, 100Base-T - 100Mbit/s, 1000Base-T - 1000Mbit/s
F10-T One XFP optical port that supports OTU2, STM-64/OC-192, 10GbE LAN/WAN or
10GFC/FC1200.
Up to two discrete optics ports that support OTU2.
XFP supported Interface Rates:
• OC-192 - 9.95328Gbps
• OTU2 - 10.709225Gbps or 11.1 Gbps
• STM-64 -9.95328Gbps
• 10GFC/FC1200 - 10.51875
• 10GbE LAN: 10.31250 Gbps
• 10GbE WAN: 9.95328 Gbps

302 Appendix A -
Table A-3. Modules for 4200 (Continued)

Module Description
Quad-10T Transponds/regenerates 10G services, long reach, 4 removable, 4 OE-XFPs.
XFP supported interface rates:
• 10G SONET/SDH/WAN: 9.95Gbps
• 10GbE: 10.3Gbps
• OTU2 - 10.7Gbps
• OTU2e: 11.09Gbps
4200 RS chassis ONLY
2RS Four SFPs (two client, two network).
The client interfaces accept 1310, ESCON (200Mbps) SFPs.
The network interfaces accept DWDM SFPs.
F10-A Two SFP optical ports that support 850 nm, 1310 nm, CWDM, or DWDM wavelengths
Up to two discrete optics ports that support OTU2.
• OC-3 - 155Mbps, OC-12 - 622Mbps, OC-48 - 2.49Gbps
• OTU1 - 2.67Gbps
• ESCON - 200Mbps
• GbE - 1Gbps
• FC100 -1Gbps, FC200 - 2Gbps
• STM-1 -155Mbps, STM-4 - 622Mbps, STM-16 - 2.49Gbps
• 10Base-T - 10Mbit/s, 100Base-T - 100Mbit/s, 1000Base-T - 1000Mbit/s
FSLM CoreDirector cards supporting OTN interfaces and OTN switching down to the OPVC
level, allowing them to close 4200 rings and cross-connect any 4200-originated service.
FSLM-2(-TN) [OTU2], C-Band tunable (LT-EXFP) interface operating within 1529.55nm -
1565.42nm
FSLM-2 supported 10G XFPs:

• XFP-OPT-LR,TRANSCEIVER, 1310NM XFP, OC192 SR-1/ 10GBASE-LR
• XFP-OPT-SR,TRANSCEIVER, OPT, 850NM MM XFP, 10GBASE-SR
• XFP-OPT-ER,TRANSCEIVER, OPT, 1550NM XFP/ OC192 IR-2/ 10GBASE-ER
• XFP-OPT-UR,TRANSCEIVER, OPT, 1550NM XFP, OC192 LR-2/ 10GBASE-
80KM
• DWDM XFP 192.0 to 196.0 THZ, OC192 LR-2/ 10GBASE-80KM
FSLM-20 [OTU1], 8xOTU1

FSLM-20 supported SFPs: 20 split across 2 port groups:
• Ports 1-4 and Ports 17-20 support GbE/155M/622M
• Ports 5-16 support GbE/155M/622M
FC4-T One discrete optics port that supports OTU2.
• FC200
• FC400

Appendix A - 303

Module Description
G6S Six SFP optical ports that support OTU1 and Inter-System Communications (ISC).
• OTU1: 2.67Gbps
• ISC2 and ISC3c (compatibility mode): 1.0625 Gbps, OPT-ISC
• ISC3p (peer): 2.125 Gbps, OPT-ISC
G10 Ten SFP ports that support 1GbE LAN/WAN.
• GbE - 1Gbps
G10X One XFP optical port that supports 10GbE LAN/WAN.
XFP supported interface rates:
• 10GbE LAN: 10.31250 Gbps
• 10GbE WAN: 9.95328 Gbps
CWDM Filter
CN-<xx>S-00 (xx = 47, CWDM MUX-DEMUX, channel <nnnn>, one network and one express port (nnnn =
49, 51, 53, 55, 57, 59, 1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611)
61)
CN-<xx>S-13 (xx = 47, CWDM MUX-DEMUX, channel <nnnn> with 1310, one network and one express port
49, 51, 53, 55, 57, 59, (nnnn = 1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611)
61)
CN-<xx>S-15 (xx = 47, CWDM MUX-DEMUX, channel <nnnn> with 1550, one network and one express port
49, 59, 61) (nnnn = 1471, 1491, 1591, 1611)
CN-47D-00 CWDM MUX-DEMUX, channels 1471 and 1491, one network and one express port
CN-47D-13 CWDM MUX-DEMUX with 1310, channels 1471 and 1491, one network and one
express port
express port
express port
express port
express port
express port

304 Appendix A -

Module Description
CN-C4D-15 CWDM MUX-DEMUX with 1550; channels 1471, 1491, 1591, 1611; one network port
CN-C4H-00 CWDM MUX-DEMUX; channels 1551, 1571, 1591, 1611; one network and one express
port
CN-C4H-13 CWDM MUX-DEMUX with 1310; channels 1551, 1571, 1591, 1611; one network and
one express port
CN-C4L-00 CWDM MUX-DEMUX; channels 1471, 1491, 1511, 1531; one network and one express
port
CN-C4L-13 CWDM MUX-DEMUX with 1310; channels 1471, 1491, 1511, 1531; one network and
one express port
CN-C80-00 CWDM MUX-DEMUX; channels 1471 - 1611 (8 channels); one network
CN-C80-13 CWDM MUX-DEMUX with 1310
DWDM Filter Module
CN-200-23D 2-channel; 200 GHz; MUX-DEMUX channels 23, 25; one network, one monitor, one
express port
CN-200-27D 2-channels; 200 GHz; MUX-DEMUX channels 73, 29; one network, one monitor, one
express port
express port
express port
express port
express port
express port
express port
CN-200-B4H 4-channels; 200 GHz; MUX-DEMUX channels 53, 55, 57, 59; one network, one monitor,
one express port
CN-200-B4L 4-channels; 200 GHz; MUX-DEMUX channels 45, 47, 49, 51; one network, one monitor,
one express port
CN-200-R4H 4-channels; 200 GHz; MUX-DEMUX channels 31, 33, 35, 37; one network, one monitor,
one express port
CN-200-R4L 4-channels; 200 GHz; MUX-DEMUX channels 23, 25, 27, 29; one network, one monitor,
one express port
CN-200-B80 8-channels; 200 GHz; MUX-DEMUX channels 45, 47, 49, 51, 53, 55, 57, 59; one
network, one monitor port
CN-200-R80 8-channels; 200 GHz; MUX-DEMUX channels 23, 25, 27, 29, 31, 33, 35, 37; one
network, one monitor port
DWDM Bandsplitter (200 GHz)
CN-200-RBS Red-blue band
DWDM Filter (100 GHz)

Appendix A - 305

Module Description
CN-100-A4H 4-channels; 100 GHz; MUX-DEMUX channels 56, 57, 58, 59; one network, one monitor,
one express port
CN-100-A4L 4-channels; 100 GHz; MUX-DEMUX channels 52, 53, 54, 55; one network, one monitor,
one express port
CN-100-B4H 4-channels; 100 GHz; MUX-DEMUX channels 47, 48, 49, 50; one network, one monitor,
one express port
CN-100-B4L 4-channels; 100 GHz; MUX-DEMUX channels 43, 44, 45, 46; one network, one monitor,
one express port
CN-100-C4H 4-channels; 100 GHz; MUX-DEMUX channels 38, 39, 40, 41; one network, one monitor,
one express port
CN-100-C4L 4-channels; 100 GHz; MUX-DEMUX channels 34, 35, 36, 37; one network, one monitor,
one express port
CN-100-D4H 4-channels; 100 GHz; MUX-DEMUX channels 29, 30, 31, 32; one network, one monitor,
one express port
CN-100-D4L 4-channels; 100 GHz; MUX-DEMUX channels 25, 26, 27, 28; one network, one monitor,
one express port
CN-100-E4H 4-channels; 100 GHz; MUX-DEMUX channels 20, 21, 22, 23; one network, one monitor,
one express port
CN-100-E4L 4-channels; 100 GHz; MUX-DEMUX channels 16, 17, 18, 19; one network, one monitor,
one express port
CN-100-A80 8-channels; 100 GHz; MUX-DEMUX channels 52-59; one network, one monitor port
CN-100-B80 8-channels; 100 GHz; MUX-DEMUX channels 43-50; one network, one monitor port
CN-100-C80 8-channels; 100 GHz; MUX-DEMUX channels 34-41; one network, one monitor port
CN-100-D80 8-channels; 100 GHz; MUX-DEMUX channels 25-32; one network, one monitor port
CN-100-E80 8-channels; 100 GHz; MUX-DEMUX channels 16-23; one network, one monitor port
DWDM Filter (50 GHz)
MDX-50-1 44-channels; 50 GHz; AWG MUX/DEMUX, odd channels
MDX-50-2 44-channels; 50 GHz; AWG MUX/DEMUX, even channels
DWDM Bandsplitter (100 GHz)
CN-BS1-<xx> (xx = one group (A-E), one network, one monitor port
A,B,C,D,E)
CN-BS2-AB two groups, one network, one monitor port
CN-BS2-CD two groups, one network, one monitor port
CN-BS2-ABE three groups, one network port
CN-BS5 five groups, one network, one monitor port
VMUX Filters
VMUX-A4L 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 52, 53, 54, 55)
VMUX-A4H 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 56, 57, 58, 59)
VMUX-B4L 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 43, 44, 45, 46)
VMUX-B4H 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 47, 48, 49, 50)
VMUX-C4L 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 34, 35, 36, 37)
VMUX-C4H 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 38, 39, 40, 41)

306 Appendix A -

Module Description
VMUX-D4L 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 25, 26, 27, 28)
VMUX-D4H 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 29, 30, 31, 32)
VMUX-E4L 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 16, 17, 18, 19)
VMUX-E4H 4-channel, 100 GHz with VOA, MUX+DEMUX (channels 20, 21, 22, 23)
VMUX-E80 8-channel, 100 GHz with VOA, MUX+DEMUX (channels 16, 17, 18, 19, 20, 21, 22, 23)
VMUX-D80 8-channel, 100 GHz with VOA, MUX+DEMUX (channels 25, 26, 27, 28, 29, 30, 31, 32)
VMUX-C80 8-channel, 100 GHz with VOA, MUX+DEMUX (channels 34, 35, 36, 37, 38, 39, 40, 41)
VMUX-B80 8-channel, 100 GHz with VOA, MUX+DEMUX (channels 43, 44, 45, 46, 47, 48, 49,50)
VMUX-A80 8-channel, 100 GHz with VOA, MUX+DEMUX (channels 52, 53, 54, 55, 56, 57, 58, 59)
Optical Protection
CN-OPS-x Optical protection card
Add/Drop Module
WSS-ROADM 1 by 9 port wavelength selectable switch - dynamic wavelength router with 1 network
port, supports channels 16-59
Card Slot Rules for 4200 Chassis

The 4200 Classic chassis can support a maximum of five interface modules, and the 4200 MC
chassis can support a maximum of two interface modules. For the Classic chassis, slots C and D
can be configured for either full-width or half-width modules. For the MC chassis, slot A can be
configured for either full-width or half-width modules. When half-width modules are required, a
divider is installed in the4200 platform for that slot. The interface modules that can be installed in
both configurations of chassis are the same. Table A-4 provides a summary of the modules slot
location and functionality.

Appendix A - 307
Table A-4. Module Locations, 4200 Classic and 4200 MC

No. of
Module System Port Optical Compact
Module Interface Module Slots
Width Controller Format Ports/ Flash
Switches
M3S Yes (slot Main) A-D SFP 3 Yes

M6S Yes (slot Main) A-C SFP 6 Yes
G6S Yes (slot Main) A-C SFP 6 Yes
G10 Yes (slot Main) A-C SFP 10 Yes
G10X Yes (slot Main) A-C XFP 1 Yes
XFP 1
F10-T Yes (slot Main) A-C Yes
Fixed 2
SFP, 2
F10-A No A-C No
Fixed 2
SFP, 3
FC4-T Yes (slot Main) A-C Yes
Fixed 1
Full
OAF-00-1-C Yes (slot Main) A-D Fixed 2 Yes
OAF-BC-B No A-D Fixed 7 No
OAF-BC-HP No A-D Fixed 7 No
OAV-0S-U-C Yes (slot Main) A-D Fixed 4 Yes
OAV-VS-U-CP Yes (slot Main) A-D Fixed 4 Yes
OAV-VS-HP Yes (slot Main) A-D Fixed 4 Yes
MAN-0S-C Yes (slot Main) A-D Fixed 3 Yes
MAN-0S-CP Yes (slot Main) A-D Fixed 3 Yes
Optical Filter No C-D Fixed No
Raman No A-B, B-C, C-D Fixed 2 No
OPS-1 No A1, A2 (MC chassis) Fixed 1 No
OPS-2 No Fixed 2 No
OPS-2-850 No C1,C2, D1, D2 (CL chassis) Fixed 2 No
A1, A2 (MC chassis)
Half Optical Filter No Fixed - No
C1,C2, D1, D2 (CL chassis)
A1, A2 (MC chassis)
2RS No SFP 4 No
C1,C2, D1, D2 (CL chassis)
* The Raman module is a 2-slot wide module. Although it occupies two slots, it only allows the user to assign it to the
higher slot number.

308 Appendix A -
Module Locations within the 4200 RS

The 4200 RS chassis can support a maximum of 17 (RS form-factor) full-height modules, or up to
14 (RS form-factor) full-height modules with the right-most four slots capable of supporting two
(classic form-factor) half-width modules per slot. When (classic form-factor) half-width modules are
used in the right four slots, a divider is installed in the 4200 RS chassis for that slot. The half-width
module capable slots are configured with dividers from right to left (slot 17 to slot 14). Existing classic
form-factor full- and half-width modules are supported in the 4200 RS chassis with the use of a 12V
Adapter Module installed to the top of the module to make it an RS form-factor full-height module.
The 12V Adapter Module is installed on the classic form-factor full-width module prior to installation
in the module.
The 4200 RS chassis can support all classic form-factor full- and half-width modules with the use of
12V Adapter Module; however, the 4200 Classic/MC chassis cannot support RS form-factor full-
height modules. Table A-5 provides a summary of the modules slot location and functionality.
Table A-5. Module Locations, 4200 RS Chassis

No. of
Module System Interface Port Optical Compact
Module
Size Controller Module Slots Format Ports/ Flash
Switches
RJ-45
Node Controller Yes (slot 1) None Control 0 Yes
Only
RJ-45
Shelf Controller Yes (slot 1) None Control 0 Yes
Only
Fixed
DWR No 2-17 9 No
RS Full- Optical
height
Fixed
OCM-8 No 2-17 8 No
Optical
RS-Raman* No 2-17 Fixed 2 No
Fixed
VMUX4** No 2-17 6 No
Optical
Fixed
VMUX8 No 2-17 10 No
Optical
Classic 2-17 with one Refer to
All as identified in In accordance Refer to Refer to
Full- 12V Adapter Table A-
Table A-4 with Table A-4 Table A-4 Table A-4
Width Module per slot 4
Classic 14-17 with one
All as identified in Refer to Refer to
Half- No 12V Adapter No
Table A-4 Table A-4 Table A-4
Width Module per slot
* The Raman module is a 2-slot wide module. Although it occupies two slots, it only allows the user to
assign it to the higher slot number.
** When used with the 12V Adapter Module.

Appendix A - 309
Rules for Visio Reports

When Chassis Configuration Save and Exit is clicked, the 4200 reporting engine runs and writes
the Visio XML block in the main XML file. The reporting engine processing considers the following
tables and information while processing to populate the cards into chassis at each node and/or site.
The year attributes of service cards, OPS cards, and Fixed Filter cards are shown in Table A-6.

310 Appendix A -
Table A-6. Y1/YN Attribute
If the year attribute in the network design parameters is Y1+YN, the service, OPS, and Fixed Filter
cards, which all have the year attribute Y1 as well as year attribute YN, are populated into a chassis.
The necessary and sufficient number of chassis is then calculated to populate both Y1 and YN cards.
If the year attribute in the network design parameters is Y1, the service, OPS, and Fixed Filter cards,
all with year attribute Y1, are populated into a chassis. The chassis calculation then follows the steps
below:

Appendix A - 311
1. Find the required chassis to populate both Y1 and YN cards, and also the cards that do not
bear a year attribute (e.g., DCMs, OSCs)
2. From each of the chassis, empty all slots by removing all the populated cards
3. Beginning with the first emptied chassis, populate the Y1 cards and the cards that do not bear
a year attribute (e.g., DCMs, OSCs) into the emptied chassis
4. Delete the remaining empty chassis after populating all relevant cards
When additional cards are added to a parent card using the ADD button in the Channel Card and
Port Info link in the Service Card Config tab, the newly added service card is called the child card.
There can be a maximum of three child cards to one parent card. The parent and its child cards are
treated as a group, and that group, as a single entity, must be populated in the same chassis. Table
A-7 lists the allowed slot combinations for different chassis in case of different card groups.
Table A-7. Card Groups

312 Appendix A -
Table A-8. CN 2110 Chassis Population Rules

Allowed Slots in 2110
DCM Form Factor
Chassis
CN 2110-T0-90
CN 2110-T0-100
CN 2110-T0-110
CN 2110-T0-120
Full width A1
CN 2110-T3-100
CN 2110-T3-120
CN 2110-T3-140
CN 2110-T3-160
CN 2110-T0-10
CN 2110-T0-20
CN 2110-T0-30
CN 2110-T0-40
CN 2110-T0-50
CN 2110-T0-60 Half width A1, A2
CN 2110-T0-70
CN 2110-T0-80
CN 2110-T3-20
CN 2110-T3-40
CN 2110-T3-60
CN 2110-T3-
CN 2110-T0-70L Half width 1,2
CN 2110-T0-80L Half width 1,2
CN 2110-T0-90L
CN 2110-T0-100L
CN 2110-T0-110L
CN 2110-T0-120L
Full width 1
CN 2110-T0-130L
CN 2110-T0-140L
CN 2110-T0-150L
CN 2110-T0-160L
CN 2110-T0-170L

Appendix A - 313
Table A-9. Micro, Classic, RS, and CN 2150 Chassis Population Rules
System
Card
Card Controller Form Factor Allowed Slots in Actual Equipment
Category
Function
Micro Classic RS 2150
Chassis Chassis Chassis Chassis
Service Cards M6S-F/M6S- Yes Full Width Main, A Main, A, 2-17 N/A
TDM-F/M6S- B, C
ESCON-F/
M6S-GEFC-F/
M3S-F/F-10T/
F10P-T/FC-
4T/G6S
Service Cards F10-A/F10PA No Full Width A A, B, C 2-17 N/A
Service Cards ETR-CLO No Half Width A1, A2 C1, C2, 14B, 14C, N/A
D1, D2 15B, 15C,
16B, 16C,
17B, 17C
Amplifier MAN-0S-C/ Yes Full Width Main, A Main, A, 2-17 N/A
Cards MAN-0S-CP/ B, C, D
OAF-00-1-C/
OAV-OS-U-C/
OAV-VS-U-C
and OSC
padded
variants
Amplifier OAF-BC-B/ No Full Width A A, B, C, 2-17 N/A
Cards OAF-BC-X D
Filter Cards CN-100-A80/ No Full Width A C, D 14-17 A1, A2,
CN-100-B80/ B1, B2
CN-100-C80/
CN-100-D80/
CN-100-E80/

314 Appendix A -
System
Card
Card Controller Form Factor Allowed Slots in Actual Equipment
Category
Function
Micro Classic RS 2150
Chassis Chassis Chassis Chassis
Filter Cards CN-BS1-A/ No Half Width A1, A2 C1, C2, 14B, 14C, A1, A2,
CN-BS1-B/ D1, D2 15B, 15C, A3, B1,
CN-BS1-C/ 16B, 16C, B2, B3
CN-BS1-D/ 17B, 17C
CN-BS1-E/
CN-BS2-AB/
CN-BS2-CD/
CN-BS3-ABE/
CN-BS5/ CN-
100-A4H/ CN-
100-A4L/CN-
100-B4H/CN-
100-B4L/CN-
100-C4H/CN-
100-C4L/CN-
100-D4H/CN-
100-D4L/CN-
100-E4H/CN-
100-E4L/
OPS1/OPS2/
2R
Filter Cards WSS-ROADM N/A Full Width N/A N/A 2-16 N/A
Filter Cards VMUX-A4L/ N/A Full Width N/A N/A 2-17 N/A
VMUX-A4H/
VMUX-B4L/
VMUX-B4H/
VMUX-C4L/
VMUX-C4H/
VMUX-D4L/
VMUX-D4H
VMUX-E4L/
VMUX-E4H
OCM OCM-8 N/A Full Width N/A N/A 2-17 N/A
Note: WSS-ROADM card occupies two slots in the RS chassis.

Appendix A - 315
CND Dispersion Windows
Table A-10. Dispersion Windows Used by CND for Different Transceivers
Dispersion Dispersion
Transceiver Type Description Bound
Bound (wide) (narrow)
Low High Low High

OPT_XX_D_U OTU1 -1300 1800 -800 1600
CN_F10_AT_90 OTU2_SWAP -400 1500 -200 1000
CN_F10_AT_90_DT OTU2_SWAP_DT -400 1500 -200 1000
CN_F10_AT_90_TN_DT OETUNE_to_OETUNE -400 1500 -200 1000
CN_F10_AT_90_XX_DT OEMOD_to_OEMOD -400 1500 -200 1000
CN 2110 DCMs
Table A-11. CN 2110 DCMs
Module Description
CN 2110-T0-xx ER3 DCM Type 0 module, compensating dispersion and dispersion slope of xx
(10-120) km standard fiber (G.652), half-width
CN 2110-T3-xx DCM Type 3 module compensating dispersion and dispersion slope of xx (20, 40,
60, 80, 100, 120, 140) km ELEAF fiber (G.655), half-width
CN 2110-T0-70/80L Low loss DCM Type 0 for 70/80 km standard fiber (G.652), half-width
CN 2110-T0-90/100/ Low loss DCM Type 0 for 90/100/110/120/130/140/150/160/170 km standard fiber
110/120/130/140/ (G.652), full-width
150/160/170L
Power Consumption for 4200 Cards
Table A-12. Power Consumption for 4200 Cards

Power
Main Built-in
4200 Modules Consumed Width Description
Slot OSC
(watts)
EM6 (-Base/-Flex) Y N 110.6 Full Service card
M6S Y N 65 Full Service card
M3S Y N 46 Full Service card
F10-T90-XX Y N 46 Full Service card
F10P-T90-XX Y N 35 Full Service card
F10E-T90-TN Y N 41 Full Service card
F10EP-T90-TN Y N 41 Full Service card
F10-A N N 68 Full Service card

316 Appendix A -
Table A-12. Power Consumption for 4200 Cards (Continued)

Power
Main Built-in
4200 Modules Consumed Width Description
Slot OSC
(watts)
G6S Y N 57.2 Full Service card
G10 Y N 88 Full Service card
G10X Y N 92 Full Service card
RS-ESOM (and -IP) Y N 120 Full Service card
CN-ESOM (and -IP) Y N 115 Full Service card
CN-2RS Y N 26.4 Full Service card
FC4-T90-TN Y N 46.7 Full Service card
FC4-T90-XX Y N 40.7 Full Service card
F10-A90-XX Y N 65 Full Service card
F10E-A90-TN Y N 71 Full Service card
F10EP-A90-TN Y N 71 Full Service card
Quad-10T Y N 110.4 Full Service card
CN-OPS-x N N 1.6-2.1 Half Optical protection
CN-100/200/CWDM N N 0 Full or Passive filters
half
OAF-00-01-C Y N 15 Full Amplifier
OAV-0S-U-C Y Y 20 Full Amplifier
OAV-VS-U-CP and OSC padded Y Y 20 Full Amplifier
variants
OAV-VS-HP and OSC padded Y Y 20 Full Amplifier
variants
OAF-BC-B Y N 15 Full Amplifier
OAF-BC-HP Y N 18 Full Amplifier
CN-RAMAN Y N 65 Full Amplifier
RS-RAMAN Y N 74.3 Full Amplifier
MAN-0S-CP and OSC padded Y Y 12 Full OSC only
variants
VMUX4 N N 15 Full Variable mux/demux
VMUX8 N N 20 Full Variable mux/demux

Appendix A - 317
Protection Options
Table A-13. Protection Options by Wave

Wave Type Card Line-side Protection Schemes
OPS 1+1 Port 1+1 Card 1+1 Chassis

Unprotected
Protected Protected Protected Protected
OTU1 M6S Y Y Y Y Y
M3S Y Y Y Y Y
G6S Y Y Y Y Y
GDPS OTU1 Y Y Y Y Y
OTU2 F10-A/T Y Y Y Y Y
OTU2e FC4-T Y Y N Y Y
(FC200/400)
OTU2e F10-T Y Y N Y Y
(10GbE)
FC1200 F10-T Y Y N Y Y
OTU3P RS-F40M-S Y Y N Y Y
RS-F40M-P
NTK539PDE5
NTK539PCE5
NTK539PBE5
NTK539PAE5
Note: 1+1 port protection is allowed for OTU2 data rate with DWDM XFP (FSLM-2) or LT-
EXFP (FSLM-2-TN) as the network module selection.

318 Appendix A -
Available Amplifiers
Table A-14. Available Amplifiers
Noise Noise
Amplifier Function Gain, dB Figure, Figure, Comments
typical worst
OAV-0S-U-C Rx 18.8-21.3 5.5-8.5 Variable gain amplifier with mid-
stage access for DCM insertion
(max loss of 9 dB)
OSC, OCM and DCM ports, SC
(compatible with UV)
Note that DCM loss up to 8.9 dB is
hidden inside OAV-0S-U-C.
Combination of DCM modules with
total loss greater than 8.9dB not
allowed in mid-stage.
OAV-VS-U-CP Rx 16.9-21.9 6.0-6.7 Two-stage amplifier, OSC, OCM,
and OSC DCM ports, SC (compatible with
padded UV) Gain 0-16.9 via input VOA
variants
OAV-VS-HP Rx 0-25 High-gain 2-stage amp, OSC,
and OSC OCM, DCM ports, SC (compatible
padded with UV)
variants
OAF-00-1-C Tx 19.3 5.5 Constant gain 21 dB amplifier
Rx
OAF-BC-B Tx 11 (thru port) 14.1-14.8 Transmit amplifier supporting 4
(thru port) degree, 2 local add and 1
expansion ports
14 (at port) 11.1-11.8

(at port)
OAF-BC-HP Tx 25 High-gain transmit amp supporting
4 degree, 2 local add and 1
expansion ports
MAN-0S-CP NO OA, OSC, OCM ports, shelf
and OSC controller
padded
variants
CN-RAMAN Distributed NDSF 7.0-9.4 NDSF 0.5-1.4 Distributed amplification of the
amp NZDSF 9.1-11.5 NZDSF/DSF payload signal, and to lesser extent
DSF 11.1-13 the OSC channel, by pumping the
0.1-1.9 transmission fiber with 14XX
wavelengths

Appendix A - 319
DCMs by Fiber Type

Table A-15. DCMs by Fiber Type
Transmission Fiber DCM Type, Type 0 (Low
DCM Type, Default Selection
in Link Loss) Selection
NSDF CN 2110-10 to CN 2110-120 CN 2110-10 to CN 2110-120
ELEAF CN 2110-T3-20 to CN 2110-T3-160 CN 2110-10 to CN 2110-120
LEAF CN 2110-T3-20 to CN 2110-T3-160 CN 2110-10 to CN 2110-120
TW Classic (TWC) CN 2110-T3-20 to CN 2110-T3-160 CN 2110-10 to CN 2110-120
TW Plus (TW+) CN 2110-T3-20 to CN 2110-T3-160 CN 2110-10 to CN 2110-120
TW-RS CN 2110-10 to CN 2110-120 CN 2110-10 to CN 2110-120
TW-Reach CN 2110-10 to CN 2110-120 CN 2110-10 to CN 2110-120
Teralight CN 2110-10 to CN 2110-120 CN 2110-10 to CN 2110-120
Old-LS No DCM deployed No DCM deployed
LS No DCM deployed No DCM deployed
DSF No DCM deployed No DCM deployed
Affected Parts List with Minimum Revision for AutoDT Capability
Table A-16. Affected Parts List with Minimum Revision for AutoDT Capability
F10-T Modules
Fixed B-720-1086-3XX F10-T90-XX ABB
Fixed B-720-1086-4XX F10P-T90-XX ABA
Tunable B-720-1086-300 F10-T90-TN ADC
Tunable B-720-1086-301 F10E-T90-TN ACC
Tunable B-720-1086-400 F10P-T90-TN ABC
Tunable B-720-1086-401 F10EP-T90-TN ABC
F10-A Modules
Fixed B-720-1087-3XX F10-A90-XX ABB
Fixed B-720-1087-4XX F10P-A90-XX ABB
Tunable B-720-1087-300 F10-A90-TN ABA
Tunable B-720-1087-301 F10E-A90-TN ABA
Tunable B-720-1087-400 F10P-A90-TN ABA
Tunable B-720-1087-401 F10EP-A90-TN ABA
FC4-T Modules
Fixed B-720-0025-1XX FC4-T90-XX BCA
Tunable B-720-0025-200 FC4-T90-TN BCA

320 Appendix A -
Pass-through Definitions
NETWORK EXPRESS EXPRESS NETWORK
NETWORK NETWORK
BAND BAND
NETWORK NETWORK
CHANNEL CHANNEL

Appendix A - 321
BAND BAND
NETWORK
EXPRESS
BAND BAND
NETWORK NETWORK
EXPRESS EXPRESS

322 Appendix A -
NETWORK NETWORK
EXPRESS
BAND
NETWORK
BAND
NETWORK EXPRESS NETWORK
BAND

Appendix A - 323
NETWORK
EXPRESS
BAND
NETWORK
EXPRESS
NETWORK
BAND
NETWORK
EXPRESS
NETWORK
EXPRESS
BAND
NETWORK
EXPRESS

324 Appendix A -
Locking Menu Options

The Locking menu options are context-sensitive based on which view is enabled in the GUI view
(network view/node view/link view/lightpath view), or which GUI items have been selected. The
following table summarizes each of these menu options and the relevant action.The lock/unlock
operations can be executed either using the main menu bar and/or using right-click menu option in
various CND views.
Table A-17. Locking Menu Options


009-2011-160 (CND R5.2 User Manual) RevA

Uploaded by

Copyright:

Available Formats

009-2011-160 (CND R5.2 User Manual) RevA

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

009-2011-160 (CND R5.2 User Manual) RevA

Uploaded by

Copyright:

Available Formats

Ciena Network Designer

Copyright© 2011 Ciena® Corporation

Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com

Ciena Network Designer (CND) 009-2011-160 - Revision A

Ciena Network Designer (CND) 009-2011-160 - Revision A

Ciena Network Designer (CND) 009-2011-160 - Revision A

Release Notes and Document Updates

Ciena Network Designer (CND) 009-2011-160 - Revision A

Table 1. Printing History

Issue/Revision Release Date Content Description

Ciena Network Designer (CND) 009-2011-160 - Revision A

4200 Advanced Services Platform (formerly known as ActivSpan

CoreStream Regional Customer Documents

Ciena Network Designer (CND) 009-2011-160 - Revision A

• CoreStream Transport System, Release 7.3, Maintenance and Upgrade Manual

CoreStream ULH (Agility) Documents

Document Ordering Information

Additional Product Information

Ciena Network Designer (CND) 009-2011-160 - Revision A

Features and Enhancements in CND Release 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

CoreStream Reference Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4200 Reference Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Ciena Network Designer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

General introduction to Ciena Network Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Begin Using the Ciena Network Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Ciena Network Designer (CND) 009-2011-160 - Revision A

Reports Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

General Information About Excel Input Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

CoreStream Input Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4200 Input Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Network Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Flow Chart Blocks: Detailed Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Ciena Network Designer (CND) 009-2011-160 - Revision A

Block D. Configure 4200 Network Design Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Network Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Flow Chart Blocks: Detailed Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Viewing GUI Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Viewing Kernel Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

CoreStream Product Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

4200, CN 2110, and CN 2150 Product Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Ciena Network Designer (CND) 009-2011-160 - Revision A

Ciena Network Designer (CND) 009-2011-160 - Revision A

Ciena Network Designer (CND) 009-2011-160 - Revision A

Features and Enhancements in CND Release 5.2

10G and 40G Non-Linear Launch Power Levels

Ciena Network Designer (CND) 009-2011-160 - Revision A

1 2 1 1.1 0 -0.5 0.5 1.1 -2 -3

Ciena Network Designer (CND) 009-2011-160 - Revision A

1 0 0.5 -2 0 -0.5 -2 0 -1 -2 0 -1.5 -2

Support for R8.0 OSC and OAV Cards

Ciena Network Designer (CND) 009-2011-160 - Revision A

OSC Link Budget Considerations

MAN-0S-CP-4 (R8.0) 30.5 dB or less

MAN-0S-CP-8 (R8.0) 26.2 dB or less

Default Placement of VMUX8 Selection

Other Features and Enhancements

Ciena Network Designer (CND) 009-2011-160 - Revision A

40G Non-Linear Report Generation

Fiber Types Supported in 40G Non-Linear Validation