Installation Guide 1.3.1

Transcription

1 Tioli Netcool Performance Manager Wireline Component Document Reision R1E10 Installation Guide 1.3.1

2 Note Before using this information and the product it supports, read the information in Notices on page 219. Copyright IBM Corporation 2006, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Preface ii Audience ii Tioli Netcool Performance Manager - Wireline Component ii The Default UNIX Shell ix Chapter 1. Introduction Tioli Netcool Performance Manager architecture.. 1 Co-location rules Inheritance Notable subcomponents and features Typical installation topology Basic topology scenario Intermediate topology scenario Adanced topology scenario Tioli Netcool Performance Manager distribution.. 11 Chapter 2. Installing and configuring the prerequisite software Oeriew Supported platforms Pre-Installation setup tasks Setting up a remote X Window display Changing the ethernet characteristics Adding the puser login name Setting the resource limits (AIX only) Set the system parameters (Solaris only) Enable FTP on Linux systems (Linux only) Disable SELinux (Linux only) Set the kernel parameters (Linux only) Install a libcrypto.so Deployer pre-requisites Operating system check Mount points check Authentication between distributed serers Downloading the Tioli Netcool Performance Manager distribution to disk Downloading Tioli Common Reporting to disk 27 General Oracle setup tasks Specifying a basename for DB_USER_ROOT.. 28 Specifying Oracle login passwords Assumed alues Installing the Oracle serer Ensure that the Oracle User is not in NIS Download the Oracle distribution and patch to disk Verify the required operating system packages.. 32 Run the Oracle serer configuration script Set a password for the Oracle login name Run the pre-installation script Run the rootpre.sh script (AIX only) Verify PATH and enironment for the Oracle login name Install Oracle Run the root.sh script Install Oracle patches Relax permissions on ORACLE_HOME Set the ORACLE_SID ariable Set automatic startup of the database instance.. 45 Configure the Oracle listener Configure the Oracle net client Shut down of performance impacting Oracle jobs 50 Installing the Oracle client Ensure that the Oracle User is not in NIS Download the Oracle distribution and patch to disk Run the Oracle client configuration script Set a password for the Oracle login name Run the pre-installation script Verify PATH and enironment for the Oracle login name Install the Oracle client Run the root.sh script Install Oracle patches Relax permissions on ORACLE_HOME Configure the Oracle net client Next steps Chapter 3. Installing in a distributed enironment Distributed installation process Starting the Launchpad Installing the Topology Editor Starting the Topology Editor Creating a new topology Adding and configuring the Tioli Netcool Performance Manager components Add the hosts Add a database configurations component Add a DataMart Add a Discoery Serer Add a Tioli Integrated Portal Add a DataView Add the DataChannel administratie components 76 Add a DataChannel Add a Collector Add a Cross Collector CME Saing the topology Opening an existing topology file Starting the Deployer Primary Deployer Secondary Deployers Pre-deployment check Deploying the topology Next steps Resuming a partially successful first-time installation Chapter 4. Installing as a minimal deployment Copyright IBM Corp. 2006, 2010 iii

4 Oeriew Before you begin Special consideration Oerriding default alues Installing a minimal deployment Download the MIB-II files Starting the Launchpad Start the installation The post-installation script Next steps Chapter 5. Modifying the current deployment Opening a deployed topology Adding a new component Changing configuration parameters of existing Tioli Netcool Performance Manager components. 98 Moing components to a different host Moing a deployed collector to a different host.. 99 Moing a deployed SNMP collector Moing a deployed UBA bulk collector Chapter 6. Using the High Aailability Manager Oeriew HAM basics The parts of a collector Clusters HAM cluster configuration Types of spare hosts Types of HAM clusters Example HAM clusters Resource pools How the SNMP collector works How failoer works with the HAM and the SNMP collector Obtaining collector status Creating a HAM enironment Topology prerequisites s Create the HAM and a HAM cluster Add the designated spare Add the managed definitions Define the resource pools Sae and start the HAM Creating an additional HAM enironment Modifying a HAM enironment Remoing HAM components Stopping and restarting modified components 125 Viewing the current configuration Show Collector Process... dialog Show Managed Definition... dialog Chapter 7. Uninstalling components 129 Remoing a component from the topology Restrictions and behaior Remoing a component Uninstalling the entire Tioli Netcool Performance Manager system Order of uninstall Restrictions and behaior Performing the uninstall Uninstalling the topology editor Residual files Appendix A. Remote installation issues When remote install is not possible FTP is possible, but REXEC or RSH are not Neither FTP nor REXEC/RSH are possible Installing on a remote host using a secondary deployer Appendix B. DataChannels Data collection Data aggregation Management programs and watchdog scripts 142 DataChannel application programs Starting the DataLoad SNMP collector DataChannel management components in a distributed configuration Manually starting the Channel Manager programs Adding DataChannels to an existing system DataChannel terminology Appendix C. Aggregation sets Oeriew Configuring aggregation sets Installing aggregation sets Start the Tioli Netcool Performance Manager setup program Set aggregation set installation parameters Edit aggregation set parameters file Linking DataView groups to timezones Appendix D. Deployer CLI options 159 Using the -DTarget option Appendix E. Secure file transfer installation Oeriew Enabling SFTP Installing OpenSSH AIX systems Solaris systems Linux systems Configuring OpenSSH Configuring the OpenSSH serer Configuring OpenSSH client Generating public and priate keys Testing OpenSSH and SFTP Troubleshooting Netcool/Proisio SFTP errors Appendix F. LDAP integration Supported LDAP serers LDAP configuration Enable LDAP configuration i IBM Tioli Netcool Performance Manager: Installation Guide

5 Verifying the DataView installation Assigning Tioli Netcool Performance Manager roles to LDAP users Appendix G. Using silent mode Sample properties files The Deployer Running the Deployer in silent mode Confirming the status of a silent install Restrictions The Topology Editor Appendix H. Installing an interim fix 183 Oeriew Installation rules Behaior and restrictions Before you begin Installing a patch Appendix I. Error codes and log files 187 Error codes Deployer messages Topology Editor messages InstallAnywhere messages Log files COI log files Deployer log file Eclipse log file Trace log file Appendix J. Troubleshooting Deployment problems Saing installation configuration files Tioli Netcool Performance Manager component problems Topology Editor problems Telnet problems Jaa problems Testing connectiity to the database Testing external procedure call access Appendix K. Migrating DataView content and users Moing DataView content between Tioli Integrated Portal serers The synchronize command Migrating SilerStream content to the Tioli Integrated Portal SilerStream page conersion The migrate command Notices Trademarks Contents

6 i IBM Tioli Netcool Performance Manager: Installation Guide

7 Preface The purpose of this manual IBM Tioli Netcool Performance Manager is a bundled product consisting of a wireline component and a wireless component. The purpose of this guide is to help you install thetioli Netcool Performance Manager product suite and the Oracle database management system. This guide proides instructions for installing Tioli Netcool Performance Manager components, but not necessarily for configuring the installed components into a finished system that produces management reports. After going through the steps in this guide, you will hae a set of running Tioli Netcool Performance Manager components ready to configure into a fully functional system. The goal of this guide is to get each component installed and running in its barest form. The running component does not necessarily hae network statistical data flowing into and out of it yet. In particular, at the end of this installation procedure, there are no or few management reports that can be iewed in DataView. Configuring installed components into a working system is the subject of other manuals in the Tioli Netcool Performance Manager documentation set. Audience The audience for this manual. The audience for this manual is the network administrator or operations specialist responsible for installing the Tioli Netcool Performance Manager product suite on an enterprise network. To install Tioli Netcool Performance Manager successfully, you should hae a thorough understanding of the following subjects: Basic principles of TCP/IP networks and network management SNMP concepts Administration of the Linux, Solaris or AIX operating enironment Administration of the Oracle database management system Tioli Netcool Performance Manager Tioli Netcool Performance Manager - Wireline Component IBM Tioli Netcool Performance Manager consists of a wireline component (formerly Netcool/Proiso) and a wireless component (formerly Tioli Netcool Performance Manager for Wireless). Tioli Netcool Performance Manager - Wireline Component consists of the following subcomponents: DataMart is a set of management, configuration, and troubleshooting GUIs. The Tioli Netcool Performance Manager System Administrator uses the GUIs to define policies and configuration, and to erify and troubleshoot operations. Copyright IBM Corp. 2006, 2010 ii

8 DataLoad proides flexible, distributed data collection and data import of SNMP and non-snmp data to a centralized database. DataChannel aggregates the data collected through Tioli Netcool Performance Manager DataLoad for use by the Tioli Netcool Performance Manager DataView reporting functions. It also processes online calculations and detects real-time threshold iolations. DataView is a reliable application serer for on-demand, web-based network reports. Technology Packs extend the Tioli Netcool Performance Manager system with serice-ready reports for network operations, business deelopment, and customer iewing. The following figure shows the different Tioli Netcool Performance Manager modules. Tioli Netcool Performance Manager documentation consists of the following: Release notes Configuration recommendations User guides Technical notes Online help The documentation is aailable for iewing and downloading on the information center at com.ibm.netcool_pm.doc/welcome_tnpm.htm. iii IBM Tioli Netcool Performance Manager: Installation Guide

9 The Default UNIX Shell Add short description The installation scripts and procedures in this manual generally presume, but do not require, the use of the Korn or Bash shells, and only Korn shell syntax is shown in examples. If you are a user of the C shell or Tcsh, make the necessary adjustments in the commands shown as examples throughout this manual. This guide uses the following shell prompts in the examples: # (pound sign) indicates commands you perform when logged in as root. $ (dollar sign) indicates commands you perform when logged in as oracle or puser. SQL> indicates commands you perform at the SQL*Plus prompt. Preface ix

10 x IBM Tioli Netcool Performance Manager: Installation Guide

11 Chapter 1. Introduction Introduction to Tioli Netcool Performance Manager installation. This chapter proides an oeriew of the Tioli Netcool Performance Manager product suite and proides important pre-installation setup information. In addition, this chapter proides an oeriew of the installation interface introduced in ersion Tioli Netcool Performance Manager architecture Tioli Netcool Performance Manager system components. The Tioli Netcool Performance Manager components run on: SPARC-based serers from Sun Microsystems that run the Solaris operating system AIX serers from IBM Linux serers Exact, release-specific requirements, prerequisites, and recommendations for hardware and software are described in detail in the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide. You can work with Professional Serices to plan and size the deployment of Tioli Netcool Performance Manager components in your enironment. The following diagram proides a high-leel oeriew of the Tioli Netcool Performance Manager architecture. The Tioli Netcool Performance Manager system components are as follows: Tioli Netcool Performance Manager database - The Tioli Netcool Performance Manager database is hosted on Oracle. Copyright IBM Corp. 2006,

12 Tioli Netcool Performance Manager DataMart - Tioli Netcool Performance Manager DataMart is the user and administratie interface to the Tioli Netcool Performance Manager database and to other Tioli Netcool Performance Manager components. Tioli Netcool Performance Manager DataLoad - Tioli Netcool Performance Manager DataLoad consists of one or more components that collect network statistical raw data from network deices and from network management systems. Tioli Netcool Performance Manager DataChannel - Tioli Netcool Performance Manager DataChannel is a collection of components that collect data from DataLoad collectors, aggregate and process the data, and load the data into the Tioli Netcool Performance Manager database. DataChannel components also sere as the escalation point for collected data that is determined to be oer threshold limits. Tioli Netcool Performance Manager DataView - Tioli Netcool Performance Manager DataView is the Web serer hosting and analysis platform. This platform is used to display Web-based management reports based on network data aggregated and placed in the Tioli Netcool Performance Manager database. Tioli Netcool Performance Manager Technology Packs - Each technology pack is a set of components that describes the format and structure of network statistical data generated by network deices. Each technology pack is specific for a particular deice, or class of deices; or for a particular company's deices; or for a protocol (such as standard SNMP alues) common to many deices. Tioli Integrated Portal - The Tioli Integrated Portal application proides a database-aware Web serer foundation for the Web-based management reports displayed by Tioli Netcool Performance Manager DataView. The Tioli Integrated Portal application serer is an essential component of each DataView installation. Platform support All components of the Tioli Netcool Performance Manager - Wireline Component can run on a heterogenous mix of AIX, Linux, and Solaris operating systems. Co-location rules Allowed component deployment numbers and co-location rules. Table 1 lists how many of each component can be deployed per Tioli Netcool Performance Manager system and whether multiple instances can be installed on the same serer. In this table: N - Depends on how many subchannels there are per channel, and how many channels there are per system. For example, if there are 40 subchannels per channel and 8 channels, theoretically N=320. Howeer, the practical limit is probably much lower. System - The entire Tioli Netcool Performance Manager system. Per host - A single physical host can be partitioned using zones, which effectiely gies you multiple hosts. Note: All CME, DLDR, FTE, and LDR components within a channel must share the same filesystem. 2 IBM Tioli Netcool Performance Manager: Installation Guide

13 Table 1. Co-location rules Component AMGR Number of Instances Allowed One per host that supports DataChannel components BCOL N per system One per corresponding subchannel Co-Location Constraints CME One per subchannel Filesystem Yes CMGR One per system Yes Database One per system Yes Database channel One per DataChannel; maximum of 8 Yes DataLoad (SNMP collector) N per system One per corresponding subchannel One per host DataMart N per system One per host DataView N per system One per host Discoery Serer N per system One per host Co-locate with corresponding DataMart DLDR One per channel Filesystem Yes FTE One per subchannel Filesystem Yes HAM N+M per system, where N is the number of collectors that HAM is monitoring, and M is the number of standby collectors Yes LDR One per channel Filesystem Yes Log One per system Yes UBA (simple) N per system Yes One per corresponding subchannel Yes Yes Yes Yes Co-Location Constraints Supported by Deployer? One per system. UBA (complex) Pack-dependent Pack-dependent Pack-dependent Yes Chapter 1. Introduction 3

14 In the Logical iew of the Topology Editor, the DataChannel component contains the subchannels, LDR, and DLDR components, with a maximum of 8 channels per system. The subchannel contains the collector, FTE, and CME, with a maximum of 40 subchannels per channel. Inheritance Inheritance is the method by which a parent object propagates its property alues to a child component. The following rules should be kept in mind when dealing with these properties. A Child Property can be read only, but is not always. If the Child Property is not read only, then it can be changed to a alue different from the Parent Property. If the Parent Property changes, and the Child and Parent properties were the same before the change, then the child property will be changed to reflect the new Parent Property alue If the Child Property changes, the Parent Property alue will not be updated The Default Value of the Child Property is always the current Parent Property alue Example As an example of how a new component inherits property alues: The Disk Usage Serer (DUS) is a child component of the Host object. The DUS Remote User property inherits its alue from the Host PV User Property on creation of the DUS. The DUS property alue will be taken from the Host property alue. Child properties that hae been inherited are marked as inherited. As an example of what happens when you change inherited property alues: If we change the Host PV User Property alue, it gets pushed down to the DUS Remote User property alue, updating it. The asscociated Default Value is also updated. If we change the DUS Remote User property alue, that is the child alue, it does not propogate up to the host; the parent Host PV User Property alue remains unchanged. Now the child and parent properties are out of sync, and if we change the parent property alue it is not reflected in the child property, though the default alue continues to be updated. 4 IBM Tioli Netcool Performance Manager: Installation Guide

15 Notable subcomponents and features The following sections describe a subset of the Tioli Netcool Performance Manager that should be considered before deciding on your topology configuration. Collectors Collectors description. The DataLoad collector takes in the unrefined network data and stores it in a file that Tioli Netcool Performance Manager can read. This file is known as a binary object format file (BOF). The following processes are employed in the DataLoad module: SNMP Collector - The DataLoad SNMP Collector sends SNMP requests to network objects. Only the data requested by the configuration that was defined for those network objects is retrieed. Bulk Collector - The Bulk Collector uses a Bulk Adaptor, which is indiidually written for specific network resources, to format the unrefined data into a file, called a PVline file, which is passed to the Bulk Collector. Installation or topology considerations: Installation and topology considerations for collectors. The DataLoad modules can be loaded on lightweight serers and placed as close to the network as possible (often inside the network firewall). Because a DataLoad module does not contain a database, the hardware can be relatiely inexpensie and can still reliably handle high olumes of data. Up to 320 DataLoad modules can be supported per Tioli Netcool Performance Manager installation. The number of collectors in your system will affect the topology configuration. You can hae multiple BULK collectors, UBA or BCOL, on a single host, but you can only hae one SNMP based collector per host. The number of collectors is in turn drien by the number of required Technology Packs. Technology packs Technology packs description. Tioli Netcool Performance Manager Technology Packs are custom designed collections of MIBs, discoery formulas, collection formulas, complex formulas, grouping rules, reporters, and other functions. Technology packs proide all Tioli Netcool Performance Manager needs to gather data for targeted deices. Technology packs make it possible for Tioli Netcool Performance Manager to report on technology from multiple endors. Installation or topology considerations: Installation and topology considerations for technology packs. If you are creating a UBA collector, you must associate it with a specific technology pack. Chapter 1. Introduction 5

16 Note: General installation information for technology packs can be found in the IBM Tioli Netcool Performance Manager: Technology Pack Installation Guide, pack-specific installation guides are also proided. Please consult both sets of documentation for important installation or topology information. High Aailability High Aailability description. High aailability can be implemented for Tioli Netcool Performance Manager in two forms: High Aailability Manager (HAM): This is a DataChannel component that can be configured to handle aailability of SNMP collectors. Veritas Cluster or Sun Cluster (referred to as HA within the documentation): This method of implementing high aailability has a much broader scope and can coer all or a combination of the database, DataChannel, DataMart and DataView components. The following High Aailability (HA) documents are aailable for download from the Tioli Open Process Automation Library (OPAL), software/brandcatalog/opal/. TNPM High Aailability Oeriew Describes high aailability solutions for the Tioli Netcool Performance Manager product. Sun Cluster TNPM Agent Guide Describes how Sun Clusters can be used with TNPM to created a high aailability Tioli Netcool Performance Manager system. High Aailability Operations and Deployment Describes an example system that was configured to proide high aailability. TNPM High Aailability Installation and Configuration Describes the steps necessary to install and configure components of Tioli Netcool Performance Manager in a highly aailable configuration. For information coering the High Aailability Manager, see mtnpm_installguide_usingham.ditamap Installation or topology considerations: Installation and topology considerations for the High Aailability Manager. The HAM must be put on the same machine as the channel manager. Disk Usage Serer This Disk Usage Serer component is responsible for maintaining the properties necessary for quota management (flow control) of DataChannel. The DataChannel component requires a Disk Usage Serer. This component is responsible for maintaining the properties necessary for quota management (flow control) of DataChannel. DataChannel components can only be added to hosts that include a Disk Usage Serer. Multiple Disk Usage Serers can be configured per host; therefore, allowing multiple DataChannel directories to exist on a single host. There are two major reasons why a user may want to configure multiple Disk Usage Serers: 6 IBM Tioli Netcool Performance Manager: Installation Guide

17 Disk space is running low: Disk space may be impacted by the addition of a new DataChannel component. In which case, the user may want to add a new file system managed by a new Disk Usage Serer. Separate disk quota management: The user may want to separately manage the quotas assigned to discrete DataChannel components. For more information, see Disk quota management. The user can assign the management of a new file system to a Disk Usage Serer by editing the local_root_directory property of that Disk Usage Serer using the Topology Editor. The user can then add DataChannel components to the host, and can assign the component to a Disk Usage Serer, either in the creation wizard or by editing the DUS_NUMBER property inside the component. Disk quota management: Disk Quota Management description. The addition of a Disk Usage Serer endeaors to make the process of assigning space to a component much easier than it has been preiously. No longer is a user required to calculate the requirements of each component and assign that space indiidually, but components now work together to more effectiely utilize the space they hae under the Disk Usage Serer. Also, the user is relieed of trying to figure out which component needs extra space and then changing the quota for that component. Now, the user can just change the quota of the DUS and all components on that Disk Usage Serer will get the update and share the space on an as needed basis. Good judgement of space requirements is still needed. Howeer, the estimating of space requirements is being made at a higher leel; and should an estimate be incorrect, only one number needs to be changed instead of potentially updating the quota for each component separately. Flow control: Flow Control description. Optimized flow control further eliminates problems with component leel quotas. Each component holds on to only a fie hours of input and output, and once it has reached this limit, it stops processing until the downstream component picks up some of the data. This aoids the cascading scenario where one component stops processing and the components feeding it begin to stockpile files, which results in the quota being filled and causes all components to shut down because they hae run out of file space. Installation or topology considerations: Installation or Topology considerations for flow control. DataChannel components can only be added to hosts that include a Disk Usage Serer. Chapter 1. Introduction 7

18 Typical installation topology Example topology scenarios. Table 2 proides an example of where to install Tioli Netcool Performance Manager components, using four serers. Use this example as a guide to help you determine where to install the Tioli Netcool Performance Manager components in your enironment. Basic topology scenario A basic example topology. Table 2. Tioli Netcool Performance Manager basic topology scenario Serer Name Tioli Netcool Performance Manager Components Hosted delphi Oracle serer Tioli Netcool Performance Manager Database Tioli Netcool Performance Manager DataMart Tioli Netcool Performance Manager Discoery Serer corinth Oracle client Tioli Netcool Performance Manager DataLoad, SNMP collector Tioli Netcool Performance Manager DataLoad, Bulk Load collector sparta Oracle client Tioli Netcool Performance Manager DataChannel athens Oracle client Tioli Integrated Portal Tioli Netcool Performance Manager DataView Notes Install the Topology Editor and primary deployer on this system. You could install Tioli Netcool Performance Manager components remotely on this system. You could install Tioli Netcool Performance Manager components remotely on this system You could install Tioli Netcool Performance Manager components remotely on this system. Your configuration can use a pre-existing Tioli Integrated Portal, or install and include a new instance. 8 IBM Tioli Netcool Performance Manager: Installation Guide

19 Intermediate topology scenario An intermediate example topology scenario. Table 3. Tioli Netcool Performance Manager intermediate topology scenario Serer Name Tioli Netcool Performance Manager Components Hosted delphi Oracle serer Tioli Netcool Performance Manager Database Tioli Netcool Performance Manager DataMart Tioli Netcool Performance Manager Discoery Serer corinth Oracle client Tioli Netcool Performance Manager DataLoad, SNMP collector Tioli Netcool Performance Manager DataLoad, Bulk Load collector sparta Oracle client Tioli Netcool Performance Manager DataChannel thessaloniki Oracle client Tioli Netcool Performance Manager DataChannel Also running the Channel Manager. Tioli Netcool Performance Manager DataLoad, SNMP collector Tioli Netcool Performance Manager DataLoad, Bulk Load collector High Aailability Manager athens Oracle client Tioli Integrated Portal Tioli Netcool Performance Manager DataView Notes Install the Topology Editor and primary deployer on this system. You could install Tioli Netcool Performance Manager components remotely on this system. You could install Tioli Netcool Performance Manager components remotely on this system You could install Tioli Netcool Performance Manager components remotely on this system. This serer contains a duplicate set of collectors to allow for high aailability. You could install Tioli Netcool Performance Manager components remotely on this system. Your configuration can use a pre-existing Tioli Integrated Portal, or install and include a new instance. Chapter 1. Introduction 9

20 This scenario has an added copy of both collectors on corinth to a second machine, thessaloniki, for the purposes of failoer. HAM only manages SNMP collectors; therefore, the HAM in this scenario will manage aailability of the DataLoad SNMP collector and not the Bulk Load collector. The HAM must be put on the same machine as the channel manager. Adanced topology scenario An adanced example topology scenario. Table 4. Tioli Netcool Performance Manager adanced topology scenario Serer Name Tioli Netcool Performance Manager Components Hosted delphi Oracle serer Tioli Netcool Performance Manager Database Tioli Netcool Performance Manager DataMart Tioli Netcool Performance Manager Discoery Serer corinth Oracle client Tioli Netcool Performance Manager DataLoad, SNMP collector Tioli Netcool Performance Manager DataLoad, Bulk Load collector sparta Oracle client Tioli Netcool Performance Manager DataChannel thessaloniki Oracle client Tioli Netcool Performance Manager DataChannel Also running the Channel Manager. Tioli Netcool Performance Manager DataLoad, SNMP collector Tioli Netcool Performance Manager DataLoad, Bulk Load collector High Aailability Manager Notes Install the Topology Editor and primary deployer on this system. You could install Tioli Netcool Performance Manager components remotely on this system. You could install Tioli Netcool Performance Manager components remotely on this system You could install Tioli Netcool Performance Manager components remotely on this system 10 IBM Tioli Netcool Performance Manager: Installation Guide

