Beta Draft Confidential

Network Management Station Installation Guide

For NavisCore Release 08.00.03.00

Product Code: 80130 Revision 04 September 2004 Beta Draft Confidential

Copyright© 2004 Lucent Technologies. All Rights Reserved.

This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the express written consent of Lucent Technologies.

For permission to reproduce or distribute, please contact: Technical Publications, Integrated Network Solutions/Core Switching Division at 978-692-2600.

Notice. Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change.

Trademarks. IP Navigator, Navis, NavisXtend, Navis iEngineer, NavisCore, and GX 550 are trademarks of Lucent Technologies. CBX 500 and B-STDX 9000 are registered trademarks of Lucent Technologies. Other trademarks and trade names mentioned in this document belong to their respective owners.

Limited Warranty. Lucent Technologies provides a limited warranty to this product. For more information, see the software license agreement in this document.

Ordering Information. To order copies of this document, use the online ordering instructions presented later in this guide.

Support Telephone Numbers. For technical support and other services, see the customer support contact information in the “About This Guide” section of this document.

ii8/30/04 Network Management Station Installation Guide Beta Draft Confidential

LUCENT TECHNOLOGIES END-USER LICENSE AGREEMENT

LUCENT TECHNOLOGIES IS WILLING TO LICENSE THE ENCLOSED SOFTWARE AND ACCOMPANYING USER DOCUMENTATION (COLLECTIVELY, THE “PROGRAM”) TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. PLEASE READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY BEFORE OPENING THE PACKAGE(S) OR USING THE LUCENT SWITCH(ES) CONTAINING THE SOFTWARE, AND BEFORE USING THE ACCOMPANYING USER DOCUMENTATION. OPENING THE PACKAGE(S) OR USING THE LUCENT SWITCH(ES) CONTAINING THE PROGRAM WILL INDICATE YOUR ACCEPTANCE OF THE TERMS OF THIS LICENSE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY THE TERMS OF THIS LICENSE AGREEMENT, LUCENT IS UNWILLING TO LICENSE THE PROGRAM TO YOU, IN WHICH EVENT YOU SHOULD RETURN THE PROGRAM WITHIN TEN (10) DAYS FROM SHIPMENT TO THE PLACE FROM WHICH IT WAS ACQUIRED, AND YOUR LICENSE FEE WILL BE REFUNDED. THIS LICENSE AGREEMENT REPRESENTS THE ENTIRE AGREEMENT CONCERNING THE PROGRAM BETWEEN YOU AND LUCENT, AND IT SUPERSEDES ANY PRIOR PROPOSAL, REPRESENTATION OR UNDERSTANDING BETWEEN THE PARTIES.

1. License Grant. Lucent hereby grants to you, and you accept, a non-exclusive, non-transferable license to use the computer software, including all patches, error corrections, updates and revisions thereto in machine-readable, object code form only (the “Software”), and the accompanying User Documentation, only as authorized in this License Agreement. The Software may be used only on a single computer owned, leased, or otherwise controlled by you; or in the event of inoperability of that computer, on a backup computer selected by you. You agree that you will not pledge, lease, rent, or share your rights under this License Agreement, and that you will not, without Lucent’s prior written consent, assign or transfer your rights hereunder. You agree that you may not modify, reverse assemble, reverse compile, or otherwise translate the Software or permit a third party to do so. You may make one copy of the Software and User Documentation for backup purposes. Any such copies of the Software or the User Documentation shall include Lucent’s copyright and other proprietary notices. Except as authorized under this paragraph, no copies of the Program or any portions thereof may be made by you or any person under your authority or control.

2. Lucent’s Rights. You agree that the Software and the User Documentation are proprietary, confidential products of Lucent or Lucent's licensor protected under US copyright law and you will use your best efforts to maintain their confidentiality. You further acknowledge and agree that all right, title and interest in and to the Program, including associated intellectual property rights, are and shall remain with Lucent or Lucent's licensor. This License Agreement does not convey to you an interest in or to the Program, but only a limited right of use revocable in accordance with the terms of this License Agreement.

Network Management Station Installation Guide 8/30/04iii Beta Draft Confidential

3. License Fees. The license fees paid by you are paid in consideration of the license granted under this License Agreement.

4. Term. This License Agreement is effective upon your opening of the package(s) or use of the switch(es) containing Software and shall continue until terminated. You may terminate this License Agreement at any time by returning the Program and all copies or portions thereof to Lucent. Lucent may terminate this License Agreement upon the breach by you of any term hereof. Upon such termination by Lucent, you agree to return to Lucent the Program and all copies or portions thereof. Termination of this License Agreement shall not prejudice Lucent's rights to damages or any other available remedy.

5. Limited Warranty. Lucent warrants, for your benefit alone, for a period of 90 days from the date of shipment of the Program by Lucent (the “Warranty Period”) that the program diskettes in which the Software is contained are free from defects in material and workmanship. Lucent further warrants, for your benefit alone, that during the Warranty Period the Program shall operate substantially in accordance with the User Documentation. If during the Warranty Period, a defect in the Program appears, you may return the Program to the party from which the Program was acquired for either replacement or, if so elected by such party, refund of amounts paid by you under this License Agreement. You agree that the foregoing constitutes your sole and exclusive remedy for breach by Lucent of any warranties made under this Agreement. EXCEPT FOR THE WARRANTIES SET FORTH ABOVE, THE PROGRAM IS LICENSED “AS IS”, AND LUCENT DISCLAIMS ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTIES OF NONINFRINGEMENT.

6. Limitation of Liability. Lucent’s cumulative liability to you or any other party for any loss or damages resulting from any claims, demands, or actions arising out of or relating to this License Agreement shall not exceed the greater of: (i) ten thousand US dollars ($10,000) or (ii) the total license fee paid to Lucent for the use of the Program. In no event shall Lucent be liable for any indirect, incidental, consequential, special, punitive or exemplary damages or lost profits, even if Lucent has been advised of the possibility of such damages.

iv8/30/04 Network Management Station Installation Guide Beta Draft Confidential

7. Proprietary Rights Indemnification. Lucent shall at its expense defend you against and, subject to the limitations set forth elsewhere herein, pay all costs and damages made in settlement or awarded against you resulting from a claim that the Program as supplied by Lucent infringes a United States copyright or a United States patent, or misappropriates a United States trade secret, provided that you: (a) provide prompt written notice of any such claim, (b) allow Lucent to direct the defense and settlement of the claim, and (c) provide Lucent with the authority, information, and assistance that Lucent deems reasonably necessary for the defense and settlement of the claim. You shall not consent to any judgment or decree or do any other act in compromise of any such claim without first obtaining Lucent’s written consent. In any action based on such a claim, Lucent may, at its sole option, either: (1) obtain for you the right to continue using the Program, (2) replace or modify the Program to avoid the claim, or (3) if neither (1) nor (2) can reasonably be effected by Lucent, terminate the license granted hereunder and give you a prorata refund of the license fee paid for such Program, calculated on the basis of straight-line depreciation over a five-year useful life. Notwithstanding the preceding sentence, Lucent will have no liability for any infringement or misappropriation claim of any kind if such claim is based on: (i) the use of other than the current unaltered release of the Program and Lucent has provided or offers to provide such release to you for its then current license fee, or (ii) use or combination of the Program with programs or data not supplied or approved by Lucent to the extent such use or combination caused the claim.

8. Export Control. You agree not to export or disclose to anyone except a United States national any portion of the Program supplied by Lucent without first obtaining the required permits or licenses to do so from the US Office of Export Administration, and any other appropriate government agency.

9. Governing Law. This License Agreement shall be construed and governed in accordance with the laws and under the jurisdiction of the Commonwealth of Massachusetts, USA. Any dispute arising out of this Agreement shall be referred to an arbitration proceeding in Boston, Massachusetts, USA by the American Arbitration Association.

10. Miscellaneous. If any action is brought by either party to this License Agreement against the other party regarding the subject matter hereof, the prevailing party shall be entitled to recover, in addition to any other relief granted, reasonable attorneys’ fees and expenses of arbitration. Should any term of this License Agreement be declared void or unenforceable by any court of competent jurisdiction, such declaration shall have no effect on the remaining terms hereof. The failure of either party to enforce any rights granted hereunder or to take action against the other party in the event of any breach hereunder shall not be deemed a waiver by that party as to subsequent enforcement of rights or subsequent actions in the event of future breaches.

Network Management Station Installation Guide 8/30/04v Beta Draft Confidential

vi8/30/04 Network Management Station Installation Guide Beta Draft Confidential

Contents

About This Guide What You Need to Know...... xiii Reading Path ...... xiv NMS Documentation...... xiv Documentation for New Modules ...... xvi How to Use This Guide...... xvi Conventions ...... xvii Related Documents ...... xviii Lucent...... xviii Third Party...... xix Ordering Printed Manuals Online...... xix Customer Comments...... xix Technical Support ...... xix

Chapter 1 Overview General Requirements...... 1-1 NMS System Configuration Requirements ...... 1-1 SCSI Device Addresses...... 1-6 NMS Software Requirements ...... 1-6 Solaris ...... 1-6 Solaris 8 Patch Cluster ...... 1-7 Sybase 12.5.0.1...... 1-7 Open Client 12.5...... 1-7 HP OpenView 6.2...... 1-7 HP OpenView 6.2 Patches ...... 1-8 NavisCore 08.00.03.00...... 1-8 Installation Scripts ...... 1-9 Installation Sequence ...... 1-10

Chapter 2 Installing Solaris 8 Before You Begin ...... 2-1 Solaris 8 Installation ...... 2-2 Installing Solaris 8...... 2-2 Installing the Solaris 8 Patch Cluster...... 2-10

Network Management Station Installation Guide rvii Beta Draft Confidential Contents

Chapter 3 Sybase Prerequisite Tasks Before You Begin ...... 3-1 Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions...... 3-3 Defining Partitions 1 and 7...... 3-5 Defining Partition 2...... 3-6 Creating a Master Device on Partition 0 ...... 3-7 Creating a Tempdb Device on Partition 3...... 3-8 Creating a Sysprocsdev device on Partition 4...... 3-8 Creating a NavisCore Data Device on Partition 5...... 3-9 Creating a NavisCore Log Device on Partition 6...... 3-10 Defining Partition 7 (Optional) ...... 3-11 Verifying Partition Sizes ...... 3-11 Partition Table Examples ...... 3-12 Loading the Lucent-supplied Sybase 12.5.0.1 CD-ROM...... 3-13 Setting Up the System...... 3-15 Using Raw Partitions for the Master Device...... 3-20 Using File System Files for the Master Device (Lab Configurations Only) ...... 3-22

Chapter 4 Installing Sybase 12.5.0.1 Before You Begin ...... 4-1 Installing Sybase 12.5.0.1 ...... 4-2

Chapter 5 Installing HP OpenView 6.2 Before You Begin ...... 5-1 Setting Up the System...... 5-2 Installing HP OpenView 6.2...... 5-6 Disabling IP Discovery ...... 5-14 Verifying the HP OpenView Installation ...... 5-15

Chapter 6 Installing NavisCore Before You Begin ...... 6-1 Installing NavisCore ...... 6-2 Defining a Static Route to the NMS ...... 6-12

Chapter 7 Backup Procedures First-time Backup to the Local Backup Server...... 7-2 Subsequent Backups to the Local Backup Server...... 7-4 Backing Up HP OpenView ...... 7-7 Saving Sybase 12.5.0.1 and HP OpenView Databases to Tape...... 7-8 Restoring HP OpenView Databases ...... 7-9 Maintaining Backup Data in OV Databases ...... 7-10 Recreating file...... 7-10 Changing the System Administrator (SA) Password...... 7-13

viii8/30/04 Network Management Station Installation Guide Beta Draft Confidential Contents

Chapter 8 Installing a Two-system Configuration Two-System Installation Outline ...... 8-1 NMS Post-Installation Sequence ...... 8-2 Sybase Server (System 1)...... 8-2 HP OpenView Server (System 2)...... 8-3 Verifying That HP OpenView Services Are Running (System 2) ...... 8-3 Adding the Sybase Server Hostname (System 2) ...... 8-4 Copying the Interfaces File (System 2) ...... 8-6

Appendix A Installing a New Remote Backup Server Adding the Remote Backup Server Hostname ...... A-2 Installing the Remote Backup Server ...... A-4 Adding the Remote Backup Server’s Interfaces File Contents ...... A-8 Configuring the Remote Backup Server...... A-10

Appendix B Backing up to the Remote Backup Server First-time Backup to the Remote Backup Server ...... B-2 Subsequent Backups to the Remote Backup Server ...... B-4 Backing Up HP OpenView Databases...... B-6 Saving Sybase 12.5.0.1 and HP OpenView Databases to Tape...... B-7

Appendix C IP Discovery Enabling IP Discovery ...... C-2 Disabling IP Discovery...... C-3

Appendix D Integrating NavisCore with HP OpenView Integrating NavisCore with HP OpenView ...... D-1

Appendix E NMS Startup and Shutdown Procedures Starting Up the NMS ...... E-1 Shutting Down the NMS...... E-3

Appendix F Sybase Worksheet Prerequisites ...... F-1 Using Raw Partitions for the Sybase Devices...... F-2 Using File System Files for the Sybase Devices (For Lab Only) ...... F-2 Remote Backup Server Parameters ...... F-2

Acronyms

Index

Network Management Station Installation Guide ix Beta Draft Confidential Contents List of Figures

Figure 2-1. Solaris Install Console Window ...... 2-3 Figure 2-2. Solaris Install Console Window ...... 2-4 Figure 2-3. Solaris Install Console Window ...... 2-6 Figure 3-1. Format Menu ...... 3-3 Figure 3-2. Partition Menu ...... 3-4 Figure 3-3. Partition Table for 8.49-GB Drive...... 3-10 Figure 3-4. Partition Table for 4.01-GB Drive...... 3-10 Figure 3-5. Sybase Installation Menu...... 3-12 Figure 3-6. Device Installation Menu...... 3-16 Figure 3-7. Sybase Master Device Menu ...... 3-17 Figure 3-8. Warning Window...... 3-20 Figure 3-9. Disk Space Report Window...... 3-21 Figure 4-1. Sybase Installation Menu...... 4-3 Figure 4-2. Raw Partition Parameters ...... 4-4 Figure 5-1. NavisCore/UX Installation Menu...... 5-3 Figure 5-2. HP OpenView Installation Menu...... 5-4 Figure 5-3. NavisCore/UX Installation Menu...... 5-7 Figure 5-4. HP OpenView Installation Menu...... 5-7 Figure 5-5. HP OpenView 6.10 Window ...... 5-14 Figure 6-1. Sybase Server Messages...... 6-2 Figure 6-2. HP OpenView Services window ...... 6-3 Figure 6-3. NavisCore/UX Installation Menu...... 6-4 Figure 6-4. NavisCore Installation Menu...... 6-5 Figure 6-5. Static Route Connection Example...... 6-13 Figure 7-1. Bulk Copy Output...... 7-6 Figure 8-1. Showserver Window...... 8-3 Figure 8-2. HP OpenView Services Window...... 8-4 Figure 8-3. Admintool: Users Dialog Box ...... 8-5 Figure 8-4. Admintool: Hosts Dialog Box ...... 8-5 Figure 8-5. Admintool: Add Host Dialog Box...... 8-5 Figure A-1. Admintool: Users Dialog Box ...... A-2 Figure A-2. Admintool: Hosts Dialog Box ...... A-3 Figure A-3. Admintool: Add Host Dialog Box...... A-3 Figure A-4. Sybase Backup Server Installation Parameters Window...... A-6 Figure A-5. Interfaces File Window...... A-9 Figure A-6. Showserver Window (Remote Backup Server)...... A-11 Figure B-1. Bulk Copy Output...... B-6 Figure D-1. NavisCore/UX Installation Menu...... D-2 Figure E-1. HP OpenView 6.0 Window ...... E-2

x8/30/04 Network Management Station Installation Guide Beta Draft Confidential Contents List of Tables

Table 1-1. NavisCore System Configuration Requirements...... 1-2 Table 1-2. SCSI Device Addresses ...... 1-6 Table 1-3. Single-System NMS - Installation Sequence...... 1-10 Table 1-4. Two-System NMS - Installation Sequence on System 1...... 1-11 Table 1-5. Two-System NMS - Installation Sequence on System 2...... 1-11 Table 2-1. Single-system NMS With Two Drives...... 2-8 Table 2-2. Two-system NMS (Sybase Server) ...... 2-9 Table 2-3. Two-system NMS (HP Server)...... 2-10 Table 2-4. Single-system NMS With One Drive (Lab Configurations Only) 2-11 Table 3-1. Partition Settings...... 3-2 Table 4-1. Sybase Configuration Parameters...... 4-5

Network Management Station Installation Guide 8/30/04xi Beta Draft Confidential Contents

xii8/30/04 Network Management Station Installation Guide Beta Draft Confidential

About This Guide

The Network Management Station Installation Guide provides software installation instructions for setting up your UNIX Network Management Station (NMS) platform. This task-oriented guide describes, step-by-step, the process for installing the required software for configuring Lucent switches.

This guide supports the following NMS software release: •NavisCore™, Release 08.00.03.00

This guide is intended to be used for fresh installations of NMS software. It should not be used for upgrading existing networks. Upgrades are network/configuration specific with this release and should not be attempted prior to contacting Lucent Technical Assistance Center. See “Technical Support” on page xix.

What You Need to Know

As a reader of this guide, you should be familiar with UNIX and HP OpenView. You should also know about relational databases to properly maintain Sybase, which is used by NavisCore.

This guide assumes that you have already installed the Lucent switch hardware. See the “Related Documents” section (page xviii) for a list of documents that describe these and other tasks.

Be sure to read the Software Release Notice (SRN) that accompanies each product. The SRN contains the most current feature information and requirements.

Network Management Station Installation Guide xiii Beta Draft Confidential About This Guide

Reading Path

This section describes all of the documents that support the NavisCore NMS and switch software.

NMS Documentation

Read the following documents to install and operate NavisCore Release 08.00.03.00. Be sure to review the NavisCore Software Release Notice for any changes not included in these guides.

This guide describes prerequisite tasks, hardware and software requirements, and instructions for installing Solaris, HP OpenView, and NavisCore on the NMS.

Network Management Station Installation Guide

This guide describes how to configure and manage NavisCore, network maps, and Lucent switches. It also describes how to add third-party objects to the map and access them through NavisCore.

NavisCore NMS Getting Started Guide

This guide describes the processor and input/output modules (IOMs) on each switch platform, and how to configure physical ports, timing, and other attributes through NavisCore.

NavisCore Physical Interface Configuration Guide

xiv8/30/04 Network Management Station Installation Guide Beta Draft Confidential About This Guide

This guide describes procedures for upgrading a Lucent switch to the current software release.

Switch Software Upgrade Guide

The following guides describe how to configure wide area network (WAN) services on the supported switch platforms:

• NavisCore Frame Relay Configuration Guide

NavisCore • NavisCore ATM Configuration Guide Configuration Guides • NavisCore IP Navigator Configuration Guide

This guide describes how to monitor and diagnose problems in your NavisCore switch network.

NavisCore Diagnostics Guide

This reference lists and describes the switch console commands.

Console Command Reference

Network Management Station Installation Guide 8/30/04xv Beta Draft Confidential About This Guide

Documentation for New Modules

The following guides provide information about hardware installation and switch software configuration for specific modules. • 8-Port Subrate DS3 FR/IP I/O Module User’s Guide (Product Code: 80166) • Base Input/Output 2 (BIO2) Module User’s Guide (Product Code: 80124) • 32-Port Channelized T1/E1 FR/IP I/O Module User’s Guide (Product Code: 80140) • 3-Port Channelized DS3/1 IMA I/O Module User’s Guide (Product Code: 80141)

How to Use This Guide

Before you read this guide, read the Lucent Technologies Software Release Notices for Sybase 12.5.0.1, HP OpenView 6.2, and NavisCore 08.00.03.00. The following table highlights the chapters and contents of this guide.

Read To Learn About

Chapter 1 Installation prerequisites, and system, hardware, and software requirements

Chapter 2 The Lucent-recommended instructions for installing Solaris 8 and Common Desktop Environment (CDE) on your UNIX NMS platform

Chapter 3 Preparing to install Sybase 12.5.0.1

Chapter 4 Installing Sybase 12.5.0.1

Chapter 5 • Preparing to install HP OpenView 6.2

• Installing HP OpenView 6.2

Chapter 6 Installing NavisCore

Chapter 7 Backup procedures

Chapter 8 Installing a two-system configuration

Appendix A Installing a remote backup server

Appendix B Sybase 12.5.0.1 backups to the remote backup server

Appendix C Enabling/Disabling IP Discovery

Appendix D Re-integrating NavisCore with HP OpenView

Appendix E NMS startup/shutdown procedures

Appendix F Sybase 12.5.0.1 worksheet

xvi8/30/04 Network Management Station Installation Guide Beta Draft Confidential About This Guide

Conventions

This guide uses the following conventions, when applicable:

Convention Indicates Example

Courier Regular System output, filenames, and Please wait... command names.

supplies a value. /docs/ atmcfg.pdf to display...

Variable text output. /docs/ atmcfg.pdf

Courier Bold User input. > show ospf names

Menu => Option A selection from a menu. NavisCore => Logon

Italics Book titles, new terms, and Network Management emphasized text. Station Installation Guide

A box around text A note, caution, or warning. See examples below.

Notes provide additional information or helpful suggestions that may apply to the subject text.

Cautions notify the reader to proceed carefully to avoid possible equipment ! damage or data loss.

Network Management Station Installation Guide 8/30/04xvii Beta Draft Confidential About This Guide

Related Documents

This section lists the related Lucent and third-party documentation that may be helpful to read.

