Professional Documents
Culture Documents
450-3251-201 (OneControl R5.0 OSP Installation and Configuration) 07.01
450-3251-201 (OneControl R5.0 OSP Installation and Configuration) 07.01
Whats inside...
Installation and upgrade
Configuration
Uninstallation and troubleshooting
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
1-800-CIENA24 (243-6224)
410-865-4961
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
E-mail: sales@ciena.com
In Europe
+44-207-012-5500 (UK)
E-mail: sales@ciena.com
In Asia
+81-3-3248-4680 (Japan)
E-mail: sales@ciena.com
In India
+91-124-434-0500
E-mail: sales@ciena.com
In Latin America
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.
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.
Publication history
August 2015
Issue 07.01 of the OneControl Unified Management System 5.0 Optical
Service Provisioner Installation and Configuration Guide.
January 2015
Issue 06.01 of the OneControl Unified Management System 4.2 Optical
Service Provisioner Installation and Configuration Guide.
August 2014
Issue 05.01 of the OneControl Unified Management System 4.1 Optical
Service Provisioner Installation and Configuration Guide.
April 2014
Issue 04.01 of the OneControl Unified Management System 4.0 Optical
Service Provisioner Installation and Configuration Guide.
December 2013
Issue 03.01 of the OneControl Unified Management System 3.2 Optical
Service Provisioner Installation and Configuration Guide.
July 2013
Issue 02.01 of the OneControl Unified Management System 3.1 Optical
Service Provisioner Installation and Configuration Guide.
April 2013
Issue 01.01 of the OneControl Unified Management System 3.0 Optical
Service Provisioner Installation and Configuration Guide.
vi Publication history
vii
Contents
Publication history
About this document
v
ix
1-1
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
viii Contents
3-4
3-5
3-6
3-7
ix
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.
4
5
6
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).
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.
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.
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.
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
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.
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.
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.
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.
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 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.
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
Description
User choice
Is blank connection ID
allowed?
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
Description
User choice
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:
Single - Select this option (also known as the
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.
Description
User choice
Description
User choice
Description
User choice
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.
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:
Procedures
This section contains the following procedures:
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:
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
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
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
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>
If the response is anything else, see the Applications Platform Installation and
Administration Guide, 450-3101-201.
Starting the software installation
3
Action
If
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
Action
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:
SONET
NE
yes
yes
disabled
none
none
Then
continued
Action
12
Then
GUI only
Selecting the preferred standard for the display of connection rates, statuses, and payloads
13
Then
SONET formats
SDH formats
Action
If you want to
Then
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
Then go to
step 16
step 16
step 25
Action
Then
Then
continued
Action
Then
continued
Action
Action
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
Then go to
step 35
continued
Action
25
Then
Then
enter 1 and go to
step 31
continued
Action
Then
continued
Action
Action
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.
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
Action
Then
Action
Note 2: If the addition failed, verify that you have the correct IP address and
try to add the server again.
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
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.
Alternate topology server set to 43.1.2.3.
If the following message appears, 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 IP 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.
continued
Action
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:
preferred port naming type:
maximum instances:
maximum connection ID length:
blank connection ID allowed:
SONET
NE
no
yes
If you enter n at this point, you must answer all the questions again. Enter y
and go to step 37.
continued
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
========================================================
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
========================================================
Do you wish to continue [y/n]? y
continued
Action
Enter y to continue in both cases.
Note: Do not interrupt the installation or upgrade at this stage.
38
39
If you are installing using the OSP installation CD, unmount the CD by
entering:
cd /
/sbin/umount /cdrom
40
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
Before you perform this procedure, you must
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.
Step
Action
Log in to the workstation where you plan to install the OSP software using the
oneadmin user ID and password.
continued
Action
step 3
step 13
Then go to
Solaris
step 5
Linux
step 7
For Solaris
5
Then
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
10
11
12
Go to step 15.
13
14
15
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
Action
17
18
19
Then go to
software DVD
step 19
software download
step 21
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
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
Action
To display the current settings, see Displaying the current OSP configuration
settings on page 3-9.
25
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:
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
Before you perform this procedure, you must
Step
Action
continued
Action
You can delete the online help directory. This is the directory from step 2.
rm -R /<directory>
end
2-1
Configuration
2-
Procedures
This section contains the following 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
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
Before you perform this procedure, you must
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.
Configuration 2-3
Procedure 2-1 (continued)
Configuring OSP access privileges for Manager for 6k, OM5k and CPL users on a Linux or Solaris
platform
Step
Action
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
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.
Each prompt presents a default choice (a number that represents a line in a
list) you can select by pressing Enter. In addition:
At most prompts, you can abort the changes by entering the command
abort.
Requirements
Before you perform this procedure, you must
complete Table 1-1 on page 1-4 and, if required, Table 1-2 on page 1-12
Step
Action
Log in to the workstation containing the OSP software using the root user ID
and password.
Configuration 2-5
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
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
2-6 Configuration
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
Step
Action
Then
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
continued
Configuration 2-7
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
Step
Action
Selecting the preferred standard for the display of connection rates for the GUI
6
Then
SONET format
SDH format
Then
universal format
2-8 Configuration
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
Step
Action
Selecting the preferred standard for the display of connection rates for this NDS server
11
Then
SONET format
SDH format
Configuration 2-9
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
Step
Action
Then
universal format
2-10 Configuration
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
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
Adding an NDS server to the list
15
Configuration 2-11
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
Step
Action
2-12 Configuration
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
Step
Action
Configuration 2-13
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
Step
Action
21
Return to step 5. If the selection failed, verify that you have the correct IP
address and try to add the server again.
continued
2-14 Configuration
Procedure 2-2 (continued)
Editing OSP configuration settings on an HP platform
Step
Action
SONET
NE
10
64
yes
enabled
43.12.3.73
none
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
Linux or Solaris operating system.
This procedure shows all options, as available for a workstation on which both
a GUI and an NDS server are installed.
Each prompt presents a default choice (a number that represents a line in a
list) that you can select by pressing Enter. In addition:
At most prompts, you can abort the changes by entering the command
abort.
Requirements
Before you perform this procedure, you must
complete Table 1-1 on page 1-4 and, if required, Table 1-2 on page 1-12
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
Log in to the workstation containing the OSP software using the root user ID
and password.
Verifying the LAN line interface (only one LAN line interface must be active)
2
2-16 Configuration
Procedure 2-3 (continued)
Editing OSP configuration settings on a Linux or Solaris platform
Step
Action
Configuration 2-17
Procedure 2-3 (continued)
Editing OSP configuration settings on a Linux or Solaris platform
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).
Then
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
continued
2-18 Configuration
Procedure 2-3 (continued)
Editing OSP configuration settings on a Linux or Solaris platform
Step
Action
Selecting the preferred standard for the display of connection rates for the GUI
8
Then
SONET format
SDH format
Then
NE type-specific format
universal format
Configuration 2-19
Procedure 2-3 (continued)
Editing OSP configuration settings on a Linux or Solaris platform
Step
Action
Selecting the preferred standard for the display of connection rates for this NDS server
12
Then
SONET format
SDH format
2-20 Configuration
Procedure 2-3 (continued)
Editing OSP configuration settings on a Linux or Solaris platform
Step
Action
Then
NE type-specific format
universal format
Configuration 2-21
Procedure 2-3 (continued)
Editing OSP configuration settings on a Linux or Solaris platform
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
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
2-22 Configuration
Procedure 2-3 (continued)
Editing OSP configuration settings on a Linux or Solaris platform
Step
Action
Configuration 2-23
Procedure 2-3 (continued)
Editing OSP configuration settings on a Linux or Solaris platform
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.
2-24 Configuration
Procedure 2-3 (continued)
Editing OSP configuration settings on a Linux or Solaris platform
Step
Action
The workstation must be physically connected and configured on the LAN
and IP address updated in the /etc/hosts file on both servers for the script
to validate the address.
Return to step 7. If the selection failed, verify that you have the correct IP
address and try to add the server again.
SONET
NE
64
yes
enabled
1.2.3.4(localhost)
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
Go to the directory:
C:\Users\Public\OSP_Client_<version>
where
<version>
Using a text editor, open the ocm.properties file. For a summary of the
properties, see Table 2-1 on page 2-26.
2-26 Configuration
Procedure 2-4 (continued)
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
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
Default value:
false
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
ocm.nameServer
Entry format:
ocm.nameServer[.X] = corbaloc::<host
IP>:<port>/NameService
Examples:
ocm.nameServer =
corbaloc::10.0.0.1:58772/NameService
ocm.nameServer.1 =
corbaloc::10.0.0.2:58772/NameService
ocm.omeaServerIp
see the
Description
column
Default value:
localhost
2-28 Configuration
Table 2-1
Summary of OSP configurable properties on a Windows platform (continued)
Property
Possible values
Description
ocm.spanSourceIp
see the
Description
column
Default value:
localhost
Examples:
ocm.spanSourceIp = localhost
ocm.spanSourceIp.1 = 1.2.3.4
ocm.preferredServer
true
ocm.preCaching
Configuration 2-29
Table 2-1
Summary of OSP configurable properties on a Windows platform (continued)
Property
Possible values
Description
ocm.networkAuditDay
1 to 7
Default value: 7
ocm.networkAuditHour
ocm.networkAuditMinute
ocm.networkAuditOccurrence
Default value: 0
0 to 59
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
2-30 Configuration
Table 2-1
Summary of OSP configurable properties on a Windows platform (continued)
Property
Possible values
Description
nds.cacheDumpDay
1 to 7
Default value: 1
nds.cacheDumpHour
0 to 23
Default value: 0
nds.cacheDumpMinute
0 to 59
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.
Configuration 2-31
Table 2-1
Summary of OSP configurable properties on a Windows platform (continued)
Property
Possible values
Description
ocm.connectionquery.maxRequestAtte
mpts
1 to 3
>0
Integer value that
is greater than
zero.
15 to 99
Default value: 64
ocm.topologyPollingInterval
Default value: 60
ocm.topologyEnabled
false
true
Default value:
false
2-32 Configuration
Table 2-1
Summary of OSP configurable properties on a Windows platform (continued)
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
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
nbi.logDuration
Default value: 24
Configuration 2-33
Table 2-1
Summary of OSP configurable properties on a Windows platform (continued)
Property
Possible values
Description
xdr.logSize
Default value: 25
nbi.logSize
Default value: 25
xdr.logRotation
Default value: 5
nbi.logRotation
Default value: 5
nds.toleranceLog
true
false
Default value:
false
end
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
Linux or Solaris operating system.
Requirements
Before you perform this procedure, you must
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
Configuration 2-35
Procedure 2-5 (continued)
Configuring OSP for resiliency on Linux or Solaris platform
Step
Action
Select a configuration option to manage the NDS server list by entering the
corresponding number.
If you want to
Then
enter 9
enter 10
manage Manager for 6k, OM5k and CPL list used by OSP
GUI clients
enter 11
Enter 2.
The following message appears:
Enter the address of the server ['q' to return to the
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:
Validating address... done.
Server 1.2.3.4 added.
If the following message appears, 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 on both servers for the script to
validate the address.
continued
2-36 Configuration
Procedure 2-5 (continued)
Configuring OSP for resiliency on Linux or Solaris platform
Step
Action
If
Then
you want to exit without applying any changes enter 0 and you have
completed this procedure
end
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:
Requirements
Before you perform this procedure, you must
Step
Action
Log in to the workstation containing the OSP software using the root user ID
and password.
2-38 Configuration
Procedure 2-6 (continued)
Configuring the NEs/controllers for an NDS server on an HP platform
Step
Action
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
Then
enter 2 then
enter 2 then
enter 1 and
go to step 6
enter 2 then
enter 2 then
enter 2 and
go to step 10
enter 2 then
enter 3 and
go to step 15
enter 3 then
enter 2 then
enter 1 and
go to step 19
continued
Configuration 2-39
Procedure 2-6 (continued)
Configuring the NEs/controllers for an NDS server on an HP platform
Step
Action
If you want to
Then
enter 3 then
enter 3 and
go to step 28
enter 1 and
go to step 32
enter 2 then
enter 1 then
go to step 37
enter 3 then
enter 1 then
go to step 40
enter 2 then
enter 4 then
go to step 43
enter 3 then
enter 4 then
go to step 47
enter 5 and
go to step 51
enter 6 and
go to step 54
enter 0 and
go to step 56
continued
2-40 Configuration
Procedure 2-6 (continued)
Configuring the NEs/controllers for an NDS server on an HP platform
Step
Action
OPT-DX? (Y/N) :
Enter Y.
8
Go to step 5.
10
11
12
13
14
Go to step 5.
15
Configuration 2-41
Procedure 2-6 (continued)
Configuring the NEs/controllers for an NDS server on an HP platform
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
20
Enter the number corresponding to the span of the NE. The following is an
example of the menu that appears:
[0] Return to the previous menu
[1] 1615 Montreal
[2] 1617 Toronto
Displaying 1 - 2 of 2
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
23
Go to step 5.
24
25
Enter the controller IP address and the NE ID, press Enter, and confirm your
selection.
26
27
Go to step 5.
continued
2-42 Configuration
Procedure 2-6 (continued)
Configuring the NEs/controllers for an NDS server on an HP platform
Step
Action
28
29
Enter the number corresponding to the software release and confirm your
selection.
30
Select 0 to return to the previous menu and 0 again to return to the main
menu.
31
Go to step 5.
32
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
35
Enter Y.
continued
Configuration 2-43
Procedure 2-6 (continued)
Configuring the NEs/controllers for an NDS server on an HP platform
Step
Action
36
Go to step 5.
37
38
Select 0 to return to the previous menu and 0 again to return to the main
menu .
39
Go to step 5.
40
41
Select 0 to return to the previous menu and 0 again to return to the main
menu.
42
Go to step 5.
43
44
Enter the number corresponding to the span to be included and confirm your
choice.
45
Select 0 to return to the previous menu and 0 again to return to the main
menu.
46
Go to step 5.
continued
2-44 Configuration
Procedure 2-6 (continued)
Configuring the NEs/controllers for an NDS server on an HP platform
Step
Action
47
48
49
Select 0 to return to the previous menu and 0 again to return to the main
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
55
Go to step 5.
56
Select 0.
end
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:
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
2-46 Configuration
Procedure 2-7 (continued)
Starting, stopping, restarting, or displaying status of the OSP components on an HP platform
Step
Action
Then enter
./osp_admin start
./osp_admin stop
./osp_admin restart
./osp_admin status
3-1
3-
This section describes how to uninstall and troubleshoot the OSP software.
Procedures
This section contains the following procedures:
Procedure 3-7, Displaying log files for OSP software installation and
uninstallation on page 3-13
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
Before you perform this procedure, you must
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
Action
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
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
Before you perform this procedure, you must
make sure all local and remote OSP client sessions communicating with
the NDS server to be removed have been closed
Step
Action
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
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
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).
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
Before you perform this procedure, you must
be able to log in to the OSP workstation using the root user account
Step
Action
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
Before you perform this procedure, you must
be able to log in to the OSP workstation using the oneadmin user account
Step
Action
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
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
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
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).
Action
(example for HP platform)
========================================================
Current configuration:
GUI
preferred standard:
SONET
GUI
NE
GUI
maximum instances:
14
GUI
16
GUI
no
SONET
NE
enabled
47.134.40.145
none
Action
(example for Linux or Solaris platform)
========================================================
Current configuration:
GUI
preferred standard:
SONET
GUI
NE
GUI
64
GUI
no
SONET
NE
enabled
47.134.40.118
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
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
Before you perform this procedure, you must
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
Use a text editor to open the log file and display the content of the file.
end