21 Table 4. Tioli Netcool Performance Manager adanced topology scenario (continued) Serer Name Tioli Netcool Performance Manager Components Hosted athens Oracle client Tioli Integrated Portal Tioli Netcool Performance Manager DataView rhodes Oracle client Tioli Integrated Portal Tioli Netcool Performance Manager DataView Notes You could install Tioli Netcool Performance Manager components remotely on this system. Your configuration can use a pre-existing Tioli Integrated Portal, or install and include a new instance. You could install Tioli Netcool Performance Manager components remotely on this system. Your configuration can use a pre-existing Tioli Integrated Portal, or install and include a new instance. Tioli Netcool Performance Manager distribution How to get your hands on the product distribution. The Tioli Netcool Performance Manager distribution is aailable as a DVD/CD and as an electronic image. The instructions in this guide assume that you are installing from an electronic image. If you install the product from an electronic image, be sure to keep a copy of the distribution image in a well-known directory, because you will need this image in the future to make any changes to the enironment, including uninstalling Tioli Netcool Performance Manager. Chapter 1. Introduction 11

22 12 IBM Tioli Netcool Performance Manager: Installation Guide

23 Chapter 2. Installing and configuring the prerequisite software Oeriew Installing and configuring the software required by Tioli Netcool Performance Manager. This chapter describes how to install and configure the prerequisite software for Tioli Netcool Performance Manager. Before beginning the Tioli Netcool Performance Manager installation, you must install the prerequisite software listed in the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide. The required software includes: Oracle serer: To use Oracle with Tioli Netcool Performance Manager, you must install Oracle as described in this chapter - do not use a separate Oracle installation method proided by Oracle Corporation. Oracle client: You must install Oracle client software on each system where you plan to install a Tioli Netcool Performance Manager component, except for the system where you installed the Oracle serer. When you complete the steps in this chapter, the Oracle serer and client will be installed and running, with tablespaces sized and ready to accept the installation of a Tioli Netcool Performance Manager DataMart database. You can communicate with Oracle using the SQLPlus command-line utility. The steps in this chapter use IBM-proided installation scripts to install and configure the Oracle database from the Oracle distribution and patch. For use with Tioli Netcool Performance Manager, you must install Oracle as described in this chapter. Do not use a separate Oracle installation method proided by Oracle Corporation. You should obtain the official Oracle distribution from your edeliery site (after purchase of an Oracle license). See the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide for recommendations when purchasing a license from Oracle. Note: The Tioli Netcool Performance Manager script used to install Oracle is platform-independent and can be used to install on Solaris, AIX, or Linux, regardless of the operating system distribution media. OpenSSH: You must install and configure OpenSSH before installing Tioli Netcool Performance Manager. For details, see Appendix E, Secure file transfer installation, on page 163. Linux systems require the installation of VSFTP (Very Secure FTP). Web browser: The launchpad requires a Web browser. IBM recommends using Mozilla with the launchpad. For the complete list of supported browsers, see the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide document. Jaa: Jaa is used by DataMart, DataLoad, and the technology packs. You must ensure you are using the IBM JRE and not the RHEL JRE. The IBM JRE is supplied with the Topology Editor or with TIP. To ensure you are using the right JRE you can either: Copyright IBM Corp. 2006,

24 Set the JRE path to conform to that used by the Topology Editor, do this using the following commands (using the default location for the primary deployer): PATH=/opt/IBM/proiso/topologyEditor/jre/bin:$PATH export $PATH For a remote serer, that is one that does not host the primary deployer, you must download and install the required JRE, and set the correct JRE path. See the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide document for JRE download details. Note: See the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide document for the complete list of prerequisite software and their supported ersions. Supported platforms The platforms supported by Tioli Netcool Performance Manager. Refer to the following table for platform requirement information. Tioli Netcool Performance Manager Component All Tioli Netcool Performance Manager Components: Database DataView DataChannel DataLoad DataMart Required Oracle Software Solaris bit AIX bit RHEL 5.5, 64-bit Pre-Installation setup tasks Before installing the prerequisite software, perform the tasks outlined in this section. Setting up a remote X Window display Setting Up a Remote X Window Display About this task For most installations, it does not matter whether you use a Telnet, rlogin, Xterm, or Terminal window to get to a shell prompt. Some installation steps must be performed from a window that supports the X Window serer protocols. This means that the steps described in later chapters must be run from an Xterm window on a remote system or from a terminal window on the target system's graphical display. Note: See the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide document for the list of supported X emulators. 14 IBM Tioli Netcool Performance Manager: Installation Guide

25 Specifying the DISPLAY enironment ariable If you use an X Window System shell window such as Xterm, you must set the DISPLAY enironment ariable to point to the IP address and screen number of the system you are using. About this task Command sequences in this manual do not remind you at eery stage to set this ariable. If you use the su command to become different users, be especially igilant to set DISPLAY before running X Window System-compliant programs. In general, set DISPLAY as follows: $ DISPLAY=Host_IP_Address:0.0 $ export DISPLAY To make sure the DISPLAY enironment ariable is set, use the echo command: $ echo $DISPLAY Disabling access control to the display If you encounter error messages when trying to run X Window System-based programs, you might need to temporarily disable X Window System access control so an installation step can proceed. About this task To disable access control: 1. Set the DISPLAY enironment ariable. 2. Enter the following command when logged in as root: # /usr/openwin/bin/xhost + Note: Disabling access control is what enables access to the current machine from X clients on other machines. Changing the ethernet characteristics Before installing Tioli Netcool Performance Manager, you must force both the ethernet adapter and the port on the switch to 100 full duplex mode - autonegotiate settings are not enough. AIX systems Changing ethernet characteristics on AIX. About this task To change the setting to full duplex: Note: If the AIX node is a irtual partition, you must perform these steps on the irtual I/O serer (including the reboot). Chapter 2. Installing and configuring the prerequisite software 15

26 1. Using the System Management Interface Tool (SMIT), naigate to Deices > Communication > Ethernet Adapter > Change/Show Characteristics of an Ethernet Adapter. 2. Select your ethernet adapter (the default is ent0). 3. Change the Media Speed setting to 100_Full_Duplex. 4. Change the setting Apply change to DATABASE only to yes. 5. Set the port on the switch or router that the AIX node is plugged into to 100_Full_Duplex. 6. Reboot your system. Solaris systems This section describes how to set a network interface card (NIC) and a BGE network drier to full duplex mode. NIC: Change the NIC to full duplex mode on Solaris systems About this task To change the NIC to full duplex mode: 1. Determine which type of adapter you hae by running the following command: ifconfig -a 2. To determine the current settings of the NIC, run the command ndd -get /de/hme with one of the following parameters: Command Parameter link_status link_speed link_mode ad_autoneg_cap Description Determines whether the link is up 1-Up 0 - Down Determines the link speed 0-10Mb/sec 1-100Mb/sec Determines the duplex mode 0 - Half duplex 1 - Full duplex Determines whether auto negotiation is on 0-Off 1-On For example: ndd -get /de/hme link_status In these commands, /de/hme is your NIC; you might need to substitute your own /de/xxx. 3. To set your NIC to 100Mb/s with full duplex for the current session, run the following commands: 16 IBM Tioli Netcool Performance Manager: Installation Guide

27 ndd -set /de/hme ad_100hdx_cap 0 ndd -set /de/hme ad_100fdx_cap 1 ndd -set /de/hme ad_autoneg_cap 0 Howeer, these commands change the NIC settings for the current session only. If you reboot, the settings will be lost. To make the settings permanent, edit the /etc/system file and add the following entries: set hme:hme_ad_autoneg_cap=0 set hme:hme_ad_100hdx_cap=0 set hme:hme_ad_100fdx_cap=1 4. Verify that your NIC is functioning as required by rerunning the commands listed in Step 2. BGE network drier: Change a BGE network drier to full duplex mode. About this task To change a BGE network drier to full duplex mode. 1. To determine the link speed and current duplex setting, run the following command: % kstat bge:0 egrep speed duplex The output is similar to the following: duplex full ifspeed link_duplex 2 link_speed 100 The parameters are as follows: link_duplex link_speed Parameter Description Determines the duplex setting 1 - Half-duplex 2 - Full duplex Determines the link speed Mb/sec Mb/sec Gb/sec 2. Create a file namedbge.conf in the /platform/uname -i/kernel/dr directory (for example, /platform/sunw,sun-fire-v210/kernel/dr/bge.conf). 3. Add the following lines to the file: speed=100; full duplex=1; 4. Reboot the machine to hae your changes take effect. Linux systems Enabling 100 full duplex mode on Linux systems. Chapter 2. Installing and configuring the prerequisite software 17

28 About this task Use your primary network interface to enable 100 full duplex mode. To check if full duplex is enabled: 1. Enter the following command: # dmesg grep -i duplex This should result in output similar to the following: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 2. Confirm the output contains the words: Full Duplex If this is not contained within the output, you must enable full duplex mode. The example output resulting from the command executed in step 1: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 indicate that the primary network interface is eth0. The actions specified in the following process presume that your primary network interface is eth0. Enabling full duplex mode on Linux: To enable full duplex mode. 1. Open the file ifcfg-eth0, which is contained in: /etc/sysconfig/network-scripts/ 2. Add the ETHTOOL_OPTS setting by adding the following text: ETHTOOL_OPTS="speed 100 duplex full autoneg off" Note: The ETHTOOL_OPTS speed setting can be set to either 100 or 1000 depending on speed of connection aailable 100Mbit/s or 1000Mbit/s (1Gbit/s). Adding the puser login name puser is the default name used within this document to describe the required Tioli Netcool Performance Manager Unix user. The required user can be gien any name of your choosing. Howeer, for the remainder of this document this user will be referred to as "puser". Decide in adance where to place the home directory of the puser login username. Use a standard home directory mounted on /home or /export/home, as aailable. Note: Do not place the home directory in the same location as the Tioli Netcool Performance Manager program files. That is, do not use /opt/proiso or any other directory in /opt for the home directory. Add the puser login name to eery system on which you install a Tioli Netcool Performance Manager component, including the system hosting the Oracle serer. 18 IBM Tioli Netcool Performance Manager: Installation Guide

29 Adding puser to a Standalone Computer Use the steps in this section to add the puser login name to each standalone computer. About this task These steps add the login name only to the local system files on each computer (that is, to the local /etc/passwd and /etc/shadow files). If your network uses a network-wide database of login names such as Yellow Pages or Network Information Serices (NIS or NIS+), see Adding puser on an NIS-managed network on page 20. To add puser: 1. Log in as root. 2. Set and export the DISPLAY enironment ariable. (see Setting up a remote X Window display on page 14.) 3. If one does not already exist, create a group to which you can add puser. You can create a group with the name of your choice using the following command: groupadd <group> where: <group> is the name of the new group, for example, staff. 4. At a shell prompt, run the following command: # useradd -g <group> -m -d <home_dir>/<username> -k /etc/skel -s /bin/ksh <username> Where: <group> is the name of the group to which you want to add puser. <home_dir> is the home directory for the new user, for example, /export/home/ can be used as the example home directory. <username> is the name of the new user. This can be set to any string. Note: For the remainder of this document this user will be referred to as puser. 5. Set a password for puser: # passwd puser The system prompts you to specify a new password twice. The default puser password assumed by the Tioli Netcool Performance Manager installer is p. This can be set to a password conforming to your organization's standards. 6. Test logging in as puser, either by logging out and back in, or with the su command, such as: # su - puser Confirm that you are logged in as puser with the id command: $id These instructions create a puser login name with the following attributes: login name Attribute puser Value member of group staff Chapter 2. Installing and configuring the prerequisite software 19

30 Attribute Value home directory /home/export/puser login shell copy skeleton setup files (.profile, and so on) from this directory Korn shell (/bin/ksh) /etc/skel Note: The puser account must hae write access to the /tmp directory. Multiple computer considerations If you are creating the puser login name on more than one computer in your network, aoid confusion by specifying the same user ID number for each puser login name on each computer. When you hae created the first puser login name, log in as puser and run the id command. The system responds with the user name and user ID number (and the group name and group ID number). For example: $ id uid=1001(puser) gid=10(staff) When you create the puser login name on the next computer, add the -u option to the useradd command to specify the same user ID number: # useradd -g <group> -m -d <home_dir>/puser -k /etc/skel -s /bin/ksh -u 1001 puser Where: <group> is the name of the group to which you want to add puser. <home_dir> is the home directory for the new user, for example, /export/home/ can be used as the example home directory. <username> is the name of the new user. This can be set to any string. Adding puser on an NIS-managed network Adding puser on an NIS-Managed Network. If your site's network uses NIS or NIS+ to manage a distributed set of login names, see your network administrator to determine whether puser should be added to each Tioli Netcool Performance Manager computer's local setup files, or to the network login name database. Setting the resource limits (AIX only) On AIX systems, it is possible that the default user process limits are not adequate for Tioli Netcool Performance Manager. About this task If the default user process limits are not adequate for Tioli Netcool Performance Manager, do the following. To set the user process limits on AIX systems: 1. Log in as root. 2. Change your working directory to /etc/security by entering the following command: 20 IBM Tioli Netcool Performance Manager: Installation Guide

31 # cd /etc/security 3. Make a backup copy of the limits file by entering the following command: # cp limits limits.orig 4. Using a text editor, open the limits file and set the following alues: default: fsize = -1 core = -1 cpu = -1 data = -1 rss = stack = nofiles = 2000 totalprocesses = 800 Note: Apply these settings to eery AIX system running a Tioli Netcool Performance Manager program: the database serer, DataLoad serers, DataChannel serers, and DataMart serers. 5. Write and quit the file. 6. After modifying the settings, log off eery Tioli Netcool Performance Manager user and then log in again for the changes to take effect. Set the system parameters (Solaris only) Before you install the Oracle serer, you must set the Solaris shared memory and semaphore parameters. About this task If using Solaris 10 containers, typically the ariable in /etc/system is set only in the root container, and project ariables are set for each container. Refer to Solaris 10 container documentation for further information. When you install Tioli Netcool Performance Manager, you specify the size of the deployment - small, medium, or large. The alue you select affects the Oracle PROCESSES parameter. You must set the appropriate kernel parameter leel in order for the deployment to work properly. Note: These entries are only for the system running the Oracle serer, not the Oracle client. To set Solaris system parameters: 1. Set the NOEXEC_USER_STACK parameter in the system file: a. Log in as root. b. Change to the /etc directory: # cd /etc c. Create a backup of the system file, then open the system file with a text editor. d. Set the parameter NOEXEC_USER_STACK to 1, by adding the following line at the bottom of the file: set NOEXEC_USER_STACK=1 e. Sae and exit the system file. 2. Set resource controls correctly. The parameters affected by the deployment size are project.max-sem-ids, process.max-sem-nsems, project.max-shm-memory, and project.max-shm-ids. These parameters define the maximum size of a semaphore set and the maximum number of semaphores in the system. a. In Solaris 10, kernel parameters are replaced by resource controls. See Oracle Database Installation Guide 10g Release 2 (10.2) for Solaris Operating System (SPARC 64-Bit) Part Number B Chapter 2. Installing and configuring the prerequisite software 21

32 ( pre_install.htm#sthref259), section 2.6: Configuring Kernel Parameters. See also Oracle Metalink ID , Oracle Database on Unix AIX, HP-UX, Linux, Mac OS X, Solaris, Tru64 Unix Operating Systems Installation and Configuration Requirements Quick Reference (8.0.5 to 11.2), which lists Solaris requirements. b. Oracle recommends the following alues, noting that they are guidelines and should be tuned for production database systems. If you use a custom configuration, you must change the alues of the parameters to the appropriate leel. Resource Control Recommended Value project.max-sem-ids 100 process.max-sem-nsems 256 project.max-shm-memory project.max-shm-ids 100 c. Log in as the Oracle user (for example, oracle). d. To find the current kernel parameter settings, check the project id, and then check the resource control settings for that project id: $id-p uid=4074(oracle) gid=9999(dba) projid=3(default) $ prctl -n project.max-shm-memory -i project 3 project: 3: default NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-memory priileged 1.95GB - deny - system 16.0EB max deny - $ prctl -n project.max-sem-ids -i project 3 project: 1: user.root NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-sem-ids priileged deny - system 16.8M max deny - $ prctl -n project.max-shm-ids -i project 3 project: 3: default NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-ids priileged deny - system 16.8M max deny - $ prctl -n process.max-sem-nsems $$ process: 12134: bash NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT process.max-sem-nsems priileged deny - system 32.8M max deny - e. To change alues, check the Solaris documentation for complete information on projects. Here is one example, which sets the alue of project.max-shm-memory to 4GB. Log in as root and add a project, attached to the dba group (assuming the oracle user is part of the dba group), and set the alue: # projadd -p 100 -G dba -c "Oracle Project" \ -K "project.max-shm-memory=(priileged,4g,deny)" group.dba f. Check by logging back in as oracle, checking with id -p that the projid is now the new project number 100, and run prctl again to check that the max-shm-memory alue has been updated. 22 IBM Tioli Netcool Performance Manager: Installation Guide

33 $id-p uid=4074(oracle) gid=9999(dba) projid=100(group.dba) bash-3.00$ prctl -n project.max-shm-memory -i project 100 project: 100: group.dba NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-memory priileged 4.00GB - deny - system 16.0EB max deny - 3. Reboot your system before continuing to the next step. Enable FTP on Linux systems (Linux only) By default, FTP is not enabled on Linux systems. About this task To enable FTP on your Linux host: 1. Log in as root: 2. Change to the following directory: # /etc/init.d 3. Run the following command: #./sftpd start Disable SELinux (Linux only) Tioli Netcool Performance Manager will not install properly if the SELinux security policy is set to "enforcing". About this task To change the SELinux security policy is set to "enforcing" you must: 1. Open the SELinux config file for editing: $ cat /etc/selinux/config 2. Change the line in the file. SELINUX=enforcing To: SELINUX=disabled Note: You can also set the SELINUX setting to permissie. Setting SELINUX to permissie will result in a number of warnings at install time, but it will allow the installation code to run. Chapter 2. Installing and configuring the prerequisite software 23

34 Set the kernel parameters (Linux only) Required changes to Linux kernel parameters. About this task The following steps hae been taken from the Metalink Note , which is aailable from the Oracle website. 1. Add the following the lines in the file /etc/sysctl.conf kernel.shmall = physical RAM size / pagesize For most systems, this will be the alue See Note , which is aailable from the Oracle website, for more information. kernel.shmmax = 1/2 of physical RAM, but not greater than 4GB. This would be the alue for a system with 4Gb of physical RAM. kernel.shmmni = 4096 kernel.sem = fs.file-max = 512 x processes (for example for 128 processes) net.ip4.ip_local_port_range = net.core.rmem_default = net.core.rmem_max = net.core.wmem_default = net.core.wmem_max = fs.aio-max-nr = To effect these changes, execute the command: # sysctl -p Install a libcrypto.so For full SNMP3 support, SNMP DataLoad must hae access to the libcrypto.so. About this task Note: As libcrypto.so is deliered as standard on Linux platforms, steps 1 and 2 are not required if you are running on Linux. For each new and existing SNMP DataLoad, you must perform the following steps. 1. Install the OpenSSL package. This package can be downloaded from 2. As root, extract and install the libcrypto.so file using the following code: # cd /usr/lib # ar -x./libcrypto.a # ln -s libcrypto.so libcrypto.so 3. Update the dataload.en file so that the LD_LIBRARY_PATH (on Solaris & Linux) or LIBPATH (on AIX) enironment ariables include the path: /ProisoAutomation/proiso/thirdparty/openssl.org/openssl-0.9.8o/{YourOS}/lib 24 IBM Tioli Netcool Performance Manager: Installation Guide

35 What to do next Check the ariable has been set by doing the following: 1. Open a fresh shell 2. Check the dataload.en file. 3. Bounce the SNMP DL Upon startup, with a alid library, the collector will log the following log messages: INFO:CRYPTOLIB_LOADED Library libcrypto.so (OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008, 0x90802f) has been loaded. INFO:SNMPV3_SUPPORT_OK Full SNMP3 support Auth(None,MD5,SHA-1) x Pri(None,DES,AES) is aailable. Deployer pre-requisites Minimum filesystem specification and pre-requisites for the Deployer script. The Deployer will check the for the items described under the following headings. You should ensure that all elements are installed before running the deployer. Operating system check The Deployer will fail if the required patches listed in this file are not installed. The Deployer performs a check on the operating system ersions and that the minimum required packages are installed. For more information on the complete set of requirements for installation on Linux, AIX and Solaris, please consult the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide. Mount points check The Deployer assesses the aailable filesystem space for the defined mount point locations. The space requirements are calculated based on: The defined topology: The more components added to a single serer the more space is required on that serer. The component install location: Any directory set as the install location for a component will require sufficient space to store that component. The default install directory is /opt. You do not hae to use the default. This can be set to any directory location that has sufficient space. Remote installation of components: If components are being installed remotely, sufficient space must be assigned in the /tmp directory to store the software before it can be transferred to the remote serers. For a statement of minimum space requirements per serer in a distributed install or for a single serer in a proof of concept install, please consult the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide documentation. Chapter 2. Installing and configuring the prerequisite software 25

36 Authentication between distributed serers Why you must authenticate between distributed serers. If you are performing an installation that has a topology coering a set of distributed serers, ensure that RSA keys hae been cached between serers for root and puser prior to installation. If there are new serers that form part of installation topology which hae not been authenticated, the installation will fail. Note: puser is the required Tioli Netcool Performance Manager Unix user. Adding this user to your system is described in Adding the puser login name on page 18. Downloading the Tioli Netcool Performance Manager distribution to disk To download the Tioli Netcool Performance Manager distribution to a directory on a target serer's hard disk: 1. On the target host, log in as the Tioli Netcool Performance Manager user, such as puser. 2. Create a directory to hold the contents of your Tioli Netcool Performance Manager distribution. For example: $ mkdir /ar/tmp/cdproiso Note: Any further references to this directory within the install will be made using the token <DIST_DIR>. You will run a ariety of scripts and programs from directories residing in the directory created on the hard drie, including: Oracle configuration script Pre-installation script Installation script Tioli Netcool Performance Manager setup program 3. Download the Tioli Netcool Performance Manager distribution to the host directory created in the preious step and expand the contents of the distribution package. 4. If the current host is the primary deployer do the following: a. Change to the following directory: On Solaris systems: $ cd <DIST_DIR>/proiso/SOLARIS/DataChannel/SOL10/sparc On AIX systems: $ cd <DIST_DIR>/proiso/AIX/DataChannel/AIX/powerpc On Linux systems: $ cd <DIST_DIR>/proiso/RHEL/DataChannel/RHEL5/i686/ b. Untar the dc.tar file. For example: tar -xf dc.tar 26 IBM Tioli Netcool Performance Manager: Installation Guide

37 Downloading Tioli Common Reporting to disk To download the TCR distribution to a directory on a target serer's hard disk. About this task General Oracle setup tasks The TCR drier must be untarred so it can be used by the Tioli Netcool Performance Manager Common Installer. The following process ensures the user is required to specify the TCR media location only once: 1. Create a folder named TCR as a peer to the other Tioli Netcool Performance Manager Components, that is, DataView, DataChannel, etc. For example: <DIST_DIR>/proiso/SOLARIS/TCR 2. Extract the TCR 2.1 inside this folder. Should the user decide not to extract the tar as a peer to the other components, a TCR folder must still be created haing a path to the TCR install.sh the same as:./tcr/tcrinstaller/install.sh Note: If the user extracts the tar directly into the same root location as the Tioli Netcool Performance Manager Components then the TCR launchpad.sh will oerwrite the Tioli Netcool Performance Manager Installer launchpad.sh, meaning the launchpad cannot be started for the installer. How to install Oracle for use with Tioli Netcool Performance Manager. To install Oracle you will need: An appropriately sized serer with the operating system installed and running (for the Oracle serer). Note: For a basic oeriew of the minimum CPU speed, memory size, and disk configuration requirements for your Tioli Netcool Performance Manager installation, see the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide. For more detailed information you can contact IBM Professional Serices. The current ersion of Tioli Netcool Performance Manager software. The downloaded files for the Oracle installation. Oracle serer patch files. Oracle client patch files. If you are installing Oracle on an AIX system, follow the instructions in Asynchronous I/O Support (AIX Only) before installing Oracle. Before installing Oracle, read the setup and password information. Note: Tioli Netcool Performance Manager should be installed and run as a standalone database. It should not be placed on a serer that already has a database as the installation program will likely interfere. The co-hosting of TNPM will also affect performance in unknown ways. If a co-host is required then the Customer should seek out Professional Serices for support. Chapter 2. Installing and configuring the prerequisite software 27

38 Specifying a basename for DB_USER_ROOT Tioli Netcool Performance Manager components use distinct Oracle login names so that database access can be controlled separately by component, and for database troubleshooting clarity. About this task The Tioli Netcool Performance Manager installation generates the appropriate login names for each Tioli Netcool Performance Manager subsystem. Proide a basename, which the installation retains as the ariable DB_USER_ROOT. Note: This is not an operating system enironment ariable, but a ariable used internally by the installer. The default DB_USER_ROOT alue is PV. IBM strongly encourages you to retain the default alue. Results Oracle login names are generated from the DB_USER_ROOT basename by appending a function or subsystem identifier to the basename, as in the following examples: PV_ADMIN PV_INSTALL PV_LDR PV_CHANNEL PV_COLL PV_CHNL_MANAGER PV_GUI In addition, separate Oracle login names are generated for each Tioli Netcool Performance Manager DataChannel and subsystem, identified by an appended channel number, as in the following examples: PV_CHANNEL_01 PV_CHANNEL_02 PV_LDR_01 PV_LDR_02 Specifying Oracle login passwords For each component that requires an Oracle login name, you must proide a password for that login name. About this task In eery case, the installer uses the default Oracle password, PV. Oracle passwords are not case-sensitie, so PV and p are the same password. The default password is usually shown in uppercase, but is sometimes shown in lowercase. In both cases, the same default password is intended. 28 IBM Tioli Netcool Performance Manager: Installation Guide

39 You can retain the default password, or enter passwords of your own according to your site password standards. You should use the same password for all Tioli Netcool Performance Manager subsystem Oracle login names. If you use different passwords for each login name, keep a record of the passwords you assign to each login name. Results The Tioli Netcool Performance Manager installer uses PV for three default alues, as described in Table 5. Table 5: Uses of PV as Default Values Installer Default Value Used As Recommendation PV Default alue of the DB_USER_ROOT ariable, the basename on which Oracle login names are generated In all instances, use the default alue PV, unless your site has an explicit naming standard or an explicit password policy. PV or p PV Default password for all Oracle login names Default Oracle database name, also called the Oracle TNS name What to do next Note: If you use a non-default alue, you must remember to use the same alue in all installation stages. For example, if you set your Oracle TNS name to PROV instead of PV, you must oerride the default PV entry in all subsequent steps that call for the TNS name. Assumed alues The steps in this chapter assume the following default alues: Setting Hostname of the Oracle serer delphi Value Assumed in this Chapter Oracle serer program files installed in /opt/oracle ORACLE_BASE = /opt/oracle Operating system login name for Oracle user oracle Note: The default name created is oracle. Howeer, you can set another name for the Oracle user. Password for Oracle user oracle ORACLE_SID = PV TNS name for Tioli Netcool Performance PV Manager database instance Chapter 2. Installing and configuring the prerequisite software 29

40 Setting Oracle installed in (ORACLE_HOME =) Value Assumed in this Chapter /opt/oracle/product/n Note: The alue of ORACLE_HOME cannot contain soft links to other directories or filesystems. Be sure to specify the entire absolute path to Oracle. Tioli Netcool Performance Manager expects an Optimal Flexible Architecture (OFA) structure where ORACLE_HOME is a sub-directory to ORACLE_BASE. Oracle login name for database administrator (DBA) Password for Oracle DBA login name DB_USER_ROOT = Path for Oracle data, mount point 1 system manager PV /raid_2/oradata Path for Oracle data, mount point 2 /raid_3/oradata Installing the Oracle serer Note: If your site has established naming or password conentions, you can substitute site-specific alues for these settings. Howeer, IBM strongly recommends using the default alues the first time you install Tioli Netcool Performance Manager. See Specifying a basename for DB_USER_ROOT on page 28 for more information. This section describes the steps required to install the Oracle serer and erify the installation. The instructions in this section contain information on installing the Oracle 10 serer software with the ersion patch. Note: The Tioli Netcool Performance Manager documentation describes how to configure Oracle using the init.ora file. It is possible to configure Oracle using a SPFILE; howeer, the documentation does not coer how this is achieed. Ensure that the Oracle User is not in NIS The oracle user must be created locally, and must not be part of Network Information Serices (NIS). About this task The configure_ora script does not support oracle users who are part of NIS. If the oracle account is already in NIS, do the following: 1. On the system where the Oracle database is to be installed, disable NIS. For more information, see your operating system documentation. 30 IBM Tioli Netcool Performance Manager: Installation Guide

41 2. Run the configure_ora script to create a local oracle account (see Run the Oracle serer configuration script on page 33). 3. Re-enable NIS. Note: The local Oracle account should be used before the NIS Oracle user. Download the Oracle distribution and patch to disk The process of downloading the Oracle distribution About this task To download the Oracle installation files to your target serer's hard disk: 1. Log in as root. 2. Create a directory to hold the contents of the Oracle distribution. For example: # mkdir /ar/tmp/oracle10201 # mkdir /ar/tmp/oracle Download the Oracle files to the /ar/tmp/oracle10201 directory. 4. Locate the appropriate upgrade patch file for your ersion of Oracle on the Oracle Web site and download it to your /ar/tmp/oracle10204 directory. 5. Unzip the oracle distribution files that now reside in the /ar/tmp/oracle10201 and /ar/tmp/oracle10204 directories. Before you proceed to the next step, make sure that you obtain the upgrade instructions proided by Oracle for the patch. The instructions contain information on performing steps required for the upgrade that are not documented in this guide. If you are installing the Oracle patch on an AIX system, you might need to run the sbinclean command and execute the catpatch.sql and utlrp.sql SQL scripts as part of the upgrade procedure. Additional requirements might exist for other platforms. See your database administrator to determine whether there are any company-specific requirements for installing Oracle in your enironment. If you hae downloaded Oracle using OTN If you hae downloaded the Oracle installation files using OTN there are a number of steps you must perform. About this task If you hae downloaded the Oracle installation files using OTN, you must do the following: 1. Log in as root. 2. Create a directory to contain your Oracle files. For example: # mkdir /ar/tmp/oracle Download your gzipped 'cpio' Oracle files to this directory. 4. Oracle Serer folder setup: a. Within the oracle distribution directory you hae created, create a subdirectory called 'database'. b. Gunzip the '10gr2_db_sol.cpio.gz' file that was downloaded from Oracle. c. Cpio extract '10gr2_db_sol.cpio' into the 'database' subdirectory Chapter 2. Installing and configuring the prerequisite software 31

42 cd database cpio -idm < 10gr2_db_sol.cpio 5. Oracle Client folder setup: a. Within the oracle distribution directory you hae created, create a subdirectory called 'client'. b. Gunzip the '10gr2_client_sol.cpio.gz ' file that was downloaded from Oracle. c. Cpio extract '10gr2_client_sol.cpio' into the 'client' subdirectory: cd client cpio -idm < 10gr2_client_sol.cpio) Verify the required operating system packages The set of required Oracle packages ary by platform. About this task Before installing the Oracle serer, do the following: Make sure all the required Solaris packages and patches are installed on your system. All required packages and patches are specified in the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide. Verify the required operating system packages The set of required Oracle packages ary by platform. About this task Before installing the Oracle serer, do the following: Make sure all the required Solaris packages and patches are installed on your system. All required packages and patches are specified in the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide. On AIX systems Verify that your AIX system has all prerequisite packages and patches. Before you install Oracle on AIX systems, erify that your system meets the required release leel, as specified in the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide document. Before installing the Oracle serer, make sure all the required AIX packages and patches are installed on your system. All required packages and patches are specified in the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide document. On Linux systems Verify that your Linux system has all prerequisite packages and patches. Before you install Oracle on Linux systems, erify that your system meets the required release leel, and make sure all required Linux packages and patches are installed on your system. Release leel and all required packages and patches are specified in the IBM Tioli Netcool Performance Manager: Configuration 32 IBM Tioli Netcool Performance Manager: Installation Guide