Lucent • CBX 500 Hardware Installation Guide (Product Code: 80011) • GX 550 Multiservice WAN Switch Hardware Installation Guide (Product Code: 80077) • Base Input/Output 2 (BIO2) Module User’s Guide (Product Code: 80124) • 3-Port Channelized DS3/1 IMA I/O Module User’s Guide (Product Code: 80141) • 8-Port Subrate DS3 FR/IP I/O Module User’s Guide (Product Code: 80166) • 32-Port Channelized T1/E1 FR/IP I/O Module User’s Guide (Product Code: 80140) • NavisCore NMS Getting Started Guide (Product Code: 80139) • NavisCore Physical Interface Configuration Guide (Product Code: 80132) • NavisCore Frame Relay Configuration Guide (Product Code: 80133) • NavisCore ATM Configuration Guide (Product Code: 80134) • NavisCore IP Navigator Configuration Guide (Product Code: 80135) • NavisCore Diagnostics Guide (Product Code: 80138) • NavisCore Troubleshooting Guide (Product Code: 80137) • Console Command Reference (Product Code: 80136) • Switch Software Upgrade Guide (Product Code: 80162)

All manuals for Core Switching Division and the Master Glossary are available on the Core Switching Division Technical Publications Documentation Library CD-ROM (Product Code: 80025).

xviii8/30/04 Network Management Station Installation Guide Beta Draft Confidential About This Guide

Third Party • Solaris 8 Advanced Installation Guide • Solaris 8 (SPARC Platform Edition) Release Notes • Solaris 8 Sun Hardware Platform Guide • Installation Guide Sybase Adaptive Server™ Enterprise on Sun Solaris • Quick Start Installation Guide for HP OpenView Network Node Manager and HP OpenView Customer Views for NNM on Solaris • HP OpenView 6.2 Release Notes

Ordering Printed Manuals Online

You can order Core Switching manuals online. Use the following URL to access the Lucent Bookstore: http://www.lucentdocs.com

Customer Comments

Customer comments are welcome. Please respond in one of the following ways: • Fill out the Customer Comment Form located at the back of this guide and return it to us. • E-mail your comments to [email protected]. • FAX your comments to 978-692-1510, attention Technical Publications.

Technical Support

The Lucent Technical Assistance Center (TAC) is available to assist you with any problems encountered while using this Lucent product. Log on to our Customer Support web site to obtain telephone numbers for the Lucent TAC in your region:

http://www.lucent.com/support

Network Management Station Installation Guide 8/30/04xix Beta Draft Confidential About This Guide

xx8/30/04 Network Management Station Installation Guide Beta Draft Confidential

1

Overview

The Network Management Station (NMS) is a dedicated Sun system on which you run software programs to configure, monitor, and control a Lucent switch network. This chapter describes the recommended hardware and required software to install the NMS.

General Requirements

Lucent requires that you use a dedicated Sun system for network management. Lucent does not support any other UNIX operating system.

NMS System Configuration Requirements

You can configure your NMS in the following ways:

Single-system NMS Configuration — Sybase and one Lucent product (NavisCore, Statistics Server, or CNM Proxy Agent) reside on one workstation.

Two-system NMS Configuration — HP OpenView and NavisCore reside on one workstation, and Sybase resides on another. This type of configuration enables Sybase to support multiple Sybase databases (NavisCore, Statistics Server, and CNM Proxy Agent).

Large-system NMS Configuration — Sybase, Statistics Server, and one other Lucent product (NavisCore or CNM Proxy Agent) all reside on one workstation. Sybase can support all Lucent server products that reside on remote systems. For this configuration, Lucent recommends the Sun™ Enterprise™ 4500 (see Table 1-1 on page 1-2).

Network Management Station Installation Guide 1-1 Beta Draft Confidential Overview NMS System Configuration Requirements

Table 1-1 lists the system configuration specifications required by the NMS for optimal performance.

In addition, your workstation(s) must be equipped with the following: •CD-ROM drive • Tape drive

You do not need the tape drive for the NMS installation because the NMS software comes on CD-ROM. However, you need the tape drive for Sybase database backups. The tape drive does not need to be directly connected to either the HP OpenView/NavisCore or Sybase NMS Servers. However, to perform Sybase backups, the database must be saved to tape and the tape drive needs to be accessible from the Sybase Server.

Lucent recommends that you use a 21-inch monitor for optimal appearance of windows and fonts in the HP OpenView/NavisCore graphical user interface.

Table 1-1. NavisCore System Configuration Requirements

Environment System Role System Type CPUs RAM Disk(s)

Single-system Configuration (See “Single-system NMS” on page 1-10)

Small Network: System 1: Sun Enterprise 250 Four 400 4 GB • 9 GB Disk MHz (NavisCore / • 15-60 switches NavisCore / HP OpenView / HP OpenView / • 1-15 users Provisioning Provisioning Server) Server / Sybase • 9 GB Disk (Sybase)

Medium Network: System 1: Sun Enterprise 3500 Six to 8 GB • 9 GB Disk Eight (NavisCore / • 61-300 switches NavisCore / 400 MHz HP OpenView / HP OpenView / • 16-50 users Provisioning Provisioning Server) Server / Sybase • 9 GB Disk (Sybase)

1-2 Network Management Station Installation Guide Beta Draft Confidential Overview NMS System Configuration Requirements

Table 1-1. NavisCore System Configuration Requirements (Continued)

Environment System Role System Type CPUs RAM Disk(s)

Two-system Configuration (See “Two-system NMS” on page 1-11)

Small Network: System 1: Sun Enterprise 250 Two 400 1 GB • 9 GB Disk MHz • 15-60 switches NavisCore / • 1-15 users HP OpenView / Provisioning Server / Sybase Open Client

System 2: Sun Enterprise 250 Two 400 2 GB Each device below Sybase MHz requires space on a separate (9 GB minimum) disk: • 1 GB Data •1 GB Log

Medium Network: System 1: Sun Enterprise 450 Four 400 4 to 8 • 9GB Disk or Enterprise 3500 MHz GB • 61-300 switches NavisCore / HP OpenView / • 16-50 users Provisioning Server / Sybase Open Client

System 2: Sun Enterprise 450 Four 400 2 GB Each device below Sybase or Enterprise 3500 MHz requires space on a separate (9 GB minimum) disk: • 2 GB Data •2 GB Log

Network Management Station Installation Guide 8/30/041-3 Beta Draft Confidential Overview NMS System Configuration Requirements

Table 1-1. NavisCore System Configuration Requirements (Continued)

Environment System Role System Type CPUs RAM Disk(s)

Large System Configuration

Large Network: System 1: Sun Enterprise 4500 Four 400 8 GB • 9 GB Disk • 301-700 switches NavisCore / MHz • 51-100 users HP OpenView / Provisioning Server / Sybase Open Client

System 2: Sun Enterprise 4500 Six to 8 GB • 9 GB Disk Eight 400 NavisCore / MHz HP OpenView / Provisioning Server / Sybase Open Client

System 3: Sun Enterprise 4500 Six to 8 GB •6 Disk Fibre Eight 400 Array NavisCore / MHz HP OpenView / • Two 9 GB Disks: Provisioning NavisCore / Server / Provisioning Sybase Open Server Client

System 4: Sun Enterprise 4500 Eight 400 8 GB • 9 GB Data Disk Sybase MHz • 9 GB Log Disk

1-4 Network Management Station Installation Guide Beta Draft Confidential Overview NMS System Configuration Requirements

Table 1-1. NavisCore System Configuration Requirements (Continued)

Environment System Role System Type CPUs RAM Disk(s)

The following constraints and assumptions apply to these recommendations: • Each system requires an OS disk. • The requirements above apply to NavisCore 05.00.05.00 or greater. • NavisCore / Provisioning Server includes Access Control Server (ACS) requirements. • Recommendations assume Lucent NavisCore and Provisioning Server only; additional software on a system will increase system requirements. • Recommendations assume an average of provisioning up to 10,000 circuits a day per Provisioning Server. Note: if you share a database, the larger the number of circuits provisioned a day, the greater the load on the Sybase database. • Support for higher densities will increase resource requirements. • Users include a combination of applications and end-users accessing the system; the more intensive the application or user access, and the larger the number of simultaneous logins, the greater the load on the system. • Two-disk database installation is the default. Four disk database installation is recommended if the customer has the extra disks: it will increase performance. • Lucent recommends using a two- or large-system NMS configuration for optimized network performance. • Users should be shared across NavisCore / Provisioning Server installations where multiple servers are recommended. • These recommendations are based upon performance of NavisCore software within Lucent lab environments. Customer-specific requirements may require additional resources to provide the level of expected performance. • Call Lucent NetworkCare Professional Services for quotes on custom installations and network planning.

For specific system requirements for NavisXtend™ applications, see the appropriate NavisXtend SRN.

If you need help determining which system(s) best fits your NMS configuration, contact Lucent NetworkCare Professional Services through your Account representative.

You cannot run Sybase 12.5.0.1 with less than 512-MB RAM.

Network Management Station Installation Guide 8/30/041-5 Beta Draft Confidential Overview NMS Software Requirements

SCSI Device Addresses

Verify that the Small Computer System Interface (SCSI) device addresses (on the back of each device) are set as follows: Table 1-2. SCSI Device Addresses

SCSI Device Address

CD-ROM drive 6

Tape drive 4

NMS Software Requirements

The NMS requires that you install the following minimum software: • Solaris 8 and Common Desktop Environment • Solaris 8 Patch Cluster • Sybase 12.5.0.1 • Open Client Server 12.5 • HP OpenView 6.2 • HP OpenView 6.2 Patches • NavisCore 08.00.03.00

The sections that follow describe these software packages in more detail.

Solaris Operating System

The Solaris operating system consists of the following:

Sun Microsystems Solaris 8 Operating Environment — Operating system environment that includes advanced technologies for multithreading, symmetric multiprocessing, integrated TCP/IP-based networking, and centralized network administration tools.

Common Desktop Environment (CDE) — Provides users with a desktop graphical interface on a Sun workstation running Solaris 2.4 or later. This desktop provides windows, workspaces, controls, menus, and a front panel.

1-6 Network Management Station Installation Guide Beta Draft Confidential Overview NMS Software Requirements

Solaris 8 Patch Cluster

Before you install the NMS software programs, you must obtain the file 8_Recommended.zip. Additional Solaris 8 patch(es) may also be needed.

To obtain the patch(es), do one of the following: • Contact Sun at 1-800-USA-4SUN.

Access these files from Sun MicroSystems’ SunSolve Web site at http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access.

After you install the Solaris 8 operating system, you need to install the patch cluster.

For additional Lucent-recommended Solaris patch(es), see the appropriate NavisCore SRN.

Sybase 12.5.0.1

Sybase Adaptive Server Enterprise (ASE) 12.5.0.1, which will be referred to simply as Sybase 12.5.0.1 in this guide, is a relational database software program used to store database information and provide backup and recovery of database files.

For details on the Lucent-recommended Sybase 12.5.0.1 patches, see the latest Software Release Notice for Sybase 12.5.0.1.

Open Client 12.5

Open Client 12.5 is a programming interface that allows transparent access to any data source, information application, or system service.

HP OpenView 6.2

HP OpenView Network Node Manager (NNM) 6.2, which will be referred to simply as HP OpenView 6.2 in this guide, is a graphical Simple Network Management Protocol (SNMP) management application that provides fault, configuration, and performance management for multivendor Transmission Control Protocol/Internet Protocol (TCP/IP) networks. In addition, HP OpenView 6.2: • Manages custom SNMP devices and objects • Performs trap formatting and actions • Performs remote diagnostics and automatic status propagation

Network Management Station Installation Guide 8/30/041-7 Beta Draft Confidential Overview NMS Software Requirements

HP OpenView Windows is the graphical user interface for HP Openview 6.2, which permits extensive customization. This includes the definition of icons, maps, background graphics, symbols, and application representations.

HP OpenView 6.2 Patches

The patches for HP OpenView 6.2 must be installed on Solaris 8 systems after installing HP OpenView 6.2.

The required patches will be provided on a Lucent-supplied CD-ROM. You can also access the latest patches through HP OpenView’s Web site at http://ovweb.external.hp.com/cpe/patches.

For details on the Lucent-recommended HP OpenView patches, see the Software Release Notice for HP OpenView 6.2.

NavisCore 08.00.03.00

NavisCore provides the Lucent-specific configuration and monitoring tools needed to configure, monitor, and control a Lucent network. NavisCore configuration and monitoring tools are fully integrated within the HP OpenView graphical user interface.

Combined, these software programs present an easy-to-use graphical user interface that enables you to configure and maintain a Lucent network. NavisCore enables you to create several network maps and configure multiple networks from a single source (the NMS). HP OpenView provides the interface to add, modify, and delete nodes, trunks, and switch configurations from the network map and database.

1-8 Network Management Station Installation Guide Beta Draft Confidential Overview Installation Scripts

Installation Scripts

Lucent provides two installation scripts to facilitate installing NMS software.

Sybase Installation Script (install_sybase)

Run this script to: • Set up the system for a new Sybase 12.5.0.1 installation • Install Sybase 12.5.0.1 software on the system • Install the local Backup Server

HP OpenView/NavisCore Installation Script (install_cvux)

Run this script to: • Install HP OpenView 6.2 • Install NavisCore

Network Management Station Installation Guide 8/30/041-9 Beta Draft Confidential Overview Installation Sequence

Installation Sequence

The NMS installation sequence varies according to NMS configurations setups.

Lucent recommends using a two- or large-system NMS configuration for optimized network performance.

Single-system NMS

Table 1-3 provides a navigation path to install NMS software on a single-system configuration. Table 1-3. Single-System NMS - Installation Sequence

Action Described In

Install Solaris 8 Chapter 2

Install Solaris 8 patch cluster Chapter 2

Perform Sybase prerequisite tasks Chapter 3

Install Sybase 12.5.0.1 Chapter 4

Install HP OpenView 6.2 Chapter 5

Install HP OpenView 6.2 patches Chapter 5 and Software Release Notice for HP OpenView 6.2

Install NavisCore Chapter 6

1-10 Network Management Station Installation Guide Beta Draft Confidential Overview Installation Sequence

Two-system NMS

Table 1-4 and Table 1-5 provides a navigation path to install NMS software on a two-system configuration.

Table 1-4. Two-System NMS - Installation Sequence on System 1

Action Described In

Install Solaris 8 Chapter 2

Install Solaris 8 patch cluster Chapter 2

Perform Sybase prerequisite tasks Chapter 3

Install Sybase 12.5.0.1 Chapter 4

Install a two-system configuration Chapter 8

Table 1-5. Two-System NMS - Installation Sequence on System 2

Action Described In

Install Solaris 8 Chapter 2

Install Solaris 8 patch cluster Chapter 2

Install HP OpenView 6.2 Chapter 5

Install HP OpenView 6.2 patches Chapter 5 and Software Release Notice for HP OpenView 6.2

Install a two-system configuration Chapter 8

Install NavisCore Chapter 6

Before you install NMS software, fill out the Sybase worksheet (Appendix F). It provides parameter information you will need for the NMS installation.

Network Management Station Installation Guide 8/30/041-11 Beta Draft Confidential Overview Installation Sequence

1-12 Network Management Station Installation Guide Beta Draft Confidential

2

Installing Solaris 8

This chapter describes how to install Solaris 8 software on a SPARC-based system from a local CD-ROM drive using the Solaris 8 Interactive Installation Program.

The Solaris 8 operating system environment includes advanced technologies for multithreading, symmetric multiprocessing, integrated TCP/IP-based networking, and centralized network administration tools.

This chapter describes how to install the following software: •Solaris 8 • Solaris 8 patch cluster

Certain Sun Microsystems hardware is shipped pre-installed with Version 8 or greater of the Solaris operating system software.

Common Desktop Environment (CDE) is automatically installed during the Solaris 8 installation.

Before You Begin

Before you install Solaris 8, verify that you: • Are following the correct NMS installation sequence (See “Installation Sequence” on page 1-10) • Have read the general requirements for network management • Have read the NMS hardware and software requirements • Have obtained the Solaris 8 patch cluster

Network Management Station Installation Guide 2-1 Beta Draft Confidential Installing Solaris 8 Solaris 8 Installation

Solaris 8 Installation

Sun Microsystems Solaris, Version 8 (Solaris 8) is the operating system software you install on the NMS Sun system. Although you can follow the installation instructions provided in the Solaris 8 Advanced Installation Guide, this chapter provides the Lucent-recommended settings for installing and running NavisCore.

Installing Solaris 8

To install Solaris 8 on your Sun system as the initial operating system: 1. Obtain an Internet Protocol (IP) address and verify the given Subnet Mask from your network administrator. (This IP address must be registered as a valid address on your network.) 2. Power on the Sun system. 3. When the system comes up, hold down the Stop key and press the A key. The system displays the ok prompt. a. Insert the CD labeled Solaris 8 Software 1 of 2 SPARC Platform Edition into the CD-ROM drive. b. At the ok prompt, enter: boot cdrom The system boots the operating system from the CD-ROM drive. After several seconds, the system displays the following: Select a language 0. English 1. French 2. German 3. Italian 4. Japanese 5. Korean 6. Simplified Chinese 7. Spanish 8. Swedish 9. Traditional Chinese Please make a choice (0-9), or press h or ? for help. 4. Enter . A menu of locales is displayed.

2-2 Network Management Station Installation Guide Beta Draft Confidential Installing Solaris 8 Solaris 8 Installation

5. Enter . The OpenWindows™ desktop starts. An empty desktop and the Solaris Install Console windows are displayed with the message: The system is coming up. Please wait. The Solaris Installation Program dialog box is displayed. 6. At the Solaris Installation Program dialog box, choose Continue. 7. At the Identify This System dialog box, choose Continue. 8. At the Network Connectivity dialog box, select Yes and choose Continue. 9. At the DHCP dialog box, select No and choose Continue. 10. A Primary Network Interface dialog box is displayed if your network has more than one network interface. At the Primary Network Interface dialog box, select the primary network interface and choose Continue. (For example, .) 11. At the Host Name dialog box, enter and choose Continue. (For example, .) 12. At the IP Address dialog box, enter and choose Continue. (For example, <152.148.56.131>.) 13. At the Subnets dialog box, select Yes to make this system part of a subnet. Choose Continue. 14. At the Netmask dialog box, enter (or leave the default netmask) and choose Next. (For example, <255.255.248.0>.) 15. At the IPv6 dialog box, select No and choose Continue. 16. At Confirm Information dialog box, review the displayed information. If it is correct, choose Continue. To change any information, choose Change. 17. At the Configure Security Policy dialog box, select No and choose Continue. 18. At the Confirm Information dialog box, choose Continue. Once you confirm information, the Name Service dialog box is displayed.

Consult your system administrator for assistance if you are using a name service.

19. At the Name Service dialog box, select None and choose Continue. 20. At the Confirm Information dialog box, review the displayed information. If it is correct, choose Continue. To change any information, choose Change.

Network Management Station Installation Guide 8/30/042-3 Beta Draft Confidential Installing Solaris 8 Solaris 8 Installation

21. At the Time Zone dialog box, select Geographic Region and choose Set. 22. At the Geographic Region dialog box, select a region from the list on the left, and a time zone from the list on the right. Choose Continue. (For example, region and time zone.) 23. At the Date and Time dialog box, accept the default date and time or enter new values. Choose Continue. 24. At Confirm Information dialog box, review the displayed information. If it is correct, choose Continue. To change any information, choose Change. 25. At the Solaris Interactive Installation dialog box, choose Initial. 26. At the next Solaris Interactive Installation dialog box, choose Continue. 27. At the Select Geographic Regions dialog box, choose Continue. 28. At the Select Software dialog box, select Entire Distribution Plus OEM Support and choose Continue. 29. At the Select Disks dialog box, select the disk(s) for installing Solaris software by selecting it in the Available Disks window and moving it to the Selected Disks window and choose Continue. 30. At the Preserve Data dialog box, choose Continue. 31. At the Automatically Layout File Systems dialog box, choose Manual Layout. 32. At the File System and Disk Layout dialog box, choose Customize. 33. At the Customize Disks dialog box, lay out files systems (based on guidelines provided in Table 2-1 on page 2-6, Table 2-2 on page 2-7, Table 2-3 on page 2-8, and Table 2-4 on page 2-9) and choose Ok.

Do not partition the disk(s) to be used for Sybase at this time. That procedure is covered in Chapter 3, “Sybase Prerequisite Tasks.”

34. At the File System and Disk Layout dialog box, choose Continue. 35. At the Mount Remote File Systems dialog box, choose Continue. 36. At the Profile dialog box, verify the profile you created and choose Begin Installation. A dialog box with two buttons on it is displayed: Auto Reboot and Manual Reboot. 37. Choose Auto Reboot. The Installing Solaris Software - Progress status window is displayed, indicating the progress of the installation. This can take up to 2 hours depending on the software you’ve selected and the speed of the network or local CD-ROM. When Solaris software is completely installed, the message “Installation complete” will be displayed.

2-4 Network Management Station Installation Guide Beta Draft Confidential Installing Solaris 8 Solaris 8 Installation

The system automatically reboots. When the system comes back up, you will be prompted to enter your root password. Enter it twice when prompted. The following is displayed: System Identification is completed. ======This system is configured to conserve energy. ======After 30 minutes of idle time on this system, your system state will automatically be saved to disk, and the system will power-off. Later, when you want to use the system again, and you turn the power back on, your system will be restored to its previous state, including all the programs that you were running. Do you want this automatic power-saving shutdown? 38. Enter n. The following message is displayed: Autoshutdown has been disabled. Do you want the system to ask about this again, when you next reboot? (This gives you the chance to try it before deciding whether to keep it.) [y, n, ?] 39. Enter n. 40. At the Specify Media dialog box, select CD and choose Next. The Solaris 8 Software 1 of 2 CD is ejected. 41. Insert the CD labeled Solaris 8 Software 2 of 2 SPARC Platform Edition into the CD-ROM drive. 42. At the Insert CD dialog box, choose Ok. An Installing... status window is displayed with the following message: Installing Solaris 8 Software 2 43. At the Installation Summary dialog box, choose Next. The Solaris 8 Software 2 of 2 CD is ejected. 44. At the Specify Media dialog box, choose Skip to skip the installation of Solaris 8 (SPARC) Localizations. 45. At the Reboot dialog box, choose Reboot Now. 46. Proceed to “Installing the Solaris 8 Patch Cluster” on page 2-10.

