450-3201-010 (OneControl 5.0 Engineering Guide) 11.01

OneControl Unified Management System
Engineering Guide
Release 5.0
What’s inside...
Introduction to OneControl 5.0
Deployment configurations
Geographical redundancy
Network sizing and engineering considerations
Platform requirements
Port requirements
Ordering information
Appendix A - AP platform requirements & engineering considerations
Appendix B - OSP deployments on AP systems
450-3201-010 - Standard Issue 11.01

August 2015
Copyright© 2011-2015 Ciena® Corporation. All rights reserved.
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 PRINTING; 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
with out notice.
Any usage in this document of Nortel, Nortel Networks, the Nortel logo, and Globemark now refer to Ciena
Corporation.
Copyright© 2011-2015 Ciena® Corporation
All Rights Reserved
The material contained in this document is also protected by copyright laws of the United States of America and other
countries. It may not be reproduced or distributed in any form by any means, altered in any fashion, or stored in a data
base or retrieval system, without express written permission of the Ciena Corporation.
Security
Ciena® cannot be responsible for unauthorized use of equipment and will not make allowance or credit for
unauthorized use or access.
Contacting Ciena
Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com
Customer Technical Support/Warranty
In North America 1-800-CIENA24 (243-6224)
410-865-4961
In Europe, Middle East, 800-CIENA24-7 (800-2436-2247)
and Africa +44-207-012-5508
In Asia-Pacific 800-CIENA24-7 (800-2436-2247)
+81-3-6367-3989
+91-124-4340-600
In Caribbean and Latin 800-CIENA24-7 (800-2436-2247)
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.
OneControl Unified Management System Engineering Guide

Release 5.0 450-3201-010 Standard Issue 11.01
Copyright© 2011-2015 Ciena® Corporation August 2015
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.

v
Publication history 0
August 2015
Issue 11.01 of the OneControl Unified Management System 5.0 Engineering
Guide
April 2015
Guide
January 2015
Guide
August 2014
Guide
April 2014
Guide
December 2013
Guide
December 2013
Guide
September 2013
Guide
August 2013
Guide

vi Publication history
July 2013
Guide
April 2013
Guide
April 2013
Guide
September 2012
Guide.
September 2012
Guide.
August 2012
Guide.
July 2012
Guide.
March 2012
Guide.
October 2011
Guide.
August 2011
Guide.

vii
Contents 0
About this document xi
Introduction to OneControl 5.0 1-1

What is OneControl? 1-1
OneControl high level architecture 1-2
Supported/Integrated Element Management Systems 1-3
OneControl Integrated Element Management 1-3
Supported network element releases 1-3
Upgrades and migrations 1-3
Supported upgrades 1-4
Supported migrations 1-5
Deployment configurations 2-1

Supported deployments 2-1
Architecture 2-1
Co-resident and standalone 2-2
Database 2-5
Client software 2-5
Mandatory install order for co-resident deployments 2-5
Geographical redundancy 3-1

OneControl redundant configuration using GR 3-1
Peer-to-Peer and Active/Backup modes 3-2
Forced replication 3-4
OneControl GR behavior with sub-EMS redundancy 3-5
Licensing 3-6
Data synchronized over OneControl security channel 3-7
Data synchronized over OneControl GR channel 3-8
Data not synchronized in a OneControl GR deployment 3-9
Network sizing and engineering considerations 4-1

OneControl 5.0 - How to size and engineer 4-2
Determine the type of NEs to be managed 4-2
Determine the total number of NEUs/NEs to be managed 4-2
Determine the type of and number of services to be managed 4-3
Determine platform type and whether virtualization is to be used 4-3
Determine database requirements 4-4

viii Contents
Choose a hardware platform 4-4

Review and understand all engineering considerations and platform
requirements 4-5
Virtualization 4-5
Oracle VM for SPARC Solaris virtualization 4-6
VMware ESXi for Linux (RHEL/OL) virtualization 4-7
Network element equivalent units (NEUs) 4-9
Maximum NEUs/NEs/services 4-12
Guidelines and considerations for medium and large networks 4-25
OneControl client sessions 4-30
Maximum OneControl client GUIs on a client only platform 4-30
Maximum client sessions to a OneControl server 4-31
OneControl general engineering limits 4-32
Bandwidth requirements 4-32
Scheduled Jobs and procedures 4-35
Platform requirements 5-1

Hardware platform requirements 5-3
Server platform requirements 5-3
Client platform requirements 5-10
LAN/WAN requirements 5-14
Database requirements 5-17
MySQL Database Deployments 5-18
Oracle Database Deployments 5-18
Server platforms - Operating system requirements 5-27
Solaris/Linux OS release 5-27
Solaris/Linux OS bundles/patches 5-30
Virtualized Deployments 5-31
Hard disk configuration 5-31
Hostname, FQDN, hosts file, and IP address requirements 5-41
Domain Name Service (DNS) 5-42
Umask and shell requirements 5-44
Kernel parameters 5-45
Solaris OS hardening (optional) 5-47
Client platforms - Operating system requirements 5-50
OneControl software patches 5-52
Port requirements 6-1

Ports for OneControl (base install) 6-2
Ports for OneControl (additional if using features: 5400/CD, 4200, CoreStream,
SONET/SDH Control Plane services, or OTN services) 6-5
Ports for OneControl (if using feature: Manager for 6k, OM5k and CPL) 6-6
Ports for SLM 6-15
Ports for MTOSI northbound interface 6-16
Ports for UOG northbound interface 6-16
Ports for TMF northbound interface 6-17
Ports for OSP 6-19
Ports for NSV 6-21
Ports for CESD NEs (managed via ESM) 6-22

Contents ix
Ports for 5410/5430 NEs 6-23

Ports for CoreDirector NEs 6-25
Ports for 4200 NEs 6-28
Ports for CoreStream NEs 6-31
Ports for FlexSelect 40G NEs 6-32
Ports for O-APS NEs 6-33
Ports for CN2130/CN2300 NEs 6-33
Ports for OM5000 NEs 6-34
Ports for CPL NEs 6-37
Ports for 6500 NEs 6-40
Ports for 6100/6200 NEs 6-45
Ordering information 7-1

Operating System and Database Ordering Guidelines 7-2
Software download 7-2
Ciena Software Key Code Manager 7-3
OneControl 5.0 - How to order 7-3
Determine the number of elements to be managed 7-3
Determine the deployment size or bundle kit required 7-4
Determine the NE types to be managed 7-6
Determine which optional features to enable 7-6
Determine service management functionality to enable 7-6
Determine platform type and redundancy requirements 7-7
Understanding the WSM changes in OneControl 5.0 7-8
Follow flowchart to determine order codes 7-10
Order codes - Core functionality 7-13
Order codes - NE Types 7-18
Order codes - Optional components 7-22
Order codes - Packet services 7-32
Order codes - Wavelength services 7-35
Order codes - SONET/SDH Control Plane services 7-38
Order codes - OTN services 7-41
Appendix A - AP platform requirements & engineering

considerations 8-1
HP hardware platform requirements 8-2
AP 11.0 - Recommended and supported hardware platforms 8-2
OSP with AP 11.0 - Recommended and supported hardware platforms 8-3
Additional HP hardware platform requirements 8-5
HP RX2660, RX3600, RX2800 supported HP itanium servers 8-5
HP-UX Operating System (OS) configuration requirements 8-6
HP-UX OS release and configuration 8-6
HP-UX OS patches 8-9
Hard disk configuration 8-11
Kernel parameters for all HP platforms 8-11
HP-UX desktop environments 8-13
HP-UX environment variables 8-13
HP platforms - Additional requirements 8-13
LAN/WAN requirements 8-13

x Contents
Engineering considerations 8-13

Engineering rules - Generic 8-14
Engineering rules - Manager for 6k, OM5k and CPL specific 8-14
Engineering rules - OSP specific 8-15
Engineering rules - TMF specific 8-15
Network size 8-16
Network element equivalent units (NEUs) 8-16
Maximum NEUs supported 8-17
Manager for 6k, OM5k and CPL GUI scalability 8-18
Manager for 6k, OM5k and CPL GUI equivalent units 8-18
NSV GUI scalability 8-18
NSV GUI equivalency units 8-19
Maximum NSV GUI equivalent units supported 8-19
Maximum NSV GUIs supported per PC 8-20
OSP GUI scalability 8-20
OSP GUI sessions 8-21
AP GUI (GNB) sessions 8-24
OSP firewall considerations 8-24
NSV firewall considerations 8-25
TMF firewall considerations 8-30
Appendix B - OSP deployments on AP systems 9-1

Partitioned NDS server deployments 9-1
Comparing Options for OSP Deployments on AP systems 9-5
Planning your OSP Deployment on AP systems 9-7

xi
About this document 0
This document describes the deployment options and engineering guidelines

for OneControl 5.0.
ATTENTION
Check for updated versions of this document on the Ciena Customer Service
Center portal at: https://portal.ciena.com. Once you are logged into this
portal, click the Documentation tab and then select OneControl. On this
page, navigate to the required release and documentation.
Documentation download
To download this guide or any other OneControl documents you need,
perform the following steps:
• As a registered user with a Ciena portal account, log into the Ciena
Customer Service Center portal at:
https://portal.ciena.com
• Once you are logged into this portal, click the Documentation tab.
• In the Browse list under Product Documentation Search, select
OneControl.
• Click Release 5.0.
• Find the OneControl Engineering Guide or any other OneControl
documents you need, and click the link.
• Download the document(s).
Audience for this document

This document is specifically prepared for the following audience:
• strategic and current planners
• transmission standards engineers
• network administrators

xii About this document
References
This document references the following Technical Publication and other
documentation:
• OneControl Fundamentals, 450-3201-001
• OneControl Installation, 450-3201-201
• OneControl Manager for 6k, OM5k and CPL Standard Operations Guide,
450-3241-301
• OneControl Service Management, 450-3201-302
• OneControl TMF Interface Fundamentals, 450-3271-001
• ONM Applications Platform Introduction, 450-3101-100
• Applications Platform Planning Guide, 450-3101-601
• ESM Release 6.6 product documentation
• ESM Engineering Guide, 009-3216-022
• PinPoint Portal Fundamentals, 450-3502-001
Technical support and information

Ciena provides technical support for OneControl customer accounts. The
support provided consists of emergency and regular technical support and a
OneControl Product Services suite of additional support services. Refer to
“Contacting Ciena” on page ii for contact information specific to your location.
Emergency technical support

You can reach emergency technical support personnel outside of the regular
technical support hours through an automatic paging system.
Ciena provides emergency technical support for OneControl customers who

have purchased a support contract. For the period covered by the support
contract, technical support for critical issues is provided outside of regular
business hours.
Attention: For the period covered by the support contract, access to

regular technical support for all issues defined in the support contract is
also available.
Issues considered critical include:

• issues that are now having an effect on, or have the potential to
immediately have an effect on, services carried by the managed nodes

About this document xiii
• issues causing the loss of network visibility or loss of fault management

functionality to one or more of the managed nodes
Regular technical support

Ciena provides regular technical support for OneControl customers who have
purchased a support contract.
Use the regular technical support to report and receive help for issues covered
by the product warranty, as described in your purchase agreement with Ciena.
You can be charged a standard rate for service requests that Ciena considers
to be outside the scope or period covered by the product warranty. You can
purchase extended warranty coverage and additional support services. These
support contracts are part of the OneControl Product Services suite.
OneControl Product Services

A full suite of optional, value-added services and support contracts is
available for purchase through the OneControl Product Services suite.
The services include:

• extended product warranty support
• advanced technical support
• installation planning and support
• on-site installation
• technical training
• software upgrades
• network planning and integration consultation
• Network Management System Audits and Performance Reports
Contact your Ciena representative for more information about the OneControl
Product Services suite.
CE conformance
There are no European Union Directives that require the fitting of the CE
marking which apply to this software product.

xiv About this document

1-1
Introduction to OneControl 5.0 1-
What is OneControl?
Ciena’s OneControl Unified Management System provides a single solution
for network and service management capabilities across the whole portfolio
of Ciena’s Ethernet, Transport, and Switching services.
OneControl provides a single central platform with a consistent look and feel
for monitoring and managing fault, performance management, service
management, and provisioning across the Layer 0, Layer 1, and Layer 2
network services. OneControl operators can use a common interface to view
and respond to alarms raised by any managed NE in the network, any of the
supported or integrated Element Management Systems (EMSs), and
OneControl itself.
The following software products may also be used in conjunction with

OneControl 5.0:
• Ethernet Services Manager (ESM) 6.6, and associated Integrated
Services Manager (ISM) 5.1.2
For information on ESM and ISM, refer to the ESM Release 6.6 product
documentation.
• OnePlanner 3.5
• Photonic Network Capture (PNC) 4.3
• PinPoint Portal 1.0
The PinPoint Portal application can be installed co-resident on the same
platform as OneControl, or standalone on its own platform. When installed
co-resident with OneControl it does not affect the OneControl engineering
guidelines (all guidelines are the same with or without PinPoint Portal
present). For information on PinPoint Portal and its engineering guidelines
when installed standalone, refer to the PinPoint Portal Fundamentals,
450-3502-001.

1-2 Introduction to OneControl 5.0
OneControl high level architecture

Figure 1-1 on page 1-2 illustrates the OneControl 5.0 functionality
architecture. The OneControl 5.0 architecture is composed of core
components that include Network Map and Navigation, and Fault
Management functionality. It is also composed of various optional licensed
features/components, some of which are installed separately. These features
include support for the provisioning and troubleshooting of various managed
services including wavelength, packet, OTN switched and control plane
services, and SONET/SDH control plane. Northbound OSS integration is also
supported via several different northbound interfaces. For more details on
supported functionality, refer to the OneControl Fundamentals Guide,
450-3201-001.
Figure 1-1
OneControl functionality architecture

Supported/Integrated Element Management Systems

OneControl 5.0 continues to directly embed ON-Center functionality for
management of 4200, CoreStream, CoreDirector and 5400. OneControl 5.0
also continues to integrate Manager for 6k, OM5k and CPL functionality. As in
previous releases, OneControl can be configured to integrate with Ethernet
Services Manager (ESM).
OneControl Integrated Element Management
Manager for 6k, OM5k and CPL
OneControl 5.0 integrates Manager for 6k, OM5k and CPL functionality.
OneControl enables fault management capabilities and element management
applications specific to the network element type being managed. These
applications are available through the Manager for 6k, OM5k and CPL
desktop. Detailed descriptions of Manager for 6k, OM5k and CPL
applications, and procedures for using them, are described in the OneControl
Manager for 6k, OM5k and CPL Standard Operations Guide, 450-3241-301).
Manager for 6k, OM5k and CPL also provides access to other optional
applications such as TMF for northbound integration with OSSs, OSP (Optical
Service Provisioner) for non-Control Plane Layer 1 connection management
and Layer 1 NSV (Network and Service Viewer) for visualization and
troubleshooting of services.
Ethernet Services Manager (ESM)

Ciena’s Ethernet Services Manager (ESM) is a carrier-grade element
management platform for Ciena's Carrier Ethernet Solutions. It performs
device discovery, surveillance, management and can also perform service
creation, activation and management, allowing operators to efficiently build
and manage large-scale Carrier Ethernet networks.
The ESM is a comprehensive suite of integrated software tools built on a low

touch, service-oriented architecture that transparently handles the details of
deploying, delivering, and sustaining Carrier Ethernet services.
Supported network element releases

For the list of network element types and releases supported by the
OneControl 5.0 software, refer to the OneControl Fundamentals,
450-3201-001 (Compatibilities chapter).
Upgrades and migrations

An upgrade to OneControl 5.0 refers to a deployment that is currently running
a previous version of OneControl that needs to move to OneControl 5.0. A
migration to OneControl 5.0 refers to a deployment that currently has Ciena’s
ON-Center, or OSR (including OMEA) network management solution
deployed, that needs to move to OneControl 5.0.

Supported upgrades
The following upgrade paths are supported:
• OneControl 4.0 (with latest patches) to 5.0
For all upgrades, the OneControl release being upgraded from must have all
currently available OneControl patches applied before the upgrade process is
started. For details on available OneControl patches, see “OneControl
software patches” on page 5-52.
For existing customers currently running a version of OneControl older than

4.0, an upgrade can be done to OneControl 4.0 first. Then an upgrade can be
done from OneControl 4.0 to OneControl 5.0.
Attention: Operating system changes/upgrades are not supported for

upgrades. The operating system type and version at the from and to release
of an upgrade must be the same.
Attention: The database used before and after an upgrade must be the
same (MySQL to MySQL, local Oracle to local Oracle, remote Oracle to
remote Oracle, custom remote Oracle to custom remote Oracle, Oracle EE
to Oracle EE, Oracle SE to Oracle SE).
Attention: The OneControl features/licenses present before and after an

upgrade must be the same. If new features/licenses need to be added for use
in OneControl 5.0, this is done as a post-upgrade activity.
In this scenario, two separate license files should be generated. First

generate a license file by assigning all the upgrade licenses required to
upgrade the current features/functionality. Load this license file while
performing the upgrade. After the upgrade is completed, generate a second
license file by assigning any remaining install licenses for the new features
to be used in OneControl 5.0. Use this license file in conjunction with the
appropriate procedure to add functionality post-install.
See OneControl Installation Part 1, 450-3201-201 for details on license files,

and for the procedures for adding OneControl features to an existing
installation.

Attention: When OneControl 5.0 is used with an Oracle database, the

database software must be at release 11.2.0.4. For details on database
requirements, see “Database requirements” on page 5-17.
Some previous releases of OneControl used Oracle database software

11.2.0.1. When upgrading from a OneControl 4.0/4.1 deployment that uses
a Oracle database, part of the upgrade process includes upgrading the
Oracle database and software from 11.2.0.1 to 11.2.0.4.
See OneControl Installation Part 1, 450-3201-201 for details on upgrades.
Attention: OneControl 5.0 introduces a new paradigm for provisioning and

management of wavelength services, which has resulted in workflow
changes. The Wavelength Service Management (WSM) functionality now
provides management of line-to-line services. The management of client
services previously available in WSM is now provided by the Transport
Switched Connections (TSC) functionality.
When upgrading to OneControl 5.0, customers currently using WSM should

review the new behavior to understand the steps involved in maintaining
currently used functionality, and/or to take advantage of additional
functionality provided by TSC.
For additional details, refer to “Understanding the WSM changes in

OneControl 5.0” on page 7-8.
Supported migrations
There are currently no migration paths supported directly to OneControl 5.0.
For existing customers with Ciena's OSR network management solution

deployed, migrations can be done to OneControl 3.0. Then an upgrade can be
done from OneControl 3.0 to OneControl 4.0, and then OneControl 4.0 to
OneControl 5.0.
For existing customers with Ciena's ON-Center network management solution

deployed, migrations can be done to OneControl 3.2. Then an upgrade can be
done from OneControl 3.2 to OneControl 4.2, and then OneControl 4.2 to
OneControl 5.0.


2-1
Deployment configurations 2-
This chapter describes all the various ways in which OneControl 5.0 can be
deployed.
Supported deployments
Architecture
OneControl uses a client-server architecture:
• the OneControl client software can reside on
— a PC platform running the Microsoft Windows operating system
— a server platform running the Citrix on Microsoft Windows operating
system
• the OneControl server software resides on a physical or virtual server
running the Oracle Linux, Red Hat Linux, or Oracle Solaris operating
system. OneControl can also connect to one or more Ciena subordinate
Element Management Systems (EMSes).
Attention: For details on the hardware platform and the operating system
requirements for OneControl client and OneControl server software, see
Chapter 5, “Platform requirements”.
Attention: Some functionality is only available when deploying the

OneControl server software on certain operating system types/releases. See
“Determine platform type and redundancy requirements” on page 7-7.
Attention: The recommended hardware platform for the OneControl client

is a Windows PC or a Citrix server PC, as indicated in this section. The
OneControl client can also be run on a Solaris/Linux platform (using the
Solaris/Linux OneControl client). However, in this scenario, some
considerations apply. For details see “Guidelines and considerations for
choosing OneControl client platform” on page 5-11.

2-2 Deployment configurations
Co-resident and standalone

The figures in this section are intended to represent the installable software
packages associated with OneControl, and their physical location on the
same or separate servers. For a summary of the OneControl software
features from a functionality perspective, see Figure 1-1 on page 1-2.
Features/components are enabled in accordance with the software licenses
purchased.
In a co-resident deployment, OneControl is installed on a server with one

ESM, one Manager for 6k, OM5k and CPL component, or both (see Figure 2-1
on page 2-2).
Figure 2-1
OneControl co-resident with ESM and Manager for 6k, OM5k and CPL

In a standalone deployment, OneControl is installed on a server without ESM

or Manager for 6k, OM5k and CPL. The OneControl can connect to one ESM
on a separate platform. The OneControl can also connect to one or more
instances of the remote Manager for 6k, OM5k and CPL on separate platforms
(see Figure 2-2 on page 2-3).
Figure 2-2
OneControl standalone with Remote Manager for 6k, OM5k and CPL and Remote ESM

It is also possible to have a co-resident deployment where OneControl

connects to both a co-resident instance of the Manager for 6k, OM5k and CPL
component, and a remote instance of the Manager for 6k, OM5k and CPL
component. This allows larger scaling for those NE types managed by the
Manager for 6k, OM5k and CPL component (up to the maximum number
supported by OneControl). If ESM is used in this scenario, it can be installed
co-resident with OneControl or on a separate platform (see Figure 2-3 on
page 2-4).
Figure 2-3
OneControl with both co-resident and Remote Manager for 6k, OM5k and CPL

Database
OneControl software is used in conjunction with a supporting database
(embedded MySQL database, and/or Oracle database separately installed by
the customer). The database that must be used will depend on the
OneControl and network configuration. For details, refer to “Database
requirements” on page 5-17.
Client software
The OneControl client can be downloaded directly from the server. Once the
server is installed clients can be downloaded from:
http://<server>:9001/client.html
See Chapter 5, “Platform requirements” for supported platforms and OS

details on which OneControl clients can be deployed.
All required client software modules, including those related to ESM and
Manager for 6k, OM5k and CPL functionality, are installed as part of the
OneControl client software (or in some cases are automatically downloaded
on the first launch of the related OneControl client menu items).
Mandatory install order for co-resident deployments

For a summary of the OneControl software features from a functionality
perspective, see Figure 1-1 on page 1-2.
When OneControl is installed co-resident with other applications, the

applications must be installed in this order:
• CoreStream Management Software
• OneControl (any licensed components will be enabled)
• ESM
• Any other optional software can be installed at any time after the
OneControl package, including:
— TMF
— UOG
When OneControl is installed, any other optional components that are

deployed on separate platforms can be installed, including:
• Any remote Managers for 6k, OM5k and CPL (with OSP/NSV co-resident
if required)


3-1
Geographical redundancy 3-
This chapter describes how GR (Geographical Redundancy) works for

OneControl 5.0, in the following sections.
• “OneControl redundant configuration using GR” on page 3-1
• “Data synchronized over OneControl security channel” on page 3-7
• “Data synchronized over OneControl GR channel” on page 3-8
• “Data not synchronized in a OneControl GR deployment” on page 3-9
OneControl redundant configuration using GR

OneControl offers the ability to deploy in a Geographical Redundancy (GR)
configuration. Two OneControl platforms, located in geographically diverse
locations, and connected via a communications network, constitute such a
configuration. This configuration provides high availability by allowing clients
to communicate with either site. Data replication is utilized to ensure
consistent user provided data is available in both locations.
Both servers communicate with the network of managed Network Elements

(NEs). Each server receives NE events at (approximately) the same time and
will independently process them (including events such as alarms, packet
service management data, etc.).
For content not emanating from NEs, such as operator entered data, the GR
Channel is used to transport and replicate between sites. If communication
between sites is interrupted, the data is queued (persisted) locally and
transmitted when communication becomes available. Upon receipt, the other
site makes a best-effort approach at applying the received data locally.
Attention: In a GR configuration, both servers in the GR pair should be the

same server model, with the same hardware specifications and running the
same type/release of operating system.

3-2 Geographical redundancy
Figure 3-1 on page 3-2 shows the supported GR configuration in OneControl.
Figure 3-1
Supported OneControl GR configuration
Peer-to-Peer and Active/Backup modes

There are two redundancy modes in OneControl. The one that applies to your
deployment depends on the OneControl and network configuration.
• Peer-to-Peer
— This configuration is used if none of the following OneControl
features/licenses are present:
– 4200
– CoreStream
– SLM
– Transport Switched Connections (this functionality is present
whenever Control Plane service management or OTN service
management licenses are present, or when Wavelength service
management licenses are present and the administrator has
chosen to enable TSC)
— Each site is fully operational. OneControl clients can communicate to
either site with full access.

— Both sites have the ability to create, modify and delete data. Changes
to non-network data at one site are replicated to the other site.
• Active/Backup
— This configuration is used if one or more of the following OneControl
features/licenses are present:
– 4200
– CoreStream
– SLM
– Transport Switched Connections (this functionality is present
whenever Control Plane service management or OTN service
management licenses are present, or when Wavelength service
management licenses are present and the administrator has
chosen to enable TSC)
— The active site is fully operational. OneControl clients communicating
with the backup system have read-only access (with some
exceptions).
— Only the active site has the ability to create, modify and delete data
(with some exceptions). Changes to non-network data at the active
site is replicated to the backup site.
— The network administrator designates the sites with active role or
backup role. The roles can be switched at any time manually (e.g. for
maintenance, or during an active site failure).
Attention: For existing GR setups, if upgrading from a previous release of

OneControl, or migrating from ON-Center, it may be necessary to move from
a Peer-to-Peer GR setup to an Active/Backup GR setup. This is necessary if,
as part of the upgrade/migration, you are adding functionality that is only
supported in Active/Backup mode. Review the GR mode descriptions to
determine if any of the functionality you intend to deploy requires an
Active/Backup GR setup.
The OneControl Installation Part 1, 450-3201-201, details the migration

procedures required for moving from a Peer-to-Peer GR setup to an
Active/Backup GR setup.

Attention: Refer to OneControl Installation Parts 1 & 2, 450-3201-201, for

additional details on the behavior of a GR configuration when 4200,
CoreStream or SLM features are enabled. That document provides
additional guidance on setup and configuration requirements, as well as the
behavior of these components in a GR configuration.
Attention: The database type and version supported for use with
OneControl will depend on the OneControl features and licenses present, as
well as whether GR will be used. For details on which database type/version
must be used for GR configurations, see “Database requirements” on page
5-17.
Forced replication
In a OneControl GR configuration, the user can perform a forced replication of
data.
• Peer-to-Peer
— In peer-to-peer mode, non-network data flows in both directions
between sites.
— A forced replication can be initiated from either site. The force
replication button on both sites is disabled until the operation
completes.
— A forced replication happens in one direction. To have forced
replication in both directions, two separate operations must be
initiated, one from each site.
— The forced replication attempts a best-effort merge of the content from
the initiating site with the content on the target site. At an object level,
the operation does not delete content on the target site, because
neither peer site is the master of the information. For example if
non-network data on peer A is deleted, and peer B does not receive
the notifications (e.g. during communication outage between peers), a
forced replication from peer A to peer B will not remove this content
from peer B. This content needs to be manually deleted at peer B.
• Active/Backup
— In active/backup mode, non-network data flows from the active site to
the backup site.

— A forced replication can be initiated from the active site to the backup
site. The force replication button on the active site is disabled until the
operation is complete. The force replication button on the backup site
is always disabled.
OneControl GR behavior with sub-EMS redundancy

The following is the behavior of OneControl GR with underlying sub-EMS
redundancy:
• OneControl GR with Manager for 6k, OM5k and CPL HA
— Manager for 6k, OM5k and CPL pair is configured as redundant
(Manager for 6k, OM5k and CPL HA).
— Each OneControl site enrolls the Manager for 6k, OM5k and CPL that
is installed co-resident. OneControl discovers that a Manager for 6k,
OM5k and CPL HA pair exists and shows details of the pair. However
it connects to and actively gets data only from the one that was entered
by the user.
— If either OneControl site in peer-to-peer fails, clients can connect to the
other OneControl site.
— If active OneControl site in active/backup fails, administrator must
change OneControl secondary server role to active. Clients can
connect to the other OneControl site.
— If there is a loss of communication between the OneControl core
module and the master Manager for 6k, OM5k and CPL module (e.g.
hardware failure, module failure, restart, etc., of primary Manager for
6k, OM5k and CPL), OneControl will continue to try to regain
communication (and all NEs managed by that Manager for 6k, OM5k
and CPL will have a loss of comms to OneControl). For extended
outages, the administrator can initiate a switch to the peer Manager for
6k, OM5k and CPL. Clients can continue to connect to same
OneControl site as before if it is still available (or can connect to the
other OneControl site if the type of failure results in it not being
available).
— If there is a mastership switch from the current master Manager for 6k,
OM5k and CPL to the peer (with no failure of comms between the
OneControl core module and the primary Manager for 6k, OM5k and
CPL), both OneControl sites continue to connect to the same Manager
for 6k, OM5k and CPL. There is no loss of association to any NEs
during or after the switch. Clients continue to connect to the same
OneControl site as before.
— If the Manager for 6k, OM5k and CPL servers are in a Master - Master
state (e.g. during a communications loss between the servers), any
open OSP GUIs on the original Master switch to read-only mode. Any
open OSP GUIs on the original Slave (now Master) lose visibility to all

the NEs. This OSP GUI will need to be closed, and a new session
opened to clear the LOA condition. The OSP GUIs will communicate
to the local NDS server in all scenarios. In cases where the local NDS
server is not reachable, the OSP GUI will communicate with the NDS
server in the Remote server. There will be a delay (up to 4 minutes)
while launching OSP from secondary server on master-master
scenario.
• OneControl GR with ESM
— ESM is NOT configured as redundant (each ESM is independent). Any
changes on one ESM must be manually done on the other ESM. This
mainly consists of managing devices on both ESMs.
— Each OneControl site enrolls the ESM at its respective site.
— If either OneControl site in peer-to-peer fails, clients can connect to the
other OneControl site.
— If active OneControl site in active/backup fails, administrator must
change OneControl secondary server role to active. Clients can
connect to the other OneControl site.
— If either ESM fails, clients can connect to the other OneControl site
(which has the other ESM enrolled).
Licensing
When you want to install or upgrade a pair of OneControl servers in a GR
configuration, the license file for the primary server has the base OneControl
entitlement and any additional desired entitlements. The license file for the
secondary server has only one entitlement identifying it as a redundant server.
The presence of the redundant entitlement on the OneControl secondary
server enables the same set of features as those entitled on the primary
server. Therefore, you order the entitlements once for the primary server and
those same features are enabled on the secondary server.
When there are Remote Manager for 6k, OM5k and CPL servers in a GR
deployment included in your OneControl deployment, the same approach is
used. The license file for the primary server has the base Remote Manager
for 6k, OM5k and CPL entitlement and any additional desired entitlements.
The license file for the secondary server has only one entitlement identifying
it as a redundant Remote Manager for 6k, OM5k and CPL server.
When communication is lost between the primary server and the secondary
server, the secondary server continues to enable the licensed functionality.
This continues up to 45 days without contact with the primary server, as long
as the software process associated with OneControl licensing is not restarted.

Attention: Any time the software process associated with OneControl

licensing, referred to as the kls_server, is restarted on a secondary server, it
attempts to communicate with the primary server in order to determine what
functionality has been licensed. If it cannot communicate with the primary
server, it cannot retrieve that information and will not be functional.
As a result, during a failure scenario where communication between the

primary server and secondary server is lost, care must be taken not to
perform any action on the secondary server that would result in the
kls_server component being restarted. This includes, but is not limited to,
rebooting the secondary server, manually restarting the kls_server process,
etc.
Data synchronized over OneControl security channel

All user account data is replicated by a security subsystem channel between
the two servers. This channel is separate from the OneControl GR channel
that synchronizes other types of data.

Data synchronized over OneControl GR channel

The following data is synchronized between the two servers when OneControl
is deployed in a GR configuration:
Table 3-1
Data synchronized over OneControl GR channel
Type of data Details about replicated data
Alarms • Annotations
• Manual clears
• Acknowledgements/unacknowledgements of alarms
• OneControl EMS alarm assert and clear
Historical alarms • Annotations

• Manual clear of alarms
• Acknowledgement and unacknowledgement of alarms
• OneControl EMS alarm assert and clear
Note that historical alarms are not copied over the GR channel.
Network Elements • Annotations

• Drawn NE creation/deletion
Links • Annotations
• Drawn link creation/deletion
Groups Group creation, deletion, annotation, background image,

background map scale, and containment relationships
Note: If you add a new image file on the server, assign it to a group
and do a force replication, only the assignment is replicated, not the
image file.
Configuration data • Data retention policies

(Administration GUI content) Note: The content of the geographic redundant configuration and
sub-EMSs configuration is not replicated
Audit logs • All audit logs
User Preferences All user preferences including:

• Watch lists
• Bookmarks
• User defined levels of service (for transport switched connections)
• Dashboard and health monitor layout changes (e.g. panel
shuffling, iconize)
—continued—

Table 3-1 (continued)

Data synchronized over OneControl GR channel (continued)
Type of data Details about replicated data
Security • Security user administration data (user accounts and per-user

attributes, roles, rules, and associations)
• Security settings (user password, user account, login warning text,
RADIUS idle timeout, multiple login, and client inactivity settings)
(see Note 1)
• RADIUS accounting configuration
• External RADIUS configuration, with the exception of the scheme
Note 1: The "Apply to" options in security settings are used
run-time, therefore not saved or replicated in LDAP.
Note 2: The following data is not replicated: user sessions,
RADIUS server secret, and external RADIUS scheme
configuration.
Note 3: Forced replication does not update the security data.
Layer 1 Connections • Annotations

(including SONET/SDH Control • Name
Plane services)
• Label
• Customer name
Wavelength Service Management • Home path of service

(Layer 0) • Original and destination services during a restoration or reversion
operation
Data not synchronized in a OneControl GR deployment

The following data is not synchronized via the GR channel in a GR
configuration:
• GR configuration content is not replicated
• Sub-EMS configuration content is not replicated (including PSM & WSM
configuration data)
• Health Monitor data is not replicated


4-1
Network sizing and engineering

considerations 4-
This chapter details the engineering considerations that apply to OneControl

5.0.
WARNING
The engineering limits in this document were calculated using specific
workstation/server types.
If a higher performance workstation/server is used to exceed the stated
engineering limits, Ciena does not accept responsibility, or provide support
for any performance-related issues which may arise as a result. Ciena
agrees only to provide support for problems that are
non-performance-related when the engineering limits are exceeded.
Customers should also be aware that surpassing these prescribed limits
may lead to behavior which may not be initially perceived to be
performance-related, i.e. corruption, core dumps, etc. In summary,
responsibility for any performance-related issues which arise as a result of
surpassing the prescribed engineering limits must be understood and
accepted by the customer.
If a lower performance workstation/server is used, Ciena does not accept
responsibility, or provide support for any performance-related issues which
may arise as a result. Ciena agrees only to provide support for problems that
are non-performance-related. Customers should also be aware that low
performance may lead to behavior which may not be initially perceived to be
performance-related, i.e. corruption, core dumps, etc. In summary,
responsibility for any performance-related issues which arise as a result of
not using the minimum prescribed platform configuration, must be
understood and accepted by the customer.

4-2 Network sizing and engineering considerations
OneControl 5.0 - How to size and engineer

This section provides an overview of the steps involved to size and engineer
your OneControl solution.
Determine the type of NEs to be managed
The type of NEs managed affect what OneControl components and sub-EMS
components need to be deployed, and may affect the size of hardware
platform required.
Use the sub-headings in Table 4-1 on page 4-9 to determine which of the
following NE types will be managed by OneControl:
• Directly managed in OneControl
• Managed via ESM sub-EMS - In this case the ESM sub-EMS will need to
be installed on the same platform as OneControl, or on a remote platform.
• Managed via Manager for 6k, OM5k and CPL component - In this case the
Manager for 6k, OM5k and CPL component will need to be installed on the
same platform as OneControl, or on a remote platform.
Determine the total number of NEUs/NEs to be managed

The maximum number of network elements (NEs) that can be managed by
OneControl depends on factors including:
• The type of hardware platforms used.
• The software applications installed on the hardware platform.
• The number and types of NEs deployed in the network. Different types of
NEs can place a different load on the software because some NE types
are capable of reporting a larger number of ports and connections than
other NE types. Because of this, the concept of a network element (NE)
equivalent unit is used. In order to engineer your network, you must
calculate the total number of NE equivalent units in your network.
Use Table 4-1 on page 4-9 to calculate:

• The total number of NE equivalent units (NEUs) and NEs you have in your
network.
• The portion of that total NEUs/NEs count that falls into the Managed via
Manager for 6k, OM5k and CPL component sub-category.
Attention: If the total NEUs/NEs count in the Managed via Manager for 6k,
OM5k and CPL component sub-category exceeds the maximums supported
by a hardware platform, you can deploy additional platforms with the Remote
Manager for 6k, OM5k and CPL component.

Determine the type of and number of services to be managed

The type and number of services present in the network may affect the size of
hardware platform required if OneControl will be used for management of
those services.
Determine the following about your network:

• L0 - Max 6500 L0 Ctrl Plane enabled shelves.
• L0 - Max wavelength services present in the network.
• L0 - Max 6500/CPL shelves with WSM supported services on them.
• L2 - Max packet service endpoints present in the network.
• L2 - Max shelves with packet service endpoints terminating on them.
• L2 - Max LSPs
• L1 - Max L1 Ctrl Plane enabled shelves/nodes present in the network
— includes 6500/5430/5410/CD SONET/SDH Ctrl Plane shelves/nodes
if using SONET/SDH Ctrl Plane service management in OneControl,
and
— includes 6500/5430/5410/CD OTN Ctrl Plane shelves/nodes if using
OTN service management in OneControl
• L1 - Max SONET/SDH/OTN CP & OTN non-CP services present in the
network
— includes 6500/5430/5410/CD SONET/SDH Ctrl Plane services if
using SONET/SDH Ctrl Plane service management in OneControl,
and
— includes 6500/5430/5410/CD OTN Ctrl Plane services if using OTN
service management in OneControl, and
— includes 6500 OTN non-Ctrl Plane services if using OTN service
management in OneControl
Attention: In this chapter, Tables 4-2 to 4-12 list the maximum

NEUs/NEs/services supported by OneControl. In these tables, an asterisk
indicates that the corresponding value has changed since the previous
OneControl release.
Determine platform type and whether virtualization is to be used

OneControl server software can be deployed on Oracle SPARC platforms or
Intel platforms.
Virtualization is also supported for larger networks. If virtualization is to be

used, review and understand “Virtualization” on page 4-5.

Determine database requirements

The database type and version supported for use with OneControl will depend
on the OneControl features and licenses present, as well as whether GR will
be used. For details on which database type/version must be used, see
“Database requirements” on page 5-17.
Choose a hardware platform

For deployments without virtualization:
• Refer to “Maximum NEUs/NEs/services” on page 4-12.
• Use the tables corresponding to your operating system (without
virtualization) to decide which hardware platform meets the criteria
identified so far, including:
— Configurations supported
— Max NEUs/NEs enrolled in OneControl
— Max NEUs/NEs enrolled in Manager for 6k, OM5k and CPL
component
— Max services
• Take note of the hardware platform type (and memory) chosen.
• Determine the detailed hardware requirements for the chosen platform
from one of the following tables in Chapter 5: Table 5-1, Table 5-2, Table
5-4, or Table 5-5.
For Oracle SPARC deployments with virtualization:

• Use the tables corresponding to Oracle SPARC deployments with
virtualization, to determine the appropriate LDOM configurations (in terms
of vCPU, memory and disk space) that meet the criteria identified so far.
• Add the vCPU, memory, and disk of the different LDOMs plus the
corresponding resources of the primary LDOM together to obtain the total
vCPU, total RAM and total disk space required for the physical server
holding the LDOMs.
• Use these numbers to select the most appropriate server from the
specifications in Table 5-3 on page 5-6.
For Intel deployments with virtualization:

• Use the tables corresponding to Intel deployments with virtualization, to
determine the appropriate VM configurations (in terms of CPU, memory
and disk space) that meet the criteria identified so far.

• Add the CPU, memory and disk of the different VMs to obtain the total
CPU, total RAM and total disk space required for the physical server
holding the VMs.
• Use these numbers to select the most appropriate server from the
specification in Table 5-6 on page 5-9.
Review and understand all engineering considerations and platform

requirements
Review and understand all remaining engineering considerations in Chapter
4, including:
• “Guidelines and considerations for medium and large networks” on page
4-25
• “OneControl client sessions” on page 4-30
• “OneControl general engineering limits” on page 4-32
• “Bandwidth requirements” on page 4-32
• “Scheduled Jobs and procedures” on page 4-35
Review and understand all platform requirements in Chapter 5, including:

• “Hardware platform requirements” on page 5-3
• “Database requirements” on page 5-17
• “Server platforms - Operating system requirements” on page 5-27
• “Client platforms - Operating system requirements” on page 5-50
• “OneControl software patches” on page 5-52
Virtualization
Operating System (OS) virtualization is supported in OneControl to
consolidate complex multi-server deployments in fewer larger servers, and to
help the load balancing and scalability increase for large and very large
deployments as they grow.
OS virtualization is:
• Not recommended for deployments that are under 1,000 NEUs/NEs. The
benefit of consolidation introduced by the OS virtualization is out-weighed
by the cost of the hardware server specification required.
• Can be considered for deployments that are over 2,000 NEUs/NEs and
where the customer network growth is expected to increase in the future
to above 5,000 NEUs/NEs.
The hardware specifications for OS virtualization supported by OneControl

are based on having a large amount of physical memory available that can be
assigned to the different virtual servers.

Oracle VM for SPARC Solaris virtualization

Oracle VM for SPARC (LDOM) is the supported OS virtualization solution for
Solaris 10 and Solaris 11.1/11.2, for the SPARC T5 and T4 class servers
specified in Table 5-3 on page 5-6.
The solution is based on physical partitions of a server into Logical Domains

(LDOM). Each LDOM is equivalent to an independent server with its own MAC
address, IP address, etc., which runs its own copy of the Solaris operating
system.
On T5/T4 servers running Solaris, virtualization is provided directly at the

firmware level (LDOM hypervisor functionality). In order to use and configure
LDOM virtualization:
• Requirements:
— Operating system: Solaris 10 (10/09 or later) or Solaris 11.1/11.2 (plus
the Ciena recommended bundle)
— Virtualization software:
– When running Solaris 10: Oracle VM for SPARC v 2.2 (obtained
from Oracle via download of patch)
— When running Solaris 11.1/11.2: No additional package is required, it
is integrated with Solaris 11.1/11.2 (Oracle VM for SPARC v2.2)
• Create a primary LDOM for the LDOM administration:
— This provides the ability to create other LDOMs and map physical
server resources to the different LDOMs.
— The primary LDOM uses minimum resources (8 vCPU = 1 core; 8GB
RAM; a dedicated disk for the copy of the Solaris OS installed in the
primary LDOM).
• Create all other LDOMs required on the server:
— Use primary LDOM to create all the other LDOMs required on the
server, and assign them physical resources (CPU, RAM, disk space
and network interfaces)
— Install a copy of the Solaris OS (plus the Ciena recommended bundle)
in each LDOM. Then install the required OneControl components in
each LDOM.
When using OneControl with Solaris 11.1/11.2 in a virtualized environment,

the following should be considered for disk layout:
• Primary LDOM - One physical disk will be used (as rpool for primary
LDOM - use a second disk as a mirror)

• LDOM for remote Oracle - One or more physical disks should be assigned
to the LDOM. Then the disks should be assigned to the required ZFS
pools (rpool, dbpool, onecpool)
• LDOM(s) for OneControl - The remaining multiple physical disks should be
used to create a ZFS pool (ldompool) that uses RAIDZ. Then from that
ldompool, a ZFS volume should be created for and assigned to each
LDOM. This configuration (RAIDZ vs. mirroring) allows for the best
performance from the ZFS file system without sacrificing space (ZFS
performance gets better the more physical disks you use)
• For details on disk layout and ZFS pools, see “Solaris 11.1/11.2 disk layout
- OneControl 5.0” on page 5-38.
As a reference, an example of the LDOM configuration task flow for a

supported server is provided on the Ciena web portal, in the document
entitled: "Solaris 10 and 11.1 LDOM Virtualization - Example".
VMware ESXi for Linux (RHEL/OL) virtualization

VMware ESXi is the supported OS virtualization solution for Red Hat
Enterprise Linux and Oracle Linux, for the Intel servers specified in Table 5-6
on page 5-9.
The solution is based on logical partitions of a server into Virtual Machines

(VMs). Each VM is equivalent to an independent server with its own MAC
address, IP address, etc., which runs its own copy of the RHEL/OL operating
system.
On Intel servers running RHEL/OL, virtualization is provided through the use

of VMware ESXi software. In order to use and configure VMware ESXi VM
virtualization:
• Requirements:
— Operating system: Red Hat Enterprise Linux or Oracle Linux 5.8, 5.9,
5.10, 5.11, 6.4, 6.5 or 6.6 (plus the Ciena Linux OS bundle)
— Virtualization software: VMware ESXi 5.0/5.1/5.5
• Install the VMware ESXi virtualization software on a bare Intel server
• Create all VMs required on the server:
— Use the VMware ESXi HTML-based configuration tool to create VMs,
and assign them physical resources: (CPU, RAM, disk space and
network interfaces)
— Install a copy of the RHEL/OL OS (plus the Ciena recommended
bundle) in each VM. Then install the required OneControl components
in each VM.

As a reference, an example of the VMware ESXi configuration task flow for a

supported Intel server is provided on the Ciena web portal, in the document
entitled: "RHEL OL 5.8 VMware ESXi 5.x Virtualization - Example".

Network element equivalent units (NEUs)

Table 4-1 on page 4-9 defines the number of NE equivalent units that must be
used to represent each NE type, in order to calculate the total number of NE
equivalent units you have in your network.
Table 4-1
Network element equivalent units for each NE type
NE type and configuration NE equivalent units
Directly managed in OneControl
O-APS - 1
2300 - 1.4
FlexSelect 40G - 2
CoreStream Without SOADM 1
With SOADM 2
4200 - 2
4200 MC - 1.4
4200 RS (per shelf) (Note 3) - 4
CoreDirector/CoreDirector CI - 10
(Note 3)
5410 (Optical) Without Control Plane 10
(Note 1, Note 3) With Control Plane 20
5430 Without Control Plane 30
(Note 3) With Control Plane 45
Managed via ESM sub-EMS
LE-311v - 0.5
3902, 3903, 3904, 3905 - 0.2
3911, 3920 - 0.3
3916, 3930, 3931, 3932, - 0.5
3938vi, 3940, 3942
3960 - 1
5140, 5142 - 1
5150 - 1.5
5160 - 3
5305 - 15
5410 (Packet) (Note 2) - 30
8700 4-slot 15
(Note 3) 10-slot 45
—continued—


Managed via Manager for 6k, OM5k and CPL component
CPL shelf (Note 4) - 1
5100 / 5200 / 565 - 1 (0-25%), 1.7 (26-50%)
(Note 7) 2.4 (51-75%), or 3.0 (76-100%)
6110 - 1
6130 / 6150 / 6200 No VT/VC 1
(Note 5) Full VT/VC below 1500 connections 1
Full VT/VC above 1500 connections 2
6500 Broadband shelf or With 0 to 10 SuperMux cards 1
Photonic shelf, with or With 11 to 14 SuperMux cards 2
without Layer0 Control Plane
(Note 6, Note 9)
6500 MSPP shelf, STS-1/VC-3 X-Conn - 2 (0-25%), 3.3 (26-50%)
(32-slot, 14-slot, 7-slot) 80G, 160G/0G, or 240G/0G (Note 7) 4.6 (51-75%), or 6 (76-100%)
(Note 6, Note 9) STS-1/VC-3 X-Conn - 8
640G/0G
VT-1.5/VC-12 X-Conn - 8
20G/20G, or 80G/20G
(Note 8)
VT-1.5/VC-12 X-Conn - 9
80G/80G, or 240G/80G - 32% full
(Note 8)
VT-1.5/VC-12 X-Conn - 14
80G/80G, or 240G/80G - 50% full
(Note 8)
VT-1.5/VC-12 X-Conn - 28
80G/80G, or 240G/80G - 100% full
(Note 8)
SONET/SDH Control Plane enabled 45
shelf
6500 PKT/OTN shelf PKT/OTN X-Conn - 600G 1
(32-slot, 14-slot, 7-slot) PKT/OTN X-Conn - 1200G 1
(Note 6, Note 9)
PKT/OTN X-Conn - 1600G 2
PKT/OTN X-Conn - 3200G 2
OTN Control Plane enabled shelf 45
6500 (2-slot) (Note 6, Note 9) - 0.15
6500 eMOTR card (Note 9) Add this value to total, for each eMOTR 1.5
card present in the network
—continued—


Note 1: The NEU value in this 5410 row, is for the Optical version of the NE managed directly in
OneControl. For the Ethernet version managed via ESM, see the 5410 row in the “Managed via ESM
sub-EMS” section of this table.
Note 2: The NEU value in this 5410 row, is for the Ethernet version of the NE managed via ESM. For
the Optical version, see the 5410 row in the “Directly managed in OneControl” section of this table.
Note 3: The equivalent units value provided is for a network element (NE) that is fully loaded. If the NE
is not fully loaded, the value can be multiplied by the percentage of the NE bandwidth that will be used.
Note 4: CPL supports the Consolidated Channel Access (CCA) NE configuration. In this configuration,
the NEU value must be calculated for each shelf separately in the consolidated NE.
Note 5: For 6130/6150 NEU weighting, in this context, a connection is a uni-directional cross connect.
Note 6: 6500 supports the Consolidated NE (CNE) NE type. In this configuration, the NEU value must
be calculated for each shelf separately in the consolidated NE.
Note 7: The equivalency unit that must be used depends on what percentage of the total NEs enrolled
in the Manager for 6k, OM5k and CPL are configured with 15-min PM collection enabled:
•0-25%: use the first equivalency unit provided
•26-50%: use the second equivalency unit provided
•51-75%: use the third equivalency unit provided
•76-100%: use the fourth equivalency unit provided
Note 8: The equivalent units value provided is for a network element (NE) fully loaded and configured
with only VT/VC (low order) connections. The value is higher on a fully loaded VT/VC managed NE
because the number of alarms and connections that OMEA must manage is much higher (as compared
to an NE with no VT/VC connections). If the NE is not fully loaded with VT/VC, the value can be multiplied
by the percentage of the NE bandwidth that will be VT/VC managed. Note that the minimum equivalent
units for the NE cannot be lower than what is specified for the NE with no VT/VC management.
Note 9: If eMOTR cards are present on any 6500 shelves, these add an additional amount to the total
NEUs in your network. The total NEUs for all 6500 shelves should be calculated as before. An additional
amount of (1.5*Number of eMOTR cards present in the network) should be added to the total.

Maximum NEUs/NEs/services
Tables 4-2 to 4-12 list the maximum number of NEUs, NEs, and services by
supported platform type. Before referring to the details you must know what
type of platform will be used (Oracle SPARC or Intel), and whether
virtualization will be used.
For Oracle SPARC deployments without virtualization, see:

• Table 4-2, “ Max NEUs/NEs/services - Oracle SPARC - NO virtualization (Part 1 of 3)”
For Oracle SPARC deployments with virtualization, see:

• Table 4-5, “ Max NEUs/NEs/services - Oracle SPARC - WITH virtualization (Part 1 of 3)”
For Intel deployments without virtualization, see:

• Table 4-8, “ Max NEUs/NEs/services - Intel - NO virtualization (Part 1 of 3)”
For Intel deployments with virtualization, see:

• Table 4-11, “ Max NEUs/NEs/services - Intel - WITH virtualization (Part 1 of 2)”
• Table 4-12, “ Max NEUs/NEs/services - Intel - WITH virtualization (Part 2 of 2)”
Notes applicable to all tables

The following notes apply to all tables from Table 4-2 to 4-12
• L0 - Max 6500 L0 Ctrl Plane enabled shelves - This engineering limit
details the maximum supported number of 6500 L0 Ctrl Plane enabled
shelves doing Ctrl Plane switches concurrently. The maximum value
assumes that each L0 Ctrl Plane shelf has 44 wavelengths. Note that:
— In a consolidated TID configuration (TIDc), the function of each shelf
must be considered separately. Any shelves within the TIDc that are
used for L0 Ctrl Plane should be counted as 1.
— If the entry in this row is N/A for a particular column / platform type, this
means that this platform type is not supported for management of a
6500 L0 Ctrl Plane network.
— If the shelves have more/less than 44 wavelengths, the max value
must be decreased/increased proportionately. For example if all the L0
Ctrl Plane enabled shelves have a maximum of 88 wavelengths, the

the value provided in the table must be halved. On the other hand if all
the L0 Ctrl Plane enabled shelves have a maximum of 22 wavelengths,
the value provided in the table can be doubled.
— For example: If the platform used is a T4-2 (64GB RAM), according to
Table 4-2, the maximum number of 6500 L0 Ctrl Plane enabled
shelves doing Ctrl Plane switches concurrently is 50. This assumes
that each L0 Ctrl Plane shelf has 44 wavelengths per shelf. The L0 Ctrl
Plane network can consist of more than 50 shelves, however any fault
must not result in more than 50 shelves having to re-route wavelengths
at one time.
If in fact all the L0 Ctrl Plane enabled shelves have a maximum of 22

wavelengths, the value provided in the table can be doubled to 100
(2*50).

Table 4-2
Max NEUs/NEs/services - Oracle SPARC - NO virtualization (Part 1 of 3)
Max NEUs/NEs/services (based on co-resident apps & T4-4 (2x8-core) (128G), OR T4-2 (2x8-core) (128G), OR
features/licenses) T5-2 (2x16-core) (256G) T5-2 (1x16-core) (128G)
Configurations Supported
OneControl (with or w/o ESM and Manager for 6k/OM5k/CPL) √ √
Remote Manager for 6k, OM5k and CPL √ √
Support for deployments requiring Oracle DB √ √
Support for Oracle DB co-resident with OneControl √ √
Support for use as Remote Oracle DB server √ √
Max NEUs/NEs enrolled in OneControl
OneControl (with or w/o ESM) Oracle DB: 12,000/12,000 Oracle DB: 12,000/12,000
MySQL DB: 20,000/20,000 MySQL DB: 15,000/15,000
OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM) Oracle DB: 12,000/12,000 Oracle DB: 12,000/12,000
MySQL DB: 20,000/20,000 MySQL DB: 15,000/15,000
Max NEUs/NEs enrolled in Manager for 6k, OM5k and CPL component (Note 1)
continued in Table 4-3

OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM) 3,000/3,000 3,000/3,000
Remote Manager for 6k, OM5k and CPL 3,000/3,000 3,000/3,000
Max services
L0 - Max 6500 L0 Ctrl Plane enabled shelves doing Ctrl Plane

100 80
switches concurrently (up to 44 wavelengths per shelf) (Note 2)
L0 - Max wavelength services (Note 1) Oracle DB: 4,000 Oracle DB: 3,000
MySQL DB: 10,000 * MySQL DB: 4,700 *
L0 - Max 6500/CPL shelves with WSM supported services Oracle DB: 4,000 Oracle DB: 2,000
MySQL DB: 10,000 * MySQL DB: 3,500 *
L2 - Max packet service endpoints Oracle DB: 50,000 Oracle DB: 50,000
MySQL DB: 100,000 MySQL DB: 100,000
L2 - Max shelves with packet service endpoints terminating Oracle DB: 10,000 Oracle DB: 10,000
L2 - Max LSPs 3,000 * 2,000 *
L1 - Max L1 Ctrl Plane enabled shelves/nodes Oracle DB: 300 * Oracle DB: 300 *
(6500/5430/5410/CD) MySQL DB: 500 * MySQL DB: 375 *
L1 - Max SONET/SDH/OTN CP & OTN non-CP services Oracle DB: 60,000 * Oracle DB: 30,000 *
MySQL DB: 90,000 * MySQL DB: 45,000 *
Note 1: Each Manager for 6k, OM5k, and CPL component supports up to a maximum of 3,400 L0 wavelength services. In order
to support more L0 wavelength services under OneControl, deploy additional Remote Manager for 6k, OM5k, and CPL instances.
Note 2: For details on this limit, see “Notes applicable to all tables” on page 4-12.
* In this table, an asterisk indicates that the corresponding value has changed since the previous OneControl release.

Table 4-3
Max NEUs/NEs/services (based on co-resident apps & T4-2 T4-1 T4-1 M5000
features/licenses) (64G) (64G) (32G) (128G)
OneControl (with or w/o ESM and Manager for

√ √ NO √
6k/OM5k/CPL)
Remote Manager for 6k, OM5k and CPL √ √ √ √
Support for deployments requiring Oracle DB √ √ N/A √
Support for Oracle DB co-resident with OneControl √ √ N/A √
Support for use as Remote Oracle DB server √ √ √ √
OneControl (with or w/o ESM) 6,000/ 3,000/ 7,200/

5,000 2,000 8,000
N/A
OneControl + Manager for 6k, OM5k and CPL (with or w/o 6,000/ 2,800/ 7,200/
ESM) 4,000 1,400 8,000
Max NEUs/NEs enrolled in Manager for 6k, OM5k and CPL component

OneControl + Manager for 6k, OM5k and CPL (with or w/o 3,000/ 2,000/ 2,000/
N/A
ESM) 3,000 3,000 3,000
Remote Manager for 6k, OM5k and CPL 3,000/ 2,000/ 1,100/ 2,000/
3,000 3,000 1,500 3,000
Max services
L0 - Max 6500 L0 Ctrl Plane enabled shelves doing Ctrl

Plane switches concurrently (up to 44 wavelengths per 60 50 N/A 80
shelf) (Note 1)
L0 - Max wavelength services Oracle DB: 1,200

700 N/A 1,600
MySQL DB: 2,000 *
L0 - Max 6500/CPL shelves with WSM supported services Oracle DB: 1,000
550 N/A 1,100
MySQL DB: 1.500 *
L2 - Max packet service endpoints 50,000 20,000 N/A 10,000
L2 - Max shelves with packet service endpoints terminating 5,000 2,500 N/A 8,000
L2 - Max LSPs 1,500 * 1,000 * N/A 500 *
L1 - Max L1 Ctrl Plane enabled shelves/nodes

300 * 300 * 300 * 300 *
(6500/5430/5410/CD)
N/A 4,500
MySQL DB: 22,500 * MySQL DB: 10,000 *

Table 4-4
Max NEUs/NEs/services (based on co-resident apps & T3-2
features/licenses) (64G)
OneControl (with or w/o ESM and Manager for 6k/OM5k/CPL) √
Remote Manager for 6k, OM5k and CPL √
Support for deployments requiring Oracle DB √
Support for Oracle DB co-resident with OneControl √
Support for use as Remote Oracle DB server √
OneControl (with or w/o ESM) 4,500/

2,500
OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM) 4,500/
1,600
OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM) 2,000/2,000
Remote Manager for 6k, OM5k and CPL 2,000/2,000
Max services

50
L0 - Max wavelength services 900
L0 - Max 6500/CPL shelves with WSM supported services 600
L2 - Max packet service endpoints 20,000
L2 - Max shelves with packet service endpoints terminating 4,000
L2 - Max LSPs 800 *

300 *
(6500/5430/5410/CD)
L1 - Max SONET/SDH/OTN CP & OTN non-CP services 2,000

Table 4-5
Max NEUs/NEs/services - Oracle SPARC - WITH virtualization (Part 1 of 3)
Max NEUs/NEs/services (based on co-resident apps & Number of virtual CPUs (vCPUs) and amount of
features/licenses) RAM assigned to LDOM
128 vCPU (T5-2 OR T4-4) (128G)
Remote Manager for 6k, OM5k and CPL -
Size of Oracle DB required if remote Large
Support for use as Medium Remote Oracle DB server -
Support for use as Large Remote Oracle DB server -
OneControl (with or w/o ESM) Oracle DB: 15,000/15,000

MySQL DB: 20,000/20,000
OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM)
Max services

100
L0 - Max wavelength services (Note 1) Oracle DB: 4,000, MySQL DB: 10,000 *
L0 - Max 6500/CPL shelves with WSM supported services Oracle DB: 4,000, MySQL DB: 10,000 *
L2 - Max packet service endpoints Oracle DB: 50,000, MySQL DB: 100,000
L2 - Max shelves with packet service endpoints terminating Oracle DB: 10,000, MySQL DB: 20,000
L2 - Max LSPs 3,000 *

Oracle DB: 300 *, MySQL DB: 500 *
(6500/5430/5410/CD)
L1 - Max SONET/SDH/OTN CP & OTN non-CP services Oracle DB: 60,000 *, MySQL DB: 90,000 *

Table 4-6
Max NEUs/NEs/services (based on co-resident apps & Number of virtual CPUs (vCPUs) and amount of
features/licenses) RAM assigned to LDOM
128 vCPU (T4-2) (128G)
Size of Oracle DB required if remote Large
Support for use as Medium Remote Oracle DB server -
Support for use as Large Remote Oracle DB server -
OneControl (with or w/o ESM) Oracle DB: 12,000/12,000

MySQL DB: 15,000/15,000
OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM)
Max services

80
L0 - Max wavelength services (Note 1) Oracle DB: 3,000, MySQL DB: 5,000 *
L0 - Max 6500/CPL shelves with WSM supported services Oracle DB: 2,000, MySQL DB: 3,500 *
L2 - Max packet service endpoints Oracle DB: 50,000, MySQL DB: 100,000
L2 - Max shelves with packet service endpoints terminating Oracle DB: 8,000, MySQL DB: 15,000
L2 - Max LSPs 2,000 *

Oracle DB: 300 *, MySQL DB: 500 *
(6500/5430/5410/CD)
L1 - Max SONET/SDH/OTN CP & OTN non-CP services Oracle DB: 30,000 *, MySQL DB: 45,000 *

Table 4-7
Max NEUs/NEs/services (based on co-resident apps & Number of virtual CPUs (vCPUs) and amount of RAM
features/licenses) assigned to LDOM
64 vCPU 32 vCPU 64 vCPU 56 vCPU 32 vCPU 32 vCPU

(64G) (64G) (48G) (48G) (32G) (24G)

√ NO NO NO NO
(Note 1)
Remote Manager for 6k, OM5k and CPL - - √ √ √ NO
Support for deployments requiring Oracle DB √ NO N/A N/A N/A N/A
Support for Oracle DB co-resident with OneControl √ N/A N/A N/A N/A N/A
Size of Oracle DB required if remote Medium N/A N/A N/A N/A N/A
Support for use as Medium Remote Oracle DB server - - - - - √
Support for use as Large Remote Oracle DB server - - - - √ NO

N/A
7,200/ 4,000
8,000
OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM) N/A N/A
N/A N/A
3,000
Remote Manager for 6k, OM5k and CPL 2,000/ 1,700/ 900/
- - N/A
3,000 2,600 900
Max services

60 N/A N/A
switches concurrently (up to 44 wavelengths per shelf)
L0 - Max wavelength services 1,000 500 N/A
L0 - Max 6500/CPL shelves with WSM supported services 1,000 600 N/A
L2 - Max packet service endpoints 25,000 2,500 N/A
L2 - Max shelves with packet service endpoints terminating 5,000 2,000 N/A
L2 - Max LSPs 1,500 * 800 * N/A

200 * N/A N/A
(6500/5430/5410/CD)
L1 - Max SONET/SDH/OTN CP & OTN non-CP services 3,000 * N/A N/A
Note 1: Not supported with Manager for 6k, OM5k, and CPL component installed co-resident (only ESM can be installed
co-resident). Can be used in conjunction with a Remote Manager for 6k, OM5k, and CPL instance if required.

Table 4-8
Max NEUs/NEs/services - Intel - NO virtualization (Part 1 of 3)
Max NEUs/NEs/services (based on co-resident apps & BL680c BL620c G7, BL660c G8 *
features/licenses) G7 (128G) (128G)
Remote Manager for 6k, OM5k and CPL √ √
Support for use as Remote Oracle DB server √ √
OneControl (with or w/o ESM)

Oracle DB: 8,000/8,000
OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM) MySQL DB: 10,000/10,000
OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM) 2,000/3,000 2,000/3,000

Remote Manager for 6k, OM5k and CPL 2,000/3,000 2,000/3,000
Max services

100 100
MySQL DB: 5,500 * MySQL DB: 2,500 *
MySQL DB: 5,500 * MySQL DB: 2,500 *
L2 - Max LSPs 3,000 * 3, 000 *

200 * 200 *
(6500/5430/5410/CD)
MySQL DB: 70,000 * MySQL DB: 35,000 *

Table 4-9
Max NEUs/NEs/services (based on co-resident apps & BL680c BL620c G7, X5-2 System DL360c
features/licenses) G7 (64G) BL660cG8* 2x8core X, R820, G7,DL3
(64G) (128G) * DL560c 60p G8
G8 (64G) (64G)
OneControl (with or w/o ESM and Manager for 6k/OM5k/CPL) √ √ √ √ √
Remote Manager for 6k, OM5k and CPL √ √ √ √ √
Support for deployments requiring Oracle DB √ √ √ √ √
Support for Oracle DB co-resident with OneControl √ √ √ √ √
Support for use as Remote Oracle DB server √ √ √ √ √
OneControl (with or w/o ESM) 5,000/ 5,000/ 2,000/ 2,000/ 1,500/

2,000 2,000 2,000 * 2,000 1,500
OneControl + Manager for 6k, OM5k and CPL (with or w/o 3,000/ 3,000/ 2,000/ 2,000/ 1,500/
ESM) 2,000 2,000 2,000 * 2,000 1,500

OneControl + Manager for 6k, OM5k and CPL (with or w/o 2,000/ 2,000/ 2,000/ 2,000/ 1,500/
ESM) 3,000 3,000 2,000 * 3,000 1,500
Remote Manager for 6k, OM5k and CPL 2,000/ 2,000/ 2,000/ 2,000/ 1,500/
3,000 3,000 3,000 * 3,000 1,500
Max services

80 80 80 * 80 50
L0 - Max wavelength services 1,200 1,200 2,500 * 900 550
L0 - Max 6500/CPL shelves with WSM supported services 1,000 1,000 2,000 * 1,000 500
L2 - Max packet service endpoints 50,000 * 50,000 * 50,000 * 10,000 5,000
L2 - Max shelves with packet service endpoints terminating 4,000 4,000 2,000 * 1,500 800
L2 - Max LSPs 1,500 * 1,500 * 1,400 * 1,200 * 1,200 *

160 * 160 * 160 * 160 * 160 *
(6500/5430/5410/CD)
L1 - Max SONET/SDH/OTN CP & OTN non-CP services Oracle DB: Oracle DB:
25,000 * 12,500 *
5,000 * 1,000 500
MySQL DB: MySQL DB:
35,000 * 17,500 *

Table 4-10
Max NEUs/NEs/services (based on co-resident apps & X5-2, X4-2 X4-2 OR 4270 2270 2270 4270
features/licenses) 2x8core X3-2 M2 M2 M2 M2
OR X3-2 2x4core (64G) (64G) (32G) (48G)
2x6-core (48G)
(64G)

√ √ √ √ NO
(Note 2)
Remote Manager for 6k, OM5k and CPL √ √ √ √ √ NO
Support for deployments requiring Oracle DB √ √ √ √ NO N/A
Support for Oracle DB co-resident with OneControl √ NO √ NO NO N/A
Support for use as Remote Oracle DB server √ √ √ NO NO √
OneControl (with or w/o ESM) 800/ 500/

500 500
1,000/ 500/ 1,000/
N/A
1,000 500 1,000
OneControl + Manager for 6k, OM5k and CPL (with or w/o 500/ 300/
ESM) 500 300
OneControl + Manager for 6k, OM5k and CPL (with or w/o 300/
ESM) 300
1,000/ 500/ 1,000/ 500/
N/A
Remote Manager for 6k, OM5k and CPL 1,000 500 1,000 500 300/
300
Max services

50 50 50 50 N/A
L0 - Max wavelength services 2,000 1,500 1,200 1,200 900
L0 - Max 6500/CPL shelves with WSM supported services 2,000 1,500 1,000 1,000 1,000
L2 - Max packet service endpoints 50,000 50,000 25,000 25,000 10,000

N/A
L2 - Max shelves with packet service endpoints terminating 8,000 8,000 4,000 4,000 1,500
L2 - Max LSPs 1,200 * 900 * 900 * 900 * 300 *

160 * 160 * 160 * 160 * 160 *
(6500/5430/5410/CD)
L1 - Max SONET/SDH/OTN CP & OTN non-CP services 4,000 4,000 2,000 2,000 1,000
Note 2: Not supported with Manager for 6k, OM5k, and CPL component installed co-resident (only ESM can be installed
co-resident). Can be used in conjunction with a Remote Manager for 6k, OM5k, and CPL instance if required.

Table 4-11
Max NEUs/NEs/services - Intel - WITH virtualization (Part 1 of 2)
Max NEUs/NEs/services (based on co-resident apps & Number of cores and amount of RAM
features/licenses) assigned to VM
2x10-core 2x8-core
(128G) (128G)
Remote Manager for 6k, OM5k and CPL - -
Support for use as Remote Oracle DB server - -
OneControl (with or w/o ESM)

Oracle DB: 10,000/10,000
OneControl + Manager for 6k, OM5k and CPL (with or w/o ESM) MySQL DB: 15,000/15,000

Max services
L0 - Max 6500 L0 Ctrl Plane enabled shelves doing Ctrl Plane switches
100 100
concurrently (up to 44 wavelengths per shelf) (Note 2)
MySQL DB: 10,000 * MySQL DB: 6,000 *
MySQL DB: 10,000 * MySQL DB: 6,000 *
L2 - Max LSPs 3,000 * 3,000 *
L1 - Max L1 Ctrl Plane enabled shelves/nodes (6500/5430/5410/CD) 200 * 200 *
MySQL DB: 42,000 * MySQL DB: 35,000 *

Table 4-12
Max NEUs/NEs/services - Intel - WITH virtualization (Part 2 of 2)
Max NEUs/NEs/services (based on co-resident apps & Number of cores and amount of RAM assigned to VM
features/licenses)
2x10-core, OR 1x 1x 1x
2x8-core 8-core 8-core 8-core
(64G) (64G) (48G) (32G)
OneControl (with or w/o ESM and Manager for 6k/OM5k/CPL) √ √ NO NO
Remote Manager for 6k, OM5k and CPL - - √ √
Support for deployments requiring Oracle DB √ √ N/A N/A
Support for Oracle DB co-resident with OneControl √ NO N/A N/A
Support for use as Remote Oracle DB server - - - √

2,000
5,000/
N/A
5,000
1,200
2,000/3,000 N/A
1,200
Remote Manager for 6k, OM5k and CPL 2,000/ 2,000/

3,000 2,000
Max services

80 80
L0 - Max wavelength services 1,500 900
L0 - Max 6500/CPL shelves with WSM supported services 2,000 900
L2 - Max packet service endpoints 50,000 * 10,000

N/A
L2 - Max shelves with packet service endpoints terminating 5,000 2,000
L2 - Max LSPs 1,500 * 1,000 *

160 * 160 *
(6500/5430/5410/CD)
L1 - Max SONET/SDH/OTN CP & OTN non-CP services Oracle DB: 12,500 *

500
MySQL DB: 17,500 *

Guidelines and considerations for medium and large networks

The following guidelines should be taken into account for medium and large
networks:
• ESM as a sub-EMS
— The recommended memory allocation requirement for ESM should be
a minimum of 2 GB. If your deployment involves more than 2,000 NEs,
the allocated memory should be increased to 6GB. Refer to the ESM
documentation for details.
— If ESM needs to be halted, and ESM is managing more than 5,000
NEs, you should wait at least 20 minutes after the halt, before
restarting ESM.
— If ESM needs to be halted, and ESM is managing more than 10,000
NEs, it is recommended that OneControl should be halted first (and
then restarted after ESM has been restarted).
• Adding and removing sub-EMSs
— When adding a sub-EMS to OneControl, an initial discovery and
alignment is performed for all NEs managed by that sub-EMS. Once
this has begun, the alignment process to all NEs should be allowed to
complete. During this process, the sub-EMS should not be removed
from OneControl.
— When removing a sub-EMS from OneControl, all NEs managed by
that sub-EMS are removed from the map view. Once this has begun,
the removal of all NEs should be allowed to complete. During this
process, the sub-EMS should not be re-managed in OneControl.
• Status of managed NEs
— When doing a restart of a OneControl with more than 15,000 NEs
managed, some NEs may remain in Suspect state after the restart. If
this occurs, those NEs can be manually resynched (either individually,
or all at once, using the State column to sort the entries and then bulk
select and resynch).
• Managing 5430/5410/CD/6500 Control Plane networks
— A 5430/5410/CD/6500 Control Plane network must have at least one
gateway NE (GNE) defined for the NEs in the Control Plane network
to be managed by OneControl. It is recommended that no more than
one of these GNEs be enrolled in OneControl, and allow the remaining
NEs in that Control Plane network to be auto-discovered via that GNE
(i.e. in the NE Configuration/Discovery Administration dialog, only the
GNE IP should be added). Adding more than one GNE per network to
OneControl can introduce performance degradation and instability.

— For Control Plane networks being newly enrolled - Ensure that any
6500 NEs involved in the Control Plane network are enrolled in the
Manager for 6k, OM5k and CPL component before enrolling the
5430/5410/CD/6500 GNE in the NE Configuration/Discovery
Administration dialog (i.e. standard procedure for dual enrolled 6500
NEs).
— For existing Control Plane networks where new NEs are being added
- If a new 5430/5410/CD NE is being added, it is recommended that
the Force Discovery functionality be used to trigger discovery of the
new NE. If a new 6500 NE is being added, it is recommended that the
NE first be enrolled in the Manager for 6k, OM5k and CPL component,
and then the Force Discovery functionality be used to trigger discovery
of the new NE (Force Discovery functionality is available within the NE
Configuration/Discovery Administration dialog).
• Network map
— The recommended maximum number of entities that can be placed in
any map group is 2,000 (entities include NEs, links, and off page
connectors). This applies to any group that can be selected from the
navigation tree, including the top level map group. Any entities in the
stage area of a map group are considered to be part of that group.
— As soon as the first network discovery completes following the
management of a large network, it is recommended that NEs be
moved from the stage area to map groups. This should be done before
beginning any service provisioning, or in general launching any
applications reporting a network map.
— The time needed to move NEs from the stage area to the map varies
depending on the size of the managed network (eg. with 20,000 NEs
managed, it could take 7-8 seconds per NE being moved).
— If your deployment includes more than 1,000 NEs that are not placed
on the network map, it is not recommended to open the network map
(or PWSM, Managed/Provisioned TSC GUIs), until all of the NEs have
completed synching.
• Retrievals of historical data
— When retrieving historical alarms from the OneControl client or
Manager for 6k, OM5k and CPL client, it is recommended that the
search criteria be restricted to avoid delays or timeouts in the retrieval
of the desired information.
— When retrieving historical PMs from the Manager for 6k, OM5k and
CPL client, it is recommended that the search criteria be restricted to
avoid delays or timeouts in the retrieval of the desired information.
— The maximum number of records displayed for any query is 10,000.
The search criteria can be adjusted to target the time period desired.

• Packet Service Management

— The max number of packet service endpoints includes all packet
service endpoints present on all managed devices, whether or not
Packet Service functionality in OneControl is enabled/used.
— The time needed to perform the initial discovery and alignment of all
packet services when a sub-EMS is first added to OneControl varies
depending on the size of the managed network. On a managed
network consisting of up to 1,000 service endpoints, this initial
alignment process can take more than 1 hour (this alignment occurs
in parallel with initial alignment of wavelength services).
— Performing a search within PSM using the partial string match
functionality may take a long time to complete for large networks (eg.
with more than 10,000 NEs managed, it could take 3-4 minutes for the
search to complete if a large number of entries match the search
criteria).
— Some types of PSM services may require a long time to be fully
provisioned in the network (eg. very large E-LAN service
configurations with many endpoints may take 8-10 minutes to
complete). When provisioning services, always wait for the
provisioning task to complete in the PSM GUI before moving onto
another task (i.e. wait for a confirmation that the provisioning task has
completed successfully, or an error message indicating that the
provisioning task has failed). Performing other operations in the GUI,
or closing the OneControl client, before a provisioning task is complete
may result in complete or partial provisioning failure and/or the
OneControl client becoming unresponsive.
• Wavelength Service Management
— The time needed to perform the initial discovery and alignment of all
wavelength services when a sub-EMS is first added to OneControl
varies depending on the size of the managed network. On a managed
network consisting of 700 shelves and 1,200 wavelength services, or
more, this initial alignment process can take over 6 hours.
• Transport Switched Connections
— The launch of the Transport Switched Connections tab (Manage TSC
or Provision TSC tab) can take up to 2 minutes for networks with over
4,500 transport switched connection services.
— For customers who need to use TSC to manage only non-Control
Plane services, OneControl can be configured so that it does not
discover OTN and SONET/SDH Control Plane services in the
managed network. For details, refer to the OneControl Service
Management Guide, 450-3201-302.

• Additional configuration settings for larger networks

— Table 4-13 on page 4-28 lists additional configuration settings that are
required for larger networks. Each entry identifies the name and
location of the file affected, as well as the line within that file that must
be changed. The value within that line that must be changed is in bold
blue characters. Note that in all cases the file referenced is located on
the OneControl server, and that if the file does not exist on your server,
then your deployment does not include the affected component.
Table 4-13
Additional settings for larger networks
Setting, location and name Value for Value for Value for
small medium large
networks networks networks
(500-1000 (1000-2000 (2000-3000+
NEUs) NEUs) NEUs)
Client - When using UNIX or Windows (64-bit) clients 1024 1024 2048
Files:
/var/opt/CIENAoc/install_location/template/emsclient.jnlp
/var/opt/CIENAoc/install_location/client/emsclient.jnlp
Line:
<j2se version="1.6*" java-vm-args="-XX:PermSize=64M
-XX:MaxPermSize=128M" initial-heap-size="128M"
max-heap-size="368M"
Client - When using Windows (32-bit) clients 1024 1024 1024

Files:
/var/opt/CIENAoc/install_location/template/emsclient.jnlp
/var/opt/CIENAoc/install_location/client/emsclient.jnlp
Line:
<j2se version="1.6*" java-vm-args="-XX:PermSize=64M
-XX:MaxPermSize=128M" initial-heap-size="128M"
max-heap-size="368M"
OC Server 2048 2560 3072

Files:
/var/opt/CIENAoc/install_location/template/startManagedWebLogic.sh
/var/opt/CIENAoc/install_location/installdir/template/startManagedWebLo
gic.sh
/var/opt/CIENAoc/install_location/user_projects/domains/oncenter/startM
anagedWebLogic.sh
Line:
MEM_ARGS="-Xms768m -Xmx2048m -Xss512k
-XX:MaxPermSize=256m -XX:HeapDumpPath=${OC_LOGS}
-XX:+HeapDumpOnOutOfMemoryError"
—continued—

Table 4-13
Additional settings for larger networks
Setting, location and name Value for Value for Value for
small medium large
networks networks networks
(500-1000 (1000-2000 (2000-3000+
NEUs) NEUs) NEUs)
NCS Client 1024 1024 2048

Files:
/var/opt/CIENAoc/install_location/template/NcsClientProperties/jem.xml
/var/opt/CIENAoc/install_location/ems_client/ncsPortUtil/ncs/jem.xml
Line:
<ARG>-Xmx1024m</ARG>
JSNMP receive buffer 1048576 1048576 2097152

File:
/var/opt/CIENAncs/install_location/ipi/ncs/config/jsnmp.properties
Line:
receiveBufferSize=1048576
NBI server 1024 1024 2048

File:
/var/opt/CIENAnbi/install_location/bin/startNBI.sh
Line:
exec java -ms32m -mx192m -XX:HeapDumpPath=${NBI_LOGS}
-XX:+HeapDumpOnOutOfMemoryError \
IPI Mediator 1024 2048 3072

Files:
/var/opt/CIENAoc/install_location/template/ems_cluster.properties
/var/opt/CIENAoc/install_location/installdir/template/cienaClasses/server/
cluster/ems_cluster.properties
/var/opt/CIENAoc/install_location/user_projects/domains/oncenter/ciena
Classes/server/cluster/ems_cluster.properties
Line:
mediatorGroup.ipi.stdVms.vmArgs=-Xms256m;-Xmx512m;-Dorg.omg.C
ORBA.ORBClass=org.jacorb.orb.ORB;-Dorg.omg.CORBA.ORBSingleto
nClass=org.jacorb.orb.ORBSingleton;-Dweblogic.ThreadPoolSize=40;-D
ORBInitRef.NameService=corbaloc::47.114.250.166:5656/NameService;
-Dweblogic.ThreadPoolPercentSocketReaders=33;-Dcom.ciena.ems.ser
ver.mediation.ncs.propertyfilename=/opt/ciena/ON-Center/OC/4.2.1c/CIE
NAoc/user_projects/domains/oncenter/cienaClasses/server/mediators/nc
s/etc/NCSml.properties;-Dems.config=/opt/ciena/ON-Center/OC/4.2.1c/C
IENAoc/user_projects/domains/oncenter/cienaClasses/server/mediators/
ncs/etc/IpiMediatorConfigBootstrap.xml

OneControl client sessions

Maximum OneControl client GUIs on a client only platform
Table 4-14 on page 4-30 lists the maximum number of concurrent OneControl
GUIs that a client only platform can support.
Table 4-14
Maximum number of OneControl client GUIs per client platform
Type of OneControl client Maximum number of OneControl client GUIs

platform supported per client platform
Windows PC (single client) 1

(Note 1, Note 2)
Windows server (multiple 40

clients using Remote
Desktop)
Citrix server PC (multiple 40

clients)
(Note 2)
Note 1: Only one OneControl client GUI is supported on a Windows PC (even if

more than one can be launched on the same PC). Only one exception exists. For
scenarios where OneControl GR is used, a second OneControl client GUI can be
launched on the same PC to connect to the other server in the same GR pair at the
same time. This second GUI is only supported for brief actions. It should not be used
for an extended period of time, and should not be used for resource intensive
operations.
Note 2: In terms of GUI Cut-through (i.e. sub-EMS application launch from within
OneControl), each OneControl client GUI can launch one sub-EMS GUI session
from within the OneControl Tools menu, i.e. one Manager for 6k, OM5k and CPL
GUI, one ESM session.

Maximum client sessions to a OneControl server

Table 4-15 on page 4-31 lists the maximum number of OneControl GUI
sessions that can be connected to a OneControl server concurrently.
Table 4-15
Maximum number of remote client sessions to a OneControl server
Maximum remote client session connections
Platform model of OneControl server from a Windows/Citrix PC
to a OneControl server (Note 1, Note 2)
LDOM (128 vCPU, 128G), 75 *

T5-2 (2x16-core,256G), T5-2 (1x16-core,128G), T4-4 (128G)
T4-2 (128GB), 65 *
VM (2x10-core, 128G), VM (2x8-core, 128G),
HP BL680cG7 (128G), HP BL620cG7 (128G), HP BL660cG8 (128G)
System X (128G), R820 (128G) 45 *
M5000 (128GB) 40
LDOM (64 vCPU, 64G), 35 *

T4-2 (64G),
VM (2x10-core, 64G), VM (2x8-core, 64G),
X5-2 (2x8-core, 128G), HP BL680cG7 (64G), HP BL620cG7 (64G),
HP BL660cG8 (64G)
T3-2 (64G), 30
System X (64G), R820 (64G), HP DL560cG8 (64G)
T4-1 (64G), 27
X5-2 (2x8-core, 64G), X4-2 (2x8core, 64G), X3-2 (2x6core, 64G), 4270
M2 (64G)
VM (1x8-core, 64G), 25
HP DL360p G8 (64G), HP DL360cG7 (64G)
LDOM (32 vCPU, 64G), 20

2270 M2 (64G)
X4-2 (2x4core, 48G), X3-2 (2x4core, 48G) 12
Note 1: The OneControl client GUI can also be installed on the same platform as the OneControl server. This allows client
sessions to be run locally (as opposed to those connecting from a remote PC). In this scenario the total number of remote
sessions supported is reduced according to the formula:
(Total remote clients) + 3*(Total local clients) <= (Max remote clients supported)
Example: If the OneControl server is installed on a T4-2 platform with 128GB of RAM, these are possible combinations of total
concurrent client sessions allowed to that OneControl server:
• 50 remote Windows PC client sessions, or
• 15 remote Windows PC + 5 remote Citrix PC + 10 local client sessions, or
• 16 local client sessions
Exception: For T4-1 (64GB) running Solaris 11.x, replace the number 3 with the number 5 in the formula above.
Note 2: Although multiple remote client sessions can connect to a OneControl server, when running the Solaris/Linux OneControl
client, only one client is supported within a given UNIX login session (a second, separate, UNIX login session can be opened to
run another client).

OneControl general engineering limits

Table 4-16 on page 4-32 lists additional engineering limits that apply to
OneControl.
Table 4-16
General engineering limits for OneControl
Engineering parameter Value
Maximum number of users that can be defined in OneControl 500
Historical alarms (number of days that it will be stored on the server) 1 to 31 days
(Default 7 days)
Total number of logs (audit logs) that can be stored on the server 1 to 45 days
Maximum number of Manager for 6k, OM5k and CPL (single servers or HA 5
pairs) managed in OneControl
Bandwidth requirements
Table 4-17 on page 4-32 to Table 4-21 on page 4-35 detail OneControl
bandwidth requirements.
Table 4-17
OneControl bandwidth requirements
Communications channel Recommended bandwidth
OneControl server OneControl client GUI 1.5 Mbits/s per OneControl

(from PC) GUI session
OneControl server Remote Manager for 6k, 10 Mbits/s

OM5k and CPL server
OneControl server ESM 10 Mbits/s
OneControl server OneControl server 10 Mbits/s

(GR Configuration) (GR Configuration)

Table 4-18
Manager for 6k, OM5k and CPL bandwidth requirements

(Note 4, Note 5)
Manager CPL 128 kbits/s per NE (Note 1)

for 6k,
OM5k and 5100/5200 128 kbits/s per NE
CPL 6110/6130/6150/6200 128 kbits/s per NE
6500 4.0 128 kbits/s per NE
6500 5.0 and higher 200 kbits/s per NE (Note 2)
Manager for 6k, OM5k and CPL GUI (from PC 1.5 Mbits/s per Manager for 6k, OM5k and
or SUN) CPL GUI session
Applications Platform 1.544 Mbits/s per Manager for 6k, OM5k

and CPL GUI session +
1.544 Mbits/s per NE craft session
(up to maximum of 100Mbits/s)
Manager for 6k, OM5k and CPL (between 10 Mbits/s +

Manager for 6k, OM5k and CPL servers in HA 1.5 Mbits/s per Manager for 6k, OM5k and
pair) CPL GUI session (Note 3)
UNIX Emulator desktop 1.544 Mbits/s
Note 1: CPL supports the Consolidated Channel Access (CCA) NE configuration. In this NE
configuration, multiple CPL shelves can be grouped together and share the same TID, with each shelf
having a unique shelf number. For NEs in this configuration, the recommended bandwidth is equal to
the value in this table, multiplied by the number of CPL shelves that form the CCA NE.
Note 2: 6500 supports the Consolidated NE (CNE) NE type. In this NE configuration, multiple 6500
shelves can be grouped together and share the same TID, with each shelf having a unique shelf
number. For NEs in this configuration, the recommended bandwidth is equal to the value in this table
multiplied by the number of shelves that form the CNE.
Note 3: The required bandwidth between Manager for 6k, OM5k and CPL servers in an HA pair
includes a fixed minimum (10Mbits/s) and an amount per Manager for 6k, OM5k and CPL GUI session
established by a user (1.5 Mbits/s per Manager for 6k, OM5k and CPL GUI session).
Note 4: The average delay on any segments of the DCN should not exceed 200ms, and these DCN
segments should have no packet loss. This includes DCN segments from the OneControl platforms to
the NEs, between OneControl platforms, and between OneControl platforms and platforms where user
sessions are launched.
Note 5: All DCN, DCC, and bandwidth rules must be respected on the NEs being managed. This
includes the scenario where NEs are set up in a GNE (Gateway Network Element) configuration. GNEs
must be configured to support the total bandwidth required for Manager for 6k, OM5k and CPL to
manage all remote NEs through the GNE.

Table 4-19
L1 NSV bandwidth requirements
NSV Applications Platform 1.544 Mbits/s per NSV GUI session

(Standalone or (up to maximum of 100Mbits/s)
co-resident
with OMEA)
NSV Between Resilient Pairs 1.544 Mbits/s

(Standalone or
co-resident
with OMEA)
NSV Between NSV servers 1.544 Mbits/s

(co-resident (NSV server to NDS server)
with OMEA)
Table 4-20
OSP bandwidth requirements
NDS server Network Element Controllers 1.544 Mbits/s

component of (Note 1)
OSP
(co-resident
with AP)
NDS server OSP GUI component of OSP 3 Mbits/s minimum (for first 5 OSP
component of (co-resident with AP) GUI sessions) +
OSP + 100 Kbits/s per additional OSP
(co-resident GUI session
with AP) (Note 2, Note 3)
Note 1: This is the same as the bandwidth requirements between AP and element
controllers. No additional bandwidth is required for OSP.
Note 2: This is in addition to the bandwidth required between the two platforms for
AP communications. The required bandwidth between AP platforms must be
calculated separately and added.
Note 3: The bandwidth values provided are for a typical OSP GUI session, however
sessions that involve intensive operations will require more bandwidth. For example,
an OSP GUI session can require up to 900 Kbits/s when doing retrievals against
large systems with 22,000 connections.

Table 4-21
TMF bandwidth requirements
TMF AP 1.54 Mbits/s

(on dedicated Solaris platform)
TMF TMF client 1.54 Mbits/s per client

(on dedicated Solaris platform) session session
(Note 1)
Note 1: In order to achieve optimum performance, it is recommended that the TMF

Interface platform have a 10Mbits/s link to the network and that TMF Interface client
sessions are run on the same LAN segment as the TMF Interface platform.
Attention: Some configurations may require more than 100 MBit/s of

bandwidth. In these configurations a 10/100 Mbit/s LAN card is not sufficient.
See http://www.oracle.com for compatible LAN cards that have more
capacity, such as 1000 Mbits/s.
Scheduled Jobs and procedures

The following scheduled jobs/procedures run automatically on the OneControl
server to perform specific tasks:
• A historical database purge scheduler runs at 2:30am local time, every 24
hours, to clean up the historical alarms once the maximum age and
retention period as defined by the user has been reached, or a% of
maximum database space has been reached. Users can change the
retention criteria (e.g. the number of days historical alarms can be stored)
but not how often or when the scheduler runs.
• Removal of map data (removal of elements de-enrolled from the map for
more than 7 days) is enforced by another data scheduler which runs at
1:00am local time.
• Data deletion is done via special functions available within the DB
enterprise configuration where tables are configured in data partitions
based on age. Data deletion is therefore done by removing entire data
partitions which is efficient in terms of resource usage (i.e. a large amount
of data can be quickly removed with low CPU activity). Direct access to the
database in terms of invoking SQL commands (or queries) is not available
to end users.


5-1
Platform requirements 5-
This chapter details the hardware, operating system and database

requirements that apply to OneControl 5.0.

5-2 Platform requirements
ATTENTION
The hardware platforms and configurations explicitly mentioned in this guide have been used to validate the
OneControl 5.0 functionality, performance, and scalability. Therefore Ciena recommends deploying
OneControl on these hardware models and in these configurations to ensure best results for the software in
terms of installation, functionality, performance, scalability levels, and product support.
For Linux OS deployments, the OneControl application will also install and run on other Intel based hardware
platforms not validated by Ciena. Although it is not possible for Ciena to test OneControl on all customer
desired hardware platforms/configurations, Ciena would like to accommodate our customers' needs to do
deploy on alternative platforms if possible. As such, limited product support will be provided should a
customer choose to deploy OneControl 5.0 on a non-validated, Intel processor based server. Ciena will
investigate customer raised product issues. If an issue is encountered that can be reproduced on a validated
platform/configuration, Ciena will support the resolution of that issue as it would were it found on a validated
platform/configuration. To reduce the risk of encountering platform related issues with the deployment, it is
recommended that Intel based platforms from the following vendors be selected if choosing to deploy on a
server that Ciena has not validated with OneControl; HP, Oracle, Dell or IBM.
Caveats to the support that is provided include, but are not limited to, the following:
• This is regarding Linux based deployments on Intel/x86_64 processor based servers only. AMD processors
based servers are not supported. For Solaris OS based deployments only Oracle SPARC processor based
servers are supported, and only the systems that are recommended in the Engineering Guide.
• It is required that the chosen platform be specified with a sufficient amount of resources (CPU, RAM, Hard
Disks) for the particular application configuration and network to be managed. This means resources which
are at least at the level specified for the recommended platform of equivalent size in this guide.
• If OneControl is deployed in a non-validated configuration Ciena must be informed of the details of the
configuration upon completion of the installation. Please contact your Ciena Customer Support Manager or
sales representative, who will provide this information to Global Product Support.
• The customer acknowledges that due to the untested environment full root cause analysis may not be
possible for issues encountered related to the particular environment, or investigations impeded by the
particular environment.
• Performance and Scalability guarantees can only be provided on validated platforms/configurations.
• The customer accepts the risk that an issue may be encountered which is due to the untested release lineup.
If such an issue is encountered and determined to be due to the specific untested configuration, and if the
issue would require product changes to resolve or cannot be resolved, then the customer:
– would have to await the fix or enhancement in a future release of OneControl, or OneControl patch
bundle, should Ciena be able to and decide to implement a fix, OR
– deploy the OneControl software on a validated configuration in order and resolve the issue until/unless
the fix is delivered in a future OneControl release or OneControl patch bundle, OR
– accept the product issue or functional limitation that is associated with the issue.
• In general, Ciena will not validate OneControl 5.0 on specific customer desired hardware platforms or
configurations. Should a customer want Ciena to do so, please contact your Ciena sales representative to
discuss pursuing this via a Professional Service.
If there are doubts as to whether platforms/configurations would or would not be covered under this limited
support statement, please contact your Ciena technical representative.

Hardware platform requirements

This section provides the recommended hardware requirements for both
OneControl server and OneControl client platforms.
Attention: Before choosing a hardware platform, review “OneControl 5.0 -

How to size and engineer” on page 4-2 of this document. It provides an
overview of the steps involved to size and engineer your OneControl
solution, and guides you through the information you will need to gather in
order to decide which platform is the most appropriate for your deployment.
Server platform requirements

The OneControl server is supported on Oracle SPARC server platforms and
Intel server platforms:
• Oracle SPARC deployments without virtualization - Table 5-1 specifies
the Oracle SPARC platforms that are recommended for new deployments
without virtualization. Table 5-2 specifies the Oracle SPARC platforms that
continue to be supported for existing deployments without virtualization.
• Oracle SPARC deployments with virtualization - Table 5-3 specifies the
Oracle SPARC platforms that are recommended and supported for
deployments with virtualization.
• Intel platform deployments without virtualization - Table 5-4 specifies
the Intel server platforms that are recommended for new deployments
without virtualization. Table 5-5 specifies the Intel server platforms that
continue to be supported for existing deployments without virtualization.
• Intel platform deployments with virtualization - Table 5-6 specifies the
Intel server platforms that are recommended and supported for
deployments with virtualization.
Attention: For deployments that use the Manager for 6k, OM5k and CPL in
conjunction with AP (formerly the OMEA deployment for all NE Types), refer
to Chapter 8, “Appendix A - AP platform requirements & engineering
considerations” to determine the requirements for HP hardware platforms.

Table 5-1
Oracle SPARC platforms - Recommended for new deployments WITHOUT virtualization
Architecture Oracle SPARC
Hardware and OS specs
Model (Note 1, Note 2) T5-2 T5-2 T4-1 T4-1
CPU 2x 16-core 1x 16-core 1x 8-core 1x 8-core

SPARC T5 SPARC T5 SPARC T4 SPARC T4
3.6 GHz 3.6 GHz 2.85 GHz 2.85 GHz
RAM (GB) (Note 3) 256 128 64 32
Hard disks (GB) (Note 4) 6 x 600 6 x 600 2 x 600 2 x 600
Operating System Solaris 10/11.1/11.2 (Refer to “Solaris OS version required” on page 5-28 for
details)
OneControl (with or w/o ESM

and Manager for √ √ √ NO
6k/OM5k/CPL)
Remote Manager for 6k, OM5k

√ √ √ √
and CPL
Support for deployments

√ √ √ N/A
requiring Oracle DB
Support for Oracle DB

√ √ √ N/A
co-resident with OneControl
Support for use as Remote

√ √ √ √
Oracle DB server (Note 5)
Note 1: Both Enterprise and Netra versions are supported.

Note 2: The Management of CoreStream software is not supported on Solaris 11.x (only Solaris 10).
Note 3: Do not use memory DIMMS smaller than 8GB per DIMM to allow for memory upgrades.
Note 4: The number of disks specified assumes half the disks are optionally used for disk mirroring (i.e. in a 6x600
disk configuration, 3 disks will be actively used by OneControl).
Note 5: If the platform is being used as a Remote Oracle DB server, use 4x600 GB hard disks.

Table 5-2
Oracle SPARC platforms - Supported for existing deployments WITHOUT virtualization
Architecture Oracle SPARC
Model (Note 1, Note 2) T4-4 T4-2 M5000 T3-2
CPU 2x 8-core 2x 8-core 1x 4-core 2x 16-core

SPARC T4 SPARC T4 SPARC64 V11 SPARC T3
3.0 GHz 2.85 GHz 2.4GHz 1.65 GHz
RAM (GB) 128 128 64 128 64
Hard disks (GB) (Note 3, Note 4) 6 x 600 6x600 4x600 14 x 300 6 x 600
Operating System Solaris 10/11.1/11.2 (Refer to “Solaris OS version required” on page 5-28
for details)
Configurations supported
OneControl (with or w/o ESM and

√ √ √ √ √
Manager for 6k/OM5k/CPL)
Remote Manager for 6k, OM5k and

√ √ √ √ √
CPL
Support for deployments requiring

√ √ √ √ √
Oracle DB
Support for Oracle DB co-resident

√ √ √ √ √
with OneControl
Support for use as Remote Oracle DB

√ √ √ √ √
server
Note 1: Both Enterprise and Netra versions are supported.

Note 3: The number of disks specified assumes half the disks are optionally used for disk mirroring (i.e. in a 6x600
disk configuration, 3 disks will be actively used by OneControl).
Note 4: If the platform is being used as a Remote Oracle DB server, use 3x600 GB hard disks.

Table 5-3
Oracle SPARC platforms - Recommended and supported for deployments WITH virtualization
LDOM Configuration Primary OneControl Remote Manager for 6k, Remote Oracle DB
(Note 2, Note 3, Note 4) LDOM OM5k and CPL
Large Medium
Platform model See Note 1

When deployed in a virtualized Oracle SPARC LDOM environment, OneControl is only
supported and certified for the Oracle SPARC hardware platforms specified in the note.
vCPUs to assign to 8 128 64 32 64 56 32 32 32

LDOM (Note 7)
RAM (GB) 8 128 64 64 48 48 32 32 24
Hard disk space 1 x 300 4 x 600 2 x 600 2 x 600 2 x 600 2 x 600 2 x 600 4 x 600 3 x 600
assigned to LDOM(GB) (Note 5) (Note 6) (Note 6)
Local Oracle DB N/A YES YES N/A N/A N/A N/A N/A N/A
Remote Oracle DB N/A Large Medium N/A N/A N/A N/A N/A N/A
Operating System Solaris 10/11.1/11.2 (Refer to “Solaris OS version required” on page 5-28 for details)
Virtualization software: Oracle VM for SPARC 2.2 or later

(Refer to “Oracle VM for SPARC Solaris virtualization” on page 4-6 for details)
Note 1: When deployed in a virtualized Oracle SPARC LDOM environment, OneControl is only supported and certified on
LDOMs:
Hard Min/max Max vCPU available after
Model CPUs disks RAM(GB) primary LDOM assigned
• T5-2 2x16-core SPARC T4, 3.6 GHz 6x600GB 256/512 248
• The T5-2 model is recommended for new deployments
• The T4-4,T4-2 and T4-1 models continue to be supported for existing deployments
• Both Enterprise and Netra versions are supported
• Do not use memory DIMMS smaller than 8GB per DIMM to allow for memory upgrades
Note 2: Use the LDOM configuration specified in this table to calculate how many LDOMs can be housed on each of the
supported hardware models. Each physical hardware platform must have one primary LDOM defined. Eg. In a T4-2, you can split
the hardware into one primary LDOM (8vCPUs), one medium OneControl LDOM (64 vCPUs), and one medium Remote Manager
for 6k, OM5k and CPL (56 vCPUs).
Note 3: The T5-2 server can accommodate a maximum of 6 internal disks. If using the T5-2 in a virtualized environment, and in
conjunction with disk mirroring, these 6 disks may not be enough to configure the maximum number of LDOMSs supported by the
total vCPUs available. In this scenario, an additional external attached disk storage solution may be required. Please contact your
Ciena technical representative for guidance if this scenario applies to you.
Note 5: The primary LDOM requires 1 dedicated disk of at least 300GB.
Note 6: If remote Oracle DB LDOM is used, hard disk requirement for OneControl LDOM can be reduced to 2 x 600.
Note 7: Not supported for deployments that require an Oracle DB. Not supported with Manager for 6k, OM5k, and CPL
component installed co-resident (only ESM can be installed co-resident). Can be used in conjunction with a Remote Manager for
6k, OM5k, and CPL instance if required.

Table 5-4
Intel platforms - Recommended for new deployments WITHOUT virtualization
Architecture Intel (Note 1, Note 2, Note 3)
Model HP HP HP IBM Dell R820 HP HP Oracle

BL680c BL660c BL620c System X DL560c DL360p X5-2
G7 G8 G7 3690 X5 G8 G8
CPU (Intel Xeon) 2x8-core 2x8-core 2x8-core 2x8-core 2x8-core 2x8-core 2x6-core 2x8-core
E7-4800 E5-4620 E7-2830 E5-2830 E5-4640 E5-4650 E5-2640 E5-2650
2.13GHz v2 2.13GHz 2.13GHz 2.4GHz, 2.7GHz 2.5GHz, 2.5GHz
2.6GHz E5-4640v2 E5-2630
2.2 GHz, or v2 2.6
E5-4650 GHz
2.7GHz
RAM(GB) (Note 4,Note 5) 128 64 128 64 128 64 128 64 128 64 64 64 128 64
Hard disks (Note 6) 4x 2x 2x 2 x 1.2TB 2 x 1.2TB 2x 2x 6 x 4x

1.2TB 1.2TB 1.2TB 1.2TB 1.2TB 600 600
GB GB
Operating System Red Hat Enterprise Linux or Oracle Linux: 5.8, 5.9, 5.10, 5.11, 6.4, 6.5, 6.6 (64-bit)
(Refer to “Linux OS version required” on page 5-28 for details)
OneControl (with or w/o

ESM and Manager for √ √ √ √ √ √ √ √ √ √ √ √ √ √
6k/OM5k/CPL)
Remote Manager for 6k,

√ √ √ √ √ √ √ √ √ √ √ √ √ √
OM5k and CPL

√ √ √ √ √ √ √ √ √ √ √ √ √ √
requiring Oracle DB
Support for Oracle DB co-

√ √ √ √ √ √ √ √ √ √ √ √ √ √
resident with OneControl
Support for use as

√ √ √ √ √ √ √ √ √ √ √ √ √ √
Remote Oracle DB server
Note 1: External Alarm Interface (EAI) supported only on Solaris 10, 11.1 & 11.2, and Linux 5.8, 5.9, 5.10, 5.11 &
6.6 (not supported on Linux 6.4, 6.5). Management of CoreStream supported only on Solaris 10 (not supported on
Linux, Solaris 11.x).
Note 2: Linux platforms are not supported for use in conjunction with the legacy Preside AP software. If you intend
to use OneControl’s Manager for 6k, OM5k and CPL component in conjunction with Preside AP, all Manager for 6k,
OM5k and CPL components (local or remote) must be deployed on Solaris platforms.
Note 3: For multi blade deployments, up to 2 x BL680cG7 blades, or up to 4 x BL620cG7 blades, are supported
using a C3000 enclosure. To allow for future growth, a C7000 enclosure can be used.
Note 4: Do not use memory DIMMS smaller than 8GB per DIMM to allow for memory upgrades
Note 5: If the platform is being used as a Remote Oracle DB server, the amount of RAM can be dropped to 32G.
Note 6: If the platform is being used as a Remote Oracle DB server, use 2x1 TB hard disks.

Table 5-5
Intel platforms - Supported for existing deployments WITHOUT virtualization
Architecture Intel (Note 1, Note 2)
Model HP Oracle X4-2 Oracle X3-2 Oracle Oracle 2270

DL360c 4270 M2 M2
G7
CPU (Intel Xeon) 2x6-core 2x8-core 2x4-core 2x 6-core 2x 4-core 2x 6-core 2x 4-core
E5649 E5-2650 E5-2609 E5-2640 E5-2609 X5675 E5620
2.53GHz 2.5GHz 2.50GHz 2.5 GHz 2.40 GHz 3.06 GHz 2.40 GHz
RAM (GB) (Note 3) 64 64 48 64 48 64 48 64 32
Hard disks 2x 4 x 600 2x 4x600 GB 2x 4 x 600 or 2 x 600 2 x 600

1.2TB GB 600GB or 1x1.2 TB 600GB 1 x 1.2 TB GB GB
OneControl only √ √ √ √ √ √ NO √ √
OneControl + ESM √ √ √ √ √ √ NO √ √
OneControl + ESM +
√ √ √ √ √ √ NO √ NO
Manager for 6k/OM5k/CPL
Remote Manager for 6k,

√ √ √ √ √ √ NO √ √
OM5k and CPL

√ √ √ √ √ √ N/A √ NO
requiring Oracle DB
Support for Oracle DB

√ √ NO √ NO √ N/A NO NO
co-resident with OneControl
Support for use as Remote

√ √ √ √ √ √ √ NO NO
Oracle DB server
Note 1: External Alarm Interface (EAI) supported only on Solaris 10, 11.1 & 11.2, and Linux 5.8, 5.9, 5.10, 5.11 &
6.6 (not supported on Linux 6.4, 6.5). Management of CoreStream supported only on Solaris 10 (not supported on
Linux, Solaris 11.x).
Note 2: Linux platforms are not supported for use in conjunction with the legacy Preside AP software. If you intend
to use OneControl’s Manager for 6k, OM5k and CPL component in conjunction with Preside AP, all Manager for 6k,
OM5k and CPL components (local or remote) must be deployed on Solaris platforms.
Note 3: If the platform is being used as a Remote Oracle DB server, the amount of RAM can be dropped to 48G.

Table 5-6
Intel platforms - Recommended and supported for deployments WITH virtualization
VM Configuration (Note 2, OneControl Remote Manager for Remote
Note 4, Note 5, Note 6) 6k, OM5k and CPL Oracle DB
Platform model See Note 1 - When deployed in a virtualized Intel VMware environment, OneControl is only
supported and certified for the Intel hardware platforms specified in the note.
CPUs to assign to VM 2x10-core 2x8-core Intel 1x8-core Intel 1x8-core Intel Xeon 1x8-core
Intel Xeon Xeon E7-4830, Xeon E7-4830, E7-4870, Intel Xeon
E7-4870 E7-2830 E7-2830 E7-4830,E7-2830 E7-2830
VMware config: (Note 3)

Virtual sockets: 2 2 1 1 1
Cores per socket: 10 8 8 8 8
Total cores: 20 16 8 8 8
RAM (GB) 128 / 64 128 / 64 64 64 / 32 32
Hard disk space for VM 1.2TB 1.2TB 500GB 500GB or 1.2TB 2 x 1.2TB
Local Oracle DB YES YES NO N/A N/A
Virtualization software: VMware ESXi 5.0/5.1/5.5
(Refer to “VMware ESXi for Linux (RHEL/OL) virtualization” on page 4-7 for details)
Note 1: When deployed in a virtualized Intel VMware environment, OneControl is only supported and certified on VMs created
on the following hardware platforms. Use of different vendor hardware models with the same Intel Xeon CPU specifications does
not guarantee the same capacities, throughputs and response times, and can only be supported on a best effort basis:
Disk slots Max RAM Total cores
Model Max CPUs possible available possible possible
• HP BL680cG7 4x10-core E7-4870, 2.4 GHz 4x1.2TB 2.0TB 40
• HP BL680cG7 4x8-core E7-4830, 2.13 GHz 4x1.2TB 2.0TB 32
• IBM System x3690 X5 2x8-core E7-2830, 2.13GHz 2x1.2TB 512GB 16
• Dell R820 4x8-core E5-4650, 2.7GHz 16x1.0TB 1.5TB 32
• HP DL560c G8 4x8-core E5-4650, 2.7G Hz 5x1.2TB 1.5TB 16
• HP BL660c G8 2x8-core E5-4620v2, 2.6 GHz 2x1.2TB 1.0TB 16
• HP BL620c G7 2x8-core E7-2830, 2.13 GHz 2x1.2TB 1.0TB 16
• Most platforms can be ordered with number of CPUs desired (from 1 to max)
• On most platforms the max RAM possible decreases proportionately if the max CPUs possible
is not used (eg. BL680cG7 with only 2 CPUs can have max RAM of 1TB)
• Memory DIMMs of up to 32G each may be required to reach the max RAM possible
• Requirements in this table refer to cores (not to be confused with logical processors, which
is a parameter VMware displays for CPUs that support hyperthreading).
Note 2: Use the VM configuration specified in this table to calculate how many VMs can be housed on each of the supported
hardware models. Eg. In a BL620cG7, you can create two Remote Manager for 6k, OM5k and CPL VMs (each one requires 8
physical cores, and the BL620cG7 has a total of 16 physical cores available).
Note 3: The VMware config required is in terms of virtual sockets, cores per socket and total cores (the parameters displayed
when creating a new VM). Post-creation, the VM config summary displays this as CPUs or vCPUs. To see if an existing VM meets
OneControl requirements, ensure you compare cores (not logical processors). The required CPU resources must be fully
reserved for OneControl, and not be oversubscribed. Oversubscription can result in CPU resources not being available during
high volume network events. If oversubscription is used, the OneControl performance detailed in this guide cannot be guaranteed.
Note 4: For multi blade deployments, up to 2 x BL680cG7 blades, or up to 4 x BL620cG7 blades, are supported using a C3000
enclosure. To allow for future growth, a C7000 enclosure can be used.
Note 5: Linux platforms are not supported for use in conjunction with the legacy Preside AP software. If you intend to use
OneControl’s Manager for 6k, OM5k and CPL component in conjunction with Preside AP, all Manager for 6k, OM5k and CPL
components (local or remote) must be deployed on Solaris platforms.
Note 6: External Alarm Interface (EAI) supported only on Solaris 10, 11.1 & 11.2, and Linux 5.8, 5.9, 5.10, 5.11 & 6.6 (not
supported on Linux 6.4, 6.5). Management of CoreStream supported only on Solaris 10 (not supported on Linux, Solaris 11.x).

Client platform requirements

The OneControl client is supported on the hardware platforms specified in
Table 5-7.
Table 5-7
Client hardware platforms
Platform Windows PC Windows PC Citrix server PC Oracle SPARC or Intel
architecture (single client) (multiple clients) (multiple clients) hardware platform
(multiple clients)
Platform model Intel based PC Intel based PC Intel based PC All Oracle SPARC
platforms (running
CPU Dual Core Quad Core (eg. i7) Quad Core (eg. i7) Solaris), and all Intel
2.2 GHz or better 3 GHz or better 3 GHz or better hardware platforms
(running Linux) that are
RAM (GB) 4 (Note 1, Note 2) 64 (Note 3) 64 (Note 3)
supported for OneControl
Hard disk free 20 (Note 4) 200 (Note 5) 200 (Note 5) server. Must meet same
space (GB) OS requirements and
Ciena OS bundle
Operating • Windows 7 • Windows 2012 • Windows 2008 requirements as those for
System Professional, Server (64-bit) Server R2 (64-bit) OneControl server.
Ultimate or using Remote running Citrix Xen
Enterprise Edition Desktop App 5.6 or 6.0
(32-bit & 64-bit) (Note 7, Note 8) (Note 9)
(Note 6)
Browser • IE 6.1 or later • IE 6.1 or later • IE 6.1 or later

• Firefox 3.6.x or • Firefox 3.6.x or later • Firefox 3.6.x or later
later
Limitations and Refer to “Guidelines and considerations for choosing OneControl client platform” on page 5-11
considerations for important considerations when choosing platform for OneControl client.
Note 1: At least 1.5 GB of the RAM must be reserved for the OneControl client only.
Note 2: This configuration allows for 2 instances of the Integrated Site Manager functionality to be launched per
OneControl client.
Note 3: This configuration allows for 3-4 instances of the Integrated Site Manager functionality to be launched per
OneControl client. If more instances are required additional RAM is required (approximately 300MB per Integrated
Site Manager instance, per OneControl client).
Note 4: The hard disk space listed for Windows PC (single client) is for the OneControl client only. Any space
required for the Windows operating system and other user files must be added to this value.
Note 5: The hard disk space listed for Windows PC (multiple clients) & Citrix server PC (multiple clients) includes
the space required for the OneControl client, the Windows operating system (and the Citrix Xen App software if
applicable).
Note 6: Refer to “Windows OS requirements (single client platforms)” on page 5-50 for details.
Note 7: Refer to “Windows OS requirements (multiple client platforms)” on page 5-50 for details.
Note 8: When using the OneControl client on a Windows 2012 platform, desktop experience mode should not be
turned off. This functionality is required for using the Site Manager functionality (NE Manager for 6500).
Note 9: Refer to “Citrix requirements (multiple client platforms)” on page 5-51 for details.

Guidelines and considerations for choosing OneControl client platform

The following guidelines should be taken into account when choosing a
platform for the OneControl client:
• The recommended hardware platform for the OneControl client is a
Windows PC or a Citrix server PC, as indicated in Table 5-7. The
Solaris/Linux OneControl client). However, for optimal client performance,
a Windows PC or a Citrix server PC is recommended.
• Users who will install the OneControl client must have:
— administrator privileges (Windows)
— privileges to read and write to the directory or folder where the
OneControl client will be installed
— privileges to read and write to their own home directory or folder
• Users who will use the OneControl client after the installation is complete,
must have:
— privileges to read and write to their own home directory or folder
— privileges to read, write, and read & execute for the onc.jnlp file
(Windows)
Attention: The onc.jnlp file is only present and used when the
deployment includes one of following features/licenses: Management of
4200, Management of CoreStream, Management of 5400 and CoreDirector,
SLM, SONET/SDH Control Plane service management, OTN service
management. The onc.jnlp file will only be present after the first launch of
a OneControl client menu item related to those features. It is located in the
OC folder within the OneControl client folder (eg. C:\Program Files
(x86)\Ciena\OneControl_Client_5.0.0\OC\onc.jnlp).
Users of the OneControl client must have privileges to read, write, and read
& execute for the onc.jnlp file. On Windows deployments supporting
multiple clients (eg. Windows 2012), this implies multiple users must have
these privileges on the same file. Once the file is present, ways to achieve
this include: creating individual users in the Windows security and assigning
each individual user privileges to the file, or assign all users to a security
group and assign the group privileges to the file.
• When running the OneControl client on a Solaris or Linux platform,

co-resident with the OneControl server, the following limitations apply:
— The Shelf Level View functionality is not supported on Linux 5.x clients
or Solaris clients. It is only supported on Windows and Linux 6.x
clients.

— The Site Manager (SM) nodal craft interface for 6500/CPL cannot be
launched for any NEs managed via Remote Manager for 6k, OM5k
and CPL components.
— The System Manager Interface (SMI) nodal craft interface for
565/5100/5200 is not supported on Linux (and so cannot be launched
if the OneControl client is running on Linux). It can also not be
launched from within the Manager for 6k, OM5k and CPL dialog when
the OneControl client is running on Solaris.
— CTM client launch for CoreStream NEs is not supported on Solaris or
Linux platforms.
• When running the OneControl client on a Solaris or Linux platform, and on
a separate platform from the OneControl server, the following limitations
apply:
— The Shelf Level View is not supported on Linux 5.x clients or Solaris
clients. It is only supported on Windows and Linux 6.x clients.
— The nodal craft interface cannot be launched for any NEs managed via
any Manager for 6k, OM5k and CPL components (this includes 6110,
6130, 6150, 6200, 6500, CPL, 565, 5100, 5200 NE types).
— CTM client launch for CoreStream NEs is not supported on Solaris or
Linux platforms.
• When running the OneControl client specifically on Linux 6.x, the Linux 6.x
base OS install includes only TWM Window Manager (doesn’t support
right mouse button, or left double-click). In order to access any menu items
usually accessible via right-clink or double-click you can:
— Install another window manager package on top of the Linux 6.x base
install (eg. GNOME), or
— For right-click, hold down the right button and hit the middle button. For
left button double-click, hold down the left button and double click on
the middle button.
• When running multiple OneControl clients using a Citrix server PC:
— Each OneControl client instance must run in its own user login session
(i.e. every Citrix "client session" must correspond to a separate
Windows user login session, and all processes and memory spaces
used by one Windows user must not interact in any way with other user
sessions). See Figure 5-1 on page 5-13 for an example.

Figure 5-1
Citrix server deployment

LAN/WAN requirements
TCP/IP connections between all platforms and NEs are required (must be
IPv4).
Attention: NAT (Network Address Translation) is not supported between the

OneControl server and any of the following: OneControl client, OneControl
server in a GR pair, Remote Manager for 6k, OM5k and CPL, ESM Network
Elements. For NAT support details between ESM and the NEs, refer to the
ESM documentation.
DCN delay
The DCN between EMS and network, between EMS nodes and between EMS
servers and EMS clients average delay on any transfer rate on each of the
DCN segments should not exceed 200 ms with absence of packet loss.
Multiple LAN ports

OneControl supports only one LAN port activated on the server.
WARNING
Only one LAN port can be enabled during the installation of
OneControl software products. During the installation, all services
will be aligned to this LAN port. Thus all services will only listen and
broadcast to this LAN port. If multiple LAN ports are enabled during
the installation, these services could be spread across these LAN
ports, and OneControl software products will not work properly.
Additional LAN ports can be enabled after the installation. However,

these LAN ports cannot be used as a normal access to platform.
These other LAN ports can be used for additional DCN access for
transfer of data and other miscellaneous tools that require access to
the platform. If other LAN ports are activated, they must be
deactivated prior to an upgrade.
If you intend to activate additional LAN ports in your deployment

after installation, or if you intend to use special configurations such
as bonded interfaces, your Ciena technical representative should be
contacted for guidance.
It is the customer's responsibility to ensure that additional LAN

cards do not cause any adverse side-effects to the OneControl
software product. It is not possible for Ciena to test and make
recommendations for all third-party packages used by all
customers. Furthermore, Ciena cannot accept liabilities related to
third party packages or support the third party packages, unless
specifically tested by Ciena verification teams and documented in a
specific commercial support agreement. If specific problems are
encountered with the OneControl software product, Ciena reserves
the right to request that extra LAN cards be temporarily deactivated
during the investigation of a problem.

Manager for 6k, OM5k and CPL - IPSec support for 5100/5200 NEs (optional)
IPsec is a network layer protocol that employs a robust set of security
mechanisms to secure network traffic. The Manager for 6k, OM5k and CPL
provides hardware IPSec support between Manager for 6k, OM5k and CPL
and 5100/5200 release 9.2 and higher NEs.
To support this functionality, the following is required:

• the Manager for 6k, OM5k and CPL must be deployed on an Oracle
SPARC T-class server
• the Sun Crypto Accelerator 6000 card (SCA6000) must be purchased with
the Oracle SPARC T-class server
• the corresponding SCA6000 software must be installed and configured on
the server
• you must download the IPsec configuration software and readme file
posted online by Ciena, at the same location described in “OneControl
software patches” on page 5-52
• the 5100/5200 NEs must be configured to support IPsec
Link Speed
The minimum speed supported is 100 Full Duplex.
Attention: Some configurations may require more than 100 MBit/s of

bandwidth. This means that a 10/100 Mbit/s LAN card would not be
sufficient. See http://www.oracle.com. for LAN cards that have more
capacity, such as a 1000 Mbits/s LAN card.
In some cases, network switches do not negotiate properly with the ethernet
cards of the server. This can result with a problem that is difficult to diagnose
due to errors at the TCP/IP layer. Usually the auto negotiation software within
the switch can determine that the network card on the server is able to
establish a link at 100 Mbs, but is unable to confirm that it can do so in full
duplex. The switch establishes the link at the lowest common default, which
results in a link running at 100 Half Duplex.
In this case, the link will seem very slow, and you will see many packet
collisions on the interface when the user executes the following command:
netstat -i
The user can force the LAN card to a given speed by creating or modifying the
/kernel/drv/<LAN card type i.e.: e1000g>.conf file. When the LAN card on a
server is set to a specified speed, the corresponding switch should also be set
accordingly.

The following is an example of the e1000g.conf file forced to 100 Full duplex,
where a 1 must be placed on the selected speed and a 0 on all of the other
options:
adv_1000fdx_cap=0;
adv_1000hdx_cap=0;
adv_100fdx_cap=1;
adv_100hdx_cap=0;
adv_10fdx_cap=0;
adv_10hdx_cap=0;
adv_autoneg_cap=0;
For the required changes to take effect, reboot the system using the reboot
command.

Database requirements
When deploying OneControl, you must decide which database it will be used
in conjunction with. The database that must be used depends on the
OneControl and network configuration (see also Figure 5-2 on page 5-18):
• If deployment includes any of the following licenses, you must use an
Oracle database
— Management of 4200
— Management of CoreStream
• If deployment does not include any of the following licenses, you must use
a MySQL database
— Management of 4200
— Management of CoreStream
— Management of 5400 and CoreDirector
— SLM
— SONET/SDH Control Plane service management
— OTN service management
• If deployment includes any of the following licenses (but no 4200/NCS and
no CoreStream/CTM), you can use either a MySQL or Oracle database:
— Management of 5400 and CoreDirector
— SLM
— SONET/SDH Control Plane service management
— OTN service management
Attention: When Ethernet Services Manager (ESM) is deployed

co-resident with OneControl, it uses the MySQL database software
embedded in OneControl, regardless of what database OneControl uses
(i.e. when co-resident with OneControl, ESM never uses an Oracle
database).
Attention: The database used before and after an upgrade must be the
same (MySQL to MySQL, local Oracle to local Oracle, remote Oracle to
remote Oracle, custom remote Oracle to custom remote Oracle).

Figure 5-2
Determine which database to use
Determine which
database to use
Does the OneControl deployment

include the Management of 4200 or
Yes Management of CoreStream? No
Does the OneControl

deployment include any of the
following features: Management
Is this a GR of 5400 and CoreDirector, SLM,
deployment? SONET/SDH Control Plane
Yes
service management, OTN
service management?
Yes No
No
Is this a GR
deployment?
Yes No
Use: Use: Use: Use: Use:

Database
Oracle EE Oracle EE, or Oracle EE, or Oracle EE, or MySQL
that must be
Oracle SE MySQL Oracle SE, or
used
MySQL
MySQL Database Deployments

When OneControl is used with a MySQL database, no separate database
software needs to be ordered or installed. MySQL database software is
embedded and delivered with the OneControl software.
Oracle Database Deployments

When OneControl is used with an Oracle database, the Oracle installation
must be completed by the customer and must meet certain requirements.

The following release and editions of Oracle database software are

supported:
• For GR deployments you must use - Oracle 11g rel 2 (11.2.0.4) Enterprise
Edition (EE) with Partitioning Option
• For deployments with no redundancy you must use - Oracle 11g rel 2
(11.2.0.4) Enterprise Edition (EE) with Partitioning Option, or Oracle 11g
rel 2 (11.2.0.4) Standard Edition (SE)
• If Oracle 11g Standard Edition is used (instead of Enterprise Edition), it is
recommended that the number of days set for historical data does not
exceed 7 days.
• The remote database option in Oracle is supported for use with
OneControl (however the Oracle RAC feature is not supported)
See these sections for the Oracle database requirements:

• “Oracle database user and user environment requirements” on page 5-20.
• “Oracle database software install parameter requirements” on page 5-21.
• “Oracle database creation requirements” on page 5-25.
• “Oracle database requirements for remote or custom database
deployments” on page 5-26.
See these sections for how to download documents that provide guidance on
Oracle database installation and upgrades:
• “Downloading Oracle database installation example” on page 5-26
• “Downloading Oracle database upgrade document” on page 5-26
Attention: When OneControl is used with an Oracle database, the

database software must be at release 11.2.0.4. If you intend to apply any
Oracle CPU patches applicable to 11.2.0.4, this must be done after
OneControl is installed (the database creation scripts used by OneControl
require that the database be at release 11.2.0.4).
Attention: When OneControl is used with an Oracle database, installation,

maintenance and troubleshooting of the Oracle database is the customer's
responsibility. Any OneControl activities, or issues identified, that require
action on the Oracle database will be the responsibility of the customer's
Oracle database administrator.

Attention: Previous releases of OneControl used Oracle database software

11.2.0.1. When upgrading from a OneControl 3.2/4.0/4.1 deployment that
uses a Oracle database, part of the upgrade process includes upgrading the
Oracle database and software from 11.2.0.1 to 11.2.0.4.
See OneControl Installation Part 1, 450-3201-201 for details on upgrades.
Oracle database user and user environment requirements

Tables 5-8 to 5-9 list the Oracle database user and user environment
requirements.
Table 5-8 on page 5-20 lists the Oracle database user and group
requirements.
Table 5-8
Oracle database user and group requirements
Setting Value Details (Note 1)
Oracle software owner oracle UNIX user id that owns the Oracle
software.
Oracle Inventory group dba UNIX user id that owns the Oracle
software.
Database Administrator (OSDBA) group dba UNIX group to be used as database

administrator groups.
Database operator (OSOPER) group dba UNIX group to be used as database

operator group.
Note 1: The OneControl documentation assumes these values are set as indicated. For fresh installs
of OneControl, different Oracle owner/groups can be used. However, if this is done, OneControl
installation and configuration procedures should be adapted to use the selected userid or group.
OneControl 3.x/4.x releases required that the Oracle userid/group be set to oracle/dba. When
upgrading to OneControl 5.0 from one of these previous releases, the Oracle userid/group must not be
changed over the upgrade (oracle/dba must continue to be used).

Table 5-9 on page 5-21 lists the Oracle software user environment
requirements.
Table 5-9
Oracle software user environment variables
Name of variable Value Details

in oracle user
profile
ORACLE_BASE /opt/oracle Oracle application base install directory.

The OneControl software expects this
value to be set in the Oracle user’s
environment.
The OneControl documentation
assumes this value is set as indicated
(and guides the user to set this value in
the Oracle user’s .profile file). A different
Oracle base directory can be used for
your Oracle installation. However, if this
is done, OneControl installation and
configuration procedures should be
adapted to point to the new location as
required.
ORACLE_HOME $ORACLE_BASE/11.2.0.4/dbhome_1 Oracle application home install

directory.
The OneControl software expects this
value to be set in the Oracle user’s
environment.
The OneControl documentation
assumes this value is set as indicated
(and guides the user to set this value in
the Oracle user’s .profile file). A different
Oracle base directory can be used for
your Oracle installation. However, if this
is done, OneControl installation and
configuration procedures should be
adapted to point to the new location as
required.
Oracle database software install parameter requirements

Tables 5-10 to 5-12 list the parameters that should be chosen when installing
the Oracle database software.

Table 5-10 on page 5-22 lists the Oracle database software install parameters.
Table 5-10
Oracle database software install parameters
Setting Value Details
Email notifications No Choose whether to receive email notifications.
Database creation Install database software only Do not create a database.

This value must be used (it should not be
changed). OneControl installation and
configuration procedures include steps for
creating the database.
Type of database Single instance database Type of installation.

installation installation This value must be used (it should not be
changed). The Oracle RAC feature is not
supported.
Languages English Choose the languages desired.
Database Edition Enterprise Edition (EE) or Database edition.

Standard Edition (SE) See Figure 5-2 on page 5-18 to determine the
database edition required for your deployment.
Oracle Base /opt/oracle Oracle database software base install directory.

The OneControl software and documentation
assumes this value is set as indicated. A different
Oracle base directory can be used for your
Oracle installation. However, if this is done,
OneControl installation and configuration
procedures should be adapted to point to the
new location as required.
Oracle Home /opt/oracle/11.2.0.4/dbhome_1 Oracle database software home install directory.

Oracle home directory can be used for your
Oracle installation. However, if this is done,
OneControl installation and configuration
procedures should be adapted to point to the
new location as required.
Database dba UNIX groups to be used as database

Administrator administrator and operator groups.
(OSDBA) group
Database operator dba This value must be used (it should not be
(OSOPER) group changed).

Table 5-11 on page 5-23 lists the Oracle 32-bit client software install
parameters. The Oracle 32-bit client software only needs to be installed if the
Service Layer Manager (SLM) component of OneControl is used.
Table 5-11
Oracle 32-bit client software install parameters
Type of Administrator Type of installation.

database
installation
This value must be used (it should not be changed).
Oracle Base /opt/oracle Oracle 32-bit client software base install directory.

Oracle base directory can be used for your Oracle
installation. However, if this is done, OneControl
installation and configuration procedures should be
adapted to point to the new location as required.
Oracle Home /opt/oracle/11.2.0/client_32bit Oracle 32-bit client software home install directory.

Oracle home directory can be used for your Oracle
installation and configuration procedures should be
adapted to point to the new location as required.

Table 5-12 on page 5-24 lists the Oracle 64-bit client software install
parameters. The Oracle 64-bit client software only needs to be installed on the
OneControl server, if a remote Oracle database server is used.
Table 5-12
Oracle 64-bit client software install parameters
Type of database Administrator Type of installation.

installation
This value must be used (it should not be

changed).
Oracle Base /opt/oracle Oracle 64-bit client software base install directory.

Oracle base directory can be used for your Oracle
installation and configuration procedures should
be adapted to point to the new location as
required.
Oracle Home /opt/oracle/11.2.0/client_64bit Oracle 64-bit client software home install directory.

Oracle home directory can be used for your Oracle
installation and configuration procedures should
be adapted to point to the new location as
required.

Oracle database creation requirements

Table 5-13 on page 5-25 lists Oracle database parameters for the creation of
the database.
Table 5-13
Oracle database creation
Parameter Value Details
Oracle data /u03/emsdata Location where OneControl Oracle data is

directory stored.
This is the default value used by the
OneControl software. The user can select a
different value when configuring the Oracle
database.
Oracle redo log /u04/oradata Location where OneControl Oracle redo logs
directory are stored.
This is the default value used by the
database.
Oracle database onedb SID of OneControl Oracle database.

System ID (SID) This is the default value used by the
database.
Oracle database onedb.<hostname_or_8char_alias> Service Name of OneControl Oracle database.

service name This is the default value used by the
database.
Oracle database 1521 Port of OneControl Oracle database.

port This is the default value used by the
database.
Archiving Disabled Oracle archiving mode.

All OneControl engineering guidelines and
values have been tested with archiving mode
disabled.
Database users Various Database users and passwords.

and passwords The OneControl software creates various
database accounts. The user can select the
userid and password for each required account.

Oracle database requirements for remote or custom database deployments
Attention: When OneControl is used with a remote Oracle database, the

network link between the OneControl platform and the Oracle database
platform must be reliable, fast, and have no packet loss. It is recommended
that the two platforms be deployed in the same geographic region (on the
same local network whenever possible), with 1 Gb/s network switches.
Table 5-14 on page 5-26 lists Oracle database parameter requirements for
deployments where a customized database is used.
Table 5-14
Oracle database requirements for custom deployments
Parameter Value
open_cursors 1800
processes 1250
sga_max_size 10G
Server mode Dedicated server mode (not shared server mode)
Archive mode Disabled. All OneControl engineering guidelines and values have
been tested with archiving mode disabled.
Downloading Oracle database installation example

Sample instructions for installing the Oracle database following the
OneControl requirements can be downloaded by doing the following:
• Once you are logged into this portal, click the Software tab.
• Select OneControl from the available list of products.
• To facilitate the search, sort the results by part number by clicking on the
Ciena Part # column heading.
• Find the "Oracle 11.2.0.4 DB Installation Example for OneControl" item
(Part number: ORCL_11204_INST).
• Download the installation example.
Downloading Oracle database upgrade document

Instructions for upgrading from Oracle 11.2.0.1 to 11.2.0.4 as part of a
OneControl upgrade can be downloaded by doing the following:

• Find the "Oracle 11.2.0.1 to 11.2.0.4 DB Upgrade Example for
OneControl" item (Part number: ORCL_11204_UPG).
The procedures in this document are only one portion of the steps that must
be run to upgrade a current OneControl deployment from a previous release
to 4.2. They are not intended to be used in any other context, and should only
be run when instructed to do so at the appropriate point during the OneControl
upgrade.
Server platforms - Operating system requirements

This section describes the operating system requirements for OneControl
server platforms.
Solaris/Linux OS release
Oracle SPARC hardware platforms installed with OneControl 5.0 must run on
a Solaris 10, 11.1 or 11.2 operating system. The operating system must be
directly ordered/downloaded from Oracle. It is not provided by Ciena.
Intel hardware platforms installed with OneControl 5.0 must run on a Linux
5.8, 5.9, 5.10, 5.11, 6.4, 6.5 or 6.6 operating system. The operating system
must be directly ordered/downloaded from Oracle or Red Hat. It is not
provided by Ciena.
Determining the required Solaris/LInux operating system version

The following sections detail the Solaris/Linux OS versions required for
OneControl 5.0. The information provided is accurate at the time of availability
of this document. However, OS requirements and recommendations may be
updated at a later date. The latest information on operating system
requirements can be downloaded by doing the following:

• Find the “Recommended operating system versions and patch bundles”

item (Part number: OS_TOC).
• Download the document. Use the document to identify the supported
Solaris/Linux operating system version for OneControl 5.0.
Solaris OS version required

The following Solaris OS versions are supported for OneControl 5.0:
• For T5 platforms: Solaris 11.1 or 11.2, or Solaris 10 (01/13 or later) +
Ciena Solaris OS bundle (for Solaris 10 or Solaris 11.x)
• For T4 platforms: Solaris 11.1 or 11.2, or Solaris 10 (10/09 or later) +
Ciena Solaris OS bundle (for Solaris 10 or Solaris 11.x)
• For T3 platforms: Solaris 10 (10/09 or later) + Ciena Solaris OS bundle (for
Solaris 10)
• For M5000 platforms: Solaris 10 (10/08 or later) + Ciena Solaris OS
bundle (for Solaris 10)
For Solaris 10: Oracle offers various versions of the Solaris 10 operating
system, usually labelled with the month and year of release. Only those
versions specifically supported by Ciena for use with OneControl should be
used. All packages must be applied when installing the operating system. This
means that when installing the operating system the "Entire distribution plus
OEM support" option must be selected.
For Solaris 11.1/11.2: The Solaris 11.1/11.2 operating system must be

installed following the steps provided in the "Solaris 11.x installation example"
document provided on the Ciena portal. This document highlights the options
that must be selected during installation.
Attention: There is a known Oracle issue with the T4 platform. The T4

cannot boot from a Solaris10 10/09 (U8) OS DVD from the internal DVD
drive. This does not occur with later versions of Solaris 10. Workarounds
include using the DVD on a remote PC connected via the network or using
an external USB DVD directly attached to the T4 platform. Contact Oracle for
details.
Linux OS version required

For all supported HP Intel platforms, Red Hat Enterprise Linux must be used.
For all supported Oracle Intel platforms, Oracle Linux or Red Hat Enterprise
Linux must be used.
The following Linux OS distributions are supported for OneControl 5.0:

• Linux 5.8 (kernel 2.6.18-308) 64-bit Server


• Linux 6.4 (kernel 2.6.32-358) 64-bit Server, Basic Server option only, with
Secure Linux (SELinux) in permissive mode
• The following platforms require a minimum of Linux 5.8: HP DL560cG8,
HP BL680cG7, Oracle X3-2
• The following platforms require a minimum of Linux 5.9 or 6.4: Oracle X4-2
• The following platforms require a minimum of Linux 6.4: Dell R820
• The following platforms require a minimum of Linux 6.5: Oracle X5-2
• For all platforms the Ciena Linux OS bundle must be applied.
• For all platforms refer to the manufacturer’s documentation for the most up
to date information on Linux version compatibility.
For all virtualized deployments the following virtualization software is

supported:
• VMware ESXi 5.0/5.1/5.5 + Ciena Linux OS bundle
• VMware ESXi 5.5 introduces supportability for virtual machine disks larger
than 2 TB
• Compatibility between Linux releases and ESXi releases should be
verified with VMware
The Linux operating system must be installed following the steps provided in
the "Linux installation example" document provided on the Ciena portal. This
document highlights the options that must be selected during installation
(including required configuration steps for certain packages).
Attention: Only those Linux versions specifically supported by Ciena for use
with OneControl should be used.
Attention: OneControl 5.0 does not support Linux 5.6 (OneControl 4.2 was
the last release to support the use of Linux 5.6).

Downloading operating system installation example

Instructions for installing the operating system can be downloaded by doing
the following:
• Find the "Solaris 10 Installation example", "Solaris 11.1x Installation
example", or "Linux Installation example" item (Part number:
SOL10_INSTEX, SOL11_INSTEX, or LINUX_INSTEX).
Solaris/Linux OS bundles/patches
After the Solaris/Linux operating system is installed, a Ciena recommended
OS bundle must be applied to the OS. There is a minimum OS bundle
required. In addition, the recommended OS bundle is updated periodically,
and posted online by Ciena.
The minimum OS bundle required for OneControl 5.0 is:

• For Solaris 10: 4Q2014
• For Solaris 11.1: 4Q2014
• For Solaris 11.2: 4Q2014
• For Linux: 4Q2014
There is a separate OS bundle for each operating system (i.e. there are 3
different bundles.). Select the one that applies to the OS you are using. The
OS bundle is released with an associated Readme file that explains how to
apply the bundle to your system. The administrator must always read the
documentation before attempting to install the bundle.

WARNING
OneControl has been verified against a specific set of patches.
Installation of any additional patches other than the ones listed
or provided is not supported, and Ciena Corporation does not
accept responsibility, or provide support for any related issues
which may arise as a result. Customers should also be aware
that installing any additional patches may lead to undesirable
behavior (performance related, corruption, core dumps, etc). In
summary, responsibility for any issues which arise as a result
of installing additional patches other than the ones listed or
provided must be understood and accepted by the customer.
Downloading Solaris/Linux operating system bundles

The OS bundle and documentation can be downloaded by doing the following:
item (Part number: OS_TOC).
• Download the document. Use the document to identify the OS bundle
required for OneControl 5.0.
• Find the OS bundle required (Part number format: SOLxx_xQxxxx, or
LINUX_INT_xQxx).
• Download the software and the corresponding Readme file.
Virtualized Deployments
For information on virtualized deployments refer to “Virtualization” on page
4-5.
Hard disk configuration

This section describes the hard disk configuration.
Disk space requirements

This section provides some general information on how disk space is used. In
all cases, the requirements provided in this document regarding minimum
numbers and sizes of disks, and regarding disk partitioning guidelines, should
be followed.

The required disk space can be calculated as:

Disk Space = Operating System + Swap Space + Applications + Database
+ NE Historical Data (Manager for 6k, OM5k and CPL NEs)
+ EMS Backups
The disk space required for the swap space is twice the RAM memory size of
the platform (for platforms with up to 64GB RAM), or RAM + 2GB for platforms
with 128GB RAM or more.
The disk space required for the applications and the database varies with the
size of the managed network. The platform requirements and disk partitioning
guidelines in this document take this into account and have been adjusted
accordingly.
The disk space required for EMS backups depends on network size and on
the number of days of history kept. Each EMS backup can require anywhere
from 1GB to 100GB of space. The disk size requirements and disk partitioning
guidelines in this document do not allocate any significant space for EMS
backup file storage. These files are used for system recovery, and as such, it
is recommended that they be directed to and stored on a separate platform
from the OneControl.
The disk space required for NE historical data of Manager for 6k, OM5k and
CPL NE types depends on the type and number of NEs managed and on the
number of days of history kept. This value must be calculated using the values
in Table 5-15 on page 5-32. The value should then be compared to the disk
partitioning scenario used in this document to determine if it is more than what
has been set aside for this purpose in the guidelines provided.
Table 5-15
NE historical data disk space required - Manager for 6k, OM5k and CPL NEs
NE type NE data size per day

(PMs plus 1 NE backup per day)
CPL 20 Mbyte
5100/5200 20 Mbyte
6110/6130/6150/6200 20 Mbyte
6500 4.0 and below 41 Mbyte
6500 5.0 and above (single shelf 50 Mbyte

TID/TIDc)
6500 5.0 and above (5 shelf TIDc) 150-200 Mbyte

For example, if you want to keep 30 days of NE Data and you are managing:
• 25 CPL (25x20MB=500MB)
• 25 6110 (25x20MB=500MB)
• 6 6500 (6x50MB=300MB)
• 10 5200 (10x20MB=200MB)
then the disk space required would be approximately 1.5 GByte per day. The
disk space requirement for 30 days would be (30 days x 1.5 GByte)=45GByte.
That value must now be compared to see if more storage space is needed. If
for example we have a Solaris 10 deployment and are using the column for
partitioning using 4 disks in Table 5-16 on page 5-35, no additional space is
required (since, as per the note in the table, 100GB has been set aside for this
purpose in this scenario). If however we have fewer disks and are using the
column for partitioning using 2 disks we need additional space (since, as per
the note in the table, only 20GB has been set aside for this purpose in this
scenario).
If more space is required then you can:

• use larger disks and increase the size allocated to /opt/nortel accordingly
• move /opt/nortel to another disk where more space can be allocated to it
• create a manual link to redirect only the subfolder containing the NE data
to another location/disk
• in all cases the subfolder containing the NE data must have sufficient
space available and allocated to contain the total size of the NE data
required (i.e. data cannot be split between multiple directories)
Disk mirroring and RAID configurations

Ciena does not provide any tools to perform volume management or Disk
Mirroring (RAID); these tools can be acquired via Oracle or other 3rd party
vendors. These tools must be installed and configured prior to the installation
of the OneControl software.
Attention: When other applications or 3rd party tools are used on the
server, such as volume management or Disk Mirroring (RAID), other kernel
parameter values could be required by these applications. The administrator
should use the higher of the two numbers. Failure to do so could affect
performance and stability, and could result in the OneControl software not
starting properly.

WARNING
If you want to configure disk mirroring, you must do this prior to
installing any of the OneControl 5.0 products on your server.
Solaris 10 disk layout

Table 5-16 on page 5-35 specifies the disk layout for Oracle SPARC platforms
running Solaris 10 with OneControl 5.0 (including deployments with the
Manager for 6k, OM5k and CPL).

Table 5-16
Solaris 10 disk layout
Partition (Note 3, Partition location and min. size based on no. of disks (or mirrored disk pairs) used
Note 4,Note 5,
Note 6) 1 disk/pair 2 disks/pairs 3 disks/pairs 4 disks/pairs
/ (root) (Slice 0) Disk0 Disk0 Disk0 Disk0

all remaining (after all remaining (after all remaining (after all remaining (after
others allocated) swap allocated) swap & /opt allocated) swap allocated)
swap (Slice 1) Disk0 Disk0 Disk0 Disk0

(Note 1) 2 x RAM 2 x RAM 2 x RAM 2 x RAM
overlap (Slice 2) Disk0 Disk0 Disk0 Disk0

(Note 2) total disk space total disk space total disk space total disk space
/opt Disk0 Disk1 Disk0 Disk1

50 GB (Note 8) all remaining (after 100 GB all remaining (after
/opt/oracle, /u04, /u02 & /opt/nortel allocated)
/u03 allocated) (Note 9)
/opt/nortel Not Required Not Required Disk1 Disk1

(Note 7) (Note 7) 200 GB (Note 9) 400 GB (Note 10)
/opt/ciena Not Required Not Required Disk1 Disk3

(Note 7) (Note 7) 200 GB 200 GB
/opt/oracle Disk0 Disk1 Disk1 Disk2

(only with Oracle DB) 50 GB 80 GB 100 GB 200 GB
/u04 Disk0 Disk1 Disk1 Disk2

(only with Oracle DB) 30 GB 50 GB all remaining 100 GB

(only with Oracle DB) 30 GB 50 GB 50 GB 80 GB

(only with Oracle DB) 150 GB 250 GB all remaining (after /u02 all remaining (after
allocated) /opt/ciena allocated)
Note 1: For platforms with up to 64 GB of total RAM, set the swap size to twice the size of RAM. For platforms with
128 GB of total RAM or more, set the swap size to RAM + 2 GB. If the swap space is greater than half of the disk
space, it should be distributed across multiple disks.
Note 2: Slice 2 overlap cannot be changed, as it is the total disk space.
Note 3: The UFS file system should be used.
Note 4: Disks should meet minimum size requirements for supported platform types. See “Hardware platform
requirements” on page 5-3. Values in this table assume disks of size 600 GB.
Note 5: When using OneControl with a remote Oracle database, the following folders must still be present: /u02,
/u03, /u04 (even though the Oracle database server software is not installed co-resident). The folders must exist
(but do not need to be partitions with disk space size assigned to them).
Note 6: For platforms running only the Remote Manager for 6k, OM5k and CPL component, only the /, swap, /opt,
/opt/nortel, /opt/ciena partitions are required.
Note 7: No separate /opt/nortel and /opt/ciena partitions are needed for these scenarios (space is included in /opt).
Note 8: Includes 5GB of space for historical PM/NE data of Manager for 6k, OM5k and CPL managed NE types.

Linux disk layout

Table 5-17 on page 5-36 specifies the disk layout for Intel platforms running
Linux, when OneControl is used with a MySQL database.
Table 5-18 on page 5-37 specifies the disk layout for Intel platforms running
Linux, when OneControl is used with an Oracle database. For the database
requirements that apply to your deployment, see “Database requirements” on
page 5-17.
Table 5-17
Linux disk layout - mySQL
Partition (Note 2, Note 5) Minimum partition size for Minimum partition size for File system
2x600GB disk (or 2x600GB 1x1.2TB disk (or 1x1.2TB (Note 7)
mirrored disk pairs) - 1.2TB mirrored disk pair) - 1.2TB
of storage capacity total of storage capacity total
boot Disk0 - 100 MB Disk0 - 100 MB ext3
/dev/sda2 (/ file system) Disk0 - all remaining (after Disk0 - all remaining (after Extended ext3
others allocated, see Note 6) others allocated, see Note 6)
/dev/sda3 (swap file Disk0 - 2 x RAM (Note 1) Disk0 - 2 x RAM (Note 1) swap
system)
/home - Disk0 - 50 GB ext3
/var - Disk0 - 70 GB ext3
/opt Disk0 - 300 GB Disk0 - 300 GB ext3
/opt/nortel Disk0 - 300 GB (Note 3) Disk0 - 400 GB (Note 4) ext3
Note 1: For platforms with up to 64 GB of total RAM, set the swap size to twice the size of RAM. For
platforms with 128 GB of total RAM or more, set the swap size to RAM + 2 GB. If the swap space is
greater than half of the disk space, it should be distributed across multiple disks.
Note 2: Disks should meet minimum size requirements for supported platform types. See “Hardware
platform requirements” on page 5-3. Values in this table assume disks of size 600 GB or 1.2 TB.
Note 3: Includes 100GB of space for historical PM/NE data of Manager for 6k, OM5k and CPL managed
NE types.
Note 4: Includes 150GB of space for historical PM/NE data of Manager for 6k, OM5k and CPL managed
NE types.
Note 5: For platforms running only the Remote Manager for 6k, OM5k and CPL component, only the /,
swap, /opt, /opt/nortel, /opt/ciena partitions are required.
Note 6: The disk layouts in this guide have been used to validate the OneControl functionality,
performance, and scalability. Therefore Ciena recommends deploying OneControl with these disk
layouts. Of particular importance to highlight are the size recommendations for the root (/) partition.
Ciena recommends that customers do not attempt to further divide the root partition to a lower level of
granularity.
Note 7: LVM (Logical Volume Manager) and ext4 file systems are not currently supported in conjunction
with OneControl.

Table 5-18
Linux disk layout - Oracle
Partition (Note 2, Note 3) Minimum partition size for 2x1.2TB disks (or File system
2x1.2TB mirrored disk pairs) - 2.4TB of storage (Note 6)
capacity total
boot Disk0 - 100 MB ext3
/dev/sda2 (/ file system) Disk0 - all remaining (after others allocated, see Note 5) Extended ext3
/dev/sda3 (swap file system) Disk0 - 2 x RAM (Note 1) swap
/home Disk0 - 50 GB ext3
/var Disk0 - 70 GB ext3
/opt Disk0 - 300GB ext3
/opt/nortel Disk0 - 400GB (Note 4) ext3
/opt/oracle Disk1 - 80 GB ext3
/u02 Disk1 - 50 GB ext3
/u04 Disk1 - 50 GB ext3
/u03 Disk1 - all remaining (after others allocated) ext3
Note 1: For platforms with up to 64 GB of total RAM, set the swap size to twice the size of RAM. For
platforms with 128 GB of total RAM or more, set the swap size to RAM + 2 GB. If the swap space is
greater than half of the disk space, it should be distributed across multiple disks.
Note 2: Disks should meet minimum size requirements for supported platform types. See “Hardware
platform requirements” on page 5-3. Values in this table assume disks of size 1.2 TB.
Note 3: When using OneControl with a remote Oracle database, the following folders must still be
present: /u02, /u03, /u04 (even though the Oracle database server software is not installed co-resident).
The folders must exist (but do not need to be partitions with disk space size assigned to them).
Note 4: Includes 150GB of space for historical PM/NE data of Manager for 6k, OM5k and CPL
managed NE types.
Note 5: The disk layouts in this guide have been used to validate the OneControl functionality,
performance, and scalability. Therefore Ciena recommends deploying OneControl with these disk
layouts. Of particular importance to highlight are the size recommendations for the root (/) partition.
Ciena recommends that customers do not attempt to further divide the root partition to a lower level of
granularity.
Note 6: LVM (Logical Volume Manager) and ext4 file systems are not currently supported in
conjunction with OneControl.

Solaris 11.1/11.2 disk layout - OneControl 5.0

Starting with Solaris 11, Oracle requires the use of ZFS for the root volume.
When using Solaris 11.1/11.2 with OneControl:
• The ZFS file system must be used.
• One or more ZFS pools are created, depending on the number of physical
disks. Mirroring may be used in any of the pools, but RAIDZ should not be
used in the rpool or the dbpool .
• ZFS file systems are created within each ZFS pool. All ZFS file systems in
a pool share the space (as compared to UFS file systems where each file
system is created with a specific size).
OneControl supports the use of ZFS for Solaris 11.1/11.2 installations only
(ZFS is not supported for Solaris 10 installations due to performance issues
with ZFS on Solaris 10).
For deployments using Solaris 11.1/11.2 use the following disk layout tables:
• If you are not using virtualization, disk layout will be determined based
on the number of internal disks you have.
— Use Table 5-19 on page 5-39 to determine which ZFS pools to create
and which disks to use for each pool (use column matching your total
disks).
— Then use Table 5-21 on page 5-40 to determine which ZFS file
systems to create and which ZFS pool to assign each one to (use
column matching your total disks).
• If you are using virtualization, and are using a T5-2 platform in
conjunction with disk mirroring, the 6 internal disks available on this
platform may not be enough to maximize the number of LDOMs possible.
In this scenario, the Oracle ZS3-2 ZFS storage solution should be used.
— Use Table 5-20 on page 5-39 to determine which ZFS pools to create
and which disks to use for each pool (for each LDOM).
— Then use Table 5-21 on page 5-40 to determine which ZFS file
systems to create for each ZFS pool.

Table 5-19
Solaris 11.1/11.2 disk layout - ZFS pools (using internal disks)
ZFS pool Disks to assign to each pool based on number of disks used (600 GB disks, Note 4)
to create
2 disks 4 disks 6 disks 8 disks
rpool Disk0 (+Disk1 mirror) Disk0 (+Disk1 mirror) Disk0 (+Disk1 mirror) Disk0 (+Disk1 mirror)
(the root pool) (600 GB) (600 GB) (600 GB) (600 GB)
(Note 1, Note 2)
onecpool N/A Disk2 (+Disk3 mirror) Disk2 + Disk3 + Disk4 Disk2 + Disk3 + Disk4
(600 GB) + Disk5 (RAIDZ) + Disk5 (RAIDZ)
(1.5 TB) (1.5 TB)
dbpool (Note 3) N/A N/A N/A Disk6 (+Disk7 mirror)

(600 GB)
Note 1: The rpool contains one entire disk (but can include a mirror disk). All OS file systems will be created in this
pool (including swap and /opt).
Note 2: For platforms running only the Remote Manager for 6k, OM5k and CPL component, create just one pool
(rpool). Only one disk, or a mirrored set of disks, can be assigned to rpool.
Note 3: For deployments that use an Oracle database, the ZFS block size for dbpool should be set to 16k.
requirements” on page 5-3. Values in this table assume disks of size 600 GB.
Table 5-20
Solaris 11.1/11.2 disk layout - ZFS pools (using T5-2 with ZS3-2 external storage)
LDOM ZFS pool Disks to assign to each pool based on number Storage capacity per
to create of disks used (600 GB disks, Note 2, Note 3) pool
Primary LDOM rpool Internal disks: Disk0 (+Disk1 mirror) 600 GB

(the root pool)
(Note 1)
LDOM1 ldom1pool Internal disks: Disk2 + Disk3 + Disk4 + Disk5 1.5 TB

(optional) (RAIDZ)
LDOM2 ldom2pool External Group 1 (5 x 300GB in RAIDZ) 1.2 TB
Note 1: The rpool contains one entire disk (but can include a mirror disk). All OS file systems will be created in this
pool (including swap and /opt).
requirements” on page 5-3. Values in this table assume internal disks of size 600 GB.
Note 3: The Oracle ZS3-2 is a ZFS storage appliance that can be directly attached via Fiber Channel to extend the
storage capacity of T5-2 servers with Solaris 11.1/11.2. The minimum recommended ZS3-2 configuration is a
Performance Configuration with 20 x 300GB SAS disks and at least one 8 Gbs Fiber Channel dual-port module. An
HBA 8Gbs Fiber Channel adaptor is required on the T5-2 server to connect the server with the ZS3-2. The
recommended configuration is to create 4 groups of 5 disks each in a RAIDZ configuration. Each of the groups can
be assigned to a different LDOM as indicated in this table.

Table 5-21
Solaris 11.1/11.2 disk layout - ZFS file systems
ZFS file system Pools to assign file system to

to create
2 disk 4 disks 6 disks 8 disks ZS3-2 (with
LDOMs)
/ (root) (Note 2, Note 3) rpool rpool rpool rpool Assign all file
systems to the
swap (Note 3, Note 4) rpool rpool rpool rpool ldom<x>pool of
/var (Note 3) rpool rpool rpool rpool the LDOM
being used.
/opt (Note 3) rpool rpool rpool rpool
/opt/nortel rpool onecpool onecpool onecpool

(Note 5) (Note 5) (Note 5)
/opt/ciena rpool onecpool onecpool onecpool
/opt/oracle rpool rpool onecpool onecpool

(only with Oracle DB)
/u02 rpool rpool rpool rpool

/u04 rpool rpool rpool onecpool

/u03 (Note 1) rpool onecpool onecpool dbpool

Note 1: The record size for /u03 should be set to 16k and the logbias should be set to throughput.
Note 2: For platforms running only the Remote Manager for 6k, OM5k and CPL component, use the
pool created (rpool). The required file systems are /, swap, /opt, /opt/nortel, /opt/ciena.
Note 3: The / , /var, /opt and swap file systems are automatically created as part of the OS
installation. Users should not attempt to manually create these file systems.
Note 4: The size of swap is automatically configured as 2xRAM during install. Ensure that 2xRAM is
used if a custom install is done.
Note 5: Set a ZFS reservation for the /opt/nortel file system based on the amount of disk space
required for NE historical data of Manager for 6k, OM5k and CPL NE types (see “Disk space
requirements” on page 5-31). For the 4 disk scenario set it to 50 GB (includes 5GB of space for historical
PM/NE data). For the 6/8 disk scenario set it to 200 GB (includes 20GB of space for historical PM/NE
data).

Hostname, FQDN, hosts file, and IP address requirements

CAUTION
Once OneControl has been installed, you cannot change the
platform hostname or domain name. To change any of these,
you will be required to uninstall OneControl.
Once OneControl has been freshly installed, you can only

change the platform IP address if:
- No NEs have ever been managed in OneControl
- No external sub-EMS has ever been added
- GR has never been configured
If any of these conditions are not met, you cannot change the
platform IP address. To change the platform IP address you will
be required to uninstall OneControl.
A fully qualified domain name (FQDN) is a name that uniquely identifies a

server within a network. It is composed of the hostname and the domain
name. For example, a server with hostname pbany1e2 and domain name
ott.ciena.com, has a FQDN of pbay1e2.ott.ciena.com .
The following requirements apply to the UNIX hostname and FQDN of the
OneControl platform:
• the hostname must be a minimum of 4, and a maximum of 60 characters
• the hostname can include only alphanumeric characters a to z, A to Z, 0
to 9, and can include a hyphen "-"
• the hostname must begin with an alphabetic character a to z, A to Z
• the domain name must consist of at least 2 levels (eg. for a platform with
hostname server1, a FQDN of server1.ciena.com is supported, but
a FQDN of server1.com is not supported)
• If OneControl is deployed using an Oracle database, the following also
applies (except for platforms with only the Remote Manager for 6k, OM5k
and CPL component):
— an 8-character alias must be used:
– if the hostname is between 9 and 60 characters, or
– if the hostname contains a hyphen
— if an 8-character alias must be used:
– the alias can contain only alphanumeric characters a to z, A to Z,
0 to 9 (it must not contain a hyphen or any non-alphanumeric
characters)
– the alias must begin with an alphabetic character a to z, A to Z
– the installation documentation highlights where the alias must be
used (see OneControl Installation Part 1, 450-3201-201)

Attention: The hostname must be unique in the network, even if the domain
name is different. For instance do not use ciena1c.mydomain1.com and
ciena1c.mydomain2.com (i.e. the short name should be unique within
your hosts file and within the part of your network managed by the same
DNS, if DNS is used).
The following requirements apply to the /etc/hosts file on OneControl:

• the entries within the /etc/hosts file must be separated by a tab
character and not by spaces
• if you are using an alias, the alias entry must be added before the loghost
entry (the alias entry should not be added after the loghost entry)
• the format of the entries in the file must be:
<IP local server> <FQDN> <hostname> <alias if used> loghost
<IP redundant server> <FQDN> <hostname> <alias if used>
The following are examples of the /etc/hosts file for various scenarios:
Example 1 - OneControl GR pair, with hostnames greater than 8 characters,

using an Oracle database. In this case an 8-character alias must be used. The
hostname of the local server is wcars0e3-1c, and its alias is cienavm1. The
hostname of the other server in the redundant pair is wcars0e3-2c, and its
alias is cienavm2.
47.34.40.22 wcars0e3-1c.ciena.com wcars0e3-1c cienavm1 loghost

47.45.25.44 wcars0e3-2c.ciena.com wcars0e3-2c cienavm2
Example 2 - OneControl GR pair, with 7-character hostname. The hostname

of the local server is pbany1f. The hostname of the other server in the
redundant pair is pbany3f.
47.114.250.21 pbany1f.ciena.com pbany1f loghost

47.114.244.130 pbany3f.ciena.com pbany3f
Domain Name Service (DNS)

OneControl is supported in an environment where:
• No DNS server is used - Only supported for non-AP deployments, i.e.
deployments where OneControl is not used in conjunction with
Applications Platform (the installation documentation highlights what
configuration steps are required if DNS is not used, see OneControl
Installation Part 1, 450-3201-201)
• Network DNS server is used
• Local DNS server

If DNS is used, the configuration of the DNS server must be completed before
installation of the OneControl application.
WARNING
Once OneControl has been installed, it does not support
changing the DNS server configuration. To change the DNS
server configuration, you will be required to uninstall the
OneControl software application before making a change.
Following re-configuration of the DNS server, you will be
required to re-install the OneControl application.
No DNS Server configuration

Even if no DNS server is used, a fully qualified domain name must be defined
locally for the OneControl server in the /etc/hosts file. See “Hostname,
FQDN, hosts file, and IP address requirements” on page 5-41, for details.
Network DNS Server Configuration

Customers that already have a DNS server in their network should configure
all platforms with OneControl server installed, to point to that DNS server. This
configuration should be done during the installation or upgrade of the OS. The
information on how to configure this is included in the Solaris and Linux
install/upgrade examples provided by Ciena.
The DNS server must be configured to include the platforms being used for
OneControl, if it does not already (eg. if these platforms are new, entries for
them may not have been added yet to the DNS server). Customers should
contact their system administrator responsible for the DNS server in order to
confirm that this has been done.
Local DNS Server Configuration

Customers that do not already have a DNS server within their network, should
configure the OneControl server to be a DNS server itself. In this scenario, a
local DNS server is set up on the platform, and all address resolution is done
by that local DNS server.
An example of configuring this for Solaris 10 or Linux can be downloaded by

doing the following:

• Find the “Solaris 10 Local DNS Setup Example” or "Linux Local DNS
Setup Configurator" item (Part number: SOL10_DNS or LINUXDNS).
The Readme file contains an example of how to configure a local DNS server.
Domain name and domain configuration requirements (network or local DNS)

The following requirements apply to the UNIX domain name of the hardware
platform, and to the configuration of the domain. Installation of OneControl will
fail if these requirements are not met:
• The /etc/resolv.conf file contains the DNS server configuration for
the platform and has the following format:
domain <domain name>
nameserver <first name server IP>
nameserver <second name server IP>
search <domain name>
• The /etc/resolv.conf file must contain:
— only one line that starts with the word domain, with only one domain
name after it.
— at least one line that starts with the word nameserver.
Name/address resolution (all configurations)

In all configurations (whether a DNS server is used or not), name/address
resolution must be enabled between OneControl client and server:
• For configurations using a DNS server, one way of ensuring this is by
having both the OneControl client and OneControl server platforms point
to the same DNS sever.
• For configurations where no DNS server is used, one way of ensuring this
is by manually adding the hostname and fully qualified domain name of the
OneControl server into the hosts file of the OneControl client PC.
• In all configurations, it may be necessary to manually add the hostname
and fully qualified domain name of the OneControl server into the hosts
file on a OneControl client PC. This may be required in some scenarios
where name/address resolution between the two is not accurate (eg.
some VPN configurations).
Umask and shell requirements

It is recommended that the umask value for the root user be left at the default
value (0022) before performing an installation. For upgrades and installations
OneControl scripts will work with the standard shells that come with the
operating system packages (bourne, bash, csh).

Kernel parameters
This section describes the required operating system kernel parameters.
Solaris kernel parameters

Table 5-22 on page 5-45 specifies the kernel parameters that must be set on
Oracle SPARC platforms running Solaris (both Solaris 10 and 11.1). All kernel
parameters not specified should remain at their default values. Table 5-23 on
page 5-45 specifies additional the kernel parameters that must be set on
Oracle SPARC platforms running Solaris 11.1/11.2.
Table 5-22
Solaris 10 & 11.1/11.2 required kernel parameters (all supported Oracle SPARC
platforms)
Solaris 10 & 11.1 kernel parameter Value
msgsys:msginfo_msgtql 1024
msgsys:msginfo_msgmnb 65536
shmsys:shminfo_shmmax 4294967295
shmsys:shminfo_shmmni 400
semsys:seminfo_semmns 2048
semsys:seminfo_semmni 128 (Note 1)
semsys:seminfo_semmsl 512 (Note 1)
semsys:seminfo_semopm 512 (Note 1)
semsys:seminfo_semvmx 32767
rlim_fd_cur 65536
rlim_fd_max 65536
Note 1: These 3 parameters are not used in the Solaris 11.1/11.2 operating
system. However they are still checked during OneControl installation and when
using the checkOSversion script (and flagged as a warning if not set at these
minimums). In the Solaris 11.1/11.2 scenario these warnings can be ignored.
Table 5-23
Solaris 11.1/11.2 - Additional required kernel parameters
Solaris kernel parameter Value
zfs:zfs_arc_max (Note 1) 8589934592
Note 1: This kernel parameter is a critical setting that must be set for deployments
on platforms running Solaris 11.1/11.2. If it is not set, the platform may become
extremely slow after only a few days of use.

Attention: When other network management applications or 3rd party tools

are used on the Sun platform, such as volume management or Disk Mirroring
(RAID), other kernel parameters could be required. The administrator should
use the highest number specified, otherwise the performance and stability
could be affected (including but not limited to software not being able to start
properly).
The /etc/system file contains the kernel parameter settings for the platform.
A separate line is used to define each parameter and has the following format:
set <parameter_name>=<parameter_value>
For OneControl to be successfully installed, there must not be any spaces
between the parameter name and the equals sign, or between the equals sign
and the parameter value.
Linux kernel parameters

Table 5-24 on page 5-46 specifies the kernel parameters that must be set on
Intel platforms running Linux. All kernel parameters not specified should
remain at their default values. When the OneControl Linux OS requirements
are met, these kernel parameters are automatically set (they are applied to the
system during the application of the required Linux OS patch bundle).
Table 5-24
Linux required kernel parameters (all supported Intel platforms)
Linux kernel parameter Value
net.ipv4.ip_forward 0
net.ipv4.conf.default.rp_filter 1
net.ipv4.conf.default.accept_source_route 0
kernel.sysrq 0
kernel.core_uses_pid 1
net.ipv4.tcp_syncookies 1
kernel.msgmnb 65536
kernel.msgmax 65536
kernel.shmmax 68719476736
kernel.shmall 4294967296
kernel.sem 250 32000 100 128

—continued—


Linux required kernel parameters (all supported Intel platforms)
fs.file-max 6815744
fs.aio-max-nr 1048576
net.core.rmem_default 262144
net.core.wmem_default 262144
net.core.rmem_max 25165824
net.core.wmem_max 25165824
net.ipv4.tcp_rmem 4096 262144 25165824
net.ipv4.tcp_wmem 4096 262144 25165824
net.ipv4.ip_local_port_range 32768 65500
net.ipv4.neigh.default.gc_thresh1 8192
net.core.netdev_max_backlog 5000
The /etc/sysctl.conf file contains the kernel parameter settings for the
platform. A separate line is used to define each parameter and has the
following format:
<parameter_name> = <parameter_value>
For OneControl to be successfully installed, there must be a space between
the parameter name and the equals sign, and between the equals sign and
the parameter value.
Solaris OS hardening (optional)

OneControl supports the following options for Solaris hardening:
• OS hardening scripts provided by Ciena (Solaris 10 only)
• A set of ports that can be disabled using the Solaris IPFilters functionality
(Solaris 10 and 11.1)
• Disabling of telnet and ftp services (Solaris 10 and 11.1)

Solaris 10 OS hardening scripts

Ciena provides OS hardening scripts that can be applied to a platform running
the Solaris 10 operating system to disable the standard services that are not
used. A script is also available to re-enable the services.
WARNING
OneControl 5.0 software products have been verified against a
specific set of Ciena OS hardening scripts. Disabling or
removing services other than the ones listed in the readme file
of the OS hardening scripts is not supported, and Ciena does
not accept responsibility, or provide support for any related
issues which may arise as a result. Customers should also be
aware that disabling or removing other services may lead to
undesirable behavior (software not responding, performance
related, corruption, core dumps, etc). In summary,
responsibility for any issues which arise as a result of disabling
or removing other services other than the ones listed in the
readme file of the OS hardening scripts must be understood
and accepted by the customer.
Any changes made to the original OS configuration, such as changing

ownership of directories or files, changing umask of users, custom OS
hardening excluding the OS hardening procedures that Ciena distributes,
could cause issues when upgrading. The system must be reconfigured back
to the original OS defaults before proceeding with any upgrade.
Downloading Solaris 10 OS hardening scripts

The Ciena OS hardening scripts can be downloaded by doing the following:
• Find the “Solaris 10 OS Hardening Scripts” item (Part number:
SOL10_HARDENING).
Solaris 10 and 11.1 IPFilters

A set of IPFilters can be added to block internal ports on the OneControl
servers (of the resilient pair) that are not being used.

Attention: Using IPFilters is not supported in a deployment where

OneControl’s TMF Interface component is used in conjunction with the
Applications Platform (AP). In this deployment scenario, IPFilters must not
be used to block ports on any platforms involved in this deployment.
To configure the IPFilters execute the following:

• Edit the file /etc/ipf/ipf.conf and add the following entries:
— block in quick proto tcp from any to any port = 37

Attention: You can add an IP filter rule to block port 53, only if you are not
using this port for a local DNS server. For details on DNS requirements, see
“Domain Name Service (DNS)” on page 5-42.
Attention: You can add an IP filter rule to block port 2123, only if you are not
using this port (for FTP) according to the firewall tables in the Chapter 6,
“Port requirements”.
• disable the ipfilter by typing: svcadm disable -s ipfilter

• re-enable ipfilter by typing: svcadm enable -s ipfilter
Solaris 10 and 11.1 disabling of telnet and ftp

You can also disable telnet and ftp services for additional OS hardening. To do
this execute the following:
• disable the telnet service by typing: svadm disable telnet
• disable the ftp service by typing: svadm disable ftp
WARNING
After this step you will only be able to login to the server using
ssh. You will also need to manage all of your network elements
via ssh mode and use sftp for file transfers (eg. NE backups).
Client platforms - Operating system requirements

This section describes the operating system requirements for OneControl
client platforms.
Windows OS requirements (single client platforms)

The following Windows operating systems are supported for OneControl 5.0
single client platforms:
• Windows 7 Professional, Ultimate or Enterprise Edition (32-bit & 64-bit)
The following browsers are supported for Windows based single client
platforms:
• Internet Explorer 6.1 or later
• Firefox 3.6.x or later
Windows OS requirements (multiple client platforms)

The following Windows operating systems are supported for OneControl 5.0
multiple client platforms:
• Windows 2012 Server (64-bit)

• Each user connects to a separate Remote Desktop session to run the

OneControl client
The following browsers are supported for Windows based multiple client
platforms:
Citrix requirements (multiple client platforms)

The following requirements apply to Citrix servers used as OneControl 5.0
client platforms:
• Windows 2008 Server R2 (64-bit)
• Citrix XenApp 5.6 or 6.0
The following browsers are supported for Citrix based client platforms:
Attention: The recommended hardware platform for the OneControl client

is a Windows PC or a Citrix server PC, as indicated in this section. The
Solaris/Linux OneControl client). However, for optimal client performance,
this is not recommended (and in this scenario, some craft launch
considerations may apply).
Attention: When accessing Oracle SPARC platforms running Solaris 10 via

a local or remote graphical session, the Common Desktop Environment
(CDE) must be selected. Other desktop managers are not supported.
Attention: When using X11 emulation software, it must:

- Support the operating system version being used
- Support Java 1.6
- Support the Ciena recommended OS bundle (the OS patches
affect the Xserver component)
- Have automatic font substitution disabled. Configure the
software to use the fonts provided by the platform on which the
OneControl 5.0 software products are installed.
- Additional requirements may apply. Contact your X11
emulation software vendor as required.

OneControl software patches

After the installation of the OneControl software product, the latest available
patches must be applied. On rare occasions, issues may be discovered in
these software products after they have achieved the General Availability (GA)
status (and are generally available for orders). Ciena may make available to
customers a patch bundle to resolve such issues. A patch bundle can also be
generated to add support for new network elements. These patch bundles do
not contain any operating system patches. Customers are generally notified
by a Product Change Notice (PCN) or via a bulletin of the availability of a new
patch bundle; it is recommended to periodically check online for new patch
bundles posted by Ciena.
The patch bundle is released with an associated Readme file that explains
how to apply the patch bundle to your system. The administrator should
always read the documentation before attempting to install the patch bundle.
Downloading patches for OneControl software products

The patch bundle and documentation can be downloaded by doing the
following:
• Identify the name of the latest recommended software patch that applies
to your OneControl release by looking for the word "patch" in the
description, and select link. (Part numbers for patches usually end with the
characters P0x, eg. ONEC400P02, OMEAR400P02)
Attention: If there is no link present for your OneControl release, there is no

patch bundle currently required. A maximum number of software links are
displayed on each page (you may need to check the pages beyond the first
one).

6-1
Port requirements 6-
This chapter details the ports used by OneControl 5.0.
The port information provided is valid for usage with simple single firewall
configurations. If your deployment involves a more complex firewall
configuration (such as a dual firewall layer) contact Ciena for additional
information.
Additional port information may be provided in future releases.
All ports have a bidirectional data flow unless otherwise noted.

6-2 Port requirements
Ports for OneControl (base install)

Table 6-1 on page 6-2 lists the ports used by OneControl components as part
of a base install.
Table 6-1
Port information for OneControl core components (base install)
Source SrcPort Destination DstPort Proto Application Description
OneControl core components
OneControl any OneControl 22 TCP SSH

client server
DNS server any OneControl 53 UDP Only required if DNS

server server is used
OneControl any NTP server 123 UDP NTP Only required if timing
server from external NTP
source.
any 123 or OneControl 123 UDP NTP Required from any other
any server platforms if timing from
OneControl server. All
platforms and all NEs
part of same
OneControl deployment
should be timed off of
the same NTP source.
(Always required if
6500/CPL NEs are
managed)
OneControl any OneControl 444 TCP Client-server

client server communication
OneControl any Oracle 1521 TCP Oracle listener Only required if remote
Server Server Oracle database used
OneControl any OneControl 1636 TCP LDAP LDAP port

client server
OneControl any External 1812 UDP RADIUS RADIUS authentication

Server RADIUS
server
OneControl any External 1813 UDP RADIUS RADIUS accounting

Server RADIUS
server
OneControl any OneControl 3469 TCP Adobe FLEX

client server
DNS any OneControl 5353 TCP

server
—continued—


OneControl any OneControl 7001 TCP Weblogic

client server

client server

client server
OneControl any OneControl 9002 TCP Shelf Level View

client server
OneControl any OneControl 9005 TCP WebLogic WebLogic admin (used

client server in patch installation)
OneControl any OneControl 9008 TCP WebLogic

client server
OneControl any OneControl 9009 TCP WebLogic

client server
REST API any OneControl 9010 TCP Only required if using

client server REST API functionality
REST API any OneControl 9011 TCP Only required if using

client server REST API functionality
any any OneControl 14444 TCP Security Channel Retrieval of user

server account information
OneControl any OneControl 31210 TCP License server Comms between client
client server and License server
(required between client
and server only if OSP is
deployed).
OneControl any OneControl 31500 TCP

client server
OneControl any OneControl 54964 TCP

client server
—continued—


OneControl core components if also using GR
OneControl any OneControl 1636 TCP GR OneControl data

server 1/2 server 2/1 replication
OneControl any OneControl 2636 TCP GR security channel OneControl security

server 1/2 server 2/1 data replication




OneControl any OneControl 18989 TCP GR OneControl security

server 1/2 server 2/1 data replication
OneControl any OneControl 31210 TCP License server Comms between

server 1/2 server 2/1 License servers in GR

Ports for OneControl (additional if using features: 5400/CD, 4200,

CoreStream, SONET/SDH Control Plane services, or OTN services)
Table 6-2 on page 6-5 lists the additional ports used by OneControl
components if any of the following additional features/licenses are present:
• 5400/CD
• 4200
• CoreStream
• SONET/SDH Control Plane service management
• OTN service management
Table 6-2
Port information for OneControl (additional if using features: 5400/CD, 4200, CoreStream,
SONET/SDH Control Plane services, or OTN services)
OneControl (if using: 5400/CD, 4200, CoreStream, SONET/SDH Control Plane, or OTN)
OneControl any LDAP svr 636 TCP LDAP (SSL)

Server
OneControl any LDAP svr 389 TCP LDAP (unsecure, Not recommended
Server TLS)
OneControl any RADIUS svr 1812 UDP RADIUS

Server
RADIUS svr 1812 OneControl any UDP RADIUS response Stateful reply
Server
OneControl any OneControl 7001 TCP weblogic t3 Client download and

Client Server clients without encryption
OneControl any OneControl 7002 TCP weblogic t3s Clients with SSL
Client Server encryption
OneControl if using GR (if using: 5400/CD, 4200, CoreStream, SONET/SDH Control Plane, or OTN)
OneControl NA OneControl 0/8 ICMP Echo Request/Reply

Server 1/2 Server 2/1 (ping)
OneControl any OneControl 7001 TCP Geographic Also if using SSL

Server 1/2 Server 2/1 Replication encryption
OneControl any OneControl 7002 TCP Geographic Only if using SSL

Server 1/2 Server 2/1 Replication encryption
OneControl any OneControl 31300 TCP Geographic PM replication for

Server 1/2 Server 2/1 Replication CD/5400 (from Active
server to Backup server).
Only required if MySQL
database used.

Ports for OneControl (if using feature: Manager for 6k, OM5k and CPL)
Table 6-3 on page 6-6 lists the additional ports used by OneControl
components if any of the following additional features/licenses are present:
• Manager for 6k, OM5k and CPL (co-resident with OneControl)
• Remote Manager for 6k, OM5k and CPL
Table 6-3
Port information for Manager for 6k, OM5k and CPL
Source Src Destination DstPort Proto Application Description
Port
Between client and server

(CLIENT: OneControl client - Manager for 6k, OM5k and CPL module; SERVER: OneControl server with
co-resident Manager for 6k, OM5k and CPL module, or Remote Manager for 6k, OM5k and CPL)
Client any Server 443 TCP HTTPS Client download, online

help
Client any Server 636 TCP LDAP (SSL) Security directory
Client any Server 1275 TCP Client-server

(Note 2) communication
Client any Server 1812 - 1814 UDP RADIUS RADIUS requests are
sent to this port by
default.
Client any Server 2636 TCP LDAP LDAP access port.

Uses secure LDAPS
protocol.
Client any Server 5433, TCP Client-server

5600, communication
Server Client 5649-5660
Client any Server 8003, TCP Tomcat Used for Manager for
8004 6k, OM5k and CPL
online help.
Client any Server 8004, TCP Online help Manager for 6k, OM5k,
8080 and CPL online help.
(Note 1)
Client any Server 9012 TCP HTTP (Tomcat) Client-server

(Note 3) communication (FLEX
Server Client server)
Client any Server 9014 TCP Summary server Client-server

(Note 3) communication
Server Client
—continued—


Port
Client any Server 9016 TCP HTTPS (Tomcat) Client-server

communication (FLEX
Server Client server)
Client any Server 9020 TCP Summary server Client-server

communication
Server Client
Client any Server 9022 TCP Base Server Client-server

communication (SSL)
Server Client
Client any Server 33389 TCP LDAP OMEA directory
Client any Server 55441 TCP Base Server Client-server

58081 communication
Server Client
(Note 3)
Between OneControl server and any Remote Manager for 6k, OM5k and CPL (if OneControl is using GR
this also includes any Manager for 6k, OM5k and CPL instance installed co-resident with the redundant
OneControl server)
OneControl server any Remote Manager 1099 TCP Listening port for initial
for 6k, OM5k and session connection.
CPL
OneControl server any Remote Manager 2636 TCP LDAP LDAP access port.
for 6k, OM5k and Uses secure LDAPS
CPL protocol. Required for
retrieving status details
(displayed on
Dashboard, etc.).
Remote Manager any OneControl server 9001 TCP RMI notifications

for 6k, OM5k and
CPL
OneControl server any Remote Manager 32768 - TCP RMI session port
for 6k, OM5k and 65535
CPL
OneControl server any Remote Manager 42500 - TCP TL1 gateway

for 6k, OM5k and 45600
CPL
—continued—


Port
Between resilient Manager for 6k, OM5k and CPL (whether co-resident with OneControl or remote)
Server 1/2 - Server 2/1 - - All ports required

between OneControl
server and any Remote
Manager for 6k, OM5k
and CPL (as detailed
above in this table), are
also required between
resilient Manager for 6k,
OM5k and CPL servers.
Server 1/2 any Server 2/1 20 TCP FTP Standard FTP data port
(Note 4)
Server 1/2 any Server 2/1 21 TCP FTP Standard FTP control
session port.(Note 5)
Server 1/2 any Server 2/1 22 TCP SSH Required for SSH
and CPL resiliency.
Server 1/2 any Server 2/1 23 TCP TELNET Used for technical
support access to
and CPL and ONM AP.
For use during Manager
for 6k, OM5k and CPL
upgrades, ONM AP
reachthrough to
and CPL Desktop, and
ONM AP Reachthrough
to SMI and Site
Manager.
ONM AP provides
Telnet access to
and CPL from the ONM
AP Graphical Network
Browser
—continued—


Port
Server 1/2 any Server 2/1 1024 - 5000 TCP FTP When the NE acts as the
FTP client in active FTP
mode, a port in this
range will be used to
receive an FTP data
connection from port 20
on an external FTP
server. TL1 upgrades,
backups and restores
use active FTP, with the
client on the NE.
Server 1/2 any Server 2/1 1097 TCP Required for Manager
resiliency.
Server 1/2 any Server 2/1 1812 - 1814 UDP RADIUS RADIUS requests are
sent to this port by
default, however the
port number is
provisionable. Any
change to the default
value would require a
corresponding change
to firewall settings.
Server 1/2 any Server 2/1 2636 TCP LDAP (SSL) LDAP access port.
and CPL resiliency.
Server 1/2 any Server 2/1 5433 TCP 9920, Required for Manager
30107, for 6k, OM5k and CPL
32598, resiliency.
32967,
61626
Server 1/2 any Server 2/1 24444 TCP LDAP (SSL) LDAP admin port.
and CPL resiliency.
Server 1/2 any Server 2/1 28989 TCP LDAP (SSL) LDAP replication port.
and CPL resiliency.
—continued—


Port
Server 1/2 any Server 2/1 30101 TCP REGE, Transient port used by
resiliency the REGE process
within Manager for 6k,
OM5k and CPL AP
gateway feature and
also used for Manager
resiliency.
For use when a Trail
Manager attempts to
manage an Manager for
6k, OM5k and CPL
controller to validate the
controller details.
As this is a transient
port, the connection is
dropped after the
controller has been
validated.
Server 1/2 any Server 2/1 31210 TCP License server Communication
between License
servers in GR pair
resiliency.
resiliency.
resiliency.
—continued—


Port
Between AP and Manager for 6k, OM5k and CPL (whether co-resident with OneControl or remote)
AP any OneControl server 23 TCP TELNET Used for technical

(Manager for 6k, support access to
OM5k and CPL Manager for 6k, OM5k
module) and CPL and ONM AP.
OneControl server any AP
(Manager for 6k,
upgrades, ONM AP
OM5k and CPL
reachthrough to
module)
ONM AP Reachthrough
to SMI and Site
Manager.
ONM AP provides
Telnet access to
Browser
AP any OneControl server 512 - 1024 TCP Remote login For use in Manager for
(Manager for 6k, 6k, OM5k and CPL/NE
OM5k and CPL reachthroughs from AP.
module) Also used for
communication between
and CPL resilient server
pairs.
AP any OneControl server 1812 - 1814 UDP RADIUS RADIUS requests are
(Manager for 6k, sent to this port by
OM5k and CPL default, however the
module) port number is
provisionable. Any
change to the default
value would require a
corresponding change
OneControl server any AP 6000- TCP X-Based Login For use in Manager for
(Manager for 6k, 6020 6k, OM5k and CPL
OM5k and CPL reachthroughs from AP.
module)
—continued—


Port
AP any OneControl server 9012 TCP Tomcat Used for SSO

(Manager for 6k, connection services
OM5k and CPL between AP and
module) Manager for 6k, OM5k
and CPL server.
(Manager for 6k,
OM5k and CPL
module)
AP any OneControl server 30001, TCP REGD Transient port used by

(Manager for 6k, 30011 the REGD process
OM5k and CPL within Manager for 6k,
module) OM5k and CPL AP
gateway feature.
OneControl server any AP For use after AP has
(Manager for 6k, successfully validated
OM5k and CPL an Manager for 6k,
module) OM5k and CPL
controller. AP uses this
port to send an xdr
message containing a
permanent TCP port
number which the
and CPL will use to
connect to the AP.
dropped after it is no
longer needed.
—continued—


Port
AP any OneControl server 30002, TCP REGB Transient port used by

(Manager for 6k, 30012 the REGB process
module) OM5k and CPL’s AP
gateway feature.
OneControl server any AP For use when AP
(Manager for 6k, attempts to manage an
module) and CPL controller to
validate the controller
details.
dropped after the
controller has been
validated.
AP any OneControl server 30101, TCP REGE Transient port used by

(Manager for 6k, 30111 the REGE process
module) OM5k and CPL AP
gateway feature.
For use when a Trail
(Manager for 6k,
Manager attempts to
OM5k and CPL
manage an Manager for
module)
6k, OM5k and CPL
controller to validate the
controller details.
dropped after the
controller has been
validated.
AP any OneControl server 30201 - TCP/ GNB Used by GNB for

(Manager for 6k, 30250 UDP Manager for 6k, OM5k
OM5k and CPL and CPL desktop to
module) launch GNB
applications such as
OneControl server any AP Alarm Manager and
(Manager for 6k, OSP GUI.
OM5k and CPL
module)
—continued—


Port
Between external components and Manager for 6k, OM5k and CPL
Xterminal any OneControl server 7 TCP echo Standard echo session

emulator (Manager for 6k, port. For external clients
OM5k and CPL such as Exceed to
module) determine the server
availability before
establishing connection.
This may cause delays if
the Exceed session is
being established
through a firewall.
OneControl server any NSV server 23 TCP TELNET Used for technical
(Manager for 6k, support access to
module) and CPL and ONM AP.
upgrades, ONM AP
reachthrough to
ONM AP Reachthrough
to SMI and Site
Manager.
ONM AP provides
Telnet access to
Browser
OneControl server any EAI client (OSS) 1024 - 5000 TCP EAI server EAI dynamically assign
(Manager for 6k, ports
OM5k and CPL
module)
EAI client (OSS) any OneControl server 30005 TCP Manager for 6k, EAI listening port for
(Manager for 6k, OM5k and CPL platforms where telnet is
OM5k and CPL EAI server supported
module)
EAI client (OSS) any OneControl server 30006 TCP Manager for 6k, EAI listening port for
(Manager for 6k, OM5k and CPL platforms where only
OM5k and CPL EAI server ssh is supported
module)
—continued—


Port
Note 1: The data flow for these ports is Unidirectional. All other ports have a bidirectional data flow unless
otherwise noted.
Note 2: These ports are only required if a dual firewall layer is configured between the Manager for 6k, OM5k and
CPL server and the Manager for 6k, OM5k and CPL PC client. if you plan to use this dual firewall configuration,
contact Ciena for more information.
Note 3: Secure ports 9012, 9014, 55441 (used by the Manager for 6k, OM5k and CPL client to communicate with
the Summary, Tomcat and Manager for 6k, OM5k and CPL Base servers) can be disabled when configuring the
Manager for 6k, OM5k and CPL server with the SSL only option.
Note 4: For an external FTP client, using passive FTP mode, this port is not used.For an external FTP client, using
active FTP mode, this port is used by the Manager for 6k, OM5k and CPL FTP server to initiate the FTP data
connection. For an internal FTP client, using active FTP mode, the Manager for 6k, OM5k and CPL FTP client
receives FTP data connection requests from this port on the external FTP server. Internal FTP client using passive
FTP mode is not supported. System Manager installed on Manager for 6k, OM5k and CPL uses passive FTP to
the System Manager on the 5100/5200. TL1 upgrades, backups and restores use active FTP, with the client on the
NE.
Note 5: For an external FTP client, using active or passive FTP mode, the Manager for 6k, OM5k and CPL receives
FTP control session requests on this port. For an internal FTP client, in active FTP mode, the Manager for 6k, OM5k
and CPL initiates FTP control session requests to this port on the external FTP server. Internal FTP client using
passive FTP mode is not supported. System Manager installed on Manager for 6k, OM5k and CPL uses passive
FTP to the System Manager on the Optical Metro 5100/5200. TL1 upgrades, backups and restores use active FTP,
with the client on the NE.
Ports for SLM

Table 6-4 on page 6-15 lists the ports used by OneControl if any of the
following additional features/licenses are present:
• SLM
Table 6-4
Port information for SLM
SLM
OneControl any OneControl 14940 TCP RMI

Client Server (SLM
module)
OneControl any OneControl 1024 - 65535 TCP RMI Random allocated RMI
Client Server (SLM port
module)
OneControl any OneControl 1024 - 65535 TCP RMI Random allocated RMI
Server (SLM Client port
module)

Ports for MTOSI northbound interface

• MTOSI
Table 6-5
Port information for MTOSI
MTOSI
MTOSI client any OneControl 9006 TCP

server
MTOSI client any OneControl 9007 TCP

server
OneControl any MTOSI client 9009/ TCP Notification channel Use value configured on
server variable client for notification
(9009 or configure
other)
Ports for UOG northbound interface

• UOG
Table 6-6
Port information for UOG
UOG
UOG Client any OneControl 20025 TCP CORBA.

Server (UOG NamingService
module)
UOG Client any OneControl 18001 TCP NBI main server Port configurable,
Server (UOG random assigned if not
module) specified
UOG Client any OneControl CORBA range TCP CORBA Port range configurable,
Server (UOG random assigned if not
module) specified
UOG Client any OneControl 18003 TCP NBI Port configurable,

Server (UOG NotificationService random assigned if not
module) specified
OneControl any UOG Client variable TCP NBI EventChannel Port depends on client
Server (UOG app, Netcool seems to
module) use 20025 by default

Ports for TMF northbound interface

• TMF
Table 6-7
Port information for TMF
TMF
TMF client variable TMF Server 52480 TCP CORBA. Base TMF TMF client to allocate
functionality. (Note 1, Note 2)
TMF client variable TMF Server 52481 TCP CORBA. TMF client to allocate
Event service. (Note 1, Note 2)
TMF client variable TMF Server 52486 TCP CORBA. TMF client to allocate
Naming Service. (Note 1, Note 2)
TMF Server any TMF client variable TCP CORBA. TMF client to allocate
NMS_Session ping. fixed port (Note 1, Note
2)
TMF Server 540 Manager for any TCP remsh port. When retrieval of OM5k
6k, OM5k OM5k Intra-NE Intra-NE topological
and CPL topological link links is enabled. (Note 3)
server
TMF Server 10001 OM5k NEs any TCP OM5k Intra-NE When retrieval of OM5k
topological link Intra-NE topological
links is enabled. (Note 3)
TMF Server 30001, Manager for any TCP (Note 3)

30002, 6k, OM5k
30011, and CPL
30012, server
30101,
30111
Manager for any TMF Server 52450-52470 TCP (Note 3)

6k, OM5k
and CPL
server
—continued—


Port information for TMF
Note 1: TMF allows configuration of what ports are used by the interface to facilitate usage with a firewall between
the server and client. For more information on this enhancement, and how to change specific ports, refer to the
appropriate procedure in the OneControl TMF Interface Fundamentals, 450-3271-001.
Note 2: To note for TMF client to TMF Server interaction:
•To use TMF, TMF clients need to obtain the TMF server’s IOR. The TMF server's IOR can be obtained
several ways, including connecting to the CORBA Name service (which runs on port 52486). Once it
has the IOR, the TMF client opens a connection to the TMF server (on port 52480).
•On connecting to the TMF Server, the TMF client passes an NMS_Session instance. The TMF Server
uses this instance to verify the client is alive (using the session's “ping” method periodically). It is the
responsibility of the TMF client to allocate a fixed port for the NMS_Session object (or open all outgoing
ports from the TMF server to all TMF clients).
•Once a client has connected to the TMF server, it can use the CORBA event service to retrieve
asynchronous events from the TMF Server. The CORBA event service is a separate process (on port
52481) and uses separate sockets to pass events to the client.
Note 3: To note for TMF Server to NE/controller interaction:
•The TMF server connects to each controller (i.e. Manager for 6k, OM5k and CPL server) by connecting
to its “regd” port. The controller then opens a connection to the TMF Server. Separate channels may
be opened for trail, attribute management, and inventory data feeds. If OM5k Intra-NE topological link
retrieval is enabled, the TMF server will use “rmsh” to the Manager for 6k, OM5k and CPL server
managing the NE and perform a TL1 login to each NE.

Ports for OSP

• OSP
Table 6-8
Port information for OSP
OSP (when installed co-resident with Manager for 6k, OM5k and CPL)
OneControl any NDS server 7 TCP TCP Echo See Note 1

client (OSP
GUI)
OneControl any NDS server 1187 TCP Base OSP functionality

server (access to OSP cache).
(Manager for Also applies between
6k, OM5k Manager for 6k, OM5k
and CPL and CPL resilient
module) servers (whether
co-resident with
OneControl or Remote)
OneControl any NDS server 8080 TCP Help file access

client (OSP
GUI)
NDS server 35000-35 OneControl any TCP CORBA. Base OSP CORBA ports used by
599 client (OSP functionality NDS server to
GUI) communicate with all
north-bound clients
(OSP GUI, Resource
Tool, Topology
Provisioner tool, etc.)
OneControl 58000-58 NDS server any TCP CORBA. Base OSP CORBA ports used by
client (OSP 199 functionality OSP GUI to
GUI) communicate with NDS
server. (Note 1)
any any NDS server 58772 TCP Naming Service
OneControl - NDS server - ICMP ICMP ping

client (OSP
GUI)
NDS server - OneControl - ICMP ICMP ping

client (OSP
GUI)
—continued—


Port information for OSP
OSP (when installed co-resident with AP, in an AP deployment)
OSP GUI any NDS server 1187 TCP Base OSP

functionality (access
to OSP cache)
OSP GUI any NDS server 8080 TCP Help file access
(AP server (AP server
where OSP where NDS
GUI is server is
installed and installed)
launched
from)
NDS server 35000-35 OSP GUI any TCP CORBA. Base OSP CORBA ports used by
(AP server 599 (AP server functionality NDS server to
where NDS where OSP communicate with all
server is GUI is north-bound clients
installed) installed and (OSP GUI, Resource
launched Tool, Topology
from) Provisioner tool, etc.)
OSP GUI 58000-58 NDS server any TCP CORBA. Base OSP CORBA ports used by
(AP server 199 (AP server functionality OSP GUI to
where OSP where NDS communicate with NDS
GUI is server is server.
installed and installed)
launched
from)
any any NDS server 58772 TCP Naming Service
Note 1: If the OSP GUI is communicating with the NDS server through a VPN setup:
• Port 7, the echo port, may need to be opened, and echo services may need to be enabled. Echo
services can be enabled by entering the following UNIX commands in a terminal session on the SUN
platform (as the root user):
svcadm enable svc:/network/echo:dgram
svcadm enable svc:/network/echo:stream
• The outbound communication from the OSP GUI to the NDS server must be routed through the public
VPN assigned IP of the PC that the OSP GUI is running on. If any other IP is used to establish the
session (eg. the private IP of the PC), the OSP GUI will not be able to communicate with the NDS
server. Contact your system administrator to ensure that the DCN/router setup meets this requirement.
Your system administrator can check this by verifying the IP address used for the TCP connection
between the port 58*** (000-199) on the PC, and port 58772 of the NDS server.

Ports for NSV

• NSV
Table 6-9
Port information for NSV
NSV
Manager for 6k any AP 58772 TCP/ NSV Used by NSV server

OM5k & CPL / UDP component to
NSV server communicate with NDS
Server on AP or Solaris.
AP any Manager for
6k OM5k &
CPL/ NSV
server
Manager for 6k any Manager for

OM5k & CPL/ 6k OM5k &
NSV server CPL/ NSV
server resilient

NSV server CPL/ NSV
resilient server

NSV server CPL/ NSV
that has the server Need to
NDS access NDS

NSV server CPL/ NSV
Need to server that has
access NDS the NDS

Ports for CESD NEs (managed via ESM)

Table 6-10 on page 6-22 lists the ports used when CESD NEs are managed
(via ESM). Additional ports may be required by the ESM software. Refer to the
ESM Engineering Guide, 009-3216-022, for more information.
Table 6-10
Port information for CESD NEs
CESD NEs
CESD NEs any OneControl 137 UDP

server

server
OneControl any ESM server 3602 TCP See Note 1.

client (ESM
module)
OneControl any ESM server 3605 TCP See Note 1.

client (ESM
module)

server
CESD NEs any OneControl 10062 UDP/

server TCP
ESM server any OneControl 10062 UDP/

server TCP
CESD NEs any OneControl 14000 TCP

server
OneControl any ESM server 14934 TCP

server

server

server

server

server
Note 1: Additional ports may be required by the ESM software. Refer to the ESM Engineering Guide,
009-3216-022, for more information. Of specific interest is the scenario where a firewall is placed between an
ESM/OneControl client and an ESM/OneControl server. in this scenario, users should consult the section in the
ESM Engineering Guide on how to make dynamic ports static.

Ports for 5410/5430 NEs

Table 6-11 on page 6-23 lists the ports used when 5410/5430 NEs are
managed.
Table 6-11
Port information for 5410/5430 NEs
5410/5430 NEs
OneControl any 5400 80 TCP HTTP Configurable on NE

Server
OneControl any 5400 23 TCP Telnet Config backups

Server
OneControl any 5400 992 TCP Secure telnet Config backups, can
Server replace telnet
OneControl any 5400 683 TCP CORBA IIOP Configurable on NE.

Server Fixed port can be
specified via NE CLI.
Default used is 683.
5400 any OneControl any/ TCP CORBA Event Configurable in

Server CORBA Range Channel OneControl. See Note 1
for details.
OneControl any 5400 7 TCP TCP Echo Keepalive on all 5 NE

Server addresses
OneControl any 5400 10201 TCP TL1 Configurable on NE, not

Server used by OneControl
5400 any OneControl 7002 TCP HTTPS Config backups, can

Server replace FTP
5400 any OneControl 21 TCP FTP control Config backups, SW

Server download
OneControl 20 5400 any TCP FTP data Config backups, SW

Server download
OneControl any 5400 21 TCP FTP control FTP server on NE, not
Server used by OC
5400 20 OneControl any TCP FTP data FTP server on NE, not
Server used by OC
OneControl any 5400 22 TCP SSH Standard SSH port.

Server Used for NE
management via SSH
5400 any OneControl 22 TCP SSH and sftp.
Server
—continued—


OneControl any 5400 80 TCP HTTP Configurable on NE

Client (Node
Manager)
OneControl any 5400 683 TCP CORBA IIOP Configurable on NE.

Client (Node Fixed port can be
Manager) specified via NE CLI.
Default used is 683.
5400 any OneControl 35001-35011 TCP CORBA Event Configurable in env.txt

Client (Node Channel (default 35001-35011),
Manager) minimum 1 port per
active NM session
OneControl any 5400 as configured in TCP When using a

Server 5400 GNE port configuration with 6500
NAT table RNEs behind a 5400
(possible GNE, a reverse port
range: NAT table is used on the
49152-65535) 5400 to map each 6500
RNE telnet/ssh port
(10001/20001) to a port
visible on the DCN.
Only those ports
actually being used in
the range need to be
enabled.
OneControl any 5400 7 TCP TCP Echo Keepalive on all 5 NE

Client (Node addresses
Manager)
Note 1: By default OneControl selects any port available. This can be changed by selecting a CORBA
range of values in the OC Configure GUI of OneControl (Integrations>CD tab). The range must be large
enough to handle all CoreDirector and 5410/5430 NE types. To determine the range:
• Calculate the number of Core Director NEs managed. Reserve 9 ports for each NE.
• Calculate the number of 5410/5430 NEs managed. Reserve 6 ports for each NE.
• Choose a starting port that will be less likely to overlap with ports used by other applications (eg.
starting port 30300).
• Double the range to allow for growth and possible overlap with ports used by other applications.
• Eg. For a network with 10 5410/5430s and 5 CDs, use range 30300-30510.

Ports for CoreDirector NEs

Table 6-12 on page 6-25 lists the ports used when CoreDirector NEs are
managed.
Table 6-12
Port information for CoreDirector NEs
CoreDirector NEs
OneControl any CoreDirector 80 TCP HTTP

Server
OneControl any CoreDirector 23 TCP telnet Config backups

Server
OneControl any CoreDirector BOA Main Port/ TCP CORBA BOA main port is
Server 1024-1030 configurable. Fixed port
can be specified via NE
CLI. Default used is
1024-1030.
OneControl any CoreDirector 3083 TCP TL1 Not used by OneControl

Server
CoreDirector any OneControl any/ TCP CORBA Event Configurable in

Server CORBA Range Channel OneControl. See Note 1
for details.
OneControl any/ CoreDirector 30003 UDP Application Level Configurable in

Server UDP Ping Request OneControl. See Note 2
Range for details.
CoreDirector 30003 OneControl any UDP Application Level Reply can originate from
Server Ping Reply different IP than the
destination of the ALP
request
OneControl any CoreDirector 19023 TCP Secure telnet Config backups, can
Server replace telnet
CoreDirector any OneControl 7002 TCP HTTPS Config backups, can

Server replace FTP
CoreDirector any OneControl 21 TCP FTP control Config backups, SW

Server download
OneControl 20 CoreDirector any TCP FTP data Config backups, SW

Server download
OneControl any CoreDirector 21 TCP FTP control FTP server on NE, not
—continued—


CoreDirector 20 OneControl any TCP FTP data FTP server on NE, not
OneControl NA CoreDirector 8 ICMP Echo request

Server
CoreDirector NA OneControl 0 ICMP Echo reply Stateful ping

Server
OneControl any CoreDirector 30003 UDP Application Level All addresses of the NE,
Client (Node Ping Request Mgmt as well as both
Manager) CM Main and Aux if
configured
CoreDirector 30003 OneControl any UDP Application Level Reply can originate from
Client (Node Ping Reply different IP than the
Manager) destination of the ALP
request
OneControl any CoreDirector 80 TCP HTTP

Client (Node
Manager)
OneControl any CoreDirector BOA Main Port/ TCP CORBA BOA main port is
Client (Node 1024-1030 configurable. Fixed port
Manager) can be specified via NE
CLI. Default used is
1024-1030.
CoreDirector any OneControl any TCP CORBA Event channels

Client (Node
Manager)
CoreDirector any LDAP svr 636 TCP LDAP (SSL)
CoreDirector any LDAP svr 389 TCP LDAP (unsecure, Not recommended
TLS)
CoreDirector any RADIUS svr 1812 UDP RADIUS From R6.2 onwards
—continued—


Note 1: By default OneControl selects any port available. This can be changed by selecting a CORBA
enough to handle all CoreDirector and 5410/5430 NE types. To determine the range:
• Calculate the number of 5410/5430 NEs managed. Reserve 6 ports for each NE.
• Eg. For a network with 10 5410/5430s and 5 CDs, use range 30300-30510.
Note 2: By default OneControl selects any port available. This can be changed by selecting a UDP
enough to handle all CoreDirector NE types. To determine the range:

Ports for 4200 NEs

Table 6-13 on page 6-28 lists the ports used when 4200 NEs are managed.
Table 6-13
Port information for 4200 NEs
4200 NEs
OneControl any OneControl 1521 TCP Oracle replication

Server (4200 Server (4200
module) 1/2 module)2/1
OneControl any OneControl 22 TCP SSH File replication

Server (4200 Server (4200
module) 1/2 module) 2/1
OneControl any 4200 80 TCP HTTP/XML Unsecure option, NE

Server (4200 config
module)
OneControl any 4200 443 TCP HTTS/XML Secure option, NE

Server (4200 config
module)
OneControl any 4200 23 TCP telnet/CLI Unsecure option, NE

Server (4200 config
module)
OneControl any 4200 22 TCP SSH/SecureCLI Secure option, NE

Server (4200 config
module)
OneControl any 4200 3083 TCP TL1 Manual use

Server (4200
module)
OneControl any 4200 161 UDP SNMP

Server (4200
module)
4200 161 OneControl any UDP SNMP Stateful reply

Server (4200
module)
4200 any OneControl 21 TCP FTP control Unsecure option, NE

Server (4200 config
module)
OneControl 20 4200 any TCP FTP data Manual use

Server
—continued—


4200 any OneControl 40600-40700 TCP Passive FTP data If restricted on FTP
Server (4200 Server, by default
module) 1024-65535
4200 any OneControl 22 TCP SFTP Secure option, NE

Server (4200 config
module)
4200 any OneControl 16500 UDP SNMP traps

Server (4200
module)
OneControl any 4200 33434-33524 UDP traceroute

Server (4200
module)
4200 NA OneControl 3 ICMP ICMP Destination

Server (4200 unreachable
module)
DCN NA OneControl 11 ICMP ICMP Time exceeded

Server (4200
module)
4200 any OneControl 33434-33524 UDP traceroute

Server (4200
module)
OneControl NA 4200 3 ICMP ICMP Destination

Server (4200 unreachable
module)
DCN NA 4200 11 ICMP ICMP Time exceeded
OneControl NA 4200 8 ICMP Echo request

Server
4200 NA OneControl 0 ICMP Echo reply Stateful ping

Server
OneControl any 4200 80 TCP HTTP NodeManager Unsecure option, NE

Client (NM) config
OneControl any 4200 443 TCP HTTPS Secure option, NE

Client (NM) NodeManager config
OneControl any 4200 23 TCP telnet CLI Unsecure option, NE

Client config
OneControl any 4200 22 TCP SSH SecureCLI Secure option, NE

Client config
—continued—


OneControl any 4200 161 UDP SNMP real time PM

Client
4200 161 OneControl any UDP SNMP real time PM Stateful reply
Client
4200 any OneControl 33434-33524 UDP traceroute May causes severe

Client delay on NodeManager
if blocked
OneControl NA 4200 3 ICMP ICMP Destination May causes severe

Client unreachable delay on NodeManager
if blocked
DCN NA 4200 11 ICMP ICMP Time exceeded May causes severe

delay on NodeManager
if blocked
4200 any RADIUS svr 1812 UDP RADIUS

(RADIUS)
RADIUS svr 1812 4200 any (RADIUS) UDP RADIUS response Stateful reply
OneControl any OneControl 5656 TCP CORBA Naming

Client Server (4200 Service
module)
OneControl any OneControl 6565 TCP CORBA Naming

Client Server (4200 Service SSL
module)
OneControl any OneControl 5757 TCP G10 support Defined as Naming

Client Server (4200 Service port + 101
module)
OneControl 4001-500 OneControl 5501-5700 TCP NCS (CORBA Configurable in

Client 0 Server (4200 services) ipiNCS.prop. Defaults:
module) • com.ciena.server.serve
r.port.min=5501
OneControl 60001-61 OneControl 3001-3100 TCP NCS (CORBA,
Server (4200 000 Client EventService) • com.ciena.server.serve
module) r.port.max=5700
• com.ciena.server.client
OneControl any OneControl 60001-61000 TCP NCS (CORBA, .port.min=60001
Client Server (4200 EventService)
• com.ciena.server.client
module)
.port.max=61000
• com.ciena.client.port.m
in=3001
• com.ciena.client.port.m
ax=3100

Ports for CoreStream NEs

Table 6-14 on page 6-31 lists the ports used when CoreStream NEs are
managed.
Table 6-14
Port information for CoreStream NEs
CoreStream NEs
OneControl any CoreStream 6000 TCP GDMO

Server (CS
module)
OneControl any CoreStream 161 TCP NodeManager

Server (CS
module)
OneControl any CoreStream 23 TCP Craft

Server (CS
module)
OneControl any CoreStream 992 TCP Secure telnet Secure option, NE

Server (CS config
module)
OneControl NA CoreStream 8 ICMP Echo request Prior to Craft session

Server (CS
module)
CoreStream NA OneControl 0 ICMP Echo reply Prior to Craft session,

Server (CS stateful ping
module)
CoreStream variable_ OneControl 69 UDP TFTP Config backup/restore,

TFTP1 Server (CS APM, SW download
module)
OneControl variable_ CoreStream variable_TFTP UDP TFTP Config backup/restore,

Server (CS TFTP2 1 APM, SW download,
module) stateful TFTP
CoreStream any HTTPS 443 TCP HTTPS Config backup/restore,

Server APM, SW download
OneControl any CoreStream 161 TCP NodeManager

Client (Craft)
OneControl any CoreStream 23 TCP Craft

Client (Craft)
OneControl any CoreStream 992 TCP Secure telnet Secure option, NE

Client (Craft) config
—continued—


Port information for CoreStream NEs
OneControl NA CoreStream 8 ICMP Echo request Prior to Craft session

Client (Craft)
CoreStream NA OneControl 0 ICMP Echo reply Prior to Craft session,

Client (Craft) stateful ping
OneControl any OneControl 22 TCP SSH CTM client with

Client Server Xencryption
OneControl any OneControl 512 TCP rexec CTM client without

Client Server Xencryption
OneControl 32768 - OneControl any TCP rexec CTM client without

Server 65535 Client Xencryption
OneControl any OneControl 6000 TCP X11 CTM client without

Server Client Xencryption
OneControl any OneControl 25000-26000 TCP CoreStream Upper limit is 25000 + 2*

Server Client NodeManager number of users
CoreStream any RADIUS svr 1812 UDP RADIUS
RADIUS svr 1812 CoreStream any UDP RADIUS response Stateful reply
Ports for FlexSelect 40G NEs

Table 6-15 on page 6-32 lists the ports used when FlexSelect 40G NEs are
managed.
Table 6-15
Port information for FlexSelect 40G NEs
FlexSelect 40G NEs
OneControl NA 40G 8 ICMP Echo request

Server
OneControl any 40G 161 UDP SNMP

Server (SNMP)
40G NA OneControl 0 ICMP Echo reply

Server
40G 161 OneControl any (SNMP) UDP SNMP Stateful reply

Server
40G any OneControl 16200 UDP SNMP traps Listen port configurable,
Server might be more than 1 for
large 40G networks

Ports for O-APS NEs

Table 6-16 on page 6-33 lists the ports used when O-APS NEs are managed.
Table 6-16
Port information for O-APS NEs
O-APS NEs
OneControl any OAPS 3082 TCP TL1

Server
OAPS any OneControl 21 TCP FTP control SW download

Server
OneControl 20 OAPS any TCP FTP data SW download

Server
OneControl NA OAPS 8 ICMP Echo request Prior to NM session

Client (Node
Manager)
OAPS NA OneControl 0 ICMP Echo reply Prior to NM session,

Client (Node stateful ping
Manager)
OneControl any OAPS 3082 TCP TL1 Node Manager

Client (Node
Manager)
Ports for CN2130/CN2300 NEs

Table 6-17 on page 6-33 lists the ports used when CN2130/CN2300 NEs are
managed.
Table 6-17
Port information for CN2130/CN2300 NEs
CN2130/CN2300 NEs
OneControl any CN2130, 80 TCP HTTP/XML Secure option, NE

Server CN2300 config
OneControl any CN2130, 161 UDP SNMP

Server (SNMP) CN2300
CN2130, 161 OneControl any (SNMP) UDP SNMP Stateful reply

CN2300 Server
CN2130, any OneControl 162 UDP SNMP traps

CN2300 Server

Ports for OM5000 NEs

Table 6-18 on page 6-34 lists the ports used when OM5000 NEs are
managed.
Table 6-18
Port information for OM5000 NEs
OM5000 NEs
Manager for 6k, any 5000 20 TCP FTP Standard FTP data session port.
OM5k and CPL server (Note 1)
5000 any Manager for 6k,
OM5k and CPL server
Manager for 6k, any 5000 21 TCP FTP Standard FTP control session
OM5k and CPL server port.(Note 2)
OM5k and CPL server
Manager for 6k, any 5000 23 TCP TELNET Used for technical support.
OM5k and CPL server
OM5k and CPL server
Manager for 6k, any Manager for 6k, 80 TCP HTTP Used to launch System Manager.
OM5k and CPL PC & OM5k and CPL server Used by Manager for 6k, OM5k
SUN desktop and CPL Desktop to establish
connection to the Manager for 6k,
OM5k and CPL Server.
Manager for 6k, any 5000 161 TCP / NTP Standard SNMP access port.
OM5k and CPL server UDP Used by System Manager and
5000 any Manager for 6k, 3rd-party SNMP-based
managers. In public-IP mode, all
OM5k and CPL server
shelves are accessed using this
port. In private-IP mode, this port
is used to access the host shelf (a
GNE). Ports 8001 to 8064 are
used to access the remaining
shelves (see below).
When System Manager is used,
SNMP traps are sent from this
port on the NE to a random port
on the System Manager
workstation, determined on
System Manager start-up.
Manager for 6k, any NE 162 UDP SNMPTRAP Optional
OM5k and CPL server Standard SNMP trap listening
port used only by 3rd-party SNMP
based management stations.
—continued—


Manager for 6k, any NE 179 TCP BGP Standard port used for BGP peer
OM5k and CPL server connections. Only used when
BGP is provisioned as the GNE
NE any Manager for 6k,
OM5k and CPL server DCN gateway routing protocol.
The connection may be initiated
by either the Optical Metro
5100/5200 GNE or the external
router.
Manager for 6k, any 5000 1024 to TCP FTP When the NE acts as the FTP
OM5k and CPL server 5000 client in active FTP mode, a port
(include NE craft) in this range will be used to
5000 any Manager for 6k, receive an FTP data connection
from port 20 on an external FTP
OM5k and CPL server
server. TL1 upgrades, backups
and restores use active FTP, with
the client on the NE.
Manager for 6k, any 5000 1812 UDP RADIUS RADIUS requests are sent to this
OM5k and CPL server (included port by default, however the port
in 1024 to number is provisionable. Any
5000 port) change to the default value would
OM5k and CPL server
require a corresponding change
Manager for 6k, any Session Manager 1966 TCP Session System Manager accesses this
OM5k and CPL server (SMI) (included Manager port for session management.
in 1024 to (SMI)
5000 port)
Manager for 6k, any 5000 2122 and TCP FTP When the NE acts as the FTP
OM5k and CPL server 2123 client in active FTP mode, a port
(included in this range will be used to
in 1024 to receive an FTP data connection
OM5k and CPL server
5000) from port 20 on an external FTP
server. TL1 upgrades, backups
and restores use active FTP, with
the client on the NE.
Manager for 6k, any 5000 5566 TCP NE For use when upgrading the NE
OM5k and CPL server upgrades software from Manager for 6k,
OM5k and CPL platform
OM5k and CPL server
Manager for 6k, any 5000 5567 TCP NE For use when upgrading the NE
OM5k and CPL server upgrades software from Manager for 6k,
OM5k and CPL platform
OM5k and CPL server
Manager for 6k, any 5000 8001 to UDP SNMP Used in private-IP mode only to
OM5k and CPL server 8064 access non-System
Manager-host shelves. The
specific port for a particular NE is
OM5k and CPL server
(8000 + shelfID). Used by System
Manager and 3rd-party
SNMP-based managers.
—continued—


Manager for 6k, any 5000 8180 UDP HTTP For http.
OM5k and CPL server
OM5k and CPL server
Manager for 6k, any 5000 10001 TCP Manager for For use by Manager for 6k, OM5k
OM5k and CPL / NSV 6k, OM5k and CPL Mediation when gaining
server and CPL association with an NE.
5000 any Manager for 6k, Mediation
OM5k and CPL / NSV
server
Manager for 6k, any 5000 10002 TCP TELNET Standard debug port for TL1
OM5k and CPL server terminal session.
OM5k and CPL server
Manager for 6k, any Manager for 6k,
OM5k and CPL PC & OM5k and CPL server
Sun desktop
Note 1: For an external FTP client, using passive FTP mode, this port is not used. For an external FTP client, using active FTP
mode, this port is used by the Manager for 6k, OM5k and CPL FTP server to initiate the FTP data connection. For an internal FTP
client, using active FTP mode, the Manager for 6k, OM5k and CPL FTP client receives FTP data connection requests from this
port on the external FTP server. Internal FTP client using passive FTP mode is not supported. i.e System Manager installed on
Manager for 6k, OM5k and CPL uses passive FTP to the System Manager on the 5100/5200. backups / restores and Software
Delivery use active FTP, with the client on the NE
Note 2: For an external FTP client, using active or passive FTP mode, the Manager for 6k, OM5k and CPL receives FTP control
session requests on this port. For an internal FTP client, in active FTP mode, the Manager for 6k, OM5k and CPL initiates FTP
control session requests to this port on the external FTP server. Internal FTP client using passive FTP mode is not supported.
System Manager installed on Manager for 6k, OM5k and CPL uses passive FTP to the System Manager on the 5100/5200.
backups / restores and Software Delivery use active FTP, with the client on the NE.

Ports for CPL NEs

Attention: When managing CPL and 6500 NEs in Manager for 6k, OM5k
and CPL, you must take into consideration the Secure Mode column that is
included within the Firewall table. If you are managing your CPL or 6500 NEs
in secure mode (enrolling the NEs in Manager for 6k, OM5k and CPL by
selecting the Use SSH option), then you must open the ports labelled as
Secure and Both. If you are not in secure mode (enrolling the NEs in
Manager for 6k, OM5k and CPL without selecting the Use SSH option), then
you must open the ports labelled as Non Secure and Both.
Table 6-19 on page 6-37 lists the ports used when CPL NEs are managed.
Table 6-19
Port information for CPL NEs
Source SrcPort Destination DstPort Proto Application Secure Description
Mode
CPL NEs
Manager for any CPL 20 TCP FTP non- Standard FTP data session port. (Note
6k, OM5k secure 1)
and CPL
server
CPL any Manager for
6k, OM5k and
CPL server
Manager for any CPL 21 TCP FTP non- Standard FTP control session port.
6k, OM5k secure (Note 2)
and CPL
server
CPL any Manager for
6k, OM5k and
CPL server
Manager for any CPL 23 TCP TELNET Both Used for technical support.
6k, OM5k
and CPL
server
CPL any Manager for
6k, OM5k and
CPL server
Manager for any CPL 80 TCP HTTP Both Used to launch craft.
6k, OM5k Used by Manager for 6k, OM5k and
and CPL CPL Desktop to establish connection
server to the Manager for 6k, OM5k and CPL
Server.
—continued—


Mode
Manager for any CPL 1024 to TCP FTP non- When the NE acts as the FTP client in
6k, OM5k 5000 secure active FTP mode, a port in this range
and CPL will be used to receive an FTP data
server connection from port 20 on an external
(include NE FTP server. TL1 upgrades, backups
craft) and restores use active FTP, with the
client on the NE.
CPL any Manager for
6k, OM5k and
CPL server
Manager for any CPL 1812 UDP RADIUS Secure RADIUS requests are sent to this port
6k, OM5k (part of by default, however the port number is
and CPL 1024 to provisionable. Any change to the
server 5000) default value would require a
corresponding change to firewall
CPL any Manager for
settings.
6k, OM5k and
CPL server
Manager for any CPL 2122 & TCP FTP non- When the NE acts as the FTP client in
6k, OM5k 2123 secure active FTP mode, a port in this range
and CPL (part of will be used to receive an FTP data
server 1024 to connection from port 20 on an external
CPL any Manager for 5000) FTP server. TL1 upgrades, backups
and restores use active FTP, with the
6k, OM5k and
client on the NE.
CPL server
Manager for any CPL 10001 TCP Manager for non- For use by Manager for 6k, OM5k and
6k, OM5k 6k, OM5k secure CPL Mediation when gaining
and CPL and CPL association with an NE.
server Mediation
CPL any Manager for
6k, OM5k and
CPL / NSV
server
Manager for any CPL 10002 TCP TELNET Both Standard debug port for TL1 terminal
6k, OM5k session.
and CPL
server
CPL any Manager for
6k, OM5k and
CPL server
Manager for any Manager for
6k, OM5k 6k, OM5k and
and CPL PC CPL server
& Sun
desktop
—continued—


Mode
Manager for any CPL 20000 TCP Manager for Secure For use by the Manager for 6k, OM5k
6k, OM5k 6k, OM5k and CPL mediation layer when gaining
and CPL and CPL association with the NE (SSH mode).
server Mediation
CPL any Manager for Only required for CPL 10.1 or later.
6k, OM5k and
CPL server
Manager for any CPL 20001 TCP Manager for Secure For use by the Manager for 6k, OM5k
6k, OM5k 6k, OM5k and CPL mediation layer when gaining
server Mediation
CPL any Manager for
6k, OM5k and
CPL server
Manager for any 6500 20004 TCP SFTP Secure Used for SFTP SSH when the NE is
6k, OM5k to the SFTP client.
and CPL 20020
server
Note 1: For an external FTP client, using passive FTP mode, this port is not used. For an external FTP client, using active FTP
port on the external FTP server. Internal FTP client using passive FTP mode is not supported. i.e System Manager installed on
Manager for 6k, OM5k and CPL uses passive FTP to the System Manager on the Optical Metro 5100/5200. backups / restores
and Software Delivery use active FTP, with the client on the NE.
System Manager installed on Manager for 6k, OM5k and CPL uses passive FTP to the System Manager on the Optical Metro
5100/5200. backups / restores and Software Delivery use active FTP, with the client on the NE.

Ports for 6500 NEs

Attention: When managing CPL and 6500 NEs in Manager for 6k, OM5k
and CPL, you must take into consideration the Secure Mode column that is
included within the Firewall table. If you are managing your CPL or 6500 NEs
in secure mode (enrolling the NEs in Manager for 6k, OM5k and CPL by
selecting the Use SSH option), then you must open the ports labelled as
Secure and Both. If you are not in secure mode (enrolling the NEs in
Manager for 6k, OM5k and CPL without selecting the Use SSH option), then
you must open the ports labelled as Non Secure and Both.
Table 6-20 on page 6-40 lists the ports used when 6500 NEs are managed.
Table 6-20
Mode
6500 NEs
Manager for any 6500 20 TCP FTP non- Standard FTP data session port. (Note 1)
6k, OM5k secure
and CPL
server
6500 any Manager for
6k, OM5k
and CPL
server
Manager for any 6500 21 TCP FTP non- Standard FTP control session port. (Note
6k, OM5k secure 2)
and CPL
server
6k, OM5k
and CPL
server
Manager for any 6500 22 TCP SSH Secure Standard SSH port.
6k, OM5k Used for network element management
and CPL via SSH and sftp.
server
6k, OM5k
and CPL
server
—continued—


Mode
Manager for any 6500 23 TCP TELNET Both Used for technical support. Echo is ON
6k, OM5k (Optional).
and CPL
server
6k, OM5k
and CPL
server
Manager for any Manager for 80 TCP HTTP Both Used to launch System Manager.
6k, OM5k 6k, OM5k Used by Manager for 6k, OM5k and CPL
and CPL PC and CPL Desktop to establish connection to the
& SUN server Manager for 6k, OM5k and CPL Server.
desktop
Manager for any 6500 161 UDP SNMP Both Standard SNMP access port. Used by
6k, OM5k System Manager and 3rd-party
and CPL SNMP-based managers. In public-IP
server mode, all shelves are accessed using
this port. In private-IP mode, this port is
6k, OM5k used to access the host shelf (a GNE).
Ports 8001 to 8064 are used to access
and CPL
the remaining shelves (see below).
server
Manager for any NE 162 UDP SNMPTRAP Both Standard SNMP trap listening port used
6k, OM5k only by 3rd-party SNMP based
and CPL management stations (Optional).
server
Manager for any 6500 1024 to TCP FTP Non- When the NE acts as the FTP client in
6k, OM5k 5000 secure active FTP mode, a port in this range will
and CPL be used to receive an FTP data
server connection from port 20 on an external
(include NE FTP server. TL1 upgrades, backups and
craft) restores use active FTP, with the client
on the NE.
6k, OM5k
and CPL
server
Manager for any 6500 1812, UDP RADIUS Secure RADIUS requests are sent to this port by
6k, OM5k 1813 default, however the port number is
and CPL (in 1024 provisionable. Any change to the default
server to 5000) value would require a corresponding
change to firewall settings.
6k, OM5k
and CPL
server
—continued—


Mode
Manager for any 6500 2122 TCP FTP Non- When the NE acts as the FTP client in
6k, OM5k and secure active FTP mode, a port in this range will
and CPL 2123 be used to receive an FTP data
server (in 1024 connection from port 20 on an external
to 5000) FTP server. TL1 upgrades, backups and
6k, OM5k restores use active FTP, with the client
on the NE.
and CPL
server
Manager for any 6500 8888 TCP TELNET Both Used for remote debug access to 6500
6k, OM5k BB by Ciena (Optional).
and CPL
server
6k, OM5k
and CPL
server
Manager for any 6500 10001 TCP Manager for Non- For use by Manager for 6k, OM5k and
6k, OM5k 6k, OM5k secure CPL Mediation when gaining association
and CPL and CPL with an NE. Echo is OFF.
server Mediation
6k, OM5k
and CPL
server
Manager for any 6500 10002 TCP TELNET Both Standard debug port for TL1 terminal
6k, OM5k session (Optional).
and CPL
server
6k, OM5k
and CPL
server
6k, OM5k 6k, OM5k
and CPL PC and CPL
& Sun server
desktop
Manager for any 6500 10010 TCP Manager for Both Used by the Manager for 6k, OM5k and
6k, OM5k 6k, OM5k CPL to access OSI Rlogin from the
and CPL and CPL General Utilities.
server Mediation
6k, OM5k
and CPL
server
—continued—


Mode
Manager for any 6500 10020 TCP Manager for Both Used to access Ciena command line
6k, OM5k 6k, OM5k interface.
and CPL and CPL
server Mediation
6k, OM5k
and CPL
server
Manager for any 6500 20000 TCP Manager for Secure For use by the Manager for 6k, OM5k and
6k, OM5k 6k, OM5k CPL mediation layer when gaining
server Mediation
6500 any Manager for Only required for 6500 10.1 or later.
6k, OM5k
and CPL
server
Manager for any 6500 20001 TCP Manager for Secure For use by the Manager for 6k, OM5k and
6k, OM5k 6k, OM5k CPL mediation layer when gaining
server Mediation
6k, OM5k
and CPL
server
Manager for any 6500 20002 TCP SSH Secure Standard debug port for TL-1 terminal
6k, OM5k session (SSH Mediation).
and CPL
server
6k, OM5k
and CPL
server
Manager for any 6500 28888 TCP SSH Both Used for remote debug access to the
6k, OM5k 6500 by Ciena.
and CPL
server
6k, OM5k
and CPL
server
Manager for any 6500 20004 TCP SFTP Secure Used for SFTP SSH when the NE is the
6k, OM5k to SFTP client.
and CPL 20020
server
6k, OM5k
and CPL
server
—continued—


Mode
6500 any Manager for 50000 TCP / Manager for Secure Default source ports for all TCP and UDP
6k, OM5k to UDP 6k, OM5k flows from the GNE. This is configurable
and CPL 50511 and CPL using the ED-NAT command on the NE.
server Mediation This is also the port range used by the
GNE for requesting data connections for
any RNE/GNE originated FTP file
transfers.
These ports were introduced in
conjunction with Private IP support.
6500 (when single managed, enrolled as O-Shelf only)
OneControl any 6500 22 TCP SSH
Server
OneControl any 6500 22 TCP SSH
Client
6500 any SFTP 22 TCP SFTP B&R - secure option
Server
6500 any FTP Server 21 TCP FTP-Cmd B&R
FTP Server 20 6500 any TCP FTP-Data B&R
OneControl any 6500 8888 TCP Telnet Maintenance purpose
Client/
OneControl
Server
OneControl any 6500 1010 TCP Telnet Maintenance purpose
Client/
OneControl
Server
Note 1: For an external FTP client, using passive FTP mode, this port is not used.For an external FTP client, using active FTP
port on the external FTP server. Internal FTP client using passive FTP mode is not supported.backups / restores and Software
Delivery use active FTP, with the client on the NE.
backups / restores and Software Delivery use active FTP, with the client on the NE.

Ports for 6100/6200 NEs

Table 6-21 on page 6-45 lists the ports used when 6100/6200 NEs are
managed.
Table 6-21
6100/6200 NEs
Manager for any 6110/6130 1812 TCP Radius RADIUS requests are sent to this port by
6k, OM5k (included default, however the port number is
and CPL in 1024 to provisionable. Any change to the default value
server 5000 port) would require a corresponding change to
firewall settings.
6110/6130 any Manager for
6k, OM5k
and CPL
server
Manager for any NE 20 and 21 TCP FTP When the NE acts as the FTP client in active
6k, OM5k FTP mode, a port in this range will be used to
and CPL receive an FTP data connection from port 20
server on an external FTP server. TL1 upgrades,
backups and restores use active FTP, with the
NE any Manager for
6k, OM5k client on the NE.
and CPL
server
Manager for any NE 161 UDP SNMP Standard SNMP access port. Used by craft
6k, OM5k and 3rd-party SNMP-based managers.
and CPL
server
NE any Manager for
6k, OM5k
and CPL
server
Manager for any NE 162 UDP SNMPTRAP Optional
6k, OM5k Standard SNMP trap listening port used only
and CPL by 3rd-party SNMP based management
server stations.
Manager for any NE 873 TCP / NE rsync
6k, OM5k UDP
and CPL
server
(include NE
craft)
NE any Manager for
6k, OM5k
and CPL
server
—continued—


Manager for any NE 2023 TCP Telnet Used for technical support access.
6k, OM5k
and CPL
server
NE any Manager for
6k, OM5k
and CPL
server
Manager for any NE 2122 and TCP FTP When the NE acts as the FTP client in active
6k, OM5k 2123 FTP mode, a port in this range will be used to
and CPL (included receive an FTP data connection from port 20
server in 1024 to on an external FTP server. TL1 upgrades,
5000) backups and restores use active FTP, with the
NE any Manager for
6k, OM5k client on the NE.
and CPL
server
Manager for any NE 3021 TCP FTP ftp on dual processor system.
6k, OM5k Same as port 20 and 21
and CPL
server
NE any Manager for
6k, OM5k
and CPL
server
Manager for any NE 3023 TCP TELNET on dual processor system
6k, OM5k Same as port 2023.
and CPL
server
NE any Manager for
6k, OM5k
and CPL
server
Manager for any NE 10001 TCP Manager for For use by Manager for 6k, OM5k and CPL
6k, OM5k 6k, OM5k Mediation when gaining association with an
and CPL and CPL NE.
server Mediation
NE any Manager for
6k, OM5k
and CPL
server
—continued—


Manager for any NE 10002 TCP TELNET Standard debug port for TL1 terminal session.
6k, OM5k
and CPL
server
NE any Manager for
6k, OM5k
and CPL
server
6k, OM5k 6k, OM5k
and CPL and CPL
desktop server
Manager for any NE 10059 TCP TELNET config-db, alive reporting
6k, OM5k
and CPL
server
Manager for any NE 20080 TCP HTTP Used to launch craft.
6k, OM5k Used by Manager for 6k, OM5k and CPL
and CPL Desktop to establish connection to the
server Manager for 6k, OM5k and CPL Server.
Manager for any NE 20090 TCP TELNET debug port for an application to connect tcp
6k, OM5k port and SerialPort like rs232c
and CPL
server


7-1
Ordering information 7-
This chapter provides the information required to order the OneControl 5.0
software application, and covers the following topics:
• “Operating System and Database Ordering Guidelines” on page 2

• “Software download” on page 2
• “Ciena Software Key Code Manager” on page 3
• “OneControl 5.0 - How to order” on page 3
• “Order codes - Core functionality” on page 13
• “Order codes - NE Types” on page 18
• “Order codes - Packet services” on page 32
• “Order codes - Wavelength services” on page 35
• “Order codes - SONET/SDH Control Plane services” on page 38
• “Order codes - OTN services” on page 41
Attention: Information on ordering the Network Element (NE) Craft

interfaces is not included in this document. Refer to the appropriate NE
documentation for this information.
Attention: Information on ordering sub-EMS software, such as the Ethernet

Services Manager (ESM), is not included in this document. Refer to the ESM
Engineering Guide, 009-3216-022, for more information.

7-2 Ordering information
Operating System and Database Ordering Guidelines

To determine the operating system and database required for your
configuration, refer to Chapter 5, “Platform requirements”.
All operating systems must be ordered directly from the manufacturer.
When OneControl is used with a MySQL database, no separate database

software needs to be ordered or installed. MySQL database software is
embedded and delivered with the OneControl software.
When OneControl is used with an Oracle database, the Oracle database

software must be purchased and installed by the customer. To purchase,
please contact your Oracle support representative (in some select regions, it
can be purchased through Ciena; please contact your Ciena representative).
Software download
OneControl supports electronic delivery of software. Therefore, purchased
software can be downloaded from https://portal.ciena.com.
The option to purchase physical DVD media is still available. In both cases,
the software is in an encrypted format that must be decrypted using a license
file generated using the Ciena Software Key Code Manager.
To download software, perform the following steps:

1 As a registered user with a Ciena portal account, log into the Ciena
2 Once you are logged into this portal, click the Software tab.
3 From the drop down list of items/product select OneControl.
4 Download the software file(s) and readme file (if a readme file is present,
it will contain any instructions that might be required).
To purchase physical DVD media, refer to Table 7-1, “OneControl 5.0 order
codes - OneControl Software DVDs”.
Table 7-1
OneControl 5.0 order codes - OneControl Software DVDs
How many Code Description Details

to order
0 or 1 S11-1C-D500 ONECONTROL UMS- R5.0 SW Software DVDs. Software also

DVDs available from Ciena web portal.

Ciena Software Key Code Manager

The Ciena Software Key Code Manager is a web-based software licensing
solution used to obtain and manage licenses for OneControl applications in
addition to other Ciena software products.
For additional information about the Ciena Software Key Code Manager, see
the OneControl Installation Part 1, 450-3201-201.
OneControl 5.0 - How to order

Attention: The correct license(s) must be ordered to be able to generate the
Ciena key code license file(s) required for installation of the software.
This section details the network information you need to gather in order to
place your order. Read the following sub-sections to determine what
information needs to be gathered before ordering. Then follow the flowchart
to compile the list of codes that need to be ordered.
Determine the number of elements to be managed

To determine the number of elements the OneControl server (or server pair)
will manage, use the following formula:
Total elements =
(# GroupA shelves) + 0.4*(# GroupB shelves) + 0.1*(# GroupC shelves)
where
(# GroupA shelves) Any 6k, OM5k and CPL NE types
includes Any NE types formerly managed by ON-Center
ESM managed NE types: 5150, 5160, 5305,
5410, 8700
(# GroupB shelves) ESM managed NE types: 3911, 3916, 3920,
includes 3930, 3931, 3932, 3938vi, 3940, 3942, 3960,
5140, 5142, LE-311v
(# GroupC shelves) ESM managed NE types: 3902, 3903, 3904,
includes 3905
Note 1: For NE types where multiple shelves can be consolidated into one
NE for management purposes, each shelf must be counted separately as 1.
Note 2: For the Ethernet version of the 5410 NE managed via ESM, the
number of shelves is considered to be equal to the number of PSLM 40-4
line modules present.

Attention: The total elements calculated here are to be used strictly for
ordering purposes to determine the types of licenses necessary. This should
not be confused with the concept of NEUs (network element equivalent
units), which is used to determine network size for the purpose of server
sizing.
Determine the deployment size or bundle kit required

The OneControl order codes are categorized according to the size of the
managed network, allowing for a graduated pricing model.
Solutions supporting all NE types:

• Up to 25 elements - For small networks. The licenses in this category
allow management of up to 25 elements.
• Up to 50 elements - For small networks. The licenses in this category
• Up to 100 elements - For medium networks. The licenses in this category
• Maximum elements - For large networks. The licenses in this category
allow management of a maximum number of elements, up to the
maximum supported for a specific platform type.
Attention: For these four categories, should the network size grow beyond
the size initially planned, licenses can be purchased to transition to the next
category.
For small networks managing only optical or CES NE types, solution bundle
kits are available to simplify ordering.
• Bundle kits available:
— Up to 15 optical elements - with Wavelength Service Management
For small networks where only 6k, OM5k and CPL NE types will be
managed. The licenses in this category allow management of up to 25
devices, and include licenses for Wavelength Service Provisioning
and Wavelength Service Troubleshooting. This is an ideal bundle for
customers that are not adding NE types other than 6k, OM5k and CPL
devices or growing beyond 15 managed elements.
— Up to 25 optical elements - with Wavelength and Packet Service
Management
For small networks where only 6k, OM5k and CPL NE types will be
managed. The licenses in this category allow management of up to 25
devices, and include licenses for Wavelength Service Provisioning,

Wavelength Service Troubleshooting, Packet Service Provisioning

and Packet Service Troubleshooting. This is an ideal bundle for
customers that are not adding NE types other than 6k, OM5k and CPL
devices or growing beyond 25 managed elements.
— Up to 25 CES elements - with Packet Service Management
For small networks where only CES NE types will be managed. The
licenses included in this bundle allow management of up to 25 CES
devices, and include licenses for Packet Service Provisioning and
Packet Service Troubleshooting. This is an ideal bundle for customers
that are not adding NE types other than CES devices or growing
beyond 25 managed elements.
— Up to 25 optical or CES elements - with Wavelength and Packet
Service Management
For small networks where only CES, 6k, OM5k and CPL NE types will
be managed. The licenses in this category allow management of up to
25 devices, and include licenses for Wavelength Service Provisioning,
Wavelength Service Troubleshooting, Packet Service Provisioning
and Packet Service Troubleshooting. This is an ideal deployment
solution for customers that are not adding NE types other than CES,
6k, OM5k and CPL devices or growing beyond 25 managed elements.
Attention: For ESM managed NEs, the Ethernet Services Manager (ESM)
software must be ordered separately (and requires its own license separate
from OneControl licensing). The ESM license purchased is for a specified
number of NEs.
When used solely in conjunction with OneControl, ESM requires what is

referred to as the ESM Back End (BE) server license (OneControl does not
require what is referred to as the ESM Front End server license). Refer to the
ESM Engineering Guide, 009-3216-022, for more information.

Determine the NE types to be managed

Determine which NE types will be managed by OneControl:
• Will NEs managed by the sub-EMS ESM be enrolled?
• Which of these NE types will be enrolled:
— 5410, 5430, CoreDirector, CoreDirector CI, Corestream, 4200,
4200MC?
— 6k, OM5k and CPL?
• Will you be installing a co-resident server (refer to Figure 2-1 on page 2-2)
or a standalone server (refer to Figure 2-2 on page 2-3)?
Determine which optional features to enable
OneControl provides several optional value add features that can be enabled.
Determine which features will be enabled:
• Submarine repeater Scan
• Service Layer Manager (SLM)?
• Network and Service Viewer for L1 (NSV L1)
• Optical Service Provisioner (OSP)
• Software Upgrade Manager (SUM)
• North Bound Interfaces: TMF/UOG, MTOSI, EAI?
Determine service management functionality to enable

OneControl 5.0 has the following service management functionality that can
be enabled:
Packet Service Management (for ESM managed and 6500 NE types)
For Packet Service Management (PSM), do you require:
• Packet Service Provisioning?
• Packet Service Troubleshooting?
• How many packet service endpoints will be present in your managed
network?
Wavelength Service Management (for 6500 & CPL NE types)
For Wavelength Service Management (WSM), do you require:
• Wavelength Service Provisioning?
• WSP Advance Routing? (Implicit Routing)
• Wavelength Service Troubleshooting?
• Wavelength Service Restoration?
• How many wavelength services will be present in your managed network?

SONET/SDH Control Plane Service Management (for 5410, 5430, and 6500 NE
types)
For SONET/SDH Control Plane Service Management, do you require:
• SONET/SDH Control Plane Service Provisioning?
• Layer 1 Advanced Explicit Routing?
• How many SONET/SDH control plane services will be present in your
managed network?
OTN Service Management (for 5410, 5430, and 6500 NE types)
For OTN Service Management, do you require:
• OTN Service Provisioning (for 5410, 5430, and 6500 NE types)?
• Layer 1 Advanced Explicit Routing?
• How many OTN services will be present in your managed network?
Determine platform type and redundancy requirements

OneControl 5.0 server software can be deployed on platforms running Solaris
or Linux. Before continuing you must determine which platform type will be
used and whether a redundant platform will be used. For supported platform
types, see Chapter 5, “Platform requirements”. For engineering numbers
associated with supported platform types, see Chapter 4, “Network sizing and
engineering considerations”.
Although OneControl order codes are the same regardless of what operating
system type/release is used, note that the following functionality is only
available when deploying the OneControl server software on certain operating
system types/releases:
• External Alarm Interface (EAI) - Supported only on Solaris 10, 11.1 & 11.2,
and Linux 5.8, 5.9, 5.10, 5.11 & 6.6 (not supported on Linux 6.4 or 6.5).
• NSV L1 Federation - Supported only on Solaris 10, 11.1 & 11.2 (not
supported on Linux).
• CoreStream Management (CTM) - Supported only on Solaris 10 (not
supported on Solaris 11.1, 11.2 or Linux).
Also note that certain functionality is only available when deploying the
OneControl client software on certain operating system types/releases. See
“Client platform requirements” on page 5-10 for details.
Attention: When OneControl is deployed on a hardware platform where

virtualization is used, each LDOM (Solaris) or VM (Linux) is treated as a
separate system for the purposes of licensing and key code management.
For details on virtualization, see “Virtualized Deployments” on page 5-31 and
“Virtualization” on page 4-5.

Understanding the WSM changes in OneControl 5.0

OneControl 5.0 introduces a new paradigm for provisioning and management
of wavelength services, which has resulted in workflow changes. The
Wavelength Service Management (WSM) functionality now provides
management of line-to-line services. The management of client services
previously available in WSM is now provided by the Transport Switched
Connections (TSC) functionality. For details on WSM and TSC functionality,
refer to the OneControl Service Management Guide, 450-3201-302.
WSM functionality is enabled by the WSM licenses in Table 7-25, “OneControl

order codes - Wavelength Service Management”.
TSC functionality is enabled by the OTN licenses in Table 7-29, “OneControl

order codes - OTN Service Management”.
For new installs:

• Review the functionality to determine whether you need WSM and/or TSC
• Review the license and GR behavior in this section to determine whether
you need WSM licenses only, or also need OTN licenses
For upgrades:
• If you currently have both WSM and OTN licenses, no additional action is
required
• If you currently use WSM only for line-to-line service management
functionality within WSM (and not for client service management), no
additional action is required. After the upgrade you will continue to use
WSM as you do currently.
• If you currently use WSM for client service management, review the
license and GR behavior in this section in order to decide whether you will:
— Maintain only your current WSM licenses, and not enable TSC
— Maintain only your current WSM licenses, and enable TSC to use the
functionality available to you through WSM only licenses
— Order new OTN licenses, allowing you to use all TSC functionality
• The high level steps of your upgrade will consist of:
— Proceed with upgrade as in previous releases using the documented
upgrade procedures
— If you choose to enable TSC after the upgrade, use the documented
post install procedure for enabling TSC
— If you choose to add a new OTN license, use the documented post
install procedure for adding new licenses

License and GR behavior:

• If the WSM Provisioning license is present:
— Both Provision TSC and Manage TSC menu items will automatically
be enabled based on presence of WSP license
— Provisioning & visualization of supported OTN non-control plane
services possible
— Provisioning of OTN Control Plane services blocked
— If SLM functionality needed, license needs to be purchased separately
and will not be enabled based on presence of WSP license
— If provisioning on OTN Control Plane or Explicit Routing is needed,
license needs to be purchased separately
• If the WSM Troubleshooting license is present (with no WSP):
— Manage TSC menu items will automatically be enabled based on
presence of WST license
— If SLM functionality needed, license needs to be purchased separately
and will not be enabled based on presence of WSP license
• The maximum number of wavelength services allowed in WSM continues
to be bound by how many wavelength service volume licenses are
present/ordered
• The maximum number of services allowed in TSC is equal to the number
of OTN service volume licenses present/ordered, plus any left over
wavelength service volume licenses not being used by WSM.
— Example1: The customer has purchased 150 wavelength service
licenses and no OTN service licenses. If there are currently 50
wavelength services deployed, TSC will be allowed to manage up to
100 services before the maximum volume license threshold is
reached.
— Example2: The customer has purchased 200 wavelength service
licenses and 500 OTN service licenses. If there are currently 150
wavelength services deployed, TSC will be allowed to manage up to
550 services before the maximum volume license threshold is
reached.
• When TSC functionality is enabled, if Geographical Redundancy (GR) is
required, the Active/Backup mode must be used (if your current
deployment uses Peer-to-Peer GR mode, you will need to switch to
Active/Backup mode if you choose to enable TSC or to order a new OTN
license).

Follow flowchart to determine order codes

Once you have determined the number of elements, your deployment
category, and the optional functionality required, you are ready to select the
order codes that are required.
Start with the flowchart in Figure 7-1 on page 7-11. The flowchart covers initial
install and upgrade scenarios. For upgrades it is assumed that the same
feature functionality is desired after the upgrade. If additional new functionality
is desired after an upgrade (eg. add a new NE type) then step through the flow
chart again assuming an initial install, and reference only the items/tables for
any new features that need to be enabled.
Attention: The flowchart in Figure 7-1 on page 7-11 covers only initial
installs, and supported upgrade paths (see “Supported upgrades” on page
1-4). Additional licenses may be required if moving from an earlier
OneControl release from which a direct upgrade path is not supported.

Figure 7-1
Determine order codes
Order codes for

OneControl 5.0
Install Upgrade from 4.x

Install or
Upgrade?
Order core install licenses: Order core upgrade

- Up to 25, 50, 100, or maximum from 4.x licenses:
NEs: Table 7-2 - Up to 25, 50, 100, or
- Bundle kits:Table 7-3 max NEs: Table 7-5
- Bundle kits:Table 7-6
Existing NMS Yes

Order Transition
deployments
to OneControl
transitioning to
RTUs: Table 7-4
OneControl?
Increase NE max:
Yes
- Table 7-7 Adding NEs?
No
Order Mgmt Base NE RTUs: Add new Mgmt Base NE RTUs: No

- Table 7-8 - Table 7-8
Order NE types licenses: Add new NE types: Yes

Adding new
- Table 7-9 - Table 7-9 NE types?
No
Remote Manager Yes Order Remote Order Remote Yes Remote Manager
for 6k, OM5k and Manager for Manager for for 6k, OM5k and
CPL platforms
6k, OM5k and 6k, OM5k and CPL platforms to
needed? CPL: CPL upgrade: upgrade?
No No
Order optional feature licenses: Order optional feature upgrade licenses:

- EAI: Table 7-12 - EAI: Table 7-12
- Submarine Repeater Scan: Table 7-13 - Submarine Repeater Scan: Table 7-13
- SUM: Table 7-14 - SUM: Table 7-14
- SLM:Table 7-15 - SLM:Table 7-19
- NSV L1: Table 7-16 - NSV L1: Table 7-20
- OSP: Table 7-17 - OSP: Table 7-21
- TMF/UOG/MTOSI: Table 7-18 - TMF/UOG/MTOSI: Table 7-22
Continued on Figure 7-2

Figure 7-2
Determine order codes
Continued from Figure 7-1
PSM functionality
No Enable No
already enabled Add services
Packet Services
or elements
(PSM)?
Yes Yes
Order Volume Increment or

Order PSM licenses: additional elements licenses:
WSM functionality
No Enable already enabled No
Add services
Wavelength Services
or elements
(WSM)?
Yes Yes

Order WSM licenses: additional elements licenses:
SONET/SDH CP
functionality
Enable already enabled No
No Add services
SONET/SDH Ctrl
or elements
Plane (CP)?
Yes Yes

Order SONET/SDH CP licenses:
additional elements licenses:
- Table 7-27
- Table 7-28
OTN functionality
No Enable OTN already enabled Add services No
Services? or elements
Yes Yes
Order OTN services licenses:
additional elements licenses:
- Table 7-29
- Table 7-30
End

Order codes - Core functionality

This section contains the order codes for OneControl 5.0 core functionality.
Core functionality includes:
• Basic install licenses
• Transition RTU licenses
• Basic upgrade licenses
Attention: Before consulting these tables, for installs and upgrades, you
must refer to the ordering guidelines and flowcharts in “OneControl 5.0 - How
to order” on page 7-3. You will be directed to gather the required information
and follow a flowchart. The steps in the flowchart will direct you to the tables
that apply to your scenario.
The flowchart will direct you to use one of the following tables:
• Table 7-2, “OneControl 5.0 order codes - Initial install”
• Table 7-3, “OneControl 5.0 order codes - Initial install - Bundle kits”
• Table 7-4, “OneControl 5.0 order codes - Transition to OneControl RTUs”
• Table 7-5, “OneControl 5.0 order codes - Upgrade from 4.x”
• Table 7-6, “OneControl 5.0 order codes - Upgrade from 4.x - Bundle kits”
In addition, the following table lists order codes needed if the number of
elements managed by an existing OneControl deployment is increasing.
• Table 7-7, “OneControl order codes - Adding elements”
Table 7-2
OneControl 5.0 order codes - Initial install
How Code Code Description Details
many to (for main (for redundant All codes enable basic install.
order server) server)
1 S11-1C-500 S11-1C-RED ONECONTROL R5.0 Select the row that matches your
SERVER LICENSE MAX network size.
S11-1CC-500 S11-1CC-RED ONECONTROL R5.0 Order 1 of the code in the main server
SERVER LICENSE column for a standalone deployment (or
UP TO 100 ELEMENTS for the main server in a redundant pair).
S11-1CB-500 S11-1CB-RED ONECONTROL R5.0
If you have a redundant server setup,
SERVER LICENSE
order 1 of the code in the redundant
UP TO 50 ELEMENTS
server column for the redundant server.
S11-1CD-500 S11-1CD-RED ONECONTROL R5.0
SERVER LICENSE
UP TO 25 ELEMENTS

Table 7-3
OneControl 5.0 order codes - Initial install - Bundle kits
many (for main (for redundant All kits enable basic install.
to server) server) To order:
order
• Select the bundle that matches your
needs.
• Order 1 of the code in the main server
column for a standalone deployment (or
for the main server in a redundant pair).
• If you have a redundant server setup,
order 1 of the code in the redundant
server column for the redundant server.
1 S11-K15-500 S11-K15-500 ONECONTROL R5.0 KIT Bundle includes licenses:

UP TO 15 • Up to 15 optical devices (S11-1Cx-500,
OPTICAL ELEMENTS S11-OME-1)
WITH WSM
• Wavelength Prov & Trbl, with 50
wavelengths (S11-WPx-S210,
S11-WTx-S210, S11-WV-50)
S11-K25-500 S11-K25-RED ONECONTROL R5.0 KIT Bundle includes licenses:

UP TO 25 • Up to 25 optical devices
OPTICAL ELEMENTS (S11-1CD-500, S11-OME-1)
WITH WSM & PSM
wavelengths (S11-WPD-S210,
S11-WTD-S210, S11-WV-50)
• Packet Prov & Trbl, with 500 packet
service endpoints (S11-PPD-S200,
S11-PTD-S200, S11-PV-500)
S11-CES-500 S11-K25-RED ONECONTROL R5.0 KIT Bundle includes licenses:

UP TO 25 • Up to 25 CES devices (S11-1CD-500)
CES ELEMENTS
WITH PSM (Note 1)
S11-PTD-S200, S11-PV-500)
S11-K25C-500 S11-K25-RED ONECONTROL R5.0 KIT Bundle includes licenses:

UP TO 25 • Up to 25 optical devices
OPTICAL & CES ELEMENTS (S11-1CD-500, S11-OME-1)
WITH WSM & PSM (Note 1)
wavelengths (S11-WPD-S200,
S11-WTD-S200, S11-WV-50)
S11-PTD-S200, S11-PV-500)
Note 1: ESM has to be ordered separately.

Table 7-4
OneControl 5.0 order codes - Transition to OneControl RTUs

to order (Note 1)
0+ S11-ONC-MIG ON-Center Transition to Order 1 per ON-Center server migrating to

OneControl server RTU OneControl
S11-OMEA-MIG OMEA Transition to Order 1 per OMEA server migrating to

S11-OSR-MIG OSR Transition to Order 1 per server migrating to OneControl for

OneControl server RTU the following apps:
• NSV federation
• OMEA with L1 NSV, OSP and/or TMF
S11-ESM-MIG ESM Transition to Order 1 per ESM server migrating to

Note 1: These migration RTUs are used for administrative purposes and should be ordered whenever
a current ON-Center, OSR, or OMEA server is being migrated to OneControl.
Table 7-5
OneControl 5.0 order codes - Upgrade from 4.x

many (for main (for redundant Enables basic upgrade. (Note 1)
to server) server)
order
1 S11-1CU-500 - ONECONTROL R5.0 Select the row that matches your

UPGRADE LICENSE network size.
S11-1CCU-500 - ONECONTROL R5.0

UPGRADE LICENSE Order 1 of the code in the main
UP TO 100 ELEMENTS server column for a standalone
deployment (or for the main
S11-1CBU-500 - ONECONTROL R5.0 server in a redundant pair).
UPGRADE LICENSE
UP TO 50 ELEMENTS
If you have a redundant server
S11-1CDU-500 - ONECONTROL R5.0 setup currently at 4.x, the
UPGRADE LICENSE redundant server already has
UP TO 25 ELEMENTS the license for this functionality.
Do not order any new licenses
for the redundant server.
Note 1: Upgrade licenses are only valid when the release being upgraded from is an active OneControl
release, i.e. the release is still supported by Ciena and has not reached End Of Life (EOL) status.

Table 7-6
OneControl 5.0 order codes - Upgrade from 4.x - Bundle kits
many (for main (for redundant Enables basic upgrade (existing WSM or
to server) server) PSM functionality purchased on current
order release continues to be enabled). (Note
1)
To order:
• Select the bundle upgrade that matches
your currently deployed bundle kit.
• Order 1 of the code in the main server
column for a standalone deployment (or
for the main server in a redundant pair).
• If you have a redundant server setup
currently at 4.x, order 1 of the code in
the redundant server column for the
redundant server (only for the case in
the first row; for the other rows, the
redundant server already has the
license for this functionality).
1 S11-K15U-500 S11-K15U-500 ONECONTROL R5.0 Intended for customers who purchased:

UPGRADE KIT • S11-K15-4x0 (OneControl R4.x Kit for
UP TO 15 15 optical elements with WSM), and
OPTICAL ELEMENTS who are upgrading from OneControl 4.x
WITH WSM to 5.0.
S11-K25U-500 - ONECONTROL R5.0 Intended for customers who purchased:

UPGRADE KIT • S11-K25-4x0 (OneControl R4.x Kit for
UP TO 25 25 optical elements with WSM & PSM),
OPTICAL ELEMENTS and who are upgrading from
WITH WSM & PSM OneControl 4.x to 5.0.
S11-CESU-500 - ONECONTROL R5.0 Intended for customers who purchased:

UPGRADE KIT • S11-CES-4x0 (OneControl R4.x Kit for
UP TO 25 25 CES elements with PSM), and who
CES ELEMENTS are upgrading from OneControl 4.x to
WITH PSM (Note 2) 5.0.
S11-K25U-500 - ONECONTROL R5.0 Intended for customers who purchased:

UPGRADE KIT • S11-K25C-4x0 (OneControl R4.x Kit for
UP TO 25 25 optical & CES elements with WSM &
OPTICAL & CES PSM), and who are upgrading from
ELEMENTS OneControl 4.x to 5.0.
WITH WSM & PSM (Note 2)
Note 1: Upgrade licenses are only valid when the release being upgraded from is an active OneControl release,
i.e. the release is still supported by Ciena and has not reached End Of Life (EOL) status.
Note 2: ESM has to be ordered/upgraded separately.

Table 7-7
OneControl order codes - Adding elements
many (for main (for Order to increase the number of
to server) redundant elements currently licensed to support
order server) OneControl core functionality
0 or 1 S11-1CI-50 - ONECONTROL To go from:

FROM 25 TO 50 ELEMENTS • 25 to 50 - S11-1CI-50
• 25 to 100 - S11-1CI-50, S11-1CI-100
0 or 1 S11-1CI-100 - ONECONTROL
• 25 to Max - order all 3 licenses
FROM 50 TO 100 ELEMENTS
• 50 to 100 - S11-1CI-100
0 or 1 S11-1CI-00 - ONECONTROL • 50 to Max - S11-1CI-100, S11-1CI-00
FROM 100 TO MAX ELEMENTS • 100 to Max - S11-1CI-00
If you have a redundant server setup,

licenses for this increase only need to
be ordered once, for the main server in
the pair. Do not order any licenses for
the redundant server.

Order codes - NE Types

This section contains the order codes for OneControl 5.0 NE specific
functionality. This includes:
• Licenses for management of specific NE types (6k, OM5k, CPL, 5430,
5410, CoreDirector, Corestream, 4200) & the associated management
base NE RTUs
The flowchart will direct you to use two of the following tables depending on
install or upgrade:
• Table 7-8, “OneControl 5.0 order codes - Base NE RTUs”
• Table 7-9, “OneControl 5.0 order codes - NE types - Installs”
• Table 7-10, “OneControl 5.0 order codes - Remote Manager for 6k, OM5k
and CPL - Installs”
• Table 7-11, “OneControl 5.0 order codes - Remote Manager for 6k, OM5k
and CPL - Upgrades”

Table 7-8
OneControl 5.0 order codes - Base NE RTUs
to order (Note 1)
0 or more 009-2002-377 CoreDirector OneControl Base NE RTU Order 1 Base NE RTU

for every NE/card in the
009-2002-378 CoreDirector CI Base NE RTU network that will be
managed by
009-2002-379 CoreStream/Sentry Base NE RTU
OneControl.
B-990-0014-004 4200 Classic & RS Base NE RTU (Note 2)
S11-MCNCS-RTU 4200 MC Base NE RTU
S11-5430-OCRTU 5430 (Optical) Base NE RTU
S11-5410-OCRTU 5410 (Optical) Base NE RTU (Note 3)

Base NE RTUs are
purchased once for a
S11-OCS40G-83 Flex 40G Base NE RTU
particular NE, even when
S11-6500-OCRTU 6500 ON-CENTER Base NE RTU managed by a redundant
OneControl server pair.
NTNM70FE 6500 Base NE RTU for 2-SLOT Base NE RTUs are also
valid for use with future
NTNM70FA 6500 Base NE RTU for 7-SLOT OneControl releases.
NTNM70EJ 6500 Base NE RTU for 14-SLOT
NTNM70ER 6500 Base NE RTU for 32-SLOT
NTNM70ET 6500 Base NE RTU for WSS card
NTNM70EW 6500 RTU, UMS base per 40G OCLD card
NTNM70FB 6500 RTU, UMS base for 100G OCLD card
NTNM70FH 6500 RTU, UMS base for 200G OCLD card
NTNM70EB CPL Base NE RTU for DOSC or UOSC
NTNM70EC CPL Base NE RTU for GMD or OMEBB
NTNM70ED CPL Base NE RTU for WSS card
NTNM70EH OM5100 Base NE RTU
NTNM70EE OM5200 Base NE RTU
NTNM70EY OM565 Base NE RTU
NTNM70EF 6110 Base NE RTU
NTNM70EN 6130 Base NE RTU
NTNM70EG 6150 Base NE RTU
NTNM70RY 6200 Base NE RTU
Note 1: Base NE RTUs for CES devices (managed via ESM), are not included in this table. Refer to the ESM Engineering Guide,
009-3216-022, for more information on ordering NE RTUs for these devices.
Note 2: Applicable to 4200 classic and RS chassis. Order 1 per chassis (if multiple chassis in a TID, order 1 per physical chassis).
Note 3: This RTU is for the Optical/Switching version of the NE (not the Ethernet version managed via ESM).

Table 7-9
OneControl 5.0 order codes - NE types - Installs
How Code Description Details

many (for main server) (Note 1, Note 2)
to
order
0 or 1 S11-OME-1 ONECONTROL LICENSE FOR 6k, Order 1 if co-resident

OM5k & CPL (Note 3) Manager for 6k, OM5k and
CPL required.
0 or 1 S11-1CSM-1 ONECONTROL LICENSE FOR 5400 & Order 1 if managing 54x0/CD

COREDIRECTOR on this OneControl server.
0 or 1 S11-1NCS-1 ONECONTROL LICENSE FOR 4200 Order 1 if managing 4200 on

(Note 4) this OneControl server.
0 or 1 S11-1CTM-1 ONECONTROL LICENSE FOR Order if managing

CORESTREAM (Note 5, Note 6, Note 7) CoreStream on this
OneControl server.
0 or 1 S11-CTMD-TRANS CORE TRANSPORT MANAGER Order 1 if already using CTM

DSET transfer license (Note 7) but now moving to different
server.
Note 1: Do not order these licenses for a redundant server. If you have a redundant server setup,
licenses for this functionality only need to be ordered once, for the main server in the pair.
Note 2: For upgrades: If you have a server currently at 4.x with one of these NE type licenses, the
license remains valid for OneControl 5.0. Do not order the license again.
Note 3: Refer to Figure 2-1‚ Figure 2-2‚ and Figure 2-3 for deployment options.
Note 4: When ordering the 4200 (NCS) functionality for the first time you must order S11-1NCS-1.
Previous releases of OneControl also required an additional third-party license file to be ordered
(ipiNCS.lic). This is no longer required (the additional third-party license file is now automatically
included in the OneControl software).
Note 5: CoreStream (CTM) functionality available only when deploying on platforms running Solaris 10.
Note 6: When ordering the CoreStream (CTM) functionality for the first time for a fresh install, you must
order S11-1CTM-1. Additional third-party license files are also required to install CTM (license,
license.dat). These software license files are separate from Ciena’s Software Keycode Manager
functionality. Contact your Ciena account representative to obtain the required license files.
Note 7: If CoreStream (CTM) functionality is already installed in a current ON-Center deployment that
is being moved to OneControl, you must still order S11-1CTM-1. If CTM will be staying on the same
server when it is re-installed as part of the OneControl deployment, the CTM third-party license files
(license, license.dat) should be saved from the current deployment and re-used. If CTM is being moved
to a different server as part of the OneControl deployment, then S11-CTMD-TRANS must also be
ordered to have the third-party license files transferred to this new server (the current files will be
transferred and regenerated for use on the new server).

Table 7-10
OneControl 5.0 order codes - Remote Manager for 6k, OM5k and CPL - Installs

many (for main (for redundant (Note 1)
to server) server)
order
0 or 1 S11-OMER-500 S11-OMER-RED ONECONTROL R5.0 Order 1 if server will be a

REMOTE SERVER Remote Manager for 6k,
LICENSE FOR 6k, OM5k & OM5k and CPL.
CPL If you have a redundant
server setup, order 1 of the
code in the redundant
server column for the
redundant server.
Note 1: Refer to Figure 2-1‚ Figure 2-2‚ and Figure 2-3 for deployment options. Remote Manager for
6k, OM5k and CPL servers are deployed when the number of NEUs/NEs exceeds the maximum
supported by the Manager for 6k, OM5k and CPL instance that is co-resident with OneControl.
Table 7-11
OneControl 5.0 order codes - Remote Manager for 6k, OM5k and CPL - Upgrades

many (for main server) (for redundant (Note 1)
to server)
order
0 or 1 S11-OMERU-500 - ONECONTROL R5.0 Order 1 if server will be a

REMOTE SERVER Remote Manager for 6k,
LICENSE FOR 6k, OM5k OM5k and CPL.
& CPL If you have a redundant
server setup currently at
4.x, the redundant server
already has the license for
this functionality. Do not
order any new licenses for
the redundant server.
Note 1: Refer to Figure 2-1‚ Figure 2-2‚ and Figure 2-3 for deployment options. Remote Manager for
6k, OM5k and CPL servers are deployed when the number of NEUs/NEs exceeds the maximum
supported by the Manager for 6k, OM5k and CPL instance that is co-resident with OneControl.

Order codes - Optional components

This section contains the order codes for OneControl 5.0 optional
components. This includes:
• External Alarm Interface (EAI) licenses
• Submarine Repeater Scan licenses
• Software Upgrade Manager (SUM) licenses and the SUM NE RTUs
• Service Layer Manager (SLM) licenses and the SLM NE RTUs
• Network and Service Viewer for L1 (NSV L1) and the NSV L1 NE RTUs
• Optical Service Provisioner (OSP) and the OSP NE RTUs
• North Bound Interfaces: TMF/UOG/MTOSI licenses and NBI NE RTUs
The flowchart will direct you to use two of the following tables depending on
install or upgrade:
• Table 7-12, “OneControl order codes - EAI - Installs & Upgrades”
• Table 7-13, “OneControl order codes - Submarine Repeater Scan - Installs
& Upgrades”
• Table 7-14, “OneControl 5.0 order codes - SUM - Installs & Upgrades”
• Table 7-15, “OneControl 5.0 order codes - SLM - Installs”
• Table 7-16, “OneControl 5.0 order codes - NSV L1 - Installs”
• Table 7-17, “OneControl 5.0 order codes - OSP - Installs”
• Table 7-18, “OneControl 5.0 order codes - NBI (TMF/UOG/MTOSI)
functionality - Installs”
• Table 7-19, “OneControl 5.0 order codes - SLM - Upgrades”
• Table 7-20, “OneControl 5.0 order codes - NSV L1 - Upgrades”
• Table 7-21, “OneControl 5.0 order codes - OSP - Upgrades”
• Table 7-22, “OneControl 5.0 order codes - NBI - TMF/UOG/MTOSI -
Upgrades”

Table 7-12
OneControl order codes - EAI - Installs & Upgrades

many to (for main (Note 1)
order server)
0 or more S11-1C-EAI ONECONTROL EAI For installs: If EAI will be used, order 1 per
SERVER LICENSE FOR OneControl server and 1 per Remote
6k, OM5k and CPL Manager for 6k, OM5k and CPL server.
For upgrades: If you have a server currently

at 4.x with an EAI license, the license
remains valid for OneControl 5.0. Do not
order the license again.
Note: EAI functionality available only when

deploying on Solaris 10, 11.1 & 11.2, and
Linux 5.8, 5.9, 5.10, 5.11 & 6.6 platforms
(not supported on Linux 6.4 or 6.5).
Table 7-13
OneControl order codes - Submarine Repeater Scan - Installs & Upgrades

to order (for main (Note 1)
server)
0 or more S11-SUB-SCAN ONECONTROL For installs: Order 1 if SRS will be used

SUBMARINE REPEATER on this OneControl server.
SCAN LICENSE
For upgrades: If you have a server
currently at 4.x with an SRS license, the
license remains valid for OneControl 5.0.
Do not order the license again.

Table 7-14
OneControl 5.0 order codes - SUM - Installs & Upgrades
to order (for main server) (Note 1)
0 or 1 S11-6KSUM-500 ONECONTROL R5.0 For installs & upgrades: Order 1 per OneControl
LICENSE FOR server and 1 per OneControl remote server where
SOFTWARE UPGRADE a license for 6k, OM5k and CPL is present.
MANAGER FOR 6K
For the SUM feature, the same order code is used
for both installs and upgrades.
SUM NE RTUs
0 or more S11-6KSUMPS-500 6500 - SUM NE RTU per For installs & upgrades: If SUM will be used, order
shelf 1 SUM NE RTU for every shelf in the network.
For the SUM feature, NE RTUs must be purchased

every OneControl release, for every shelf in the
network on which this feature will be used. A SUM
NE RTU purchased for a particular shelf in
OneControl 4.2, is not valid for use in Onecontrol
5.0.
Note 1: Do not order these licenses for a redundant server. If you have a redundant server setup, licenses for this
functionality only need to be ordered once, for the main server in the pair.
Table 7-15
OneControl 5.0 order codes - SLM - Installs
0 or 1 S11-1SLM-500 ONECONTROL R5.0 LICENSE FOR Order 1 if SLM will be used on this
SERVICE LAYER MANAGER OneControl server.
SLM NE RTUs
0 or more 009-2002-388 CoreDirector - SLM NE RTU If SLM will be used, order 1 SLM
NE RTU for every NE in the
009-2002-389 CoreDirector CI - SLM NE RTU network.
009-2002-390 CoreStream/Sentry - SLM NE RTU
For the SLM feature, NE RTUs are
B-990-0016-001 4200 - SLM NE RTU purchased once for a particular
NE, even when managed by a
S11-SLM-42MC 4200 MC - SLM NE RTU
redundant OneControl server pair.
S11-5430-SLMRTU 5430 - SLM NE RTU SLM NE RTUs are also valid for
use with future OneControl
S11-5410-SLMRTU 5410 - SLM NE RTU releases.
S11-6500-SLMRTU 6500 - SLM NE RTU

Table 7-16
OneControl 5.0 order codes - NSV L1 - Installs

to server) server)
order
0 or 1 S11-NSV-500 - ONECONTROL R5.0 NSV L1 If NSV L1 will be used,

LICENSE FOR 6k, OM5k and order 1 per OneControl
CPL server and 1 per Remote
and CPL server.
0 or 1 S11-NSVF-500 S11-NSVF-500R ONECONTROL R5.0 NSV L1 Order 1 license per

FEDERATION LICENSE standalone server.
0 or 1 S11-NSVF-D500 - ONECONTROL R5.0 NSV L1 Order 1 software DVD kit

FEDERATION SW DVD KIT (only if not also ordering
OSP for HP DVD kit
S11-OSP-D500).
Only for existing AP
deployments.
NSV L1 NE RTUs
0 or NTNM70RU - 6500 - NSV NE RTU for 2 slot If NSV L1 will be used,

more order 1 NSV Element
NTNM70RT - 6500 - NSV NE RTU for 7 slot RTU for every NE/shelf in
NTNM70RM - 6500 - NSV NE RTU for 14 slot the network.
NTNM70RM - 6500 - NSV NE RTU for 32 slot

For the NSV feature, NE
NTNM70RG - 5100 - NSV NE RTU RTUs are purchased
once for a particular NE,
NTNM70RS - 565 - NSV NE RTU even when managed by a
NTNM70RK - 5200 - NSV NE RTU redundant OneControl
server pair. NSV NE
NTNM70RE - 6110 - NSV NE RTU RTUs are also valid for
use with future
NTNM70RF - 6130 - NSV NE RTU OneControl releases.
NTNM70RL - 6150 - NSV NE RTU

Table 7-17
OneControl 5.0 order codes - OSP - Installs

0 or 1 S11-OSP-500 ONECONTROL R5.0 OSP If OSP will be used, order 1 per

LICENSE FOR 6k, OM5k and OneControl server and 1 per
CPL Remote Manager for 6k, OM5k and
CPL server.
0 or 1 S11-OSP-D500 ONECONTROL R5.0 OSP If OSP will be used, order 1 per HP

APPLICATION KIT FOR HP server where the application is
installed. Only for existing AP
deployments.
OSP NE RTUs
0 or more NTNM67LR 6500 - OSP NE RTU for 2 slot If OSP will be used, order 1 OSP
NE RTU for every NE/shelf in the
NTNM67LQ 6500 - OSP NE RTU for 7 slot network.
NTNM67LH 6500 - OSP NE RTU for 14 slot
NTNM67LJ 6500 - OSP NE RTU for 32 slot

For the OSP feature, NE RTUs are
NTNM67LC 6110 - OSP NE RTU purchased once for a particular NE,
even when managed by a
NTNM67LD 6130 - OSP NE RTU redundant OneControl server pair.
NTNM67LF 6150 - OSP NE RTU OSP NE RTUs are also valid for use
with future OneControl releases.
NTNM67LW 6200 - OSP NE RTU

Table 7-18
OneControl 5.0 order codes - NBI (TMF/UOG/MTOSI) functionality - Installs

many to (for main server) (Note 1)
order
0 or 1 S11-TMF-500 ONECONTROL R5.0 TMF-UOG LICENSE This license enables the

(Note 2, Note 3) installation of either the
TMF or UOG components
(or both) as north bound
interface for OSS
integration.
0 or 1 S11-MTO-500 ONECONTROL R5.0 LICENSE FOR MTOSI Order 1 per OneControl

(Note 4) server if required.
NBI NE RTUs
0 or S11-NBI-RTU ONECONTROL GATEWAY-NE RTU If TMF, UOG or MTOSI will

more be used, order 1 NBI NE
RTU for every NE/shelf in
the network.
For the NBI features, NE

RTUs are purchased once
for a particular NE, even
when managed by a
redundant OneControl
server pair. NBI NE RTUs
are also valid for use with
future OneControl
releases.
Note 2: If only the TMF component will be used, order 1 per OneControl server with a Manager for 6k,
OM5k and CPL component, and 1 per Remote Manager for 6k, OM5k and CPL. If only the UOG
component will be used, order 1 per OneControl server.
Note 3: When ordering the UOG functionality for the first time, you must order S11-TMF-420. Previous
releases of OneControl also required an additional third-party license file to be ordered (<number>.lic).
This is no longer required (the additional third-party license file is now automatically included in the
OneControl software).
Note 4: If the MTOSI interface will be used to manage OTN services, one of the following licenses must
also be ordered and present on the OneControl server:
• OneControl OTN Provisioning (S11-OPx-300)
• OneControl SONET/SDH Control Plane Provisioning (S11-SPx-S210)

Table 7-19
OneControl 5.0 order codes - SLM - Upgrades

0 or 1 S11-1SLMU-500 ONECONTROL - R5.0 Order 1 of each type of

UPGRADE LICENSE FOR functionality that will be used on
SERVICE LAYER MANAGER this OneControl server.
SLM NE RTUs
0 or more See Table 7-15. See Table 7-15. There is a For upgrades: Only order this code
separate order code for each NE if new NEs have been added to the
type. network for which SLM will be used
(and this RTU has not previously
been purchased for this NE). Order
1 SLM NE RTU for every new NE
in the network.
For the SLM feature, NE RTUs are

purchased once for a particular
NE, even when managed by a
redundant OneControl server pair.
SLM NE RTUs are also valid for
releases.

Table 7-20
OneControl 5.0 order codes - NSV L1 - Upgrades

to server) server)
order
0 or 1 S11-NSVU-500 - ONECONTROL R5.0 NSV Order 1 per OneControl

L1 UPGRADE LICENSE server and 1 per
FOR 6k, OM5k and CPL OneControl remote server
where a license for 6k,
OM5k and CPL is present.
0 or 1 S11-NSVFU-500 S11-NSVFU-500R ONECONTROL R5.0 NSV Order 1 license per

L1 FEDERATION standalone server.
UPGRADE LICENSE Order 1 software DVD kit
0 or 1 S11-NSVF-D500 - ONECONTROL R5.0 NSV (only if not also ordering
L1 FEDERATION SW DVD OSP for HP DVD kit
KIT S11-OSP-D500).
Only for existing AP
deployments.
NSV L1 NE RTUs
0 or See Table 7-16. - See Table 7-16. There is a For upgrades: Only order
more separate order code for this code if new
each NE type. NEs/shelves have been
added to the network for
which NSV will be used
(and this RTU has not
previously been
purchased for this
NE/shelf). Order 1 NSV
NE RTU for every new
NE/shelf in the network.
For the NSV feature, NE

RTUs are purchased
once for a particular
NE/shelf, even when
managed by a redundant
OneControl server pair.
NSV NE RTUs are also
valid for use with future
OneControl releases.

Table 7-21
OneControl 5.0 order codes - OSP - Upgrades

0 or 1 S11-OSPU-500 ONECONTROL R5.0 OSP Order 1 per OneControl server and

UPGRADE LICENSE FOR 6k, 1 per OneControl remote server
OM5k and CPL where a license for 6k, OM5k and
CPL is present.
0 or 1 S11-OSPU-D500 ONECONTROL R5.0 OSP Order 1 per HP server where the

UPGRADE APPLICATION KIT application is installed. Only for
FOR HP existing AP deployments.
OSP NE RTUs
0 or more See Table 7-17. See Table 7-17. There is a For upgrades: Only order this code
separate order code for each NE if new NEs/shelves have been
type. added to the network for which
OSP will be used (and this RTU
has not previously been purchased
for this NE/shelf). Order 1 OSP NE
RTU for every new NE/shelf in the
network.
For the OSP feature, NE RTUs are

purchased once for a particular
NE/shelf, even when managed by
a redundant OneControl server
pair. OSP NE RTUs are also valid
for use with future OneControl
releases.

Table 7-22
OneControl 5.0 order codes - NBI - TMF/UOG/MTOSI - Upgrades

0 or 1 S11-TMFU-500 ONECONTROL R5.0 TMF-UOG Order 1 per OneControl

UPGRADE LICENSE (Note 2) server if required.
0 or 1 S11-MTOU-500 ONECONTROL R5.0 UPGRADE Order 1 per OneControl

LICENSE FOR MTOSI server if required.
NBI NE RTUs
0 or more S11-NBI-RTU ONECONTROL GATEWAY-NE RTU For upgrades: Only order this
code if new NEs/shelves have
been added to the network for
which TMF, UOG or MTOSI
will be used (and this RTU
has not previously been
purchased for this NE/shelf).
Order 1 NBI NE RTU for
every new NE/shelf in the
network.
For the NBI features, NE

RTUs are purchased once for
a particular NE, even when
managed by a redundant
OneControl server pair. NBI
NE RTUs are also valid for
releases.
Note 2: Enables upgrade of purchased functionality on current OneControl release. To enable any new
TMF/ UOG/MTOSI features (beyond those present at the current OneControl release), please contact
Ciena.

Order codes - Packet services

This section contains the order codes for OneControl packet service
management functionality. This includes:
• Packet provisioning licenses
• Packet troubleshooting licenses
• Volume of packet service endpoints licenses
The flowchart will direct you to the following table if packet service
management functionality is being added to the deployment:
• Table 7-23, “OneControl order codes - Packet Service Management”
elements/packet service endpoints managed by an existing OneControl
deployment is increasing.
• Table 7-24, “OneControl order codes - Packet Service Management -
Adding elements or service endpoints”

Table 7-23
OneControl order codes - Packet Service Management

order server)
0 or 1 S11-PP-S200 PACKET PROVISIONING Order 1 of these, if this

SERVER LICENSE, MAX ELEMENTS functionality will be used on
this OneControl server.
S11-PPC-S200 PACKET PROVISIONING
Order the code that
UP TO 100 ELEMENTS
matches your network size.
S11-PPB-S200 PACKET PROVISIONING
UP TO 50 ELEMENTS
S11-PPD-S200 PACKET PROVISIONING

UP TO 25 ELEMENTS
0 or 1 S11-PT-S200 PACKET TROUBLESHOOTING Order 1 of these, if this

SERVER LICENSE, MAX ELEMENTS functionality will be used on
this OneControl server.
S11-PTC-S200 PACKET TROUBLESHOOTING
Order the code that
UP TO 100 ELEMENTS
matches your network size.
S11-PTB-S200 PACKET TROUBLESHOOTING
UP TO 50 ELEMENTS
S11-PTD-S200 PACKET TROUBLESHOOTING

UP TO 25 ELEMENTS
1 S11-PV-500 500 PACKET SERVICE ENDPOINTS Order 1. This base volume

VOLUME BASE of service license enables
the OneControl server to
manage up to 500 packet
service endpoints. (Note 2)
0 or more S11-PI-500 500 PACKET SERVICE ENDPOINTS Only order if more than 500
VOLUME INCREMENT packet service endpoints
will be managed by this
OneControl server.
This volume increment
license allows you to add
blocks of 500 packet
service endpoints. Order as
many as needed. (Note 2)
Note 2: Examples: (a) To manage 500 packet service endpoints, order 1 of S11-PV-500, (b) To manage
1,500 packet service endpoints, order 1 of S11-PV-500 and 2 of S11-PI-500.

Table 7-24
OneControl order codes - Packet Service Management - Adding elements or service endpoints

many (for main Order to increase the number of elements
to server) currently licensed to support each feature or
order to increase the number of services endpoints.
(Note 1)
0 or 1 S11-PPI-50 PACKET PROVISIONING For Packet Provisioning, to go from:

FROM 25 TO 50 ELEMENTS • 25 to 50 - S11-PPI-50
• 25 to 100 - S11-PPI-50, S11-PPI-100
0 or 1 S11-PPI-100 PACKET PROVISIONING • 25 to Maximum - Order all 3 licenses
FROM 50 TO 100 ELEMENTS • 50 to 100 - S11-PPI-100
0 or 1 S11-PPI-00 PACKET PROVISIONING • 50 to Maximum - S11-PPI-100, S11-PPI-00
FROM 100 TO MAXIMUM • 100 to Maximum - S11-PPI-00
0 or 1 S11-PTI-50 PACKET TROUBLESHOOTING For Packet Troubleshooting, to go from:

FROM 25 TO 50 ELEMENTS • 25 to 50 - S11-PTI-50
• 25 to 100 - S11-PTI-50, S11-PTI-100
0 or 1 S11-PTI-100 PACKET TROUBLESHOOTING • 25 to Maximum - Order all 3 licenses
FROM 50 TO 100 ELEMENTS • 50 to 100 - S11-PTI-100
0 or 1 S11-PTI-00 PACKET TROUBLESHOOTING • 50 to Maximum - S11-PTI-100, S11-PTI-00

FROM 100 TO MAXIMUM • 100 to Maximum - S11-PTI-00
0 or S11-PI-500 500 PACKET SERVICE This volume increment license allows you to
more ENDPOINTS add blocks of 500 packet service endpoints.
VOLUME INCREMENT Order as many as needed. (Note 2)
Note 2: Examples: (a) If this OneControl server is currently licensed to support up to 1,500 packet
service endpoints, to increase this to 2,500, then order 2 of S11-PI-500.

Order codes - Wavelength services

This section contains the order codes for OneControl wavelength service
• Wavelength provisioning licenses
• Wavelength provisioning advanced routing licenses (Implicit Routing)
• Wavelength troubleshooting licenses
• Wavelength restoration licenses
• Volume of wavelength services licenses
The flowchart will direct you to the following table if wavelength service
management functionality is being added to the deployment:
• Table 7-25, “OneControl order codes - Wavelength Service Management”
elements/wavelength services managed by an existing OneControl
• Table 7-26, “OneControl order codes - Wavelength Service Management
- Adding elements or services”

Table 7-25
OneControl order codes - Wavelength Service Management
many to (for main server) (Note 1)
order
0 or 1 S11-WP-S210 WAVELENGTH SERVICE PROVISIONING, Order 1 of these, if this functionality will be

SERVER LICENSE, MAX ELEMENTS used on this OneControl server.
Order the code that matches your network
S11-WPC-S210 WSP, UP TO 100 ELEMENTS size.
S11-WPB-S210 WSP, UP TO 50 ELEMENTS
S11-WPD-S210 WSP, UP TO 25 ELEMENTS
0 or 1 S11-WPA-S210 WSP ADVANCE ROUTING Order 1 of these, if this functionality will be

S11-WPAC-S210 WSP AR, UP TO 100 ELEMENTS
size.
S11-WPAB-S210 WSP AR, UP TO 50 ELEMENTS
S11-WPAD-S210 WSP AR, UP TO 25 ELEMENTS
0 or 1 S11-WT-S210 WAVELENGTH SERVICE TROUBLESHOOTING Order 1 of these, if this functionality will be

S11-WTC-S210 WST, UP TO 100 ELEMENTS
size.
S11-WTB-S210 WST, UP TO 50 ELEMENTS
S11-WTD-S210 WST, UP TO 25 ELEMENTS
0 or 1 S11-WR-S210 WAVELENGTH SERVICE RESTORATION Order 1 of these, if this functionality will be

S11-WRC-S210 WSR, UP TO 100 ELEMENTS
size.
S11-WRB-S210 WSR, UP TO 50 ELEMENTS
S11-WRD-S210 WSR, UP TO 25 ELEMENTS
1 or more S11-WV-50 50 WAVELENGTH SERVICES Order 1. This base volume of service license
VOLUME BASE enables the OneControl server to manage up
to 50 wavelength services. (Note 2)
0 or more S11-WI-50 50 WAVELENGTH SERVICES Only order if more than 50 wavelength

VOLUME INCREMENT services will be managed by this OneControl
server.
This volume increment license allows you to
add blocks of 50 wavelength services. Order
as many as needed. (Note 2)
Note 1: Do not order these licenses for a redundant server. If you have a redundant server setup, licenses for this functionality
only need to be ordered once, for the main server in the pair.
Note 2: Examples: (a) To manage 50 wavelength services, order 1 of S11-WV-50, (b) To manage 150 wavelength services, order
1 of S11-WV-50 and 2 of S11-WI-50.

Table 7-26
OneControl order codes - Wavelength Service Management - Adding elements or services
many to (for main server) Order to increase the number of elements
order currently licensed to support each feature or to
increase the number of services. (Note 1)
0 or 1 S11-WPI-50 WAVELENGTH SERVICE For WSP to go from:

PROVISIONING • 25 to 50 - S11-WPI-50
FROM 25 TO 50 ELEMENTS • 25 to 100 -S11-WPI-50, S11-WPI-100
• 25 to Max - Order all 3 licenses
0 or 1 S11-WPI-100 WSP
• 50 to 100 - S11-WPI-100
• 50 to 100 - S11-WPI-100
0 or 1 S11-WPI-00 WSP • 50 to Max-S11-WPI-100, S11-WPI-00
FROM 100 TO MAXIMUM • 100 to Max - S11-WPI-00
0 or 1 S11-WPAI-50 WSP ADVANCE ROUTING For WSP Advance Routing to go from:

FROM 25 TO 50 ELEMENTS • 25 to 50-S11-WPAI-50
• 25 to 100-S11-WPAI-50, S11-WPAI-100
0 or 1 S11-WPAI-100 WSP AR
• 50 to 100 - S11-WPAI-100
0 or 1 S11-WPAI-00 WSP AR • 50 to Max - S11-WPAI-100, S11-WPAI-00
FROM 100 TO MAXIMUM • 100 to Max - S11-WPAI-00
0 or 1 S11-WTI-50 WAVELENGTH SERVICE For WST to go from:

TROUBLESHOOTING • 25 to 50-S11-WTI-50
FROM 25 TO 50 ELEMENTS • 25 to 100-S11-WTI-50, S11-WTI-100
0 or 1 S11-WTI-100 WST
• 50 to 100 - S11-WTI-100
• 50 to Max - S11-WTI-100, S11-WTI-00
0 or 1 S11-WTI-00 WST • 100 to Max - S11-WTI-00
FROM 100 TO MAXIMUM
0 or 1 S11-WRI-50 WAVELENGTH SERVICE For WSR to go from:

RESTORATION • 25 to 50-S11-WRI-50
FROM 25 TO 50 ELEMENTS • 25 to 100-S11-WRI-50, S11-WRI-100
0 or 1 S11-WRI-100 WSR
• 50 to 100 - S11-WRI-100
• 50 to Max - S11-WRI-100, S11-WRI-00
0 or 1 S11-WRI-00 WSR • 100 to Max - S11-WRI-00
FROM 100 TO MAXIMUM
0 or more S11-WI-50 50 WAVELENGTH SERVICES This volume increment license allows you to
VOLUME INCREMENT add blocks of 50 wavelength services. Order as
many as needed. (Note 2)
Note 2: Examples: (a) If this OneControl server is currently licensed to support up to 150 wavelength services, to
increase this to 250, then order 2 of S11-WI-50.

Order codes - SONET/SDH Control Plane services

This section contains the order codes for OneControl SONET/SDH control
plane service management functionality. This includes:
• SONET/SDH control plane provisioning licenses
• SONET/SDH control plane troubleshooting licenses
• Volume of SONET/SDH control plane services licenses
The flowchart will direct you to the following table if SONET/SDH control plane
service management functionality is being added to the deployment:
• Table 7-27, “OneControl order codes - SONET/SDH Control Plane
Service Management”
elements/control plane services managed by an existing OneControl
• Table 7-28, “OneControl order codes - SONET/SDH Control Plane
Service Management - Adding elements or services”

Table 7-27
OneControl order codes - SONET/SDH Control Plane Service Management

order server)
0 or 1 S11-SP-S210 SONET-SDH CP PROVISIONING Order 1 of these, if this functionality

SERVER LICENSE, MAX ELEMENTS will be used on this OneControl
server.
S11-SPC-S210 SONET-SDH CP PROVISIONING
Order the code that matches your
UP TO 100 ELEMENTS
network size.
S11-SPB-S210 SONET-SDH CP PROVISIONING
UP TO 50 ELEMENTS
S11-SPD-S210 SONET-SDH CP PROVISIONING

UP TO 25 ELEMENTS
0 or 1 S11-L1-AR L1 CIRCUIT PROVISION Order 1 of these, if this functionality

ADVANCED EXPLICIT ROUTING will be used on this OneControl
LICENSE server.
1 or S11-SV-500 500 SONET-SDH CP SERVICES Order 1. This base volume of

more VOLUME BASE service license enables the
OneControl server to manage up to
500 SONET-SDH CP services.
(Note 2)
0 or S11-SI-500 500 SONET-SDH CP SERVICES Only order if more than 500

more VOLUME INCREMENT SONET-SDH CP services will be
managed by this OneControl
server.
This volume increment license
allows you to add blocks of 500
SONET-SDH CP services. Order
as many as needed. (Note 2)
Note 2: Examples: (a) To manage 500 SONET-SDH CP services, order 1 of S11-SV-500, (b) To
manage 1,500 SONET-SDH CP services, order 1 of S11-SV-500 and 2 of S11-SI-500.

Table 7-28
OneControl order codes - SONET/SDH Control Plane Service Management - Adding elements or
services

to server) currently licensed to support each feature or to
order increase the number of services. (Note 1)
0 or 1 S11-SPI-50 SONET-SDH CP For SONET/SDH CP Provisioning, to go from:

PROVISIONING • 25 to 50 - S11-SPI-50
FROM 25 TO 50 ELEMENTS • 25 to 100 - S11-SPI-50, S11-SPI-100
0 or 1 S11-SPI-10 SONET-SDH CP
• 50 to 100 - S11-SPI-100
0 PROVISIONING
• 50 to Max - S11-SPI-100, S11-SPI-00
• 100 to Max - S11-SPI-00
0 or 1 S11-SPI-00 SONET-SDH CP
PROVISIONING
FROM 100 TO MAXIMUM
0 or S11-SI-500 500 SONET-SDH CP This volume increment license allows you to

more SERVICES add blocks of 5o0 SONET-SDH CP services.
VOLUME INCREMENT Order as many as needed. (Note 2)
Note 2: Examples: (a) If this OneControl server is currently licensed to support up to 1,500
SONET-SDH CP services, to increase this to 2,500, then order 2 of S11-SI-500.

Order codes - OTN services

This section contains the order codes for OneControl OTN service
• OTN provisioning licenses
• Volume of OTN services licenses
The flowchart will direct you to the following table if OTN service management
functionality is being added to the deployment:
• Table 7-29, “OneControl order codes - OTN Service Management”
elements/OTN services managed by an existing OneControl deployment is
increasing.
• Table 7-30, “OneControl order codes - OTN Service Management -
Adding elements or services”

Table 7-29
OneControl order codes - OTN Service Management

order server)
0 or 1 S11-OP-300 OTN PROVISIONING Order 1 of these, if this

SERVER LICENSE, MAX ELEMENTS functionality will be used on this
OneControl server.
S11-OPC-300 OTN PROVISIONING
Order the code that matches
UP TO 100 ELEMENTS
your network size.
S11-OPB-300 OTN PROVISIONING
UP TO 50 ELEMENTS
S11-OPD-300 OTN PROVISIONING

UP TO 25 ELEMENTS
0 or 1 S11-L1-AR L1 CIRCUIT PROVISION Order 1 of these, if this

ADVANCED EXPLICIT ROUTING functionality will be used on this
LICENSE OneControl server.
1 or more S11-OV-50 50 OTN SERVICES Order 1. This base volume of

VOLUME BASE service license enables the
OneControl server to manage
up to 50 OTN services. (Note 2)
0 or more S11-OI-50 50 OTN SERVICES Only order if more than 50 OTN

VOLUME INCREMENT services will be managed by this
OneControl server.
This volume increment license
allows you to add blocks of 50
OTN services. Order as many
as needed. (Note 2)
Note 2: Examples: (a) To manage 50 OTN services, order 1 of S11-OV-50, (b) To manage 150 OTN
services, order 1 of S11-OV-50 and 2 of S11-OI-50.

Table 7-30
OneControl order codes - OTN Service Management - Adding elements or services

to server) currently licensed to support each feature or to
order increase the number of services. (Note 1)
0 or 1 S11-OPI-50 OTN PROVISIONING For OTN Provisioning, to go from:

• 25 to 50 - S11-OPI-50
• 25 to 100 - S11-OPI-50, S11-OPI-100
0 or 1 S11-OPI-100 OTN PROVISIONING
• 25 to Maximum - Order all 3 licenses
• 50 to 100 - S11-OPI-100
0 or 1 S11-OPI-00 OTN PROVISIONING • 50 to Maximum - S11-OPI-100, S11-OPI-00
FROM 100 TO MAXIMUM • 100 to Maximum - S11-OPI-00
0 or S11-OI-50 50 OTN SERVICES This volume increment license allows you to

more VOLUME INCREMENT add blocks of 50 OTN services. Order as many
as needed. (Note 2)
Note 2: Examples: (a) If this OneControl server is currently licensed to support up to 150 OTN services,
to increase this to 250, then order 2 of S11-OI-50.


8-1
Appendix A - AP platform requirements

& engineering considerations 8-
This chapter details the platform requirements and engineering

considerations that apply to the legacy Applications Platform (AP) software.
Attention: Several factors must be taken into consideration when using

OneControl in conjunction with an existing legacy Applications Platform (AP)
setup. Details are provided below.
The following should be noted when using OneControl in conjunction with an

existing legacy Applications Platform (AP) setup:
• Linux platforms are not supported for use in conjunction with the legacy
AP software. If you intend to use any OneControl components in
conjunction with AP, all those components must be deployed on Solaris
platforms. This includes all Manager for 6k, OM5k and CPL components
(local or remote), NSV Layer1 Federated, TMF (note that this implies that
the if you want to use the TMF interface component of OneControl on top
of AP as a northbound interface, it cannot be installed co-resident with AP;
it must be installed on a separate Solaris platform).
• OSP - A deployment formerly known as OSP for all NE types was
available for use with AP. This deployment involves OSP software being
installed co-resident on AP platforms (both the OSP Client and NDS
server components), and allows the use of OSP against all supported NE
types visible in AP. This deployment scenario continues to be supported
(if using OneControl in conjunction with AP). For this support, the OSP
software must be upgraded to the OSP component delivered with
OneControl 5.0.
• NSV - A deployment formerly known as NSV for all NE types was available
for use with AP. This deployment involves NSV software (NDS server
component) being installed co-resident on AP platforms, and NSV
software (NSV client component) being installed standalone on a Solaris
platform. It allows the use of NSV against all supported NE types visible in

8-2 Appendix A - AP platform requirements & engineering considerations
AP. This deployment scenario continues to be supported (if using

OneControl in conjunction with AP). For this support, the NSV software
must be upgraded to the NSV component delivered with OneControl 5.0.
The ONM AP is a network management system that uses the Manager for 6k,
OM5k and CPL as a mediation layer to the AP user interface and other AP
applications. ONM AP provides fault management, reach-through to the
Manager for 6k, OM5k and CPL, network element auto-discovery and, using
the Graphical Network Browser (GNB), you can display network elements as
icons structured to represent your network. You can launch the Manager for
6k, OM5k and CPL user interface (UI) from ONM AP but you cannot launch
the OneControl user interface.
For more information about ONM AP, see ONM Applications Platform
Introduction, 450-3101-100.
This section provides the recommended hardware requirements for AP based

deployments and covers the following topics:
• “HP hardware platform requirements” on page 8-2

• “HP-UX Operating System (OS) configuration requirements” on page 8-6
• “Engineering considerations” on page 8-13
• “LAN/WAN requirements” on page 8-13
Attention: For information on, and any additional platform requirements for
AP not detailed in this chapter, refer to the Applications Platform Planning
Guide, 450-3101-601.
HP hardware platform requirements

This section describes the hardware requirements for HP platforms.
AP 11.0 - Recommended and supported hardware platforms

The Applications Platform (AP) software is installed on an HP platform.
For a list of legacy supported platforms, refer to the Applications Platform

Planning Guide, 450-3101-601.
When purchasing a new platform, the RX2660, RX3600,RX2800 can be

ordered. See “HP RX2660, RX3600, RX2800 supported HP itanium servers”
on page 8-5 for how to get details on the support of these platforms. Note that
for AP, only the AP GUI and the External Alarm Interface components are
supported on the RX2660/RX3600/RX2800 platform. No other AP software
components are supported (eg. Building Blocks are not supported; the
CORBA framework components are not supported).

Appendix A - AP platform requirements & engineering considerations 8-3
OSP with AP 11.0 - Recommended and supported hardware platforms

In the OSP for all NE types (HP-UX) deployment, OSP is installed on an HP
platform. The OSP hardware platform requirements are divided into
recommended systems, which should be acquired for all new deployments,
and supported legacy systems, which include all previously recommended
systems that are still supported but may be discontinued by the manufacturer
(HP).
Table 8-1 on page 8-4 lists the recommended and supported hardware
platforms, and for each platform, the following requirements are listed:
• CPU - For some platforms, both 1 CPU and 2 CPU configurations are
supported. Refer to the notes in the table for any additional requirements
on CPU type and speed.
• Memory - The minimum memory required.
• Disk space - The minimum number and size of hard disks.
To determine your platform requirements, you must know which configuration

will be used for each platform in your deployment. Refer to “Appendix B - OSP
deployments on AP systems” on page 9-1 for an overview of the deployment
options and configurations. For each platform you must know what role that
individual platform will play in the overall configuration (i.e. what components
will be installed on it):
• NDS server, OSP client & AP - NDS server and OSP client are installed
co-resident with AP. This platform supports AP GUI sessions and OSP
client GUI sessions.
• NDS server & AP (no GUIs) - NDS server is installed co-resident with AP
without the OSP client. AP GUI sessions are only launched for
administrative purposes.
• OSP client & AP - OSP client is installed co-resident with AP. This
platform supports AP GUI sessions and OSP client GUI sessions.

Table 8-1
OSP supported HP platforms & hardware requirements (Note 1, Note 2, Note 3, Note 4, Note 7)
- - RX2660 (2 CPU)
Recommended RX3600 (2 CPU)
RX2800 (2CPU)
Platform RP2450 (1CPU) RP3410 (2CPU) RP2450 (2 CPU) RP3440 (2 CPU)
C3600 RP2470 (1CPU) J6000 (2 CPU) RP2470 (2 CPU)
Supported
C3750, C3700 J5600 (2 CPU) J6750 (2 CPU)
J6700 (2 CPU)
NDS server, 6 or 8 GBytes

4 GByte 4 GByte 6 GByte
OSP client & AP (see Note 5)
NDS server &

Memory 4 GByte 4 GByte 4 GByte 4 GByte
AP (no GUIs)
6 or 8 GBytes
OSP client & AP 5 GByte 6 GByte 8 GByte
(see Note 5)
NDS server,
Minimum: 2x36G
OSP client & AP Minimum: Minimum: Minimum:
Disk 1x18G 1x18G 1x36G or 2x18G Recommended:
NDS server & 2x72G
(Note 6) Recommended: Recommended: Recommended:
AP (no GUIs) RX2660/RX3600:
2x72G 2x72G 2x72G
2x146G
OSP client & AP
Note 1: The following platforms have CPU requirements as indicated:
For RP3440/RP3410 - configured with PA8800 or PA8900 CPU(s), minimum 800MHz
For RP2470 - configured with PA8700 CPU(s), minimum 750MHz
For RP2450 - configured with PA8600 CPU(s)
For RX2660/RX3600/RX2800-configured with 2 x 1.6 GHz/18MB dual-core processor modules (9140M)
Note 2: The RP3400 series platforms have what is referred to as a Dual Core CPU. A Dual Core CPU contains 2 CPU
processors which can be activated individually (whether one or both CPUs is active depends on what package is ordered
from HP). In the context of OSP requirements, 2 CPUs means that both CPU processors on the Dual Core CPU have been
activated.
Note 3: The RX2660/RX3600/RX2800 can be ordered with 1 or 2 CPU processor modules. Each CPU processor module
can be single-core (contains 1 processor core) or dual-core (contains 2 processor cores). The RX2660/RX3600 must have
2 CPU processor modules where each module contains 2 processor cores (i.e. 4 processor cores in total are active).
Note 4: As detailed in the table, a platform that has only the OSP client & AP installed, requires more memory than a
platform that has the NDS server, OSP client & AP installed. This is due to the increased number of OSP client GUI
sessions allowed on an OSP client & AP platform. For details on engineering limits, see Chapter 4, “Network sizing and
engineering considerations”.
Note 5: For RX2660/RX3600/RX2800 platforms the first disk is configured and used, while the second disk is reserved
for future expansion (or alternatively can be used for disk mirroring). For all other platforms, two values are specified for
the memory requirements on these platforms. The lower value specifies the amount of memory required for the OSP client
to support up to 15000 NE equivalent units. The higher value (an increase of 2 GBytes), specifies the amount of memory
required for the OSP client to support up to 30000 NE equivalent units. Refer to Chapter 4, “Network sizing and
engineering considerations”, where Table 8-3 on page 8-17 details the maximum NE equivalent units supported by the
OSP client.
Note 6: For minimum disk setup: number and size of hard disks must be met, and all disk space is configured and used.
For recommended disk setup: all disk space on the first disk is configured and used, while the second disk is reserved for
future expansion (or alternatively used for disk mirroring).
Note 7: Some of these platforms have been discontinued by the manufacturer. Support for hardware exists only while
HP continues to provide hardware or software support for that particular platform.

Additional HP hardware platform requirements

In the OSP for all NE types (HP-UX) deployment, OSP is installed co-resident
on the same platform as Applications Platform (AP). Therefore, they share
similar hardware configuration details such as graphics display requirements
and mandatory hardware requirements. For these hardware configuration
details, refer to the Applications Platform Planning Guide, 450-3101-601.
HP RX2660, RX3600, RX2800 supported HP itanium servers

The HP RX2660, RX3600 and RX2800 have been added to the list of
platforms supported by the following applications:
• Applications Platform (AP) 11.0 – GUI component only (with AP 11.0
Patch A, or later)
• Applications Platform (AP) 11.0 – External Alarm Interface (EAI)
component
• Federation View Manager (FVM) 3.0
• Multiservice MOA (MMOA) 16.0
• Optical Service Provisioner (OSP) 6.0 and later
• Manager for 6k, OM5k and CPL Reverse Bridge Patch applied to AP
Attention: For AP, only the AP GUI and the External Alarm Interface
components are supported on the RX2660/RX3600/RX2800 platform. No
other AP software components are supported (eg. Building Blocks are not
supported; the CORBA framework components are not supported).
Attention: When using AP in conjunction with the Manager for 6k, OM5k
and CPL, a patch must be applied to all AP servers that will be
communicating with the Manager for 6k, OM5k and CPL server. This patch
is referred to as the Manager for 6k, OM5k and CPL reverse bridge patch,
and is distributed with software. An updated version of the Manager for 6k,
OM5k and CPL Reverse Bridge Patch is required to activate support of the
RX2660/RX3600/RX2800 platform.
Attention: When using AP on the RX2660/RX3600/RX2800 platform, SSO

must be set to Off. The SSO feature is not currently supported on the
RX2660/RX3600/RX2800 platform.

Attention: For successful launch of the NSV GUI from AP on the

RX2660/RX3600/RX2800 platform, you must execute the procedure
entitled, Configuring RX2660/RX3600/RX2800 for NSV GUI launch from AP
within the “Installing AP 11.0 on supported HP Itanium servers” document.
Refer to the information below to download this document.
For detailed information on how to deploy the HP RX2660, RX3600 and

RX2800 platforms in your network refer to the “Installing AP 11.0 on supported
HP Itanium servers” document. The latest version of this document can be
downloaded by doing the following:
• In the browse list under Browse Available Downloads For, select
APPLICATION PLATFORM
• Find the “Installing AP 11.0 on supported HP Itanium servers” item that
has a document attached to it, and select the link.
• Download the document.
HP-UX Operating System (OS) configuration requirements

This section describes the operating system configuration requirements for
HP platforms.
HP-UX OS release and configuration

This section describes the operating system HP-UX release and configuration
requirements.
HP-UX operating system requirements for RX2660/RX3600/RX2800 platforms

For detailed information on operating system requirements to deploy the HP
RX2660,RX3600, RX2800 platforms in your network refer to the “Installing AP
11.0 on supported HP Itanium servers” document. The latest version of this
document can be downloaded by doing the following:


HP-UX operating system requirements for all other platforms

All other supported HP platforms must run the HP-UX 11i v1 64 Bit operating
system. The HP-UX 11i v1 64 Bit operating system is no longer orderable with
Ciena or with HP. Therefore for existing HP PA-RISC platforms, continue to
use the OS CDs previously ordered.
HP offers various flavours of the HP-UX 11i v1 operating systems, referred to

as Operating Environments. In addition, various versions of these operating
environments are available, usually labelled with the month and year of
release. Only those operating environments and versions specifically
supported by Ciena can be used. No other operating environments or
versions can be used.
An HP-UX OS upgrade from previous releases of HP-UX to HP-UX 11i v1 is

not supported. If this is a new deployment, the HP-UX 11i v1 operating system
must be freshly installed according to the HP platform deployed.
WARNING
The operating system requirements provided in this document
are accurate at the time of availability of this document.
However, OS requirements and recommendations may be
updated at a later date. The latest requirements should be
consulted (see “Determining the required HP-UX operating
system version” on page 8-7).
Determining the required HP-UX operating system version

The following sections detail the HP-UX OS operating environments and
versions required. The information provided is accurate at the time of
availability of this document. However, OS requirements and
recommendations may be updated at a later date. The latest information on
operating system requirements can be downloaded by doing the following:
• In the browse list under Browse Available Downloads For, select any
one of the products (OMEA, OSP, TMF or NSV)
item.

• Download the document(s) that detail(s) the recommended operating

system. Use the document(s) to identify the supported HP-UX operating
system version.
The document contains the most recent operating system requirements.
HP-UX OS version supported for upgrades to existing deployments

For existing HP hardware platforms already deployed in a network, the
operating system requirement as documented in previous OSR software
product releases was one of the following:
• the HP-UX Release 11i v1 64 Bit Operating Environment (OE) June 2001
release, with HP Common Desktop Environment (CDE)
• the HP-UX Release 11i v1 64 Bit Technical Computing Operating
Environment (TCOE) March 2003 release
• the HP-UX Release 11i v1 64 Bit Foundation Operating Environment (OE)
June 2004 release, with HP Common Desktop Environment (CDE)
For these existing deployments, these operating system versions continue to

be supported.
HP-UX OS version required for new deployments

For all new HP hardware platforms being deployed in a network, or if the
operating system is being freshly installed on an existing platform, the
operating system version that must be used is the following:
• For HP RX2660/RX3600/RX2800 servers: HP-UX 11i v3 Base Operating
Environment (BOE), September 2008 release, with HP Common Desktop
Environment (CDE
• For all other HP servers: HP-UX Release 11i v1 64 Bit Foundation
Operating Environment (OE) June 2004 release, with HP Common
Desktop Environment (CDE)
Attention: HP PA-RISC platforms are supported platforms that have PA-RISC

based CPUs (includes RP3410, RP3440), however the HP-UX 11i v1 OS is no
longer orderable. For existing HP PA-RISC platforms, continue to use the OS CDs
previously ordered.
Downloading HP-UX operating system installation example

Sample instructions for installing the operating system can be downloaded by
doing the following:


• Find the "HP-UX 11i installation example" item.
• Download the HP-UX 11i installation example.
The document contains the most recent details on how to install the operating
system. These instructions are intended to be a sample of common install
scenarios.
HP-UX OS patches
After the HP-UX operating system is installed, a series of operating system
patches recommended by Ciena must be applied. There is a minimum OS
patch bundle required. In addition, the recommended OS patch bundle is
updated periodically, and posted online by Ciena.
The OS patch bundle is released with an associated Readme file that explains
how to apply the patch bundle to your system. The administrator should
always read the documentation before attempting to install the patch bundle.
WARNING
Ciena software products have been verified against a specific
set of patches. Installation of any additional patches other than
the ones listed or provided is not supported, and Ciena
Corporation does not accept responsibility, or provide support
for any related issues which may arise as a result. Customers
should also be aware that installing any additional patches may
lead to undesirable behavior (performance related, corruption,
core dumps, etc). In summary, responsibility for any issues
which arise as a result of installing additional patches other
than the ones listed or provided must be understood and
accepted by the customer.
Downloading HP-UX 11i operating system patches

The OS patch bundle and documentation can be downloaded by doing the
following:
item.

• Download the document(s) that detail(s) the recommended operating

system patches. Use the document(s) to identify the name of the latest
recommended OS patch bundle that applies to the HP-UX OS.
• Find the name of the OS patch bundle you need, and download the
software and the corresponding Readme file.

Hard disk configuration

This section describes the hard disk configuration on a HP-UX platform.
Disk space requirements

For disk space requirements for OSP, see Table 8-1 on page 8-4.
Disk partitioning
Refer to the disk partition requirements in the Applications Platform Planning
Guide, 450-3101-601.
Disk partitioning for RX2660/RX2800/RX3600 platforms

For detailed information on disk partitioning requirements to deploy the HP
RX2660, RX2800 and RX3600 platforms in your network refer to the
“Installing AP 11.0 on supported HP Itanium servers” document. The latest
version of this document is available on the Ciena Web site. To download the
latest version, do the following:
Kernel parameters for all HP platforms

Table 8-2 on page 8-12 specifies the kernel parameters that must be set on all
HP platforms (including the RX2660/RX2800/RX3600 platforms). All kernel
parameters not specified should remain at their default values.
Kernel parameters can be set using the HP-UX System Management

Homepage (SMH) for RX2660/RX2800/RX3600 platforms, or the HP-UX
System Administration Manager (SAM) for all other supported HP platforms.

Alternatively, details on how to set the kernel parameters are included in the
documentation provided for installing HP-UX operating system patches (see
“HP-UX OS patches” on page 8-9).
Table 8-2
HP-UX required kernel parameters (all supported HP platforms)
HP-UX kernel Value

parameter
maxdsiz 2063835136
maxdsiz_64bit 2063835136
maxfiles For RX2660/RX2800/RX3600 platforms: 2048

For all other supported HP platforms: 8192
maxfiles_lim For RX2660/RX2800/RX3600 platforms: 2048

For all other supported HP platforms: 8192
maxssiz 0x04000000
maxssiz_64bit 0x04000000
maxswapchunks 4096 (Note:)
max_thread_proc 1200
maxuprc 512
maxusers 512 (Note:)
msgtql 1024
ncallout (16+NKTHREAD) (Note:)
nfile 9000 (Note:)
ninode 3048
nkthread For RX2660/RX2800/RX3600 platforms: 5176

For all other supported HP platforms: ((NPROC*2)+(1000))
nproc 2088
npty 200
semmni 128
semmns 512
semmnu 512
shmmax 1073741824


HP-UX required kernel parameters (all supported HP platforms)
HP-UX kernel Value

parameter
shmseg 120
vps_ceiling 16
Note: The following parameters do not apply to RX2660/RX2800/RX3600 servers:

maxswapchunks, maxusers, ncallout, nfile.
HP-UX desktop environments

When accessing the platform via the console or by using UNIX emulation
software, the Common Desktop Environment (CDE) window manager must
be selected. Other window managers are not supported.
HP-UX environment variables

The locale settings for the operating system must be set to NULL. If not set
during the OS install, when the OS reboots after installation you may be
prompted to set the language or locale. Select null (the option may appear as
NULL or SET_NULL_LOCALE).
HP platforms - Additional requirements

For details on other hardware requirements such as peripheral devices
required, refer to Applications Platform Planning Guide, 450-3101-601.
LAN/WAN requirements
TCP/IP connections between all workstations/servers and network elements
are required.
The DCN between EMS and network, between EMS nodes and between
EMS servers and EMS clients average delay on any transfer rate on each of
the DCN segments should not exceed 200 ms with absence of packet loss.
NAT (Network Address Translation) is not supported between the Manager for
6k, OM5k and CPL server and ONM AP.
Engineering considerations
This section details the engineering considerations that apply to ONM AP
deployments.

Engineering rules - Generic

The following engineering rules apply:
• A controller supports a total of up to 4 connections from software products
that use connection management and/or logical inventory services. This
includes the following applications:
— NDS server component of Optical Service Provisioner (OSP)
— NDS server component of Network and Service Viewer (NSV)
— TMF Interface
— Trail Management/OSV/DWDM View servers (since Trail
Management, OSV and DWDM View must all be installed co-resident
and use the same server process, they collectively count as one
connection to the controller)
— Data Mining application
— Redundant configurations of any of the software products mentioned
require additional connections
All applications above connect to the same service on the controller.

Thus, when deploying OSR software products, care must to taken to ensure
that when all software products in the network are considered, no controller in
the network has more than 4 applications connecting to this service.
Engineering rules - Manager for 6k, OM5k and CPL specific

• If Manager for 6k, OM5k and CPL is deployed in a network managed by
Applications Platform (AP), a patch must be applied to all the AP platforms
that will be communicating with Manager for 6k, OM5k and CPL. This
patch is referred to as the Manager for 6k, OM5k and CPL reverse bridge
patch, and is delivered as part of the OneControl software load.
Instructions on how and when to install the Manager for 6k, OM5k and
CPL reverse bridge patch are included as part of the install and upgrade
procedures in the OneControl Installation, 450-3201-201.
CAUTION
Multiple releases of Manager for 6k, OM5k an CPL not supported
in network managed by ONM AP
Ciena does not support multiple releases of Manager for 6k,
OM5k and CPL, present in a network managed by Optical
Network Manager Applications Platform. While this should not
cause critical failures (i.e. fault reporting should still function
properly), there may be issues with certain functionality being
unavailable. The only resolution is to upgrade all platforms to
the latest release.

Engineering rules - OSP specific

• When OSP is deployed on an HP platform, it must co-reside with the AP
graphical user interface (GUI). All engineering rules that apply to AP must
be followed. For more information, refer to Applications Platform Planning
Guide, 450-3101-601.
• All OPC controllers supported by OSP must be bridged to the Applications
Platform (AP) release being used.
• For all controllers, if a backup/secondary controller exists, the
corresponding primary controller must be enrolled in AP. Enrolling a
backup/secondary controller without enrolling the primary controller is not
supported by OSP.
• When deploying OSP, multiple NDS servers can be installed to provide
redundancy (Resilient NDS server deployments) and scalability
(Partitioned NDS server deployments). When this is done, each NE
cannot be managed by more than one NDS server if the NDS servers
communicate with each other. This implies that:
— In Resilient NDS server deployments, the NDS servers should not be
configured to communicate with each other.
— In Partitioned NDS server deployments, there should not be any
overlap of the controllers managed by each NDS server. To ensure
that no controller/NE is managed by more than one of these NDS
servers, the resource allocation tool must be used to exclude the
appropriate controllers/NEs on each NDS server. This also implies
that if a new controller is added in AP, this controller must immediately
be excluded in OSP from all but one NDS server.
• In Partitioned NDS server deployments, all NDS servers must be
configured to communicate with each other in order to properly handle
topological links. The maximum number of NDS servers that can be
configured to communicate with each other is 3.
Engineering rules - TMF specific

The following engineering rules apply to TMF:
• TMF can be deployed:
— on a SUN platform co-resident with Manager for 6k, OM5k and CPL
— on a dedicated SUN platform (with no other applications co-resident,
except optionally TMF Light Data Mining).
• If TMF is deployed on a SUN platform co-resident with Manager for 6k,
OM5k and CPL, Manager for 6k, OM5k and CPL must be installed first
before installing TMF.

• If TMF is deployed on a dedicated SUN platform, it can be configured to

work in conjunction with only one of the following:
— A maximum of one AP platform (no other APs or Managers for 6k,
OM5k and CPL). In this case TMF will manage the same
controllers/NEs managed by that AP.
— A maximum of one Manager for 6k, OM5k and CPL platform (no other
APs or Managers for 6k, OM5k and CPL). In this case TMF will
manage the same NEs managed by that Manager for 6k, OM5k and
CPL.
• If TMF is deployed on a dedicated SUN platform:
— Any Manager for 6k, OM5k and CPL platforms that are being managed
by TMF can each have a maximum number of 2,100 NEs managed.
• If there are multiple Managers for 6k, OM5k and CPL managing different
sets of network elements in the network, then users can choose to:
— use an AP deployment where multiple Managers for 6k, OM5k and
CPL are reporting into AP and the AP provides the data feed into the
TMF application, or
— install TMF co-resident with each Manager for 6k, OM5k and CPL (this
implies that the client application connecting to TMF will need to
manage multiple feeds)
• If TMF is deployed co-resident with TMF Light Data Mining, there may be
additional engineering considerations that have to be taken into account.
Refer to the TMF Light Data Mining User Guide.
• a max number of 2,100 NEs can be managed in Manager for 6K enrolled
to TMF Standalone
Network size
The maximum number of network elements (NEs) that can be managed
depends on the following factors:
• The type of hardware platforms used.
• The software applications installed on the hardware platform.
• The number and types of NEs deployed in the network. Different types of
NEs can place a different load on the software because some NE types
are capable of reporting a larger number of ports and connections than
other NE types. Because of this, the concept of a network element (NE)
equivalent unit is used. In order to engineer your network, you must
calculate the total number of NE equivalent units in your network.
Network element equivalent units (NEUs)
Table 4-1 on page 4-9 defines the number of NE equivalent units that must be
used to represent each NE type, in order to calculate the total number of NE
equivalent units you have in your network.

Maximum NEUs supported

Tables 4-2 to 4-12 list the maximum number of NE equivalent units supported
on Oracle SPARC and on Intel platforms. Table 8-3 on page 8-17 lists the
maximum number of NE equivalent units supported on HP platforms.
Table 8-3
Maximum number of NEUs supported on HP platforms
Maximum number of NE equivalent units supported

(see Table 4-1 on page 4-9 for unit description)
RX3600 (2CPUs) RP2450 (2CPUs) RP3410 (2CPUs) RP2450 (1CPU)

Applications, RX2800 (2CPUs) J6000 (2CPUs) RP2470 (1CPU) C3600
Components RX2660 (2CPUs) J5600 (2CPUs) C3750
co-resident RP3440 (2CPUs) C3700
RP2470 (2CPUs)
J6750 (2CPUs)
J6700 (2CPUs)
AP & OSP (OSP GUI, 15000

5200 2400 2000
NDS server, or both) (Note 1)
Note 1: Up to 15000 NE equivalent units are supported when using the standard recommended
memory requirements on these platforms. It is possible to manage a larger network by using what is
referred to as a Partitioned NDS server deployment. In this deployment, multiple NDS servers are used
to balance the load of the network (with each NDS server not exceeding the 15000 NEU limit). The OSP
GUI in this deployment can support up to 30000 NE equivalent units, if the memory is increased by 2
GBytes. Refer to Chapter 5, “Platform requirements”, which details the memory requirements for each
platform.

Manager for 6k, OM5k and CPL GUI scalability

The maximum number of Manager for 6k, OM5k and CPL GUIs that can be
launched against an Manager for 6k, OM5k and CPL server depends on the
following factors:
• The type of hardware platforms used to install Manager for 6k, OM5k and
CPL.
• The software applications installed co-resident with Manager for 6k, OM5k
and CPL.
• Where the Manager for 6k, OM5k and CPL GUIs are launched. An
Manager for 6k, OM5k and CPL GUI run locally on the Manager for 6k,
OM5k and CPL server places a larger load on the hardware than an
Manager for 6k, OM5k and CPL GUI run on a remote platform. Because
of this, the concept of a GUI equivalent unit is used.
Manager for 6k, OM5k and CPL GUI equivalent units

Table 8-4 on page 8-18 defines the number of Manager for 6k, OM5k and CPL
GUI equivalent units that must be used to represent each type of Manager for
6k, OM5k and CPL GUI session.
Table 8-4
Manager for 6k, OM5k and CPL GUI equivalent units by type of Manager for 6k, OM5k and CPL
GUI session
Manager for 6k, OM5k and CPL GUI equivalent units

by type of Manager for 6k, OM5k and CPL GUI session
Type of Manager
for 6k, OM5k and T4-1, T5220-8, V890, HP620c V490 T5220-8, Oracle
CPL GUI T4-2 (64G) V880 G7 (64G) (32G) T5220-4, 2270 M2
session (32G) Oracle V490 V440, N440 (24G)
4270 M2 (16G)
(48G)
AP reach-through
to Manager for
2.5 2.5 2.5 2.5 2.5 2.5
6k, OM5k and
CPL GUI
NSV GUI scalability

The maximum number of NSV GUIs supported in NSV deployments with
ONM AP depends on the following factors:
• The type of hardware platforms used to install NSV.

• Where the NSV GUIs are launched. The concept of an NSV GUI
equivalent unit is used.
NSV GUI equivalency units

Table 8-5 on page 8-19 defines the number of NSV GUI equivalent units that
must be used to represent each type of NSV GUI session.
Table 8-5
NSV GUI equivalency units by NSV hardware platform
NSV GUI equivalency units

by hardware platform NSV is installed on
Type of NSV GUI T5220-8 V890, V490 T5220-8, V490,
session (32G) V880 (32G) T5220-4, V440, (16G)
(32G) N440
(16G)
NSV GUI launch

2.5 2.5 2.5 2.5 2.5
directly from AP
NSV GUI remote 1 1 1 1 1

launch from a PC
Maximum NSV GUI equivalent units supported

Table 8-6 on page 8-19 lists the maximum number of NSV GUIs supported.
Table 8-6
Maximum number of NSV GUIs supported
Maximum number of NSV GUI equivalent units supported

(NSV for all NE types)
Applications (see Table 8-5 on page 8-19 for unit description)
co-resident T5220-8 V890, V490 T5220-8, T5220-4, V490,
(32G) V880 (32G) V440, N440 (16G)
(32G) (16G)
NSV only 50 38 35 25 25

Maximum NSV GUIs supported per PC

Table 8-7 on page 8-20 lists the maximum number of NSV GUIs that a PC can
support.
Table 8-7
Maximum number of NSV GUIs supported on a PC
Type of NSV GUI session Maximum number of NSV GUIs supported on a PC
Launch from PC 5
Note 1: This type of launch is only applicable to the NSV for all NE types
deployment, where the user chooses to launch NSV manually from a web browser
on a PC, instead of through the AP GUI session.
Note 2: When using this launch option, the NSV GUI is launched without context
(no NE is selected by default for searches). It is recommended that an NE be
selected in the search criteria before performing any queries. If a query is done
without context, no more than 1 query of this type should be performed at any time.
OSP GUI scalability

This section lists the engineering limits that apply to OSP deployments with
ONM AP.
The maximum number of OSP GUIs supported in this deployment depends

on the following factors:
• The type of hardware platforms used to install OSP.
• The OSP software components installed co-resident.
• Where the OSP GUIs are launched. An OSP GUI run on the same
machine as the NDS server places a larger load on the hardware than an
OSP GUI run on a remote platform. Because of this, the concept of a GUI
equivalent unit is used.

OSP GUI sessions

Table 8-8 on page 8-21 lists the maximum number of OSP GUI sessions that
can be run on a platform where the OSP GUI is installed.
Table 8-8
Maximum local OSP GUI sessions supported
Maximum local OSP GUI sessions supported
RP2450 (1 CPU) RP3410 (2 CPUs) RP2450 (2 CPUs) RX3600 (2CPUs)

Components C3600 RP2470 (1 CPU) J6000 (2 CPUs) RX2800 (2CPUs)
installed C3750 J5600 (2 CPUs) RX2660 (2CPUs)
co-resident C3700 RP3440 (2 CPUs)
(Note:) RP2470 (2 CPUs)
J6750 (2 CPUs)
J6700 (2 CPUs)
NDS server, OSP 3 4 8 12

GUI & AP
NDS server & AP N/A N/A N/A N/A

(no GUIs)
OSP GUI & AP 10 12 18 24
Note: The maximum number of OSP GUIs that can be launched from a single AP GUI session is 2.
The total number of concurrent OSP GUI sessions that can be run on a
platform where the OSP GUI is installed, is enforced on each system through
a configurable parameter. This value is configured via the osp_admin
configure tool located in the /opt/nortel/osp directory. The default for
this variable is 10. This value should be changed to the values specified in the
tables.
OSP GUI sessions hosted by an NDS server

The hardware platform on which you deploy the NDS server will determine the
maximum number of OSP GUI sessions that can be established to it. An OSP
GUI session can place a different load on the NDS server, depending on
whether it is launched on the same platform as the NDS server or from a
remote platform. As a result, the concept of an OSP GUI equivalent session
is used.
Table 8-9 on page 8-22 lists the maximum number of OSP GUI equivalent unit
sessions that an NDS server can host concurrently. Table 8-10 on page 8-23
defines the number of OSP GUI equivalent unit sessions that must be used to
represent each type of OSP GUI session.

In engineering your OSP deployment, you must take into account the scenario
where the maximum number of OSP GUI sessions are launched on every
platform where an OSP GUI is installed. In this scenario, the total number of
OSP GUI equivalent unit sessions established to the NDS server must not
exceed the maximum allowed. If it does, the maximum number of OSP GUI
sessions will need to be lowered on some of the platforms.
Attention: You must also take into account any Network and Service
Viewer (NSV) server sessions established to the NDS server. Network and
Service Viewer (NSV) is a separate software application. In some
configurations, the NSV server can be deployed such that it uses the NDS
server component of OSP as its underlying server component (i.e. it acts like
another client to the NDS server, just like the OSP GUI).
Table 8-9
Maximum OSP GUI equivalent unit sessions supported to an NDS server
Maximum OSP GUI equivalent unit sessions supported to an NDS server

(see Table 8-10 on page 8-23 for unit description)

RP2470 (2 CPUs)
J6750 (2 CPUs)
J6700 (2 CPUs)
AP, NDS server, 13 14 22 24

OSP GUI
NDS server & AP 13 14 22 24

(no GUIs)
OSP GUI & AP N/A N/A N/A N/A

Table 8-10
OSP GUI equivalency units
OSP GUI equivalency units

C3600 RP2470 (1 CPU) J6000 (2 CPUs) RX2800 (2CPUs)
Client session C3750 J5600 (2 CPUs) RX2660 (2CPUs)
type C3700 RP3440 (2 CPUs)
RP2470 (2 CPUs)
J6750 (2 CPUs)
J6700 (2 CPUs)
OSP GUI session 4.25 3.5 2.75 2

launched locally
(i.e. on the same
machine as the
NDS server)
OSP GUI session 1 1 1 1

launched remotely
(i.e. from another
machine to the NDS
server)
NSV server session 1 1 1 1

connected remotely
(i.e. from another
machine to the NDS
server) (Note:)
Note: Network and Service Viewer (NSV) is a separate software application. In some configurations,
the NSV server can be deployed such that it uses the NDS server component of OSP as its underlying
server component (i.e. it acts like another client to the NDS server, just like the OSP GUI).
For example, consider a deployment that consists of only two platforms:

• an HP RP3440 platform with both the NDS server and the OSP GUI
installed
• an HP C3750 platform with the OSP GUI installed
In this scenario, if the HP C3750 is configured to allow up to 12 OSP GUI

sessions to be launched, then the maximum OSP GUI sessions allowed on
the HP RP3440 is 6 (since this results in 24 equivalent unit sessions to the
NDS server):
OSP GUI sessions OSP GUI sessions Total OSP GUI equivalent unit
launched remotely launched locally sessions to the NDS server
(12 x 1) + (6 x 2) = 24 OSP GUI equivalent unit sessions

AP GUI (GNB) sessions

When OSP is installed on the same platform as AP, the number of AP GUI
(GNB) sessions that can be launched on that platform is impacted.
Table 8-11 on page 8-24 lists the maximum number of AP GUI (GNB)
sessions supported on a platform where OSP is installed.
Table 8-11
Maximum AP GUI (GNB) sessions supported
Maximum AP GUI (GNB) sessions supported

RP2470 (2 CPUs)
J6750 (2 CPUs)
J6700 (2 CPUs)
NDS server, OSP 8 10 15 18

GUI & AP
NDS server & AP 1 1 1 1

(no GUIs) (for administrative (for administrative (for administrative (for administrative
purposes only) purposes only) purposes only) purposes only)
OSP GUI & AP 10 12 18 27
The total number of concurrent AP GUI (GNB) sessions is enforced on each

system through a configurable variable named GNBMaxInstances in the file
/usr/bin/noc/user.resources. The default for this variable is 10. This
value should be changed to the values specified in the tables.
OSP firewall considerations

In the OSP for all NE types (HP-UX) deployment, in order for OSP to function
correctly in a firewall environment, the following ports must be opened:
• 3306: access to OSP cache (MySQL)
• 8080: Help File access
• 58772: Naming Service
• 35000-35599: CORBA ports used by NDS server to communicate with all
north-bound clients (OSP GUI, Resource Tool, Topology Provisioner tool,
etc.)
• 58000-58199: CORBA ports used by OSP GUI to communicate with NDS
server

• In addition to the ports above, the NDS server picks a port number
randomly from the free ports available in order to establish communication
with the controllers being managed.
NSV firewall considerations
In order for the NSV deployment for all NE types to function correctly in a
firewall environment, the ports listed in Table 8-12 on page 8-25 must be
opened:
Table 8-12
NSV Standalone Firewall (also required between redundant NSV servers)
Port Service request initial Data flow Application TCP or Description
direction UDP
based
Source Destination
7 Xterminal NSV server Bidirectional echo TCP Standard echo session port. For external
emulator clients such as Exceed to determine the
server availability before establishing
connection.
This may cause delays if the Exceed
session is being established through a
firewall.
20 NSV server NSV server Bidirectional FTP TCP Standard FTP data session port. For an
resilient external FTP client, using passive FTP
mode, this port is not used.
NSV server NSV server
resilient For an external FTP client, using active
FTP mode, this port is used by the
Manager for 6k, OM5k and CPL FTP
server to initiate the FTP data connection.
For an internal FTP client, using active
FTP mode, the Manager for 6k, OM5k
and CPL FTP client receives FTP data
connection requests from this port on the
external FTP server.
Internal FTP client using passive FTP
mode is not supported.
21 NSV server NSV server Bidirectional FTP TCP Standard FTP control session port.
resilient For an external FTP client, using active or
passive FTP mode, the Manager for 6k,
resilient OM5k and CPL receives FTP control
session requests on this port.
For an internal FTP client, in active FTP
mode, the Manager for 6k, OM5k and
CPL initiates FTP control session
requests to this port on the external FTP
server
Internal FTP client using passive FTP
mode is not supported.


direction UDP
Source Destination based
23 NSV server AP Bidirectional TELNET TCP Used for technical support access NSV.
For use during NSV upgrades, AP
AP NSV server
reachthrough to NSV Client.
NSV server Manager for NSV Reachthrough to AP to launch NE
6k, OM5k craft. Manager for 6k, OM5k and CPL
and CPL reachthrough to NSV Client. NSV
server Reachthrough to Manager for 6k, OM5k
Manager for NSV server and CPL to launch NE craft.
6k, OM5k Resiliency communication between NSV
and CPL server.
server
80 Manager for Manager for Bidirectional HTTP TCP Used to launch System Manager.
6k, OM5k 6k, OM5k Used by Manager for 6k, OM5k and CPL
and CPL/ and Desktop to establish connection to the
NSV CPL/NSV Manager for 6k, OM5k and CPL Server.
Desktop server
123 NSV server AP or Bidirectional NTP TCP / Standard NTP port.
Manager for UDP For use on NSV platforms to align time
6k, OM5k using NTP.
and CPL or In asymmetric (Peer-to-Peer) mode, two
NTP server devices share NTP information and
maintain state information during the
exchange of time information. Both hosts
use UDP port 123 for communication.
When port 123 is used for both the source
and destination port numbers, it signals
the receiver that asynchronous mode is
being used.
In Symmetric (Client-Server), Clients
request time from servers and the servers
respond without using any state
information. In this mode, a request is
sent to destination port 123 on the server
and a different source port is used for the
client. The different port numbers indicate
which device is acting as server and
which as client.
1024 to NSV server NSV server Bidirectional FTP TCP When the NE acts as the FTP client in
5000 Resilient active FTP mode, a port in this range will
be used to receive an FTP data
connection from port 20 on an external
Resilient FTP server. TL1 upgrades, backups and
restores use active FTP, with the client on
the NE.


direction UDP
1814 NSV server NSV server Bidirectional RADIUS UDP RADIUS requests are sent to this port by
(included resilient default, however the port number is
in 1024 to provisionable. Any change to the default
5000 port) resilient value would require a corresponding
change to firewall settings.
AP NSV server
NSV server external
RADIUS
server
Optional
NSV server Manager for
6k, OM5k
and CPL
server
Manager for NSV server
6k, OM5k
and CPL
server
6k, OM5k
and CPL
server
1812 Manager for Session Bidirectional Session TCP System Manager accesses this port for
(included 6k, OM5k Manager Manager session management
in 1024 to and CPL/ (SMI) (SMI)
5000 port) NSV server
2636 Manager for Manager for Bidirectional LDAP TCP LDAP access port. Uses secure LDAPS
6k, OM5k 6k, OM5k protocol.
and CPL and CPL
server server
6000-6020 NSV server AP Bidirectional X-Based Login TCP For use in NSV reachthroughs from AP.
8003 Manager for NSV server Bidirectional Tomcat TCP This port is used from the service allowing
6k, OM5k the download of the SUN client software
and CPL/ from the NSV server.
NSV client
8004 Manager for NSV server Bidirectional Tomcat TCP Tomcat secure software distribution port.
6k, OM5k
and CPL/
NSV client
9011 Manager for Manager for Bidirectional Manager for 6k, TCP Default port for historical alarms
6k, OM5k 6k, OM5k OM5k and CPL
and CPL/ and CPL
NSV Server Server


direction UDP
9012 and Manager for Manager for Bidirectional Tomcat TCP Tomcat services ports
9013 6k, OM5k 6k, OM5k
and CPL/ and CPL GUI
NSV server
Server
Manager for Manager for
6k, OM5k 6k, OM5k
and CPL and
GUI server CPL/NSV
Server
9014 Manager for Manager for Bidirectional Client-server TCP Used for connection services between PC
6k, OM5k 6k, OM5k main connection Manager for 6k, OM5k and CPL/NSV and
and CPL/ and CPL GUI service Manager for 6k, OM5k and CPL/NSV
NSV Server server server.
Manager for Manager for Required for both server and PC desktop.
6k, OM5k 6k, OM5k
and CPL and CPL/
GUI server NSV
Server
9016 to Manager for Manager for Bidirectional Client-server TCP Used for platform services
9019 6k, OM5k 6k, OM5k main connection communication between PC Manager for
and CPL/ and CPL GUI service 6k, OM5k and CPL/NSV and Manager for
NSV Server server 6k, OM5k and CPL/NSV server.
Manager for Manager for Required for both server and PC desktop.
6k, OM5k 6k, OM5k
and CPL and CPL/
GUI server NSV
Server
9020 Manager for Manager for Bidirectional Platform TCP Summary secure port.
6k, OM5k 6k, OM5k Services
and CPL and CPL/
GUI server NSV
Server
14001 NSV server NSV server Bidirectional TELNET TCP TL1 port used between NSV and AP, also
resilient use between NSV resilient pair and
NSV server NSV server between NSV and Manager for 6k, OM5k
and CPL.
resilient
NSV server AP
AP NSV server
6k, OM5k
and CPL
server
6k, OM5k
and CPL
server


direction UDP
30001 and NSV server AP REGD TCP Transient port used by the REGD process
30011 within Manager for 6k, OM5k and CPL's
AP NSV server
AP gateway feature.
For use after AP has successfully
6k, OM5k
validated an Manager for 6k, OM5k and
and CPL CPL controller. AP uses this port to send
servers
an xdr message containing a permanent
Manager for NSV server TCP port number which the Manager for
6k, OM5k 6k, OM5k and CPL will use to connect to
and CPL the AP.
servers As this is a transient port, the connection
is dropped after it is no longer needed.
30002 and NSV server AP Bidirectional REGB TCP Transient port used by the REGB process
30012 AP NSV server within Manager for 6k, OM5k and CPL AP
gateway feature.
NSV server Manager for For use when AP attempts to manage an
6k, OM5k Manager for 6k, OM5k and CPL controller
and CPL to validate the controller details.
servers As this is a transient port, the connection
Manager for NSV server is dropped after the controller has been
6k, OM5k validated.
and CPL
servers
30101 and NSV server AP Bidirectional REGE TCP Transient port used by the REGE process
30111 within Manager for 6k, OM5k and CPL AP
AP NSV server
gateway feature.
NSV server Manager for For use when a Trail Manager attempts to
6k, OM5k manage an Manager for 6k, OM5k and
and CPL CPL controller to validate the controller
servers details.
Manager for NSV server As this is a transient port, the connection
6k, OM5k is dropped after the controller has been
and CPL validated.
servers
30201 to NSV server AP Bidirectional GNB TCP / Used by GNB for NSV client to launch
30250 AP NSV server UDP GNB applications such as Alarm Manager
and OSP GUI.


direction UDP
58000 to NSV server AP Bidirectional NSV TCP / used by NSV server component to
58199 UDP communicate with NDS Server on AP or
AP NSV server
Solaris.
resilient
resilient
6k, OM5k
and CPL
servers
6k, OM5k
and CPL
servers
TMF firewall considerations

TMF Server standalone on a Sun Server with AP
This section is relevant if a firewall is to be placed between the TMF server
and the HPUX workstation running the NocSsnSrv component.
When TMF is running on a stand alone Solaris workstation and

communicating to a HPUX workstation running the NocSsnsrv component,
the following additional communications will take place. The TMF server
obtains its basic resource feed from the NocSsnSrv component.
Open ports 52490-52491 outgoing from the TMF server to the HPUX
workstation running the NocSsnSrv component.
The sections “Client to TMF server” and “TMF server to controller/NEs” are
still relevant.

9-1
Appendix B - OSP deployments on AP

systems 9-
This chapter is dedicated to providing additional information that may be

required for OSP deployments where OSP is installed co-resident with the
legacy Applications Platform (AP) software. This deployment was formerly
referred to as the OSP deployment for all NE types.
This section covers the following topics:
• “Partitioned NDS server deployments” on page 9-1
• “Comparing Options for OSP Deployments on AP systems” on page 9-5
• “Planning your OSP Deployment on AP systems” on page 9-7
Partitioned NDS server deployments

This section presents examples of various deployment options that can be
used when Partitioned NDS servers are required for deployments in larger
networks.
Deploying Partitioned NDS servers is not the same as deploying a Resilient

NDS server. The term Partitioned NDS server is used to refer to the scenario
where each NDS server manages only some NEs in the network (as opposed
to Single or Redundant NDS server deployments where each NDS server
manages all NEs in the network).
Deploying Partitioned NDS servers is required if the total number of NE

equivalent units in your network exceeds the maximum supported by OSP. In
this setup, multiple NDS servers are installed, each managing a subset of
controllers. This permits the sharing of connection management tasks across
portions of a larger network. From the user’s perspective, one OSP client GUI
can still be used to work with a consolidated view of the network (including
topology between NEs managed by different NDS servers).

9-2 Appendix B - OSP deployments on AP systems
Attention: In Partitioned NDS server deployments, all NDS servers must be

configured to communicate with each other in order to properly handle
topological links. The maximum number of NDS servers that can be
configured to communicate with each other is 3.
Partitioned NDS server - AP federation

Figure 9-1 on page 9-2 shows an example of a simple hybrid AP federation
after OSP has been deployed in a resilient manner.
As depicted in the figure, in the resilient NDS server deployment, each NDS
server manages all the controllers/NEs in the network.
Figure 9-1
AP hybrid federation after resilient NDS with new platforms (NDS
communications)
Figure 9-2 on page 9-3 also shows a hybrid AP federation, however in this
case, two Partitioned NDS servers have been deployed (this would be done if
the total number of NEs in the network exceeds the maximum supported by
OSP).

It is important to note that in this scenario, there is a distinction between the

controllers/NEs managed by AP, and the controllers/NEs managed by the
NDS server. In the example, all the AP platforms are configured as Hybrid or
Indirect nodes in FVM. They all have a view of the entire network (with some
controllers managed directly, and others managed indirectly). However, each
NDS server is configured to manage only part of the network.
The two NDS servers are configured to communicate with each other,
allowing them to exchange information (such as topology between NEs
managed by different NDS servers).
Attention: When deploying Partitioned NDS servers in a hierarchical

federation, the NDS servers can be deployed on those platforms designated
as Direct in the FVM federation. However, this is not a recommended
approach given that Direct platforms may not meet the OSP engineering
rules and limits as outlined in this document.
Figure 9-2
AP hybrid federation after Partitioned NDS with new platforms (NDS
communications)

The approach used to configure each Partitioned NDS server is to specify an

exclusion list, by specifying the NEs that should not be managed by that
particular Partitioned NDS server. NEs can be excluded using the following
criteria:
• Controllers, by software release:
— Controller type + Controller software release (selected from default
controller list)
• Controllers, by IP address:
— Controller IP address + Controller type (selected from default
controller list)
— Controller IP address (manually entered)
• NEs, by software release:
— NE type + NE software release (selected from default controller list)
• NEs, by controller IP address and NE ID:
— Controller IP address + NE ID (selected from default controller list)
— Controller IP address + NE ID (manually entered)
OSP starts with the default controller list provided by AP. It then removes
controllers/NEs based on what is defined in the exclusion list. The remaining
controllers/NEs become the part of the network that will be managed by the
NDS server.
Redundant Partitioned NDS server - AP federation

Figure 9-2 on page 9-3 shows a hybrid AP federation, where two Partitioned
NDS servers have been deployed. This deployment balances the load of
connection management tasks across portions of a larger network. However,
no redundancy exists for the scenario where one of the NDS servers fails.
Turning this into a resilient setup can be accomplished by simply adding two
additional platforms. The two new platforms must be configured exactly the
same way as the existing two NDS server platforms.
Attention: In Redundant Partitioned NDS server deployments, the first set

of NDS servers communicate with each other. The second set of NDS
servers communicate with each other. But NDS servers in the first set do not
communicate with NDS servers in the second set. Also, two resilient sets of
OSP clients must be deployed. The first set will talk to the first set of NDS
servers. The second set will talk to the second set of NDS servers.

Comparing Options for OSP Deployments on AP systems

Table 9-1 on page 9-5 compares the different deployment options described
in the previous sections. It also summarizes the advantages and
disadvantages of each one.
Table 9-1
Comparison of NDS server deployment options
Single NDS Redundant Partitioned NDS server Redundant Partitioned

server NDS server NDS server
AP (where All NEs in the All NEs in the All NEs in the network All NEs in the network
NDS server network network (either (either Direct or Indirect (either Direct or Indirect
is installed) (either Direct or Direct or Indirect connection to controller) connection to controller)
manages Indirect connection to
NEs... connection to controller)
controller)
Number of 1 2 2 or more NDS servers • 2 groups

NDS • 2 or more NDS servers
servers per group
NDS One NDS server Each NDS Each NDS server Each NDS server
servers manages all server manages manages a subset of the manages a portion of the
manage NEs in the all NEs in the NEs in the network. NEs in the network. Each
NEs... network network Each NE is managed by NE is managed by only
only one NDS server. two NDS servers.
Comms N/A NDS servers do All NDS servers The first set of NDS
between not communicate with each servers communicate
NDS communicate other with each other. The
servers with each other second set of NDS
servers communicate
with each other. NDS
servers in the first set do
not communicate with
NDS servers in the
second set.


Comparison of NDS server deployment options
Single NDS Redundant Partitioned NDS server Redundant Partitioned

server NDS server NDS server
All OSP All NDS servers All NDS servers All NDS servers Two resilient sets of OSP
clients talk (1) (2) (2 or more) clients must be deployed.
to The first set will talk to the
first set of NDS servers.
The second set will talk to
the second set of NDS
servers.
Advantages • Only 1 • No single point • Can be used in large • Can be used in large
hardware of failure (if networks networks
platform multiple OSP • No single point of failure
required for clients exist) (if multiple OSP clients
NDS server exist)
Dis- • Cannot be • Cannot be • 2 or more hardware • 4 or more hardware

advantages used in large used in large platforms required for platforms required for
networks networks NDS servers NDS servers
• Single point of • 2 hardware • Single point of failure • Additional
failure for platforms for connection administration required
connection required for management tasks (for to balance load of NEs
management NDS servers the subset of NEs between NDS servers
tasks (for all managed by the failed
NEs) NDS server)
• Additional
administration required
to balance load of NEs
between NDS servers

Planning your OSP Deployment on AP systems

The intent of this section is to provide a high-level overview of the steps to take
when planning your OSP deployment. However, this document should be read
in its entirety to ensure a thorough understanding of OSP.
The steps involved

The high-level steps to follow when deploying OSP into a management
network are:
• Identify how Applications Platform (AP) is currently set up in your network
(e.g. no federation, hybrid federation, hierarchical federation).
• Make a graphical representation of the workstations/servers managing
your network. For each platform, identify the role it plays in the federation
(if applicable), as well as all the applications installed on that platform.
• Decide whether you want/need:
— Single NDS server
— Redundant NDS servers
— Partitioned NDS servers
— Redundant Partitioned NDS servers
• Review the examples of OSP deployments discussed in this chapter.
• Using the examples discussed in this chapter as a guideline, determine:
— which platform the NDS server(s) will be installed on
— whether the NDS server(s) will have a view of the full network, or will
be partitioned (if they are partitioned you must determine how the NEs
will be balanced between the NDS servers)
— which platforms the OSP client will be installed on
— which NDS servers will be configured to talk to each other (depending
on whether this is a Redundant NDS server, Partitioned NDS server,
or Redundant Partitioned NDS server deployment)
— which NDS servers each OSP client will be configured to talk to (if this
is a Redundant Partitioned NDS server deployment)


OneControl Unified Management System
Engineering Guide

All Rights Reserved
Printed in Canada, India, and the United States of America

Release 5.0
Publication: 450-3201-010
Document issue: 11.01
Document release date: August 2015
CONTACT CIENA
For additional information, office locations, and phone numbers, please visit the Ciena web site at
www.ciena.com.
LEGAL NOTICE
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 with out notice.
Any usage in this document of Nortel, Nortel Networks, the Nortel logo, and Globemark now refer to Ciena
Corporation.
All other trademarks are the property of the respective owners.

450-3201-010 (OneControl 5.0 Engineering Guide) 11.01

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

450-3201-010 (OneControl 5.0 Engineering Guide) 11.01

Uploaded by

Copyright:

Available Formats

OneControl Unified Management System

450-3201-010 - Standard Issue 11.01

Ciena® Confidential and Proprietary

OneControl Unified Management System Engineering Guide

OneControl Unified Management System Engineering Guide

OneControl Unified Management System Engineering Guide

OneControl Unified Management System Engineering Guide

OneControl Unified Management System Engineering Guide

About this document xi

Introduction to OneControl 5.0 1-1

Deployment configurations 2-1

Geographical redundancy 3-1

Network sizing and engineering considerations 4-1

OneControl Unified Management System Engineering Guide

Choose a hardware platform 4-4

Platform requirements 5-1

Port requirements 6-1

OneControl Unified Management System Engineering Guide

Ports for 5410/5430 NEs 6-23

Ordering information 7-1

Appendix A - AP platform requirements & engineering

OneControl Unified Management System Engineering Guide

Engineering considerations 8-13

Appendix B - OSP deployments on AP systems 9-1

OneControl Unified Management System Engineering Guide

About this document 0

This document describes the deployment options and engineering guidelines

Audience for this document

OneControl Unified Management System Engineering Guide

Technical support and information

Emergency technical support

Ciena provides emergency technical support for OneControl customers who

Attention: For the period covered by the support contract, access to

Issues considered critical include:

OneControl Unified Management System Engineering Guide

• issues causing the loss of network visibility or loss of fault management

Regular technical support

OneControl Product Services

The services include:

OneControl Unified Management System Engineering Guide

OneControl Unified Management System Engineering Guide

Introduction to OneControl 5.0 1-

The following software products may also be used in conjunction with

OneControl Unified Management System Engineering Guide

OneControl high level architecture

OneControl Unified Management System Engineering Guide

Supported/Integrated Element Management Systems

Ethernet Services Manager (ESM)

The ESM is a comprehensive suite of integrated software tools built on a low

Supported network element releases

Upgrades and migrations

OneControl Unified Management System Engineering Guide

For existing customers currently running a version of OneControl older than

Attention: Operating system changes/upgrades are not supported for

Attention: The OneControl features/licenses present before and after an

In this scenario, two separate license files should be generated. First

See OneControl Installation Part 1, 450-3201-201 for details on license files,

OneControl Unified Management System Engineering Guide

Attention: When OneControl 5.0 is used with an Oracle database, the

Some previous releases of OneControl used Oracle database software

See OneControl Installation Part 1, 450-3201-201 for details on upgrades.

Attention: OneControl 5.0 introduces a new paradigm for provisioning and

When upgrading to OneControl 5.0, customers currently using WSM should