43 Recommendations Guide. Run the Oracle serer configuration script In this step, you set up the Oracle enironment using the configure_ora script proided with the Tioli Netcool Performance Manager DataMart files on the Tioli Netcool Performance Manager distribution. About this task This script automatically creates the following configuration: Adds the dba and oinstall groups to /etc/group Adds the login name oracle, the primary group membership of which is dba and secondary group membership is oinstall, plus: The default login name created is oracle; howeer, you can set this to be any name of your choosing. ORACLE_BASE is set as the user home directory. If you would prefer to use a different home directory for the oracle user, create the oracle user manually before running configure_ora. Note: If.profile already exists and ORACLE_HOME has already been set, then the configure_ora script will not update it. If you are changing the alue of ORACLE_BASE or ORACLE_HOME, you must edit.profile manually to make these changes. Note: It is possible for you to create the oracle user manually, before running the configure_ora script, but this is not recommended. Oracle requires that certain attributes are set for the oracle user, if these attributes are not in place, errors may occur. Creates the Oracle directory structure. Creates startup and shutdown scripts for Oracle serer processes. To configure the Oracle installation enironment using the configure_ora script: 1. Log in as root. 2. Set the ORACLE_BASE enironment ariable to point to the top-leel directory where you want the Oracle serer files installed. The default installation directory is /opt/oracle. This can be set to any directory required by your organization. For example: # ORACLE_BASE=/opt/oracle # export ORACLE_BASE Note: The configure_ora script places this ariable into the oracle login account's.profile file. To check that the ariable is set correctly, enter the following command: # en grep ORA 3. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/instance AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX/instance Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/instance where: Chapter 2. Installing and configuring the prerequisite software 33

44 <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Run the Oracle configuration script by entering the following command: #./configure_ora The following screen is displayed: configure_ora Setting the Oracle enironment <Current Date> OS... : [ SunOS 5.10 Generic ] Host... : [ delphi ] Logname... : [ root ] ORACLE_BASE.. : [ /opt/oracle ] DBA group... : [ dba ] OUI Inentory group... : [ oinstall ] Oracle Software owner... : [ oracle ] Configure Oracle release.. : [ ] Menu : 1. Modify Oracle software owner. 2. Next supported release 3. Check enironment. 0. Exit Choice: 5. (Optional) To create a different name for the Oracle user other than the default oracle, type 1 and follow the instructions. Note: The Oracle user will be referred to as "oracle" for the remainder of this document. If you hae set the username to be a non-default string, that is, something other than "oracle", make sure to substitute your non- default string for each occurrence of "oracle" within any task description. 6. Type 3 at the Choice prompt and press Enter. The script creates the dba and oinstall groups and the ORACLE_BASE directory, unless they already exist: Checking enironment... Checking for group [ dba ] --> Created. Checking for group [ oinstall ] --> Created. Checking ORACLE_BASE ** WARNING ** ORACLE_BASE directory does not exist. ** [ /opt/oracle ] ** ** Create it? (n/y) y 7. Type y and press Enter. The script creates the /opt/oracle directory and continues as follows: Checking for user [ oracle ] ** WARNING ** User [ oracle ] does not exist. ** ** Create it locally? (n/y) y 8. Type y and press Enter. The script creates the oracle user and continues as follows: 34 IBM Tioli Netcool Performance Manager: Installation Guide

45 --> Created. Checking for oracle directory tree : [ /opt/oracle/product ] --> Created. [ /opt/oracle/product/ ] --> Created. [ /opt/oracle/product/10.2.0/dbs ] --> Created. [ /opt/oracle/admin ] --> Created. [ /opt/oracle/admin/skeleton ] --> Created. [ /opt/oracle/admin/skeleton/lib ] --> Ok. [ /opt/oracle/admin/skeleton/lib/libpmextc.so ] --> Created. [ /opt/oracle/admin/skeleton/lib/libmultitask.so ] --> Created. [ /opt/oracle/admin/skeleton/lib/libcmu.so ] --> Created. [ /opt/oracle/admin/skeleton/bin ] --> Ok. [ /opt/oracle/admin/skeleton/bin/snmptrap ] --> Created. [ /opt/oracle/local ] --> Created. Checking for oracle.profile file --> Created. Checking for dbora file --> Created. /etc/rc0.d/k10dbora link --> Created. /etc/rc1.d/k10dbora link --> Created. /etc/rc2.d/s99dbora link --> Created. Checking for dbora configuration files : /ar/opt/oracle/oratab --> Created. /ar/opt/oracle/lsnrtab --> Created. Press Enter to continue Press the Enter key to continue. The configure_ora main screen is refreshed. 10. Type 0 and press Enter to exit the configure_ora script. Note: You must set a password for the oracle login name (see Set a password for the Oracle login name on page 36). Structure created by the configure_ora script The configure_ora script creates the Oracle directory structure. The following example shows the directory structure created for Oracle, where ORACLE_BASE was set to /opt/oracle: /opt/oracle/product /opt/oracle/product/ /opt/oracle/product/10.2.0/dbs /opt/oracle/admin /opt/oracle/admin/skeleton /opt/oracle/admin/skeleton/bin /opt/oracle/local The script creates the following setup files: Solaris specific files: /etc/init.d/dbora, which starts the Oracle Listener and database serer automatically on each system boot Symbolic links to /etc/init.d/dbora in /etc/rc0.d, /etc/rc1.d, and /etc/rc2.d Oracle configuration files /ar/opt/oracle/oratab and lsnrtab. AIX specific files: /etc/inittab is modified to contain the dbstart and lsnrctl startup calls. /etc/rc.shutdown is modified to contain the dbshut and lsnrctl stop commands. Oracle configuration files /etc/oratab and /etc/lsnrtab. Note: AIX does not use init.d. Common files: Chapter 2. Installing and configuring the prerequisite software 35

46 A.profile file for the oracle user containing the following lines: # -- Begin Oracle Settings -- umask 022 ORACLE_BASE=/opt/oracle ORACLE_HOME=$ORACLE_BASE/product/ NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data LD_LIBRARY_PATH=$ORACLE_HOME/lib TNS_ADMIN=$ORACLE_HOME/network/admin PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpmextc.so export PATH ORACLE_BASE ORACLE_HOME NLS_LANG export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMIN export EXTPROC_DLLS # -- End Oracle Settings -- Note the following: The alue of ORACLE_HOME cannot contain soft links to other directories or filesystems. Be sure to specify the entire absolute path to Oracle. You will add the ORACLE_SID ariable to this file later, in Set the ORACLE_SID ariable on page 45. Set a password for the Oracle login name You must assign a password for the oracle login name to maintain system security. About this task The configure_ora script you ran in the preious section creates the oracle login name. You must assign a password for the oracle login name to maintain system security, and because subsequent installation steps expect the password to be already set. To set a password: 1. Log in as root. 2. Enter the following command: # passwd oracle 3. Enter and re-enter the password (oracle, by default) as prompted. The password is set. Run the pre-installation script The steps required to run the pre-installation script. About this task Note: If you are installing on a Solaris system, it is required that you hae already completed the tasks as described in Set the system parameters (Solaris only) on page 21 before continuing your Oracle serer installation on Solaris. Run the pre-installation script that erifies readiness to install Oracle: 1. Log in as root. 2. Change to the following directory: 36 IBM Tioli Netcool Performance Manager: Installation Guide

47 Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/instance/ora_installer where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Set the ORACLE_BASE enironment ariable. For example: # ORACLE_BASE=/opt/oracle # export ORACLE_BASE You must use the same ORACLE_BASE setting that you specified in Run the Oracle serer configuration script on page Enter the following command: #./pre_install_as_root The following messages indicate success: Checking that you are logged in as root --> Ok. Checking ORACLE_BASE --> Ok. Checking orainst.loc file --> Ok. If the script shows an error, correct the situation causing the error before proceeding to the next step. Run the rootpre.sh script (AIX only) To run the rootpre.sh script. 1. Log in as root or become superuser. 2. Set the DISPLAY enironment ariable. 3. Change to the directory /ar/tmp/oracle10201/database/rootpre. Note: The Oracle serer distribution is downloaded to /ar/tmp/oracle10201 as per the instructions in the section Downloading the Tioli Netcool Performance Manager distribution to disk on page Run the following command:./rootpre.sh rootpre.sh may return an error like the following: Configuring Asynchronous I/O... Asynchronous I/O is not installed on this system. This error can safely be ignored. Note: For more information on this Oracle error, see Oracle Metalink Article Chapter 2. Installing and configuring the prerequisite software 37

48 Verify PATH and enironment for the Oracle login name The steps required to erify PATH and Enironment for the Oracle Login Name. About this task Before proceeding to install Oracle serer files, make sure the /usr/ccs/bin directory is in the PATH enironment ariable for the oracle login name. To erify the PATH and enironment: 1. Log in as oracle. 2. Set and export the DISPLAY enironment ariable. If you are using the su command to become oracle, use a hyphen as the second argument so the oracle name's login enironment is loaded: # su - oracle 3. Verify that the enironment ariable ORACLE_BASE has been set by entering the following command: $ en grep ORA If the response does not include ORACLE_BASE=/opt/oracle, stop and make sure the.profile file was set for the oracle user as described in Run the Oracle serer configuration script on page To erify the path, enter the following command: $ echo $PATH The output should show that /usr/ccs/bin is part of the search path. For example: /usr/bin:/opt/oracle/product/10.2.0/bin:/usr/ccs/bin a. If the directory does not appear in the path, add it by entering the following commands: $ PATH=$PATH:/usr/ccs/bin $ export PATH Install Oracle There are two ways to install the Oracle database files. Using the menu-based script : The Oracle installation script proided by IBM is used to install Oracle serer, Oracle client, and to install upgrade patches. You should follow this step if you are not familiar with the Oracle installation process. Using batch mode on page 40: If you understand and are ery familiar with the Oracle installation process, use batch mode. Note: Choose one method, either the menu based script or the batch mode, do not implement both. Using the menu-based script The steps required to install the Oracle serer using the menu-based script. About this task To install the Oracle serer using the menu-based script: 38 IBM Tioli Netcool Performance Manager: Installation Guide

49 1. Log in as oracle. 2. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/instance/ora_installer where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Enter the following command to start the installer: $./perform_oracle_inst The installation menu is displayed: perform_oracle_inst Installation of oracle binaries <Current Date> OS... : [ SunOS 5.10 Generic ] Host... : [ delphi ] Logname... : [ oracle ] Install Oracle release... : [ ] Installation type... : [ Serer ] Enter the appropriate letter to modify the entries below: a) ORACLE_BASE.. : [ /opt/oracle ] b) ORACLE_HOME.. : [ /opt/oracle/product/ ] c) DBA group... : [ dba ] d) OUI Inentory group... : [ oinstall ] e) Oracle Software owner... : [ oracle ] f) Directory where CDs were copied: [ ] Menu : 1. Next supported release 2. Set install type to: Client 3. Perform install 0. Exit Choice : 4. Verify the following settings: The Oracle release number should be The Installation type field should be set to Serer. This field cycles between three settings: Serer, Client, and Patch. Type 2 at the Choice prompt and press Enter until Serer is displayed. 5. Type f at the Choice prompt and press Enter. 6. At the Choice prompt, enter the full path to the directory containing the installation files. For example: Choice: f Enter new alue for CD directory: /ar/tmp/oracle Edit other menu settings as required. Chapter 2. Installing and configuring the prerequisite software 39

50 For example, if you used non-default alues for ORACLE_BASE or ORACLE_HOME, enter your settings until the menu shows the correct information. 8. To begin the Oracle installation, type 3 at the Choice prompt and press Enter. The installation script checks the enironment, then asks whether you want to perform the installation. 9. Type Y at the Choice prompt and press Enter. The installation script starts installing Oracle and displays a series of status messages. Note: You can safely ignore: any "font.properties not found" messages in the output, or any Linux operating system prerequisite failure, as this relates to a problem with the Oracle Uniersal Installer. For more information on this problem with the Oracle Uniersal Installer, see the Oracle technote "Prerequisite Checks Fail When Installing 10.2 On Red Hat 5 (RHEL5) [ID ]". When the installation reaches the In Summary Page stage, the installation slows down significantly while Oracle files are copied and linked. 10. When the installation is complete, messages similar to the following are displayed: In End of Installation Page The installation of Oracle10 Database was successful. Please check /opt/oracle/orainentory/logs/silentinstall _ pm.log for more details. The Oracle installation has completed. Please check the messages aboe to determine if the install completed successfully. If you do not see successful completion messages, consult the install log at: /opt/oracle/orainentory/logs Press C to continue... Note: Write down the log file location to aid in troubleshooting if there is an installation error. 11. Type C and press Enter to return to the installation menu. 12. Type 0 and press Enter to exit the installation menu. Using batch mode Batch mode is the only Oracle installation method that lets you change the settings for the Oracle primary and secondary group names, and the name of the oracle user login, if you hae not used the default settings. About this task Note: The IBM-proided Oracle installation script is used to install Oracle serer, Oracle client, and to install upgrade patches to an existing Oracle serer or client installation. You should follow this step if you are familiar with the Oracle installation process because it is more efficient to install Oracle using batch mode. If you do not understand the Oracle installation process, use the menu-based script (see Install Oracle on page 38). If you installed the Oracle serer, Oracle client, or upgrade patches to the Oracle serer or Oracle client using the menu-based script, skip this step. To install Oracle using batch mode: 40 IBM Tioli Netcool Performance Manager: Installation Guide

51 1. Log in as oracle. 2. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/instance/ora_installer where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Open the perform_oracle_inst.ini file with a text editor. This file contains a number of Oracle installation settings similar to the following: # You can install either a serer install, # a client install or a patchset. To # install in batch mode you must enter a # alue. Uncomment the appropriate alue. # #ORA_TYPE=Serer #ORA_TYPE=Client #ORA_TYPE=Patch # # What is the directory where you copied the # Oracle install CD s. # INSTALL_DIRECTORY= # # Script will automatically use the # ORACLE_BASE defined in you enironment # or you can define it below. # #ORACLE_BASE= # # Script will automatically use the # ORACLE_HOME defined in you enironment # or you can define it below. # #ORACLE_HOME= # # What unix account is the oracle software # owner? A typical default is supplied. # ORA_USR_OWN=oracle # # What is the oracle dba unix group name? # A typical default is supplied. # ORA_GRP_DBA=dba # # What is the oracle oui unix group name? # A typical default is supplied. # ORA_GRP_OUI=oinstall 4. Make the necessary edits to the installation alues. You can uncomment lines already included in the file to use those alues for the installation. For example, uncomment the following line to install Oracle serer: ORA_TYPE=Serer Chapter 2. Installing and configuring the prerequisite software 41

52 5. Sae your edits and close the file. 6. Run the installation script with the b flag: $./perform_oracle_inst b The installation program erifies the alues and performs the installation as shown in the section for the menu-based installation (see Install Oracle on page 38). Run the root.sh script After successfully running an Oracle serer installation, you must run the root.sh script. About this task To run the root.sh script: 1. Log in as root or become superuser. 2. Change to the directory where Oracle files were installed. (This is the alue of the ORACLE_HOME enironment ariable as seen by the oracle login name.) For example: # cd /opt/oracle/product/ Run the following command:./root.sh Messages similar to the following are displayed: Running Oracle10 root.sh script... The following enironment ariables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /opt/oracle/product/ Enter the full pathname of the local bin directory: [/usr/local/bin]: 4. If the default entry, /usr/local/bin, is writable by root, press Enter to accept the default alue. The default entry might be NFS-mounted at your site so it can be shared among seeral workstations and therefore might be write-protected. If so, enter the location of a machine-specific alternate bin directory. (You might need to create this alternate directory at a shell prompt first.) For example, enter /usr/delphi/bin. 5. The script continues as follows:... Adding entry to /ar/opt/oracle/oratab file... Entries will be added to the /ar/opt/oracle/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will be performed. # 6. The script runs to completion with no further prompts. 42 IBM Tioli Netcool Performance Manager: Installation Guide

53 Install Oracle patches After you install Oracle, you must install the patchset for your ersion of Oracle to bring the Oracle ersion up to the IBM-alidated patch leel. About this task The basic patch required for Oracle 10g is patch ersion See the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide for up-to-date information about the required patches. In the interests of keeping this manual as short as possible, instructions proided by Oracle on how to perform an installation are not replicated within this manual. It is, howeer, recommended that before you complete this step that you obtain and read the upgrade instructions proided by Oracle for the patch that you wish to install. Your specific system may require supplementary steps not coered in this document, but which the Oracle instructions coer in detail. For example, if you are installing the Oracle patch on an AIX system, it is possible you may need to run the sbinclean command and execute the catpatch.sql and utlrp.sql SQL scripts as part of the upgrade procedure. Additional requirements might exist for other platforms. Note: Do not skip this step. Upgrade the Oracle ersion before you install the Tioli Netcool Performance Manager database structure. To install the Oracle patchset: 1. Log in as oracle. 2. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/instance/ora_installer where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Enter the following command to start the installer: $./perform_oracle_inst 4. Verify the following settings: The Oracle release number should be The Installation type field should be set to Patch. This field cycles between three settings: Serer, Client, and Patch. Type 2 at the Choice prompt and press Enter until Patch is displayed. 5. To specify the path, type f at the Choice prompt and press Enter. Chapter 2. Installing and configuring the prerequisite software 43

54 6. At the Choice prompt, enter the full path to the patch directory you created to hold the contents of the patch release (see Download the Oracle distribution and patch to disk on page 31). For example: Choice: f Enter new alue for CD directory: /ar/tmp/oracle To begin the upgrade installation, type 3 at the Choice prompt and press Enter. The installation script checks the enironment, then asks whether you want to perform the installation. 8. Type y at the Choice prompt and press Enter. The script proceeds to install the patch release files, showing a long series of messages much like the ones shown during installation of the base release. Note: You can safely ignore any "font.properties not found" messages in the output. In the messages, look for "success" notifications. If the script shows unsuccessful installation messages, check the installation log file specified in the message. Correct the error conditions identified in the log file, then rerun the patch installation and double-check all menu settings. 9. When the installation is complete, type C and press Enter. Note: The message telling you to press C might hae already scrolled past, because messages from seeral installation threads are written to the same screen. 10. Exit from the menu. Note: If you try to start Oracle as the database administrator (DBA) at this point, the startup will fail because the file initpv.ora does not yet exist. This file is created during the Tioli Netcool Performance Manager installation. 11. Carry out the steps as described in Run the root.sh script on page 42. This step is also required after an Oracle patch installation. Relax permissions on ORACLE_HOME When the install has finished, you must change permissions on the directories under ORACLE_HOME. About this task During the installation, Oracle sets ery restrictie permissions on ORACLE_HOME. Oracle proides a script that can be run after the install to relax permissions. To run the script: 1. Log in as oracle. 2. Change to the following directory: $ cd ORACLE_HOME/install. 3. Enter the following command to start the script: $./changeperm.sh 44 IBM Tioli Netcool Performance Manager: Installation Guide

