Installing and Administering Optivity NMS 10.3

Part No. 205969-H November 2004

4655 Great America Parkway Santa Clara, CA 95054

All rights reserved. Printed in the USA. November 2004. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks Inc. The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license. A summary of the Software License is included in this document.

Trademarks

Nortel Networks, the Nortel Networks logo, the Globemark, Accelar, Bay Networks, BayStack, Centillion, Meridian, Optivity, Passport, Unified Networks, and Versalar are trademarks of Nortel Networks. Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated. Alteon is a trademark of Alteon Websystems Incorporated. HyperHelp is a trademark of Bristol Technology. Cisco and Cisco Systems are trademarks of Cisco Systems, Incorporated. HP-UX and OpenView are trademarks of Hewlett-Packard Corporation. Oracle is a trademark of Oracle Corporation. IBM, NetView, RS/6000, Tivoli, TME, and TME 10 are trademarks of IBM Corporation. Intel and Pentium are registered trademarks of Intel Corporation. Microsoft, MS-DOS, Win32, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Netscape Navigator is a trademark of Netscape Communications Corporation. UNIX is a registered trademark of X/Open Company Limited. SPARC and SPARCstation are trademarks of Sparc International, Inc. Sun, Solaris, and Java are trademarks or registered trademarks of Sun Microsystems, Incorporated. The asterisk after a name denotes a trademarked item.

Restricted Rights Legend

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Statement of Conditions

In the interest of improving internal design, operational function, and/or reliability, Nortel Networks Inc. reserves the right to make changes to the products described in this document without notice. Nortel Networks Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein.

205969-H

Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission. SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties).

Nortel Networks Inc. Optivity network management software license agreement

NOTICE: Please carefully read this license agreement before copying or using the accompanying Optivity network management software or installing the hardware unit with pre-enabled Optivity network management software (each of which is referred to as “Software” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER WHICH NORTEL NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price. 1. License grant. Nortel Networks Inc. (“Nortel Networks”) grants the end user of the Software (“Licensee”) a personal, nonexclusive license: a) to use the Software either on a single computer or, if applicable, on a single authorized device identified by host ID; b) to copy the Software solely for backup purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend to Nortel Networks Agent software or other Nortel Networks software products. Nortel Networks Agent software or other Nortel Networks software products are licensed for use under the terms of the applicable Nortel Networks Inc. Software License Agreement that accompanies such software and upon payment by the end user of the applicable license fees for such software. 2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright laws. Nortel Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any revisions made by Nortel Networks or its licensors. The copyright notice must be reproduced and included with any copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Nortel Networks’ and its licensors’ confidential and proprietary intellectual property. Licensee shall not disclose to any third party the Software, or any information about the operation, design, performance, or implementation of the Software and user manuals that is confidential to Nortel Networks and its licensors; however, Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s facility, provided they have agreed to use the Software only in accordance with the terms of this license.

Installing and Administering Optivity NMS 10.3

3. Limited warranty. Nortel Networks warrants each item of Software, as delivered by Nortel Networks and properly installed and operated on Nortel Networks hardware or other equipment it is originally licensed for, to function substantially as described in its accompanying user manual during its warranty period, which begins on the date Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole remedy Nortel Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be included in a future Software release. Nortel Networks further warrants to Licensee that the media on which the Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days from the date the Software is first shipped to Licensee. Nortel Networks will replace defective media at no charge if it is returned to Nortel Networks during the warranty period along with proof of the date of shipment. This warranty does not apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from the Software. Nortel Networks does not warrant a) that the functions contained in the software will meet the Licensee’s requirements, b) that the Software will operate in the hardware or software combinations that the Licensee may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the operation of the Software will be corrected. Nortel Networks is not obligated to remedy any Software defect that cannot be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered, except by Nortel Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product, resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs. 4. Limitation of liability. IN NO EVENT WILL NORTEL NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF NORTEL NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO NORTEL NETWORKS FOR THE SOFTWARE LICENSE. 5. Government licensees. This provision applies to all Software and documentation acquired directly or indirectly by or on behalf of the United States Government. The Software and documentation are commercial products, licensed on the open market at market prices, and were developed entirely at private expense and without the use of any U.S. Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial Computer Software––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for civilian agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS 252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable. 6. Use of software in the European Community. This provision applies to all Software acquired for use within the European Community. If Licensee uses the Software within a country in the European Community, the Software Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the examination of the Software to facilitate interoperability. Licensee agrees to notify Nortel Networks of any such intended examination of the Software and may procure support and assistance from Nortel Networks. 7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Nortel Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Nortel Networks copyright; those restrictions relating to use and disclosure of Nortel Networks’ confidential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason, Licensee will immediately destroy or return to Nortel Networks the Software, user manuals, and all copies. Nortel Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.

205969-H

8. Export and re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical data or information without first obtaining any required export licenses or other governmental approvals. Without limiting the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports are restricted or embargoed under United States export control laws and regulations, or to any national or resident of such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any military end user or for any military end use, including the design, development, or production of any chemical, nuclear, or biological weapons. 9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement will be governed by the laws of the state of California. Should you have any questions concerning this Agreement, contact Nortel Networks Inc., 2375 N. Glenville Dr., Richardson, TX 75082. LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN NORTEL NETWORKS AND LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST NORTEL NETWORKS UNLESS NORTEL NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.

Installing and Administering Optivity NMS 10.3

205969-H

7 Contents

Preface ...... 19

Before you begin ...... 19 Text conventions ...... 20 Acronyms ...... 21 Related publications ...... 22 Hard-copy technical manuals ...... 23 How to get help ...... 23

Chapter 1 Optivity NMS installation overview ...... 25

Software license options ...... 26 Optivity NMS 10.3 components ...... 26 Optivity NMS server ...... 27 Optivity NMS client ...... 27 Optivity NMS database ...... 28 Oracle 9i database management system ...... 28 Optivity legacy applications ...... 28 Optivity NMS client/server configurations ...... 29 Single server and single client ...... 29 Single server and multiple clients ...... 30 Device support using the Optivity Integration Toolkit ...... 30 OIT files on the Web ...... 31 How OIT updates are handled ...... 32 OIT inventory tool ...... 32 Silent Installation ...... 33 Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5 ...... 33 Package contents ...... 34

Installing and Administering Optivity NMS 10.3 8 Contents

Chapter 2 Installing Optivity NMS 10.3 on Windows ...... 37

Checking system prerequisites ...... 38 Installation notes ...... 40 Installation procedures ...... 41 Installation flow chart for Windows ...... 42 Migrating the Optivity NMS 10.2.x database ...... 44 Removing previous versions of Optivity NMS ...... 45 Removing Optivity NMS 10.2.0.1, 10.2.1, and 10.2.0.2 maintenance releases 45 Removing Optivity NMS 10.2 and earlier software ...... 46 Installing the Oracle database software ...... 47 Installing Oracle 9i database software ...... 47 Installing the Oracle 9.2.0.4 patch ...... 50 Installing Optivity NMS 10.3 client or server/client software ...... 51 Using graphic interface installation ...... 52 Using command-line installation ...... 53 Using silent installation ...... 53 Installing the license key ...... 54 Installing the Optivity NMS 10.3 license key number ...... 55 Stopping and restarting the Optivity NMS 10.3 services ...... 56 Installing the JRE 1.4.2_02 plug-in on Windows ...... 57 Installing the plug-in for Internet Explorer ...... 57 Installing the plug-in for Netscape 7.0 ...... 58 Postinstallation notes ...... 59 Uninstalling Optivity NMS 10.3 ...... 60 Uninstalling Optivity NMS 10.3 client/server applications ...... 60 Uninstalling Optivity NMS database Installer ...... 61

Chapter 3 Installing Optivity NMS 10.3 on Solaris ...... 65

Solaris system requirements ...... 65 Solaris platform and browser requirements Solaris system requirements ...... 66 Solaris / HP OpenView Patches ...... 68 Pre-installation notes ...... 69

205969-H

Contents 9

Setting up the platform environment ...... 70 Setting up the Network Node Manager platform environment ...... 71 Setting up the NetView platform environment ...... 71 Installation procedures ...... 72 Installation flow chart for Solaris ...... 73 Migrating the Optivity NMS 10.2.x database ...... 74 Removing previous versions of Optivity NMS ...... 76 Removing Optivity NMS 10.2.0.1, 10.2.1, and 10.2.0.2 maintenance releases 76 Removing Optivity NMS 10.2 and earlier software ...... 77 Installing the Oracle database software ...... 78 Installing Oracle 9i database software ...... 78 Installing the Oracle 9.2.0.4 patch ...... 80 Installing Optivity NMS 10.3 client or server/client software ...... 81 Using graphic interface installation ...... 81 Using command-line installation ...... 82 Using silent installation ...... 83 Modifying Optivity NMS user login scripts ...... 84 Installing the license key ...... 85 Installing the Optivity NMS 10.3 license key number ...... 86 Stopping and restarting Optivity NMS 10.3 daemons ...... 86 Installing the JRE 1.4.2_02 plug-in on Solaris ...... 87 Optivity NMS installation on NFS-mounted file systems ...... 88 Postinstallation notes ...... 89

Chapter 4 Installing Optivity NMS 10.3 on HP-UX ...... 91

Checking system prerequisites ...... 91 Operating system patches ...... 92 JRE Patches ...... 93 Additional HP-UX Operating System Requirements ...... 94 Required executables ...... 94 Netscape 7 for HP-UX ...... 95 JDK version ...... 95 Setting up the platform environment ...... 95 Setting up the Network Node Manager platform environment ...... 96

Installing and Administering Optivity NMS 10.3 10 Contents

Setting up the NetView platform environment ...... 96 Mounting a local CD drive in the HP-UX environment ...... 97 Installation procedures ...... 99 Installation flow chart for HP-UX ...... 100 Migrating the Optivity NMS 10.2x database ...... 102 Removing previous versions of Optivity NMS ...... 104 Removing Optivity NMS 10.2.0.1, 10.2.1, and 10.2.0.2 maintenance releases 104 Removing Optivity NMS 10.2 and earlier software ...... 105 Installing the Oracle database software ...... 106 Checking HP-UX Kernel Parameter Settings ...... 107 Installing the Oracle 9i database software on HP-UX ...... 109 Installing the Oracle 9.2.0.4 patch ...... 111 Installing Optivity NMS 10.3 client or server/client software ...... 112 Using graphic interface installation ...... 112 Using Command-line installation ...... 113 Using silent installation ...... 114 Modifying Optivity NMS user login scripts ...... 115 Installing the license key ...... 116 Installing the Optivity NMS 10.3 license key number ...... 117 Stopping and restarting Optivity NMS 10.3 daemons ...... 117 Installing the JRE 1.4.2 plug-in on HP-UX ...... 118 Postinstallation notes ...... 120

Chapter 5 Getting started with Optivity NMS ...... 121

Operational considerations ...... 121 Discovering and administering your network ...... 122 Understanding the workflow process ...... 124 Logging in to Optivity NMS ...... 124 Starting InfoCenter for the first time ...... 125 Specifying device community strings ...... 126 User security ...... 127 Discovering network resources ...... 128 Configuring a discovery seed ...... 128 Monitoring the topology discovery process ...... 129

205969-H

Contents 11

Viewing network resources ...... 130 Configuring network management applications ...... 130 Setting access control ...... 131 Backing up the database ...... 132 Customizing Optivity NMS InfoCenter ...... 133 Using Optivity NMS applications ...... 133

Chapter 6 Administering Optivity NMS processes...... 135

Optivity NMS daemons and services ...... 135 Managing Optivity NMS Services on Windows ...... 136 Viewing services status on Windows ...... 137 Starting services on Windows ...... 137 Stopping services on Windows ...... 138 Managing Optivity NMS Daemons on UNIX ...... 139 Viewing daemon status on UNIX ...... 139 Starting daemons on UNIX ...... 140 Stopping daemons on UNIX ...... 141

Chapter 7 Managing Optivity NMS firewall support ...... 143

Firewall support overview ...... 143 Required firewall ports ...... 143 Installing or activating the firewall support feature ...... 144 Restricting access according to IP address ...... 145

Appendix A Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5 ...... 147

System prerequisites ...... 149 System configuration ...... 149 Configuring Knowledge Scripts in NetIQ Vivinet Manager ...... 150 Knowledge Script trap numbers ...... 156

Appendix B

Installing and Administering Optivity NMS 10.3 12 Contents

Silent Installation answer file reference...... 161

Appendix C Optivity NMS 10.3 installed directories and files ...... 165

Optivity NMS 10.3 for UNIX directory structure ...... 165 Optivity NMS for UNIX miscellaneous directories and files ...... 167 HP NNM for Solaris directories and files ...... 168 Optivity NMS application control files ...... 168 Optivity NMS log files ...... 169 Optivity NMS configuration files ...... 170 Optivity NMS 10.3 for Windows directories and files ...... 171

Appendix D Troubleshooting Optivity NMS ...... 173

Before you install Optivity NMS ...... 173 Using the Optivity NMS install log file ...... 173 Viewing daemon status ...... 174 Operational notes ...... 174 Oracle installation hangs (HP-UX) ...... 174 Oracle operational note ...... 175 Optivity Integration Toolkit operational note ...... 175 Trap Server operational note ...... 176 Troubleshooting database silent installation on Windows ...... 176 Using verify_connect92.bat to resolve a connection test failure ...... 178 What verify_connect92.bat does ...... 178 verify_connect92.bat error messages ...... 179 Example 1: Usage error ...... 179 Example 2: Usage error—File missing ...... 180 Troubleshooting Optivity NMS applications ...... 180 Administering Optivity NMS databases ...... 180 Autotopology Manager ...... 181 InfoCenter ...... 182 Weboptsrvr ...... 182 Versalar Config Utility http port 80 conflict ...... 182 Site Manager and Network Node Manager port 161 conflict ...... 183

205969-H

Contents 13

Resolving Optivity NMS database installer issues ...... 184 Index ...... 185

Installing and Administering Optivity NMS 10.3 14 Contents

205969-H

15 Figures

Figure 1 Optivity NMS single server/single client configuration ...... 29 Figure 2 Optivity NMS single server/multiple client configuration ...... 30 Figure 3 Installation procedure overview, Windows ...... 43 Figure 4 Welcome to database installer window ...... 48 Figure 5 Oracle Universal Installer window ...... 49 Figure 6 Disk location dialog box ...... 49 Figure 7 Confirm file deletion dialog box ...... 62 Figure 8 Oracle inventory window ...... 62 Figure 9 Installation procedure overview, Solaris ...... 73 Figure 10 HP-UX ioscan output ...... 98 Figure 11 Installation procedure overview, HP-UX ...... 101 Figure 12 BCM faults displayed in Fault Summary ...... 147 Figure 13 Choosing Action_SnmpTrap ...... 152 Figure 14 Properties for Action_SnmpTrap dialog box ...... 153 Figure 15 Job properties dialog box, Advanced tab ...... 155

Installing and Administering Optivity NMS 10.3 16 Figures

205969-H

17 Tables

Table 1 Specific package contents ...... 34 Table 2 Optivity NMS 10.3 client/server minimum system requirements ...... 38 Table 3 Installation notes for the Windows environment ...... 40 Table 4 Starting Optivity NMS installation on Windows ...... 42 Table 5 Postinstallation notes for the Windows environment ...... 59 Table 6 Optivity NMS 10.3 client/server minimum system requirements for Solaris 66 Table 7 Solaris system requirements ...... 67 Table 8 Solaris/HP OpenView patches ...... 68 Table 9 Pre-installation notes for Solaris ...... 69 Table 10 Starting Optivity NMS installation on Solaris ...... 72 Table 11 Postinstallation notes for the Windows environment ...... 89 Table 12 HP-UX System requirements ...... 91 Table 13 HP-UX JRE patches ...... 93 Table 14 HP-UX environment variables ...... 95 Table 15 Starting Optivity NMS installation ...... 100 Table 16 HP-UX kernel parameter settings ...... 107 Table 17 Postinstallation notes for the Windows environment ...... 120 Table 18 Default display window preferences ...... 133 Table 19 Optivity NMS daemons (UNIX) or services and services (Windows) . . . 135 Table 20 System Prerequisites ...... 149 Table 21 NortelBCM package contents ...... 149 Table 22 Schedule properties ...... 151 Table 23 Value properties ...... 151 Table 24 Default values for Action_SnmpTrap ...... 152 Table 25 Action_SnmpTrap properties ...... 153 Table 26 Values for Action_ExtendedSnmpTrap ...... 154 Table 27 Action_ExtendedSnmpTrap properties ...... 154 Table 28 NortelBCM Knowledge Scripts and trap numbers ...... 156 Table 29 Answer file options ...... 163

Installing and Administering Optivity NMS 10.3 18 Tables

Table 30 Optivity NMS 10.3 $LNMSHOME core installation directories ...... 165 Table 31 Optivity NMS miscellaneous directories and files ...... 167 Table 32 HP Network Node Manager (NNM) specific directories ...... 168 Table 33 Optivity NMS control files ...... 168 Table 34 Optivity NMS log files ...... 169 Table 35 Optivity NMS configuration files ...... 170 Table 36 Optivity NMS 10.3 for Windows-specific directories and files ...... 171 Table 37 Install/Uninstall log file names ...... 173 Table 38 Install/Uninstall log file locations ...... 174 Table 39 Windows silent installation result codes ...... 177

205969-H

19 Preface

Optivity* Network Management System (NMS) 10.3 is a Nortel Networks* integrated suite of applications for the Solaris and HP-UX* UNIX* operating systems, and also for the Microsoft* Windows NT,* Windows* 2000, and Windows XP* operating systems. Optivity NMS delivers system-level management for converging campus and enterprise networks.

Optivity NMS is a primary component of Unified Networks*, a solution set from Nortel Networks designed to create greater value for customers worldwide through the integration of voice, video, and data networking. Through Unified Networks, enterprises can leverage LAN and WAN convergence, application and infrastructure convergence, and voice and data convergence to achieve greater efficiency and reduced operational cost. Unified Networks provides a systematic transition from today's disparate networks.

The Optivity NMS common graphical interfaces and proven technology provide the necessary tools to manage the converging Unified Network. Optivity NMS provides graphical views from physical connections between LAN and WANs to the logical connections of a VLAN. This combination provides the tools necessary for you to manage Unified Networks.

Before you begin

This guide is intended for network managers using a UNIX and Windows-based management station. Prior knowledge of installing Optivity NMS is suggested. This guide assumes that you have the following background:

• Working knowledge of Solaris* and HP-UX. • Working knowledge of the Microsoft Windows operating environments, including Windows NT client/server, Windows 98, Windows 2000 client/ server, Windows XP, and Windows 2003 server. • Familiarity with managing and troubleshooting large, complex networks.

Installing and Administering Optivity NMS 10.3

20 Preface

• Experience with working with Nortel Networks and standards-based networking devices. • Working knowledge of the transmission and management protocols used on your network. • (Optional) Familiarity with the network management applications (for example, HP* OpenView* Network Node Manager or Tivoli* TME 10* Netview) on the system with which you are using Optivity NMS.

Text conventions

This guide uses the following text conventions:

angle brackets (< >) Indicate that you choose the text to enter based on the description inside the brackets. Do not type the brackets when entering the command. Example: If the command syntax is ping , you enter ping 192.32.10.12 bold Courier text Indicates command names and options and text that you need to enter. Example: Use the dinfo command. Example: Enter show ip {alerts|routes}. braces ({}) Indicate required elements in syntax descriptions where there is more than one option. You must choose only one of the options. Do not type the braces when entering the command. Example: If the command syntax is show ip {alerts|routes}, you must enter either show ip alerts or show ip routes, but not both. brackets ([ ]) Indicate optional elements in syntax descriptions. Do not type the brackets when entering the command. Example: If the command syntax is show ip interfaces [-alerts], you can enter either show ip interfaces or show ip interfaces -alerts.

205969-H

Preface 21

ellipsis points (. . . ) Indicate that you repeat the last element of the command as needed. Example: If the command syntax is ethernet/2/1 [ ]... , you enter ethernet/2/1 and as many parameter-value pairs as needed. italic text Indicates new terms, book titles, and variables in command syntax descriptions. Where a variable is two or more words, the words are connected by an underscore. Example: If the command syntax is show at , valid_route is one variable and you substitute one value for it. plain Courier Indicates command syntax and system output, for text example, prompts and system messages. Example: Set Trap Monitor Filters separator ( > ) Shows menu paths. Example: Protocols > IP identifies the IP option on the Protocols menu. vertical line ( | ) Separates choices for command keywords and arguments. Enter only one of the choices. Do not type the vertical line when entering the command. Example: If the command syntax is show ip {alerts|routes}, you enter either show ip alerts or show ip routes, but not both.

Acronyms

This guide includes the following acronyms:

ATM Asynchronous Transfer Mode IP Internet Protocol LAN Local Area Network MIB Management Information Base NMS Network Management System SNMP Simple Network Management Protocol

Installing and Administering Optivity NMS 10.3

22 Preface

OIT Optivity Integration Toolkit VLAN Virtual LAN WAN Wide Area Network

Related publications

For more information about using Optivity Network Management System (NMS) 10.3, refer to the following publications: • Using Optivity NMS 10.3 Applications (Part number 207569-F) Describes how to use the integrated Optivity NMS tools and applications to proactively get the most out of your network resources. This document is located on the Optivity NMS 10.3 for Windows* CLIENT Only and Documentation CD. • Release Notes for Optivity NMS 10.3 (Part number 205970-H) Contains the latest information about Optivity NMS 10.3, including informational notes, known problems, and bug fixes. • Quick Installation and Startup for Optivity NMS 10.3 for Windows* (Part number 217232-A) Provides quick procedures for installing Optivity NMS 10.3 on a Windows machine. • Quick Installation and Startup for Optivity NMS 10.3 for Solaris (Part number 217233-A) Provides quick installation procedures for installing Optivity NMS 10.3 on a Solaris machine. • Quick Installation and Startup for Optivity NMS 10.3 for HP-UX (Part number 217234-A) Provides quick installation procedures for installing Optivity NMS 10.3 on an HP-UX machine.

205969-H

Preface 23

Hard-copy technical manuals

You can print selected technical manuals and release notes free, directly from the Internet. Go to the www.nortelnetworks.com/documentation URL. Find the product for which you need documentation. Then locate the specific category and model or version for your hardware or software product. Use Adobe* Acrobat Reader* to open the manuals and release notes, search for the sections you need, and print them on most standard printers. Go to Adobe Systems at the www.adobe.com URL to download a free copy of Acrobat Reader.

How to get help

If you purchased a service contract for your Nortel Networks product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance.

If you purchased a Nortel Networks service program, contact Nortel Networks Technical Support. To obtain contact information online, go to the www.nortelnetworks.com/cgi-bin/comments/comments.cgi URL, then click on Technical Support.

From the Technical Support page, you can open a Customer Service Request online or find the telephone number for the nearest Technical Solutions Center. If you are not connected to the Internet, you can call 1-800-4NORTEL (1-800-466-7835) to learn the telephone number for the nearest Technical Solutions Center.

An Express Routing Code (ERC) is available for many Nortel Networks products and services. When you use an ERC, your call is routed to a technical support person who specializes in supporting that product or service. To locate an ERC for your product or service, go to the following URL:

http://www.nortelnetworks.com/help/contact/erc/index.html

Installing and Administering Optivity NMS 10.3

24 Preface

205969-H

25 Chapter 1 Optivity NMS installation overview

Optivity NMS 10.3 is a Java*-based, Web-enabled, client/server network management application. You use Optivity Campus NMS to administer campus networks or Optivity Enterprise NMS to administer enterprise networks at a system level. Optivity NMS has the same look and feel in a UNIX, Windows, and Web browser-based user interface.

This guide describes how to install and administer Optivity NMS 10.3 to start managing your network. There are two basic installation scenarios addressed in this document:

• You are installing Optivity NMS for the first time: Optivity NMS software has not been installed on the system. • You have Optivity NMS 10.2 on your system(s) and you are migrating from Optivity NMS 10.2 to Optivity NMS 10.3.

Note: There is no direct upgrade path from Optivity NMS 10.1 or earlier to Optivity NMS 10.3.

Information in this chapter is organized as follows:

• “Software license options‚” next • “Optivity NMS 10.3 components” on page 26 • “Optivity NMS client/server configurations” on page 29 • “Device support using the Optivity Integration Toolkit” on page 30 • “Silent Installation” on page 33 • “Package contents” on page 34

Installing and Administering Optivity NMS 10.3

26 Chapter 1 Optivity NMS installation overview

Software license options

Nortel Networks lets you install a free 60-day evaluation version of Optivity Campus NMS. After 30 days, Optivity NMS software displays a message letting you know how many days remain in the evaluation period.

When you install Optivity NMS, you must install a license key so that the software can detect your product license and permit uninterrupted access to the features and functions. Your license key is located on the Optivity NMS 10.3 License document.

The license document included in your software kit lets you use one of three license levels for Optivity NMS 10.3:

• Campus - Optivity NMS 10.3 Campus lets you manage up to 500 network element IP addresses • Enterprise - Optivity NMS 10.3 Enterprise lets you manage up to 5,000 network element IP addresses • Enterprise Upgrade - Optivity NMS 10.3 Enterprise Upgrade lets you manage up to 10,000 network element IP addresses

To purchase a license key, contact your local Nortel Networks sales office, supplier, or distributor.

Optivity NMS 10.3 components

Optivity NMS includes the components described in the following sections:

• “Optivity NMS server‚” next • “Optivity NMS client” on page 27 • “Optivity NMS database” on page 28

205969-H

Chapter 1 Optivity NMS installation overview 27

You install the Optivity NMS components as follows:

• On the Windows or UNIX network management station, install the Oracle database management software, Optivity NMS server, and Optivity NMS client.

Note: To increase performance characteristics, Nortel Networks recommends that you access an Optivity NMS 10.3 for Windows server from an Optivity NMS client installed on a separate network management station whenever possible. Users who access the Optivity NMS 10.3 server from an Optivity NMS client installed on the same Windows server may experience a degradation in performance.

• On client management stations, install only the Optivity NMS client.

For more information about installing Optivity NMS components, see the following chapters:

