Beta Draft Confidential
Network Management Station Upgrade Guide
Product Code: 80126 Revision 01 December 2000 Beta Draft Confidential
Copyright© 2000 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, InterNetworking Systems/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. Cascade, IP Navigator, Navis, NavisXtend, NavisCore, Priority Frame, Rapid Upgrade, and WebXtend are 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, contact your Lucent Technologies account representative.
Support Telephone Numbers. For technical support and other services, see the customer support contact information in the “About This Guide” section of this document.
ii12/28/00 Network Management Station Upgrade 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 Upgrade Guide 12/28/00iii 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.
iv12/28/00 Network Management Station Upgrade 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 Upgrade Guide 12/28/00v Beta Draft Confidential
vi12/28/00 Network Management Station Upgrade Guide Beta Draft Confidential
Contents
About This Guide What You Need to Know...... xiii Reading Path ...... xiv NMS Documentation...... xiv Switch Software Documentation...... xv How to Use This Guide...... xvi What’s New in This Guide ...... xvi Conventions ...... xvii Related Documents ...... xviii Third Party...... xix Ordering Printed Manuals Online...... xix Customer Comments...... xix Customer Support ...... xx
Chapter 1 Overview Upgrade Requirements...... 1-2 General Requirements ...... 1-2 NMS System Configuration Requirements...... 1-2 SCSI Device Addresses ...... 1-7 Software Requirements ...... 1-7 Solaris ...... 1-7 Sybase ...... 1-7 Sybase Space...... 1-8 HP OpenView...... 1-9 NavisCore ...... 1-9 NMS Software ...... 1-9 Solaris Operating System ...... 1-9 Solaris 2.6 Cluster Patch ...... 1-10 Sybase 11.9.2 SQL Server...... 1-10 Open Client, Version 11.1.1...... 1-10 HP OpenView Network Node Manager Version 5.01...... 1-11 Installation Scripts ...... 1-12 Sybase...... 1-12 HP OpenView...... 1-12
Network Management Station Upgrade Guide rvii Beta Draft Confidential Contents
Upgrade Path...... 1-13 Single-System NMS...... 1-13 Two-System NMS...... 1-14
Chapter 2 Upgrading to Solaris 2.6 Before You Begin ...... 2-1 Upgrading to Solaris 2.6 ...... 2-2 Installing the Solaris Cluster Patch...... 2-7 Editing the New Solaris 2.6 Inittab File...... 2-8
Chapter 3 Completing Sybase Prerequisite Tasks Before You Begin ...... 3-1 Checking the Sybase Version ...... 3-2 Completing the Sybase Upgrade Worksheet ...... 3-3 Logging Off All Sybase Users...... 3-3 Backing Up and Verifying Your Databases...... 3-5 First-time Backup to the Local Backup Server ...... 3-5 Subsequent Backups to the Local Backup Server...... 3-8 Increasing the Size of the sybsystemprocs and model Databases...... 3-11 Memory Considerations for the NMS and Sybase ...... 3-15 Physical Memory...... 3-16 Adding Physical Memory ...... 3-16 Shared Memory ...... 3-17 Changing Shared Memory...... 3-17 Sybase Total Memory ...... 3-18 Changing Sybase Total Memory ...... 3-18
Chapter 4 Upgrading to Sybase 11.9.2 Before You Begin ...... 4-1 Running the Upgrade Script...... 4-2 Extracting OpenClient 11.1.1...... 4-15 Backup Procedures...... 4-16 First-time Backup to the Local Backup Server ...... 4-17 Subsequent Backups to the Local Backup Server...... 4-19 Saving Sybase 11.9.2 Databases to Tape ...... 4-21 Changing the System Administrator (SA) Password ...... 4-22
Chapter 5 Upgrading to HP OpenView 5.01 Before You Begin ...... 5-1 Upgrading to HP OpenView 5.01...... 5-2 Disabling IP Discovery ...... 5-7 Verifying the HP OpenView Installation ...... 5-8 Backing Up HP OpenView Databases...... 5-9
Chapter 6 Installing a Two-System Configuration NMS Post-Installation Sequence ...... 6-1 Sybase Server (System 1)...... 6-2 viii12/28/00 Network Management Station Upgrade Guide Beta Draft Confidential Contents
HP OpenView Server (System 2)...... 6-3 Verifying That HP OpenView Services Are Running (System 2) ...... 6-3 Adding the Sybase Server Hostname (System 2) ...... 6-4 Copying the Interfaces File (System 2)...... 6-6
Appendix A IP Discovery Enabling IP Discovery ...... A-2 Disabling IP Discovery...... A-4
Appendix B HP OpenView 5.01 Upgrade Error Messages Tail Window Error Messages...... B-1 Installation Xterm Window Error Messages...... B-2
Appendix C Sybase Worksheet
Index
Network Management Station Upgrade Guide ix Beta Draft Confidential Contents List Of Figures
Figure 2-1. IP Address and Subnet Mask Window ...... 2-2 Figure 2-2. Solaris Install Console Window ...... 2-3 Figure 2-3. Solaris Install Console Window ...... 2-5 Figure 3-1. Showserver Command...... 3-3 Figure 3-2. Bulk Copy Output...... 3-10 Figure 4-1. Sybase Installation Menu...... 4-4 Figure 4-2. Sybase Upgrade Parameters ...... 4-8 Figure 4-3. Bulk Copy Output...... 4-21 Figure 5-1. NavisCore/UX Installation Menu...... 5-3 Figure 5-2. HP OpenView Installation Menu...... 5-3 Figure 5-3. Installation Messages...... 5-5 Figure 5-4. HP OpenView 5.01 Window ...... 5-8 Figure 6-1. Showserver Window...... 6-2 Figure 6-2. HP OpenView Services Window...... 6-3 Figure 6-3. Admintool: Users Dialog Box ...... 6-4 Figure 6-4. Admintool: Hosts Dialog Box ...... 6-5 Figure 6-5. Admintool: Add Host Dialog Box...... 6-5
x12/28/00 Network Management Station Upgrade Guide Beta Draft Confidential Contents
Network Management Station Upgrade Guide 12/28/00xi Beta Draft Confidential Contents List Of Tables
Table 1-1. NavisCore System Configuration Requirements...... 1-3 Table 1-2. SCSI Device Addresses ...... 1-7 Table 1-3. Single-System Upgrade Path ...... 1-13 Table 1-4. Sybase Server Upgrade Path...... 1-14 Table 1-5. HP OpenView/NavisCore Upgrade Path...... 1-14 Table 4-1. Scenario 1 for TCP Socket Configuration...... 4-6 Table 4-2. Scenario 2 for TCP Socket Configuration...... 4-6
xii12/28/00 Network Management Station Upgrade Guide Beta Draft Confidential
About This Guide
The Network Management Station Upgrade Guide describes software upgrade instructions for your UNIX Network Management Station (NMS) platform. This task-oriented guide describes, step-by-step, the process for upgrading the required software (Solaris 2.6, Sybase 11.9.2, HP OpenView 5.01) for configuring Lucent switches.
This guide supports the following NMS software release:
•NavisCore™, Release 5.1 or greater
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 for a list of documents that describe this 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 Upgrade Guide xiii Beta Draft Confidential About This Guide Reading Path
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 5.1 or greater. 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
xiv12/28/00 Network Management Station Upgrade Guide Beta Draft Confidential About This Guide Reading Path
Switch Software Documentation
Read the following documents to configure software for the B-STDX 8000/9000™, CBX 500™,andGX550™ switch platforms.
This guide describes the processor and I/O modules on each switch platform, and how to configure physical ports, timing, and other attributes through NavisCore.
NavisCore Physical Interface Configuration Guide
The following guides describe how to configure WAN services on the B-STDX, CBX, and GX switch platforms:
• NavisCore Frame Relay Configuration Guide
NavisCore • NavisCore ATM Configuration Guide Configuration Guides
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 Upgrade Guide 12/28/00xv Beta Draft Confidential About This Guide How to Use This Guide
How to Use This Guide
Before you read this guide, read the Software Release Notices for Sybase 11.9.2 and HP OpenView 5.01.
This guide contains the following information:
Read To Learn About
Chapter 1 Upgrade overview
Chapter 2 Installing Solaris 2.6
Chapter 3 Preparing for Sybase 11.9.2 installation
Chapter 4 Installing Sybase 11.9.2
Chapter 5 • Setting up the system for HP OpenView 5.01 upgrade
• Upgrading to HP OpenView 5.01
Chapter 6 Installing a two-system configuration
Appendix A Enabling/Disabling IP Discovery
Appendix B HP OpenView 5.01 upgrade error messages
Appendix C Sybase worksheet
What’s New in This Guide
This guide includes the following changes and enhancements:
Changes/Enhancements See
Revised NMS system configuration information section to reflect page 1-2 optimal performance requirements.
Updated Sybase patch display example. page 4-14
Revised two-system configuration installation instructions. page 6-6
xvi12/28/00 Network Management Station Upgrade Guide Beta Draft Confidential About This Guide Conventions
Conventions
This guide uses the following conventions, when applicable:
Convention Indicates Example
Courier Regular System messages and output, Please wait... prompts, pathnames, filenames, and command names.
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
Boxes around text Notes, warnings, cautions. 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 Upgrade Guide 12/28/00xvii Beta Draft Confidential About This Guide Related Documents
Related Documents
This section lists the related Lucent documentation that may be helpful to read.
• B-STDX 8000/9000 Hardware Installation Guide (Product Code: 80005)
• CBX 500 Hardware Installation Guide (Product Code: 80011)
• GX 550 Multiservice WAN Switch Hardware Installation Guide (Product Code: 80077)
• GX 250 Multiservice Extender Hardware Installation Guide (Product Code: 80086)
• 8-Port Subrate DS3 FR/IP I/O Module User’s Guide (Product Code: 80123)
• Base Input/Output 2 (BIO2) Module User’s Guide (Product Code: 80124)
• Network Management Station Installation Guide (for new installations of Solaris 2.6, Sybase 11.9.2, and HP OpenView 5.01, and NavisCore) (Product Code: 80097)
• NavisCore NMS Getting Started Guide (Product Code: 80106)
• NavisCore Physical Interface Configuration Guide (Product Code: 80099)
• NavisCore Frame Relay Configuration Guide (Product Code: 80100)
• NavisCore ATM Configuration Guide (Product Code: 80101)
• NavisCore IP Navigator Configuration Guide (for B-STDX 6.5.2.x, CBX 3.5.2.x, and GX 1.5.2.x) (Product Code: 80114)
• NavisCore Diagnostics Guide (Product Code: 80105)
• NavisCore Troubleshooting Guide (Product Code: 80104)
• Console Command Reference (for B-STDX 7.2.2.x, CBX 4.2.2.x, and GX 2.2.2.x) (Product Code: 80103)
• Console Command Reference (for B-STDX 6.5.2.x, CBX 3.5.2.x, and GX 1.5.2.x) (Product Code: 80125)
All manuals for Core Systems and the Master Glossary are available on the Core Systems Documentation Library CD-ROM (Product Code: 80025).
xviii12/28/00 Network Management Station Upgrade Guide Beta Draft Confidential About This Guide Ordering Printed Manuals Online
Third Party
• Solaris SMCC™ Hardware Platform Guide
• Sybase SQL Server Installation and Configuration Guide
• Sybase SQL Server System Administrator’s Guide
• Sybase SQL Reference manual, Volumes 1 and 2
• HP OpenView NNM 5.01 Documentation Set
Ordering Printed Manuals Online
You can order Core Switching manuals online. Use the following URL to access the Lucent INS Bookstore: http://www.lucent.com/ins/bookstore
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.
Network Management Station Upgrade Guide 12/28/00xix Beta Draft Confidential About This Guide Customer Support
Customer Support
To obtain release notes, technical tips, or support, contact the Lucent Technical Assistance Center (TAC) in your region.
Country/Region Phone Number
United States and Canada 1-800-DIAL-WAN (1-800-342-5926) or 1-978-952-7299
United Kingdom 0-800-96-2229
Europe +33-4-9296-5656
Australia +61-3-9656-7000
Japan +81-3-5325-7397
xx12/28/00 Network Management Station Upgrade Guide Beta Draft Confidential
1
Overview
The Network Management Station (NMS) is a dedicated Sun SPARCstation that runs software used to configure, monitor, and control an Lucent switch network. This chapter describes requirements to upgrade to Solaris 2.6, Sybase 11.9.2, and HP OpenView 5.01.
Network Management Station Upgrade Guide 1-1 Beta Draft Confidential Overview Upgrade Requirements
Upgrade Requirements
This section describes: • General requirements • NMS system configuration requirements • Software requirements
General Requirements
See the Network Management Station Installation Guide to back up your Sybase and HP OpenView databases.
NMS System Configuration Requirements
If you plan on migrating to a new hardware platform (see Table 1-1), contact the ! Technical Assistance Center. Do not continue until you contact the TAC. See “Customer Support” on page -xx.
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-3).
1-2 Network Management Station Upgrade Guide Beta Draft Confidential Overview Upgrade 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-ROMdrive •Tapedrive
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-13)
Small Network: System 1: Sun Enterprise 450 4 400 Mhz 4 GB • 9 GB Disk (NavisCore / • 15-60 switches NavisCore / HP OpenView / HP OpenView / • 1-15 users Provisioning Provisioning Server) • 150 LPorts/switch Server / • 200 PVCs/switch Sybase • 9 GB Disk (Sybase)
Medium Network: System 1: Sun Enterprise 3500 6 to 8 8GB • 9 GB Disk (NavisCore / • 61-300 switches NavisCore / 400 Mhz HP OpenView / HP OpenView / • 16-50 users Provisioning Provisioning Server) • 150 LPorts/switch Server / • 200-300 Sybase • 9 GB Disk PVCs/switch (Sybase)
Network Management Station Upgrade Guide 12/28/001-3 Beta Draft Confidential Overview Upgrade 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-14)
Small Network: System 1: Sun Enterprise 250 2 400 Mhz 1 GB • 9 GB Disk • 15-60 switches NavisCore / HP OpenView / • 1-15 users Provisioning • 150 LPorts/switch Server / • 200 PVCs/switch Sybase Open Client
System 2: Sun Enterprise 250 2 400 Mhz 2 GB Each device below requires space on a Sybase separate (9 GB minimum) disk: • 1 GB Data •1GBLog
Medium Network: System 1: Sun Enterprise 450 4400Mhz 4to8 • 9GB Disk • 61-300 switches NavisCore / or Enterprise 3500 GB HP OpenView / • 16-50 users Provisioning • 150 LPorts/switch Server / • 200-300 Sybase Open PVCs/switch Client System 2: Sun Enterprise 450 4 400 Mhz 2 GB Each device below Sybase or Enterprise 3500 requires space on a separate (9 GB minimum) disk: • 2 GB Data •2GBLog
1-4 Network Management Station Upgrade Guide Beta Draft Confidential Overview Upgrade 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 4400Mhz 8GB • 9 GB Disk • 301-700 switches NavisCore / HP OpenView / •51-100users Provisioning • 150 LPorts/switch Server / • 200-300 Sybase Open PVCs/switch Client System 2: Sun Enterprise 4500 6-8 400 8GB • 9 GB Disk Mhz NavisCore / HP OpenView / Provisioning Server / Sybase Open Client
System 3: Sun Enterprise 4500 6-8 400 8GB •6DiskFibre Mhz Array NavisCore / HP OpenView / •(2)9GBDisks: Provisioning NavisCore / Server / Provisioning Sybase Open Server Client • 9 GB Data Disk System 4: Sun Enterprise 4500 8400Mhz 8GB •9GBLogDisk Sybase
Network Management Station Upgrade Guide 12/28/001-5 Beta Draft Confidential Overview Upgrade 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.01.00.00 only. • 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 11.9.2 with less than 512-MB RAM.
1-6 Network Management Station Upgrade Guide Beta Draft Confidential Overview Upgrade 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
Software Requirements
Solaris
Prior to upgrading to Solaris 2.6, your NMS must have: • Solaris 2.5.1, Common Desktop Environment (CDE), and the latest Solaris 2.5.1 cluster patch installed on your system. • 150-MB of free space in /usr.
If your /usr file system has 300-MB of total space (that is, the df -k command output displays 288-MB in the "kbytes" column for /usr), call the Lucent Technical Assistance Center (TAC) to discuss upgrade issues. See “Customer Support” on page -xx. It is important that you consult the TAC because Lucent previously recommended 300-MB of total space for /usr. If you followed this recommendation, 150-MB of space in /usr has not been left free for the Solaris 2.6 upgrade.
Sybase
Prior to upgrading to Sybase 11.9.2, your NMS must have Sybase 11.0.2 or 11.0.3.3, installed on your system.
If you are running Sybase 4.9.2, you must upgrade to Sybase 11.0.2 or 11.0.3.3 using Lucent’s installation scripts, then upgrade to Sybase 11.9.2. In addition, this guide does not provide instructions on installing a remote backup server. If you want to upgrade Sybase 4.9.2 to Sybase 11.0.2 or 11.0.3.3, or install a remote backup server, call the Technical Assistance Center. See “Customer Support” on page -xx.
Network Management Station Upgrade Guide 12/28/001-7 Beta Draft Confidential Overview Upgrade Requirements
Sybase Space
Space requirements depend on your upgrade scenario:
Scenario 1
If you have 490-MB of free space in /opt, note the following: • You need to extract the 258-MB Sybase 11.9.2 tar file from the CD-ROM device to a temporary directory in /opt (for example, /opt/sybase_new). • The next space requirement depends on your Sybase version (11.0.2 or 11.0.3.3): – If you are upgrading from Sybase 11.0.2, then the Sybase 11.0.2 directory is 40-MB. Therefore, you will need an additional 234-MB of free space in /opt/sybase because the Sybase 11.0.2 directory (/opt/sybase) is overwritten by the 258-MB Sybase 11.9.2 file and the 16-MB OpenClient 11.1.1 file. – If you are upgrading from Sybase 11.0.3.3, then the Sybase 11.0.3.3 directory is 184-MB. Therefore you will need an additional 90-MB of free space in /opt/sybase because the Sybase 11.0.3.3 directory (/opt/sybase) is overwritten by the 258-MB Sybase 11.9.2 file and the 16-MB OpenClient 11.1.1 file.
If you have disk space questions, contact the Technical Assistance Center. See “Customer Support” on page -xx.
Scenario 2
If you do not have 490-MB of free space in /opt, note the following: • You need to extract the 258-MB Sybase 11.9.2 tar file to a temporary directory (for example, /usr). • The next space requirement depends on your Sybase version (11.0.2 or 11.0.3.3): – If you are upgrading from Sybase 11.0.2, then the Sybase 11.0.2 directory is 40-MB. Therefore, you will need an additional 234-MB of free space in /opt/sybase because the Sybase 11.0.2 directory (/opt/sybase) is overwritten by the 258-MB Sybase 11.9.2 file and the 16-MB OpenClient 11.1.1 file. – If you are upgrading from Sybase 11.0.3.3, then the Sybase 11.0.3.3 directory is 184-MB. Therefore you will need an additional 90-MB of free space in /opt/sybase because the Sybase 11.0.3.3 directory (/opt/sybase) is overwritten by the 258-MB Sybase 11.9.2 file and the 16-MB OpenClient 11.1.1 file.
If you have disk space questions, contact the Technical Assistance Center. See “Customer Support” on page -xx.
1-8 Network Management Station Upgrade Guide Beta Draft Confidential Overview NMS Software
HP OpenView
Prior to upgrading to HP OpenView 5.01, you must have: • HP OpenView 4.11 installed on your system • 75-MB of free space in /opt
If you are running HP OpenView 3.3.1, you must upgrade to version 4.11 using Lucent’s installation scripts, then upgrade to 5.01. If you want to upgrade HP OpenView 3.3.1 to 4.11, call the Technical Assistance Center. See “Customer Support” on page -xx.
NavisCore
See the latest NavisCore SRN for the NavisCore version that supports the NMS upgrade.
NMS Software
Lucent requires you to upgrade to the following software: • Solaris 2.6 and CDE • Solaris 2.6 Cluster Patch • Sybase 11.9.2 SQL Server • Open Client Version 11.1.1 • HP OpenView Network Node Manager Version 5.01
Solaris Operating System
The Solaris operating system is comprised of the following:
Sun Microsystems SunSoft™ Solaris®2.6 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.
Network Management Station Upgrade Guide 12/28/001-9 Beta Draft Confidential Overview NMS Software
Solaris 2.6 Cluster Patch
Before you install the NMS software programs, obtain the file 2.6_Recommended.tar.Z. There are several versions of this file (Patch.0, Patch.1, Patch.2, Patch.3). Select the latest numerical version.
To get the patch, do one of the following: • Contact Sun at 1-800-USA-4SUN. • Access these files from SunSolve’s website at http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access.
After you install the Solaris operating system, you need to install the patch.
For additional Lucent recommended Solaris patches, see the appropriate NavisCore Software Release Notice (SRN).
Sybase 11.9.2 SQL Server
Sybase 11.9.2 SQL Server is a relational database software program used to store database information and provide backup and recovery of database files.
Sybase versions 11.0.5 and greater are now referred to as Adaptive Server. However, this guide refers to Adaptive Server as Sybase SQL Server.
Open Client, Version 11.1.1
Open Client 11.1.1 is a programming interface that allows transparent access to any data source, information application, or system service.
1-10 Network Management Station Upgrade Guide Beta Draft Confidential Overview NMS Software
HP OpenView Network Node Manager Version 5.01
HP OpenView Network Node Manager (NNM) 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 NNM 5.01: • Manages custom SNMP devices and objects • Performs trap formatting and actions • Performs remote diagnostics and automatic status propagation
HP OpenView Windows is the graphical user interface for Network Node Manager 5.01, which permits extensive customization. This includes the definition of icons, maps, background graphics, symbols, and application representations.
Network Management Station Upgrade Guide 12/28/001-11 Beta Draft Confidential Overview Installation Scripts
Installation Scripts
Lucent provides scripts to install Sybase and HP OpenView.
Sybase
The install_sybase script: • Upgrades Sybase 11.0.2 or 11.0.3.3 to 11.9.2 • Installs the local backup server
If you are upgrading from Sybase 11.0.2, the script first upgrades Sybase to 11.0.3.3, then to 11.9.2
There are two Sybase tar files on the CD-ROM: syb_install.03.xx.xx.xx – Used for Sybase 11.9.2 installations syb_install.02.00.00.00 – Used for Sybase 11.0.3.3 installations When you enter the path for the CD-ROM, the script automatically determines which tar file is used. NOTE: xx.xx.xx is given as the last digits of the Sybase 11.9.2 tar file because the tar file is updated repeatedly. Before starting the upgrade, verify that the CD-ROM contains the Sybase 11.9.2 tar file required by your NavisCore version. The Software Release Notice (SRN) for your NavisCore version describes release-specific Sybase requirements.
HP OpenView
The install_cvux script: • Sets up the system • Upgrades HP OpenView 4.11 to 5.01
1-12 Network Management Station Upgrade Guide Beta Draft Confidential Overview Upgrade Path
Upgrade Path
The following section provides navigation paths to install either a single- or two-system NMS.
Single-System NMS
Table 1-3 provides a navigation path to upgrade NMS software on a single-system NMS: Table 1-3. Single-System Upgrade Path
Action Described In
Upgrade to Solaris 2.6 Chapter 2
Install Solaris 2.6 cluster patches Chapter 2
Prepare for Sybase 11.9.2 upgrade Chapter 3
Upgrade to 11.9.2 Chapter 4
Upgrade to HP OpenView 5.01 Chapter 5
Install HP OpenView patches Chapter 5
Upgrade to NavisCore xx.xx.xx.xx See the Software Release Notice for NavisCore Release xx.xx.xx.xx
Network Management Station Upgrade Guide 12/28/001-13 Beta Draft Confidential Overview Upgrade Path
Two-System NMS
Table 1-4 and Table 1-5 provide navigation paths to upgrade NMS software on a two-system NMS: Table 1-4. Sybase Server Upgrade Path
Action Described In
Upgrade to Solaris 2.6 Chapter 2
Prepare for Sybase 11.9.2 upgrade Chapter 3
Upgrade to Sybase 11.9.2 Chapter 4
Post-installation tasks Chapter 6
Table 1-5. HP OpenView/NavisCore Upgrade Path
Action Described In
Upgrade to Solaris 2.6 Chapter 2
Set up system and upgrade to HP OpenView 5.01 Chapter 5
Upgrade to NavisCore xx.xx.xx.xx See the Software Release Notice for NavisCore Release xx.xx.xx.xx
Post-installation tasks Chapter 6
1-14 Network Management Station Upgrade Guide Beta Draft Confidential
2
Upgrading to Solaris 2.6
Solaris 2.6 is the operating system environment that includes advanced technologies for multithreading, symmetric multiprocessing, integrated TCP/IP-based networking, and centralized network administration tools.
When you upgrade your system, Solaris 2.6 merges with local modifications of the existing system.
This chapter provides procedures for upgrading from Solaris Version 2.5.1 to Solaris 2.6 only. If your Sun workstation is pre-installed with Solaris Version 2.7 or greater, you must replace the existing operating system installation with the Solaris 2.6 software required by the NMS. See the Network Management Station Installation Guide for details on this procedure.
Before You Begin
Prior to upgrading to Solaris 2.6, verify that you have: • At least 150-MB of free space in /usr • Backed up your Sybase and HP OpenView databases
If your /usr file system has 300-MB of total space (that is, the df -k command output displays 288-MB in the "kbytes" column for /usr), call the Lucent Technical Assistance Center to discuss upgrade issues. See “Customer Support” on page -xx. It is important that you consult the Technical Assistance Center because Lucent previously recommended 300-MB of total space for /usr; however, if you followed this recommendation, 150-MB of free space in /usr has not been left free for the Solaris 2.6 upgrade.
Network Management Station Upgrade Guide 2-1 Beta Draft Confidential Upgrading to Solaris 2.6 Upgrading to Solaris 2.6
Do not use Solaris Auto Layout during the Solaris upgrade. !
Do not proceed without saving the Sybase and HP OpenView databases. For ! Sybase backups, see “Backing Up and Verifying Your Databases” on page 3-5, and for HP OpenView backups, see “Backing Up HP OpenView Databases” on page 5-9.Theufsdump command will not preserve the Sybase raw device databases.
Upgrading to Solaris 2.6
To upgrade to Solaris 2.6: 1. Log in as root by entering su - root. When prompted, enter
In this example, the IP address is 152.148.12.105, and the subnet mask is 152.148
Figure 2-1. IP Address and Subnet Mask Window 3. Make a note of the displayed IP address and subnet mask. You will need this information during the upgrade. 4. Save the contents of the /etc/hosts file by entering: cp /etc/hosts /etc/hosts.orig 5. If you are using an external CD-ROM drive, verify that the jumper switch, located on the back of the CD-ROM drive, is set to SCSI ID 6.
2-2 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Solaris 2.6 Upgrading to Solaris 2.6
6. To halt the system, enter: init 0 The system displays the ok prompt. 7. Insert the Solaris 2.6 Software CD into the CD-ROM drive. 8. At the ok prompt, enter: boot cdrom The system boots the operating system from the CD-ROM drive. After several minutes, the system displays the following message: Starting Open Windows... The Solaris logo appears and the Solaris Install Console window displays the following message:
Solaris Install Console The system is coming up. Please wait.
Figure 2-2. Solaris Install Console Window 9. At the Select Language and Locale dialog box, choose Continue. 10. At the Solaris Installation Program dialog box, choose Continue. 11. At the Identify This System dialog box, choose Continue. 12. At the Host Name dialog box, enter
Network Management Station Upgrade Guide 12/28/002-3 Beta Draft Confidential Upgrading to Solaris 2.6 Upgrading to Solaris 2.6
15. At the Confirm Information dialog box, verify the displayed information. If it is correct, choose Continue. To change any information, choose Change. The Solaris Install Console window displays the following message: Starting remote procedure call (RPC) services: sysidnis
Prior to step 16, consult your system administrator for assistance if you are using a name service. Lucent recommends you select None if you are not using a name service.
16. At the Name Service dialog box, select None and choose Continue.
If you are running Network Information Services (NIS), consult your System Administrator.
17. At the Confirm Information dialog box, verify the displayed information. If it is correct, choose Continue. To change any information, choose Change. 18. At the Subnets dialog box, select Yes to make this system part of a subnet. Choose Continue. 19. At the Netmask dialog box, enter
2-4 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Solaris 2.6 Upgrading to Solaris 2.6
The Solaris Install Console window displays several messages. For example:
Solaris Install Console System Identification is completed. Starting Solaris installation program... Executing JumpStart preinstall phase... Searching for SolStart directory... Checking rules.ok file... Using begin script: install_begin Using finish script: patch_finish Executing SolStart preinstall phase... Executing begin script “install_begin”... Begin script install_begin execution completed.
Figure 2-3. Solaris Install Console Window 24. At the Solaris Interactive Installation dialog box, choose Upgrade. 25. At the Select Languages dialog box, select the desired language(s) and choose Add and Continue, or choose Continue to only accept the default (English). The Analyzing System dialog box appears. The Solaris 2.6 software determines whether the system can be upgraded. This includes checking for sufficient disk space (e.g.,150-MBfreespacein/usr). 26. At the Customize Software dialog box, choose Customize. 27. At the Customize Software dialog box (under the Software Clusters and Packages section), unselect JavaVM (a blank gray box indicates JavaVM is unselected). Choose OK. 28. At the Customize Software dialog box, choose Continue.
A warning box may appear discussing “dependency” issues. Choose OK to continue.
29. At the Profile dialog box, verify the profile you created and choose Begin Upgrade. This may take up to two hours. The Upgrading Solaris Software - Progress dialog box appears, indicating the progress of the upgrade. When the upgrade completes, the Upgrading Solaris Software - Progress dialog box displays “Upgrade Complete.”
Network Management Station Upgrade Guide 12/28/002-5 Beta Draft Confidential Upgrading to Solaris 2.6 Upgrading to Solaris 2.6
30. In the Solaris Install Console dialog box, at the # prompt enter init 6 to reboot the system. After system reboot, the following message appears: ************************************************************ This system is configured to conserve energy. After 30 minutes without activity, the system state will be saved to disk and the system will be powered off automatically.
A system that has been suspended in this way can be restored back to exactly where it was by pressing the power key. The definition of inactivity and the timeout are user configurable. The dtpower (1m) man page has more information. ************************************************************ Do you wish to accept this default configuration, allowing your system to save its state then power off automatically when it has been idle for 30 minutes? (If this system is used as a server, answer n. By default autoshutdown is enabled.) [y, n, ?] 31. Enter n. The following message appears: Autoshutdown has been disabled.
Should the system save your answer so it won't need to ask The question again when you next reboot? (By default the Question will not be asked again.) [y, n, ?] n 32. Enter y. The system displays the console login prompt. 33. At the console login prompt, log in as the root user and enter the root password. The system returns a # prompt (the default shell prompt for the root user). 34. When the software prompts you for a windowing system, select either Common Desktop Environment or OpenWindows. Lucent recommends using CDE. 35. Open an Xterm window and enter: eject cdrom 36. Remove the CD-ROM from the CD-ROM drive. 37. Proceed to “Installing the Solaris Cluster Patch” on page 2-7.
2-6 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Solaris 2.6 Installing the Solaris Cluster Patch
Installing the Solaris Cluster Patch
You must install the Solaris 2.6 cluster patch file 2.6_Recommended.tar.Z on your system. There are several versions of the 2.6_Recommended.tar.Z file (Patch.0, Patch.1, Patch.2, Patch.3). Select the latest numerical version.
For additional Lucent recommended Solaris patches, see the appropriate NavisCore Software Release Notice (SRN).
To install the Solaris 2.6 cluster patch: 1. Put the Solaris 2.6 cluster patch file in /tmp. 2. In an Xterm window, enter: cd /tmp uncompress 2.6_Recommended.tar.Z tar xvf 2.6_Recommended.tar 3. When the # prompt appears, enter: cd /tmp/2.6_Recommended/ ./install_cluster After several lines of output, the following message appears: Are you ready to continue with install? [y/n]: 4. Enter y to continue. The installation takes several minutes to complete. 5. When the # prompt appears, enter: init 6 6. Proceed to “Editing the New Solaris 2.6 Inittab File” on page 2-8.
Network Management Station Upgrade Guide 12/28/002-7 Beta Draft Confidential Upgrading to Solaris 2.6 Editing the New Solaris 2.6 Inittab File
Editing the New Solaris 2.6 Inittab File
When you upgrade to Solaris 2.6, Solaris loads a new version of the /etc/inittab file and renames the existing /etc/inittab file. As part of the NavisCore installation, you added a line to the inittab file so that the system would invoke the Lucent tftp daemon to listen to the default tftp port for requests rather than using inetd. You must edit the new version of the inittab file to include the line that invokes the Lucent tftp daemon.
To add the line to inittab: 1. At the Login prompt, enter root. When prompted for root password, enter
You cannot retrieve and display trace and status information if you use Sun ! Microsystem’s tftp daemon. If you use Sun Microsystem’s tftp daemon, configure it to run with the command: in.tftpd/tfpboot.DonotrunTFTPin secure mode (with the -s option) or switch-download and configuration-sync operations will fail. Lucent does not support Sun Microsystem’s tftp daemon on all Lucent switches.
9. Proceed to Chapter 3, “Completing Sybase Prerequisite Tasks.”
2-8 Network Management Station Upgrade Guide Beta Draft Confidential
3
Completing Sybase Prerequisite Tasks
Sybase 11.9.2 SQL Server is a relational database software program used to store database information and provide backup and recovery of database files.
This chapter describes the following procedures that must be completed before upgrading to Sybase 11.9.2: • Check the Sybase version • Complete the Sybase 11.9.2 upgrade worksheet • Log off all Sybase users • Back up your databases • Increase the size of the sybsystemprocs and model databases • Complete the memory consideration task for the NMS and Sybase
Before You Begin
Prior to completing prerequisite tasks, verify that you have: • Installed Sybase 11.0.2 or 11.0.3.3 • Upgraded to Solaris 2.6
Network Management Station Upgrade Guide 3-1 Beta Draft Confidential Completing Sybase Prerequisite Tasks Checking the Sybase Version
Checking the Sybase Version
Lucent supports upgrades from Sybase 11.0.2 or 11.0.3.3.
If you are running an earlier or later version than Sybase 11.0.2 or 11.0.3.3, contact the Technical Assistance Center. See “Customer Support” on page -xx
To check your Sybase version: 1. Log in as Sybase user by entering su - sybase. 2. Enter isql by entering: isql -U sa -P
If the output shows any SQL Server other than 11.0.2 or 11.0.3.3, do not ! proceed. Call the Technical Assistance Center. See “Customer Support” on page -xx.
5. Proceed to “Completing the Sybase Upgrade Worksheet.”
3-2 Network Management Station Upgrade Guide Beta Draft Confidential Completing Sybase Prerequisite Tasks Completing the Sybase Upgrade Worksheet
Completing the Sybase Upgrade Worksheet
Complete the Sybase upgrade worksheet in Appendix C. You will use this information for procedures in other chapters.
Logging Off All Sybase Users
To log off all Sybase users: 1. From the HP OpenView File Menu, choose File Þ Exit to exit NavisCore. 2. Log in as the root user by entering: su - root When prompted, enter
$ showserver UID PID PPID C STIME TTY TIME CMD root 1031 1 0 14:09:03 ? 27:43 /opt/sybase/bin/dataserver -d/dev /rdsk/c0t1d0s0 -e/opt/sybase/install/SERVERNAME_err root 1097 1096 0 14:09:17 ? 0:00 /opt/sybase/bin/backupserver -e/opt/sybase/install/SERVERNAME_bckup_err.log -N25 -C2
Figure 3-1. Showserver Command If the server is not running, proceed to step 8.
Network Management Station Upgrade Guide 12/28/003-3 Beta Draft Confidential Completing Sybase Prerequisite Tasks Logging Off All Sybase Users
6. Logintoisqlbyentering: isql -U sa -P
3-4 Network Management Station Upgrade Guide Beta Draft Confidential Completing Sybase Prerequisite Tasks Backing Up and Verifying Your Databases
Backing Up and Verifying Your Databases
The primary method for backing up your Sybase database is the isql dump command.
You must back up your databases before performing the Sybase 11.9.2 upgrade. This enables you to restore Sybase 11.0.2 or 11.0.3.3, if necessary. In addition, you must verify the integrity of your databases before performing the upgrade.
There are two procedures for backing up your databases: • Ifthisisyourfirst database backup, follow the instructions in “First-time Backup to the Local Backup Server.”
Your first database backup should have been performed already since this is an upgrade.
• If this is not your first backup, follow the instructions in “Subsequent Backups to the Local Backup Server.”
Lucent recommends customers periodically test the integrity of Sybase and HP OpenView backups by loading the backups on a separate test Sun SPARCstation.
First-time Backup to the Local Backup Server
To back up the Sybase 11.0.2 or 11.0.3.3 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 Open- View/NavisCore on another), log on to either server workstation. 2. Create a backup directory by entering: mkdir backup 3. Enter the following command: script /opt/sybase/backup/sybck.out The script command saves any database output from the dbcc checkdb command (step 5) and places it in the sybck.out file. In addition, output is displayed on screen.
Network Management Station Upgrade Guide 12/28/003-5 Beta Draft Confidential Completing Sybase Prerequisite Tasks Backing Up and Verifying Your Databases
4. Initiate an isql session by entering: isql -U sa -P
If you encounter errors when you perform the dbcc checkdb command, do not proceed any further and call the Technical Assistance Center. See “Customer Support” on page -xx.
3-6 Network Management Station Upgrade Guide Beta Draft Confidential Completing Sybase Prerequisite Tasks Backing Up and Verifying Your Databases
6. Press
For example, superbase. 9. If there are no dbcc errors, save the master and cascview databases by entering: 1> dump database master to "/opt/sybase/backup/masterbackup.
When you perform backups via the dump command, make sure you copy the backup files to tape or ftp the backup files to another SPARCstation.
10. Proceed to “Increasing the Size of the sybsystemprocs and model Databases” on page 3-11.
Network Management Station Upgrade Guide 12/28/003-7 Beta Draft Confidential Completing Sybase Prerequisite Tasks Backing Up and Verifying Your Databases
Subsequent Backups to the Local Backup Server
Use these steps to back up the Sybase 11 Server to the Local Backup Server on a daily basis.
The Lucent Technical Assistance Center strongly recommends that you back up the Sybase Server daily.
1. Log in as the Sybase user by entering: su - sybase If you have a two-system configuration (Sybase on one workstation, HP/Navis- Core on another), log on to either server workstation. 2. Enter: 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
3-8 Network Management Station Upgrade Guide Beta Draft Confidential Completing Sybase Prerequisite Tasks Backing Up and Verifying Your Databases
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 and call the Technical Assistance Center. See “Customer Support” on page -xx.
5. Press
When you perform backups via the dump command, make sure you copy the backup files to tape or ftp the backup files to another SPARCstation.
Network Management Station Upgrade Guide 12/28/003-9 Beta Draft Confidential Completing Sybase Prerequisite Tasks Backing Up and Verifying Your Databases
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
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 3-2. Bulk Copy Output A file called CVCOPY_cascview_data.tar is created in the /opt/sybase/backups/storedb directory.
When you perform backups via the bulk copy command, make sure you copy the backup files to tape or ftp the backup files to another SPARCstation.
12. Proceed to “Increasing the Size of the sybsystemprocs and model Databases” on page 3-11.
3-10 Network Management Station Upgrade Guide Beta Draft Confidential Completing Sybase Prerequisite Tasks Increasing the Size of the sybsystemprocs and model Databases
Increasing the Size of the sybsystemprocs and model Databases
The sybsystemprocs device sysprocsdev (default system name) stores the sybsystemprocs database. The sybsystemprocs database must be at least 100-MB. Before you upgrade to Sybase 11.9.2, use the following procedures to determine if you need to increase the size of the sybsystemprocs database. 1. Log in as Sybase user by entering: su - sybase 2. Enter isql by entering: isql -U sa -P
This is the most common path because Lucent previously set recommendations for sysprocsdev at 25-MB.
•Ifthesysprocsdev device from the sp_helpdevice command is 100MB or greater, increase the size of sybsystemprocs database to 100-MB using the alter database command:
1> use master 2> go
1> alter database sybsystemprocs on sysprocsdev = x
where x is the number that brings sybsystemprocs to 100-MB.
2> go
Network Management Station Upgrade Guide 12/28/003-11 Beta Draft Confidential Completing Sybase Prerequisite Tasks Increasing the Size of the sybsystemprocs and model Databases
5. Do one of the following: •Ifsysprocsdev is 100-MB, proceed to step 16 on page 3-14. •Ifsysprocsdev is not 100-MB, proceed to step 6 to drop the device and re-add it.
Dropping the sysprocs device and re-adding it removes all stored procedures you createdatyoursite.Beforeyoudropthedeviceandre-additinstep 6, back up your stored procedures or relocate them to a safe storage area using the defncopy utility. For assistance on this procedure, call the Technical Assistance Center. See “Customer Support” on page -xx. If you did not create your own stored procedures, proceed to step 6.
6. Run the following commands to retrieve and save the physical_name and device_number of sysprocsdev by entering: 1> sp_helpdb sybsystemprocs 2> go 1> sp_helpdevice 2> go
You need the device number “vdveno” for step 12 when you recreate the sysprocs device.
7. Drop the existing sybsystemprocs database and use the name you assigned to sysprocsdev.Enter: 1> sp_configure “allow update”, 1 2> go 1> reconfigure with override 2> go 1> use master 2> go 1> drop database sybsystemprocs 2> go 1> begin transaction 2> delete from sysdevices 3> where name = “sysprocsdev” 4> go
3-12 Network Management Station Upgrade Guide Beta Draft Confidential Completing Sybase Prerequisite Tasks Increasing the Size of the sybsystemprocs and model Databases
8. Do one of the following:
If you make a typographical error in step 7 on page 3-12, roll back the transaction using the procedures in the second bullet in step 8 and repeat step 7 without making any errors.
• If the commands in step 7 affect one row, then commit the transaction by entering: 1> commit transaction 2> go Proceed to step 9. • If the commands in step 7 affect more than one row, roll back the transaction by entering: 1> rollback transaction 2> go Do not proceed any further and call the Technical Assistance Center. See “Customer Support” on page -xx. 9. Shut down the Sybase Server: 1> shutdown 2> go 1> quit 10. If your sysprocsdev device was a UNIX file, delete it. 11. Restart the Sybase 11 Server by entering either: • startserver -f RUN_SERVERNAME & SERVERNAME is the DSQUERY value, which you can find in the following file: /opt/sybase/interfaces • RUN_
Network Management Station Upgrade Guide 12/28/003-13 Beta Draft Confidential Completing Sybase Prerequisite Tasks Increasing the Size of the sybsystemprocs and model Databases
12. Find another device that has 100-MB. This requires you to format a slice on a disk as a raw partition: isql -U sa -P
3-14 Network Management Station Upgrade Guide Beta Draft Confidential Completing Sybase Prerequisite Tasks Memory Considerations for the NMS and Sybase
Memory Considerations for the NMS and Sybase
This section explains: • Three memory types (Physical Memory, Shared Memory,andSybase Total Memory) • How to determine the value of each memory type • How to change the value of each memory type (if necessary)
The Sybase installation script for new Sybase 11.9.2 installations automatically resets: • NMS shared memory to half the NMS physical memory • Sybase “total memory” to half the NMS shared memory
The Sybase upgrade script does not do this for upgrades to Sybase 11.9.2. The script only saves the existing Sybase memory values and restores them after the upgrade. Therefore, customers must follow the following steps to ensure that the physical, shared, and Sybase total memory values are set properly.
See for Chapter 1, “Overview,” for additional system configuration specifications required for optimal performance.
Network Management Station Upgrade Guide 12/28/003-15 Beta Draft Confidential Completing Sybase Prerequisite Tasks Memory Considerations for the NMS and Sybase
Physical Memory
To determine the physical memory (RAM) on the NMS: 1. Log in as Sybase user by entering: su - sybase 2. At the $ prompt, enter: /usr/bin/dmesg | grep -i mem The following messages appear: mem = 524288K (0x20000000) avail mem = 517750784 mem = 524288K (0x20000000) avail mem = 517750784 mem = 524288K (0x20000000) avail mem = 517750784 mem = 524288K (0x20000000) avail mem = 517750784 There may be several “avail mem” and “mem” entries; however these are duplicates. In the step 2 example, physical memory (“mem”) is 524288K or 512-MB (524288000 / 1024).
Adding Physical Memory
Lucent supports 512-MB as the minimum physical memory for Sybase 11.9.2 installations and upgrades.
To determine the correct physical memory for your specific environment and number of users, call the Technical Assistance Center. (See “Customer Support” on page -xx.) If physical memory is too low, add additional RAM.
3-16 Network Management Station Upgrade Guide Beta Draft Confidential Completing Sybase Prerequisite Tasks Memory Considerations for the NMS and Sybase
Shared Memory
The "shmsys:shminfo_shmmax" parameter in the /etc/system file determines shared memory. SPARC shared memory should be half of physical memory. Using the Physical Memory example in step 2, since physical memory is 512-MB, the "shmsys:shminfo_shmmax" parameter should be 256 (262144000 bytes).
To determine shared memory: 1. Log in as Sybase user by entering: su - sybase 2. Enter: tail /etc/system The following messages appear: set semsys:seminfo_semaem=16384 set semsys:seminfo_semmap=66 set semsys:seminfo_semmni=70 set semsys:seminfo_semmns=200 set semsys:seminfo_semmnu=30 set semsys:seminfo_semume=10 set semsys:seminfo_semvmx=32767 set shmsys:shminfo_shmmax=262144000 set shmsys:shminfo_shmseg=6 The bold line indicates shared memory.
Changing Shared Memory
To change the shared memory value, open the /etc/system file using the vi text editor and change the "shmsys:shminfo_shmmax" parameter to half of physical memory. The /etc/system file is read-only during system boot. Therefore, if you change the "shmsys:shminfo_shmmax" parameter, reboot the system (init 6) for the parameter to take effect.
Network Management Station Upgrade Guide 12/28/003-17 Beta Draft Confidential Completing Sybase Prerequisite Tasks Memory Considerations for the NMS and Sybase
Sybase Total Memory
Sybase total memory should be half of the shared memory value or one quarter of the physical memory.
To check the Sybase “total memory” value: 1. Log in as the Sybase user by entering: su - sybase 2. Determine the DSQUERY variable by entering: env | grep DSQUERY For example, the following appears: DSQUERY=CASCADE 3. Determine Sybase total memory by entering: grep -i "total memory"
The following appears: total memory = XXXXXX For example, using CASCADE as the DSQUERY name: grep -i "total memory" CASCADE.cfg The following appears: total memory = 64000
The value of Sybase “total memory” is in 2K pages. For the example of 64000 2K pages, Sybase total memory is 128-MB or 64000 x 2048 = 131072000 bytes.
Changing Sybase Total Memory
To change Sybase total memory: 1. Vi the /opt/sybase/
3-18 Network Management Station Upgrade Guide Beta Draft Confidential Completing Sybase Prerequisite Tasks Memory Considerations for the NMS and Sybase
3. Shut down the Sybase Server by entering: /etc/rc0.d/K01sybase The following messages appear: Server SHUTDOWN by request. The SQL Server is terminating this process. DB-LIBRARY error: Unexpected EOF from SQL Server. 4. Restart the Sybase Server by entering: /etc/rc2.d/S97sybase The following messages appear: 00:00/02/05 22:28:23.40 kernel Using config area from primary master device. 00:00/02/05 22:28:24.14 kernel Using 1024 file descriptors. 00:00/02/05 22:28:24.14 kernel SQL Server/11.0.2/P/Sun_svr4/OS 5.4/1/OPT/Tue Sep 10 14:03:23 PDT 1996 . . . 00:00/02/05 22:28:47.73 server SQL Server's default sort order is: 00:00/02/05 22:28:47.73 server 'bin_iso_1' (ID = 50) 00:00/02/05 22:28:47.73 server on top of default character set: 00:00/02/05 22:28:47.73 server 'iso_1' (ID = 1). 5. Proceed to Chapter 4, “Upgrading to Sybase 11.9.2.”.
Network Management Station Upgrade Guide 12/28/003-19 Beta Draft Confidential Completing Sybase Prerequisite Tasks Memory Considerations for the NMS and Sybase
3-20 Network Management Station Upgrade Guide Beta Draft Confidential
4
Upgrading to Sybase 11.9.2
This chapter describes how to: • Upgrade to Sybase 11.9.2 • Extract OpenClient 11.1.1 • Back up your databases
Before You Begin
Verify that you have completed the prerequisite tasks described in Chapter 3.
Network Management Station Upgrade Guide 4-1 Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
Running the Upgrade Script
The upgrade script: • Installs the Sybase 11.9.2 software on the system. • Converts Sybase 11.0.2 or 11.0.3.3 databases to Sybase 11.9.2 format. • Upgrades local backup server.
To run the upgrade script: 1. Log in as root by entering: su - root When prompted, enter
There are two Sybase tar files on the CD-ROM: syb_install.03.xx.xx.xx – Used for Sybase 11.9.2 installations syb_install.02.00.00.00 – Used for Sybase 11.0.3.3 installations Use the syb_install.03.xx.xx.xx tar file. NOTE: xx.xx.xx is given as the last digits of the tar file because the tar file is updated repeatedly. Before proceeding with the upgrade, verify that the CD-ROM contains the Sybase 11.9.2 tar file required by your NavisCore version. The SRN for your NavisCore version describes release-specific Sybase requirements.
4-2 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
During the extraction, the following messages appear: x cv_scripts, 0 bytes, 0 tape blocks x cv_scripts/common_sh, 41280 bytes, 81 tape blocks x cv_scripts/install_sybase, 72046 bytes, 141 tape blocks x cv_scripts/new.rs, 4221 bytes, 9 tape blocks x cv_scripts/upgrade.rs, 4121 bytes, 9 tape blocks x cv_scripts/bsrv.rs, 2202 bytes, 5 tape blocks x cv_scripts/README, 11060 bytes, 22 tape blocks x cv_scripts/setup-syb.hlp, 3297 bytes, 7 tape blocks x cv_scripts/check_sys, 10187 bytes, 20 tape blocks x cv_scripts/sp_chk_space1.scr, 1874 bytes, 4 tape blocks x cv_scripts/sp_chk_space2.scr, 5045 bytes, 10 tape blocks x cv_scripts/sp_devinfo, 12540 bytes, 25 tape blocks x cv_scripts/sql_server.sql, 173092 bytes, 339 tape blocks 5. After the extraction completes, change to the cv_scripts directory by entering: cd /opt/cv_scripts 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 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)?
Network Management Station Upgrade Guide 12/28/004-3 Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
8. Press Return or enter
[Press^Ctoabort...]
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. Help... 7. Exit
Please select one of the above options [1-7]?
Figure 4-1. Sybase Installation Menu 9. At the Sybase Installation Menu, enter 3. The following message appears: Complete all upgrade prerequisites before continuing. See Sybase Upgrade Documentation. Do you wish to continue?
See Appendix C, “Sybase Worksheet,” to complete step 11 through step 16.
4-4 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
11. At the “Enter the Old Sybase release path (default=/opt/sybase)” prompt, do one of the following: • Press Return to accept the default of /opt/sybase. •Enter
The /opt/sybase_new directory is a temporary directory. The script copies this directory over the existing Sybase directory when the upgrade completes.
13. At the “Enter the Database Server Name (default=
The script checks if CASCADE is in the interfaces file. If it is, the script uses CASCADE as the database server name. If it is not, the script uses the hostname of your system as the database server name.
14. At the “Enter the name for the error log (default=
Network Management Station Upgrade Guide 12/28/004-5 Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
Table 4-1. Scenario 1 for TCP Socket Configuration
Message Action
If the script locates the TCP socket number in a. Verify the TCP socket number is /etc/services, it displays the following message: correct and press Return. Setting TCP Socket device for Sybase b. Proceed to page 4-7. ------The Socket Number for SYBASE is 1025 The Socket Number for SYBASE BACKUP is 1026 Do you wish to continue?
Table 4-2. Scenario 2 for TCP Socket Configuration
Message Action
If the script locates the TCP number in the Sybase interfaces a. Enter: file, it displays the message:
After you enter the TCP socket number, the script enters it b. Verify the TCP socket number is in the /etc/services file. The following message appears: correct and press Return. Setting TCP Socket device for Sybase ------c. Proceed to page 4-7. The Socket Number for SYBASE is 1025 The Socket Number for SYBASE BACKUP is 1026 Do you wish to continue?
The TCP socket numbers for Sybase and Backup server in Table 4-1 and Table 4-2 are examples.
4-6 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
After performing the appropriate step, the following message appears: Getting the Master Device currently being upgraded ------The script searches for the partition on which the Master device is mounted. If it cannot locate the Master device, the script prompts you for the correct path.
Your Master Partition Device may be different than the following example.
The system displays the following: Searching...... Found. Master Partition Device=/dev/rdsk/c1t0d0s0 Do you wish to continue?
Network Management Station Upgrade Guide 12/28/004-7 Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
The system displays the parameters you entered (Figure 4-2): Sybase Upgrade Installation Parameters *************************************
Parameter Value ********* *************************
0. Done Editing
1. SYBASE /opt/sybase_new
1a. SYBASEOLD /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_new/install/CENTRAL_error.log
9. SYB_MASTER_Dev /dev/rdsk/c0t1d0s0
10. SYB_Procs /dev/rdsk/c0t1d0s4
11. SYB_Procs_Size 100
Enter the number of the parameter you wish to alter Figure 4-2. Sybase Upgrade Parameters
4-8 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
19. Verify that all parameters are correct. If you need to make any changes, enter the parameter number and make the appropriate changes. 20. Once you have made your changes, enter 0 and press Return to continue. The following message appears: Supply the directory only, the script will find the tar file. What is the path of the sybase tar file (default = ‘/cdrom/cdrom0’)?
There are two Sybase tar files on the CD-ROM: syb_install.03.xx.xx.xx – Used for Sybase 11.9.2 installations syb_install.02.00.00.00 – Used for Sybase 11.0.3.3 installations When you enter the path for the CD-ROM, the script automatically determines which tar file is used.
21. Press Return to accept the default /cdrom/cdrom0.
When the upgrade begins, do not interrupt it. The upgrade time varies according ! to your databases sizes. Call the Lucent Technical Assistance Center. See “Customer Support” on page -xx.
Network Management Station Upgrade Guide 12/28/004-9 Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
The following output displays an example of an upgrade from Sybase 11.0.2. The script upgrades to version 11.0.3.3, then to version 11.9.2. If you are upgrading from Sybase 11.0.3.3, the script upgrades directly to version 11.9.2; therefore, you will receive different installation messages from those shown in the following example:
You may see the following error messages. Disregard them and continue with the upgrade. Adaptive Server message 7948, state 1, severity 16: Page 214911, object 8, index 0, level 0, was found with fixed-row status improperly set. That status has been cleared by DBCC. Adaptive Server message 7948, state 1, severity 16: Page 214912, object 8, index 0, level 0, was found with fixed-row status improperly set. That status has been cleared by DBCC. Adaptive Server message 7948, state 1, severity 16: Page 214913, object 8, index 0, level 0, was found with fixed-row status improperly set. That status has been cleared by DBCC. Adaptive Server message 7948, state 1, severity 16: Page 214914, object 8, index 0, level 0, was found with fixed-row status improperly set. That status has been cleared by DBCC. Adaptive Server message 7948, state 1, severity 16: Page 214915, object 8, index 0, level 0, was found with fixed-row status improperly set. That status has been cleared by DBCC. DB-LIBRARY error: 20018 General SQL Server error: Check messages from the SQL Server.
Your version of sybase is 11.0.2.x, so the scripts need to upgrade sybase to 11.0.3.3 before upgrading to 11.9.2 Extracting /cdrom/cdrom0/syb_install.02.00.00.00 into /opt/sybase_new ...Done. Running 'sybinit' and creating the sybase server...Install Sybase Successful... Applying 11.0.3.3 sybase patch Running installmaster Running instmsgs.ebf Running upgrade_1103x.sql Shutting down servers and restarting Shutting down the Sybase Server temporarily. Relocating the New Sybase Media to /opt/sybase...... Done Successfully. Restarting Sybase Server. Extracting /cdrom/cdrom0/syb_install.03.xx.xx.xx into /opt/sybase_new ...Done. Running 'sqlupgraderes' and creating the sybase server.../opt/sybase_new/bin/sqlupgraderes: Checking for Total Memory configured... /opt/sybase_new/bin/sqlupgraderes: The Total Memory Check for the server passed. /opt/sybase_new/bin/sqlupgraderes: Checking for free space in each database... /opt/sybase_new/bin/sqlupgraderes: Database free space checks passed. /opt/sybase_new/bin/sqlupgraderes: Checking database status... /opt/sybase_new/bin/sqlupgraderes: Database status checks passed. /opt/sybase_new/bin/sqlupgraderes: Checking reserved words in each database... /opt/sybase_new/bin/sqlupgraderes: No reserved word conflicts were found. /opt/sybase_new/bin/sqlupgraderes: Checkpointing all databases...
4-10 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
The following messages appear:
/opt/sybase_new/bin/sqlupgraderes: All databases have been checkpointed. /opt/sybase_new/bin/sqlupgraderes: Copying interfaces file entry to new directory... /opt/sybase_new/bin/sqlupgraderes: The interfaces file entry has been copied to the new directory. /opt/sybase_new/bin/sqlupgraderes: Copying configuration file to new directory... /opt/sybase_new/bin/sqlupgraderes: The configuration file has been copied to the new directory. /opt/sybase_new/bin/sqlupgraderes: Updating RUN_SERVER file... /opt/sybase_new/bin/sqlupgraderes: The RUN_SERVER file has been updated. /opt/sybase_new/bin/sqlupgraderes: Doing pre-upgrade modifications... /opt/sybase_new/bin/sqlupgraderes: Pre-upgrade modifications succeeded. /opt/sybase_new/bin/sqlupgraderes: Restarting Adaptive Server.... /opt/sybase_new/bin/sqlupgraderes: Adaptive Server has been restarted. /opt/sybase_new/bin/sqlupgraderes: Running upgrade program... /opt/sybase_new/bin/sqlupgraderes: The upgrade program has completed successfully. /opt/sybase_new/bin/sqlupgraderes: Restarting Adaptive Server.... /opt/sybase_new/bin/sqlupgraderes: Adaptive Server has been restarted. /opt/sybase_new/bin/sqlupgraderes: Running installmaster script... /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 10% complete. /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 20% complete. /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 30% complete. /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 40% complete. /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 50% complete. /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 60% complete. /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 70% complete. /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 80% complete. /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 90% complete. /opt/sybase_new/bin/sqlupgraderes: /opt/sybase_new/scripts/installmaster: 100% complete.
Network Management Station Upgrade Guide 12/28/004-11 Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
The following messages appear:
/opt/sybase_new/bin/sqlupgraderes: The installmaster script has been successfully installed. /opt/sybase_new/bin/sqlupgraderes: Installing common character sets (Code Page 437, Code Page 850, ISO Latin-1, Macintosh and HP Roman-8)... /opt/sybase_new/bin/sqlupgraderes: Character sets installed. Install Sybase Successful... Increasing the Memory allocations to 28672 for improved performance ... Shutting down the Sybase Server temporarily. Relocating the New Sybase Media to /opt/sybase...... Done Successfully.
The Lucent script increases memory allocation to allow basic 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 Sybase SQL Server Installation and Configuration Guide.
The following messages appear:
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 to increase the total connections above 150 then enter the number of connections you require. Enter the number of user connections [default=150] ? 22. Do one of the following: • Press Return to accept the default of 150. •Enter
4-12 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
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 ------Done... Please wait... Restarting Server with increased options Shutting down the Sybase Server temporarily. Relocating the New Sybase Media to /opt/sybase...... Done Successfully. Restarting Sybase Server. Upgrading the Backup Server *************************** Backup Server/11.9.2/1032/P/Sun_svr4/OS 5.5.1/OPT/Thu Aug 13 22:10:45 1998 Confidential property of Sybase, Inc. Copyright 1987, 1998 Sybase, Inc. All rights reserved. Unpublished rights reserved under U.S. copyright laws. This software contains confidential and trade secret information of Sybase, Inc. Use, duplication or disclosure of the software and documentation by the U.S. Government is subject to restrictions set forth in a license agreement between the Government and Sybase, Inc. or other written agreement specifying the Government's rights to use the software and any applicable FAR provisions, for example, FAR 52.227-19. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608, USA Logging Backup Server messages in file '/opt/sybase/install/CENTRAL_bckup_err.log' The Upgrade is completed. You should also do new backups for this release of Backup Server. Press Return to Continue ...
When the upgrade completes, the script copies the new Sybase directory over the old one.
Network Management Station Upgrade Guide 12/28/004-13 Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
23. Press Return. The Sybase Installation Menu appears. 24. At the Sybase Installation Menu, enter 7 to exit. 25. To close the Tail window, with the cursor in the window, hold down
See the latest Software Release Notice (SRN) for Sybase 11.9.2 to verify the correct Sybase SWR patch release number.
29. Delete the /opt/sybase/syb1133.tar file by entering: rm /opt/sybasesyb1133.tar 30. Proceed to “Extracting OpenClient 11.1.1” on page 4-15.
4-14 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Running the Upgrade Script
Extracting OpenClient 11.1.1
If you install Sybase 11.9.2 in a single-system NMS configuration, you now need to extract the Open Client 11.1.1 tar file in the /opt/sybase file system using the following procedure. Open Client 11.1.1 corrects a problem with the bulk copy command.
If you installed Sybase 11.9.2 in a two-NMS configuration, do not perform these procedures. The guide prompts you to in Chapter 6, “Installing a Two-System Configuration.” 1. Log in as Sybase user by entering: su - sybase 2. Put the OpenClient 11.1.1 CD-ROM in the CD-ROM drive. 3. Change to the /opt/sybase directory by entering: cd /opt/sybase 4. Extract Open Client 11.1.1 by entering: tar xvf /cdrom/cdrom0/
Network Management Station Upgrade Guide 12/28/004-15 Beta Draft Confidential Upgrading to Sybase 11.9.2 Backup Procedures
Backup Procedures
This section describes how to: • Back up the Sybase 11.9.2 Server to the Local Backup Server the first time • Perform subsequent Sybase 11.9.2 backups to the Local Backup Server • Save Sybase 11.9.2 database to tape • Change the SA password
The Technical Assistance Center recommends that you perform daily backups of the Sybase 11.9.2 Server. For more information on Sybase 11.9.2 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 “Customer Support” on page -xx.
Lucent recommends customers periodically test the integrity of Sybase and HP OpenView backups by loading the backups on a separate test SPARC workstation.
You can script the backup procedures to perform backups automatically. However, Lucent does not provide these scripts. These scripts are left to the customer’s discretion.
4-16 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Backup Procedures
First-time Backup to the Local Backup Server
To back up the Sybase 11.9.2 Server to the Local Backup Server the first time: 1. Log in as Sybase user by entering: su - sybase If you have a two-system configuration (Sybase on one workstation, HP Open- View/NavisCore on another) log on to either server workstation. 2. Create a backup directory by entering: mkdir backup 3. Enter the following command: script /opt/sybase/backup/sybck.out The script command saves any database output from the dbcc checkdb command (step 5) and places it in the sybck.out file. In addition, output is displayed on screen. 4. Initiate an isql session by entering: isql -U sa -P
Network Management Station Upgrade Guide 12/28/004-17 Beta Draft Confidential Upgrading to Sybase 11.9.2 Backup Procedures
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 “Customer Support” on page -xx.
6. Press
4-18 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Backup Procedures
Subsequent Backups to the Local Backup Server
Use these steps to back up the Sybase 11.9.2 Server to the Local Backup Server on a daily basis.
The Lucent Technical Assistance Center strongly recommends that you back up the Sybase Server daily.
1. Log in as Sybase user by entering: su - sybase If you have a two-system configuration (Sybase on one workstation, HP/Navis- Core 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
Network Management Station Upgrade Guide 12/28/004-19 Beta Draft Confidential Upgrading to Sybase 11.9.2 Backup Procedures
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 “Customer Support” on page -xx.
5. Press
4-20 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to Sybase 11.9.2 Backup Procedures
Figure 4-3 shows some 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 4-3. Bulk Copy Output A file called CVCOPY_cascview_data.tar is created in the /opt/sybase/backups/storedb directory.
Saving Sybase 11.9.2 Databases to Tape
To back up the Sybase 11.9.2 databases to tape: 1. Back up the /opt/sybase/backup directory to tape. For example, as the root user, enter: tar cvf /dev/rmt/0 /opt/sybase/backup If you have a two-system configuration (Sybase on one workstation, HP and NavisCore on another), you must log on to the HP/NavisCore workstation to save the Sybase and HP OV databases to tape.
The Technical Assistance Center recommends that you back up your database daily. The preceding steps create multiple backups because the date extension changes daily. Keep at least one week’s work of database backups.
Network Management Station Upgrade Guide 12/28/004-21 Beta Draft Confidential Upgrading to Sybase 11.9.2 Backup Procedures
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
When prompted, enter
Do not forget the SA password. 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).
4. Log in as root by entering su - root. When prompted, enter
4-22 Network Management Station Upgrade Guide Beta Draft Confidential
5
Upgrading to HP OpenView 5.01
Lucent provides an installation script (install_cvux) that upgrades HP OpenView 4.11 to 5.01.
Before You Begin
Before upgrading to HP OpenView 5.01, verify that you have: • Installed HP OpenView 4.11 • Upgraded to Solaris 2.6 • Installed Sybase 11.9.2
Network Management Station Upgrade Guide 5-1 Beta Draft Confidential Upgrading to HP OpenView 5.01 Upgrading to HP OpenView 5.01
Upgrading to HP OpenView 5.01
This section describes how to: • Load the Lucent-supplied HP OpenView media • Extract the installation script from the media • Run the installation script •Verify/opt file system has 75-MB of free space
You do not have to run HP OpenView 4.11 when you upgrade to version 5.01.
To set up the system: 1. Verify 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
5-2 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to HP OpenView 5.01 Upgrading to HP OpenView 5.01
The NavisCore/UX Installation Menu appears.
[Press^Ctoabort...] 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 5. At the NavisCore/UX Installation Menu, enter 1 to view the HP OpenView Installation Menu. The HP OpenView Installation Menu appears.
[Press^Ctoabort...]
HP OpenView Installation Menu...
1. Install HP OpenView 4.11 or 5.01 2. Upgrade HP OpenView 3.3.1 to 4.11 3. Upgrade HP OpenView 4.11 to 5.01 4. Re-Enable IP Discovery Mechanism 4.11 or 5.01 (Unsupported) 5. Disable IP Discovery Mechanism 4.11 or 5.01 6. Install Latest HP OpenView Patches (as of this release) 7. Return to Main Menu
Please select one of the above options [1-7]?
Figure 5-2. HP OpenView Installation Menu
Network Management Station Upgrade Guide 12/28/005-3 Beta Draft Confidential Upgrading to HP OpenView 5.01 Upgrading to HP OpenView 5.01
6. At the HP OpenView Installation Menu, enter 3 to set up the system for upgrade. 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. 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
5-4 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to HP OpenView 5.01 Upgrading to HP OpenView 5.01
12. Enter 1. The following message appears: You could have purchased either the full or entry NNM product. Look at the product name on the Entitlement Certificate or the Update Letter that was shipped to you with NNM to determine which of the products to choose. 1) Network Node Manager Full product 2) Network Node Manager 250 product Enter the number corresponding to the product you purchased: 13. Enter 1 or 2. The following message appears: Do you want to install the manpages? (y|n): 14. Enter y or n. The following message appears: Do you want to install printable manuals (y|n): 15. Enter y or n. The following messages appear:
This installation will put the following software on your system: HP OpenView Network Node Manager entry product for Solaris 2.x HP OpenView Network Node Manager man pages Emanate SNMP Simple Agent Emanate SNMP Simple Agent Man Pages HP OpenView Network Node Manager printable English manuals There are many factors that can affect the amount of time this installation could take. However, it averages around 30 to 45 minutes. Do you want to continue with this installation? (y|n) :
Figure 5-3. Installation Messages
Network Management Station Upgrade Guide 12/28/005-5 Beta Draft Confidential Upgrading to HP OpenView 5.01 Upgrading to HP OpenView 5.01
16. Enter y to continue. The installation process takes approximately 30 to 45 minutes. The following messages appear during the upgrade:
The installation should complete without further interaction. WARNING: do NOT use the kill command or Control-C to get out of this installation because that could leave your system in a corrupt state. 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 Notes and warnings will be written to this log as well as indications of the installation's progress. ======09/28/98 14:18:36 EDT BEGIN swinstall SESSION (setup mode) * Target connection succeeded for "/". * Analysis phase succeeded for "/". ERROR: Execution phase for "/" had errors.
* More information may be found in the agent logfile (location is /var/adm/sw/swagent.log).
======09/28/98 14:33:00 EDT END swinstall SESSION (setup mode)
********************************************************* * Errors have been encountered in your installation. * * * For details, review * Please look at the log file (/var/adm/sw/swagent.log)* the installation log. * for more information. You will need to look at the * * last session in that file. Each session is marked * * with the starting date and time. * *********************************************************
Hit the Return Key to Continue...
During the installation, the Tail and Xterm installation windows display error messages. For example, in the Tail window:
ERROR: OV - move_files: cpio failed ERROR: OV - move_files: cpio failed
You can ignore the cpio error(s) because these errors are caused by the HP OpenView 5.01 installation/upgrade process not being aware of the custom directory locations Lucent used for the HP OpenView 4.11 installation. The upgrade to HP OpenView 5.01 will complete successfully regardless of the error messages. To see the exact error messages, see Appendix B, “HP OpenView 5.01 Upgrade Error Messages.”
5-6 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to HP OpenView 5.01 Upgrading to HP OpenView 5.01
17. When the upgrade completes, review the installation log for details (/var/adm/sw/swagent). 18. At the Hit Return to Continue prompt, press Return. The following message appears: HP Openview Network Node Manager Configuration ********************************************** Setting up Symbolic Links...... Done.
DisablingIPDiscovery
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 A, “IP Discovery” for information about this feature.
Lucent does not support IP Discovery. Enabling this feature severely affects the ! performance of your NMS Server.
The screen displays the following messages: 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. Starting the HP OpenView object database...Done. Processing field registration entries...Done. Do you wish to continue?
Network Management Station Upgrade Guide 12/28/005-7 Beta Draft Confidential Upgrading to HP OpenView 5.01 Upgrading to HP OpenView 5.01
Verifying the HP OpenView Installation
The upgrade successfully completes when you see the HP OpenView window, Event Categories window, and NavisCore icon as shown in Figure 5-4.
Figure 5-4. HP OpenView 5.01 Window
Complete the installation by performing the following steps: 1. Exit the HP OpenView window and Event Categories window by selecting Map Þ Exit. 2. At the OpenView windows WARNING dialog box, choose OK. The HP OpenView window and Event Categories window disappears. 3. At the HP OpenView Installation Menu, enter 7 to exit. 4. At the NavisCore/UX Installation Menu, enter 4 to exit. The following message appears: Cleaning up temporary files...... Done. Exiting Installation script.
5-8 Network Management Station Upgrade Guide Beta Draft Confidential Upgrading to HP OpenView 5.01 Backing Up HP OpenView Databases
5. To close the Tail window, with the cursor in the window, hold down
The HP OpenView installation is not complete. You must install mandatory HP ! OpenView patches. See the latest Software Release Notice for HP OpenView 5.01 for information on obtaining and installing mandatory patches.
Backing Up HP OpenView Databases
To back up HP OpenView databases by saving the /opt/OV/databases/openview directory: 1. InanXterm,loginasrootbyentering: su - root When the system prompts you for the root password, enter:
Network Management Station Upgrade Guide 12/28/005-9 Beta Draft Confidential Upgrading to HP OpenView 5.01 Backing Up HP OpenView Databases
5-10 Network Management Station Upgrade Guide Beta Draft Confidential
6
Installing a Two-System Configuration
A two-system configuration is an NMS configuration where Sybase is installed on one workstation and HP OpenView and NavisCore are installed on another.
Use Chapter 3 and Chapter 4 to upgrade to Sybase 11.9.2 on the Sybase Server workstation.
Use Chapter 5 and the latest NavisCore Software Release Notice to upgrade HP OpenView to version 5.01 and to upgrade NavisCore on your HP OpenView/NavisCore Server workstation.
NMS Post-Installation Sequence
After you upgrade the NMS software on both systems, perform the following post-installation tasks:
Task See
Verify that the Sybase Server is running (System 1). page 6-2
Verify that HP OpenView Services is running (System 2). page 6-3
Add the Sybase Server hostname and IP address to HP OpenView page 6-4 Server’s /etc/hosts file (System 2).
Create an interfaces file and add Sybase Server information to the page 6-6 HP OpenView Server’s interfaces file (System 2).
Network Management Station Upgrade Guide 6-1 Beta Draft Confidential Installing a Two-System Configuration NMS Post-Installation Sequence
Sybase Server (System 1)
To verify the Sybase and local backup server are running: 1. Log in as sybase by entering su - sybase. When prompted, enter
Figure 6-1. Showserver Window If Sybase and the 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).”
6-2 Network Management Station Upgrade Guide Beta Draft Confidential Installing a Two-System Configuration NMS Post-Installation Sequence
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 the 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. If you are not logged in as root, enter su - root. When prompted, enter
Figure 6-2. HP OpenView Services Window
Network Management Station Upgrade Guide 12/28/006-3 Beta Draft Confidential Installing a Two-System Configuration NMS Post-Installation Sequence
3. If HP OpenView Services are not running, enter: /opt/OV/bin/ovstart 4. Proceed to “Adding the Sybase Server Hostname (System 2).”
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.
Figure 6-3. Admintool: Users Dialog Box 3. Select Browse Þ Hosts. The Admintool: Hosts dialog box appears.
6-4 Network Management Station Upgrade Guide Beta Draft Confidential Installing a Two-System Configuration NMS Post-Installation Sequence
Figure 6-4. Admintool: Hosts Dialog Box 4. Select Edit Þ Add. The Admintool: Add Host dialog box appears.
Figure 6-5. Admintool: Add Host Dialog Box 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. Proceed to “Copying the Interfaces File (System 2).”
Network Management Station Upgrade Guide 12/28/006-5 Beta Draft Confidential Installing a Two-System Configuration NMS Post-Installation Sequence
Copying the Interfaces File (System 2)
To enable communication between the HP OpenView Server and the Sybase Server, you must: • Extract the Open Client 11.1.1 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. Log in as Sybase user by entering: su - sybase 2. Put the OpenClient 11.1.1 CD-ROM in the CD-ROM drive. 3. Create the /opt/sybase directory on the HP OpenView Server by entering: mkdir /opt/sybase 4. Change to the /opt/sybase directory by entering: cd /opt/sybase 5. Extract Open Client 11.1.1 from the tar file by entering: tar xvf /cdrom/cdrom0/
6-6 Network Management Station Upgrade Guide Beta Draft Confidential Installing a Two-System Configuration NMS Post-Installation Sequence
12. Verify that you completed the task successfully by logging into isql. Enter: isql -U sa -P
Network Management Station Upgrade Guide 12/28/006-7 Beta Draft Confidential Installing a Two-System Configuration NMS Post-Installation Sequence
6-8 Network Management Station Upgrade Guide Beta Draft Confidential
A
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 5.01. 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 Upgrade Guide A-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:
A-212/28/00 Network Management Station Upgrade Guide Beta Draft Confidential IP Discovery Enabling IP Discovery
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 7. 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 active window, hold down
Network Management Station Upgrade Guide 12/28/00A-3 Beta Draft Confidential IP Discovery Disabling IP Discovery
Disabling IP Discovery
To disable IP Discovery: 1. Log in as root user by entering: su - root When prompted, enter:
A-412/28/00 Network Management Station Upgrade Guide 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 7 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 active window, hold down
Network Management Station Upgrade Guide 12/28/00A-5 Beta Draft Confidential IP Discovery Disabling IP Discovery
A-612/28/00 Network Management Station Upgrade Guide Beta Draft Confidential
B
HP OpenView 5.01 Upgrade Error Messages
Error messages appear during the HP OpenView 5.01 upgrade. The upgrade will complete successfully regardless of these errors. See the appropriate section for the displayed error messages:
• “Tail Window Error Messages” on page B-1
• “Installation Xterm Window Error Messages” on page B-2
Tail Window Error Messages
The tail window displays the following error messages during the upgrade: ERROR: OV - move_files: cpio failed ERROR: OV - move_files: cpio failed ERROR: OV - move_files: cpio failed ERROR: The "postinstall" script for "OVPlatform.OVWIN" failed (exit * This script had errors but the execution of this product will ERROR: OV - move_files: cpio failed ERROR: OV - Could not move files to new directory location. ERROR: OV - move_files: cpio failed ERROR: The "configure" script for "OVNNMgr.OVNNM-RUN" failed (exit * This script had errors but the execution of this product will ERROR: OVPlatform.OVWIN,r=B.05.01.00 Installed ERROR: OVNNMgr.OVNNM-RUN,r=B.05.01.00 Installed ERROR: The Execution Phase had errors. See the above output for 5
You can ignore the cipo error(s) because they are caused by HP OpenView 5.01 installation/upgrade processes not being aware of custom directory locations Lucent used for the HP OpenView 4.11 installation.
Network Management Station Upgrade Guide B-1 Beta Draft Confidential HP OpenView 5.01 Upgrade Error Messages
Installation Xterm Window Error Messages
Error Messages When the Upgrade Nears Completion
When the upgrade nears completion, the following error messages appear in the installation Xterm window: ERROR: Execution phase for "/" had errors.
* More information may be found in the agent logfile (location is /var/adm/sw/swagent.log).
======09/28/98 14:33:00 EDT END swinstall SESSION (setup mode)
********************************************************* * Errors have been encountered in your installation. * * * * Please look at the log file (/var/adm/sw/swagent.log) * * for more information. You will need to look at the * * last session in that file. Each session is marked * * with the starting date and time. * *********************************************************
Hit the Return Key to Continue...
B-212/28/00 Network Management Station Upgrade Guide Beta Draft Confidential
C
Sybase Worksheet
Complete the worksheet before you start the Sybase upgrade. The script prompts you for the following new and existing information. 1. Sybase 11.0.2 or 11.0.3.3 release path (for example, /opt/sybase): ______2. Sybase 11.9.2 install path (for example, /opt/sybase_new): ______
The /opt/sybase_new directory is a temporary directory. The script copies this directory over the existing Sybase directory (/opt/sybase) when the upgrade completes.
3. Existing database server name (Your Hostname in CAPITAL LETTERS): ______4. Sybase 11.9.2 error log pathname ([Your Hostname in CAPITAL LETTERS]_err.log): ______5. Local Backup Server name (for example, SYB_BACKUP) ______6. Database SA password (for example, superbase): ______7. TCP socket number of Sybase 11.0.2 or 11.0.3.3 (for example, 1025): ______8. TCP socket number of backup server (for example, 1026): ______9. Sybase 11.0.2 or 11.0.3.3 master partition device (for example, /dev/rdsk/c0t1d0s0): ______
Network Management Station Upgrade Guide C-1 Beta Draft Confidential Sybase Worksheet
10. Sybase 11.9.2 system procs device directory (for example, /dev/rdsk/c0t1d0s4): ______11. Sybase 11.9.2 system procs device size (for example, 100): ______12. Number of remote users (for example, 150): ______
C-212/28/00 Network Management Station Upgrade Guide Beta Draft Confidential
Index
B H
Backup procedures HP OpenView HP OpenView database backups, 5-9 upgrading to, 5-1 to 5-9 performing subsequent Sybase backups to the HP OpenView 5.01 Local Backup Server, 4-19 error messages, B-1 subsequent backups to the local backup server, installation window, 5-3 3-8 loading Lucent-supplied HP OpenView media, Sybase, 4-16 5-2 Bulk copy procedures Sybase databases, 3-10, 4-20 I
D Inittab, editing for Solaris 2.6, 2-8 Installing Database server, entering for Sybase, 4-5 OpenClient, 4-15 Disabling IP Discovery, A-4 Solaris 2.6 cluster patch, 2-7 DSQUERY, entering, 4-5 two-system configuration, 6-1 to 6-7 IP Discovery disabling, A-4 E enabling, A-2
Enabling IP Discovery, A-2 Entering the Sybase release pathname, 4-5 L Errorlog, entering, 4-5 Local Backup Server backing up Sybase databases to. See Backup G procedures entering name, 4-5 General requirements, 1-2 Logging off Sybase users, 3-3
Network Management Station Upgrade Guide Index-1 Beta Draft Confidential Index
M install_cvux.See Upgrade Script install_sybase. See Upgrade Script Master device, locating, 4-7 Shared memory, changing, 3-17 Model database, increasing the size, 3-11 Single-system NMS configuration upgrade path, 1-13 Software requirements, 1-7 N Solaris 2.6 editing the inittab file, 2-8 Network Management Station installing the cluster patch, 2-7 requirements upgrading to, 2-1 to 2-6 system configuration, 1-2 to 1-6 Sybase New Sybase Install pathname, entering, 4-5 determining version, 3-2 entering database SA password, 4-5 O database server name, 4-5 errorlog, 4-5 OpenClient 11.1.1 local backup server name, 4-5 extracting in single-system NMS, 4-15 new Sybase install path, 4-5 extracting in two-system NMS, 6-6 old sybase release path, 4-5 release pathname, 4-5 TCP socket numbers, 4-5 P installation window, 4-4 logging off users, 3-3 Physical memory, adding, 3-16 prerequisite tasks, 3-1 to 3-19 Prerequisite tasks total memory HP OpenView, 5-2 changing, 3-18 Sybase, 3-1 to 3-19 upgrading, 4-1 to 4-15 sybsystemprocs database, increasing the size, 3-11 R T Requirements general, 1-2 TCP socket number, entering software for Backup Server, 4-5 HP OpenView 5.01, 1-11 for Sybase Server, 4-5 Solaris, 1-9 Two-system configuration, 6-1 to 6-7 Sybase 11.9.2 SQL Server, 1-10 HP Server, adding Sybase Server’s hostname, 6-4 HP Server, creating the interfaces file, 6-6 S HP Server, starting HP OpenView Services, 6-3 upgrade path, 1-14 SA password changing, 4-22 entering, 4-5 Scripts
Index-2 Network Management Station Upgrade Guide Beta Draft Confidential Index
U
Upgrade features HP OpenView script, 1-12 Sybase scripts, 1-12 Upgrade path single-system, 1-13 two-system configuration, 1-14 Upgrade script running the HP OpenView script, 5-2 running the Sybase script, 4-2 Upgrading HP OpenView, 5-1 to 5-9 Solaris, 2-1 to 2-6 Sybase, 4-1 to 4-15
Network Management Station Upgrade Guide Index-3 Beta Draft Confidential Index
Index-4 Network Management Station Upgrade Guide Network Management Station Upgrade 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 cantheybeimproved?
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.