55 Set the ORACLE_SID ariable A system identifier (SID) identifies each Oracle database instance for internal connectiity on the Oracle serer itself. (Connectiity from Oracle Clients to the serer is controlled by the TNS names system configured later.) The enironment ariable for the system identifier is ORACLE_SID. About this task Decide on an SID to use for your Tioli Netcool Performance Manager database instance. The assumed default for the Tioli Netcool Performance Manager installation is PV. IBM recommends using this default SID unless your site has established Oracle SID naming conentions. To set the ORACLE_SID enironment ariable: 1. Log in as oracle. 2. Open the.profile file with a text editor. 3. Add the following line anywhere between the Begin and End Oracle Settings comment lines: ORACLE_SID=PV; export ORACLE_SID For example: # -- Begin Oracle Settings -- umask 022 ORACLE_BASE=/opt/oracle ORACLE_HOME=$ORACLE_BASE/product/ ORACLE_SID=PV; export ORACLE_SID NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data LD_LIBRARY_PATH=$ORACLE_HOME/lib TNS_ADMIN=$ORACLE_HOME/network/admin PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/delphi/bin EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpmextc.so export PATH ORACLE_BASE ORACLE_HOME NLS_LANG export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMIN export EXTPROC_DLLS # -- End Oracle Settings Sae and exit the.profile file. 5. Enter the following shell command to actiate the change to your profile: $../.profile 6. Make sure the ariable was set by entering the following command: $ en grep ORACLE_SID Set automatic startup of the database instance You must configure your Oracle host to automatically start the Tioli Netcool Performance Manager database instance at system startup time. About this task To set up automatic startup: 1. Log in as oracle. 2. Depending on your operating system, change to the following directory: Chapter 2. Installing and configuring the prerequisite software 45

56 Solaris systems: $ cd /ar/opt/oracle AIX systems: $ cd /etc Linux Systems: $ cd /etc 3. Edit the oratab file with a text editor. The last line of this file looks like this example: *:/opt/oracle/product/10.2.0:n 4. Make the following edits to this line: Replace * with $ORACLE_SID (PV by default). Replace N with Y. The last line should now be: PV:/opt/oracle/product/10.2.0:Y 5. Sae and close the oratab file. Configure the Oracle listener How to configure the Oracle Listener. About this task Note: Instead of creating the listener.ora file manually, as described in the steps that follow, you can create it by running the Oracle Net Configuration Assistant utility. See the Oracle Corporation documentation for information about Net Configuration Assistant. The Oracle Listener process manages database connection requests from Oracle clients to an Oracle serer. To configure the Oracle Listener: 1. Log in as oracle. 2. Change to one of the following directories: $ cd $TNS_ADMIN or $ cd /opt/oracle/product/10.2.0/network/admin 3. Copy the sample listener.ora contained in the opt/oracle/admin/skeleton/ bin directory: $ cp /opt/oracle/admin/skeleton/bin/template.example_tnpm.listener.ora listener.ora Note: By Oracle conention, the keywords in this file are in uppercase but uppercase is not required. # listener.ora network configuration file in directory # /opt/oracle/product/10.2.0/network/admin LISTENER= (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = yourhost) (PORT = 1521)) ) 46 IBM Tioli Netcool Performance Manager: Installation Guide

57 (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC)) ) ) ) SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = /opt/oracle/product/10.2.0) (PROGRAM = extproc) ) (SID_DESC = (GLOBAL_DBNAME = PV.WORLD) (SID_NAME = PV) (ORACLE_HOME = /opt/oracle/product/10.2.0) ) ) 4. Using a text editor, change the following: a. Replace the string yourhost in the line (HOST = yourhost) with the name of your Oracle serer. Note: Specify the host using the hostname only, do not use the IP address. b. (optional) Replace the default port number 1521 in the line (PORT = 1521) with your required port number. c. Write and quit the file. 5. Depending on your operating system, change to the following directory: Solaris systems: $ cd /ar/opt/oracle AIX systems: $ cd /etc Linux Systems: $ cd /etc 6. Edit the lsnrtab file and add a line in the following format to the end of the file (after the initial comments): LISTENER:alue_of_ORACLE-HOME:Y For example: LISTENER:/opt/oracle/product/10.2.0:Y In this syntax, LISTENER is the name of the listener process. 7. Write and quit the file. 8. Test that the listener process works correctly by starting it manually using the following command: lsnrctl start (The lsnrctl command also accepts the stop and status arguments.) Look for a successful completion message. Chapter 2. Installing and configuring the prerequisite software 47

58 Configure the Oracle net client You must configure an Oracle Net client by setting up the TNS (Transport Network Substrate) serice names for your Tioli Netcool Performance Manager database instance. About this task To set up the TNS serice names: 1. Log in as oracle. 2. Change to one of the following directories: $ cd $TNS_ADMIN or $ cd /opt/oracle/product/10.2.0/network/admin 3. Create the sqlnet.ora file, which will manage Oracle network operations. You must create an sqlnet.ora file for both Oracle serer and Oracle client installations. Follow these steps: a. Copy the sample sqlnet.ora file, template.example_tnpm.sqlnet.ora, contained in the opt/oracle/admin/skeleton/bin/ directory: $ cp /opt/oracle/admin/skeleton/bin/template.example_tnpm.sqlnet.ora sqlnet.ora b. Add the following lines to this file: NAMES.DIRECTORY_PATH=(TNSNAMES) NAMES.DEFAULT_DOMAIN=WORLD For example: # sqlnet.ora network configuration file in # /opt/oracle/product/10.2.0/network/admin NAMES.DIRECTORY_PATH=(TNSNAMES) NAMES.DEFAULT_DOMAIN=WORLD Note: If you do not use WORLD as the DEFAULT_DOMAIN alue, make sure you enter the same alue for DEFAULT_DOMAIN in both sqlnet.ora and tnsnames.ora. c. Write and quit the file. 4. Create the tnsnames.ora file, which maintains the relationships between logical node names and physical locations of Oracle Serers in the network. You can do this by copying the existing sample file: cp /opt/oracle/admin/skeleton/bin/template.example_tnpm.tnsnames.ora tnsnames.ora Follow these steps: a. Enter lines similar to the following example, using the actual name of your Oracle serer in the HOST=delphi line and replacing {SID} with PV or your Oracle SID. # tnsnames.ora network configuration file in # /opt/oracle/product/10.2.0/network/admin # # The EXTPROC entry only needs to exist in the # tnsnames.ora file on the Oracle serer. # For Oracle client installations, tnsnames.ora # only needs the PV.WORLD entry. EXTPROC_CONNECTION_DATA.WORLD = (DESCRIPTION = (ADDRESS_LIST = 48 IBM Tioli Netcool Performance Manager: Installation Guide

59 (ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC) ) ) (CONNECT_DATA = (SID = PLSExtProc) (PRESENTATION = RO) ) ) PV.WORLD = (DESCRIPTION = (ENABLE=BROKEN) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = delphi) (PORT = 1521) ) ) (CONNECT_DATA = (SERVICE_NAME = PV.WORLD) (INSTANCE_NAME = PV) ) ) Note: Indents in this file must be presered. Note the following: You will use the alue in the INSTANCE_NAME field as the TNS entry when installing Tioli Netcool Performance Manager DataMart. IBM strongly recommends that you include the line (ENABLE=BROKEN) in the PV.WORLD entry, as shown in the example. This parameter setting preents CME processes from hanging in the eent that the CME is disconnected from the database before results are returned to the CME. If configuring tnsnames.ora for a serer installation, be sure to append the same domain suffix to all entries including EXTPROC_CONNECTION_DATA that you specified for the NAMES.DEFAULT_DOMAIN entry in the sqlnet.ora file. That is, append.world to each entry. b. Write and quit the file. 5. Test the Oracle Net configuration by entering a command with the following syntax: tnsping Net_serice_name.domain 10 For example: $ tnsping PV.WORLD 10 Look for successful completion messages (OK). To test without using the domain suffix, enter a command with the following syntax: tnsping Net_serice_name 10 For example: $ tnsping PV 10 Note: If either test is not successful, check your configuration and retest. Chapter 2. Installing and configuring the prerequisite software 49

60 Shut down of performance impacting Oracle jobs There are a few Oracle jobs that impact on performance, these are automatically shut down by the installation code. About this task It should be noted that the following Oracle jobs are automatically disabled by the installation code in order to maintain an acceptable leel of performance: GATHER_STATS_JOB: statistics gathering job. AUTO_SPACE_ADVISOR_JOB: auto space adisor maintenance job MGMT_CONFIG_JOB: Configuration collection job. MGMT_STATS_CONFIG_JOB: OCM Statistics collection job. It is recommended that these jobs should remain shut down. Installing the Oracle client Should you discern any impact to performance, please confirm that these jobs are not in operation. You must install Oracle client software on each system where you plan to install a Tioli Netcool Performance Manager component, with the exception of the system where you installed the Oracle serer. The instructions in this section contain information on installing the Oracle client software with the ersion patch. Ensure that the Oracle User is not in NIS The oracle user must be created locally, and must not be part of Network Information Serices (NIS). About this task The configure_ora script does not support oracle users who are part of NIS. If the oracle account is already in NIS, do the following: 1. On the system where the Oracle database is to be installed, disable NIS. For more information, see your operating system documentation. 2. Run the configure_ora script to create a local oracle account (see Run the Oracle serer configuration script on page 33). 3. Re-enable NIS. Note: The local Oracle account should be used before the NIS Oracle user. 50 IBM Tioli Netcool Performance Manager: Installation Guide

61 Download the Oracle distribution and patch to disk The process of downloading the Oracle distribution About this task To download the Oracle installation files to your target serer's hard disk: 1. Log in as root. 2. Create a directory to hold the contents of the Oracle distribution. For example: # mkdir /ar/tmp/oracle10201 # mkdir /ar/tmp/oracle Download the Oracle files to the /ar/tmp/oracle10201 directory. 4. Locate the appropriate upgrade patch file for your ersion of Oracle on the Oracle Web site and download it to your /ar/tmp/oracle10204 directory. 5. Unzip the oracle distribution files that now reside in the /ar/tmp/oracle10201 and /ar/tmp/oracle10204 directories. Before you proceed to the next step, make sure that you obtain the upgrade instructions proided by Oracle for the patch. The instructions contain information on performing steps required for the upgrade that are not documented in this guide. If you are installing the Oracle patch on an AIX system, you might need to run the sbinclean command and execute the catpatch.sql and utlrp.sql SQL scripts as part of the upgrade procedure. Additional requirements might exist for other platforms. See your database administrator to determine whether there are any company-specific requirements for installing Oracle in your enironment. If you hae downloaded Oracle using OTN If you hae downloaded the Oracle installation files using OTN there are a number of steps you must perform. About this task If you hae downloaded the Oracle installation files using OTN, you must do the following: 1. Log in as root. 2. Create a directory to contain your Oracle files. For example: # mkdir /ar/tmp/oracle Download your gzipped 'cpio' Oracle files to this directory. 4. Oracle Serer folder setup: a. Within the oracle distribution directory you hae created, create a subdirectory called 'database'. b. Gunzip the '10gr2_db_sol.cpio.gz' file that was downloaded from Oracle. c. Cpio extract '10gr2_db_sol.cpio' into the 'database' subdirectory cd database cpio -idm < 10gr2_db_sol.cpio 5. Oracle Client folder setup: a. Within the oracle distribution directory you hae created, create a subdirectory called 'client'. Chapter 2. Installing and configuring the prerequisite software 51

62 b. Gunzip the '10gr2_client_sol.cpio.gz ' file that was downloaded from Oracle. c. Cpio extract '10gr2_client_sol.cpio' into the 'client' subdirectory: cd client cpio -idm < 10gr2_client_sol.cpio) Run the Oracle client configuration script The Oracle client configuration script is a shell script that creates the enironment for the client software installation on the local system. About this task This script is named configure_client and is located with the Tioli Netcool Performance Manager files that you obtained in Downloading the Tioli Netcool Performance Manager distribution to disk on page 26. If you are performing this step as part of an upgrade procedure, make sure that you run the configuration script proided with the target ersion of Tioli Netcool Performance Manager. The client configuration script makes the following changes to the local system: Adds the dba and oinstall groups to /etc/group. Adds the Solaris login name oracle, whose primary group membership is dba, and secondary group membership is oinstall. Creates the Oracle client directory structure. When you create the enironment for patch ersion , the default location for this directory structure is $ORACLE_BASE/product/ You specify this directory as the target location when you install the Oracle client. To configure the Oracle installation enironment: 1. Log in as root. 2. Set the ORACLE_BASE enironment ariable to point to the top-leel directory where you want the Oracle client files installed. The default installation directory is /opt/oracle. For example: # ORACLE_BASE=/opt/oracle # export ORACLE_BASE Note: The configure_client script places this ariable into the oracle login name's.profile file. To check that the ariable is set correctly, enter the following command: # en grep ORA 3. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/instance AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX/instance Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/instance where: 52 IBM Tioli Netcool Performance Manager: Installation Guide

63 <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Run the Oracle configuration script using the following command: #./configure_client The following screen is displayed: configure_client Setting the Oracle client enironment <Current Date> OS... : [ SunOS 5.10 Generic ] Host... : [ corinth ] Logname... : [ root ] ORACLE_BASE.. : [ /opt/oracle ] DBA group... : [ dba ] OUI Inentory group... : [ oinstall ] Oracle Software owner... : [ oracle ] Configure Oracle release.. : [ ] Menu : 1. Modify Oracle software owner. 2. Next supported release. 3. Check enironment. 4. Add client support. 0. Exit Choice: 5. (Optional) To create a different name for the Oracle user other than the default oracle, type 1 and follow the instructions. Note: The Oracle user will be referred to as "oracle" for the remainder of this document. If you hae set the username to be a non-default string, that is, something other than "oracle", make sure to substitute your non- default string for each occurance of "oracle" within any task description. 6. Type 3 at the Choice prompt and press Enter. The script creates the dba and oinstall groups, and the ORACLE_BASE directory, unless they already exist. Checking enironment... Checking for group [ dba ] --> Created. Checking for group [ oinstall ] --> Created. Checking ORACLE_BASE ** WARNING ** ORACLE_BASE directory does not exist. ** [ /opt/oracle ] ** ** Create it? (n/y) y If prompted, type y and press Enter. The script creates the /opt/oracle directory and continues as follows: Checking for user [ oracle ] ** WARNING ** User [ oracle ] does not exist. ** ** Create it locally? (n/y) y If prompted, type y to create the oracle user and press Enter. The script creates the oracle user and continues as follows: Chapter 2. Installing and configuring the prerequisite software 53

64 --> Created. Checking for oracle directory tree : [ /opt/oracle/product ] --> Created. [ /opt/oracle/product ] --> Created. [ /opt/oracle/product/9.2.0 ] --> Created. Checking for oracle.profile file --> Created. Press Enter to continue Press Enter to continue. The configure_client main screen is displayed. 8. Type 0 and press Enter to exit the script. Set a password for the Oracle login name You must assign a password for the oracle login name to maintain system security. About this task The configure_ora script you ran in the preious section creates the oracle login name. You must assign a password for the oracle login name to maintain system security, and because subsequent installation steps expect the password to be already set. To set a password: 1. Log in as root. 2. Enter the following command: # passwd oracle 3. Enter and re-enter the password (oracle, by default) as prompted. The password is set. Run the pre-installation script The steps required to run the pre-installation script. About this task Note: If you are installing on a Solaris system, it is required that you hae already completed the tasks as described in Set the system parameters (Solaris only) on page 21 before continuing your Oracle serer installation on Solaris. Run the pre-installation script that erifies readiness to install Oracle: 1. Log in as root. 2. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/instance/ora_installer where: 54 IBM Tioli Netcool Performance Manager: Installation Guide

65 <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Set the ORACLE_BASE enironment ariable. For example: # ORACLE_BASE=/opt/oracle # export ORACLE_BASE You must use the same ORACLE_BASE setting that you specified in Run the Oracle serer configuration script on page Enter the following command: #./pre_install_as_root The following messages indicate success: Checking that you are logged in as root --> Ok. Checking ORACLE_BASE --> Ok. Checking orainst.loc file --> Ok. If the script shows an error, correct the situation causing the error before proceeding to the next step. Verify PATH and enironment for the Oracle login name The steps required to erify PATH and Enironment for the Oracle Login Name. About this task Before proceeding to install Oracle serer files, make sure the /usr/ccs/bin directory is in the PATH enironment ariable for the oracle login name. To erify the PATH and enironment: 1. Log in as oracle. 2. Set and export the DISPLAY enironment ariable. If you are using the su command to become oracle, use a hyphen as the second argument so the oracle name's login enironment is loaded: # su - oracle 3. Verify that the enironment ariable ORACLE_BASE has been set by entering the following command: $ en grep ORA If the response does not include ORACLE_BASE=/opt/oracle, stop and make sure the.profile file was set for the oracle user as described in Run the Oracle serer configuration script on page To erify the path, enter the following command: $ echo $PATH The output should show that /usr/ccs/bin is part of the search path. For example: /usr/bin:/opt/oracle/product/10.2.0/bin:/usr/ccs/bin a. If the directory does not appear in the path, add it by entering the following commands: $ PATH=$PATH:/usr/ccs/bin $ export PATH Chapter 2. Installing and configuring the prerequisite software 55

66 Install the Oracle client The Oracle installation script is a shell script that you can use to install the Oracle serer, Oracle client software, or patches to existing installations of the Oracle serer and client. About this task This script is named perform_oracle_inst and is located with the Tioli Netcool Performance Manager files that you obtained in Downloading the Tioli Netcool Performance Manager distribution to disk on page 26. This script is proided by IBM as part of the Tioli Netcool Performance Manager installation package. An Oracle client installation is not usable until the following Net configuration files are configured and installed: tnsnames.ora sqlnet.ora You will configure these files in later steps. To install the Oracle client: 1. Log in as oracle. 2. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/instance/ora_installer where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Enter the following command to start the installer: $./perform_oracle_inst The installation menu is displayed: 56 IBM Tioli Netcool Performance Manager: Installation Guide

67 perform_oracle_inst Installation of oracle binaries <Current Date> OS... : [ SunOS 5.10 Generic ] Host... : [ delphi ] Logname... : [ oracle ] Install Oracle release... : [ ] Installation type... : [ Client ] Enter the appropriate letter to modify the entries below: a) ORACLE_BASE.. : [ /opt/oracle ] b) ORACLE_HOME.. : [ /opt/oracle/product/ ] c) DBA group... : [ dba ] d) OUI Inentory group... : [ oinstall ] e) Oracle Software owner... : [ oracle ] f) Directory where CDs were copied: [ ] Menu : 1. Next supported release 2. Set install type to: Client 3. Perform install 0. Exit Choice : 4. Enter f at the Choice prompt and press Enter. 5. Enter the full path to the directory you created to hold the Oracle distribution in Download the Oracle distribution and patch to disk on page 31. For example: Choice: f Enter new alue for CD directory: /ar/tmp/oracle Edit any other menu settings as necessary. Make sure that the alues for ORACLE_BASE and ORACLE_HOME correspond to the locations you specified when you ran the Oracle client configuration script. 7. To start the Oracle installation, type 3 at the Choice prompt and press Enter. 8. The installation script checks the enironment, then asks whether you want to perform the installation. Type Y at the Choice prompt and press Enter. The installation script starts installing Oracle and displays a series of status messages. Note: You can safely ignore any "font.properties not found" messages in the output. When the installation reaches the In Summary Page stage, the installation slows down significantly while Oracle files are copied and linked. 9. When the installation process completes, the installation displays a success message. Write down the log file location to aid in troubleshooting if there is an installation error. 10. Type C and press Enter to return to the installation menu. 11. Type 0 and press Enter to exit the installation menu. 12. Perform the steps in Run the root.sh script on page 42. Chapter 2. Installing and configuring the prerequisite software 57

68 Run the root.sh script After successfully running an Oracle serer installation, you must run the root.sh script. About this task To run the root.sh script: 1. Log in as root or become superuser. 2. Change to the directory where Oracle files were installed. (This is the alue of the ORACLE_HOME enironment ariable as seen by the oracle login name.) For example: # cd /opt/oracle/product/ Run the following command:./root.sh Messages similar to the following are displayed: Running Oracle10 root.sh script... The following enironment ariables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /opt/oracle/product/ Enter the full pathname of the local bin directory: [/usr/local/bin]: 4. If the default entry, /usr/local/bin, is writable by root, press Enter to accept the default alue. The default entry might be NFS-mounted at your site so it can be shared among seeral workstations and therefore might be write-protected. If so, enter the location of a machine-specific alternate bin directory. (You might need to create this alternate directory at a shell prompt first.) For example, enter /usr/delphi/bin. 5. The script continues as follows:... Adding entry to /ar/opt/oracle/oratab file... Entries will be added to the /ar/opt/oracle/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will be performed. # 6. The script runs to completion with no further prompts. Install Oracle patches After you install the Oracle client software, you must install patch ersion About this task In the interests of keeping this manual as short as possible, instructions proided by Oracle on how to perform an installation are not replicated within this manual. It is, howeer, recommended that before you complete this step that you obtain and read the upgrade instructions proided by Oracle for the patch that you wish to install. 58 IBM Tioli Netcool Performance Manager: Installation Guide

69 Your specific system may require supplementary steps not coered in this document, but which the Oracle instructions coer in detail. For example, if you are installing the Oracle patch on an AIX system, it is possible you may need to run the sbinclean command and execute the catpatch.sql and utlrp.sql SQL scripts as part of the upgrade procedure. Additional requirements might exist for other platforms. Note: Do not skip this step. Upgrade the Oracle ersion before you install the Tioli Netcool Performance Manager database structure. To install the Oracle patchset: 1. Follow the instructions to run the perform_oracle_inst script, as shown in Install Oracle patches on page 43. Go through the menus as described in that section, with the following changes: a. Enter 2 at the Choice prompt and press Enter until the Installation type field is set to Patch. b. Type f at the Choice prompt and press Enter. c. At the Choice prompt, type the full path to the patch directory you created in Download the Oracle distribution and patch to disk on page 31 to hold the client patch contents. For example: Choice: f Enter new alue for CD directory: /ar/tmp/oracle Type 3 at the Choice prompt and press Enter. The script checks the enironment and displays a series of messages. 3. Type y at the Choice prompt and press Enter to begin the patch installation. The script proceeds to install the patch release files, showing a series of messages much like the ones shown during installation of the base release. Note: You can safely ignore any "font.properties not found" messages in the output. 4. Watch the script's messages for success entries. Note: If the script shows unsuccessful installation messages, check the installation log file named in the message. Correct the error conditions identified in the log file, then rerun the patch installation and double-check all menu settings. 5. At the Choice prompt, type C and press Enter to continue. The message telling you to press C may hae already scrolled past, because messages from seeral installation threads are written to the same screen. If the installation has paused, type C to continue.relax Permissions on ORACLE_HOME Chapter 2. Installing and configuring the prerequisite software 59

70 Relax permissions on ORACLE_HOME When the install has finished, you must change permissions on the directories under ORACLE_HOME. About this task During the installation, Oracle sets ery restrictie permissions on ORACLE_HOME. Oracle proides a script that can be run after the install to relax permissions. To run the script: 1. Log in as oracle. 2. Change to the following directory: $ cd ORACLE_HOME/install. 3. Enter the following command to start the script: $./changeperm.sh Configure the Oracle net client You must configure the Oracle Net client by setting up the TNS (Transport Network Substrate) serice names for your Tioli Netcool Performance Manager database instance. About this task Next, you configure the Oracle Net client by setting up the TNS (Transport Network Substrate) serice names for your Tioli Netcool Performance Manager database instance. You must perform this step for each instance of the Oracle client software that you installed on the system. You must configure sqlnet.ora and tnsnames.ora files for both Oracle serer and Oracle client installations. Howeer, the tnsnames.ora file for client installations should not hae the EXTPROC_CONNECTION_DATA section. If you are installing DataView and one or more other Tioli Netcool Performance Manager components on the same system, you must make sure that the tnsnames.ora and sqlnet.ora files for each set of client software are identical. The easiest way to do this is to create these files when you are configuring the first client instance for Net and then to copy it to the corresponding directory when you configure the second instance. Create the sqlnet.ora file The sqlnet.ora file manages Oracle network operations. You can create a new sqlnet.ora file, or FTP the file from your Oracle serer. About this task To set up the TNS serice names: 1. Log in as oracle. 2. Change to the following directory: $ cd $ORACLE_HOME/network/admin 3. To create the sqlnet.ora file, FTP the following file from your Oracle serer: 60 IBM Tioli Netcool Performance Manager: Installation Guide

