450-3251-201 (OneControl R5.0 OSP Installation and Configuration) 07.01

OneControl Unified Management System
Optical Service Provisioner
Installation and Configuration Guide

Release 5.0
Whats inside...
Installation and upgrade
Configuration
Uninstallation and troubleshooting
450-3251-201 - Standard Issue 07.01

August 2015
Copyright 2013-2015 Ciena Corporation. All rights reserved.
LEGAL NOTICES
THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA
CORPORATION AND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE
OR DISCLOSE ITS CONTENTS, OR TO MANUFACTURE, USE, OR SELL ANYTHING THAT IT MAY DESCRIBE.
REPRODUCTION, DISCLOSURE, OR USE IN WHOLE OR IN PART WITHOUT THE SPECIFIC WRITTEN
AUTHORIZATION OF CIENA CORPORATION IS STRICTLY FORBIDDEN.
EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS
COMPLETE AND ACCURATE AT THE TIME OF PUBLISHING; HOWEVER, THE INFORMATION CONTAINED IN
THIS DOCUMENT IS SUBJECT TO CHANGE.
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed
to in writing CIENA PROVIDES THIS DOCUMENT AS IS WITHOUT WARRANTY OR CONDITION OF ANY
KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to
change without notice.
Copyright 2013-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,

and Africa
800-CIENA-24-7 (800-2436-2247)
In Asia-Pacific
800-CIENA-24-7 (800-2436-2247)
+81-3-6367-3989
+44-207-012-5508
+91-124-4340-600
In Caribbean and Latin
America
Sales and General Information
800-CIENA-24-7 (800-2436-2247)
410-865-4944 (USA)
410-694-5700
E-mail: sales@ciena.com
In North America
410-694-5700 or 800-207-3714
In Europe
+44-207-012-5500 (UK)
In Asia
+81-3-3248-4680 (Japan)
In India
+91-124-434-0500
In Latin America
011-5255-1719-0220 (Mexico City) E-mail: sales@ciena.com
Training
877-CIENA-TD (243-6283)
or 410-865-8996
E-mail: techtng@ciena.com
For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.
OneControl Unified Management System - OSP

Release 5.0
Copyright 2013-2015 Ciena Corporation

450-3251-201 Standard Issue 07.01
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, reexport, or import Software.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
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.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Publication history
August 2015
Issue 07.01 of the OneControl Unified Management System 5.0 Optical
Service Provisioner Installation and Configuration Guide.
January 2015
August 2014
April 2014
December 2013
July 2013
April 2013

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
vi Publication history

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
vii
Contents
Publication history
About this document
v
ix
1-1
Deployment options 1-1

NDS server and OSP client software components 1-1
Number of NDS server instances 1-2
AP and Manager for 6k, OM5k and CPL views 1-3
Workstation requirements 1-3
Installation of OSP client software 1-3
Installation options 1-3
Resource Allocation tool on an HP platform 1-12
Upgrades 1-13
List of procedures
1-1
Installing or upgrading OSP software on an HP platform 1-14
1-2
Installing OSP software on a Linux or Solaris platform 1-34
1-3
Installing the OSP online help on an HP platform 1-39
Configuration
2-1
List of procedures
2-1
Configuring OSP access privileges for Manager for 6k, OM5k and CPL users
on a Linux or Solaris platform 2-2
2-2
Editing OSP configuration settings on an HP platform 2-4
2-3
Editing OSP configuration settings on a Linux or Solaris platform 2-15
2-4
Editing OSP configuration properties on Windows platform 2-25
2-5
Configuring OSP for resiliency on Linux or Solaris platform 2-34
2-6
Configuring the NEs/controllers for an NDS server on an HP platform 2-37
2-7
Starting, stopping, restarting, or displaying status of the OSP components on
an HP platform 2-45
3-1
List of procedures
3-1
Uninstalling OSP server software from an HP platform 3-2
3-2
Uninstalling OSP server software from a Linux or Solaris platform 3-4
3-3
Displaying the OSP components status 3-5

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
viii Contents
3-4
3-5
3-6
3-7
Displaying the version of the installed OSP software on an HP platform 3-6

Displaying the version of the installed OSP software on a Linux or Solaris
platform 3-7
Displaying the current OSP configuration settings 3-9
Displaying log files for OSP software installation and uninstallation 3-13

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
ix
About this document
This document describes the installation and configuration of the OneControl

Optical Service Provisioner (OSP) software.
ATTENTION
Check for updated versions of this document on the Ciena portal (for
download instructions, see Documentation download on page ix).
ATTENTION
Within this document, the term "Manager for 6k, OM5k and CPL" should be
interpreted to mean OneControl Manager for the following network elements:
ActivFlex 6110 Multiservice Optical Platform (ActivFlex 6110), ActivFlex
6130 Multiservice Optical Platform (ActivFlex 6130), Optical Multiservice
Edge 6150 (OME6150), 6200 Packet-Optical Platform (6200), 6500 PacketOptical Platform (6500), 565/5100/5200 Advanced Services Platform (565/
5100/5200), Optical Metro 5040/5080 (OM5040/5080), and Common
Photonic Layer (CPL).
ATTENTION
Manager for 6k, OM5k and CPL represents the evolution of OMEA;
however, you may still see OMEA in certain commands, menus, and
system prompts. Consider OMEA to mean Manager for 6k, OM5k and
CPL.
Documentation download
You can download OSP documents and other related OneControl documents
from the Ciena portal.
To download a document, perform the following steps:
1
2
3
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 Unified Management System.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
x About this document
4
5
6
Click the required Release.

Find the document you want to download and click the link.
Download the document.
Software download
ATTENTION
Following the installation of the OneControl OSP software, ensure to check
the Ciena portal and apply the latest recommended software patches.
OSP supports the electronic delivery of software. Therefore, you now have the
option to download purchased OSP software from https://portal.ciena.com.
The option to purchase physical DVDs (or CDs, as applicable) 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
2
3
4
5
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 Software tab.
From Browse Available Downloads For: select OneControl.
Find the OSP software or other files you need and click the link.
Download the software file(s) and readme file (if a readme file is present,
it will contain any instructions that might be required).
Ciena Software Key Code Manager

The Ciena Software Key Code Manager provides a secure environment for
managing key codes containing software entitlements. For details about the
Ciena Software Key Code Manager, see OneControl Installation, Part 1, 4503201-201.
Conventions used in this document

Throughout this document you see system information, such as command
strings and prompts and responses, represented in consistent ways.
Command strings
Command strings you enter appear in bold face courier font as in the following
example:
cd /tmp
Note: You must enter the command string exactly as shown, including
spaces, and press Enter, as indicated.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
About this document xi
Variable parameters appear in angle brackets, as in the following example:

mkdir /<directory name>
An explanation of the variable may follow the command string, as in the

following example:
where
<directory name>
is the name of the CD-ROM directory
Prompts and responses from the system

System prompts and responses appear in courier font as in the following
example:
Press Enter to continue.
Directory and path names

Directory and path names appear in courier font as in the following example:
/opt/nortel/omea
Buttons and menu items

Buttons and menu items in the application interface appear in bold face as in
the following example:
Click OK.
In some cases, the user interface supports menu commands and buttons with
equivalent capabilities. In the procedures, we suggest the use of buttons
where they exist. Menu command equivalents have the same or equivalent
name as the button, if you prefer to use them.
Keyboard keys
Keyboard key names appear in bold face as in the following example:
Press Enter.
Window and field names

Names of objects displayed in windows are written as shown on the screen.
Since these expressions can contain several words, all words in the name
begin with capitals.
Results of an action and comments

Results of an action and comments are printed in italic type, as follows:
The window opens.
When a new window or dialog box opens as a result of a procedure step, the
new context is included as follows:
In the Find dialog box, enter a User ID in the Name field.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
xii About this document

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
1-1
1-
This section introduces the deployment options and provides the procedures
required to install the Optical Service Provisioner (OSP). The OneControl
Engineering Guide, 450-3201-010 (see Documentation download on
page ix for details) contains a full treatment of the deployment options. Review
that document before performing the procedures in this section.
You can start the OSP application from the Optical Network Manager
Applications Platform (AP), from the Manager for 6k, OM5k and CPL, or from
OneControl. Therefore, you must install every instance of OSP (server or GUI)
co-resident with an AP, a Manager for 6k, OM5k and CPL, or a OneControl
server.
For details on how to start OSP, see the OneControl Optical Service
Provisioner Standard Operations Guide, 450-3251-028.
The section contains the following topics:
Deployment options on page 1-1
Workstation requirements on page 1-3
Installation of OSP client software on page 1-3
Installation options on page 1-3
Resource Allocation tool on an HP platform on page 1-12
Upgrades on page 1-13
Procedures on page 1-13
Deployment options
Before you begin to install the OSP software, you must understand the
components that are used by OSP and consider the options described in this
section.
NDS server and OSP client software components
The Network Data Server (NDS) is responsible for communicating with

network elements and performing connection management operations. All
topological data is stored in the NDS server which includes data provided

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
1-2 Installation and upgrade
by network elements to the NDS server and topological data entered in

Custom Topology. For larger networks, multiple NDS servers can be
installed, each with a subset of controllers. The NDS server component is
also shared with Network Server Viewer (NSV) and Network View
Manager (NVM).
The NDS server can be installed by the Manager for 6k, OM5k and CPL
on a Manager for 6k, OM5k and CPL co-resident Linux or Solaris
workstation or OSP co-resident with AP on an HP workstation.
Additionally, multiple NDS servers can be configured for redundancy
purposes or for load balancing in large networks.
The OSP GUI functions as a client of the NDS server and supports the
user interface, through which users initiate connection management
requests. If OSP is co-resident with AP, each instance of the OSP GUI
must be installed co-resident with an instance of AP. If OSP is co-resident
with the Manager for 6k, OM5k and CPL, the OSP GUI must be installed
co-resident with an instance of the Manager for 6k, OM5k and CPL or coresident with an instance of AP configured to communicate with the
Manager for 6k, OM5k and CPL server.
The NDS server and OSP GUI can be installed on separate platforms. This
arrangement allows for the deployment of one or more dedicated NDS servers
that minimize the impact on existing management servers. Otherwise, the
NDS server and GUI can be installed co-resident for smaller networks or
where the hardware platform is large enough to support the number of
network elements.
Number of NDS server instances

You can deploy one or multiple instances of the NDS server to manage the
network. Multiple NDS server instances can be used for the following:
Redundancy avoids a loss of capability during a hardware platform failure.
Partitioning allows the deployment of OSP to be scaled into large

networks. You can balance the load of NEs between multiple NDS servers
while still allowing all tasks to be done from one GUI instance (and
topology to be consolidated).
Each NDS server instance is installed on a different AP or Manager for 6k,

OM5k and CPL platform. Each NDS server manages the portion of the
network to which access is provided by the AP or Manager for 6k, OM5k and
CPL operating on the same workstation (except in the case of partitioned NDS
servers, where only a subset of that portion is used).
When OSP is co-resident with the Manager for 6k, OM5k and CPL, only the
resilient setup (two servers) is supported.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Installation and upgrade 1-3
Note: For deployment of multiple NDS servers, make sure that consistent
entries for all the NDS servers are placed into each others /etc/hosts
file.
AP and Manager for 6k, OM5k and CPL views

Since OSP relies on AP or the Manager for 6k, OM5k and CPL for its view of
the network, you must perform the following actions:
On each node targeted for NDS server deployment, the AP or Manager for
6k, OM5k and CPL user interface must have a view of the network that the
NDS server should manage.
On each node targeted for OSP client GUI deployment, the AP or

Manager for 6k, OM5k and CPL user interface must have a view of the
network that OSP client GUI users need access to. When installing the
OSP client GUI, all NDS servers that the OSP client GUI needs to
communicate with must be identified.
Workstation requirements
Workstation requirements are proportional to the size of the network
managed. Specific requirements are provided in the OneControl Engineering
Guide, 450-3201-010 (see Documentation download on page ix for details).
ATTENTION
If you are installing the OSP software on the Solaris platform, make sure that
your root user password does not contain the equal sign (=).
Installation of OSP client software