• Chapter 2, “Installing Optivity NMS 10.3 on Windows,” on page 37 • Chapter 3, “Installing Optivity NMS 10.3 on Solaris,” on page 65 • Chapter 4, “Installing Optivity NMS 10.3 on HP-UX,” on page 91

Optivity NMS server

The Optivity NMS server component contains the application engines, database structures, and administrative processes for Optivity NMS. The server also contains the Web server (Apache Web Server) component of Optivity NMS.

Optivity NMS client

The Optivity NMS client component represents the Java-based application interfaces used to access the Optivity NMS server. Install the client software on any supported network management station to allow access to the server processes and the database.

Installing and Administering Optivity NMS 10.3

28 Chapter 1 Optivity NMS installation overview

Optivity NMS database

The Optivity NMS database is implemented as a single database that consists eight core databases (dynamic and pre-packaged) and as many user databases as you want to define. Optivity NMS generates some databases dynamically, as you create data or use a feature. Optivity NMS also installs pre-packed database on your system. Others are created and initialized during the installation.

Oracle 9i database management system

The Oracle database management software contains the relational database management system used with the Optivity NMS server. Install Oracle on the same network management station as the Optivity NMS server.

If Oracle 9i is already installed, you do not have to reinstall Oracle. However, you must install the Oracle 9.2.0.4 patch as described in the installation procedures.

Optivity legacy applications

In addition to the new and updated applications described in the previous sections, Optivity NMS 10.3 retains the following legacy applications that are no longer fully supported, but are still installed (optionally) on the Optivity NMS server:

• LANarchitect • Conversation Steering Control • Threshold Manager • Redundant Link Manager • Expanded View for System 2000 and System 3000 hubs • BaySecure LAN Access •PCAP/TAP

These legacy applications (with the exception of BaySecure LAN Access) are not Java- or Web-based, and you must start them locally from the Optivity NMS 10.3 server.

205969-H

Chapter 1 Optivity NMS installation overview 29

The Optivity NMS 10.3 installation program installs the Optivity legacy applications as follows:

• For Windows—By default, the legacy applications are installed in the %lnmshome%\unsupported directory of the Optivity NMS server. Optivity NMS legacy applications require that the folder names be eight characters or less and not have any spaces in the path or folder name. • For UNIX—By default, the legacy applications are installed in the $LNMSHOME/unsupported directory of the Optivity NMS server. The Optivity NMS installation program does not let you change where the legacy applications are installed.

Optivity NMS client/server configurations

You can install Optivity NMS in two client/server configurations:

• Single server and single client—In this case, you install the Optivity NMS client and server on one system. • Single server and multiple clients—In this case, you install the Optivity NMS client and server on one system and install the client on multiple systems.

Single server and single client

You can install Optivity NMS client/server on a single UNIX or Windows network management station. The network management station functions as both the Optivity NMS client and the Optivity NMS server to provide network management (Figure 1).

Figure 1 Optivity NMS single server/single client configuration

Optivity NMS server

Optivity NMS client

Network Oracle database management system management station 9161RK

Installing and Administering Optivity NMS 10.3

30 Chapter 1 Optivity NMS installation overview

Multiple network administrators must use the same network management station to perform network management tasks using Optivity NMS.

Single server and multiple clients

You can install Optivity NMS 10.3 so that you can access the server and share applications with multiple clients. You can access an Optivity NMS server from UNIX (HP-UX or Solaris), Windows, and Web browser clients (Figure 2).

Figure 2 Optivity NMS single server/multiple client configuration Windows Windows NT Windows 98 Windows 2000 Web browser XP client client client Professional client client

UNIX Server network management station 9163EC

The Optivity NMS client on Windows workstations connect to the Optivity NMS server using the TCP/IP protocol. Web browsers connect to the Optivity NMS server using the HTTP protocol.

Device support using the Optivity Integration Toolkit

The Optivity Integration Toolkit (OIT) lets you obtain new device support from the Web whenever a new Nortel Networks device, an upgraded agent, or a device management application is released.

You can use either of two OIT applications to administer OIT packages:

• OIT Administration Tool (graphical user interface) application • oitInstall application (command line driven)

205969-H

Chapter 1 Optivity NMS installation overview 31

The OIT Administration Tool and oitInstall application let you download the OIT files from the Customer Support Web site soon after the new release is announced. You download these files to your Optivity NMS server and then use the OIT Administration Tool or oitInstall application to add support for the new devices.

For example, to download the latest device support using the oitInstall application:

1 Start a Web browser. 2 Enter: http://www.nortelnetworks.com/ The Nortel Networks Home page opens. 3 In the Support area of the page, click Software Downloads. The Software page opens. 4 In the Product Family area, click Optivity. The Optivity Products page opens. 5 In the Optivity list, click Optivity Network Management System OIT. The Optivity Network Management System OIT page opens. 6 Choose the OIT files for your devices. The Electronic Software Distribution download page opens.

See Chapter 18, “Administering device support using OIT,” in Using NMS Optivity NMS 10.3 Applications (part number 207569-D) for more information.

OIT files on the Web

There are two types of OIT files provided on the Web site:

• Device support files allow Optivity NMS applications such as InfoCenter and OmniView to recognize the new device and/or agent. • Application launch files allow you to start new device management applications (for example, Site Manager for BayRS or Device Manager for Passport* 8600) from InfoCenter. The device management applications themselves are not distributed on the Customer Support Web site, but are available when you purchase the individual devices.

Installing and Administering Optivity NMS 10.3

32 Chapter 1 Optivity NMS installation overview

You can start a device management application independent of or from within Optivity NMS. You can install and run a device management application on any of the following: — An Optivity NMS client — An Optivity NMS client and server

There is also a readme file (Readme for Windows and README for UNIX) as part of the OIT package on the Web site. The readme file describes the Optivity NMS features supported for this device and provides detailed instructions for installing the OIT file.

How OIT updates are handled

Optivity NMS 10.3 includes integrated device support for devices previously added using OIT. For more information about devices supported in Optivity NMS 10.3, see Chapter 19 in Using Optivity NMS 10.3 Applications (part number 207569-G).

However, you might have loaded an OIT file that is not included in Optivity NMS 10.3, perhaps because you waited several months before upgrading to Optivity NMS 10.3.

For example, consider this scenario. You have added device support to Optivity NMS 10.2 using OIT, and want to upgrade to Optivity NMS 10.3. You review the release notes and discover that the devices you have added to Optivity NMS 10.2 are not listed in the release notes. No problem. When you upgrade, the Optivity NMS 10.3 installation program automatically incorporates your previous device support into Optivity NMS 10.3.

OIT inventory tool

Optivity NMS includes an OIT inventory tool that maintains information about each OIT file that you install.

The OIT inventory tool maintains the following information:

• The name of the OIT file that is installed • The version of the OIT file that is installed

205969-H

Chapter 1 Optivity NMS installation overview 33

• The date and time when the file is installed • The user ID of the person who installed the OIT file

For more information, see Chapter 19 in Using Optivity NMS 10.3 Applications (part number 207569-G).

Silent Installation

Silent install is a non-interactive installation procedure automates the installation the Optivity NMS 10.3 software. You can use this feature as an alternative to the regular graphical or command-line interactive installation procedures. This feature makes it easier to perform bulk Optivity NMS 10.3 installations on numerous systems, or to automate repeated installations on the same system.

The silent install feature installs Optivity NMS according to information that you write in a text file. You can create this text file using a template supplied on the Optivity NMS 10.3 installation CDs.

Silent installation is described in detail in each of the chapters on installing Optivity NMS 10.3 on Windows, Solaris, and HP-UX.

Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5

You can configure Nortel Networks BCM (Business Communication Manager) devices and NetIQ Vivinet Manager so that Optivity NMS displays faults for BCM devices. The faults are based on traps sent to the Optivity NMS management station by NetIQ Vivinet Manager on behalf of the BCM devices. When so configured, InfoCenter also propagates fault status colors based on the NetIQ Vivinet Manager traps. See Appendix A, “Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5,” on page 147 for more information.

Installing and Administering Optivity NMS 10.3

34 Chapter 1 Optivity NMS installation overview

Package contents

Check to see that your Optivity NMS 10.3 product package includes the following general items:

• Installing and Administering Optivity NMS 10.3 (Part number 205969-H) • Release Notes for Optivity NMS 10.3 (Part number 205970-G)

Check to see that your Optivity NMS 10.3 product package includes other items specific to your Windows or UNIX package (Table 1).

Table 1 Specific package contents

Optivity NMS package Contents Optivity Campus NMS 10.3 • Optivity NMS 10.3 for Windows* CLIENT and for Windows SERVER CD (part number 205964-10.3) • Optivity NMS 10.3 for Windows* CLIENT ONLY and Documentation CD (part number 205965-10.3) • Optivity NMS 10.3 Database Installer for Windows* (1 of 3) CD (part number 213127-10.3) • Optivity NMS 10.3 Database Installer for Windows* (2 of 3) CD (part number 216280-10.3) • Optivity NMS 10.3 Database Installer for Windows* (3 of 3) CD (part number 216281-10.3) • Quick Installation and Startup for Optivity NMS 10.3 for Windows* (part number 217232-A) • Optivity NMS 10.3 Campus License (part number 209001-F) Optivity Enterprise NMS • Optivity NMS 10.3 for Windows* CLIENT and 10.3 SERVER CD (part number 205964-10.3) for Windows • Optivity NMS 10.3 for Windows* CLIENT ONLY and Documentation CD (part number 205965-10.3) • Optivity NMS 10.3 Database Installer for Windows* (1 of 3) CD (part number 213127-10.3) • Optivity NMS 10.3 Database Installer for Windows* (2 of 3) CD (part number 216280-10.3) • Optivity NMS 10.3 Database Installer for Windows* (3 of 3) CD (part number 216281-10.3) • Quick Installation and Startup for Optivity NMS 10.3 for Windows* (part number 217232-A) • Optivity NMS 10.3 Enterprise License (part number 214491-B)

205969-H

Chapter 1 Optivity NMS installation overview 35

Table 1 Specific package contents (continued)

Optivity NMS package Contents Optivity Enterprise NMS • Optivity NMS 10.3 for Solaris CLIENT and 10.3 SERVER CD (part number 205963-10.3) for Solaris • Optivity NMS 10.3 for Windows* CLIENT ONLY and Documentation CD (part number 205965-10.3) • Optivity NMS 10.3 Database Installer for Solaris (1 of 4) CD (part number 213128-10.3) • Optivity NMS 10.3 Database Installer for Solaris (2 of 4) CD (part number 213238-10.3) • Optivity NMS 10.3 Database Installer for Solaris (3 of 4) CD (part number 216282-10.3) • Optivity NMS 10.3 Database Installer for Solaris (4 of 4) CD (part number 216493-10.3) • Quick Installation and Startup for Optivity NMS 10.3 for Solaris (part number 217233-A) • Optivity NMS 10.3 Enterprise License (part number 214491-B) Optivity Enterprise NMS • Optivity NMS 10.3 for HP-UX CLIENT and 10.3 SERVER CD (part number 208943-10.3) for HP-UX • Optivity NMS 10.3 for Windows* CLIENT ONLY and Documentation CD (part number 205965-10.3) • Optivity NMS 10.3 Database Installer for HP-UX (1 of 5) CD (part number 216497-10.3) • Optivity NMS 10.3 Database Installer for HP-UX (2 of 5) CD (part number 216285-10.3) • Optivity NMS 10.3 Database Installer for HP-UX (3 of 5) CD (part number 216498-10.3) • Optivity NMS 10.3 Database Installer for HP-UX (4 of 5) CD (part number 216494-10.3) • Optivity NMS 10.3 Database Installer for HP-UX (5 of 5) CD (part number 216495-10.3) • Quick Installation and Startup for Optivity NMS 10.3 for HP-UX (part number 217234-A) • Optivity NMS 10.3 Enterprise License (part number 214491-B)

For more information about administering Optivity NMS daemons and services, see Appendix B, “Administering Optivity NMS processes,” on page 75. For more information about Optivity NMS troubleshooting, see Appendix D, “Troubleshooting Optivity NMS,” on page 173.

Installing and Administering Optivity NMS 10.3

36 Chapter 1 Optivity NMS installation overview

205969-H

37 Chapter 2 Installing Optivity NMS 10.3 on Windows

This chapter describes how to install Optivity NMS 10.3 to run on a network management station running any of the following Windows versions:

• Windows 2003 • Windows 2000 •Windows NT • Windows 98 (client only) • Windows XP (client only) • Windows NT Workstation (client only)

Additionally, this chapter describes how to uninstall Optivity NMS 10.3.

The following sections describe how to install Optivity NMS 10.3 on Windows:

• “Checking system prerequisites‚” next • “Installation procedures” on page 41 • “Postinstallation notes” on page 59 • “Uninstalling Optivity NMS 10.3” on page 60

Installing and Administering Optivity NMS 10.3

38 Chapter 2 Installing Optivity NMS 10.3 on Windows

Checking system prerequisites

Before you install Optivity NMS 10.3, ensure that the network management station(s) upon which you install the server and the client meet(s) the recommended system requirements defined in Table 2.

Table 2 Optivity NMS 10.3 client/server minimum system requirements

Requirement Optivity NMS 10.3 server Optivity NMS 10.3 client Hardware Recommended processor, RAM, hard drive: • Intel Pentium 4 PC • Large network (10000 managed IP •512 MHz interfaces): • 1 GB of RAM Pentium 4, 2.6 Ghz processor, 2 Gb RAM, 20 Gb hard drive • Medium network (5000 managed IP interfaces): Pentium 4, 1.2 Ghz processor, 2 Gb RAM, 20 Gb hard drive • Small network (500 managed IP interfaces): Pentium 4, 512 Mhz processor, 2 Gb RAM, 15 Gb hard drive Operating One of the following: One of the following: Environment and • Microsoft Windows NT 4.0 with Service • Windows NT 4.0 Workstation with Service packs Pack (SP) 6a (not provided with Optivity SP6a or Windows NT 4.0 Server NMS 10.3) with SP6a (not provided with Optivity • Windows 2000 Server or Windows 2000 NMS 10.3) Advanced Server with Service Pack 4 • Windows 98 • Windows 2003 Enterprise Server • Windows XP • Windows 2000 Professional Disk Space 8 GB, allocated as follows for components: At least 120 MB for basic installation • Client/server, 500 MB • Client only, 120 MB • Oracle software, 3 GB • Oracle database (pre-packaged), 4 GB Optional Network One of the following: None Management • Tivoli TME 10 NetView 7.1.4 for Platform Windows NT, Windows 2000 Server or Windows 2000 Advanced Server • HP OpenView Network Node Manager 7.0.1 for Windows 2000 Server or Win- dows 2000 Advanced Server

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 39

Table 2 Optivity NMS 10.3 client/server minimum system requirements (continued)

Requirement Optivity NMS 10.3 server Optivity NMS 10.3 client Web browser and One of the following: One of the following: plug-in • Windows NT, Windows 2000, • Windows XP, Windows NT Windows 2003: Workstation, Windows 2000 — Netscape Communicator 7.0 Professional, Windows 98: — Internet Explorer 6.0, SP1 — Netscape Communicator 7.0 — Java 2 version 1.4.2_021 — Internet Explorer 6.0, SP1 — Java 2 version 1.4.2_02 Host Control If your Windows server uses Dynamic Host Protocol (DHCP) Control Protocol (DHCP) to obtain an IP address, Optivity NMS 10.3 does not function properly. Optivity NMS 10.3 only supports a Windows server with a static IP address. Temp directory A TEMP environment variable must be set. The Optivity NMS 10.3 installation program requires that a temp directory (24 MB minimum space) be resident on the client system where Optivity NMS 10.3 is installed. The installation fails if a temp directory is not located. Administrator Ensure that you have local Administrator privileges for the Windows system. privileges The user installing Optivity NMS 10.3 must have system administration and super user access permissions for installing Optivity NMS 10.3. System drive The installation program creates temporary files on the system drive during the installation process. The installation program checks that 140 MB of space is available. The environment identifies the system drive. The Temp variable points to the location of the temp directory. The temp directory might be on a drive other than the system drive. Network Unsupported configuration—If you are running a CiscoWorks network management management application from Cisco Systems* Incorporated, you must stop the CiscoWorks applications services manually before installing Optivity NMS 10.3. Optivity NMS 10.3 and CiscoWorks run together in the Windows environment after you reboot the machine. Network If you are running a network management platform on your system, do not shut down management the network management platform software. The Optivity NMS 10.3 installation platform program requires the presence of a running network management platform for software integration. Internet Explorer There is a known operational problem that requires that Microsoft Internet Explorer 6.0 be installed on your system. If Internet Explorer 6.0 is not installed on your system, Optivity NMS 10.3 online Help does not open. You do not have to use Internet Explorer as your browser. After you install Internet Explorer, manually launch your preferred browser. After doing so, the Optivity NMS 10.3 online Help opens. Windows users All Optivity NMS users must be members of the Windows Administrators group.

Installing and Administering Optivity NMS 10.3

40 Chapter 2 Installing Optivity NMS 10.3 on Windows

Table 2 Optivity NMS 10.3 client/server minimum system requirements (continued)

Requirement Optivity NMS 10.3 server Optivity NMS 10.3 client License key • Evaluation software—If you are installing evaluation software, you only need a license key if you plan on using Optivity NMS 10.3 after the 60-day evaluation period. To obtain a license key, contact your local Nortel Networks sales office, supplier, or distributor. • Licensed software—If you install licensed software, or if you are upgrading from Optivity Campus NMS 10.3 to Optivity Enterprise NMS 10.3, you need to have the license key available. Your license key is available on your Optivity NMS 10.3 license key document. Language Your Windows language setting must be English (United States) in order to install Optivity NMS. To set the language setting, choose Start > Settings > Control Panel > Regional Settings. If you have installed Oracle under a different language, you must remove and reinstall Oracle with the language set to English (United States). Windows SNMP When you install Optivity NMS 10.3 server on a platformless Windows system, you trap service must stop the Windows SNMP trap service and set it to manual start. Thereafter, do not start the Windows SNMP trap service.

1 See “Installing the JRE 1.4.2_02 plug-in on Windows” on page 57 for more information.

Installation notes

Table 3 describes information related to Optivity NMS 10.3 installation in a Windows environment.

Table 3 Installation notes for the Windows environment

Topic Consideration

Windows The services must be running before starting the Optivity NMS 10.3 environment installation. Port 80 assignment If a pre installed Apache Web server is bound to port 80, during installation you must choose a different port, for example, port 8585, for Optivity NMS 10.3 during installation.

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 41

Table 3 Installation notes for the Windows environment (continued)

Topic Consideration Port 8009 The Optivity NMS installation program will try to assign port 8009 for assignment for the Apache servlet engine. Apache servlet The installation program temporarily binds to this port to verify that engine the port is available. If the installation program is unable to bind to the port, the installation program tries to bind to successive ports (8010, 8011, and so forth), and uses the next available port for the Optivity NMS Apache servlet engine. You can view the apache config file to determine which port number is assigned. The apache config file contains the following entries: <%lnmshome%>\apache\jserv\conf\jserv.properties port= <%lnmshome%>\apache\jserv\conf\mod_jserv.conf ApJservDefaultPort= Ter minal Ser vices You cannot install Optivity NMS 10.3 on a Windows 2000 system running terminal services. Also, you cannot install Optivity NMS 10.3 from a terminal services session. Read-only File You cannot install Optivity NMS 10.3 on a read-only file system. System If you attempt such an installation using the graphical installation program, clicking Next does not advance to the next screen. Instead, it adds one iteration of the text “\lnms” to the installation location text box for each click on the Next button. (CR Q00838436) Apache already Do not install the Optivity NMS 10.3 server on a system where the installed Apache Web server is already installed. The Optivity NMS 10.3 server installation program installs its own Apache Web server as a Windows service called “Apache”. The installation program cannot install its Apache service if a service with the same name already exists on the system. In such an installation the Optivity NMS services will not start (CR Q00586044) Users with blank On a Windows 2003 server, each user must have their password set passwords to a non-blank string in order to use the Optivity NMS applications. (CR Q00849276)

Installation procedures

This section is divided into the following major sections. You perform some or all of the procedures in these sections to install Optivity NMS 10.3:

• “Installation flow chart for Windows‚” next • “Migrating the Optivity NMS 10.2.x database” on page 44

Installing and Administering Optivity NMS 10.3

42 Chapter 2 Installing Optivity NMS 10.3 on Windows

• “Removing previous versions of Optivity NMS” on page 45 • “Installing the Oracle database software” on page 47 • “Installing Optivity NMS 10.3 client or server/client software” on page 51 • “Installing the license key” on page 54 • “Installing the JRE 1.4.2_02 plug-in on Windows” on page 57

Table 5 describes where to start installing Optivity NMS 10.3, depending on the type of installation and whether you are upgrading from a previous release of Optivity NMS. At the end of each section there are instructions on which procedure to do next, depending on your installation type.

Table 4 Starting Optivity NMS installation on Windows

If you have this Optivity NMS And you want to install the And you want to install the version currently installed: Optivity NMS Server/Client Optivity NMS Client-only software: software: None Go to “Installing the Oracle Go to “Installing Optivity NMS 10.3 database software” on page 47 client or server/client software” on page 51 Any of: • To preserve your Optivity NMS Go to “Removing previous versions • 10.2 10.2x database, go to “Migrating of Optivity NMS” on page 45 the Optivity NMS 10.2.x • 10.2.0.x database” on page 44 • 10.2.x • If you don’t need to preserve your Optivity NMS 10.2x database, go to “Removing previous versions of Optivity NMS” on page 45 10.1 or prior Go to “Removing Optivity NMS 10.2 and earlier software” on page 46

Installation flow chart for Windows

The flow chart in Figure 3 shows an overall view of the procedures for installing Optivity NMS 10.3 on Windows.

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 43

Figure 3 Installation procedure overview, Windows

Start

Installation Client-only type Server/client

ONMS version 10.2.x ONMS version 10.1 or installed? 10.2x earlier 10.1 or installed? earlier Yes (10.2.0.x or Yes (10.2.0.x or None ONMS version None Patched? installed? 10.2.x installed) 10.2.x installed) Uninstall old Uninstall old Optivity NMS Remove patch to Optivity NMS Preserve 10.2 revert to 10.2 No topology Ye s database? Do data migration Uninstall No procedure version 10.2

Remove patch to revert to 10.2

Uninstall version 10.2

Oracle 9i No installed? Install Oracle 9i Ye s

Install Oracle 9.2.0.4 patch

Installation GUI Silent (easiest) option Command line “install” “install -c” Create answer file

answer answer “install --silent prompts prompts ”

Installation Server/client type? Install Client-only license key

End

Installing and Administering Optivity NMS 10.3

44 Chapter 2 Installing Optivity NMS 10.3 on Windows

Migrating the Optivity NMS 10.2.x database

If you have upgraded your Optivity NMS 10.2 installation with any of the Optivity NMS 10.2.0.x or 10.2.x maintenance releases and you want to preserve your Optivity NMS database, follow the procedure below to migrate your database to Optivity NMS 10.3 format.

You can skip this procedure if:

• You have not installed any of the Optivity NMS 10.2.0.x or 10.2.x maintenance releases. In this case your database does not need to be migrated. • If you have installed any of the Optivity NMS 10.2.0.x or 10.2.x maintenance releases, but do not want to preserve your database. You will have to rediscover your network and reestablish your Optivity NMS database from scratch.

In either of these cases, skip ahead to “Removing previous versions of Optivity NMS” on page 45.

Follow the procedure below to migrate your Optivity NMS 10.2.x or 10.2.0.x database to Optivity NMS 10.3 format:

1 Login as Administrator. 2 Find the software CD marked “Optivity NMS 10.3 for Windows* CLIENT and SERVER” and insert it into the CD-ROM drive. 3 Open a command window. 4 In the command window, change to the CD drive and change directory to the \dm directory. d: cd \dm 5 In the \dm\ directory of the CD, invoke the dm.bat file: dm 6 If Optivity NMS 10.2x is currently installed, the program prompts whether you want to back up the topology database. 7 Enter Y to back up the topology database.

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 45

8 The program prompts for a directory to which to back up the database.

Note: There must be no spaces in any of the directory names in the path.

The program backs up the database to the selected directory and converts the data to Optivity NMS 10.3 format.

After you migrate your database to Optivity NMS 10.3 format, proceed to “Removing previous versions of Optivity NMS‚” next.

Removing previous versions of Optivity NMS

If you have previously installed Optivity NMS on your system, go to one of the following sections:

• If you have upgraded your Optivity NMS with maintenance release version 10.2.0.1, 10.2.0.2, or 10.2.1, go to “Removing Optivity NMS 10.2.0.1, 10.2.1, and 10.2.0.2 maintenance releases‚” next. to revert to Optivity NMS 10.2. Afterwards, go to the section “Removing Optivity NMS 10.2 and earlier software” on page 46 to remove Optivity NMS 10.2. • If your Optivity NMS version is 10.2 or earlier, and you have not upgraded to either maintenance release, go to “Removing Optivity NMS 10.2 and earlier software” on page 46.

Removing Optivity NMS 10.2.0.1, 10.2.1, and 10.2.0.2 maintenance releases

If you have upgraded your Optivity NMS with maintenance release version 10.2.0.1, 10.2.1 or 10.2.0.2, you must remove the maintenance release software to revert to version 10.2, and then remove Optivity NMS 10.2.

Follow this procedure to remove the Optivity NMS 10.2.0.1, 10.2.1 or 10.2.0.2, maintenance release software and revert to version 10.2:

1 Login in as Administrator. 2 Stop all ONMS applications. 3 Stop all platform services (in a platform system only).

Installing and Administering Optivity NMS 10.3

46 Chapter 2 Installing Optivity NMS 10.3 on Windows

4 Determine which maintenance release has been installed. Change to the directory %lnmshome% and look for subdirectories named p10201, p10202 and p1021. • If only p10201 is present, then only the 10.2.0.1 maintenance release is installed. • If both p10201 and p1021 subdirectories are present, then both the 10.2.0.1 and the 10.2.1 maintenance releases have been installed. • If only p10102 is present, then only the 10.2.0.2 maintenance release is installed. 5 Change directory (cd) to the subdirectory for the latest (numerically greatest) maintenance release. For example, if both %lnmshome%\p10201 and %lnmshome%\p1021 are present, cd to %lnmshome%\p1021 6 Run the uninstall batch file “uninstall_main.bat”. The batch file removes the Optivity NMS maintenance release software. If both the 10.2.0.1 and the 10.2.1 maintenance releases have been installed, the program prompts whether you want to revert to 10.2.0.1 or to 10.2. 7 If so prompted, choose to revert to 10.2.