Network Management Station Installation Guide 8/30/042-5 Beta Draft Confidential Installing Solaris 8 Solaris 8 Installation

Use Table 2-1 if you are installing a single-system NMS that has two drives.

The second drive uses raw devices for the Sybase database. The installation requires you to partition the second drive later in Chapter 3, “Sybase Prerequisite Tasks.”

The recommended partition settings are only a guideline. The examples in the table assume a 9-GB drive. If you are installing the operating system on a different size drive, consult your UNIX System Administrator or call the Technical Assistance Center. See “Technical Support” on page xix.

Table 2-1. Single-system NMS With Two Drives

File Systems Drive 1 (9-GB Drive)

Slice Mount Point Size

Slice 0 / 1000-MB

Slice 1 swap 1000-MBa

Slice 2 DO NOT CHANGE

Slice 3 DO NOT CHANGE

Slice 4 DO NOT CHANGE

Slice 5 /usr 1000-MB

Slice 6 /opt Remaining unallocated space on drive after all other settings have been configured; for example, 6-GB for a 9-GB drive

Slice 7 DO NOT CHANGE

a For swap space, 1000-MB is a minimum. 2 x RAM is recommended.

2-6 Network Management Station Installation Guide Beta Draft Confidential Installing Solaris 8 Solaris 8 Installation

Use Table 2-2 if you are installing the Sybase Server in a two-system NMS configuration.

This system has two drives, and the second drive uses raw devices for the Sybase database. The installation requires you to partition the second drive later in Chapter 3, “Sybase Prerequisite Tasks.”

The recommended partition settings are only a guideline. The examples in the table assume a 9-GB drive. If you are installing the operating system on a different size drive, consult your UNIX System Administrator or call the Technical Assistance Center. See “Technical Support” on page xix.

Table 2-2. Two-system NMS (Sybase Server)

File Systems Drive 1 (Internal) (9-GB Drive, 1-GB Memory)

Slice Mount Point Size

Slice 0 / 1000-MB

Slice 1 swap 1000-MBa

Slice 2 DO NOT CHANGE

Slice 3 DO NOT CHANGE

Slice 4 DO NOT CHANGE

Slice 5 /usr 1000-MB

Slice 6 /opt Remaining unallocated space on drive after all other settings have been configured; for example, 6-GB for a 9-GB drive

Slice 7 DO NOT CHANGE

a For swap space, 1000-MB is a minimum. 2 x RAM is recommended.

Network Management Station Installation Guide 8/30/042-7 Beta Draft Confidential Installing Solaris 8 Solaris 8 Installation

Use Table 2-3 if you are installing the HP Server in a two-system NMS configuration. This system has two drives.

The recommended partition settings are only a guideline. The examples in the table assume a 9-GB drive using a raw partition. If you are installing the operating system on a different size drive, consult your UNIX System Administrator or call the Technical Assistance Center. See “Technical Support” on page xix.

Table 2-3. Two-system NMS (HP Server)

File Systems Drive 1 (internal) File Systems Drive 2 (9-GB Drive, 1-GB Memory) (9-GB Drive, 1-GB Memory)

Slice Mount Size Slice Mount Size Point Point

Slice 0 / 1000-MB Slice 0

Slice 1 swap 1000-MBa Slice 1 swap 1000-MBa

Slice 2 DO NOT CHANGE Slice 2 DO NOT CHANGE

Slice 3 DO NOT CHANGE Slice 3 DO NOT CHANGE

Slice 4 DO NOT CHANGE Slice 4 DO NOT CHANGE

Slice 5 /usr Remaining Slice 5 /opt Remaining unallocated space on unallocated space on drive after all other drive after all other settings have been settings have been configured; for configured; for example, 7-GB for a example, 8-GB for a 9-GB drive 9-GB drive

Slice 6 DO NOT CHANGE Slice 6 DO NOT CHANGE

Slice 7 DO NOT CHANGE Slice 7 DO NOT CHANGE

a For swap space, 1000-MB is a minimum. 2 x RAM is recommended for the whole system.

2-8 Network Management Station Installation Guide Beta Draft Confidential Installing Solaris 8 Solaris 8 Installation

Use Table 2-4 if you are installing a single-system NMS that has one drive. This drive uses File Systems for the Sybase database. The partition settings are for lab configurations only.

The recommended partition settings are only a guideline. The examples in the table assume a 9-GB drive using a file system database (lab configurations only). If you are installing the operating system on a different size drive, consult your UNIX System Administrator or call the Technical Assistance Center. See “Technical Support” on page xix.

Table 2-4. Single-system NMS With One Drive (Lab Configurations Only)

File System Files Using One Drive (9-GB Drive, 1-GB memory)

Slice Mount Point Size

Slice 0 / 1000-MB

Slice 1 swap 1000-MB

Slice 2 DO NOT CHANGE

Slice 3 DO NOT CHANGE

Slice 4 DO NOT CHANGE

Slice 5 /usr 1000-MB

Slice 6 /opt Remaining unallocated space on drive after all other settings have been configured; 6-GB minimum recommended

Slice 7 DO NOT CHANGE

Network Management Station Installation Guide 8/30/042-9 Beta Draft Confidential Installing Solaris 8 Installing the Solaris 8 Patch Cluster

Installing the Solaris 8 Patch Cluster

You must install the Solaris 8 patch cluster file 8_Recommended.zip on your system.

For additional Lucent-recommended Solaris patches, see the appropriate NavisCore Software Release Notice (SRN).

To install the Solaris 8 patch cluster: 1. As root user, use a browser to download the patches from the Sun Microsystems Web site. The URL is: http://sunsolve.sun.com 2. Select Patches from the menu on the left side of the screen. 3. Select 8 from the Recommended Solaris Patch Clusters menu. (The number in parenthesis after 8 is the size of the cluster file in megabytes.) 4. Select the protocol used for downloading - HTTP or FTP. 5. Choose the GO button. 6. In the Save As... window, choose OK to select the default directory and filename. The download takes several minutes to complete. 7. Once the download has completed, enter the following in an Xterm window: cp 8_Recommended.zip /tmp cd /tmp unzip 8_Recommended.zip rm 8_Recommended.zip 8. When the # prompt appears, enter: cd 8_Recommended ./install_cluster After several lines of output which warns against having enough disk space, the following message appears: Are you ready to continue with install? [y/n]: 9. Enter y to continue. The installation may take up to 1.5 hours to complete. 10. When the # prompt appears, enter: init 6 11. Proceed to Chapter 3, “Sybase Prerequisite Tasks.”

2-10 Network Management Station Installation Guide Beta Draft Confidential

3

Sybase Prerequisite Tasks

In this guide, Sybase Adaptive Server Enterprise (ASE) 12.5.0.1 will be referred to as Sybase 12.5.0.1.

The Sybase 12.5.0.1 relational database software program stores database information and provides backup and recovery of database files.

This chapter describes Sybase prerequisite tasks, which include: • Partitioning the second disk(s) using raw partitions • Loading the Lucent-supplied Sybase 12.5.0.1 CD-ROM and extracting the scripts • Setting up the system before installing Sybase 12.5.0.1

Before You Begin

Before you perform Sybase prerequisite tasks, verify that you: • Are following the correct NMS installation sequence (See “Installation Sequence” on page 1-10) • Have installed Solaris 8 • Have installed Solaris 8 patch(es) • Do not already have Sybase installed on your machine

You can verify if Sybase has been installed on your machine by checking to see if the /opt/sybase directory exists and/or by trying to become the Sybase user by entering the following command:

su - sybase

The procedures in Chapter 3, “Sybase Prerequisite Tasks” and Chapter 4, “Installing Sybase 12.5.0.1” utilize the Lucent script to install Sybase. If you are not using the Lucent script to install Sybase, contact Technical Assistance Center prior to installing Sybase. See “Technical Support” on page xix.

Network Management Station Installation Guide 3-1 Beta Draft Confidential Sybase Prerequisite Tasks Before You Begin

Default Sybase parameters will not support the NavisCore database. Sybase must be tuned on a per server, per configuration basis. Contact Technical Assistance Center prior to installing Sybase. See “Technical Support” on page xix.

The entire Sybase installation process (prerequisite tasks and the actual installation) could take up to 1 and a half hours, depending on your configuration.

If you have a single-drive NMS that uses file-system files, proceed to “Loading the Lucent-supplied Sybase 12.5.0.1 CD-ROM” on page 3-13. This is for lab configurations only.

If you have a two or more drive NMS that uses raw partitions for the disks to be used for the Sybase installation, proceed to “Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions” on page 3-3.

3-2 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

Table 3-1 lists the recommended partition settings for the disk(s) that Sybase will be installed on. Table 3-1. Partition Settings

Partition(s) Function

1 and 7 These partitions are not used

0 Master device for Sybase

3 Tempdb device for Sybase

4 System Procs device for Sybase

5 NavisCore device for Sybase

6 Log device for Sybase

Sybase 12.5.0.1 allows a maximum 32-GB partition size.

Before you partition the disk(s), make sure the disk(s) you are about to partition ! is not the same disk you partitioned during the Solaris install. If you did not use the recommended partition settings (see Table 2-1 on page 2-6 through Table 2-3 on page 2-8), consult your System Administrator before completing this section.

Network Management Station Installation Guide 8/30/043-3 Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

To partition the Sybase disk(s): 1. At the Login prompt, enter root. When prompted for the root password, enter . 2. In an Xterm window, enter format. The Format Menu appears (Figure 3-1).

Figure 3-1. Format Menu 3. At the format prompt, enter disk. 4. At the Specify disk (enter its number) prompt, enter .

If you choose the disk that was already partitioned, the system displays the following: Warning: Current Disk has mounted partitions. a. At the format prompt, enter quit. b. Go to step 3 and select the disk that you did not partition.

5. At the format prompt, enter partition.

3-4 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

The Partition Menu appears (Figure 3-2).

Figure 3-2. Partition Menu

Defining Partitions 1 and 7

Perform the following steps to define the partition. 1. At the partition prompt, enter 1. 2. At the Enter partition id tag prompt, enter unassigned. 3. At the Enter partition permission flags prompt, enter wm. 4. At the Enter new starting cyl prompt, enter 0. 5. At the Enter partition size prompt, enter 0mb.

Repeat step 1 through step 5 for partition 7.

Network Management Station Installation Guide 8/30/043-5 Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

6. When you finish defining partitions 1 and 7, at the partition prompt, enter print. The partition table appears. Do not make changes to partition 2 if it uses the entire disk. Figure 3-3 on page 3-12 shows partition 2 defined as “backup” and uses the entire disk because “Total Disk Cylinders Available” is 4924 and the Cylinders column shows the value “0-4923,” which is 4924 cylinders. Proceed as follows: • If partition 2 is defined similar to Figure 3-3 on page 3-12, and uses the entire disk, proceed to “Creating a Master Device on Partition 0” on page 3-7. • If partition 2 does not use the entire disk, proceed to “Defining Partition 2” on page 3-6.

You need to define partition 2 if it does not use the entire disk. Several cases have been seen in the field where partition 2 did not use the entire disk.

Defining Partition 2

To define partition 2: 1. At the partition prompt, enter print. 2. Locate the “Total disk cylinders available” line in the partition table. Make a note of the number next to this line. Do not use the number next to reserved cylinders. 3. At the partition prompt, enter 2. 4. At the Enter partition id tag [unassigned] prompt, enter backup. 5. At the Enter partition permission flags [wm] prompt, enter wu. 6. At the Enter new starting cyl [0] prompt, enter 0. 7. At the Enter partition size prompt, enter $. (Entering $ at the Enter partition size prompt will allocate the remaining disk space to partition 2.) 8. Proceed to “Creating a Master Device on Partition 0.”

3-6 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

Creating a Master Device on Partition 0

To create a master device for Sybase on Partition 0: 1. At the partition prompt, enter 0. 2. At the Enter partition id tag prompt, enter unassigned. 3. At the Enter partition permission flags prompt, enter wm.

It is important that you enter 1 in step 4 for the starting cylinder for partition 0 and not 0.

4. At the Enter new starting cyl[1]: prompt, enter 1. 5. At the Enter partition size prompt, enter 200MB. 6. At the partition prompt, view the partition table by entering print. Figure 3-3 on page 3-12 is an example of a completed partition table after all 5 partitions have been defined. Partition 0 is complete. 7. Proceed to “Creating a Tempdb Device on Partition 3.”

Network Management Station Installation Guide 8/30/043-7 Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

Creating a Tempdb Device on Partition 3

To create a tempdb device for Sybase on Partition 3: 1. At the partition prompt, enter 3. 2. At the Enter partition id tag prompt, enter unassigned. 3. At the Enter partition permission flags prompt, enter wm. 4. At the Enter new starting cyl[xxxx]: prompt, enter: (Using Figure 3-3 on page 3-12 as an example, this value would be 116.)

Although Lucent recommends that you allocate 1 GB to partition 3 (step 5), this number depends on your disk space availability. A partition size of 200MB is the minimum value for the Tempdb Device.

5. At the Enter partition size prompt, enter 1GB. 6. At the partition prompt, view the partition table by entering print. Figure 3-3 on page 3-12 is an example of a completed partition table after all 5 partitions have been defined. Partition 3 is complete. 7. Proceed to “Creating a Sysprocsdev device on Partition 4.”

Creating a Sysprocsdev device on Partition 4

The default system name for this device is sysprocsdev. However, it is frequently referred to as the sybsystemprocs device since it stores the sybsystemprocs database.

To create a sysprocsdev device for Sybase on Partition 4: 1. At the partition prompt, enter 4. 2. At the Enter partition id tag prompt, enter unassigned. 3. At the Enter partition permission flags prompt, enter wm. 4. At the Enter new starting cyl[xxxx]: prompt, enter: (Using Figure 3-3 on page 3-12 as an example, this value would be 701.) 5. At the Enter partition size prompt, enter 200MB.

3-8 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

6. At the partition prompt, view the partition table by entering print. Partition 4 is complete. 7. Proceed to “Creating a NavisCore Data Device on Partition 5.”

Creating a NavisCore Data Device on Partition 5

To create a NavisCore data device for Sybase on Partition 5: 1. At the partition prompt, enter 5. 2. At the Enter partition id tag prompt, enter unassigned. 3. At the Enter partition permission flags prompt, enter wm. 4. At the Enter new starting cyl[xxxx]: prompt, enter: Using Figure 3-3 on page 3-12 as an example, this value would be 816. 5. At the Enter partition size prompt, do the following: a. To allocate the remaining disk space for the NavisCore Data and Log devices, use the following equation to calculate the partition size for each device: ( - )/2 = For example, using the values shown in Figure 3-3 on page 3-12: (4924 (available cylinders on drive) - 815 (total used cylinders)) / 2 = 2054 (NavisCore data device size). b. In this example, you would enter 2054c at the Enter partition size prompt. 6. At the partition prompt, view the partition table by entering print. Partition 5 is complete. 7. Proceed to “Creating a NavisCore Log Device on Partition 6.”

Network Management Station Installation Guide 8/30/043-9 Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

Creating a NavisCore Log Device on Partition 6

To create a NavisCore log device for Sybase on Partition 6: 1. At the partition prompt, enter 6. 2. At the Enter partition id tag prompt, enter unassigned. 3. At the Enter partition permission flags prompt, enter wm. 4. At the Enter new starting cyl[xxxx]: prompt, enter:

Using Figure 3-3 on page 3-12 as an example, this value would be 2870. 5. At the Enter partition size prompt, do the following: a. To allocate the remaining disk space for the Log device, use the equation in step 5 on page 3-9 to calculate the partition size: ( - )/2 = For example, using the values shown in Figure 3-3 on page 3-12: (4924 (available cylinders on drive) - 815 (total used cylinders)) / 2 = 2054 (NavisCore data device size). b. In this example, you would enter 2054c at the Enter partition size prompt. 6. When you have finished defining the Log device, do one of the following: • If you wish to define partition 7 using any unallocated disk space, proceed to “Defining Partition 7 (Optional)” on page 3-11. • If you have allocated the entire disk to Sybase databases, proceed to “Verifying Partition Sizes” on page 3-11.

3-10 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

Defining Partition 7 (Optional)

If you have not used the entire disk for Sybase devices, define Partition 7 using the remaining unallocated space: 1. At the partition prompt, enter print to view the partition table. 2. Locate the “Total disk cylinders available” line in the partition table. Make a note of the number next to this line. Do not use the number next to reserved cylinders. Figure 3-3 on page 3-12 is an example of an 8.49-GB disk drive. 3. Subtract the Partition 6 ending cylinder number from the “Total disk cylinders available” number, then subtract 1. Make a note of this number. 4. At the partition prompt, enter 7. 5. At the Enter partition id tag prompt, enter unassigned. 6. At the Enter partition permission flags prompt, enter wm. 7. At the Enter new starting cyl[xxxx]: prompt, enter: 8. At the Enter partition size prompt, enter c. 9. Proceed to “Verifying Partition Sizes.”

Verifying Partition Sizes

Follow the steps below to verify the partition sizes for the Sybase disk: 1. At the partition prompt, enter print to view the final partition table. Confirm that the cylinders are contiguous for partition 0, 3, 4, 5, 6, and 7. (Partition 7 will be contiguous only if it was defined.) 2. At the partition prompt, enter quit. 3. At the format prompt, label and save the partitions by entering label. 4. At the Ready to label disk prompt, enter y. 5. If you are using a two-disk configuration, at the format prompt, enter quit. If you are using more than two disks, proceed to step 4 on page 3-4 to partition the next disk to be used for Sybase. 6. Proceed to “Loading the Lucent-supplied Sybase 12.5.0.1 CD-ROM” on page 3-13.

Network Management Station Installation Guide 8/30/043-11 Beta Draft Confidential Sybase Prerequisite Tasks Partitioning the Disk(s) to be Used for Sybase Using Raw Partitions

Partition Table Examples

Use either Figure 3-3 or Figure 3-4 when you define partitions 0, 1, 2, 3, 4, 5, 6, and 7.

Figure 3-3. Partition Table for 8.49-GB Drive

Figure 3-4. Partition Table for 4.01-GB Drive

3-12 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Loading the Lucent-supplied Sybase 12.5.0.1 CD-ROM

Loading the Lucent-supplied Sybase 12.5.0.1 CD-ROM

To load the Lucent-supplied Sybase CD-ROM: 1. Verify that you are logged in as root. You should see a # prompt in the Xterm window. If you are not logged in as root, in the Xterm window enter su - root. When prompted, enter . 2. Insert the Sybase 12.5.0.1 CD into the CD-ROM drive. 3. In an Xterm window, change to the /opt directory by entering: cd /opt 4. Unzip the Sybase tar file and remove the installation script from the tar file by entering: gunzip -c /cdrom/cdrom0/|tar xvf - ./cv_scripts See the latest Software Release Notice (SRN) for Sybase 12.5.0.1 for the Sybase tar file name. 5. Change to the cv_scripts directory by entering: cd /opt/cv_scripts

In a new Xterm window on the local system, run “xhost +” as the user who controls the system console. Executing this command enables you to display the installation log on the local system.

6. Run the Sybase installation script by entering: ./install_sybase The following message appears: Verifying super user privileges... Would you like to view (tail -f) the install log (default=y)? The Tail window allows users to view the installation log. 7. Press Return to accept the default (yes). The following message appears: What display should the install log xterm go to (default:0.0)? 8. Press Return or enter :0.0. The Tail and Sybase Installation Menu windows appear simultaneously. The pathname in the Tail window indicates where the installation log can be found.

Network Management Station Installation Guide 8/30/043-13 Beta Draft Confidential Sybase Prerequisite Tasks Loading the Lucent-supplied Sybase 12.5.0.1 CD-ROM

[Press ^ C to abort...] Sybase Installation Menu... 1. Set up the system before SYBASE Installation 2. Install Sybase 3. Upgrade Sybase 4. Configure a Remote Sybase Backup Server 5. Configure an Additional Sybase Data Device 6. Exit Please select one of the above options [1-6]?

Figure 3-5. Sybase Installation Menu The Lucent-supplied Sybase installation scripts are loaded on your system. The next section describes how to set up your system before installing the Sybase 12.5.0.1 software.

3-14 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

Setting Up the System

The Sybase installation script: • Creates the Sybase and NMS user accounts • Creates additional user accounts • Assigns TCP socket numbers to the Sybase and backup servers • Sets the NavisCore device names • Sets the Master, Tempdb, Sysprocsdev, Data, and Log devices

Refer to the Sybase Worksheet in Appendix F to record selected parameter settings.

To set up your system: 1. At the Sybase Installation Menu, set up the system by entering 1. The following message appears: Complete all prerequisite tasks before continuing. See Lucent’s Installation Documentation for more information. Do you wish to continue? [default=y]: 2. Press Return to continue. The following message appears: Setting up your system for the Sybase Install ------Creating the dba group for database system administrator. Successfully added group ‘dba’ with gid 300 Creating a user account for sybase ------Enter user’s home directory [default : /opt/sybase] ? 3. Press Return to accept the default of /opt/sybase. The following message appears: Adding user sybase. Please wait... Successfully added user sybase... Configuring the user account with environment files. ------Enter the Database Server Name (default=) ?

Network Management Station Installation Guide 8/30/043-15 Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

In step 4, do not enter CASCADE for your database server name (it is a reserved ! Sybase word); the installation fails if you use it. By default, the script uses the system hostname. If the hostname contains a hyphen (-), you must not use the hyphen because the installation fails.

4. At the Enter the Database Server Name prompt, do one of the following: • Press Return to accept the default of . •Enter . 5. At the Enter the name for the error log prompt, press Return to accept the default (_err.log).

In step 6, choose a secure password that you can remember (for example, superbase). The password must be at least six characters in length. If you enter a password with fewer characters, you will be unable to initiate an isql session after completing the installation. Do not enter CASCADE for the Database SA Password (it is a reserved Sybase word).

6. At the Enter the Database SA Password prompt, enter: When prompted, re-enter the password.