When you perform the installation of the OneControl client software, the
installer also installs the OSP client. For details on the installation of the
OneControl client software, see the OneControl Installation, Part 1, 450-3201201.
Installation options
Table 1-1 on page 1-4 lists the installation prompts that appear when installing
the Optical Service Provisioner software and describes each option. (During
the installation or upgrade, prompts not applicable to the particular installation
or upgrade do not appear.)
It is important before beginning any installation that you decide which
components are to go on which server. Once you have made the decisions,
you can print Table 1-1 on page 1-4 for each workstation that will have either
the NDS server or GUI installed. A completed table serves as a useful
reference tool and simplifies the task of installing the OSP.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Table 1-1
OSP installation options
Enter the workstation hostname here:
OSP install question
Description
User choice
Selecting the installation type The NDS server communicates with network
element controllers and performs operations such
The options available are:
as adding, deleting, editing, and querying
the NDS server, or the GUI, connections, maintaining the status of NEs, and
or both on HP
consolidating topologies.
Only GUI on Linux or Solaris The GUI is a client graphical user interface with
since the NDS server is
which users interact to manage connections within
already installed by Manager the network. Depending on the intended use of the
for 6k, OM5k and CPL
workstation, you can install one or both of these
components.
The GUI does not need to reside on the same
workstation as the NDS server. The GUI can be
installed without the NDS server component on the
highest level of a hierarchical federation.
The NDS server can be installed without the GUI in
a network where the NDS server was purchased
with NSV. It can also be installed on the lowest
level of a hierarchical federation.
Selecting the preferred
standard for the display of
connection rates for the OSP
GUI
You can configure the OSP GUI to show

connection rates in either SONET or SDH formats.
This parameter is only required if the GUI is
installed on the workstation.
This parameter sets the default value for the GUI,
but you can change the preference on a persession basis.
Selecting the preferred

standard for the display of
connection rates for the NDS
server
This parameter allows server audit logs to display

connection rates in SONET or SDH format.
Note: Depending on the

installation, this question can
appear differently.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Table 1-1
OSP installation options (continued)
Description
User choice
Selecting the preferred port

naming type
OSP can be configured to show port names in

either a universal format or a format specific to
network element types.
If the NDS server is installed, this parameter
determines the display of port names in the NDS
server audit logs.
If the GUI is installed, this parameter sets the
default value, but you can change the preference
on a per-session basis.
Entering the maximum

This is the maximum number of GUI instances that
number of OSP GUI instances can run concurrently on the workstation on which
the software has been installed. The maximum
(on HP only)
number depends on the capabilities of the
workstation and the number of other processes
that are also running on this workstation. For the
recommended engineering limits, see the
OneControl Engineering Guide, 450-3201-010.
Entering the maximum
connection ID length
This is the maximum number of characters allowed

in the connection ID. The default is 64. The
configurable range is 15 to 99.
Is blank connection ID
allowed?
The GUI can be configured for handling paths with

blank connection IDs. The possible answers and
the resulting GUI behavior are as follows:
y - This option allows the creation of new paths with
blank connection IDs and removal of the
connection ID from existing paths (set to blank).
n - This option means new paths cannot have a
blank connection ID and existing connection IDs
cannot be edited to a blank value. However, you
can still retrieve blank connection IDs from the
network. For broadband (BB) rates, the Connection
ID can be left blank irrespective of the OSP blank
connection ID setting.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Table 1-1
Description
User choice
Selecting the GUI deployment The GUI must communicate with at least one NDS
server, but can communicate with any number of
type
servers. In the case of multiple servers, the GUI
can be configured to communicate with the NDS
Note: Select Single only if the server locally along with NDS servers on other
GUI will be communicating
workstations. Another option is to have only the
with only one NDS server
GUI on the workstation that communicates with
located on the same
NDS servers on other workstations. The options
are:
workstation.
Single - Select this option (also known as the
local server) if the GUI and NDS server are coresident on this workstation. You can just choose
Single and the GUI will be installed and configured
automatically with the NDS server on the same
workstation.
Multiple - Select this option if the GUI
communicates with one or more NDS servers
located on different (remote) workstations.
Remote NDS servers are specified by their IP
address in the prompts following the selection of
the Multiple option.
For multiple NDS server deployments, this menu
gives you the options to add and remove remote
servers in the local configuration and also to list the
configured set of remote servers. This function
does not ensure that those servers are installed
Note: If you have decided that and properly configured themselves.
this GUI will communicate with
For these NDS servers to work together, you must
other servers, the servers
configure each installation with a list of all the
should also be listed to speed remote servers.
up the process of entering
If the deployment is a single NDS server, all GUIs
them.
should enroll the NDS server regardless of where
they are installed. In a multiple server deployment,
all servers must be enrolled in the GUI. Take into
account load balancing when configuring the GUIs.
The GUI client list should be constructed in a way
that each server does not get overloaded with
client requests.
Identifying the NDS servers
that the GUI communicates
with

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Table 1-1
Description
User choice
The user interface must communicate with at least

one Manager for 6k, OM5k and CPL server, but
can communicate with multiple servers. In the case
of multiple servers, the user interface can be
configured to communicate with the Manager for
6k, OM5k and CPL server locally along with
Note: Select Single only if the Manager for 6k, OM5k and CPL servers on other
GUI will be communicating
workstations. The options are:
with only one Manager for 6k,
OM5k and CPL server located
local server) if the GUI and Manager for 6k, OM5k
on the same workstation.
and CPL server are co-resident on this workstation.
Selecting the Manager for 6k,
OM5k and CPL server
deployment type (on Linux or
Solaris only)
You can just choose Single and the GUI will be

installed and configured automatically with the
Manager for 6k, OM5k and CPL server on the
same workstation.
Multiple - Select this option if the GUI
communicates with two Manager for 6k, OM5k and
CPL servers located on different workstation but
configured with resiliency between them.
Peer Manager for 6k, OM5k and CPL server is
specified by their IP address in the prompts
following the selection of the Multiple option.
For multiple Manager for 6k, OM5k and CPL server

deployments, this menu gives you the options to
add and remove remote servers in the local
configuration and also to list the configured set of
Note: This box applies if you remote servers. This function does not ensure that
those servers are installed and properly configured
selected Multiple in the
themselves.
previous box.
For these Manager for 6k, OM5k and CPL servers
to work together, you must configure each
installation with a list of all the remote servers.
Identifying the Manager for 6k,
OM5k and CPL servers that
the GUI communicates with
(on Linux or Solaris only)

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Table 1-1
Description
User choice
Does the Network Data Server The server can start learning the network based on
use the default controller list the default controller list as soon as the installation
(on HP only)?
or upgrade is completed, or it can postpone
learning the network until additional configuration
steps are carried out.
The options are:
y - Start learning the network as soon as the
installation or upgrade is finished.
n - Postpone learning the network until additional
configuration steps are performed. (For example,
NEs are not listed in OSP GUI, as soon as the
installation and upgrade is complete.)
To display the list of NEs managed by OSP after
the installation and upgrade is complete, run the
resourceTool to turn the precaching on.
If you are balancing the load for multiple servers,
you must configure the exclusion list after the
installation of the server software. Refer to
Resource Allocation tool on an HP platform on
page 1-12 and, if required, fill out Table 1-2 on page
1-12 for every NDS server.
Selecting the NDS server
The local NDS server can be configured to
deployment type (on HP only) communicate with other remote servers. The
options are:
local server) if the NDS server being installed on
this workstation does not communicate with any
other NDS server.
Multiple - Select this option if the local NDS server
communicates with other remote NDS servers.
Remote NDS servers are specified by the IP
address of the workstation on which they are
installed in the prompts that follow the selection of
the Multiple option for this prompt.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Table 1-1
Description
User choice
Identifying other servers

(NDS) that this server will
communicate with (on HP
only)
In any deployment, there can be a number of NDS

servers configured.
For these servers to work together, you must

configure each installation with a list of all the
Note: This box applies if you remote servers.
This menu gives you the option to add and remove
previous box.
remote servers in the local configuration, and also
to list the configured set of remote servers.
This function does not ensure that those servers
are installed and properly configured.
The list of remote servers that the GUI
communicates with is independent of the list of
remote servers that the local server communicates
with. The two lists must be managed separately.
If you are deploying the NDS server and GUI on the
same workstation and you do not want them to
communicate with other servers, you can continue
with the installation without configuring any
additional servers.
Selecting the span server
deployment type (on Linux or
Solaris only)
The local NDS server can be configured to

communicate with other remote Manager for 6k,
OM5k and CPL servers. The options are:
local server) if the NDS server being installed on
this workstation communicates only with the local
Manager for 6k, OM5k and CPL server. You can
just select Single and the NDS will be installed and
configured automatically with the Manager for 6k,
OM5k and CPL server on the same workstation.
Multiple - Select this option if the local NDS server
communicates with multiple Manager for 6k, OM5k
and CPL servers located on different (remote)
workstations. Only resilient setup (2 servers) is
supported.
Remote Manager for 6k, OM5k and CPL servers
are specified by the IP address of the workstation
on which they are installed in the prompts that
follow the selection of the Multiple option for this
prompt.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Table 1-1
Description
User choice
For multiple Manager for 6k, OM5k and CPL server

deployments, this menu gives you the options to
add and remove remote servers in the local
configuration and also to list the configured set of
remote servers. This function does not ensure that
Note: This box applies if you those servers are installed and properly configured
themselves.
For these Manager for 6k, OM5k and CPL servers
previous box.
to work together, you must configure each
installation with a list of all the remote servers.
Identifying other Manager for
6k, OM5k and CPL servers
that this server will
communicate with (on Linux or
Solaris only)
The preferred server is the master of a group of

servers that communicate with each other. It is the
first server to be queried for information about the
Note: This prompt appears
network being managed. Defining a preferred
on HP only. On Linux or
server in multi-server deployments improves
Solaris, the default is yes. You
performance.
can change the value after
installation by editing the OSP Only one master can exist in a group of servers. If
multiple servers are defined as the preferred
configuration settings.
server, the servers arbitrarily demote themselves
until only one preferred server remains in the
system.
Is this the preferred server
(NDS)?
Enable the local custom

topology server
OSP can be configured to use topology

information manually entered in the custom
topology database.
Custom topology must be enabled if the topology
cannot be learned from the network and must be
entered manually. (See the OneControl OSP and
Layer 1 NSV Custom Topology User Guide, 4503251-189.)
You can have up to two custom topology servers
enabled in your network.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Table 1-1
Description
User choice
Set the IP address of the

preferred custom topology
server
If you enable custom topology in your network, you

must define the IP address for the preferred
custom topology server. The preferred custom
topology server should be the same on all the NDS
servers.
The IP address, when set, is always displayed
when you are prompted to add a new address. If
not, the address is shown as none.
If the IP address is the localhost, (localhost) is
displayed after the IP address. To specify the
localhost, you have the option of entering the term
localhost (or the first letter of localhost) instead
the IP address.
Set the IP address of the

alternate custom topology
server (on HP only)
You can define an alternate custom topology

server for redundancy. If you do, the alternate
custom topology server should be the same on all
the NDS servers.
You can only provision the alternate server when
the preferred server has been provisioned.
The IP address, when set, is always displayed
when you are prompted to add a new address. If
not, the address is shown as none. If both the
preferred and alternate IP addresses are set and
the preferred server IP address is set to none, the
alternate server IP address is also set to none.
If the IP address is the localhost, (localhost) is
displayed after the IP address. To specify the
localhost, you have the option of entering the term
localhost (or the first letter of localhost) instead
the IP address.
Note: You can make changes to the settings after the installation by following Procedure 2-2,Editing
OSP configuration settings on an HP platform on page 2-4 or Procedure 2-3,Editing OSP configuration
settings on a Linux or Solaris platform on page 2-15.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Resource Allocation tool on an HP platform

The Resource Allocation tool is used for the multiple (partitioned) NDS server
deployments. The tool provides the flexibility to balance the load of managing
the network across multiple NDS servers. The tool allows each NDS server to
exclude NEs or controllers from being managed by that NDS server. The
exclusion list should be configured for every NDS server part of a partitioned
NDS server deployment. Print and complete a copy of Table 1-2 on page 1-12
for every NDS server to decide how to exclude NEs and controllers. Then
proceed to Procedure 2-6, Configuring the NEs/controllers for an NDS server
on an HP platform on page 2-37.
Table 1-2
NDS server exclusion list
Enter the NDS server hostname here:
Exclusion list items
Enter the IP address, software release, NE