After removing the maintenance release software to revert to version 10.2, proceed to “Removing Optivity NMS 10.2 and earlier software‚” next.

Removing Optivity NMS 10.2 and earlier software

Follow this procedure to remove the Optivity NMS 10.2 and earlier software:

1 Login in as Administrator. 2 On the task bar, choose Start > Programs > Optivity > Uninstall Optivity The uninstallation window opens. 3 Use the uninstallation window to remove all Optivity NMS components.

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 47

After removing the Optivity NMS 10.2 or earlier software, proceed to one of the following sections:

• If you are installing Optivity NMS on a system that will be an Optivity NMS server, go to “Installing the Oracle database software” on page 47. • If you are installing Optivity NMS on a system that will be an Optivity NMS client, go to “Installing Optivity NMS 10.3 client or server/client software” on page 51.

Installing the Oracle database software

For an Optivity NMS 10.3 server installation you install Oracle 9i, and then upgrade Oracle 9i with the 9.2.0.4 patch.

For an Optivity NMS 10.3 client-only installation, you do not need to install the Oracle database software. Proceed to the section “Installing Optivity NMS 10.3 client or server/client software” on page 51.

To install the Oracle 9i database software, go to one of the following sections:

• If the system you are installing Optivity NMS on has no Oracle database software installed, go to “Installing Oracle 9i database software” on page 47. Then go to “Installing the Oracle 9.2.0.4 patch” on page 50 to upgrade Oracle 9i with the 9.2.0.4 patch. • If Oracle 9i had been previously installed on the system, go to “Installing the Oracle 9.2.0.4 patch” on page 50 to upgrade Oracle 9i with the 9.2.0.4 patch.

Installing Oracle 9i database software

Follow this procedure to install the Oracle 9i database software.

1 Find the software CD marked “Optivity NMS 10.3 Database Installer for Windows* (1 of 3)” and insert it into the CD-ROM drive. 2 On the Windows desktop, double-click on: a My Computer b The CD drive c Setup.exe

Installing and Administering Optivity NMS 10.3

48 Chapter 2 Installing Optivity NMS 10.3 on Windows

The Optivity NMS database installation program starts (Figure 4).

Figure 4 Welcome to database installer window

3 Click Next to navigate through the installation program. As you proceed, respond to the program prompts about your system and configuration.

Note: When the program prompts you for the destination directory for the Oracle database software, Nortel Networks recommends that you use the default location of \oracle\ora92. If the folder does not exist, the installation program will offer to create it for you.

An alert box opens to say that InstallShield has checked the system requirements. 4 Click Next to continue. The installation program starts the Oracle Universal Installer to install the Oracle 9i database software (Figure 5).

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 49

Figure 5 Oracle Universal Installer window

After installing all the elements on the CD, the Oracle universal installer opens an alert box that prompts you “Please insert Oracle 9i disk 2 into your drive or specify an alternate location” (Figure 6).

Figure 6 Disk location dialog box

Installing and Administering Optivity NMS 10.3

50 Chapter 2 Installing Optivity NMS 10.3 on Windows

5 Find the software CD marked “Optivity NMS 10.3 Database Installer for Windows* (2 of 3)” and insert it into the CD-ROM drive. 6 On the alert box, change the default path from \Disk1\ to \Disk2\ and click OK. After installing all the elements on the CD, the Oracle universal installer opens an alert box that prompts you “Please insert Oracle 9i disk 3 into your drive or specify an alternate location.” 7 Find the software CD marked “Optivity NMS 10.3 Database Installer for Windows* (3 of 3)” and insert it into the CD-ROM drive. 8 On the alert box, change the default path from \Disk1\ to \Disk3\ and click OK. After installing all the elements on the CD, an alert box opens to tell you that the Oracle installation was successful. On this window, the Exit button is disabled. 9 Use the close button (the X in the upper right corner of the window) to close the alert box. The Oracle Universal Installer window closes.

After installing the Oracle 9i software, proceed to “Installing the Oracle 9.2.0.4 patch” on page 50.

Installing the Oracle 9.2.0.4 patch

You must install the Oracle 9.2.0.4 64-bit patch after installing Oracle 9i database software.

Follow these instructions to install the Oracle 9.2.0.4 patch:

1 Find the software CD marked “Optivity NMS 10.3 Database Installer for Windows* (3 of 3)” and insert it into the CD-ROM drive. 2 On the Windows desktop, double-click on: a My Computer b The CD drive c The \orapatch9204\ directory of the CD d install.bat

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 51

The Oracle 9.2.0.4 patch installation program starts. 3 Respond with the requested information if the program prompts you. If you installed Oracle 9.2 from the Optivity NMS CDs, the batch file will not prompts you for any information. Otherwise, the batch file may prompt you: • Whether you have Oracle 9.2 installed • For the directory containing the Oracle software (the default location is c:\oracle\ora92). Also, the program opens an alert box that tells you not to click Next or Cancel until the installation finishes. The installation program stops the Oracle services, and then launches the Oracle Universal Installer. The Oracle Universal Installer then installs the Oracle 9.2.0.4 patch. After installing the patch, the Oracle Universal Installer closes.

After installing the Oracle 9.2.0.4 patch, proceed to “Installing Optivity NMS 10.3 client or server/client software‚” next.

Installing Optivity NMS 10.3 client or server/client software

You have three options for installing the Optivity NMS 10.3 client or server/client software. Go to one of the following sections:

• GUI installation gives you an easy-to-use wizard-style graphic interface. Simply respond to the prompts for information about your installation. See “Using graphic interface installation‚” next for more information. • Command-line installation uses the same familiar text interface as previous Optivity NMS installations. See “Using command-line installation” on page 53 for more information. • Silent installation is a non-interactive installation procedure that you can use to automate the installation of Optivity NMS 10.3 software. See “Using silent installation” on page 53 for more information.

Installing and Administering Optivity NMS 10.3

52 Chapter 2 Installing Optivity NMS 10.3 on Windows

Using graphic interface installation

To install the Optivity NMS server/client software using the graphic interface:

Note: In the installation window, the scroll bars do not work. To scroll, click anywhere inside the window & use the arrow keys for navigation

At the end of the installation, the installation program prompts you to reboot the system. 6 Select Yes to reboot the system. The system reboots. When it starts back up, it starts the Optivity NMS services. The services take between three and five minutes to start.

After installing the Optivity NMS 10.3 client or server/client software, proceed to one of the following sections:

• If you are installing Optivity NMS on a system that will be an Optivity NMS server, go to “Installing the license key” on page 54. • If you are installing Optivity NMS on a system that will be an Optivity NMS client, you have completed the installation.

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 53

Using command-line installation

To install the Optivity NMS server/client software using the command-line interface:

1 Find the software CD marked “Optivity NMS 10.3 for Windows* CLIENT and SERVER” and insert it into the CD-ROM drive. 2 Open a command window. 3 In the command window, change to the \install directory on the CD: cd \install 4 In the command window, execute the following command: install -c 5 Respond to the installation program prompts for information about Optivity NMS components you want to install, and where you want to install them. At the end of the installation, the installation program prompts you to reboot the system. 6 Select Yes to reboot the system. The system reboots. When it starts back up, it starts the Optivity NMS services. The services take between three and five minutes to start.

After installing the Optivity NMS 10.3 client or server/client software, proceed to one of the following sections:

Using silent installation

The silent installation system uses configuration information from a text file that you provide. To use silent installation, perform the following steps:

1 Find the software CD marked “Optivity NMS 10.3 for Windows* CLIENT and SERVER” and insert it into the CD-ROM drive.

Installing and Administering Optivity NMS 10.3

54 Chapter 2 Installing Optivity NMS 10.3 on Windows

2 On the CD, find the following file and copy it to a local directory: :\install\template.rsp This text file is a template for the answer file where you specify installation parameters for Optivity NMS. 3 Edit the template to create an .rsp answer file for your installation. The elements of the answer file are described in comment text in the template. See Appendix B, “Silent Installation answer file reference,” on page 161 for more information. 4 Open a command window. 5 In the command window, change to the \install directory on the CD: cd \install 6 In the command window, execute the following command: install --silent For example: install --silent c:\temp\ONMS_silent.rsp The system reboots. When it starts back up, it starts the Optivity NMS services. The services take between three and five minutes to start.

After installing the Optivity NMS 10.3 client or server/client software, proceed to one of the following sections:

Installing the license key

Nortel Networks lets you install a 60-day evaluation copy of Optivity NMS 10.3. To continue using Optivity NMS 10.3, or if you have licensed Optivity NMS 10.3, you must install the license key on the Optivity NMS server.

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 55

The license key number is printed on a document that is included in your Optivity NMS 10.3 software kit. There are three license levels available for Optivity NMS 10.3:

You must install the license key when you:

• Install a licensed version of Optivity Campus NMS 10.3 or Optivity Enterprise NMS 10.3 • Upgrade from an evaluation copy to a licensed version of Optivity NMS 10.3

To install the license key:

1 Add the license key number to the license.dat file. For more information about installing the license key, see “Installing the Optivity NMS 10.3 license key number” on page 55. 2 Stop and then restart all of the Optivity NMS 10.3 services. For more information about starting Optivity NMS 10.3 services, see “Stopping and restarting the Optivity NMS 10.3 services” on page 56.

Installing the Optivity NMS 10.3 license key number

To install the license key number:

1 From the Windows NT or Windows 2000 task bar, choose Start > Programs > Windows Explorer. 2 Navigate to the %lnmshome%\registration\weboptsrvr\ directory. 3 Open the license.dat file in a text editor, for example Notepad.

Installing and Administering Optivity NMS 10.3

56 Chapter 2 Installing Optivity NMS 10.3 on Windows

4 Type your license key number in the file. The license key number is printed on a document that is included in your Optivity NMS 10.3 software kit. 5 In the text editor, choose File > Save. 6 Ensure that the updated file name is license.dat. Some text editors append “.txt” to every file edited, so make sure that you’re not saving the file as “license.dat.txt”.

Stopping and restarting the Optivity NMS 10.3 services

To stop and restart all of the Optivity NMS 10.3 services:

1 Open the Services dialog box, and verify that the service named OracleServicenmsdb is started. 2 Open a Command Prompt window. 3 Use this command to stop all Optivity NMS services: optivity_apps stop 4 Use this command to start all Optivity NMS services: optivity_apps start All of the services are started. 5 To verify that all of the services are started, at the command line, enter: optstatus -fe The system displays a list of services and their status. 6 Close the Services dialog box.

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 57

Installing the JRE 1.4.2_02 plug-in on Windows

In order to open Optivity NMS 10.3 applications in a browser window, you must download and install the JRE 1.4.2_02 plug-in for Internet Explorer or Netscape 7.0. If the plug-in is not installed, and you start an Optivity NMS 10.3 application in the browser, one of the following occurs:

• For Internet Explorer 6.0—You are prompted to download the j2re*-i586-p.exe executable from the Optivity server. • For Netscape 7.0—You are prompted to install the plug-in. If you agree, the link takes you to an Optivity plug-in install Web page. On that page, click the link to the Nortel Networks support web page from which you can download the plug-in.

In either case, you must install the plug-in and restart the browser. See “Installing the plug-in for Internet Explorer‚” next and “Installing the plug-in for Netscape 7.0” on page 58 for more information.

Installing the plug-in for Internet Explorer

To install the plug-in for JRE 1.4.2_02 on Microsoft Internet Explorer:

1 Start Internet Explorer. 2 Enter the IP address or host name of the Optivity server. For example, enter one of the following: • http://OptivityNMS • http://10.127.50.15 • http://localhost The Optivity NMS applications and administrative tools page opens. 3 Click an Optivity NMS application, for example, InfoCenter. If the plug-in is not installed on your system, you are prompted to download the j2re*-i586-p.exe file. 4 Download j2re*-i586-p.exe. 5 Double-click j2re*-i586-p.exe to install it. The file is installed. You are prompted to associate the plug-in with the Internet Explorer 6.0.

Installing and Administering Optivity NMS 10.3

58 Chapter 2 Installing Optivity NMS 10.3 on Windows

6 Select the box to associate the plug-in with Internet Explorer. 7 Restart the browser after the plug-in is installed.

Note: When you connect to an HP-UX Optivity NMS server from Internet Explorer, download the j2re*-i586-p.exe file from the following URL: http://www130.nortelnetworks.com/cgi-bin/eserv/cs/ main.jsp?cscat=swdetail&SoftwareOID=275170 After opening this URL, click on the link “Windows Java RTE Plug-in for Optivity NMS 10.3” to download the plug-in.

Installing the plug-in for Netscape 7.0

To install the plug-in for JRE 1.4.2_02:

1 Start Netscape 7.0. 2 Enter the IP address or host name of the Optivity server. For example, enter one of the following: • http://OptivityNMS • http://10.127.50.15 • http://localhost The Optivity NMS applications and administrative tools page opens. 3 Click an Optivity NMS application, for example, InfoCenter. If the plug-in is not installed on your system, you are prompted to install the plug-in. 4 Click the button to accept and download the file. The system opens the Optivity plug-in install web page. 5 Click Plug-in for Windows. The system opens the Nortel Networks support web page that contains the downloadable Java Runtime plug-in. 6 Click on “Windows Java RTE Plug-in for Optivity NMS 10.3”.

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 59

7 The system downloads j2re*-i586-p.exe from the Nortel Networks support web page. 8 Save the file. 9 Double-click j2re*-i586-p.exe to install the plug-in. 10 Restart the browser after the plug-in is installed.

Note: If the link on the Optivity NMS plug-in installation web page does not work, download the JRE plug-in from the following URL: http://www130.nortelnetworks.com/cgi-bin/eserv/cs/ main.jsp?cscat=swdetail&SoftwareOID=275170

Postinstallation notes

Table 5 describes postinstallation issues that you might need to address after you have installed Optivity NMS 10.3 software.

Table 5 Postinstallation notes for the Windows environment

Subject Issue Community Strings Use the Optivity NMS Community Strings Editor to manage SNMP community strings and configure SNMPv3 user security settings when Optivity NMS is installed as a standalone network management system (platformless). However, if you are integrating Optivity NMS with a third-party network management platform such as HP OpenView Network Node Manager or Tivoli NetView, Optivity NMS uses the community strings of the platform software. Discovery process Allow enough time for Autotopology Manager to complete the discovery process. Wait until you see the message Router and Subnet Discovery is Complete displayed in the Autotopology Manager window before you close the window. Failure to do so results in an incomplete discovery.

Installing and Administering Optivity NMS 10.3

60 Chapter 2 Installing Optivity NMS 10.3 on Windows

Uninstalling Optivity NMS 10.3

The following sections describe how to uninstall Optivity NMS 10.3 components:

• “Uninstalling Optivity NMS 10.3 client/server applications‚” next • “Uninstalling Optivity NMS database Installer” on page 61

Uninstalling Optivity NMS 10.3 client/server applications

This section describes how to uninstall Optivity NMS 10.3 applications from your Windows network management station.

To uninstall Optivity NMS 10.3:

1 Reboot the system. This action stops any back end processes that might be running. 2 Log in with local administrator privileges. 3 From the Windows task bar choose Start > Settings > Control Panel > Add/ remove programs. The Add/Remove Programs window opens. 4 In the list of currently installed programs, choose Optivity NMS 10.3 and click Change/Remove. The Optivity NMS 10.3 Uninstallation window opens. 5 Select the Optivity NMS 10.3 component(s) that you want to uninstall. If the Optivity NMS legacy applications are installed, they are automatically removed. 6 Click Remove. The Uninstall validation window opens. Confirm the Optivity NMS 10.3 component(s) that you want to uninstall. 7 Click Next.

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 61

8 Determine whether or not you want to back up the Optivity NMS 10.3 database. • If you click Yes, you can back up the Optivity NMS 10.3 database to: — The default location at: c:\opt\bay\install\customizations — A location of your choosing. • If you click No, your Optivity NMS 10.3 database is discarded, but your customization data is still automatically backed up to the directory: c:\opt\bay\install\customizations The Uninstall program stops the Web server and uninstalls the Optivity NMS 10.3 Server and Optivity NMS 10.3 client software, and the Optivity NMS 10.3 database. When the uninstall process is complete, a message box opens asking you whether or not you want to restart your computer. 9 Do one of the following: • Click Yes to restart your computer immediately. • Click No to restart your computer later. Restarting your network management station removes files that were in use during the uninstall process and cleans up the registry.

Uninstalling Optivity NMS database Installer

To remove the Optivity NMS Database Installer:

1 Login as Administrator. 2 From the Windows task bar choose Start > Settings > Control Panel > Add/ remove programs. The Add/Remove Programs window opens. 3 In the list of currently installed programs, choose Optivity NMS Database Installer and click Change/Remove. The Confirm File Deletion dialog box (Figure 7) opens to prompt whether you want to completely remove the application.

Installing and Administering Optivity NMS 10.3

62 Chapter 2 Installing Optivity NMS 10.3 on Windows

Figure 7 Confirm file deletion dialog box

4 Click OK. The database installer product and registry entries are removed. Then the Oracle Inventory window opens (Figure 8).

Figure 8 Oracle inventory window

205969-H

Chapter 2 Installing Optivity NMS 10.3 on Windows 63

5 Use the Inventory window to select all Oracle database software components and click Remove. An alert box prompts you to confirm that you want to remove the selected components. 6 Click Yes to confirm. 7 After removing all of the components, click Close. The Oracle Universal Installer window closes.

Installing and Administering Optivity NMS 10.3

64 Chapter 2 Installing Optivity NMS 10.3 on Windows

205969-H

65 Chapter 3 Installing Optivity NMS 10.3 on Solaris

This chapter describes how to install Optivity NMS 10.3 on Solaris. Additionally, this chapter describes how to uninstall Optivity NMS 10.3.

The following sections describe how to install Optivity NMS 10.3 on Solaris:

• “Solaris system requirements‚” next • “Installation procedures” on page 72 • “Postinstallation notes” on page 89

Solaris system requirements

Before you install Optivity NMS 10.3 on Solaris, ensure that the network management station(s) upon which you install the client and server software meet(s) the recommended system requirements defined in Table 6 and Table 7.

Installing and Administering Optivity NMS 10.3

66 Chapter 3 Installing Optivity NMS 10.3 on Solaris

Solaris platform and browser requirements

Table 6 Optivity NMS 10.3 client/server minimum system requirements for Solaris

Optivity NMS Server Optivity NMS client

Network management Operating Web browser1 and platform environment Operating system plug-in HP OpenView CDE Solaris 2.8, Windows 98, Win- Netscape* 7.0.1 dows NT 4.0 workstation, Win- Navigator* 7.0 and dows XP, Windows 2000 Java 2 version Professional 1.4.2_022 TME 10 NetView CDE Solaris 2.8, Windows 98, Win- Netscape 7.1.4 dows NT 4.0 workstation, Win- Navigator 7.0 dows XP, Windows 2000 Java 2 version 1.4.2_02 Professional Platformless N/A Solaris 2.8, Windows 98, Win- Netscape dows NT 4.0 workstation, Win- Navigator 7.0 dows XP, Windows 2000 Microsoft Internet Professional Explorer 6.0

1 The Internet Explorer 6.0 Web browser is not supported in the UNIX environment. 2 The Java 2 version 1.4.2_02 plug-in is required for Netscape Navigator 7.0. See “Installing the JRE 1.4.2_02 plug-in on Solaris” on page 87 for more information.

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 67

Solaris system requirements

Table 7 Solaris system requirements

Topic Consideration Hardware Recommended processor, RAM, hard drive: • Large network (10000 managed IP interfaces): SunFire V240 or Sun 2000; 1.2 Ghz processor, 2 Gb RAM, 20 Gb hard drive • Medium network (5000 managed IP interfaces): Sun 2000 or Ultra 60, 900 Mhz processor, 2 Gb RAM, 20 Gb hard drive • Small network (500 managed IP interfaces): Ultra 60, 512 Mhz processor, 2 Gb RAM, 15 Gb hard drive Minimum partition sizes • Oracle software 3 GB • Optivity NMS software 1 GB • Optivity NMS database 10 GB Swap space Three times the amount of Physical Memory for Swap space (unless the system exceeds 1 GB of Physical Memory, where two times the amount of Physical Memory for Swap space is sufficient) To check: $ /usr/sbin/swapinfo -a Solaris operating system Solaris 2.8 (64-bit): Update 5 (07/02) http://sunsolve.sun.com patches Determining Installed Patches: $ showrev -p Supported shells Optivity NMS only supports the following UNIX shells: • Bourne shell (sh) • c-shell (csh) • korn shell (ksh) Operating system • Solaris Packages: requirements — SUNWarc — SUNWbtool — SUNWhea — SUNWlibm — SUNWlibms — SUNWsprot — SUNWtoo. • X-windows must be installed on the system from where the installer is run. Use any Sun-supported X-windows server (dtwm, twm, olwm) that supports Motif.

Installing and Administering Optivity NMS 10.3

68 Chapter 3 Installing Optivity NMS 10.3 on Solaris

Table 7 Solaris system requirements (continued)

Topic Consideration Solaris Font Packages SUNWi1of and SUNWxwfnt are required for all locations. You for Java may need to obtain additional font packages to support font styles used at your location. Refer to the following Web site for a listings of Solaris font packages: http://java.sun.com/j2se/1.3/font-requirements.html $ pkginfo -i os_package Required executables The following executables must be present in the /usr/ccs/bin directory: •make •ar •ld •nm Use the which command to determine if you are using the correct system executables, for example: # which ld /usr/ccs/bin/ld On Solaris, if the commands are not present, add /usr/ccs/bin to the beginning of the PATH environment variable in the current shell. If you require /usr/ucb in your search path, make sure it comes after /usr/ccs/bin in the PATH settings. Language Optivity NMS only supports English-language installations of Solaris.

Solaris / HP OpenView Patches

In order to integrate Optivity NMS 10.3 with HP OpenView version 7.0.1 on Solaris 2.8, the following HP OpenView patches must be installed:

Table 8 Solaris/HP OpenView patches

Patch number Description 108652-56 # X11 6.4.1: Xsun patch 108921-15 # CDE 1.4: dtwm patch 112003-03 # SunOS 5.8: Unable to load fontset in 64-bit Solaris 8 iso-1 or iso-15 108773-15 # SunOS 5.8: IIIM and X Input & Output Method patch 111293-04 # SunOS 5.8: /usr/lib/libdevinfo.so.1 patch 111310-01 # SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 69

Table 8 Solaris/HP OpenView patches (continued)

Patch number Description 112472-01 # SunOS 5.8: Font2DTest2 abort when Lucida Sans Thai Typewriter selected 108714-07 # CDE 1.4: libDtWidget patch 111111-03 # SunOS 5.8: /usr/bin/nawk patch 112396-02 # SunOS 5.8: /usr/bin/fgrep patch 108940-46 # Motif 1.2.7 and 2.1.1: Runtime library patch for Solaris 8 108987-09 # SunOS 5.8: Patch for patchadd and patchrm 108528-15 # SunOS 5.8: kernel update patch 108989-02 # SunOS 5.8: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch 108827-26 # SunOS 5.8: /usr/lib/libthread.so.1 patch

Pre-installation notes

Nortel Networks strongly recommends that you review the information in Table 9 to ensure that the listed requirements are met before you install or uninstall Optivity NMS 10.3.

Table 9 Pre-installation notes for Solaris

Topic Consideration System administration The Oracle and Optivity NMS 10.3 installation must be requirements performed by a user that has root access permission. License key Licensed software—If you install licensed software, you need to have the license key available. Your license key is available on your Optivity NMS 10.3 license key document. For more information about installing the license key on UNIX see “Installing the license key” on page 85. Operational conflicts Operational conflicts are: Versalar* port 80—For more information about the operational conflict between Optivity NMS 10.3 and Versalar port 80, see “Versalar Config Utility http port 80 conflict” on page 182. Network Node Manager—For more information about the operational conflict between Site Manager and Network Node Manager, see “Site Manager and Network Node Manager port 161 conflict” on page 183.

Installing and Administering Optivity NMS 10.3

70 Chapter 3 Installing Optivity NMS 10.3 on Solaris

Table 9 Pre-installation notes for Solaris (continued)

Topic Consideration Network Management The network management platform daemons must be running platform daemons before you start the Optivity NMS 10.3 installation. See “Setting up the platform environment” on page 70 for more information. Total disk space When you install the Optivity NMS 10.3 client/server software, the Welcome to Optivity NMS 10.3 Installation window may not display the total disk space requirement. Refer to “Solaris system requirements” on page 65. Port 80 assignment If a pre-installed Apache Web server is bound to port 80, during installation you can choose a different port, for example, port 8580, for Optivity NMS 10.3. UNIX Term settings Before installing Optivity NMS 10.3, make sure that the setting of the environment variable TERM is something that is defined in /etc/termcap such as xterm or vt100. Otherwise, the installation will fail. (CR Q00514083) Read-only File System You cannot install Optivity NMS 10.3 on a read-only file system. If you attempt such an installation using the graphical installation program, clicking Next does not advance to the next screen. Instead, it adds one iteration of the text “\lnms” to the installation location text box for each click on the Next button. (CR Q00838436)

Setting up the platform environment

If you are using a platform manager (Network Node Manager or NetView), Nortel Networks recommends that you first set up the network management platform environment before installing Optivity NMS.

In summary, the Optivity NMS installation requires the following:

• Network management platform is installed • Network management platform patches (as required) are installed • Network management platform is configured, all daemons are up and running; and the environment variables for the network management platform are set, including the $DISPLAY variable

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 71

For detail instructions on how to perform the required steps, Nortel Networks recommends that you see the appropriate network management platform installation and configuration guide.

Nortel Networks recommends that you configure the universal path names into your environment by running the appropriate script or by adding the line to your login start-up file (.cshrc or .profile):