The following message appears: Creating /etc/rc2.d/S97sybase..Done. Creating /etc/rc0.d/K01sybase..Done. Creating /etc/rc2.d/S98sybase..Done. The script creates the three listed files that activate and deactivate the Sybase 12.5.0.1 Server and the backup server. The script uses these files later in the installation to shut down and start up the Sybase Server. The following message appears: You must add at least one more user account. Enter name of the new user [default: nms] ? 7. Press Return to accept the default (nms).

3-16 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

8. At the Enter group to which new user belongs prompt, press Return to accept the default of staff. The following message appears: Creating a user account for nms ------Enter User’s home directory [default : /opt/nms] ? 9. Press Return to accept the default of /opt/nms. The following message appears: Adding user nms. Please Wait... Successfully added user nms... Configuring the user account with environment files. ------Setting Shared Memory Allocations ------The Lucent script increases Sybase’s shared memory. The script accomplishes this by adding the line set shmsys:shminfo_shmmax=131072000 to the /etc/system file. The system displays the following: Making a backup copy of '/etc/system' in '/etc/system.cv' Setting TCP Socket device for Sybase ------The Socket Number for SYBASE is 1025 The Socket Number for SYBASE BACKUP is 1026 The Lucent script assigns TCP socket numbers to Sybase and the local backup server. The socket number 1025 is assigned to Sybase and 1026 is assigned to the local backup server. If these numbers are already in use, the script assigns the next available numbers. The system displays the following: Do you wish to continue? [default=y]: 10. Press Return to continue. The following message appears: Creating Additional User Accounts ------1. Create User Account. 2. Proceed to the Next Step. Please select one of the above options [1-2]?

Network Management Station Installation Guide 8/30/043-17 Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

11. Select one of the following options: •Enter1 to create additional user accounts. The script prompts you for information similar to what you provided for the nms user account. See step 7 on page 3-16. Once you create the additional user, the Creating Additional User Accounts Menu reappears. •Enter 2 to proceed to the next step. The Device Installation Menu appears.

Device Installation Menu... 1. NavisCore Device Installation 2. CNM Device Installation 3. Fault Server Device Installation 4. Bulk Stats Device Installation 5. Other Device Installation Please select one of the above options [1-5]?

Figure 3-6. Device Installation Menu 12. Enter 1 to install the NavisCore device. The following message appears: NavisCore Device Installation Selected...

If you use Sybase in conjunction with other Lucent products (CNM Proxy Agent, NavisXtend Statistics Server (Bulk Statistics), and NavisXtend Fault Server), you must configure additional devices for these products. Call the Technical Assistance Center for assistance. See “Technical Support” on page xix.

3-18 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

The following menu appears:

Setting the master device used for Sybase ------You can create the Master Device on a RAW PARTITION or on a FILE SYSTEM FILE. Select the type of device for Master Device 1. Raw Partition. 2. File System File. 3. Proceed to the Next Step.

Enter Selection [1-3]?

Figure 3-7. Sybase Master Device Menu 13. Specify your master device as follows: • To select Raw Partitions, enter 1. Proceed to “Using Raw Partitions for the Master Device” on page 3-20. • To select File System Files (for lab configurations only), enter 2. Proceed to “Using File System Files for the Master Device (Lab Configurations Only)” on page 3-22.

Network Management Station Installation Guide 8/30/043-19 Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

Using Raw Partitions for the Master Device If you selected Raw Partitions in step 13 on page 3-19, the following message appears: WARNING: IF YOU INSTALL THE SQL SERVER ON A RAW PARTITION, ANY EXISTING FILES ON THAT PARTITION WILL BE OVERWRITTEN. Do you wish to continue? [default=y]: 1. Press Return to continue.

The Lucent script does not provide defaults for the following prompts because customer configurations vary.

The following message appears: Setting up Raw Partition Devices ------Enter the Master Device Path Name (e.g. /dev/rdsk/c0t1d0s0): 2. Enter . For example, /dev/rdsk/c0t1d0s0 The following message appears: Setting device permissions. Please Wait.. Device /dev/rdsk/c0t1d0s0 has been set. Enter the tempdb Device Path Name (e.g. /dev/rdsk/c0t1d0s3): 3. Enter . For example, /dev/rdsk/c0t1d0s3 The following message appears: Setting device permissions. Please wait.. Device /dev/rdsk/c0t1d0s3 has been set. Enter the Procs Device Path Name (e.g. /dev/rdsk/c0t1d0s4): 4. Enter . For example, /dev/rdsk/c0t1d0s4 The following message appears: Setting device permissions. Please Wait.. Device /dev/rdsk/c0t1d0s4 has been set Enter the Cascade Device Path Name (e.g. /dev/rdsk/c0t1d0s5):

3-20 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

5. Enter . For example, /dev/rdsk/c0t1d0s5 The following message appears: Setting device permissions. Please Wait.. Device /dev/rdsk/c0t1d0s5 has been set. Enter the Log Device Path Name (e.g. /dev/rdsk/c0t1d0s6): 6. Enter . For example, /dev/rdsk/c0t1d0s6 The following message appears: Setting device permissions. Please wait.. Device /dev/rdsk/c0t1d0s6 has been set. The maximum value for your Master Device has been calculated to maximize the size of your raw partition. By accepting the default you will be utilizing the whole raw device. A minimum value has been established at 200 Mbytes. You will not be allowed to go below that threshold. NOTE: It is recommended that you accept the maximum value. Otherwise, the space left over will be wasted. Enter size of your Master Device in Megabytes: 7. Press Return to accept the default of 200. The following message appears: ****************************************************** If you have completed the initial SYBASE setup successfully, please REBOOT the workstation now. 8. At the # prompt, reboot the system by entering: init 6 The Sybase prerequisite tasks are complete. 9. Proceed to Chapter 4, “Installing Sybase 12.5.0.1.”

Network Management Station Installation Guide 8/30/043-21 Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

Using File System Files for the Master Device (Lab Configurations Only)

If you selected File System Files (for lab configurations only) in step 13 on page 3-19, the following message appears:

WARNING: Do not create Sybase master devices as regular UNIX files on ‘Production’ SQL Servers. I/O to operating system files is buffered I/O, so your data may not be recoverable in the case of a system crash or other failure. Avoid remote mounted file systems. Do not create or use devices on remote NFS-mounted or RFS mounted directories. You also need to determine if there is enough space in the file system for master device. NOTE: Consult your Lucent manual for recommended space requirements. Press Return to Continue....

Figure 3-8. Warning Window

3-22 Network Management Station Installation Guide Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

1. Press Return to continue. The following window appears:

Disk space report ------

Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 96019 23866 62553 28% / /dev/dsk/c0t0d0s4 288556 197752 61954 77% /usr /dev/dsk/c1t0d0s4 3939604 501 3545143 1% /VIEWS_central /dev/dsk/c0t0d0s5 3188923 1572215 1297818 55% /opt

Do you want to Continue with the configuration (y/n) ? y

Figure 3-9. Disk Space Report Window 2. To continue, enter y. 3. At the Enter name for database device directory prompt, press Return to accept the default of /opt/databases. 4. The following message appears. The minimum value for your Master Device has been established at 200 MBytes. By accepting the default you will be assigning the minimum space allowed for an initial NavisCore Installation. NOTE: Consult your Lucent manual for recommended sizes. Enter the size of the Master Device in Megabytes [default=200]: Enter the size of your Master Device in Megabytes: 5. Press Return to accept the default of 200.

Although Lucent recommends that you allocate 1 GB to Tempdb device (step 6), this number depends on your disk space availability. A partition size of 200MB is the minimum value for the Tempdb Device.

6. At the Enter the size of your Tempdb Device in Megabytes prompt, enter 1000.

Network Management Station Installation Guide 8/30/043-23 Beta Draft Confidential Sybase Prerequisite Tasks Setting Up the System

7. At the Enter the size of your System Procs Device in Megabytes prompt, press Return to accept the default of 200. 8. At the Enter the size of your Data Device in Megabytes prompt, press Return to accept the default of 300.

For file system file configurations, /opt requires at least 1.7-GB for the database files.

9. At the Enter the size of your Log Device in Megabytes prompt, press Return to accept the default of 300. The following message appears: Creating Master Device file... Making directory for the master device... Press Enter to return... 10. Press Return to continue. The following message appears: ****************************************************** If you have completed the initial SYBASE setup successfully, please REBOOT the workstation now. 11. At the # prompt, reboot the system by entering init 6. The Sybase prerequisite tasks are complete. 12. Proceed to Chapter 4, “Installing Sybase 12.5.0.1.”

3-24 Network Management Station Installation Guide Beta Draft Confidential

4

Installing Sybase 12.5.0.1

This chapter describes how to install Sybase 12.5.0.1.

Before You Begin

Before you begin, verify that you: • Are following the correct NMS installation sequence (See “Installation Sequence” on page 1-10) • Have partitioned the disk(s) using raw partitions • Have set up the system

Network Management Station Installation Guide 4-1 Beta Draft Confidential Installing Sybase 12.5.0.1 Installing Sybase 12.5.0.1

Installing Sybase 12.5.0.1

To run the Sybase 12.5.0.1 installation script: 1. At the console login, enter root. When prompted, enter . 2. Insert the Sybase 12.5.0.1 CD into the CD-ROM drive.

In a new Xterm window on the local system, run “xhost +” as the user who controls the system console. Executing this command enables you to display the installation log on the local system.

3. Unzip the Sybase install file by entering: gunzip -c /cdrom/cdrom0/ > /tmp/ For example, gunzip -c /cdrom/cdrom0/syb_install.03.00.07.00.tgz > /tmp/syb_install.03.00.07.00.tar 4. Change to the /opt/cv_scripts directory by entering: cd /opt/cv_scripts 5. Run the Sybase installation script by entering: ./install_sybase The following message appears: Verifying super user privileges... Would you like to view (tail -f) the install log (default=y)? The Tail window allows users to view a log of the installation process. 6. Press Return to accept the default (yes). The following message appears: What display should the install log xterm go to (default:0.0)? 7. Press Return or enter :0.0.

4-2 Network Management Station Installation Guide Beta Draft Confidential Installing Sybase 12.5.0.1 Installing Sybase 12.5.0.1

The Tail Window and Sybase Installation Menu appear:

[Press ^ C to abort...]

Sybase Installation Menu...

1. Set Up the system before SYBASE Installation 2. Install Sybase 3. Upgrade Sybase 4. Configure a Remote Sybase Backup Server 5. Configure an Additional Sybase Data Device 6. Exit

Please select one of the above options [1-6]?

Figure 4-1. Sybase Installation Menu 8. At the Sybase Installation Menu, enter 2. The following message appears: The following items are required to be completed before performing this step. 1. Space requirements must be clarified. 2. Step 1 from the Sybase menu must be completed. Do you wish to continue? [default=y]: 9. Press Return to continue. The system displays the parameters you entered and prompts you to make any necessary changes. Figure 4-2 shows an example of raw partition parameters.

Network Management Station Installation Guide 8/30/044-3 Beta Draft Confidential Installing Sybase 12.5.0.1 Installing Sybase 12.5.0.1

Sybase Installation Parameter *******************************

Parameter Value ********* ***********************

0. Done Editing

1. SYBASE /opt/sybase

2. DSQUERY CENTRAL

3. HOSTNAME central

4. BACKUP_HOSTNAME central

5. SYB_TCP_Sock 1025

6. SYB_BACKUP_TCP_Sock 1026

7. SA_USER sa

8. SYB_ERR_LOG /opt/sybase/ASE-12_5/install/CENTRAL_err.log

9. SYB_Master_Dev /dev/rdsk/c0t1d0s0

10. SYB_Master_Size (MB) 200

11. SYB_Procs_Dev /dev/rdsk/c0t1d0s4

12. SYB_Procs_Size (MB) 200

13. SYB_Cascade_Dev /dev/rdsk/c0t1d0s5

14. SYB_Cascade_Size (MB) 300

15. SYB_Log_Dev /dev/rdsk/c0t1d0s6

16. SYB_Log_Size (MB) 300

17. SYB_tempdb_Dev /dev/rdsk/c0t2d0s3

18. SYB_tempdb_Size (MB) 1000

19. SYB_Dev_Type Raw

Enter the number of the parameter you wish to alter :

Figure 4-2. Raw Partition Parameters

4-4 Network Management Station Installation Guide Beta Draft Confidential Installing Sybase 12.5.0.1 Installing Sybase 12.5.0.1

10. If you need to make additional changes, keep the following in mind: • If you change parameters 9 through 19, the Sybase Master Device Menu reappears. See Figure 3-7 on page 3-19. • If you change parameter 1, the script prompts you to change parameter 8 (SYB_ERR_LOG). Table 4-1 provides a description for each of the Sybase parameters. Table 4-1. Sybase Configuration Parameters

Sybase Parameter Description

SYBASE Target directory for Sybase installation.

DSQUERY Sybase Server name, which should be your system’s HOSTNAME (capital letters, no hyphens).

HOSTNAME Name of Sybase workstation.

BACKUP_HOSTNAME Name of Sybase workstation (same as HOSTNAME).

SYB_TCP_Sock TCP socket number for Sybase.

SYB_BACKUP_TCP_Sock TCP socket number for backup Sybase.

SA_USER Default Sybase system administrator user name.

SYB_ERR_LOG Default pathname of log file that contains all SQL Sybase errors.

SYB_Master_Dev Pathname of Sybase Master device.

SYB_Master_Size (MB) Size (in megabytes) of Master device.

SYB_Procs_Dev Pathname of Sysprocsdev device.

SYB_Procs_Size (MB) Size (in megabytes) of Sysprocsdev device.

SYB_Cascade_Dev Pathname of NavisCore data device.

SYB_Cascade_Size (MB) Size (in megabytes) of NavisCore data device.

SYB_Log_Dev Pathname of NavisCore log device.

SYB_Log_Size (MB) Size (in megabytes) of NavisCore log device.

SYB_tempdb_Dev Pathname of tempdb device.

SYB_tempdb_Size (MB) Size (in megabytes) of tempdb device.

SYB_Dev_Type Type of Sybase device installation (FileSystem or Raw). The install program sets this value automatically.

Network Management Station Installation Guide 8/30/044-5 Beta Draft Confidential Installing Sybase 12.5.0.1 Installing Sybase 12.5.0.1

11. When you complete your changes, enter 0 to continue. The following message appears: Do you wish to extract Sybase Installation media ‘y|n’ (default = ‘y’)? 12. Press Return. 13. The following message appears: Install the media in your local device now. ******************************************* Enter the full path of the media device: 14. Enter: /tmp/ (For example, /tmp/syb_install.03.00.07.00.tar) See the latest Software Release Notice for Sybase 12.5.0.1 for the Sybase tar file name. The following message appears: The device was found and is ready for extraction. Press Return to Continue.... 15. Press Return.

4-6 Network Management Station Installation Guide Beta Draft Confidential Installing Sybase 12.5.0.1 Installing Sybase 12.5.0.1

The following messages appear: Extracting Sybase Installation Media from the device ...Done. Running ’srvbuildres’ and creating the sybase server.../opt/sybase/ASE-12_5/bin/srvbuildres: Port number ’1025’ is being reserved or currently in use by a running server. /opt/sybase/ASE-12_5/bin/srvbuildres: Building Adaptive Server ’CENTRAL’: /opt/sybase/ASE-12_5/bin/srvbuildres: Building master device... /opt/sybase/ASE-12_5/bin/srvbuildres: Master device complete. /opt/sybase/ASE-12_5/bin/srvbuildres: Writing entry into directory services... /opt/sybase/ASE-12_5/bin/srvbuildres: Directory services entry complete. /opt/sybase/ASE-12_5/bin/srvbuildres: Writing RUN_SERVER file... /opt/sybase/ASE-12_5/bin/srvbuildres: RUN_SERVER file complete. /opt/sybase/ASE-12_5/bin/srvbuildres: Starting server... /opt/sybase/ASE-12_5/bin/srvbuildres: Server started. /opt/sybase/ASE-12_5/bin/srvbuildres: Building sysprocs device and sybsystemprocs database... /opt/sybase/ASE-12_5/bin/srvbuildres: Sybprocs device and sybsystemprocs database created. /opt/sybase/ASE-12_5/bin/srvbuildres: Running installmaster script to install system stored procedures... /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 10% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 20% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 30% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 40% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 50% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 60% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 70% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 80% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 90% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: /opt/sybase/ASE-12_5/scripts/installmaster: 100% complete. /opt/sybase/ASE-12_5/bin/srvbuildres: installmaster script complete. /opt/sybase/ASE-12_5/bin/srvbuildres: Installing common character sets (Code Page 437, Code Page 850, ISO Latin-1, Macintosh and HP Roman-8)... /opt/sybase/ASE-12_5/bin/srvbuildres: Character sets installed. /opt/sybase/ASE-12_5/bin/srvbuildres: Setting server name in Adaptive Server... /opt/sybase/ASE-12_5/bin/srvbuildres: Server name added. The name will be visible from SQL after restarting the server. /opt/sybase/ASE-12_5/bin/srvbuildres: Server ’CENTRAL’ was successfully created. Done Successfully. Creating the Data and Log devices

Network Management Station Installation Guide 8/30/044-7 Beta Draft Confidential Installing Sybase 12.5.0.1 Installing Sybase 12.5.0.1

Please wait... Running ’alter’ commands to expand the master device and the tempdb file. This may take a few moments. Please Wait ...Done Successfully. Increasing the Memory allocations to 28672 for improved performance ...

The Lucent script increases memory allocation to allow Sybase commands to execute. The script increases the allocation because the system defaults have insufficient byte memory for Sybase commands. For more information, see the Installation Guide Sybase Adaptive Server Enterprise on Sun Solaris.

The screen displays the following: Increasing the Number of Users Connections ------By default, the Sybase installation sets the number of user connections to 25. Lucent sets it to 150. If you need a different number of connections then enter the number of connections (25 or higher). Enter the number of user connections [default=150] ? 16. Do one of the following: • Press Return to accept the default of 150. •Enter . The following messages appear: Done... Now increasing number of open objects for NavisCore ------Done... Now increasing number of open databases for NavisCore ------Done... Now increasing stack guard size for NavisCore ------Done... Now increasing number of locks for NavisCore ------

4-8 Network Management Station Installation Guide Beta Draft Confidential Installing Sybase 12.5.0.1 Installing Sybase 12.5.0.1

Done... Please wait... Restarting Server with increased options The script shuts down and restarts the Sybase Server, enabling the new configuration parameters to take effect. The following messages appear: Configuring Local Backup Server ******************************* Running ’srvbuildres’ and creating the sybase server.../opt/sybase/ASE-12_5/bin/srvbuildres: Port number ’1026’ is being reserved or currently in use by a running server. /opt/sybase/ASE-12_5/bin/srvbuildres: Building Backup Server ’SYB_BACKUP’: /opt/sybase/ASE-12_5/bin/srvbuildres: Writing entry into directory services... /opt/sybase/ASE-12_5/bin/srvbuildres: Directory services entry complete. /opt/sybase/ASE-12_5/bin/srvbuildres: Writing RUN_SERVER file... /opt/sybase/ASE-12_5/bin/srvbuildres: RUN_SERVER file complete. /opt/sybase/ASE-12_5/bin/srvbuildres: Starting server... /opt/sybase/ASE-12_5/bin/srvbuildres: Server started. /opt/sybase/ASE-12_5/bin/srvbuildres: Server ’SYB_BACKUP’ was successfully created. Backup Server Install Successful... The SYBASE Installation Process is Complete... ********************************************** Press Return to Continue ... 17. Press Return to continue. The Sybase Installation Menu appears. 18. At the Sybase Installation Menu, enter 6 to exit. The following message appears: Cleaning up temporary files...... Done. Exiting Installation script. 19. Remove the CD-ROM from the CD-ROM device. 20. To close the Tail window, with the cursor in the window, hold down and press C. The Sybase installation is complete.

Network Management Station Installation Guide 8/30/044-9 Beta Draft Confidential Installing Sybase 12.5.0.1 Installing Sybase 12.5.0.1

21. Source file that sets the environment variables by entering one of the following commands: If you are using C shell, enter: source /opt/sybase/SYBASE.csh If you are using Bourne shell, enter: . /opt/sybase/SYBASE.sh 22. Become the Sybase user by entering: su - sybase 23. Initiate an isql session by entering: isql -U sa -P For example, superbase. 24. Check the Sybase version that is currently running by entering: 1> select @@version 2> go 1> quit The following output is an example: Adaptive Server Enterprise/12.5.0.1/SWR 9982 IR/P/Sun_svr4/OS 5.8/rel12501/1776/64-bit/FBO/Tue Feb 26 01:22:10 2002

For information on Lucent-recommended patches, see the Software Release Notice for Sybase 12.5.0.1.

25. If you installed Sybase 12.5.0.1 in a two-system NMS configuration, proceed to Chapter 8, “Installing a Two-system Configuration.” 26. If you installed Sybase 12.5.0.1 in a single-system NMS configuration, proceed to Chapter 5, “Installing HP OpenView 6.2.”

4-10 Network Management Station Installation Guide Beta Draft Confidential

5

Installing HP OpenView 6.2

The HP OpenView for Sun system Version 6.2 network management software application runs in conjunction with NavisCore on the NMS. This chapter describes how to: • Set up the system • Install HP OpenView 6.2 software on the system • Disable IP Discovery • Verify the installation • Obtain information on installing HP OpenView patches

In this guide, HP OpenView Network Node Manager (NNM) will simply be referred to as HP OpenView.

Before You Begin

Before you set up the system, verify that you: • Are following the correct NMS installation sequence (See “Installation Sequence” on page 1-10) • Have installed Solaris 8 • Have installed Solaris 8 patch(es) • Have installed Sybase 12.5.0.1 • Have installed a Sybase backup server (local, remote, or both)

Network Management Station Installation Guide 5-1 Beta Draft Confidential Installing HP OpenView 6.2 Setting Up the System

Setting Up the System

The procedure in this section includes: • Loading the Lucent-supplied HP OpenView media • Extracting the installation script from the media • Running the installation script • Setting up the system