ID, or NE software release (as applicable)
Excluding a controller by its IP address (from available

controllers)
Excluding a controller by its IP address (entered

manually)
Excluding a controller by its software release (from

available controllers)
Excluding an NE using its controller IP address and its

NE ID (from available controllers)
Excluding an NE using its controller IP address and its

NE ID (entered manually)
Excluding NEs using the NE software release (from

available NEs)

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Upgrades
ATTENTION
Prior to performing an OSP upgrade, you must first review and follow the
Upgrades procedure sequence in the Upgrades chapter of the
OneControl 5.0 Installation, Part 1, 450- 3201-201.
The following upgrade paths are supported:
OneControl 4.0 (with latest patches) to 5.0

Note: With the upgrade from OneControl 4.0. 4.1, or 4.2 to
OneControl 5.0, you are also upgrading OSP from 13.0, 13.1, or 13.2 to
14.0 respectively.
Procedures
This section contains the following procedures:
Procedure 1-1, Installing or upgrading OSP software on an HP platform

on page 1-14
Procedure 1-2, Installing OSP software on a Linux or Solaris platform on

page 1-34
Procedure 1-3, Installing the OSP online help on an HP platform on page

1-39

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Procedure 1-1
Installing or upgrading OSP software on an HP
platform
Use this procedure to install or upgrade the OSP software on an HP platform
with the ONM Applications Platform (AP).
Note: For information on the number of OSP software instances you can
deploy in an AP federation, see the OneControl Engineering Guide, 4503201-010 (see Documentation download on page ix).
ATTENTION
Prior to performing an OSP upgrade, you must review and follow the
Upgrades procedure sequence in the Upgrades chapter of the
OneControl 5.0 Installation, Part 1, 450- 3201-201.
Each prompt presents a default choice (a number that represents a line in a
list) that you can select by pressing Enter. In addition:
You can display help by entering ?.
At most prompts, you can abort the installation or upgrade by entering the
command abort. No further action is required.
The actual prompts displayed can differ from the examples shown in this
procedure, depending on the operation and options.
Note: If the system aborts the installation because prerequisites were not
satisfied, you must resolve the underlying problem before beginning the
installation again. If an upgrade is aborted before the new load is
completely installed or if the old load cannot be removed, call Ciena
Technical Support.
CAUTION
Risk of installation failure
If you are installing the OSP software after a successful

uninstallation of the software, make sure to leave a gap of at
least five minutes between the end of the uninstallation and the
start of the new installation.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Procedure 1-1 (continued)
Installing or upgrading OSP software on an HP platform
CAUTION
Risk of database corruption
Before you reboot or shut down the server, stop the OSP
application, ensure that none of MySQL processes are running
on the server, and then wait two minutes. If you do not follow
this sequence of actions, you can cause the corruption of the
database. You may not be able to perform any operation on a
corrupted database.
Requirements
Before you perform this procedure, you must
have the OSP Software CD. Software download from the Ciena portal is
not supported on an HP platform
be able to log in to the workstation using the root user account
have AP 11.0 Patch A installed
complete Table 1-1 on page 1-4 and, if required, Table 1-2 on page 1-12
make sure consistent entries for all the NDS servers are placed into each
others /etc/hosts file, if your deployment is for multiple NDS servers
apply the latest available patches. For information about downloading

patches, see the OneControl Engineering Guide, 450-3201-010.
make sure the Custom Topology server is running and is configured

correctly, if Custom Topology data exists on the server
export Custom Topology data, if Custom Topology is installed and used by

OSP. For information about how to export Custom Topology data, see the
OneControl OSP and Layer 1 NSV Custom Topology User Guide, 4503251-189.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Log in to the workstation where you plan to install the OSP software using the
root user ID and password.
Verify that the Applications Platform (AP) software has been installed on the
workstation by entering:
ls -d /opt/nortel/OnmAP11
The following response indicates that the AP software has been installed:
/opt/nortel/<installed software>
where
<installed software>
is the software that is installed, for example:

OnmAP11 for AP 11
If the response is anything else, see the Applications Platform Installation and
Administration Guide, 450-3101-201.
Starting the software installation
3
Insert the CD containing the OSP software into the CD drive.
Create the directory in which the CD device will be mounted by entering:

mkdir /cdrom
A message may inform you that the directory already exists.
Determine the name of the CD device by entering:

ls /dev/dsk
A list of device names appears.
Record the name of the CD device as <device name>.
(An example device name is c0t0d0.)
Mount the CD device by entering:

mount /dev/dsk/<device name> /cdrom
Change to the directory in which you mounted the CD by entering:

cd /cdrom
Start the OSP software installation by entering:

./osp_install
The system indicates the progress of the installation.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
If
Then the system displays the following prompt
there is no OSP GUI and

NDS server already
installed on this
workstation
Installation begins. This may take

some time...
Reading system settings. Please
wait...
The default settings are:
an OSP GUI is already

installed on this
workstation without an
NDS server
Installation begins. This may take

some time...
Reading system settings. Please
wait ...
The settings that were used in the
old load are:
an NDS server is already

installed on this
workstation with or without
an OSP GUI
Upgrade begins. This may take some

time...
Please close all local and remote
GUI sessions connected to this
server before proceeding. Failure
to close all GUIs will result in
unexpected or erratic behaviour of
the GUIs.
Do not start the Data Export Tool
during an upgrade.
Do not start the
topology_provisioner during an
upgrade.
Do you wish to continue [y/n]?
10
Enter y to continue.
The following message appears:
Reading system settings. Please wait ...
The settings that were used in the old load are:
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Selecting the installation type

11
The existing settings appear (for an upgrade) or the default settings appear
(for a new installation):
The default settings are:
========================================================
Components to install:
Install GUI:
Install server:
yes
yes
GUI
GUI
GUI
GUI
GUI
SONET
NE
10
64
no
preferred standard:
preferred port naming type:
maximum instances:
maximum connection ID length
blank connection ID allowed:
Server preferred standard:

Server preferred port naming type:
Server uses default controller list:
Local server is the preferred server:
SONET
NE
yes
yes
Local custom topology server:

Preferred custom topology server:
Alternate custom topology server:
disabled
none
none
Local OSP GUI communicates with the following servers:

43.2.3.5 (localhost)
Local server communicates with the following remote
servers:
None.
========================================================
Do you accept these settings [y/n, abort, ? for help,
default=y]?
If you want to
Then
keep the settings listed
enter y and go to step 37
change the settings listed
enter n and continue
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
12
The following menu appears:

Select the <installation or upgrade> type from the
following options:
[1] Both server and graphical user interface
[2] Graphical user interface only (no server)
[3] Server only (no graphical user interface)
Enter [1-3, abort, ? for help, default=1]
where
<installation or upgrade>
is the type related to step 9
If you want to install (or upgrade)
Then
both NDS server and GUI
enter 1 and continue
GUI only
NDS server only
Selecting the preferred standard for the display of connection rates, statuses, and payloads
13

Select the preferred standard for <installation type>
from the following options:
[1] SONET
[2] SDH
Enter [1-2, abort, ? for help, default=1]:
where
<installation type>
is the option you selected in step 12
If you want to use
Then
SONET formats
SDH formats

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Selecting a port format

14

Select the preferred port format type for <installation
type> from the following options:
[1] NE-type specific
[2] Universal
where
<installation type>
is the option you selected in step 12
If you want to
Then
show port names in NE type-specific format
show port names in universal format
Note: In an installation that contains both NDS server and GUI components,
you can set the connection rate display and port name parameters to different
values for each component after the installation (see Procedure 2-2, Editing
OSP configuration settings on an HP platform on page 2-4).
15
Select your next step.

If you are installing
Then go to
both an NDS server and GUI
step 16
the GUI only
step 16
an NDS server only
step 25
Selecting the maximum GUI instances

16

Enter the maximum number of GUI instances
[1-24, abort, ? for help, default=10]:
Enter the maximum number of concurrent GUI sessions. This value must be
set as recommended in the engineering limits detailed in the OneControl
Engineering Guide, 450-3201-010.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Selecting the maximum connection ID length

17

Enter the maximum length of connection ID
[15-99, abort, ? for help, default=64]:
Enter the maximum connection ID length. This value must be set as
recommended in the engineering limits detailed in the OneControl
Engineering Guide, 450-3201-010.
Selecting whether blank connection ID is allowed

18

Is blank connection ID allowed [y/n, abort, ? for help,
default=n]
If you want
Then
to allow blank connection IDs
enter y and continue
to not allow blank connection IDs
Selecting the GUI deployment type

19

Select the GUI deployment type from the following options:
[1] Single (local) server
[2] Multiple servers
If you plan to deploy
Then
a single NDS server
enter 1 and go to step 25
multiple NDS servers
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Identifying NDS servers that the GUI communicates with

20

Select an action from the following options:
[1]
[2]
[3]
[4]
Continue with installation

Add server
Remove server
List all servers

Now identify all other NDS servers with which the GUI will communicate.
The installation software does not ensure that the identified NDS servers are
installed and properly configured (only that a workstation is defined at the
specified IP address). Therefore, at this time you can identify all workstations
that will eventually be NDS servers in the configuration, if the workstation is
operational at the specified IP address.
Note: For an upgrade, the [1] selection in the menu shows Continue with
upgrade.
If you want to
Then
add an NDS server to the list
remove an NDS server from the list
display the list of NDS servers
continue the installation with the current list of

NDS servers
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Adding an NDS server to the list

21

Enter the address of the server
['q' to return to the menu]:
Enter the IP address of the remote server. The installation software validates
the address. If the following message appears, the address has been
validated and the remote server has been added to the local configuration:
Validating address... done.
Server 43.2.3.5 added.
If the following message appears, then the address has not been added:
Validating address... failed.
<error message>
where
<error message> provides a description of the cause of the failure
The workstation must be physically connected and configured on the LAN
and IP address updated in the /etc/hosts file using the root user on both
servers for the script to validate the address. If not on the LAN, the
workstation must be added (after the OSP software installation), using
Procedure 2-2, Editing OSP configuration settings on an HP platform on
page 2-4.
Note 1: The IP address must be used. Do not use hostnames or aliases.
Note 2: If the addition failed, verify that you have the correct IP address and
try to add the server again.
Return to step 20.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Removing an NDS server from the list

22

Select a server to remove:
[0] Return to server menu
[1] 43.2.3.4
[2] 45.2.3.5 (localhost)
Enter [0-1, ? for help]:
The menu lists the remote servers that you have previously identified (for
example, 43.2.3.4). Enter the number of the server you wish to remove.
Note: The localhost cannot be removed from the list.
Server removed.
Return to step 20.
Listing all identified NDS servers

23
A list of the NDS servers that you have identified appears. These are the NDS
servers with which the local GUI communicates. The following is an example:
The local GUI communicates with the following servers:
[1] 43.2.3.4
[2] 45.2.3.5 (localhost)
Return to step 20.
24

If you are installing
Then go to
NDS server with or without a GUI on the same workstation step 25

only the GUI on this workstation
step 35
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
25

Does the server use the default controller list
[y/n, abort, ? for help, default=y]
If
Then
you are not using the default controller list
Once the installation is complete, perform

Procedure 2-6, Configuring the NEs/controllers for
an NDS server on an HP platform on page 2-37.
you are using the default controller list
Selecting the server deployment options

26
The remote NDS server IP addresses are provisioned and managed in a

similar manner to the GUI that needs to communicate with remote servers.
The following prompt appears:
Select the server deployment type from the following
options:
[1] Single (local) server
[2] Multiple servers
If you want to deploy
Then
a single NDS server
enter 1 and go to
step 31
multiple NDS servers
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Identifying other NDS servers

27

[1]
[2]
[3]
[4]
Continue with installation

Add server
Remove server
List all servers