71 /opt/oracle/admin/skeleton/bin/template.example_tnpm.sqlnet.ora 4. Add the following lines to it: NAMES.DIRECTORY_PATH=(TNSNAMES) NAMES.DEFAULT_DOMAIN=WORLD For example: # sqlnet.ora network configuration file in # /opt/oracle/product/10.2.0/network/admin NAMES.DIRECTORY_PATH=(TNSNAMES) NAMES.DEFAULT_DOMAIN=WORLD Note: If you do not use WORLD as the DEFAULT_DOMAIN alue, make sure you enter the same alue for DEFAULT_DOMAIN in both sqlnet.ora and tnsnames.ora. 5. Write and quit the sqlnet.ora file. Create the tnsnames.ora file The tnsnames.ora file maintains the relationships between logical node names and physical locations of Oracle serers in the network. About this task You can create a new tnsnames.ora file, or FTP the file from your Oracle serer. To create the tnsnames.ora file: 1., FTP the following file from your Oracle serer: /opt/oracle/admin/skeleton/bin/template.example_tnpm.tnsnames.ora 2. Add the following lines: # tnsnames.ora network configuration file in # /opt/oracle/product/10.2.0/network/admin # # For Oracle client installations, tnsnames.ora # only needs the PV.WORLD entry. PV.WORLD = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = yourhost) (PORT = 1521) ) ) (CONNECT_DATA = (SERVICE_NAME = PV.WORLD) (INSTANCE_NAME = PV) ) ) Note: Indents in this file must be presered. 3. Replace the string yourhost in the line (HOST = yourhost) with the name of your Oracle serer. Note the following: You will use the alue in the INSTANCE_NAME field as the TNS entry when installing DataMart. Chapter 2. Installing and configuring the prerequisite software 61

72 If you reconfigure the Oracle client to connect to a different Oracle database in another Tioli Netcool Performance Manager installation, be sure you update the HOST entry in the tnsnames.ora file, then restart the Oracle client. Specify the host using the hostname only, do not use the IP address. 4. (optional) Replace the default port number 1521 in the line (PORT = 1521) with your required port number. 5. Write and quit the file. Test the Oracle net configuration The steps required to test the Oracle Net configuration. About this task To test the Oracle Net configuration: 1. Log in as oracle. 2. Enter a command with the following syntax: tnsping Net_serice_name 10 For example: tnsping PV.WORLD Test again, using the same Net instance name without the domain suffix: tnsping PV 10 Look for successful completion messages (OK). Next steps The steps that follow installation of the prerequisite software. Once you hae installed the prerequisite software, you are ready to begin the actual installation of Tioli Netcool Performance Manager. Depending on the type of installation you require, follow the directions in the appropriate chapter: Chapter 4, Installing as a minimal deployment, on page 89 - Describes how to install Tioli Netcool Performance Manager in a distributed production enironment. Chapter 5, Modifying the current deployment, on page 95 - Describes how to install Tioli Netcool Performance Manager as a minimal deployment, which is used primarily for demonstration or ealuation purposes. If you are planning on Installing Tioli Netcool Performance Manager as a distributed enironment that uses clustering for high aailability, please reiew the Tioli Netcool Performance Manager HA (High Aailability) documentation, which is aailable for download by going to brandcatalog/opal/ and searching for "Netcool Proiso HA Documentation". 62 IBM Tioli Netcool Performance Manager: Installation Guide

73 Chapter 3. Installing in a distributed enironment This section describes how to install Tioli Netcool Performance Manager for the first time in a fresh, distributed enironment. For information about installing the Tioli Netcool Performance Manager components using a minimal deployment, see Chapter 4, Installing as a minimal deployment, on page 89. Distributed installation process The mains steps inoled in a distributed installation. A production Tioli Netcool Performance Manager system that generates and produces management reports for a real-world network is likely to be installed on seeral serers. Tioli Netcool Performance Manager components can be installed to run on as few as two or three serers, up to dozens of serers. Copyright IBM Corp. 2006,

74 Before installing Tioli Netcool Performance Manager, you must hae installed the prerequisite software. For detailed information, see Chapter 2, Installing and configuring the prerequisite software, on page 13. In addition, you must hae decided how you want to configure your system. Refer to the following sections: Co-location rules on page 2 Typical installation topology on page 8 Appendix A, Remote installation issues, on page 137 The general steps used to install Tioli Netcool Performance Manager are as follows: Start the launchpad. Install the Topology Editor. Start the Topology Editor. Create the topology. 64 IBM Tioli Netcool Performance Manager: Installation Guide

75 Add the Tioli Netcool Performance Manager components. Sae the topology to an XML file. Start the deployer. Install Tioli Netcool Performance Manager using the deployer. Starting the Launchpad The following sections describe each of these steps in detail. Note: Before you start the installation, erify that all the database tests hae been performed. Otherwise, the installation might fail. See Chapter 2, Installing and configuring the prerequisite software, on page 13 for information about tnsping. The steps required to start the launchpad. About this task To start the launchpad: 1. Log in as root. 2. Set and export the DISPLAY ariable (see Setting up a remote X Window display on page 14). 3. Set and export the BROWSER ariable to point to your Web browser. For example: On Solaris systems: # BROWSER=/opt/mozilla/mozilla # export BROWSER On AIX systems: # BROWSER=/usr/mozilla/firefox/firefox # export BROWSER On Linux systems: # BROWSER=/usr/bin/firefox # export BROWSER Note: The BROWSER command cannot include any spaces around the equal sign. 4. Change directory to the directory where the launchpad resides. On Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS On AIX systems: # cd <DIST_DIR>/proiso/AIX On Linux systems: # cd <DIST_DIR>/proiso/RHEL <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Enter the following command to start the launchpad: #./launchpad.sh Chapter 3. Installing in a distributed enironment 65

76 Installing the Topology Editor The steps required to install the Topology Editor. About this task Only one instance of the Topology Editor can exist in the Tioli Netcool Performance Manager enironment. Install the Topology Editor on the same system that will host database serer. You can install the Topology Editor from the launchpad or from the command line. To install the Topology Editor: 1. You can begin the Topology Editor installation procedure from the command line or from the Launchpad. From the launchpad: a. On the launchpad, click the Install Topology Editor option in the list of tasks. b. On the Install Topology Editor page, click the Install Topology Editor link. From the command line: a. Log in as root. b. Change directory to the directory that contains the Topology Editor installation script: On Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/Install/SOL10/topologyEditor/Disk1/InstData/VM On AIX systems: # cd <DIST_DIR>/proiso/AIX/Install/topologyEditor/Disk1/InstData/VM On Linux systems: # cd <DIST_DIR>/proiso/RHEL/Install/topologyEditor/Disk1/InstData/VM <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page 26 c. Enter the following command: #./installer.bin 2. The installation wizard opens in a separate window, displaying a welcome page. Click Next. 3. Reiew and accept the license agreement, then click Next. 4. Confirm the wizard is pointing to the correct directory. The default is /opt/ibm/proiso. If you hae preiously installed the Topology Editor on this system, the installer does not prompt you for an installation directory and instead uses the directory where you last installed the application. 5. Click Next to continue. 6. Confirm the wizard is pointing to the correct base installation directory of the Oracle JDBC drier (/opt/oracle/product/ersion/jdbc/lib), or click Choose to naigate to another directory. 7. Click Next to continue. 8. Reiew the installation information, then click Run. 9. When the installation is complete, click Done to close the wizard. 66 IBM Tioli Netcool Performance Manager: Installation Guide

77 The installation wizard installs the Topology Editor and an instance of the deployer in the following directories: Interface Directory Topology Editor install_dir/topologyeditor For example: /opt/ibm/proiso/topologyeditor Deployer install_dir/deployer For example: /opt/ibm/proiso/deployer Starting the Topology Editor The combination of the Topology Editor and the deployer is referred to as the primary deployer. For more information, see Resuming a partially successful first-time installation on page 87. Note: To uninstall the Topology Editor, follow the instructions in Uninstalling the topology editor on page 133. Do not delete the /opt/ibm directory. Doing so will cause problems when you try to reinstall the Topology Editor. If the /opt/ibm directory is accidentally deleted, perform the following steps: a. Change to the /ar directory. b. Rename the hidden file.com.zerog.registry.xml (for example, rename it to.com.zerog.registry.xml.backup). c. Reinstall the Topology Editor. d. Rename the backup file to the original name (.com.zerog.registry.xml). After you hae installed the Topology Editor, you can inoke it from either the launchpad or from the command line. To start the Topology Editor from the launchpad: 1. If the Install Topology Editor page is not already open, click the Install Topology Editor option in the list of tasks to open it. 2. On the Install Topology Editor page, click the Start Topology Editor link. To start the Topology Editor from the command line: 1. Log in as root. 2. Change directory to the directory in which you installed the Topology Editor. For example: # cd /opt/ibm/proiso/topologyeditor 3. Enter the following command: #./topologyeditor Note: If your DISPLAY enironment ariable is not set, the Topology Editor will fail with a Jaa assertion message (core dump). Chapter 3. Installing in a distributed enironment 67

78 Creating a new topology The steps required to create a new topology. 1. In the Topology Editor, select Topology > Create new topology. The New Topology window is displayed. 2. Enter the Number of resources to be managed by Tioli Netcool Performance Manager. The default alue is The size of your deployment affects the database sizing. 3. Click Finish. The Topology Editor creates the following entities: In the Logical iew, fie items are listed: Tioli Netcool Performance Manager Topology, Cross Collector CMEs, DataChannels, DataMarts and Tioli Integrated Portals. In the Physical iew, there is a new Hosts folder. Adding and configuring the Tioli Netcool Performance Manager components Your next step is to add and configure the indiidual Tioli Netcool Performance Manager components. Add the hosts The first step is to specify all the serers that will host Tioli Netcool Performance Manager components. About this task Each host that you define has an associated property named PV User. PV User is the default operating system user for all Tioli Netcool Performance Manager components. You can oerride this setting in the Adanced Properties tab when you set the deployment properties for indiidual components (for example, DataMart and DataView). This allows you to install and run different components on the same system as different users. Note: DataChannel components always use the default user associated with the host. The user account used to transfer files using FTP or SCP/SFTP during installation is always the PV User defined at the host leel, rather than component leel. To add a single host to the topology: 1. In the Physical iew, right-click the Hosts folder and select Add Host from the menu. The Add Host window opens. 2. Specify the details for the host machine. The fields are as follows: 68 IBM Tioli Netcool Performance Manager: Installation Guide

79 Host name - Enter the name of the host (for example, delphi). Operating system - Specifies the operating system (for example, SOLARIS). This field is filled in for you. Oracle home - Specifies the default ORACLE_HOME directory for all Tioli Netcool Performance Manager components installed on the system (by default, /opt/oracle/product/10.2.0). PV User - Specifies the default Tioli Netcool Performance Manager Unix user (for example, puser) for all Tioli Netcool Performance Manager components installed on the system. PV user password - Specifies the password for the default Tioli Netcool Performance Manager user (for example, PV). Create Disk Usage Serer for this Host? - Selecting this check box creates a DataChannel subcomponent to handle disk quota and flow control. If you hae not chosen to create a Disk Usage Serer, Click Finish to create the host. The Topology Editor adds the host under the Hosts folder in the Physical iew. If you hae chosen to create a Disk Usage Serer, click Next and the Add Host window will allow you to add details for your Disk Usage Serer. 3. Specify the details for the Disk Usage Serer. The fields are as follows: Local Root Directory - The local DataChannel root directory. This property allows you to differentiate between a local directory and a remote directory mounted to allow for FTP access. Remote Root Directory - Remote directory mounted for FTP access. This property allows you to differentiate between a local directory and a remote directory mounted to allow for FTP access. FC FSLL - This is the Flow Control Free Space Low Limit property. When this set limit is reached the Disk Usage Serer will contact all components who reside in this root directory and tell them to free up all space possible. FC QUOTA - This is the Flow Control Quota property. This property allows you to set the amount of disk space in bytes aailable to Tioli Netcool Performance Manager components on this file system. Remote User - User account used when attempting to access this Disk Usage Serer remotely. Remote User Password - User account password used when attempting to access this Disk Usage Serer remotely. Secure file transfer to be used - Boolean indicator identifying if ssh should be used when attempting to access this directory remotely. Port Number - Port number to use for remote access (sftp) in case it is a non default port. Click Finishto create the host. The Topology Editor adds the host under the Hosts folder in the Physical iew. Note: The DataChannel properties will be filled in automatically at a later stage. Adding multiple hosts You may wish to add multiple hosts at one time. About this task To add multiple hosts to the topology: Chapter 3. Installing in a distributed enironment 69

80 1. In the Physical iew, right-click the Hosts folder and select Add Multiple Host from the menu. The Add Multiple Hosts window opens. 2. Add new hosts by typing their names into the Host Name field as a comma separated list. 3. Click Next. 4. Configure all added hosts. The Configure hosts dialog allows you to enter configuration settings and apply these settings to one or more of the specified host set. To apply configuration settings to one or more of the specified host set: a. Enter the appropriate host configuration alues. All configuration options are described in Steps 2, and 3 of the preious process, Add the hosts on page 68. b. Select the check box opposite each of the hosts to which you want to apply the entered alues. c. Click Next. The hosts for which all configuration settings hae been specified disappear from the set of selectable hosts. d. Repeat steps a, b and c till all hosts are configured. 5. Click Finish. Add a database configurations component The Database Configurations component hosts all the database-specific parameters. About this task You define the parameters once, and their alues are propagated as needed to the underlying installation scripts. To add a Database Configurations component: 1. In the Logical iew, right-click the Tioli Netcool Performance Manager Topology component and select Add Database Configurations from the menu. The host selection window opens. 2. You must add the Database Configuration component to the same serer that hosts the Oracle serer (for example, delphi). Select the appropriate host using the drop-down list. Note: The operating system of the host where you configure the Database Configurations component determines the main platform for the entire Tioli Netcool Performance Manager deployment. This means that you should install all the other main components (DataView, DataMart, DataChannel and Tioli Integrated Portal) on machines with the same operating system. The Topology Editor enforces this constraint by listing only those hosts with the same operating system used to host the database. 3. Click Next to configure the mount points for the database. 4. Add the correct number of mount points. To add a new mount point, click Add Mount Point. A new, blank row is added to the window. Fill in the fields as appropriate for the new mount point. 5. Enter the required configuration information for each mount point. a. Enter the mount point location: 70 IBM Tioli Netcool Performance Manager: Installation Guide

81 Mount Point Directory Name (for example, /raid_2/oradata) Note: The mount point directories can be named using any string as required by your organizations naming standards. Used for Metadata Tablespaces? (A check mark indicates True.) Used for Temporary Tablespaces? (A check mark indicates True.) Used for Metric Tablespaces? (A check mark indicates True.) Used for System Tablespaces and Redo? (A check mark indicates True.) b. Click Back to return to the original page. c. Click Finish to create the component. The Topology Editor adds the new Database Configurations component to the Logical iew. 6. Highlight the Database Configurations component to display its properties. Reiew the property alues to make sure they are alid. For the complete list of properties for this component, see the IBM Tioli Netcool Performance Manager: Property Reference Guide. The Database Configurations component has the following subelements: Channel tablespace configurations Database Channels Database Clients configurations Tablespace configurations Temporary tablespace configurations Note: Before you actually install Tioli Netcool Performance Manager, erify that both the raid_2/oradata and raid_3/oradata directory structures hae been created, and that the oradata subdirectories are owned by oracle:dba. Add a DataMart The steps required to add a DataMart component to your topology. About this task Tioli Netcool Performance Manager DataMart is normally installed on the same serer on which you installed Oracle serer and the Tioli Netcool Performance Manager database configuration. Howeer, there is no requirement that forces DataMart to reside on the database serer. Note the following: If you are installing DataMart on an AIX system or any remote AIX, Linux or Solaris system, you must add the IBM JRE to the PATH enironment ariable for the Tioli Netcool Performance Manager Unix user, puser. You must ensure you are using the IBM JRE and not the RHEL JRE. The IBM JRE is supplied with the Topology Editor or with Tioli Integrated Portal. To ensure you are using the right JRE you can either: Set the JRE path to conform to that used by the Topology Editor, do this using the following commands (using the default location for the primary deployer): PATH=/opt/IBM/proiso/topologyEditor/jre/bin:$PATH export $PATH For a remote serer, that is one that does not host the primary deployer, you must download and install the required JRE, and set the correct JRE path. See Chapter 3. Installing in a distributed enironment 71

82 the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide document for JRE download details. To add a DataMart component: 1. In the Logical iew, right-click the DataMarts folder and select Add DataMart from the menu. The host selection host window is displayed. 2. Using the drop-down list of aailable hosts, select the machine on which DataMart should be installed (for example, delphi). 3. Click Finish. The Topology Editor adds the new DataMart x component (for example, DataMart 1) under the DataMarts folder in the Logical iew. 4. Highlight the DataMart x component to display its properties. Reiew the property alues to make sure they are alid. You can specify an alternate installation user for the DataMart component by changing the alues of the USER_LOGIN and USER_PASSWORD properties in the Adanced Properties tab. For the complete list of properties for this component, see the IBM Tioli Netcool Performance Manager: Property Reference Guide. Eent notification scripts When you install the DataMart component, two eent notification scripts are installed. The scripts are called as needed by tablespace size checking routines in Oracle and in Tioli Netcool Performance Manager, if either routine detects low disk space conditions on a disk partition hosting a portion of the Tioli Netcool Performance Manager database. Both scripts by default send their notifications by to a local login name. The two files and their installation locations are as follows: The script installed as $ORACLE_BASE/admin/$ORACLE_SID/bin/notifyDBSpace notifies the login name oracle by of impending database space problems. This script is called as needed by an Oracle routine that periodically checks for aailable disk space. The script installed as /opt/datamart/bin/notifydbspace notifies the login name puser of the same condition. This script is called as needed by the Hourly Loader component of Tioli Netcool Performance Manager DataChannel. The loader checks for aailable disk space before attempting its hourly upload of data to the database. Either file can be customized to send its warnings to a different address on the local machine, to an SMTP serer for transmission to a remote machine, or to send the notices to the local network's SNMP fault management system (that is, to an SNMP trap manager). You can modify either script to send notifications to an SNMP trap, instead of, or in addition to its default notification. 72 IBM Tioli Netcool Performance Manager: Installation Guide

83 Add a Discoery Serer The Discoery Serer is the Tioli Netcool Performance Manager component responsible for SNMP discoery. About this task You can add a discoery serer for each DataMart defined in the topology. To add a Discoery Serer: In the Logical iew, right-click the DataMart x folder and select Add Discoery serer from the menu. The Topology Editor displays the new Discoery Serer under the DataMart n folder in the Logical iew. Adding multiple Discoery Serers The steps required to add multiple Discoery serers. About this task If you want to run multiple Discoery serers on multiple hosts in your enironment, you must perform additional steps at deployment to make sure that each host system contains identical inentory files and identical copies of the inentory hook script. IBM recommends that you only use identically-configured instances of the Discoery Serer. The inentory files used by the Discoery Serer are configuration files named inentory_elements.txt and inentory_subelements.txt. These files are located in the $PVMHOME/conf directory of the system where you install the DataMart component. Some technology packs proide custom sub-elements inentory files with names different from inentory_subelements.txt that are also used by the Discoery Serer. To add multiple Discoery Serers, do the following: Install the primary instance of DataMart and the Discoery Serer on one target host system. Install and configure any required technology packs on the primary host. You modify the contents of the inentory files during this step. Install secondary instances of DataMart and the Discoery Serer on corresponding target host systems. Replicate the inentory files from the system where the primary instance of DataMart is running to the $PVMHOME/conf directory on the secondary hosts. You must also replicate the InentoryHook.sh script that is located in the $PVMHOME/bin directory and any other files that this script requires. Chapter 3. Installing in a distributed enironment 73

84 Add a Tioli Integrated Portal The Tioli Integrated Portal (TIP) proides an integrated console for users to log on and iew information contained on the DataView serer. About this task To add a Tioli Integrated Portal: 1. In the Logical iew, right-click on the Tioli Integrated Portals folder and select Add TIP from the menu. The Configure TIP Wizard is displayed. 2. The Topology Editor gies you the choice of adding an already existing Tioli Integrated Portal to the topology or to create a new Tioli Integrated Portal. To create a new TIP, select the Create a new TIP radio button. To import an already existing Tioli Integrated Portal into the topology, select the Import existing TIPs from host radio button. 3. Using the drop-down list of aailable hosts, select the host on which Tioli Integrated Portal should be installed (for example, delphi). Note: The hostname of the host selected for the TCR install must not contain underscores. Underscores in the hostname will cause the installation of TCR to fail. 4. Click Finish. The Topology Editor adds the new Tioli Integrated Portal component to the Logical iew. 5. Highlight the Tioli Integrated Portal component to display its properties. 6. Reiew the other property alues to make sure they are alid. For the complete list of properties for this component, see the IBM Tioli Netcool Performance Manager: Property Reference Guide. Discoering existing Tioli Integrated Portals About this task To discoer existing Tioli Integrated Portals: This step runs an asychronous check for existing Tioli Integrated Portals on each selected DataView host. If a Tioli Integrated Portal is discoered to exist on a host. The discoered Tioli Integrated Portal detail is added to the topology. 1. In the Logical iew, right-click on the Tioli Integrated Portals folder and select Import existing TIPs from host from the menu. The Run TIP Discoery Wizard Page is displayed. 2. Select the check box for each host on which you would like to perform Tioli Integrated Portal discoery. 3. Click Add TIP. If the discoered Tioli Integrated Portal is an old ersion, it is flagged within the topology for upgrade. Any DataView without a Tioli Integrated Portal is flagged within the topology for Tioli Integrated Portal installation on that host. The deployer will take the appropriate action when run. 74 IBM Tioli Netcool Performance Manager: Installation Guide

85 4. Click Next. 5. Configure Tioli Integrated Portal properties. a. Enter the appropriate host configuration alues. TCR_INSTALLATION_DIRECTORY: This is the directory in which Tioli Common Reporting is installed. TIP_INSTALLATION_DIRECTORY: This is the directory in which Tioli Integrated Portal is installed. WAS_USER_NAME: This is the WAS user name. WAS_PASSWORD: This is the WAS password. If you would like to configure LDAP for Tioli Integrated Portal, select the LDAP check box. b. Select the check box opposite each of the Tioli Integrated Portal hosts to which you want to apply the entered alues. c. Click Next. The hosts for which all configuration settings hae been specified disappear from the set of selectable hosts. d. Repeat steps a, b and c till all hosts are configured. 6. Click Next to add the discoered Tioli Intergrated Portals to the topology. Note: If you discoer a Tioli Common Reporting/Tioli Intergrated Portal of ersion 2.1 that was installed using the Tioli Common Reporting installer and not the Tioli Netcool Performance Manager installer, the port will not align with a Technology Pack automatically. To align the port numbers you must specify the Tioli Intergrated Portal port when performing the Technology Pack installation. Add a DataView How to add a DataView. About this task Note: To display DataView real-time charts, you must hae the Jaa runtime enironment (JRE) installed on the browser where the charts are to be displayed. You can download the JRE from the Sun download page at To add a DataView component: In the Logical iew, right-click on a Tioli Integrated Portal and select Add DataView from the menu. The DataView is automatically added inheriting its properties from the Tioli Integrated Portal instance. Chapter 3. Installing in a distributed enironment 75

86 Add the DataChannel administratie components The steps required to add DataChannel Administratie components. 1. In the Logical iew, right-click the DataChannels folder and select Add Administratie Components from the menu. The host selection window opens. 2. Using the drop-down list of aailable hosts, select the machine that you want to be the Channel Manager host for your DataChannel configuration (for example, corinth). 3. Click Finish. The Topology Editor adds a set of new components to the Logical iew: Channel Manager - Enables you to start and stop indiidual DataChannels and monitor the state of arious DataChannel programs. There is one Channel Manager for the entire DataChannel configuration. The Channel Manager components are installed on the first host you specify Corba Naming Serer - Proides near real-time data to DataView. High Aailability Managers - This is mainly used for large installations that want to use redundant SNMP collection paths. The HAM constantly monitors the aailability of one or more SNMP collection hosts, and switches collection to a backup host (called a spare) if a primary host becomes unaailable. Log Serer - Used to store user, debug, and error information. Plan Builder - Creates the metric data routing and processing plan for the other components in the DataChannel. Custom DataChannel properties - These are the custom property alues that apply to all DataChannel components. Global DataChannel properties - These are the global property alues that apply to all DataChannel components. Add a DataChannel A DataChannel is a software module that receies and processes network statistical information from both SNMP and non-snmp (BULK) sources. About this task This statistical information is then loaded into a database where it can be queried by SQL applications and captured as raw data or displayed on a portal in a ariety of reports. Typically, collectors are associated with technology packs, a suite of Tioli Netcool Performance Manager programs specific to a particular network deice or technology. A technology pack tells the collector what kind of data to collect on target deices and how to process that data. See the Technology Pack Installation Guide for detailed information about technology packs. To add a DataChannel: 1. In the Logical iew, right-click the DataChannels folder and select Add DataChannel from the menu. The Configure the DataChannel window is displayed. 76 IBM Tioli Netcool Performance Manager: Installation Guide

