OpenLane® 5.3.2 Service Level Management for Solaris
Quick Start Installation Instructions
Document Number 7800-A2-GZ41-40
November 2000
Product Description
Paradyne’s OpenLane® Service Level Management Solution is an open,
standards-based, highly distributable system offering robust scalability and flexible
integration points. A Web browser-enabled user interface provides accessibility
anywhere, anytime.
Paradyne’s network management solution features support for diagnostics,
real-time performance monitoring, historical reporting, and detailed health and
status indicators for Paradyne’s wide array of SNMP-managed narrow and
broadband network access device families. Support is provided for Paradyne’s
FrameSaver® and Hotwire® products. OpenLane also supports Paradyne’s 31xx,
7xxx, and 9xxx T1 and subrate access products.
Network Monitoring
OpenLane enables a customer to proactively and reactively monitor, analyze, and
troubleshoot their network with easy-to-use management tools – searching out
trouble spots and resolving them before they affect service. With OpenLane, the
user has the ability to verify line quality and the level of service provided, as well as
to monitor bandwidth utilization.
OpenLane is comprised of several integrated features that provide extensive
element, network, and service level management capabilities for network service
providers, network managers, and their end customers.
Easy Installation
OpenLane is installed through an easy-to-use graphical interface. OpenLane’s
highly scalable architecture offers flexibility to grow your system as management
scope increases. OpenLane can span customer network sizes from small
customers with a few dozen devices and a few users to carrier-class installations
with thousands of devices and many users.
7800-A2-GZ41-40
November 2000
1
OpenLane Features
„
„
„
„
„
„
Easy-to-use Web browser-based user interface
Support for the full array of Paradyne SNMP-manageable devices
Support for four levels of user access
Easy-to-use graphical interface installs and configures each module
E-commerce-class distributed architecture supports small-scale end-user
networks up to carrier-class deployments
Distributed architecture supports:
— Customer-supplied Oracle 8i database or Sybase database
— Distributed Web server
— Distributed Poller/Reader
— LDAP directory service
„
„
„
„
„
„
„
„
„
2
Integrates with HP OpenView
Online Help system with full text search capability
Device configuration through the Web interface
Scheduled and on-demand Firmware Maintenance downloads
Service Level Reporting, enabling quality of service (QoS) verification
Historical data collection and reporting (FrameSaver only)
On-demand polling
Real-time device health and status, diagnostics, and performance monitoring
Extensive Web-based diagnostics, including non-disruptive PVC loopback and
end-to-end connectivity testing
November 2000
7800-A2-GZ41-40
Product Documentation Online
Complete documentation for this product is available at www.paradyne.com.
Select Library → Technical Manuals → OpenLane Network Management
Solutions.
Document Number
Document Title
7800-A2-GZ42
OpenLane Service Level Management for Windows
Quick Start Installation Instructions
7800-A2-GZ43
OpenLane 5.3 Distributed Database Configuration
Quick Start Instructions
7800-A2-GZ44
OpenLane 5.3 Distributed Components
Configuration Quick Start Instructions
About These Instructions
These instructions provide you with the necessary information to get your
OpenLane Service Level Management software installed and running as quickly
as possible. It is not intended to be a complete, detailed reference. Please see the
online Help system for detailed instructions on specific operational aspects of the
OpenLane product. Refer to the readme.txt file for distributed infrastructure details.
Installers should be familiar with Solaris and Solaris administration functions and
tasks to use these Quick Start Installation Instructions.
Planning the Installation
Before installing OpenLane:
„
„
7800-A2-GZ41-40
Review the Installation Requirements on page 4.
Verify the JRE version on your system. Refer to Checking the Java Runtime
Environment Version on page 5.
November 2000
3
Installation Requirements
Review the following Minimum Hardware Requirements and Software
Requirements to verify that you meet the prerequisites.
Minimum Hardware Requirements
Networks with
Less Than 500 Devices*
Networks with
500–2000 Devices
Networks with
2000–5000 Devices
„
„
„
„
„
„
„
„
Sun Ultra 10
256 MB RAM
Sun Ultra 10
512 MB RAM
Sun Enterprise 450 Server
512 MB RAM
100 MB free disk space
Additional disk space for storage of performance data: 500 KB of disk space per PVC
per day (250 KB per DLCI per day)
* A device is an SNMP-manageable line card, management card, endpoint, CSU,
DSU, or other access unit.
Software Requirements
Operating
System
Sun Solaris 2.6
or
Solaris 2.8
Java Runtime Environment (JRE)
Java Runtime Environment (JRE) 1.1.8_09a
The JRE is available from Sun Microsystems at:
http://java.sun.com/products/jdk/1.1/jre/index.html
The following TCP ports are used by the OpenLane server:
„
„
„
„
„
„
Port 80: Apache Web server 1.3.12 (for http Requests)*
Port 1521: Oracle Database (if used)
Port 2099: Remote Method Invocation (RMI for Application Communications)
Port 3890: LDAP (Lightweight Directory Access Protocol) Directory Services
Port 4100: Sybase Database (if used)
Port 8007: Apache JServ (for Java Servlet Communications)
Optional: Distributed architecture with customer-supplied:
„
„
Oracle 8i (Standard or Enterprise), or
Sybase Adaptive Server Enterprise Version 11.9.2 or 12.0
OpenLane’s internal Cloudscape database will accommodate up to 180 PVCs (360
DLCIs). For larger networks, an Oracle or Sybase database must be installed.
* The port used for the Apache Web server can be changed during the installation
process. See Configuring Apache to Use a Different Port on page 17.
4
November 2000
7800-A2-GZ41-40
Web Client Software Requirements
„
Internet Explorer 5.5 (recommended for Windows-based clients)
– or –
„
Netscape Communicator 4.7 (recommended for Solaris-based clients)
Checking the Java Runtime Environment Version
Before installing the OpenLane Service Level Management software, you need to
verify that the Java Runtime Environment (JRE) has been installed correctly.
Procedure
To verify the JRE installation:
1. Open a terminal window. Type jre and press Enter.
The window should display the Java Runtime Environment Version number
and a list of options. Verify that you have Version 1.1.8_09a or above.
Version Number
2. If you receive a message that the JRE cannot be found or another version is
found, verify that the path to the correct JRE is in your PATH environment
variable. To display the PATH environment variable:
Type echo $PATH and press Enter
7800-A2-GZ41-40
November 2000
5
Upgrading from Earlier Software
If you are installing OpenLane on a system that is currently running:
„
„
„
DCE Manager, see Uninstalling DCE Manager, below.
Performance Wizard 4.2, see Uninstalling Performance Wizard, below.
An earlier version of OpenLane 5, the upgrade is handled automatically
during the OpenLane installation. Do not uninstall the earlier version. If you
use an Oracle or Sybase database, use the appropriate migration script to
update the schema. See Migration to 5.3.2 for Oracle or Sybase on page 11.
Uninstalling DCE Manager
To uninstall DCE Manager, follow this procedure before installing OpenLane:
Procedure
1. Start the DCEinstall program.
— If you downloaded the software from the World Wide Web, change to the
directory where you expanded the file and run the installation program:
cd <directory>
./DCEinstall
— If you mounted the CD-ROM for Sun systems:
cd /tmp/cdrom/DCE/SOLARIS2
./DCEinstall
2. The script detects the existing version and prompts you to uninstall it. Select
OK.
3. When the software is uninstalled, the installation script prompts you to install
DCE Manager. Select No.
Uninstalling Performance Wizard
Procedure
1. Run UnInstallToOV:
cd /opt/OV/pdn/PerfWiz
./UnInstallToOV
2. Delete the /opt/OV/pdn/ directory and all subordinate directories and files:
rm -rf /opt/OV/pdn
6
November 2000
7800-A2-GZ41-40
The OpenLane Installation Program
The OpenLane installation program:
„
Optionally installs and configures the Apache 1.3.12 Web server and the
Apache JServ. (This is not required for upgrades from earlier versions of
OpenLane 5.)
By default, the Apache software is installed with the following parameters:
Apache Parameter
Setting
Installation directory
/opt/apache
TCP Port for http requests
80
User
nobody
Group
nobody
These options can be changed during the installation process. To modify the
Apache Web server to use a port other than port 80 after installation, see
Configuring Apache to Use a Different Port on page 17.
The default installation path for Apache software is:
/opt/apache
„
Installs the OpenLane components, including the Cloudscape Java SQL
Database.
The default installation path for OpenLane software is:
/opt/pdn/OpenLane
„
„
Provides a startup command to control all Apache and OpenLane processes.
Includes Management Platform Integration Adapters for HP OpenView
Network Node Manager for Sun Solaris.
The software-based platform adapters provide integration points for:
— Paradyne device-specific map icon creation
— Trap definition files
In addition, OpenLane is added to OpenView’s menu structure.
NOTES:
— You do not have to install the Apache Web server in /opt/apache and
OpenLane in /opt/pdn/OpenLane. However, it is highly recommended
that you install Apache and OpenLane on the same mount point.
If you do not use the standard directory names, substitute the names you
use for the directory references in this document.
— If you will be distributing the Web server, you must install OpenLane and
Apache in the same directory path on the Web server and the OpenLane
Management system.
7800-A2-GZ41-40
November 2000
7
Obtaining a License Key
An OpenLane license key is required to install OpenLane. If you are upgrading an
earlier version of OpenLane 5, the installation program automatically uses the
existing license key. Otherwise you can request a temporary license key from the
Paradyne Web site. A 30-day temporary license key is provided by e-mail.
After purchasing the product, a license key form is provided. Complete and fax the
license key form to obtain your permanent license key.
Installing from Paradyne’s Web Site
Procedure
1. Log on to the system as root.
2. Obtain a temporary license key and the OpenLane software from
www.paradyne.com/pdn/key. You will not require the license key if you are
upgrading a version of OpenLane 5.
3. Save the setup.sh file in /tmp or any directory you choose.
4. Exit your Web browser if it is running. Change to the /tmp directory.
5. Change the file permissions:
chmod 777 setup.sh
6. Run the setup.sh file:
./setup.sh
7. Follow the instructions on each screen with these exceptions:
— If you are upgrading a version of OpenLane 5, do not remove the old
version when prompted. Select Continue.
— When prompted for the Apache User and Group information, use:
— User = nobody
— Group = nobody
8
November 2000
7800-A2-GZ41-40
Installing from CD-ROM
Procedure
1. Log on to the system as root.
2. Exit your Web browser if it is running. Insert the OpenLane CD-ROM into the
CD-ROM drive and mount it.
3. Change to the CD-ROM drive.
4. Change to the OpenLane directory and run the setup.sh file.
5. Follow the instructions on each screen with these exceptions:
— If you are upgrading a version of OpenLane 5, do not remove the old
version when prompted. Select Continue.
— When prompted for the Apache User and Group information, use:
— User = nobody
— Group = nobody
Installing from FTP Files
Contact Technical Support to arrange this type of installation:
„
7800-A2-GZ41-40
1-800-795-8004
November 2000
9
Installing Remotely Using X
You can install OpenLane from a remote host using the X windows system.
Procedure
1. On the local host, execute the following commands:
xhost + remote_host_name
rlogin remote_host_name -l username
username must have root privilege.
2. On the remote host, execute the following command or commands:
If using the Bourne shell (sh):
DISPLAY=local_host_name:0.0
export DISPLAY
If using the Korn shell (ksh):
export DISPLAY=local_host_name:0.0
If using the C shell (csh):
setenv DISPLAY local_host_name:0.0
3. On the remote host, change the directory to the path where setup.sh resides:
cd /tmp
4. Run setup.sh:
./setup.sh
Installing the Permanent License Key
Procedure
1. Change the directory to /opt/pdn/OpenLane:
cd /opt/pdn/OpenLane
2. Enter the command to install the permanent key:
OLCmd key permanent_key
Where permanent_key is the key faxed to you by Paradyne. For example:
OLCmd key ALUKB-KAC9Y-H987N-CX5GK
10
November 2000
7800-A2-GZ41-40
Locating the License Key On an Installed System
To locate the license key on the system once OpenLane is installed, use one of
these methods:
„
„
Display the OpenLane About screen by clicking the About OpenLane
Service Level Management link on the OpenLane Administration screen
Display the /opt/pdn/OpenLane/pdnKey.txt file using a text editor
Migration to 5.3.2 for Oracle or Sybase
If you use an Oracle or a Sybase database for OpenLane, you must run a
migration script to update the schema after OpenLane is installed.
Procedure
1. If OpenLane is running, stop it:
OLControl stop
2. Start the SQL processor for your database (SQL*Plus or SQL Advantage).
3. Execute the appropriate script:
/opt/pdn/OpenLane/data/sql/scripts/Oracle/migrateOL532.sql
– or –
/opt/pdn/OpenLane/data/sql/scripts/Sybase/migrateSYB532.sql
7800-A2-GZ41-40
November 2000
11
Starting OpenLane Web and Database Services
Procedure
1. From a terminal window, change the directory to /opt/pdn/OpenLane:
cd /opt/pdn/OpenLane
2. Type OLControl start and press Enter. The following services are started:
— Apache Web Server
— Cloudscape JDBMS
— OpenLane Services
— RMI Application Server
— SCM Poller
— OpenLDAP Directory Services
— User History Poller
— User History Reader
NOTE:
The OpenLane new installation is complete. Continue with Accessing the
OpenLane Web Applications on page 13.
Stopping OpenLane Web and Database Services
Procedure
1. From a terminal window, change the directory to /opt/pdn/OpenLane:
cd /opt/pdn/OpenLane
2. Type OLControl stop and press Enter.
12
November 2000
7800-A2-GZ41-40
Accessing the OpenLane Web Applications
Procedure
1. Using your Web browser, enter the URL of the OpenLane system.
Example: http://172.24.9.1/OpenLane/
NOTE:
You can use the IP address or the host machine name in the URL to
access the OpenLane system.
2. When the OpenLane login screen appears, enter Admin in the Customer Id
field to access the system as an administrator.
You are now ready to create additional Customer Profiles and add manageable
devices. See the OpenLane online help for more information.
Adding a Device
Procedure
To add a device to the OpenLane System:
1. If you have not already done so, log in to the OpenLane system with the
customer ID of:
Admin
2. Select the Network Diagnostics link.
3. Select the New Device button from the bottom frame on the screen.
7800-A2-GZ41-40
November 2000
13
4. The following New Device screen appears:
New Device
Field Names
Field Description*
IP Address
IP Address of the device being added.
Read Community
Read Community Name. Must match the Read Community Name
set in the device. Default = public.
Write Community
Write Community Name. Must match the Write Community Name
set in the device. Default = public.
FTP Login
FTP Login. Must match FTP Login in this device. Used by RMON
Data Collection and Firmware Download.
FTP Password
FTP Password. Must match FTP Password in this device. Used by
RMON Data Collection and Firmware Download.
Enable Polling
Enables RMON Data Collection. Default = Disabled.
Enable SCM
Polling
Enables polling for Hotwire GranDSLAM devices. Used to speed
the display of cross-connect information. Default = Disabled.
Polling Domain
User history polling domain. Should be left as “default.”
Polling Interval
Number of minutes between each RMON Data Collection.
Default = 480 minutes.
Keep Data For
Number of calendar days to keep RMON data for this device in the
SQL database. Used by the dbage utility. Default = 100 calendar
days.
Save
Adds the new device to the OpenLane Directory Services
database.
* Default values for fields can altered by modifying the file Preferences.dat. See the
OpenLane online Help for information.
14
November 2000
7800-A2-GZ41-40
New Device
Field Names
Save and Sync
Field Description*
Adds the new device to the OpenLane Directory Services
database and performs a device synchronization to ensure that
the OpenLane directory matches the current configuration of the
device. The behavior of the device synchronization can be
changed using the following options:
Device Sync Options:
❑
❑
❑
Discover circuits and endpoints
Resync already discovered endpoints
Overwrite circuit names
* Default values for fields can altered by modifying the file Preferences.dat. See the
OpenLane online Help for information.
5. Make sure Discovered circuits and endpoints is checked and click
on Save and Sync.
6. Use the Device Browser to verify that the device is added properly and
endpoints and circuits are discovered. See the OpenLane online Help for more
information.
Adding a Customer ID
Procedure
To create a new Customer ID for Web-based report access:
1. Log in to the OpenLane system with the Customer ID of:
Admin
2. Choose Customer Profiles.
3. Under 1. Select a customer profile, enter a new Customer ID.
4. Under 2. Select an action to perform on the customer
profile:, select Create a new customer profile.
7800-A2-GZ41-40
November 2000
15
5. The following form appears:
6. Fill in the customer information in the fields provided.
7. Under 2. Select a system access level, select one of Scheduled
Reports Only, Reports Only, or Realtime:
— Scheduled Reports Only – User can view scheduled FrameSaver SLV
reports.
— Reports Only – User can view scheduled FrameSaver SLV reports and
DSL inventory reports, and run on-demand reports.
— Realtime – User can generate Performance graphs (real-time and
historical), generate on-demand reports, view scheduled reports, view
Health and Status, view configurations, run nondisruptive tests, and use
the Device Browser in read-only mode. Apache user access
authentication must be active for read-only restrictions to be enforced on a
user with Realtime access. See Apache User Access Authentication on
page 18.
The Administrative access level gives the user read/write access to all
features, including scheduling reports and running disruptive tests, so is not
ordinarily suitable for a customer.
16
November 2000
7800-A2-GZ41-40
8. Press the Save button to save the customer profile.
9. Assign devices to the customer using the Modify Assigned Devices link of the
Customer Profile Administration screen.
Configuring Apache to Use a Different Port
By default, the Apache Web server is installed and configured to use TCP port 80
(unless you changed it at installation time). You can configure the Apache Web
server to use another port after installation, as long as that port is not in use by
another service.
Procedure
To change the TCP port:
1. From a terminal window, change the directory to /opt/pdn/OpenLane:
cd /opt/pdn/OpenLane
2. To stop OpenLane, type OLControl stop and press Enter.
3. Change the directory to /opt/apache/conf:
cd /opt/apache/conf
4. Edit the file httpd.conf using a text editor, such as vi.
5. Find the entry for PORT. Change the value from 80 to the new port number.
6. Save the file after making changes.
7. Change the directory to /opt/pdn/OpenLane:
cd /opt/pdn/OpenLane
8. To start OpenLane, type OLControl start and press Enter.
7800-A2-GZ41-40
November 2000
17
Apache User Access Authentication
User Access Authentication provides password protection to OpenLane through
the Apache server. When authentication is enabled, the first OpenLane Login
page displays a Log In! button instead of an Enter your Customer Id prompt.
Clicking on the button invokes a window for entering User Name and Password.
Follow this procedure to configure HTTP Challenge/Response for OpenLane
access authentication with the Apache Web server.
Procedure
1. If OpenLane is running, open a terminal window and change the directory to
/opt/pdn/OpenLane:
cd /opt/pdn/OpenLane
Type OLControl stop and press Enter.
2. Change the directory to /opt/apache/conf:
cd /opt/apache/conf
3. Edit the file: httpd.conf
If the Apache configuration files were installed with OpenLane, then the
following text is commented out in the httpd.conf file. Uncomment the text and
make sure the AuthUserFile path is correct.
<Location "/OLServlets/*"
order allow,deny
allow from all
AuthType Basic
AuthName "OpenLane"
AuthUserFile /opt/pdn/OpenLane/database/config/.htpasswd
require valid-user
</Location>
If the commented text is not found, add the text as shown to the bottom of the
httpd.conf file.
4. Change the directory to /opt/apache/bin:
cd /opt/apache/bin
5. Run htpasswd. The first time you use the htpasswd command, use the -c
parameter to create the password file:
htpasswd -c /opt/pdn/OpenLane/database/config/.htpasswd
username
Where username is the name of the user being added.
Enter a password when prompted.
6. Add additional usernames by running htpasswd without the -c parameter:
htpasswd /opt/pdn/OpenLane/database/config/.htpasswd
otheruser
18
November 2000
7800-A2-GZ41-40
7. Change the directory to /opt/pdn/OpenLane:
cd /opt/pdn/OpenLane
8. Turn on authentication with the confauth command:
OLCmd confauth on
9. To start OpenLane, type OLControl start and press Enter.
7800-A2-GZ41-40
November 2000
19
Warranty, Sales, Service, and Training Information
Contact your local sales representative, service representative, or distributor
directly for any help needed. For additional information concerning warranty, sales,
service, repair, installation, documentation, training, distributor locations, or
Paradyne worldwide office locations, use one of the following methods:
„
„
Internet: Visit the Paradyne World Wide Web site at www.paradyne.com.
(Be sure to register your warranty at www.paradyne.com/warranty.)
Telephone: Call our automated system to receive current information by fax
or to speak with a company representative.
— Within the U.S.A., call 1-800-870-2221
— Outside the U.S.A., call 1-727-530-2340
Document Feedback
We welcome your comments and suggestions about this document. Please mail
them to Technical Publications, Paradyne Corporation, 8545 126th Ave. N., Largo,
FL 33773, or send e-mail to userdoc@paradyne.com. Include the number and
title of this document in your correspondence. Please include your name and
phone number if you are willing to provide additional clarification.
Trademarks
FrameSaver, Hotwire, MVL, and OpenLane are registered trademarks of Paradyne
Corporation. All other products and services mentioned herein are the trademarks,
service marks, registered trademarks, or registered service marks of their
respective owners.
.
*7800-A2-GZ41-40*
Copyright © 2000 Paradyne Corporation. Printed in U.S.A.
20
November 2000
7800-A2-GZ41-40