The installation software does not ensure that the identified NDS servers are
installed and properly configured (only that a workstation is defined at the
specified IP address). Therefore, at this time you can identify all workstations
that will eventually be NDS servers in the configuration, if the workstation is
defined at the specified IP address.
Note 1: For an upgrade, the [1] selection in the menu shows Continue with
upgrade.
Note 2: When configuring the remote servers that communicate with local
NDS servers, you only enter the addresses of the remote servers. The IP
address of the localhost is not required and therefore cannot be entered.
If you want to
Then
continue the installation with the current list of

NDS servers
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action

28

Enter the address of the server
['q' to return to the menu]:
Enter the IP address of the remote NDS server. The installation software
validates the address. If the following message appears, the address has
been validated and the remote server has been added to the local
configuration:
If the following message appears, the address has not been added:
<error message>
where
servers for the script to validate the IP address. If not on the LAN, the
page 2-4.
Return to step 27.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action

29

[1] 45.2.3.2
[2] 45.3.66.5
The menu lists the remote NDS servers you have previously identified (for
example, 45.2.3.2). Enter the number of the NDS server you wish to remove.
Server removed.
Return to step 27.

30
A list of the NDS servers that you have identified appears. The following is an
example:
The local server communicates with the following servers:
[1] 45.2.3.2
[2] 45.3.66.5
Return to step 27.
Defining the preferred NDS server

31
If a list of IP addresses for NDS servers has not been configured, go to step
32. If the list of NDS server IP addresses has been provisioned, you are
prompted for whether the local server is to be the preferred server:
Is the local server a preferred server
[y/n, abort, ? for help, default=y]:
There can only be one preferred server in the network. If another NDS server
in your network is designated as the preferred server, select n. Otherwise,
select y (which defines the local server as the preferred server) and continue
with step 32.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Enabling/disabling the custom topology server

32

Should custom topology be enabled on this workstation
[y/n, abort, ? for help, default=n]:
If you want to
Then
enable the custom topology server on this

workstation
disable the custom topology server on this

workstation
Defining the preferred custom topology server

33

Enter preferred topology server IP address
[IP, localhost, none, abort, ? for help, default=none]:
Enter the IP address of the preferred custom topology server. The installation
software validates the address. Alternatively, enter l for localhost and it will
automatically pick up the local host's IP address.
If the following message appears, the address has been validated and the
remote server has been added to the local configuration:
Validating address...done.
Preferred topology server set to 45.2.3.5.
<error message>
where
page 2-4.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Defining the alternate custom topology server

34
The following message will appear only if an IP address other than none has
been specified for the preferred topology server:
Enter alternate topology server IP address
[IP, localhost, none, abort, ? for help, default=none]:
Enter the IP address of the alternate custom topology server. The installation
software validates the address. Alternatively, enter l for localhost and it will
remote server has been added to the local configuration:
Validating address...done.
Alternate topology server set to 43.1.2.3.
<error message>
where
page 2-4.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Completing the installation or upgrade

35
The settings are displayed and a prompt confirms that they are to be used.
The following is an example when both the GUI and NDS server are installed
or upgraded.
========================================================
Components to install:
Install GUI:
Install server:
yes
yes
GUI
GUI
GUI
GUI
GUI
SONET
NE
10
64
no
preferred standard:
maximum instances:
maximum connection ID length:

Server uses default controller list:
Local server is the preferred server:
SONET
NE
no
yes

enabled
Preferred custom topology server: 45.11.22.86 (localhost)
Alternate custom topology server: none
45.11.22.86 (localhost)
servers:
None.
========================================================
Do you accept these settings [y/n, abort, ? for help,
default=y]?
36
If you enter n at this point, you must answer all the questions again. Enter y
and go to step 37.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
37
The tasks that will be performed are listed and confirmation is requested.
Similar messages appear if this is a new installation of the NDS server with
the GUI. Some lines may not appear if the NDS server or GUI is not installed
or if the custom topology server is not enabled.
========================================================
The following actions will be performed:
* The 3rd party software will be installed and configured.
* The 3rd party software will be started.
*
*
*
*
*
The
The
The
The
The
new server will

new GUI will be
custom topology
new server will
custom topology
be installed and configured.

installed and configured.
will be installed and configured.
be started.
server will be started.
========================================================
Do you wish to continue [y/n]?
Similar messages appear if this is an OSP upgrade. In the following case, the
NDS server and the OSP GUI were already installed and both components
are being upgraded. The custom topology server is also enabled. Some lines
do not appear if the upgrade is not exactly the same.
========================================================
The following actions will be performed:
* The existing server will be terminated.
* The existing version of the software will be removed.
* The 3rd party software will be installed and configured.
* The 3rd party software will be started.
*
*
*
*
*
The
The
The
The
The
new server will

new GUI will be
custom topology
new server will
custom topology
be installed and configured.

installed and configured.
will be installed and configured.
be started.
server will be started.
========================================================
Do you wish to continue [y/n]? y
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Enter y to continue in both cases.
Note: Do not interrupt the installation or upgrade at this stage.
38
Status messages appear as the installation or upgrade proceeds. When the

installation or upgrade is completed, the following message appears:
OSP software has been successfully installed.
or
OSP software has been successfully upgraded.
39
If you are installing using the OSP installation CD, unmount the CD by
entering:
cd /
/sbin/umount /cdrom
40
Create the following directories (required to use the Custom Topology

Server):
mkdir /opt/nortel/nds_data
mkdir /opt/nortel/nds_backup
Note 1: The following messages appear if the directories already exist:
mkdir: cannot create /opt/nortel/nds_data: File exists
mkdir: cannot create /opt/nortel/nds_backup: File exists
Note 2: These directories must have read/write/execute permission for the
entire directory path by all users.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Procedure 1-2
Installing OSP software on a Linux or Solaris platform
Use this procedure to install the OSP server software on a platform running
the Linux or Solaris operating system.
Note: If the system aborts the installation because prerequisites were not
satisfied, you must resolve the underlying problem before beginning the
installation again. If an installation is aborted before the load is completely
installed, call Ciena Technical Support.
Requirements
have the OneControl 5.0 Installation DVD4 or download the software from
the Ciena portal (see Software download on page x)
review the section on Ciena Software Key Code Manager on page x and
perform the required steps related to server registration and key code
generation and use
be able to log in to the workstation using the oneadmin and root user
accounts
ensure that the Manager for 6k, OM5k and CPL is installed. For more
information about installing the Manager for 6k, OM5k and CPL, see the
OneControl Installation Parts 1 and 3, 450-3201-201.
make sure that consistent entries for both NDS servers are placed into
each others /etc/hosts file, if you are installing OSP on Manager for 6k,
OM5k and CPL servers in a resilient pair
install OSP on the secondary server first, if you are installing OSP on
Manager for 6k, OM5k and CPL servers in a resilient pair. Then install
OSP on the primary server.
ensure that you set up the peer server as the remote host as indicated in
the procedure, if you are installing OSP on Manager for 6k, OM5k and CPL
servers in a resilient pair. The default server settings cannot be used.
make sure there is sufficient disk space available on the workstation
complete Table 1-1 on page 1-4
Step
Action
Log in to the workstation where you plan to install the OSP software using the
oneadmin user ID and password.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Starting the software installation

2
If you are installing using the Then go to

OneControl 5.0 Installation
DVD4
step 3
software downloaded from

the Ciena portal
step 13
Insert the DVD4 into the DVD drive.
If you are using
Then go to
Solaris
step 5
Linux
step 7
For Solaris
5
If the platform model of the

server is
Then
T3-2, T4-1, T4-2, or T4-4

and the server is running
Solaris 10
a. Verify that the DVD is mounted correctly

by entering:
ls /cdrom/cdrom1
b. Change directory by entering:
cd /cdrom/cdrom1
any other supported model

running Solaris 10, 11.1, or
11.2
a. Verify that the DVD is mounted correctly

by entering:
ls /cdrom/cdrom0
Note: For a list of supported b. Change directory by entering:
server models, see the
cd /cdrom/cdrom0
Platform requirements
chapter of the OneControl
Engineering Guide, 4503201-010.
6
Go to step 9.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

For Linux
7
Using the root user account, mount the DVD by entering:

mount -t iso9660 /dev/cdrom /media
Note: If the system displays a message indicating that the media location
(/media) is busy and there is no DVD mounted under /media, then repeat the
mount command.
Change directory by entering:

cd /media
Create the /opt/load directory by entering:

mkdir /opt/load
10
Copy the files by entering:

cp -rf OneControl_5_0_osp /opt/load/OneControl_5_0_osp
11

cd /opt/load/OneControl_5_0_osp
12
Go to step 15.
13
Untar the file you downloaded:

cd <directory to which you downloaded the tar file for
OSP>
tar -xvf OneControl_5_0_osp.tar
14
Change to the directory where the unzipped files are located:

cd OneControl_5_0_osp
15
Start the installation by entering:

./startInstall
Note: Do not interrupt the installation at this stage.
16
At the prompt, enter the location of the key code license file that you
downloaded from the Ciena Software Key Code Manager system on the
Ciena portal web site.
An example of the prompt follows:
Enter the full path and filename of the license file
[filename, abort, default=none]:
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
17
The installation starts. The following prompt appears:

OSP installation started. This may take some time....
Configuring OSP...
Assigning permissions... done.
Configuration of OSP completed successfully.
Activating OSP...
Activation of OSP completed successfully.
OSP Software has been successfully installed.
18
19
If you installed the OSP server software using the
Then go to
software DVD
step 19
software download
step 21
Eject the DVD by entering:

cd /
eject cd
20
Go to step 22.
21
If you are finished using the downloaded software, clear the contents of the
directory in which the files were stored.
22
Create the following directories (required to use the Custom Topology

Server):
mkdir /opt/nortel/nds_data
mkdir /opt/nortel/nds_backup
Note 1: The following messages appear if the directories already exist:
mkdir: cannot create /opt/nortel/nds_data: File exists
mkdir: cannot create /opt/nortel/nds_backup: File exists
Note 2: These directories must have read/write/execute permission for the
entire directory path by all users.
23
If you are installing the software on a standalone server, you have completed
this procedure. If you are installing the software on a resilient pair, install OSP
on both servers. After the OSP installation has completed, make sure that the
correct Manager for 6k, OM5k and CPL server is the master. For more
information, see OneControl Installation, Part 3, 450-3201-201.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
Displaying and editing the OSP current settings

24
To display the current settings, see Displaying the current OSP configuration
settings on page 3-9.
25
To edit the current settings, see Editing OSP configuration settings on a

Linux or Solaris platform on page 2-15.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Procedure 1-3
Installing the OSP online help on an HP platform
Use this procedure to install the OSP online help files on an HP platform.
Online help gives you access to the HTML files of the following OSP
documents:
OneControl Optical Service Provisioner Standard Operations Guide, 4503251-028
OneControl Optical Service Provisioner and Layer 1 Network and Service

Viewer Custom Topology User Guide, 450-3251-189
The OSP online help on Linux and Solaris is included in the OneControl online
help files. For more information, see OneControl Installation, Part 1, 4503201-201.
Requirements
have the online help installer downloaded from https://portal.ciena.com.

For information about downloading the online help installer from https://
portal.ciena.com, see Software download on page x.
log in to the server using the root user account
install Adobe Acrobat Reader, if it is not present

Note: The Acrobat plug-in support for HP will be automatically installed
with the Manager for 6k, OM5k and CPL server.
Step
Action
Log in to the server using the root user account.
Change to the online help directory by entering:

cd /<directory>
where
<directory>
is the directory to which you downloaded the file

(.tar.gz) for the OSP online help.
Unzip the online help file you downloaded by entering:

gunzip <online_help_file>
where
<online_help_file>
is the file (.tar.gz) you downloaded for the OSP

online help. The resulting file is .tar.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Installing the OSP online help on an HP platform
Step
Action
Uncompress the online help files by entering:

tar -xvf ../<online_help_file>
where
<online_help_file>
is the file (.tar) for the OSP online help.

cd OSP_HP_Help
Install the online help by entering:

./<osp_online_help>
where
<osp_online_help>
is the script file (.sh) used to install the OSP

online help.
You can delete the online help directory. This is the directory from step 2.
rm -R /<directory>
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-1
Configuration
2-
This section describes how to configure the OSP software.
Procedures
Procedure 2-1, Configuring OSP access privileges for Manager for 6k,
OM5k and CPL users on a Linux or Solaris platform on page 2-2