When you run the installation script the first time, the script sets up the system by adding semaphores to the /etc/system file. A semaphore is an interprocess communication signal that indicates the status of a shared system resource, such as shared memory. The installation encounters problems if you do not add semaphores to the /etc/system file. After the script updates this file, reboot the workstation.

To set up the system: 1. Verify that you are logged in as root user. You should see a # prompt in the Xterm window. If you are not logged in as root, enter su - root in the Xterm window. When prompted, enter . 2. Insert the HP OpenView 6.2 CD into the CD-ROM drive. 3. Change to the scripts directory by entering: cd /cdrom/cdrom0/cv_scripts 4. Run the HP OpenView installation script by entering: ./install_cvux The following message appears: Verifying superuser privileges.....

5-2 Network Management Station Installation Guide Beta Draft Confidential Installing HP OpenView 6.2 Setting Up the System

The NavisCore/UX Installation Menu appears (Figure 5-1).

[Press ^ C to abort...] NavisCore/UX Installation... 1. Install HPOV 2. Install NavisCore 3. Help... 4. Exit Please select one of the above options [1-4]?

Figure 5-1. NavisCore/UX Installation Menu

Network Management Station Installation Guide 8/30/045-3 Beta Draft Confidential Installing HP OpenView 6.2 Setting Up the System

5. At the NavisCore/UX Installation Menu, view the HP OpenView Installation Menu by entering 1. The HP OpenView Installation Menu appears (Figure 5-2).

[Press ^ C to abort...]

HP OpenView Installation Menu...

1. Install/Upgrade HP OpenView (to version 6.2) 2. Install Latest HP OpenView Patches (as of this release) 3. Enable IP Discovery Mechanism (Unsupported) 4. Disable IP Discovery Mechanism 5. Return to Main Menu

NOTE: Please refrain from using the ‘kill -9 [pid]’ command since this may leave your system in an undesired state.

Please select one of the above options [1-5]?

Figure 5-2. HP OpenView Installation Menu

5-4 Network Management Station Installation Guide Beta Draft Confidential Installing HP OpenView 6.2 Setting Up the System

6. At the HP OpenView Installation Menu, set up the system by entering 1.

When you select option 1 the first time, the script modifies the /etc/system file. These modifications take effect once you reboot the system. However, when you select option 1 again, the script installs HP OpenView 6.2.

The following message appears: Would you like to view (tail -f) the install log (default=y)? The Tail window allows users to view a log of the installation process. 7. Press Return.

In a new Xterm window on the local system, run “xhost +” as the user who controls the system console. Executing this command enables you to display the installation log on the local system.

The following message appears: What display should the install log xterm go to (default:0.0)? 8. Press Return or enter :0.0. The Tail Window appears and the following message appears in the Xterm window: Note: In order to restore back to the original state of your HP OpenView installation, it is recommended that you back your system up before continuing with this procedure. Complete all prerequisites before continuing. Do you wish to continue? [default=y]: 9. Press Return to continue. The following message appears: Modifications have been made to ‘/etc/system’. For the changes to take effect, you must REBOOT the workstation now. Then re-run the scripts after the system resumes. # 10. At the # prompt, enter init 6 to reboot the system. When the system reboots, the Sybase Server automatically shuts down and restarts. If you installed a two-system configuration, the Sybase Server does not shut down because Sybase now resides on another system. 11. Proceed to “Installing HP OpenView 6.2.”

Network Management Station Installation Guide 8/30/045-5 Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

Installing HP OpenView 6.2

In this section, you will: • Run the installation script • Install HP OpenView 6.2 software on the system • Disable IP map discovery • Verify the installation

To install HP OpenView 6.2: 1. Verify that you are logged in as root user. You should see a # prompt in the Xterm window. If you are not logged in as root, enter: su - root When prompted, enter: 2. Change to the cv_scripts directory by entering: cd /cdrom/cdrom0/cv_scripts 3. Run the HP OpenView installation script by entering: ./install_cvux The following message appears: Verifying superuser privileges.....

5-6 Network Management Station Installation Guide Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

The NavisCore/UX Installation Menu appears (Figure 5-3).

[Press ^ C to abort...] NavisCore/UX Installation... 1. Install HPOV 2. Install NavisCore 3. Help... 4. Exit Please select one of the above options [1-4]?

Figure 5-3. NavisCore/UX Installation Menu 4. At the NavisCore/UX Installation Menu, view the HP OpenView Installation Menu by entering 1. The HP OpenView Installation Menu appears (Figure 5-4).

[Press ^ C to abort...]

HP OpenView Installation Menu...

1. Install/Upgrade HP OpenView (to version 6.2) 2. Install Latest HP OpenView Patches (as of this release) 3. Enable IP Discovery Mechanism (Unsupported) 4. Disable IP Discovery Mechanism 5. Return to Main Menu

NOTE: Please refrain from using the ‘kill -9 [pid]’ command since this may leave your system in an undesired state.

Please select one of the above options [1-5]?

Figure 5-4. HP OpenView Installation Menu

Network Management Station Installation Guide 8/30/045-7 Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

5. At the HP OpenView Installation Menu, enter 1 to install HP OpenView 6.2. The following message appears: Would you like to view (tail -f) the install log (default=y)? The Tail window allows users to view the installation log. 6. Press Return.

In a new Xterm window on the local system, run “xhost +” as the user who controls the system console. Executing this command enables you to display the installation log on the local system.

The following message appears: What display should the install log xterm go to (default:0.0)? 7. Press Return or enter :0.0. The following message appears: Note: In order to restore back to the original state of your HP OpenView installation, it is recommended that you back your system up before continuing with this procedure. Complete all prerequisites before continuing. Do you wish to continue? [default=y]: 8. Press Return to continue. The script creates the Sybase and NMS user accounts. The script does this to provide user accounts on the HP Server if you install a two-system configuration (Sybase on one system, HP OpenView and NavisCore on another). If you are installing a single-system configuration, the user accounts have already been created by the Sybase installation script. The following messages assume a single-system configuration: Creating Group Account for ‘dba’ ------The group, ‘dba’, already exists. Creating a user account for sybase ------The user, sybase, already exists. Enter the Sybase environment path [default : /opt/sybase] ?

5-8 Network Management Station Installation Guide Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

9. Press Return to accept the default of /opt/sybase. The following message appears: You must add at least one more user account. Enter the name of the user [default : nms]? 10. Press Return to accept the default. The following message appears: Enter group to which the new user belongs [default : staff]? 11. Press Return to accept the default of staff. The following messages appear: Creating a user account for nms ------The user, nms, already exists. Enter the Sybase Server name [default : ] 12. Press Return to accept the default. The following message appears: Do you wish to continue? [default=y]: 13. Press Return to continue. The following message appears: Creating Additional User Accounts ------1. Create User Account. 2. Proceed to the Next Step. Please select one of the above options [1 or 2] ? 14. Do one of the following: • To create additional user accounts, enter 1. The script prompts you for information similar to that provided for the nms user account (see step 13 on page 5-9). Once you create the additional user, the Creating Additional User Accounts Menu reappears. • To proceed to the next step, enter 2. The following message appears when you enter 2: Install the media in your device now. ************************************** What is the path on the Local Host: 15. Enter /cdrom/cdrom0

Network Management Station Installation Guide 8/30/045-9 Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

The following message appears: The CD Installation media was found! [Hit Return to continue with the installation.] 16. Press Return. The following message appears: ======Welcome to the HP OpenView Network Node Manager Installation NNM Release B.06.20 for SunOS Apr 23 2001 Copyright (c) 1990-2001 Hewlett-Packard Company, All Rights Reserved. ======Do you want to install the manpages? (y|n): 17. Enter y or n. The following messages may appear, depending on your configuration: We did not detect any discovery data on your system. We recommend that you let Network Node Manager discover your network automatically. NOTE: Advanced users may not want to autodiscover if you want to configure how Network Node Manager performs discovery (e.g. install discovery filters, use a seedfile, or configure level 2 discovery). To start Network Node Manager discovery manually, you can select "Options -> Network Polling Configuration: IP" from the Network Node Manager user interface (ovw). Do you want Network Node Manager to discover your network automatically after the installation? (y/n): 18. Enter n. The following message appears: Do you want the Network Node Manager user interface to be displayed after the installation? (y|n): 19. Enter y. If you have a web browser installed, the following message appears: ** NOTE ** This install program has chosen the following browser for you: /usr/dt/bin/netscape to launch Network Node Manager web interface. If this is not the browser you would like to use, please edit the /etc/opt/OV/share/conf/ovweb.conf file after this installation.

5-10 Network Management Station Installation Guide Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

If you do not have a web browser installed, the following message appears: * * * WARNING * * * Install was not able to find a Web Browser in well known locations on your system. Until you install a Web Browser, you will not be able to request your license over the Web, nor will you be able to access the Network Node Manager Web interface. Please enter your Web Browser with full directory path or enter "s" to skip: /usr/dt/bin/netscape The following messages appear if you entered “s” to skip when prompted for the directory path of your Web Browser. * * * WARNING * * * If you plan to install a Web Browser at a later time, you will need to create the /etc/opt/OV/share/conf/ovweb.conf file after your browser installation. You need to add the following two lines to the file: Browser: %s Port: 8880 ** NOTE ** This install program has chosen the following browser for you: /opt/software/tools/bin/netscape to launch Network Node Manager web interface. If this is not the browser you would like to use, please edit the /etc/opt/OV/share/conf/ovweb.conf file after this installation. Messages similar to the following appear: This installation will put the following software on your system: HP OpenView Network Node Manager for Solaris 2.x HP OpenView Network Node Manager Manpages

Do you want to continue with this installation? (y|n): 20. To continue, enter y. The following messages appear: No further interaction is needed for this installation.

A typical Network Node Manager installation takes about 25 to 35 minutes.

If you want to closely track the progress of the installation, open a separate terminal window and give the command: tail -f /var/adm/sw/swagent.log

Network Management Station Installation Guide 8/30/045-11 Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

Notes and warnings will be written to this log as well as indications of the installation’s progress.

Do not use the kill command or Control-C to exit the install script once the installation process has begun. Using these commands may leave files on your system in a corrupt state.

The following messages appear: Congratulations! Your installation was successful. Starting Network Node Manager daemons:

Name PID State Last Message(s)

OVsPMD 5372 RUNNING -

pmd 5373 RUNNING Initialization complete.

ovrequestd 5374 RUNNING Initialization complete.

ovtrapd 5455 RUNNING Initialization complete.

ovsessionmgr 5453 RUNNING Initialization complete.

ovactiond 5456 RUNNING Initialization complete.

ovwdb 5454 RUNNING Initialization complete.

ovalarmsrv 5457 RUNNING Loading alarms from database

ovtopmd 5461 RUNNING Connected to native database “openview”.

ovuispmd 5468 RUNNING Initialized. 0 ovw clients registered.

ovalarmsrv 5457 RUNNING Initialization complete.

snmpCollect 5470 RUNNING Initialization complete.

netmon 5469 RUNNING Loading databases...

httpd - unknown (Does not communicate with ovspmd.)

ovdbcheck 5458 RUNNING Connected to embedded database.

5-12 Network Management Station Installation Guide Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

ovspmd: Attempt to start HP OpenView services is complete. Would you like to view the Release Notes? (y|n): 21. Enter n. The following messages appear: You can view the Release Notes at URL: file:/opt/OV/www/htdocs/C/ReleaseNotes/README_NNMGR.html

Network Node Manager Installation complete.

You may access the Network Node Manager interface by running: /opt/OV/bin/ovw & You may access the HP OpenView Java-based Web Interface using a Web Browswer pointed at the URL: http://[system_name]:8880/OvCgi/ovlaunch.exe

See the Release Notes for supported Web Browsers and for more details on using the HP OpenView Java-based Web Interface. Hit the Return key to Continue...

For details on the installation, review the log file (/var/adm/sw/swagent.log).

Network Management Station Installation Guide 8/30/045-13 Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

Disabling IP Discovery

IP Discovery finds all IP-addressable nodes on your network and creates an object for each discovered node. Lucent switches do not respond to IP Discovery; therefore, the script disables it. See Appendix C, “IP Discovery” to re-enable IP Discovery.

Lucent does not support IP Discovery. Enabling this feature severely affects the ! performance of your NMS Server.

When IP Discovery is disabled, the following messages display: HP OpenView Network Node Manager Configuration ********************************************** Setting up Symbolic Links...... Done. Disabling HP OpenView IP Configuration **************************************** Stopping the OV Platform...Done. Removing netmon...Done. Removing ovrepld...Done. Removing snmpcollect...Done. Removing ipmap...Done. Disabling XNmevents for netmon and snmpCollect...Done. The disabling of IP Map discovery is complete. Starting the HP OpenView object database...Done. Processing field registration entries...Done. Do you wish to continue? [default=y]: 22. Press Return to continue. The following message appears: Verifying the HPOV installation ------The HP OpenView Window and the Events Category dialog box will appear. Choose Map => Exit from HP OpenView to end the verification.

5-14 Network Management Station Installation Guide Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

Verifying the HP OpenView Installation The HP OpenView 6.2 installation successfully completes when you see the HP OpenView Window and Event Categories window (Figure 5-5).

Figure 5-5. HP OpenView 6.2 Window

To complete the installation: 23. Exit the HP OpenView window and Events Category window by selecting Map ⇒ Exit. 24. At the OpenView Windows WARNING dialog box, choose OK. The HP OpenView window and Events Category window disappears. 25. At the HP OpenView Installation Menu, enter 2 to install the HP OpenView patches. The following message appears: Would you like to view (tail -f) the install log (default=y)? 26. Press Return.

Network Management Station Installation Guide 8/30/045-15 Beta Draft Confidential Installing HP OpenView 6.2 Installing HP OpenView 6.2

In a new Xterm window on the local system, run “xhost +” as the user who controls the system console. Executing this command enables you to display the installation log on the local system.

The following message appears: What display should the install log xterm go to (default:0.0)? 27. Press Return. 28. After the patches are installed, at the HP OpenView Installation Menu, enter 5 to return to the main menu. 29. At the NavisCore/UX Installation Menu, exit by entering 4. The following message appears: Cleaning up temporary files...... Done. Exiting Installation script. 30. To close the Tail window, with the cursor in the window, hold down and press C.

See the latest Software Release Notice for HP OpenView 6.2 to verify that you have the latest mandatory patches.

5-16 Network Management Station Installation Guide Beta Draft Confidential

6

Installing NavisCore

NavisCore is an integrated network-management software application that incorporates HP OpenView to: • Create and edit network maps • Configure Lucent switches • Create and edit both nodes and trunks • Monitor network activity

This chapter describes how to install NavisCore and add a static route to the Network Management Station.

Before You Begin

Before you install NavisCore, verify that you: • Are following the correct NMS installation sequence (See “Installation Sequence” on page 1-10) • Have installed Solaris 8 • Have installed Solaris 8 patch(es) • Have installed Sybase 12.5.0.1 • Have installed HP OpenView 6.2 • Have installed HP OpenView 6.2 patches

Network Management Station Installation Guide 6-1 Beta Draft Confidential Installing NavisCore Installing NavisCore

Installing NavisCore

To install NavisCore: 1. Verify that you are logged in as root. If you are not logged in as root, enter: su - root When prompted, enter: 2. At the # prompt, verify Sybase is running by entering: ps -aef | grep data A message similar to the following appears:

The second line of output indicates Sybase is running.

Figure 6-1. Sybase Server Messages 3. If Sybase is not running, enter: /etc/rc2.d/S97sybase 4. Verify that HP OpenView Services is running by entering: /opt/OV/bin/ovstatus

6-2 Network Management Station Installation Guide Beta Draft Confidential Installing NavisCore Installing NavisCore

A similar message to the following appears if HP OpenView Services are running.

Figure 6-2. HP OpenView Services window 5. If HP OpenView Services are not running, enter: /opt/OV/bin/ovstart 6. Insert the NavisCore CD-ROM into the CD-ROM drive. 7. Change to the cv_scripts directory by entering: cd /cdrom/cdrom0/cv_scripts 8. Run the installation script by entering: ./install_cvux

Network Management Station Installation Guide 8/30/046-3 Beta Draft Confidential Installing NavisCore Installing NavisCore

The NavisCore/UX Installation Menu appears:

[Press ^ C to abort...] NavisCore/UX Installation... 1. Install HPOV 2. Install NavisCore 3. Help... 4. Exit Please select one of the above options [1-4]?

Figure 6-3. NavisCore/UX Installation Menu 9. At the NavisCore/UX Installation Menu, enter 2. The following message appears: Would you like to view (tail -f) the install log (default=y)? The Tail window allows users to view the installation log. 10. Press Return.

In a new Xterm window on the local system, run “xhost +” as the user who controls the system console. Executing this command enables you to display the installation log on the local system.

The following message appears: What display should the install log xterm go to (default:0.0)? 11. Press Return or enter :0.0.

6-4 Network Management Station Installation Guide Beta Draft Confidential Installing NavisCore Installing NavisCore

The Tail Window and the NavisCore Installation Menu appear:

[Press ^ C to abort...] NavisCore Installation Menu... 1. New NavisCore Installation (DB Creation) 2. Upgrade NavisCore Installation (DB Upgrade) 3. HP OpenView Integration only (NO DB Action) 4. Return to Main Menu Please select one of the above options [1-4]?

Figure 6-4. NavisCore Installation Menu 12. Select a new NavisCore installation by entering 1. The following messages appear: ********************************************************** This install will only work for the Solaris 7 Operating System and later. ********************************************************** Complete all prerequisite tasks before continuing. See the CV/UX Installation Documentation for more information. Do you wish to continue? [default=y]: 13. Press Return to continue.

See the Sybase worksheet in Appendix F for step 15 through step 19.

The following message appears: Sybase Information Request ***************************** Select the version of Sybase 1. Sybase 11.9.2 2. Sybase 12.5 Please enter 1 or 2

Network Management Station Installation Guide 8/30/046-5 Beta Draft Confidential Installing NavisCore Installing NavisCore

14. Enter 2. The following message appears: Enter the Sybase install path (default=/opt/sybase)? 15. Press Return to accept the default of /opt/sybase or enter . 16. At the Enter Database Server Name prompt, do either of the following: • Press Return to accept the default,. •Enter . 17. At the Enter the Sybase system administrator user name prompt, press Return to accept the default (sa). 18. At the Enter the NavisCore database name prompt, press Return to accept the default (cascview) or enter . 19. At the Enter Database SA Password prompt, enter . (For example, superbase) When prompted, re-enter the SA password. The following message appears: Do you wish to preserve trapd.conf customizations ‘y/n’ (default = ‘y’)? 20. Press Return to accept the default. The following message appears: Do you wish to extract CV/UX Installation media ‘y|n’ (default = ‘y’) ? 21. Press Return. The following message appears: Install the media in your device now. *********************************** 22. If you are prompted to enter the path of the local host, enter: /cdrom/cdrom0/ where is the NavisCore tar file name. See the latest Software Release Notice for the NavisCore tar file name. The following message appears: The CD Installation Media was found! [Hit Return to continue with the installation.]

6-6 Network Management Station Installation Guide Beta Draft Confidential Installing NavisCore Installing NavisCore

23. Press Return to continue. The following message appears: Extracting CV/UX Installation Media into /opt...Done. Do you wish to continue? [default=y]: 24. Press Return to continue. The following message appears: Checking for pre-existing NavisCore Installations *************************************************** Creating a New NavisCore database ************************************** Enter the NavisCore database data size (default: 100): 25. Press Return to accept the default of 100. 26. At the Enter the NavisCore database Log size prompt, press Return to accept the default, 100. The following message appears: Creating the NavisCore database... Data Space = ‘100’ MB Log Space = ‘100’ MB Checking for pre-existing NavisCore Installations ************************************************* Running database script DBUTL_CreateDB.scr...Done. Running database script DBUTL_UpgradeDB.scr...Done

Configuring NavisCore Environment *********************************** Setting $SYBASE in /opt/CascadeView/etc/cvdb.cfg to ‘/opt/sybase’. Setting the database server name in /opt/CascadeView/etc/cvdb.cfg to Installing Java 2 Runtime Environment *************************************

NavisCore releases prior to 05.xx.xx.xx do not install the Java 2 Runtime Environment.

uncompressing package file..... Extracting package file.... Processing package instance from JDK 1.2 run time environment (sparc) 1.2.2,REV=2000.03.17.13.20 ## Software contents file initialized

Network Management Station Installation Guide 8/30/046-7 Beta Draft Confidential Installing NavisCore Installing NavisCore

The selected base directory must exist before installation is attempted. Do you want this directory created now [y,n,?,q] 27. Enter y and press Return. Using as the package base directory. ## Processing package information. ## Processing system information. ## Verifying package dependencies. The following messages appear: WARNING: The package "Core Architecture, (Root)" is a prerequisite package and should be installed. WARNING: The package "Core Architecture, (Kvm)" is a prerequisite package and should be installed. WARNING: The package "Core Solaris, (Root)" is a prerequisite package and should be installed. WARNING: The package "Core Solaris, (Usr)" is a prerequisite package and should be installed. WARNING: The package "Core Solaris Devices" is a prerequisite package and should be installed. WARNING: The package "Motif RunTime Kit" is a prerequisite package and should be installed. Do you want to continue with the installation of [y,n,?] 28. Enter y and press Return. The following messages appear: ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of [y,n,?]

6-8 Network Management Station Installation Guide Beta Draft Confidential Installing NavisCore Installing NavisCore

29. Enter y and press Return. The following messages appear: Installing JDK 1.2 run time environment as ## Installing part 1 of 1. clgrnam(): fopen(3C) failed for /opt/CascadeView/jre/jre1.2/etc/group. clpwnam(): fopen(3C) failed for /opt/CascadeView/jre/jre1.2/etc/passwd. /opt/CascadeView/jre/jre1.2/usr/java1.2/COPYRIGHT /opt/CascadeView/jre/jre1.2/usr/java1.2/bin/java /opt/CascadeView/jre/jre1.2/usr/java1.2/bin/keytool /opt/CascadeView/jre/jre1.2/usr/java1.2/bin/policytool /opt/CascadeView/jre/jre1.2/usr/java1.2/bin/rmid /opt/CascadeView/jre/jre1.2/usr/java1.2/bin/rmiregistry ...... [ verifying class ] ## Executing postinstall script.