87 2. Using the drop-down list of aailable hosts, select the machine that will host the DataChannel (for example, corinth). 3. Accept the default channel number (for example, 1). 4. Click Finish. The Topology Editor adds the new DataChannel (for example, DataChannel 1) to the Logical iew. 5. Highlight the DataChannel to display its properties. Note that the DataChannel always installs and runs as the default user for the host (the Tioli Netcool Performance Manager Unix username, puser). Reiew the other property alues to make sure they are alid. For the complete list of properties for this component, see the IBM Tioli Netcool Performance Manager: Property Reference Guide. The DataChannel has the following subelements: Daily Loader x - Processes 24 hours of raw data eery day, merges it together, then loads it into the database. The loader process proides statistics on metric channel tables and metric tablespaces. Hourly Loader x - Reads files output by the Complex Metric Engine (CME) and loads the data into the database eery hour. The loader process proides statistics on metric channel tables and metric tablespaces. The Topology Editor includes the channel number in the element names. For example, DataChannel 1 would hae Daily Loader 1 and File Transfer Engine 1. Note: When you add DataChannel x, the Problems iew shows that the Input_Components property for the Hourly Loader is blank. This missing alue will automatically be filled in when you add a DataLoad collector (as described in the next section) and the error will be resoled. Separating the data and executable directories You may wish to separate the data and executable directories for your DataChannel About this task If you wish to separate the data and executable directories for your DataChannel, perform the following steps: 1. Create two directories on the DataChannel host, for example, DATA_DIR to hold the data and EXE_DIR to hold the executable. 2. Change the LOCAL_ROOT_DIRECTORY alue on that host's Disk Usage Serer to the data root folder DATA_DIR. In the Host adanced properties you will see the DATA_DIR alue propagated to all DC folder alues for the host. 3. Change DC_ROOT_EXE_DIRECTORY to the executable directory EXE_DIR. This change will propagate to the DC conf directory, the DataChannel Bin Directory and the Datachannel executable file name. Note: For adanced information about DataChannels, see Appendix B, DataChannels, on page 141. Chapter 3. Installing in a distributed enironment 77

88 Add a Collector Collectors collect and process raw statistical data about network deices obtained from arious network resources. The collectors send the receied data through a DataChannel for loading into the Tioli Netcool Performance Manager database. Note that collectors do not need to be on the same machine as the Oracle serer and DataMart. Collector types Collector types and their description, plus the steps required to associate a collector with a Technology Pack. About this task There are two basic types of collectors: SNMP collector - Collects data using SNMP polling directly to network serices. Specify this collector type if you plan to install a Tioli Netcool Performance Manager SNMP technology pack. These technology packs operate in networking enironments where the associated deices on which they operate use an SNMP protocol. Bulk DataLoad collector - Imports data from files. The files can hae multiple origins, including log files generated by network deices, files generated by SNMP collectors on remote networks, or files generated by a non-tioli Netcool Performance Manager network management database. There are two types of bulk collectors: UBA. A Uniersal Bulk Adapter (UBA) Collector that handles bulk input files generated by non-snmp deices. Specify this collector type if you plan to install a Tioli Netcool Performance Manager UBA technology pack, including Alcatel 5620 NM, Alcatel 5620 SAM, and Cisco CWM. BCOL. A bulk Collector that retriees and interprets the flat file output of network deices or network management systems. This collector type is not recommended for Tioli Netcool Performance Manager UBA technology packs, and is used in custom technology packs. If you are creating a UBA collector, you must associate it with a specific technology pack. For this reason, IBM recommends that you install the releant technology pack before creating the UBA collector. Therefore, you would perform the following sequence of steps: 1. Install Tioli Netcool Performance Manager, without creating the UBA collector. 2. Download and install the technology pack. 3. Open the deployed topology file to load the technology pack and add the UBA collector for it. Note: For detailed information about UBA technology packs and the installation process, see the Technology Pack Installation Guide. Configure the installed pack by following the instructions in the pack-specific user's guide. Restrictions There are a number of collector restrictions that must be noted. Note the following restrictions: 78 IBM Tioli Netcool Performance Manager: Installation Guide

89 The maximum collector identification number is 999. There is no relationship between the channel number and the collector number (that is, there is no predefined range for collector numbers based on channel number). Therefore, collector 555 could be attached to DataChannel 7. Each database channel can hae a maximum of 40 subchannels (and therefore, 40 collectors). Creating an SNMP collector How to create an SNMP collector. About this task To add an SNMP collector: 1. In the Logical iew, right-click the DataChannel x folder. The pop-up menu lists the following options: Add Collector SNMP - Creates an SNMP collector. Add Collector UBA - Creates a UBA collector. Add Collector BCOL - Creates a BCOL collector. This collector type is used in custom technology packs. DataMart must be added to the topology before a BCOL collector can be added. Select Add Collector SNMP. The Configure Collector window opens. 2. Using the drop-down list of aailable hosts on the Configure Collector window, select the machine that will host the collector (for example, corinth). 3. Accept the default collector number (for example, 1). 4. Click Finish. The Topology Editor displays the new collector under the DataChannel x folder in the Logical iew. 5. Highlight the collector to iew its properties. The Topology Editor displays both the SNMP collector core parameters and the SNMP technology pack-specific parameters. The core parameters are configured with all SNMP technology packs. You can specify an alternate installation user for the SNMP collector by changing the alues of the p_user, p_user_group and p_user_password properties in the Adanced Properties tab. Reiew the alues for the parameters to make sure they are alid. Note: For information about the core parameters, see the IBM Tioli Netcool Performance Manager: Property Reference Guide. Results The collector has two components: Complex Metric Engine x - Perform calculations on the collected data. File Transfer Engine (FTE) x - Transfers files from the collector's output directories and places them in the input directory of the CME. The FTE writes data to the file /ar/adm/wtmpx on each system that hosts a collector. As part of routine maintenance, check the size of this file to preent it from growing too large. Chapter 3. Installing in a distributed enironment 79

90 Note: Your Solaris ersion can be configured with strict access default settings for secure enironments. Strict FTP access settings might interfere with automatic transfers between a DataChannel subchannel and the DataLoad serer. Check for FTP lockouts in /etc/ftpd/ftpusers, and check for strict FTP rules in /etc/ftpd/ftpaccess. Note: The Topology Editor includes the channel and collector numbers in the element names. For example, DataChannel 1 could hae Collector SNMP 1.1, with Complex Metric Engine 1.1. and File Transfer Engine 1.1. Add a Cross Collector CME The steps required to add a Cross Collector CME. 1. In the Logical iew, right-click the Cross Collector CME folder and select Add Cross Collector CME from the menu. The Specify the Cross Collector CME details window is displayed. 2. Using the drop-down list of aailable hosts, select the machine that will host the Cross-Collector CME (for example, corinth). 3. Select the desired Disk Usage Serer on the selected host. 4. Select the desired channel number (for example, 1). 5. Click Finish. The Topology Editor adds the new Cross-Collector CME (for example, Cross-Collector CME 2000) to the Logical iew. 6. Highlight the Cross-Collector CME to display its properties. Note: The Cross-Collector CME always installs and runs as the default user for the host (the Tioli Netcool Performance Manager Unix username, puser). 7. Reiew the other property alues to make sure they are alid. For the complete list of properties for this component, see the IBM Tioli Netcool Performance Manager: Property Reference Guide 8. After running the deployer to install the Cross-Collector CME you will need to restart the CMGR process. Note: You will notice that dccmd start all will not start the Cross-Collector CME at this point. 9. You must first deploy a formula against the Cross-Collector CME using the DataChannel frmi tool. Run the frmi tool. The following is an example command: frmi ecma_formula.js -labels formula_labels.txt Where: The format of formula_labels.txt is 2 columns separated by an "=" sign. First column is Full Path to formula. Second is the number of the Cross-Collector CME. The file formula_labels.txt is of the format: Path_to_ECMA_formulas~Formula1Name=2000 Path_to_ECMA_formulas~Formula2Name=2001 Note: When a Cross-Collector CME (CC-CME) is installed on the system and formulas are applied against it, the remoal of collectors that the CC-CME 80 IBM Tioli Netcool Performance Manager: Installation Guide

91 Saing the topology depends on is not supported. This is an exceptional case, that is, if you hae not installed a CC-CME, collectors can be remoed. Adding multiple Cross Collectors About this task To add multiple Cross Collectors: 1. In the Logical iew, right-click the Cross Collector CME folder and select Add multiple Cross Collectors from the menu. The Add Cross Collector CME window is displayed. 2. (Optional) Click Add Hosts to add to the set of Cross Collector hosts. Only hosts that hae a DUS can be added. Note: It is recommended that you hae 20 Cross Collector CMEs spread across the set of toplolgy hosts. 3. Set the number of Cross Collector CMEs for the set of hosts, there are two ways you can do this: Click Calculate Defaults to use the wizard to calculate the recommended spread across the added hosts. This will set the number of Cross Collector CMEs to the default alue. To manually set the number of cross collector for each host, use the drop-down menu opposite each host name. 4. Click Finish. When you are satisfied with the infrastructure, erify that all the property alues are correct and that any problems hae been resoled, then sae the topology to an XML file. About this task To sae the topology as an XML file: 1. In the Topology Editor, select Topology then either Sae Topology As or Sae Topology. Click Browse to naigate to the directory in which to sae the file. By default, the topology is saed as topology.xml file in the topologyeditor directory. 2. Accept the default alue or choose another name or location, then click OK to close the file browser window. 3. The file name and path is displayed in the original window. Click Finish to sae the file and close the window. You are now ready to deploy the topology file (see Starting the Deployer on page 82). Note: Until you actually deploy the topology file, you can continue making changes to it as needed by following the directions in Opening an existing topology file on page 82. See Chapter 5, Modifying the current deployment, on page 95 for more information about making changes to a deployed topology file. Chapter 3. Installing in a distributed enironment 81

92 Note: Only when you begin the process of deploying a topology is it saed to the database. For more information, see the section Deploying the Topology. Opening an existing topology file As you create the topology, you can sae the file and update it as needed. Starting the Deployer About this task To open a topology file that exists but that has not yet been deployed: 1. If it is not already open, open the Topology Editor (see Starting the Topology Editor on page 67). 2. In the Topology Editor, select Topology > Open existing topology. The Open Topology window is displayed. 3. For the topology source, click local then use Browse to naigate to the correct directory and file. Once you hae selected the file, click OK. The selected file is displayed in the Open Topology window. Click Finish. The topology is displayed in the Topology Editor. 4. Change the topology as needed. The primary deployer is installed on the same machine as the Topology Editor. You first run the topology file on the primary deployer, and then run secondary installers on the other machines in the distributed enironment. See Resuming a partially successful first-time installation on page 87 for more information about the difference between primary and secondary deployers. Note: Before you start the deployer, erify that all the database tests hae been performed. Otherwise, the installation might fail. See Chapter 2, Installing and configuring the prerequisite software, on page 13 for more information. Primary Deployer The steps required to run the primary deployer from the Topology Editor Click Run > Run Deployer for Installation. Note: When you use the Run menu options (install or uninstall), the deployer uses the last saed topology file, not the current one. Be sure to sae the topology file before using a Run command. 82 IBM Tioli Netcool Performance Manager: Installation Guide

93 Secondary Deployers A secondary deployer is only required if remote installation using the primary deployer is not possible. About this task For more information on why you may need to use a secondary deployer, see Appendix A, Remote installation issues, on page 137. To run a secondary deployer: To run a secondary deployer from the launchpad: 1. On the launchpad, click Start the Deployer. 2. On the Start Deployer page, click the Start Deployer link. To run a secondary deployer from the command line: 1. Log in as root. 2. Change to the directory containing the deployer within the downloaded Tioli Netcool Performance Manager distribution: On Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/Install/SOL10/deployer/ On AIX systems: # cd <DIST_DIR>/proiso/AIX/Install/deployer/ On Linux systems: # cd <DIST_DIR>/proiso/RHEL/Install/deployer/ <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Enter the following command: #./deployer.bin Note: See Appendix D, Deployer CLI options, on page 159 for the list of supported command-line options. Pre-deployment check The Deployer will fail if the required patches listed in this file are not installed. About this task The Deployer performs a check on the operating system ersions and that the minimum required packages are installed. The Deployer checks for the files as listed in the releant check_os.ini file. The check_os.ini can be found at: The check_os.ini file detailing Solaris requirements can be found at: /SOLARIS/Install/SOL10/deployer/proiso/bin/Check/check_os.ini The check_os.ini file detailing AIX requirements can be found at: /AIX/Install/deployer/proiso/bin/Check/check_os.ini The check_os.ini file detailing Linux requirements can be found at: /RHEL/Install/deployer/proiso/bin/Check/check_os.ini Chapter 3. Installing in a distributed enironment 83

94 Deploying the topology To check if the required packages are installed: 1. Click Run > Run Deployer for Installation to start the Deployer. 2. Select the Check prerequisites check box. 3. Click Next. The check will return a failure if any of the required files are missing. To repair a failure: 1. Log in as root. 2. Install the packages listed as missing. 3. (Linux only) If any openmotif package is listed as missing: Install the missing openmotif package and update the package DB using the command: # updatedb 4. Rerun the check prerequisites step. How to deploy your defined topology. About this task The deployer displays a series of pages to guide you through the Tioli Netcool Performance Manager installation. The installation steps are displayed in a table, which enables you to run each step indiidually or to run all the steps at once. For more information about the deployer interface, see Primary Deployer on page 82. Important: By default, Tioli Netcool Performance Manager uses Monday to determine when a new week begins. If you wish to specify a different day, you must change the FIRST_WEEK_DAY parameter in the Database Registry using the dbregedit utility. This parameter can only be changed when you first deploy the topology that installs your Tioli Netcool Performance Manager enironment, and it must be changed BEFORE the Database Channel is installed. For more information, see the Tioli Netcool Performance Manager Registry and Space Management Tech Note. If you need to stop the installation, you can resume it at a later time. For more information, see Resuming a partially successful first-time installation on page 87. To deploy the Tioli Netcool Performance Manager topology: 1. The deployer opens, displaying a welcome page. Click Next to continue. 2. If you started the deployer from the launchpad or from the command line, enter the full path to your topology file, or click Choose to naigate to the correct location. Click Next to continue. Note: If you start the deployer from within the Topology Editor, this step is skipped. The database access window prompts for the security credentials. 84 IBM Tioli Netcool Performance Manager: Installation Guide

95 3. Enter the host name (for example, delphi) and database administrator password (for example, PV), and erify the other alues (port number, SID, and user name). Note that if the database does not yet exist, these parameters must match the alues you specified when you created the database configuration component (see Add a database configurations component on page 70). Click Next to continue. 4. The node selection window shows the target systems and how the files will be transferred (see Secondary Deployers on page 83 for an explanation of this window). The table has one row for each machine where at least one Tioli Netcool Performance Manager component will be installed. The default settings are as follows: The Enable checkbox is selected. If this option is not selected, no actions will be performed on that machine. The Check prerequisites checkbox is not selected, if selected scripts are run to erify that the prerequisite software has been installed. Remote execution is enabled, using both RSH and SSH. If remote execution cannot be enabled, perhaps due to a particular customer's security protocols, see Appendix A, Remote installation issues, on page 137 and Resuming a partially successful first-time installation on page 87. File transfer using FTP is enabled. If desired, reset the alues as appropriate for your deployment. Click Next to continue. 5. Proide media location details. The Tioli Netcool Performance Manager Media Location for components window is displayed, listing component and component platform. a. Click on the Choose the Proiso Media button. You will be asked to proide location of the media for each component. b. Enter the base directory in which your media is located. If any of the component media is not within the directory specified, you will be asked to proide media location detail for that component. 6. The deployer displays summary information about the installation. Reiew the information, then click Next. The deployer displays the table of installation steps (see Pre-deployment check on page 83 for an oeriew of the steps table). Note the following: Regardless of whether the steps are run, or if they pass or fail, closing the wizard will result in the topology being posted to the Tioli Netcool Performance Manager Database, assuming it exists. If an installation step fails, see Resuming a partially successful first-time installation on page 87 for debugging information. Continue the installation by following the instructions in Resuming a partially successful first-time installation on page 87. If the TCR installation step fails, which can happen when there is not enough space aailable in /usr and /tmp or directory cleanup has not been carried out, run the tcrclean.sh script. To run this script: a. Copy the tcrclean.sh script from the Primary Deployer (host where the Topology Editor is installed) to the serer where the TCR installation step fails. The tcrclean.sh script can be found on the Primary Deployer in the directory: /opt/ibm/proiso/deployer/proiso/bin/util/ Chapter 3. Installing in a distributed enironment 85

96 b. Run tcrclean.sh. c. When prompted, enter the install location of TCR. d. Continue the installation by following the instructions in Resuming a partially successful first-time installation on page Click Run All to run all the steps in sequence. 8. The deployer prompts you for the location of the setup files. Use the file selection window to naigate to the top-leel directory for your operating system to aoid further prompts. For example: <DIST_DIR>/RHEL/ <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page 26. Note: This assumes that the Tioli Netcool Performance Manager distribution was downloaded to the folder /ar/tmp/cdproiso as per the instructions in Downloading the Tioli Netcool Performance Manager distribution to disk on page 26. If Tioli Integrated Portal is configured to install on a remote host, the Run Remote TIP Install step is included. This step will prompt the user to enter the root password. The deployer requires this information in order to run as root on the remote host and perform the Tioli Integrated Portal installation. 9. When all the steps hae completed successfully, click Done to close the wizard. 10. Stop and start TCR: a. Naigate to the /tip_install_dir/products/tcr/bin/ directory. b. Set the ORACLE_HOME enironment ariable. For example: ORACLE_HOME=/opt/oracle/product/ export ORACLE_HOME c. Execute the following: LD_LIBRARY_PATH= $ORACLE_HOME/lib32:$LD_LIBRARY_PATH export LD_LIBRARY_PATH d. Run the following scripts: stoptcrserer.sh <username> <password> starttcrserer.sh Note: These scripts must be run eery time Tioli Integrated Portal is restarted. Note: The Topology Editor must be closed after eery deployment. Next steps The steps to perform after deployement. The next step is to install the technology packs, as described in Technology Pack Installation Guide. Once you hae created the topology and installed Tioli Netcool Performance Manager, it is ery easy to make changes to the enironment. Simply open the deployed topology file (loading it from the database), make your changes, and run 86 IBM Tioli Netcool Performance Manager: Installation Guide

97 the deployer with the updated topology file as input. For more information about performing incremental installations, see Chapter 5, Modifying the current deployment, on page 95. Note: After your initial deployment, always load the topology file from the database to make any additional changes (such as adding or remoing a component), because it reflects the current status of your enironment. Once you hae made your changes, you must deploy the updated topology so that it is propagated to the database. To make any subsequent changes following this deployment, you must load the topology file from the database again. To improe performance, IBM recommends that you regularly compute the statistics on metadata tables. You can compute these statistics by creating a cron entry that executes the dbmgr (Database Manager Utility) analyzemetadatatables command at interals. The following example shows a cron entry that checks statistics eery hour at 30 minutes past the hour. Note that the ForceCollection option is set to N, so that statistics will only be calculated when the internal calendar determines that it is necessary, and not eery hour: 05***[-f/opt/DM/dataMart.en ] && [ -x /opt/dm/bin/dbmgr ] &&. /opt/dm/datamart.en && dbmgr analyzemetadatatables A N For more information on dbmgr and the analyzemetadatatables command, see the Tioli Netcool Performance Manager dbmgr Reference Guide. For each new SNMP DataLoad, change the en file of the TNPM user to add the directory with the openssh libcrypto.so to the LD_LIBRARY_PATH (or LIBPATH). Resuming a partially successful first-time installation Should your quit during an installation, this section describes how you can resume the installation process. About this task In this scenario, you try deploying a Tioli Netcool Performance Manager topology for the first time. You define the topology and start the installation. Although some of the components of the Tioli Netcool Performance Manager topology are installed successfully, the oerall installation does not complete successfully. It addition, it is possible to skip a section of the installation. For example, a remote node might not be accessible for some reason. After skipping this portion of the installation, resume the installation to continue with the remaining steps. The deployer will list only those steps needed to complete the installation on the missing node. For example, suppose that during the first installation, Oracle wasn't running, so the database check failed. Stop the installation, start Oracle, then resume the installation. To resume a partial installation: 1. After correcting the problem, restart the deployer from the command line using the following command: Chapter 3. Installing in a distributed enironment 87

98 ./deployer.bin -Daction=resume Using the resume switch enables you to resume the installation exactly where you left off. Note: If you are asked to select a topology file in order to resume your installation, select the topology file you saed before beginning the install. 2. The deployer opens, displaying a welcome page. Click Next to continue. 3. Accept the default location of the base installation directory of the Oracle JDBC drier (/opt/oracle/product/ersion/jdbc/lib), or click Choose to naigate to another directory. Click Next to continue. 4. The steps page shows the installation steps in the ery same state they were in when you stopped the installation (with the completed steps marked Success, the failed step marked Error, and the remaining steps marked Held). 5. Select the step that preiously failed, reset it to Ready, then click Run Next. Verify that this installation step now completes successfully. 6. Run any remaining installation steps, erifying that they complete successfully. 7. At the end of the installation, the deployer loads the updated topology information into the database. 88 IBM Tioli Netcool Performance Manager: Installation Guide

99 Chapter 4. Installing as a minimal deployment This chapter describes how to install Tioli Netcool Performance Manager as a minimal deployment. Oeriew A minimal deployment installation is used primarily for demonstration or ealuation purposes, and installs the product on the smallest number of machines possible, with minimal user input. Before you begin This installation type installs all the Tioli Netcool Performance Manager components on the local host using a predefined topology file to define the infrastructure. The minimal deployment installation also installs the MIB-II SNMP technology pack. When you perform a minimal deployment installation, the Tioli Netcool Performance Manager components are installed on the serer you are running the deployer from. Before installing Tioli Netcool Performance Manager, you must hae installed the prerequisite software. For detailed information, see Chapter 2, Installing and configuring the prerequisite software, on page 13. Note: Before you start the installation, erify that all the database tests hae been performed. Otherwise, the installation might fail. See Chapter 2, Installing and configuring the prerequisite software, on page 13 for information about tnsping. Minimal Installation Process: If you are setting up a demonstration or ealuation system, it is possible to install all Tioli Netcool Performance Manager components on a single serer for Linux, Solaris or AIX systems. In this case your installation process will go as follows: Copyright IBM Corp. 2006,

100 Special consideration By default, Tioli Netcool Performance Manager uses Monday to determine when a new week begins. If you wish to specify a different day, you must change the FIRST_WEEK_DAY parameter in the Database Registry using the dbregedit utility. This parameter can only be changed when you first deploy the topology that installs your Tioli Netcool Performance Manager enironment, and it must be changed BEFORE the Database Channel is installed. For more information, see the Tioli Netcool Performance Manager Database Administration Guide. No resume of partial install aailable There is no resume functionality aailable to a minimal deployment installation. As a result a minimal deployment installation must be carried out in full if it is to be attempted. Oerriding default alues When performing a minimal deployment installation you must accept all default alues. The exceptions are listed in this section. The expections to this are: The location of the oracle jdbc drier. The default is /opt/oracle/product/10.2.0/jdbc/li The Tioli Netcool Performance Manager installation destination folder. The default is /opt/proiso Oracle serer params. The defaults are: Oracle Base: /opt/oracle Oracle home: /opt/oracle/product/ Oracle Port: IBM Tioli Netcool Performance Manager: Installation Guide

101 Installing a minimal deployment This section proides step-by-step instructions for installing Tioli Netcool Performance Manager on a single Solaris, AIX or Linux serer. Download the MIB-II files The minimal deployment ersion installs the MIB-II Technology Pack. About this task Before beginning the installation, you must download both the Technology Pack Installer and the MIB-II jar files. To download these files, access either of the following distributions: The product distribution site: softwareandserices Located on the product distribution site are the ProisoPackInstaller.jar file, the bundled jar file, and indiidual stand-alone technology pack jar files. (Optional) The Tioli Netcool Performance Manager CD distribution, which contains the ProisoPackInstaller.jar file and the jar files for the Starter Kit components. See your IBM customer representatie for more information about obtaining software. Note: Technology Pack Installer and the MIB-II jar files must be in the same directory (for example, AP), and no other application jar files should be present, if there are any more jars in that folder the installation step will fail due to "too many jars" in the specified folder. In addition, you must add the AP directory to the Tioli Netcool Performance Manager distribution's directory structure. Starting the Launchpad The steps required to start the launchpad. About this task To start the launchpad: 1. Log in as root. 2. Set and export the DISPLAY ariable (see Setting up a remote X Window display on page 14). 3. Set and export the BROWSER ariable to point to your Web browser. For example: On Solaris systems: # BROWSER=/opt/mozilla/mozilla # export BROWSER On AIX systems: # BROWSER=/usr/mozilla/firefox/firefox # export BROWSER On Linux systems: Chapter 4. Installing as a minimal deployment 91