page 2-4
Procedure 2-3, Editing OSP configuration settings on a Linux or Solaris

platform on page 2-15
Procedure 2-4, Editing OSP configuration properties on Windows

Procedure 2-5, Configuring OSP for resiliency on Linux or Solaris

Procedure 2-6, Configuring the NEs/controllers for an NDS server on an

HP platform on page 2-37
Procedure 2-7, Starting, stopping, restarting, or displaying status of the

OSP components on an HP platform on page 2-45

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-2 Configuration
Procedure 2-1
Configuring OSP access privileges for Manager for
6k, OM5k and CPL users on a Linux or Solaris
platform
ATTENTION
Perform this procedure only if you are configuring the access privileges for a
new Manager for 6k, OM5k and CPL user. This procedure is not required if
you are using the default Manager for 6k, OM5k and CPL user IDs such as
admin or prov.
Use this procedure to configure the access privileges for a Manager for 6k,
OM5k and CPL user to enable access to the OSP application and the OSP
NEs controlled under the Manager for 6k, OM5k and CPL. Perform this
procedure after the OSP installation is completed on a platform running the
Linux or Solaris operating system.
For more information about OSP access privileges for the Manager for 6k,
OM5k and CPL users, see the OneControl OSP Standard Operations Guide,
450-3251-028. For detailed procedures on using the Manager for 6k, OM5k
and CPL security administration applications, see the OneControl Security
Administration Procedures, 450-3201-351.
Requirements
complete the OSP software installation on the Linux or Solaris platform
be a member of the Top-level Admin role in the Manager for 6k, OM5k and
CPL to access the Manager for 6k, OM5k and CPL security administration
applications
Step
Action
Start the Manager for 6k, OM5k and CPL user interface using the appropriate
procedure in the OneControl Manager for 6k, OM5k and CPL Standard
Operations Guide, 450-3241-301.
Log in with a user account that is a member of the Top-level Admin role.
From the Manager for 6k, OM5k and CPL main menu, select Security.
Select Manage User/Roles/Rules.

The User Administration window opens.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-3
Configuring OSP access privileges for Manager for 6k, OM5k and CPL users on a Linux or Solaris
platform
Step
Action
Add the privileges to a user using the predefined roles/rules.
Associate one of the following roles with the user to which you want to add
OSP privileges:
Global_Administrator
Global_Provisioner
Note 1: Do not modify the default set of rules corresponding to their default
roles (Global_Administrator and Global_Provisioner).
Note 2: You can also create a new user by selecting the Users tab and
clicking Create User. Then assign the user to the role.
These users will be granted access to the OSP application and the OSP NEs.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-4 Configuration
Procedure 2-2
Editing OSP configuration settings on an HP platform
Use this procedure to view or change the configuration settings that were set
during installation on an HP platform.
The configuration options available depend on the components installed. This
procedure shows all options, as available for a workstation on which both a
GUI and an NDS server are installed.
list) you can select by pressing Enter. In addition:
At most prompts, you can abort the changes by entering the command
abort.
Requirements

Note: If you change the GUI properties, the new properties only affect
GUIs that are opened from that point, but not the GUIs that are already
open.

Step
Action
Log in to the workstation containing the OSP software using the root user ID
and password.
Change to the OSP directory by entering:

cd /bin/osp
Run the configuration script by entering:

./osp_admin configure
The current configuration appears.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-5
Step
Action
Press Enter to display the main menu. The prompts displayed depend on
whether the GUI, server, or both have been installed. If only the server or the
GUI has been installed, a subset of the following is displayed:
Select one of the following options:
[0] Cancel (exit without saving changes)
[1] Apply (exit, save changes)
[2] Set GUI preferred standard (SONET / SDH)
[3] Set GUI preferred port naming type (Universal / NEspecific)
[4] Set maximum GUI instances (1-24)
[5] Set GUI maximum connection ID length (15-99)
[6] Allow blank connection ID in new paths (yes / no)
[7] Set server preferred standard (SONET / SDH)
[8] Set server preferred port naming type (Universal / NEspecific)
[9] Set local server to be preferred server (yes / no)
[10] Manage server list used by the local GUI
[11] Manage server list used by the local server
[12] Enable or disable the local custom topology server
[13] Set IP address of the preferred custom topology
server
[14] Set IP address of the alternate custom topology
server
[15] Show current configuration
Enter [0-15]:
Note: Configuration changes are only applied when the corresponding
option is selected from the main menu. If the configuration is aborted at any
time, the aborted setting is lost, but all other changes made are retained in
memory. You can save the other settings and exit or abort the entire session
(exit without saving).
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-6 Configuration
Step
Action
Select a configuration option by entering the corresponding number. Then go

to the step identified as follows.
If you want to
Then
change the standard used for the display of

connection rates (either SONET or SDH
formats) for the GUI only
change the port format for the GUI only
change the maximum number of GUI instances enter 4 and go to step 8

change the maximum connection ID length
allow or disallow blank IDs in the connection

paths

formats) for the NDS server only
change the port format for the NDS server only enter 8 and go to step 12
change the preferred server setting of the NDS enter 9 and go to step 13
server
manage the remote NDS server list used by
the GUI
manage the NDS server list used by the local

server
enable or disable the local custom topology

server
set the IP address for the preferred custom

topology server
set the IP address for the alternate custom

topology server
display the current configuration values
apply all changes and exit
enter 1 and you have

completed this procedure
exit without applying any changes

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-7
Step
Action
Selecting the preferred standard for the display of connection rates for the GUI
6

Select the preferred standard for the GUI from the
following options:
[1] SONET
[2] SDH
The GUI can be configured to show connection rates in either SONET or SDH
formats. This parameter sets the default value, but you can change the
preference on a per-session basis.
If you want to use the
Then
SONET format
enter 1 and return to step 5
SDH format
Selecting a port format default for GUI

7

Select the preferred port format type for the GUI from the
following options:
[2] Universal
The GUI can be configured to show port names in either a universal or a
network element type-specific format. This parameter sets the default value,
but you can change your preference on a per-session basis.
If you want to show port names in
Then
NE-type specific format
universal format

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-8 Configuration
Step
Action
Selecting maximum number of GUI instances

8

Enter the maximum number of GUI instances
[1-24, abort, ? for help, default=10]
Enter the number and return to step 5.
Selecting maximum connection ID length

9

Selecting to change the blank ID option

10

default=n]:
Make a selection and return to step 5.
Selecting the preferred standard for the display of connection rates for this NDS server
11

Select the preferred standard for the server from the
following options:
[1] SONET
[2] SDH
This parameter determines the display of connection rates in the NDS audit
logs.
Then
SONET format
SDH format

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-9
Step
Action
Selecting a port format default for NDS server

12

Select the preferred port format type for the server from
the following options:
[2] Universal
This parameter determines the display of port names in NDS audit logs.
If you want to show the port names in
Then
NE-type specific format
universal format
Selecting the preferred server setting

13

Managing the NDS server list

14

[1]
[2]
[3]
[4]
Continue with configuration

Add server
Remove server
List all servers

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-10 Configuration
Step
Action
The software does not ensure that the NDS servers are installed and properly
configured (only that a workstation is defined at the specified IP address).
If you want to
Then
return to the main menu to either continue with enter 1 and go to step 5
the configuration or to apply all your changes
15

Enter the address of the server ['q' to return to the
menu]:
Enter the IP address of the remote NDS server. The installation software
validates the address. If the following message appears, the address has
been validated and the remote server has been added to the local
configuration:
<error message>
where
and IP address updated in the /etc/hosts file on both servers for the script to
validate the address.
Return to step 14. If the addition failed, verify that you have the correct IP
address and try to add the server again.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-11
Step
Action

16

[1] 56.3.4.2
[2] 34.4.5.1 (localhost)
Note: The item for localhost is shown in the menu only when you are
configuring servers with which the local GUI communicates.
The menu lists the remote servers you have previously identified (for
Server removed.
Return to step 14.

17
A list of the NDS servers that you have identified appears.

The following example is for the GUI:
[1] 43.12.242.86 (localhost)
The following example is for the NDS server:
The local server communicates with the following servers:
[1] 45.12.15.12
Return to step 14.
Enabling or disabling the local custom topology server

18

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-12 Configuration
Step
Action
Managing the preferred custom topology server

19

IP address of the preferred topology server is not
configured.
Enter preferred topology server IP address [IP,
localhost, none, abort, ? for help, default=none]:
Enter the IP address of the preferred custom topology server. The software
validates the address. Alternatively, enter l for localhost and the software will
server has been set as the preferred custom topology server.
<error message>
where
and IP address updated in the /etc/hosts file on both servers for the script
to validate the address.
Return to step 5. If the selection failed, verify that you have the correct IP
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-13
Step
Action
Managing the alternate custom topology server

20

Note: If the IP address of the preferred topology server is not configured (set
to none), you will receive a WARNING: You must configure the preferred
topology server before configuring the alternate message and you will be
returned to the main menu.
IP address of the alternate topology server is not
configured.
Enter alternate topology server IP address [IP,
Enter the IP address of the alternate custom topology server. The software
validates the address. Alternatively, enter l for localhost and it will
automatically pick up the local host's IP address. If the following message
appears, the address has been validated and the server has been set as the
alternate custom topology server.
Alternate topology server set to 43.12.3.73.
<error message>
where
21
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-14 Configuration
Step
Action
Displaying the current configuration

22
The current configuration appears. The following is an example:

Current configuration:
GUI
preferred standard:
GUI
GUI
maximum instances:
GUI
maximum connection ID length
GUI
SONET
NE
10
64
yes

SONET
NE
Local server is the preferred server: yes
(localhost)
enabled
43.12.3.73
none
Local GUI communicates with the following servers:

43.12.3.73 (localhost)
servers:
none
========================================================
Press [Enter] to continue...
Press Enter and return to step 5.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-15
Procedure 2-3
Editing OSP configuration settings on a Linux or
Solaris platform
Use this procedure to edit the configuration settings on a platform running the
This procedure shows all options, as available for a workstation on which both
a GUI and an NDS server are installed.
list) that you can select by pressing Enter. In addition:
At most prompts, you can abort the changes by entering the command
abort.
Requirements
be able to log in to the workstation using the root user account with the
ability to switch to the oneadmin user
Note: If you change the GUI properties, the new properties only affect
GUIs that are opened from that point, but not the GUIs that are already
open.

Step
Action
and password.
Verifying the LAN line interface (only one LAN line interface must be active)
2
Verify the LAN line interface by entering:

ifconfig -a
Ensure that there is only one LAN interface active against the IP address of
the server. For example, the line with the inet addr matching the IP address
of the server should appear in only one of the interfaces.
If more than one interface exists, contact your server administrator to remove
the other interface(s).
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-16 Configuration
Editing OSP configuration settings on a Linux or Solaris platform
Step
Action

3
Switch to the oneadmin user by entering:

su - oneadmin

cd /opt/nortel/bin/osp

Press Enter to display the main menu.

[0] Cancel (exit without saving changes)
[1] Apply (exit, save changes)
[2] Set GUI preferred standard (SONET / SDH)
[3] Set GUI preferred port naming type (Universal / NEtype specific)
[4] Set GUI maximum connection ID length (15-99)
[5] Allow blank connection ID in new paths (yes / no)
[6] Set server preferred standard (SONET / SDH)
[7] Set server preferred port naming type (Universal / NEtype specific)
[8] Set local server to be preferred server (yes / no)
[9] Manage server list used by the local GUI
[10] Manage span server list used by the local server
[11] Manage OMEA server list used by OSP GUI clients
[12] Enable or disable the local custom topology server
[13] Set IP address of the preferred topology server
[14] Show current configuration
Enter [0-14]:
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-17
Step
Action
Note: Configuration changes are only applied when the corresponding
option is selected from the main menu. If the configuration is aborted at any
time, the aborted setting is lost, but all other changes made are retained in
memory. You can save the other settings and exit or abort the entire session
(exit without saving).
Select a configuration option by entering the corresponding number. Then go

to the step identified as follows:
If you want to
Then

formats) for the GUI only
change the port format for the GUI only
change the maximum connection ID length
allow or disallow blank IDs in the connection