Installation of was successful. Copying HP OpenView configuration files.... Done. Setting up NavisCore fields in HP OpenView database.... Done. Unloading MIBs from HP OpenView...Done. Loading Lucent MIBs into HP OpenView...... Done. Loading Standard MIBs into HP OpenView...... Done. Loading Lucent trap formats into HP OpenView (using -load option only).... Using -load option on /opt/CascadeView/conf/cv_load_trapd.conf ....Done. Resetting Trap Events...Done. Installing the NavisCore trap log daemon...Done. Installing the cv_ovstart...Done. Starting the trap log daemon...Done. Editing the inittab file ... Inserted entry into the inittab file for cvtraplogd ... The trap log daemon is started Use 'ovstatus cvtraplogd' to check the status of the daemon. Starting the setclock.crontab script...Done. Check the Perl Path defined in dbschema file....Done. HP OpenView Configuration Continued

Network Management Station Installation Guide 8/30/046-9 Beta Draft Confidential Installing NavisCore Installing NavisCore

*********************************** Setting up symbolic links to /opt/CascadeView.....Done. Resetting inetd...Done. Editing the inittab file...Done. Creating Startup scripts for tftpserv process...Done. ************************************** Install NavisCore Successful... Hit Return to Continue...

You may see the following messages during the installation. You can ignore them. Loading Lucent MIBs into HP OpenView...... Loading Standard MIBs into HP OpenView..... Warning: Unresolved User Defined Type Found 'XXXXXXX', will try to resolve it globally from all loaded modules where XXXXXXX varies. Examples are TimeStamp, TruthValue, etc.

6-10 Network Management Station Installation Guide Beta Draft Confidential Installing NavisCore Installing NavisCore

30. Press Return to continue. The NavisCore Installation Menu reappears. 31. At the NavisCore Installation Menu, exit by entering 4. 32. At the NavisCore/UX Installation Menu, exit by entering 4. 33. To close the Tail window, with the cursor in the window, hold down and press C. The installation of NavisCore is complete. 34. Proceed to “Defining a Static Route to the NMS” on page 6-12.

Network Management Station Installation Guide 8/30/046-11 Beta Draft Confidential Installing NavisCore Defining a Static Route to the NMS

Defining a Static Route to the NMS

To communicate with your network and manage your switches, you must add a static route from your NMS to your gateway switch. Figure 6-5 shows a sample static route connection. When you first create the Map, the default internal network address (152.148.0.0) is displayed.

• This section assumes you have already installed the gateway switch. See the appropriate manual (B-STDX 8000/9000 Hardware Installation Guide, CBX 500 Hardware Installation Guide, or GX 550 Multiservice WAN Switch Hardware Installation Guide).

If you use Routing Information Protocol (RIP) to communicate with your network, you do not have to define a Static Route to the NMS. For more information on RIP, see the NavisCore IP Navigator Configuration Guide.

Network 152.148.0.0 152.148.0.3 152.148.0.2

152.148.0.1

152.148.51.31

Gateway

152.148.51.0

152.148.51.194 NMS

Figure 6-5. Static Route Connection Example

6-12 Network Management Station Installation Guide Beta Draft Confidential Installing NavisCore Defining a Static Route to the NMS

To define a static route from the switch to the NMS: 1. Verify that you are logged in as the root user. You should see a # prompt. 2. Enter the following command: vi /etc/rc2.d/S98netmgt The script /etc/rc2.d/S98netmgt adds the static route automatically during system reboot. 3. While holding down the Shift key, type G and press Return to go to the end of the file. 4. Type o and press Return to open a new line. 5. Add the following lines to the end of the file: /usr/sbin/route add net 1

For the switch network number, use a valid IP address assigned to you by the American Registry for Internet Numbers (ARIN).

6. Press the Esc key. 7. Type :wq! and press Return. 8. Log in as root user. Enter the password when prompted. 9. Enter the following command to add the static route: route add net 1

Network Management Station Installation Guide 8/30/046-13 Beta Draft Confidential Installing NavisCore Defining a Static Route to the NMS

6-14 Network Management Station Installation Guide Beta Draft Confidential

7

Backup Procedures

This chapter describes how to: • Back up the Sybase 12.5.0.1 Server to the local backup server the first time • Perform subsequent Sybase 12.5.0.1 backups to the local backup server • Back up HP OpenView 6.2 databases • Save Sybase 12.5.0.1 and HP OpenView databases to tape • Change the SA password

The Technical Assistance Center (TAC) strongly recommends that you perform daily backups of the Sybase cascview database. For more information on Sybase 12.5.0.1 backup procedures, see the Configuration Guide Sybase Adaptive Server Enterprise for UNIX.

Lucent recommends that you periodically test the integrity of Sybase and HP OpenView backups by loading the backups on a separate test Sun workstation. Also, Lucent recommends testing the recovery of switch data in the “cascview” database to ensure that it loads properly. Contact the Technical Assistance Center for specific instructions. See “Technical Support” on page xix.

You can use scripts to perform backups automatically. However, Lucent does not provide these scripts. These scripts are left to your discretion.

Network Management Station Installation Guide 7-1 Beta Draft Confidential Backup Procedures First-time Backup to the Local Backup Server

First-time Backup to the Local Backup Server

To back up the Sybase 12.5.0.1 Server to the local backup server the first time: 1. Log in as the Sybase user by entering: su - sybase If you have a two-system configuration (Sybase on one workstation, HP OpenView/NavisCore on another), log on to either server workstation. 2. Change to the /opt/sybase directory by entering: cd /opt/sybase 3. Create a backup directory by entering: mkdir backup 4. Enter the following command: script /opt/sybase/backup/sybck.out The script command saves any database output from the dbcc checkdb command (step 6) and places it in the sybck.out file. In addition, output is displayed on screen. 5. Initiate an isql session by entering: isql -U sa -P For example, superbase. 6. Check for database errors by entering: 1> dbcc checkdb(master) 2> go 1> dbcc checkdb(cascview) 2> go 1> dbcc checkalloc(master) 2> go 1> dbcc checkalloc(cascview) 2> go 1> dbcc checkcatalog(master) 2> go 1> dbcc checkcatalog(cascview) 2> go 1> quit The following message is normal and should be disregarded: *** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.

7-2 Network Management Station Installation Guide Beta Draft Confidential Backup Procedures First-time Backup to the Local Backup Server

If you encounter errors when you perform the dbcc checkdb command, do not proceed any further and call the Technical Assistance Center. See “Technical Support” on page xix.

7. Press and D to stop the script command. 8. Check for errors in the /opt/sybase/backup/sybck.out file. 9. Initiate an isql session by entering: isql -U sa -P For example, superbase. 10. If there are no dbcc errors, save the master and cascview databases by entering: 1> dump database master to "/opt/sybase/backup/masterbackup." 2> go 1> dump database cascview to "/opt/sybase/backup/cascbackup." 2> go 1> quit The refers to today’s date in MM-DD-YY format. 11. Proceed to “Backing Up HP OpenView Databases” on page 7-7.

Network Management Station Installation Guide 8/30/047-3 Beta Draft Confidential Backup Procedures Subsequent Backups to the Local Backup Server

Subsequent Backups to the Local Backup Server

Use these steps to back up the Sybase 12.5.0.1 Server to the local backup server on a daily basis.

The Technical Assistance Center strongly recommends that you back up the Sybase “cascview” database daily.

1. Log in as the Sybase user by entering: su - sybase If you have a two-system configuration (Sybase on one workstation, HP OpenView/NavisCore on another), log on to either server workstation. 2. Enter the following command: script /opt/sybase/backup/sybck.out The script command saves any database output from the dbcc checkdb command (step 4) and places it in the sybck.out file. In addition, the output is displayed on screen. 3. Initiate an isql session by entering: isql -U sa -P For example, superbase. 4. To check the consistency of the database, enter: 1> dbcc checkdb(master) 2> go 1> dbcc checkdb(cascview) 2> go 1> dbcc checkalloc(master) 2> go 1> dbcc checkalloc(cascview) 2> go 1> dbcc checkcatalog(master) 2> go 1> dbcc checkcatalog(cascview) 2> go 1> quit The following message is normal and should be disregarded: *** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.

7-4 Network Management Station Installation Guide Beta Draft Confidential Backup Procedures Subsequent Backups to the Local Backup Server

If you encounter errors when you perform the dbcc checkdb command, do not proceed any further and call the Technical Assistance Center. See “Technical Support” on page xix.

5. Press and D to stop the script command. 6. Check for errors in the file /opt/sybase/backup/sybck.out. 7. Initiate an isql session by entering: isql -U sa -P For example, superbase. 8. Save the transaction log by entering: 1> dump transaction cascview to “/opt/sybase/backup/transbackup.” 2> go The refers to today’s date in MM-DD-YY format. 9. Save the master and cascview databases by entering: 1> dump database master to "/opt/sybase/backup/masterbackup." 2> go 1> dump database cascview to "/opt/sybase/backup/cascbackup." 2> go 1> quit The refers to today’s date in MM-DD-YY format. The backup procedures now require you to bulk copy out your Sybase database. 10. If you do not have a directory to save the bulk copy files, create a directory by entering: mkdir /opt/sybase/backup/storedb 11. Bulk copy the database to the storedb directory by entering: /opt/CascadeView/bin/cv-copydb.sh out cascview /opt/sybase/backup/storedb For example, could be superbase.

Network Management Station Installation Guide 8/30/047-5 Beta Draft Confidential Backup Procedures Subsequent Backups to the Local Backup Server

Figure 7-1 shows sample output. Tables vary with each NavisCore release.

Getting database information for: cascview ...... Done. The total data device size is: 50 The total log device size is 150 dbschema.pl on Database cascview Add user-defined data types...Done Create rules...Done Create defaults...Done Bind rules & defaults to user data types...Done Create Tables & Indices...Object does not have any indexes. Done Create views...Done Create stored procs...Done Create triggers...Done Looks like I'm all done! Dumping Table: cascview.dbo.Access Dumping Table: cascview.dbo.AccessTypeTable . . . Database Schema transaction completed successfully.

Figure 7-1. Bulk Copy Output A file called CVCOPY_cascview_data.tar is created in the /opt/sybase/backups/storedb directory.

7-6 Network Management Station Installation Guide Beta Draft Confidential Backup Procedures Backing Up HP OpenView Databases

Backing Up HP OpenView Databases

Use the following procedure to back up HP OpenView databases, the application programs and datafiles, and the configuration files by saving the /opt/OV/databases/openview, /opt/CascadeView, and /opt/CascadeView.var directories. 1. Log in as the root user by entering: su - root When the system prompts you for the root password, enter: If you have a two-system configuration (Sybase on one workstation, HP OpenView and NavisCore on another), you must log on to the HP OpenView/NavisCore workstation to perform HP OpenView backups. 2. Shut down all NavisCore sessions. Verify that all NavisCore sessions are shut down by entering: ps -ef | grep ovw If all NavisCore sessions are shut down, the only process you should see running is ovwdb. 3. Shut down HP OpenView services by entering: /opt/OV/bin/ovstop 4. Access the databases directory by entering: cd /opt/sybase/backup 5. Enter the following command to back up HP OpenView databases: tar cvpf ovwdb.tar. /opt/OV/databases/openview 6. Enter the following command to back up the application programs and datafiles: tar cvpf ovwapp.tar. /opt/CascadeView 7. Enter the following command to back up the configuration files (all of the files downloaded to or uploaded from the switches): tar cvpf ovwconfig.tar. /opt/CascadeView.var The refers to today’s date in YYYYMMDD format. 8. Restart HP OpenView Services directory by entering: /opt/OV/bin/ovstart

In the event that the HP OpenView databases, application programs or associated files need to be restored, proceed to “Restoring HP OpenView Databases” on page 7-9.

Network Management Station Installation Guide 8/30/047-7 Beta Draft Confidential Backup Procedures Saving Sybase 12.5.0.1 and HP OpenView Databases to Tape

Saving Sybase 12.5.0.1 and HP OpenView Databases to Tape

To back up the Sybase 12.5.0.1 and HP OpenView databases to tape: 1. Back up the /opt/sybase/backup directory to tape. For example, as the root user, type: tar cvf /dev/rmt/0 /opt/sybase/backup If you have a two-system configuration (Sybase on one workstation, HP OpenView and NavisCore on another), you must log on to the HP OpenView/NavisCore workstation to save the Sybase and HP OpenView databases to tape.

Lucent recommends daily database backups. The preceding steps create multiple backups because the date extension changes daily. Keep at least one week’s worth of database backups.

7-8 Network Management Station Installation Guide Beta Draft Confidential Backup Procedures Restoring HP OpenView Databases

Restoring HP OpenView Databases

In the event that you need to restore the HP OpenView databases, application programs and datafiles, or the files downloaded to or uploaded from the switches, do the following: 1. Access the databases directory by entering: cd /opt/sybase/backup 2. Shut down HP OpenView services by entering: /opt/OV/bin/ovstop 3. Enter the following command to restore HP OpenView databases: tar xvpf ovwdb.tar. 4. Enter the following command to restore the application programs and datafiles, if necessary: tar xvpf ovwapp.tar. 5. Enter the following command to restore the configuration files, if necessary: tar xvpf ovwconfig.tar. 6. Restart HP OpenView Services directory by entering: /opt/OV/bin/ovstart

To restore the Sybase 12.5.0.1 and HP OpenView databases from tape: – Restore the /opt/sybase/backup directory from tape. For example, as the root user, type: tar xvpf /dev/rmt/0

Network Management Station Installation Guide 8/30/047-9 Beta Draft Confidential Backup Procedures Maintaining Backup Data in OV Databases

Maintaining Backup Data in OV Databases

There are built in procedures in HP OpenView that back up the data in OV databases. As a result of this, the size of the solid.db file in path /opt/OV/var/share/databases/analysis/default keeps increasing. The default maximum size of the solid.db file is 2 GB. If the file gets larger than that, the ovdbcheck process will fail and the solid.db file will have to be recreated.

To prevent this from happening, you should do regular housekeeping to control the size of the solid.db file. To do that, do the following: 1. Trim the snmp collect data by entering: /opt/OV/bin/ovdwtrend -u ovdb -password ovdb -trim 2. Trim the event data by entering: /opt/OV/bin/ovdwevent -trim

Recreating database file

In the event that the solid.db file exceeds 2 GB and the ovdbcheck process fails, then the solid.db will have to be recreated. To reinitialize the solid.db file, do the following: 1. If the ovdbcheck process is running, stop it by entering: /opt/OV/bin/ovdbcheck -stop 2. Change the current working directory by entering: cd /opt/OV/var/share/databases/analysis/default 3. Delete current database file by entering: rm solid.db 4. Delete current database files by entering: rm solmsg.* 5. Delete current database files by entering: rm ./log/sol*.log 6. Change the current working directory by entering: cd /opt/OV/var/share/databases/analysis/default 7. Create a new database file by entering: ovdbrun -x exit -u ovdb -p ovdb The following message will be displayed: Database does not exist. Do you want to create a new database (y/n)?

7-10 Network Management Station Installation Guide Beta Draft Confidential Backup Procedures Maintaining Backup Data in OV Databases

8. Enter y. The following message will be displayed: Give system catalog, administrator’s username and password. 9. When prompted for a System Catalog name, enter solid.db. 10. When prompted for Username, enter ovdb. 11. When prompted for Password, enter ovdb. Enter it again when prompted. The following message will be displayed: Creating a new database, please wait ... 12. Change the current working directory by entering: cd /opt/OV/share/conf/analysis 13. Recreate the ovdw.conf file by entering: /opt/OV/bin/ovdwcfggetset -file ovdw.conf -s : -set “user: ovdb” The following message is displayed: Adding element name: user 14. Execute the following command: /opt/OV/bin/ovdwcfggetset -file ovdw.conf -s : -set “password: ovdb” -encrypt 1 The following message is displayed: Adding element name: password 15. Execute the following command: /opt/OV/bin/ovdwcfggetset -file ovdw.conf -s “:@” -set “db: yes” The following message is displayed: Adding element name: db 16. Change the current working directory by entering: cd /opt/OV/share/conf/analysis/sqlScripts 17. Start the ovdbcheck process by entering: /opt/OV/bin/ovdbcheck -start The following messages are displayed: Connecting as user “ovdb” with password Validate accessability to “tcpip 2690” database Start embedded database if needed 18. Create a new table in the solid.db file by entering: /opt/OV/bin/ovdwquery -file tables_common.solid

Network Management Station Installation Guide 8/30/047-11 Beta Draft Confidential Backup Procedures Maintaining Backup Data in OV Databases

19. Create another new table in the solid.db file by entering: /opt/OV/bin/ovdwquery -file tables_event.solid 20. Create another new table in the solid.db file by entering: /opt/OV/bin/ovdwquery -file tables_trend.solid 21. Create another new table in the solid.db file by entering: /opt/OV/bin/ovdwquery -file tables_topo.solid 22. Stop the ovdbcheck process by entering: /opt/OV/bin/ovdbcheck -stop 23. Start the ovdbcheck process by entering: /opt/OV/bin/ovstart -v ovdbcheck

7-12 Network Management Station Installation Guide Beta Draft Confidential Backup Procedures Changing the System Administrator (SA) Password

Changing the System Administrator (SA) Password

For security purposes, Lucent recommends you change the default password (superbase) to one you define yourself. This password is similar to the UNIX root password. If you lose the SA password, you cannot log in as the system administrator.

To change the Sybase password: 1. At the # prompt, enter: su - sybase 2. Initiate an isql session by entering: isql -U sa -P For example, superbase.

Do not forget the SA password in step 3. You need the SA password to initiate an isql session.The password must be at least six characters in length. If you enter a password with fewer characters, you will be unable to initiate an isql session. Do not enter CASCADE for the Database SA Password (it is a reserved Sybase word).

3. At the prompts, enter: 1> sp_password , 2> go 1> quit 4. Log in as root by entering su - root. When prompted, enter . 5. To change the ownership of the /etc/rc0.d/K01sybase file so only root can read it, enter: chmod 400 /etc/rc0.d/K01sybase 6. If necessary, use vi to edit the file and change the default SA password to the password you defined in step 1 through step 3.

Network Management Station Installation Guide 8/30/047-13 Beta Draft Confidential Backup Procedures Changing the System Administrator (SA) Password

7-14 Network Management Station Installation Guide Beta Draft Confidential

8

Installing a Two-system Configuration

A two-system NMS configuration has Solaris and Sybase installed on one workstation, and Solaris, HP OpenView, and NavisCore installed on another.

Two-System Installation Outline

You need to use the following sequence to install a two-system configuration:

System 1 1. Install Solaris 8 (Chapter 2) 2. Install Solaris 8 patch cluster (Chapter 2) 3. Install Sybase 12.5.0.1 (Chapter 3 and Chapter 4) System 2 1. Install Solaris 8 (Chapter 2) 2. Install Solaris 8 patch cluster (Chapter 2) 3. Install HP OpenView 6.2 (Chapter 5) 4. Install HP OpenView 6.2 patches (SRN For HP OpenView 6.2) 5. Install NavisCore (Chapter 6)

Refer to the latest Software Release Notice for Sybase 12.5.0.1 for any required Sybase 12.5.0.1 patches.

Network Management Station Installation Guide 8-1 Beta Draft Confidential Installing a Two-system Configuration NMS Post-Installation Sequence

NMS Post-Installation Sequence

After you install NMS software on both systems, make sure you have 123-MB of free space in /opt on the HP OpenView/NavisCore workstation.

After you install the NMS software on both systems, do the following:

Task See

Verify that the Sybase Server is running (System 1). page 8-2

Verify that HP OpenView Services are running (System 2). page 8-3

Add the Sybase Server hostname and IP address to HP page 8-4 OpenView Server’s /etc/hosts file (System 2).

Create an interfaces file and add Sybase Server information page 8-6 to the HP OpenView Server’s interfaces file (System 2).

Sybase Server (System 1)

To verify that the Sybase and local backup server are running: 1. Become the sybase user by entering su - sybase. 2. Change to the install directory by entering: cd ASE-12_5/install

8-2 Network Management Station Installation Guide Beta Draft Confidential Installing a Two-system Configuration NMS Post-Installation Sequence

3. Verify Sybase is running by entering: showserver If Sybase and local backup server are running, a message similar to the following appears:

Figure 8-1. Showserver Window If Sybase and local backup server are not running, do the following: a. At the $ prompt, enter exit. b. At the # prompt, start the Sybase Server by entering: /etc/rc2.d/S97sybase c. Start the local backup server by entering: /etc/rc2.d/S98sybase 4. Proceed to “Verifying That HP OpenView Services Are Running (System 2)” on page 8-3.

HP OpenView Server (System 2)

This section requires you to: • Verify that HP OpenView Services are running. • Add the Sybase Server hostname and IP address to HP OpenView Server’s /etc/hosts file. • Create an interfaces file and add Sybase Server information to the HP OpenView Server’s interfaces file.

Verifying That HP OpenView Services Are Running (System 2)

To verify that HP OpenView Services are running: 1. Make sure that you are logged in as root user. You should see a # prompt.

Network Management Station Installation Guide 8/30/048-3 Beta Draft Confidential Installing a Two-system Configuration NMS Post-Installation Sequence

If you are not logged in as root, enter su - root. When prompted, enter . 2. Enter the following command to verify that HP OpenView Services are running: /opt/OV/bin/ovstatus The following messages appear if HP OpenView Services are running:

Figure 8-2. HP OpenView Services Window 3. If HP OpenView Services are not running, enter: /opt/OV/bin/ovstart 4. Continue with the following section.

Adding the Sybase Server Hostname (System 2)

You must add the Sybase Server hostname and IP address to HP OpenView’s /etc/hosts file. To add the hostname and IP address: 1. Verify that you are logged in as root. You should see a # prompt. 2. In the Xterm window, enter: admintool & The Admintool: Users dialog box appears.