See “Setting up the Network Node Manager platform environment, next or “Setting up the NetView platform environment” on page 71 for more information.

Setting up the Network Node Manager platform environment

To set up the Network Node Manager network management platform environment, do one of the following:

• For the Korn shell, edit the .profile file to include the following: PATH=$PATH:/opt/OV/bin export PATH . /opt/OV/bin/ov.envvars.sh • For the C shell, edit $HOME/.cshrc to include the following: set path= ( $path /opt/OV/bin ) source /opt/OV/bin/ov.envvars.csh

Setting up the NetView platform environment To set up the NetView network management platform environment:

cd /usr/OV/bin ./NVenvironment

Nortel Networks recommends that you see the Network Node Manager or NetView installation guide for more information.

Installing and Administering Optivity NMS 10.3

72 Chapter 3 Installing Optivity NMS 10.3 on Solaris

Installation procedures

This section is divided into the following major sections. You perform some or all of the procedures in these sections to install Optivity NMS 10.3:

• “Installation flow chart for Solaris‚” next • “Migrating the Optivity NMS 10.2.x database” on page 74 • “Removing previous versions of Optivity NMS” on page 76 • “Installing the Oracle database software” on page 78 • “Installing Optivity NMS 10.3 client or server/client software” on page 81 • “Modifying Optivity NMS user login scripts” on page 84 • “Installing the license key” on page 85 • “Installing the JRE 1.4.2_02 plug-in on Solaris” on page 87 • “Optivity NMS installation on NFS-mounted file systems” on page 88

Table 11 describes where to start installing Optivity NMS 10.3, depending on the type of installation and whether you are upgrading from a previous release of Optivity NMS. At the end of each section there are instructions on which procedure to do next, depending on your installation type.

Table 10 Starting Optivity NMS installation on Solaris

If you have this Optivity NMS And you want to install the And you want to install the version currently installed: Optivity NMS Server/Client Optivity NMS Client-only software: software: None Go to “Installing the Oracle database Go to “Installing Optivity NMS 10.3 software” on page 78 client or server/client software” on page 81 Any of: • To preserve your Optivity NMS Go to “Removing previous versions • 10.2 10.2x database, go to “Migrating of Optivity NMS” on page 76 the Optivity NMS 10.2.x • 10.2.0.x database” on page 74 • 10.2.x • If you don’t need to preserve your Optivity NMS 10.2x database, go to “Removing previous versions of Optivity NMS” on page 76 10.1 or prior Go to “Removing Optivity NMS 10.2 and earlier software” on page 77

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 73

Installation flow chart for Solaris

The flow chart in Figure 9 shows an overall view of the procedures for installing Optivity NMS 10.3 on Solaris.

Figure 9 Installation procedure overview, Solaris

Start

Client-only Installation type Server/client

ONMS version 10.1 or ONMS version 10.1 or 10.2.x installed? 10.2x earlier installed? earlier None ONMS version Yes (10.2.0.x or None Yes (10.2.0.x or 10.2.1 installed) Patched? 10.2.1 installed) Uninstall old installed? Uninstall old Optivity NMS Remove patch to Optivity NMS Preserve 10.2 revert to 10.2 No topology Ye s database? Do data migration Uninstall No procedure version 10.2

Remove patch to revert to 10.2

Uninstall version 10.2

Oracle 9i No installed?

Ye s Install Oracle 9i

Install Oracle 9.2.0.4 patch

GUI Installation (easiest) option Silent Command line Create answer “install” “install -c” file

answer answer “install --silent prompts prompts ”

Installation Server/client type? Install Client-only license key

End

Installing and Administering Optivity NMS 10.3

74 Chapter 3 Installing Optivity NMS 10.3 on Solaris

Migrating the Optivity NMS 10.2.x database

You can skip this procedure if:

In either of these cases, skip ahead to “Removing previous versions of Optivity NMS” on page 76.

Follow the procedure below to migrate your Optivity NMS 10.2.x or 10.2.0.x database to Optivity NMS 10.3 format:

1 Login as root. 2 Find the software CD marked “Optivity NMS 10.3 for Solaris CLIENT and SERVER” and insert it into the CD-ROM drive. 3 Open a terminal window. 4 At the command , enter: xhost + 5 From your local UNIX workstation, log into the system where you will run Oracle Universal Installer. 6 Set the DISPLAY variable to the system name or IP address, X-server, and screen used by your workstation. Do not use the host name or IP address of the system where the software is being installed, unless you are performing the installation from that system's X-windows console. Use the machine name or IP of your own workstation if you are installing from a remote system. If you are not sure what the X-server and screen should be set to, use 0 (zero) for both.

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 75

7 Do one of the following: • For the Bourne or Korn shell, enter: DISPLAY=[| ];export DISPLAY • For the C shell, enter: setenv DISPLAY [| ] 8 In the terminal window, change to the CD drive and change directory to the dm directory. cd cdrom/dm 9 In the /dm directory of the CD, invoke the dm.bat file: dm 10 If Optivity NMS 10.2x is currently installed, the program prompts whether you want to back up the topology database. 11 Enter Y to back up the topology database. 12 The program prompts for a directory to which to back up the database.

Note: There must be no spaces in any of the directory names in the path.

The program backs up the database to the selected directory and converts the data to Optivity NMS 10.3 format.

After you migrate your database to Optivity NMS 10.3 format, proceed to “Removing previous versions of Optivity NMS‚” next.

Installing and Administering Optivity NMS 10.3

76 Chapter 3 Installing Optivity NMS 10.3 on Solaris

Removing previous versions of Optivity NMS

If you have previously installed Optivity NMS on your system, go to one of the following sections:

• If you have upgraded your Optivity NMS with maintenance release version 10.2.0.1, 10.2.0.2, or 10.2.1, go to “Removing Optivity NMS 10.2.0.1, 10.2.1, and 10.2.0.2 maintenance releases‚” next. to revert to Optivity NMS 10.2. Afterwards, go to the section “Removing Optivity NMS 10.2 and earlier software” on page 77 to remove Optivity NMS 10.2. • If your Optivity NMS version is 10.2 or earlier, go to “Removing Optivity NMS 10.2 and earlier software” on page 77.

Removing Optivity NMS 10.2.0.1, 10.2.1, and 10.2.0.2 maintenance releases

Follow this procedure to remove the Optivity NMS 10.2.0.1, 10.2.1 or 10.2.0.2, maintenance release software and revert to version 10.2:

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 77

6 Determine which maintenance release has been installed: In the /opt/bay/install directory, look for files named uninstall10101 and uninstall10102 • If only uninstall10201 is present, then only the 10.2.0.1 maintenance release is installed. • If both uninstall10201 and uninstall1021 files are present, then both the 10.2.0.1 and the 10.2.1 maintenance releases have been installed. • If only uninstall10202 is present, then only the 10.2.0.2 maintenance release is installed. 7 Execute the latest (numerically greater) maintenance release uninstallation program. For example, if both uninstall10201 and uninstall1021 are present, run uninstall1021: ./uninstall1021 The batch file removes the Optivity NMS maintenance release software. If both the 10.2.0.1 and the 10.2.1 maintenance releases have been installed, the program prompts whether you want to revert to 10.2.0.1 or to 10.2. 8 If so prompted, choose to revert to 10.2. 9 Restart all NMS platform daemons (in a platform system only). 10 Start all Optivity NMS daemons using the “optivity_apps start” command. 11 Run the command “optstatus -fe” to ensure that all Optivity NMS daemons are running.

After removing the maintenance release software to revert to version 10.2, proceed to “Removing Optivity NMS 10.2 and earlier software‚” next.

Removing Optivity NMS 10.2 and earlier software

Follow this procedure to remove the Optivity NMS 10.2 and earlier software:

1 Login in as root. 2 CD to the /opt/bay/install directory 3 Invoke the following script: ./uninstall

Installing and Administering Optivity NMS 10.3

78 Chapter 3 Installing Optivity NMS 10.3 on Solaris

The script uninstalls Optivity NMS. Respond to the prompts as appropriate.

After removing the Optivity NMS 10.2 or earlier software, proceed to one of the following sections:

• If you are installing Optivity NMS on a system that will be an Optivity NMS server, go to “Installing the Oracle database software‚” next. • If you are installing Optivity NMS on a system that will be an Optivity NMS client, go to “Installing Optivity NMS 10.3 client or server/client software” on page 81.

Installing the Oracle database software

For an Optivity NMS 10.3 server installation install Oracle 9i, and then upgrade Oracle 9i with the 9.2.0.4 patch.

To install the Oracle 9i database software, go to one of the following sections:

• If the system you are installing Optivity NMS on has no Oracle database software installed, go to “Installing Oracle 9i database software” on page 78. Then go to “Installing the Oracle 9.2.0.4 patch” on page 80 to upgrade Oracle 9i with the 9.2.0.4 patch. • If Oracle 9i had been previously installed on the system, go to “Installing the Oracle 9.2.0.4 patch” on page 80 to upgrade Oracle 9i with the 9.2.0.4 patch.

Installing Oracle 9i database software

Follow this procedure to install the Oracle 9i database on a Solaris system:

1 Find the software CD marked “Optivity NMS 10.3 Database Installer for Solaris (1 of 4).” and insert it into the CD-ROM drive.

Note: Inserting the CD causes Solaris to open a file manager window for the CD. Do not use this window to start the installation. Use a terminal window as described in this procedure.

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 79

2 In a terminal window, execute the following command to change to the root directory: cd / 3 Execute the following command to start the installation program: /cdrom/cdrom0/install

Note: Execute the command from the root directory. Do not cd to the /cdrom directory. Doing so would interfere with your ability to eject the CD when required.

The installation program prompts you: Provide a directory to unpack Disk2 (620 Mb minimum) [/] : 4 Enter the name of the directory with at least 620 MB of free space. The installation program copies the contents of the Oracle 1 CD to the directory, and then prompts you to insert the Oracle 2 CD: Insert Oracle CD # 2 5 Open a second terminal window and use the eject command to eject the first CD: eject 6 Insert the CD marked “Optivity NMS 10.3 Database Installer for Solaris (2 of 4)” into the CD-ROM drive. The installation program prompts you for the path to the Disk3 directory on the CD: Enter path to Disk3 [/cdrom/cdrom0/Products/Oracle/9.2/ distribution]: 7 Enter the name of the directory. On the CD, the directory is /cdrom/cdrom0/Products/Oracle/9.2/distribution The installation program prompts you: Provide a directory to unpack Disk3 (500 Mb minimum) [/] : 8 Enter the name of the directory with at least 500MB of free space.

Installing and Administering Optivity NMS 10.3

80 Chapter 3 Installing Optivity NMS 10.3 on Solaris

The installation program copies the contents of the Oracle 2 CD to the directory, and then prompts you to insert the Oracle 3 CD: Insert Oracle CD # 3 to continue with Oracle install 9 Eject the first CD as described in step 5 and insert the CD marked “Optivity NMS 10.3 Database Installer for Solaris (3 of 4).” into the CD-ROM drive. 10 Use the cd command to change to the following directory on the CD: cd /cdrom/cdrom0 11 Execute the following command to run the pre-installation check of system parameters: ./preinstall -i 12 Respond to the installation program prompts for information about the Oracle installation. If the preinstallation check reports any anomalies in your system configuration, resolve them and then proceed with the installation. 13 Execute the following command: ./install The installation program installs the Oracle database software on the system. At the end of the installation, the program prompts you to install the Oracle 9.2.0.4 patch: Insert Oracle CD # 4 to proceed with Oracle 9.2.0.4 patch install

After installing the Oracle 9i software, proceed to “Installing the Oracle 9.2.0.4 patch‚” next.

Installing the Oracle 9.2.0.4 patch

You must install the Oracle 9.2.0.4 64-bit patch after installing Oracle 9i database software. Follow these instructions to install the Oracle 9.2.0.4 patch:

1 Log in as root. 2 Insert the CD marked “Optivity NMS 10.3 Database Installer for Solaris (4 of 4).”

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 81

3 Use the following commands to run the patch installer script from the /cdrom directory: cd /cdrom/cdrom0 ./install_patch The script installs Oracle Universal Installer 2.2.0.18.0 followed by Oracle9iR2 Server PatchSet 9.2.0.4.0 4 Press the Return key when prompted by the script 5 Press 'y' key to continue with Post-installation tasks. Post-installation runs SQL scripts in the database. This process takes about 20 minutes.

At the end of installation database server and all Optivity NMS apps are running.

After installing the Oracle 9.2.0.4 patch, proceed to “Installing Optivity NMS 10.3 client or server/client software‚” next.

Installing Optivity NMS 10.3 client or server/client software

You have three options for installing the Optivity NMS 10.3 client or server/client software. Go to one of the following sections:

• GUI installation gives you an easy-to-use wizard-style graphic interface. Simply respond to the prompts for information about your installation. See “Using graphic interface installation‚” next for more information. • Command-line installation uses the same familiar text interface as previous Optivity NMS installations. See “Using command-line installation” on page 82 for more information. • Silent installation is a non-interactive installation procedure that you can use to automate the installation of Optivity NMS 10.3 software. See “Using silent installation” on page 83 for more information.

Using graphic interface installation

To install the Optivity NMS server/client software using the graphic interface:

1 Find the software CD marked “Optivity NMS 10.3 for Solaris CLIENT and SERVER” and insert it into the CD-ROM drive.

Installing and Administering Optivity NMS 10.3

82 Chapter 3 Installing Optivity NMS 10.3 on Solaris

2 Use the following command to change to the install directory on the CD: cd /cdrom/cdrom0/install 3 In a terminal window, execute the following command: ./install 4 Respond to the installation program prompts for information about Optivity NMS components you want to install, and where you want to install them.

Note: In the installation window, the scroll bars do not work. To scroll, click anywhere inside the window & use the arrow keys for navigation

After installing the Optivity NMS 10.3 client or server/client software, proceed to one of the following sections:

• If you are installing Optivity NMS on a system that will be an Optivity NMS server, go to “Installing the license key” on page 85. • If you are installing Optivity NMS on a system that will be an Optivity NMS client, go to “Installing the JRE 1.4.2_02 plug-in on Solaris” on page 87.

Using command-line installation

To install the Optivity NMS server/client software using the graphic interface:

1 Find the software CD marked “Optivity NMS 10.3 for Solaris CLIENT and SERVER” and insert it into the CD-ROM drive. 2 Use the following command to change to the install directory on the CD: cd /cdrom/cdrom0/install 3 In a terminal window, execute the following command: ./install -c 4 Respond to the installation program prompts for information about Optivity NMS components you want to install, and where you want to install them. The installation program installs Optivity NMS according to the parameters in the answer file and then starts the Optivity NMS daemons. The daemons take between three and five minutes to start.

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 83

After installing the Optivity NMS 10.3 client or server/client software, proceed to one of the following sections:

Using silent installation

The silent installation system uses configuration information from a text file that you provide. To use silent installation, perform the following steps:

1 Find the software CD marked “Optivity NMS 10.3 for Solaris CLIENT and SERVER” and insert it into the CD-ROM drive. 2 On the CD, find the following file and copy it to a local directory: /cdrom/cdrom0/install/template.rsp This text file is a template for the answer file where you specify installation parameters for Optivity NMS. 3 Edit the template to create an .rsp answer file for your installation. The elements of the answer file are described in comment text in the template. See Appendix B, “Silent Installation answer file reference,” on page 161 for more information. 4 Use the following command to change to the install directory on the CD: cd /cdrom/cdrom0/install 5 Run the install program with the silent option: # ./install --silent For example: # ./install --silent /tmp/onms_silent.rsp The installation program installs Optivity NMS according to the parameters in the answer file and then starts the Optivity NMS daemons. The daemons take between three and five minutes to start.

Installing and Administering Optivity NMS 10.3

84 Chapter 3 Installing Optivity NMS 10.3 on Solaris

After installing the Optivity NMS 10.3 client or server/client software, proceed to one of the following sections:

Modifying Optivity NMS user login scripts

For an Optivity NMS 10.3 server installation, you must modify each Optivity NMS user’s login script.

Using vi or another text editor, add the following lines to each Optivity NMS user's login script:

• For the C shell, add the following lines to the .cshrc file: umask 022 if ( -f /opt/lnms/bin/opt_cshrc ) then source /opt/lnms/bin/opt_cshrc endif • For the Korn shell, add the following lines to the .kshrc file: umask 022 if [ -f /opt/lnms/bin/opt_kshrc ];then . /opt/lnms/bin/opt_kshrc fi • For the Bourne shell, add the following lines to the .profile file: umask 022 if [ -f /opt/lnms/bin/opt_kshrc ];then . /opt/lnms/bin/opt_kshrc fi

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 85

After modifying the Optivity NMS 10.3 user login scripts, proceed to one of the following sections:

Installing the license key

The license key number is printed on a document that is included in your Optivity NMS 10.3 software kit. There are three license levels available for Optivity NMS 10.3:

You must install the license key when you:

• Install a licensed version of Optivity Campus NMS 10.3 or Optivity Enterprise NMS 10.3 • Upgrade from an evaluation copy to a licensed version of Optivity NMS 10.3

To install the license key:

1 Add the license key number to the license.dat file. For more information about installing the license key, see “Installing the Optivity NMS 10.3 license key number‚” next. 2 Stop and restart all of the Optivity NMS 10.3 daemons.

Installing and Administering Optivity NMS 10.3

86 Chapter 3 Installing Optivity NMS 10.3 on Solaris

For more information about starting Optivity NMS 10.3 services, see “Stopping and restarting Optivity NMS 10.3 daemons” on page 86.

Installing the Optivity NMS 10.3 license key number

To install the license key number:

1 Login as root. 2 Create or open the following file in a text editor: /usr/lnms/registration/weboptsrvr/license.dat To open the file using vi, enter: vi /usr/lnms/registration/weboptsrvr/license.dat 3 Type the Optivity Enterprise NMS 10.3 license key in the file. 4 Use the :wq! command to save the file and exit vi.

Stopping and restarting Optivity NMS 10.3 daemons

To stop and restart all Optivity NMS 10.3 daemons:

1 Login as root. 2 Open a UNIX terminal window. 3 Set the environment: • For the C shell: source /opt/lnms/bin/opt_cshrc • For the Korn shell: . /opt/lnms/bin/opt_kshrc • For the Bourne shell: . /opt/lnms/bin/opt_kshrc 4 Stop the daemons with this command: optivity_apps stop 5 Restart the daemons with this command: optivity_apps start

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 87

6 To verify that daemons started, enter: optstatus -fe

Installing the JRE 1.4.2_02 plug-in on Solaris

In order to open Optivity NMS 10.3 applications in a browser window, you must download and install the JRE 1.4.2_02 plugin for Netscape 7.0. If the plug-in is not installed, and you start an Optivity NMS 10.3 application in the browser, you are prompted to install the plug-in. If you agree, the link opens an Optivity plug-in install Web page, where you click a link to go to the Nortel Networks support web page from which you can download the plug-in.

To install the JRE 1.4.2_02 plugin for Netscape 7.0:

1 Start Netscape 7.0. 2 Enter the IP address or host name of the Optivity server. For example, enter one of the following: • http://OptivityNMS • http://10.127.50.15 • http://localhost The Optivity NMS applications and administrative tools page opens. 3 Click an Optivity NMS application, for example, InfoCenter. If the plug-in is not installed on your system, the program prompts you to install the plug-in. 4 Click the button to accept and download the file. The system opens the Optivity NMS plug-in installation page. 5 Click the Plug-in for Solaris. The system opens the Nortel Networks support web page which contains the downloadable Java Runtime plug-in. 6 Click on “Solaris Java RTE Plug-in for Optivity NMS 10.3” The browser downloads the file j2re*-solaris-sparc.sh from the Nortel Networks support web page. 7 Save the file.

Installing and Administering Optivity NMS 10.3

88 Chapter 3 Installing Optivity NMS 10.3 on Solaris

8 Run j2re*-solaris-sparc.sh from the shell to install the plug-in. Make sure that the .sh file has executable permissions set. 9 Find the directory where netscape is installed by entering: which netscape The system responds with the directory where Netscape is installed. 10 Change to the directory where netscape is installed: cd /plugins 11 If the directory contains the soft link file libjavaplugin_oji.so, delete the file and create a soft link to the newly installed Java plug-in by entering: ln -s /plugin/ sparc/ns610/libjavaplugin_oji.so libjavaplugin_oji.so 12 Restart the browser.

Optivity NMS installation on NFS-mounted file systems

If you install Optivity NMS and/or Oracle on an NFS-mounted filesystem, you must modify the following http configuration files in order to make the Apache Web server work properly:

•//app/oracle/products/8.1.7/Apache/Apache/conf/httpd.conf •//opt/optivity/nms/lnms/apache/conf/httpd.conf

To modify the files:

1 Create a file anywhere on your local drive called httpd.lock, for example: /opt/lock/httpd.lock

205969-H

Chapter 3 Installing Optivity NMS 10.3 on Solaris 89

2 For each of the http configuration files, make the following modifications: a Find the line that contains the LockFile directive. The default settings for the LockFile directive are: • #LockFile $oraclehome/Apache/Apache/logs/httpd.lock (Oracle) • #LockFile /nms/base/products/apache/logs/httpd.lock (Optivity) b Change the LockFile directive to uncomment it and point to the local httpd.lock file, for example: LockFile /opt/lock/httpd.lock 3 Use the following commands to stop and start the Optivity NMS and Oracle daemons: optivity_apps stop optivity_apps start

Postinstallation notes

Table 11 describes postinstallation issues that you might need to address after you have installed Optivity NMS 10.3 software.

Table 11 Postinstallation notes for the Windows environment

Installing and Administering Optivity NMS 10.3

90 Chapter 3 Installing Optivity NMS 10.3 on Solaris

205969-H

91 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

The following sections describe how to install Optivity NMS 10.3 on HP-UX:

• “Checking system prerequisites‚” next • “Installation procedures” on page 99 • “Postinstallation notes” on page 120

Checking system prerequisites

Before you install Optivity NMS 10.3, ensure that the network management station(s) upon which you install the server and the client meet(s) the recommended system requirements defined in Table 12.

Table 12 HP-UX System requirements

Requirement Description Hardware Recommended processor, RAM, hard drive: • Large network (10000 managed IP interfaces): HP-UX (PA-RISC) C-series, 552 Mhz processor, 2 Gb RAM, 20 Gb hard drive • Medium network (5000 managed IP interfaces): HP-UX (PA-RISC) C-series, 552 Mhz processor, 2 Gb RAM, 20 Gb hard drive • Small network (500 managed IP interfaces): HP-UX (PA-RISC) C-series, 400 Mhz processor, 2 Gb RAM, 15 Gb hard drive Memory A minimum of 512 MB of RAM is required to install Oracle9i Server To check: $ grep MemTotal /proc/meminfo Minimum parti- • Oracle software 3 GB tion sizes • Optivity NMS software 1 GB • Optivity NMS database 10 GB

Installing and Administering Optivity NMS 10.3

92 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

Table 12 HP-UX System requirements (continued)

Requirement Description Swap space Three times the amount of Physical Memory for Swap space (unless the system exceeds 1 GB of Physical Memory, where two times the amount of Physical Memory for Swap space is sufficient) To check: $ /usr/sbin/swapinfo -a Disk Space 3.59 GB for database software Requirements Temporar y The Oracle Universal Installer requires up to 400 MB of space in the / Disk Space tmp directory. If you do not have enough space in the /tmp directory, set Required by the TMPDIR and TMP environment variables to specify a directory with the Oracle sufficient space Universal Installer Supported Optivity NMS only supports the following UNIX shells: shells • Bourne shell (sh) • c-shell (csh) • korn shell (ksh) Operating HP-UX version 11.11 (64-bit) System To check: $ uname -a Requirements: Network On HP-UX 11.11, Optivity NMS 10.3 supports the HP OpenView 7.0.1 management network management platform. platform If you are running a network management platform on your system, do not shut down the network management platform daemons. The Optivity NMS 10.3 installation program requires the presence of a running network management platform daemons. See “Setting up the platform environment” on page 95 for more information. Language Optivity NMS only supports English-language installations of HP-UX. OS packages For HP-UX 11.11 you must install the December 2002 Quality Pack (Gold Patch Set) or higher.

Operating system patches

For HP-UX 11i (64-bit) platform, the following OS patches must be installed:

• PHCO_25452 • PHKL_ _25994 • PHKL_25389

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 93

• PHKL_25729 • PHKL_25842 • PHKL_27092. • PHKL_25506 • PHSS_26560 • PHSS_24638

If you are using ServiceGuard OPS Edition version 11.13 for HP-UX lli, then you must install the following patch:

• PHSS_26674

JRE Patches

The following Web page lists HP-UX patches required for Java™:

http://www.hp.com/products1/unix/java/patches/index.html

Install the most recent QPK1100 or GOLDBASE11i from Software Depot at http://www.software.hp.com/SUPPORT_PLUS/qpk.html (Each successive quality pack includes patches from earlier Quality Packs.)

HP-UX 11.11 patches required for Java™ 1.4 with the June '04 Quality Pack:

http://www.hp.com/products1/unix/java/patches/g-11.11-1.4-1111.0306.html

Table 13 HP-UX JRE patches

Earliest patch Problem Description

PHKL_25468 improves performance and capacity i/o of polling PHKL_25842 supports Solaris-like semantics for concurrent close (thread termination) PHCO_29109 solves pthread synchronization causing hangs. must install starting with 1.3.1.09, 1.4.1.03. PHCO_300049 Solves problem with dld while loading native libraries for class ServerSocket

Installing and Administering Optivity NMS 10.3

94 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

Additional HP-UX Operating System Requirements

X Server and Window Manager: Use any X server supported by your UNIX operating system. Use any supported window manager supported by your UNIX operating system. For Hummingbird Exceed, use a native window manager. For WRQ Reflections, allow a remote window manager. To determine if your X Window System is working properly on your local system, enter the following command:

$ xclock

Before installing Optivity NMS 10.3, make sure that the setting of the environment variable TERM is something defined in /etc/termcap such as xterm or vt100. Otherwise, the installation fails.

Do not attempt to install Optivity NMS on a read-only file system. If you attempt such an installation using the graphical installation program, clicking Next does not advance to the next screen. Instead, it adds one iteration of the text “/lnms” to the installation location text box for each click on the Next button.