paths

formats) for the NDS server only
change the port format for the NDS server only enter 7 and go to step 13
set local server to be preferred server
manage NDS server list used by the local GUI enter 9 and go to step 15
manage span server list used by the local
server
manage Manager for 6k, OM5k and CPL list

used by OSP GUI clients
enable or disable the local custom topology

server
set the IP address for the preferred custom

topology server
display the current configuration values

exit without applying any changes

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-18 Configuration
Step
Action
Selecting the preferred standard for the display of connection rates for the GUI
8

Select the preferred standard for the GUI from the
following options:
[1] SONET
[2] SDH
The GUI can be configured to show connection rates in either SONET or SDH
formats. This parameter sets the default value, but you can change the
preference on a per-session basis.
Then
SONET format
SDH format
Selecting a port format default for GUI

9

Select the preferred port format type for the GUI from the
following options:
[2] Universal
The GUI can be configured to show port names in either a universal or a
network element type-specific format. This parameter sets the default value,
but you can change your preference on a per-session basis.
If you want to show port names in
Then
NE type-specific format
universal format

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-19
Step
Action
Selecting maximum connection ID length

10

Selecting to change the blank ID option

11

default=n]:
Selecting the preferred standard for the display of connection rates for this NDS server
12

Select the preferred standard for the server from the
following options:
[1] SONET
[2] SDH
This parameter determines the display of connection rates in the NDS audit
logs.
Then
SONET format
SDH format

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-20 Configuration
Step
Action
Selecting a port format default for NDS server

13

Select the preferred port format type for the server from
the following options:
[2] Universal
This parameter determines the display of port names in NDS audit logs.
If you want to show the port names in
Then
NE type-specific format
universal format
Selecting the preferred server setting

14

Managing the server list

15

[1]
[2]
[3]
[4]

Add server
Remove server
List all servers

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-21
Step
Action
The software does not ensure that the servers are installed and properly
configured (only that a workstation is defined at the specified IP address).
If you want to
Then
add a server to the list
remove a server from the list
display the list of servers
return to the main menu to either continue with enter 1 and go to step 7
the configuration or to apply all your changes
Adding a server to the list
16

menu]:
Enter the IP address of the remote server. The software validates the
address. If the following message appears, the address has been validated
and the remote server has been added to the local configuration:
<error message>
where
Return to step 15. If the addition failed, verify that you have the correct IP
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-22 Configuration
Step
Action
Removing a server from the list

17

