Netview Migration

Tivoli NetView for UNIX and Linux
Version 7.1.5
Installation Guide
GC32-1842-00
Tivoli NetView for UNIX and Linux
Version 7.1.5
Installation Guide
GC32-1842-00
Note Before using this information and the product it supports, read the information in Notices on page 85.
First Edition (October 2006) This edition applies to version 7, release 1, modification 5 of IBM Tivoli NetView (product number 5698-NTV) and to all subsequent releases and modifications until otherwise indicated in new editions. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
About this guide . . . . . . . . . . . v
Who should read this guide . . . . . . . . . v Publications . . . . . . . . . . . . . . v IBM Tivoli NetView for UNIX and Linux library . v Accessing terminology online . . . . . . . vi Accessing publications online . . . . . . . vi Ordering publications . . . . . . . . . . vii Tivoli technical training . . . . . . . . . . vii Support Information . . . . . . . . . . . vii Participating in newsgroups . . . . . . . . . vii Conventions used in this guide . . . . . . . viii Typeface conventions . . . . . . . . . . viii Installing the Tivoli NetView Framework patch before integrating with the Tivoli Management Framework . . . . . . . . . . . . . Installing or upgrading to version 7.1.5 . . . . . Procedure . . . . . . . . . . . . . . Command syntax for the instalnv script . . . . Installing Tivoli NetView optional software . . . . Installing, upgrading, and configuring the Web console . . . . . . . . . . . . . . . Installing updates to the Web console. . . . . AIX system: Installing and configuring the trapgend daemon . . . . . . . . . . . AIX system and Solaris environment: Installing CiscoWorks integration . . . . . . . . . AIX, Solaris, and Windows systems: Installing mid-level managers . . . . . . . . . . . Installing IBM Tivoli Monitoring: Tivoli NetView Server Agent . . . . . . . . . . . . . After installing or upgrading the Tivoli NetView program . . . . . . . . . . . . . . . Backing up the Tivoli NetView databases . . . Initializing the Tivoli NetView runtime environment . . . . . . . . . . . . . Synchronizing topology changes on a backup Tivoli NetView server . . . . . . . . . . Configuring client/server access . . . . . . After installing or upgrading the language packs . . Enabling language support . . . . . . . . Customizing security files after an upgrade. . . Linux systems: Specifying a language pack input method . . . . . . . . . . . . . . . Configuring a Web browser to run the Web console as an applet . . . . . . . . . . Resolving font quality problems when using the Web console . . . . . . . . . . . . . Linux systems: Setting text encoding for the Simplified Chinese locale when forwarding events to the Tivoli Enterprise Console server . . Configuring the Tivoli NetView program . . . . 20 21 21 23 25 25 30 32 34 35 35 35 36 36 36 38 39 40 40 41 41 41
Chapter 1. Planning for installation . . . 1

Tivoli NetView components . . . . . . . . Planning for deployment . . . . . . . . . Determining where to install the Tivoli NetView server. . . . . . . . . . . . . . . Determining whether to use and synchronize backup servers. . . . . . . . . . . . Deciding whether and where to install the Web console . . . . . . . . . . . . . . AIX and Solaris environments: Determining whether and where to install clients . . . . Determining which data collector application to use . . . . . . . . . . . . . . . AIX system: Planning to install the trapgend subagent . . . . . . . . . . . . . . AIX and Solaris environments: Determining whether to install mid-level managers . . . . Determining whether to integrate with the Tivoli Management Framework . . . . . . . . Planning to install the language packs . . . . Product requirements . . . . . . . . . . Hardware requirements . . . . . . . . . Software requirements . . . . . . . . . . 1 . 2 . 2 . 3 . 4 . 4 . 5 . 5 . 6 . . . . . 6 6 7 7 9
Chapter 2. Installing or upgrading the Tivoli NetView program . . . . . . . 17

Before you begin . . . . . . . . . . . Ensuring that Tivoli NetView messages display correctly . . . . . . . . . . . . . Determining if your system meets the product requirements . . . . . . . . . . . . Configuring Linux systems for topology discovery . . . . . . . . . . . . . Removing registration information for vendor-acquired software . . . . . . . . Upgrading from version 7.1.4 on a Red Hat Enterprise Linux 3 system . . . . . . . Renaming or deleting backup files from earlier versions . . . . . . . . . . . . . Cleaning up old traps . . . . . . . . . AIX and Solaris systems: Migrating IP topology data in an RDBMS from version 7.1.4 to 7.1.5 .
Copyright IBM Corp. 2006
42 42
. 17 . 18 . 18 . 18 . 19 . 19 . 19 . 20 . 20
Chapter 3. Starting and stopping the Tivoli NetView program . . . . . . . 45

Before starting the Tivoli NetView program. . . Checking the daemon status . . . . . . . Registering and unregistering the daemons for optional functions . . . . . . . . . . Starting the Tivoli NetView program . . . . . Using the netview shell script . . . . . . Using the Tivoli desktop . . . . . . . . Recycling the daemons . . . . . . . . Logging output . . . . . . . . . . . Accessing the online help . . . . . . . . Stopping the Tivoli NetView program . . . . Starting the Server Setup application . . . . . Starting the Client Setup application . . . . . . 45 . 45 . . . . . . . . . . 45 47 47 48 48 48 49 49 49 50
iii
Starting and stopping the daemons . Using the command line . . . . Using the Server Setup application
. . .
. . .
. . .
. . .
. 50 . 50 . 52
Appendix C. Files that are migrated during an upgrade installation . . . . 71 Appendix D. AIX system and Solaris environment: Tuning the NDBM Databases . . . . . . . . . . . . . 75
NDBM component overview . . . . . NDBM utilities . . . . . . . . . . The dbmcompress utility . . . . . . The dbmlist utility . . . . . . . . The nvTurboDatabase utility . . . . . Implementing database improvements . . Improving the performance of the NDBM databases . . . . . . . . . . . Migration options . . . . . . . . Possible migration strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 76 76 76 77 77
Chapter 4. Uninstalling the Tivoli NetView program . . . . . . . . . . 53

Uninstalling a client . . . . . . Uninstalling a server . . . . . . Uninstalling the Web console . . . AIX system: Uninstalling the trapgend Uninstalling the Mid-Level Manager . . . . . . . . . . daemon . . . . . . . . . . . . . 53 53 54 54 54
Chapter 5. Troubleshooting common installation problems . . . . . . . . 55

Solaris 10 systems: Error message when configuring the DB2 database . . . . . . . . . . . . Solaris and Linux systems: Too many open semaphores . . . . . . . . . . . . . . Community name changes . . . . . . . . . Cannot communicate with local SNMP agent . . . Error messages in the tdwdaemon.log file . . . . The netviewd daemon does not start . . . . . . For non-English language systems: If Tivoli NetView applications or Web consoles display in the English language . . . . . . . . . . . . . . . 55 55 55 55 56 56
. 77 . 78 . 78
Appendix E. Support information . . . 81

Obtaining fixes . . . . . . . . . . . . . 81 Contacting IBM Software Support . . . . . . . 81 Determine the business impact of your problem 82 Describe your problem and gather background information . . . . . . . . . . . . . 82 Submit your problem to IBM Software Support 83
57
Appendix A. Hardware, memory, and tuning recommendations . . . . . . . 61

Determining the size of your network . . . Hardware and tuning recommendations . . . Recommendations for a small network . . Recommendations for a medium network . Recommendations for a large network . . Recommendations for a very large network . . . . . . . . . . . . 61 63 63 64 65 67
Notices . . . . . . . . . . . . . . 85
Trademarks . . . . . . . . . . . . . . 86
Additional copyright and license information . . . . . . . . . . . . . 89 Index . . . . . . . . . . . . . . . 91
Appendix B. Installation entries . . . . 69
iv
Installation Guide
About this guide

The IBM Tivoli NetView program is a network management program that discovers TCP/IP networks, displays network topologies, correlates and manages events and SNMP traps, monitors network health, and gathers performance data. The IBM Tivoli NetView for UNIX and Linux Installation Guide describes how to install, upgrade, and uninstall the Tivoli NetView program. When referring to the host connection, this book assumes you are connecting to Tivoli NetView for z/OS.
Who should read this guide

This guide is for administrators and network operators who are responsible for installing the Tivoli NetView program. Readers should be familiar with the following topics: v Network management v The operating systems that your enterprise uses v Optionally, Tivoli Management Framework
Publications
This section lists publications in the IBM Tivoli NetView library and related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications.
IBM Tivoli NetView for UNIX and Linux library

v IBM Tivoli Monitoring: Tivoli NetView Server Agent User's Guide, GC32-1859 Provides information about installing, configuring, and using the Monitoring Agent for Tivoli NetView Server. v IBM Tivoli NetView for UNIX and Linux Administrators Guide, SC32-1837 Provides information about how to manage and monitor a multiprotocol network with the Tivoli NetView program. v IBM Tivoli NetView for UNIX and Linux Administrators Reference, SC32-1838 v Provides information about the Tivoli NetView daemons, commands, and files. IBM Tivoli NetView for UNIX Database Guide, SC32-1839 Provides information about how to configure the Tivoli NetView program to work with a relational database management system. IBM Tivoli NetView for UNIX and Linux Diagnosis Guide, SC32-1840 Provides information about how to diagnose problems that can occur with the Tivoli NetView program. IBM Tivoli NetView for UNIX and Linux Installation Guide, GC32-1842 Provides information about how to install, upgrade, and uninstall the Tivoli NetView program. IBM Tivoli NetView for UNIX and Linux Programmers Guide, SC32-1844
Provides information about how to write application programs to run with the Tivoli NetView program. v IBM Tivoli NetView for UNIX and Linux Programmers Reference, SC32-1845 Provides information about the Tivoli NetView APIs. v IBM Tivoli NetView for UNIX and Linux Release Notes, GI11-4108 Provides release-specific information that is not available until just before the product is sent to market. v IBM Tivoli NetView for UNIX and Linux Users Guide for Beginners, SC32-1847 Provides introductory information and step-by-step tasks that help a new user understand how to use the Tivoli NetView program to manage networks. v IBM Tivoli NetView Mid-Level Manager Users Guide, SC32-1843 Provides information about installing, configuring, and how to distribute network monitoring and management to mid-level managers. v IBM Tivoli NetView Quick Start Guide Provides the information you need to get up and running with a base configuration of the Tivoli NetView program. v IBM Tivoli NetView Web Console Users Guide, SC32-1848 Provides information about using the Web console to manage a network. v IBM Tivoli NetView Warehouse Enablement Pack: Implementation Guide, SC32-1237 Describes how to install and configure the warehouse enablement pack for the Tivoli NetView product and describes the data flow and structures that are used by the warehouse pack.
Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at the following Tivoli software library Web site: http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology Web site at the following Web address: http://www.ibm.com/ibm/terminology
Accessing publications online

The Quick Start CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. Refer to the readme file on the CD for instructions on how to access the documentation. IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: http://www.ibm.com/software/tivoli/library/ Click Tivoli product manuals. In the Tivoli Technical Product Documents Alphabetical Listing window, click IBM Tivoli NetView to access the product library at the Tivoli software information center.
vi
Installation Guide
Note: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your local paper.
Ordering publications
You can order many Tivoli publications online at the following Web site: http://www.elink.ibmlink.ibm.com/public/applications/publications/ cgibin/pbi.cgi You can also order by telephone by calling one of these numbers: v In the United States: 800-879-2755 v In Canada: 800-426-4968 In other countries, contact your software account representative to order Tivoli publications. To locate the telephone number of your local representative, perform the following steps: 1. Go to http://www.elink.ibmlink.ibm.com/public/applications/publications/ cgibin/pbi.cgi. 2. Select your country from the list and click Go. 3. Click About this site in the main panel to see an information page that includes the telephone number of your local representative.
Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: http://www.ibm.com/software/tivoli/education
Support Information
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: v Searching knowledge bases. You can search across a large collection of known problems and workarounds, Technotes, and other information. v Obtaining fixes: You can locate the fixes that are already available for your product. v Containing IBM Software Support: If you still cannot resolve your problem, and you need to work with someone from IBM, you can use a variety of ways to contact IBM Software Support. For more information about these three ways of resolving problems, see Appendix E, Support information, on page 81.
Participating in newsgroups
User groups provide software professionals with a forum for communicating ideas, technical expertise, and experiences related to the product. They are located on the Internet and are available using standard news reader programs. These groups are primarily intended for user-to-user communication and are not a replacement for formal support.
About this guide
vii
To subscribe to the Tivoli NetView forum, send an e-mail to majordomo@lists.us.ibm.com and include the following line in the body of the note:
subscribe nv-l
To access a newsgroup, use the instructions appropriate for your browser. IBM Tivoli Enterprise Console news://news.software.ibm.com/ibm.software.tivoli.enterprise-console Tivoli Data Warehouse news://news.software.ibm.com/ibm.software.tivoli.enterprise-data-warehouse
Conventions used in this guide

This guide uses several conventions for special terms and actions, operating system-dependent commands and paths, and margin graphics.
Typeface conventions
This guide uses the following typeface conventions: Bold v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text Italic v v v v Words defined in text Emphasis of words (words as words) New terms in text (except in a definition list) Variables and values you must provide
Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options
viii
Installation Guide
Chapter 1. Planning for installation

This chapter describes the Tivoli NetView components, and it describes how to plan for installing the Tivoli NetView program. Before installing the Tivoli NetView program, read the information in the following sections: v Tivoli NetView components v Planning for deployment on page 2 v Product requirements on page 7
Tivoli NetView components

The Tivoli NetView program is a network management program that uses SNMP to discover, monitor and configure TCP/IP networks. It is comprised of required and optional software components. The following software component is required: Tivoli NetView server The required code for Tivoli NetView server operation. The following software components are optional: Tivoli NetView Client (AIX and Solaris environments only) The code for the Tivoli NetView client. This component cannot be installed on a system where the Tivoli NetView server is installed. Tivoli NetView native console An X/Motif-based GUI, which administrators can use to configure the Tivoli NetView server. It provides administrator and operator functionality. This component is installed automatically when the Tivoli NetView server is installed. Tivoli NetView Web console A Java-based graphical user interface (GUI), which operators can use to view the network topology. It provides most operator functionality, and it provides diagnostic and informational tools to aid in troubleshooting network problems. Tivoli NetView Database (AIX and Solaris environments only) Provides relational database support through the use of the Tivoli Management Framework RIM feature. If you have the Tivoli Management Framework product and a relational database installed, you can install the database component if you want to store IP topology, trapd log, and snmpCollect data in your relational database. For information about the relational databases that are supported, refer to the Tivoli Management Framework Reference. For information about configuring the Tivoli NetView program to use a relational database, refer to the IBM Tivoli NetView for UNIX Database Guide. Tivoli NetView Mid-Level Manager (AIX, Solaris, and Windows environments only) Acts as an intermediate Simple Network Management Protocol (SNMP) manager, reducing the amount of network traffic and the amount of processing that must be done by the central network manager. For more
information about using the mid-level manager software, refer to the IBM Tivoli NetView Mid-Level Manager Users Guide. Tivoli NetView Language Packs Provides support for the following languages: v AIX system: Korean EUC Japanese EUC Japanese SJIS Simpified Chinese EUC v Linux system and Solaris environment: Korean EUC Japanese EUC Simplified Chinese EUC Note: You are entitled to use an unlimited number of Tivoli NetView clients and Tivoli NetView mid-level managers with each copy of the Tivoli NetView server that you have purchased.
Planning for deployment

When planning for deployment of the Tivoli NetView program, you need to decide how you want to manage your network. The information in this section can help you make the following decisions: v Determining where to install the Tivoli NetView server v Determining whether to use and synchronize backup servers on page 3 v Deciding whether and where to install the Web console on page 4 v AIX and Solaris environments: Determining whether and where to install clients on page 4 v Determining which data collector application to use on page 5 v AIX system: Planning to install the trapgend subagent on page 5 v AIX and Solaris environments: Determining whether to install mid-level managers on page 6 v Determining whether to integrate with the Tivoli Management Framework on page 6
Determining where to install the Tivoli NetView server

Tivoli NetView servers must run on a system with a fixed TCP/IP address, not one that uses DHCP. When you select a system on which to install the Tivoli NetView server, you should also consider a number of capacity and workload issues, such as: v Size of the managed network v Number (and types) of Tivoli NetView operators v Polling intervals for status monitoring and SNMP collections v Speed of the network connections between the Tivoli NetView program and the managed resources v Whether to use Tivoli NetView mid-level managers v Whether to use Tivoli NetView client systems or Web consoles
Installation Guide
For small networks, you can use a current model pSeries, xSeries, or Sun Solaris system as Tivoli NetView servers. A small IP network is defined here as a network that includes the following: v 5000 objects or 2000 interfaces v One local operator v Network response times of 4 to 10 microseconds for an ICMP ping v Default polling intervals As a network grows in size, the number of operators increases and other major applications are added to the system. Memory and processor capacity needs also increase substantially. For larger networks, systems with multiple processors are strongly recommended and, in some cases, multiple systems must be used to distribute the management workloads. For more information about hardware recommendations, refer to Appendix A, Hardware, memory, and tuning recommendations, on page 61.
Determining whether to use and synchronize backup servers

Depending on your license agreement, you can install and run the Tivoli NetView server on multiple computers. If you decide that you require a backup or secondary server to provide failover services in the event the primary Tivoli NetView server experiences a problem, you can deploy one or more secondary Tivoli NetView servers as part of your overall failover strategy. The secondary servers can automatically receive information from the primary server about the topology changes occurring in your network. This topology synchronization requires that you make minor configuration changes to both the primary and secondary Tivoli NetView servers after installation. The advantages of configuring topology synchronization across servers are as follows: v It can be part of your overall strategy for hot standby deployment and failure readiness. v It can help to reduce the cost of provisioning and maintaining the synchronization of the topology database used by the secondary server. Without automatic synchronization of network changes, network administrators must add topology changes to the secondary server by using a seed file, local hosts, by manually adding them to the network map, or by allowing the secondary server to perform automatic discovery of new devices. This can be time consuming as nodes or interfaces to host systems are added or deleted in your network. v You can reduce the amount of polling done on secondary servers by limiting it to status polling only. Topology changes are propagated automatically to the topology database on the secondary server. For more information about configuring the servers to perform this synchronization, see Synchronizing topology changes on a backup Tivoli NetView server on page 36. Besides considering a plan to deploy one or more Tivoli NetView backup servers, you should also consider a plan for performing periodic (for example, weekly) backups of the Tivoli NetView databases from the primary server to the secondary server because events are not guaranteed to be delivered under all circumstances (for instance, the trapd daemon could experience a problem and traps might not be
delivered). For information about backing up the Tivoli NetView databases using the hot backup function, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide.
Deciding whether and where to install the Web console

You can deploy the Web console on any supported UNIX, Linux, or Windows operating system to connect to a Tivoli NetView server on any supported platform. For example, a Web console on a Windows system can be connected to a Tivoli NetView server on an AIX system. To run the Web console without requiring a user to log into the native console on the Tivoli NetView server, you can run the Tivoli NetView program as the netviewd daemon. For more information about the netviewd daemon, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide.
AIX and Solaris environments: Determining whether and where to install clients
The Tivoli NetView client is typically deployed as the number of operators or the size of the managed network increases. The reason for deploying the Tivoli NetView client is to remove the memory and processor capacity requirements for supporting operators from the Tivoli NetView server and to distribute the requirements to another system. When you install a client, you must complete the following procedures: v Configure the server to give the client access. v Configure the client to access the server. v For the AIX system, optionally, install the trapgend subagent from the server. When you are selecting hardware for the Tivoli NetView client, questions about processor capacity are limited to memory needs and the number of operators. To install the Tivoli NetView client in a small network, entry-level workstations from a variety of vendors are acceptable. As the number of operators increases, the memory and processor capacity needs to increase substantially. For a larger number of operators (10 or more who are active simultaneously), systems with multiple processors are strongly recommended. A single system with adequate memory and processor capacity might be used to support multiple operators. Another alternative is to use multiple entry-level systems as a combination Tivoli NetView client and operator workstation. Notes: 1. You cannot install the Tivoli NetView server and the client on the same system. 2. Client and server systems must reside on the same operating system. For example, you cannot configure a Tivoli NetView client on a Solaris system to use a Tivoli NetView server on an AIX system. To determine where your maps reside, consider the following advantages and disadvantages: v If you want all your maps to reside on the server machine, you can mount your map database using the network file system (NFS). In this case, making changes to all the maps is easier because they are all in one physical place. Everyone can use the same set of maps. However, if the map database is on the server, you are not offloading that memory utilization onto the clients. v If you want each client to have a set of maps, you can keep your maps locally on the clients. In this case, the memory utilization is distributed onto the client
Installation Guide
machines. However, making changes to all the maps is complex because all the maps physically reside on different computers. Users also cannot share the same maps.
Determining which data collector application to use