8-4 Network Management Station Installation Guide Beta Draft Confidential Installing a Two-system Configuration NMS Post-Installation Sequence

Figure 8-3. Admintool: Users Dialog Box 3. Select Browse ⇒ Hosts. The Admintool: Hosts dialog box appears.

Figure 8-4. Admintool: Hosts Dialog Box 4. Select Edit ⇒ Add. The Admintool: Add Host dialog box appears.

Figure 8-5. Admintool: Add Host Dialog Box

Network Management Station Installation Guide 8/30/048-5 Beta Draft Confidential Installing a Two-system Configuration NMS Post-Installation Sequence

5. In the Admintool: Add Host dialog box, enter: Host Name — Enter Sybase Server’s hostname. IP Address — Enter Sybase Server’s IP address. 6. Choose Apply. The system adds the Sybase Server’s hostname and IP address to the HP OpenView Server’s host table. 7. Choose OK. 8. At the Admintool: Hosts dialog box, select File ⇒ Exit. 9. Continue with the following section.

Copying the Interfaces File (System 2)

To enable communication between the HP OpenView Server and the Sybase Server, you must: • Extract Open Client 12.5 tar file and place it on the HP OpenView Server. • Copy an interfaces file for the HP OpenView Server.

To create an interfaces file: 1. Become the Sybase user by entering: 2. su - sybase 3. Put the Open Client 12.5 CD-ROM in the CD-ROM drive. 4. Create an /opt/sybase directory on the HP OpenView Server by entering: mkdir /opt/sybase 5. Gunzip the Sybase Open Client file by entering: gunzip -c /cdrom/cdrom0/ > /opt/sybase/ For example, gunzip -c /cdrom/cdrom0/syb_client.03.00.07.00.tgz > /opt/sybase/syb_client.03.00.07.00.tar 6. Change to the /opt/sybase directory by entering: cd /opt/sybase 7. Extract Open Client 12.5 from the tar file by entering: tar xvf See the latest Software Release Notice for Sybase 12.5.0.1 for the Open Client tar file name.

8-6 Network Management Station Installation Guide Beta Draft Confidential Installing a Two-system Configuration NMS Post-Installation Sequence

8. Source file that sets the environment variables by entering one of the following commands: If you are using C shell, enter: source /opt/sybase/SYBASE.csh If you are using Bourne shell, enter: . /opt/sybase/SYBASE.sh 9. Open a File Transfer Protocol (FTP) connection to the Sybase Server by entering: ftp 10. Copy the interfaces file by entering: get interfaces 11. Exit by entering: quit 12. Change to the /opt directory by entering: cd /opt 13. Change ownership to Sybase user by entering: chown -R sybase sybase 14. Change the group to dba by entering: chgrp -R dba sybase 15. Verify that you completed the task successfully by logging into isql. Enter: isql -U sa -P For example, superbase. The 1> prompt appears. 16. At the 1> prompt, enter: quit 17. Add a static route from the HP OpenView/NavisCore Server to the gateway switch (see “Defining a Static Route to the NMS” on page 6-12). 18. See Table 1-4 on page 1-11 and Table 1-5 on page 1-11 to determine how to proceed.

Network Management Station Installation Guide 8/30/048-7 Beta Draft Confidential Installing a Two-system Configuration NMS Post-Installation Sequence

8-8 Network Management Station Installation Guide Beta Draft Confidential

A

Installing a New Remote Backup Server

This appendix describes how to install a new remote backup server. These steps are: • Adding the Remote Backup Server Hostname • Installing the Remote Backup Server • Adding the Remote Backup Server’s Interfaces File Contents • Configuring the Remote Backup Server

Before you install a new remote backup server, contact the Technical Assistance Center. See “Technical Support” on page xix.

Network Management Station Installation Guide A-1 Beta Draft Confidential Installing a New Remote Backup Server Adding the Remote Backup Server Hostname

Adding the Remote Backup Server Hostname

Before you configure a remote backup server, you must add the backup server hostname to the Sybase Server host table on the Sybase Server workstation. Then, perform the following steps: 1. In an Xterm window, log in as root by entering: su - root When prompted, enter: 2. In the Xterm window, enter: admintool & The Admintool: Users dialog box appears.

Figure A-1. Admintool: Users Dialog Box

A-28/30/04 Network Management Station Installation Guide Beta Draft Confidential Installing a New Remote Backup Server Adding the Remote Backup Server Hostname

3. Select Browse ⇒ Hosts. The Admintool: Hosts dialog box appears.

Figure A-2. Admintool: Hosts Dialog Box 4. Select Edit ⇒ Add. The Admintool: Add Host dialog box appears.

Figure A-3. Admintool: Add Host Dialog Box 5. Complete the following fields: Host Name — Enter the remote backup server’s hostname. IP Address — Enter the remote backup server’s IP address. See the Appendix F, “Sybase Worksheet,” to complete the fields. 6. Choose Apply. The system adds the remote backup server’s hostname to the Sybase Server’s host table. 7. Choose OK. The Admintool: Hosts dialog box reappears. 8. Select File ⇒ Exit.

Network Management Station Installation Guide 8/30/04A-3 Beta Draft Confidential Installing a New Remote Backup Server Installing the Remote Backup Server

Installing the Remote Backup Server

This section describes how to: • Install the Sybase backup server on the remote backup server workstation. • Create a backup directory on the remote backup server workstation.

To install the remote backup server, perform the following steps: 1. Log in as the root user by entering: su - root When prompted, enter: 2. Insert the Sybase 12.5.0.1 CD-ROM into the CD-ROM drive. 3. In an Xterm window, enter: cd /opt 4. Remove the installation scripts from the Sybase tar file by entering: tar xvf /cdrom/cdrom0/ cv_scripts See the latest Software Release Notice for Sybase 12.5.0.1 for the Sybase tar file name. 5. Change to the cv_scripts directory by entering: cd /opt/cv_scripts 6. Run the Sybase installation script by entering: ./install_sybase 7. At the Would you like to view (tail -f) the install log (default=y) prompt, press Return to accept the default (yes).

In a new Xterm window on the local system, run “xhost +” as the user who controls the system console. Executing this command enables you to display the installation log on the local system.

The following message appears: What display should the install log xterm go to (default:0.0)? 8. Press Return or enter :0.0.

A-48/30/04 Network Management Station Installation Guide Beta Draft Confidential Installing a New Remote Backup Server Installing the Remote Backup Server

9. At the Sybase Installation Menu, enter 4 to configure a remote Sybase backup server. The following message appears: Complete all upgrade prerequisites before continuing. See Sybase 11 Upgrade Documentation. Do you wish to continue? , [default=y]: 10. Press Return to continue. The following message appears: Setting up your system for the Sybase Install ------Creating the dba group for database system administrator. Successfully added group ‘dba’ with gid 300 Creating a user account for sybase ------Enter User’s home directory [default : /opt/sybase] ? 11. Press Return to accept the default of /opt/sybase. The following message appears: Adding user sybase. Please Wait... Successfully added user sybase... Configuring the user account with environment files. ------Creating /etc/rc2.d/S98sybase..Done. Do you wish to continue? [default=y]:

Network Management Station Installation Guide 8/30/04A-5 Beta Draft Confidential Installing a New Remote Backup Server Installing the Remote Backup Server

12. Press Return to continue. The system displays the configured Backup Server parameters in a window similar to Figure A-4.

Figure A-4. Sybase Backup Server Installation Parameters Window 13. To change any parameters, enter the parameter number and make the appropriate changes. 14. When you have made your changes, continue by entering 0. The following message appears: Backup Server Configuration ********************************************* Backup Server requires the same utilities loaded as the Sybase Server. You will need to load the sybase media in the device now. Do you wish to continue? [default=y]: 15. Press Return to continue. The following message appears: Do you wish to extract Sybase Installation media ‘y|n’ (default = ‘y’)? 16. Press Return.

A-68/30/04 Network Management Station Installation Guide Beta Draft Confidential Installing a New Remote Backup Server Installing the Remote Backup Server

17. The following message appears: Install the media in your local device now. ******************************************* Enter the full path of the media device: 18. Enter: /cdrom/cdrom0/ See the latest Software Release Notice for Sybase 12.5.0.1 for the Sybase tar file name. The following message appears: The device was found and is ready for extraction. Press Return to Continue.... 19. Press Return. Extracting Sybase Media from media device...Done. Running ‘sybinit’ and creating the sybase server...Backup Sybase Server Install Successful... Do you wish to continue? [default=y]:

Running the sybinit utility takes approximately five minutes.

20. To continue, press Return. The Sybase Installation Menu appears. 21. At the Sybase Installation Menu, enter 6 to exit. 22. Remove the media from the media device drive. 23. Open an Xterm window and log in as the sybase user by entering: su - sybase 24. Create a backup directory by entering: mkdir backup 25. Proceed to “Adding the Remote Backup Server’s Interfaces File Contents” on page A-8.

Network Management Station Installation Guide 8/30/04A-7 Beta Draft Confidential Installing a New Remote Backup Server Adding the Remote Backup Server’s Interfaces File Contents

Adding the Remote Backup Server’s Interfaces File Contents

To enable communication between the remote backup server and the Sybase 12.5.0.1 Server, from the Sybase Server workstation use the dsedit utility to add the contents of the remote backup server interfaces file to the Sybase Server interfaces file. Then, perform the following steps: 1. Open an Xterm window and enter: su - sybase 2. Enter: cd /opt/sybase/OCS-12_5/bin 3. Run the dsedit utility by entering: ./dsedit The dsedit-Select a Directory Service dialog box appears. 4. Select the Sybase interfaces file and choose OK. The dsedit-Directory Service Section dialog box appears. 5. Choose Add New Server Entry. The dsedit -Server Entry Editor dialog box appears. 6. In the dsedit-Server Entry dialog box, do the following: a. In the “Enter Name of Remote Syb Backup Server” field, enter REMOTE_SYB_BACKUP. b. Choose Add New Network Transport. The dsedit-Network Transport Editor dialog box appears. 7. Do the following: a. In the “Transport Type” field, select tlitcp. b. In the “Hostname” field, enter . c. In the “Enter Port Number” field, enter 1027. d. Choose OK. The Server Entry Editor dialog box appears. 8. Choose OK. The Directory Service Session dialog box appears. 9. Choose Close Session. The Select a Directory Service dialog box appears. 10. Choose Exit.

A-88/30/04 Network Management Station Installation Guide Beta Draft Confidential Installing a New Remote Backup Server Adding the Remote Backup Server’s Interfaces File Contents

11. At the $ prompt, view the updated interfaces file by entering: cat interfaces Figure A-5 shows an example of an interfaces file.

Remote Backup server parameters

Figure A-5. Interfaces File Window 12. Proceed to “Configuring the Remote Backup Server” on page A-10.

Network Management Station Installation Guide 8/30/04A-9 Beta Draft Confidential Installing a New Remote Backup Server Configuring the Remote Backup Server

Configuring the Remote Backup Server

Before you backup the Sybase 12.5.0.1 Server to the remote backup server for the first time, follow the steps below to complete the configuration process.

On the Sybase Server Workstation: 1. Log in as the Sybase user by entering: su - sybase 2. At the $ prompt, view the interfaces file by entering: cat interfaces 3. Verify that the interfaces file entry for REMOTE_SYB_BACKUP on the Sybase Server is identical to the entry for REMOTE_SYB_BACKUP on the remote backup server.

If necessary, use a text editor such as vi to cut and paste the entry for REMOTE_SYB_BACKUP from the interfaces file on the remote backup server to the interfaces file on the Sybase Server.

4. Add an entry into the sysservers table for REMOTE_SYB_BACKUP by doing the following: a. Initiate an isql session by entering: isql -U sa -P For example, superbase. The 1> prompt appears. b. At the 1> prompt, enter: 1> sp_addserver REMOTE_SYB_BACKUP, null 2> go 1> quit

On the Remote Backup Server:

Perform the following steps to start a backup server process with the name RUN_REMOTE_SYB_BACKUP on the backup server workstation. 1. Change to the install directory by entering: cd /opt/sybase/ASE-12_5/install 2. Create a file to start up the backup server process by entering: cp RUN_SYB_BACKUP RUN_REMOTE_SYB_BACKUP

A-108/30/04 Network Management Station Installation Guide Beta Draft Confidential Installing a New Remote Backup Server Configuring the Remote Backup Server

3. Use a text editor to modify the Error Log Path (-e) and the “Backup Server Name” field (-S) in the RUN_REMOTE_SYB_BACKUP file that you created on the backup server. Replace the existing entries with the following text:

Error Log Path: -e/opt/sybase/ASE-12_5/install/REMOTE_err.log \ -e

Backup Server Name: -SREMOTE_SYB_BACKUP \ -S

4. Start up the backup process on the remote server by entering: startserver -f ./RUN_REMOTE_SYB_BACKUP 5. Verify that the remote backup server process is running by entering: showserver If the local backup server and the remote backup server are running, messages similar to the following appear:

tetra: /opt/sybase/ASE-12_5/install/showserver UID PID PPID C STIME TTYTIMECMD root 319 317 45 14:13:01117:07 /opt/sybase/ASE-12_5/bin/backupserver -d/dev/rdsk/c0t8d0s0 -e/opt/sybase/ASE-12_5/install/TETRA_backup_err.log root 319 317 45 14:13:01117:07 /opt/sybase/ASE-12_5/bin/remotebackupserver -d/dev/rdsk/c0t8d0s0 -e/opt/sybase/ASE-12_5/install/TETRA_remote_backup_err.log

Figure A-6. Showserver Window (Remote Backup Server) 6. Initiate an isql session by entering: isql -U sa -P For example, superbase. The 1> prompt appears. 7. At the 1> prompt, save the cascview database by entering: 1> dump database cascview to "/opt/sybase/backup/cascview.dmp" at REMOTE_SYB_BACKUP 2> go 1> quit 8. Proceed to Appendix B, “Backing up to the Remote Backup Server.”

Network Management Station Installation Guide 8/30/04A-11 Beta Draft Confidential Installing a New Remote Backup Server Configuring the Remote Backup Server

A-128/30/04 Network Management Station Installation Guide Beta Draft Confidential

B

Backing up to the Remote Backup Server

This appendix describes how to back up Sybase 12.5.0.1 to the remote backup server and save the Sybase 12.5.0.1 database to tape.

The Technical Assistance Center recommends that you backup the Sybase 12.5.0.1 Server daily. For more information on Sybase 12.5.0.1 backup procedures, see the Sybase SQL Server System Administrator’s Guide and the Sybase SQL Reference Manual, Volumes 1 and 2.

If you need to recover switch data in the cascview database, contact the Technical Assistance Center for specific instructions. Do not attempt to restore this database without Lucent’s help. See “Technical Support” on page xix.

Lucent recommends customers to periodically test the integrity of Sybase and HP OpenView backups by loading the backups on a separate test Sun workstation.

You can use scripts to automatically perform backups. However, Lucent does not provide these scripts. These scripts are left to the customer’s discretion.

Network Management Station Installation Guide B-1 Beta Draft Confidential Backing up to the Remote Backup Server First-time Backup to the Remote Backup Server

First-time Backup to the Remote Backup Server

To back up the Sybase 12.5.0.1 Server to the remote backup server on the Sybase/HP OpenView/NavisCore Server workstation the first time:

If you have a three-system configuration (HP OpenView/NavisCore installed on a workstation, Sybase installed on another workstation, and remote backup server installed on a third workstation), log on to the HP OpenView/NavisCore workstation.

1. Become the Sybase user by entering: su - sybase 2. Change to the /opt/sybase directory by entering: cd /opt/sybase 3. Create a backup directory by entering: mkdir backup Sybase backups to the remote backup server do not go to the backup directory. This directory will contain the sybck.out log. 4. Enter: script /opt/sybase/backup/sybck.out The script command saves output from the dbcc checkdb command (step 6) and places it in the sybck.out file. In addition, the output goes to the screen. 5. Initiate an isql session by entering: isql -U sa -P For example, superbase.

B-28/30/04 Network Management Station Installation Guide Beta Draft Confidential Backing up to the Remote Backup Server First-time Backup to the Remote Backup Server

6. Check for database errors by entering: 1> dbcc checkdb(master) 2> go 1> dbcc checkdb(cascview) 2> go 1> dbcc checkalloc(master) 2> go 1> dbcc checkalloc(cascview) 2> go 1> dbcc checkcatalog(master) 2> go 1> dbcc checkcatalog(cascview) 2> go 1> quit The following message is normal and should be disregarded: *** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.

If you encounter errors when you perform the dbcc checkdb command, do not proceed any further. Call the Technical Assistance Center. See “Technical Support” on page xix.

7. Press and D to stop the script command. 8. Check for errors in the /opt/sybase/backup/sybck.out file. 9. Initiate an isql session by entering: isql -U sa -P For example, superbase. 10. If there are no dbcc errors, save the master and cascview databases by entering: 1> dump database master to "/opt/sybase/backup/masterbackup." at REMOTE_SYB_BACKUP 2> go 1> dump database cascview to "/opt/sybase/backup/cascbackup." at REMOTE_SYB_BACKUP 2> go 1> quit The refers to today’s date in MM-DD-YY format.

Network Management Station Installation Guide 8/30/04B-3 Beta Draft Confidential Backing up to the Remote Backup Server Subsequent Backups to the Remote Backup Server

Subsequent Backups to the Remote Backup Server

Use the following steps from the Sybase/HP/NavisCore workstation to backup the Sybase 12.5.0.1 Server to the Remote Backup Server on a daily basis.

The Technical Assistance Center strongly recommends that you back up the Sybase “cascview” database daily.

If you have a three-system configuration (HP OpenView/NavisCore installed on a workstation, Sybase installed on another workstation, and remote backup server installed on a third workstation), log on to the HP OpenView/NavisCore workstation.

1. Log in as the Sybase user by entering: su - sybase 2. Enter: script /opt/sybase/backup/sybck.out The script command saves output from the dbcc checkdb command (step 4) and places it in the sybck.out file. In addition, the output goes to the screen. 3. Initiate an isql session by entering: isql -U sa -P For example, superbase. 4. To check the consistency of the database, enter: 1> dbcc checkdb(master) 2> go 1> dbcc checkdb(cascview) 2> go 1> dbcc checkalloc(master) 2> go 1> dbcc checkalloc(cascview) 2> go 1> dbcc checkcatalog(master) 2> go 1> dbcc checkcatalog(cascview) 2> go 1> quit

B-48/30/04 Network Management Station Installation Guide Beta Draft Confidential Backing up to the Remote Backup Server Subsequent Backups to the Remote Backup Server

The following message is normal and should be disregarded: *** NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device.

In addition, if you encounter errors when you perform the dbcc checkdb command, do not proceed any further and call the Technical Assistance Center. See “Technical Support” on page xix.

5. Press and D to stop the script command. 6. Check for errors in the /opt/sybase/backup/sybck.out file. 7. Enter the following command: isql -U sa -P For example, superbase. 8. Save the transaction log by entering: 1> dump transaction cascview to “/opt/sybase/backup/transbackup.” at REMOTE_SYB_BACKUP 2> go The refers to today’s date in MM-DD-YY format. 9. Save the master and cascview databases by entering: 1> dump database master to "/opt/sybase/backup/masterbackup." at REMOTE_SYB_BACKUP 2> go 1> dump database cascview to "/opt/sybase/backup/cascbackup." at REMOTE_SYB_BACKUP 2> go 1> quit The refers to today’s date in MM-DD-YY format. The backup procedures now require you to bulk copy out your Sybase database. 10. If you do not have a directory to save the bulk copy files, create a directory by entering: mkdir /opt/sybase/backup/storedb

Network Management Station Installation Guide 8/30/04B-5 Beta Draft Confidential Backing up to the Remote Backup Server Backing Up HP OpenView Databases

11. Bulk copy the database to the storedb directory by entering: /opt/CascadeView/bin/cv-copydb.sh out cascview /opt/sybase/backup/storedb For example, could be superbase. Figure B-1 shows sample bulk copy output. Tables vary with each NavisCore release.

Getting database information for: cascview ...... Done. The total data device size is: 50 The total log device size is 150 dbschema.pl on Database cascview Add user-defined data types...Done Create rules...Done Create defaults...Done Bind rules & defaults to user data types...Done Create Tables & Indices...Object does not have any indexes. Done Create views...Done Create stored procs...Done Create triggers...Done Looks like I'm all done! Dumping Table: cascview.dbo.Access Dumping Table: cascview.dbo.AccessTypeTable . . . Database Schema transaction completed successfully.

Figure B-1. Bulk Copy Output A file called CVCOPY_cascview_data.tar is created in the /opt/sybase/backups/storedb directory.

Backing Up HP OpenView Databases

See “Backing Up HP OpenView Databases” on page 7-7 to back up your HP OpenView databases.

B-68/30/04 Network Management Station Installation Guide Beta Draft Confidential Backing up to the Remote Backup Server Saving Sybase 12.5.0.1 and HP OpenView Databases to Tape

Saving Sybase 12.5.0.1 and HP OpenView Databases to Tape

To back up the Sybase 12.5.0.1 and HP OpenView databases to tape on the Remote Backup Server Workstation: Back up the /opt/sybase/backup directory to tape. For example, as the root user, type: tar cvf /dev/rmt/0 /opt/sybase/backup

Lucent recommends daily backups. The preceding steps create multiple backups because the date extension changes daily. Keep at least one week’s worth of backups.

You can use scripts to perform backups automatically. However, Lucent does not provide these scripts. These scripts are left to the customer’s discretion.

Network Management Station Installation Guide 8/30/04B-7 Beta Draft Confidential Backing up to the Remote Backup Server Saving Sybase 12.5.0.1 and HP OpenView Databases to Tape

B-88/30/04 Network Management Station Installation Guide Beta Draft Confidential

C

IP Discovery

This appendix describes how to enable/disable IP Discovery. IP Discovery finds all IP-addressable nodes on your network and creates an object for each discovered node.