[1] 1.2.3.4
[2] 1.2.3.5 (localhost)
Note: The item for localhost is shown in the menu only when you are
configuring servers that the GUI communicates with.
The menu lists the remote servers you have previously identified (for
Server removed.
Return to step 15.
Listing all identified servers

18
A list of the servers that you have identified appears.

The following example is for the option: Manage server list used by the local
GUI:
[1] 1.2.3.4
[2] 1.2.3.5 (localhost)
The following example is for the option: Manage span server list used by the
local server:
The local server communicates with the following span
servers:
[1] 1.2.3.4
[2] 1.2.3.5 (localhost)
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-23
Step
Action
The following example is for the option: Manage the Manager for 6k, OM5k
and CPL server list used by OSP GUI clients:
The OSP GUI clients communicate with the following OMEA
servers:
[1] 1.2.3.4
[2] 1.2.3.5 (localhost)
Return to step 15.
Enabling or disabling the local custom topology server

19

Managing the preferred custom topology server

20

IP address of the preferred topology server is not
configured.
Enter preferred topology server IP address [IP,
Enter the IP address of the preferred custom topology server. Alternatively,
enter l for localhost and it will automatically pick up the local host's IP address.
The software validates the address.
server has been set as the preferred custom topology server.
<error message>
where
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-24 Configuration
Step
Action
Displaying the current configuration

21
The current configuration appears. The following is an example:

GUI
preferred standard:
GUI
GUI
GUI
SONET
NE
64
yes

SONET
NE
enabled
1.2.3.4(localhost)
OSP GUI clients communicate with the following OMEA

servers:
1.2.3.5
1.2.3.4 (localhost)
Local NDS server communicates with the following span
servers:
1.2.3.5
1.2.3.4 (localhost)
1.2.3.5
1.2.3.4 (localhost)
========================================================
Press [Enter] to continue...
Press Enter and return to step 7.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-25
Procedure 2-4
Editing OSP configuration properties on Windows
platform
Use this procedure to edit the OSP configuration properties on a Windows
platform.
Requirements
Before you perform this procedure, you must ensure that the OSP client is
installed on the Windows PC (see Installation of OSP client software on
page 1-3).
Step
Action
Log on to the machine.
Go to the directory:
C:\Users\Public\OSP_Client_<version>
where
<version>
is the OSP client version.

Example: 14.0.0.0
Using a text editor, open the ocm.properties file. For a summary of the
properties, see Table 2-1 on page 2-26.
Edit the file, as required.
Save and close the file.
Close the text editor.

continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-26 Configuration
Editing OSP configuration properties on Windows platform
Table 2-1
Summary of OSP configurable properties on a Windows platform
Property
Possible values
Description
ocm.ui.preferredStandard
SONET
You can configure the UI to show

connection rates in either SONET or
SDH format. You can change the
preference on a per-session basis but
this property sets the default value.
SDH
Default value:
SONET
ocm.server.preferredStandard
SONET
SDH
Default value:
SONET
ocm.ui.preferredPortFormatType
UNIVERSAL
NE
Default value: NE
ocm.server.preferredPortFormatType
UNIVERSAL
NE
Default value: NE
ocm.ui.blankConnectionIDAllowed
false
true
You can configure the server to show

connection rates in either SONET or
SDH formats. This property specifically
applies to the display of connection rates
in audit logs.
You can configure the UI to show port
names in either a universal (generic) or
network element type-specific format.
You can change the preference on a persession basis but this property sets the
default value.
You can configure the server to show
port names in either a universal (generic)
or network element type-specific format.
This property specifically applies to the
display of connection rates in audit logs.
You can configure the UI so that blank
connection IDs are allowed.
Default value:
false

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-27
Table 2-1
Summary of OSP configurable properties on a Windows platform (continued)
Property
Possible values
ocm.logLevel
0 - trace logs
Description
The log level property controls the

amount of logging that is done. All log
100 - internal
messages that are at the specified level
information logs
or higher are sent to the log file. For
200 - customer
example, if the level is 200 (customer
information logs
information logs), then the system
300 - warning logs displays all customer information logs,
warning logs, software error logs, and
400 - software
critical error logs.
error logs
500 - critical error
logs
Default value: 200
ocm.nameServer
The name service is used to find the

server instance that is managing a
particular network element. You can
specify multiple name servers by adding
Default value:
corbaloc::localhos additional 'ocm.nameServer.X' entries,
where 'X' is a unique alphanumeric
t:58772/
identifier.
NameService
This group of IP addresses is used by the
UI.
see the
Description
column
Entry format:
ocm.nameServer[.X] = corbaloc::<host
IP>:<port>/NameService
Examples:
ocm.nameServer =
corbaloc::10.0.0.1:58772/NameService
ocm.nameServer.1 =
ocm.omeaServerIp
see the
Description
column
Default value:
localhost
You can configure the OSP GUI client

running on Solaris to communicate with
multiple Manager for 6k, OM5k and CPL
(OMEA) servers.
Examples:
ocm.omeaServerIp = localhost
ocm.omeaServerIp.1 = 1.2.3.4

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-28 Configuration
Table 2-1
Property
Possible values
Description
ocm.spanSourceIp
see the
Description
column
You can configure the OCM server to

communicate with remote spans. For
now, this is intended for the remote
Manager for 6k, OM5k and CPL servers
when OCM is running on Solaris.
Default value:
localhost
Examples:
ocm.spanSourceIp = localhost
ocm.spanSourceIp.1 = 1.2.3.4
ocm.preferredServer
true
The preferred server is the "Master" and

only one can exist in the group of servers
false
that communicate with each other. The
Default value: true IP addresses that precede (if any) are
the other remote servers that this server
communicates with.
The format is similar as for the list of
servers that the UI talks to.
Examples:
ocm.serverIpAddress =
ocm.preCaching
You can configure the OCM server to

pre-cache network information; if this is
enabled then the OCM server will prefalse - The preload its cache with network data rather
caching is OFF.
than waiting for clients to indicate spans
Default value: true of interest.
true - The precaching is ON.
Enabling this option generally enhances

client performance at the cost of
additional memory and bandwidth usage
on the server; leaving it disabled will
cause the server to only load network
data as needed by clients (which means
that clients will have to wait for network
data to be loaded before they can be
used effectively).

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-29
Table 2-1
Property
Possible values
Description
ocm.networkAuditDay
1 to 7
The OCM Server periodically audits the

network to maintain consistent data.
Default value: 7
ocm.networkAuditHour
ocm.networkAuditMinute
ocm.networkAuditOccurrence
Default value: 0
To have no audits use "0" for AuditDay,

AuditHour, AuditMinute, and
AuditOccurence.
0 to 59
Values for networkAuditDay:
Default value: 0
1 = Sunday
0 to 23
0 to 365
Default value: 7
2 = Monday
3 = Tuesday
4 = Wednesday
ocm.networkAuditMaxNumberToAuditA 0-N
tOnce
Default value: 20
5 = Thursday
nds.networkAuditSizeCheck
7 = Saturday
true
6 = Friday
false
The initial start day for audits to occur. If

Default value: true the Occurrence value is not a multiple of
7, then the day in which network audits
occur will shift according to the
occurrence value.
Values for networkAuditHour: 0 to 23 (24
hr clock)
Values for networkAuditMinute: 0 to 59
Values for networkAuditOccurrence: 0 to
365
The Occurrence values controls how
long to wait in days, before OCM will
attempt another audit.
Values for networkAuditMaxNumber
ToAuditAtOnce: 0-N
This number allows the control of the
throttling controllers during the audit
cycle. By entering 0, no limit is set.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-30 Configuration
Table 2-1
Property
Possible values
Description
nds.cacheDumpDay
1 to 7
Properties for scheduling the cache

dump. The properties are preserved
across upgrades, but cannot be modified
during installation or via osp_admin.
Default value: 1
nds.cacheDumpHour
0 to 23
Default value: 0
nds.cacheDumpMinute
0 to 59
The meaning of the parameters is the

same as for the network audit.
Default value: 0
nds.cacheDumpInterval
Default value: 7
nds.cacheDumpEnabled
true
false
Default value:
false
nds.cacheDumpDirName
Default value:
/opt/nortel/logs
nds.cacheDumpFileName
Default value:
/cmsbb-cachedump.txt
ocm.alignmentThrottle
10-N
Default value: 10
ocm.resourcestore.topologicallinks.max 10 to 3000
subnetworkentries
The lower value
may cause
frequently
dumping the
entries and
retrieving
topological links;
higher value will
occupy more
memory.
Upon startup OCM will attempt to learn

the network. This number controls now
many controllers OCM will align
simultaneously.
The OCM client caches topological links
to improve the performance. This
property defines maximum subnetwork
entries that topological link cache holds.
The topological link cache will dump
some subnetwork entries when this limit
is reached.
ResourceStore class uses this property
to pre-allocate memory to avoid rehash
the hash tables.
Default value: 100

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-31
Table 2-1
Property
Possible values
Description
ocm.connectionquery.maxRequestAtte
mpts
1 to 3
The OCM client may resend requests to

the OCM server that have timed out.
The lower values

will be less
tolerant of
requests to the
server timing out.
This property defines the maximum

number of attempts that the client should
make before it stops resending and
declares the timeout an error.
This value must be

at least 1.
Default value: 2
ocm.client.maxGuiInstances
>0
Integer value that
is greater than
zero.
The maximum OCM client instances that

can run on a single workstation.
Setting this value

to 0, unspecified,
or other
unsupported
value, will disable
this feature.
Default value: 10
ocm.client.maxconnectionIdChar
15 to 99
Default value: 64
ocm.topologyPollingInterval
Default value: 60
The maximum connection ID length that

is supported.
Properties controlling the behaviour of
Custom Topology introduced in OSP5.
These properties are preserved across
upgrades, and can be modified by users.
On Solaris, the polling frequency at
which the control script checks the value
of the topologyEnabled variable in order
to stop or start the custom topology
process. Parameter not applicable on
HP.
ocm.topologyEnabled
false
true
Default value:
false

Release 5.0
If false, topology server is not running on

localhost; otherwise it is. This property
serves as an anchor for the
topologyPreferredIp properties and
topologyAlternateIp properties which
may or may not be present.

450-3251-201 Standard Issue 07.01
August 2015
2-32 Configuration
Table 2-1
Property
Possible values
Description
Properties needed for checking the
sanity of the Orb process. These
properties are preserved across
upgrades and cannot be modified by
users.
nds.TimeBetweenOrbAudits = 15
nds.AcceptableTimeBetweenFailures =
14
nds.TimeOrbCheckerToWaitForReply =
5
nds.restartOnSun = true
nds.restartOnHp = false
nds.restartOrbSun = true
nds.restartOrbHp = false
nds.maxNumOfCorbaFailures = 5
nds.corbaAudit = true
nds.BDEreconnect
0 to 50
Default value: 5
nds.BDEthTime
Properties needed for checking the

number of re-connects for the NDS.
0 to 5000000
Default value: 0
nds.BDEsystemwaitTime
0 to 3000000
Default value:
30000
nds.BDEretryTime
0 to 300000
Default value:
30000
nds.BDExcSize
1 to 500000
Default value:
10000
nds.BDEWorkers
1 to 6
Default value: 2
xdr.logDuration
Default value: 12
The time difference between two audits

for log compression.
nbi.logDuration
Default value: 24
The time difference between two audits

for log compression.

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-33
Table 2-1
Property
Possible values
Description
xdr.logSize
Default value: 25
The maximum size of the log for

compression.
nbi.logSize
Default value: 25
The maximum size of the log for

compression.
xdr.logRotation
Default value: 5
The number of compressed files to be

maintained.
nbi.logRotation
Default value: 5
The number of compressed files to be

maintained.
nds.toleranceLog
true
Set the property value to true to enable

the tolerance logs.
false
Default value:
false
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-34 Configuration
Procedure 2-5
Configuring OSP for resiliency on Linux or Solaris
platform
Use this procedure to configure OSP for resiliency on a platform running the
Requirements
complete the OSP software installation on the Linux or Solaris platform
be able to log in to the workstation using the root user account with the
ability to switch to the oneadmin user

Step
Action
Log in to the workstation containing the OSP software using the oneadmin
user ID and password.
Verifying the LAN line interface (only one LAN line interface must be active)
2
Verify the LAN line interface by entering:

ifconfig -a
Ensure that there is only one LAN interface active against the IP address of
the server. For example, the line with the inet addr matching the IP address
of the server should appear in only one of the interfaces.
If more than one interface exists, contact your server administrator to remove
the other interface(s).
Configuring OSP for resiliency on Linux or Solaris platform

3
Switch to the oneadmin user by entering:

su - oneadmin


continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-35
Step
Action
Select a configuration option to manage the NDS server list by entering the
corresponding number.
If you want to
Then
manage NDS server list used by the local GUI
enter 9
manage span server list used by the local server
enter 10
manage Manager for 6k, OM5k and CPL list used by OSP
GUI clients
enter 11

[1]
[2]
[3]
[4]

Add server
Remove server
List all servers

7
Enter 2.
menu]:
Enter the IP address of the remote server. The software validates the
address. If the following message appears, the address has been validated
and the remote server has been added to the local configuration:
<error message>
where
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-36 Configuration
Step
Action
If
Then
the addition failed
verify that you have the

correct IP address and try
to add the server again
the addition was successful and you want to


you want to exit without applying any changes enter 0 and you have
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-37
Procedure 2-6
Configuring the NEs/controllers for an NDS server on
an HP platform
Use this procedure to configure the NEs and controllers for an NDS server on
an HP platform.
For Solaris deployments, load balancing is not supported.
Use this procedure to:
exclude specific NEs (manually or using a list of available NEs)
exclude specific controllers (manually or using a list of available

controllers)
exclude specific controllers by release
reset the current exclusion list
include NEs that have been previously excluded
include controllers that have been previously excluded

Note: The current list of available spans and NEs is based on what was
known to the AP Graphical Network Browser (GNB) at the time you started
the Resource Allocation tool. You can select Refresh available spans to
update the list of available spans and NEs and include the recently added
span.
Requirements
ensure that NDS is running
Step
Action
and password.

cd /bin/osp
Start the resource allocation tool by entering:

./resourceTool
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-38 Configuration
Configuring the NEs/controllers for an NDS server on an HP platform
Step
Action

Starting the Resource Allocation Tool
.....................................
===================================
= OSP Resource Allocation Tool =
===================================
[0]
[1]
[2]
[3]
[4]
[5]
[6]
Exit
Reset Exclusion List
Manage supported spans
Manage supported Network Elements
Refresh available spans
Audit the NDS Federation
Turn precaching off
Enter [0-6]:
5
Select an option from the following table.

If you want to
Then
exclude a controller by its IP address (from available

controllers)
enter 2 then
enter 2 then
enter 1 and
go to step 6
exclude a controller by its IP address (entered manually)
enter 2 then
enter 2 then
enter 2 and
go to step 10
exclude a controller by its software release (from available

controllers)
enter 2 then
enter 3 and
go to step 15
exclude an NE using its controller IP address and its NE ID

(from available controllers)
enter 3 then
enter 2 then
enter 1 and
go to step 19
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-39
Step
Action
If you want to
Then
exclude an NE using its controller IP address and its enter 3 then

NE ID (entered manually)
enter 2 then
enter 2 and
go to step 24
exclude NEs using the NE software release (from
available NEs)
enter 3 then
enter 3 and
go to step 28
reset the exclusion list
enter 1 and
go to step 32
list controllers that are currently excluded (from

available controllers or entered manually)
enter 2 then
enter 1 then
go to step 37
list NEs that are currently excluded (from available

NEs or entered manually)
enter 3 then
enter 1 then
go to step 40
include a controller that is currently excluded
enter 2 then
enter 4 then
go to step 43
include an NE that is currently excluded
enter 3 then
enter 4 then
go to step 47
audit the NDS federation
enter 5 and
go to step 51
turn precaching on or off
enter 6 and
go to step 54
exit the application
enter 0 and
go to step 56
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-40 Configuration
Step
Action
A list of controllers appears as follows. Select the controller to be excluded.

[0] Return to the previous menu
[1] 42.67.241.139 OPT-DX
[2] 42.11.241.155 OPT-LH
Displaying 1 - 2 of 2
Enter the number corresponding to the span to be excluded:

Exclude 42.67.241.139
OPT-DX? (Y/N) :
Enter Y.
8
Select 0 to return to the previous menu, 0 again to return to the previous

menu, and 0 again to return to the main menu.
Go to step 5.
10

Enter the span IP address or 0 to return to the previous
menu:
Note: There is no validation on the IP address being entered.
11
Enter the IP address of the controller to be excluded and press enter.
12
The following is an example of the message that appears:

Exclude 24.114.241.139(Y/N) :
Enter Y.
13

14
Go to step 5.
15
The following is an example of the menu that appears:

[1] MULTISERVICE MOA REL 13.0
[2] OPT-DX REL 06.03
Enter the number corresponding to the span to be excluded:
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-41
Step
Action
16
Enter the number corresponding to the span to be excluded and confirm your
choice.
17
Select 0 to return to the previous menu and 0 again to return to the main
menu.
18
Go to step 5.
19

[1] 25.114.241.139 OPT-DX
[2] 25.114.241.155 OPT-LH
Enter the number corresponding to the span of the NE to
be excluded:
20
Enter the number corresponding to the span of the NE. The following is an
example of the menu that appears:
[1] 1615 Montreal
[2] 1617 Toronto
Enter the number corresponding to the NE to be excluded:
21
Select the corresponding number for the NE to be excluded and confirm the
selection.
22

menu, 0 again to return to the previous menu, and 0 again to return to the
main menu.
23
Go to step 5.
24
The following messages appears:

Enter the Span IP address followed by a space and then the
NE ID, or 0 to return to the previous menu:
25
Enter the controller IP address and the NE ID, press Enter, and confirm your
selection.
26

27
Go to step 5.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-42 Configuration
Step
Action
28
The following is an example of the menu that appears:

[1] Common Photonic Layer OADM 2.0
[2] DWDM Repeater
[3] NE Controller
[4] OC192 Multiplexer Ring ADM
[5] OC48 Multiplexer LTE OC-48 REL 17
[6] Optical Cross Connect DX Mixed Config Hub
[7] Optical Metro 3500 REL1300S.DS
[8] Optical Metro 5100/5200 ADM 8.0.55.1
[9] Optical Metro 5100/5200 OFA 8.0.55.1
[10] Optical Multiservice Edge 6110 2.0
Enter the number corresponding to the NE to be excluded:
29
Enter the number corresponding to the software release and confirm your
selection.
30
menu.
31
Go to step 5.
32

Are you sure you want to remove ALL items from the
exclusion list? [Y/N]
CAUTION
All items previously excluded are included at this time.
Make sure that the engineering limits are respected. If
the engineering limits are exceeded, you must redo the
exclusion list to make sure the limits are respected. For
information on the engineering limits, see the
OneControl Engineering Guide, 450-3201-010.
33
Select Y.
34

All spans and NEs presently excluded will now be included.
Continue? [Y/N]
35
Enter Y.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-43
Step
Action
36
Go to step 5.
37
A list of excluded controllers appears as shown in the following menu:

[1] 25.114.241.139 OPT-DX
[2] 25.114.241.155 OPT-LH
Enter 0 to return to the main menu:
38
menu .
39
Go to step 5.
40
A list of excluded NEs appears as shown in the following menu:

[1] 25.114.241.139 OPT-DX 1715 DX1715
[2] 25.114.241.139 OPT-DX 5005 DX_NE_LAB_B18
Enter 0 to return to the main menu:
41
menu.
42
Go to step 5.
43
A list of excluded controllers appears as shown in the following menu:

[1] 25.114.241.139 OPT-DX
[2] 25.114.241.155 OPT-LH
Enter the number corresponding to the span to be included:
44
Enter the number corresponding to the span to be included and confirm your
choice.
45
menu.
46
Go to step 5.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-44 Configuration
Step
Action
47
A list of excluded NEs appears as shown in the following menu:

[1] 25.114.241.139 OPT-DX 1715 DX1715
[2] 25.114.241.139 OPT-DX 5005 DX_NE_LAB_B18
Enter the number corresponding to the NE to be included:
48
Enter the number corresponding to the NE to be included and confirm the

choice.
49
menu.
50
Go to step 5.
51
A message similar to the following one appears with the current date and time
as the output file:
Date:Thu_Aug_31_14:07:39_EDT_2006
The output will be printed to /opt/nortel/logs/
ResourceTool/audit_Thu_Aug_31_14:07:39_EDT_2006.txt
Do you want to change the path? (Yes/No)
52
Enter N.
A message similar to the following one appears:
The file has been printed out to the following location:
/opt/nortel/logs/ResourceTool/
audit_Thu_Aug_31_14:07:39_EDT_2006.txt
53
Go to step 5.
54
If precaching was already turned on, the following message appears:

PreCaching has been turned off.
Items removed from the exclusion list will not take
effect until preCaching is turned back on.
Precaching is now turned on and the NDS server retrieves the information for
the NEs and controllers in the AP list, less those excluded by resourceTool.
If precaching was already turned off, the following message appears:
PreCaching has been turned on.
55
Go to step 5.
56
Select 0.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Configuration 2-45
Procedure 2-7
Starting, stopping, restarting, or displaying status of
the OSP components on an HP platform
Use this procedure to manage the OSP components on an HP platform. This
procedure can be used for all deployment options. You can use this procedure
to:
start the OSP components
stop the OSP components
restart the OSP components
display the OSP components status
Stopping the OSP server will not kill any local or remote OSP clients. In a split
NDS deployment these clients will still be able to use the remote NDS. In a
resilient NDS deployment the remote clients will still be able to use their own
NDS for full network visibility. If the NSV clients are using this NDS
(deployment for all NE types), the NSV clients will lose visibility of the nodes
managed by this NDS.
Stopping the OSP server in a split NDS deployment will impact the network
visibility of the node managed by this NDS (so the local or remote OSP clients
will lose visibility to the nodes managed by this NDS). If this OSP server is the
preferred custom topology server, other OSP servers will need to have an
alternate custom topology server defined to continue using custom topology
information.
Starting/restarting the OSP server will trigger a network re-discovery. As such
the process will use a lot of CPU until the re-alignment is complete.
Requirements
Before you perform this procedure, you must be able to log in to the HP
platform using the root user account.
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
2-46 Configuration
Starting, stopping, restarting, or displaying status of the OSP components on an HP platform
Step
Action
Log in to the workstation using the root user account.

cd /bin/osp
Run the osp_admin script.

If you want to
Then enter
start the OSP server
./osp_admin start
stop the OSP server
./osp_admin stop
restart the OSP server
./osp_admin restart
display the OSP server status
./osp_admin status
A message confirming the command execution is displayed.

If you are checking the status of the OSP server, a message similar to the
following is displayed:
Status:
server running (pid=29887)
naming service running (pid=29872)
custom topology running (pid=29905)
All processes have correct status.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
3-1
3-
This section describes how to uninstall and troubleshoot the OSP software.
Procedures
Procedure 3-1, Uninstalling OSP server software from an HP platform on

page 3-2
Procedure 3-2, Uninstalling OSP server software from a Linux or Solaris

Procedure 3-3, Displaying the OSP components status on page 3-5
Procedure 3-4, Displaying the version of the installed OSP software on an

HP platform on page 3-6
Procedure 3-5, Displaying the version of the installed OSP software on a

Linux or Solaris platform on page 3-7
Procedure 3-6, Displaying the current OSP configuration settings on

page 3-9
Procedure 3-7, Displaying log files for OSP software installation and
uninstallation on page 3-13

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
3-2 Uninstallation and troubleshooting
Procedure 3-1
Uninstalling OSP server software from an HP platform
Use this procedure to uninstall the OSP server software from an HP
workstation on which no new load is to be installed. This procedure removes
the OSP client, NDS server, and related third-party software.
Requirements
make sure the topology_provisioner tool or the NDS Bulk Data Export tool
is not running
make sure all local and remote OSP client sessions communicating with
the NDS server to be removed have been closed
save any data (the contents of the custom topology database, for
example) that you want to keep in a safe directory. The /opt/nortel/osp
directory and all of its contents will be removed.

Step
Action
Log in to the workstation using the root user account.
Remove the OSP software by entering:

/opt/nortel/bin/osp/uninstall.sh
A message similar to the following appears (the message depends on the
software present):
Please close all local and remote GUI sessions connected
to this server.
This will remove the OSP GUI from the system.
Do you want to uninstall the software [y/n]?
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Uninstallation and troubleshooting 3-3

Uninstalling OSP server software from an HP platform
Step
Action

If you are
Then
using custom topology and want to make a enter n. The script will abort
backup of the custom topology database
the uninstall.
before performing the uninstall
not using custom topology or have already enter y.
performed a backup of the custom topology Note: Do not interrupt the
database
uninstallation at this stage.
Go to the step 4.
The following message appears after the software has been successfully
removed:
Stopping processes... done.
Removing OSP package... done.
Starting processes... done.
All software has been successfully removed.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Procedure 3-2
Uninstalling OSP server software from a Linux or
Solaris platform
Use this procedure to uninstall the OSP server software from a platform
running the Linux or Solaris operating system on which no new load is to be
installed. This procedure removes the OSP components.
Requirements
be able to log in to the workstation using the oneadmin user account
make sure all local and remote OSP client sessions communicating with
the NDS server to be removed have been closed
Step
Action
Log in to the workstation using the oneadmin user account.

Remove the OSP software by entering:

./uninstall.sh
The system displays the following prompt:
Do you want to uninstall the software [y/n]?
Enter y.
Note: Do not interrupt the uninstallation at this stage.
The following message appears after the software has been successfully
removed:
All software has been successfully removed.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Procedure 3-3
Displaying the OSP components status
Use this procedure to check the OSP components status on a platform
running the HP, Linux or Solaris operating system. This procedure can be
used for all deployment options.
Note: Start, stop or restart operations are not supported on the Linux or
Solaris platform.
Requirements
Before you perform this procedure you must be able to log in to the
workstation using
the root user account, if on an HP platform
the oneadmin user account, if on a Linux or Solaris platform
Step
Action
Log in to the workstation using the root user account (if on an HP platform) or
oneadmin user account (if on a Linux or Solaris platform).

Run the osp_admin script by entering:

./osp_admin status
The system displays the status. An example follows:
Status:
server running
naming service running
custom topology running
All processes have correct status.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Procedure 3-4
Displaying the version of the installed OSP software
on an HP platform
Use this procedure to display the version of the installed OSP software on an
HP platform.
Requirements
make sure the OSP software is already installed on the workstation
be able to log in to the OSP workstation using the root user account
Step
Action
Log in to the OSP workstation using the root user account.
Change to the directory where the osp_release.ext file is located.

cd /bin/osp
Display the osp_release.ext file.

more osp_release.ext
The system displays the OSP release information. An example follows:
PRODUCT_NAME=Optical Service Provisioner
PRODUCT_VERSION=14.0.0.0
PRODUCT_LOAD=263712
Log out of the workstation.

end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Procedure 3-5
Displaying the version of the installed OSP software
on a Linux or Solaris platform
Use this procedure to display the version of the installed OSP software on a
platform running the Linux or Solaris operating system.
Requirements
make sure the OSP software is already installed on the workstation
be able to log in to the OSP workstation using the oneadmin user account
Step
Action
Log in to the OSP workstation using the oneadmin user account.
Change to the directory where the osp_release.ext file is located.

cd /opt/nortel/applications/nds/current_nds/ospgui
Display the osp_release.ext file.

more osp_release.ext
The system displays the OSP release information. An example follows:
PRODUCT_NAME=Optical Service Provisioner
PRODUCT_VERSION=14.0.0.0
PRODUCT_LOAD=263712
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Displaying the version of the installed OSP software on a Linux or Solaris platform
Step
Action
You can also display the OSP version by running the following command:
/opt/nortel/bin/load_info
The system displays the OSP version. An example follows:
Checking existing application loads.
Common SW Mgmt
14.0.0.0_263712
CMP SW Mgmt
14.0.0.0_263712
Manager for 6k, OM5k and CPL Product 14.0.0.0_263712

Manager for 6k, OM5k and CPL
14.0.0.0_263712
EMS GUI
14.0.0.0_263712
PlatformService
14.0.0.0_263712
NDS
14.0.0.0_263712
OSP
14.0.0.0_263712
NSV Product
14.0.0.0_263712
NSV Server
14.0.0.0_263712
NSV Client
14.0.0.0_263712
Note: The NSV entry appears only if OSP is installed co-resident with NSV.
5
Log out of the workstation.

end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Procedure 3-6
Displaying the current OSP configuration settings
Use this procedure to display the current OSP configuration settings on the
HP, Linux, or Solaris platform.
Requirements
Before you perform this procedure, you must be able to log in to the
workstation using
the root user account, if on an HP platform
the oneadmin user account, if on a Linux or Solaris platform
Step
Action
Log in to the workstation using the root user account (if on an HP platform) or
oneadmin user account (if on a Linux or Solaris platform).

Run the osp_admin script by entering:

./osp_admin list
The system displays the current OSP configuration settings. Example follow:
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
(example for HP platform)
========================================================
GUI
preferred standard:
SONET
GUI
NE
GUI
maximum instances:
14
GUI
16
GUI
no
SONET
NE

enabled

(localhost)
47.134.40.145
none

47.134.40.145 (localhost)
servers: None.
========================================================
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
(example for Linux or Solaris platform)
========================================================
GUI
preferred standard:
SONET
GUI
NE
GUI
64
GUI
no
SONET
NE

enabled

(localhost)
47.134.40.118
OSP GUI clients communicate with the following OMEA

servers:
47.134.25.165
47.134.40.118 (localhost)
Local NDS server communicates with the following span
servers:
47.134.25.165
47.134.40.118 (localhost)
47.134.25.165
47.134.40.118 (localhost)
=======================================================
continued

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Step
Action
If you want to edit the current settings, see Procedure 2-2, Editing OSP
configuration settings on an HP platform on page 2-4 or Procedure 2-3,
Editing OSP configuration settings on a Linux or Solaris platform on page
2-15.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
Procedure 3-7
Displaying log files for OSP software installation and
uninstallation
Use this procedure to display log files for the OSP software installation and
uninstallation on a platform running the Linux or Solaris operating system.
The OSP log file names are:
installOSP<timestamp>.log
uninstallOSP<timestamp>.log
where timestamp takes the format of <yyyy-mm-dd_hhmmss>
HP platform
During the OSP software installation on an HP platform, the system generates
a log file in the /var/tmp/osp_install.log directory. If the OSP software
installation is successful, the install log (osp_install.log) file is removed from
the server. If the OSP software installation fails, the install log file remains in
the directory.
Requirements
make sure the OSP software is already installed or uninstalled
be able to log in to the OSP workstation using the oneadmin user account
be able to open and display UNIX system text files using a text editor such
as vi
Step
Action
Log in to the OSP workstation using the oneadmin user account.
Change to the directory where the log file is located by entering:

cd /var/nortel/logs/applications/osp
Use a text editor to open the log file and display the content of the file.
end

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015

Release 5.0

450-3251-201 Standard Issue 07.01
August 2015
OneControl Unified Management System

Optical Service Provisioner
Copyright 2013-2015 Ciena Corporation. All rights reserved.
Release 5.0
Publication: 450-3251-201
Document status: Standard
Issue 07.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

450-3251-201 (OneControl R5.0 OSP Installation and Configuration) 07.01

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

450-3251-201 (OneControl R5.0 OSP Installation and Configuration) 07.01

Diunggah oleh

Hak Cipta:

Format Tersedia

OneControl Unified Management System

Optical Service Provisioner

Installation and Configuration Guide

450-3251-201 - Standard Issue 07.01

Customer Technical Support/Warranty

In Europe, Middle East,

011-5255-1719-0220 (Mexico City) E-mail: sales@ciena.com

OneControl Unified Management System - OSP

Installation and Configuration Guide

IMPORTANT: PLEASE READ THIS LICENSE AGREEMENT (AGREEMENT) CAREFULLY BEFORE

OneControl Unified Management System - OSP

Installation and Configuration Guide

OneControl Unified Management System - OSP

Installation and Configuration Guide

OneControl Unified Management System - OSP

Installation and Configuration Guide

OneControl Unified Management System - OSP

Installation and Configuration Guide

Installation and upgrade

Deployment options 1-1

Uninstallation and troubleshooting

OneControl Unified Management System - OSP

Installation and Configuration Guide

Displaying the version of the installed OSP software on an HP platform 3-6

OneControl Unified Management System - OSP

Installation and Configuration Guide

About this document

This document describes the installation and configuration of the OneControl

OneControl Unified Management System - OSP

Installation and Configuration Guide

x About this document

Click the required Release.

Ciena Software Key Code Manager

Conventions used in this document

OneControl Unified Management System - OSP

Installation and Configuration Guide

About this document xi

Variable parameters appear in angle brackets, as in the following example:

An explanation of the variable may follow the command string, as in the

is the name of the CD-ROM directory

Prompts and responses from the system

Directory and path names

Buttons and menu items

Window and field names

Results of an action and comments

OneControl Unified Management System - OSP

Installation and Configuration Guide

xii About this document

OneControl Unified Management System - OSP

Installation and Configuration Guide

Installation and upgrade

Deployment options on page 1-1

Workstation requirements on page 1-3

Installation of OSP client software on page 1-3

Installation options on page 1-3

Resource Allocation tool on an HP platform on page 1-12

Upgrades on page 1-13

Procedures on page 1-13

NDS server and OSP client software components

The Network Data Server (NDS) is responsible for communicating with

OneControl Unified Management System - OSP

Installation and Configuration Guide

1-2 Installation and upgrade

by network elements to the NDS server and topological data entered in