To collect data for historical analysis, you can use the SNMPv1 MIB Collector (snmpCollect), or you can use the SNMPv1/v2 SNMP Collector (nvcollectord). The SNMPv1/v2 SNMP Collector (nvcollectord) provides SNMPv2 and Counter64 support and uses the IBM DB2 product. The SNMPv1 MIB Collector (snmpCollect) can forward data to Tivoli Data Warehouse. Use the SNMPv1 MIB Collector (snmpCollect) for the following reasons: v You want to continue forwarding data to Tivoli Data Warehouse. v You do not require SNMPv2 and Counter64 support. v You do not want to install the DB2 product. If you are not forwarding data to Tivoli Data Warehouse, then you do not need the DB2 product to use the SNMPv1 MIB Collector. Use the SNMPv1/v2 SNMP Collector (nvcollectord) if you require SNMPv2 and Counter64 support. When you install the Tivoli NetView program, you can configure it to use either the SNMPv1 MIB Collector (snmpCollect) or the SNMPv1/v2 SNMP Collector (nvcollectord). You cannot use both types of SNMP data collectors at the same time. Using both at the same time is not supported by the Tivoli NetView program. You can also change the data collector application you want to use at any time after the installation. For information about how to change the data collector application, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide.
AIX system: Planning to install the trapgend subagent

Whether you decide to install clients or not, you can install the trapgend subagent on all your remote AIX nodes. The trapgend subagent enables remote AIX nodes to collect additional data and send the data in a more efficient manner to the system where the Tivoli NetView server is installed (where the trapd daemon resides). Install the latest level of the trapgend daemon on all remote AIX nodes to provide additional management capabilities as follows: v Enabling remote ping v Enabling processor use and disk space monitoring v Converting AIX alertable errors to SNMP traps The trapgend daemon converts alertable errors generated by a remote AIX node to SNMP traps and sends them to the Tivoli NetView management system. The traps can be found in two places. On the agent, the trap can be found in system error log (errpt -c). On the management system, the trap can be found in the trapd.log. Note: To include failing hardware information in the alerts, you must install the Product Topology Data diskette on the remote AIX node. This diskette contains vital product data for your system unit. For information about installing the Product Topology Data diskette, refer to the documentation shipped with your system unit.
For more information about the trapgend daemon, refer to the man page and to the IBM Tivoli NetView for UNIX and Linux Administrators Guide.
AIX and Solaris environments: Determining whether to install mid-level managers

To determine whether to install mid-level managers, consider the following system and network management benefits that mid-level managers can provide: v Close monitoring of MIB characteristics on a critical node. When an SNMP agent is installed on a node, you can obtain system information about that node and monitor the information from a mid-level manager workstation. v Management of remote nodes and LAN segments. You can place mid-level managers in strategic locations throughout a network and move some of the monitoring tasks from the top-level manager to the mid-level managers. A mid-level manager can poll the managed nodes in its segment and, using its filtering and thresholding capabilities, control the amount of information that is forwarded to the top-level manager in the form of traps. v Offloading of new node detection and status-checking tasks from the top-level network manager. Mid-level managers in the network can take over discovery and status monitoring for their subnets, reducing network traffic and more efficiently discovering changes in the network. For more information about using a mid-level manager, refer to the IBM Tivoli NetView Mid-Level Manager Users Guide.
Determining whether to integrate with the Tivoli Management Framework

If you have the Tivoli Management Framework product installed, you can integrate the Tivoli NetView program with the Tivoli Management Framework when you install the Tivoli NetView program. Doing so adds the Tivoli NetView configuration menus to the Tivoli desktop. The Tivoli Management Framework software is also required to use the Tivoli NetView Database component, which provides relational database support. This is because relational database support requires RIM support.
Planning to install the language packs

Tivoli NetView language packs
The Tivoli NetView program provides language packs for the following languages: v AIX system: Korean EUC Japanese EUC Japanese SJIS Simpified Chinese EUC v Linux and Solaris environments: Korean EUC Japanese EUC Simplified Chinese EUC
Language pack requirements

The following hardware and software is required for installing a Tivoli NetView language pack.
Installation Guide
v Tivoli NetView for UNIX and Linux, version 7.1.5, English language product You can install a language pack at the same time that you install the English language product, or you can install the language pack separately after you install the English language product. v 30 MB additional disk space in the /usr/OV file system for each language pack. v Client and server systems must be set to the same code set and must reside on the same operating system. v The Web console and the Tivoli NetView server must be set to the same code set. v To display Tivoli NetView applications on a remote X server, the system on which the application is being displayed must also have the appropriate locale installed and set. Otherwise, unreadable characters are displayed in the maps and menus. Remote X display is only supported between machines running the same platform. Using a remote X display between different platforms might result in font compatibility issues. v For the Linux system: All Linux operating systems require KDE Version 3 v For Korean: The baekmuk-ttf font package to run the Web console on SUSE Linux Enterprise Server 9.
Product requirements
This section lists the hardware and software requirements for the Tivoli NetView program.
Hardware requirements
This section lists the hardware requirements for the Tivoli NetView program.
Platform requirements
The following hardware requirements apply to all platforms on which the Tivoli NetView program is installed. v A minimum of 1 GB of paging space. To determine how much paging space is available, enter one of the following commands: AIX system:
lsps -s
Linux system:
cat /proc/swaps
Note that paging space is reported in KB. Solaris environment:

swap -s
v A minimum of 512 MB of system memory; 1 GB is recommended. v Adequate disk space in the /usr/OV directory as described in Table 1.
Table 1. Disk space requirements in the /usr/OV directory Component Server Client (AIX and Solaris environments only) Fresh installation 800 MB 250 MB Upgrade installation 800 MB 75 MB
Table 1. Disk space requirements in the /usr/OV directory (continued) Component Fresh installation Upgrade installation 500 MB
Relational database (AIX 500 MB and Solaris environments only) Notes:
1. Do not install the Tivoli NetView program in an NFS-mounted /usr/OV file system because the results are unpredictable. 2. Every 200 nodes requires 1 MB of disk space. This requirement assumes that you have one read-write map. Each additional read-write map requires 1 MB of disk space. 3. Your system might require additional disk space depending on the network size and management load. For a medium-sized network, consider adding up to 512 MB of additional space in the partition that contains the /usr/OV directory.
For more information about disk space requirements, refer to Appendix A, Hardware, memory, and tuning recommendations, on page 61. v If you are upgrading from a previous version of the Tivoli NetView program, you need adequate disk space in the /usr file system because the Tivoli NetView directories are backed up in this file system. To determine the amount of disk space that is required, stop the native console and run the following command:
/usr/OV/install/tools/nvp.v7r1 test -p /usr/OV/ALL
v Additional disk space for installation in a Tivoli environment as follows:

Table 2. Additional disk space requirements for installation in a Tivoli environment File system /var /tmp $BINDIR /etc/lpp /etc
1 1
Minimum disk space requirement 8 MB 5 MB 100 MB 4 MB 1 MB
The $BINDIR file system refers to the disk where the Tivoli Management Framework product is installed. A minimum of 512 MB of paging space is also required.
v The X Window/Motif system must be configured with the options described in Table 3:
Table 3. Color display requirements Features Minimum number of colors Depth Bits in color Dimensions Resolution Video memory on adapter Requirement 256 8 planes 24 bits 1280 x 1024 pixels 91 x 92 dots per inch 1 MB minimum
Using less color can result in run time problems, such as fatal X errors. This problem is more prevalent on Linux systems.
v A network adapter (a PCI adapter is strongly recommended for best performance)
Installation Guide
v A mouse
Web console hardware requirements

The following hardware requirements apply to systems on which a Web console is installed.
Hardware Processor Memory Hard disk space Minimum 450 MHz 256 MB RAM Recommended 1 GHz 512 MB RAM
10 170 MB depending on 10 170 MB the Web console package that you install. For more information about the Web console packages, see Table 6 on page 27.
Software requirements
This section lists the software required for the Tivoli NetView program.
Operating system support

The Tivoli NetView program supports the following operating environments:
Platform1 AIX Required level v AIX 5.2 with the X11.compat package (X11R5) and Maintenance Level 03 v AIX 5.2H with the X11.compat package (X11R5) v AIX 5.3 with the X11.compat package (X11R5), 32 and 64-bit kernel Additional requirements For AIX 5.2 and 5.3, the SNMP V1 version of the snmp daemon is required. On AIX 5.2 and 5.3, the default SNMP agent is SNMP V3. Use the following procedure to determine which version of the snmp daemon is running and to change to the snmpdv1 or snmpd64v1 (64-bit kernel) version if necessary. 1. Run the following command to determine the version of the snmp daemon that you are running: ps -eo comm | grep snmpd 2. If the result is snmpdv1 or snmpd64v1, no further action is necessary. If the result is snmpdv3ne, run the following command to change the symbolic links and to run the SNMP V1 version. /usr/sbin/snmpv3_ssw -1
Sun Solaris
v Sun Solaris 9 with all Sun-required patches v Sun Solaris 10 with all Sun-required patches (an image dated 01/06 or later is required)
The SUNWbtool must be installed. Solaris 10 Local Zones are not supported.
Platform1 Linux Intel

2
Required level v Red Flag 5 v Red Hat Enterprise Linux 4.0, 32 or 64-bit kernel v SUSE Linux Enterprise Server 9, 32 or 64-bit kernel
Additional requirements The following packages and software must be installed: v binutils v inetd or xinetd v ucd-snmpd, ucdsnmp, or net-snmp v Xvfb (Red Hat rpm is xorg-x11-Xfb and SLES 9 rpm is XFree-86-Xvfb)3 v The latest pdk shell v KDE Version 3 is required for Language Kit support. Additional requirements for zSeries operating systems: v For zSeries SLES 9: glibc-2.3.3-98.47 glibc-32bit-9-200506070135 glibc-devel-2.3.3-98.47 glibc-devel-32bit-9-200506070135 glibc-i18ndata-2.3.3-98.47 glibc-info-2.3.3-98.47 glibc-locale-2.3.3-98.47 glibc-locale-32bit-9-200506070135 v The Konqueror product v If the Tivoli Management Framework 4.1 product is installed, Patch 14 is required for endpoint adapters on zSeries operating systems. The patch must be applied to the systems on which the Tivoli Enterprise Console server and the Tivoli NetView server are installed.
Linux for zSeries2
v Red Hat Enterprise Linux 4.0, 31-bit kernel only v SUSE Linux Enterprise Server 9, 31-bit kernel only
The Tivoli NetView program is a 32-bit application. It has been certified on the 64-bit operating systems listed in this table.
2
The following functions are not included in the Linux platform release of the Tivoli NetView program:
v Cisco Adapter v Native Client Support (the Web console replaces the native client mechanism) v X/Open Management Protocols (XMP) API support for Common Management Information Protocol (CMIP) and CMIP over TCP/IP (CMOT) applications v RDBMS Interface Module (RIM) Database Support (there is no support for Tivoli management region RIM) v Backup Manager v Mid-Level Manager v Agent Policy Manager (APM) Testing was performed on the IA32, AMD64, and EM64T architectures. The Itanium architecture (IA64) is not supported.
3
rpm is the Red Hat Package Manager. For more information about rpm, see the man pages.
Online help and Web Console requirements

To use the online help from the native console or to use the applet version of the Web console, one of the following browsers is required:
Platform AIX Linux Intel
Operating system versions 5.2 and 5.3 v Red Flag 5 v Red Hat Enterprise Linux 4.0 v SUSE Linux Enterprise Server 9
Supported Web browsers Mozilla 1.7.12 or higher Firefox 1.5.0.1 or higher
10
Installation Guide
Platform Linux Intel Linux Intel Sun Solaris Windows
Operating system versions Red Hat Enterprise Linux 4.0 SUSE Linux Enterprise Server 9 9 and 10 Windows 2003 and XP Professional
Supported Web browsers Konqueror 3.3.1.5.8 (using KDE 3.3.1-3.11) or higher Konqueror 3.2.1 (using KDE 3.2.1) or higher Mozilla 1.7.12 or higher v Internet Explorer 6.0 with the latest service pack and security patches v Firefox 1.5.0.1 or higher
To run the Web console as an applet with the Konqueror Web browser, you must set up the Java plug-in. To do this, follow these steps: 1. From the menu bar of the Konqueror Web browser, select Settings Configure Konqueror. 2. Go to the Java&JavaScript page. 3. In the Path to Java Executable field, type the path where the Java Runtime Environment version 1.4.2 is installed. If you have the Tivoli NetView server installed, the path is similar to /usr/OV/jre/bin/java. If you have another JRE installed, the path is similar to /usr/local/lib/j2sdk1.4.2/jre/bin/java. 4. Ensure that the following options are selected: v Enable Java globally v Show Java console 5. Close all active Konqueror windows.
For UNIX and Linux systems: To use the online help from the native console, you must set the MOZILLA_HOME environment variable to the path that contains the executable file for your Web browser. The applet version of the Web console requires a Java plug-in that is provided with the Java Runtime Environment version 1.4.2. When the applet version of the Web console is started in a browser, the applet causes the browser to go to the appropriate Web site for the Java plug-in if it is not installed. To download the Java plug-in, go to the appropriate Web site for your operating system as follows:
Operating system AIX Linux, Solaris, and Windows Web site http://www.ibm.com/developerworks/java/jdk/aix/service.html http://java.sun.com/j2se/1.4.2/download.html
AIX and Solaris environments: Tivoli NetView Database component requirement

Installation of the Tivoli NetView Database component, which provides relational database support, requires Tivoli Management Framework version 4.1 or higher with all the latest patches for RIM support. For information about the relational databases that are supported, refer to the Tivoli Management Framework Reference. For information about configuring the Tivoli NetView program to use a relational database, refer to the IBM Tivoli NetView for UNIX Database Guide.
11
Requirement for data collection

IBM DB2 Universal Database Version 8.2.1 with the latest DB2 fix pack must be installed for either of the following situations: v You plan to use the SNMPv1 MIB Collector (snmpCollect) and you want to export the data to Tivoli Data Warehouse v You plan to use the SNMPv1/v2 SNMP Collector (nvcollectord) For information about determining which data collector application to use, see Determining which data collector application to use on page 5. To install the DB2 product, use the appropriate DB2 UDB ESE V8.2.1 for Tivoli NetView V7.1.5 CD, which is provided with the Tivoli NetView package. The latest DB2 fix pack can be obtained from the following DB2 support Web site: http://www.ibm.com/software/data/db2/udb/support/downloadv8.html The Tivoli NetView product was tested with DB2 version 8.2.5 (version 8.2 with fix pack 12). Important DB2 installation information for Linux systems: Before installing the DB2 product, update your Linux kernel parameters. This avoids the problem of the DB2 product using all semaphores and causing the Tivoli NetView installation to fail or to fail to restart the daemons due to a lack of system resources. You must have root authority to modify the kernel parameters. To modify the kernel parameters, follow these steps: 1. Add the following entries to the default system control file, /etc/sysctl.conf:
kernel.msgmni = 1024 kernel.sem = 250 256000 32 1024
where:
max semaphores system wide = max number of arrays x max semaphores/array
2. Run the following command to load the sysctl settings from the /etc/sysctl.conf file:
sysctl -p
The entries in the sysctl.conf file are ready during startup by the network initialization script. Note that on some distributions, you might be required to add the sysctl -p command to one of the system initialization files, such as the rc.local file, so that the kernel parameters are set after each reboot. The IBM DB2 Universal Database Version 8.2.1 product is packaged with the IBM Tivoli NetView product for limited use with the Tivoli NetView product. The following license information applies to the use of the DB2 software that is packaged with the Tivoli NetView product: DB2 Universal Database Components: The Tivoli NetView program includes portions of the IBM DB2 Universal Database product. You are authorized to install and use one copy of these components only in association with your licensed use of the Tivoli NetView program for the storage and management of data used and generated by the Tivoli NetView program, and not for other data management purposes. DB2 Universal Database components are to be used only by the Tivoli NetView program. For example, DB2 Universal Database components can be used as a repository for configuration information generated by the Tivoli NetView
12
Installation Guide
program and cannot be used to build or extend custom applications that store business data; this license does not permit inbound connections to the database from other applications for queries or report generation. You are authorized to install and use the DB2 Universal Database components only with and on the same workstation as the Tivoli NetView program. Your use of the DB2 Universal Database components is subject to the terms and conditions of the license agreement which accompany the components except as limited by this license. The DB2 components may not be used for any other purpose. Please contact your DB2 Reseller if your needs exceed this license agreement to obtain a full DB2 Universal Database program.
Tivoli NetView upgrade requirements

To upgrade to the Tivoli NetView version 7.1.5 product, you must have version 7.1.4 installed.
Requirements for integrating with the Tivoli Management Framework

To integrate the Tivoli NetView program with the Tivoli Management Framework, Tivoli Management Framework Version 4.1 or higher with all the latest patches is required.
TCP/IP connection requirements

As a network manager, the Tivoli NetView program depends on access to the network, even during installation. To ensure that the TCP/IP communication between the system to be installed and the rest of the network is working correctly, follow these steps: 1. Run each of the following system commands if your system is configured to use a domain name server (DNS). If your system does not use DNS, the host names should be resolved in the /etc/hosts file. v To check communication on the system, enter the following command:
ping 127.0.0.1
v To check the connection to the name server, enter the following command:
nslookup 127.0.0.1
v To check name resolution, enter the following command:

nslookup local_ip_address
v To check host name resolution, enter the following command:

hostname
v To check communication to the system, enter the following command:

ping local_system_name
v To check connectivity to another system, enter the following command:

ping another_system_name
v To ensure that the SNMP agent is running, enter the following command:
ps -ef | grep snmpd
2. Ensure that all ports required by the Tivoli NetView program as described in Table 4 on page 14 are not already in use. If necessary, close any programs that are using these ports. To check the status of the ports, enter the following command:
netstat -a
13
Table 4. Required ports Port/Protocol 162/tcp 162/udp 163/tcp 163/tcp 164/udp 164/udp 1661/tcp 1663/tcp 1664/tcp 1666/tcp 1667/tcp 1668/tcp 1669/tcp 1670/tcp 1670/udp 1671/tcp 1672/tcp 1673/tcp 1674/tcp 1675/tcp 2112/tcp 2113/tcp 3113/tcp 8888/tcp 9999/tcp 18892/tcp 18893/tcp Service name nvtrapd-trap nvtrapd-trap cmot_manager cmot_manager cmot_agent cmot_agent nvtrapd-client nvsecd nvcold nvcorrd nvsecltd C5_server nvlockd actionsvr mgragentd nvpagerd otmd snmpserver tdwdaemon tdwnetmon gtmd pmd xxmd ovtopmd ovwdb nvcollectord nvpollerd Purpose Tivoli NetView trapd monitor trap port Tivoli NetView trapd monitor trap port Tivoli NetView CMOT Manager port Tivoli NetView CMOT Manager port Tivoli NetView CMOT Agent port Tivoli NetView CMOT Agent port Tivoli NetView trapd client application port Tivoli NetView security daemon port Tivoli NetView SmartSet facility port Tivoli NetView correlation daemon port Tivoli NetView security client daemon Tivoli NetView C5 consolidated console and threshold management port Tivoli NetView General Topology Manager lock daemon Tivoli NetView correlation action daemon port Tivoli NetView mgragentd agent Tivoli NetView pager daemon Tivoli NetView open topology stream port Tivoli NetView SNMP server port Tivoli NetView and Tivoli Data Warehouse daemon socket communication Tivoli NetView and Tivoli Data Warehouse daemon netmon communication Tivoli NetView General Topology Manager port Tivoli NetView postmaster daemon port Tivoli NetView General Topology Manager child process port Tivoli NetView IP topology daemon port Tivoli NetView object database daemon port Tivoli NetView SNMP Collector communication Tivoli NetView SNMP Poller communication
IBM Support Assistant and Tivoli NetView plug-in requirements

To use the optional IBM client application known as the IBM Support Assistant to access IBM support information and to automatically collect Tivoli NetView system information for Problem Management Reports (PMRs), you must use the Tivoli
14
Installation Guide
NetView plug-in for the IBM Support Assistant. The plug-in defines the log files and output files collected by the IBM Support Assistant for diagnosing problems related to the Tivoli NetView program. The IBM Support Assistant and the Tivoli NetView plug-in are not provided on the Tivoli NetView installation media. You can download the IBM Support Assistant from either of the following IBM Web sites: http://www.ibm.com/software/support/isa (IBM Support Assistant main site)
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=isa Follow the instructions on the Web site to download IBM Support Assistant Version 3.0 or higher for your platform. To install and use the IBM Support Assistant, refer to the directions that are provided in the IBM Support Assistant Installation and Troubleshooting Guide, which is available in the downloaded package. To install the Tivoli NetView product plug-in, follow the product plug-in installation instructions that are provided on the main Web site for the IBM Support Assistant. The IBM Support Assistant documentation provides details about specific platform requirements. To ensure the Tivoli NetView plug-in will work properly, you must use it on a platform that is supported by the Tivoli NetView product.
15
16
Installation Guide
Chapter 2. Installing or upgrading the Tivoli NetView program

This chapter describes the tasks you must complete before installing or upgrading the Tivoli NetView program. It describes how to install the Tivoli NetView program for the first time (a previous version of the Tivoli NetView program is not installed and you do not want to migrate any previously saved Tivoli NetView backup directories), and it describes how to upgrade the Tivoli NetView program. You can upgrade the Tivoli NetView program to version 7.1.5 if version 7.1.4 is already installed or a Tivoli NetView migration 7.1.4 backup directory exists. For information about the files that are migrated during an upgrade installation, see Appendix C, Files that are migrated during an upgrade installation, on page 71. The installation process adds entries for the Tivoli NetView processes to the appropriate files. For a description of the installation entries, see Appendix B, Installation entries, on page 69.
Before you begin