Required executables

The following executables must be present: make, ar, ld, nm.

Due to a known HP bug (Doc. id: KBRC00003627), the default HP-UX (64-bit) operating system installation does not create a few required X library symbolic links. These links must be created manually before starting Oracle9i installation. To create these links you must have superuser privileges, as the links are to be created in the /usr/lib directory. After enabling superuser privileges, run:

$ cd /usr/lib $ ln -s /usr/lib/libX11.3 libX11.sl $ ln -s /usr/lib/libXIE.2 libXIE.sl $ ln -s /usr/lib/libXext.3 libXext.sl $ ln -s /usr/lib/libXhp11.3 libXhp11.sl $ ln -s /usr/lib/libXi.3 libXi.sl $ ln -s /usr/lib/libXm.4 libXm.sl $ ln -s /usr/lib/libXp.2 libXp.sl $ ln -s /usr/lib/libXt.3 libXt.sl $ ln -s /usr/lib/libXtst.2 libXtst.sl

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 95

Netscape 7 for HP-UX

You should install ximian gnome 1.4 gtk+ libraries for hp-ux prior to installing Netscape 7.

For best results, make sure environment variables described in Table 14 are defined:

Table 14 HP-UX environment variables

Variable Description DISPLAY=displaystation:0.0 define appropriately with the address of your display HOME=/home/yourhomedir Netscape requires HOME to be appropriately defined this should be defined to be the directory in which Netscape is located /opt/Netscape/netscape runs a shell script that invokes Netscape 7

The script that invokes Netscape outputs a number of diagnostic messages. These messages are normal, and do not indicate an error condition. The shell script cannot be run asynchronously with the “&” operator.

JDK version

You must have installed the JDK 1.3.0 version or higher that the Oracle HTTP Server module requires prior to installing Oracle9i on HPUX. You will be prompted for the installed JDK home during installation.

Setting up the platform environment

If you are using a platform manager (Network Node Manager or NetView), Nortel Networks recommends that you first set up the network management platform environment before installing Optivity NMS.

In summary, the Optivity NMS installation requires the following:

• Network management platform is installed • Network management platform patches (as required) are installed

Installing and Administering Optivity NMS 10.3

96 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

• Network management platform is configured, all daemons are up and running; and the environment variables for the network management platform are set, including the $DISPLAY variable

For detail instructions on how to perform the required steps, Nortel Networks recommends that you see the appropriate network management platform installation and configuration guide.

Nortel Networks recommends that you configure the universal path names into your environment by running the appropriate script or by adding the line to your login start-up file (.cshrc or .profile):

See “Setting up the Network Node Manager platform environment, next or “Setting up the NetView platform environment” on page 96 for more information.

Setting up the Network Node Manager platform environment

To set up the Network Node Manager network management platform environment, do one of the following:

Setting up the NetView platform environment To set up the NetView network management platform environment:

cd /usr/OV/bin ./NVenvironment

Nortel Networks recommends that you see the Network Node Manager or NetView installation guide for more information.

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 97

Mounting a local CD drive in the HP-UX environment

To mount a local CD drive in the HP-UX 11.11 environment:

1 Insert the CD in the CD drive. 2 Open a shell window. 3 Use the following command to create the pfs file system table: touch /etc/pfs_fstab 4 Use the following command to start the pfsd_mountd and pfsd_mountd.rpc daemons: /usr/sbin/pfs_mountd & 5 Use the following command to start the pfsd and pfsd.rpc daemons: /usr/sbin/pfsd & 6 If a mount point directory does not already exist, create one by entering: mkdir for example: mkdir /cdrom 7 Enter the following command to mount the CD: /usr/sbin/pfs_mount Where: • is the mount point directory • is the block device for the CD drive. For example: /usr/sbin/pfs_mount /dev/dsk/c0t0d0 /cdrom

Installing and Administering Optivity NMS 10.3

98 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

You can use the following command to find the block device for your CD drive: $ ioscan -funC disk The system responds with a table of available disk drives (Figure 10).

Figure 10 HP-UX ioscan output

# ioscan -funC disk Class I H/W Path Driver S/W State H/W Type Description ======disk 0 10/0/14/0.0.0 sdisk CLAIMED DEVICE TEAC CD-532E-B /dev/dsk/c0t0d0 /dev/rdsk/c0t0d0 disk 1 10/0/15/1.6.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC /dev/dsk/c3t6d0 /dev/rdsk/c3t6d0

In the row for the CD drive, note the block device. In the example in Figure 10, the CD block device name is /dev/dsk/c0t0d0.

To unmount the CD drive::

Enter:

/usr/sbin/pfs_umount For example: /usr/sbin/pfs_umount /cdrom The CD is unmounted.

To mount subsequent CDs

1 Use the following command to check that the pfs daemons are running: ps -ef | grep pfs The following daemons should be running: • pfsd_mountd • pfsd_mountd.rpc •pfsd • pfsd.rpc

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 99

2 If necessary, use the following commands to start the pfs daemons: /usr/sbin/pfs_mountd & /usr/sbin/pfsd & 3 Enter the following command to mount the CD: /usr/sbin/pfs_mount For example: /usr/sbin/pfs_mount /dev/dsk/c0t0d0 /cdrom The new CD is mounted.

Installation procedures

This section is divided into the following major sections. You perform some or all of the procedures in these sections to install Optivity NMS 10.3:

• “Installation flow chart for HP-UX‚” next • “Migrating the Optivity NMS 10.2x database” on page 102 • “Removing previous versions of Optivity NMS” on page 104 • “Installing the Oracle database software” on page 106 • “Installing Optivity NMS 10.3 client or server/client software” on page 112 • “Modifying Optivity NMS user login scripts” on page 115 • “Installing the license key” on page 116 • “Installing the JRE 1.4.2 plug-in on HP-UX” on page 118

Installing and Administering Optivity NMS 10.3

100 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

Table 17 describes where to start installing Optivity NMS 10.3, depending on the type of installation and whether you are upgrading from a previous release of Optivity NMS. At the end of each section there are instructions on which procedure to do next, depending on your installation type:

Table 15 Starting Optivity NMS installation

If you have this Optivity NMS And you want to install the And you want to install the version currently installed: Optivity NMS Server/Client Optivity NMS Client-only software: software: None Go to “Installing the Oracle Go to “Installing Optivity NMS 10.3 database software” on page 106 client or server/client software” on page 112 Any of: • To preserve your Optivity NMS Go to “Removing previous versions • 10.2 10.2x database, go to “Migrating of Optivity NMS” on page 104 the Optivity NMS 10.2x • 10.2.0.x database” on page 102 • 10.2.x • If you don’t need to preserve your Optivity NMS 10.2x database, go to “Removing previous versions of Optivity NMS” on page 104 10.1 or prior Go to “Removing previous versions of Optivity NMS” on page 104

Installation flow chart for HP-UX

The flow chart in Figure 11 shows an overall view of the procedures for installing Optivity NMS 10.3 on HP-UX.

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 101

Figure 11 Installation procedure overview, HP-UX

Start

Client-only Installation type Server/client

ONMS version 10.1 or ONMS version 10.0 or 10.1.x installed? 10.2x earlier installed? earlier Yes (10.2.0.x or None ONMS version 10.1.0.x Patched? 10.2.1 installed) Uninstall old installed? Uninstall old Optivity NMS Remove patch to Optivity NMS Preserve 10.1 revert to 10.1 No topology database? Do data migration Uninstall No procedure version 10.1

Remove patch to revert to 10.2

Uninstall version 10.2

Oracle 9i No installed? Check HP-UX kernel Ye s parameters9i

Install Oracle 9i

Install Oracle 9.2.0.4 patch

GUI Installation (easiest) option Silent Command line Create answer “install” “install -c” file

answer answer “install --silent prompts prompts ”

Installation Server/client type? Install Client-only license key

End

Installing and Administering Optivity NMS 10.3

102 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

Migrating the Optivity NMS 10.2x database

You can skip this procedure if:

In either of these cases, skip ahead to “Removing previous versions of Optivity NMS” on page 104.

Follow the procedure below to migrate your Optivity NMS 10.2.x or 10.2.0.x database to Optivity NMS 10.3 format:

1 Login as root. 2 Find the software CD marked “Optivity NMS 10.3 for HP-UX CLIENT and SERVER” and insert it into the CD-ROM drive. 3 Open a terminal window. 4 Use pfsmount to mount the CD drive. For instructions on mounting the CD drive on an HP-UX system, see “Mounting a local CD drive in the HP-UX environment” on page 97. 5 At the command prompt, enter: xhost + 6 From your local UNIX workstation, log into the system where you will run Oracle Universal Installer. 7 Set the DISPLAY variable to the system name or IP address, X-server, and screen used by your workstation.

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 103

Do not use the host name or IP address of the system where the software is being installed, unless you are performing the installation from that system's X-windows console. Use the machine name or IP of your own workstation if you are installing from a remote system. If you are not sure what the X-server and screen should be set to, use 0 (zero) for both. 8 Do one of the following: • For the Bourne or Korn shell, enter: DISPLAY=[| ];export DISPLAY • For the C shell, enter: setenv DISPLAY [| ] 9 In the terminal window, change to the CD drive and change directory to the dm directory. cd cdrom/cdrom0/dm 10 In the /dm directory of the CD, invoke the dm.bat file: dm 11 If Optivity NMS 10.2x is currently installed, the program prompts whether you want to back up the topology database. 12 Enter Y to back up the topology database. 13 The program prompts for a directory to which to back up the database.

Note: There must be no spaces in any of the directory names in the path.

The program backs up the database to the selected directory and converts the data to Optivity NMS 10.3 format.

After you migrate your database to Optivity NMS 10.3 format, proceed to “Removing previous versions of Optivity NMS‚” next.

Installing and Administering Optivity NMS 10.3

104 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

Removing previous versions of Optivity NMS

If you have previously installed Optivity NMS on your system, go to one of the following sections:

• If you have upgraded your Optivity NMS with maintenance release version 10.2.0.1, 10.2.0.2, or 10.2.1, go to “Removing Optivity NMS 10.2.0.1, 10.2.1, and 10.2.0.2 maintenance releases” on page 104. • IfIf your Optivity NMS version is 10.2 or earlier, go to “Removing Optivity NMS 10.2 and earlier software” on page 105.

Removing Optivity NMS 10.2.0.1, 10.2.1, and 10.2.0.2 maintenance releases

Follow this procedure to remove the Optivity NMS 10.2.0.1, 10.2.1 or 10.2.0.2, maintenance release software and revert to version 10.2:

1 Login in as root. 2 If root is not configured to run Optivity NMS, then run one of the following commands: • Bourne, k-shell: . /usr/lnms/bin/opt_kshrc • C-shell: source /usr/lnms/bin/opt_cshrc 3 Stop all ONMS applications. 4 Stop all NMS platform daemons (in a platform system only). 5 Change directory (cd) to /opt/bay/install. 6 Determine which maintenance release has been installed: In the /opt/bay/install directory, look for files named uninstall10101 and uninstall10102

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 105

• If only uninstall10201 is present, then only the 10.2.0.1 maintenance release is installed. • If both uninstall10201 and uninstall1021 files are present, then both the 10.2.0.1 and the 10.2.1 maintenance releases have been installed. • If only uninstall10202 is present, then only the 10.2.0.2 maintenance release is installed. 7 Execute the latest (numerically greater) maintenance release uninstallation program. For example, if both uninstall10201 and uninstall1021 are present, run uninstall1021: ./uninstall1021 The batch file removes the Optivity NMS maintenance release software. If both the 10.2.0.1 and the 10.2.1 maintenance releases have been installed, the program prompts whether you want to revert to 10.2.0.1 or to 10.2. 8 If so prompted, choose to revert to 10.2. 9 Restart all NMS platform daemons (in a platform system only). 10 Start all Optivity NMS daemons using the “optivity_apps start” command. 11 Run the command “optstatus -fe” to ensure that all Optivity NMS daemons are running.

After removing the maintenance release software to revert to version 10.2, proceed to “Removing Optivity NMS 10.2 and earlier software” on page 105.

Removing Optivity NMS 10.2 and earlier software

Follow this procedure to remove the Optivity NMS 10.2 and earlier software:

1 Login in as root. 2 CD to the /opt/bay/install directory 3 Invoke the following script: ./uninstall The script uninstalls Optivity NMS. Respond to the script prompts as necessary.

Installing and Administering Optivity NMS 10.3

106 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

After removing the Optivity NMS 10.2 or earlier software, proceed to

• If you are installing Optivity NMS on a system that will be an Optivity NMS server, go to “Installing the Oracle database software” on page 106. • If you are installing Optivity NMS on a system that will be an Optivity NMS client, go to “Installing Optivity NMS 10.3 client or server/client software” on page 112.

Installing the Oracle database software

For an Optivity NMS 10.3 server installation you install Oracle 9i, and then upgrade Oracle 9i with the 9.2.0.4 patch.

To install the Oracle 9i database software, go to one of the following sections:

• If the system you are installing Optivity NMS on has no Oracle database software installed, go to “Checking HP-UX Kernel Parameter Settings‚” next. Then proceed to go to “Installing the Oracle 9i database software on HP-UX” on page 109. Then go to “Installing the Oracle 9.2.0.4 patch” on page 111 to upgrade Oracle 9i with the 9.2.0.4 patch. • If Oracle 9i had been previously installed on the system, go to “Installing the Oracle 9.2.0.4 patch” on page 111 to upgrade Oracle 9i with the 9.2.0.4 patch.

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 107

Checking HP-UX Kernel Parameter Settings

Before installing Oracle 9i database software, make sure your HP-UX system has the following kernel parameter settings:

Table 16 HP-UX kernel parameter settings

Parameter Setting Description KSI_ALLOC_MAX (NPROC * 8) Defines the systemwide limit of queued signals that can be allocated. MAX_THREAD_PROC 256 Defines the maximum number of kernel threads allowed per process. You may need to increase the value if required by your application. Setting it to a default or low value may lead to an out of memory error for certain applications. MAXUSERS 400 Defines the maximum number of users. MAXFILES 2048 Defines the maximum number of files. MAXDSIZ 1073741824 bytes Refers to the maximum data segment size in bytes for 32-bit systems. Setting this value too low may caprocesses to run out of memory. MAXDSIZ_64 2147483648 bytes Refers to the maximum data segment size in bytes for 64-bit systems. Setting this value too low may caprocesses to run out of memory. MAXSSIZ 134217728 bytes Defines the maximum stack segment size in bytes for 32-bit systems. MAXSSIZ_64BIT 1073741824 Defines the maximum stack segment size in bytes for 64-bit systems. MAXSWAPCHUNKS 16384 Defines the maximum number of swap chunks where SWCHUNK is the swap chunk size (1 KB blocks). SWCHUNK is 2048 by default. It specifies the maximum amount of configurable swap space on the system. NPROC 4096 Defines the maximum number of processes. MSGTQL NPROC Defines the number of message headers. MAXUPRC ((NPROC*9)/10) Defines the maximum number of user processes. MSGMAP (MSGTQL + 2) Defines the maximum number of message map entries. MSGMNI NPROC Defines the number of message queue identifiers. MSGSEG 32767 Defines the number of segments available for messages. NCALLOUT (NPROC + 16) Defines the maximum number of pending timeouts.

Installing and Administering Optivity NMS 10.3

108 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

Table 16 HP-UX kernel parameter settings (continued)

Parameter Setting Description NCSIZE ((8 * NPROC + 2048) + Defines the Directory Name Lookup Cache (DNLC) VX_NCSIZE) space needed for inodes. VX_NCSIZE is by default 1024. NFILE (15 * NPROC + 2048) Defines the maximum number of open files. NFLOCKS 4096 Defines the maximum number of file locks available on the system. NINODE (8 * NPROC + 2048) Defines the maximum number of open inodes. NKTHREAD (((NPROC * 7) / 4) + 16) Defines the maximum number of kernel threads supported by the system. SEMMNI 4096 Defines the maximum number of semaphore sets in the entire system. SEMMAP (SEMMNI + 2) Defines the maximum number of semaphore map entries. SEMMNS (SEMMNI * 2) Defines the maximum number of semaphores in the system. The default value of SEMMNS is 128, which is, in most cases, too low for Oracle9i software. SEMMNU (NPROC - 4) Defines the number of semaphore undo structures. SEMVMX 32768 Defines the maximum value of a semaphore. SHMMAX Available physical memory Defines the maximum allowable size of one shared memory segment. The SHMMAX setting should be large enough to hold the entire SGA in one shared memory segment. A low setting can cause creation of multiple shared memory segments which may lead to performance degradation. SHMMNI 512 Defines the maximum number of shared memory segments in the entire system. SHMSEG 32 Defines the maximum number of shared memory segments one process can attach. VPS_CEILING 64 Defines the maximum System-Selected Page Size in kilobytes.

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 109

Installing the Oracle 9i database software on HP-UX

For an Optivity NMS 10.3 server, you must install the Oracle 9i database software before you install Optivity NMS 10.3. If you have already installed Oracle 9i, or if you are only installing the Optivity NMS 10.3 client software, skip ahead to the section Installing Optivity NMS 10.3 software on HP-UX.

Note: Your system language setting must be English (United States) in order to install Optivity NMS. If you have installed Oracle under a different language setting, you must remove and reinstall Oracle with the language set to English (United States).

To install the Oracle 9i database software on an HP-UX system:

1 Find the software CD marked “Optivity NMS 10.3 Database Installer for HP-UX (1 of 5).” and insert it into the CD-ROM drive. 2 Open a terminal window. 3 Use pfsmount to mount the CD drive. For instructions on mounting and unmounting the CD drive on an HP-UX system, see “Mounting a local CD drive in the HP-UX environment” on page 97. 4 In a terminal window, execute the following command to change to the root directory: cd / 5 In a terminal window, execute the following command: /cdrom/install

Note: Execute the command from the root directory. Do not cd to the /cdrom directory. Doing so would interfere with your ability to eject the CD when required.

The installation program prompts you: Provide a directory to unpack Disk2 (650 Mb minimum) [/] : 6 Enter the name of the directory with at least 650 MB of free space.

Installing and Administering Optivity NMS 10.3

110 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

The installation program copies the contents of the Oracle 1 CD to the directory, and then prompts you to insert the Oracle 2 CD: Insert Oracle CD # 2 7 Insert the CD marked “Optivity NMS 10.3 Database Installer for HP-UX (2 of 5).” into the CD-ROM drive. The installation program prompts you for the path to the Disk3 directory on the CD: Enter path to Disk3 [/cdrom/Products/Oracle/9.2/ distribution]: 8 Enter the name of the directory. On the CD, the directory is /cdrom/Products/ Oracle/9.2/distribution. The installation program prompts you: Provide a directory to unpack Disk3 (610 Mb minimum) [/] : 9 Insert the CD marked “Optivity NMS 10.3 Database Installer for HP-UX (3 of 5).” into the CD-ROM drive. The installation program prompts you for the path to the Disk4 directory on the CD: Enter path to Disk4 [/cdrom/Products/Oracle/9.2/ distribution]: 10 Enter the name of the directory. On the CD, the directory is /cdrom/Products/ Oracle/9.2/distribution. The installation program prompts you: Provide a directory to unpack Disk4 (141 Mb minimum) [/] : 11 Enter the name of the directory with at least 141 MB of free space. The installation program copies the contents of the Oracle 3 CD to the directory, and then prompts you to insert the Oracle 4 CD: Insert Oracle CD # 4 to continue with Oracle install 12 Insert the CD marked “Optivity NMS 10.3 Database Installer for HP-UX (4 of 5).” into the CD-ROM drive. 13 Use the cd command to change to the /cdrom directory on the CD. 14 Execute the following command: ./preinstall -i

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 111

15 Respond to the installation program prompts for information about the Oracle installation. 16 Execute the following command: ./install The installation program installs the Oracle database software on the system. At the end of the installation, the program prompts you to install the Oracle 9.2.0.4 patch: Insert Oracle CD # 5 to proceed with Oracle 9.2.0.4 patch install

After installing the Oracle 9i software, proceed to “Installing the Oracle 9.2.0.4 patch‚” next.

Installing the Oracle 9.2.0.4 patch

You must install the Oracle 9.2.0.4 64-bit patch after installing Oracle 9i database software.

Follow these instructions to install the Oracle 9.2.0.4 patch:

1 Log in as root. 2 Insert the CD marked “Optivity NMS 10.3 Database Installer for HP-UX (5 of 5).”. 3 Use pfsmount to mount the CD drive. For instructions on mounting the CD drive on an HP-UX system, see “Mounting a local CD drive in the HP-UX environment” on page 97. 4 Use the following commands to run the patch installer script from the CDROM directory: cd /cdrom ./install_patch The script installs Oracle Universal Installer 2.2.0.18.0 followed by Oracle9iR2 Server PatchSet 9.2.0.4.0 5 Press the Return key when prompted by the script. 6 Press 'y' key to continue with Post-installation tasks.

Installing and Administering Optivity NMS 10.3

112 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

Post-installation will run SQL scripts in the database. This process takes about 20 minutes. 7 Unmount the cdrom and remove the CD. For instructions on mounting and unmounting the CD drive on an HP-UX system, see “Mounting a local CD drive in the HP-UX environment” on page 97.

Note: Sometimes, the CD drive does not umount properly in response to the pfs_umount command. If this happens, close all shell windows and then invoke the pfs_umount command in a new shell window.

After installing the Oracle 9.2.0.4 patch, proceed to “Installing Optivity NMS 10.3 client or server/client software‚” next.

Installing Optivity NMS 10.3 client or server/client software

You have three options for installing the Optivity NMS 10.3 client or server/client software. Go to one of the following sections:

• GUI installation gives you an easy-to-use wizard-style graphic interface. Simply respond to the prompts for information about your installation. See “Using graphic interface installation‚” next for more information. • Command-line installation uses the same familiar text interface as previous Optivity NMS installations. See “Using Command-line installation” on page 113 for more information. • Silent installation is a non-interactive installation procedure that you can use to automate the installation of Optivity NMS 10.3 software. See “Using silent installation” on page 114 for more information.

Using graphic interface installation

To install the Optivity NMS server/client software using the graphic interface:

1 Find the software CD marked “Optivity NMS 10.3 for HP-UX CLIENT and SERVER” and insert it into the CD-ROM drive. 2 Use pfsmount to mount the CD drive.

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 113

For instructions on mounting and unmounting the CD drive on an HP-UX system, see “Mounting a local CD drive in the HP-UX environment” on page 97. 3 Use the following command to change to the install directory on the CD: cd /cdrom/install 4 In a terminal window, execute the following command: ./install 5 Respond to the installation program prompts for information about Optivity NMS components you want to install, and where you want to install them.

Note: In the installation window, the scroll bars do not work. To scroll, click anywhere inside the window & use the arrow keys for navigation

After installing the Optivity NMS 10.3 client or server/client software, proceed to one of the following sections:

• If you are installing Optivity NMS on a system that will be an Optivity NMS server, go to “Installing the license key” on page 116. • If you are installing Optivity NMS on a system that will be an Optivity NMS client, you have completed the installation.

Using Command-line installation

To install the Optivity NMS server/client software using the command-line interface:

Installing and Administering Optivity NMS 10.3

114 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

4 In a terminal window, execute the following command: ./install -c 5 Respond to the installation program prompts for information about Optivity NMS components you want to install, and where you want to install them. The system reboots. When it starts back up, it starts the Optivity NMS services. The services take between three and five minutes to start.

After installing the Optivity NMS 10.3 client or server/client software, proceed to one of the following sections:

Using silent installation

The silent installation system uses configuration information from a text file that you provide. To use silent installation, perform the following steps:

1 Find the software CD marked “Optivity NMS 10.3 for HP-UX CLIENT and SERVER” and insert it into the CD-ROM drive. 2 Use pfsmount to mount the CD drive. For instructions on mounting and unmounting the CD drive on an HP-UX system, see “Mounting a local CD drive in the HP-UX environment” on page 97. 3 On the CD, find the following file and copy it to a local directory: /cdrom/install/template.rsp This text file is a template for the answer file where you specify installation parameters for Optivity NMS. 4 Edit the template to create an .rsp answer file for your installation. The elements of the answer file are described in comment text in the template. See Appendix B, “Silent Installation answer file reference,” on page 161 for more information.

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 115

5 Use the following command to change to the install directory on the CD: cd /cdrom/install 6 Run the install program with the silent option: # ./install --silent For example: # ./install --silent /tmp/onms_silent.rsp The installation program installs Optivity NMS according to the parameters in the answer file and then starts the Optivity NMS daemons. The daemons take between three and five minutes to start.

After installing the Optivity NMS 10.3 client or server/client software, proceed to one of the following sections:

Modifying Optivity NMS user login scripts

For an Optivity NMS 10.3 server installation, you must modify each Optivity NMS user’s login script.

Using vi or another text editor, add the following lines to each Optivity NMS user's login script:

• For the C shell, add the following line to the .cshrc file: umask 022 if ( -f /opt/lnms/bin/opt_cshrc ) then source /opt/lnms/bin/opt_cshrc endif

Installing and Administering Optivity NMS 10.3

116 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

• For the Korn shell, add the following line to the .kshrc file: umask 022 if [ -f /opt/lnms/bin/opt_kshrc ];then . /opt/lnms/bin/opt_kshrc fi • For the Bourne shell, add the following to the .profile file: umask 022 if [ -f /opt/lnms/bin/opt_kshrc ];then . /opt/lnms/bin/opt_kshrc fi

After modifying the Optivity NMS 10.3 user login scripts, proceed to one of the following sections:

Installing the license key

The license key number is printed on a document that is included in your Optivity NMS 10.3 software kit. There are three license levels available for Optivity NMS 10.3:

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 117

You must install the license key when you:

• Install a licensed version of Optivity Campus NMS 10.3 or Optivity Enterprise NMS 10.3 • Upgrade from an evaluation copy to a licensed version of Optivity NMS 10.3

To install the license key:

1 Add the license key number to the license.dat file. For more information about installing the license key, see “Installing the Optivity NMS 10.3 license key number” on page 117. 2 Stop and restart all of the Optivity NMS 10.3 daemons. For more information about starting Optivity NMS 10.3 services, see “Stopping and restarting Optivity NMS 10.3 daemons” on page 117.