102 # BROWSER=/usr/bin/firefox # export BROWSER Note: The BROWSER command cannot include any spaces around the equal sign. 4. Change directory to the directory where the launchpad resides. On Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS On AIX systems: # cd <DIST_DIR>/proiso/AIX On Linux systems: # cd <DIST_DIR>/proiso/RHEL <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Downloading the Tioli Netcool Performance Manager distribution to disk on page Enter the following command to start the launchpad: #./launchpad.sh Start the installation Steps required to install. About this task A minimal deployment installation uses a predefined topology file. To start the installation: 1. On the launchpad, click the Install Tioli Netcool Performance Manager for Minimal Deployment option in the list of tasks, then click the Install Tioli Netcool Performance Manager for Minimal Deployment link to start the deployer. Alternatiely, you can start the deployer from the command line, as follows: a. Log in as root. b. Set and export your DISPLAY ariable (see Setting up a remote X Window display on page 14). c. Change directory to the directory that contains the deployer: On Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/Install/SOL10/deployer On AIX systems: # cd <DIST_DIR>/proiso/AIX/Install/deployer On Linux systems: # cd <DIST_DIR>/proiso/RHEL/Install/deployer d. Enter the following command: #./deployer.bin -Daction=poc -DPrimary=true 2. The deployer opens, displaying a welcome page. Click Next to continue. 3. Accept the terms of the license agreement, then click Next. 4. Accept the default location of the base installation directory of the Oracle JDBC drier (/opt/oracle/product/ersion/jdbc/lib), or click Choose to naigate to another directory. Click Next to continue. 92 IBM Tioli Netcool Performance Manager: Installation Guide

103 5. The deployer prompts for the directory in which to install Tioli Netcool Performance Manager. Accept the default alue (/opt/proiso) or click Choose to naigate to another directory. Click Next to continue. 6. Verify the following additional information about the Oracle database: Oracle Base. The base directory for the Oracle installation (for example, /opt/oracle). Accept the proided path or click Choose to naigate to another directory. Oracle Home. The root directory of the Oracle database (for example, /opt/oracle/product/10.2.0). Accept the proided path or click Choose to naigate to another directory. Oracle Port. The port used for Oracle communications. The default alue is Click Next to continue. 7. The node selection window shows the target system and how the files will be transferred. These settings are ignored for a minimal deployment installation because all the components are installed on a single serer. Click Next to continue. 8. Proide media location details. The Tioli Netcool Performance Manager Media Location for components window is displayed, listing component and component platform. a. Click on the Choose the Proiso Media button. You will be asked to proide location of the media for each component. b. Enter the base directory in which your media is located. If any of the component media is not within the directory specified, you will be asked to proide media location detail for that component. 9. The deployer displays summary information about the installation. Reiew the information, then click Next to begin the installation. The deployer displays the table of installation steps (see Pre-deployment check on page 83 for an oeriew of the steps table). Note the following: If an installation step fails, see Appendix I, Error codes and log files, on page 187 for debugging information. Continue the installation by following the instructions in Resuming a partially successful first-time installation on page 87 Some of the installation steps can take a long time to complete. Howeer, if an installation step fails, it will fail in a short amount of time. 10. Click Run All to run all the steps in sequence. 11. When all the steps hae completed successfully, click Done to close the wizard. 12. Run chmod -R 777 on /opt/ibm/tioli in order to make all files in the TIP directory structure accessible. Your installation is complete. See The post-installation script on page 94 for information about the post-installation script, or Next steps on page 94 for what to do next. Chapter 4. Installing as a minimal deployment 93

104 The post-installation script Next steps The post-installation script is run automatically when installation is complete. About this task For a minimal deployment the script performs four actions: 1. Starts the DataChannel. 2. Starts the DataLoad SNMP Collector, if it is not already running. 3. Creates a DataView user named tnpm. 4. Gies the poc user permission to iew reports under the NOC Reporting group, with the default password of tnpm. Results The script writes a detailed log to the file /ar/tmp/poc-postinstall.${timestamp}.log. The steps to be performed following the deployment of your system. When the installation is complete, you are ready to perform the final configuration tasks that enable you to iew reports on the health of your network. These steps are documented in detail in the Tioli Netcool Performance Manager documentation set. For information about the MIB-II Technology Pack, see the MIB-II Technology Pack User's Guide. For information about installing additional technology packs, see the Technology Pack Installation Guide For each new SNMP DataLoad, change the en file of the TNPM user to add the directory with the openssh libcrypto.so to the LD_LIBRARY_PATH (or LIBPATH). 94 IBM Tioli Netcool Performance Manager: Installation Guide

105 Chapter 5. Modifying the current deployment Opening a deployed topology This chapter describes how to modify an installation of Tioli Netcool Performance Manager. It is possible to modify Tioli Netcool Performance Manager after it has been installed. To add, delete or upgrade components, load the deployed topology from the database, make your changes, and run the deployer with the updated topology as input. Note: You must run the updated topology through the deployer in order for your changes to take effect. Note the following: After your initial deployment, always load the topology from the database to make any additional changes (such as adding or remoing a component), because it reflects the current status of your enironment. Once you hae made your changes, you must deploy the updated topology so that it is propagated to the database. To make any subsequent changes following this deployment, you must load the topology from the database again. You might hae a situation where you hae modified a topology by both adding new components and remoing components (marking them "To Be Remoed"). Howeer, the deployer can work in only one mode at a time - installation mode or uninstallation mode. In this situation, first run the deployer in uninstallation mode, then run it again in installation mode. For information about deleting components from an existing topology, see Remoing a component from the topology on page 129. Once you hae installed Tioli Netcool Performance Manager, you can perform incremental installations by modifying the topology that is stored in the database. About this task You retriee the topology, modify it, then pass the updated data to the deployer. When the installation is complete, the deployer stores the reised topology data in the database. To open a deployed topology: 1. If it is not already open, open the Topology Editor (see Starting the Topology Editor on page 67). 2. In the Topology Editor, select Topology > Open existing topology. The Open Topology window is displayed. 3. For the topology source, select From database (. 443) and click Next. 4. Verify that all of the fields for the database connection are filled in with the correct alues: Copyright IBM Corp. 2006,

106 Database hostname - The name of the database host. The default alue is localhost. Port - The port number used for communication with the database. The default alue is Database user - The user name used to access the database. The default alue is PV_INSTALL. Database Password - The password for the database user account. For example, PV. SID - The SID for the database. The default alue is PV. If desired, click Sae as defaults to sae these alues for future incremental installations. Click Finish. Results Adding a new component The topology is retrieed from the database and is displayed in the Topology Editor. After you hae deployed your topology, you might need to make changes to it. About this task For example, you might want to add another SNMP collector. To add a new component to the topology: 1. If it is not already open, open the Topology Editor (see Starting the Topology Editor on page 67). 2. Open the existing topology (see Opening a deployed topology on page 95). 3. In the Logical iew of the Topology Editor, right-click the folder for the component you want to add. 4. Select Add XXX from the pop-up menu, where XXX is the name of the component you want to add. 5. The Topology Editor prompts for whateer information is needed to create the component. See the appropriate section for the component you want to add: Add the hosts on page 68 Add a database configurations component on page 70 Add a DataMart on page 71 Add a Discoery Serer on page 73 Add a Tioli Integrated Portal on page 74 Add a DataView on page 75 Add the DataChannel administratie components on page 76 Add a DataChannel on page 76 Add a Collector on page 78 Note: that if you add a collector to a topology that has already been deployed, you must manually bounce the DataChannel management 96 IBM Tioli Netcool Performance Manager: Installation Guide

107 components (cnsw, logw, cmgrw, amgrw). For more information, see Manually starting the Channel Manager programs on page 146. Add a Discoery Serer on page The new component is displayed in the Logical iew of the Topology Editor. 7. Sae the updated topology. You must sae the topology after you add the component and before you run the deployer. This step is not optional. 8. Run the deployer (see Starting the Deployer on page 82), passing the updated topology as input. The deployer can determine that most of the components described in the topology are already installed, and installs only the new component. 9. When the installation ends successfully, the deployer uploads the updated topology into the database. For information about remoing a component from the Tioli Netcool Performance Manager enironment, see Remoing a component from the topology on page 129. Example In this example, you update the installed ersion of Tioli Netcool Performance Manager to add a new DataChannel and two SNMP DataLoaders to the existing system. To update the Tioli Netcool Performance Manager installation: 1. If it is not already open, open the Topology Editor (see Starting the Topology Editor on page 67). 2. Open the existing topology (see Opening a deployed topology on page 95). 3. In the Logical iew of the Topology Editor, right-click the DataChannels folder. 4. Select Add Data Channel from the pop-up menu. Following the directions in Add a DataChannel on page 76, add the following components: a. Add a new DataChannel (Data Channel 2) with two different SNMP DataLoaders to the topology. The Topology Editor creates the new DataChannel. b. Add two SNMP collectors to the channel structure created by the Topology Editor. The editor automatically creates a Daily Loader component, an Hourly Loader component, and two Sub Channels with an FTE component and a CME component. 5. Sae the updated topology. 6. Run the deployer (see Starting the Deployer on page 82), passing the updated topology as input. The deployer can determine that most of the components described in the topology are already installed, and installs only the new components (in the example, DataChannel 5 with two new subchannels and DataLoaders). 7. When the installation ends, successful or not, the deployer uploads the updated topology into the database. Chapter 5. Modifying the current deployment 97

108 Changing configuration parameters of existing Tioli Netcool Performance Manager components Configuration information is stored in the database. This enables the DataChannel-related components to retriee the configuration from the database at run time. You set the configuration information using the Topology Editor. As with the other components, if you make changes to the configuration alues, you must pass the updated topology data to the deployer to hae the changes propagated to both the enironment and the database. Note: After the updated configuration has been stored in the database, you must manually start, stop, or bounce the affected DataChannel component to hae your changes take effect. Moing components to a different host You can use the Topology Editor to moe components between hosts. About this task You can moe all components between hosts when they hae not yet been installed and are in the configured state. You can moe SNMP and UBA collectors when they are in the configured state or after they hae been deployed and are in the installed state. If the component in the topology has not yet been deployed and is in the configured state, the Topology Editor proides a Change Host option in the pop-up menu when you click the component name in the Logical iew. This option allows you to change the host associated with the component prior to deployment. If the component is an SNMP or UBA collector that was preiously deployed and is in the installed state, the Topology Editor proides a Migrate option in the pop-up menu. This option instructs the deployer to uninstall the component from the preious host and re-install it on the new system. For instructions on moing deployed SNMP and UBA collectors after deployment, see Moing a deployed collector to a different host on page 99. For instructions on moing components that hae not yet been deployed, see the information below. Note: The Moement of installed DataChannel Remote components is not supported. All other components can be moed. To change the host associated with a component before deployment: 1. tart the Topology Editor (if it is not already running) and open the topology that includes the component's current host (see Starting the Topology Editor on page 67 and Opening a deployed topology on page 95). 2. In the Logical iew, naigate to the name of the component to moe. 3. Right-click the component name, then click Change Host from the pop-up menu. 98 IBM Tioli Netcool Performance Manager: Installation Guide

109 The Migrate Component dialog appears, containing a drop-down list of hosts where you can moe the component. 4. Select the name of the new host from the list, then click Finish. The name of the new host appears in the Properties tab. Moing a deployed collector to a different host You can moe a deployed SNMP or UBA collector to a different host. The instructions for doing so differ for SNMP collectors and UBA collectors. After you moe a collector to a new host, it may take seeral hours for the change to be registered in the database. Moing a deployed SNMP collector The steps required to moe a deployed SNMP collector to a different host About this task Note: To aoid the loss of collected data, leae the collector running on the original host until you complete Step 7 on page 108. To moe a deployed SNMP collector to a different host: 1. Start the Topology Editor (if it is not already running) and open the topology that includes the collector's current host (see Starting the Topology Editor on page 67 and Opening a deployed topology on page 95). 2. In the Logical iew, naigate to the name of the collector to moe. For example if moing SNMP 1.1, naigate as follows: DataChannels > DataChannel 1 > Collector 1.1 > Collector SNMP Right-click the collector name (for example, Collector SNMP 1.1), then click Migrate from the pop-up menu. The Migrate Collector dialog appears, containing a drop-down list of hosts where you can moe the collector. Note: If you are moing a collector that has not been deployed, select Change host from the pop-up menu (Migrate is grayed out). After the Migrate Collector dialog appears, continue with the steps below. 4. Select the name of the new host from the list, then click Finish. In the Physical iew, the status of the collector on the new host is Configured. The status of the collector on the original host is To be uninstalled. You will remoe the collector from the original host in Step 9. Note: If you are migrating a collector that has not been deployed, the name of the original host is automatically remoed from the Physical iew. 5. Click Topology > Sae Topology to sae the topology data. 6. Click Run > Run Deployer for Installation to run the deployer, passing the updated topology as input. For more information on running the deployer, see Starting the Deployer on page 82. The deployer installs the collector on the new host and starts it. Chapter 5. Modifying the current deployment 99

110 Note: Both collectors are now collecting data - the original collector on the original host, and the new collector on the new host. 7. Before continuing with the steps below, note the current time, and wait until a time period equialent to two of the collector's collection periods elapses. Doing so guards against data loss between collections on the original host and the start of collections on the new host. Because data collection on the new host is likely to begin sometime after the first collection period begins, the data collected during the first collection period will likely be incomplete. By waiting for two collection time periods to elapse, you can be confident that data for one full collection period will be collected. The default collection period is 15 minutes. You can find the collection period for the sub-element, sub-element group, or collection formula associated with the collector in the DataMart Request Editor. For information on iewing and setting a collection period, see the Tioli Netcool Performance Manager DataMart Configuration Guide. 8. Bounce the FTE for the collector on the collector's new host, as in the following example:./dccmd bounce FTE.1.1 The FTE now recognizes the collector's configuration on the new host, and will begin retrieing data from the collector's output directory on the new host. 9. In the current Topology Editor session, click Run > Run Deployer for Uninstallation to remoe the collector from the original host, passing the updated topology as input. For more information, see Remoing a component from the topology on page 129. Note: This step is not necessary if you are moing a collector that has not been deployed. Moing a deployed SNMP collector to or from a HAM enironment If you moe a deployed SNMP collector into or out of a High Aailability Manager (HAM) enironment, you must perform the steps in this section. About this task To moe a deployed SNMP collector to or from a HAM enironment: 1. Moe the collector as described in Moing a deployed SNMP collector on page 99. Note: If you are moing a spare collector out of the HAM enironment, the naigation path is different than the path shown in Step 2 of the aboe instructions. For example, suppose you hae a single HAM enironment with a cluster MyCluster on host MyHost, and you are moing the second SNMP spare out of the HAM. The naigation path to the spare would be as follows: DataChannels > Administratie Components > High Aailability Managers > HAM MySerer.1 > MyCluster > Collector Processes > Collection Process SNMP Spare Log in as Tioli Netcool Performance Manager Unix user, puser, on the collector's new host. 3. Change to the directory where DataLoad is installed. For example: 100 IBM Tioli Netcool Performance Manager: Installation Guide

111 cd /opt/dataload 4. Source the DataLoad enironment:../dataload.en 5. Stop the SNMP collector: pmdmgr stop 6. Edit the file dataload.en and set the field DL_HA_MODE as follows: Set DL_HA_MODE=true if you moed the collector onto a HAM host. Set DL_HA_MODE=false if you moed the collector off of a HAM host. 7. Source the DataLoad enironment again:../dataload.en 8. Start the SNMP collector: pmdmgr start Note: If you moe an SNMP collector to or from a HAM host, you must bounce the HAM. For information, see Stopping and restarting modified components on page 125. Moing a deployed UBA bulk collector The steps required to moe a deployed UBA collector to a different host. About this task Note: You cannot moe BCOL collectors, or UBA collectors that hae a BLB or QCIF subcomponent. If you want to moe a UBA collector that has these subcomponents, you must manually remoe it from the old host in the topology and then add it to the new host. To moe a deployed UBA collector to a different host: 1. Log in as puser to the DataChannel host where the UBA collector is running. 2. Change to the directory where DataChannel is installed. For example: cd /opt/datachannel 3. Source the DataChannel enironment:. datachannel.en 4. Stop the collector's UBA and FTE components. For example, to stop these components for UBA collector 1.1, run the following commands: dccmd stop UBA.1.1 and... dccmd stop FTE.1.1 For information on the dccmd command, see the Tioli Netcool Performance Manager Command Line Interface Guide. Note: Some technology packs hae additional pack-specific components that must be shut down - namely, BLB (bulk load balancer) and IF (inentory file) components. IF component names hae the format xxxif, where xxx is a pack-specific name. For example, Cisco CWM packs hae a CWMIF component, Alcatel 5620 SAM packs hae a SAMIF component, and Alcatel 5620 NM packs hae a QCIF component. Other packs do not use these technology-specific components. Chapter 5. Modifying the current deployment 101

112 5. Tar up the UBA collector's UBA directory. You will copy this directory to the collector's new host later in the procedure (Step 13). For example, to tar up a UBA directory for UBA collector 1.1, run the following command: Note: This step is not necessary if the collector's current host and the new host share a file system. tar -cf UBA_1_1.tar./UBA.1.1/* Note: Some technology packs hae additional pack-specific directories that need to be moed. These directories hae the same names as the corresponding pack-specific components described in Step Start the Topology Editor (if it is not already running) and open the topology that includes the collector's current host (see Starting the Topology Editor on page 67 and Opening a deployed topology on page 95). 7. In the Logical iew, naigate to the name of the collector to moe - for example, Collector UBA Right-click the collector name and select Migrate from the pop-up menu. The Migrate Collector dialog appears, containing a drop-down list of hosts where you can moe the collector. 9. Select the name of the new host from the list, then click Finish. In the Physical iew, the status of the collector on the new host is Configured. The collector is no longer listed under the original host. Note: If the UBA collector was the only DataChannel component on the original host, the collector will be listed under that host, and its status will be "To be uninstalled." You can remoe the DataChannel installation from the original host after you finish the steps below. For information on remoing DataChannel from the host, see Remoing a component from the topology on page Click Topology > Sae Topology to sae the topology. 11. Click Run > Run Deployer for Installation to run the deployer, passing the updated topology as input. For more information on running the deployer, see Starting the Deployer on page 82. If DataChannel is not already installed on the new host, this step installs it. 12. Click Run > Run Deployer for Uninstallation to remoe the collector from the original host, passing the updated topology as input. For more information, see Remoing a component from the topology on page Copy any directory you tarred in Step 5 and the associated JaaScript files to the new host. Note: This step is not necessary if the collector's original host and the new host share a file system. For example, to copy UBA_1_1.tar and the JaaScript files from the collector's original host: a. Log in as puser to the UBA collector's new host. b. Change to the directory where DataChannel is installed. For example: cd /opt/datachannel c. FTP to the collector's original host. d. Run the following commands to copy the tar file to the new host. For example: 102 IBM Tioli Netcool Performance Manager: Installation Guide

113 cd /opt/datachannel get UBA_1_1.tar bye tar -xf UBA_1_1.tar e. Change to the directory where the JaaScript files for the technology pack associated with the collector are located: cd /opt/datachannel/scripts f. FTP the JaaScript files from the /opt/datachannel/scripts directory on the original host to the /opt/datachannel/scripts directory on the new host. 14. Log in as puser to the Channel Manager host where the Administrator Components (including CMGR) are running. 15. Stop and restart the Channel Manager by performing the following steps: a. Change to the $DC_HOME directory (typically, /opt/datachannel). b. Source the DataChannel enironment:. datachannel.en c. Get the CMGR process ID by running the following command: ps -ef grep CMGR The process ID appears in the output immediately after the user ID, as shown below in bold: puser Aug 21? 3:04 /opt/datachannel/bin/cmgr_isualn/dc.im -a CMG d. Stop the CMGR process. For example, if 6561 is the CMGR process ID: kill e. Change to the $DC_HOME/bin directory (typically, /opt/datachannel/bin). f. Restart CMGR by running the following command:./cmgrw 16. Log in as puser to the UBA collector's new host and change to the $DC_HOME/bin directory (typically, /opt/datachannel/bin). 17. Run the following command to erify that Application Manager (AMGR) is running on the new host:./findisual If the AMGR process is running, you will see output that includes an entry like the following: puser Aug 21? 3:43 /opt/datachannel/bin/amgr_isual -nologo /opt/da Note: If AMGR is not running on the new host, do not continue. Verify that you hae performed the preceding steps correctly. 18. Start the collector's UBA and FTE components on the new host. For example, to start these components for collector 1.1, run the following commands:./dccmd start UBA.1.1 and..../dccmd start FTE.1.1 Note: If any pack-specific components were shut down on the old host (see Step 4), you must also start those components on the new host. Chapter 5. Modifying the current deployment 103

114 104 IBM Tioli Netcool Performance Manager: Installation Guide

115 Chapter 6. Using the High Aailability Manager This chapter describes the optional Tioli Netcool Performance Manager High Aailability Manager (HAM), including how to set up a HAM enironment. Oeriew The High Aailability Manager (HAM) is an optional component for large installations that want to use redundant SNMP collection paths. The HAM constantly monitors the aailability of one or more SNMP collection hosts, and switches collection to a backup host (called a spare) if a primary host becomes unaailable. The following figure shows a simple HAM configuration with one primary host and one spare. In the panel on the left, the primary host is operating normally. SNMP data is being collected from the network and channeled to the primary host. In the panel on the right, the HAM has detected that the primary host is unaailable, so it dynamically unbinds the collection path from the primary host and binds it to the spare. HAM basics An SNMP collector collects data from a specific set of network resources according to a set of configuration properties. A collector has two basic parts: the collector process running on the host computer, and the collector profile that defines the collector's properties. Note: Do not confuse a "collector profile" with an "inentory profile." A collector profile contains properties used in the collection of data from network resources - properties such as collector number, polling interal, and output directory for the collected data. An inentory profile contains information used to discoer network resources - properties such as the addresses of the resources to look for and the mode of discoery. A collector that is not part of a HAM enironment is static - that is, the collector process and the collector profile are inseparable. But in a HAM enironment, the Copyright IBM Corp. 2006,

116 collector process and collector profile are managed as separate entities. This means that if a collector process is unaailable (due to a collector process crash or a host machine outage), the HAM can dynamically reconfigure the collector, allowing data collection to continue. The HAM does so by unbinding the collector profile from the unaailable collector process on the primary host, and then binding the collector profile to a collector process on a backup (spare) host. Note: It may take seeral minutes for the HAM to reconfigure a collector, depending on the amount of data being collected. The parts of a collector Collector parts and their description. When you set up a HAM configuration in the Topology Editor, you manage the two parts of a collector - the collector process and the collector profile - through the following folders in the Logical iew: Collector Processes. Acollector process is a Unix process representing a runtime instance of a collector. A collector process is identified by the name of the host where the process is running and by the collector process port (typically 3002). A host can hae just one SNMP collector process. Managed Definitions. Amanaged definition identifies a collector profile through the unique collector number defined in the profile. Eery managed definition has a default binding to a host and to the collector process on that host. The default host and collector process are called the managed definition's primary host and collector process. A host that you designate as a spare host has a collector process but no default managed definition. The following figure shows the parts of a collector that you manage through the Collector Process and Managed Definition folders. In the figure, the HAM dynamically unbinds the collector profile from the collector process on the primary host, and then binds the profile to the collector process on the spare. This dynamic re-binding of the collector is accomplished when the HAM binds the managed definition - in this case, represented by the unique collector ID, Collector 1- to the collector process on the spare. 106 IBM Tioli Netcool Performance Manager: Installation Guide

117 Clusters A HAM enironment can consist of a single set of hosts or multiple sets of hosts. Each set of hosts in a HAM enironment is called a cluster. HAM cluster configuration A cluster is a logical grouping of hosts and collector processes that are managed by a HAM. The use of multiple clusters is optional. Whether you use multiple clusters or just one has no affect on the operation of the HAM. Clusters simply gie you a way to separate one group of collectors from another, so that you can better deploy and manage your primary and spare collectors in a way that is appropriate for your needs. Multiple clusters may be useful if you hae a large number of SNMP collector hosts to manage, or if the hosts are located in arious geographic areas. The clusters in a gien HAM enironment are distinct from one another. In other words, the HAM cannot bind a managed definition in one cluster to a collector process in another. For host failoer to occur, a HAM cluster must hae at least one aailable spare host. The cluster can hae as few as two hosts - one primary and one spare. Or, it can hae multiple primary hosts with one or more spares ready to replace primary hosts that become unaailable. The ratio of primary hosts to spare hosts is expressed as p + s. For example, a HAM cluster with four primary hosts and two spares is referred to as a 4+2 cluster. Types of spare hosts There are two types of spare hosts: Designated spare. The sole purpose of this type of spare in a HAM cluster is to act as a backup host. A designated spare has a collector process, but no default managed definition. Its collector process remains idle until the HAM detects an outage on one of the actie hosts, and binds that host's managed definition to the spare's collector process. A HAM cluster must hae at least one designated spare. Floating spare. This type of spare is a primary host that can also act as a backup host for one or more managed definitions. Chapter 6. Using the High Aailability Manager 107