Before you install or upgrade the Tivoli NetView program, ensure that you have root access, then complete the tasks that are appropriate for your situation as described in Table 5.
Table 5. Pre-installation tasks Task Ensuring that Tivoli NetView messages display correctly on page 18 Determining if your system meets the product requirements on page 18 Configuring Linux systems for topology discovery on page 18 Removing registration information for vendor-acquired software on page 19 Systems that require completion of this task All All Linux systems All systems when upgrading the Tivoli NetView program to a different server and vendor-acquired software is integrated with the Tivoli NetView program
Upgrading from version 7.1.4 on a Red Hat Red Hat Linux 3.0 systems when upgrading Enterprise Linux 3 system on page 19 the Tivoli NetView program Renaming or deleting backup files from earlier versions on page 19 Cleaning up old traps on page 20 AIX and Solaris systems: Migrating IP topology data in an RDBMS from version 7.1.4 to 7.1.5 on page 20 Installing the Tivoli NetView Framework patch before integrating with the Tivoli Management Framework on page 20 All systems when upgrading the Tivoli NetView program All systems when upgrading the Tivoli NetView program AIX and Solaris systems when upgrading the Tivoli NetView program and IP topology data is stored in a relational database management system (RDBMS) All systems for a new installation of the Tivoli NetView program when integrating it with the Tivoli Management Framework
17
Ensuring that Tivoli NetView messages display correctly

To ensure that Tivoli NetView messages display correctly and that the Tivoli NetView program runs correctly, you must set the LANG and the LC_MESSAGES environment variables to the English language locale of en_US, before you install the Tivoli NetView program. The default setting for the LANG and the LC_MESSAGES environment variables is C. Set these variables to en_US if these variables are set to C, set to another locale, or are not set. After the installation, to get full message function, set the LANG and the LC_MESSAGES environment variables to the LANG value that is appropriate for your language and system. To set the LANG and LC_MESSAGES variables, do one of the following: v When using a Bourne or a Korn shell, enter the following commands:
export LANG=en_US export LC_MESSAGES=en_US
v When using a C shell, enter the following commands:

setenv LANG en_US setenv LC_MESSAGES en_US
The Tivoli NetView program has algorithms for finding language-sensitive files. An attempt is made to locate the files based on the value of the LANG environment variable. However, the Tivoli NetView program defaults to operating as though the LANG environment variable is set to C if one of the following conditions exists: v The LANG environment variable is not set. v The value of the LANG variable is not a recognized locale. v A required file is not found in the path referenced by the LANG variable.
Determining if your system meets the product requirements

Before installing the Tivoli NetView program, you can run the nvPrqchk script to determine if your system meets the product requirements and is ready for installation. The nvPrqchk script is located on the Tivoli NetView CD-ROM in the TOOLS directory. To determine if your system meets the product requirements, follow these steps: 1. On the computer on which you want to install the Tivoli NetView program, mount the Tivoli NetView CD-ROM. 2. Change directories to the TOOLS directory:
cd cd_mount_point/TOOLS
Where cd_mount_point is the directory where the Tivoli NetView CD-ROM is mounted. 3. Run the nvPrqchk script:
nvPrqchk component
Where component is one of the following components: SERVER If you are installing the Tivoli NetView Server component. CLIENT If you are installing the Tivoli NetView Client component.
Configuring Linux systems for topology discovery

Before installing the Tivoli NetView program on a Linux system, you must configure the /etc/hosts file to ensure correct topology discovery. The /etc/hosts
18
Installation Guide
file must include both the fully qualified host name and the simple host name on the line that specifies the IP address of the host. An entry in the /etc/hosts file must be similar to the following example:
123.45.67.89 myhost.local.domain.com myhost
Removing registration information for vendor-acquired software

If you plan to back up the Tivoli NetView program and move it to a different server prior to upgrading to version 7.1.5 and you have integrated vendor-acquired software with the Tivoli NetView program, you must first remove registration information for vendor-acquired software. For example, to upgrade the Tivoli NetView program to a new server when you have integrated vendor-acquired software, complete the following tasks in this order: 1. Remove registration information for the vendor-acquired software by using the /usr/OV/bin/ovdelobj command and remove all registration files (ARF and SRF files) for the vendor-acquired software. 2. Back up the Tivoli NetView program. 3. Copy the /usr/OV.back.v7r1 directory to the new server. 4. Upgrade the Tivoli NetView program as described in Installing or upgrading to version 7.1.5 on page 21. 5. Install the vendor-acquired software on the new server.
Upgrading from version 7.1.4 on a Red Hat Enterprise Linux 3 system

Before upgrading the Tivoli NetView program to version 7.1.5 from version 7.1.4 on a Red Hat Enterprise Linux 3 system, you must first upgrade the Red Hat Enterprise Linux 3 system to version 4.0. To do this, follow these steps: 1. Exit any native consoles and Web consoles that are running. 2. Stop all the daemons. 3. From the command line, enter /usr/OV/bin/serversetup to start the Server Setup application. 4. Click Maintain Backup Selective Data. 5. In the Backup Selective Data dialog box, select /usr/OV/ALL in the Directories to save field to back up all categories of Tivoli NetView data. 6. Copy the /usr/OV.back.v7r1 directory to a different computer than the one on which you created the backup. 7. Install the Red Hat Enterprise Linux 4.0 operating system. 8. Put the /usr/OV.back.v7r1 directory back onto the computer on which you installed the Red Hat Enterprise Linux 4.0 operating system. 9. Upgrade the Tivoli NetView program to version 7.1.5 as described in Installing or upgrading to version 7.1.5 on page 21.
Renaming or deleting backup files from earlier versions

Before upgrading your Tivoli NetView installation, you must remove or rename any existing /usr/OV.back.v7r1 directories from earlier upgrades of any version 7.x release. If you do not rename or delete the backup directories, the upgrade installation will fail and the following message is written in the /usr/OV/install/installation.log file:
An update install was requested when both a NetView installation and a NetView backup exists. Please remove one and rerun the installation script.
19
This message is provided to prevent you from inadvertently using an old /usr/OV.back.v7r1 directory from an earlier version of the Tivoli NetView program during migration. This problem does not occur if you create a custom /usr/OV.back.v7r1 directory from your current version 7.1.4 of the Tivoli NetView program using the Server Setup application or the nvp.v7r1 backup utility prior to upgrading to version 7.1.5. Note: It is a good idea to store a TAR file of the backup directory to tape or another archive medium in case you need it at a later date.
Cleaning up old traps

To clean up traps, determine whether any lines or sections of the trapd.conf file are too long (more than 99 fields). To do this, run the chktrapd script, which is provided on the Tivoli NetView CD-ROM in the TOOLS directory. To run the script, enter the following command:
chktrapd /usr/OV/conf/C/trapd.conf
Errors found by the script are saved in the /tmp/trapd.confchk file. Correct any errors in the trapd.conf file before upgrading the Tivoli NetView program.
AIX and Solaris systems: Migrating IP topology data in an RDBMS from version 7.1.4 to 7.1.5
Because the IP topology database fields have changed in version 7.1.5, perform the following procedure to ensure a successful migration of your IP topology data that is stored in a relational database management system (RDBMS). No special steps are required to migrate snmpCollect and trapd.log data. 1. Convert the IP topology data back to flat files. 2. Upgrade the Tivoli NetView program to version 7.1.5. 3. Drop the 7.1.4 RDBMS topology tables. 4. Create the topology tables using the version 7.1.5 database schema. 5. Transfer the IP topology data from the flat files to the RDBMS.
Installing the Tivoli NetView Framework patch before integrating with the Tivoli Management Framework
If you want to integrate the Tivoli NetView program with the Tivoli Management Framework, you must first install the Tivoli NetView Framework patch on the Tivoli server and on the managed nodes where the Tivoli NetView program will reside. This patch provides the configuration menus and enables the Tivoli Management Framework software to recognize the presence of the Tivoli NetView program. Installation of the patch is required for a new installation of the Tivoli NetView program and is not required if you are upgrading from a previous version. To install the Tivoli NetView Framework patch, follow these steps: 1. From the command line, mount the Tivoli NetView Additional Options CD-ROM. 2. Start the Tivoli desktop. 3. Click Desktop Install Install Patch.
20
Installation Guide
4. Click Select Media to display the File Browser dialog box and to set the path name to the directory where the Tivoli NetView CD-ROM is mounted. The Tivoli NetView Framework Patch is located in the TMF directory. 5. Click Set Media & Close. 6. Select Tivoli NetView Framework Patch 7.1.5. 7. Select the Tivoli endpoints on which to install the patch. If necessary, move endpoints from the Clients to Install On list to the Available Clients list. 8. Click Install & Close. The Patch Install dialog box is displayed, and it lists the operations that occur during the installation. It can also contain warnings about problems that you might want to fix before installing the patch. 9. Click Continue Install. 10. Click Close. 11. Enter the following command to recycle the Tivoli server:
odadmin reexec
Installing or upgrading to version 7.1.5

To install or upgrade the Tivoli NetView program, use the instalnv script, which is located on the Tivoli NetView CD-ROM in the NetView directory. During installation, you can configure the Tivoli NetView program in the following ways: v Turn on event forwarding to the specified Tivoli Enterprise Console server. v Set the discovery mode. v Add a list of alternate community names. v Enable the tdwdaemon. v Configure a list of IBM Tivoli Monitoring servers to query for use by the servmon daemon. v Configure the data collector application you want to use, the SNMPv1 MIB Collector (snmpCollect) or the SNMPv1/v2 SNMP Collector (nvcollectord). v Integrate the Tivoli NetView program with the Tivoli Management Framework. Installation note: To install a Tivoli NetView language pack, you must install the Tivoli NetView English language product. You can install a Tivoli NetView language pack at the same time that you install the English language product, or you can install the language pack separately after installing the English language product.
Procedure
To install the Tivoli NetView program using the instalnv script, follow these steps: 1. If you are upgrading from an earlier release, follow these steps: a. For AIX systems with extremely large databases, determine whether special processing is required before upgrading to version 7.1.5. To do this, run the following command:
/usr/OV/bin/ovtopofix -a
If the ovtopofix command completes without an error, you can continue to upgrade the Tivoli NetView program. If the ovtopofix command fails, contact IBM Software Support. b. Verify that all Tivoli NetView and independent vendor software application daemons start without error. Remove any daemons from
21
startup that do not start correctly, or correct the reason for the failure. All daemons must start without error for a successful Tivoli NetView migration. In general, verify that the Tivoli NetView program and its associated applications are running correctly at the currently installed level. c. For a client, remove the server using the Client Setup application (/usr/OV/bin/clientsetup). To do this, click Configure Remove Server. The client upgrade installation fails if a server is set for the client. d. Close all Tivoli NetView windows and Web consoles. e. Turn off Tivoli NetView security if it is currently turned on. f. The upgrade process automatically backs up and migrates your customized Tivoli NetView data. However, if you want to manually back up the Tivoli NetView databases as a precautionary measure, use the Maintain Backup Selective Data option in the Server Setup application to backup the data (select the /usr/OV/ALL category of files) and then move the resulting backup directory to a different computer. g. Stop all daemons for independent software vendor applications. h. Enter the following command to stop all Tivoli NetView daemons:
/usr/OV/bin/ovstop nvsecd
2. (Optional) Restart the computer on which you are going to install the Tivoli NetView program. This step is recommended. 3. If you are exporting your display to a computer other than the one on which you are installing the Tivoli NetView product, make sure that your DISPLAY environment variable is correctly set. Otherwise, you will not be able to accept the license agreement during the installation, and the installation cannot proceed. 4. On the computer on which you want to install the Tivoli NetView program, mount the Tivoli NetView CD-ROM. 5. Change directories to the NetView directory:
cd cd_mount_point/NetView
Where cd_mount_point is the directory where the Tivoli NetView CD-ROM is mounted. 6. Enter one of the following commands, adding additional installation and configuration options as appropriate. For information about the syntax of the instalnv command, see Command syntax for the instalnv script on page 23. v To install the Tivoli NetView server for the first time, enter the following command:
instalnv -k SERVER
v To install the Tivoli NetView client for the first time, enter the following command:
instalnv -k CLIENT
v To upgrade the Tivoli NetView server from an earlier version, enter the following command:
instalnv -k SERVER -u
v To upgrade the Tivoli NetView client from an earlier version, enter the following command:
instalnv -k CLIENT -u
Notes: a. Use the -l option with or without the -k option to install a language pack.
22
Installation Guide
b. Use the -f option during a new installation if you want to integrate the Tivoli NetView program with the Tivoli Management Framework. 7. When prompted to continue the installation, click y, then click Accept to agree to the terms of the license agreement. Prerequisites are checked, the installation continues, and the progress of the installation is displayed. When the installation is complete, the message Installation completed successfully is displayed and the /tmp/update.log file is displayed. Installation messages are logged in the /tmp/update.log file and are also copied to the /usr/OV/install/configuration.log file. The /usr/OV/install/installation.log shows the options that were used during the installation. View the /usr/OV/install/configuration.log file to resolve error messages and investigate warning messages that might also indicate a problem. To find the error messages, enter the following command:
grep -i error /usr/OV/install/configuration.log
8. If you installed or upgraded the Tivoli NetView client, configure client/server access as described in Configuring client/server access on page 38. 9. If you upgraded from a language pack from an earlier version, you might need to add your modifications to the standard security registration files as described in Customizing security files after an upgrade on page 40. 10. If you plan to install Tivoli NetView optional software, proceed to Installing Tivoli NetView optional software on page 25. If you do not plan to install Tivoli NetView optional software, proceed to Table 8 on page 35.
Command syntax for the instalnv script

Use the following command syntax for the instalnv script: instalnv k kit [c community_name_list] [d b|a|l] [D db_user_name] [t server_name [p port] [w]] [U db_user_name [P db_user_password]] [f] [l locale] [q] instalnv k kit [c community_name_list] [d b|a|l] [D db_user_name] [T [e endpoint]] [U db_user_name [P db_user_password]] [f] [l locale] [q] instalnv k kit u [l locale] [U db_user_name [P db_user_password]] [q] instalnv l locale [q] [u] instalnv h k kit Specifies the Tivoli NetView component to install: SERVER or CLIENT. You cannot install the Tivoli NetView Client component on a Linux system. c community_name_list Specifies a list of up to six community names used for network discovery. The specified community names are added to the /usr/OV/conf/ communityNames.conf file. Each community name must be separated by a space and the entire list must be enclosed in double quotation marks (), for example, "name1 name2 name3". This parameter is optional, but if it is not specified, discovery might be limited if community names other than public are in use. d b|a|l Specifies the discovery mode as follows:
23
b a l
Backbone only All networks Local subnet only
The default value is local subnet only. For more information about these automatic discovery options, refer to the netmon man page. D db_user_name Displays a Java-based GUI to configure and enable the tdwdaemon daemon, where db_user_name is the DB2 instance user ID. Use this option when you want to use the SNMPv1 MIB Collector (snmpCollect) and forward data to Tivoli Data Warehouse. The installation process configures, registers, and starts the snmpCollect daemon. The tdwdaemon is also configured, registered, and started after the database is successfully created. For more information about exporting data to Tivoli Data Warehouse, refer to the IBM Tivoli NetView Warehouse Enablement Pack: Implementation Guide. You can switch between using the SNMPv1 MIB Collector and the SNMPv1/v2 SNMP Collector at any time after installation. For information about how to do this, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide. e endpoint Specifies the Tivoli endpoint instance number to use. The default number is 1. This option can only be used in conjunction with the T option. f Integrates the Tivoli NetView program with the Tivoli Management Framework and provides RIM support for the Tivoli NetView Database component. Installs the specified language pack on the server or client, where locale is one of the following values: v ko_KR (Korean) v ja_JP (Japanese EUC) v AIX systems only: Ja_JP (Japanese SJIS) v zh_CN (Simplified Chinese) v Red Flag Intel systems only: zh_CN.GB18030 (Simplified Chinese) p port Specifies the port to use when forwarding events to the Tivoli Enterprise Console server using the socket-based communication method. You must specify this parameter if the port has been customized. Otherwise, the default value (5529 for a Windows Tivoli Enterprise Console server or 0 for a UNIX or Linux Tivoli Enterprise Console server) is used. This option can only be used in conjunction with the -t option. t server_name Specifies the name of the Tivoli Enterprise Console server to which events are forwarded using the socket-based communication method. This option displays a Java-based GUI in which you can configure the list of IBM Tivoli Monitoring servers to query for use by the servmon daemon. T Specifies that the Tivoli communication method is used when forwarding events to the Tivoli Enterprise Console server. This option displays a Java-based GUI in which you can configure the list of IBM Tivoli Monitoring servers to query for use by the servmon daemon.
l locale
24
Installation Guide
U db_user_name Configures the DB2 database for data collection, where db_user_name is the DB2 Instance user ID. Use this option when you want to use the SNMPv1/v2 SNMP Collector for SNMPv2 and Counter64 support. The installation process configures, registers, and starts the nvcollectord and nvpollerd SNMP Collector daemons. If you are upgrading from version 7.1.4, active collection configurations in the /usr/OV/conf/snmpCol.conf file are migrated. (Collected data is not migrated.) If you do not specify this option, the Tivoli NetView program is configured to use the SNMPv1 MIB Collector (snmpCollect). You can change the data collector application you want to use at any time after installation. For information about how to do this, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide. P db_user_password Specifies the DB2 password for the DB2 Instance user ID specified with the U option. If you do not specify this option in conjunction with the U option, you are prompted for the DB2 password. Use this option for a silent installation. q u w Runs a silent installation. Upgrades the Tivoli NetView program from an earlier version to the current version. Indicates that the Tivoli Enterprise Console server specified with the t parameter is a Windows system. You must use this option for a Windows Tivoli Enterprise Console server to configure the port correctly. Displays the command syntax.
Installing Tivoli NetView optional software

The following topics provide information about how to install Tivoli NetView optional software: v Installing, upgrading, and configuring the Web console v Installing updates to the Web console on page 30 v AIX system: Installing and configuring the trapgend daemon on page 32 v AIX system and Solaris environment: Installing CiscoWorks integration on page 34 v AIX, Solaris, and Windows systems: Installing mid-level managers on page 35 v Installing IBM Tivoli Monitoring: Tivoli NetView Server Agent on page 35
Installing, upgrading, and configuring the Web console

You can use the following Web console software: v Full Web console Install the full Web console if system space is not a concern and you do not want to run the Web console in a Web browser. This is the recommended method. The full Web console runs as an application and contains all the files required to run the Web console. The Tivoli NetView program provides full Web console packages with and without the Java 2 Runtime Environment. v Thin Web console Install the thin Web console if system space is a concern.
25
The thin Web console runs as an application like the full Web console, but it uses less system disk space than the full Web console. Because it does not include all the files required to run the Web console, it connects to the Tivoli NetView server to load the Web console classes, as needed. It requires version 1.4.2 of the Java 2 Runtime Environment. v Applet version of the Web console Use the applet version of the Web console if you want to run the Web console in a Web browser. The applet version of the Web console does not require installation. The applet version of the Web console, like the thin Web console, connects to the Tivoli NetView server to load the Web console classes. It requires version 1.4.2 of the Java 2 Runtime Environment. SSL is disabled when running the Web console as an applet. For more information about running the applet version of the Web console, see Starting the Web console on page 29. You can install the full or thin Web console from the Tivoli NetView server, and you can install the Web console on Windows systems from the Tivoli NetView CD. If the Web console is already installed from a previous release, you must upgrade it to version 7.1.5 because you must use the same version of the Web console as the Tivoli NetView server. To determine if you have the required Java runtime environment for using the thin Web console or the applet version of the Web console, enter the following command on the command line:
java -fullversion
You must have version 1.4.2 of the Java 2 Runtime Environment, which also contains the Java plug-in for the applet version of the Web console. To obtain version 1.4.2 of the Java 2 Runtime Environment, go to one of the following Web sites:
Operating system AIX Web site http://www.ibm.com/developerworks/java/jdk/aix/service.html Click the appropriate option (Java 1.4.2 32bit or Java 1.4.2 64bit) in the table to download the jre142.tar file. Linux, Solaris, and Windows http://www.java.sun.com/j2se/1.4.2/download.html
Installing or upgrading the Web console from the Tivoli NetView server
To install or upgrade the Web console from the Tivoli NetView server, follow these steps: 1. If you are upgrading the Web console, complete these steps: a. Optional: Manually save the web_console_installation_directory/lib/ properties/DefaultHostAndPort.properties file, which is not migrated. The DefaultHostAndPort.properties file is located in the directory where you installed the Web console, and it contains the list of hosts that the Web console has connected to. This list is displayed in the Web console login window.
26
Installation Guide
b. Uninstall the previous version of the Web console using one of the following methods: v For Windows systems: If you installed the Web console using the nvwcinstall.exe executable file, use the Add or Remove Programs utility from the Control panel. If you installed the Web console using the nvwc_thin.zip file, manually remove the directory in which the Web console software is installed. v For UNIX and Linux systems: Run the /web_install_dir/nvwc/uninstall_nvwc command on the computer where the Web console is installed, where web_install_dir is the directory in which the Web console is installed. 2. From your Web browser, go to the following Web site:
http://server:8080/download
Where server is the host name of the Tivoli NetView server. 3. Download the appropriate Web console software package as described in the following table:
Table 6. Web console software packages Web console software Full Web console Operating system AIX, Linux, and Solaris AIX Linux Solaris Windows Thin console AIX, Linux, and Solaris Windows Software package to download nvwc.tar (without the Java 2 Runtime Environment) nvwc_aix_jre_1.4.tar (includes the Java 2 Runtime Environment) nvwc_linux_jre_1.4.tar (includes the Java 2 Runtime Environment) nvwc_solaris_jre_1.4.tar (includes the Java 2 Runtime Environment) nvwcinstall.exe (includes the Java 2 Runtime Environment) nvwc_thin.tar nvwc_thin.zip Hard disk space requirements 22 MB 160 MB 150 MB 170 MB 90 MB 10 MB 10 MB
Delete the TAR or ZIP file after the installation to free half of the required disk space. 40 MB of the required disk space is temporarily required during installation.
4. Do one of the following: v For a TAR or zipped file, extract the Web console files into the directory of your choice. v For the Windows executable file, nvwcinstall.exe, double-click the file, and the InstallShield wizard guides you through the installation. The Web console software is installed in the C:\Program Files\Tivoli Systems\Tivoli NetView Web Console directory by default, or you can click Browse during the installation procedure to navigate to the directory where you want to install the Web console software. 5. If you installed the thin Web console, follow one of these procedures from the directory in which you installed the Web console files: v UNIX and Linux systems: a. Open the nvwc/bin/nvwc.sh file in a text editor.
27
b. Go to the following line in the nvwc.sh file:

#JAVA_HOME=/usr/java
c. Add a line that sets JAVA_HOME to the Java installation directory similar to the following example:
JAVA_HOME=/usr/java/jdk1.4.2
d. Save the nvwc.sh file. v Windows systems: a. Open the nvwc\bin\nvwc.bat file in a text editor. b. Go to the following line in the nvwc.bat file:
REM set JAVA_EXE=yourpath\java.exe
c. Add a line that sets JAVA_EXE to the full path where the java.exe file is located similar to the following example:
set JAVA_EXE=C:\Program Files\ibm\Java142\jre\bin\jave.exe
d. Save the nvwc.bat file. v Optional: If you manually saved the DefaultHostAndPort.properties in step 1a on page 26, manually restore the DefaultHostAndPort.properties file to the web_console_installation_directory/lib/properties directory. 6. Start the Web console by entering the appropriate sequence of commands from the directory in which you installed the Web console files: v UNIX and Linux systems:
cd nvwc/bin nvwc.sh hostname 8080
Where hostname is the fully qualified host name of the Tivoli NetView server. v Windows systems: If you installed the Web console using the zipped file, enter the following sequence of commands:
cd nvwc\bin nvwc.bat hostname 8080
Where hostname is the fully qualified host name of the Tivoli NetView server. If you installed the Web console using the nvwcinstall.exe file, from the Start menu, click Programs Tivoli NetView NetView Web Console.
Windows systems: Installing or upgrading the Web console from the Tivoli NetView installation CD
To install the Web console from the Tivoli NetView installation CD, follow these steps: 1. If you are upgrading the Web console, complete these steps: a. Optional: Manually save the web_console_installation_directory/lib/ properties/DefaultHostAndPort.properties file, which is not migrated. The DefaultHostAndPort.properties file is located in the directory where you installed the Web console, and it contains the list of hosts that the Web console has connected to. This list is displayed in the Web console login window. b. Uninstall the previous version of the Web console using one of the following methods: v If you installed the Web console using the nvwcinstall.exe file, use the Add or Remove Programs utility from the Control panel. v If you installed the Web console using the nvwc_thin.zip file, manually remove the directory in which the Web console software is installed.
28
Installation Guide
2. From the Tivoli NetView Installation window, select Install Web Console Only. 3. When prompted to continue with the installation, click Yes. 4. Click Next to accept the default installation directory, C:\Program Files\Tivoli Systems\Tivoli NetView Web Console, or click Browse to navigate to the installation directory of your choice. 5. From the final installation window, you can start the Web console. 6. Click Finish. 7. Optional: If you manually saved the DefaultHostAndPort.properties in step 1a on page 28, manually restore the DefaultHostAndPort.properties file to the web_console_installation_directory/lib/properties directory.
Starting the Web console

To start the Web console, use one of the following methods: v UNIX and Linux systems: Run the nvwc.sh script, which is located in the nvwc/bin directory under the directory where you extracted the Web console software files. v Windows systems: From the Start menu, click Programs Tivoli NetView NetView Web Console or run the nvwc.bat script, which is located in the nvwc\bin directory under the directory where you installed the Web console software. You can start the Web console from the Start menu if you used the nvwcinstall.exe script to install the Web console. v To start the Web console as an applet, type the following URL in your Web browser: http://hostname:8080/netview/NetViewApplet Where hostname is the host name of your Web server. Upgrade information: Before starting the Web console as an applet, you must clear the Java plug-in cache on all machines that ran the Web console applet connected to a previous version of the Web server. Refer to your Java plug-in documentation for information on how to clear the cache.
Configuring the Web daemons

To configure the Web daemons from the Server Setup menu, click Configure Configure Web Server Enable Web Daemons to display the Enable Web Daemons window. Use this window to perform the following tasks: v Enable the webserver daemon and configure its port. v Enable Secure Socket Layer (SSL) security for the Web server and configure its port. v Enable the snmpserver daemon. v Enable the netviewd daemon. v Start and stop the snmpserver and netviewd daemons Note: SSL is not supported in the applet version of the Web console. Enabling SSL: To enable SSL, follow these steps: 1. Stop any Web consoles that are running. 2. From the Server Setup menu click Configure Configure Web Server Enable Web Daemons. 3. Verify that yes is displayed on the Enable webserver daemon button and that the correct port number is displayed. If no is displayed, select yes from the list.
29
4. Select yes from the Enable SSL for Secure Web Server Communications list. 5. Verify that you want to use the default port number that is specified. Specify a different port number if you do not want to use the default value. 6. Click either OK or Apply. 7. Stop and restart the webserver daemon. Note: After logging on to the Web console using port 8080 with SSL enabled, https:server:8443 instead of http:server:8080 is displayed (where server is the name of the server). Disabling SSL: To disable SSL, follow these steps: 1. Stop any Web consoles that are running. 2. From Server Setup click Configure Configure Web Server Enable Web Daemons. 3. Select no from the Enable SSL For Secure Web Server Communications list. 4. Click either OK or Apply. 5. Stop and restart the webserver daemon.
Installing updates to the Web console

When you start the Web console, you might receive a notice from the Web Console Updater indicating software updates to the Web console are available for installation. Web console users can install these updates directly from the Web console without having to uninstall and reinstall the entire Web console. Use the Web Console Updater to install the following types of updates to the full version of the Web console only: v Fix packs for the Web console v Interim fixes for the Web console The Web Console Updater can also be accessed from the Tools menu in the Web console (Tools Web Console Updater).
How the Web Console Updater works

At Web console startup, the time stamps of the Web console build packages are compared between the Web console and the Tivoli NetView server. If the timestamps do not match, one or more updates are available for the Web console and the Tivoli Web Console Updater window is displayed so you can apply the updates directly from the Web console. You can view the following type of information in the Web Console Updater window: v The updates available for installation (update packages available on the server that are not installed on the local Web console) v The updates that were already installed (for possible rollback or uninstallation) v Brief description of the update v More detailed information about the update, such as a readme file or release notes document (or links to that information) The directory on the Tivoli NetView server that is searched for updates is /usr/OV/www/wwwroot/updates/Vn.n, where n.n is the release and modification level. Updates are listed in this directory as packages containing individual XML files.
30
Installation Guide
When you install updates through the Web Console Updater, a backout directory is created on the system under the Web console installation directory (Web_Console_install_dir/services/Vn.n/package_name ) with the affected files before they are updated. It is not necessary to access these files manually to perform a rollback because the Web Console Updater handles the rollback.
Installing updates
Use the following procedure to install an update to the Web console: 1. Click Tools Web Console Updater. 2. On the Updates tab, review the list of available updates. Select the updates to install and click Install Updates. You can install multiple updates at the same time. A progress bar is displayed with the package name, file name downloaded, and download percentage completed. 3. At the prompt to shut down the Web console, click OK to complete the installation. 4. Restart the Web console.
Viewing installed updates

Use the following procedure to see a list of updates that were already installed on the local Web console. 1. Click Tools Web Console Updater. 2. Click Rollbacks. A list of updates is displayed with the dates when they were installed.
Uninstalling updates
Use the following procedure to uninstall (roll back) applied updates: 1. Click Tools Web Console Updater. 2. Click Rollbacks. A list of updates is displayed with the dates when they were installed. The installation date is checked to see if it is earlier than any unselected installed updates. If it is, a message is displayed to inform you that a conflicting update exists and the roll back is cancelled. (You cannot roll back an update if a more current update exists and is not rolled back first.) To correct the conflict, unselect the update for roll back and select the more recent update for rolling back first. 3. Select the items to roll back and click Rollback updates. 4. At the prompt, click OK to exit the Web console to complete the rollback and restart the console.
Web Console Updater error logs

Additional details about errors occurring during the update checking, installation, and rollback processes are provided in the following files: v Errors related to checking the Tivoli NetView server for available updates: /usr/OV/www/logs/netviewservlets.log v Errors related to installing an update: /java_temporary_directory/ webConsoleUpdate.log (the prompt that is displayed to shut down the Web console after the Install Updates button is clicked displays the location of the update log file) v Errors related to rolling back an update: /java_temporary_directory/ backoutWebConsole.log (the prompt that is displayed to shut down the Web console after the Rollback updates button is clicked displays the location of the backout log file)
31
Review these files as appropriate for additional information if necessary.
AIX system: Installing and configuring the trapgend daemon

To install and configure the trapgend daemon, use the following methods. A root password is required with either method. The trapgend subagent enables remote AIX nodes to collect additional data and send the data in a more efficient manner to the system where the Tivoli NetView server is installed. v Using the command line: When running the nv6000_smit shell script from the command line, you can perform multiple trapgend operations on a remote node. v Using the Server Setup application (/usr/OV/bin/serversetup): When using the Server Setup application for trapgend daemon operations, you can perform one trapgend operation at a time on a remote node. Note: You should use the Server Setup application or the command line to install and configure the trapgend daemon. However, if you use SMIT to install and configure the trapgend daemon, be aware that when you enter the password in the SMIT dialog, the password is written in the smit.log and smit.script files, which anyone can read. If you leave the SMIT password field blank, you are prompted for the password, and the password is not be written in the smit.log or smit.script files. You can perform the following trapgend operations using the Server Setup application or the nv6000_smit shell script from the command line: v Install or update the trapgend daemon. v Add and delete trap destinations. v Start and stop the trapgend daemon. v Check the status and test the trapgend daemon. v Remove the trapgend daemon. Note: You can remove the trapgend daemon from a remote node only if the Tivoli NetView server program is not installed on the remote node.
Using the command line

To install and configure the trapgend daemon, you can create a shell script that calls the /usr/OV/bin/nv6000_smit shell script. You can use the /usr/OV/bin/nv6000_smit shell script to perform multiple trapgend operations on remote nodes. For more information, refer to IBM Tivoli NetView for UNIX and Linux Programmers Reference. Note: The /usr/OV/bin/nv6000_smit shell script requires a password for the user ID you specify in your shell script. If you do not want to include the password in your shell script, run the shell script in the foreground, and you will be prompted to enter the password. If you want to run your shell script unattended, you must include the password in your shell script. To install and configure the trapgend daemon using the /usr/OV/bin/nv6000_smit shell script, follow these steps: 1. Create a shell script. For an example, see Example of a shell script on page 33. 2. Add a new line for each operation you want the shell script to perform. See Example of a shell script on page 33 for an example of lines in the netview shell script. Each line in the shell script must call the /usr/OV/bin/nv6000_smit shell script and include the following parameters:
32
Installation Guide
v Keyword (subagentR) v Operation to perform (install, update, status, start, test, stop, addtrap, deletetrap, or remove) v Remote node name or IP address v User ID on the remote node (root or a user ID with the appropriate permissions, a member of the system group, group 0) v Community name v Trap destination v Optional: Password for the user ID on the remote node. If you do not specify a password, you are prompted to enter one when your shell script is run. 3. Save and run the shell script file.
Example of a shell script

The following example shows lines in a shell script created for multiple trapgend daemon operations. The first line adds a trap destination for a remote node. The second line installs the trapgend daemon on a remote node.
/usr/OV/bin/nv6000_smit subagentR addtrap mlsnm003 userID \ public 9.67.5.189 /usr/OV/bin/nv6000_smit subagentR install mdcnm008 userID \ public 9.67.163.41 password
The variables indicate the following: subagentR Keyword addtrap Remote operation mlsnm003 Remote node name userID User ID on the remote node (root or the user ID with the appropriate permissions, a member of the system group, group 0) public Community name 9.67.5.189 IP address of the manager node to receive traps password Password for the user ID on the remote node
Using the Server Setup application

To install and configure the trapgend daemon using the Server Setup application, follow these steps: 1. Enter /usr/OV/bin/serversetup to start the Server Setup application. 2. Click Configure Install/configure subagent (trapgend) on remote RISC System/6000. 3. Complete the fields in the dialog box as described in Table 7 on page 34.
33
Table 7. trapgend options Option Remote Operation Action Select one of the following operations that you want to perform on the remote node: Add trap destination only Add a trap destination on a remote node. Delete trap destination only Delete a trap destination on a remote node. Install subagent Install the trapgend daemon on a remote node. Remove subagent Remove the trapgend daemon from a remote node. The Tivoli NetView program cannot be installed on the remote node. Start subagent Start the trapgend daemon without any other options. Status of subagent View status of the trapgend daemon and trap destinations. Stop subagent Stop the trapgend daemon. Test subagent Test the operation of the trapgend daemon. Update subagent Update the remote trapgend key files to the same level at the server. Remote node name or IP address User ID on remote node Enter the node name or IP address of the remote node. Enter the user ID on the remote node. The default is root, but you can specify a user ID that has the appropriate permissions (a member of the system group, group 0). Enter the community name of the remote node. The default is public. Enter the IP address of the manager node set to receive traps from the remote node (if different than the default provided). Enter the password for the user ID on the remote node. If you type the password here, it is displayed as you type it. If you leave this field blank, the program prompts you for a password, and it is not displayed as you type it.
Community name for snmpd and trapgend IP address of trap destination node User password for remote node
4. Click OK. 5. Do one of the following: v If you entered a password in the User password for remote node field of the Install/configure subagent dialog, click Close. v If you did not enter a password, enter a password when the program prompts you for it. The password is not displayed as you type it, and the cursor does not move as you type. Then, click Close.
AIX system and Solaris environment: Installing CiscoWorks integration

The Tivoli NetView program supports the CiscoWorks integration model. The necessary Cisco adapters are shipped on the Tivoli NetView Additional Options CD in the ADAPTERS directory. For information about performing the CiscoWorks integration, refer to the readme files in the ADAPTERS directory. For more
34
Installation Guide
information about these procedures and the overall integration model, go to the following Cisco Web site (a CCO login is required): http://cisco.com/warp/customer/cc/cisco/mkt/enm/cw2000/ tech/cwnms_tb.html
AIX, Solaris, and Windows systems: Installing mid-level managers

The mid-level manager software is located on the Tivoli NetView Additional Options CD in the MLM directory. For information about installing the mid-level manager software, refer to the IBM Tivoli NetView Mid-Level Manager Users Guide.
Installing IBM Tivoli Monitoring: Tivoli NetView Server Agent

The Tivoli NetView product also ships a monitoring agent, IBM Tivoli Monitoring: Tivoli NetView Server Agent, which you can use with IBM Tivoli Monitoring version 6.1 to monitor the health of the Tivoli NetView program. The monitoring agent software is located on the Tivoli NetView Additional Options CD in the ITM directory. The language packs for the monitoring agent are located in the IRA directory. For information about installing and using IBM Tivoli Monitoring: Tivoli NetView Server Agent, refer to the IBM Tivoli Monitoring: Tivoli NetView Server Agent User's Guide.
After installing or upgrading the Tivoli NetView program

After installing the Tivoli NetView program, complete the tasks that are appropriate for your situation as described in Table 8:
Table 8. Tasks to complete after installing the Tivoli NetView program Task Backing up the Tivoli NetView databases on page 36 Initializing the Tivoli NetView runtime environment on page 36 Synchronizing topology changes on a backup Tivoli NetView server on page 36 Configuring client/server access on page 38 Linux system: Configuring the SNMP agent on page 39 Systems that require completion of this task All All (Optional) Primary and secondary Tivoli NetView servers if you have Tivoli NetView installed on a secondary server All, when you have installed Tivoli NetView clients Linux systems
Before starting the Tivoli NetView program, you might want to customize the discovery process by creating a seed file, defining the automatic discovery mode, and specifying community names (if you did not already define the discovery mode and community names during the installation process). You can define the discovery mode and seed file by configuring the netmon daemon using the Server Setup application. You might also want to customize the map layout using the location.conf file. For information about customizing discovery and the map layout, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide.
35
You might also need to set up user accounts to permit access to the Web server. For information about setting up user accounts for the Web server, refer to the IBM Tivoli NetView Web Console Users Guide.
Backing up the Tivoli NetView databases

When you are satisfied that your Tivoli NetView installation is successful, back up the /usr/OV/databases/openview directory and plan to do so on a periodic basis. If you need to restore the Tivoli NetView databases later, you must have a backup that was created at the same version level of the Tivoli NetView program. For example, you cannot successfully restore Tivoli NetView version 7.1.4 databases to version 7.1.5 of the Tivoli NetView program. For information about backing up the Tivoli NetView databases using the hot backup function, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide.
Initializing the Tivoli NetView runtime environment

Before you start the Tivoli NetView program, you must initialize the Tivoli NetView runtime environment using the /usr/OV/bin/NVenvironment shell script. Source the NVenvironment shell script from your login script. For example, if you are using the Bourne shell, add . /usr/OV/bin/NVenvironment to your .profile file.
Synchronizing topology changes on a backup Tivoli NetView server