Installing the Optivity NMS 10.3 license key number

To install the license key number:

Stopping and restarting Optivity NMS 10.3 daemons

To stop and restart all Optivity NMS 10.3 daemons:

1 Login as root. 2 Open a UNIX terminal window.

Installing and Administering Optivity NMS 10.3

118 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

3 Set the environment: • For the C shell: source /opt/lnms/bin/opt_cshrc • For the Korn shell: . /opt/lnms/bin/opt_kshrc • For the Bourne shell: . /opt/lnms/bin/opt_kshrc 4 Stop the daemons with this command: optivity_apps stop 5 Restart the daemons with this command: optivity_apps start 6 To verify that daemons started, enter: optstatus -fe

Installing the JRE 1.4.2 plug-in on HP-UX

In order to open Optivity NMS 10.3 applications in a browser window, you must download and install the JRE 1.4.2_02 runtime and plugin for Netscape 7.0. If the plug-in is not installed, and you start an Optivity NMS 10.3 application in the browser, you are prompted to install the plug-in. If you agree, the link takes you to an Optivity plug-in install Web page, where you click a link to download the plug-in.

To install the JRE 1.4.2_02 plugin for Netscape 7.0:

205969-H

Chapter 4 Installing Optivity NMS 10.3 on HP-UX 119

If the plug-in is not installed on your system, you are prompted to install the plug-in.

Note: Some browsers do not recognize the “.depot” format and treat the file as a text file. If this happens, try pressing the shift key at the same time as you click the download link.

4 Use SAM to install the plugin. The Runtime will be installed under “/opt/java1.4/jre” & the plugin under “/ opt/java1.4/jre/plugin”. If you have a previous installation of 1.4, please uninstall it using swremove and move any personal files from your existing / opt/java1.4 directory. You need approximately 60 MB of disk space on your system to install the software. To install the software from the .depot file you need an additional 100 MB disk space. 5 As root user, use the SD-UX swinstall command to install the software: /usr/sbin/swinstall& 6 After completing the installation, remove the directory where your download software is located. For further details, see: http://www.hp.com/products1/unix/java/java2/sdkrte14/downloads/ index.html http://www.hp.com/products1/unix/java/java2/jpi/downloads/index.html 7 In order to use all Optivity NMS application features in a browser, copy all *.jar files from the $LNMSHOME/applets directory into the /opt/java1.4/jre/ lib/ext directory. 8 Start your browser on HP and start using Optivity NMS the client from the browser.

Installing and Administering Optivity NMS 10.3

120 Chapter 4 Installing Optivity NMS 10.3 on HP-UX

Postinstallation notes

Table 17 describes postinstallation issues that you might need to address after you have installed Optivity NMS 10.3 software.

Table 17 Postinstallation notes for the Windows environment

205969-H

121 Chapter 5 Getting started with Optivity NMS

This chapter describes the sequence that Nortel Networks suggests that you follow to discover the devices in your network, populate the Optivity NMS database, and begin managing your network.

This chapter includes the following information:

• “Operational considerations‚” next • “Discovering and administering your network” on page 122 • “Understanding the workflow process” on page 124 • “Using Optivity NMS applications” on page 133

Operational considerations

There are certain operational considerations for operating Optivity NMS 10.3 on your management station.

For more information about operational requirements, see the following:

• “Oracle operational note” on page 175 • “Optivity Integration Toolkit operational note” on page 175 • “Trap Server operational note” on page 176

Installing and Administering Optivity NMS 10.3

122 Chapter 5 Getting started with Optivity NMS

Discovering and administering your network

This section describes the procedure for using Optivity NMS to discover and administer your network for the first time. There are multiple methods you can use to get started using Optivity NMS InfoCenter to manage your network. Nortel Networks suggests that you use the workflow described in this chapter.

To discover and administer your network for the first time:

1 Start Optivity NMS InfoCenter: • In Windows, choose Start > Programs > Optivity > InfoCenter • In UNIX, open a command window, cd to $LNMSHOME and enter infocenter. For more information about logging into InfoCenter, see “Logging in to Optivity NMS” on page 124. For more information about starting InfoCenter for the first time, see “Starting InfoCenter for the first time” on page 125. For more information about InfoCenter, see Using Optivity NMS 10.3 Applications (part number 207569-G) and the InfoCenter Online Help System.

2 If applicable, to specify non-default community strings and SNMPv3 user security for a platformless installation: a From the InfoCenter menu bar, choose Admin > Community Strings. The Community Strings Editor window opens. b Enter the non-default community strings. c Enter the Optivity user and individual user permissions. For more information about specifying non-default community strings, see “Specifying device community strings” on page 126. For information about using the Community Strings Editor, see Using Optivity NMS 10.3 Applications (part number 207569-G) and the Community Strings Editor Online Help system.

3 To discover devices in your network: a Make sure that you have entered community strings and user security entries for all of the subnets that you intend to discover. The

205969-H

Chapter 5 Getting started with Optivity NMS 123

Autotopology applications must have SNMP read community strings for the all of the devices to be discovered. b Start AutoTopology Manager and configure one or more discovery seeds using the Seed Information dialog box. For more information about specifying non-default community strings, see “Discovering network resources” on page 128. For information about using the AutoTopology Manager, see Using Optivity NMS 10.3 Applications (part number 207569-G) and the AutoTopology Manager Online Help system.

c Click Start Discovery to start the discovery process. d Monitor the discovery process using the progress pane of the Autotopology Manager window or the Details window. For more information about viewing discovered network resources, see “Viewing network resources” on page 130 and the Autotopology Manager Online Help system. 4 To customize the monitoring options for an object: a Select a physical device, segment, or subnet in the InfoCenter window. b Choose Monitor Options from the InfoCenter Admin menu. The Monitor Options dialog box opens. c Click the Customize radio button in the Monitor Options dialog box. d Select the topology and fault options for the object. e To prevent its parent’s settings from overriding the settings for this object, click the Retain Options check box. f Click Apply or OK. Apply saves your settings and keeps the Monitor Options dialog box open. OK saves your settings and closes the dialog box. For more information about configuring applications to start on a specific device, see “Configuring network management applications” on page 130. For more information about the Monitor Options tool see Using Optivity NMS 10.3 Applications (part number 207569-G) and the InfoCenter Online Help system.

Installing and Administering Optivity NMS 10.3

124 Chapter 5 Getting started with Optivity NMS

5 Set access control for applications and users. For more information about setting access control for applications and users, see “Setting access control” on page 131 and the Access Control Administration Online Help system.

6 Back up the discovered data base. For more information about backing up the discovered database, see “Backing up the database” on page 132 and the Database Admin Tool Online Help system.

7 Customize InfoCenter for your particular application. For more information about customizing InfoCenter for your particular network requirements, see “Customizing Optivity NMS InfoCenter” on page 133 and the InfoCenter Online Help system.

Understanding the workflow process

This section provides additional information about using Optivity NMS to discover and administer your network for the first time. For additional information about Optivity NMS applications that are referenced in this chapter, see Using Optivity NMS 10.3 Applications (part number 207569-G) and online Help for the respective Optivity NMS application.

Logging in to Optivity NMS

When you start InfoCenter, the Connect to Optivity NMS Server dialog box opens. This dialog box lets you add:

• Your User Name—Use any valid user ID name on the Optivity NMS Server. Your user name is based on the network where the Optivity NMS Server is installed. Use a UNIX user ID if the Optivity NMS Server is installed on a UNIX management station. Use a Windows user ID name if the Optivity NMS Server is installed on a Windows NT management station.

205969-H

Chapter 5 Getting started with Optivity NMS 125

If the Optivity NMS Server resides in a domain different from the Optivity NMS Client, you should precede your user name with the server domain name.

Note: If there is no domain configured, you must have a locally defined Windows NT account on the Optivity NMS Server when logging into InfoCenter from a Windows NT client management station.

If you are using Windows NT or Windows 2000, your user account must be in the same domain as the Optivity NMS Server. If not, your user login will not be authenticated.

• Your Password—Your password on the Optivity NMS Server. • Host Name—The host name or IP address of the Optivity NMS Server to which you want to connect. If the Optivity NMS Server and Client are installed on the same management station, localhost is the default host name.

When you click OK in the Connect to Optivity NMS Server dialog box, Optivity NMS authenticates your user account on the local network and then your network account. If one of your account names is authentic, InfoCenter opens. If not, the InfoCenter window does not open.

Starting InfoCenter for the first time

When you start InfoCenter for the first time, the Optivity NMS database is empty, and there are no network resources.

There are two tasks you must do to display your network resources in InfoCenter:

• Ensure that Optivity NMS has information about the customized community strings of all of your network resources. You can use the Community Strings Editor, see “Specifying device community strings” on page 126, or you can use your network management platform.

Installing and Administering Optivity NMS 10.3

126 Chapter 5 Getting started with Optivity NMS

• Use the Optivity NMS Autotopology Manager to discover the resources in your network and to populate the Optivity NMS database with the discovered devices before you begin to use Optivity NMS to monitor and manage your network.

For more information about populating the Optivity NMS database, see “Discovering network resources” on page 128.

Specifying device community strings

Before you use Autotopology Manager to discover the resources in your network, you need to give Optivity NMS information about any non-default community strings and user security permission for each user that are set to restrict access to your network resources. Optivity NMS provides the Community Strings Editor for specifying existing community strings and adding new ones. You can import community strings files from another management station. You can also export community strings information in file format to another Optivity NMS Server management station.

Note: To discover multicast protocol visualization information on BayRS routers during the discovery process, you must use the Community Strings Editor to add telnet login information.

If Optivity NMS is integrated with a network management platform such as HP OpenView or Tivoli TME 10 NetView, you probably have already specified the community strings for resource access using the community string management utilities in the platform software. Also, if Optivity NMS is integrated with a network management platform, you can only use the Community Strings Editor to modify the telnet password information for your routers as used by Path Trace. If Optivity is installed platformless (without a network management platform), you can use the Optivity Community Strings Editor to specify your community strings.

Note: If you use non-default community strings for your routers, for discovery of subnet devices to be successful, you must make certain that all interface IP addresses are accounted for in your community strings configuration.

205969-H

Chapter 5 Getting started with Optivity NMS 127

Community strings control access to your network resources. There are two types of SNMP community strings:

•Read • Read/write

The read community string controls which management station can read the management information base (MIB) for a particular device. The read/write community string controls which management station can have full access (read and write) to the MIB of a device.

By default, the read community string of a device is set to “public.” The read/write community string of a device is set to “private.” This means that any management station can access information for that device.

If all of the devices on your network have the default community strings, you do not need to use the Community Strings Editor. You are ready to run Autotopology Manager to discover your network resources (see “Discovering network resources” on page 128).

If you have changed the community strings from the default settings, then you need to specify those changed community strings for Optivity NMS using the Community Strings Editor (see “Specifying device community strings” on page 126). Otherwise Autotopology Manager will not be able to discover these devices.

User security

The Community Strings Editor also supports the SNMPv3 user security model (USM) that lets you administer user security to accommodate your network requirements. The USM lets you specify authentication and privacy security features for:

• Each user • Multiple users for a specific IP or a range of IP addresses • A single Optivity user for trap registration

The Community Strings Editor stores information about community strings and security in the Optivity NMS topology database.

Installing and Administering Optivity NMS 10.3

128 Chapter 5 Getting started with Optivity NMS

Discovering network resources

To populate the Optivity NMS database with resource information and to display your network resources in InfoCenter, you need to run the discovery process using Autotopology Manager. Autotopology Manager performs layer 1 to 3, and end node network resource discovery.

Make sure that you have entered community strings and user security permissions for all of the subnets that you intend to discover.

The Autotopology applications must have SNMP read community strings for the all of the devices to be discovered (see “Specifying device community strings” on page 126).

If Optivity NMS is installed on a network management platform such as HP OpenView or Tivoli NetView, use the community string management utilities in the network management platform software to enter and manage the community strings.

If Optivity NMS is installed either platformless (without a network management platform), use the Optivity NMS Community Strings Editor.

Configuring a discovery seed

Discovery seeds are the starting points that the topology applications and daemons use to discover subnets, devices, end nodes, and the types of protocols running in your network.

The seed information defines the seed router from which to begin discovery, the IP address range within which to discover network resources, and the types of protocols running in the network. Autotopology reads the Address Resolution Protocol (ARP) cache table of the seed router to map an IP address to a physical machine address that is recognized in the local network.

205969-H

Chapter 5 Getting started with Optivity NMS 129

The topcd daemon running on the Optivity server performs the topology discovery. This daemon manages the following topology applications that also run on the Optivity server:

• Network Layer topology—(toprt) Discovers routers and subnets by downloading the routing tables and ipAddrTable from routers. Router Topology starts with the ipAddrTable of the seed router, and obtains the addresses of other routers from ipRouteTable. Router Topology queries all of the routers that it discovers using this process. However, it only adds routers with IP addresses within the specified subnet address range to the Optivity NMS database. • Data Link Layer topology—(topst) Uses information previously added to the Optivity database to locate Nortel Networks devices within subnets. Subnet topology queries the Nortel Networks devices about device and logical topology, but does not query about workstations or end nodes. The topst process filters out Nortel Network devices from non-Nortel Network devices and updates the database to account for these devices. • End Node Topology—(topdt) Uses information from Nortel Networks devices to discover the workstations and end nodes connected to the Nortel Networks devices. • Protocol Discovery—(protur, protmr, protfr) Discovers unicast, multicast, and frame relay protocols running on routers discovered by Router Topology. The protur, protmr, and protfr processes are started by topcd process and exit once they have completed their task.

Monitoring the topology discovery process

Monitor the discovery process by viewing the Progress pane of the AutoTopology Manager window or the Details Window.

For more information about the status and error messages that might appear in the Progress pane, see the Topology Manager Status Messages topic in the AutoTopology Manager online Help system.

To view the Autotopology Manager online Help, choose Help > AutoTopology Manager Help.

The Autotopology process is complete when you see the “Router and Subnet Discovery is Complete” message.

Installing and Administering Optivity NMS 10.3

130 Chapter 5 Getting started with Optivity NMS

Viewing network resources

Once the discovery process is complete, you can use InfoCenter to manage the discovered network. You can see your network resources in the Resource folders.

To manage the discovered network, you can use InfoCenter to do the following:

• Add a seed to your database view—Before you can view objects, you must add the seed you used to discover network resources to your database view. The seed information is saved on the server. Your resource view is associated with your user login ID. The seed(s) that you added to your database view are added to your User Seeds folder.

• Remove a seed from your database view—You can remove a seed from the database view, so that the devices discovered through that seed are not displayed within InfoCenter. For example, in a network environment with multiple remote sites, to reduce the amount of data displayed at one time, you can remove the seeds for sites of less interest.

Configuring network management applications

Application Launch lets you configure applications you can start from within Optivity NMS to manage various network resources.

Using Application Launch, you can:

• Add a new application that you want to manage specific network resources. • Modify existing application configuration to manage different network resources. • Delete existing applications that you do not want to manage network resources.

Application Launch lets you specify the startup environment in which an application runs, including operating platform and command line options. You can also specify the number of devices an application manages.

205969-H

Chapter 5 Getting started with Optivity NMS 131

By default, all Optivity NMS applications (for example, Expanded View, OmniView, and Fault Summary) are configured to start for specific network resources. The Optivity NMS applications that you can start on a particular network resource is dependent upon the MIBs the device supports.

Optivity NMS stores application launch information in the database.

Setting access control

Access Control Administration is an Optivity NMS security management application that manages a list of valid users with their specified access rights and privileges. You can limit access to read-only, read/write, or restricted from starting an application. You can create a customized group of access permissions, thus allowing quick assignment of access privileges to a specific user or users.

When you start the Optivity NMS client, the client module checks for user authorization to connect to the Optivity NMS Server. Upon successful user authentication, Access Control Administration approves the user login name and queries the database for the user access privileges.

When you first start Optivity NMS, Access Control Administration is disabled by default. Any user with a valid user ID can access any Optivity NMS application. Therefore, you must enable Access Control Administration to control user access. For additional information about enabling or disabling Access Control, see Using Optivity NMS 10.3 Applications (part number 207569-G).

After you enable Access Control Administration, only the root and the Administrator user can access Optivity NMS until you add users and configure their access permissions. For additional information about adding and deleting user access permissions, see Using Optivity Network Management System 10.3 Applications (part number 207569-B).

Installing and Administering Optivity NMS 10.3

132 Chapter 5 Getting started with Optivity NMS

Backing up the database

As with any important data, you should periodically back up the Optivity NMS database to protect it from hard disk failure, accidental deletion, or other unexpected loss. Backing up the database also gives you a “snapshot” of the database information at a certain point in time. After backing up the database, you can later restore the backup copy of the database if it should become necessary.

Note: You can only back up or restore an Optivity NMS database when you run the Database Admin Tool on the system where the Optivity NMS server software is installed. If you attempt to back up or restore a database from different workstation, Database Admin Tool displays a Permission Denied alert box.

When you back up an Optivity NMS database, you are only prompted for a single file name for the backup, which is used as the base name for the backup files. If you select multiple database objects to include in the backup, Database Admin Tool creates one backup file for each selected database object. The file names are displayed in a message at the end of the backup process.

For more information about restoring or backing up the database, see Using Optivity NMS 10.3 Applications (part number 207569-G) and the Database Admin Tool online Help system.

205969-H

Chapter 5 Getting started with Optivity NMS 133

Customizing Optivity NMS InfoCenter

The InfoCenter display window gives you flexibility in viewing folder contents. You can set default preferences that will apply to all folders for viewing format, layout, and network layer. You can then change the current view as the need arises. Table 18 describes the display window defaults preferences at installation.

Table 18 Default display window preferences

Preference Default Description Format Tabular Displays folder contents in the form of a sortable, scrollable, column-based table. Displays device label, IP address, and DNS name. The rows are color-coded to reflect a network object’s operational status. You can also resize or reposition the columns. Layout Grid Nodes are arranged into a grid pattern. Layer Database The most detailed folder view. You can see folder contents, interconnected links, and discovered devices as they are represented in the Optivity NMS database, independent of the object layer attributes and topology.

For more information about customizing viewing preferences, see the InfoCenter Online Help system and Optivity NMS 10.3 Applications.

Using Optivity NMS applications

Optivity NMS includes the following applications:

• OmniView—Provides network monitoring statistics, from the enterprise level (for example, LAN, VLAN, ELAN, and WAN) to the device level (for example, a hub or switch in a single network). You can use OmniView to view statistics, in both graphical and tabular form, for network resources that use standard MIBs, such as MIB2 and RMON and SMON. • Path Trace in InfoCenter—Lets you visualize a path between two end nodes and localize the source of network problems. • Expanded View—An application that presents a graphical view of the front panel of a network device. It lets you monitor, configure, and retrieve vital statistics for the managed device.

Installing and Administering Optivity NMS 10.3

134 Chapter 5 Getting started with Optivity NMS

• ATM Call View—An application that provides a graphical view of all ATM entities and virtual circuits included in ATM networks. It Collects ATM/ LANE call and configuration information from switches. It also counts and correlates logical control and data ATM calls. • InfoCenter—Lets you view your discovered network, providing enhanced graphical viewing tools. Optivity Enterprise NMS 10.3 lets you view up to 5000 objects and Optivity Campus NMS 10.3 lets you view up to 1500 objects. • AutoTopology Manager—Lets you perform advanced IP discovery, to completely discover all Nortel Network devices. • Community Strings Editor—Lets you configure SNMPv3 user security for each user. • OIT Administration Tool—An application that lets you administer device support from a graphic interface. You can install, download, and view all the devices installed on the system. • Fault Summary—An intelligent fault engine that links into topology to provide true correlation and aggregation of faults. Faults are then summarized in a graphical viewer that provides solutions. • Device Inventory Viewer—Lets you view and manage information about your network assets, including information about modules installed inside hubs, switches, and chassis. It also lets you view and edit information about the versions of agent software running on devices in the inventory.

For more detailed information about using these Optivity NMS applications, see the Optivity NMS online Help system. To view the Help from within an application, choose Help > Help. To get Help from within some application dialog boxes, click the Help button in that dialog box.

205969-H

135 Chapter 6 Administering Optivity NMS processes

This appendix provides reference information about the Optivity NMS daemons (UNIX) and services (Windows NT). These are processes that must be running for Optivity NMS to run properly.

Note: Always use OptStatus to view daemon status on a Windows NT or Windows 2000 management station. The daemon status shown in the Services dialog box may not accurately represent the current status of Optivity NMS services.

This appendix includes the following sections:

• “Optivity NMS daemons and services‚” next • “Managing Optivity NMS Services on Windows” on page 136 • “Managing Optivity NMS Daemons on UNIX” on page 139

Optivity NMS daemons and services

Table 19 lists the daemons and services that must be running for Optivity NMS to function properly.

Table 19 Optivity NMS daemons (UNIX) or services and services (Windows)

Services Daemons (UNIX) Name (Windows NT) apache Apache Apache Web server weboptsrvr OptWeboptsrvr Web Support icd OptInfoCenter Info Center trapreg OptTrapReg Trap Registration

Installing and Administering Optivity NMS 10.3

136 Administering Optivity NMS processes

Table 19 Optivity NMS daemons (UNIX) or services and services (Windows)

Services Daemons (UNIX) Name (Windows NT) topcd OptTopology Topology trapsrv OptTrapSrv Trap Server fc_daemon OptFaultCorr Fault Correlator state_recdr OptStateRecorder State Recorder superp OptSuperPing Superping otfi_server OptOTFIServer OTFI Server scriptsrv OptScriptSrv Script Server OptStartService Start Database and all Optivity NMS services syslogproc OptSyslogproc Syslog processor syslogreg OptSyslogreg Syslog registration ebd OptEbd Fault Summary server divs OptDivs Device Inventory Viewer server OptServletEngine Service for: • Notification Server servlet • Registration Server servlet

Managing Optivity NMS Services on Windows

The following sections describe how to start and stop the Optivity NMS services on Windows:

• “Viewing services status on Windows‚” next • “Starting services on Windows” on page 137 • “Stopping services on Windows” on page 138

205969-H

Administering Optivity NMS processes 137

Viewing services status on Windows

Note: Always use OptStatus to view daemon status on a Windows NT management station. The daemon status shown in the Services dialog box may not accurately represent the current status of Optivity daemons.

To verify if the Optivity NMS services are running on the Windows NT platform:

1 From the Windows task bar, choose Start > Programs > Command Prompt. The Command Prompt windows opens. 2 Enter one of the following: • optstatus –f • optstatus –fe

To verify if the Optivity NMS services are running on the Windows NT platform from the Control panel:

1 From the Windows NT task bar, choose Start > Settings > Control Panel. The Control Panel window opens.

2 In the Control Panel window, click Services. The Services dialog box opens.

3 Verify that the services that begin with “Opt” are started.

Starting services on Windows

The services must be started in a certain sequence in order for the Optivity NMS applications to fully function.

To start all of the Optivity NMS 10.3 services:

1 Open the Services dialog box, and verify that the service named OracleServicenmsdb is started. 2 Open a Command Prompt window.

Installing and Administering Optivity NMS 10.3

138 Administering Optivity NMS processes

3 Enter: cd \$LNMSHOME\bin 4 Enter: start_all_services.bat The database is mounted and all of the services are started. 5 To verify that all of the services are started, at the command line, enter: optstatus -fe The system displays a list of services and their status. If a service is not running, go to step 6.

6 To start an Optivity NMS service on Windows NT or Windows 2000 control panel: From the Windows NT or Windows 2000 task bar, choose Start > Settings > Control Panel.

The Control Panel opens.

7 Click Services. The Services dialog box opens.

8 Select a service name starting with Opt, and click Start. The service starts.

Stopping services on Windows

To stop a service on Windows NT or Windows 2000:

1 On the Windows NT or Windows 2000 task bar, click Start > Settings > Control Panel. The Control Panel window opens.

2 Click Services. The Services dialog box opens.

3 Select a service starting with Opt.

205969-H

Administering Optivity NMS processes 139

4 Click Stop. The Stopping dialog box opens.

5 Click OK. The Service Control message box opens. The service stops.

To start or stop a particular service (for example, OptInfocenter) from the command line:

1 Open a Command Prompt windows: 2 Do one of the following: • To start the service, enter: Net start optinfocenter • To stop the service, enter: Net stop optinfocenter

Managing Optivity NMS Daemons on UNIX

The following sections describe how to start and stop the Optivity NMS daemons on UNIX:

• “Viewing daemon status on UNIX‚” next • “Starting daemons on UNIX” on page 140 • “Stopping daemons on UNIX” on page 141

Viewing daemon status on UNIX

Use the optstatus command to view Optivity NMS daemon status on UNIX . This command displays a list of daemons that are currently running. It also displays a list of daemons that are not running and shows the command and path name to execute them. The command syntax is:

optstatus -

Installing and Administering Optivity NMS 10.3

140 Administering Optivity NMS processes

where -f displays the status of all Optivity NMS daemons and –fe displays the daemons that are not running.

To view daemon status on a UNIX workstation:

➨ Open a command terminal window, and enter one of the following:

• optstatus -f Enter optstatus -f if you have installed Optivity on a network management station. A list of processes, their required status, and their current status displays.

• optstatus -fe Enter optstatus -fe to get an error report only, without the interrelationship of the daemons. If any of the daemons are not running, error messages are displayed. If daemons are not running, or if errors are displayed, reboot the system and pay attention to the system boot process to make sure that the Optivity daemons are loading along with the system.

Starting daemons on UNIX

To start an Optivity NMS daemon on a UNIX workstation:

1 Start a root session. 2 At the command line, enter: cd $LNMSHOME/opt_install

3 Enter: ./ic_restart start

optstatus –f The status of the Optivity NMS daemon that you specified at the command line is displayed.

To start all Optivity NMS daemon on UNIX:

1 Open a UNIX terminal window.

205969-H

Administering Optivity NMS processes 141

2 Enter: cd /usr/lnms/bin 3 Enter: optivity_apps start This command starts all Optivity NMS daemons.

4 To verify that daemons started, enter: optstatus -fe

Stopping daemons on UNIX

To stop a daemon from a UNIX command line:

1 Start a root session. 2 At the command line, enter: cd $LNMSHOME/opt_install

3 Enter: ./ic_restart stop

optstatus –f The status of the Optivity NMS daemons is displayed.

To stop all daemons:

1 Open a UNIX terminal window. 2 Enter:

cd /usr/lnms/bin 3 Enter: optivity_apps stop This command stops all Optivity NMS daemons.

Installing and Administering Optivity NMS 10.3

142 Administering Optivity NMS processes

4 Enter:

optstatus –f The status of the Optivity NMS daemons is displayed.

205969-H

143 Chapter 7 Managing Optivity NMS firewall support

This chapter describes how to manage the Optivity NMS firewall support feature. This feature lets you run Optivity NMS server software behind a firewall. It also lets you allow or deny access to Optivity NMS according to the client IP address.

Firewall support overview

In previous releases of Optivity NMS, running the client and server applications on different sides of a firewall was not supported. Starting with version 10.3, Optivity NMS incorporates a redirection server that manages communication between the Optivity NMS server and its clients. When enabled, this redirection server manages all communication through a single port in your firewall.

In addition to the redirection server, Optivity NMS 10.3 also lets you restrict communication with Optivity NMS server applications to only a list of trusted IP addresses. See “Restricting access according to IP address” on page 145 for more information.

Required firewall ports

In order to use the Optivity NMS firewall support feature, you must allow communication through at least three ports in your firewall for the following Optivity NMS components:

• Apache web server: default is port 80 • webOptSrvr: must be port 391 • Redirection server: any port greater than 1024

Installing and Administering Optivity NMS 10.3

144 Chapter 7 Managing Optivity NMS firewall support

You must set the ports both in your firewall configuration and in the Optivity NMS installation. You are prompted for the port numbers during the initial Optivity NMS software installation. You can also change the setting for the redirection server port after installation. See “Installing or activating the firewall support feature‚” next for more information.

Installing or activating the firewall support feature

You can enable the firewall support feature during the installation of Optivity NMS, or you can enable it after the installation:

• To enable the firewall support feature during the installation, respond yes when the installation prompts you if Optivity NMS servers will be running behind a firewall. • To enable the firewall support feature after the installation, you edit the firewall support configuration file to change the enable setting and also to specify the firewall port for client/server communication.

The firewall support configuration file is located as follows:

• On UNIX: $LNMSHOME/conf/weboptsrvr.conf • On Windows: %LNMSHOME%\conf\weboptsrvr.conf

The firewall support configuration file contains two parameters and their settings, for example:

STATUS=OFF PORT=50000

To enable the firewall support feature, edit the file so that the STATUS parameter is set to ON. To change the firewall port through which Optivity NMS communicates with the client applications, set the PORT parameter to any desired port number greater than 1024.

After editing the firewall support configuration file, you must stop and then restart all of the Optivity NMS daemons or services.

205969-H

Chapter 7 Managing Optivity NMS firewall support 145

Restricting access according to IP address

Optivity NMS lets you specify a list of trusted IP addresses that are allowed to communicate with Optivity NMS server applications. Access attempts by non-listed IP addresses is automatically blocked.

You can also specify a list of the client IP addresses that are behind the firewall and thus require no redirection by the redirection server.

You maintain the lists of IP addresses in the following file on the Optivity NMS server:

• On UNIX: $LNMSHOME/conf/restrictedIP.conf • On Windows: %LNMSHOME%\conf\restrictedIP.conf

This file contains descriptions and examples of its features in a comment block at its beginning, followed by actual tags and variables.

After editing the IP restriction file, you must stop and then restart all of the Optivity NMS daemons or services.

Installing and Administering Optivity NMS 10.3

146 Chapter 7 Managing Optivity NMS firewall support

205969-H

147 Appendix A Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5

This appendix describes how to configure Nortel Networks BCM (Business Communication Manager) devices and NetIQ Vivinet Manager so that Optivity NMS displays faults for BCM devices. The faults are based on traps sent to the Optivity NMS management station by NetIQ Vivinet Manager on behalf of the BCM devices. When so configured, InfoCenter also propagates fault status colors based on the NetIQ Vivinet Manager traps.

Figure 12 shows Fault Summary displaying BCM faults based on traps received from NetIQ Vivinet Manager on behalf of the BCM.

Figure 12 BCM faults displayed in Fault Summary

Installing and Administering Optivity NMS 10.3

148 Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5

Nortel Networks Business Communications Manager (BCM) is an IP-enabled communication system. The BCM integrates sophisticated voice and data capabilities, VoIP gateway functions, and QoS data routing features into a single system. The BCM provides a variety of desktop communications options and offers a broad choice of voice and data software applications, such as Unified Messaging and Multimedia Call Center, optimized for the small/medium business environment.

NetIQ Vivinet Manager lets you monitor various types of services on different devices. It is a management server communicating with its remote agents in devices. BCM 3.5 bundles NetIQ Vivinet Manager Agent software as part of its device agent software. The agent helps to gain easy access to diagnostics and management data from BCM. The agent collects data based on requests (in the form of jobs created from Knowledge Scripts) from Vivinet Manager. The NortelBCM package for Vivinet Manager includes Knowledge Scripts to monitor health, availability and performance of key BCM resources. By running jobs on these scripts from NetIQ Vivinet Manager, you can monitor operational status of BCM.

You can configure each Knowledge Script to send an alert, collect data for reporting, and perform automated problem management when an event occurs. You can configure the Knowledge Script to forward event details to the Optivity NMS server as SNMP traps. Optivity NMS version 10.3 includes trap and fault specifications for interpreting BCM 3.5 traps generated by NetIQ Vivinet Manager. Based on these specifications, Optivity NMS automatically processes and correlates BCM 3.5 trap. In this way, Optivity NMS lets you detect problems within the BCM operations and lets you monitor VoIP, QoS routing and other BCM services.

205969-H

Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5 149

System prerequisites

Table 20 describes the prerequisites for configuring NetIQ Vivinet Manager, Optivity NMS, and BCM as described in this document.

Table 20 System Prerequisites

Prerequisite Description NetIQ Vivinet Manager Vivinet Manager version 2.1, service pack 3 server version Optivity NMS version Optivity NMS version 10.2 BCM version BCM 3.5 Optivity NMS and Vivinet Nortel Networks recommends that the Optivity NMS server Manager server locations and Vivinet Manager server be located on different machines.

System configuration

To configure NetIQ Vivinet Manager, Optivity NMS, and BCM to work together:

1 Obtain the NortelBCM package from NetIQ. Contact your NetIQ sales representative for information about obtaining the Nortel BCM package zip file. See the NetIQ Web site at www.netiq.com for more information about contacting NetIQ.

Table 21 describes the contents of the NortelBCM package.

Table 21 NortelBCM package contents

File Description ReadMe.html Briefly describes how to install the NortelBCM package and how to activate the NetIQ Vivinet Manager agent on the BCM device. VM-NortelBCMWorkSmarter.pdf Contains Working Smarter with Vivinet Manager for Nortel Networks Business Communications Manager, an Acrobat document that describes how to monitor Nortel Networks BCM devices with NetIQ Vivinet Manager.

Installing and Administering Optivity NMS 10.3

150 Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5

Table 21 NortelBCM package contents (continued)

File Description VM2.1_NortelBCM.exe The Nortel BCM module that contains knowledge scrips for the NetIQ Vivinet Manager server. NetIQ4BCM3.5_Build2.4.exe Activates the NetIQ Vivinet Manager agent on the BCM device.

2 Activate Nortel BCM support as described in the following sections of Working Smarter with Vivinet Manager for Nortel Networks Business Communications Manager: • Step 1: Installing the Nortel BCM Module on the Vivinet Manager Server • Step 2: Activating NetIQ Support on the BCM • Step 3: Discovering Nortel BCM Resources with Vivinet Manager See Working Smarter with Vivinet Manager for Nortel Networks Business Communications Manager for more information.

3 Configure jobs on NetIQ Vivinet Manager to monitor the BCM using the NortelBCM Knowledge Scripts. You configure these jobs with specific trap numbers that Vivinet Manager forwards to Optivity NMS. See “Configuring Knowledge Scripts in NetIQ Vivinet Manager‚” next for more information.

Configuring Knowledge Scripts in NetIQ Vivinet Manager

Table 28 describes the Knowledge Scripts you can run for the BCM. For each Knowledge Script you run, you use the Actions tab to configure the value for Action_SnmpTrap and Action_ExtendedSNMPTrap (if applicable) as shown in Table 28. Setting these actions and values lets Vivinet Manager send SNMP traps to Optivity NMS with information about the status of the BCM device.

205969-H

Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5 151

To configure a Knowledge Script:

1 If you haven’t already done so, create a new job by dragging a knowledge script from the NORTELBCM Knowledge Scripts pane to the BCM device icon in the device tree in the left pane of the Vivinet Manager window. A Properties dialog box opens for the new job.

Note: Do not click OK on the job Properties dialog box until the end of this procedure. Clicking OK prematurely creates a job that is not completely configured. However, you will have to click OK on one or two action properties dialog boxes that you open from the job properties dialog box.

2 Click the Schedule tab to bring it to the front. 3 On the Schedule tab, set the values as shown in Table 22.

Table 22 Schedule properties

Property Setting Schedule type Regular intervals Every Minutes as interval time Start time Now End time No end date

4 Click the Values tab to bring it to the front. 5 On the Values tab, set the Event and Collect Data values as shown in Table 23.

Table 23 Value properties

Property Setting Event? [y/n] y Collect data? [y/n] y

6 Set all other Values properties for the Knowledge Script as required for your network configuration.

Installing and Administering Optivity NMS 10.3

152 Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5

See your Vivinet Manager documentation for detailed information about configuring knowledge scripts.

7 Click the Actions tab to bring it to the front. 8 Click New to create a new action. 9 In the row for the new action, click the Action cell and choose Action_SnmpTrap from the menu (Figure 13).

Figure 13 Choosing Action_SnmpTrap

10 In the Location, Type, and Schedule columns, keep the default values shown in Table 24:

Table 24 Default values for Action_SnmpTrap

Column Location Type Schedule

Value MS New Event Always

205969-H

Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5 153

11 Click the Properties button to open a Properties dialog box for the Action_SnmpTrap action. 12 In the Properties for Action_SnmpTrap dialog box, set the values shown in Table 25:

Table 25 Action_SnmpTrap properties

In this row: Enter: List of computers to receive SNMP The IP addresses of Optivity NMS servers, message separated by commas Community string The community string used in the trap. Use “public” or “optivity_autotrap”. Object Identifier keep the default (i.e., 1.3.6.1.4.1.1691.6.2) Specific trap number The SnmpTrap number for the Knowledge Script from Table 28 on page 156 Summarize event information? [y/n] n Custom message A custom message for the script

Figure 14 Properties for Action_SnmpTrap dialog box

SnmpTrap number from Table 28

Installing and Administering Optivity NMS 10.3

154 Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5

13 Click OK on the Properties for Action_SnmpTrap dialog box. 14 In Table 28 on page 156, check to see whether there is an Extended SnmpTrap value specified for the Knowledge Script for which you are configuring trap values. If so, continue with this procedure. If not, skip ahead to step 23. 15 On the Actions tab of the job Properties dialog box for the job that you opened in step 1, Click New to create a new action. 16 In the row for the new action, click the Action cell and choose Action_ExtendedSnmpTrap from the menu. 17 In the entry for the new action, set the values shown in Table 26:

Table 26 Values for Action_ExtendedSnmpTrap

Column Location Type Schedule

Value MS Event Down Always

18 Click the Properties button to open a Properties dialog box for the Action_ExtendedSnmpTrap action. 19 In the Properties dialog box for the extended action, set the following values:

Table 27 Action_ExtendedSnmpTrap properties

In this row: Enter: List of computers to receive SNMP The IP addresses of Optivity NMS servers, message separated by commas Community string The community string used in the trap. Use “public” or “optivity_autotrap” Object Identifier keep the default (i.e., 1.3.6.1.4.1.1691.6.2) Specific trap number The Extended SnmpTrap number for the Knowledge Script from Table 28 on page 156

20 Click OK on the Properties for Action_ExtendedSnmpTrap dialog box. 21 In the Properties dialog box for the job that you opened in step 1, click the Advanced tab to bring it to the front.

205969-H

Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5 155

22 On the Advanced tab, mark the check box for Generate a new event when original event condition no longer applies (Figure 15).

Figure 15 Job properties dialog box, Advanced tab

23 In the Properties dialog box for the job that you opened in step 1, click OK. NetIQ Vivinet Manager starts executing the job for the Knowledge Script. If you want to configure additional jobs for Knowledge Scripts, repeat this procedure starting with step 1.

Installing and Administering Optivity NMS 10.3

156 Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5

Knowledge Script trap numbers

Table 28 describes the NortelBCM Knowledge Scripts, and also lists the values that you enter as specific trap values when configuring SnmpTrap and ExtendedSnmpTrap actions for each Knowledge Script.

Table 28 NortelBCM Knowledge Scripts and trap numbers