118 Types of HAM clusters The types of HAM clusters that can be created. When the HAM binds a managed definition to a spare (either a designated spare or a floating spare), the spare becomes an actie component of the collector. It remains so unless you explicitly reassign the managed definition back to its primary host or to another aailable host in the HAM cluster. This is an important fact to consider when you plan the hosts to include in a HAM cluster. There are two types of HAM clusters: Fixed spare cluster. In this type of cluster, failoer can occur only to designated spares. There are no floating spares in this type of cluster. When the HAM binds a managed definition to the spare, the spare temporarily takes the place of the primary that has become unaailable. When the primary becomes aailable again, you must reassign the managed definition back to the primary (or to another aailable host). The primary then resumes its data collection operations, and the spare resumes its role as backup host. If you do not reassign the managed definition back to the primary, the primary cannot participate in further collection operations. Since the primary is not configured as a floating spare, it also cannot act as a spare now that its collector process is idle. As a result, the HAM cluster loses its failoer capabilities if no other spare is aailable. Note: A primary host cannot act as a spare unless it is configured as a floating spare. Floating spare cluster. This type of cluster has one or more primary hosts that can also act as a spare. Failoer can occur to a floating spare or to a designated spare. You do not need to reassign the managed definition back to this type of primary, as you do with primaries in a fixed spare cluster. When a floating spare primary becomes aailable again, it assumes the role of a spare. You can designate some or all of the primaries in a HAM cluster as floating spares. If all the primaries in a HAM cluster are floating spares, you should neer hae to reassign a managed definition to another aailable host in order to maintain failoer capability. Note: IBM recommends that all the primaries in a cluster be of the same type - either all floating spares or no floating spares. Example HAM clusters Examples of HAM cluster options. The Tioli Netcool Performance Manager High Aailability Manager feature is designed to proide great flexibility in setting up a HAM cluster. The following illustrations show just a few of the possible ariations , fixed spare A fixed spare cluster with one primary host and one designated spare. The figure below shows a fixed spare cluster with one primary host and one designated spare: In the panel on the left, Primary1 is functioning normally. The designated spare is idle. 108 IBM Tioli Netcool Performance Manager: Installation Guide

119 In the panel on the right, Primary1 experiences an outage. The HAM unbinds the collector from Primary1 and binds it to the designated spare. With the spare in use and no other spares in the HAM cluster, failoer can no longer occur - een after Primary1 returns to serice. For failoer to be possible again, you must reassign Collector 1 to Primary1. This idles the collector process on the spare, making it aailable for the next failoer operation if Primary 1 fails again. Note: When a designated spare seres as the only spare for a single primary, as in a 1+1 fixed spare cluster, the HAM pre-loads the primary's collector definition on the spare. This results in a fast failoer with a likely loss of no more than one collection cycle. The following table shows the bindings that the HAM can and cannot make in this cluster: Collector Possible Host Bindings Host Bindings Not Possible Collector 1 Primary1 (default binding) Designated spare , fixed spare A fixed spare cluster with two primary hosts and one designated spare The figure below shows a fixed spare cluster with two primary hosts and one designated spare: In the panel on the left, Primary1 and Primary2 are functioning normally. The designated spare is idle. In the panel on the right, Primary2 experiences an outage. The HAM unbinds the collector from Primary2 and binds it to the designated spare. With the spare in use and no other spares in the HAM cluster, failoer can no longer occur - een after Primary2 returns to serice. For failoer to be possible again, you must reassign Collector 2 to Primary2. This idles the collector process on the spare, making it aailable for the next failoer operation. Chapter 6. Using the High Aailability Manager 109

120 The following table shows the bindings that the HAM can and cannot make in this cluster: Collector Possible Host Bindings Host Bindings Not Possible Collector 1 Collector 2 Primary1 (default binding) Designated spare Primary2 (default binding) Designated spare Primary2 Primary , both primaries are floating spares Both primaries are floating spares. The figure below shows a floating spare cluster with two primary hosts and one designated spare, with each primary configured as a floating spare: In the panel on the left, Primary1 and Primary2 are functioning normally. The designated spare is idle. In the panel on the right, Primary2 experiences an outage. The HAM unbinds the collector from Primary2 and binds it to the designated spare. When Primary2 returns to serice, it will assume the role of spare, meaning its collector process remains idle. The host originally defined as the dedicated spare continues as the actie platform for Collector 2. The following figure shows the same cluster after Primary2 has returned to serice. In the panel on the left, Primary2 is idle, prepared to act as backup if needed. 110 IBM Tioli Netcool Performance Manager: Installation Guide

121 In the panel on the right, Primary1 experiences an outage. The HAM unbinds the collector from Primary1 and binds it to the floating spare, Primary2. The following table shows the bindings that the HAM can and cannot make in this cluster: Collector Possible Host Bindings Host Bindings Not Possible Collector 1 Primary1 (default binding) - Primary2 Collector 2 Designated spare Primary1 Primary2 (default binding) Designated spare , fixed spares A fixed spare cluster with three primary hosts and two designated spares. The figure below shows a fixed spare cluster with three primary hosts and two designated spares: In the panel on the left, all three primaries are functioning normally. The designated spares are idle. In the panel on the right, Primary3 experiences an outage. The HAM unbinds the collector from Primary3 and binds it to Designated Spare 2. The HAM chose Designated Spare 2 oer Designated Spare 1 because the managed definition for Collector 3 set the failoer priority in that order. Note: Each managed definition sets its own failoer priority. Failoer priority can be defined differently in different managed definitions. With one spare in use and one other spare aailable (Designated Spare 1), failoer is now limited to the one aailable spare - een after Primary3 returns to serice. For dual failoer to be possible again, you must reassign Collector 3 to Primary3. Chapter 6. Using the High Aailability Manager 111

122 The following table shows the bindings that the HAM can and cannot make in this cluster: Collector Possible Host Bindings Host Bindings Not Possible Collector 1 Collector 2 Collector 3 Primary1 (default binding) Designated Spare 1 Designated Spare 2 Primary2 (default binding) Designated Spare 1 Designated Spare 2 Primary3 (default binding) Designated Spare 1 Designated Spare 2 Primary2 Primary3 Primary1 Primary3 Primary1 Primary2 3+ 2, all primaries are floating spares A floating spare cluster with three primary hosts and two designated spares, with each primary configured as a floating spare. The figure below shows a floating spare cluster with three primary hosts and two designated spares, with each primary configured as a floating spare: In the panel on the left, Primary3 had preiously experienced an outage. The HAM unbound its default collector (Collector 3) from Primary3, and bound the collector to the first aailable spare in the managed definition's priority list, which happened to be Designated Spare 2. Now that Primary3 is aailable again, it is acting as a spare, while Designated Spare 2 remains the actie collector process for Collector 3. In the panel on the right, Primary2 experiences an outage. The HAM unbinds Collector 2 from Primary2, and binds it to the first aailable spare in the managed definition's priority list. This happens to be the floating spare Primary3. When Primary2 becomes aailable again, there will once more be two spares aailable - Primary2 and Designated Spare IBM Tioli Netcool Performance Manager: Installation Guide

123 The following table shows the bindings that the HAM can and cannot make in this cluster: Collector Possible Host Bindings Host Bindings Not Possible Collector 1 Primary1 (default binding) - Primary2 Primary3 Designated Spare 1 Collector 2 Collector 3 Designated Spare 2 Primary1 Primary2 (default binding) Primary3 Designated Spare 1 Designated Spare 2 Primary1 Primary2 Primary3 (default binding) Designated Spare 1 Designated Spare Chapter 6. Using the High Aailability Manager 113

124 Resource pools When you configure a managed definition in the Topology Editor, you specify the hosts that the HAM can bind to the managed definition, and also the priority order in which the hosts are to be bound. This list of hosts is called the resource pool for the managed definition. A resource pool includes: The managed definition's primary host and collector process (that is, the host and collector process that are bound to the managed definition by default). Zero or more other primary hosts in the cluster. If you add a primary host to a managed definition's resource pool, that primary host becomes a floating spare for the managed definition. Zero or more designated spares in the cluster. Typically, each managed definition includes one or more designated spares in its resource pool. How the SNMP collector works Note: If no managed definitions include a designated spare in their resource pools, there will be no aailable spares in the cluster, and therefore failoer cannot occur in the cluster. The SNMP collector capability and behaiour. The SNMP collector is state-based and designed both to perform initialization and termination actions, and to "change state" in response to eents generated by the HAM or as a result of internally-generated eents (like a timeout, for example). The following table lists the eents that the SNMP collector understands and indicates whether they can be generated by the HAM. Eent HAM-Generated Description Load Yes Load collection profile, do not begin scheduling collections. Pause Yes Stop scheduling collections; do not unload profile. Reset Yes Reset expiration timer. Start Yes Start scheduling collections. Stop Yes Stop scheduling collections; unload profile Timeout No Expiration timer expires; start scheduling collections. The SNMP collector can reside in one of the following states, as shown in the following table: 114 IBM Tioli Netcool Performance Manager: Installation Guide

125 SNMP Collector State Eent Description Idle N/A Initial state; a collector number may or may not be assigned; the collection profile has not been loaded. Loading Load Intermediate state between Idle and Ready. Occurs after a Load eent. Collector number is assigned, and the collection profile is being loaded. Ready N/A Collector number assigned, profile loaded, but not scheduling requests or performing collections. Starting Start Intermediate state between Idle and Running. Occurs after a Start eent. Collector number assigned, and profile is being loaded. Running N/A Actiely performing requests and collections. Stopping Stop/Pause Intermediate state between Running and Idle. The following state diagram shows how the SNMP collector transitions through its arious states depending upon eents or time-outs: How failoer works with the HAM and the SNMP collector How Failoer Works With the HAM and the SNMP Collector The following tables illustrate how the HAM communicates with the SNMP collectors during failoer for a 1+1 cluster and a 2+1 cluster. Chapter 6. Using the High Aailability Manager 115

126 Table 5. HAM and SNMP Collector in a 1+1 Cluster State of Primary State of Spare Eents and Actions Running Idle The HAM sends the spare the Load eent for the specified collection profile. Running Ready The HAM sends a Pause eent to the spare to extend the timeout. Note: If the timeout expires, the spare will perform start actions and transition to a Running state. Running Running The HAM sends a Pause eent to the collector process that has been in a Running state for a shorter amount of time. No response Ready The HAM sends a Start eent to the spare. Table 6. HAM and SNMP Collector in a 2+1 Cluster State of Primary State of Spare Eents and Actions Running Idle No action Running Ready No action Running Running The HAM sends a Stop eent to the collector process that has been in Running state for the shorter amount of time. No Response Idle The HAM sends a Start eent to the spare. No Response Ready The HAM sends a Start eent to the spare. Because more than one physical system may produce SNMP collections, the File Transfer Engine (FTE) must check eery capable system for a specific profile. The FTE retriees all output for the specific profile. Any duplicated collections are reconciled by the Complex Metrics Engine (CME). Obtaining collector status How to get the status of a collector. To obtain status on the SNMP collectors managed by the HAM, enter the following command on the command line: $ dccmd status HAM.<hostname>.1 The dccmd command returns output similar to the following: COMPONENT APPLICATION HOST STATUS ES DURATION EXTENDED STATUS HAM.DCAIX2.1 HAM DCAIX2 running Ok: (box1:3012 -> Running 1.1 for 5h2m26s); No aail spare; Check: dcaix2:3002, birdnestb: Ok: (box2:3002 -> Running 1.2 for 5h9m36s); No aail spare; Check: box4:3002, box5: Not Running; No aail spare; Check: box4:3002, box5: IBM Tioli Netcool Performance Manager: Installation Guide

127 Creating a HAM enironment The following list describes EXTENDED STATUS information: Load # Collection profile 1.1 Ok: - Status of the load. Ok means it is properly collected, Not Running indicates a seere problem (data losses) (box1:3012 -> Running 1.1 for 5h2m26s)- The collector that is currently performing the load, with its status and uptime. No aail spare - List of possible spare, if something happens to the collector currently working. In this example there is no spare aailable, a failoer would fail. A list of host:port would indicate the possible spare machines. Check: box4:3002, box5: Indicates what is currently wrong with the system/configuration. Machines box4:3002 and box5:3002 should be spare but are either not running, or not reachable. The user is instructed to check these machines. For a 1-to-1 failoer configuration, the dccmd command might return output like the following: $ dccmd status HAM.SERVER.1 COMPONENT APPLICATION HOST STATUS ES DURATION EXTENDED STATUS HAM.SERVER.1 HAM SERVER running Ok: (box1:3002 -> Running 1.1 for 5h2m26s); 1 aail spare: (box2:3002 -> Ready 1.1) This preceding output shows that Collector 1.1 is in a Running state on Box1, and that the Collector on Box2 is in a Ready state, with the profile for Collector 1.1 loaded. This section describes the steps required to create a 3+1 HAM enironment with a single cluster, and with all three primaries configured as floating spares. About this task This is just one of the many ariations a HAM enironment can hae. The procedures described in the following sections indicate the specific steps where you can ary the configuration. Note: If you are setting up a new Tioli Netcool Performance Manager enironment and plan to use a HAM in that enironment, perform the following tasks in the following order: 1. Install all collectors. 2. Configure and start the HAM. 3. Install all technology packs. 4. Perform the discoery. Chapter 6. Using the High Aailability Manager 117

128 Topology prerequisites The minimum component prerequisite. A 3+1 HAM cluster requires that you hae a topology with the following minimum components: Three hosts, each bound to an SNMP collector. These will act as the primary hosts. You will create a managed definition for each of the primary hosts. One additional host that is not bound to an SNMP collector. This will act as the designated spare. For information on installing these components, see Adding a new component on page 96. s The general procedures for creating a single-cluster HAM with one designated spare and three floating spares. Create the HAM and a HAM cluster To create a High Aailability Manager with a single cluster 1. Start the Topology Editor (if it is not already running) and open the topology where you want to add the HAM (see Starting the Topology Editor on page 67 and Opening a deployed topology on page 95). 2. In the Logical iew, right-click High Aailability Managers, located at DataChannels > Administratie Components. 3. Select Add High Aailability Manager from the pop-up menu. The Add High Aailability Manager Wizard appears. 4. In the Aailable hosts field, select the host where you want to add the HAM. Note: You can install the HAM on a host where a collector process is installed, but you cannot install more than one HAM on a host. 5. In the Identifier field, accept the default identifier. The identifier has the following format: HAM.<HostName>.<n> where HostName is the name of the host you selected in Step 4, and n is a HAM-assigned sequential number, beginning with 1, that uniquely identifies this HAM from others that may be defined on other hosts. 6. Click Finish. The HAM identifier appears under the High Aailability Managers folder. 7. Right-click the identifier of the HAM you just created. 8. Select Add Cluster from the pop-up menu. The Add Cluster Monitor Wizard appears. 9. In the Identifier field, type a name for the cluster and click Finish. The cluster name appears under the HAM identifier folder you added in Step 6. The following folders appear under the cluster name: Collector Processes Managed Definitions 118 IBM Tioli Netcool Performance Manager: Installation Guide

129 Note: To add additional clusters to the enironment, repeat Step 7 through Step 9. Add the designated spare How to create and add a designated spare. About this task To create a designated spare, you must hae a host defined in the Physical iew with no SNMP collector assigned to it. For information on adding a host to a topology, see Add the hosts on page 68 To add a designated spare to a cluster: 1. In the Logical iew, right-click the Collector Processes folder that you created in Step 9 of the preious section, Create the HAM and a HAM cluster on page Select Add Collection Process SNMP Spare from the pop-up menu. The Add Collection Process SNMP Spare - Configure Collector Process SNMP Spare dialog appears. 3. In the Aailable hosts field, select the host that you want to make the designated spare. This field contains the names of hosts in the Physical iew that do not hae SNMP collectors assigned to them. 4. In the Port field, specify the default port number, 3002, for the spare's collector process, then click Finish. Under the cluster's Collector Processes folder, the entry Collection Process SNMP Spare <n> appears, where n is a HAM-assigned sequential number, beginning with 1, that uniquely identifies this designated spare from others that may be defined in this cluster. Note: Repeat Step 1 through Step 4 to add an additional designated spare to the cluster. What to do next Should you be making changes to an already existing configuration, please make sure the dataload.en file contains all the right settings: 1. Change to the directory where DataLoad is installed. For example: cd /opt/dataload 2. Source the DataLoad enironment:../dataload.en 3. Make sure that DL_HA_MODE field in the dataload.en file and set to DL_HA_MODE=true. 4. Source the DataLoad enironment again:../dataload.en Chapter 6. Using the High Aailability Manager 119

130 Add the managed definitions A managed definition allows the HAM to bind a collector profile to a collector process. About this task Note: When you add a managed definition to a HAM cluster, the associated collector process is automatically added to the cluster's Collector Processes folder. To add a managed definition to a HAM cluster: 1. In the Logical iew, right-click the Managed Definitions folder that you created in Create the HAM and a HAM cluster on page Select Add Managed Definition from the pop-up menu. The Add Managed Definition - Choose Managed Definition dialog appears. 3. In the Collector number field, select the unique collector number to associate with this managed definition. 4. Click Finish. The following entries now appear for the cluster: Under the cluster's Managed Definitions folder, the entry Managed Definition <n> appears, where n is the collector number you selected in Step 3. Under the cluster's Collector Processes folder, the entry Collector Process [HostName] appears, where HostName is the host that will be bound to the SNMP collector you selected in Step 3. This host is the managed definition's primary host. Note: Repeat Step 1 though to Step 4 to add another managed definition to the cluster. Example When you finish adding managed definitions for a 3+1 HAM cluster, the Logical and Physical iews might look like the following: 120 IBM Tioli Netcool Performance Manager: Installation Guide

131 In this example, the hosts dcsol1a, dcsol1b, and docserer1 are the primaries, and docserer2 is the designated spare. Define the resource pools A resource pool is a list of the spares, in priority order, that the HAM can bind to a particular managed definition. About this task When you create a managed definition, the managed definition's primary host is the only host in its resource pool. To enable the HAM to bind a managed definition to other hosts, you must add more hosts to the managed definition's resource pool. To add hosts to a managed definition's resource pool: 1. Right-click a managed definition in the cluster's Managed Definitions folder. 2. Select Configure Managed Definition from the pop-up menu. The Configure Managed Definition - Collector Process Selection dialog appears, as shown below. In this example, the resource pool being configured is for Managed Definition 1 (that is, the managed definition associated with Collector 1). Chapter 6. Using the High Aailability Manager 121

132 3. In the Additional Collector Processes list, check the box next to each host to add to the managed definition's resource pool. Typically, you will add at least the designated spare (in this example, docserer2) to the resource pool. If you add a primary host to the resource pool, that host becomes a floating spare for the managed definition. Note: You must add at least one of the hosts in the Additional Collector Processes list to the resource pool. Since the goal in this example is to configure all primaries as floating spares, the designated spare and the two primaries (docserer1 and dcsol1a) will be added to the resource pool. 4. When finished checking the hosts to add to the resource pool, click Next. Note: If you add just one host to the resource pool, the Next button is not enabled. Click Finish to complete the definition of this resource pool. Return to Step 1 to define a resource pool for the next managed definition in the cluster, or skip to Sae and start the HAM on page 123 if you are finished defining resource pools. The Configure Managed Definition - Collector Process Order dialog appears, as shown below: 122 IBM Tioli Netcool Performance Manager: Installation Guide

133 5. Specify the failoer priority order for this managed definition. To do so: a. Select a host to moe up or down in the priority list, then click the Up or Down button until the host is positioned where you want. b. Continue moing hosts until the priority list is ordered as you want. c. Click Finish. In this example, if the primary associated with Managed Definition 1 fails, the HAM will attempt to bind the managed definition to the floating spare dcsol1a. If dcsol1a is in use or otherwise unaailable, the HAM attempts to bind the managed definition to docserer1. The designated spare docserer2 is last in priority. 6. Return to Step 1 to define a resource pool for the next managed definition in the cluster, or continue with the next section if you are finished defining resource pools. Sae and start the HAM When you finish configuring the HAM as described in the preious sections, you are ready to sae the configuration and start the HAM. About this task To sae and start the HAM: 1. Click Topology > Sae Topology to sae the topology file containing the HAM configuration. 2. Run the deployer (see Starting the Deployer on page 82), passing the updated topology file as input. 3. Open a terminal window on the DataChannel host. 4. Log in as puser. 5. Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default), as follows: cd /opt/datachannel/bin 6. Bounce (stop and restart) the Channel Manager. For instructions, see Step 15 on page Run the following command: dccmd start ham Chapter 6. Using the High Aailability Manager 123

134 Monitoring of the HAM enironment begins. For information on using dccmd, see the Tioli Netcool Performance Manager Command Line Interface Guide. Creating an additional HAM enironment How to create a HAM enironment. Typically, one HAM is sufficient to manage all the collectors you require in your HAM enironment. But for performance reasons, ery large Tioli Netcool Performance Manager deployments inoling dozens or hundreds of collector processes might benefit from more than one HAM enironment. HAM enironments are completely separate from one another. A host in one HAM enironment cannot fail oer to a host in another HAM enironment. To create an additional HAM enironment, perform all of the procedures described in Creating a HAM enironment on page 117. Modifying a HAM enironment How to modify a HAM enironment. You can modify a HAM enironment by performing any of the procedures in Creating a HAM enironment on page 117. For example, you can add collectors, add clusters, configure a primary host as a floating spare, change the failoer priority order of a resource pool, and make a number of other changes to the enironment, including moing collectors into or out of a HAM enironment. For information on moing a deployed SNMP collector into or out of a HAM enironment, see Moing a deployed SNMP collector to or from a HAM enironment on page 100. You can also modify the configuration parameters of the HAM components that are writable. For information on modifying configuration parameters, see Changing configuration parameters of existing Tioli Netcool Performance Manager components on page 98. Remoing HAM components How to remoe HAM components. You can remoe HAM components from the enironment by right-clicking the component name and selecting Remoe from the pop-up menu. The selected component and any subcomponents will be remoed. Before you can remoe a designated spare (Collection Process SNMP Spare), you must remoe the spare from any resource pools it may belong to. To remoe a designated spare from a resource pool, open the managed definition that contains the resource pool, and clear the check box next to the name of the designated spare to remoe. For information about managing resource pools, see Define the resource pools on page IBM Tioli Netcool Performance Manager: Installation Guide

135 Stopping and restarting modified components How to stop and restart modified components. About this task If you change the configuration of a HAM or any HAM components, or if you add or remoe an existing collector to or from a HAM enironment, you must bounce (stop and restart) the Tioli Netcool Performance Manager components you changed The is generally true for all Tioli Netcool Performance Manager components that you change, not just HAM. To bounce a component: 1. Open a terminal window on the DataChannel host. 2. Log in as puser. 3. Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default), as follows: cd /opt/datachannel/bin 4. Run the bounce command in the following format: dccmd bounce <component> For example: To bounce the HAM with the identifier HAM.dcsol1b.1, run: dccmd bounce ham.dcsol1b.1 To bounce all HAMs in the topology, run: dccmd bounce ham.*.* To bounce the FTE for collector 1.1 that is managed by a HAM, run: dccmd bounce fte.1.1 You do not need to bounce the HAM that the FTE and collector are in. For information on using dccmd, see the Tioli Netcool Performance Manager Command Line Interface Guide. 5. Bounce the Channel Manager. For instructions, see Step 15. Viewing the current configuration During the process of creating or modifying a HAM cluster, you may find it useful to check how the indiidual collector processes and managed definitions are currently configured. About this task To iew the current configuration of a collector process or managed definition: 1. Right-click the collector process or managed definition to iew. 2. Select Show from the pop-up menu. The Show Collector Process... or Show Managed Definition... dialog appears. The following sections describe the contents of these dialogs. Chapter 6. Using the High Aailability Manager 125

136 Show Collector Process... dialog Dialog box description. The following figure shows a collector process configured with three managed definitions. The configuration alues are described as follows: dcsol1a. The primary host where this collector process runs The port through which the collector process receies SNMP data. 3 2 (Primary) 1. The managed definitions that the HAM can bind to this collector process. The alues hae the following meanings: 3. The managed definition for Collector 3. 2 (Primary). The managed definition for Collector 2. This is the default managed definition for the collector process. 1. The managed definition for Collector 1. Show Managed Definition... dialog Dialog box description. The Show Managed Definition... dialog contains the resource pool for a particular managed definition. This dialog contains the same information that appears in the Show Collector Process... dialog, but for multiple hosts instead of just one. As such, this dialog gies you a broader iew of the cluster's configuration than a Show Managed Definition... dialog. The following figure shows a managed definition's resource pool configured with four hosts: 126 IBM Tioli Netcool Performance Manager: Installation Guide

137 Note the following about this managed definition's resource pool: The priority order of the hosts is from top to bottom - therefore, the first collector process that the HAM will attempt to bind to this managed definition is the one on host dcsol1a. The collector process on host docserer2 is last in the priority list. The first three hosts are floating spares. They are flagged as such by each haing a primary managed definition. The host docserer2 is the only designated spare in the resource pool. It is flagged as such by not haing a primary managed definition. Chapter 6. Using the High Aailability Manager 127