If you have decided to install and run Tivoli NetView on both a primary and a secondary server, you can synchronize the servers so that the backup server automatically receives information about changes in the network topology when the changes are discovered by the primary Tivoli NetView server. For example, you can forward information about new or deleted nodes or interfaces in the network, or indications when nodes or interfaces become managed or unmanaged. The primary server uses the netmon daemon to send notification of these changes in the form of specific SNMP traps to the backup server. On the secondary server, the netmon daemon handles the events associated with additions, deletions, and demand polling. The traps associated with the topology synchronization are 58785798, 58785799, 58785800, and 58785801. For a detailed description, refer to the list of Tivoli NetView internal traps in the IBM Tivoli NetView for UNIX and Linux Administrators Guide. To enable this optional synchronization, you must configure both the primary and secondary servers for this type of communication after you have installed the Tivoli NetView program on both systems. Before configuring the synchronization, ensure that the primary server and secondary server have identical databases and are configured the same in the Tivoli NetView product. (They should have the same netmon seed file and netmon.conf configuration files except for the synchronization option setting.) You can use the Tivoli NetView hot backup function to ensure the databases are identical. For information on how to use the hot backup function, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide. If the databases are not identical before you configure topology synchronization, you might later receive errors on the secondary server indicating the netmon daemon is disconnected from the trapd daemon due to the volume of traps.
36
Installation Guide
The topology synchronization function is intended to handle occasional database changes after databases are determined to be identical. It is not intended to handle the volume of database changes associated with discovering a network for the first time or when clearing the database. If you have to clear the database and rediscover networks on the primary server, use the hot backup function to back up the database on the primary server and copy the database to the secondary server. After the databases are identical, you can then use the synchronization function to keep the topology changes synchronized. To configure the synchronization of topology changes between a primary and secondary server, follow these steps in the sequence shown: 1. On the primary Tivoli NetView server, follow these steps after you have installed or upgraded the Tivoli NetView program: a. Edit the /usr/OV/conf/netmon.conf file and activate the following line (remove the # comment symbol). Set the synchronization value to TRUE and save the file:
NV_NETMON_SYNC_TOPOLOGY=TRUE
b. Use the Server Setup application in the Tivoli NetView native console to specify that the synchronization traps should be forwarded to the secondary server. Click Administer Server Setup Configure Set options for daemons Set options for event and trap processing daemons Set options for trapd daemon. c. In the Forward specific traps as events to field, type the host name or IP address of the secondary Tivoli NetView server and click OK. You can enter more than one secondary server host name. d. From the command line, enter the following command to enable the primary server. This action adds the four synchronization traps to the /usr/OV/conf/C/trapd.conf file and sets them for forwarding to the secondary server.
/usr/OV/bin/setSyncPrimary.sh
2. On the secondary Tivoli NetView server, follow these steps after you have installed or upgraded the Tivoli NetView program. a. In the Tivoli NetView native console, click Options Topology/Status Polling Intervals: IP. In the window that opens, ensure that the check box for Enable Polling and Discovery settings is selected. You should also select Poll for Status to keep the status up to date and Discover New Services if you are running the servmon daemon. Because the topology changes will be propagated to the secondary server automatically, there is no need to select Discover New Nodes or Poll for Configuration. b. From the command line, enter the following command to enable the secondary server. This action adds the four synchronization traps to the /usr/OV/conf/C/trapd.conf file and sets the action on the Synch Unmanage/Manage event (58785801).
/usr/OV/bin/setSyncSecondary.sh
3. On the primary Tivoli NetView server, enter the following commands to restart the netmon daemon:
/usr/OV/bin/ovstop netmon /usr/OV/bin/ovstart netmon
After completing this procedure, topology information is kept synchronized for you. Typically, however, you should also keep the two Tivoli NetView databases
37
synchronized thereafter by regularly copying the database from the primary to the secondary server (for example, on a weekly or monthly basis). The synchronization function can be used to keep topology changes synchronized in between the periodic copying of the database from the primary to the backup server.
Configuring client/server access

If you installed Tivoli NetView clients and Network File System (NFS) security is enabled on the Tivoli NetView server, NFS security must also be enabled on the Tivoli NetView client to ensure that the NFS mounts work correctly. To start NFS security, enter the following commands:
nfso -o portcheck=1 nfso -o nfs_use_reserved_ports=1
You must also configure the server and client in the following order: 1. Configure the server to enable the clients to access it, as described in Configuring a server to enable client access. 2. Configure the client to access the server, as described in Configuring a client to access a server. Notes: 1. When using a client/server configuration, you must stop and restart the native client if the computer on which the Tivoli NetView server resides is restarted. Restarting the Tivoli NetView server causes the loss of session information regarding the client. Stopping and restarting the client restores the session information. 2. For the Solaris environment: When configuring a client/server system for the first time in the Solaris operating system, you might see the following error message when you are adding client access:
Cant open /etc/dfs/sharetab Operation completed
This is because the /etc/dfs/sharetab file does not exist on the Solaris environment until it is created. The client setup process creates the /etc/dfs/sharetab file after access to the file fails. Therefore, you can ignore the error message.
Configuring a server to enable client access

Multiple clients can access a server simultaneously. You must configure the server to enable access for each client. To add client access, complete the following steps: 1. Enter /usr/OV/bin/serversetup from the command line to start the Tivoli NetView Server Setup application. 2. Click Configure Configure Tivoli NetView Client Add Client Access. 3. In the Add Client Access dialog box, type the name of the client and click OK. The results of the command are displayed in the Output window. If the server and client reside in different domains, the /etc/hosts file might need an additional entry to assist with communications between the server and client.
Configuring a client to access a server

A client can access only one server at a time. Ensure that you have granted the client access to the server before configuring the client. If you have not, complete the steps in the previous Configuring a server to enable client access section. To configure a client to communicate with a server, complete the following steps on the client machine:
38
Installation Guide
1. Ensure that the date and time on the client machine are the same date and time as are on the server machine. Use the date command to check this. The date and time must be synchronized for security and map administration to work correctly. 2. Enter /usr/OV/bin/clientsetup from the command line to start the Tivoli NetView Client Setup application. 3. Click Configure Add/Change Server. The Add/Change Server dialog box is displayed. 4. Complete the dialog box as follows: a. Type the name of the server. b. Type the port number (8080 is the default port) for the Web server. c. Select the location for the Map database. This value determines whether the map database resides locally on the client machine or is NFS mounted from the server. An ICMP echo request (ping) is used to test the connection to the Tivoli NetView server. If the ping is not successful, a warning message is displayed. At the time a client is configured to access a server, NFS mounts are performed from the client to the server for the following directories: v /usr/OV/conf v /usr/OV/databases/snmpCollect If the map database location is set to NFS, then NFS mounts from the server are also performed for the following directories: v /usr/OV/databases/openview/mapdb v /usr/OV/databases/openview/defmap
Linux system: Configuring the SNMP agent

After installing the Tivoli NetView program on the Linux system, you must configure the SNMP agent, snmpd, to forward a request for a MIB variable to the Tivoli NetView server. To do this, follow these steps: 1. Add the following passthrough statement to the snmpd.conf configuration file, which is located in either the /etc or /etc/snmp directory, for the SNMP agent:
pass .1.3.6.1.4.1.2.6.4.6.1 /bin/sh /usr/OV/bin/mgragentd viw system included .1
2. Stop and restart the SNMP agent by entering the following sequence of commands:
/etc/init.d/snmpd stop /etc/init.d/snmpd start
After installing or upgrading the language packs

After installing the Tivoli NetView language packs, complete the tasks that are appropriate for your situation as described in Table 9:
Table 9. Tasks to complete after installing the language packs Task Enabling language support on page 40 Customizing security files after an upgrade on page 40 Systems that require completion of this task All All, if you have upgraded from a previous release and you modified the standard Tivoli NetView security registration files
39
Table 9. Tasks to complete after installing the language packs (continued) Task Linux systems: Specifying a language pack input method on page 41 Systems that require completion of this task Linux systems
Configuring a Web browser to run the Web All console as an applet on page 41 Resolving font quality problems when using the Web console on page 41 All when using the Web console
Linux systems: Setting text encoding for the Linux systems when forwarding events in Simplified Chinese locale when forwarding the Simplified Chinese language to the Tivoli events to the Tivoli Enterprise Console Enterprise Console server server on page 42
Enabling language support

To enable language support, set the LANG and LC_ALL environment variables to the appropriate locale in your current session before you start the Tivoli NetView native console or any other Tivoli NetView applications. Table 10 lists the settings for the LANG and LC_ALL environment variables for each code set and operating system:
Table 10. Environment variable settings for language support Code set AIX Japanese EUC Japanese SJIS Korean EUC Simplified Chinese Simplified Chinese GB18030 (Red Flag Intel systems) ja_JP Ja_JP ko_KR zh_CN Not applicable Operating system Linux ja_JP Not applicable ko_KR zh_CN zh_CN.GB18030 Solaris ja Not applicable ko zh Not applicable
Customizing security files after an upgrade

If you modified the standard Tivoli NetView security registration files, you must manually add your modifications to the new version of the files because the security registration files are not migrated during the upgrade process. The security registration files are located in the following directories: v /usr/OV/security/$LANG/Domains/registration v /usr/OV/security/$LANG/Domains/SrAdmin You can find the previous version of the security registration files in the /usr/OV.back.v7r1 directory. The Tivoli NetView product does not provide the sample Oper group security registration files for the language packs. To create the security registration files for the Oper group, use the nvsec_admin application to copy from the SrAdmin group and then modify the permissions of the menus and the applications to which you want to limit access.
40
Installation Guide
Linux systems: Specifying a language pack input method

The default input method for the Japanese language pack on the Linux system is kinput2. To use a different input method, edit all of the files in the /usr/OV/app-defaults/ja_JP directory and change the string kinput2 to the name of the input method that you want to use. The Korean and Simplified Chinese language packs are not shipped with a default input method. To specify an input method, follow these steps: 1. Edit all of the files in the appropriate locale directory: v For Simplified Chinese: /usr/OV/app-defaults/zh_CN v For Korean: /usr/OV/app-defaults/ko_KR v Uncomment the line !*inputMethod: <input method> and replace <input method> with the input method that you want to use. The following example shows how to specify the xcin input method for simplified Chinese:
*inputMethod: xcin
Configuring a Web browser to run the Web console as an applet

To configure a Web browser to run the Web console as an applet, complete one of the following procedures: v For Firefox: 1. From the menu bar, click Edit Preferences. 2. In the Fonts & Colors pane of the Content tab, click Advanced. 3. In the Fonts dialog box, select a language from the Fonts for list and select the appropriate font from the font lists. 4. From the menu bar, click View Character Encoding Unicode (UTF-8). v For Internet Explorer: 1. From the menu bar, click Tools Internet Options. 2. Click Fonts and select a font from the Language script list and select a corresponding Web page font and plain text font. 3. From the menu bar, click View Encoding Unicode (UTF-8). v For Konqueror: 1. From the menu bar, click Settings Configure Konqueror. 2. From the Configure Konqueror window, click Fonts in the navigation pane on the left and select the appropriate font from the font lists on the right. 3. From the menu bar, click View Set Encoding Manual Unicode (utf8). v For Mozilla: 1. From the menu bar, click Edit Preferences. 2. Click Fonts under the Appearance category and specify the font to use from the Fonts for list. 3. From the menu bar, click View Character Coding Unicode (UTF-8). For more information about these settings, refer to the online help in your Web browser.
Resolving font quality problems when using the Web console

The JREs for all platforms for which the Tivoli NetView program offers national language support use font settings that can result in fonts not displaying properly when using the Web console in non-English language environments.
41
To overcome this problem, use the IBM World-Type font set. Contact IBM Software Support for information about how to obtain the World-Type fonts and how to configure your JRE to use these fonts.
Linux systems: Setting text encoding for the Simplified Chinese locale when forwarding events to the Tivoli Enterprise Console server
If you are forwarding events from the Tivoli NetView server that is running in the Simplified Chinese locale on a Linux system to the Tivoli Enterprise Console server, you must manually set the text encoding for the Simplified Chinese locale so that events are translated and displayed correctly in the event console. To do this, follow these steps: 1. Complete the following steps on the Tivoli Enterprise Console server: a. Run the following command to get the object dispatcher environment and save it to a temporary file:
odadmin environ get > temporary_file
b. Add the following lines to your temporary file:

LANG=zh_CN.GB18030 LC_ALL=zh_CN.GB18030 DB2CODEPAGE=1208
c. Run the following command to set the new object dispatcher environment:
odadmin environ set < temporary_file
d. Run the following commands to recycle and start all object dispatchers:
odadmin reexec odadmin start all
e. Run the following commands to stop and restart the event server:
wstopesvr wstartesvr
2. Complete the following steps on the Tivoli NetView server: a. Copy the GB18030 file from the $TISDIR/codeset directory on the event server to the /usr/OV/codeset directory on the Tivoli NetView server. b. Run the following commands:
/usr/OV/bin/ovstop nvserverd /usr/OV/bin/ovstart nvserverd
Configuring the Tivoli NetView program

After the Tivoli NetView program is installed, you can start the Tivoli NetView program using the default settings. You can also configure your system in the following ways: v Configure the Tivoli NetView program to run in unattended mode as the netviewd daemon so that the Web console can access map data without running the native console. v Customize the IP Internet map to reflect your network layout: geographically, hierarchically, or by some other criteria that is important to your company. v Customize network discovery by configuring the netmon daemon to use a seed file, which is an ASCII file in which you specify the nodes in your network that you want or do not want to be discovered. v Configure the Tivoli NetView program to forward events to the Tivoli Enterprise Console event server if you have not already done so during installation using the instalnv script.
42
Installation Guide
v Customize the startup process to set environment variables or run scripts when the Tivoli NetView program is started. v If you use mid-level managers in your network, customize the network discovery by configuring the netmon daemon to use an MLM seed file so that each mid-level manager polls nodes in its own domain and reports status changes to the Tivoli NetView program. For more information about using mid-level managers, refer to the IBM Tivoli NetView Mid-Level Manager Users Guide. v Change the Tivoli NetView daemon defaults. v Change the symbols that represent the nodes in your network. v Define additional values for the vendor and SNMP Agent fields. For information about configuring the Tivoli NetView program, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide.
43
44
Installation Guide
Chapter 3. Starting and stopping the Tivoli NetView program

This chapter provides information about starting and stopping the Tivoli NetView program and its daemons.
Before starting the Tivoli NetView program

Before starting the Tivoli NetView program, complete the following tasks: v Ensure that you have set up the Tivoli NetView runtime environment as described in Initializing the Tivoli NetView runtime environment on page 36. v Ensure that the daemons are running as described in Checking the daemon status. v Optionally, register daemons in the startup file that are not started as part of the default startup process as described in Registering and unregistering the daemons for optional functions. The gtmd, noniptopod, otmd, C5d, netviewd, and tdwdaemon daemons are not automatically registered in the startup file and, therefore, do not start when you start the Tivoli NetView program. For more information about these daemons, refer to the appropriate man pages.
Checking the daemon status

Before you start Tivoli NetView, you might want to check the statuses of the daemons and start them if necessary. You do not need root permissions to check the statuses of the daemons, but you must have root permissions to start them. If the required daemons are not running, the native console does not run. The server installation process starts all the daemons registered in the /usr/OV/conf/ovsuf file and checks the status of the daemons. If you have root permissions, the SNMP agent and all registered daemons are started when you start the native console using the netview command. To check the statuses of the daemons from the client, use the nvstatus command. To check the statuses of the daemons from the server, use the ovstatus command or the Server Setup application. For more information about the ovstatus and nvstatus commands, refer to man pages. To check the statuses of the Tivoli NetView daemons using the Server Setup application, follow these steps: 1. Enter /usr/OV/bin/serversetup from the command line to start the Tivoli NetView Server Setup application. 2. Click Control Display Tivoli NetView status Display status of daemons. All the Tivoli NetView daemons and their statuses are displayed. Have the system administrator restart the daemons if you do not have root authority. For information on restarting daemons, see Starting and stopping the daemons on page 50.
Registering and unregistering the daemons for optional functions

The daemons for optional functions (gtmd, noniptopod, otmd, C5d, tdwdaemon, and netviewd daemons) are not automatically registered in the startup file and, therefore, are not started as part of the default startup process. These daemons
45
must be registered before they can be started. After the daemons are registered, they are started every time you run the ovstart command, the netview command as root, or when you start the system. When you no longer need to run these daemons, unregister the daemons from the startup file to improve the utilization of system resources. You can register and unregister the daemons using the command line or the Server Setup application.

To register or unregister a daemon, use one of the following commands: v To register and start a daemon use the following sequence of commands:
/usr/OV/bin/ovaddobj /usr/OV/lrf/daemon.lrf /usr/OV/bin/ovstart daemon
Where daemon is the name of the daemon you are registering. v To unregister a daemon, use the following command:
/usr/OV/bin/ovdelobj /usr/OV/lrf/daemon.lrf
Where daemon is the name of the daemon you want to unregister.

To register or unregister a daemon using the Server Setup application, follow one of these procedures: v To register a daemon, follow these steps: 1. Enter /usr/OV/bin/serversetup on the command line to start the Server Setup application. 2. Click Configure Set options for daemons. 3. Select one of the following: Set options for topology, discovery, and database daemons Set options for event and trap processing daemons Set options for Agent Policy Manager daemons 4. Select the daemon you want to register. The Set Options dialog for the selected daemon is displayed. You do not need to change the defaults in the entry fields. 5. Click OK. The daemon is registered and added to the startup file. 6. Click Close. v To unregister a daemon, follow these steps: 1. Enter /usr/OV/bin/serversetup on the command line to start the Server Setup application. 2. Click Configure Delete daemon from ovsuf startup file. 3. Select the daemon that you want to delete from the dialog box that is displayed. The selected daemon is displayed in the Daemon to delete field. 4. Click OK. 5. Click OK to confirm the deletion. 6. Repeat Steps 3 and 4 for each daemon you want to delete. The selected daemons are deleted from the startup file, but the daemons are not stopped if they are running. 7. Click Close.
46
Installation Guide
Starting the Tivoli NetView program

You can start the Tivoli NetView program using the netview shell script or the Tivoli desktop. (The Tivoli desktop is available if you installed the Tivoli NetView program using the -f option with the instalnv command.) When you use the Tivoli desktop, the netview shell script is used to start the Tivoli NetView program. For more information about the netview command, refer to the man page. You can also run the Tivoli NetView program as the netviewd daemon so that the Web console can access map data without running the native console. For more information about running the Tivoli NetView program as the netviewd daemon, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide. When the daemons are first started, you can expect intense polling traffic, because the netmon daemon is working to discover objects on your network. The default management region is the management system (the node on which the Tivoli NetView program is running) and the networks to which it is directly attached. The map of the initial management region displays networks or subnets, segments, and gateways. Unmanaged nodes are displayed in light brown. For more information about the netmon daemon, refer to the man page. The first time Tivoli NetView creates a map on a client, especially if the database is NFS mounted, the synchronization might take several minutes. Generally, a client machine is smaller than a server machine, but the client has to retrieve all the map information from the server. When the client brings up the native console, it synchronizes the information that it displays with the database information. The amount of time this takes varies according to the size of your network. The native console creates and displays an interactive graphical map, which represents the logical topology of your network. For each map, an environment of interactive windows called submaps is created. A submap is a particular view of some part of the network that displays symbols that represent objects. For more information on submaps, refer to IBM Tivoli NetView for UNIX and Linux Users Guide for Beginners.
Using the netview shell script

You can use the netview shell script to start the Tivoli NetView program whether you have root permissions or not. If the /usr/OV/bin directory is not in your PATH, either run the /usr/OV/bin/netview command or add the directory /usr/OV/bin to your PATH. For more information about the options for the netview command, refer to the man page. If you are on the Tivoli NetView server and have root permissions, the netview shell script first runs the /etc/netnmrc shell script on the AIX system or the /etc/init.d/netnmrc shell script on the Linux system and the Solaris environment. The /etc/netnmrc or the /etc/init.d/netnmrc shell script starts the SNMP agent, the nettl facility (the network logging and tracing facility), if they are not running, and the daemons registered in the /usr/OV/conf/ovsuf startup file. Then, the netview shell script runs the ovw command, which starts the native console. For more information on the nettl facility, the ovstart command, or the ovw command, refer to the appropriate man page. For the Solaris environment only:
47
The snmpdx daemon and the mibiisa daemon must be running for the Tivoli NetView server to work correctly. To run the snmpdx agent, enter the following command:
/etc/init.d/init.snmpdx start
Using the Tivoli desktop

The Tivoli desktop is available if you installed the Tivoli NetView program using the -f option with the instalnv command. To start the Tivoli NetView program using the Tivoli desktop, follow these steps: 1. Enter tivoli on the command line to access the Tivoli desktop. 2. Right-click the server or client icon and click Control Start user interface from the context menu. 3. Click the buttons beside the fields to set the options you want. 4. Click OK. The Tivoli NetView program starts, and the selected map is displayed. 5. Click OK.
Recycling the daemons

If you need to recycle the Tivoli NetView daemons, follow these steps: 1. Stop any native consoles and Web consoles that are running. 2. Run the /usr/OV/bin/ovstop nvsecd command to stop all the daemons and simulate a system restart. 3. Enter one of the following commands to start the daemons again: v AIX system:
/etc/netnmrc
v Linux system and Solaris environment:

/etc/init.d/netnmrc
Note: To run the netnmrc command, you must have already intialized the Tivoli NetView runtime environment as described in Initializing the Tivoli NetView runtime environment on page 36. If you are recycling one or two daemons, you can use the /usr/OV/bin/ovstart command to restart the daemons. However, if you are recycling all the daemons, use the netnmrc script to restart them. The netnmrc script checks that SNMP is running and sets the ulimit values in addition to starting the daemons. This process ensures that the Tivoli NetView program performs better and does not fail.
Logging output
Whether the Tivoli NetView program is started from the command line, the Tivoli desktop, or the Server Setup application, messages that are displayed on the screen and output from integrated applications are logged in the netview_$LOGNAME.log file, where $LOGNAME is the UNIX or Linux login name of the user who started the Tivoli NetView program. By default, all Tivoli NetView log files are stored in the /usr/OV/log directory. When using the Tivoli Framework to start the Tivoli NetView program, you can specify an alternate location and log file name by editing the name of the log file in the Output file name field on the Start user interface dialog box. You can also change the option to log output by setting the value of the Log output field on the Start user interface dialog box to no or by starting the Tivoli NetView program using the netview -nl command. You might find this option useful if you are running applications that
48
Installation Guide
produce a large amount of data. This prevents the log file from increasing and consuming system resources. The -nl option is also useful if you have an application that writes real-time information to the stdout or stderr files, and you want to see the errors as they occur. For more information about some of the log file errors, refer to the IBM Tivoli NetView for UNIX and Linux Diagnosis Guide.
Accessing the online help

When the native console is started, you can use the online help to find task-specific information. To access the list of help topics available, click Help Help Topics from the Tivoli NetView native console. You can also access the online help by clicking Help in any Tivoli NetView dialog box.
Stopping the Tivoli NetView program

To stop the native console, select File Exit. The Exit menu option stops only the native console and does not stop the daemons. If you want the Tivoli NetView program to continuously monitor and track changes to your network and the management system, always keep the daemons running, even if the native console is not running. If you are performing multiprotocol management, the gtmd and noniptopod daemons should also be running. In addition, if you are using the Agent Policy Manager application (AIX system and Solaris environment only) the C5d daemon should be running. For more information about these daemons, refer to the man pages.
Starting the Server Setup application

The Server Setup application provides a menu-driven interface that you can use to manage a Tivoli NetView server. You can use the Server Setup application to perform the following tasks: v Customize the Tivoli NetView daemons v Monitor the status of the Tivoli NetView daemons and applications v Customize Tivoli NetView system files v Diagnose Tivoli NetView problems v Maintain the Tivoli NetView databases v Uninstall the Tivoli NetView program To start the Server Setup application, use one of the following methods: v From the command line, enter the following command:
/usr/OV/bin/serversetup
Note: If you have /usr/OV/bin as part of your PATH environment variable, enter the following command:
serversetup
Also ensure that your DISPLAY environment variable is set correctly. v From the Tivoli NetView native console, click Administer Server Setup. On a Tivoli NetView client, the Server Setup application prompts for a password on the server machine and runs remotely on the server machine. If a server has not been set up for the client, the Client Setup menus are displayed when you start the Server Setup application.
49
An open folder icon indicates an item that can be expanded, and a file icon indicates an action to be started. Click on a menu item to expand it or select it. Actions that require input data display an options dialog box before starting the action. To obtain context-sensitive help on a menu item or option field in the Server Setup application, follow these steps: 1. Click Help. 2. If you are in the main menu, click the On Context menu item. The cursor changes to a question mark (?). If you click Help in an options dialog box, the cursor changes directly to a question mark. 3. Click the menu item or option field for the help you want.
Starting the Client Setup application

The Client Setup application provides a menu-driven interface that lets you manage a Tivoli NetView client. You can use the Client Setup application to configure the server for this client, start the Tivoli NetView native console, and uninstall the client. To start the Client Setup application, use one of the following methods: v From the command line, enter the following command:
/usr/OV/bin/clientsetup
Note: If you have /usr/OV/bin as part of your PATH environment variable, enter clientsetup. v From the Tivoli NetView native console, click Administer Client Setup. An open folder icon indicates an item that can be expanded. A file icon indicates an action to be started. Click a menu item to expand it or select it. Actions that require input data display an options dialog box before starting the action. To obtain context-sensitive help on a menu item or option field in the Client Setup application, follow these steps: 1. Click Help. 2. If you are in the main menu, click the On Context menu item. The cursor changes to a question mark (?). If you click Help in an options dialog box, the cursor changes directly to a question mark. 3. Click the menu item or option field for the help you want.
Starting and stopping the daemons

You can start and stop the daemons using the command line or the Server Setup application. You must have root permissions to start or stop the daemons. You can start or stop all the Tivoli NetView daemons, or you can start or stop individual daemons. If you start the daemons individually, all prerequisite daemons are automatically started. Similarly, if you stop the daemons individually, all daemons that depend on the specified daemon are stopped.

To start all the daemons, use the /etc/netnmrc shell script for the AIX system or the /etc/init.d/netnmrc shell script for the Linux system and the Solaris environment,
50
Installation Guide
which starts the SNMP agent, the nettl facility (the network logging and tracing facility), if they are not running, and the daemons registered in the /usr/OV/conf/ovsuf startup file. The netnmrc shell script also sets the ulimit values in addition to starting the daemons. This process ensures that the Tivoli NetView program performs better and does not fail. If you are recycling one or two daemons that have previously been started correctly using the netnmrc shell script and the ovspmd process management daemon is running, you can use the /usr/OV/bin/ovstart command to restart the daemons. You should not use the ovstart command to start all the daemons because the environment will not be set correctly. To start and stop the daemons, use one of these methods: v To start all the daemons, enter one of the following commands: AIX system:
/etc/netnmrc
Linux system and Solaris environment:

/etc/init.d/netnmrc
v To individually start one or more daemons, enter the following command:

/usr/OV/bin/ovstart daemon_name1 daemon_name2 ...
Where daemon_name is the name of the daemon you want to start. For example, the following command starts the netmon daemon:
/usr/OV/bin/ovstart netmon
In general, the names that you use to start the daemons are obvious. The exceptions are listed in the following table.
Daemon name orsd ovelmd ovesmd Name to use with the ovstart command OVORS_M ems_log_agent ems_sieve_agent
The v option requests verbose mode of operation, which produces information about what is occurring during the startup process. Without the v option, the ovstart command reports only if a process fails to start. The v option is useful for diagnosing problems. For example, to start the netmon daemon with verbose mode, enter:
/usr/OV/bin/ovstart netmon -v
v To stop all the daemons, first stop the native console, Web consoles, and any other applications that use the daemons, and then enter the following command:
/usr/OV/bin/ovstop
The ovstop command stops all the daemons, except the nvsecd daemon and the ovspmd daemon. The nvsecd daemon must be running for the Tivoli NetView program to run (whether the security feature is on or off). The ovspmd daemon must be running if any of the other daemons are running (for example, nvsecd). If security is turned on and you stop the nvsecd daemon, all users are logged out. Therefore, limit stopping the nvsecd daemon to workstation shutdown or problem resolution situations. You can stop the nvsecd daemon individually. The ovspmd daemon stops when the last daemon has been stopped, which is usually the nvsecd daemon. Note: The ovstop command does not stop the nettl facility. To stop the nettl facility, enter the following command:
51
/usr/OV/bin/nettl -stop
For more information on the nettl facility, refer to the man page. v To individually stop one or more daemons, enter the following command:
/usr/OV/bin/ovstop daemon_name1 daemon_name2 ...
Where daemon_name is the name of the daemon you want to stop. For example, the following command stops the netmon and the ovtopmd daemons:
/usr/OV/bin/ovstop netmon ovtopmd

To restart Tivoli NetView daemons using the Server Setup application, follow these steps: 1. Enter /usr/OV/bin/serversetup on the command line to start the Server Setup application. 2. Do one of the following: v To start all the daemons, click Control Restart all stopped daemons, then click Close. v To start one or more specific daemons, click Control Select daemons to stop or restart, then go to step 3. v To stop all the daemons, click Control Stop all running daemons, then click Close. All daemons except the ovspmd and the nvsecd daemons are stopped. v To stop one or more specific daemons, click Control Select daemons to stop or restart, then go to step 3. 3. Select one of the following: v Topology, discovery, and database daemons to stop or restart v Event and trap processing daemons to stop or restart v SmartSet and Agent Policy Manager daemons to stop or restart v Web Server daemons to stop or restart A dialog box displays the names of the daemons. 4. Click Select next to the daemons that you want to start or stop, then select restart or Stop as appropriate. 5. Click OK. All selected daemons are restarted. 6. Click Close.
52
Installation Guide
Chapter 4. Uninstalling the Tivoli NetView program

This chapter describes how to uninstall the Tivoli NetView program. Uninstalling the Tivoli NetView program removes all Tivoli NetView directories and data, including the code for the language packs. To save the Tivoli NetView databases or any other customized data before uninstalling the program, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide.
Uninstalling a client
When you uninstall a client, the client code is removed from the client computer and the NFS mount connections are removed. AIX system: When you uninstall a client, the trapgend subagent is not removed. If you want to remove the trapgend subagent, you must do it separately. Refer to AIX system: Uninstalling the trapgend daemon on page 54. You must have root permissions to uninstall a client. If the client you are removing has local maps, delete those maps using the native console on the client before you remove the client code. For information about deleting maps on a client, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Guide. If you do not remove the local maps, the object database on the server will contain incorrect information about the number and the location of maps. To uninstall a client, follow these steps: 1. Enter /usr/OV/bin/serversetup from the command line to start the Server Setup application. 2. Click Configure Remove Server to remove the client access to the server. 3. Complete the Remove Server dialog box. Then click OK. 4. Click Maintain Deinstall Tivoli NetView Client. The Deinstall Tivoli NetView Client dialog is displayed. 5. Complete the Deinstall Tivoli NetView Client dialog box. Click OK. 6. Click OK on the verification message dialog box. 7. After the client has been uninstalled, close the Server Setup application.
Uninstalling a server
You can uninstall the server code and remove all Tivoli NetView directories and data by running the uninstnv script, which is located in the /usr/OV/service directory, or by using the Server Setup application. You must have root permissions to uninstall a server. To uninstall a server using the Server Setup application, follow these steps: 1. Exit the Tivoli NetView native console, Web consoles, and any clients or applications that use this server.
53
2. Enter /usr/OV/bin/serversetup from the command line to start the Server Setup application. 3. Click Maintain Deinstall Tivoli NetView. 4. Click either Deinstall Tivoli NetView (if no dependent products installed) or Deinstall Tivoli NetView (leave dependent products installed), depending on whether you want to uninstall Tivoli NetView even if there are dependent products installed. For more information about these options, refer to the online help. 5. Click OK on the verification message dialog box. 6. When the server has been uninstalled, close the Server Setup application. If you are using the DB2 product that is packaged with the Tivoli NetView program, uninstall the DB2 product in accordance with your license agreement. If you have a full license for the DB2 product, which you used for data collection with the SNMP Collector (nvcollectord), drop the SNMPDATA table if you want to recover space in your database. For information about uninstalling and administering the DB2 product, refer to the DB2 product documentation.
Uninstalling the Web console

To uninstall the Web console, use one of the following methods: v For Windows systems: If you installed the Web console using the nvwcinstall.exe executable file, use the Add or Remove Programs utility from the Control panel. If you installed the Web console using the nvwc_thin.zip file, manually remove the directory in which the Web console software is installed. v For UNIX and Linux systems: Run the /web_install_dir/nvwc/uninstall_nvwc command on the computer where the Web console is installed, where web_install_dir is the directory in which the Web console is installed.
AIX system: Uninstalling the trapgend daemon

You can uninstall the trapgend daemon from a remote node only if the Tivoli NetView server is not installed on the remote node. You must have root permissions to uninstall the trapgend daemon. To uninstall the trapgend daemon, follow these steps: 1. Enter /usr/OV/bin/serversetup from the command line to start the Server Setup application. 2. Click Configure Install/configure subagent (trapgend) on remote RISC System/6000. 3. Select Remove subagent in the Remote Operation field. 4. Complete the dialog box. Click OK.
Uninstalling the Mid-Level Manager

For information about how to uninstall the Mid-Level Manager, refer to the Tivoli NetView Mid-Level Manager Users Guide.
54
Installation Guide
Chapter 5. Troubleshooting common installation problems

This section describes miscellaneous installation problems and problems that might occur when installing the language packs.
Solaris 10 systems: Error message when configuring the DB2 database

When installing the Tivoli NetView program on Solaris 10 systems with the -U option of the instalnv script to specify the SNMPv1/v2 SNMP Collector (nvcollectord), the following message is received when the installation process configures the DB2 database for the SNMPDATA table:
SQL1478W The defined buffer pools could not be started. Instead, one small buffer pool for each page size support by DB2 has been started. SQLSTATE=01626
You can ignore this message.
Solaris and Linux systems: Too many open semaphores

When installing the Tivoli NetView program on Solaris or Linux systems, too many open semaphores can cause problems. One symptom of too many open semaphores can be the following message that is displayed at the start of the Tivoli NetView configuration process during installation:
Initializing the Tracing and Logging... base: Failure starting nettl tracing and logging ERR_bcfg_200 base: Failing base.config with exit code 2
To avoid problems caused by too many open semaphores, reboot the computer as recommended before installing the Tivoli NetView program or you can use the ipcs and ipcrm operating system commands.
Community name changes

Community name changes can cause problems after you install the Tivoli NetView program. To correct this situation, use the xnmsnmpconf application to enter the correct community name for the global setting as well as for 127.0.0.1. To do this, enter the following command:
/usr/OV/bin/xnmsnmpconf
Cannot communicate with local SNMP agent

During the installation, the community name of the local SNMP agent is extracted. If the extraction is successful, the community name is inserted into the ovsnmp configuration file and used as the local host address (127.0.0.1). When the netmon daemon starts, a query is made to the local SNMP agent. The community name used in the query is obtained from the ovsnmp configuration file. If the query fails, the netmon daemon fails with the following message:
Can't talk to snmpd; see netmon.trace for info Cannot communicate with the local SNMP agent. See /usr/OV/log/netmon.trace for information.
55
The netmon.trace file shows additional details for this message: Cannot communicate with the SNMP agent through loopback address 127.0.0.1. The agent is either not running or has been configured with a community name which is different from that configured in the Tivoli NetView program for this system. If a community name has been configured for the SNMP agent, that community name must be configured for address 127.0.0.1. To do this, from the native console, use the Options SNMP Configuration menu option or the xnmsnmpconf command. It must also be configured as the host name or IP address of this system. Or, the /usr/OV/conf/snmpmib and /usr/OV/conf/snmpmib.bin files are corrupted and need to be rebuilt using the option Maintain Rebuild MIB binary file with default MIB set in the Tivoli NetView Server Setup application. For more information about the xnmsnmpconf command, refer to the IBM Tivoli NetView for UNIX and Linux Administrators Reference. For more information about the Server Setup application, see Starting the Server Setup application on page 49.
Error messages in the tdwdaemon.log file

During the installation, the following message is written multiple times in the /usr/OV/log/tdwdaemon.log file:
timestamp [main] ERROR com/tivoli.netviw.tdw.DbHelper TDW Daemon encountered an error opening a connection to the database.java.sql.SQLException: No suitable driver java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnectoin(DriverManager.java:563) . . . at com.tivoli.netview.tdw.TDW_Daemon.main(TDW_Daemon.java:72) timestamp [main] ERROR com.tivoli.netview.tdw.DbHelper TDW Daemon is shutting down because it cannot connect to the database. Check database connectivity.
You can ignore this message. However, if this message is written to the /usr/OV/tdwdaemon.log file at any time after installation, a problem exists that must be corrected.
The netviewd daemon does not start

If you have trouble starting the netviewd daemon, follow these steps: 1. Stop the Xvfb process using the kill command. 2. Run the following command to restart the Xvfb process:
/usr/OV/bin/startXvfb
If the problem persists, check the /usr/OV/log/netview_daemon.log file. If the local host name entry for the Tivoli NetView server (the name in the /etc/hosts file) does not match what the domain nameserver (DNS) provides as the host name, the netviewd daemon might have a problem starting. The following message displays in the /usr/OV/log/netview_daemon.log file:
Couldn't open display
To avoid this problem, ensure that the local host name in the /etc/hosts file matches the host name provided by DNS. The /etc/hosts file must include both the fully qualified host name and the local host name on the line that specifies the IP address of the host. An entry in the /etc/hosts file must be similar to the following example:
56
Installation Guide
123.45.67.89 myhost.local.domain.com myhost
In this example, myhost is the local host name.
For non-English language systems: If Tivoli NetView applications or Web consoles display in the English language
Programmer commands and functions, advanced administrative tasks, information primarily used by IBM Software Support for problem diagnosis, and SNMP data (which is by its nature English only) are not translated or enabled. The following information is not translated in the Tivoli NetView program: v Installations for the Tivoli NetView base program and language packs v API definitions, man pages, command line utilities, and program samples v Advanced administrative tasks v Copyright screen and online help for the Mid-Level Manager Configuration application v The default role names in Web console security v Information that is used primarily by IBM Software Support for diagnosis v SNMP data v Database field names and enumerated values v Map, submap, and snapshot names v MIB Object names, descriptions, and enumerated values v SmartSet names and descriptions Symbol class and subclass names and status values Trap names Event information Event source, event attributes, and agent values Administrative support scripts used by the Server Setup and the Client Setup applications and SMIT v Tivoli NetView configuration menus in the Tivoli Management Framework v Files in the /usr/OV/conf/$LANG directory, except for explore.conf v Tracing and logging messages, with the exception of some messages in the /usr/OV/log/netview_user.log file v v v v v In addition, applications that run on the server and that are displayed on the client, such as the SNMP Configuration window, display in the English language. If you experience problems displaying Tivoli NetView applications in your language (other than those that have been described), follow these steps to solve the problem: 1. Stop all Tivoli NetView graphic applications on the server and any clients. 2. Ensure that the following environment variables are set correctly in your current session and for the root user on both the Tivoli NetView server and client: v NLSPATH This environment variable must contain the following string before any language-specific directories or CAT files:
/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%n.cat
57
v XUSERFILESEARCHPATH This environment variable must contain the following string:

/usr/lib/X11/%L/app-defaults/%N:/usr/lib/X11/app-defaults/ %L/%N/usr/lib/X11/app-defaults/%
v LANG and LC_ALL These environment variables must be set to the correct code set as described in Enabling language support on page 40, Use the locale command to display the current values. The following system files can affect variable settings for all users: v /etc/profile v /usr/OV/bin/NVenvironment v AIX system: /etc/environment v Solaris environment: Files in the /etc/default directory The settings for the NLSPATH and the XUSERFILESEARCHPATH environment variables can become very large if you have scripts running in your shell that are continuously appending to the existing path statement. If this occurs, these variables might become unusable by the shell, causing the text in applications to be displayed in the English language. If you notice that either of these variables has an extremely long path list with duplicates, reset the variable to eliminate duplicate entries. Also, run the scripts in your .profile or .login file instead of your .kshrc or .cshrc script. 3. Check that the system environment is set correctly on the Tivoli NetView server and client. v AIX system: Ensure that the cultural connection, language, and keyboard are set to the correct code set using the Manage Language Environment Show Primary Language Environment option in SMIT. v Solaris environment: Ensure that the LANG and the LC_ALL environment variables are set to the correct code set in the /etc/defaults/init and /etc/TIMEZONE files. 4. If you made any changes in step 2 on page 57 or step 3, start the computer so the changes take effect. If the problem is not resolved after performing these steps, you might be inadvertently starting the Tivoli NetView daemons in the English locale by using the Tivoli Management Framework to stop and start the daemons, or you might be performing other administrative tasks that restart the daemons. The Server Setup application is the recommended method of restarting the daemons and other administrative tasks. To determine if the daemons are starting in the English language, run the following command:
ovstatus nvsecd
If the last message field for the nvsecd daemon is displayed in the English language, then the daemons are starting in the English language. To restart the daemons in the correct locale, follow these steps: 1. AIX system only:, enter the following sequence of commands to stop and restart the inetd daemon:
stopsrc -s inetd startsrc -s inetd
2. Enter the following sequence of commands to stop and then restart the daemons:
58
Installation Guide
/usr/OV/bin/ovstop nvsecd /etc/netnmrc (AIX system) /etc/init.d/netnmrc (Linux system and Solaris environment)
59
60
Installation Guide
Appendix A. Hardware, memory, and tuning recommendations

This appendix provides information to help you determine the hardware and memory requirements for the system on which the Tivoli NetView server will be installed, and it provides tuning recommendations to help you maximize your system performance. The recommendations in this appendix were derived under ideal laboratory conditions. Therefore, use this information as a general guideline. The following assumptions are used to determine the hardware recommendations in this appendix: v The Tivoli NetView program is the single major application running on the system. v One local operator is logged on. A local operator is an operator that is logged on to the Tivoli NetView server using the console for that system. To support a local console on the Tivoli NetView server, a graphics adapter (either a graphics card or a graphics adapter that is integrated into the system board) must be installed on the Tivoli NetView server. v No customized scripts are running. v The system response time is excellent, for example, the response time for a ping is 10 - 20 milliseconds. v The domain name system (DNS) response time must be excellent. Because hardware and tuning requirements depend on the size of the network that you are managing, first determine the size of your network as described in Determining the size of your network. Then see Hardware and tuning recommendations on page 63 for hardware and tuning recommendations for your particular network size.
Determining the size of your network

After using the information in Table 11 on page 62 to determine if your network is categorized as a small, medium, large, or very large network, see Hardware and tuning recommendations on page 63 for hardware and tuning recommendations.
61
Table 11. Guidelines to help you determine the size of your network Network size Small Description Managed interfaces Layer 2 devices Web consoles X operators
1
Amount 10 000 or fewer 100 - 300 1-5 1 v The default status monitoring interval of 5 minutes is used for all managed resources located on the local area network (LAN).2 v Limited SNMP data collection is being performed. v The Tivoli NetView program is communicating with another program for event management, such as the Tivoli Enterprise Console program. Tivoli NetView program and Tivoli Switch Analyzer are deployed on a single server. v The trap rate is limited to a few traps per minute. v The default port status monitoring for Tivoli Switch Analyzer is used.
Average system workload
Medium
Managed interfaces Layer 2 devices Web consoles X operators

1
10 001 - 24 999 3 000 10 - 20 1-2 v The default ICMP status monitoring interval (5 minutes) is used for all managed resources.2 v Some SNMP data collection is being collected at 10 - 15 minute intervals. v The Tivoli NetView program is communicating with another program for event management, such as the Tivoli Enterprise Console program. v The trap rate is 10 traps per minute with some bursts of 10 or more traps per second.
Large
Managed interfaces Layer 2 devices Web consoles X operators

1
25 000 - 49 999 3 000 10 - 15 1 or more v The default status monitoring interval of 5 minutes is used for some managed resources.2 Two or more status polling intervals might be used, such as 5 minute intervals for LAN-attached devices and 15 minutes for remote, WAN-attached sites. SNMP status monitoring might be used for some of the resources. v SNMP data is being collected at 10 - 15 minute intervals, typically 3 - 5 MIB variables from 5 000 nodes. v The Tivoli NetView program is communicating with another program for event management, such as the Tivoli Enterprise Console program, and the environment includes Tivoli Switch Analyzer. v The trap rate is 1 - 2 traps per second with some bursts of more than 10 traps per second.
62
Installation Guide
Table 11. Guidelines to help you determine the size of your network (continued) Network size Very large Description Managed interfaces Local operators Web consoles X operators
1
Amount More than 50 000 1 10 - 30 3-4 v The default status monitoring interval of 5 minutes cannot be used. Specific analysis of the network determines the best rate possible.2 v SNMP data is being collected at 15 - 30 minute intervals for key router interfaces. v The Tivoli NetView program is communicating with another program for event management, such as the Tivoli Enterprise Console program. v The trap rate is 1 - 5 traps per second with some bursts of more than 10 traps per second. v Mid-level managers might be present in the environment and managing about 3 000 interfaces for status monitoring and 300 resources for SNMP data collection. v Different networks with varying response times are being monitored.
X operators use an X emulation session to connect directly to either the Tivoli NetView server or a Tivoli client system.
2
You must consider many factors when you establish the status monitor rates that you use, such as:
v Network response time v Number of interfaces that might be down at the same time v Whether a wide area network (WAN) connection is being used
Hardware and tuning recommendations

The section describes hardware and tuning recommendations for different size networks. Refer to the section that corresponds to the size of your network.
Recommendations for a small network

Table 12 describes hardware and tuning recommendations for a small network.
Table 12. Hardware and tuning recommendations for a small network Category Class of system
1
Recommendations A one or two-processor system with 512 - 1024 MB of memory, 18 GB disk drive, 100 MB Ethernet connection, and an appropriate video card. If you plan to use Tivoli Switch Analyzer with the Tivoli NetView program, plan for 1 - 1.5 GB memory. Example systems: v For AIX environments: IBM pSeries 7044-170 with single 333 MHz processors. v For Windows and Linux environments: IBM xSeries 345 with two 2.4 GHz processors or xSeries 346 with two 3.6 GHz processors.
63
Table 12. Hardware and tuning recommendations for a small network (continued) Category Memory requirements Recommendations The Tivoli NetView memory requirement for 5 000 interfaces is 216 370 MB. For a single X Client, several Web clients, routine Tivoli NetView functions and Tivoli Switch Analyzer, 1.5 GB is adequate. Each additional X client requires 20 - 30 MB. The Tivoli NetView database (by default, the /usr/OV/databases directory) requires 50 MB of disk space. This requirement does not include disk space required for tracing the Tivoli NetView daemons. v Discovery of a layer 3 network consisting of 2 000 interfaces requires about 22 MB. v Discovery of a layer 2 network consisting of 300 switches requires about 23 MB, depending on the number of switches that are discovered. v Activation of a Web console session for a layer 3 network consisting of 2 000 interfaces, requires about 49 KB. v Discovery of a layer 3 network consisting of 2 000 interfaces and 100 layer 2 devices takes 4 - 12 minutes, depending on the class of the system. Tuning Use the default status monitoring interval (5 minutes) and the Tivoli NetView default configuration with the following exceptions: v Set the ovwdb cache size to be slightly larger than the number of objects in the database. v When managing network devices that are attached to slow network connections, carefully monitor the ping queue. Use the netmon -a 11 command to dump the pingWait list and the netmon -a 12 command to dump the pingList list. Use ICMP for status monitoring. v Use a seed file for discovery.
1
Disk space requirements Network bandwidth and response time examples
Two processors are recommended if you are managing 4 000 or more interfaces.
Recommendations for a medium network

Table 13 describes hardware and tuning recommendations for a medium network.
Table 13. Hardware and tuning recommendations for a medium network Category Class of system
1
Recommendations A two or four-processor system with 2 GB of memory, one or two disk drives, 100 MB Ethernet connection, and an appropriate video card. Example systems: v For AIX environments: IBM pSeries 7028 or pSeries 550 with four processors at 1.45 - 1.6 GHz. v For Windows and Linux environments: IBM xSeries 365 with four processors at 3.0 GHz or xSeries 366 with four processors at 3.6 GHz.
Memory requirements
The Tivoli NetView memory requirement ranges from 370 - 670 MB, assuming one X operator. Each additional X operator requires 50 MB. For routine Tivoli NetView functions and Tivoli Switch Analyzer, 2.5 GB is adequate.
64
Installation Guide
Table 13. Hardware and tuning recommendations for a medium network (continued) Category Disk space requirements Recommendations The Tivoli NetView database (by default, the /usr/OV/databases directory) requires 215 MB or more of disk space. This requirement does not include disk space required for tracing the Tivoli NetView daemons. v Discovery of a layer 2 network consisting of 2 000 switches requires about 152 MB, depending on the number of switches discovered. v Activation of a Web console session for a layer 3 network consisting of 20 000 interfaces, requires about 2.5 MB for the exchange between the Tivoli NetView server and each client. v Discovery of a layer 3 network consisting of 25 000 interfaces takes 60 minutes and several hours to complete discovery of a layer 2 network consisting of 3 000 switches. Tuning v Configure the size of the ovwdb cache to be slightly larger than the number of objects in the database. v Use the netmon -q 32 option to set the queue size for ICMP pings and the -Q 32 option to set the queue size for SNMP pings. v Set the status monitor intervals from 5 - 10 minutes. Consider the following factors when you set this value: Processor speed Network response times netmon ping queue size Use the netmon -a 11 command to dump the pingWait list and the netmon -a 12 command to dump the pingList list. Switch to SNMP for status monitoring with careful monitoring of performance metrics with staged introduction of workload. v Increase the value of the Xmx variable in the /usr/OV/www/bin/ jetty.sh file from 64 MB to 256 MB. v Use a seed file for discovery. v Monitor the performance of the system, Tivoli NetView logs, and network to evaluate and tune the system.
1
Network bandwidth and response time examples2
Two processors are recommended if you are managing 12 000 or fewer interfaces. Four processors are recommended if you are managing more than 12 000 interfaces.
2
Discovery response time is highly dependent on the processor speed, number of processors, network response times, number of layer 2 devices, and so forth.
Recommendations for a large network

Table 14 on page 66 describes hardware and tuning recommendations for a large network.
65
Table 14. Hardware and tuning recommendations for a large network Category Class of system Recommendations A four-processor system with 2 - 4 GB of memory, two disk drives of 36 GB or greater, 100 MB Ethernet connection or better, and an appropriate video card to support 1280 x 1024 pixels with thousands of colors. It is a best practice to dedicate this system to the Tivoli NetView server with no other major applications other than Tivoli Switch Analyzer. Generally, it is also a best practice to use an AIX server in this environment. Example systems: v For AIX environments: IBM pSeries 7028 or pSeries 550 with four processors at 1.45 - 1.6 GHz. v Linux environments: IBM xSeries 365 with four processors at 3.0 GHz. Memory requirements The Tivoli NetView memory requirement ranges from 370 - 670 GB, assuming one X operator. Each additional X operator requires 90 100 MB. For routine Tivoli NetView functions and Tivoli Switch Analyzer, 2.5 GB is adequate. For Windows Web consoles, a minimum of 512 MB is required. The Tivoli NetView database (by default, the /usr/OV/databases directory) requires 215 MB or more of disk space. This requirement does not include disk space required for tracing the Tivoli NetView daemons. v Discovery of a layer 2 network consisting of 2 000 switches requires about 152 MB, depending on the number of switches discovered. v Activation of a Web console session for a layer 3 network consisting of 20 000 interfaces, requires about 5 MB for the exchange between the Tivoli NetView server and each client. v Discovery of a layer 3 network consisting of 45 000 interfaces takes 100 - 180 minutes and many hours to complete discovery of a layer 2 network consisting of more than 3 000 switches.
Disk space requirements
Network bandwidth and response time examples1
66
Installation Guide
Table 14. Hardware and tuning recommendations for a large network (continued) Category Tuning Recommendations v Set the status monitor intervals in the range of 5 - 10 minutes. Consider the following factors when you set this value: Processor speed Network response times netmon ping queue size Presence of mid-level managers When managing network devices attached to slow network connections, carefully monitor the ping queue. Use the netmon -a 11 command to dump the pingWait list and the netmon -a 12 command to dump the pingList list. Switching to SNMP status monitoring is more costly. v Configure the size of the ovwdb cache to be slightly larger than the number of objects in the database. v Use the netmon -q 32 option to set the queue size for ICMP pings and the -Q 32 option to set the queue size for SNMP pings. v Increase the value of the Xmx variable in the /usr/OV/www/bin/ jetty.sh file from 64 MB to 256 MB. v Consider using MLMs for status monitoring in locations with slow responding network resources (ICMP response time in the hundreds of milliseconds) and for managing resources for SNMP collection. v If you are using the Tivoli Enterprise Console product to manage events, turn off the Events application on the main X-operator session to reduce system usage on the Tivoli NetView server. v To address concerns for trap rates, filter traps that are sent to the Tivoli Enterprise Console server. v Schedule workloads, such as discovery of the layer 3 network, discovery of the layer 2 network, synchronization, and so forth for off-shift time periods. v Monitor the performance of the system, Tivoli NetView logs, and network to evaluate and tune the system.
Recommendations for a very large network

Table 15 describes hardware and tuning recommendations for a very large network.
Table 15. Hardware and tuning recommendations for a very large network Category Class of system Recommendations A four or more processor system with 4 - 6 GB of memory or greater, multiple disk drives, 1 GB Ethernet connection, and an appropriate video card. The Tivoli NetView memory requirement ranges from 1.2 - 3 GB, assuming one X operator. Each additional X operator requires 160 MB or greater. For routine Tivoli NetView functions and Tivoli Switch Analyzer, 4 - 6 GB is adequate. For Windows Web consoles, a minimum of 1024 MB is recommended. The Tivoli NetView database (by default, the /usr/OV/databases directory) requires 400 MB or more of disk space. This requirement does not include disk space required for tracing the Tivoli NetView daemons.
Memory requirements
Disk space requirements
67
Table 15. Hardware and tuning recommendations for a very large network (continued) Category Tuning Recommendations v Set the status monitor intervals in the range of 10 - 15 minutes. Consider the following factors when you set this value: Processor speed Network response times netmon ping queue size Presence of mid-level managers v Carefully monitor the use of X operators to avoid memory shortages. v Configure the size of the ovwdb cache to be slightly larger than the number of objects in the database. v Use the netmon -q 32 option to set the queue size for ICMP pings and the -Q 32 option to set the queue size for SNMP pings. v Determine whether you need to change the value of the Xmx variable in the /usr/OV/www/bin/jetty.sh file from 64 MB to 128 MB. v Monitor the performance of the system, Tivoli NetView logs, and network to evaluate and tune the system.
68
Installation Guide
Appendix B. Installation entries

The installation procedure adds the following entries for Tivoli NetView processes to the following files. Do not change these entries.
Table 16. Installation entries Entry /etc/netnmrc (for AIX systems) /etc/init.d/netnmrc (for Solaris and Linux systems) actionsvr C5_server cmot_manager cmot_manager cmot_agent cmot_agent gtmd 1670/tcp 1668/tcp 163/tcp 163/udp 164/tcp 164/udp 2112/tcp actionsvr C5d pmd pmd pmd pmd gtmd mgragentd mgragentd nvcold nvcollectord nvcorrd nvlockd nvpagerd nvpollerd nvsecd nvsecltd trapd trapd trapd otmd ovtopmd ovwdb pmd mgragentd TCP/IP Agent Tivoli NetView SNMP Server trapgend /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/snmpd.peer (AIX system only) etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/services /etc/snmpd.conf (AIX system only) /etc/services /etc/services /etc/snmpd.conf (AIX system only) Process Background daemons File /etc/inittab
mgragentd 1.3.6.1.4.1.2.6.4.6 nv6000 mgragentd nvcold nvcollectord nvcorrd nvlockd nvpagerd nvpollerd nvsecd nvsecltd nvtrapd-trap nvtrapd-trap nvtrapd-client otmd ovtopmd ovwdb pmd 1670/udp 1664/tcp 18892/tcp 1666/tcp 1669/tcp 1671/tcp 18893/tcp 1663/tcp 1667/tcp 162/tcp 162/udp 1661/tcp 1672/tcp 8888/tcp 9999/tcp 2113/tcp
smux 1.3.6.1.4.1.2.6.4.6 nv6000 snmp snmpserver 161/udp 1673/tcp
smux 1.3.6.1.4.1.2.6.4.1 nv6000
69
Table 16. Installation entries (continued) Entry tdwdaemon 1674/tcp Process File
Tivoli NetView and Tivoli /etc/services Data Warehouse daemon socket communication Tivoli NetView and Tivoli /etc/services Data Warehouse daemon netmon communication trapgend gtmd /etc/snmpd.peers (AIX system only) /etc/services
tdwnetmon
1675/tcp
trapgend 1.3.6.1.4.1.2.6.4.1 nv6000 xxmd 3113/tcp
70
Installation Guide
Appendix C. Files that are migrated during an upgrade installation

If you are upgrading to 7.1.5 or if you are reinstalling 7.1.5, the /usr/OV/ALL category of files is migrated by default. You can also selectively backup any of the categories of files listed in Table 17 at any time using the Server Setup application. Although it is not recommended, if you back up your customized data manually prior to upgrading, make sure that you select the /usr/OV/ALL category.
Table 17. File that are migrated during an upgrade installation Directory /usr/OV/ALL File Category All categories. This includes all the categories listed in this section. Use this category if you want to migrate all data. /usr/OV/ALL.USER All user-defined categories. This includes all the categories listed in this section except the categories that have the .USER extension, only the user-defined categories are migrated. For example, there are two categories for MIBs: /usr/OV/snmp_mibs and /usr/OV/snmp_mibs.USER. The .USER file contains the user-defined MIBs. If you select /usr/OV/ALL.USER, the /usr/OV/snmp_mibs.USER category is migrated, but the /usr/OV/snmp_mibs category is not. /usr/OV/app-defaults Application default files. This includes all product-defined X-Default files. /usr/OV/backgrounds All background files. This includes all product-defined and user-added backgrounds and backgrounds added by other integrated applications. /usr/OV/backgrounds.USER User background files. This includes all the background files not originally installed with Tivoli NetView. This category is a subset of the /usr/OV/background category. /usr/OV/bin.USER User bin files. This includes all the scripts or executable files that were not originally installed with Tivoli NetView. /usr/OV/bitmaps All bitmap files. This includes all product-defined and user-added bitmaps and bitmaps added by other integrated applications. /usr/OV/bitmaps.USER User bitmap files. This includes all the bitmap files not originally installed with Tivoli NetView. This category is a subset of the /usr/OV/bitmaps category.
71
Table 17. File that are migrated during an upgrade installation (continued) Directory /usr/OV/conf (Server only) File Category Configuration files. This includes the following configuration files: v All .properties files, except for log4j properties files v The backup manager seed file v C/explore.conf v C/if_to_sym v C/oid_to_sym v C/nnm_to_ovw v C/trapd.conf v communityNames.conf v dbconf.dat v emstest.src v ESE.automation v HPoid2type v itm_attributes.conf v itm_servers.conf v location.conf v mib.coerce v mib.odi v mib2.def v mibExpr.conf v mnpcodes.desc v mnpcodes.desc.undo v nc.seed v netmon.conf v netmon.seed v nv.carriers v nvpager.config v nvpager.warm v nvpaging.protocols v nvsniffer.conf v oid_to_command v oid_to_label v oid_to_protocol v oid_to_type v ovevent.db v ovevent.dest v ovors v ovsnmp.conf v ovsuf v rdb_tracemask v All .rs files in the rulesets directory v The server clients list v service_polling.conf v servmon.conf v snmpCol.conf v snmpColFiles v snmpmib v snmpmib.bin v tecint.conf v The user-defined .modem files v xmpcfg.dat /usr/OV/cron Cron files. This includes all cron job scripts or cron job information. The active list of /usr/OV/crontab entries is saved in this directory.
72
Installation Guide
Table 17. File that are migrated during an upgrade installation (continued) Directory /usr/OV/databases/openview File Category Topology map database. This includes the ovwdb, mapdb, and topology databases. Server only. /usr/OV/databases/snmpCollect SNMP collection data. This includes all data that the snmpCollect daemon gathers. The snmpCollect task definitions are stored in the /usr/OV/conf/ snmpCol.conf file, which is migrated only if you select the /usr/OV/conf file category. Server only. /usr/OV/fields Field registration files. This includes all product-defined and user-added field registration files (FRFs) and FRFs added by other integrated applications, except for the snmp_fields file. The snmp_fields file is not migrated. Server only. /usr/OV/filters Filter files. This includes all product-defined and user-added filters and filters added by other integrated applications. /usr/OV/help Help files. This includes product-defined MIB application and user-added help files, and help files added by other integrated applications. /usr/OV/icons All icon files. This includes all product-defined and user-added icon definition files and icon definition files added by other integrated applications. /usr/OV/icons.USER User icon files. This includes all the icon definition files not originally installed with Tivoli NetView. This category is a subset of the /usr/OV/icons category. /usr/OV/lrf Local registration files. This includes all product-defined and user-added local registration files (LRFs) and LRFs added by other integrated applications, except for servmon.lrf, nvexportd.lrf, snmpserver.lrf, tdwdaemon.lrf, and webserver.lrf. Server only. /usr/OV/registration Application registration files. This includes all product-defined application registration files, user-added application registration files (ARFs), and all ARFs added by other integrated applications. /usr/OV/reports Report files. This includes all product-defined and user-added reports and reports added by other integrated applications. /usr/OV/security Security files. This includes all security configuration files, product-defined and user-added security registration files (SRFs), and SRFs added by other integrated applications. Server only.
Appendix C. Files that are migrated during an upgrade installation
73
Table 17. File that are migrated during an upgrade installation (continued) Directory /usr/OV/servers/Servername/databases File Category Map database. Client only. /usr/OV/snmp_mibs All loadable MIB files. This includes all product-defined and user-added MIB files and MIBs added by other integrated applications. Server only. /usr/OV/snmp_mibs.USER User loadable MIB files. This includes all the MIB files that were not originally installed with Tivoli NetView. This category is a subset of the /usr/OV/snmp_mibs category. Server only. /usr/OV/symbols Symbol type registration files. This includes all product-defined and user-added symbol type registration files (STRFs) and STRFs added by other integrated applications. The following files are included in the /usr/OV/ALL and the /usr/OV/ALL.USER categories and migrated by default. v The servmon and CNAT databases (/usr/OV/databases/servmon and /usr/OV/databases/CNAT) v The ITSL2 directory (/usr/OV/ITSL2) v The following files in the /usr/OV/www directory: webapps/netview/WEB-INF/web.xml All files in the conf directory, except jetty.xml, buildtimestamp.txt, and all DTD files. All user-added files in the mibs directory (that are not in the base installation) mibs/mibserver.def All files in the webapps/netview/properties directory, except global.prp All files in the webapps/netview/warf directory, except all XSL and DTD files All user-added files in the webapps/netview/warf/Templates directory (that are not in the base installation
74
Installation Guide
Appendix D. AIX system and Solaris environment: Tuning the NDBM Databases
By default, the NDBM databases are tuned to optimize for space. Under regular operating conditions, you do not need to tune the NDBM databases. You might need to further tune the NDBM databases for the following reasons: v Slow response v Excessive ovwdb processor time v Unacceptable netmon and ovtopmd performance Important: Tune the NDBM databases using the utilities described in this Appendix only with the advice and guidance of IBM Software Support.
NDBM component overview

Each of the three main Tivoli NetView databases is a collection of several NDBM databases. NBDM is an expandable keyed hash table with the data residing on the disk. Each NDBM database is comprised of two files: v A directory file v A page file The directory file has an extension of .dir and contains information that NDBM uses to index into the page file. The page file actually contains the key and the data. The file is divided into pages where the data (key and value) is stored. The page number is calculated from the key and the bits in the directory file. Each page is currently 8 KB long. Two optional files are defined for each NDBM database: v A config file v An overflow file The config file contains parameters for NDBM and determines what new functions are applied to this database. The file is created by the dbmcompress utility and is not intended to be modified in an editor. If the config file does not exist, NDBM uses defaults that match the old NDBM processing, so that, even with the new code, existing databases continue to work as usual. The overflow file contains data for large values. This enables data larger than 8 KB to be stored in the database. These files provide the following capabilities: v Large values can be written to the overflow file rather than the page file. This has two benefits. First, values larger than 8 KB can be stored in the database. Second, it greatly reduces the sparse filesystem problem. v New hashing algorithms exist to help group related data items into the same area of the disk. This can reduce disk writes for database updates. v A new option to start permanently buffering database updates can reduce both disk read and writes. For some databases, buffering provides a significant performance boost only when combined with the new hashing algorithms.
75
v If the NV6K_NDBM_DEBUG environment variable is turned on, all database activity is logged to a TRC file. This is useful for debugging and occasionally for tuning. v With the dbmcompress utility, some database problems can be corrected. This utility cannot resolve inconsistencies between databases, but it can remove NULL values and inaccessible data from an individual NDBM database.
NDBM utilities
To tune the NDBM database, NDBM provides the following utilities: v dbmcompress v dbmlist v nvTurboDatabase These utilities reside in the /usr/OV/service directory.
The dbmcompress utility

The dbmcompress utility compresses an individual NDBM database. Because it compresses one database at a low level, it can complete its compression much faster than older database compression utilities. Compressing the value_info achieves most of the benefits of the ovwdbdmap -c command in about one-fifth the time. The dbmcompress utility is also used to transform databases. The transformation creates a config file and a database based on command line options to dbmcompress. The dbmcompress command has the following syntax:
dbmcompress [-o -s -a -h d|o|n|r -m -b -v ] databasename
o s n a n
Causes the new database to use an overflow file for large items Overflows objects larger than n Appends items in the overflow until file size reaches n
h d|o|n|r Determines the hashing algorithm for the new database, where d=default, o=group by oid, n=group by name, r=group by oid (method 2) m n b n v Allows the hashing to optimize for n megabytes of data for hashing algorithms other than d Causes the database to always buffer n pages Indicates verbose mode
The dbmlist utility

The dbmlist utility collects important information such as the configuration of a database, the count of items in the database, and the total size of the database. The syntax for the dbmlist command is:
dbmlist [-belcnsSh -i val -j val] databasename
b e l c
Prints block information Prints empty blocks Prints sizes of keys and values Counts the objects
76
Installation Guide
n s S h i val
Does not print the object data Prints the total size of the data and keys Suppresses database error messages Prints the key in hexadecimal Prints only keys where the first word matches val
j val Prints only keys where the second word matches val
The nvTurboDatabase utility

The nvTurboDatabase utility processes all appropriate database files and runs the dbmcompress utility to transform and compress the databases. Because some NDBM database files must trade off between speed and database size, this script has a parameter that you can use to optimize for either speed or space. Prior to compressing the databases, the nvTurboDatabase utility backs up the current database files and stores them in the /usr/OV/databases/openview directory. Before running the nvTurboDatabase utility, make sure that adequate space exists in the usr/OV directory to store the backed up files. To calculate the size of the current database, run the following command:
du -rsk /usr/OV/databases/openview
The syntax for the nvTurboDatabase command is:

nvTurboDatabase [ speed | space ]
Implementing database improvements

To implement database improvements, consider the following information: v Improving the performance of the NDBM databases v Migration options on page 78 v Possible migration strategies on page 78
Improving the performance of the NDBM databases

Before describing strategies for implementing NDBM performance tuning, it is important to improve the operation of the key NDBM databases:
Table 18. Methods for improving the performance of the NDBM databases Database nodeinfo ifinfo Methods to improve performance The netmon and the topology daemons generally update a node and interface twice during such operations as configuration checking. Buffering can reduce the number of disk writes by about 50 percent The count fields are the most often updated fields in these databases. Buffering these fields with a small number of buffers reduces unnecessary disk I/O.
topoinfo netifno segnifo
77
Table 18. Methods for improving the performance of the NDBM databases (continued) Database obj_info Methods to improve performance Hashing -d o helps group the data for one object into the same page. Buffering with a count of two should also be used here to fully realize the benefit of grouping the object data. Two problems are addressed with these changes: 1. The sparse file problems. The solution is to use an overflow file. 2. Performance The default hashing algorithm places the different fields for any given object into several different areas (pages) of the PAG file. Performance is greatly improved if the hashing is changed to o. -h o hashing tries to keep the fields for an object together in a small group of pages. When combined with buffering, this produces significant savings in ovwdb performance. The buffering count should be set to at least 3, ( that is, -b 3 ). name_inf This database has a problem of storing different names for any given object in different pages. -d n hashing tries to group the names for an object into the same page. This must also be used with buffering but a buffer value of 1 or 2 should be sufficient. This database benefits from -h o hashing because symbols tend to be updated in groups with similar oids. Buffering with a count of 2 also helps this database run faster. Buffering helps this database to run faster.
syminfo
objinfo
Migration options
You might want to pursue one of the following migration options with regard to NDBM performance tuning: 1. Remain with traditional NDBM processing. No migration steps are required. 2. Move from traditional NDBM processing to enhanced NDBM processing This can be done on an individual database basis. For example, you could use traditional NDBM processing for all databases but for value_info, and use an overflow file for it. To migrate, run the dbmcompress utility, setting the appropriate tuning options. 3. Move from enhanced NDBM processing back to traditional NDBM processing To do this, run the dbmcompress utility on a database without specifying any options.
Possible migration strategies

Before implementing NDBM performance tuning in a production environment, ensure that you have procedures for regular backups in place. When making backup copies with NetView utilities, move the BAK files out of the /usr/OV/databases directory. Then, consider the following strategies: 1. Minimize space: Run the nvTurboDatabase space command to limit sparse file system problems. 2. Maximize performance (speed): Run the nvTurboDatabase speed command to maximize speed. This solution works if your database is small enough or if your disk is large enough to allow the value_info.pag file to be backed up.
78
Installation Guide
3. A combination of minimizing space and maximizing speed: For typical operation, use the nvTurboDatabase speed command to optimize speed. For backups, perform the following steps: a. Run the nvTurboDatabase space command. This creates a database that minimizes space. b. Run the nvTurboDatabase speed command. This creates a database that optimizes speed but also moves the database files above to new files with a .BAK extension. c. Move the BAK files to a backup directory and compress them using the TAR utility if necessary. This strategy has the advantage of requiring less disk space and tarring to tapes more quickly. The disadvantage of this strategy is that the double compress takes longer to complete. In addition, this approach might require that you write a small script to copy the BAK files to the backup directory and to compress them.
79
80
Installation Guide
Appendix E. Support information

This section describes the following options for obtaining support for IBM products: v Obtaining fixes v Contacting IBM Software Support
Obtaining fixes
A product fix might be available to resolve your problem. You can determine what fixes are available for your IBM software product by checking the product support Web site: 1. Go to the IBM Software Support Web site (http://www.ibm.com/software/ support). 2. Under Products A - Z, click I, then select IBM Tivoli NetView. This opens a product-specific support site. 3. Under Self help, follow the link to Search all Downloads, where you will find a list of fixes, fix packs, and other service updates for your product. For tips on refining your search, click Search tips. 4. Click the name of a fix to read the description and optionally download the fix. To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps: 1. From the support page for any IBM product, click My support in the upper-right corner of the page. 2. If you have already registered, skip to the next step. If you have not registered, click register in the upper-right corner of the support page to establish your user ID and password. 3. Sign on to My support. 4. On the My support page, click Edit profiles in the left navigation pane, and scroll to Select Mail Preferences. Select a product family and check the appropriate boxes for the type of information you want. 5. Click Submit. 6. For e-mail notification for other products, repeat Steps 4 and 5. For more information about types of fixes, see the Software Support Handbook (http://techsupport.services.ibm.com/guides/handbook.html).
Contacting IBM Software Support

IBM Software Support provides assistance with product defects. Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have: v For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows or UNIX operating systems), enroll in Passport Advantage in one of the following ways:
81
Online: Go to the Passport Advantage Web page (http://www.lotus.com/ services/passport.nsf/WebDocs/ Passport_Advantage_Home) and click How to Enroll. By phone: For the phone number to call in your country, go to the IBM Software Support Web site (http://techsupport.services.ibm.com/guides/ contacts.html) and click the name of your geographic region. v For IBM eServer software products (including, but not limited to, DB2 and WebSphere products that run in zSeries, pSeries, and iSeries environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eServer software products, go to the IBM Technical Support Advantage Web page (http://www.ibm.com/servers/eserver/techsupport.html). If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to the contacts page of the IBM Software Support Handbook on the Web (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region for phone numbers of people who provide support for your location. Follow the steps in this topic to contact IBM Software Support: 1. Determine the business impact of your problem. 2. Describe your problem and gather background information. 3. Submit your problem to IBM Software Support.
Determine the business impact of your problem

When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem you are reporting. Use the following criteria:
Severity 1 Critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. Significant business impact: The program is usable but is severely limited. Some business impact: The program is usable with less significant features (not critical to operations) unavailable. Minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented.
Severity 2 Severity 3 Severity 4
Describe your problem and gather background information

When explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions: v What software versions were you running when the problem occurred? v Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. v Can the problem be recreated? If so, what steps led to the failure? v Have any changes been made to the system? (For example, hardware, operating system, networking software, and so on.)
82
Installation Guide
v Are you currently using a workaround for this problem? If so, please be prepared to explain it when you report the problem.
Submit your problem to IBM Software Support

You can submit your problem in one of two ways: v Online: Go to the Submit and track problems page on the IBM Software Support site (http://www.ibm.com/software/support/probsub.html). Enter your information into the appropriate problem submission tool. v By phone: For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook on the Web (techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region. If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround for you to implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions. For more information about problem resolution, see Obtaining fixes.
Appendix E. Support information
83
84
Installation Guide
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
85
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
Trademarks
AIX, DB2, DB2 Universal Database, eServer, IBM, the IBM logo, iSeries, Lotus, NetView, Passport Advantage, pSeries, Rational, RISC System/6000, RS/6000, Tivoli, the Tivoli logo, Tivoli Enterprise, Tivoli Enterprise Console, WebSphere, xSeries, z/OS, and z/Series are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
86
Installation Guide
UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others.
Notices
87
88
Installation Guide
Additional copyright and license information

The product described in this document also contains software downloaded from several web servers. Permission to download and use such software is conditioned upon inclusion of the following notices. gd 1.2 Copyright 1994, 1995, Quest Protein Database Center, Cold Spring Harbor Labs. Permission granted to copy and distribute this work provided that this notice remains intact. Credit for the library must be given to the Quest Protein Database Center, Cold Spring Harbor Labs, in all derived works. This does not affect your ownership of the derived work itself, and the intent is to assure proper credit for Quest, not to interfere with your use of gd. If you have questions, ask. (Derived works includes all programs that utilize the library. Credit must be given in user-visible documentation.) gd 1.2 was written by Thomas Boutell and is currently distributed by boutell.com, Inc. If you wish to release modifications to gd, please clear them first by sending email to boutell@boutell.com; if this is not done, any modified version of the gd library must be clearly labeled as such. The Quest Protein Database Center is funded under Grant P41-RR02188 by the National Institutes of Health. Written by Thomas Boutell, 2/948/95. The GIF compression code is based on that found in the pbmplus utilities, which in turn is based on GIFENCOD by David Rowley. See the notice below: Based on GIFENCOD by David Rowley. A Lemple-Ziv compression based on compress. Modified by Marcel Wijkstra. Copyright 1989 by Jef Poskanzer. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission appear in all supporting documentation. This software is provided as is without express or implied warranty. The Graphics Interchange Format is the Copyright property of CompuServe Incorporated. GIF (sm) is a Service Mark property of CompuServe Incorporated. The GIF decompression is based on that found in the pbmplus utilities, which in turn is based on GIFDECOD by David Koblas. See the notice below: Copyright 1990, 1991, 1993, David Koblas (koblas@netcom.com). Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above
89
copyright notice appears in all copies and that both that copyright notice and this permission appear in all supporting documentation. This software is provided as is without express or implied warranty. GIFtrans v1.12 Convert any GIF file into a GIF89a. Allows for setting the transparent or background color, changing colors, adding or removing comments. Also code to analyze GIF contents. Copyright 24.2.94 by Andreas Ley Permission to use, copy, modify, and distribute this software for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies. This software is provided as is without express or implied warranties.
90
Installation Guide
Index B
backup files deleting 19 renaming 19 books see publications daemons (continued) registering from the command line 46 using the Server Setup application 46 starting from the command line 50 using the Server Setup application 52 unregistering from the command line 46 using the Server Setup application 46 databases, backing up 36 databases, NDBM component overview 75 implementing improvements improving performance 77 migration options 78 strategies 78 tuning 75 utilities dbmcompress 76 dbmlist 76 nvTurboDatabase 77 databases, NDVM utilities 76 dbmcompress utility 76 dbmlist utility 76 deployment hardware requirements platform 7 Web console 9 planning backup servers 3 client installation 4 connecting to Tivoli Management Framework 6 language packs, requirements 6 language packs, support for 6 map location 4 mid-level managers 6 server installation 2 trapgend subagent 5 software requirements exporting data to Tivoli Data Warehouse 12 IBM Support Assistant 14 online help 10 operating system 9 SNMP data collection 12 TCP/IP connection 13 Tivoli environment 13 Tivoli NetView database component 11 upgrade requirements 13 Web console 10
E
education see Tivoli technical training vii
v, vi
F
files that are migrated during upgrade 71 fixes, obtaining 81
C
CiscoWorks 2000 integration, installing 34 client uninstalling 53 Client Setup application context-sensitive help 50 Client Setup application, starting 50 client/server access, configuring 38 clientsetup command 50 commands clientsetup 50 instalnv 23 netnmrc 47 netview 47 NVenvironment 36 nvwc.sh 29 serversetup 49 community name changes 55 components, Tivoli NetView client 1 database description 1 requirement 11 language packs 2 native console 1 server 1 Web console 1 configuring client to access a server 38 client/server access 38 server to enable client access 38 SNMP agent for Linux 39 Tivoli NetView program 42 trapgend daemon from the command line 32 using the Server Setup application 33 Web daemons disabling SSL 30 enabling SSL 29 enabling the daemons 29 conventions typeface viii customer support see Software Support 81
H
hardware recommendations determining the size of your network 61 for your network size 63 overview 61 hardware requirements platform 7 Web console 9
I
IBM Support Assistant requirements 14 installation planning backup servers 3 client installation 4 connecting to Tivoli Management Framework 6 hardware requirements 7 language packs, requirements 6 language packs, support for 6 map location 4 mid-level managers 6 server installation 2 trapgend subagent 5 installation entries 69 installation problems community name changes 55 language packs 57 tdwdaemon errors 56 too many semaphores (Solaris) 55 installing CiscoWorks 2000 integration 34 mid-level managers 35 monitoring agent 35 Tivoli NetView Framework patch 20 Tivoli NetView program before you begin 17 cleaning up old traps 20 configuring Linux for topology discovery 18 deleting old backup files 19 installation entries 69 messages, displaying 18 product requirements, determining if you meet 18
D
daemon status, checking daemons recyling 48 45
91
installing (continued) Tivoli NetView program (continued) Tivoli NetView Framework patch 20 troubleshooting 55 trapgend daemon from the command line 32 using the Server Setup application 33 Web console from the CD 28 from the Tivoli NetView server 26 instalnv command 23 Internet, searching to find software problem resolution 81
netview shell script using Solaris requirements 47 newsgroups vii NVenvironment command 36 nvPrqchk script 18 nvTurboDatabase utility 77 nvwc.sh command 29
publications v accessing online ordering vii
vi
R
recommendations hardware determining the size of your network 61 for your network size 63 tuning for your network size 63 overview 61 registering daemons from the command line 46 using the Server Setup application 46 requirements hardware platform 7 Web console 9 software exporting data to Tivoli Data Warehouse 12 IBM Support Assistant 14 online help 10 operating system 9 SNMP data collection 12 TCP/IP connection 13 Tivoli environment 13 Tivoli NetView database component 11 upgrade requirements 13 Web console 10 runtime environment, initializing 36
O
online help, accessing 49 online publications accessing vi ordering publications vii output, logging 48
L
LANG environment variable 18 language packs configuring the Web browser 41 enabling language support 40 requirements 6 security files, customizing after upgrade 40 specifying an input method for Linux 41 support for 6 language support, enabling 40 LC_MESSAGES environment variable 18 Linux configuring for topology discovery 18 logging output 48
P
planning backup servers 3 client installation 4 connecting to Tivoli Management Framework 6 hardware requirements platform 7 Web console 9 language packs requirements 6 supported languages 6 map location 4 mid-level managers 6 server installation 2 software requirements exporting data to Tivoli Data Warehouse 12 IBM Support Assistant 14 online help 10 operating system 9 SNMP data collection 12 TCP/IP connection 13 Tivoli environment 13 Tivoli NetView database component 11 upgrade requirements 13 Web console 10 trapgend subagent 5 post-installation tasks client/server access, configuring 38 configuring a client to access a server 38 configuring a server to enable client access 38 databases, backing up 36 runtime environment, initializing 36 SNMPagent, configuring for Linux 39 problem determination describing problem for IBM Software Support 82 determining business impact for IBM Software Support 82 submitting problem to IBM Software Support 83 product requirements, determining if you meet 18
M
manuals see publications v, vi mid-level managers planning for installation 6 uninstalling 54 mid-level managers, installing 35 migrating files 71 MLM See mid-level managers monitoring agent, installing 35
S
secure socket layer disabling 30 enabling 29 server uninstalling 53 Server Setup application context-sensitive help 50 Server Setup application, starting serversetup command 49 software components client 1 database description 1 requirement 11 language packs 2 native console 1 server 1 Web console 1 software requirements exporting data to Tivoli Data Warehouse 12 IBM Support Assistant 14 online help 10 operating system 9 SNMP data collection 12 TCP/IP connection 13 Tivoli environment 13
49
N
NDBM databases component overview 75 implementing improvements improving performance 77 migration options 78 strategies 78 tuning 75 utilities 76 dbmcompress 76 dbmlist 76 nvTurboDatabase 77 netnmrc command 47 netview command 47
92
Installation Guide
software requirements (continued) Tivoli NetView database component 11 upgrade requirements 13 Web console 10 Software Support contacting 81 describing problem for IBM Software Support 82 determining business impact for IBM Software Support 82 submitting problem to IBM Software Support 83 starting Client Setup application 50 daemons from the command line 50 using the Server Setup application 52 Server Setup application 49 Tivoli NetView program daemon status, checking 45 daemons, registering and unregistering 45 from the command line 47 logging output 48 online help, accessing 49 overview 45, 47 recycling the daemons 48 using the Tivoli desktop 48 Web console 29 status, daemon, checking 45 stopping Tivoli NetView program 49
tuning recommendations for your network size typeface conventions viii
63
U
uninstalling client 53 mid-level managers 54 server 53 trapgend daemon 54 Web console 54 unregistering daemons from the command line 46 using the Server Setup application 46 upgrading Tivoli NetView program before you begin 17 cleaning up old traps 20 configuring Linux for topology discovery 18 deleting old backup files 19 files that are migrated 71 messages, displaying 18 product requirements, determining if you meet 18 Tivoli NetView Framework patch 20 Web console from the CD 28 from the Tivoli NetView server 26
T
TCP/IP connection requirements 13 Tivoli environment software requirements 13 Tivoli NetView Framework patch, installing 20 Tivoli software information center vi Tivoli technical training vii topology data, migrating 20 training, Tivoli technical vii trapgend daemon configuring from the command line 32 using the Server Setup application 33 uninstalling 54 trapgend subagent installing from the command line 32 using the Server Setup application 33 planning for installation 5 traps, cleaning up 20 troubleshooting installation problems cannot communicate with SNMP agent 55 community name changes 55 language packs 57 tdwdaemon errors 56 too many semaphores (Solaris) 55
W
Web console configuring for language support 41 full Web console, description 25 hardware requirements 9 installing from the CD on Windows 28 from the Tivoli NetView server 26 software requirements 10 starting 29 thin Web console, description 25 uninstalling 54 Web daemons configuring disabling SSL 30 enabling SSL 29 enabling the daemons 29
Index
93
94
Installation Guide
Printed in USA
GC32-1842-00

Netview Migration

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Netview Migration

Загружено:

Авторское право:

Доступные форматы

Tivoli NetView for UNIX and Linux

Tivoli NetView for UNIX and Linux

Chapter 1. Planning for installation . . . 1

Chapter 2. Installing or upgrading the Tivoli NetView program . . . . . . . 17

Chapter 3. Starting and stopping the Tivoli NetView program . . . . . . . 45

Chapter 4. Uninstalling the Tivoli NetView program . . . . . . . . . . 53

Chapter 5. Troubleshooting common installation problems . . . . . . . . 55

Appendix E. Support information . . . 81

Appendix A. Hardware, memory, and tuning recommendations . . . . . . . 61

Additional copyright and license information . . . . . . . . . . . . . 89 Index . . . . . . . . . . . . . . . 91

Appendix B. Installation entries . . . . 69

About this guide

Who should read this guide

IBM Tivoli NetView for UNIX and Linux library

Copyright IBM Corp. 2006

Accessing terminology online

Accessing publications online

Tivoli technical training

About this guide

Conventions used in this guide

Chapter 1. Planning for installation

Tivoli NetView components

Copyright IBM Corp. 2006

Planning for deployment

Determining where to install the Tivoli NetView server

Determining whether to use and synchronize backup servers

Deciding whether and where to install the Web console

Determining which data collector application to use

AIX system: Planning to install the trapgend subagent

Chapter 1. Planning for installation

AIX and Solaris environments: Determining whether to install mid-level managers

Determining whether to integrate with the Tivoli Management Framework

Planning to install the language packs

Language pack requirements

Note that paging space is reported in KB. Solaris environment:

Chapter 1. Planning for installation

Relational database (AIX 500 MB and Solaris environments only) Notes:

v Additional disk space for installation in a Tivoli environment as follows:

Minimum disk space requirement 8 MB 5 MB 100 MB 4 MB 1 MB

v A network adapter (a PCI adapter is strongly recommended for best performance)

Web console hardware requirements

Operating system support

Chapter 1. Planning for installation

Platform1 Linux Intel

Linux for zSeries2

Online help and Web Console requirements

Supported Web browsers Mozilla 1.7.12 or higher Firefox 1.5.0.1 or higher

Platform Linux Intel Linux Intel Sun Solaris Windows

AIX and Solaris environments: Tivoli NetView Database component requirement

Requirement for data collection

Tivoli NetView upgrade requirements

Requirements for integrating with the Tivoli Management Framework

TCP/IP connection requirements

v To check name resolution, enter the following command:

v To check host name resolution, enter the following command:

v To check communication to the system, enter the following command:

v To check connectivity to another system, enter the following command:

Chapter 1. Planning for installation

IBM Support Assistant and Tivoli NetView plug-in requirements

Chapter 1. Planning for installation

Chapter 2. Installing or upgrading the Tivoli NetView program

Before you begin

Copyright IBM Corp. 2006