Knowledge Description Script Name Action_SnmpTrap Action_SnmpTrap Event) (New SnmpTrap Extended Down) (Event NortelBCM_BCM_HealthCheck 1001 1002 Monitors the operational (up or down) status of Nortel BCM services. NortelBCM_BCM_QoSInterfaceActivity 1003 1004 Monitors the number of dropped packets for LAN and WAN links. NortelBCM_BCM_QoSLog 1005 1006 Monitors the MOS (Mean Opinion Score) scores for the following codecs: G.711a, G.711u, G.723 (5.3 kpbs), G.723 (6.3 kpbs), and G.729. NortelBCM_BCM_QoSPrioritySessions 1007 1008 Monitors the number of priority sessions for LAN and WAN links. Priority sessions are those that request to use the Premium queue 1. NortelBCM_BCM_QoSQueueUsage 1009 1010 Monitors the number of dropped packets for the queues of LAN and WAN links. NortelBCM_BCM_SystemUsage 1011 1012 Monitors total CPU, CPU interrupt handling time, physical memory usage, and memory pages/sec for the BCM. NortelBCM_Sys_AsciiLog 1013 Monitors an ASCII text file for specific strings and messages logged since the last monitoring interval. NortelBCM_Sys_CpuByProcess 1014 1015 Monitors whether specific processes have exceeded CPU thresholds. Also monitors CPU usage for each named process, as well as the total CPU usage for all named processes NortelBCM_Sys_CpuLoaded 1016 1017 Monitors both CPU usage and the queue length.

205969-H

Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5 157

Table 28 NortelBCM Knowledge Scripts and trap numbers (continued)

Knowledge Description Script Name Action_SnmpTrap Action_SnmpTrap Event) (New Extended SnmpTrap Down) (Event NortelBCM_Sys_DNSConnectivity 1018 1019 Checks the connectivity between a computer and its DNS server. NortelBCM_Sys_EventLog 1020 Monitors and filters information in the Event Log based on criteria that you specify. NortelBCM_Sys_FailedLogon 1021 Monitors failed logon attempts to the server since the last interval. NortelBCM_Sys_FileChanged 1022 Monitors any changes in size, timestamp, and attributes of a file from one interval to the next. NortelBCM_Sys_FilesCompare 1023 Monitors any changes in size, timestamp, and attributes of two files. NortelBCM_Sys_GeneralCounter 1024 Monitors any user-specified Performance Monitor counter. This script differs from Sys_IntervalCounter in that it takes a “snapshot” of a counter when you run the script; IntervalCounter monitors the change in a counter between one run of the script and the next. NortelBCM_Sys_IntervalCounter 1025 Monitors the change in any user-specified counter. This script differs from Sys_GeneralCounter in that it monitors the change in a counter between one run of the script and the next; GeneralCounter takes a “snapshot” of a counter when you run the script. NortelBCM_Sys_LogicalDiskSpace 1026 1027 Monitors logical disk space usage. NortelBCM_Sys_MemUtil 1028 1029 Monitors the usage of physical memory, virtual memory, and paging files. NortelBCM_Sys_PagingHigh 1030 1031 Monitors reads/writes per second to the pagefile. NortelBCM_Sys_ProcessDown 1032 1033 Determines whether specified processes are currently running and raises an event if any of the processes is down. NortelBCM_Sys_Processes 1034 1035 Monitors the number of active processes.

Installing and Administering Optivity NMS 10.3

158 Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5

Table 28 NortelBCM Knowledge Scripts and trap numbers (continued)

Knowledge Description Script Name Action_SnmpTrap Action_SnmpTrap Event) (New Extended SnmpTrap Down) (Event NortelBCM_Sys_ServiceChange 1036 Monitors any changes to user-specified services. NortelBCM_Sys_ServiceDown 1037 Checks whether any user-specified service is down; this script can start the service if you set it to do so. NortelBCM_Sys_ServiceHung 1038 Detects whether a specified service is hung; this script can kill or restart the service if you set it to do so. NortelBCM_Sys_SytemUpTime 1039 Monitors the number of hours that a system has been operational since its last reboot. NortelBCM_Sys_TopCpuProcs 1040 Monitors the CPU usage of all processes and identifies the top consumers. NortelBCM_Sys_TopMemoryProcs 1041 Monitors the memory usage of all processes and identifies the top consumers.

205969-H

Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5 159

Installing and Administering Optivity NMS 10.3

160 Configuring Optivity NMS and NetIQ Vivinet Manager to monitor BCM 3.5

205969-H

161 Appendix B Silent Installation answer file reference

The .ans answer file contains information used to configure the installation, and also to check your system to make sure that it meets the installation requirements. The Optivity NMS software includes template files that you can edit to create a .ans answer file that matches your requirements. The template files include parameters as well as comment text that describes each parameter.

Note: All parameters in the answer file must be assigned values. Leaving any parameter blank causes the silent installation to fail.

In the answer file, lines starting with pound signs (#) are comments and descriptions. These lines are ignored by the silent installation program.

The answer file template file is named template.rsp, and is located on the following installation CDs:

• Optivity NMS 10.3 for Windows* CLIENT and SERVER CD, in the \install\ directory • Optivity NMS 10.3 for Windows* CLIENT ONLY and Documentation CD, in the \install directory • Optivity NMS 10.3 for Solaris CLIENT and SERVER CD, in the /cdrom/ install/ directory • Optivity NMS 10.3 for HP-UX CLIENT and SERVER CD, in the /cdrom/ install/ directory

Installing and Administering Optivity NMS 10.3

162 Appendix B Silent Installation answer file reference

The following example shows the contents of a typical answer file:

# USER_SELECTED_COMPS components to be installed # USER_HTTPD_PORT port to run httpd server # USER_INST_DIR where to install ONMS # USER_DB_BACKUP backup DB # USER_DB_BACKUP_DIR where to backup DB # USER_AUTOTRAP_ENABLE enable autotrap registration # USER_SYSLOG_FILE path to syslog file (unix only)

# common section

USER_SELECTED_COMPS=server USER_INST_DIR=D:/opt/optivity

# Server components USER_SELECTED_OPT_COMPS=legacy USER_SELECTED_OPT_PLUG=voip, vpls,ipvpn USER_DB_BACKUP=n USER_DB_BACKUP_DIR=/opt/bay/install/dbbackup USER_CUST_RESTORE= y

# Apache USER_HTTPD_PORT=80

# NMSDB ORADATA=/opt/optivity

# Fault USER_AUTOTRAP_ENABLE=y USER_SYSLOG_FILE=/var/adm/messages

# weboptsrv USER_FIREWALL_ENABLE=n USER_REDIRECT_PORT=50000

# Client components

# Legacy components

205969-H

Appendix B Silent Installation answer file reference 163

Table 29 describes the options and settings for the answer file.

Table 29 Answer file options

Option Range Description USER_SELECTED_COMPS [client][server] Optivity NMS components to install USER_HTTPD_PORT valid port Port for Apache httpd server USER_INST_DIR valid directory Directory in which to install Optivity NMS USER_DB_BACKUP y|n Whether or not to backup the database USER_DB_BACKUP_DIR valid directory Directory in which to backup the database USER_AUTOTRAP_ENABLE y|n Whether or not to enable autotrap registration USER_SYSLOG_FILE valid directory Path to syslog file (UNIX only) USER_SELECTED_OPT_COMPS [legacy] Selects Optivity NMS components to install USER_SELECTED_OPT_PLUG [voip][vpls][ipvpn] Plug-ins to install USER_CUST_RESTORE y|n Selects whether to restore backed-up customizations ORADATA valid directory Indicates the Oracle home directory USER_FIREWALL_ENABLE y|n Whether or not to enable firewall support. See Chapter 7, “Managing Optivity NMS firewall support,” on page 143 for more information. USER_REDIRECT_PORT valid port The port for the firewall support feature.

Installing and Administering Optivity NMS 10.3

164 Appendix B Silent Installation answer file reference

205969-H

165 Appendix C Optivity NMS 10.3 installed directories and files

This appendix lists and describes the directories created by the Optivity NMS Installation program for UNIX and Windows during installation.

This appendix includes the following sections:

• “Optivity NMS 10.3 for UNIX directory structure‚” next • “Optivity NMS for UNIX miscellaneous directories and files” on page 167 • “HP NNM for Solaris directories and files” on page 168 • “Optivity NMS application control files” on page 168 • “Optivity NMS log files” on page 169 • “Optivity NMS configuration files” on page 170 • “Optivity NMS 10.3 for Windows directories and files” on page 171

Optivity NMS 10.3 for UNIX directory structure

Table 30 describes the $LNMSHOME directories (the default directories into which Optivity NMS 10.3 is installed) that are created on a management station running Solaris.

Table 30 Optivity NMS 10.3 $LNMSHOME core installation directories

Directory Contents $LNMSHOME/apache Apache Web server. $LNMSHOME/apps Files used by application at start up and/or run time. $LNMSHOME/bin Optivity application executables. $LNMSHOME/boxdb Pixmap references for building Expanded Views for System 3000 and System 2000 hubs. $LNMSHOME/cgi-bin Common Gateway Interface (CGI) scripts for the Apache Web Server.

Installing and Administering Optivity NMS 10.3

166 Appendix C Optivity NMS 10.3 installed directories and files

Table 30 Optivity NMS 10.3 $LNMSHOME core installation directories (continued)

Directory Contents $LNMSHOME/classes Jar files that contain class files for Web and application mode. $LNMSHOME/conf Configuration files for Optivity integrated applications. $LNMSHOME/db Database files. $LNMSHOME/help Optivity help files. $LNMSHOME/html All client startup files for Web support. $LNMSHOME/images Optivity.GIF files used for icons, screens, etc. $LNMSHOME/jre Java Run-Time Environment used for running Java programs. $LNMSHOME/lib Shared libraries for the entire Optivity product. $LNMSHOME/lock Text files to prevent the same instance of multiple servers from running. $LNMSHOME/log Repository for daemon and process startup log files. $LNMSHOME/openview Optivity icons and icon masks. (Used with Network Node Manager only) $LNMSHOME/opt_install Optivity process startup scripts. $LNMSHOME/platform Management platform-related files. $LNMSHOME/srconf SNMP stack configuration files. These files are generated by the MIB /etc/srconf Compiler. $LNMSHOME/unsupported Scripts and utilities not currently supported by Nortel Networks. $LNMSHOME/version Optivity application version numbers. $LNMSHOME/registration/ Application registration files for Optivity NMS 10.3 Client/Server weboptsrvr communication. $LNMSHOME/registration/plugin Registration files for plugin.

205969-H

Appendix C Optivity NMS 10.3 installed directories and files 167

Optivity NMS for UNIX miscellaneous directories and files

Table 31 describes the miscellaneous Optivity NMS 10.3 directories and files.

Table 31 Optivity NMS miscellaneous directories and files

Directory/file Operating system Contents /tftpboot Solaris Default system TFTP directory. /etc/bootptab Solaris Configuration file for BootP. /etc/group Solaris, HP-UX System group membership file. /etc/hosts Solaris, HP-UX Maps Internet Protocol (IP) address to host names and alias host names. /etc/hostname.[interface] Solaris System file used to map a physical network interface to a hostname. /etc/inetd.conf Solaris, HP-UX System configuration file for network daemons. (e.g.TFTP) /etc/init.d and /etc/rcX.d Solaris System directories containing scripts used during boot and shutdown. /sbin/init.d and /sbin/rcX.d HP-UX System directories containing scripts used during boot and shutdown. /etc/nsswitch.conf Solaris, HP-UX System file used to define name resolution parameters. /etc/optivity Solaris, HP-UX Optivity NMS installation parameter files. /etc/passwd Solaris, HP-UX System user password file. /etc/resolv.conf Solaris, HP-UX System file used to define a Domain and Domain NameServer. /etc/services Solaris, HP-UX System file for defining IP ports used by network processes. (e.g. trapd, snmpd) /usr/lib Solaris, HP-UX System library directory. (only symbolic links created) /usr/lib/X11/app-defaults Solaris, HP-UX X11 application resource files. ~/.LNMSdefaults* Solaris, HP-UX Specifies default values for different applications, token ring NodalView formulas for color changes, object tools definitions, Poll Interval and Timeout Interval for Expanded View and Network Atlas* Data Link View.

* “~/”=the login user’s home directory

Installing and Administering Optivity NMS 10.3

168 Appendix C Optivity NMS 10.3 installed directories and files

HP NNM for Solaris directories and files

Table 32 describes the Hewlett Packard Network Node Manager (NNM) for Solaris-specific directories and files.

Table 32 HP Network Node Manager (NNM) specific directories

Directory/file Contents /etc/opt/OV/share/registration Registration files for menu options. /etc/opt/OV/share/fields Files that define the attributes an NNM object can have. /etc/opt/OV/share/symbols Symbols used on an NNM map. /etc/opt/OV/share/conf/oid_to_sym Maps Object IDs to symbols on NNM map. /etc/opt/OV/share/conf/oid_to_type Maps Object IDs to defined types of objects on NNM map. /etc/opt/OV/share/conf/C/trapd.conf Interprets SNMP traps received. /etc/opt/OV/share/conf/ovsnmp.conf ASCII representation of NNM SNMP database. (Do not edit this file manually. Use the xnmsnmpconf application only.) /opt/netls NNM License server primary directory (Solaris) /opt/OV/bin Executables used by NNM. /opt/OV/bin/ov.envvars.[shell] Script that sets NNM environment variables. /var/opt/netls NNM License server database directory (Solaris) /var/opt/OV/share/databases NNM map and database directories. /var/opt/OV/share/snmp_mibs Available MIBs. (e.g. used by NMM SNMP browser) /var/opt/OV/share/log Directory containing log files for NNM processes.

Optivity NMS application control files

Table 33 describes Optivity NMS control files. Do not edit these files.

Table 33 Optivity NMS control files

Path name Description $LNMSHOME/apps/appcontrol/accessadmin90.txt Used when Access Control administration is enabled. $LNMSHOME/apps/appcontrol/EVConfAppData.txt Expanded View uses this file. $LNMSHOME/apps/appcontrol/fc.txt The Fault Correlator daemon uses this file. $LNMSHOME/apps/appcontrol/ic.txt InfoCenter uses this file.

205969-H

Appendix C Optivity NMS 10.3 installed directories and files 169

Table 33 Optivity NMS control files (continued)

Path name Description $LNMSHOME/apps/appcontrol/launch.txt Applications, such as Call View, OmniView, Expanded View, and Fault Summary use this file. $LNMSHOME/apps/appcontrol/SMConfApiData.txt Used for segment information. $LNMSHOME/apps/appcontrol/superp.txt Used for Super Ping. $LNMSHOME/apps/appcontrol/TrapRegData.txt The Trap Registration daemon uses this file. $LNMSHOME/apps/appcontrol/mon_def_no_treg.txt $LNMSHOME/apps/appcontrol/preference.txt $LNMSHOME/apps/appcontrol/superp.txt $LNMSHOME/apps/appcontrol/tmp_launch_db.txt $LNMSHOME/apps/appcontrol/eb_launched.txt Fault summary launch data $LNMSHOME/apps/appcontrol/syslogRegData.txt Syslog registration data

Optivity NMS log files

Table 34 describes the Optivity NMS log files.

Table 34 Optivity NMS log files

File Description $LNMSHOME/log/apa.log Path Trace log file. $LNMSHOME/log/fc_daemon_root.log Fault Correlator daemon log file. $LNMSHOME/log/EBServer_root.log Faults log file. $LNMSHOME/log/ebd_root.log Fault summary daemon log file $LNMSHOME/log/InfoCenter.log InfoCenter daemon log file. $LNMSHOME/log/state_recdr_root.log Fault State Recorder local file. $LNMSHOME/log/super_ping_root.log Super Ping log file. $LNMSHOME/log/topology/*.log Directory in which topology log files, topcd.log, toprt.log, topdt.log, toppv.log files, are located. $LNMSHOME/log/trapsrvr_root.log Trap server log file. $LNMSHOME/log/trapreg_root.log Trap registration log file $LNMSHOME/log/NotificationServer.log Notification server log file

Installing and Administering Optivity NMS 10.3

170 Appendix C Optivity NMS 10.3 installed directories and files

Table 34 Optivity NMS log files (continued)

File Description $LNMSHOME/log/div_root.log Device Inventory Viewer log file $LNMSHOME/log/syslogproc_root.log Syslog processor log file $LNMSHOME/log/syslogreg_root.log Syslog registration log file $LNMSHOME/log/script_Serverroot.log Script server log file $LNMSHOME/log/DivServer_root.log Device Inventory Viewer server log file /opt//bay/install_optivity.log Optivity installation log file. Installation information is written to the install_optivity.log file. Uninstallation information is appended to the file. If there are previous instances of the install_optivity.log file in the same location (a file with the same name is in the location during an Optivity installation), the file is backed up with a file name install_optivity.log.snpx.1 or install_optivity.log.snpx.2, and so forth. There is only one file named install_optivity.log, which logs information about the current installation. /opt//bay/install/oracle/db_install.log Database installation log file /opt//bay/install/oracle/oracle_install.log Oracle software installation log file /opt//bay/install/oracle/oracle_preinstall.log Oracle software preinstallation log file

Optivity NMS configuration files

Table 35 describes the Optivity NMS configuration files.

Table 35 Optivity NMS configuration files

File Description $LNMSHOME/apps/appcontrol/superp.txt Super Ping configuration file. $LNMSHOME/conf/optivityUX.dep Dependency file used by optstatus to check for processes. $LNMSHOME/apps/fc/trap_specs/*.txt Traps specification files. $LNMSHOME/apps/fc/fault_specs/*.txt Fault specification files. $LNMSHOME/conf/dbprofile.conf Contains Oracle database-related parameters for the applications runtime environment and some application-specific customizable parameters.

205969-H

Appendix C Optivity NMS 10.3 installed directories and files 171

Optivity NMS 10.3 for Windows directories and files

Table 36 describes the Optivity NMS 10.3 installed directory structure on a Windows management station

Table 36 Optivity NMS 10.3 for Windows-specific directories and files

Directory Description \Optivity\lnms\legacy\campus\bin Optivity Campus application executables. \Optivity\lnms\legacy\campus\db Optivity Campus database. \Optivity\lnms\legacy\campus\unsuppt Scripts and utilities not currently supported by Nortel Networks. \Optivity\lnms\Apache Apache Web Server. \Optivity\lnms\apps Files used by applications at startup and/or runtime. \Optivity\lnms\bin Optivity application executables. \Optivity\lnms\cgi-bin Common Gateway Interface (CGI) scripts for the Apache Web Server. \Optivity\lnms\classes Jar files that contain class files for Web and application mode. \Optivity\lnms\conf Configuration files for Optivity integrated applications. \Optivity\lnms\db Database files. \Optivity\lnms\help Optivity help files. \Optivity\lnms\html All client startup files for Web support. \Optivity\lnms\images Optivity *.GIF files used for icons, screens, etc. \Optivity\lnms\jre Java Runtime Environment used for used for running Java programs. \Optivity\lnms\lib Shared libraries for the entire Optivity product. \Optivity\lnms\lock Text files to prevent the same instance of multiple servers from running. \Optivity\lnms\log Repository for daemon and process startup log files. \Optivity\lnms\openview Optivity icons and icon masks. (Used with Network Node Manager only)

Installing and Administering Optivity NMS 10.3

172 Appendix C Optivity NMS 10.3 installed directories and files

Table 36 Optivity NMS 10.3 for Windows-specific directories and files (continued)

Directory Description \Optivity\lnms\schemas Optivity schema files. \Optivity\lnms\srconf SNMP stack configuration files. These files are generated by the MIB Compiler. \Optivity\lnms\unsupported Scripts and utilities not currently supported by Nortel Networks. Optivity\lnms\registration\weboptsrvr Application registration files for Optivity NMS 10.3 Client/ Server communication. \Optivity\lnms\registration\plugin Registration files for plugins \Optivity\Oit\accelar Optivity Integration Toolkit packages for Accelar Device Manager application element management products. \Optivity\Oit\annexmanager Optivity Integration Toolkit packages for Annex Manager element management product. \Optivity\Oit\apps Optivity Integration Toolkit packages for Annex Manager element management product. \Optivity\Oit\BayStackAPManager Optivity Integration Toolkit packages for BayStack* AP Manager device and application element management products. \Optivity\Oit\passport Optivity Integration Toolkit packages for Passport device management. \Optivity\Oit\pcaptap Router management Pcap and Network Tap applications. \Optivity\Oit\sitemanager Optivity Integration Toolkit packages for router management Site Manager element management product. \Optivity\Oit\vcu Optivity Integration Toolkit packages for Remote Access Versalar Configuration Utility element management product. \opt\nmsadm\log\preinstall.log Installation and uninstallation log files \opt\nmsadm\log\postinstall.log

205969-H

173 Appendix D Troubleshooting Optivity NMS

This appendix describes how to resolve some of the Optivity NMS problems that may occur. It describes how to view troubleshooting information from the Optivity NMS online Help systems.

Before you install Optivity NMS

Nortel Networks strongly recommends you read the Release Notes for Optivity NMS 10.3 before you install Optivity NMS. This document contains the latest information about Optivity NMS, including informational notes, known problems, and bug fixes.

Using the Optivity NMS install log file

The Optivity NMS. Install and Uninstall programs create log files that you can use to troubleshoot problems that may occur during the install or uninstall process.

The install and uninstall log files are named as shown in Table 37.

Table 37 Install/Uninstall log file names

Environment Names Windows • OptivityNMS101_install.log • OptivityNMS101_uninstall.log • onms_db.log UNIX install_optivity.log

Installing and Administering Optivity NMS 10.3

174 Appendix D Troubleshooting Optivity NMS

The log files are created in the folders or directories shown in Table 37

Table 38 Install/Uninstall log file locations

Environment Location Windows NT Folder defined by system variable temp Windows 2000 Based on system configuration, it could be in the system temp location or the user temp location. • Folder defined by system variable temp, if defined • If no temp variable is defined, in the /winnt/temp folder of the system drive UNIX /opt/nmsadm/log/

Viewing daemon status

The status shown by the Services dialog box may not represent the current state of Optivity NMS daemons. Nortel Networks recommends that you run the optstatus command from the command line. For more information about using optstatus, see “Viewing daemon status on UNIX” on page 79 or “Viewing services status on Windows” on page 77.

Operational notes

This section provides information for operating Optivity NMS 10.3 on your management station.

Oracle installation hangs (HP-UX)

Sometimes, the Oracle Universal Installer hangs when installing the Oracle database software on HP-UX. When this happens, the installActions.log file contains the text “Calling query Protocol_Queries1.1.1 DetectNetworkProtocols.”

205969-H

Appendix D Troubleshooting Optivity NMS 175

This problem is caused by a hanging swlist process spawned from Universal Installer. To fix this problem:

1 Execute the following command to get the process ID: ps -ef | grep swlist 2 Execute the following command to kill the process: kill -9

Oracle operational note

The Oracle software is installed by the Oracle Universal Installer. The Oracle installation log files are located at:

\program files\Oracle\Inventory\logs.

Oracle provides the following log files:

• installActions.log—This file contains information about the most recent sessions. Previous install and uninstall sessions are backed up to the same location with the date and time stamp suffixed to the file name. For example: InstallActions2002-03-12-05-18-28-PM.log

Optivity Integration Toolkit operational note

On client-installed systems, the external chassis image directory is missing for Optivity Integration Toolkit (OIT) devices.

If you run oitinstall to add new OIT devices subsequent to installing Optivity NMS 10.3, you must transfer the GIF files to the images/external directory on the client machine.

• On the Windows NT or Windows 2000, copy the GIF files to: drive: \Optvity\nms\images\external • On the UNIX platform, copy the GIF files to: /usr/lnms/images/external

Installing and Administering Optivity NMS 10.3

176 Appendix D Troubleshooting Optivity NMS

Trap Server operational note

There is a known operational problem with the Optivity NMS trap server starting on Windows NT or Windows 2000.

On the HP Open View and platformless system, port number 162 must not be used by any other application. Do not install a Windows NT SNMP trap service using port 162.

There are two ways to resolve the port 162 conflict:

1 Stop the Windows NT SNMP Trap service. 2 To assign another port for the Windows NT SNMP Trap service, modify the port number of the Windows NT SNMP Trap service in the C:\winnt\system32\drivers\etc\services file.

To resolve the port 162 conflict on the NetView management platform, disable the Windows NT SNMP Trap service.

Troubleshooting database silent installation on Windows

The log file specified with the -f2 option while running silent installation for the Oracle database software is very useful in determining whether the database installation completed successfully or not. The contents of a typical silent install log file for a successful Optivity NMS install are shown below.

[InstallShield Silent] Version=v5.00.000 File=Log File [ResponseResult] ResultCode=0

The ResponseResult section of the log file contains the result code indicating whether or not the silent setup succeeded. An integer value is assigned to the ResultCode keyname in the ResponseResult section.

205969-H

Appendix D Troubleshooting Optivity NMS 177

A result code of zero indicates that the silent installation was successfully completed. When a non zero result code is obtained, refer to Table 39 for more information. Also view the Optivity NMS installation log files for more information.

Table 39 gives the various possible values that may be assigned to the result code.

Table 39 Windows silent installation result codes

Resultcode Description Value 0 Success. -1 General error. -2 Invalid mode. -3 Required data not found in the Setup.iss file. -4 Not enough memory available. -5 File does not exist. -6 Cannot write to the response file. -7 Unable to write to the log file. -8 Invalid path to the InstallShield Silent response file. -9 Not a valid list type (string or number). -10 Data type is invalid. -11 Unknown error during setup. -12 Dialog boxes are out of order. -51 Cannot create the specified folder -52 Cannot access the specified file or folder. -53 Invalid option selected.

Make sure that a valid path is given as destination for Optivity NMS or for Oracle installation. Failure to do so may result in a resultcode of -12. Result code -5 indicates that there may be something wrong in the path to the .iss file, or we are pointing to an .iss file from a different Installshield version. Result code -3 indicates that the response file may be inappropriate to the installation workflow that you are trying to perform.

Installing and Administering Optivity NMS 10.3

178 Appendix D Troubleshooting Optivity NMS

Using verify_connect92.bat to resolve a connection test failure

This section describes Nortel Networks recommended workflow to resolve a connection test failure. The Optivity NMS Database Installer programs runs the verify_connect92.bat batch file to verify connectivity with svrmgrl.exe. If the test fails, you can run verify_connect92.bat to determine why the connection test failed.

This section provides information about verify_connect92.bat and is organized as follows:

• “What verify_connect92.bat does‚” next • “verify_connect92.bat error messages” on page 179

The syntax and command line options for verify_connect92.bat are as follows:

verify_connect92.bat -o [value of ORACLE_HOME] -t [value of temp location]

What verify_connect92.bat does

When you run verify_connect92.bat manually, the batch file setups a temporary database service to test for connectivity to svrmgl.exe as follows:

1 Checks that you are using the command line options correctly. verify_connect92.bat -o -t 2 Creates a dummy Oracle instance service called dummydb using the Oradim utility. 3 Sets the oracle_sid variable to dummydb. 4 Starts svrmgrl.exe (which is a shell by itself). 5 Executes the following command within the svrmgrl shell: connect internal/oracle 6 If the connection test passes, svrmgrl.exe prints: “connected.” 7 Exits the svrmgrl shell.

205969-H

Appendix D Troubleshooting Optivity NMS 179

8 Parses the output for the word “connected.” If “connected” is the output result, the connection test succeeded.

The verify_connect92.bat batch file detects the following problems:

• You used invalid command line options. • In the bin directory within the ORACLE_HOME provided in the command line, verify_connect92.bat could not find oradim and svrmgrl. • Did not get the “connected” output from the session it has with svrmgrl.exe. • If the test passes, the verify_connect92.bat ERROR_FLAG variable is set to OFF and displays a message that the test is succeeded. • If the test fails, the verify_connect92.bat ERROR_FLAG variable is set to ON, displays a message that the test is failed, and displays a reason for the failure.

If you cannot resolve the connection test problem, do one of the following:

• Use the Optivity Database Installer to install Oracle Standard version 9i in a different location. • Use another valid Oracle database software installation. verify_connect92.bat error messages

The following examples describe error messages that verify_connect92.bat outputs based upon test results:

Example 1: Usage error

Error using the verify_connect92.bat command line options. For example, the command is entered as:

L:\scripts>L:\scripts\verify_connect92.bat

The system displays the following message:

Error in usage! the command line arguments are as follows:

Usage: verify_connect92.bat -o [value of ORACLE_HOME] -t [value of temp location]

Installing and Administering Optivity NMS 10.3

180 Appendix D Troubleshooting Optivity NMS

Error using the verify_connect92.bat batch file command correctly:

The ERROR_FLAG=ON

“Invalid usage of batch file command”

Example 2: Usage error—File missing

The following system message is the result of a file not being found in the bin directory.

ERROR! Unable to find oradim.exe in the path d:\orant\bin

The ERROR_FLAG=ON

The ERROR_TYPE=”Unable to find oradim.exe in d:\orant\bin”

Example 2: Connection test passed

The system displays the following message if the connection test passes.

The Connection to svrmgrl.exe succeeded The ERROR_FLAG=OFF

Troubleshooting Optivity NMS applications

Optivity NMS online Help includes troubleshooting information for each Optivity NMS 10.3 application. To view the Help from an application menu bar, choose Help > Help. In the online Help system, select the Troubleshooting or Resolving Problems Help topics.

Administering Optivity NMS databases

To backup an Optivity NMS database:

1 Open a command window.

205969-H

Appendix D Troubleshooting Optivity NMS 181

2 Enter: $LNMSHOME/bin/output_db_contents -db

To restore an Optivity NMS database:

1 Open a command window. 2 Enter: $LNMSHOME/bin/input_db_contents -db

For more detailed information about administering Optivity NMS 10.3 databases, see Using Optivity NMS 10.3 Applications (part number 207569-G) or see the Database Admin Tool Online Help system.

Autotopology Manager

The AutoTopology log file is located in the $LNMSHOME/log/topology directory. You can set the level of topology per subnet and device using the Optivity NMS Monitor Level application. Check the debug/log file information when you discover the network using Topui or by setting the same options at the command prompt.

Do not start other Optivity NMS applications during the discovery process. Doing so may cause AutoTopology to fail. To ensure that the discovery process is complete, look for the “Router and Subnet discovery completed” message.

Nortel Networks recommends that you use the AutoTopology Manager to configure discovery options. For more information, see Using Optivity NMS 10.3 Applications (part number 207569-G) or Optivity NMS AutoTopology Manager online Help.

Installing and Administering Optivity NMS 10.3

182 Appendix D Troubleshooting Optivity NMS

InfoCenter

Setting the environment flag “OPTIVITY_INFOCENTER_DEBUG” to “TRUE” logs debug information to the log file and also to the shell. This is true only when the InfoCenter server is started from a shell that is not a background process.

Weboptsrvr

The debug flags for Weboptsrvr should be: “OPTIVITY_WEBOPTSRVR_DEBUG=TRUE”

If the client user interface is an applet on a client machine, start Java console and press “9” (number 9) in the console window. This works for the Netscape browser.

On a Windows NT or Windows 2000 system, make sure the domain name servers are up and running. Since weboptsrvr on Windows NT relies on a domain name server through a Win32 system call, anything wrong in an NT domain backfires on the operating system which, in turn, affects weboptsrvr.

Versalar Config Utility http port 80 conflict

On UNIX, Windows NT, or Windows 2000, there is an http port conflict between Optivity NMS 10.3 and the Versalar Config utility.

The Versalar Config utility is a Java Web-based application that uses port 80 to listen for http requests through a Web server. By default, Optivity NMS 10.3 also uses port 80 to listen for http requests through its Apache Web server.

To resolve the conflict with the http port 80, do the following:

1 Start the Optivity NMS 10.3 installation. 2 When you are prompted to specify the Web Server Port Number, change the port number from 80 to 8080. 3 Continue with the Optivity NMS 10.3 installation.

205969-H

Appendix D Troubleshooting Optivity NMS 183

Site Manager and Network Node Manager port 161 conflict

By default, both Site Manager and Network Node Manager use port 161. This is a known issue and is documented in CSB 9811003.

Although the port conflict is between Site Manager and Network Node Manager, the same conflict may occur with Optivity NMS 10.3.

When the Site Manager application runs on Windows NT where Network Node Manager is installed, Site Manager may recognize a port conflict and display the following error message:

Connection failed, snmp agent not responding, Check IP address, and community. Time out and retries are to be increased.

When Network Node Manager is installed, the services file located at ~\winnt\system23\drivers\etc\services is modified. The services file contains Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) port mappings. Port 161 (the default port for Simple Network Management Protocol (SNMP) communication) is changed from 161 to port 8161, which leaves no port mapped for Site Manager or any other SNMP standard applications.

To resolve this problem, do the following:

1 Open the services file in a text editor, such as Notepad. 2 Type the following line above the SNMP 8161/udp entry: SNMP 161/udp For example, the services file should have the following entries:

SNMP 161/udp SNMP 8161/udp 3 Save the file and exit the text editor.

Installing and Administering Optivity NMS 10.3

184 Appendix D Troubleshooting Optivity NMS

Resolving Optivity NMS database installer issues

When you execute Setup.exe on the Optivity NMS Database Installer CD for the first time, the database installer program installs the Oracle database management software.

When the database installer is started the second time (maintenance mode), on the same system, the database installer performs an uninstall function and removes the few registry entries that were created during the first installation process and the shortcut on the Windows Program menu.

However, if the uninstall is aborted or encounters problems, it might leave behind a few registry entries that will hinder subsequent attempts to install Oracle software from the database installer CD.

In that case, there just a few registry entries that need to be removed.

To remove the registry entries:

1 From the Windows Start menu, click run. 2 Enter: regedit 3 Find and delete the following keys: HKEY_LOCAL_MACHINE\SOFTWARE\Nortel Networks\Optivity NMS Database Installer

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersi on\Uninstall\{DF771372-6696-11D5-A7A8-00B0D084C20B}

205969-H

185 Index

Symbols community strings described 127 $LNMSHOME specifying for Optivity NMS device directories, default 165 discovery 126 configuration files A BootP 167 Access Control Administration, overview 131 SNMP stack 166 apa.log file 169 configuration files, Optivity NMS fault_specs 170 Apache Web Server optivity90.dep 170 location 165 superp.txt 170 Application Launch 130 trap_specs 170 using 130 control files, Optivity NMS 168 applications, Optivity NMS 180 conventions, text 20 ATM Call View 134 customer support 23 Autotopology Manager discovery seed, creating 128 Help, getting 129 D log files 181 daemons network layer topology 129 status, viewing using optstatus subnet topology 129 UNIX 139, 174 topology progress, viewing 129 windows 137 daemons, Optivity NMS B starting under UNIX 140 starting underWindows 137 BootP configuration file 167 stopping 141 stopping under Windows 138 C database Campus license 26 Oracle software 69 CD, mounting user 28 in the HP-UX environment 97 database files, Optivity NMS, location 166 client/server model, Optivity NMS database, Optivity NMS, deleting 180 single server/multiple clients 30 device support single server/single client 29 Optivity Integration Toolkit, using 30

Installing and Administering Optivity NMS 10.3 186 Index directory structure single server/single client 29 Network Node Manager for Solaris 168 Installation program for Optivity NMS Optivity NMS for UNIX 165 overview 25 Optivity NMS for Windows 171 installation scenarios 69 Solaris-specific 167 discovery seed creating 128 L Display windows, InfoCenter language formats 133 operating system 40, 68, 92 layers 133 legacy applications 28 layouts 133 license level 26 licensed software 34, 35, 40, 54, 69, 85, 116 E log files, Optivity NMS 169 end node topology 129 apa.log 169 Enterprise and Enterprise Upgrade license 26 Autotopology Manager 181 fc_daemon_root.log 169 evaluation software 26, 40, 54, 85, 116 FSServer_root.log 169 Expanded View 133 InfoCenter.log 169 install 170, 173 F state_recdr_root.log 169 topology 169 Fault Summary 134 trapreg_root.log 169 fault_specs file 170 trapsrvr_root 169 fc_daemon_root.log file 169 logging in to Optivity NMS FSServer_root.log file 169 server host name 125 logging into Optivity NMS H password 125 user ID name 124 Help Autotopology Manager 129 Optivity NMS file location 166 N Optivity NMS, viewing 20, 134, 180 network layer topology 129

I O InfoCenter OIT OPTIVITY_INFOCENTER_DEBUG flag 182 overview 30 using the first time 125 type of files on Web 31 InfoCenter.log file 169 OIT inventory tool 32 install log file 170, 173 OmniView 133 install parameters file 167 opstatus command installation configurations, Optivity NMS parameters 140

205969-H

Index 187

using under UNIX 139 optstatus command using under Windows 137 syntax 139 Optivity NMS using 139 applications, troubleshooting 180 Oracle database management system 28 control files 168 Oracle database software 69 daemons 135 starting under UNIX 140 starting under Windows 137 P status, viewing using optstatus 137, 139 package contents, Optivity NMS 9.1 stopping 141 Solaris 35 stopping under Windows 138 Windows 34 directory structure, Windows 171 Windows NT 34 Help, viewing 180 password, logging into Optivity NMS 125 log files 169 Solaris system requirements 65 product support 23 system requirements protocol discovery 129 Windows 38, 91 publications Optivity NMS 9.1 34 hard copy 23 client/server model 29 related 22 legacy applications 28 package contents 34 R package contents, Optivity NMS 9.1 Solaris 35 related publications 22 uninstalling on Windows 60 Release Notes for Optivity NMS 9.0.1 34 Optivity NMS applications Release Notes for Optivity NMS 9.1 22, 173 Access Control Administration 131 requirements Application Launch 130 Optivity NMS for Solaris 65 ATM Call View 134 Optivity NMS for Windows 38, 91 Expanded View 133 resources Fault Summary 134 discovering using Autotopology Manager 128 Help, getting 134 OmniView 133 Optivity NMS Client 27 S Optivity NMS database 28 security user-based 127 Optivity NMS database, populating 128 server host name, logging in to Optivity NMS 125 Optivity NMS for UNIX, directory structure 165 silent installation Optivity NMS Help system 20 troubleshooting for Windows 176 Optivity NMS Server single server/multiple client configuration Apache Web Server 27 described 30 memory requirement 38 illustrated 30 optivity90.dep file 170 single server/single client configuration

Installing and Administering Optivity NMS 10.3 188 Index

described 29 V illustrated 29 views, InfoCenter SNMP stack configuration files 166 formats 133 Solaris layers 133 Network Node Manager directories 168 layouts 133 Optivity NMS directories 167 startup scripts, Optivity NMS 166 W state_recdr_root.log 169 weboptsrvr subnet topology 129 OPTIVITY_WEBOPTSRVR_DEBUG superp.txt file 170 flag 182 support, Nortel Networks 23 system requirements, Optivity NMS Windows 38, 91 system requirements, Optivity NMS for Solaris 65

T technical publications 23 technical support 23 text conventions 20 TFTP directory 167 topology log files 169 trap_specs file 170 trapreg_root.log file 169 trapsrvr_root.log 169 troubleshooting applications, Optivity NMS 180

U Uninstall program Windows database, backing up 61 starting 60, 61 uninstalling Optivity NMS 9.1 for Windows 60 user ID name, logging into Optivity NMS 124 user password file 167 user-based security model (USM) 127 USM 127

205969-H