The Lucent script automatically disables IP Discovery during the installation of HP OpenView 6.2. However, if you use HP OpenView to manage an IP network, you can re-enable it.

Lucent does not support IP Discovery. Re-enabling this feature severely affects ! the performance of your NMS Server.

Network Management Station Installation Guide C-1 Beta Draft Confidential IP Discovery Enabling IP Discovery

Enabling IP Discovery

To enable IP discovery: 1. Log in as root user by entering: su - root When prompted, enter: 2. Insert the HP OpenView CD in the CD-ROM drive. 3. Change to the cv_scripts directory by entering: cd /cdrom/cdrom0/cv_scripts 4. Start the Installation script by entering: ./install_cvux 5. At the NavisCore/UX Installation Menu, enter 1 to view the HP OpenView Installation Menu. 6. At the HP OpenView Installation Menu, enter 3 to re-enable IP discovery. 7. Press Return to view the Tail window. The following message appears: Lucent does not support the IP discovery mechanism. Enabling this feature will severely impact the performance of your NMS Server. Do you wish to continue? [default=y] 8. Press Return to continue. The following message appears: Enabling IP Configuration ************************** Adding netmon...Done. Adding ovrepld...Done. Adding ovtopmd...Done. Adding snmpcollect...Done. Adding ipmap...Done. Enabling XNmevents for netmon and snmp collect...Done. Starting IP Discovery daemons...Done. The enabling of IP Map discovery is complete. [Hit return to continue.] 9. Press Return to continue. 10. At the HP OpenView Installation Menu, go to the NavisCore/UX Installation Menu by entering 5.

C-28/30/04 Network Management Station Installation Guide Beta Draft Confidential IP Discovery Disabling IP Discovery

11. At the NavisCore/UX Installation Menu, exit by entering 4. The following message appears: Cleaning up temporary files. Done. Exiting Installation script. 12. To close the Tail window, with the cursor in the window, hold down and press c.

Disabling IP Discovery

To disable IP Discovery: 1. Log in as root user by entering: su - root When prompted, enter: 2. Insert the HP OpenView CD-ROM in the CD ROM device. 3. Change to the cv_scripts directory by entering: cd /cdrom/cdrom0/cv_scripts 4. Start the Installation script by entering: ./install_cvux 5. At the NavisCore/UX Installation Menu, enter 1 to view the HP OpenView Installation Menu. 6. At the HP OpenView Installation Menu, enter 4 to disable IP discovery. 7. Press Return to view the Tail window. The following message appears: Disabling HP OpenView IP Configuration **************************************** Stopping the OV Platform...Done. Removing netmon...Done. Removing ovrepld...Done. Removing ovtopmd...Done. Removing snmpcollect...Done. Removing ipmap...Done. Disabling XNmevents for netmon and snmpCollect...Done. The disabling of IP Map discovery is complete. [Hit return to continue.]

Network Management Station Installation Guide 8/30/04C-3 Beta Draft Confidential IP Discovery Disabling IP Discovery

8. Press Return to continue. The following message appears: Starting the OpenView object database...Done. Processing field registration entries...Done. 9. At the HP OpenView Installation Menu, enter 5 to go to the NavisCore/UX Installation Menu. 10. At the NavisCore/UX Installation Menu, enter 4 to exit. The following message appears: Cleaning up temporary files. Done. Exiting Installation script. 11. To close the Tail window, with the cursor in the window, hold down and press c.

C-48/30/04 Network Management Station Installation Guide Beta Draft Confidential

D

Integrating NavisCore with HP OpenView

This appendix provides instructions on integrating NavisCore with HP OpenView.

Integrating NavisCore with HP OpenView

Follow the steps below to integrate NavisCore with HP OpenView: 1. Log in as root by entering: su - root When prompted, enter: 2. Insert the NavisCore CD-ROM into the CD-ROM drive. 3. Change to the cv_scripts directory by entering: cd /cdrom/cdrom0/cv_scripts 4. Run the installation script by entering: ./install_cvux The NavisCore/UX Installation Menu appears (Figure D-1 on page D-2).

Network Management Station Installation Guide D-1 Beta Draft Confidential Integrating NavisCore with HP OpenView Integrating NavisCore with HP OpenView

[Press ^ C to abort...] NavisCore/UX Installation... 1. Install HPOV 2. Install NavisCore 3. Help... 4. Exit Please select one of the above options [1-4]?

Figure D-1. NavisCore/UX Installation Menu 5. At the NavisCore/UX Installation Menu, enter 2. The NavisCore Installation Menu appears. 6. At the NavisCore Installation Menu, enter 3 to integrate NavisCore with HP OpenView 6.2. The following message appears: **************************************** No Sybase Functionality will be altered. ****************************************** Do you wish to continue? : 7. Press Return to continue. 8. When prompted to Enter the path where NavisCore is installed (default=/opt/CascadeView), press Return to accept the default. The following message appears: Do you wish to extract CV/UX Installation media ‘y|n’ (default = ‘n’)? 9. Enter n. The following message appears: Do you wish to continue? [default=y]: 10. Press Return.

D-28/30/04 Network Management Station Installation Guide Beta Draft Confidential Integrating NavisCore with HP OpenView Integrating NavisCore with HP OpenView

Messages similar to the following are displayed: Configuring NavisCore Environment *********************************** Installing Java 2 Runtime Environment ************************************* uncompressing package file..... Extracting package file.... Processing package instance from /opt/cvux/CascadeView.05.01.00.00/jre> JavaVM run time environment (sparc) 1.2.0,REV=1998.12.10.01.37 This appears to be an attempt to install the same architecture and version of a package which is already installed. This installation will attempt to overwrite this package. Using as the package base directory. ## Processing package information. ## Processing system information. 143 package pathnames are already properly installed. ## Verifying package dependencies. WARNING: The package "Core Architecture, (Root)" is a prerequisite package and should be installed. WARNING: The package "Core Architecture, (Kvm)" is a prerequisite package and should be installed. WARNING: The package "Core Solaris, (Root)" is a prerequisite package and should be installed. WARNING: The package "Core Solaris, (Usr)" is a prerequisite package and should be installed. WARNING: The package "Core Solaris Devices" is a prerequisite package and should be installed. WARNING: The package "Motif RunTime Kit" is a prerequisite package and should be installed. Do you want to continue with the installation of [y,n,?] y 11. Enter y and press Return.

Network Management Station Installation Guide 8/30/04D-3 Beta Draft Confidential Integrating NavisCore with HP OpenView Integrating NavisCore with HP OpenView

Messages similar to the following are displayed: ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. Installing JavaVM run time environment as ## Installing part 1 of 1. [ verifying class ] Installation of was successful. Processing package instance from /opt/cvux/CascadeView.05.01.00.00/jre> JavaVM thread library (sparc) 1.2.0,REV=1998.12.10.01.37 This appears to be an attempt to install the same architecture and version of a package which is already installed. This installation will attempt to overwrite this package. Using as the package base directory. ## Processing package information. ## Processing system information. 12 package pathnames are already properly installed. ## Verifying package dependencies. WARNING: The package "Core Architecture, (Root)" is a prerequisite package and should be installed. WARNING: The package "Core Architecture, (Kvm)" is a prerequisite package and should be installed. The package "Core Solaris, (Root)" is a prerequisite package and should be installed. WARNING: The package "Core Solaris, (Usr)" is a prerequisite package and should be installed. WARNING: The package "Core Solaris Devices" is a prerequisite package and should be installed. Do you want to continue with the installation of [y,n,?] y 12. Enter y and press Return to continue.

D-48/30/04 Network Management Station Installation Guide Beta Draft Confidential Integrating NavisCore with HP OpenView Integrating NavisCore with HP OpenView

The following messages appear: ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of [y,n,?] y 13. Enter y and press Return to continue. Messages similar to the following are displayed: Installing JavaVM thread library as ## Installing part 1 of 1. [ verifying class ] ## Executing postinstall script. Installation of was successful. Copying HP OpenView configuration files.... Done. Setting up NavisCore fields in HP OpenView database.... Done. Unloading MIBs from HP OpenView...... Done. Loading Lucent MIBs into HP OpenView...... Done. Loading Standard MIBs into HP OpenView...... Done. Loading Lucent trap formats into HP OpenView (using -merge option).... Using -load option on /opt/CascadeView/conf/cv_load_trapd.conf ....Done. Resetting Trap Events...Done. Installing the NavisCore trap log daemon...Done. Starting the trap log daemon...Done. Use 'ovstatus cvtraplogd' to check the status of the daemon. Starting the setclock.crontab script...Done. Check the Perl Path defined in dbschema file....Done. Starting the Perl Installation....Done. HP OpenView Configuration Continued *********************************** Setting up symbolic links to /opt/CascadeView.....Done. Resetting inetd...Done. Editing the inittab file...Done. Creating Startup scripts for tftpserv process...Done. ************************************** Install NavisCore Successful... Hit Return to Continue 14. Press Return. After the integration completes, the NavisCore Installation Menu appears. 15. At the NavisCore Installation Menu, enter 4 to exit. 16. At the NavisCore/UX Installation Menu, enter 4 to exit.

Network Management Station Installation Guide 8/30/04D-5 Beta Draft Confidential Integrating NavisCore with HP OpenView Integrating NavisCore with HP OpenView

D-68/30/04 Network Management Station Installation Guide Beta Draft Confidential

E

NMS Startup and Shutdown Procedures

This chapter provides manual startup/shutdown procedures. Lucent does not require you to perform these procedures because both startup and shutdown occurs automatically with the following Lucent-provided scripts (these scripts were installed during the Sybase install, see page 3-16):

/etc/rc2.d/S97sybase — Starts Sybase data server

/etc/rc2/d/S98sybase — Starts local Sybase backup server

/etc/rc0/K01sybase — Shuts down Sybase

For example, if a power outage occurs, the script /etc/rc0/K01sybase shuts down the Sybase Server automatically. When power is restored, the scripts /etc/rc2.d/S97sybase and /etc/rc2d/S98sybase restart Sybase and local backup servers automatically.

To check if you have these files, enter cd .

Starting Up the NMS

To start the NMS: 1. Log in as root user by entering: su - root When prompted, enter: 2. Start the Sybase Server by entering: /etc/rc2.d/S97sybase

Network Management Station Installation Guide E-1 Beta Draft Confidential NMS Startup and Shutdown Procedures Starting Up the NMS

You do not have to start the local Backup Server if it was never shut down. If you need to start it, enter /etc/rc2.d/S98sybase.When the system displays the last line of text ’iso)_1’ (ID = 1), press Return.

3. Start HP OpenView Services by entering: /opt/OV/bin/ovstart 4. Log in as the nms user by entering: su - nms 5. To execute HP OpenView and NavisCore, enter: /opt/OV/bin/ovw & The system displays the HP OpenView root window, Event Categories window, and NavisCore Icon.

Figure E-1. HP OpenView 6.2 Window

E-28/30/04 Network Management Station Installation Guide Beta Draft Confidential NMS Startup and Shutdown Procedures Shutting Down the NMS

Shutting Down the NMS

To manually shut down the NMS: 1. To exit NavisCore, select Map ⇒ Εxit from the HP OpenView File Menu. 2. At the OpenView Windows Warning dialog box, select OK. 3. Log in as root by entering: su - root When prompted, enter: 4. Shut down HP OpenView Services by entering: /opt/OV/bin/ovstop 5. Shutdown the Sybase Server by entering: /etc/rc0.d/K01sybase You do not have to shut down the local Backup Server. 6. At the # prompt, halt the system by entering: init 0 Shutdown time varies according to site. 7. At the ok prompt, power off the system.

Network Management Station Installation Guide 8/30/04E-3 Beta Draft Confidential NMS Startup and Shutdown Procedures Shutting Down the NMS

E-48/30/04 Network Management Station Installation Guide Beta Draft Confidential

F

Sybase Worksheet

During the Sybase installation, the script prompts you for the parameters on this worksheet. The Lucent-recommended parameter settings are in italics.

Prerequisites 1. Sybase Home Directory:______(/opt/sybase)_ 2. Database Server Name:______(Your Hostname in CAPITAL LETTERS) 3. Error Log Pathname:______([Your Hostname in CAPITAL LETTERS]_err.log) 4. Database SA Password:______(superbase) 5. Name of additional user:______(nms) User’s group:______(staff) Home directory:______(/opt/nms) 6. TCP Socket Number of Sybase:______(1025) 7. TCP Socket Number of Local Backup Server:______(1026) 8. Number of Remote Users:______(150)

Network Management Station Installation Guide F-1 Beta Draft Confidential Sybase Worksheet

Using Raw Partitions for the Sybase Devices 1. Master Device Pathname:______(/dev/rdsk/c0t1d0s0) 2. Sysprocsdev Device Pathname:______(/dev/rdsk/c0t1d0s4) 3. NavisCore Data Device Pathname:______(/dev/rdsk/c0t1d0s5) 4. NavisCore Log Device Pathname:______(/dev/rdsk/c0t1d0s6) 5. Master Device size:______(200)

Using File System Files for the Sybase Devices (For Lab Only) 1. Database Device Directory:______(/opt/databases) 2. Master Device:______(200) 3. Sysprocsdev Device size:______(200) 4. NavisCore Data Device size:______(50) 5. NavisCore Log Device size:______(100)

Remote Backup Server Parameters

Complete if you install a Remote Backup Server. 1. Remote Backup Server’s hostname:______2. Remote Backup Server’s IP address:______3. Sybase user’s home directory:______(/opt/sybase) 4. TCP Socket Number of Remote Backup Server:______(1025)

F-28/30/04 Network Management Station Installation Guide Beta Draft Confidential

Acronyms

This guide uses the following acronyms:

Acronym Description

ACS Access Control Server

ARIN American Registry for Internet Numbers

ATM Asynchronous Transfer Mode

BIO Base Input/Output

CDE Common Desktop Environment

CD-ROM compact disc read-only memory

CNM Customer Network Management

DS1 digital signal, level 1

DS3 digital signal, level 3

FR Frame Relay

FTP File Transfer Protocol

GB gigabyte

HP Hewlett-Packard Company

IDE integrated drive electronics

IMA Inverse Multiplexing for ATM

IOM input/output module

IP Internet Protocol

MB megabyte

Network Management Station Installation Guide Acronyms-1 Beta Draft Confidential Acronyms

Acronym Description

MHz megahertz

MIB Management Information Base

NIS Network Information Service

NMS Network Management System

NNM National Network Management

OS Operating System

RAM Random Access Memory

RIP Routing Information Protocol

SCSI Small Computer System Interface

SNMP Simple Network Management Protocol

SQL structured query language

SRN Software Release Notice

TAC Technical Assistance Center

TCP Transmission Control Protocol

WAN wide area network

Acronyms-2 Network Management Station Installation Guide Beta Draft Confidential

Index

A Sybase and Backup Server’s startup and shutdown files, 3-16 Acronyms, xx to xxi the nms user, 3-16 the sybase user, 3-15 Customer comments, 1-3 B

Backup procedures, 7-1 to 7-12, B-1 to B-7 D HP OpenView database backups, 7-7, B-7 remote Sybase 11.9.2 Server, B-1 Defining partitions, 3-5 to 3-11 Sybase backups to local backup server, 7-1 to 7-6 Disabling IP Discovery, C-3 first-time backups, 7-1 to 7-3 DSQUERY, 4-5 subsequent backups, 7-3 to 7-6 Sybase backups to remote backup server, B-2 to B-6 E first-time backups, B-2 to B-3 subsequent backups, B-4 to B-6 Enabling IP Discovery, C-2 Backup Server Entering Remote. See Remote Backup Server the database SA password, 3-16 Bulk copy procedures, 7-5, B-5 the errorlog, 3-16

C H

CD-ROM HP OpenView 6.10 loading HP OpenView 6.10, 5-2 creating additional users, 5-9 loading NavisCore, 6-3 creating the Sybase and NMS user accounts, 5-8 loading Solaris 7, 2-2 database backups, 7-7 loading Sybase 11.9.2, 3-13 disabling IP Discovery, 5-15 Conventions, xvii installing, 5-6 to 5-18 Creating integrating with NavisCore, D-1 to D-6 additional Sybase user accounts, 3-17 loading Lucent-supplied media, 5-2

Network Management Station Installation Guide Index-1 Beta Draft Confidential Index

patches, 1-8, 5-18 M setting up the system, 5-2 to 5-5, ?? to 5-18 verifying the installation, 5-16 to ?? Manuals ordering online, xix Master device I pathname, 4-5 setting, 3-19 Installation scripts using file system files (lab configurations only), HP OpenView/NavisCore, 1-9 3-22 Sybase, 1-9 using raw partitions, 3-20 to 3-21 Installation sequence, 1-10 to 1-11 Installing HP OpenView 6.10, 5-6 to 5-18 N NavisCore, 6-1 to 6-15 Remote Backup Server, A-1 to A-11 NavisCore Solaris 7, 2-1 to ?? adding a static route to the NMS, 6-14 to 6-15 Solaris 7, cluster patch, 2-10 installing, 6-1 to 6-15 Sybase 11.9.2, 4-1 to ?? integrating with HP OpenView, D-1 to D-6 Two-system configuration, 8-1 to 8-7 setting the device name, 3-18 Installing Solaris 7 Network Management Station on new hardware, 2-6 installation sequence, 1-10 to 1-11 standard method, 2-2 requirements Integrating HP OpenView 6.10 with NavisCore, configuration. See system configuration D-1 to D-6 general, 1-1 IP Discovery, C-1 to C-4 software disabling, C-3 HP OpenView Network Node Manager enabling, C-2 (NNM) Version 6.10, 1-7 NavisCore 08.00.xx.xx, 1-8 Open Client Version 11.1.1, 1-7 J Solaris 7 patches, 1-7 Solaris Operating Environment, 1-6 JDBC libraries, installation messages, 6-8 Sybase 11.9.2 SQL Server, 1-7 system configuration, 1-1 to 1-5 L shutdown procedures, E-3 startup procedures, E-1 Loading NMS. See Network Management Station the HP OpenView media, 5-2 the NavisCore media, 6-3 the Solaris 7 media, 2-2 O the Sybase media, 3-13 OpenClient 11.1.1 Local Backup Server extracting in a single-system NMS, 4-10 first-time Sybase backups, 7-1 extracting in a two-system NMS, 8-6 subsequent Sybase backups, 7-3 Ordering printed manuals, xix Overview, 1-1 to 1-11

Index-2 Network Management Station Installation Guide Beta Draft Confidential Index

P patches, installing, 2-10 to ?? upgrading to, ?? to 2-5 Partitioning the second disk using raw partitions Starting the NMS, E-1 to E-2 creating a log device on partition 6, 3-10 Subsequent, 7-3 creating a master device on partition 0, 3-7, 3-8 Sybase creating a NavisCore device on partition 5, 3-9 backing up local databases, 7-5 creating a system procs device on partition 4, 3-8 backing up remote databases, B-5 defining partitions 1, 3, and 7, 3-5 configuration parameters, 4-5 error log file, 4-5 prerequisite tasks, 3-1 to 3-24 R using the dsedit utility, A-8 worksheet Remote Backup Server, A-1 prerequisites, F-1 to F-2 adding hostname to Sybase Server’s host table, remote backup server parameters, F-2 A-2 to A-3 using file system files for the master device, adding interfaces file to Sybase Server’s F-2 interfaces file, A-8 to A-9 using raw partitions for the master device, F-2 configuring, A-10 to A-11 System Procs device, pathname, 4-5 creating the sybase user account, A-5 System setup prior to Sybase installation, 3-15 first-time backups, B-2 to B-3 creating additional user accounts, 3-17 installation parameters window, A-6 creating the nms user, 3-16 installing, A-1 to A-11 creating the sybase user, 3-15 subsequent backups, B-4 to B-6 entering the database SA password, 3-16 entering the errorlog, 3-16 loading the Lucent-supplied Sybase media, 3-13 S setting the Sybase and Backup Server’s TCP socket numbers, 3-17 SA_USER, 4-5 Sybase and Backup Server’s startup and SCSI device addresses, 1-6 shutdown files, 3-16 Setting the Master device, 3-19 NavisCore device name, 3-18 T Sybase and Backup Server’s TCP socket numbers, 3-17 Tape, backing databases to, 7-8 Shutting down the NMS, E-3 Two-system configuration, 8-1 Small Computer System Interface device HP Server addresses. See SCSI device addresses adding Sybase Server’s hostname, 8-4 Software requirements, 1-6 to 1-8 creating the interfaces file, 8-6 Solaris 7 starting HP OpenView Services, 8-3 CDE. See Common Desktop Environment installing, 8-1 to 8-7 (CDE) Sybase Server, starting, 8-2 cluster patch, installing, 2-10 Common Desktop Environment (CDE), 1-6, 2-1 installing, 2-1 to 2-10 on new hardware, 2-6 standard method, 2-2

Network Management Station Installation Guide Index-3 Beta Draft Confidential Index

U

Upgrading Solaris, ?? to 2-5

V

Verifying HP OpenView 6.10 installation, 5-16 to 5-18 partition sizes, 3-11 Sybase 11.9.2 installation, 4-10

W

Worksheet remote backup server parameters, F-2 Sybase prerequisites, F-1 to F-2 using file system files for the master device, F-2 using raw partitions for the master device, F-2

Index-4 Network Management Station Installation Guide Network Management Station Installation Guide Customer Comments

Please take time to fill out this questionnaire so that we can do our best to meet your documentation needs. Then fax or e-mail your comments to our Technical Publications Dept. Your opinions are of great value to us!

FAX: (978) 692-1510 (Attn: Tech Pubs) E-MAIL: [email protected]

What tasks did you perform using this guide?

Did you install the hardware/software? If you were having trouble performing a task, were you able to find the information you needed? Was the index useful?

Were the examples and illustrations helpful for performing tasks? If not, how can they be improved?

Was there any information you needed that was not in the manual? If so, how can we best deliver that information to you?

What did you like/not like about the manual?

Do you have any other comments about the manual?

Cut Here Page Description of Error

Name Company Mailing Address

Phone E-mail address Fax No.