Installation and Configuration Guide

Transcription

1 Network Manager IP Edition Version 4 Release 1 Installation and Configuration Guide R4.1 E1

2

3 Network Manager IP Edition Version 4 Release 1 Installation and Configuration Guide R4.1 E1

4 Note Before using this information and the product it supports, read the information in Notices on page 307. This edition applies to ersion 4.1 of IBM Tioli Network Manager IP Edition (product number 5724-S45) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2006, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents About this publication Intended audience What this publication contains Publications i Accessibility ix Tioli technical training ix Support and community information x Conentions used in this publication xi Chapter 1. Planning for installation... 1 Deployment of Network Manager Deployment scenarios Deployment considerations Deployment examples Network domains Eent collection using one domain per ObjectSerer Eent collection using multiple domains per ObjectSerer Example isualization of topology from multiple domains Hardware requirements Processor selection guidelines Requirements to run the installer Requirements for the core components Requirements for the GUI components Requirements for the topology database serer 27 Disk space for eents and interfaces Swap space requirements (UNIX) Bandwidth requirements for discoery Discoery memory requirements Software requirements Requirements for other products Supported topology databases Supported operating systems Supported browsers for Web applications Supported browsers for the installer launchpad 36 Operating system tools Domain Name Serice (DNS) requirements UNIX user restrictions Installation directory requirements File handle requirements Requirements for charting About DNCIM Chapter 2. Installing Preparing to install Configuring an existing Tioli Netcool/OMNIbus installation on a remote serer Setting up a topology database Installing Tioli Common Reporting Extracting the installation file Checking system prerequisites Configuring Red Hat Linux Enterprise Edition. 49 Installing Network Manager Differences between basic and custom installation 50 About a FIPS installation Installing Network Manager using the wizard.. 51 Installing Network Manager in console mode.. 72 Installing Network Manager in silent mode Postinstallation tasks Troubleshooting the installation Viewing the installation logs Checking login URL and default ports Dependency error messages Running installation and maintenance procedures as root or non-root Not enough disk space to complete the installation Console mode installation error Backing up and restoring the Deployment Engine 90 Harmless installation messages Insufficient disk space for install Installation failure scenario Install fails after deployment engine upgrade.. 92 Uninstalling Network Manager Remoing reports Uninstalling on UNIX Installing fix packs Chapter 3. Upgrading and migrating.. 99 About upgrading and migrating Upgrade paths Default locations for different product ersions 101 Migrated files Upgrading and migrating to latest Network Manager Upgrading to latest Network Manager: full side-by-side migration Upgrading to latest Network Manager by reusing your existing Tioli Integrated Portal enironment Copying an existing V4.1 installation Troubleshooting the upgrade Viewing the upgrade logs Harmless upgrade error messages Network iews with duplicate names following import Not all GUI components were exported Poll definition classes not migrated correctly 150 Chapter 4. Configuring Network Manager Configuring integrations with other products Configuring Tioli Netcool/OMNIbus for use with Network Manager Configuring integration with Netcool Configuration Manager Exporting discoery data to CCMDB, TADDM, and TBSM Copyright IBM Corp. 2006, 2013 iii

6 Configuring the Tioli Integrated Portal Integrating with IBM Tioli Monitoring Configuring integration with IBM Systems Director Accessing discoery data from dncim Configuring Network Manager for UNIX operating systems Configuring root/non-root permissions Installing and configuring DB2 after a non-root installation Configuring connection to existing DB Configuring GUIs Administering the TopoViz client Loading updated MIB information Configuring the presentation of eents from unmanaged deices Configuring reports for existing installations Migrating the Cognos content store from Derby to DB Enabling failoer About failoer About NCIM topology database high aailability Failoer architectures Failoer operation of the Network Manager core processes Limitations of the Network Manager failoer process Configuring failoer Troubleshooting failoer Changing the IP address and hostname of the Network Manager installation Changing the IP address and hostname for Network Manager Changing the IP address and hostname on the Tioli Netcool/OMNIbus serer Updating Network Manager for a new Tioli Netcool/OMNIbus IP address and hostname Updating the Tioli Integrated Portal for a new Tioli Netcool/OMNIbus IP address and hostname Changing the IP address and hostname on the Tioli Integrated Portal serer Updating Network Manager for changed hostname of the Tioli Integrated Portal serer. 286 Changing the IP address and hostname on the Deployment Engine serer Changing the IP address for Tioli Common Reporting Configuring Network Manager for a changed IP address of the DB2 NCIM serer Setting enironment ariables Default directory structure Configuring Juniper PE Deices Proiding support for legacy deices in a FIPS installation Creating and configuring extra network domains 294 Configuring OQL Serice Proider authentication 296 Configuring the SNMP Helper Configuring SNMP Helper throttling Configuring GetBulk support for SNMP 2 and Configuring SSO between Charting and Tioli Monitoring The IBM Support Assistant (ISA) Installing the IBM Support Assistant Lite collector Appendix. Network Manager glossary 303 Notices Trademarks Index i IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

7 About this publication Intended audience IBM Tioli Network Manager IP Edition proides detailed network discoery, deice monitoring, topology isualization, and root cause analysis (RCA) capabilities. Network Manager can be extensiely customized and configured to manage different networks. Network Manager also proides extensie reporting features, and integration with other IBM products, such as IBM Tioli Application Dependency Discoery Manager, IBM Tioli Business Serice Manager and IBM Systems Director. The IBM Tioli Network Manager IP Edition Installation and Configuration Guide describes how to install Network Manager. The guide also describes post-installation configuration tasks. This publication is for administrators who need to install and set up Network Manager. This publication is intended for administrators who need to install Network Manager and perform post-installation configuration. Readers need to be familiar with the following topics: Network management Operating System configuration IBM Tioli Network Manager IP Edition works in conjunction with IBM Tioli Netcool/OMNIbus; this publication assumes that you understand how IBM Tioli Netcool/OMNIbus works. For more information on IBM Tioli Netcool/OMNIbus, see the publications described in Publications on page i. What this publication contains This publication contains the following sections: Chapter 1, Planning for installation, on page 1 Proides information on what to consider before installing Network Manager, such as deployment configurations including failoer and network domains, hardware, operating system, software, and communication requirements. Chapter 2, Installing, on page 41 Describes how to install Network Manager. Chapter 3, Upgrading and migrating, on page 99 Describes how to upgrade to the latest ersion of Network Manager, including the migration of existing data from your preious production enironment. Chapter 4, Configuring Network Manager, on page 151 Describes tasks to perform after installing Network Manager, and settings you can change later on during the use of the product. Copyright IBM Corp. 2006, 2013

8 Publications This section lists publications in the Network Manager library and related documents. The section also describes how to access Tioli publications online and how to order Tioli publications. Your Network Manager library The following documents are aailable in the Network Manager library: IBM Tioli Network Manager IP Edition Release Notes, GI Gies important and late-breaking information about IBM Tioli Network Manager IP Edition. This publication is for deployers and administrators, and should be read first. IBM Tioli Network Manager Getting Started Guide, GI Describes how to set up IBM Tioli Network Manager IP Edition after you hae installed the product. This guide describes how to start the product, make sure it is running correctly, and discoer the network. Getting a good network discoery is central to using Network Manager successfully. This guide describes how to configure and monitor a first discoery, erify the results of the discoery, configure a production discoery, and how to keep the network topology up to date. Once you hae an up-to-date network topology, this guide describes how to make the network topology aailable to Network Operators, and how to monitor the network. The essential tasks are coered in this short guide, with references to the more detailed, optional, or adanced tasks and reference material in the rest of the documentation set. IBM Tioli Network Manager IP Edition Product Oeriew, GC Gies an oeriew of IBM Tioli Network Manager IP Edition. It describes the product architecture, components and functionality. This publication is for anyone interested in IBM Tioli Network Manager IP Edition. IBM Tioli Network Manager IP Edition Installation and Configuration Guide, SC Describes how to install IBM Tioli Network Manager IP Edition. It also describes necessary and optional post-installation configuration tasks. This publication is for administrators who need to install and set up IBM Tioli Network Manager IP Edition. IBM Tioli Network Manager IP Edition Administration Guide, SC Describes administration tasks for IBM Tioli Network Manager IP Edition, such as how to administer processes, query databases and start and stop the product. This publication is for administrators who are responsible for the maintenance and aailability of IBM Tioli Network Manager IP Edition. IBM Tioli Network Manager IP Edition Discoery Guide, SC Describes how to use IBM Tioli Network Manager IP Edition to discoer your network. This publication is for administrators who are responsible for configuring and running network discoery. IBM Tioli Network Manager IP Edition Eent Management Guide, SC Describes how to use IBM Tioli Network Manager IP Edition to poll network deices, to configure the enrichment of eents from network deices, and to manage plug-ins to the Tioli Netcool/OMNIbus Eent Gateway, including configuration of the RCA plug-in for root-cause analysis purposes. This publication is for administrators who are responsible for configuring and running network polling, eent enrichment, root-cause analysis, and Eent Gateway plug-ins. i IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

9 IBM Tioli Network Manager IP Edition Network Troubleshooting Guide, GC Describes how to use IBM Tioli Network Manager IP Edition to troubleshoot network problems identified by the product. This publication is for network operators who are responsible for identifying or resoling network problems. IBM Tioli Network Manager IP Edition Network Visualization Setup Guide, SC Describes how to configure the IBM Tioli Network Manager IP Edition network isualization tools to gie your network operators a customized working enironment. This publication is for product administrators or team leaders who are responsible for facilitating the work of network operators. IBM Tioli Network Manager IP Edition Management Database Reference, SC Describes the schemas of the component databases in IBM Tioli Network Manager IP Edition. This publication is for adanced users who need to query the component databases directly. IBM Tioli Network Manager IP Edition Topology Database Reference, SC Describes the schemas of the database used for storing topology data in IBM Tioli Network Manager IP Edition. This publication is for adanced users who need to query the topology database directly. IBM Tioli Network Manager IP Edition Language Reference, SC Describes the system languages used by IBM Tioli Network Manager IP Edition, such as the Stitcher language, and the Object Query Language. This publication is for adanced users who need to customize the operation of IBM Tioli Network Manager IP Edition. IBM Tioli Network Manager IP Edition Perl API Guide, SC Describes the Perl modules that allow deelopers to write custom applications that interact with the IBM Tioli Network Manager IP Edition. Examples of custom applications that deelopers can write include Polling and Discoery Agents. This publication is for adanced Perl deelopers who need to write such custom applications. IBM Tioli Monitoring for Tioli Network Manager IP User's Guide, SC Proides information about installing and using IBM Tioli Monitoring for IBM Tioli Network Manager IP Edition. This publication is for system administrators who install and use IBM Tioli Monitoring for IBM Tioli Network Manager IP Edition to monitor and manage IBM Tioli Network Manager IP Edition resources. Prerequisite publications To use the information in this publication effectiely, you must hae some prerequisite knowledge, which you can obtain from the following publications: IBM Tioli Netcool/OMNIbus Installation and Deployment Guide, SC Includes installation and upgrade procedures for Tioli Netcool/OMNIbus, and describes how to configure security and component communications. The publication also includes examples of Tioli Netcool/OMNIbus architectures and describes how to implement them. IBM Tioli Netcool/OMNIbus User's Guide, SC Proides an oeriew of the desktop tools and describes the operator tasks related to eent management using these tools. IBM Tioli Netcool/OMNIbus Administration Guide, SC About this publication ii

10 Describes how to perform administratie tasks using the Tioli Netcool/OMNIbus Administrator GUI, command-line tools, and process control. The publication also contains descriptions and examples of ObjectSerer SQL syntax and automations. IBM Tioli Netcool/OMNIbus Probe and Gateway Guide, SC Contains introductory and reference information about probes and gateways, including probe rules file syntax and gateway commands. IBM Tioli Netcool/OMNIbus Web GUI Administration and User's Guide SC Describes how to perform administratie and eent isualization tasks using the Tioli Netcool/OMNIbus Web GUI. Accessing terminology online The IBM Terminology Web site consolidates the terminology from IBM product libraries in one conenient location. You can access the Terminology Web site at the following Web address: Accessing publications online IBM posts publications for this and all other Tioli products, as they become aailable and wheneer they are updated, to the Tioli Information Center Web site at: Note: If you print PDF documents on other than letter-sized paper, set the option in the File > Print window that allows your PDF reading application to print letter-sized pages on your local paper. Ordering publications You can order many Tioli publications online at the following Web site: You can also order by telephone by calling one of these numbers: In the United States: In Canada: In other countries, contact your software account representatie to order Tioli publications. To locate the telephone number of your local representatie, perform the following steps: 1. Go to the following Web site: 2. Select your country from the list and click Go. The Welcome to the IBM Publications Center page is displayed for your country. 3. On the left side of the page, click About this site to see an information page that includes the telephone number of your local representatie. iii IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

11 Accessibility Tioli technical training Accessibility features help users with a physical disability, such as restricted mobility or limited ision, to use software products successfully. Accessibility features The following list includes the major accessibility features in Network Manager: The console-based installer supports keyboard-only operation. Network Manager proides the following features suitable for low ision users: All non-text content used in the GUI has associated alternatie text. Low-ision users can adjust the system display settings, including high contrast mode, and can control the font sizes using the browser settings. Color is not used as the only isual means of coneying information, indicating an action, prompting a response, or distinguishing a isual element. Network Manager proides the following features suitable for photosensitie epileptic users: Web pages do not contain anything that flashes more than two times in any one second period. The Network Manager Information Center is accessibility-enabled. The accessibility features of the information center are described in Accessibility and keyboard shortcuts in the information center. Extra steps to configure Internet Explorer for accessibility If you are using Internet Explorer as your web browser, you might need to perform extra configuration steps to enable accessibility features. To enable high contrast mode, complete the following steps: 1. Click Tools > Internet Options > Accessibility. 2. Select all the check boxes in the Formatting section. If clicking View > Text Size > Largest does not increase the font size, click Ctrl + and Ctrl -. IBM and accessibility See the IBM Human Ability and Accessibility Center for more information about the commitment that IBM has to accessibility. For Tioli technical training information, refer to the following IBM Tioli Education Web site: About this publication ix

12 Support and community information Use IBM Support, Serice Management Connect, and Tioli user groups to connect with IBM and get the help and information you need. IBM Support If you hae a problem with your IBM software, you want to resole it quickly. IBM proides the following ways for you to obtain the support you need: Online Go to the IBM Software Support site at support/probsub.html and follow the instructions. IBM Support Assistant The IBM Support Assistant (ISA) is a free local software sericeability workbench that helps you resole questions and problems with IBM software products. The ISA proides quick access to support-related information and sericeability tools for problem determination. To install the ISA software, go to Tioli user groups Tioli user groups are independent, user-run membership organizations that proide Tioli users with information to assist them in the implementation of Tioli Software solutions. Through these groups, members can share information and learn from the knowledge and experience of other Tioli users. Tioli user groups include the following members and groups: 23,000+ members 144+ groups Access the link for the Tioli Users Group at Serice Management Connect Access Serice Management Connect at sericemanagement/. Use Serice Management Connect in the following ways: Become inoled with transparent deelopment, an ongoing, open engagement between other users and IBM deelopers of Tioli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code. Connect one-on-one with the experts to collaborate and network about Tioli and the (enter your community name here) community. Read blogs to benefit from the expertise and experience of others. Use wikis and forums to collaborate with the broader user community. x IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

13 Conentions used in this publication This publication uses seeral conentions for special terms and actions and operating system-dependent commands and paths. Typeface conentions This publication uses the following typeface conentions: Bold Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) Keywords and parameters in text Italic Citations (examples: titles of publications, diskettes, and CDs Words defined in text (example: a nonswitched line is called a point-to-point line) Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictie clause."; letters as letters example: "The LUN address must start with the letter L.") New terms in text (except in a definition list): a iew is a frame in a workspace that contains data. Variables and alues you must proide:... where myname represents... Monospace Examples and code examples File names, programming keywords, and other elements that are difficult to distinguish from surrounding text Message text and prompts addressed to the user Text that the user must type Values for arguments or command options Bold monospace Command names, and names of macros and utilities that you can type as commands Enironment ariable names in text Keywords Parameter names in text: API structure parameters, command parameters and arguments, and configuration parameters Process names Registry ariable names in text Script names About this publication xi

14 Operating system-dependent ariables and paths This publication uses enironment ariables without platform-specific prefixes and suffixes, unless the command applies only to specific platforms. For example, the directory where the Network Manager core components are installed is represented as NCHOME. On UNIX systems, preface enironment ariables with the dollar sign $. For example, on UNIX, NCHOME is $NCHOME. xii IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

15 Chapter 1. Planning for installation Read about deployment considerations and system requirements for Network Manager. Deployment of Network Manager Use this information for guidance on how to configure the physical deployment of your Network Manager installation. Deployment scenarios How you deploy Network Manager depends on your enironment, including factors such as the size and complexity of your network and the number of operations staff who require system access. The following are typical Network Manager deployment scenarios: Small demonstration or educational system deployment Small customer network Medium customer network Large customer network Very large customer network A further deployment scenario is the following: Telecommunications company or serice proider network. Note: Failoer can be applied to each of these Network Manager deployments. This section proides general guidance to assist you in deciding how to deploy Network Manager. For more detailed information, see the IBM Tioli Network Manager IP Edition Installation and Configuration Guide and the IBM Tioli Network Manager IP Edition Release Notes. Network and deployment comparisons Use this information to compare the example customer networks and to compare the Network Manager deployments for each of the example customer networks. Customer networks compared: Use this information to compare the example customer networks and to identify which example most closely matches your network. The following table lists typical features for each of the example customer networks. These alues are example alues only. Your specific network alues might ary. In particular, you should note the following: With regard to the alues for Aerage number of interfaces per deice specified in this table, the actual interface counts can ary considerably from the aerage interface count. An example of this is found in MPLS networks, where the number of interfaces per deice is ery high in the core network, but might be as low as 2 to 3 interfaces per deice for the edge deices. With regards to the number of deices for a telecommunications company, the alue specified (15,000) is an aerage alue. A national telecommunications Copyright IBM Corp. 2006,

16 company will hae a far larger number of deices, a small local telecommunications company will hae far fewer. Table 1. Example customer networks compared Feature Demo Enterprise Telco Small Medium Large Very large Number of deices Aerage number of interfaces per deice Network locations Network architecture Number of actie GUI clients Chassis ping polling examples SNMP polling examples to to 1,000 1,000 to 12,000 12,000 to 30,000 15, or more 30 or more 1,200 Single location Single location Distributed Global network Global network, distributed management One or more locations Flat Flat Flat Complex Complex Complex 1to3 3 5to20 5to20 5to20 5to20 Values set for demonstration purposes Values set for demonstration purposes 2-minute interals 3 to 6 alues at 30 minute interals 2-5 minutes 2-5 minutes 2-5 minutes 2-5 minutes 5 to 15 minute interals 10 to 15 minute interals. SNMP 1, 2c, or 3 polling in any of the enironments listed Interals of 15 minutes or longer 5 alues at 5 minute interals Deice and interface polls in any of the enironments listed. Tioli product integrations None None ITM with TDW ITM with TDW ITM with TDW ITM with TDW TBSM TBSM TBSM Performance data collection period TADDM TADDM TADDM 1 to 5 days 31 days 31 days 31 days 31 days 7 days Network Manager deployments compared: Use this information to compare the Network Manager deployments for each of the example customer networks. The following table lists the settings required for the Network Manager deployments for each of the example customer networks. These alues are example alues only. The alues that are appropriate for your specific deployment might ary. Note: With regard to the alues for Deployment specified in this table, these alues do not take failoer serers into account. 2 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

17 Table 2. Example Network Manager deployments compared Settings Demo Enterprise Telco Small Medium Large Very large Platform Linux x86 Any supported platform Any supported platform Linux and UNIX Linux and UNIX Deployment Single serer Single serer 1-2 serers 3-4 serers 4 or more serers Client system Single processor Any supported platform 3 serers Topology database Number of network domains Number of polling engines based on network size 2 GB DRAM minimum, or 4 GB DRAM for large networks Supported JRE and Internet browser Default database Default database Any supported RDBMS Any supported RDBMS Any supported RDBMS ormore 2ormore Consider more than one poller Consider more than one poller Consider more than one poller Any supported RDBMS Consider more than one poller Reasons for multiple domains: There are a number of reasons why you might need to partition your network into multiple domains. You might need to partition your network into multiple domains for one of the following reasons: Your network exceeds a certain size. See the section Guidelines for number of network domains to determine whether your network requires multiple domains. Discoery takes a ery long time. You can shorten your discoery times by partitioning your network into multiple domains. Operational boundaries dictate the need for multiple domains. Examples of operational boundaries include geographical boundaries and security boundaries. Your network contains oerlapping IP addresses. Guidelines for number of network domains: If your network exceeds a certain size, you might need to break up the network into multiple domains. Use this information to work out the number of network domains needed for your deployment. Use the following procedure to determine the number of required domains. For information on how to create and configure extra network domains, see the IBM Tioli Network Manager IP Edition Installation and Configuration Guide. Note: The calculations presented here proide approximate figures only. The actual number of domains required aries, depending on arious factors, including the agents used in the discoery. For example, the Entity agent discoers a lot of extra network entities, and this might require more domains. 1. Gather the following data: Chapter 1. Planning for installation 3

18 Number of deices in the network Aerage number of interfaces per deice Note: The actual interface counts on a gien deice can ary considerably from the aerage interface count. An example of this is found in MPLS networks, where the number of interfaces per deice is ery high in the core network, but might be as low as 2 to 3 interfaces per deice for the edge deices. 2. Apply the following equation to determine an approximate number of network entities: Number of network entities = Number of deices * Aerage interface count * multiplier Where: multiplier = 2 for a routed network multiplier = 3.5 for a switched network Note: Switched networks tend to generate more network entities because they contain VLANs, which contain multiple entities. 3. Apply the following equation to determine the suggested number of network domains: Number of domains required = (Number of network entities) / 250,000 Where 250,000 is the suggested maximum number of network entities in a domain. Router-centric customer The data for this customer is as follows: Number of deices in the network: 15,000 Aerage number of interfaces per deice: 20 This customer network will produce approximately 600,000 network entities: Number of network entities = 15,000 * 20 * 2 = 600,000 Based on the following calculation, this network requires three network domains: Number of domains required = 600,000 / 250,000 = 2.4 Switch-centric customer The data for this customer is as follows: Number of deices in the network: 1,000 Aerage number of interfaces per deice: 24 This customer network will produce approximately 84,000 network entities: Number of network entities = 1,000 * 24 * 3.5 = 84,000 Based on the following calculation, this network requires one network domain: Number of domains required = 84,000 / 250,000 < 1 4 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

19 Related concepts: Network domains on page 20 Before installing, you need to consider whether to partition your network into domains, or hae a single domain for the entire network. A network domain is a collection of network entities to be discoered and managed. Demonstration or educational system deployment This is a small installation for use as a demonstration system or for training and educational purposes. The following sections describe this network in greater detail and proide suggestions for a Network Manager deployment to meet the needs of this network. Description This enironment consists of about 25 network deices and key serers combined. All deices are in one location, on the same network subnet as the deices to be managed. There is one local GUI client session supported by the same machine that hosts the Network Manager product components. There might be one or two GUI client sessions on other machines. The network deices come from multiple endors. The network architecture is flat. All deices are attached to a LAN and hae Fast Ethernet connections. For demonstration purposes only, a number of network deices hae SNMP3, and a number of workstations hae IP6. Within this enironment the following example conditions apply: 1 to 3 actie GUI clients. Chassis ping polling and some SNMP polling actiity is required. No major Tioli products are integrated with the system, other than the required Tioli Netcool/OMNIbus. Performance reports are required for short data collection periods (typically 1 to 5 days) to match the length of the training course. Network Manager deployment A single-serer deployment is sufficient for this type of enironment. In addition to the single-serer deployment description proided elsewhere, the following deployment settings are appropriate for this type of enironment. System is an entry workstation class machine, with 4 to 6 GB of memory, dual-core processor preferred, single-core acceptable, reasonable current processor speed, and Fast Ethernet capability. IP6 dual stack support is required if workstations or network deices hae IP6. Default database used for the NCIM database. Client system: single processor, 3 GB of memory, supported JRE and Internet browser Chapter 1. Planning for installation 5

20 Small customer network This customer is a company with a network consisting of about network deices and key serers. The purpose of this installation is to manage this customer network by alerting the operations staff to major failures. The following sections describe this network in greater detail and proide suggestions for a Network Manager deployment to meet the needs of this network. Description The primary users of the product are the networking operations staff. All deices are in one location and managed by a small operations group of a few people. Network deices come from multiple endors. A mixture of layer 2 and layer 3 network deices are present. Approximately 20 to 30 VLANs are defined. The network architecture is fairly flat and simple. All deices to be managed are located in the same network as the Network Manager system and hae Fast Ethernet connections. Internet connections are passed through a firewall and access to the systems within the protected network is aailable through a company VPN. The network operations staff hae clients attached by means of one of the following: a local LAN, WiFi connections, or by means of a VPN established by a telecommunications serice proider. Network changes are made once a month and a new discoery is anticipated at this time. Within this enironment the following example conditions apply: 3 actie GUI clients. Chassis ping polling at two-minute interals. SNMP polling at 30 minute interals. Typically three to 6 SNMP MIB alues require polling. No major Tioli products are integrated with the system, other than the required Tioli Netcool/OMNIbus. Performance reports are required for data collection periods on the order of 31 days. Network Manager deployment A single-serer deployment is sufficient for this type of enironment. In addition to the single-serer deployment description proided elsewhere, the following deployment settings are appropriate for this type of enironment. A single network domain is sufficient for this size of network. System can be any of the supported platforms. System requires 6 to 8 GB of memory, dual-core processor, and multiple physical disks in RAID 5 configuration. Client system: single processor, 3 GB of memory, supported JRE and Internet browser Default database used for the NCIM database. A single ncp_poller polling engine is sufficient for this enironment. 6 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

21 Medium customer network This customer is a company with a central major data center and connections to seeral remote sites. The purpose of this installation is to manage this customer network by alerting the operations staff to major failures. The following sections describe this network in greater detail and proide suggestions for a Network Manager deployment to meet the needs of this network. Description This network has between 250 and 1000 network deices and key serers of interest. Workstations, while numbering in the thousands, are not managed. Network deices come from multiple endors. All deices in the central location hae Fast Ethernet or Gigabit Ethernet connections. Remote sites are connected by WAN connections. The deices and serers to be managed are distributed among the central and remote sites. Within this enironment the following example conditions apply: There are 5 to 20 actie GUI clients. Chassis ping polling at two to fie-minute interals. SNMP polling at fie to 15-minute interals. Other major Tioli products integrated with the system, other than the required Tioli Netcool/OMNIbus: IBM Tioli Monitoring with Tioli Data Warehouse running DB2 to support performance reporting. Performance reports are required for data collection periods on the order of 31 days. Network Manager deployment Each customer enironment with this kind of network is different. The key to success is adequate memory and a careful understanding of the polling targets, combined polling rates, and the eent rates. Based on these considerations, a single-serer deployment or a two-serer deployment is sufficient for this type of enironment. The following deployment settings are appropriate for this type of enironment. One or two network domains are required, depending on the size of network. Single serer deployment (up to 250 network deices and 5 to 10 concurrent users) Four processors 8 to 10 GB memory Multiple physical disks in RAID 5 configuration Two-serer deployment (up to 1000 network deices and 10 to 20 concurrent users) Four processors for system with Network Manager Four processors for system with Tioli Netcool/OMNIbus and Tioli Integrated Portal 8 GB memory for each serer Multiple physical disks in RAID 5 configuration System may be any of the supported platforms. Client system: single processor, 3 GB of memory, supported JRE and Internet browser Any supported RDBMS used for the NCIM database. Chapter 1. Planning for installation 7

22 Number of polling engines: Single-serer deployment: 1 Two-serer deployment: One poller for chassis pings, two or more pollers for SNMP polls Large customer network This customer is a large enterprise company with a globally deployed network. The purpose of this installation is to manage this customer network by alerting the operations staff to major failures and to support the latest network deices and network architecture. The following sections describe this network in greater detail and proide suggestions for a Network Manager deployment to meet the needs of this network. Description The architecture of the network is complex. and contains the most up to date technology. For example, the network contains MPLS core networks. The network deice count ranges from 1,000 to 12,000 deices, and the complexity of the network is reflected in the fact that there are 30 or more ports per deice on aerage. Network operations are done from a central location with operations staff constantly monitoring the core network. Network deices come from multiple endors. Within this enironment the following example conditions apply: There are typically 5 to 20 concurrently actie GUI clients. Polling: Chassis ping polling at two to 5 minute interals. SNMP polling at minutes. SNMP3 polling of key network deices SNMP1 polling for real time graphing as well as storage for performance reports. Other major Tioli products integrated with the system, other than the required Tioli Netcool/OMNIbus: IBM Tioli Monitoring (ITM) with Tioli Data Warehouse (TDW) running DB2 to support performance reporting. IBM Tioli Business Serice Manager (TBSM) IBM Tioli Application Dependency Discoery Manager (TADDM) Performance reports are required for data collection periods on the order of 31 days. Network Manager deployment Deployment choices ary depending on the size of the network. For the 1000 deice network in this customer range, the choice ranges from a single-serer to a two-serer deployment. Key factors for success include the network response time for the targets (gien that this is a county or global distribution of target deices), memory aailability on the supporting serers, the polling selected and the rates of polling. 8 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

23 For the top end of the network (approximately 12,000 deices), a distributed, multiple domain deployment is required. In addition to the multiple-serer deployment description proided elsewhere, the following deployment settings are appropriate for this type of enironment. Deploy two domains with two serers for each domain. Deployment of a dedicated database serer might be required. Each of the serers requires the following: Four processors. 8 GB of memory. 3 disk, RAID 5 multiple disk array For the systems used for each domain, deploy as follows: Serer 1: Network Manager Serer 2: Tioli Netcool/OMNIbus and Tioli Integrated Portal System 3 (optional): a customer-selected RDBMS supporting both domains Systems to be deployed on Linux or UNIX platform. Any supported RDBMS used for the NCIM database. Two polling engines: Use the default ncp_poller process for chassis ping. Create a separate ncp_poller for the SNMP polls. Client system: single processor, 3 GB of memory, supported JRE and Internet browser Very large customer network This customer is a ery large global enterprise company with a simple network architecture but ery large numbers of deices. The purpose of this installation is to manage this customer network by alerting the operations staff to major failures and to support short-term capacity planning. The following sections describe this network in greater detail and proide suggestions for a Network Manager deployment to meet the needs of this network. Description Network management is done from a central location and from regional locations. The network is ery large and contains oer 12,000 network deices and critical serers. Network deices come from multiple endors. The deices fall into two categories: Network deice infrastructure with interface counts in the range of 30 or more per deice. Managed deices with 1-2 interfaces per deice. The majority of the deices are in the second category, managed deices. To manage a network of this size, the network is partitioned for management on a geographical basis. Within this enironment the following example conditions apply: There are 5 to 20 actie GUI clients. Polling: Chassis ping polling at two to 5 minute interals. SNMP polling at 15 minutes or longer. Chapter 1. Planning for installation 9

24 SNMP1 data collection Other major Tioli products integrated with the system, other than the required Tioli Netcool/OMNIbus: IBM Tioli Monitoring (ITM) with Tioli Data Warehouse (TDW) running DB2 to support performance reporting. IBM Tioli Business Serice Manager (TBSM) IBM Tioli Application Dependency Discoery Manager (TADDM) Performance reports are required for data collection periods on the order of 31 days. Network Manager deployment Assistance from an experienced IBM serices group or qualified IBM business partner is highly adisable for a successful deployment. Multiple domains are needed, supported by a collection of indiidual serers, or running together on a ery large system. After completing a surey of the network to be managed, break the network up into sections that yield about K network entities, and then assign each of these sections be to a domain. In addition to the multiple-serer deployment description proided elsewhere, the following deployment settings are appropriate for this type of enironment. Multiple network domains. Platform selections: Linux and UNIX. Large systems (many processors and ery large amounts of memory) can host multiple domains as long as the memory allocations and processor counts are acceptable. Memory: 8-12 GB per domain Processors: 4-8 per domain depending on workloads Any supported RDBMS used for the NCIM database. Two polling engines for each domain: Use the default ncp_poller process for chassis ping. Create a separate ncp_poller for the SNMP polls. Indiidual process memory limitations are a factor in this enironment. Client system: single processor, 3 GB of memory, supported JRE and Internet browser Telecommunications company network This customer is a telecommunications company and internet serices proider. The purpose of this installation is to manage this customer network by alerting 24x7 network operations center staff to major failures. The following sections describe this network in greater detail and proide suggestions for a Network Manager deployment to meet the needs of this network. Description The network to be managed has about 300 network deices; with an aerage interface count per deice of 15. This is an MPLS network, and consequently the network deices are large in terms of their interface counts and complexity. Network deices come from multiple endors. All deices are in one or more locations and are managed by a small network operations group. All deices to be managed are connected ia Fast Ethernet or Gigabit Ethernet. 10 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

25 Within this enironment the following example conditions apply: Number of simultaneous actie clients: Polling requirements: chassis pings at two to 5-minute interals; SNMP polling of 5 alues at 5 minute interals. Some SNMP3 polling is in place. Other major Tioli products integrated with the system, other than the required Tioli Netcool/OMNIbus: IBM Tioli Monitoring (ITM) with Tioli Data Warehouse (TDW) running DB2 to support performance reporting. IBM Tioli Business Serice Manager (TBSM) IBM Tioli Application Dependency Discoery Manager (TADDM) Performance reports done once a day for key deices, used to assemble weekly capacity reports. Network Manager deployment A three-serer deployment is needed for this type of enironment. In addition to the multiple-serer deployment description proided elsewhere, the following deployment settings are appropriate for this type of enironment. One to two domains. A three-serer deployment is adised. System specifications: System 1: two to four processors, 6-8 GB of memory, two or more disks System 1 (where Network Manager is installed): four processors, 6-8 GB of memory, two or more disks. Note that beyond 4 processors or processor cores, the core clock speed and on-chip cache can be more important than additional cores. The general rule is as follows: select the fastest 4 cores before additional cores. System 2: two to four processors, 6-8 GB of memory, two or more disks System 3: database serer; processors, memory and disks selected by the DBA Any supported RDBMS used for the NCIM database. Two polling engines: Use the default ncp_poller process for chassis ping. Create a separate ncp_poller for the SNMP polls. Client system: single processor, 3 GB of memory, supported JRE and Internet browser Deployment considerations You can deploy your entire Network Manager installation on a single serer or as a distributed installation. During a Network Manager installation, you install the following four Network Manager components. Network Manager core This component consists of the core Network Manager processes: network discoery, polling, root cause analysis and eent enrichment. NCIM database This database stores topology data. Chapter 1. Planning for installation 11

26 Tioli Netcool/OMNIbus This component consists of the Tioli Netcool/OMNIbus eent management software. Many customers choose to hae a trouble-ticketing system integrated with Tioli Netcool/OMNIbus. Tioli Integrated Portal This component consists of the Tioli Integrated Portal user interface framework, together with the web applications. The objectie of the installation is to place these components on one or more serers. The following are typical Network Manager deployment configurations: Single-serer deployment Distributed deployment: two serers or more The factors that require an increased number of serers in a distributed deployment include the following: Actie eent rates Amount and rate of stored polling data Deice status polling rates and number of polling targets Network response times for polled targets Discoery frequency and Size of the network to be discoered (for each domain, where there are multiple domains) Note: These deployment configurations do not take into consideration requirements for other product integrations. In addition, you must consider deployment of appropriate systems to support GUI client sessions. Single-serer deployment Single-serer deployments are appropriate for small demonstration or educational systems, and for systems to support small to medium customer networks. A single-serer deployment must meet the following minimum specification: A minimum of two processors of current speeds, preferably four processors. Examples of current speeds include 3 GHz or better for processors from the Intel product line, and 1.6 GHz or better for processors from the Sun product line. A minimum of 6 GB of memory, preferably 8 GB. Distributed deployment: two serers or more In distributed deployments, Network Manager components are distributed across multiple serers, that is, two serers or more. Here are some guidelines for distributed deployments: Two-serer deployments are appropriate for the top end of the range of medium customer networks. Deployments might require three serers or more in situations where there are multiple network domains. 12 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

27 Three-serer deployments might also be deployed where it is determined that a separate serer is required to support a relational database product that proides topology data storage. In addition, a separate database serer enables the relational database to support multiple applications, in addition to Network Manager. Two-serer deployment An example of a two-serer deployment consists of the following allocation of host workstations: Serer 1: Network Manager core components and the NCIM database. The core components are the network discoery, polling, root cause analysis and eent enrichment components. Serer 2: Tioli Integrated Portal with associated Network Manager web applications. In this two-serer deployment, each serer must meet the following minimum specification: A minimum of two processors of current speeds, preferably four processors. A minimum of 4 GB of memory. For improed performance report response time, an enhanced disk I/O system, consisting of three to 6 physical disks in RAID supporting a logical olume. Three-serer deployment An example of a three-serer deployment consists of the following allocation of host workstations: Serer 1: Network Manager core components. Serer 2: Tioli Netcool/OMNIbus Serer 3: Tioli Integrated Portal with associated Network Manager web applications, together with the NCIM database. Client systems You must consider deployment of appropriate systems to support GUI client sessions. The following system specification proides support for a wide range of end-user actiities on GUI client sessions: Note: The web application clients, notably the Tioli Netcool/OMNIbus Web GUI Actie Eent List and the Network Manager Network Views, Hop View, and Structure Browser, are Jaa-based and therefore are dependent on the performance of the client system. Consequently, the more memory and CPU performance on the client system, the better. Larger display supporting comfortable iewing at higher resolution, such as 1280x1024 Current speed single or dual core processor 3 GB of memory Supported JRE and Internet browser Fast Ethernet. Processor specification: Chapter 1. Planning for installation 13

28 For normal topology displays or eent displays Single processor with the following speeds: 1 GHz or better, as found on many laptops, 2.4 GHz, as found in many workstations Enhanced time to display larger or complex topology maps and enhanced display of MIB graphs A ery current processor (3.0 GHz or better) typically aailable in the latest workstation class systems. Deployment examples Use these examples of Network Manager to help you plan your deployment architecture. Constraints for installing and starting components Some components must be installed and started before others. Use this information as well as the installation examples to understand the order in which you must install and start components. Topology database constraints You must install a topology database before you install the Network Manager core components, or as part of the same installation process. You must install a topology database before you install the Network Manager Web applications (including the Tioli Integrated Portal), or as part of the same installation process. You must create database tables only during the first installation of the Network Manager core components or the Network Manager Web applications (including the Tioli Integrated Portal), and not during subsequent installations. Tioli Netcool/OMNIbus constraints You must install Tioli Netcool/OMNIbus before you install the Network Manager Web applications (including the Tioli Integrated Portal), or as part of the same installation process. Web application constraints You must install the Network Manager core components before you install the Network Manager Web applications, or as part of the same installation process. If you are using ObjectSerer authentication for the Network Manager Web applications, Tioli Netcool/OMNIbus must be running during the installation of the Network Manager Web applications. Starting components in the right order Do not start the Network Manager core components until the installation of the Network Manager Web applications is complete. Ensure that both Tioli Netcool/OMNIbus and the topology database are running before starting the Network Manager core components. 14 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

29 Ensure that Tioli Netcool/OMNIbus, the topology database, and the Network Manager core components are running before using the Network Manager Web applications. Related reference: Serer allocation for failoer on page 251 Any primary system must be installed on a separate host to a backup system, so that if the primary host fails, the backup host is unaffected. Example simple deployment architecture Use this example to familiarize yourself with the architecture of a simple Network Manager deployment. Components This example simple deployment consists of the following components: One ObjectSerer irtual pair. One Tioli Integrated Portal serer. One Network Manager installation running one domain with failoer. One instance of the NCIM topology database. The following figure shows the architecture for this deployment. Webtop Client Network Views Tioli Integrated Portal NCIM topology database ObjectSerer irtual pair Network Manager Figure 1. Simple deployment architecture Allocation of host workstations The following figure shows an example allocation of host workstations for this deployment. Note: If you hae a particularly large topology, you might want to install the topology database on its own serer. This decision depends on the specification of Chapter 1. Planning for installation 15

30 your machines and how you want to spread the load between them. Host Machine 1 Host Machine 2 Host Machine 3 Primary ObjectSerer Bi-directional Gateway Primary Network Manager installation Tioli Integrated Portal Backup Network Manager installation Backup ObjectSerer NCIM topology database Figure 2. Simple deployment host machine allocation Steps to install a simple deployment The following steps proide an oeriew of the tasks required for this deployment, and help plan for a similar deployment.. To install the deployment described aboe, perform the following steps: 1. Install the topology database on host machine 3, create the necessary tables, and start the database. Note: The topology database must be installed and started before you start the Network Manager core components so that discoery data can be saed. 2. Install the following ObjectSerers and related components: a. Install the primary ObjectSerer and the Bi-directional Gateway on host machine 1. b. Install the backup ObjectSerer on host machine Configure and run the ObjectSerers. Note: The ObjectSerers must be running before the Network Manager core components are started. 4. Install the primary Network Manager core components on host machine Install the backup Network Manager core components on host machine Install the Network Manager Web applications on host machine 3 (part of the GUI components category in the installation wizard). The Tioli Integrated Portal serer is automatically installed with the installation of the Network Manager Web applications. Tip: If you install the Tioli Integrated Portal on a machine with no other products, performance is likely to be better than if you install it on a machine with other products. When you install the Network Manager web applications, the Tioli Netcool/OMNIbus Web GUI is installed and automatically configured on host 16 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

31 machine 3 if it is not already installed there. The Tioli Netcool/OMNIbus Web GUI was known as Netcool/Webtop in ersions 2.2 and below. Note: The Network Manager core components must be installed before the Web applications. 7. Configure the primary Network Manager for failoer and start it. 8. Configure the backup Network Manager for failoer and start it. Example large deployment architecture Use this example to familiarize yourself with the architecture of a large Network Manager deployment. Components This example deployment consists of: One ObjectSerer and one Network Manager installation in London. The London domain sends eents and topology to San Francisco. One ObjectSerer and one Network Manager installation in New York. The New York domain also sends eents and topology to San Francisco. One ObjectSerer and one Tioli Integrated Portal installation in San Francisco. The ObjectSerer in San Francisco consolidates the eents from London and New York. The Tioli Integrated Portal serer in San Francisco can access topology from both London and New York, but does not consolidate the topologies. Clients anywhere in the world can connect to the Tioli Integrated Portal serer, and iew topology from London and New York. The following figure shows the architecture for this deployment. Chapter 1. Planning for installation 17

32 London host machine 1 San Francisco host machine 1 New York host machine 1 Network Manager Tioli Integrated Portal Network Manager London host machine 2 San Francisco host machine 2 New York host machine 2 Uni-directional Gateway ObjectSerer Uni-directional Gateway ObjectSerer San Francisco host machine 3 ObjectSerer NCIM topology database Figure 3. Large deployment architecture Allocation of host workstations The following figure shows an example allocation of serers for this deployment. 18 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

33 London office Head office San Francisco New York office Network Manager Serer domain= LONDON NCIM topology database Network Manager Serer domain= NY Remote client Tioli Integrated Portal Remote client ObjectSerer LONDON ObjectSerer SANFRAN ObjectSerer NY Figure 4. Large deployment host machine allocation Steps to install a large deployment The following steps proide an oeriew of the tasks required for this deployment, and help plan for a similar deployment.. To install this deployment, perform the following steps: 1. Install the topology database on San Francisco host machine 3, and create the necessary database tables. Note: The topology database must be installed and started before you start the Network Manager core components so that discoery data can be saed. 2. Install the following ObjectSerers and related components: Install the ObjectSerer on San Francisco host machine 2. Install the ObjectSerer and the uni-directional gateway on London host machine 2. Install the ObjectSerer and the uni-directional gateway on New York host machine Configure and run the ObjectSerers. Note: The ObjectSerers must be running before the Network Manager core components are started. 4. Install the Network Manager core components on London host machine 1. Note: The Network Manager core components must be installed before the Web applications. 5. Install the Network Manager core components on New York host machine 1. Chapter 1. Planning for installation 19

34 Network domains 6. If a ersion of Tioli Netcool/OMNIbus Web GUI earlier than ersion is already present on host machine 3, then upgrade this to the Tioli Netcool/OMNIbus Web GUI ersion Network Manager is not compatible with earlier ersions of the Tioli Netcool/OMNIbus Web GUI. 7. Install the Network Manager Web applications on host machine 3 (part of the GUI components category in the installation wizard). The Tioli Integrated Portal serer is automatically installed with the installation of the Network Manager Web applications. Tip: If you install the Tioli Integrated Portal on a machine with no other products, performance is likely to be better than if you install it on a machine with other products. When you install the Network Manager web applications, Tioli Netcool/OMNIbus Web GUI ersion 7.4 is installed and automatically configured on host machine 3 if it is not already installed there. Before installing, you need to consider whether to partition your network into domains, or hae a single domain for the entire network. A network domain is a collection of network entities to be discoered and managed. Restriction: Only alphanumeric characters and the underscore (_) character may be used for domain names. Any other characters, for example the hyphen (-) are forbidden. Reasons for partitioning your network into multiple domains Partitioning your network into domains allows you to discoer your network in sections. Reasons for partitioning your network include: Scalability: Your network might be too big to be discoered in one piece. Geography: You might want to break the network into geographical regions, and make each region correspond to a domain. Logical network boundaries: You might want to discoer and manage the network based on particular network boundaries. Discoered domains can be monitored separately. You can run multiple domains in order to perform multiple network discoeries, and multiple Network Manager processes can run independently of each other on the same serer if they belong to different domains. Identifying the domain of an eent Identifying the domain of an eent enables the Network Views and Hop iew to generate the correct topology map for that eent. The domain in which an eent originates can be identified in the following ways: By using one domain per ObjectSerer and using the name of the ObjectSerer to identify the domain from which the eent originates. If using multiple domains per ObjectSerer, probes in each domain need to be configured to enable the eent itself to hold information that identifies the domain. This approach enables multiple Network Manager domains to be connected to a single ObjectSerer. 20 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

35 Related concepts: Guidelines for number of network domains on page 3 If your network exceeds a certain size, you might need to break up the network into multiple domains. Use this information to work out the number of network domains needed for your deployment. Related tasks: Creating and configuring extra network domains on page 294 If your deployment requires additional network domains, you must configure process control for the domains and register the domains with the NCIM topology database. You can also migrate the configuration and network polls from an existing domain to the new domains. Eent collection using one domain per ObjectSerer You can configure independent Network Manager domains by using a collection ObjectSerer and an aggregation ObjectSerer. Restriction: The architecture described in this topic is only applicable to Tioli Netcool/OMNIbus ersions or earlier, and is based on the standard architecture from the Eent Serices Framework (ESF) that was preiously released by the IBM Tioli Netcool Adanced Architecture Group. The collection ObjectSerer collects eents from the probes that are connected to each domain, whereas the aggregation ObjectSerer gathers eents from each of the collection ObjectSerers. As a result the Network Manager domains are independent. One domain can be up while the other is down for maintenance. Furthermore, the scopes of the discoery can oerlap. This structure is flexible as additional ObjectSerers can be added when new domains are required, proiding scalability when working with large networks. Howeer, this approach requires multiple ObjectSerers and therefore may only be of interest to customers with larger networks. The following figure shows an example architecture using one domain per ObjectSerer. Chapter 1. Planning for installation 21

36 Domain A eents eents Domain B Aggregation ObjectSerer Collection ObjectSerer Webtop Web Applications Collection ObjectSerer eents Eent Gateway Tioli Integrated Portal Eent Gateway eents Probes Probes Network Manager domain=a topology NCIM topology database topology Network Manager domain=b Network Operations Center Figure 5. Managing eent ownership: architecture for single-domain ObjectSerers Eent collection using multiple domains per ObjectSerer You can connect multiple Network Manager domains to a single ObjectSerer. In this configuration, the Tioli Netcool/OMNIbus probes collect information on the name of the domain when an eent is generated and populate the NmosDomainName field to hold this domain name. To implement this configuration you must first modify all Tioli Netcool/OMNIbus probe rules files to ensure that each eent contains an NmosDomainName field. This field is used to store the domain name associated with the eent. This also ensures that the eent is processed by the Eent Gateway. Note: The incoming eent filter in the Eent Gateway handles both single-domain and multi-domain systems by default. For more information see the IBM Tioli Network Manager IP Edition Eent Management Guide. Note: This is a less expensie approach as it requires a single ObjectSerer only. Scalability might be an issue as each new domain requires extra probe configuration. The following figure shows an example architecture using multiple domains per ObjectSerer. 22 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

37 Domain A Domain B tagged eents NmosDomainName= B filter NmosDomainName= A single ObjectSerer filter NmosDomainName= B WebGUI Web applications Eent Gateway Tioli Integrated Portal Eent Gateway Probe Probe Network Manager domain=a topology NCIM topology database topology Network Manager domain=b Network Operations Center Figure 6. Managing eent ownership: architecture for multiple-domain ObjectSerer Example isualization of topology from multiple domains Web clients using a single Tioli Integrated Portal can iew topology from more than one Network Manager domain. Multiple domains held in one topology database To enable topology isualization from multiple domains, each Network Manager domain forwards topology information to the Network Connectiity and Inentory (NCIM) topology database. When you hae multiple domains, the topology from each domain is held in NCIM. Linking discoered domains You can find links between deices in different domains by configuring and running a cross-domain discoery. The following figure shows an example of three discoery domains feeding data into a single NCIM topology database. All web clients connected to the Tioli Integrated Portal can iew topology maps in any of the domains by choosing a single domain from the domain menu. Chapter 1. Planning for installation 23

38 Network Manager Domain = TOKYO Network iews Network Manager Domain = LONDON NCIM topology database Tioli Integrated Portal Hop iew Network Manager Domain = PARIS Hardware requirements Figure 7. Viewing topology from multiple domains If cross-domain discoeries hae been run, an aggregated domain is created in the topology database, which includes deice collections from all discoered domains. All web clients connected to the Tioli Integrated Portal can iew topology maps in all domains by choosing the AGGREGATION domain from the domain menu. For more information on iewing topology, see the Network Manager Topology Visualization Guide. Hardware requirements ary according to the size and composition of your network and the features of Network Manager you want to use. Ensure that your serers meet the hardware requirements before you install Network Manager. Important: Do not run any other resource-intensie applications during the installation of Network Manager. 24 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

39 Processor selection guidelines Read about guidelines for processor requirements before selecting the right serer to install Network Manager on. The guidelines discussed here are for serers expected to support only Network Manager components. The guidelines assume the deployment of other Tioli products, such as IBM Tioli Monitoring, Tioli Data Warehouse, and IBM Tioli Business Serice Manager on other serers. To combine the deployment of multiple major products on a single serer, add the minimal requirements for each product together (see the indiidual product documentation for more information). For small customer networks and demonstration or educational system deployments, use two processors at least on all platforms. Deployments of medium or large customer networks require four processors. Note: For multiple core processors, indiidual core speed can be more important than the number of cores. While processors of any speed can be used, selecting the fastest core speed and largest on-chip cache makes a significant difference depending on the size of the network being discoered and polled. For irtualized settings (supported by VMWare ESX) use both processor and memory resources fixed to a irtual system supporting Network Manager. For more details on processor selection and other deployment considerations, see Deployment of Network Manager on page 1. Requirements to run the installer To install any components of Network Manager, your serer must meet the hardware requirements. Disk space requirements for the installer You need a certain amount of space free in certain directories to be able to run the installer, regardless of which components you are installing. On UNIX operating systems, you need at least 1 GB space in the /tmp directory and at least 350 MB space in the /usr directory, and 500 KB in the /ar directory. If you install Network Manager into any location other than /opt, you must hae at least 50 MB of space in the /opt directory. Disk space requirements for installing as a non-root user On UNIX operating systems, if you are installing as a non-root user, you must hae at least 350 MB space free in your home directory to store files related to the installation. Chapter 1. Planning for installation 25

40 Requirements for the core components To install the Network Manager core components, your serers must meet the minimum hardware requirements. Memory requirements Ensure that the serer where you want to run Network Manager meets the following memory requirements. For a single-serer deployment, where the Network Manager core components, Web applications, topology database, and Tioli Netcool/OMNIbus are all on the same serer, you need a minimum of 8 GB DRAM, preferably more for large networks. For a distributed deployment, where only the Network Manager core components are installed on the serer, you need a minimum of 4 GB DRAM. These are minimum requirements, and the amount of memory required will ary depending on the size of the network to be managed and how you deploy Network Manager. For more information, see Deployment of Network Manager on page 1. Disk space requirements Ensure that the serer where you want to run Network Manager meets the following disk space requirements. 4 GB hard disk space to store the software 4 GB hard disk space per domain for cache storage As a guidance estimate for log files, assuming that each log file is 1 GB in size and six processes are set to full debug leel, you would require 24 GB of disk space. (6 processes x 4 log or trace files each = 24 log or trace files x1gb=24 GB). 50 GB free disk space to run Network Manager. These are minimum alues for guidance, and the amount of disk space required will ary depending on the size of the network to be managed and how you deploy Network Manager. For more information, see Deployment of Network Manager on page 1. Bandwidth requirements The Network Manager serer requires a 100 Mbps full duplex fast Ethernet connection (or equialent) with the DNS serer. It is required that the systems supporting Network Manager components are placed in the data center with LAN speed connections of 100 Mbps fast Ethernet or Gigabit Ethernet to the DNS system and the core network deices to be discoered and managed. Slower connection speeds can be used, but might impact client session response times and must be factored into key workloads such as polling (including response times, retry count, and total network traffic introduced). Note: During the discoery of a network deice, many SNMP queries are made of that deice. After discoery, routine polling (ICMP and SNMP) can introduce significant traffic on the network. With the supporting network hosted by modern LAN speeds, these workloads can be accommodated. 26 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

41 For more details on discoery bandwidth requirements, see Bandwidth requirements for discoery on page 29. Other requirements You also need a DVD drie, if you are not installing the software from a download. Requirements for the GUI components The serer on which you install the GUI components of Network Manager (also referred to as Web Applications, which includes Tioli Integrated Portal and Tioli Netcool/OMNIbus Web GUI) must meet the following hardware requirements. 5.5 GB hard disk space. A minimum of 4 GB DRAM. Note: The installer checks to ensure a minimum of 3 GB DRAM is aailable to accommodate demonstration and educational system deployments. Howeer, a minimum of 4 GB DRAM is required in production enironments. 500 MB in the /tmp directory. DVD drie if not installing from download. Hardware requirements for Tioli Common Reporting To enable network management reports, you must hae Tioli Common Reporting installed. Tioli Common Reporting is an optional component that needs to be installed separately to be able to use the reporting feature of Network Manager. Reiew the hardware requirements for Tioli Common Reporting to make sure you meet your performance requirements. For detailed information on hardware requirements for Tioli Common Reporting, see the Tioli Common Reporting information center at the following URL: com.ibm.tioli.tcr.doc_211/rtcr_soft_and_hard_reqs.html Installation directory requirements If you are installing Network Manager GUI components including the Tioli Integrated Portal proided, do not install into a directory that already contains any ersion of Tioli Integrated Portal. Requirements for the topology database serer Read about Network Manager topology database requirements. Disk space requirements To store Network Manager data, ensure you hae at least 5 GB disk space aailable for your topology database. Note: These figures are minimum alues. The actual disk space required depends on the size of your network and the amount of data stored. The storage of performance data can require a large amount of disk space. If you are planning to store such large amounts of data, consider 50 GB for Network Manager-related disk space. Chapter 1. Planning for installation 27

42 For a large network contained within a single domain you should hae 5 GB for the topology data, and a total of 50 GB to coer storage data as well. For more information about planning the Network Manager deployment for your network including considerations for size and domains, see Deployment of Network Manager on page 1. Ensure that the serer where you want to run the topology database meets the following disk requirements: Three disks in RAID 1 configuration (more disks for RAID 5) High speed SATA or SCSI disks Disk space for eents and interfaces You must calculate and allow additional disk space for the number of eents and interfaces on your installation. The additional hardware requirements for Network Manager are as follows: 4 KB of disk space for each expected eent, per day of storage required 4 KB of disk space for each interface or port on a managed deice For example, if you hae 5000 ports on deices in your network, expect 3000 eents each day and require eents to be stored for 30 days, you require: 3000*30*4KB=360MB The total disk space required is therefore: 512 MB MB cache MB + (4 KB * 5000) = 1.4GB Swap space requirements (UNIX) On UNIX platforms, you must ensure that you hae adequate free disk space that is configured to be used as swap space. The exact amount of swap space needed depends on the size and composition of your network and the type of discoery. For smaller amounts of physical RAM, you need proportionally greater amounts of swap space. The following figures show the approximate amount of swap space depending on the amount of physical RAM. 4GB RAM Configure 10GB swap space. 8GB RAM Configure 16GB swap space. 12GB RAM Configure 18GB swap space. For amounts of RAM greater than 12 GB, configure the same amount of swap space. For example, for 24GB RAM, configure 24GB swap space. 28 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

43 Bandwidth requirements for discoery Network discoery operations require a minimum of broadband connection speed. Do not attempt discoeries oer dial-up connection speeds. If the connection speed is not sufficient, packets might be lost due to the amount of SNMP traffic that is generated by the default discoery and monitoring operations. Een oer a broadband connection, the number of SNMP helper threads must be kept low. This might cause the discoery to take a long time. Discoeries should be run using an Ethernet (or similar speed) connection. The required speed of the Ethernet connection depends on the size of your network: 10 Mbps full duplex speed is required to support up to 100 SNMP helper threads and a relatiely low number of deices. If you are using Telnet with SSH to access many deices in the discoery, the number of SNMP helper threads should be reduced due to the bandwidth used by the Telnet Helper. 100 Mbps full duplex fast ethernet connection (or equialent) is required for discoering a large network. Bandwidth should not be a problem oer a 100 Mbps connection regardless of the number of SNMP helper threads used, unless there are other bandwidth-hungry applications sharing the link. The aboe figures assume an aerage round trip time for an SNMP packet is 10 milliseconds, and the aerage SNMP packet size is around 125 bytes. This means each SNMP helper thread could transmit 12,500 bytes per second, and retriee 12,500 bytes per second, which equals 100,000 bits per second. If there are 20 threads, then 20 multiplied by 100,000 equals 2,000,000 bits per second, which is 2 Mbps. For 100 threads, the figure is 10 Mbps. By default, the SNMP helper runs 120 threads. These estimates assume that eery thread in the SNMP helper is in full operation at the same time, which is generally not the case. Howeer, if there is insufficient bandwidth, the UDP packets used to transport SNMP could either be lost, or the packets might queue up in the network and arrie with a delay. For more information on configuring the SNMP helper, see IBM Tioli Network Manager IP Edition Discoery Guide. Discoery memory requirements When discoering ery large networks, the discoery process (ncp_disco) and the topology model process (ncp_model) use the most memory. If the network is ery large, consider diiding it into multiple domains. Related concepts: Guidelines for number of network domains on page 3 If your network exceeds a certain size, you might need to break up the network into multiple domains. Use this information to work out the number of network domains needed for your deployment. Chapter 1. Planning for installation 29

44 Software requirements Software requirements ary according to the operating system, products, and features of Network Manager that you want to use. Requirements for other products Make sure that you meet the requirements for the products that are integrated with Network Manager. Extra product requirements Important: These requirements are in addition to any other hardware, software, installation directory, user or other requirements discussed in the indiidual product documentation. Ensure that you are familiar with all of the requirements and prerequisites before installing any product. Tioli Netcool/OMNIbus Make sure that Tioli Netcool/OMNIbus V7.3.1 or V7.4 is installed on a serer to which Network Manager can connect. If you do not hae an installation of Tioli Netcool/OMNIbus, you must install it. You must download Tioli Netcool/OMNIbus separately. If you choose the option to install eent management software, and supply the location of the downloaded package or installation media, you can install Tioli Netcool/OMNIbus as part of the Network Manager installation. The Network Manager installer expects to install Tioli Netcool/OMNIbus V7.4. You can also installtioli Netcool/OMNIbus V7.3.1 using the Network Manager installer: in this case, create a subdirectory called OMNIbus in the top-leel directory of the extracted Network Manager installation package, and extract the downloaded Tioli Netcool/OMNIbus package into this directory. If you install Tioli Netcool/OMNIbus not using the Network Manager installer, you must install from a different window to that used to install Network Manager, ensuring that any enironment ariables are set correctly according to the Tioli Netcool/OMNIbus documentation. The Tioli Netcool/OMNIbus Web GUI The Tioli Netcool/OMNIbus Web GUI was known as Netcool/Webtop in ersions 2.2 and below. If you install the Web GUI not using the Network Manager installer, you must install from a different window to that used to install Network Manager, ensuring that any enironment ariables are set correctly according to the Tioli Netcool/OMNIbus documentation. Tioli Common Reporting To enable network management reports, you must hae Tioli Common Reporting installed. Network Manager installs the reports package required for network management reports on the serer where the Network Manager GUI components are installed. If the chosen installation location for Network Manager already has existing Tioli Integrated Portal and Tioli Common Reporting instances, then Network Manager automatically configures the reports to be used with that Tioli Common Reporting instance. If you do not hae Tioli Common Reporting installed when installing Network Manager, you can install Tioli Common Reporting at a later date and configure the reports then as described in Configuring reports for existing installations on page IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

45 Restriction: Tioli Common Reporting ersion is not supported on Red Hat Enterprise Linux 6.0. If you want to run network management reports using Network Manager's reporting feature, you must install the Network Manager GUI components and Tioli Common Reporting on another supported operating system other than Red Hat Enterprise Linux 6.0. IBM Tioli Business Serice Manager You must install IBM Tioli Business Serice Manager from a different window to that used to install Network Manager, ensuring that any enironment ariables are set correctly according to the IBM Tioli Business Serice Manager documentation. Preious ersions Install Network Manager 4.1 in a different directory to Network Manager V3.9 or earlier, and Netcool/Webtop V2.1 or earlier. Related tasks: Configuring integrations with other products on page 151 You can set up Network Manager to work with a number of Tioli products. Read about necessary configuration tasks required to set up the aailable integrations. Compatibility with other Tioli products Network Manager is compatible with other Tioli products, proiding options for integrating with other products to build a solution to address your requirements. The following table describes the compatibility of Network Manager V4.1 with other Tioli products. Table 3. Compatibility of Network Manager with other products Product Compatible ersions IBM Tioli Netcool/OMNIbus Tioli Netcool/OMNIbus Web GUI (using Tioli Integrated Portal 2.2) 7.4 IBM Tioli Netcool Configuration Manager Tioli Integrated Portal 2.2 Note: Network Manager 4.1 uses Tioli Integrated Portal by default (installed by the Tioli Netcool/OMNIbus Web GUI component). Products integrating with Network Manager 4.1 must support Tioli Integrated Portal or later. To use certain browser ersions, you might need to upgrade to later Tioli Integrated Portal ersions. For more information, see Supported browsers for Web applications on page 34. Tioli Common Reporting IBM Tioli Application Dependency Discoery Manager and IBM Tioli Change and Configuration Management Database Chapter 1. Planning for installation 31

46 Table 3. Compatibility of Network Manager with other products (continued) Product Compatible ersions IBM Systems Director IBM Tioli Business Serice Manager IBM Tioli Monitoring Fix Pack 3 or later Supported topology databases IBM DB2 Uniersal Database ersion 10.1 is the default topology database for Network Manager V4.1. Network Manager also supports IBM DB2 Uniersal Database ersion 9.7. For a matrix of supported operating systems and databases, see the detailed system requirements document at: Important: Ensure that your database has all the recommended patches applied, including the latest patch leels. Important: The Network Manager V4.1 installer includes installation of DB2, either as a DB2 serer for a single-serer installation, or as a DB2 client to enable Network Manager V4.1 to talk to an existing DB2 serer installation. If the installing user has an existing DB2 client already defined in their enironment (for example, in the PATH or LD_LIBRARY_PATH enironment ariables) and this ersion of DB2 is different to the V10.1 ersion being used by Network Manager V4.1, then the existing DB2 client might interfere with the Network Manager V4.1 DB2 installation. Any references to an existing DB2 installation on the serer should be remoed from the enironment of the user that is installing Network Manager V4.1. The prerequisite checking utility performs a check to determine if there are any existing references to DB2 in the enironment. Related tasks: Setting up a topology database on page 44 You must configure an existing database or install and configure a new one to use as the topology database for Network Manager. Supported operating systems Network Manager is supported on the following operating systems. For the most current information about supported operating systems, see the detailed system requirements document at: Important: Ensure that your operating system has all the recommended patches installed, including the latest patch leels. On Intel and Adanced Micro Deices (AMD) x86 processors, the following ersions are supported: Red Hat Enterprise Linux 5 (x86-64) 32 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

47 Red Hat Enterprise Linux 6 (x86-64) Note: Network Manager 4.1 only supports installing on 64-bit hardware. You can reuse 32-bit components such as 32-bit installations of Tioli Integrated Portal and Web GUI when installing Network Manager 4.1 on a 64 bit machine. The Network Manager GUI components will work with existing 32-bit Tioli Integrated Portal and Web GUI installations. Note: On Red Hat Enterprise Linux 6, you must hae the 32-bit Red Hat Enterprise Linux libraries installed in addition to the 64-bit libraries. The default 64-bit Red Hat Enterprise Linux 6 installation does not include the 32 bit libraries. Restriction: If you hae an existing 32-bit Tioli Integrated Portal and no Web GUI installation on the serer you are installing the Network Manager GUI components on, then you must install a 32-bit Web GUI before installing the Network Manager GUI components, or remoe the 32-bit Tioli Integrated Portal and use the Network Manager installation process to install a 64-bit Web GUI and Tioli Integrated Portal. The Network Manager installer only installs 64-bit Web GUI, and that installs a 64-bit Tioli Integrated Portal. Attention: Network Manager uses the JVM ersion used by Tioli Integrated Portal on the serer hosting the GUI components. This means that if you hae a 64-bit Tioli Integrated Portal, then Network Manager runs against a 64-bit JVM, but if you hae a 32-bit Tioli Integrated Portal, then Network Manager runs against a 32-bit JVM. Restriction: Tioli Common Reporting ersion is not supported on Red Hat Enterprise Linux 6.0. If you want to run network management reports using Network Manager's reporting feature, you must install the Network Manager GUI components and Tioli Common Reporting on another supported operating system other than Red Hat Enterprise Linux 6.0. Attention: Make sure you disable Security-Enhanced Linux (SELinux) or set it to permissie in the selinux configuration file before attempting to install Network Manager. Linux systems running Security-Enhanced Linux (SELinux) are not supported. Also, Linux systems running AppArmor are not supported. Disable AppArmor to allow the installation to continue. Additional requirements for Tioli Common Reporting on Linux Ensure your system meets the following requirements for Tioli Common Reporting: On all ersions of Linux, make sure you hae the libxm.so.3 or later (aailable from the openmotif RPM 22 or later) aailable on your system before the installation. For ersions of libxm.so.x later than libxm.so.3, make a symbolic link from the later ersion to libxm.so.3, using a command similar to the following example: ln -s /usr/lib/libxm.so.4 libxm.so.3. For detailed information on software requirements for Tioli Common Reporting, see the Tioli Common Reporting information center at the following URL: com.ibm.tioli.tcr.doc_211/rtcr_soft_and_hard_reqs.html Restriction: Tioli Common Reporting ersion is not supported on Red Hat Enterprise Linux 6.0. If you want to run network management reports using Chapter 1. Planning for installation 33

48 Network Manager's reporting feature, you must install the Network Manager GUI components and Tioli Common Reporting on another supported operating system other than Red Hat Enterprise Linux 6.0. Additional requirements for Red Hat Enterprise Linux AS, ES, and WS 5 If installing Network Manager on Red Hat Enterprise Linux AS, ES, or WS 5, you must ensure that the following RPMs are aailable on your system before the installation: compat-libstdc libxp openmotif libxmu libxpm compat-libstdc These files should be aailable on the installation CDs for the operating system. For more information about obtaining packages, go to the IBM WebSphere Application Serer Information Center at infocenter/wasinfo/6r1/index.jsp, and search for the package name. Additional requirement for Linux systems Make sure you hae both the 32 bit and 64 bit ersions of the pam el6.system packages installed. Supported browsers for Web applications Ensure that clients use one of the supported Web browsers. If your Web browser is not supported, a Web application might hang or crash. The following table describes the supported Web browsers and the Jaa Runtime Enironment (JRE) ersions for each client operating system. 34 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

49 Table 4. Supported Web browser ersions for client operating systems Web browser Client operating system Internet Explorer 8.0 and 9.0 Windows XP Serice Pack 3 Note: Network Manager 4.1 includes Tioli Integrated Windows 7 Enterprise Portal which supports Internet Explorer 9.0. Windows Vista Enterprise Windows Serer 2008 (R1) Standard Edition Windows Serer 2008 (R1) Enterprise Edition Windows Serer 2008 (R2) Datacenter Edition Windows Serer 2008 (R2) Enterprise Edition Jaa Runtime Enironment (JRE) ersion IBM 1.7 and Oracle 1.7 Mozilla Firefox 17 Extended Support Release (ESR) Note: You must hae Tioli Integrated Portal or later to use Firefox 17 ESR. For more information, see the section about upgrading to Tioli Integrated Portal in Postinstallation tasks on page 81. Windows Serer 2008 (R2) Standard Edition Red Hat Enterprise Linux Desktop 5.0 and 6.0 Red Hat Enterprise Linux (RHEL) 5.0 and 6.0 SuSE Linux Enterprise Desktop (SLED) 10 and 11 SuSE Linux Enterprise Serer (SLES) 10 and 11 Solaris 9, 10, and Zones SPARC Windows XP Serice Pack 3 Windows 7 Enterprise Windows Vista Enterprise Windows Serer 2008 (R1) Standard Edition Windows Serer 2008 (R1) Enterprise Edition Windows Serer 2008 (R2) Datacenter Edition Windows Serer 2008 (R2) Enterprise Edition Windows Serer 2008 (R2) Standard Edition IBM 1.7 (not on Solaris) and Oracle 1.7 Tip: If you are using Mozilla Firefox on UNIX operating systems, refer to the Firefox documentation to ensure that the Jaa plugin is correctly installed, and that any symbolic links that might be necessary hae been made. Chapter 1. Planning for installation 35

50 Supported browsers for the installer launchpad To run the installer launchpad, you must hae a supported browser installed. List of supported browsers The supported browsers for the installer launchpad are described in the following table. Important: The supported browsers for the installer launchpad are not necessarily the same as the supported browsers for the Web applications. Note: To use the launchpad, you must hae the xterm command installed on this system. Table 5. Supported browsers for the installer launchpad Browser Version Firefox 2.0 and aboe Mozilla 1.7 and aboe Internet Explorer 5.5 and aboe SeaMonkey and aboe Operating system tools Because the stability of the installation process depends on the stability of the Operating System (OS) tools, ensure that the OS ersions of standard tools are included in your path before non-os ersions of the same tools (for example, GNU utilities). Domain Name Serice (DNS) requirements Ensure that your serers hae DNS set up correctly before installing Network Manager. Domain names Ensure that all serers onto which you want to install any components of Network Manager hae the host name defined as a fully qualified domain name. Incomplete or incorrect DNS setup can cause problems installing or using Network Manager. On UNIX platforms, the host name is defined in the /etc/hosts file. Restriction: Do not use underscore when specifying host names. Use of underscores as part of a host name causes the installation of the Tioli Integrated Portal to fail. 36 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

51 UNIX user restrictions On UNIX operating systems, if you hae installed other Tioli network management products on a particular serer, you must install Network Manager into the same directory as the same user. If you install the Network Manager Web applications as the root user, Network Manager will not integrate with IBM Tioli Business Serice Manager. If you want to use Network Manager with TBSM, you must create a different user to install and manage all Tioli products on this serer. If you install Network Manager as a non-root user, you must perform extra post-installation configuration steps in order to run the core components as the root user. If you install Network Manager as a non-root user, you must install all future Tioli products as the same user. If you install and run Network Manager as a non-root user, then it is not possible to hae two ersions of Network Manager installed on the same serer. Related tasks: Configuring root/non-root permissions on page 213 On UNIX, if you installed Network Manager as a non-root user, you must perform additional configuration. Installation directory requirements The directory where you install Network Manager must fulfill certain requirements. Requirements on all operating systems By default, the installer places Tioli Network Management products into the same directory. The full path to the installation directory must contain only alphanumeric characters (A-Z, a-z, 0-9), dashes, underscores, periods, colons, slashes, or spaces. Requirements on UNIX operating systems The user installing Network Manager must hae write permission to the installation directory, and if different, the /opt directory. Requirements for the installer The installer installs files in the main installation directory that you choose during the installation process. It also installs files in other directories, depending on the operating system being installed on and the user performing the installation. Reiew the default directory structure and ensure that the user performing installation has write access to the releant directories. Related reference: Default directory structure on page 289 Use this information to understand the Network Manager directory structure. Chapter 1. Planning for installation 37

52 File handle requirements On UNIX and Linux operating systems, ensure that there are enough file handles allowed. If you are installing Network Manager on a UNIX or Linux operating system, ensure that the number of open files for processes is set to 8192 in all enironments for the user who runs Network Manager. You can check this alue by issuing the following command as the user who is running Network Manager: ulimit -n If this alue is less than 8192, please contact your system administrator to increase the alue appropriately for your user. The following are examples of using the command to increase the alue: Linux ulimit -n 8192 Also ensure you hae the number of processes per user set to a minimum of You can check this alue using the following command: ulimit -u Note: The 1024 alue is a minimum one and this alue might need to be adjusted for your enironment based on your needs. Requirements for charting Charting is an optional component that enables you to display charts from supported Tioli products and charts that were created with the Business Intelligence and Reporting Tools Designer. The Charting option also installs the ITM Web Serice with the Tioli Integrated Portal Serer. When Tioli Management Serices is part of your networked enterprise, the ITM Web Serice is used to query attribute alues collected by your IBM Tioli Monitoring or OMEGAMON XE products and retriee them to chart portlets in the console. Important: If your installation will use the ITM Web Serice, be sure to read Configuring SSO between Charting and Tioli Monitoring on page 300 before installing Tioli Integrated Portal. Your product may already come with predefined charts or perhaps the chart format is not appropriate for your product. In either case, you will not see the Charting option during an adanced installation if it is not offered with your product. Secure Web serice connection Charting supports the HTTPS protocol for confidentiality. When data requests are made from the portal to the IBM Tioli Monitoring application serer (Tioli Enterprise Portal Serer) the credentials of the logged-in user are passed to the Web serice for authentication and authorization. When requests are made to retriee Tioli Monitoring data into a chart portlet, the user name and password that were proided at installation time are passed to the Tioli Enterprise Portal Serer, and an LTPA token is passed to the backend Web serice. To participate in this secure connection, the ITM Web Serice must be installed and run on the same Tioli Integrated Portal Serer instance. 38 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

53 About DNCIM In this ersion of Network Manager the Discoery engine, ncp_disco, uses a new embedded relational database, known as Discoery NCIM (DNCIM). During the discoery process, data is collected from the network, and the network topology is created using this data. During data collection and processing into a network topology, the network topology data is stored in different databases. Once the final network model, including connectiity and containment, is built the network topology data is stored in DNCIM. DNCIM has the same structure as the NCIM topology database. Note: DNCIM replaces the legacy scratchtopology database. For more information about DNCIM, see the IBM Tioli Network Manager IP Edition Discoery Guide. Chapter 1. Planning for installation 39

54 40 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

55 Chapter 2. Installing Preparing to install Use this information to plan and perform an installation of Network Manager. After installation, you might need to perform configuration tasks. Before you begin installing Network Manager, you must obtain and extract the installation package, and depending on your installation, complete additional tasks. If you want to integrate Network Manager with an existing installation of Tioli Netcool/OMNIbus on a different serer, you must configure the Tioli Netcool/OMNIbus installation before installing Network Manager. For information about setting up your database for an existing Network Manager installation, see the tasks about creating topology database schemas in the IBM Tioli Network Manager IP Edition Administration Guide. Click the following link to retriee technotes about known installation issues in ersion 4.1 of Network Manager: &tc=ssshrk&atrn=swversion&atr=4.1&ibm-go.x=18&ibm-go.y=12 Restriction: Any passwords you choose for use in Network Manager must conform to the password policies of the serer or system enironment. Configuring an existing Tioli Netcool/OMNIbus installation on a remote serer If you want to integrate Network Manager with an existing installation of Tioli Netcool/OMNIbus on a different serer, you must configure the Tioli Netcool/OMNIbus installation before installing Network Manager. If you are installing Tioli Netcool/OMNIbus or later on the same serer as part of the Network Manager installation, you do not need to do this task. You can use the Network Manager installer to install and configure Tioli Netcool/OMNIbus. If you want to integrate Network Manager with an existing installation of Tioli Netcool/OMNIbus or later on the same serer, you do not need to do this task. You can use the Network Manager installer to configure the existing Tioli Netcool/OMNIbus. Attention: Using the Network Manager installer to configure an existing Tioli Netcool/OMNIbus on the same serer also installs probes and the Netcool/OMNIbus Knowledge Library unless you choose not to. If you do not want to oerwrite your existing probe and Netcool/OMNIbus Knowledge Library customizations, ensure you do not select to install these Tioli Netcool/OMNIbus components during the installation. Copyright IBM Corp. 2006,

56 To configure an existing Tioli Netcool/OMNIbus for use with Network Manager, complete the following tasks. 1. Make sure you hae an existing Tioli Netcool/OMNIbus ObjectSerer installation to configure. 2. Download and extract the Network Manager installation package on the serer that contains the Tioli Netcool/OMNIbus installation. Alternatiely, if you already hae an extracted Network Manager installation package on a machine, you can also copy the ExportPackage file from that serer to the host that contains the Tioli Netcool/OMNIbus installation. The ExportPackage file includes the launchpad and script required to configure the existing Tioli Netcool/OMNIbus installation. 3. If you are configuring a Tioli Netcool/OMNIbus ersion other than 7.4 then download the installation package for the appropriate ersion of the SNMP Probe (also known as the MTTRAPD Probe). 4. To be able connect to an existing Tioli Netcool/OMNIbus on the remote serer, configure it for this Network Manager installation before installing Network Manager using one of the following options. Start the configuration script either from the installer launchpad or the command line. Option Run the script from the launchpad. Run the script from the scripts directory of the installation package. Description 1. Depending on your operating system, start the launchpad using the launchpad.sh script on UNIX or the launchpad.exe executable on Windows. 2. Go to Preinstallation and Migration and expand the Configure an existing Netcool/OMNIbus installation section. 3. Click Configure existing Netcool/OMNIbus installation. 4. Enter the access credentials for the ObjectSerer you want to configure. Depending on your operating system, run the ConfigOMNI.sh script on UNIX or the ConfigOMNI.bat script on Windows. Enter the access credentials for the ObjectSerer you want to configure. For information about running the script, see ConfigOMNI command-line options on page 43. If you install Tioli Netcool/OMNIbus as part of the Network Manager installation, the installer adds the itnmadmin, itnmuser, and itnmclient users to the ObjectSerer, turns on AES encryption, turns on process control for the Objectserer, and installs the SNMP Probe and the Netcool/OMNIbus Knowledge Library. If you use the ConfigOMNI utility (from launchpad or from command line), you can choose which options are configured using the appropriate command line arguments. If you are configuring a Tioli Netcool/OMNIbus ersion other than 7.4, supply the installation package for the appropriate ersion of the SNMP Probe using the -m command line argument. 5. Required: After you configure Tioli Netcool/OMNIbus, install Network Manager. 42 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

57 a. During the installation, select Connect to an existing Tioli Netcool/OMNIbus installation on another serer. b. Proide the details of the ObjectSerer that you configured using the script. ConfigOMNI command-line options Use the ConfigOMNI script, with optional adanced arguments, to configure Tioli Netcool/OMNIbus for use with Network Manager before installing Network Manager. The ConfigOMNI script is started by using the following command line; optional arguments are shown enclosed in square brackets. ConfigOMNI -o name -p password [-a][-c][-e][-hdirectory ][-kpackage ] [-mpackage ][-nportnumber ][-upassword ] The following example runs the script on ObjectSerer DIAMOND with the administratie password p3w0d. If the ObjectSerer DIAMOND does not already exist, it is created. Using the appropriate options, you can configure the script to add the itnmadmin, itnmuser, and itnmclient users to the ObjectSerer, turn on AES encryption, turn on process control for the Objectserer, and install the SNMP Probe and the Netcool/OMNIbus Knowledge Library. Note: The ConfigOMNI script does not perform any configuration unless the appropriate command line options are proided, or you respond to the appropriate questions. ConfigOMNI -o DIAMOND -p p3w0d The following table describes the command-line options for the ConfigOMNI script. Table 6. ConfigOMNI command-line options Command-line options Description -o name The name of the ObjectSerer that you want to create or configure. -p password The administratie password of the ObjectSerer that you want to create or configure. -a Optional. Runs the script in interactie mode, which prompts for all information. -c Optional. Configures the ObjectSerer to run under Tioli Netcool/OMNIbus process control. This is necessary for the itnm_start, itnm_stop, and itnm_status scripts to function correctly with the ObjectSerer. -e Optional. Set AES encryption for the ObjectSerer password. -h directory Optional. The directory containing the Tioli Netcool/OMNIbus installation (OMNIHOME). -k package Optional. Install Netcool/OMNIbus Knowledge Library from this package. You must specify the path to the package if it is not in the current directory. -m package Optional. Install the SNMP Probe from this package. You must specify the path to the package if it is not in the current directory. Chapter 2. Installing 43

58 Table 6. ConfigOMNI command-line options (continued) Command-line options Description -n portnumber Optional. The port number of the ObjectSerer that you want to create or configure. -u password Optional. Create the itnmadmin, itnmuser, and itnmclient users in the ObjectSerer. Setting up a topology database You must configure an existing database or install and configure a new one to use as the topology database for Network Manager. You hae the following options to set up a database for your topology: You can install and configure the default DB2 database bundled with Network Manager and set it up using the Network Manager installer. In this case, you do not need to follow any of the database setup tasks before installing Network Manager. You can start the installer and select the options for setting up a new DB2 database. If you want to use an existing DB2 database on either a local or a remote host, you must configure it before installing Network Manager as described in the following tasks. For information about setting up your database for an existing Network Manager installation, see the tasks about creating topology database schemas in the IBM Tioli Network Manager IP Edition Administration Guide. Important: Ensure that your database has all the recommended patches applied, including the latest patch leels. Related reference: Supported topology databases on page 32 IBM DB2 Uniersal Database ersion 10.1 is the default topology database for Network Manager V4.1. Setting up existing DB2 databases on UNIX To use an existing DB2 database as the topology database on UNIX, you must install DB2, configure an instance, and create a database before Network Manager is installed. The database for Network Manager is created by scripts that are contained in the /PrecisionIP/scripts directory of the extracted installation image. You must hae extracted the installation package before you install DB2 and attempt to create the database. The DB2 enironment must be set up as the DB2 administratie user on the serer hosting DB2. If the host is on a remote serer then copy the database creation scripts to the remote serer. During installation of Network Manager, the NCIM topology database is installed on the DB2 database that you create. For information on how to install and configure DB2, see your DB2 documentation. The documentation for the supported ersions of DB2 are at the following locations: 44 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

59 For DB2 9.7, see For DB2 10.1, see 1. Install DB2 and configure an instance in which the installation process can create the NCIM database. 2. Change to the directory into which the instance was installed and then change to the sqllib subdirectory. 3. Set up the enironment by typing the following command: Shell Bourne C Command../db2profile source db2cshrc The Network Manager application wrapper scripts automatically set up the DB2 enironment. For more information about how the wrapper scripts set up the enironment, see Example of how the wrapper scripts search for a file on page Change to the /PrecisionIP/scripts directory of the extracted Network Manager installation image. 5. Optional: If you are setting up DB2 on a different serer from Network Manager, copy the following scripts to the remote host where you installed DB2: create_db2_database.sh create_db2_cognos_database.sh catalog_db2_database.sh 6. Run the create_db2_database.sh script as the DB2 administratie user by typing the following command:./create_db2_database.sh database_name user_name -force where: database_name Is the required name of the database user_name Is the DB2 user that will be used to connect to the database Important: This user must not be the administratie user. This user must be an existing operating system and DB2 user. -force Is an optional argument that forces any DB2 users off the instance before the database is created. For example, to create a DB2 database called ITNM for the DB2 user ncim, type:./create_db2_database.sh ITNM ncim After running create_db2_database.sh, restart the database as the DB2 administratie user as follows: run db2stop and then run db2start. 7. When running the Network Manager installer later on, make sure you select the option to configure an existing DB2 database. The Network Manager installer can then create the tables in the database either on the local or a remote host, depending on where your database is installed. 8. Optional: After the installation of Network Manager, if you want to use network management reports with Tioli Common Reporting, you hae the option of migrating the Cognos content store database from the default Derby Chapter 2. Installing 45

60 database to DB2 using the create_db2_cognos_database.sh script. If you want to do so, follow the steps in Migrating the Cognos content store from Derby to DB2 on page 240 after installation. 9. Optional: After the installation of Network Manager, if you are setting up DB2 on a different serer to Network Manager, log in as the DB2 administrator on the DB2 client running on the Tioli Integrated Portal serer (default is db2inst9 if the DB2 runtime client is installed by Network Manager). Run the following script to catalog the database:./catalog_db2_database.sh database_name host port where database_name Is the name of the NCIM database. host Is the hostname of the serer where NCIM is installed port Is the port on which the NCIM database is running The following command shows an example usage of the script:./catalog_db2_database.sh ITNM db2serer.ibm.com Example of how the wrapper scripts search for a file Under the Bourne shell, when the wrapper scripts set up the enironment ariables for DB2, the scripts search for the following file and run it: $ITNMHOME/.db2sqllib. This file is automatically created during the install, and it first checks for the existence of a file called db2profile with which to set up the DB2 enironment. If the file exists, it is run as shown in the following example: if [ -f /home/db2inst/sqllib/db2profile ] ; then. /home/db2inst/sqllib/db2profile fi The $ITNMHOME/.db2sqllib file is parsed by the setup_run_as_setuid_root.sh script to determine the location of the DB2 client libraries (see Configuring the core components to run as non-root on page 214). Related concepts: About NCIM topology database high aailability on page 242 Network Manager allows you to configure the NCIM topology database for high aailability, minimizing the impact of computer or network failure. The following sections proide an oeriew of NCIM topology database high aailability and explain how to configure it. Network Manager failoer architecture (core processes) on page 247 Failoer of the Network Manager core processes can be implemented by setting up primary and backup Network Manager installations that run on different serers and domains. Both installations can either connect to a single Tioli Netcool/OMNIbus ObjectSerer or to a irtual pair of ObjectSerers. 46 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

61 Setting up NCIM to handle multibyte characters You must configure the NCIM database to handle multibyte characters, such as Simplified Chinese characters, if you want the NCIM database to store multibyte data. Such configuration is useful when, for example, you need to enter multibyte characters into the Description field of a poll definition. Ensure that you hae the following settings for the NCIM database: DB2 If you are running Network Manager in a locale that supports multibyte characters, then there is no need to make any configuration changes. For example, both of the following locales support multibyte characters when NCIM is running on DB2: LANG=zh_CN.gb18030 LC_ALL=zh_CN.gb18030 LANG=en_US.utf8 LC_ALL=en_US.utf8 Related information: com.ibm.glsug.doc/ids_gug_068.htm Installing Tioli Common Reporting You must hae Tioli Common Reporting installed to run the network management reports proided by Network Manager. To enable network management reports, you must hae Tioli Common Reporting installed. Network Manager installs the reports package required for network management reports on the serer where the Network Manager GUI components are installed. If the chosen installation location for Network Manager already has existing Tioli Integrated Portal and Tioli Common Reporting instances, then Network Manager automatically configures the reports to be used with that Tioli Common Reporting instance. If you do not hae Tioli Common Reporting installed when installing Network Manager, you can install Tioli Common Reporting at a later date and configure the reports then. Attention: If you hae an existing Tioli Common Reporting installation, ensure you hae the required repository for user authentication set up before installing the Network Manager GUI components. You cannot change the user authentication method with the Network Manager installer. For example, if you are planning to use the ObjectSerer-based authentication and it is not configured yet on the existing Tioli Integrated Portal installation used by your Tioli Common Reporting instance, then install the Tioli Netcool/OMNIbus Web GUI (included in the Network Manager package) into the existing Tioli Integrated Portal installation, and select the option to enable ObjectSerer-based authentication. Then install the Network Manager GUI component into the existing Tioli Integrated Portal. To install Tioli Common Reporting: 1. Download the Tioli Common Reporting package. You can download Tioli Common Reporting as an optional part from the Network Manager package. For more information, see the download document at 01.ibm.com/support/dociew.wss?rs=3117&uid=swg Chapter 2. Installing 47

62 2. Go to the Tioli Common Reporting documentation for information about installing Tioli Common Reporting: tiihelp/3r1/index.jsp?topic=%2fcom.ibm.tioli.tcr.doc_211%2fic-home.html 3. Install Tioli Common Reporting on the host where the Network Manager GUI components will be installed. 4. Install Network Manager as described in Installing Network Manager on page 49. The Network Manager installation process automatically installs the network management reports package and configures the reports to work with Tioli Common Reporting. Important: Stop Tioli Common Reporting before installing Network Manager. As the user who installed Tioli Common Reporting, run the following command from the TCR_component_dir/bin directory:./stoptcrserer.sh <tip_admin_user> <password> 5. Optional: If you do not install Tioli Common Reporting before installing Network Manager, you can configure the network management reports at a later date after installing Network Manager as described in Configuring reports for existing installations on page 239. Extracting the installation file If you hae downloaded the installation file, you must extract the installation package before installing the product. Ensure that the directory in which you extract the installation package has general read and execute permissions (for example, 755 on UNIX systems). To extract the installation file, perform the following steps: Extract the file. UNIX Type the following command: gunzip -d < installation_file.tar.gz tar xf - Checking system prerequisites You can use the Network Manager launchpad to perform an automated check of system prerequisites to determine whether your serers are suitable for installing the components you want to install. To use the launchpad, you need a browser that supports the launchpad installed on the serer. Note: To use the launchpad, you must hae the xterm command installed on this system. Important: The Network Manager V4.1 installer includes installation of DB2, either as a DB2 serer for a single-serer installation, or as a DB2 client to enable Network Manager V4.1 to talk to an existing DB2 serer installation. If the installing user has an existing DB2 client already defined in their enironment (for example, in the PATH or LD_LIBRARY_PATH enironment ariables) and this ersion of DB2 is different to the V10.1 ersion being used by Network Manager V4.1, then the existing DB2 client might interfere with the Network Manager V4.1 DB2 installation. Any references to an existing DB2 installation on the serer should be remoed from the enironment of the user that is installing Network Manager V IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

63 The prerequisite checking utility performs a check to determine if there are any existing references to DB2 in the enironment. To perform an automated check of system prerequisites: 1. Download and uncompress the installation package. 2. Start the launchpad. UNIX Run the launchpad.sh script 3. Select the Prerequisite Information menu item. 4. Enter an installation location in the Installation Location box. 5. Select the components for which you want to check the prerequisites. 6. Click Check System Prerequisites. The results of the system prerequisites check are displayed, indicating whether the current serer is suitable for installing your choice of components. Configuring Red Hat Linux Enterprise Edition Before you install on Red Hat Linux Enterprise Edition, you must disable SELinux. When Red Hat Enterprise Linux is installed, SELinux is optionally enabled. To disable SELinux, turn off SELinux enforcing by completing the following steps: 1. Open the following file: /etc/sysconfig/selinux 2. Find the following line: SELINUX=enforcing 3. Change it to SELINUX=disabled. 4. Restart the serer. Installing Network Manager You can install Network Manager in different modes, depending on your requirement If you want to use an existing installation of Tioli Netcool/OMNIbus, see Configuring an existing Tioli Netcool/OMNIbus installation on a remote serer on page 41. Attention: When installing Network Manager GUI components on a host that already has an existing Tioli Integrated Portal installation, ensure you hae the required repository for user authentication set up (file-based, ObjectSerer-based, or LDAP authentication). You cannot change the user authentication method with the Network Manager installer. For example, if you are planning to use the ObjectSerer-based authentication and it is not configured yet on the existing Tioli Integrated Portal installation, then install the Tioli Netcool/OMNIbus Web GUI (included in the Network Manager package) into the existing Tioli Integrated Portal installation, and select the option to enable ObjectSerer-based authentication. Then install the Network Manager GUI component into the existing Tioli Integrated Portal. Chapter 2. Installing 49

64 Differences between basic and custom installation Performing a custom installation gies you many more options than a basic installation. Basic installation Choose a basic installation if the following criteria apply. You are installing for demonstration or testing purposes. The installation is for a small network. You are installing all components on single serer with default options. Note: A basic installation automatically performs a network discoery after installing. Custom installation Choose a custom installation if any of the following criteria apply. The installation is for a medium or large network. You need to distribute an installation oer seeral serers. The installation is for a network with adanced technologies such as Network Address Translation (NAT) or Multiprotocol Label Path Switching (MPLS). You want to use an existing installation of Tioli Netcool/OMNIbus. You want to decide whether to install Tioli Netcool/OMNIbus probes or the Netcool/OMNIbus Knowledge Library when installing a new Tioli Netcool/OMNIbus or configuring the Network Manager installation to use an existing one. You want to use an existing installation of Tioli Integrated Portal. You want to specify the context root of the URL used to access the Tioli Integrated Portal (the default is /ibm/console). You require failoer. You want to use an existing database for topology data, or you want to set up the database with non-default alues (for example, different user name than the default). FIPS compliance is important to you. Note: A custom installation gies you the option to perform different types of network discoeries after installing. Note: During a custom installation, you must select at least one Network Manager component to install. You cannot use the Network Manager installer to install other products without installing at least one of the Network Manager components. The Network Manager installer only installs Tioli Netcool/OMNIbus and a local DB2 in conjunction with the installation of Network Manager components, and does not install them in a stand-alone setup. For distributed installations, use the natie installer of the products to ensure that the products are customized to the specific needs of the enironment. 50 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

65 About a FIPS installation Federal Information Processing Standard (FIPS) is a US Federal cryptographic standard. You can install Network Manager using a restricted set of cryptographic algorithms. Important: Network Manager cannot be said to be compliant with the FIPS standard, and nothing in this information or in the product should be understood as making this claim. Howeer, Network Manager can be installed in a mode that has been designed with FIPS specifications taken into consideration. You can install Network Manager using a restricted set of cryptographic algorithms by selecting the appropriate option from the Select Installation Options panel in the installation wizard. Restriction: If FIPS compliance is important to you, you must use only ersion or higher of IBM Tioli Netcool/OMNIbus, and you must install IBM Tioli Netcool/OMNIbus in FIPS mode. You must also ensure that all products integrating with Network Manager, such as IBM Tioli Netcool/OMNIbus, hae a FIPS mode, and you must configure the products if necessary. You must also check that your operating system uses only FIPS compliant modules. Restriction: If you choose to install Network Manager using a restricted set of cryptographic algorithms, non-compliant features are not installed. You cannot change from a FIPS installation to a non-fips installation except by uninstalling and reinstalling the product. You also cannot change from a non-fips installation to a FIPS installation except by uninstalling and reinstalling the product. Differences in a FIPS installation of Network Manager An FIPS installation differs from a normal installation in the following ways: The Telnet discoery agents do not use SSH1 to interrogate deices. This might result in a failure to connect securely to a deice if the deice supports only SSH1, or if the deice only supports non-compliant SSH2 algorithms. The SNMP Helper and the MIB browser cannot be configured to use MD5 or DES encryption. The Element Management Systems (EMS) collectors are not installed. Installing Network Manager using the wizard The easiest way to install Network Manager is by using the wizard. Before installing, ensure that you hae performed any necessary pre-installation tasks, including checking that your serers are suitable for installing Network Manager. Note: To use the launchpad, you must hae the xterm command installed on this system. Tip: The installation wizard takes focus when displaying windows. If you want to work in another window while the product is being installed, minimize the installation windows first. To start the installation wizard, perform the following steps. Chapter 2. Installing 51

66 1. Start the installer wizard from the launchpad. UNIX Run the launchpad.sh script. a. Select the Installing Network Manager item from the menu. b. Select either a basic or custom installation by clicking the Start Basic Installation or Start Custom Installation button. A basic installation installs all components of the product onto a single serer using default alues. A basic installation is shorter and simpler than a custom installation and is suitable for small networks, small enterprise customers, and demonstration purposes. A basic installation automatically starts a network discoery when it finishes. A custom installation is suitable for medium to large networks, integrating with existing products, or multi-serer installations. A custom installation gies you the option to start a network discoery when it finishes. Note: During a custom installation, you must select at least one Network Manager component to install. You cannot use the Network Manager installer to install other products without installing at least one of the Network Manager components. The Network Manager installer only installs Tioli Netcool/OMNIbus and a local DB2 in conjunction with the installation of Network Manager components, and does not install them in a stand-alone setup. For distributed installations, use the natie installer of the products to ensure that the products are customized to the specific needs of the enironment. 2. If you cannot start the launchpad, start the installation wizard from the command line. UNIX Run the install.sh script. You hae the option of choosing a basic or custom installation when the installation wizard starts, in the Select Installation Type wizard panel, which is the fourth wizard panel to be displayed. 3. Enter the appropriate alues in the wizard panels to install the product. For guidance on alues to be entered, see the alues for a basic or a custom installation, depending on your selection. At the end of a successful installation, the installer wizard displays the ports used by each product or component that was installed. The ports are also included in the NCHOME/log/install/Configuration.log file. Note: If you intend to migrate NCIM data to this Network Manager installation, do not start the processes at this time. Migrate the NCIM data first and then start the Network Manager processes from the command line. For more information, see Importing NCIM topology database data. Values for a basic installation Use this information to understand what alues to enter in the wizard panels for a basic installation. A basic installation uses a restricted set of wizard panels to collect configuration information. The following table describes the alues that you must enter for each panel. Note: The basic installation only installs the default DB2 database. To use an existing instance of a DB2 database, choose the custom installation option. 52 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

67 Tip: Print out this table for ease of reference while you install the product. You can use this table to check that you hae all the required information in adance, and to record important alues that you enter. Table 7. Wizard panels and their alues Wizard panel Value/option Description Introduction None After reading the introductory text, click Next. Validate system None This panel is only displayed if one or more of the system alidation checks fail. If any error messages are displayed in this wizard panel, you must cancel the installation, fix the errors, and start the installation again. This system alidation establishes whether the current serer is suitable in general for installing network management software. The alidation checks include checks for consistent DNS and for a minimum of aailable memory for the installation process itself. Software License Agreement I accept both the IBM and the non-ibm terms Select this option to continue the installation. Select Installation Location I do not accept the terms in the license agreement Tioli Network Manager install location If you select this option, you cannot continue installation. Use the default location or enter the location where you want Network Manager to be installed. Restriction: If you are upgrading Network Manager from a preious ersion, you must choose a different directory to the one that Network Manager is currently installed in. You cannot upgrade Network Manager by oerwriting files. Permitted characters in the installation path are alphanumeric (A-Z, a-z, 0-9), dashes, underscores, periods, colons, slashes, and spaces. Chapter 2. Installing 53

68 Table 7. Wizard panels and their alues (continued) Wizard panel Value/option Description Collect Default Installation Information Netcool Domain Name Enter a name to be used as a network domain by Network Manager. Enter a descriptie name, for example, TESTNETWORK. The domain name must consist of between one and 29 characters (letters, numbers, or both), with the letters all capitals, no spaces, and no special characters. Make a note of the domain name, because it is used when starting components manually. Domain name: Administratie Password Confirm Password Enter a password to be used as the Tioli Netcool/OMNIbus ObjectSerer root password, the topology database administrator password, and the password for the default user accounts itnmadmin and itnmuser. The password must consist of between four and eight ASCII characters, and must match any password requirements that are applicable on the machine where you are installing. Restriction: The password must not start with a dollar sign ($). Re-enter the administratie password. 54 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

69 Table 7. Wizard panels and their alues (continued) Wizard panel Value/option Description Collect Port Connection Information Netcool/OMNIbus ObjectSerer Port Tioli Integrated Portal HTTP Port Enter the port that you want to use for the ObjectSerer, or accept the default alue. If you are connecting to a failoer pair of ObjectSerers, specify details for the irtual Objectserer here. Enter the port that you want to use for the Tioli Integrated Portal, or accept the default alue. Make a note of the port number, because you use this to connect to the Web applications. HTTP port: Collect SNMP V1/V2 Community Strings DB2 database port List of community strings Enter the port that you want to use for the database, or accept the default alue. When the installation finishes, a simple discoery of the local subnet is started. Enter up to six SNMP community strings (passwords). These community strings are needed by the discoery process in order to get SNMP information from deices on your network. To reduce discoery time, list the community strings in order, from most frequently to least frequently used. Public is installed by default. Pre-Installation Summary None Reiew the information about the components that will be installed. Click Next to run a final prerequisite check before installation. Chapter 2. Installing 55

70 Table 7. Wizard panels and their alues (continued) Wizard panel Value/option Description Prerequisite Checking Results None Reiew the results of the prerequisite check. This prerequisite check establishes whether the current serer is suitable for installing the specific components that you hae chosen. If there are any serious errors, you must cancel the installation, fix the errors, and start the installation again. If there are no serious errors, click Install to install your chosen components. When prompted, accept any license agreements to continue. Values for a custom installation Use this information to understand what alues to enter in the wizard panels for a custom installation. A custom installation uses different panels to collect configuration information depending on the choices you make. The following table describes the alues that you must enter for each panel. Tip: Print out this table for ease of reference while you install the product. You can use this table to check that you hae all the required information in adance, and to record important alues that you enter. Table 8. Wizard panels and their alues Wizard panel When panel is displayed Value/option Description Introduction Always displayed. None After reading the introductory text, click Next. Validate system Displayed if the system fails alidation. None This panel is only displayed if one or more of the system alidation checks fail. Cancel the installation, fix the errors, and start the installation again. This system alidation establishes whether the current serer is suitable in general for installing network management software. The alidation checks include checks for consistent DNS and for a minimum of aailable memory for the installation process itself. 56 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

71 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Software License Agreement Always displayed. I accept both the IBM and the non-ibm terms I do not accept the terms in the license agreement Select Installation Location Always displayed. Tioli Network Manager install location Select this option to continue the installation. If you select this option, you cannot continue installation. Use the default location or enter the location where you want Network Manager to be installed. Restriction: If you are upgrading Network Manager from a preious ersion, you must choose a different directory to the one that Network Manager is currently installed in. You cannot upgrade Network Manager by oerwriting files. Permitted characters in the installation path are alphanumeric (A-Z, a-z, 0-9), dashes, underscores, periods, colons, slashes, and spaces. Chapter 2. Installing 57

72 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Select Installation Options Always displayed. Number of Serers > Single Serer Installation Select this option to install Network Manager, the DB2 topology database, and the GUI components (the Network Manager Web applications and the Tioli Integrated Portal) on the current serer. Number of Serers > Multi-serer Installation Default alues > Accept default settings Default alues > Customize settings FIPS Compliance > Use FIPS compliant cryptographic routines If you hae obtained Tioli Netcool/OMNIbus V7.4 and hae the installation package aailable, you can also install Tioli Netcool/OMNIbus V7.4 using this option. Note: If you create a subdirectory called OMNIbus in the top-leel directory of the extracted Network Manager installation package and place the Tioli Netcool/OMNIbus image there, the Network Manager installer installs Tioli Netcool/OMNIbus regardless of ersion. Select this option to choose which components to install on the current serer. Select this option to minimize the number of wizard panels displayed. Select this option to be able to customize eery installation option. Select this option if you want to install using cryptographic routines from a alidated cryptographic module. If you select this option there are restrictions to the product functionality (as described in About a FIPS installation on page 51). 58 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

73 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Select Components to Install Displayed for multi-serer installations. Core components Web Applications Select whether to install the Network Manager network discoery, polling, root cause analysis and eent enrichment components on this serer. Also referred to in the documentation as "GUI components". Select this option if you want to install the Network Manager Web applications on this serer. If the Tioli Integrated Portal is not already installed, it is installed with the Web applications. If there is an existing installation of the Tioli Integrated Portal on this serer, you can choose to use it in a later panel. Note: You must select at least one Network Manager component to install. You cannot use the Network Manager installer to install other products without installing at least one of the Network Manager components. The Network Manager installer only installs Tioli Netcool/OMNIbus and a local DB2 in conjunction with the installation of Network Manager components, and does not install them in a stand-alone setup. For distributed installations, use the natie installer of the products to ensure that the products are customized to the specific needs of the enironment. Chapter 2. Installing 59

74 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Select Components to Install (continued) Displayed for multi-serer installations. Tioli Netcool/OMNIbus You hae the following options: 1. If you want to install Tioli Netcool/OMNIbus on the same serer as Network Manager, and set it up for use with this instance of Network Manager, select the option to install Tioli Netcool/OMNIbus on this serer. You can later proide details for the installation in the Collect Netcool/OMNIbus Installation Details panel. You must hae already downloaded V7.3.1 or later to this serer. If you want to install and configure a Tioli Netcool/OMNIbus ersion other than 7.4, create a subdirectory called OMNIbus in the top-leel directory of the extracted Network Manager installation package, and extract the downloaded Tioli Netcool/OMNIbus package into this directory. Note: You do not need to create the subdirectory if you hae downloaded ersion 7.4. If the installer cannot locate the Tioli Netcool/OMNIbus 7.4 package, the installer asks for the location of the package. 60 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide 2. If you want to configure an existing Tioli Netcool/OMNIbus installation on the serer where you are installing Network Manager, select the option to configure an existing Tioli Netcool/OMNIbus installation on this serer for use with Network Manager. You can later proide details for the setup in the Configure existing ObjectSerer panel. Note: Tioli Netcool/OMNIbus must already be installed on this serer.

75 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Select Components to Install (continued) Displayed for multi-serer installations. Tioli Netcool/OMNIbus (continued) 3. If you want to use an ObjectSerer running on a different serer to this one where you are installing Network Manager, select the option to connect to an existing Tioli Netcool/OMNIbus installation on a another serer. You can later proide details for the connection in the Connect to Existing ObjectSerer panel. 4. You can also select not to install, configure, or connect to an ObjectSerer by selecting the option not to install or configure Tioli Netcool/OMNIbus at this time. Select Components to Install (continued) Displayed for multi-serer installations. Topology database Choose to install a DB2 database on this host to use as the Network Manager topology database, or connect to an existing DB2 database to use as the topology database. Note: DB2 can only be installed by the root user. If you are installing Network Manager as non-root, there is an additional post-installation step: You must log in as root after completing the Network Manager installation and complete the DB2 installation on the system. See Installing and configuring DB2 after a non-root installation on page 216 Chapter 2. Installing 61

76 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Get Netcool/OMNIbus Package Location Displayed if you selected a single serer installation or if you selected Install eent management software in a multi-serer installation. Choose directory containing the Netcool/OMNIbus package Enter the location of the downloaded package or installation media. The Network Manager installer requires Tioli Netcool/OMNIbus 7.4 packages and if it does not find them it asks for the location of the Tioli Netcool/OMNIbus image. Note: If you create a subdirectory called OMNIbus in the top-leel directory of the extracted Network Manager installation package and place the Tioli Netcool/OMNIbus image there, the Network Manager installer installs Tioli Netcool/OMNIbus regardless of ersion. 62 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

77 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Collect Default Installation Information Displayed if you selected Accept Default Settings. Netcool Domain Name Enter a name to be used as a network domain by Network Manager. Enter a descriptie name, for example, TESTNETWORK. The domain name must consist of between one and 29 characters (letters, numbers, or both), with the letters all capitals, no spaces, and no special characters. Make a note of the domain name, because it is used when starting components manually. Domain name: Administratie Password Confirm Password Enter a password to be used as the Tioli Netcool/OMNIbus ObjectSerer root password, the topology database administrator password, and the password for the default user accounts itnmadmin and itnmuser. The password must consist of between four and eight ASCII characters, and must match any password requirements that are applicable on the machine where you are installing. Re-enter the administratie password. Chapter 2. Installing 63

78 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Collect Port Connection Information Displayed if you selected Accept Default Settings. Netcool/OMNIbus ObjectSerer Port Tioli Integrated Portal HTTP Port Enter the port that you want to use for the ObjectSerer, or accept the default alue. Enter the port that you want to use for the Tioli Integrated Portal, or accept the default alue. Make a note of the port number, because you use this to connect to the Web applications. HTTP port: DB2 database port Enter the port that you want to use for the database, or accept the default alue. Collect Netcool/OMNIbus Installation Details Displayed if you chose to installtioli Netcool/OMNIbus and selected Customize Settings. Netcool/OMNIbus ObjectSerer name Netcool/OMNIbus ObjectSerer port Enter a name to use for the ObjectSerer that is being installed. The name must not contain spaces. Enter a port to use for the ObjectSerer that is being installed. The port must not currently be in use. Netcool/OMNIbus administrator account password Enter a password for the administrator account. Confirm password Confirm the password for the administrator account. Install the following Netcool/OMNIbus components Select the Tioli Netcool/OMNIbus probes or the Netcool/OMNIbus Knowledge Library if you want to install them as part of the process. Clear the selection of the ones you do not want to install. 64 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

79 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Configure existing ObjectSerer Displayed if you chose to configure an existing installation of Tioli Netcool/OMNIbus on this serer. Netcool/OMNIbus installation location (OMNIHOME) Netcool/OMNIbus ObjectSerer name Netcool/OMNIbus ObjectSerer port Netcool/OMNIbus administrator account name Netcool/OMNIbus administrator account password Confirm password Install the following Netcool/OMNIbus components The location on this serer where Tioli Netcool/OMNIbus is installed. Enter the name of the ObjectSerer that you want this installation to configure. If you are connecting to a failoer pair of ObjectSerers, specify the details of the irtual ObjectSerer here. Enter the port used by the ObjectSerer. If you are connecting to a failoer pair of ObjectSerers, specify the details of the irtual ObjectSerer here. Enter the user name for the administrator account. Enter the password for the administrator account. Confirm the password for the administrator account. Select the Tioli Netcool/OMNIbus probes or the Netcool/OMNIbus Knowledge Library if you want to install them as part of the process. Clear the selection of the ones you do not want to install. Attention: Using the Network Manager installer to configure an existing Tioli Netcool/OMNIbus on the same serer also installs probes and the Netcool/OMNIbus Knowledge Library unless you choose not to. If you do not want to oerwrite your existing probe and Netcool/OMNIbus Knowledge Library customizations, ensure you do not select to install these Tioli Netcool/OMNIbus components during the installation. Chapter 2. Installing 65

80 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Connect to Existing ObjectSerer Select installation directory for TIP Displayed if you chose to connect to an existing installation of Tioli Netcool/OMNIbus on another serer. Note: Ensure you hae configured this existing installation of Tioli Netcool/OMNIbus before installing Network Manager, as described in Configuring an existing Tioli Netcool/OMNIbus installation on a remote serer on page 41. Note: If you choose to connect to an existing Tioli Netcool/OMNIbus on another serer, you might need to complete additional post-installation tasks, as described in Configuring Tioli Netcool/OMNIbus for use with Network Manager on page 151. Displayed if you selected Install User Console and Customize Settings. Netcool/OMNIbus serer host name Netcool/OMNIbus ObjectSerer name Netcool/OMNIbus port Netcool/OMNIbus administrator account password Confirm password Choose an install folder Reuse an existing install folder Enter the name of the system where the Tioli Netcool/OMNIbus installation to use is located. Enter the name of the ObjectSerer that you want this installation to connect to. If you are connecting to a failoer pair of ObjectSerers, specify the details of the irtual ObjectSerer here. Enter the port used by the ObjectSerer. If you are connecting to a failoer pair of ObjectSerers, specify the details of the irtual ObjectSerer here. Enter the password for the administrator account. Confirm the password for the administrator account. Choose a location for the Tioli Integrated Portal to be installed. Select this option if the Tioli Integrated Portal is not already installed on this serer. Click reuse, and select the directory path of an existing installation of the Tioli Integrated Portal. If the Tioli Integrated Portal is not installed on the serer, this option is not aailable. 66 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

81 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Collect Tioli Integrated Portal Installation Details Displayed if you selected Install User Console and Customize Settings, and then you selected Choose an install folder in the Select Installation Directory for TIP panel. TIP HTTP port Enter the port to be used for the Tioli Integrated Portal. Make a note of the port number, because you use this to connect to the Web applications. HTTP port: TIP console context root TIP administrator account name TIP administrator account password Confirm password Select the initial authentication method to use The context root determines the URL that users supply to access the Tioli Integrated Portal and hence Network Manager. The default is /ibm/console. Enter a name to be used for the Tioli Integrated Portal administrator account. Enter a password to be used for the Tioli Integrated Portal administrator account. Confirm the password for the administrator account. Select Internal (File-based) or ObjectSerer, depending on which repository you want to use for authenticating Tioli Integrated Portal users. Note: To use LDAP for authentication, select either of the options and configure LDAP authentication after installation as described in in section Configuring user authentication of the IBM Tioli Netcool/OMNIbus Installation and Deployment Guide. Chapter 2. Installing 67

82 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Collect Tioli Integrated Portal Reuse details Displayed if you selected Install User Console and Customize Settings, and then you selected Reuse an existing install folder in the Select Installation Directory for TIP panel. TIP HTTP port Enter the port to be used for the Tioli Integrated Portal. Make a note of the port number, because you use this to connect to the Web applications. HTTP port: TIP administrator account name TIP administrator account password Confirm password Enter a name to be used for the Tioli Integrated Portal administrator account. Enter a password to be used for the Tioli Integrated Portal administrator account. Confirm the password for the administrator account. 68 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

83 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Collect Network Manager Installation Details Displayed if Network Manager is being installed and you selected Customize Settings. Network Manager Domain Name Enter a name to be used as a network domain by Network Manager. Enter a descriptie name, for example, TESTNETWORK. The domain name must consist of between one and 11 characters (letters, numbers, or both), with the letters all capitals, no spaces, and no special characters. Make a note of the domain name, because it is used when starting components manually. Make a note of the domain name, because it is used when starting components manually. Domain name: Discoer subnet Seed Discoery from IBM Tioli NetView Installation Seed Discoery from other network management application None Attention: The domain name is mandatory. You must enter a alue. Select this option if you want the installation process to start a network discoery of your local subnet. Select this option if you want the installation process to start a network discoery using information that you already exported from an IBM Tioli NetView installation. Select this option if you want the installation process to start a network discoery using information from another network management application. Select this option if you want to complete the installation process without starting a discoery. If you choose not to start a discoery now, you can start a discoery later using the Discoery Status GUI. Note: The domain name is mandatory. You must enter a alue under Network Manager Domain Name preiously een if you do not want to start a discoery after installation. Chapter 2. Installing 69

84 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Collect Initial Discoery Information Collect SNMP V1/V2 Community Strings Get NetView Discoery Data Get Generic Discoery Data Displayed if you chose to discoer your local subnet. Displayed if you chose to discoer your local subnet. Displayed if you chose to use NetView data to seed your discoery. Displayed if you chose to use information from another network management application to seed your discoery. IP address of the subnet to be discoered Netmask List of community strings Full name of the NetView migration script output Full name of the file containing the network nodes Full name of the file containing the SNMP community strings Enter the IP address of the subnet to be discoered. Only IP4 addresses can be entered here. Enter the netmask of the subnet. For a class C subnet, this is Enter up to six SNMP community strings (passwords). These community strings are needed by the discoery process in order to get SNMP information from deices on your network. To reduce discoery time, list the community strings in order, from most frequently to least frequently used. Enter the location of the output of the IBM Tioli NetView migration script that you ran from the Launchpad as part of the installation prerequisites. Enter the location of the file that contains a list of nodes in your network. The file must be in a format that can be parsed by the File finder, for example, a text file containing a list of IP addresses and hostnames separated by spaces. Enter the location of the file that contains a list of community strings used in your network. 70 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

85 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Collect DB2 Installation Details Create Network Manager Topology database tables Displayed if a DB2 database is being installed. Displayed if a DB2 database is not being installed. DB2 database port DB2 database name DB2 database account name DB2 database account password Confirm Password Create tables to hold topology data in selected database Enter a port to be used for connections to the DB2 database. The port must not currently be in use. The default is Enter a name for use as the DB2 database name. The default is ITNM. Enter the name of the system account to be used to access the DB2 database. The name must be in lowercase letters and numbers. The default is ncim. Note: Do not use an existing account. If the database account already exists on the operating system, an error message is displayed and you must ensure you create a new account to continue. Enter a password for the DB2 database account. Restriction: The password must not start with a dollar sign ($). Re-enter the database password. Select this option to configure the selected topology database. You only need to do this once for any topology database. If you hae already installed a component of Network Manager and selected this option in a preious installation, do not select this option now. Chapter 2. Installing 71

86 Table 8. Wizard panels and their alues (continued) Wizard panel When panel is displayed Value/option Description Connect to Existing DB2 Database Displayed if an existing DB2 database is being used for topology data. DB2 database serer host name DB2 database port DB2 database name DB2 database account name DB2 database account password Confirm Password Enter the name of the serer on which the DB2 database is installed. Enter the ports that is used for connections to the DB2 database. Enter the name for the DB2 database. Enter the name of the DB2 administrator account. Enter the password for the DB2 administrator account. Re-enter the administratie password. Pre-Installation Summary Always displayed. None Reiew the information about the components that will be installed. Click Next to run a final prerequisite check before installation. Prerequisite Checking Results Always displayed. None Reiew the results of the prerequisite check. This prerequisite check establishes whether the current serer is suitable for installing the specific components that you hae chosen. If there are any serious errors, you must cancel the installation, fix the errors, and start the installation again. If there are no serious errors, click Install to install your chosen components. When prompted, accept any license agreements to continue. Installing Network Manager in console mode If you cannot run the GUI-based installation wizard, then install Network Manager in console mode. When you install in console mode, you specify installation options by responding to menus and prompts in a text-based user interface. To run the installer in console mode, complete the following tasks: 1. Run the installation script with the -i console option. UNIX Enter the following command: install.sh -i console 2. Make the appropriate selections, and select to perform a basic or custom installation. 72 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

87 3. Follow the prompts, using the same alues as for a GUI-based basic or custom installation, depending on your choice. Note: During a custom installation, you must select at least one Network Manager component to install. You cannot use the Network Manager installer to install other products without installing at least one of the Network Manager components. The Network Manager installer only installs Tioli Netcool/OMNIbus and a local DB2 in conjunction with the installation of Network Manager components, and does not install them in a stand-alone setup. For distributed installations, use the natie installer of the products to ensure that the products are customized to the specific needs of the enironment. 4. At any time, type back to return to the preious screen, or quit to exit the installer. At the end of a successful installation, the installer records in NCHOME/log/install/Configuration.log the ports used by each product or component that was installed. Note: If you intend to migrate NCIM data to this Network Manager installation, do not start the processes at this time. Migrate the NCIM data first and then start the Network Manager processes from the command line. For more information, see Importing NCIM topology database data. Related reference: Values for a basic installation on page 52 Use this information to understand what alues to enter in the wizard panels for a basic installation. Values for a custom installation on page 56 Use this information to understand what alues to enter in the wizard panels for a custom installation. Installing Network Manager in silent mode In silent mode, the installer reads the configuration information from a file, and does not prompt you for any information. You can run the installer in silent mode if, for example, you want to deploy Network Manager with identical installation options on multiple machines, or when you are installing on a system that has no access to any GUI. You cannot cancel a silent installation once it has started. The silent mode of installation is a two-step operation that requires you to define your installation settings in a response file and then run the installation program with the settings in this file. To install in silent mode, complete the following steps. 1. Create a response file that defines the features you want to install. You hae the following options to create the response file: Option Create a response file using the launchpad Create a response file by editing the sample file proided Description Creating a response file using the launchpad on page 74 Creating a response file using sample file on page 75 Chapter 2. Installing 73

88 Option Create a response file by running the installer in console mode Description You can create a response file by running the installer in console mode and answering yes to the question Generate Silent Response File? when prompted. You can then create a silent response file interactiely by answering on-screen questions without using a GUI. Console mode then creates a file named silent-install.txt in the directory you specify as the installation directory. The default is /opt/ibm/tioli/netcool. See Installing Network Manager in console mode on page After you hae created the response file, start the installation script for your operating system: UNIX Start the install.sh script using the following command: install.sh -i silent -f path to response file At the end of a successful installation, the installer records in NCHOME/log/install/Configuration.log the ports used by each product or component that was installed. Note: If you intend to migrate NCIM data to this Network Manager installation, do not start the processes at this time. Migrate the NCIM data first and then start the Network Manager processes from the command line. For more information, see Importing NCIM topology database data. Creating a response file using the launchpad You can create the response file for your silent installation using the launchpad. To create the response file using the launchpad: 1. Go to the directory where you extracted the Network Manager installation package. 2. Start the launchpad. UNIX Run the launchpad.sh script. 3. Click Installing Network Manager. 4. Expand Create a Response File for Silent Installation and click Generate a response file for a basic installation or Generate a response file for a custom installation depending on whether you want to perform a basic or a custom installation silently later on. 5. Follow the instructions on the panels to enter alues for the response file. The panels are the same as when you install Network Manager using the wizard. Tip: Check the alues for basic or custom installation topics to understand the alues to enter in the wizard panels. 6. Sae the file. Run the installation script with the silent command line option and full path to this file. 74 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

89 Related reference: Values for a basic installation on page 52 Use this information to understand what alues to enter in the wizard panels for a basic installation. Values for a custom installation on page 56 Use this information to understand what alues to enter in the wizard panels for a custom installation. Creating a response file using sample file You can create the response file for your silent installation by editing the sample file proided. To create the response file by editing the sample: 1. Back up the sample response file. The sample response file, ITNM-sample-response.txt, is in the top leel directory, whereer the installation package was extracted. 2. Edit the sample response file in a text editor. a. Uncomment any parameters that you want to use by remoing the hash character # at the beginning of the line. b. Check the default alues of the parameters and set new alues as necessary. c. Replace all instances of --UserInput-- with the appropriate alues. 3. Sae the file in a conenient location, for example, in the same directory as the Network Manager INSTALL script. Run the installation script with the silent command line option and full path to this file. Sample response file parameters for silent mode installation: Use this information to understand how to edit the response file for a silent installation. List of response file parameters The following table lists the parameters proided in the default response file for silent installation in the order in which they appear in the file. Table 9. Response file parameters Parameter Default alue Description INSTALLER_UI SILENT Do not change this alue or remoe this line. SingleSerer 0 Do not change this alue or remoe this line. DefaultValues 0 Do not change this alue or remoe this line. Chapter 2. Installing 75

90 Table 9. Response file parameters (continued) Parameter Default alue Description $LICENSE_ACCE PTED$ USER_INSTALL_ DIR false /opt/ibm/tioli/ netcool To accept the license agreement, uncomment the ariable and change the alue to true. If the LICENSE_ACCEPTED is anything other than true, the installation will exit and no log will be produced and no indication of failure proided. By remoing the # sign before #LICENSE_ACCEPTED=false and changing false to true you hae signified acceptance of the Network Manager license agreement. If you are installing on UNIX, proide the fully qualified path to the directory where you want to install the product. installomni 0 Set the alue as follows: Set the alue to 1 to install and configure Tioli Netcool/OMNIbus, the necessary Tioli Netcool/OMNIbus probes, and the IBM Tioli Netcool/OMNIbus Knowledge Library. Set the alue to 2 to configure an existing Tioli Netcool/OMNIbus that is already installed on this system. Set the alue to 3 to connect to an existing Tioli Netcool/OMNIbus without configuring it. Set the alue to 0 if you do not want to install, configure, or connect to Tioli Netcool/OMNIbus at this time. Attention: Using the Network Manager installer to configure an existing Tioli Netcool/OMNIbus also installs the SNMP probe and the Netcool/OMNIbus Knowledge Library. If you do not want to oerwrite your existing SNMP probe and Netcool/OMNIbus Knowledge Library customizations, you must set the installomni alue to 0. After the installation of Network Manager, copy the installation package to the serer where your existing Tioli Netcool/OMNIbus installation is, and run the ConfigOMNI script to configure your Tioli Netcool/OMNIbus, but ensure you do not select options to configure the SNMP probe or the Netcool/OMNIbus Knowledge Library. For more information, see Configuring an existing Tioli Netcool/OMNIbus installation on a remote serer on page 41. installtip 0 Set the alue to 1 to install and configure the Tioli Integrated Portal, the Tioli Netcool/OMNIbus Web GUI, and the Network Manager Web applications. 76 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

91 Table 9. Response file parameters (continued) Parameter Default alue Description installitnm 0 Set the alue to 1 to install and configure the Network Manager core components (the root cause analysis, eent gateway, discoery and polling engines). installncim 0 Set the alue to 1 to install and configure DB2 for use as the topology database. IAGLOBAL_comply FIPS IALOCAL_ITNM_ PASSWORD PACKAGE.DIR. NCO 0 Set the alue to 1 to use cryptographic routines that hae been designed with FIPS compliance in mind. --UserInput-- --UserInput-- Proide a password for the default itnmadmin and itnmuser user accounts. If the IDS database account already exists on the operating system, enter the password used to access it. If IBM Tioli Netcool/OMNIbus is being installed on this system (in this case you would hae set the installomni to 1 aboe) and the package is not in the same location as the install media, uncomment the PACKAGE.DIR.NCO ariable, and change "--UserInput--" to the full path name where the Tioli Netcool/OMNIbus package can be found on the system. Then uncomment the PACKAGE.NCO ariable and change "--UserInput--" to the name of the directory or file containing Tioli Netcool/OMNIbus. Note: The installer looks for the name plus a.tar,.tar.gz,.tar.z or.zip suffix automatically, so do not add a suffix to the file name. PACKAGE.NCO --UserInput-- See the instructions for the PACKAGE.DIR.NCO parameter. OMNIHOME IAGLOBAL_OBJE CTSERVER_PRI MARY_HOST /opt/ibm/tioli/ netcool/omnibus --UserInput-- On UNIX, if IBM Tioli Netcool/OMNIbus is already installed on this system and you wish to configure it for use with Network Manager (in this case you would hae set the installomni to 2 aboe), complete the following tasks: 1. Uncomment the OMNIHOME ariable for a UNIX directory. 2. Proide the full path name of the directory that contains Tioli Netcool/OMNIbus. If this installation will be connecting to an existing IBM Tioli Netcool/OMNIbus (in this case you would hae set the installomni to 0 aboe), then uncomment the IAGLOBAL_OBJECTSERVER_PRIMARY_ HOST and proide the short name or IP address of the serer where IBM Tioli Netcool/OMNIbus is already installed. Chapter 2. Installing 77

92 Table 9. Response file parameters (continued) Parameter Default alue Description IAGLOBAL_OBJE CTSERVER_PRI MARY_NAME IAGLOBAL_OBJE CTSERVER_PRI MARY_PORT IAGLOBAL_OBJE CTSERVER_USER IALOCAL_OBJEC TSERVER_PASS WORD --UserInput-- Enter the name of the ObjectSerer that is being installed, or that you want this installation to connect to Enter the port for the ObjectSerer that is being installed, or that you want this installation to connect to. root --UserInput-- Enter the administratie user name for the ObjectSerer that is being installed, or that you want this installation to connect to. Enter the administratie password of the ObjectSerer that is being installed, or that you want this installation to connect to. Install_SYSLOG 0 Specifies whether to install the SYSLOG probe during the installation process. Set alue to 1 if you want to install the probe, or set to 0 if you do not. Install_SNMPD 0 Specifies whether to install the SNMPD probe during the installation process. Set alue to 1 if you want to install the probe, or set to 0 if you do not. Install_NCKL 1 Specifies whether to install the Netcool/OMNIbus Knowledge Library during the installation process. Set alue to 1 if you want to install the library, or set to 0 if you do not. IAGLOBAL_WAS _defaulthost IAGLOBAL _CONSOLE _CONTEXT_ROOT IAGLOBAL_WAS UserID IALOCAL_WAS Password Enter the port to be used for the Tioli Integrated Portal. /ibm/console tipadmin --UserInput-- Make a note of the port number, because you use this to connect to the Web applications. Specify the context root that determines the URL that users supply to access the Tioli Integrated Portal and hence Network Manager. Enter a name to be used for the Tioli Integrated Portal administrator account. Enter a password to be used for the Tioli Integrated Portal administrator account. TIP_INSTALL_DIR /opt/ibm/tioli/tip If you are installing on UNIX, proide the fully qualified path to the directory where you want to install the Tioli Integrated Portal. IAGLOBAL_INST ALL_LOCATION_ SELECTION create Set to create if you want to install the Tioli Integrated Portal. Set to reuse if you want to use an existing Tioli Integrated Portal. 78 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

93 Table 9. Response file parameters (continued) Parameter Default alue Description IAGLOBAL_WUI_ HOME /opt/ibm/ WebSphere/ UpdateInstaller On UNIX systems, if you are using an existing Tioli Integrated Portal and set IAGLOBAL_INSTALL_LOCATION_ SELECTION to reuse, then uncomment this parameter and proide the fully qualified path to the directory where the WAS Update Installer is located. If the WAS Update Installer has not been installed on the system, you can find the installation package in the top-leel directory of the Network Manager installation media. authomni 1 Set this parameter to 1 to use the ObjectSerer for authentication for Tioli Integrated Portal users. If this parameter is not set or set to 0, then the default internal file-based repository is used for authentication. IAGLOBAL_PREC ISION_DOMAIN0 --UserInput-- To use LDAP for authentication, set to either of the alues and configure LDAP authentication after installation as described in in section Configuring user authentication of the IBM Tioli Netcool/OMNIbus Installation and Deployment Guide. Enter a name to be used as a network domain by Network Manager. Enter a descriptie name, for example, TESTNETWORK. The domain name must consist of between one and 11 characters (letters, numbers, or both), with the letters all capitals, no spaces, and no special characters. Make a note of the domain name, because it is used when starting components manually. UI_Initial_Discoery 0 Set to 1 if you want the installation process to start a network discoery of your local subnet. UI_Import_Netiew 0 Set to 1 if you want the installation process to start a network discoery using information that you already exported from an IBM Tioli NetView installation. UI_Import_Other 0 Set to 1 if you want the installation process to start a network discoery using information from another network management application. UI_No_Discoery 1 Set to 1 if you want to complete the installation process without starting a discoery. If you choose not to start a discoery now, you can start a discoery later the using the Discoery Configuration GUI. Chapter 2. Installing 79

94 Table 9. Response file parameters (continued) Parameter Default alue Description UI_Subnet --UserInput-- If you hae selected to start a discoery, enter the IP address of the subnet to be discoered. Only IP4 addresses can be entered here. UI_Netmask If you hae selected to start a discoery, enter the netmask of the subnet. For a class C subnet, this is UI_SNMP_1 --UserInput-- If you hae selected to start a discoery, you can enter up to six SNMP community strings (passwords). UI_SNMP_2 --UserInput-- If you hae selected to start a discoery, you can enter up to six SNMP community strings (passwords). UI_SNMP_3 --UserInput-- If you hae selected to start a discoery, you can enter up to six SNMP community strings (passwords). UI_SNMP_4 --UserInput-- If you hae selected to start a discoery, you can enter up to six SNMP community strings (passwords). UI_SNMP_5 --UserInput-- If you hae selected to start a discoery, you can enter up to six SNMP community strings (passwords). UI_SNMP_6 --UserInput-- If you hae selected to start a discoery, you can enter up to six SNMP community strings (passwords). UI_Network_Nodes --UserInput-- Enter the location of the output of the IBM Tioli NetView migration script that you ran from the Launchpad as part of the installation prerequisites. UI_Network_Nodes --UserInput-- If you are seeding discoery from another Network Manager installation, enter the location of the file that contains a list of nodes in your network. UI_SNMP_Strings --UserInput-- If you are seeding discoery from another Network Manager installation, enter the location of the file that contains a list of community strings used in your network. IAGLOBAL_NCI M_SERVER IAGLOBAL_NCI M_CREATE IAGLOBAL_NCI M_PORT IAGLOBAL_NCI M_USERNAME IALOCAL_NCIM_P ASSWORD db2 yes Enter the name of the serer on which to install the NCIM topology database. Set to no if you want to use an existing NCIM topology database Enter the port for the NCIM topology database. ncim --UserInput-- Enter the username for the administrator account for the NCIM topology database. Enter the password for the administrator account for the NCIM topology database. connectdb2 1 Uncomment this line if you want to use an existing DB2 database to hold the topology data. 80 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

95 Table 9. Response file parameters (continued) Parameter Default alue Description IAGLOBAL_NCI M_HOST IAGLOBAL_NCI M_CREATE IAGLOBAL_NCI M_PORT IAGLOBAL_NCI M_DBNAME IAGLOBAL_NCI M_USERNAME IALOCAL_NCIM_P ASSWORD StartDaemons --UserInput-- yes If you are using an existing database to hold the topology data, enter the name or IP address of the host where the database is installed. If you are using an existing database to hold the topology data, set this alue to yes in order to create the NCIM database tables. Set this alue to no if the NCIM database tables already exist If you are using an existing database to hold the topology data, enter the port used by the database. ITNM ncim --UserInput-- Start IBM Tioli Network Manager before exiting If you are using an existing DB2 database to hold the topology data, enter the name of the DB2 database instance that holds the topology data. This is the user that the product uses to connect to the database. Do not change this alue. Enter the password for the ncim user. Uncomment this line if you want to start Network Manager before the installer exits. Postinstallation tasks After installing Network Manager, you might need to perform some postinstallation tasks. Make sure you hae successfully installed Network Manager. To perform postinstallation tasks: 1. Ensure your Network Manager installation has completed. 2. Optional: If you want to use an existing installation of Tioli Netcool/OMNIbus (ersion or 7.4) that is configured for a preious ersion of Network Manager (ersion 3.9 or earlier), you must follow additional post-installation steps to set up the automation for serice-affected eents (SAE), as described in Configuring automation for SAEs on page Depending on the additional settings required, perform the steps in the following topics: Option Configuring LDAP for user authentication Description After a successful installation of Network Manager, you can configure LDAP for user authentication, as described in in section Configuring user authentication of the IBM Tioli Netcool/OMNIbus Installation and Deployment Guide Chapter 2. Installing 81

96 Option Description Non-root postinstallation tasks (UNIX only) Upgrading from a preious Network Manager ersion Installing the Monitoring agent Setting up network management reports to use with Tioli Common Reporting after installing Network Manager DB2 can only be installed by the root user. If you installed Network Manager as non-root and you also selected DB2 to be installed on the same serer as part of the installation, perform the steps described in Installing and configuring DB2 after a non-root installation on page 216 If you want to use an existing DB2 installation for your topology database either on the same serer where Network Manager is installed or on a different serer, you must install the DB2 runtime client as described in Configuring connection to existing DB2 on page 217. If you installed the DB2 serer using the Network Manager installer, you do not need to follow these steps. You can configure what user manages Network Manager processes, as described in Configuring root/non-root permissions on page 213 For non-root installations, you can configure your Network Manager processes to start automatically when your system is started or restarted, as described in Non-root installation: Configuring processes to start automatically on page 215. Note: You do not need to configure this if you installed Network Manager as the root user. The automatic restart is set up as part of a root installation without the need for this post-installation step. Follow steps described in Upgrading and migrating to latest Network Manager on page 110 If you want to use IBM Tioli Monitoring for IBM Tioli Network Manager IP Edition, follow the steps described in Integrating with IBM Tioli Monitoring on page 201 During installation, Network Manager installs and configures network management reports if Tioli Common Reporting is present on the system. If you do not hae Tioli Common Reporting installed when installing Network Manager, you can install Tioli Common Reporting at a later date and configure the reports then. After installing Network Manager, configure the reports as described in Configuring reports for existing installations on page IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

97 Option Migrating Cognos content store from the default Derby database to DB2 Upgrading to Tioli Integrated Portal Increasing memory for Tioli Integrated Portal If you need to set up a topology database after installation for Network Manager. For any further configuration tasks, check topics in: After successfully installing and configuring Network Manager, see the getting started sections Description The default content store database that is used by Cognos is suitable for demonstration purposes, but it is not to be used as the content store database in a production enironment. You hae the option of migrating the Cognos content store database from the default Derby database to DB2 as described in Migrating the Cognos content store from Derby to DB2 on page 240. You must hae Tioli Integrated Portal or later to use Firefox 17 ESR. Network Manager 4.1 includes Tioli Integrated Portal To upgrade to : 1. Go to the Tioli Integrated Portal support site at ibm.com/support/fixcentral/swg/ selectfixes?parent=ibm~tioli &product=ibm/tioli/ Tioli+Integrated+Portal&release= &platform=all&function=all 2. Download the Fix Pack. 3. Follow the Fix Pack installation instructions to apply the Fix Pack. Depending on your system and network size, you might need to increase the amount of memory aailable to the Tioli Integrated Portal. To increase the amount of memory aailable to the Jaa Virtual Machine (JVM), follow the steps about increasing memory for the Jaa Virtual Machine in the IBM Tioli Network Manager IP Edition Administration Guide. You can set the initial and the maximum amount of memory, in MB (heap size). The maximum amount of memory can be increased up to 2048 MB on UNIX systems. For details of how to create the database schemas manually after installation, see the tasks about creating topology database schemas in the IBM Tioli Network Manager IP Edition Administration Guide. Chapter 4, Configuring Network Manager, on page 151 For more information, see the tasks in the IBM Tioli Network Manager Getting Started Guide. Chapter 2. Installing 83

98 Related tasks: Viewing the installation logs Viewing the installation logs can be useful for troubleshooting purposes. Troubleshooting the installation Use this information to how to troubleshoot errors that might occur during the installation of Network Manager. The following topics describe the types of error messages that you might encounter during the installation process, and the actions you can take to resole these issues. Viewing the installation logs Viewing the installation logs can be useful for troubleshooting purposes. Information about the success of the installation process is recorded in different log files. To iew the installation log information, proceed as follows. For general settings of the Network Manager installation, such as information about the ersion of Network Manager installed, the home location of components, and database connection information, see the NCHOME/etc/itnm.cfg file. Note: The Network Manager installation process inoles seeral components. This means that an unsuccessful installation might be caused by other component installers running into issues. The releant log files contain information for the cause of the failure. Consult the appropriate installation log: Symptom For an oerall idea about which part of the installation failed Action Examine NCHOME/log/install/Configuration.log first to check what part of the installation encountered problems. The Configuration.log file helps determine where you need to look next. Configuration.log also shows errors encountered by post-installation setup tasks, and contains other useful information such as the ports used by each product or component that was installed. The part of the installation that appears to hae failed inoles Tioli Netcool/OMNIbus You can also examine the InstallAnywhere log file for more details about any problems. To examine the InstallAnywhere log file: 1. Go to the home directory of the user who ran the installer. 2. Open the IA-ITNM-Install-NN.log file, where NN is a number. Typically the file is called IA-ITNM-Install- 00.log. If there are problems with Tioli Netcool/OMNIbus, examine the following files: If the problem is an installation problem, go to the home directory of the user who ran the installer, and examine the IA-Netcool-OMNIbus-Core* file. If the problem is a runtime or configuration problem, then reiew the files in OMNIHOME/log. 84 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

99 Symptom The part of the installation that appears to hae failed inoles Network Manager components The part of the installation that appears to hae failed inoles the database The part of the installation which appears to hae failed inoles the Tioli Integrated Portal or Web GUI It looks like the Tioli Integrated Portal serer itself has failed to start up successfully, een though there were no errors in any of the aboe log files, The part of the installation which appears to hae problems inoles the BIRTExtension Action For installation problems, check the files in NCHOME/log/install. The newest files in the directory are the ones that typically hae errors in them. If the problem is related to Composite Offering Installer (COI) or IBM Autonomic Deployment Engine (DE), check the files in TIPHOME/_uninst/ITNM/plan/install/logs/*/ logs and in the associated TIPHOME/_uninst/ITNM/plan/ install/machineplan_localhost directory. If the problem appears to be specifically DE-related, look for further details in /usr/ibm/common/acsi/logs/root/ de_trace.log. You can locate these log files in the following locations: If you are installing as root on UNIX, these will be in /usr/ibm/common/acsi/logs/root. If you are installing as a non-root user on UNIX, these will be in ~/.acsi_$hostname/logs/$user. For runtime problems, check files in NCHOME/log/ precision/*. If the problem appears to be a DB2 installation problem, check the NCHOME/log/install/installDB2.log file. The NCHOME/log/install/create_all_schemas.log file shows errors that occurred during the creation of the NCIM topology database. For Tioli Integrated Portal problems, check the ~/TIPInstaller-00.log file and the files in TIPHOME/logs for installation problems, and the files in TIPHOME/profiles/TIPProfile/logs/serer1 for runtime problems. For Web GUI problems, check the ~/OMNIbusWebGUI_Install-00.log file. In either case, if the problem appears to be related to the COI or DE, examine the files in NCHOME/omnibus_webgui/ _uninst/omnibuswebgui740/plan/install/logs/*/logs and in the associated NCHOME/omnibus_webgui/_uninst/ OMNIbusWebgui740/plan/install/MachinePlan_localhost directory. If the problem appears to be specifically DE-related, look for further details in /usr/ibm/common/acsi/logs/root/ de_trace.log (or ~/.acsi_$username/logs/$username/ de_trace.log ). Examine the log files in this directory: TIPHOME/profiles/ TIPProfile/logs/serer1. These log files contain information about the Tioli Integrated Portal serer status. Examine the logs in TIP_components/BIRTExtension/logs. Note: The default location for TIP_components is /opt/ibm/tioli/tip2components. Chapter 2. Installing 85

100 Symptom The part of the installation which appears to hae problems inoles the ESSSerer Action Examine the logs in TIP_components/ESSSerer/logs. Note: The default location for TIP_components is /opt/ibm/tioli/tip2components. TIPProfile_create log Reiew the TIPProfile_create log when your installation ends in error. Purpose The TIPProfile_create log records the messages that result from the successful or failed completion of a task in the process of creating the Network Manager profile during installation. Sample This is a sample of the final records of a TIPProfile_create.log where errors were encountered. <record> <date> t01:20:43</date> <millis> </millis> <sequence>1007</sequence> <logger>com.ibm.ws.profile.cli.wsprofileclimodeinoker</logger> <leel>info</leel> <class>com.ibm.ws.profile.cli.wsprofileclimodeinoker</class> <method>arecommandlineargumentsvalid</method> <thread>10</thread> <message>validation Error for profilepath: The profile path is not alid. </message> </record> <record> <date> t01:20:43</date> <millis> </millis> <sequence>1008</sequence> <logger>com.ibm.ws.profile.cli.wsprofileclimodeinoker</logger> <leel>severe</leel> <class>com.ibm.ws.profile.cli.wsprofileclimodeinoker</class> <method>inokewsprofile</method> <thread>10</thread> <message>argument Validation Failed.</message> </record> <record> <date> t01:20:43</date> <millis> </millis> <sequence>1009</sequence> <logger>com.ibm.ws.profile.cli.wsprofileclimodeinoker</logger> <leel>info</leel> <class>com.ibm.ws.profile.cli.wsprofileclimodeinoker</class> <method>inokewsprofile</method> <thread>10</thread> <message>returning with return code: INSTCONFFAILED</message> </record> <record> <date> t01:20:43</date> <millis> </millis> <sequence>1010</sequence> <logger>com.ibm.wsspi.profile.wsprofilecli</logger> <leel>info</leel> <class>com.ibm.wsspi.profile.wsprofilecli</class> 86 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

101 <method>inokewsprofile</method> <thread>10</thread> <message>returning with return code: INSTCONFFAILED</message> </record> Log files Locate and reiew the logs and related files after an installation to confirm that the components were successfully installed. Here are the logs created during a Network Manager installation. The installer creates a log called IA-TIPInstall-xx.log, which is located in the user's home directory. This should be the first log reiewed. It shows the installation as it progresses, giing tracing information. Each step that is executed in the installation creates a log in the TIPHOME/logs directory. Administratie console createprofile.err createprofile.out createtipserice.err createtipserice.out deleteprofile.err (uninstall) deleteprofile.out enableappsecurity.err enableappsecurity.out extendjaememory.err extendjaememory.out modifywassericename.err modifywassericename.out remoetipserice.err (uninstall) remoetipserice.out Common Gateway Interface Serer CGISerer.err CGISerer.out configureiauthzshlib.err configureiauthzshlib.out deployiauthzear.err deployiauthzear.out Enterprise Storage Serer deployessapplication.err deployessapplication.out ESSConfiguration.err ESSConfiguration.out osgicfginit.err osgicfginit.out IBM Tioli Monitoring Web Serice ITMWebSericeEAR.err ITMWebSericeEAR.out Charting assignchartadminrole.err assignchartadminrole.out TIPChartPortlet.err TIPChartPortlet.out Reporting Time Scheduling Serices TipTssEar.err TipTssEar.out TipTssEWASScheduler.err TipTssEWASScheduler.out TipTssJDBC.err TipTssJDBC.out TipTssSharedLibraries.err TipTssSharedLibraries.out Chapter 2. Installing 87

102 Tioli Common Reporting tcr.err tcr.out tcrconfigclient.err tcrconfigclient.out tcrspostconfig.err tcrspostconfig.out Tioli Integrated Portal configuretiptransformationshlib.err configuretiptransformationshlib.out deploytipchangepassdwar.err deploytipchangepassdwar.out deploytipredirectorear.err deploytipredirectorear.out renameidmgrrealm.err renameidmgrrealm.out Virtual Member Manager VMM.err VMM.out VMM LDAP Configuration configurevmmldap.err configurevmmldap.out VMM ObjectSerer Plugin VMMObjectSererPlugin.err VMMObjectSererPlugin.out WebSphere checkwas.err checkwas.out startwas.err startwas.out Checking login URL and default ports If you hae trouble logging in, make sure you check the URL format and the ports you use after installation. URL format Check that your URL format entered is as follows (shows default ports): (secure access). (nonsecure access). Where localhost is the fully-qualified host name or IP address of the Tioli Integrated Portal serer. Default ports is the default nonsecure port number and is the default secure port number. If your enironment was configured during installation with a port number other than the default, enter that number instead. 88 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

103 Dependency error messages Dependency error messages are generated if the installation process cannot find a required Network Manager package or component. If a dependency error message is displayed, follow the prompts and install the required components. Running installation and maintenance procedures as root or non-root The installation must be run by the same operating system user each time. Whicheer user installs the first Tioli Network Management product on a gien workstation must also install, uninstall, or modify eery subsequent Tioli Network Management product on that workstation. You can run the installation as a non-root user. Howeer, certain Network Manager configuration actions must be performed by the root user. A wizard panel at the end of the installation wizard reminds you to log in as root and make these configurations manually. Related concepts: Root and non-root installation on page 213 On UNIX Network Manager can be installed as either the root user or a non-root user. Related tasks: Configuring the core components to run as root on page 214 On UNIX, if you installed Network Manager as a non-root user, you must perform additional configuration to run the core components as the root user. Not enough disk space to complete the installation If there is not enough disk space to complete the installation, an error message is displayed and the installation is aborted. The error message is as follows: There is not enough space in DIRECTORY to install the software Please free up some space and re-run the installation In this message, DIRECTORY refers to the specified root installation directory. If you encounter this error message, clear space on the disk, or select a root directory on a partition with more space, and run the installation process again. Console mode installation error When installing Network Manager in console mode on UNIX systems, you might receie an error due to the DISPLAY enironment ariable being set. If you receie the following error message when installing Network Manager in console mode on UNIX systems, you will need to remoe the setting for the DISPLAY enironment ariable before starting the console mode installation: Chapter 2. Installing 89

104 Installing... Inocation of this Jaa Application has caused an InocationTargetException. This application will now exit. Stack Trace: jaa.lang.noclassdeffounderror: sun.awt.x11graphicsenironment (initialization failure) at jaa.lang.j9vminterals.initialize(j9vminterals.jaa:140) at jaa.lang.class.fornameimpl (Natie Method) at jaa.lang.class.forname(class.jaa:136) Use the following command: unset DISPLAY; then start the console install again. Backing up and restoring the Deployment Engine Use the Deployment Engine (DE) backup script before installing additional components or other products that are based on the Tioli Integrated Portal platform. If you need to recoer the original configuration after a failure, you can then run the Deployment Engine restore script. The Deployment Engine performs the installation of new and upgraded products. It keeps track of the installed components and skips installing a gien component if it is already present on the system. Perform the following steps to back up or restore the DE database. 1. From the command line, change to the acsi directory: Linux UNIX For Linux and UNIX-based systems, the path to the acsi directory aries depending on whether you are installing as root or as a non-root user, as follows: Installing as a non-root user, the path is relatie to the user's home directory: <non-root user home directory>/.asci_<user_name> Installing as root, the path is as follows: /ar/ibm/common/asci 2. Initialize the Deployment Engine enironment from the command line: Linux UNIX. seten.sh 3. Change to the bin directory: Linux UNIX For Linux and UNIX-based systems, the path to the bin directory aries depending on whether you are installing as root or as a non-root user, as follows: For a non-root user, change to the bin child directory, that is: <non-root user home directory>/.asci_<user_name>/bin For root, the path is as follows: /usr/ibm/common/asci/bin 4. Run the backup script to back up the Deployment Engine database, as follows: Linux UNIX de_backupdb 5. If you need to restore the Deployment Engine database, from the bin directory run the restore script: Linux UNIX de_restoredb If you backed up the Deployment Engine database, you can run the installer now to add additional components or products. If you restored the Deployment Engine database, you can resume using the original installed enironment. 90 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

105 Harmless installation messages A reiew of the installation log might show error messages that are actually harmless. After installing Network Manager, you might encounter a reflection error when reiewing the installation logs. The installation is successful, but the log shows ariations of this error: +++ Warning +++: IWAV0003E Could not reflect methods for com.ibm.sec.iauthz. InstanceAuthzSericeLocalHome because one of the methods references a type that could not be loaded. Exception: jaa.lang.noclassdeffounderror: com.ibm.sec.iauthz.instanceauthorization +++ Warning +++: IWAV0002E Failed reflecting alues +++ Warning +++: jaa.lang.noclassdeffounderror: com.ibm.sec. iauthz.instanceauthorization This error can be safely ignored. Insufficient disk space for install Hae enough space in the temporary directory for the installation or it will fail. Your product installation requires at least 500 MB of disk space for the temporary files that are used during installation. On Linux and UNIX, allocate enough space in the /tmp or /opt directory of the computer. Installation failure scenario Reiew the IA-TIPInstall-xx.log for any errors that might hae occurred during installation. IA-TIPInstall-xx.log Typically, the installation process stops when a failure occurs. But it can also appear to complete successfully and then later, such as when attempting to log in, you find that there is a problem. Reiew the IA-TIPInstall-xx.log in your home directory to confirm that the installation was successful. For example, if you are logged in as Administrator on a Windows system, then you would look in C:\Documents and Settings\Administrator. Log reiew scenario In this example on a Windows system, the ESSSererConfig.xml step failed and IA-TIPInstall-xx.log as shown here appears to hae a COI (Composite Offering Installer) failure at line 134. C:\IBM\tioli\tip\_uninst\ITNM\plan\install\MachinePlan_localhost\ 0011_IAGLOBAL_COI_STEP_ESSSererConfig\IAGLOBAL_COI_STEP_ESSSererConfig.xml:134: xec returned: 105 Wed May 28 15:25: EDT 2008 : STDERR : at org.apache.tools.ant.projecthelper. addlocationtobuildexception(projecthelper.jaa:539) Wed May 28 15:25: EDT 2008 : STDERR : at org.apache.tools.ant.taskdefs.ant. execute(ant.jaa:384) Wed May 28 15:25: EDT 2008 : STDERR : at org.apache.tools.ant.task.perform (Task.jaa:364) Wed May 28 15:25: EDT 2008 : STDERR : at com.ibm.ac.coi.impl.utils. AntHelper.ant(AntHelper.jaa:88) Wed May 28 15:25: EDT 2008 : STDERR :... 3 more Chapter 2. Installing 91

106 The log proides you with the full path to the location of the failing file. Naigate to that location, open the file indicated, and check the line that failed. In this example you would naigate to: C:\IBM\tioli\tip\_uninst\ITNM\plan\install\MachinePlan_localhost\ 00011_IAGLOBAL_COI_STEP_ESSSererConfig\IAGLOBAL_COI_STEP_ESSSererConfig.xml and study line 134. At line 134 of target configureess, the following command did not execute successfully <target name="configureess" depends="setproperties"> <echo message="start to configure Authentication Serice..."/> <iaecho message="$essserver_configuring$"/>... line134: <exec dir="${iaglobal_installlocation}/bin" executable="${iaglobal_installlocation}/bin/wsadmin${platform.script.ext}" failonerror="true"> <redirector output="${iaglobal_installlocation}/logs/ ESSConfiguration.out" error="${iaglobal_installlocation}/logs /ESSConfiguration.err"/>... As you can see, the wsadmin call from Ant sends stdout to TIPHOME/logs/ ESSConfiguration.out and stderr to TIPHOME/logs/ESSConfiguration.err. A reiew of the ESSConfiguration.out file shows that the Tioli Integrated Portal Serer (WAS) might hae a problem: WASX7209I: Connected to process "serer1" on node TIPNode using SOAP connector; The type of process is: UnManagedProcess WASX7303I: The following options are passed to the scripting enironment and are aailable as arguments that are stored in the arg ariable: "[C:/IBM/tioli/tip/logs/ltpaOutput.txt, 1ntegrate]" WASX7017E: Exception receied while running file "C:\IBM\tioli\tip\bin \configureess.jacl"; exception information: com.ibm.bsf.bsfexception: error while eal ing Jacl expression: no accessible method "isessconfigured" in class com.ibm.ws.scripting.admincommand.admintask while executing "$AdminTask isessconfigured" inoked from within "set esscheck [$AdminTask isessconfigured]" Check the TIPHOME/profiles/TIPProfile/logs/serer1/SystemOut.log for any exceptions that might be related to the Authentication Serice. If you are not able to assess this, ask the resident Tioli Integrated Portal Serer expert or gather the Network Manager logs, including SystemOut.log, and contact IBM Support. Install fails after deployment engine upgrade Running the installer on a computer that has an existing Tioli Integrated Portal enironment can fail if the deployment engine (DE) was upgraded from a ery early ersion. If you hae an old ersion of the DE installed, the Tioli Integrated Portal installer will upgrade it and continue with the installation. On rare occasions certain older ersions of the DE might not be upgraded successfully. When this happens, the installation can fail. If you are aware that your product uses a ery old ersion of the DE (such as Version 1.2), you can install on the same machine, but sign on to the portal with a different user name. If your old ersion of the DE was initially installed as root user on the Linux or UNIX operating system, consider uninstalling it if your new installation is failing after the DE upgrade. 92 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

107 Uninstalling Network Manager You must use the scripts proided to uninstall the product. Important: You must always use the scripts to uninstall the product. Uninstalling the product by remoing files and directories might result in problems reinstalling components. Remoing reports If you uninstall Network Manager, you must also remoe the Network Manager reports and the data sources for the reports. Follow these steps before uninstalling Network Manager to remoe the Network Manager reports and their settings. To remoe Network Manager reports and their data source settings: 1. Log in to the Network Manager GUI in a supported browser as a user with administrator permissions. 2. Click Common reporting in the naigation pane on the left side of the window. 3. Select the check box next to Network Manager. 4. Click the delete icon to remoe the Network Manager reports. 5. Click the Launch menu in the upper right of the window. Click Cognos Administration from the list and click the Configuration tab. 6. Select the check boxes next to the following data sources: IBM_TRAM NCIM NCMONITOR NCPGUI NCPOLLDATA PARAMETERS 7. Click the delete icon to remoe the selected data sources. Uninstalling on UNIX On UNIX operating systems, you must uninstall the product using the uninstall script. You can uninstall specific components or the entire product in a command line mode. Important: If you want to remoe any products that are integrated with Network Manager on the same serer, remoe them using their own uninstallers before remoing Network Manager. For example, make sure you remoe Tioli Common Reporting using its uninstaller before uninstalling Network Manager using the process discussed in this topic. Attention: Do not attempt to remoe any product by deleting files or directories. This can cause problems reinstalling components. You must use the uninstall script proided with the product to uninstall Network Manager. To uninstall all or part of Network Manager: 1. If you used Network Manager reports, remoe them as described in Remoing reports. You can then remoe Tioli Common Reporting using its uninstaller. Chapter 2. Installing 93

108 2. Source the enironment as follows: a. Go to the Netcool home directory. By default the Netcool home directory location is /opt/ibm/tioli/netcool, so the default command is: cd /opt/ibm/tioli/netcool b. Run the command to source the enironment:.en.sh 3. Optional: Before attempting to uninstall a local DB2 database installed by Network Manager, it might be necessary to remoe any customizations added after the Network Manager installation. For example, if the DB2 high aailability option was set on the database, then the following two DB2 commands must be run before the installation can be uninstalled: DEACTIVATE DATABASE STOP HADR For information on DB2 commands, see Related information below for links to your DB2 Information Center. 4. Optional: If you are using a remote DB2 database for NCIM, or if you hae been using reports, you must uncatalog the database when you uninstall and catalog it again if you reinstall. Use the following command: UNIX $NCHOME/precision/scripts/sql/db2/uncatalog_db2_database.sh database_name where database_name is the name of the NCIM database. 5. Optional: If you are using a DB2 database as the Tioli Data Warehouse database, you must uncatalog the database when you uninstall and catalog it again if you reinstall. For instructions, see the IBM Tioli Monitoring for Tioli Network Manager IP User's Guide. 6. Run the uninstall script: $NCHOME/Uninstall_ITNM Note: Running Uninstall_ITNM command launches the $NCHOME/bin/ CleanSystem script. The uninstall script starts and displays the options you hae. Table 10. Uninstall options Option Description -p Shuts down all processes associated with the installation. -o Remoes Tioli Netcool/OMNIbus from the system. -i Remoes the local topology database from the Network Manager installation. Note: This option can only remoe the default database proided by Network Manager. -n Remoes the Network Manager installation from the system. -t Remoes Network Manager portlets and content from the Tioli Integrated Portal serer. Note: You must run this option on the serer where the Tioli Integrated Portal is installed. 94 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

109 Table 10. Uninstall options (continued) Option Description -c Remoes from the system the Tioli Integrated Portal (including its associated component, Tioli Netcool/OMNIbus Web GUI), the Composite Offering Installer (COI), and the IBM Autonomic Deployment Engine (DE) content. Note: The use of the -c and -a options to remoe Tioli Integrated Portal, the Composite Offering Installer (COI), and the IBM Autonomic Deployment Engine (DE) content can adersely impact other IBM Tioli products installed on the system. For example, using option -c remoes components that Tioli Common Reporting requires to work. Ensure no other Tioli products on the system require those components before using either option. -a Remoes from the system all products and components that hae files or data stored in NCHOME and TIPHOME, including core components, GUI components, Tioli Netcool/OMNIbus, and database components. -h Use this option to specify the installation home directory if not using the default NCHOME. 7. Select the components that you want to remoe by entering the appropriate option. You can enter more than one option. For example, to stop all processes and remoe Tioli Netcool/OMNIbus from the system, enter:./uninstall_itnm -p -o Attention: Remoing components can cause other products that rely on those components to fail. For example, remoing Tioli Netcool/OMNIbus causes IBM Tioli Business Serice Manager to fail. Remoing the core components or the topology database causes errors in the Network Manager Web components. CAUTION: If you select the option to remoe all components, the installation framework, and the Tioli Integrated Portal, other products installed on the same serer, such as Tioli Netcool/OMNIbus, the Tioli Netcool/OMNIbus Web GUI and IBM Tioli Business Serice Manager, might not function. Do not choose this option if you hae any other Tioli products installed on this serer. 8. If you want to reinstall after remoing Network Manager, always reinstall in a new shell window and not the one used to successfully uninstall any preious installation. Note: If portions of Network Manager are being uninstalled so that newer ersions can be reinstalled, then the following directories must not exist after the appropriate Network Manager component has been remoed. If these directories do still exist, then you must remoe them before performing any reinstallation work: Chapter 2. Installing 95

110 Installing fix packs If a newer ersion of the Network Manager Web Applications is going to be reinstalled, then the following directories must not exist before the reinstallation occurs. $NCHOME/precision/integrations $NCHOME/precision/products $NCHOME/precision/profiles $NCHOME/precision/systemApps If a newer ersion of the Network Manager core is going to be reinstalled. then the following directories must not exist before the reinstallation occurs: $NCHOME/etc/precision $NCHOME/precision/adapters $NCHOME/precision/aoc $NCHOME/precision/disco $NCHOME/precision/eentGateway Related tasks: Remoing reports on page 93 If you uninstall Network Manager, you must also remoe the Network Manager reports and the data sources for the reports. Related information: IBM DB2 Version 10.1 Information Center For more information on DB HADR, search the IBM DB2 Version 10.1 Information Center. Suggested search terms inlcude "high aailability". IBM DB2 Version 9.7 Information Center For more information on DB2 9.7 HADR, search the IBM DB2 Version 9.7 Information Center. Suggested search terms inlcude "high aailability". A fix pack inoles moing from one minor release to another within a point ersion, for example, from to To identify the current ersion of any Network Manager process, run the process with the -ersion command line option. To install a fix pack, perform the following steps: 1. Go to the following site to download your fix pack: support/fixcentral/. Search the site for your product and ersion to locate the fix pack for your installation. 2. Download and extract the fix pack installation image for your product. 3. Open the README.1ST file after extracting the fix pack installation image. The README.1ST file proides information on where to locate the INSTALL and README files. 4. For information about installing the fix pack, including prerequisites and installation steps, open the INSTALL file. Consider the preinstallation steps, requirements, restrictions, installation steps, and postinstallation steps. 5. For information about the fixes and enhancements included in the fix pack, and any known problems with the fix pack, open the README file. 6. Stop any running Network Manager processes. 7. Install the fix pack as described in the INSTALL file. 96 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

111 8. Use the README file to check for any known problems with the fix pack and to make any changes necessary due to APARs. Chapter 2. Installing 97

112 98 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

113 Chapter 3. Upgrading and migrating Read about upgrading your ersion of Network Manager and migrating existing installations. Note: The default ports for logging into the application serer are different across ersions. The nonsecure access redirects you to the secure port unless you configured it otherwise (see Configuring access for HTTP and HTTPS on page 196). The default ports for Network Manager ersions 3.9 and later are as follows: (secure access). (nonsecure access). Attention: If you hae multiple Tioli products that use the Tioli Integrated Portal framework, see the Cross Product Migration Reference at Tioli%20Business%20Serice%20Manager1/page/Migration for dependencies and considerations when upgrading and migrating. About upgrading and migrating Read about upgrading your ersion of Network Manager and migrating existing installations. Upgrade paths Network Manager V4.1 is supported only on Red Hat Enterprise Linux and DB2. Use this information to understand which upgrade paths are aailable to Network Manager V4.1. Only the following configurations are supported when upgrading to Network Manager V4.1 from V3.8 or V3.9, or when copying an existing V4.1 installation: You can migrate from any Red Hat Enterprise Linux system to any other Red Hat Enterprise Linux system but migrating from other UNIX systems is not supported. Migrating from Windows systems is not supported. The source and target machines must use the same database type. The only exceptions are the following: V3.8: migrating from the preiously default MySQL source to the default DB2 in V4.1 on the target system is supported. V3.9: migrating from the preiously default Informix source to the default DB2 in V4.1 on the target system is supported. The source and target systems must both be either FIPS or non-fips installations. Migration from a FIPS installation to a non-fips installation, or the reerse, is not supported. The following table displays the supported upgrade paths. Note: Your source system must be patched up to the FixPack leel indicated in the table. Copyright IBM Corp. 2006,

114 Table 11. Supported upgrade paths From source system Version and FixPack Operating system V3.8 FixPack 6 Red Hat Enterprise Linux 4.0 or 5.0 V3.9 FixPack 3 Red Hat Enterprise Linux 5.0 or 6.0 V3.9 Refresh of full product image (release date: 2012 September 13 - build ) 2 Red Hat Enterprise Linux 5.0 or 6.0 Database Version of Tioli Integrated Portal To target system Version and FixPack Operating system MySQL V1.x V4.1 Red Hat DB2 Enterprise Linux 5.0 or Informix V2.1 DB2 Informix DB2 V2.2 Table notes: 1. Tioli Common Reporting V2.x is not supported on Red Hat Enterprise Linux Users of Netcool Network Management must use this upgrade path. Database DB2 9.7 DB2 10.x Related information: IBM Netcool Network Management V9.2 Information Center The Netcool Network Management V9.2 solution consists of IBM Tioli Netcool/OMNIbus V7.4, IBM Tioli Network Manager IP Edition V3.9, and IBM Tioli Netcool Configuration Manager V6.4. In this information center, you can find information about installing, configuring, integrating, and using the products that make up the solution. Upgrading from other products and ersions If you hae a ersion of Network Manager prior to 3.8, or if you hae Tioli NetView, and you want to upgrade to the latest ersion of Network Manager, then you must first upgrade to a later ersion. If you hae a ersion of Network Manager prior to 3.8, then do the following: 1. Upgrade to ersion 3.8. For instructions on upgrading to ersion 3.8, go to com.ibm.networkmanagerip.doc_3.8/welcome.htm. 2. Apply FixPacks to bring you up to V3.8 FixPack Follow the instructions at Upgrading and migrating to latest Network Manager on page 110. If you hae Tioli NetView, then do the following: 1. Migrate to ersion 3.9. For information on migrating from Tioli NetView to ersion 3.9, go to topic/com.ibm.networkmanagerip.doc_3.9/itnm/ip/wip/install/task/ nmip_ins_migratingfromnetiew.html. 2. Apply FixPacks to bring you up to V3.9 FixPack Follow the instructions Upgrading and migrating to latest Network Manager on page IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

115 If you hae Netcool Network Management V9.2 and you want to upgrade the Network Manager component to V4.1, then follow the instructions at Upgrading and migrating to latest Network Manager on page 110. Default locations for different product ersions The different ersions of Network Manager and related components use different directory structures and hae configuration files in different locations. If you are looking for a file or other system component that you expected to find based on the location on your old system, use this table to determine where to find the item on Network Manager V4.1. The location changes are mainly due to changes in the framework oer releases. For example, Network Manager V3.8 uses Tioli Integrated Portal 1.1.x, and Network Manager V3.9 uses Tioli Integrated Portal V2.1. As a reference, the following table contains an oeriew of how the default location of configuration files has changed oer the releases. Table 12. Default locations of configuration files Location in ersion 3.9 and Item Location in ersion 3.8 ersion 4.1 NCHOME /opt/ibm/tioli/netcool /opt/ibm/tioli/netcool ITNMHOME Not applicable /opt/ibm/tioli/netcool/ precision Note: By default, PRECISION_HOME is set to the same location as ITNMHOME, but is used by other parts of the product. TIPHOME /opt/ibm/tioli/tip /opt/ibm/tioli/tip2 GUI properties files TIPHOME/profiles/ TIPProfile/etc/tnm ITNMHOME/profiles/ TIPProfile/etc/tnm Dynamic iew templates Right-click menu and tool definition files GUI icon files WebTools configuration files TIPHOME/profiles/ TIPProfile/etc/tnm/ dynamictemplates TIPHOME/profiles/ TIPProfile/etc/tnm/menus TIPHOME/profiles/ TIPProfile/etc/tnm/tools TIPHOME/profiles/ TIPProfile/etc/tnm/resource TIPHOME/profiles/ TIPProfile/etc/tnm/tools ITNMHOME/profiles/ TIPProfile/etc/tnm/ dynamictemplates ITNMHOME/profiles/ TIPProfile/etc/tnm/menus ITNMHOME/profiles/ TIPProfile/etc/tnm/tools ITNMHOME/profiles/ TIPProfile/etc/tnm/resource ITNMHOME/profiles/ TIPProfile/etc/tnm/tools Chapter 3. Upgrading and migrating 101

116 Migrated files Network Manager is able to migrate a wide range of your customization and configuration changes. The upgrade process migrates both customization and configuration changes made on your preious system. Customization and configuration changes are defined as follows: Customization changes Coding and other deep system modifications that change the way Network Manager processes work. Configuration changes Custom settings for arious Network Manager processes. Customization and configuration changes are held in a ariety of files on your preious system, including the following: Configuration files. These are files with filetype.cfg. Agent definition files. These are files with filetype.agnt. Files that classify network entities. These are files with filetype.aoc. Stitcher files. These are files with filetype.stch. During an upgrade, these files are processed in one of the following ways. Table 13. Handling of files during the upgrade process How file is processed Result User action Automatically imported to the new system. Made aailable for user reiew. Not imported if file already exists on the new system. Not imported to the new system. The file is automatically copied into the appropriate directory on the new system, ready for use. The file is placed in a holding directory on the new system. In most cases, the file will exist on the new system, therefore these files will usually not be imported. File is not aailable on the new system. No user action is required. Backup ersions of the original installed files are saed in the original location and renamed as follows: Any agent *.agnt file: renamed filename.agnt_41file. Any collector *.cfg file: renamed filename.cfg_41file. Any collector *.dr file: renamed filename.dr_41file. During the upgrade procedure you are asked to check these files to determine if they are required on the new system, and if so, whether the user changes must be reimplemented. Examples include files that hae changed due to both modifications in the product across releases and customizations made by users on the preious installation. Important: Files that are made aailable for user reiew are generally incompatible with migration and that their contents should only be migrated if you are certain that the contents of the file will not adersely affect the operation of Network Manager V4.1. If the user changes are required on the new system, then they must be reimplemented in the file that already exists on the new system. Backup ersions of the files that were not imported are saed to the following locations: Any deice class *.aoc file: $NCHOME/precision/aoc/migration Any stitcher *.stch file: $NCHOME/ar/precision/export/disco/ stitchers Any MIB *.mib file: $NCHOME/ar/precision/export/mibs Reasons for this include the following: the file is not typically modified by the user; the file is obsolete on the new ersion of the system. Howeer, in certain cases, the file might be needed on the new system. 102 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

117 Note: Files that are made aailable for user reiew are placed into the following directories: Core changes: Most files are made aailable for user reiew in the following location: $NCHOME/etc/precision/migration Deice class *.aoc files are made aailable for user reiew in the following location: : $NCHOME/precision/aoc/migration GUI changes: $ITNMHOME/profiles/TIPProfiles/etc/tnm/migration. You must reiew and if necessary reimplement user changes in this file, prior to copying it to the correct location on the new system. Note: Domain-specific ersions of all files are automatically imported to the new system, as long as there is no file with an identical filename on the new system. Files containing customization changes The upgrade process migrates certain customization changes made on your preious system. The following sections proide information on the configuration changes that are migrated. Process customization Discoery customization Eent enrichment customization Network Manager GUI customization Serice affected eent plug-in customization Important: Files that are made aailable for user reiew are generally incompatible with migration and that their contents should only be migrated if you are certain that the contents of the file will not adersely affect the operation of Network Manager V4.1. Process customization The following table shows how each process customization file is handled by the upgrade process. All the files listed in the table are in the following directory path: $NCHOME/etc/precision. Table 14. Handling of process customization files File ClassSchema.cfg ConfigAgents.cfg ConfigSchema.cfg CtrlSchema.cfg DbLoginSchema.cfg How this file is handled Not imported if file already exists on the new system. Not imported if file already exists on the new system. Not imported if file already exists on the new system. Not imported if file already exists on the new system. Not imported if file already exists on the new system. Chapter 3. Upgrading and migrating 103

118 Table 14. Handling of process customization files (continued) File How this file is handled NcoConnectionSchema.cfg Not imported if file already exists on the new system. NcoLogin.cfg Not imported if file already exists on the new system. Precision.broker.cfg Not imported if file already exists on the new system. StoreSchema.cfg Not imported if file already exists on the new system. TelnetStackSchema.cfg Not imported if file already exists on the new system. TelnetStackPasswords.cfg Not imported if file already exists on the new system. WebToolSchema.cfg Made aailable for user reiew. Discoery customization Different aspects of the discoery can be customized. Deice classification The following table shows how discoery customization files associated with deice classification are handled by the upgrade process. Table 15. Handling of discoery customization files associated with deice classification File How this file is handled $NCHOME/precision/aoc/* Handled in one of the following ways: If the file already exists on the new system, it is made aailable for reiew in $NCHOME/precision/aoc/migration. If the file does not exist on the new system, it is automatically imported. Discoery agents and stitchers The following table shows how discoery customization files associated with discoery agents and stitchers are handled by the upgrade process. Table 16. Handling of discoery customization files associated with discoery agents and stitchers File How this file is handled $NCHOME/precision/disco/agents/* Each file in the directory is handled in one of the following ways: Made aailable for user reiew, if file already exists on the new system. Automatically imported, if file does not exist on the new system. 104 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

119 Table 16. Handling of discoery customization files associated with discoery agents and stitchers (continued) File How this file is handled $NCHOME/precision/disco/stitchers/* Each file in the directory is handled in one of the following ways: Made aailable for user reiew, if file already exists on the new system. Automatically imported, if file does not exist on the new system. Topology enrichment The following table shows how discoery customization files associated with topology enrichment are handled by the upgrade process. All the files listed in the table are in the following directory path: $NCHOME/etc/ precision. Table 17. Handling of discoery customization files associated with topology enrichment File How this file is handled DbEntityDetails.cfg Made aailable for user reiew. DiscoContrib.cfg Handled in one of the following ways: Made aailable for user reiew, if file already exists on the new system. Automatically imported, if file does not exist on the new system. ModelNcimDb.cfg Made aailable for user reiew. Collectors The following table shows how discoery customization files associated with collectors are handled by the upgrade process. The files listed in this table are in the following directory path: $NCHOME/etc/precision. Table 18. Handling of discoery customization files associated with deice classification File How this file is handled DiscoCollectorFinderSchema.cfg Handled in one of the following ways: Made aailable for user reiew, if file already exists on the new system. Automatically imported, if file does not exist on the new system. DiscoCollectorFinderSeeds.cfg Made aailable for user reiew. $NCHOME/precision/collectors/* Automatically imported to the new system. If a V4.1 ersion of the file exists, it is backed up and named filename_41file. Eent enrichment customization The following table shows how each eent enrichment customization file is handled by the upgrade process. The files listed in this table are in the following directory path: $NCHOME/etc/precision. Chapter 3. Upgrading and migrating 105

120 Table 19. Handling of eent enrichment customization files File How this file is handled EentGatewaySchema.cfg Handled in one of the following ways: Made aailable for user reiew, if file already exists on the new system. Automatically imported, if file does not exist on the new system. NcoGateInserts.cfg Made aailable for user reiew. $NCHOME/precision/eentGateway/ stitchers/* $NCHOME/etc/rules/* $NCHOME/probes/operating_system/ nco_p_ncpmonitor.rules Each file in the directory is handled in one of the following ways: Made aailable for user reiew, if file already exists on the new system. Automatically imported, if file does not exist on the new system. Not imported to the new system. Not imported to the new system. Network Manager GUI customization The following table shows how each GUI customization is handled by the upgrade process. All the files listed in the table are in the following directory path: $ITNMHOME/profiles/TIPProfile/etc/tnm. Note: Table 20. Handling of GUI customization files File autoproision/* dynamictemplates/* menus/* tools/* ncimmetadata.xml resource/* How this file is handled Automatically imported to the new system unless the file exists on the new system. Made aailable for user reiew if the file exists on the new system. Serice affected eent plug-in customization The following table shows how the customization files for the Serice affected eent (SAE) plug-in to the Eent gateway are handled by the upgrade process. All the files listed in the table are in the following directory path: $NCHOME/etc/precision. Table 21. Handling of SAE plug-in customization files File How this file is handled SaeIPPath.cfg Not imported to the new system. SaeItnmSerice.cfg Not imported to the new system. SaeMplsVpn.cfg Not imported to the new system. SAESchema.cfg Not imported to the new system. 106 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

121 Files containing configuration changes The upgrade process migrates certain configuration changes made on your preious system. Use this information to understand which configuration changes are migrated automatically and which require manual interention. The following sections proide information on the configuration changes that are migrated. Process configuration Discoery configuration DLA configuration Polling configuration Network Manager GUI configuration Root-cause analysis configuration Important: Files that are made aailable for user reiew are generally incompatible with migration and that their contents should only be migrated if you are certain that the contents of the file will not adersely affect the operation of Network Manager V4.1. Process configuration The following table shows how each process configuration file is handled by the upgrade process. All the files listed in the table are in the following directory path: $NCHOME/etc/precision. Table 22. Handling of discoery configuration files File How this file is handled ConfigItnm.cfg Not imported if file already exists on the new system. CtrlSerices.cfg Made aailable for user reiew. DbLogins.cfg Not imported. Howeer, the upgrade process creates domain-specific DbLogins.cfg files on the new system to match domains exported from the preious system. You must edit these files to point to the new database on the target system. MibDbLogin.cfg Not imported. ModelSchema.cfg Not imported if file already exists on the new system. NcPollerSchema.cfg Not imported if file already exists on the new system. SericeData.cfg Not imported. SnmpStackSchema.cfg Not imported if file already exists on the new system. TrapMuxSchema.cfg Not imported if file already exists on the new system. VirtualDomainSchema.cfg Not imported if file already exists on the new system. Chapter 3. Upgrading and migrating 107

122 Discoery configuration The following table shows how each discoery configuration file is handled by the upgrade process. Some of the files in this table are processed in the following way: "Processed with ncp_config to generate domain-specific inserts." ncp_config is the Network Manager GUI configuration file serer and its function is to read from and write to schema files. In order to handle certain files the migration script calls ncp_config to read the schema configuration file and generate the corresponding insert configuration file. For example, ncp_config is called to read the file DiscoPingFinderSchema generate domain-specific ersions of the DiscoPingFinderSeeds.cfg insert file. The files listed in the table are in the following directory path: $NCHOME/etc/precision. Table 23. Handling of discoery configuration files File How this file is handled DiscoAgents.cfg Made aailable for user reiew. DiscoARPHelperSchema.cfg Not imported if file already exists on the new system. DiscoConfig.cfg Made aailable for user reiew. DiscoDNSHelperSchema.cfg Not imported if file already exists on the new system. DiscoFileFinderParseRules.cfg Processed with ncp_config to generate domain-specific inserts. DiscoFileFinderSchema.cfg Processed with ncp_config to generate domain-specific inserts. DiscoHelperSererSchema.cfg Processed with ncp_config to generate domain-specific inserts. DiscoPingFinderSchema.cfg Processed with ncp_config to generate domain-specific inserts. DiscoPingFinderSeeds.cfg Processed with ncp_config to generate domain-specific inserts. DiscoPingHelperSchema.cfg Processed with ncp_config to generate domain-specific inserts. DiscoSchema.cfg Made aailable for user reiew. DiscoScope.cfg Migrating from V3.9 and later ersions: automatically imported to the new system Migrating from V3.8: made aailable for user reiew. DiscoSnmpHelperSchema.cfg Not imported if file already exists on the new system. DiscoTelnetHelperSchema.cfg Not imported if file already exists on the new system. DiscoXmlRpcHelperSchema.cfg Made aailable for user reiew. NATGateways.txt Made aailable for user reiew. NATTranslations.txt Made aailable for user reiew. 108 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

123 Table 23. Handling of discoery configuration files (continued) File How this file is handled $NCHOME/precision/mibs/* Not imported if file already exists on the new system. SnmpStackSecurityInfo.cfg Processed with ncp_config to generate domain-specific inserts with encrypted passwords. TelnetStackPasswords.cfg Processed with ncp_config to generate domain-specific inserts with encrypted passwords. DLA configuration The following table shows how each DLA configuration file is handled by the upgrade process. Table 24. Handling of DLA configuration files File $NCHOME/precision/adapters/ncp_dla/ ncp_dla.properties* How this file is handled Automatically imported to the new system. Polling configuration The following table shows how each polling configuration file is handled by the upgrade process. Table 25. Handling of polling configuration files Files How this file is handled $NCHOME/ar/precision/ MonitorPolicies*.xml These domain specific files are exported and used during the import process to populate the Polling engine (ncp_poller) tables with poll policies and poll definitions. Network Manager GUI configuration The following table shows how each Network Manager GUI configuration configuration file is handled by the upgrade process. Note: All the files listed in the table are in the following directory path: $ITNMHOME/profiles/TIPProfile/etc/tnm. Chapter 3. Upgrading and migrating 109

124 Table 26. Handling of GUI configuration files File discoconfig.properties discofilterlibrary.xml discofilters.xml itnmgraphdefault.properties itnmgraph.properties monitorconfig.properties ncpolldata.properties nmdb.properties status.properties structurebrowser.properties tnm.properties topoiz.properties How this file is handled Automatically imported to the new system unless the file exists on the new system. Made aailable for user reiew if the file exists on the new system. Root-cause analysis configuration The following table shows how each root-cause analysis (RCA) configuration file is handled by the upgrade process. Table 27. Handling of RCA configuration files File $NCHOME/etc/precision/RCASchema.cfg How this file is handled Not imported if file already exists on the new system. Upgrading and migrating to latest Network Manager You can upgrade to Network Manager V4.1 from ersions 3.8 or 3.9. Upgrading and migrating to the latest ersion of Network Manager inoles collecting data from your existing Network Manager installation, exporting the data, installing the new ersion of Network Manager, and importing the data to your new installation. Note: You must run the export-import scripts as the same user that installed the product. Upgrading to latest Network Manager: full side-by-side migration Follow this procedure to fully migrate all of the serers in your installation to new serers. 110 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

125 Upgrading and migrating oeriew Use this information as a step-by-step guide to upgrading Network Manager and migrating existing settings to the upgraded ersion. Upgrading and migrating steps Moing to the latest ersion of Network Manager inoles seeral steps. The process uses separate scripts for moing the core and the GUI component settings across to the new installation. To upgrade to Network Manager V4.1 from V3.8 or V3.9 and migrate your settings and customizations, perform the steps listed in the following table. Table 28. Upgrading and migrating tasks to Network Manager V4.1. Action 1. Install Network Manager Chapter 2, Installing, on page 41 V Install IBM Tioli Netcool/OMNIbus 3. Prepare your existing system. 4. Export core customization data. 5. Export GUI configuration data. 6. Identify NCIM topology database customizations 7. Apply customizations from the source NCIM topology database 8. Import preious core configuration data into your new installation. 9. Due to changes in the product, some core configuration settings must be migrated manually to the new system. 10. Import preious GUI configuration data into your new installation Step You can install IBM Tioli Netcool/OMNIbus as part of your Network Manager installation. For information about upgrading and migrating IBM Tioli Netcool/OMNIbus, see the IBM Tioli Netcool/OMNIbus Installation and Deployment Guide. Note: If you installed a new instance of IBM Tioli Netcool/OMNIbus as part of the Network Manager installation, the ObjectSerer name you proided during the installation is stored in NCHOME/etc/precision/ ConfigItnm.Network_Manager_Domain_Name.cfg Preparing for upgrade on page 112 Exporting core customization data on page 114 Exporting GUI customization data on page 115 Identifying NCIM topology database customizations on page 117 Applying customizations from the source database on page 118 Importing core customization data on page 119 Note: Any configuration files exported from your preious V3.8 installation and imported into Network Manager V3.9 that contain passwords or other strings originally encrypted using V3.8 encryption tools, will be reencrypted using FIPS compliant encryption tools as part of this upgrade. Version 3.9 files that are replaced by migrated V3.8 files during the update process are backed up with the name filename_39, where filename is the name of the original ersion 3.9 file. Importing core customization data - manual steps on page 122 Importing GUI customization data on page 130 Chapter 3. Upgrading and migrating 111

126 Table 28. Upgrading and migrating tasks to Network Manager V4.1. (continued) Action Step 11. Due to changes in the Importing GUI customization data - manual steps on page 132 product, some GUI configuration settings must be migrated manually to the new system. 12. Stop and start Network Manager, including the Tioli Integrated Portal. Starting and stopping Network Manager On your new installation, perform the following steps for each desired network domain. 13. Run a network For more information, see the IBM Tioli Network Manager IP Edition Discoery Guide. discoery. 14. Reapply manually Reapplying manually created topology to your discoered topology on page 134 created topology to your discoered topology. 15. Reapply managed status data to your discoered topology. Reapplying managed status data to your discoered topology on page 137 Preparing for upgrade Prepare your existing system for upgrade by copying oer the files required for the upgrading and migrating process. The Network Manager installation package contains all files required. Once you hae installed Network Manager V4.1 on your target machine and before proceeding with the upgrade, you must recreate all users from your preious installation on the target machine, in the appropriate repository (LDAP or ObjectSerer). Users created using Tioli Integrated Portal must also be created again. Prepare for the upgrade: 1. Go to the system where you installed the Web Applications (also referred to in the documentation as "GUI components") for Network Manager V4.1. In a single serer installation, this is the serer where you installed Network Manager V4.1. In a distributed installation, this is the Tioli Integrated Portal serer. 2. Optional: If you hae installed fixpacks for third-party GUI packages, such as Tioli Integrated Portal and Web GUI, and you want to these fix packs in the migrated package, then run the UpdatePlugins script on the system where you installed the Network Manager V4.1 Web Applications (this is required because the script uses TIPHOME): a. Go to the following location: $NCHOME/precision/install/scripts/. b. Run the following command:./updateplugins This script gathers together all of the latest upgrade packages. The UpdatePlugins script is run by default at installation time, and writes log messages to $NCHOME/log/install/Configuration.log in a section called Update Migration plugins. Howeer, the script must be run again if a Tioli Integrated Portal or Web GUI fixpack is subsequently installed. This enables the system to 112 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

127 gather the latest upgrade packages. The script produces the ExportPackage.tar archie package as output. The ExportPackage.tar archie is saed in $NCHOME/precision/install/data. Note: For the purposes of upgrade from a Network Manager V3.8 enironment (Tioli Integrated Portal 1.x), the ExportPackage.tar archie includes an archie called Preupgrade.tar. 3. Locate the following file: $NCHOME/precision/install/data/ExportPackage.tar. 4. Copy the compressed file to your existing Network Manager installation. If you hae core and GUI components on more than one serer, then copy the file to each of them. 5. Extract the file to a temporary location. Note: The temporary location must be a directory that is not the Netcool home directory $NCHOME and is not a subdirectory of $NCHOME. The files and utilities required for the upgrading and migrating process are aailable after extracting the compressed file. The main items that require attention are as follows: The launchpad utility: Use this utility to start the launchpad GUI from where you can run a data collection on your preious installation. The data collected then can be exported for applying to new installations. An import utility is also proided for use on your new installation. You can use a GUI or command line to start and use this utility. Note: You can use the export utility to collect data on Network Manager ersions 3.8, or 3.9 installations. The Preupgrade.tar: Contains utilities for exporting preious GUI settings on Network Manager V3.8 and then importing them into your new installation. Note: This file is only needed for the export-import of V3.8 GUI component data. 6. Ensure that poll policy names and poll definition names are unique. In preious releases of Network Manager, a known limitation allowed duplicate poll policy names or duplicate poll definition names to be created. In Network Manager V4.1, duplicate poll policy names or poll definition names are not allowed. If you hae created poll policies or poll definitions with the same name on your preious V3.8 installation, then you must rename one of each duplicate pair to make sure that each poll policy and each poll definition name is unique on your system. You must do this before performing any data export. Note: The poller must be running when you perform the rename operation. This is required for the names to be propagated appropriately to database fields requiring this information (for example, historical poll data when migrating from a V3.8 system). Chapter 3. Upgrading and migrating 113

128 Exporting core customization data You must collect and export your preious ersion's core customization data to make it aailable for importing to your Network Manager V4.1 installation. To use the launchpad, you need a supported browser installed on the serer. Make sure you hae copied the UNIX ExportPackage.tar file from the Network Manager V4.1 installation package to each serer where your existing Network Manager installation has components. Note: The upgrade process does not migrate discoered topology between ersions. It does, howeer, migrate the discoery configuration files from your preious installation. Once you hae completed the upgrade process, run a new discoery to populate the NCIM database with topology data. To export core customization data, perform the following steps: 1. On each serer where components of your preious ersion are installed, go to where you extracted ExportPackage, and run the data export script: To run the script from the installer launchpad, start the launchpad by running the UNIX launchpad.sh script on UNIX, select the Preinstallation and Migration menu item, expand the Upgrading from an existing Network Manager section, and click Export Network Manager Data. To run the script from the command line, run the UNIX nmexport script on UNIX from the scripts subdirectory. Note: You must run the script as the same user that installed the product. Restriction: The script does not export historical polling data. 2. Proide the answers to the prompts. Depending on the ersion of your preious Network Manager installation, the following data is extracted and saed into an export file in a location of your choice (.pkg on UNIX systems): Discoery configuration data Network iews Poll policies and poll definitions. Note: Only core component data is collected. To collect GUI component data, you must run another script, as described in Exporting GUI customization data on page 115. Note: The export process creates its own log files. If successful, all related log files are bundled into the.pkg export package file, making them aailable on the updated system. If the process fails, the package is not created and the logs are saed to the user's home directory: $HOME/itnmExportLogs. 3. If you are installing Network Manager V4.1 on a different serer, copy all the exported data to that serer, or serers, making the data aailable for importing to the new systems. 4. If you are also exporting Netcool/OMNIbus customization data, copy all the exported data to the serer where you want to install Netcool/OMNIbus. Related reference: Supported browsers for the installer launchpad on page 36 To run the installer launchpad, you must hae a supported browser installed. 114 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

129 Exporting GUI customization data Run the GUI export script to export your preious ersion's GUI customization data. To use the launchpad, you need a supported browser installed on the serer. Make sure you hae copied the UNIX ExportPackage.tar file from the Network Manager V4.1 installation package to the serer where your existing GUI components are installed. Only GUI customization data for the Network Manager GUI is migrated. Customization data for the other GUI components, Web GUI and Tioli Common Reporting, is not migrated. Consult Web GUI and Tioli Common Reporting information centers for instructions on migrating those GUI components. Important: If you are upgrading from Network Manager V3.8, then you must perform the following steps to exclude the migration of third-party GUI components, such as Web GUI and Tioli Common Reporting: 1. On your Network Manager V3.8 system, edit the following file: $TIPHOME/profiles/TIPProfile/upgrade/plugins/ITNM.properties 2. In the ITNM.properties file, find the line that reads: # components included in this product The line that follows lists the GUI components that, in addition to the Network Manager GUI, will be exported by the GUI export script. 3. Update this line so that it contains no components. This ensures that no third-party components are migrated. 4. Sae the ITNM.properties file. To export GUI customization data, perform the following steps: 1. On each serer where GUI components of your preious system are installed, go to where you extracted ExportPackage. 2. Optional: If you are migrating from Network Manager V3.8, extract the UNIX Preupgrade.tar file to TIPHOME/profiles/TIPProfile. For example, on UNIX systems, type tar -xof Preupgrade.tar -C $TIPHOME/profiles/ TIPProfile. 3. Run the GUI data export script: To run the script from the installer launchpad, start the launchpad by running the UNIX launchpad.sh script on UNIX, select the Preinstallation and Migration menu item, expand the Upgrading from an existing Network Manager section, and click Export Network Manager GUI Data. To run the script from the command line, change to the scripts subdirectory of the location where you extracted ExportPackage and run the UNIX nmguiexport: nmguiexport -u TIP_admin -p TIP_pass -d TIP_location -n netcool_location [-owebgui_location ] Where: TIP_admin is the Tioli Integrated Portal administrator user name. TIP_pass is the Tioli Integrated Portal administrator password. TIP_location is the location of the Tioli Integrated Portal installation to be migrated. netcool_location is the location of the Netcool home directory. Chapter 3. Upgrading and migrating 115

130 webgui_location is the location of the Web GUI home directory. Note: This alue is optional. If no alue is proided, then the script uses a default alue of $NCHOME/omnibus_webgui. Note: If no alues are proided, you are prompted to enter alues. If the directory locations listed in the table below are not proided, then the enironment ariables shown in the table are used. In all cases, if the enironment ariable does not exist, then you are prompted to enter a location. Table 29. Directory locations required by script Directory location Location of the Tioli Integrated Portal installation to be migrated Netcool home directory Location of the Tioli Netcool/OMNIbus Web GUI home directory Enironment ariable $TIPHOME $NCHOME $NCHOME/omnibus_webgui Note: You must run the script as the same user that installed the product. The following data is extracted and saed into the TIPHOME/profiles/ TIPProfile/upgrade/data/upgradeData.zip export file: User roles: The export saes the roles for users that existed in your source system, and applies the roles to the same user if the same user exists in V4.1. Note: Actual users defined for the V4.1 enironment need to be created separately in the appropriate repository (LDAP or ObjectSerer). Users created using Tioli Integrated Portal must also be created again. Custom Tioli Integrated Portal Pages, Views, and Roles. The export process creates its own log files in the following directories: TIPHOME/profiles/TIPProfile/upgrade/logs TIPHOME/profiles/TIPProfile/logs 4. If you are installing Network Manager V4.1 GUI components on a different serer, copy the upgradedata.zip export file to that serer, making the data aailable for importing to the new system. If you are installing on separate serers, make sure you copy the releant data to the serer where you want to install the component. 116 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

131 Related reference: Harmless upgrade error messages on page 149 The following error messages might appear during the upgrade but can be ignored. Not all GUI components were exported on page 149 During export of GUI component data, if customization data for any of the GUI components was not correctly exported then a warning is displayed. Supported operating systems on page 32 Network Manager is supported on the following operating systems. Related information: Tioli Netcool/OMNIbus Web GUI V7.4 Information Center: Upgrading and migrating Click here for instructions on upgrading toweb GUI 7.4. Tioli Netcool/OMNIbus Web GUI V7.3.1 Information Center: Upgrading and migrating Click here for instructions on upgrading to Web GUI Tioli Common Reporting Information Center: Upgrading Click here for instructions on upgrading to Tioli Common Reporting Identifying NCIM topology database customizations The upgrade scripts do not migrate customizations made to the NCIM topology database schema. Howeer, Network Manager proides a tool to identify customizations you made on the NCIM topology database on your source Network Manager installation, so that you can recreate them in the database of the target installation. To migrate NCIM customizations, you must first use the ncp_ncim_diff.pl script to identify the differences between the NCIM topology database schema on your source installation and the default NCIM topology database schema on the source installation. These differences correspond to the cutomizations made to the NCIM topology database schema on your source system. Once the target installation is installed, you can then reiew the new V4.1 schema and manually update the new NCIM topology database schema with these modifications. To compare the topology database schemas: 1. Log in to your source Network Manager installation. 2. Perform the following steps: If you are migrating from V3.9: a. Change to the following directory: $NCHOME/precision/scripts/perl/ scripts b. Run the following command:./ncp_ncim_diff.pl -domain DOMAIN -password NCIM_database_password If you are migrating from V3.8: a. Change to the following directory: ExportPackage_location/ncim Where ExportPackage_location is the location where you extracted the ExportPackage.tar archie. b. Run the following command:./ncp_db2_ncim_diff.pl -domain DOMAIN -password NCIM_database_password -file ExportPackage_location/ncimOeriew-ITNMIP3.8-FP6.xml Where: Chapter 3. Upgrading and migrating 117

132 DOMAIN is the name of your source Network Manager installation's domain whose NCIM structure you want to compare to the default schema on the source installation. Ensure that the DbLogins.DOMAIN.cfg configuration file from your source installation is aailable so that the script has all the data it needs to connect to the source database. ExportPackage_location//ncimOeriew-ITNMIP3.8-FP6.xml is the path to the XML format file which describes the default structure of the NCIM database for the ersion and fixpack of your source system. This file can be found at the location where you extracted the ExportPackage.tar archie. Note: This XML file only needs to be explicitly specified if you are migrating from V3.8. The following is an example of the output of the command for a domain named NCOMS. 67 NCIM tables and iews found in Domain NCOMS 66 NCIM tables and iews found in Default NCIM structure for ITNM 3.9 ********************************************************** Additional elements in Domain NCOMS Table CUSTOM ********************************************************** 1 differences found between Domain NCOMS and Default NCIM structure for ITNM 3.9 For more information on the ncp_ncim_diff.pl Perl script see IBM Tioli Network Manager IP Edition Administration Guide. Related tasks: Setting up a topology database on page 44 You must configure an existing database or install and configure a new one to use as the topology database for Network Manager. Applying customizations from the source database If you hae customized the NCIM database, you must manually update the new NCIM topology database schema with any customizations made. You must install the new database and run the Network Manager create database schema scripts to set up the tables and schemas. Before you run the ncp_ncim_diff.pl script, make sure that the DbLogins.DOMAIN.cfg files from the preious installation is aailable. The DbLogins.DOMAIN.cfg file contains the options for connecting to your NCIM database. Note: The migration process combined with a new discoery of the network populates the database. You only need to run ncp_ncim_diff.pl script if you hae customized changes in your source database. You ran the ncp_ncim_diff.pl script to identify customizations on the source system's NCIM database as part of the task: Identifying NCIM topology database customizations on page 117. You must now manually apply these customizations to the NCIM topology database on the target system. 118 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

133 1. Log in to your target Network Manager installation. 2. Examine the default NCIM schema on the target Network Manager installation. There might hae been changes to the schema introduced between ersions. For example, the default NCIM schema on Network Manager V4.1 has changed significantly from the default NCIM schema on Network Manager V3.9. If there hae been changes between ersions then you must take care when applying customizations to the new NCIM schema as table names and field names might hae changed. For more information on the default Network Manager V4.1 NCIM topology database schema see the IBM Tioli Network Manager IP Edition Discoery Guide. 3. Manually update the new NCIM topology database schema with the customizations reported by the script ncp_ncim_diff.pl in the task Identifying NCIM topology database customizations on page 117. Recreating custom pollers If custom pollers were configured on your preious system, then you must recreate these pollers manually on the target system before proceeding with the import. This ensures that all migrated poll policies are mapped to the correct poller. If the custom pollers are not present on the target system during the migration process, then the migrated poll policies will be mapped to the default poller and you would hae to fix all the mappings following the migration. Note: If you need to recreate custom pollers on a non-default domain, then this domain will not yet exist on the target system. In this case first create the releant domain and then add the custom poller to this domain. For information on how to create custom pollers, see IBM Tioli Network Manager IP Edition Eent Management Guide. Importing core customization data You can now import your preious ersion's core customization data. Before you can import core customization data, you must export the data from your preious installation and install ersion 4.1. Important: You must run ncp_mib if you hae copied oer custom MIBs as part of this data migration. If you do not do this then processes such as the SNMP helper, ncp_dh_snmp, will not start up when you start Network Manager. To import core customization data, perform the following tasks: 1. Log in to your preious installation as the same user that installed Network Manager. If you had a distributed setup, you must log in to each serer containing components of your preious installation and repeat the following steps for each serer. 2. Copy the export file (.pkg on UNIX systems) to the serer where you installed Network Manager V4.1. You might hae more than one export file depending on whether you had a distributed enironment. 3. On your new installation, make sure that the Network Manager core components for each domain are running. To do this, use the following command on UNIX systems: itnm_start ncp -domain DOMAIN. For example, to start the NCOMS domain, type: itnm_start ncp -domain NCOMS. This ensures that Network Manager is fully initialized and the domain tables are populated. You must stop the core components again to do the import itself, as described in the next step. Chapter 3. Upgrading and migrating 119

134 4. Stop the Network Manager core components for each domain on your new installation using the following command on UNIX systems: itnm_stop ncp -domain DOMAIN. For example, to stop the NCOMS domain, type: itnm_stop ncp -domain NCOMS Note: If you do not specify a domain name with itnm_stop, it stops the default domain created at installation. 5. On your new installation, go to the location $NCHOME/precision/install/data/ and extract the package ExportPackage.tar. 6. Run the data import script using one of the following methods: To run the script from the installer launchpad, start the launchpad by running the UNIX launchpad.sh script on UNIX, select the Postinstallation menu item, expand the Upgrading from an existing Network Manager section, and click Import Network Manager Data. Note: The launchpad can be found in the directory where you extracted the Network Manager installation package. To run the script from the command line, run the UNIX nmimport script on UNIX from the scripts subdirectory. Note: You must run the script as the same user that installed the product. 7. When prompted, proide the path to the.pkg or.zip file that contains the customization data that you preiously exported. 8. Answer the arious other questions the import process asks. Note: The following question requires special attention: Allocate new entityids during import [N] Each deice in the system has an entityid. The import process can allocate new entityids or presere the existing entityids. Presering the existing entityids is necessary when you hae links to external systems that use Network Manager data, for example, Tioli Data Warehouse. Howeer, to presere existing entityids, the target system needs to be empty. If the target system is not empty (for example, due to a preious data import or discoery), presering entityids might become a complex operation due to potential clashes between existing entityids and the entityids being imported, and the results may be unpredictable. Therefore, merging of domain data is not supported. Attention: If you hae a domain on the target system that has the same name as on your preious system, then make sure the domain on the target system does not contain data. Domain names cannot be changed during the migration process. Answer N[o] to this question to presere entityids ory[es] to allocate new entityids. If you answer N[o], then the data import script performs a check to determine whether entity data already exists in the database. Data will exist in the database in the case of a preious data import or discoery. If the check determines that entity data already exists in the database, then the script aborts with the message: System has entity data. Aborting. 120 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

135 If this happens, rerun the data import script and answer Y[es] to this question. This will ensure that new entityids are allocated. If the check determines that no entity data exists in the database, then each deice in the new installation maintains the entityid from the preious installation. If you answer Y[es], then deices are allocated new entityids. The exported data is imported into the new installation. Your passwords are unencrypted, imported, and re-encrypted. Important: Core component data is imported, while GUI component data is imported as part of the process described in Importing GUI data. The import process creates its own log files. Logs from the import process are saed to NCHOME/log/precision: ITNMDataImport.log ITNMImportHistoricalData.log get_policies.domain name.log ITNMImportNetworkViews.log The export-import process automatically detects and recreates the domains from a preious install. The import script detects the potential domains from the preious system based on the data files. Using the domain_create.pl script, the process automatically creates domains on the new installation using the domain names from the preious system. After the domains hae been created, the main topology and policy data are imported for each. The domain_create.pl script creates the discoery configuration files for the new domains in NCHOME/etc/precision using the alues in the configuration files of the default domain. The import process saes the imported files in the NCHOME/etc/precision/migration directory as read-only files. You can use the imported files to manually update the newly created files in NCHOME/etc/precision. Attention: You might receie warning messages referencing deprecated data types. These warning messages indicate planned changes in data types between releases and can be ignored. The following is an example: Leel: INFO Message: ncp_config command:- "/opt/ibm/tioli/netcool/ precision/bin/ncp_config" -domain CC -read_schemas_from "/opt/ibm/tioli/netcool/ar/precision/export/importpending" -write_schemas_to "/opt/ibm/tioli/netcool/etc/precision" -schema DiscoCollectorFinderSchema.cfg Sun Oct 3 05:48: Warning: A generic non-fatal error has occurred found in file RiOQL.y at line Deprecated type 'long' in OQL statement will be ealuated as type 'time' After importing your preious system data, you might need to perform manual settings on the new system. The export-import process proides guidance on what files require attention and manual editing to fully complete the upgrading and migrating process. Chapter 3. Upgrading and migrating 121

136 Importing core customization data - manual steps Some core customization data must be migrated manually. Migrating certain core configuration settings: Due to changes in the product and potential user customizations, you must manually migrate certain core configuration settings to the new system. Make sure you hae performed a data collection and export on your preious system and hae imported the data to your new installation. To perform manual migration steps: 1. Log in to your new installation. 2. Reiew the NCHOME/log/precision/ITNMCompareSystemsFinal.txt log file for information on what manual changes might be required. This log lists the file changes between the preious and new system, as described in the following table. Note: The following table highlights those files where editing changes are required; for example, where both the system and the user hae modified the file, and hence customizations will need to be reapplied to the file. Howeer, it is best practice to reiew all user modifications to check that these hae been copied across correctly to the new system. In the table below, the following tagging is used. All file comparisons are performed using checksum operations: Different Following installation and execution of the migration scripts, the file present on the target system is different to the file present on the source system. Same System User Table 30. File tagging within ITNMCompareSystemsFinal.txt Following installation and execution of the migration scripts, the file present on the target system is the same as the file present on the source system. The default ersion of the file on the target system is different to the default ersion of the file on the source system. On the source system, the file present is different to the default ersion of the same file. Type of file change Files that hae changed due to both modifications in the product across releases and customizations users hae made on the preious installation. Example of file tagging in ITNMCompareSystemsFinal.txt Action required? Action Different,User,System,etc/precision/CtrlSerices.cfg Yes Reiew these files. Any user customizations need to be reiewed and applied again manually. 122 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

137 Table 30. File tagging within ITNMCompareSystemsFinal.txt (continued) Type of file change Example of file tagging in ITNMCompareSystemsFinal.txt Action required? Action Files that hae changed due to customizations users hae made on the Different,User,,etc/precision/DbLogins.AUTO.cfg Some files are tagged this way due to the installation or migration process. For example: Yes Reiew these files. Any user customizations need to be preious installation. In addition following installation and execution of the DbLogins.*.cfg and ModelNcimDb.*.cfg files: Following the the V4.1 installation procedure these files are expected to hae different database setting alues from settings in the corresponding file on the source system. reiewed and applied again manually. migration scripts, the SnmpStackSecurityInfo.*.cfg and TelnetStackPasswords.*.cfg file present on the files: As these files contain passwords, the passwords target system is would hae been deencrypted as part of the export process, different to the file and reencrypted as part of the import process. Best practice present on the source is to recreate the releant passwords on Network Manager system. V4.1 and then encrypt them. This might be a system file from the preious release that was remoed from the target system during the V4.1 installation process. Files that existed on the old system, but that hae not been migrated to the new system. Files that hae changed only due to modifications within the product from one release to the next User modified files. These files hae been migrated. Files that hae not changed. Files that did not exist on the preious system, but exist on the new installation. Same,,System, precision/aoc/bntvirtualfabricswitch.aoc Yes Reiew these files. If this is a alid file then copy it to the releant directory on the target system. Potentially Obsolete,,,etc/precision/AmosSchema.cfg Note: Files tagged Potentially Obsolete require your attention: These files include customized discoery stitcher files, discoery agent files, and MIB files, which are not supported by the upgrade procedure, and are consequently not imported. If you require these customizations, then you will need to implement them again later on your new system. Files tagged Potentially Obsolete that are not discoery stitcher files, discoery agent files, or MIB files might require manual migration at this point. Check the ITNMDataImport.log for help in determining whether a file marked Potentially Obsolete requires manual migration. Different,,System,precision/aoc/ CiscoNonRoutingSwitch.aoc Yes No Reiew these files. Files with this tag that are not discoery stitcher files, discoery agent files, or MIB files, might require manual migration. File change is listed for information only. Same,User,, etc/precision/discoscope.auto.cfg No File change is listed for information only. Same,,,etc/precision/ClassSchema.cfg No File change is listed for information only. New,,,etc/precision/DiscoDNSHelperSchema.NCOMS.cfg No File change is listed for information only. Chapter 3. Upgrading and migrating 123

138 Table 31. Archied files and their locations Note: There are three CompareSystems files: ITNMCompareSystemsTgt.log ITNMCompareSystemsFinal.log ITNMCompareSystemsFinal.txt The first two are work files and you can ignore them. The one that requires attention is only the third one, ITNMCompareSystemsFinal.txt, as described aboe. Tip: For a detailed report on the export-import migration process, see $NCHOME/log/precision/ITNMDataImport.log. This file is for debugging and support purposes. 3. Files from the preious installation that might require manual adjustments are archied to the locations show in the table below. Based on information in the ITNMCompareSystemsFinal.txt file, inspect and adjust settings in the following archied files as necessary: File Any deice class *.aoc file. Any stitcher *.stch file. Any MIB *.mib file. Location Archied to: $NCHOME/precision/aoc/ migration Archied to: $NCHOME/ar/precision/export/ disco/stitchers Archied to: $NCHOME/ar/precision/export/ mibs 124 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

139 Table 31. Archied files and their locations (continued) File SnmpStackSecurityInfo.DOMAIN.cfg TelnetStackPasswords.DOMAIN.cfg ModelNcimDb.DOMAIN.cfg CtrlSerices.DOMAIN.cfg Note: If you hae migrated CtrlSerices.DOMAIN.cfg files that were used to configure failoer, there might be a conflict between the -primarydomain, -backupdomain, -irtualdomain, -backup, and -serer command-line options in the CtrlSerices.DOMAIN.cfg file, and the settings in the ConfigItnm.DOMAIN.cfg file. The command-line options in the CtrlSerices.DOMAIN.cfg file take precedence, by default, and a warning will be logged. You can disable usage of a migrated CtrlSerices.DOMAIN.cfg file by renaming it (for example, to CtrlSerices.OLD.cfg), which causes the system to default to using the CtrlSerices.cfg file. If your migrated CtrlSerices.DOMAIN.cfg file contains other customized settings for the defined processes (for example, -latency and -debug), you will need to reconfigure these settings in the default CtrlSerices.cfg file. NcoGateInserts.DOMAIN.cfg NcoGateSchema.DOMAIN.cfg VirtualDomainSchema.DOMAIN.cfg DbEntityDetails.cfg Note: You must also recreate any new NCIM tables. DiscoCollectorFinderSeeds.DOMAIN.cfg DiscoFileFinderParseRules.DOMAIN.cfg DiscoPingFinderSeeds.DOMAIN.cfg DiscoScope.DOMAIN.cfg Note: If you are migrating from V3.8 then note that the DiscoSchema.DOMAIN.cfg was split into two files in Network Manager V3.9 and this remains the same in Network Manager V4.1. The insert statements in this file were moed to the new DiscoScope.DOMAIN.cfg file. This proides a way of separating any user customizations from the fixed schema definitions. Location All files archied to: $NCHOME/etc/precision/ migration 4. After you hae edited the files and hae made the necessary modifications, copy the files to the releant location listed below: Any deice class *.aoc file: $NCHOME/precision/aoc/ Any stitcher *.stch file: $NCHOME/precision/disco/stitchers/ Any MIB *.mib file: $NCHOME/precision/mibs/ Any of the.cfg files listed in Table 31 on page 124: $NCHOME/etc/precision If you are migrating from V3.8 then depending on your preious system setup, you might need to perform further manual tasks like adjusting multiple domain settings, copying DLA properties, manually applying poll and report settings, or reiewing eent management settings and understanding the changes in the way eent enrichment and correlation works in Network Manager V4.1. Chapter 3. Upgrading and migrating 125

140 Adding changes to the discoery database schema: The discoery schema has changed in Network Manager V4.1. You must make these changes manually. The following changes were made: In the workingentities database defined in DiscoSchema.cfg, a new table was added, named workingentities.interfacemapping. In the translations database defined in DiscoSchema.cfg, a new field m_name was added to the translations.iptobasename table. You must add these changes manually to each domain specific DiscoSchema.DOMAIN.cfg file. All DiscoSchema.DOMAIN.cfg files from the preious installation are archied to NCHOME/etc/precision/migration. You must then copy these configuration files to the parent directory, prior to restarting domains. Important:. To add these changes, perform the following steps for each domain-specific DiscoSchema.DOMAIN.cfg file in the NCHOME/etc/precision/migration directory. 1. Add the new workingentities.interfacemapping table by copying the following SQL statement to the correct location in the file: create table workingentities.interfacemapping ( m_name text not null, // Unique name of an interface //on the network m_ifindex int, // SNMP ifindex m_interfaceid text, // Interface identifier m_entphysindex int, // Entity MIB physical // Index if present m_entphysname text, // Physical name to be populated // in place of m_entphysindex for // those entities represented by // non-entity-mib style data m_ifdescr text, // Interfaces RFC ifdescr m_ifname text, // Interfaces RFC ifname m_ifalias text, // Interfaces RFC ifalias field m_iftype int, // Interfaces RFC iftype m_physaddress text, // The MAC address for // this entity if present m_basename text not null, // The name of the "Base // Entity" for this deice m_addressspace text // The name of the address // space this deice is on // for public it is simply // null. ); create index we_interface_index on workingentities.interfacemapping ( m_name, m_physaddress, m_basename, m_ifdescr, m_ifname, m_ifalias ); 2. Add the new m_name field to the translations.iptobasename table within a domain specific DiscoSchema.DOMAIN.cfg file, perform the following steps: 126 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

141 a. Add the following field definition to the create table statement for the translations.iptobasename table: m_name text // Name of interface with IP // if known b. Update the create index statement to the translations.iptobasename table so that it reads as follows: create index translations_iptobasename_index on translations.iptobasename ( m_basename, m_baseaddress, m_workaddress, m_protocol, m_ipaddress, m_ismanagementip, m_isoutofband, m_name); After you hae finished importing configuration data and reconciling customizations manually, make sure you start your domains before using Network Manager. The default domain specified at installation is started when starting Network Manager, but if you hae multiple domains, then start each using the itnm_start ncp -domain DOMAIN command. Migrating DLA properties: If you use the Discoery Library Adapter (DLA) to collect data on network resources and hae DLA properties files that you set up on your preious system, the settings need to be migrated manually. To migrate DLA settings: 1. Log in to your new installation. 2. Go to NCHOME/ar/precision/export and locate the DLA properties files the export-import process archied on your preious system and copied oer. Each domain has an ncp_dla.properties.domain name file archied by the export-import process. 3. Use the archied DLA properties files for each domain to recreate the same DLA settings on your new installation: a. Go to NCHOME/precision/adapters/ncp_dla. b. Using the preconfigured ncp_dla.properties file, create an equialent DLA properties file based on each preious domain's DLA file, naming the files after each domain, for example, ncp_dla.properties.ncoms. c. Open the archied DLA properties file for each domain and make the same settings in the new respectie domain-specific file as in the preious archied ncp_dla.properties.domain name file, thus recreating the DLA file for each respectie domain on the new system. CAUTION: Do not copy-paste the preious file content as is into the new file, but copy oer settings that hae been modified on the preious system. The new file contains new parameters that did not exist in preious ersions, and might not function properly if the content is oerwritten. 4. Sae and close each DLA properties file. Related tasks: Configuring the DLA on page 180 The Discoery Library Adapter (DLA) requires a configuration properties file in order to determine the data source to connect to, the domain to query, the target directory for Discoery Library books and logging parameters. Chapter 3. Upgrading and migrating 127

142 Migrating eent handling customizations: If you are upgrading from V3.8 then note that eent enrichment and correlation changed substantially in Network Manager V3.9. Eent enrichment and correlation in Network Manager V4.1 works the same way that it works in Network Manager V3.9. If you made customizations to eent management on a V3.8 installation, then you need to understand how eent enrichment and correlation changed and re-implement your customizations in the new Network Manager V4.1 installation. To understand the changes and re-implement them: 1. Log in to your new installation. 2. Reiew the changes you made to the NcoGateSchema.DOMAIN.cfg and NcoGateInserts.DOMAIN.cfg files and make changes as necessary: a. Go to NCHOME/etc/precision/migration. b. Locate the NcoGateSchema.DOMAIN.cfg and NcoGateInserts.DOMAIN.cfg files for each domain you hae made customizations. c. Understand the eent tables to determine how to reapply any customizations to the config.precedence, config.eentmap, config.ncp2nco, and config.nco2ncp tables. For more information, see the IBM Tioli Network Manager IP Edition Management Database Reference Note: The probe rules populate the NmosEentMap field of alerts.status for all Network Manager eents raised by the poller. The config.precedence table entries are not required unless you wish to oerride the eent map or change the default precedence alue. 3. If you made customizations to the config.ncp2nco or config.nco2ncp tables, then read about the stitchers in the NCHOME/precision/eentGateway/stitchers directory and understand how they work in the current release in order to re-implement eent enrichment customizations. For more information on stitchers, see the IBM Tioli Network Manager IP Edition Eent Management Guide Migrating poll settings: To use your preious polling customizations in ersion 4.1, you must define the scope for each poll policy manually after finishing the import. You do this by associating network iews that contain the poll policy scope to the appropriate poll policy. Custom poll policies and poll definitions are moed to your new system by the export-import process. The scope of the poll policy (the network entities a policy is set to poll) is imported to a network iew, which needs to be set manually for each policy following the migration. In V3.8, the scope is defined by deice class, deice filter, and interface filter set in the poll policy. In V3.9 and V4.1, the scope is defined by the network iew it applies to and can be further refined by setting class and interface filters at the poll definition leel. Poll policies can also hae deice filters set, but they are restricted to the mainnodedetails table, and are aimed at proiding deice filtering to support the MIB Grapher and poll policies created through network iews for right-click menus. In both cases, the export-import process creates network iews based on your preious poll policy scopes and names the network iews after the poll policy. You hae to edit each poll policy and select the appropriate network iew for each after 128 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

143 importing data to your new system. You can also select a deice filter in the poll policy, or create an een more granular scope using the deice class and interface filter settings of poll definitions. In V4.1, the primary method of setting a scope is by using a network iew. You can assign one or more network iews to a poll policy to define the deice scope to be polled. To understand poll policies in V4.1, create new policies and set their scope using network iews. Note: A poll policy can be associated with multiple poll definitions in V4.1, while in V3.8 you can only hae one definition per policy. This can be useful, for example, when you want to poll information that is specific to the deice endor. In such cases you need to set up a poll definition for each endor (as each endor might hae different MIBs), but hae only one policy with all poll definitions added to get the data from across your network. To migrate poll settings, complete the following steps. 1. Use a Web browser to log into the Web applications on your new installation. 2. Make sure the network iews exist for your system: click Aailability > Network Aailability > Network Views. 3. Click Administration > Network > Network Polling. 4. Select a policy that was aailable on your preious system by clicking the name of the poll policy. The Poll Policy Editor is displayed for the policy you selected and its settings are automatically loaded into the fields. 5. Go to the Network Views tab and select the network iew with the same name as the policy. This sets the scope of the policy to the deices in the network iew that is based on your preious system's settings. Note: The poll policies from your preious system that were set up for all deices will not hae a network iew. In such cases, make sure All Deices is selected in the Network Views tab. 6. Optional: You can further refine the scope of the policy by creating a more restricted filter in the Deice Filter tab. Also, the poll definitions attached to the policy can contain more granular filtering based on deice class and interface filters. Tip: If a class or interface filter was set up in your preious system for a poll policy, those settings are defined in the poll definitions in V4.1. The export-import process takes care of moing the deice class settings oer to the new installation by creating the deice class filter setting from V3.8 at the poll definition leel in V Click Sae. 8. Repeat the steps for each poll policy from your preious system. Chapter 3. Upgrading and migrating 129

144 Importing GUI customization data You can now import your preious ersion's GUI data. Before you can import GUI data, you must export the data from your preious installation and install ersion 4.1. The import of GUI data includes import of user role data. Important: Before importing GUI data, you must first create the users required for V4.1 in the appropriate repository (LDAP or ObjectSerer), so that the users can be matched to the user role data that is imported as part of the GUI import. By default only GUI customization data for the Network Manager GUI is migrated. Customization data for the other GUI components, Web GUI and Tioli Common Reporting, is not migrated. Consult Web GUI and Tioli Common Reporting information centers for instructions on migrating those GUI components. To import GUI customization data, perform the following tasks: 1. Log in to the serer where the GUI components of your preious system are installed. 2. Copy the TIPHOME/profiles/TIPProfile/upgrade/data/upgradeData.zip export file to the serer where you installed Network Manager V4.1 GUI components. 3. On your new installation, go to where you placed your installation package. Note: The Tioli Integrated Portal serer must be running during the GUI data import. 4. Run the GUI data import script using one of the following methods: To run the script from the installer launchpad, start the launchpad by running the UNIX launchpad.sh script on UNIX, select the Postinstallation menu item, expand the Upgrading from an existing Network Manager section, and click Import Network Manager GUI Data. To run the script from the command line, change to the scripts subdirectory of the location where you extracted ExportPackage.tar, and depending on your operating system, run the UNIX nmguiimport as follows: nmguiimport -u TIP_admin -p TIP_pass -f path_to_zip -d TIP_location -n netcool_location [-o webgui_location ] Where: TIP_admin is the Tioli Integrated Portal administrator user name. TIP_pass is the Tioli Integrated Portal administrator password. path_to_zip is the path to the GUI data export.zip file. TIP_location is the location of the Tioli Integrated Portal installation to be migrated. netcool_location is the location of the Netcool home directory. webgui_location is the location of the Web GUI home directory. Note: This alue is optional. If no alue is proided, then the script uses a default alue of $NCHOME/omnibus_webgui. Note: If no alues are proided, you are prompted to enter alues. If the directory locations listed in the table below are not proided, then the 130 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

145 enironment ariables shown in the table are used. In all cases, if the enironment ariable does not exist, then you are prompted to enter a location. Table 32. Directory locations required by script Directory location Location of the Tioli Integrated Portal installation to be migrated Netcool home directory Location of the Tioli Netcool/OMNIbus Web GUI home directory Enironment ariable $TIPHOME $NCHOME $NCHOME/omnibus_webgui Note: You must run the script as the same user that installed the product. The exported GUI data is imported into the new installation. The GUI data import process creates its own log files in the following directories: TIPHOME/profiles/TIPProfile/logs/upgrade.log TIPHOME/profiles/TIPProfile/logs/tipcli.log NCHOME/log/install/itnm_gui_migration.log Note: The itnm_gui_migration.log is a migration report file, and proides information about files that are imported, backed up, and require manual reconciliation steps on the new system. After importing your preious GUI data, you must do the following: The import of GUI data does not includes import of user group membership data. At this point you must manually add users to the appropriate user groups on your new V4.1 system. You might need to perform manual settings on the new system. The export-import process proides guidance on what files require attention and manual editing to fully complete the upgrading and migrating process. Related reference: Supported operating systems on page 32 Network Manager is supported on the following operating systems. Related information: Tioli Netcool/OMNIbus Web GUI V7.4 Information Center: Upgrading and migrating Click here for instructions on upgrading toweb GUI 7.4. Tioli Netcool/OMNIbus Web GUI V7.3.1 Information Center: Upgrading and migrating Click here for instructions on upgrading to Web GUI Tioli Common Reporting Information Center: Upgrading Click here for instructions on upgrading to Tioli Common Reporting Chapter 3. Upgrading and migrating 131

146 Importing GUI customization data - manual steps Due to changes in the product, you must migrate some GUI configuration settings manually to the new system. Reiew the following tasks to determine what additional manual adjustments you need to make to your new system. Make sure you hae performed the GUI data collection and export on your preious system and hae imported the GUI data to your new installation. To ensure all GUI settings are migrated: 1. Log in to your new installation. 2. You must manually reconcile the Tioli Integrated Portal files listed in ITNMHOME/profiles/TIPProfile/etc/tnm/migration and ITNMHOME/profiles/ TIPProfile/etc/tnm/*/migration. The archied files are saed by the export-import process. 3. Use the NCHOME/log/install/itnm_gui_migration.log migration report file to check what files require manual editing to be suitable for use on the new system. 4. Any customized WebTool under NCHOME/precision/scripts/webtools are not migrated. You must manually sae them on your preious installation, and reimplement them on the new system. An example of such customization is the settings to launch into TADDM. 5. To presere any new or customized reports from your preious installation, you must perform extra configuration steps. Related tasks: Configuring Network Manager to start IBM Tioli Application Dependency Discoery Manager on page 192 Optional: To enable Network Operators to launch the IBM Tioli Application Dependency Discoery Manager GUI from Network Manager, you must add the TADDM menu options to Network Manager. Migrating reports: If you hae modified or created reports in Network Manager 3.8 or 3.9, you must migrate those reports manually. Before performing this task, you must first import the 3.8 or 3.9 GUI data, which includes the reports. The GUI data import script, nmguiimport, puts all customized reports into the Tioli Products > ITNM Reports report set. To migrate customized reports, complete the following steps: 1. Log in to Network Manager 4.1 and click Reporting > Common Reporting > Tioli Products > ITNM Reports. If this report set does not contain any new or customized reports, you do not need to do this task. You can delete the Tioli Products > ITNM Reports report set. If the report set does contain new or customized reports, choose which reports you want to migrate. 2. On the serer where Tioli Common Reporting is installed, naigate to the directory where the imported 3.8 or 3.9 custom report designs are located: NCHOME/../tip2Components/TCRComponent/data/design. 3. To moe a report to a 4.1 report group, run a command similar to the following: 132 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

147 NCHOME/../tip2Components/TCRComponent/bin/trcmd.sh -import -design report_filename -reportsetbase destination_report_set -resourcedir ITNM41 -username admin_username -password admin_password Where report_filename is the filename of the report to moe. destination_report_set is the 4.1 report set where you want the report to be moed to. Possible alues are: Reports']" Status Reports']" Technology Reports']" Views Reports']" View Reports']" Manager']/ Reports']" Technology Reports']" Reports']" Manager']/ Reports']" Reports']" admin_username is the username of a Tioli Integrated Portal administrator. admin_password is the password for the administratie user. The following command moes a report called itnm_usa_lan_summary to the Network Technology Reports report set: NCHOME/../tip2Components/TCRComponent/bin/trcmd.sh -import -design itnm_usa_lan_summary.rptdesign -reportsetbase "/content/ package[@name='network Manager']/folder[@name='Network Technology Reports']" -resourcedir ITNM41 -username tipadmin -password netcool 4. Reiew the reports that you hae moed into a 4.1 report set. If a report uses the ncmonitor or ncpolldata database, check the SQL commands against similar commands in the default 4.1 reports. The database schemas might hae changed. Important: Any parameters that were saed with reports are not presered. Chapter 3. Upgrading and migrating 133

148 Reapplying manually created topology to your discoered topology Once you hae performed a network discoery for a gien domain on your new installation, you must now reapply the manually created topology from that domain on your preious system to this newly discoered topology. In order to reapply manually created topology to your discoered topology, you must first retriee files from the export process that contain details of the manually created topology. You must then reapply the changes to the network topology from your new discoery using the topology management wizards within the Network Hop View. For each discoery domain, perform the following steps: 1. On your new installation, naigate to the following location $NCHOME/ar/precision/export/manualtopology. This directory contains XML files listing the deices and connections manually added to each domain on your preious system. There is one file for each domain. Each file is named as follows: ManualTopology.DOMAIN.xml Where DOMAIN is the name of releant domain. 2. Open the XML file for the domain you want to update with manually created topology data. 3. Apply the changes to your new discoery using the topology management wizards within the Network Hop View. You can manually add deices from any Network Hop View window. To manually add connections, the best practice is to point the Network Hop View window to the a-end deice (specified using the fromdeice attribute in the connection) and create a manual connection to the b-end deice (specified using the todeice attribute). For more information on editing network topology using the topology management wizards, see the IBM Tioli Network Manager IP Edition Network Visualization Setup Guide. The following example shows how to add a deice and how to add a connection using an XML code snippet from an XML file produced by the import script. The XML code snippet below represents three manually added deices, and three manually added connections. Note: Tag entries for connections appear before entries for deices in the XML file. Howeer, when reapplying the manual topology using the Topology Editor, you must first add all of the deices specified in the file, and subsequently add the connections. 134 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

149 Table 33. XML code snippet from a manual topology file <?xml ersion= 1.0 standalone= yes?> <ManualTopology domain="domain_39" ersion="3.9" <Connection connectiity="layer 3 Meshed Topology" fromdeice="aog.dom39.1" reason="reas" speed="1111" todeice="aog.dom39.2" / <Connection connectiity="layer 3 Meshed Topology" fromdeice="aog.dom39.2" reason="" todeice=" " tointerface="[ GigabitEthernet0/1/0/1 ]" / <Connection connectiity="layer 2 Topology" fromdeice=" " frominterface="[ Null0 ]" reason="" speed="2345" todeice=" " tointerface="[ Nu0 ]" / <Deice entityname="aog.dom39.1" accessipaddress=" " accessprotocol="ip4" classname="cisco" description="aog.dom39.1 desc" displaylabel="aog.dom39.1" ipforwarding="forwarding" modelname="aog.dom39.1 modelname" reason="aog.dom39.1 reason" serialnumber="ser.123" syscontact="aog.dom39.1 syscont" sysdescr="aog.dom39.1 sysdesc" syslocation="aog.dom39.1 sysloc" sysname="aog.dom39.1 sysname" typename="chassis" / <Deice entityname="aog.dom39.2" accessipaddress=" " accessprotocol="ip4" classname="cisco" displaylabel="aog.dom39.2" reason="" typename="chassis" / <Deice entityname="aog.dom39.3" accessprotocol="ip4" classname="cisco" displaylabel="aog.dom39.3" reason="" typename="chassis" /</ManualTopology The following table summarizes the elements and attributes in this XML code snippet: Table 34. Description of the XML code snippet from a manual topology file Line number Description 2 Domain to which this manual topology applies. 4-8 Manual connection between a manually added deice "aog.dom39.1" and another manually added deice "aog.dom39.2". Chapter 3. Upgrading and migrating 135

150 Table 34. Description of the XML code snippet from a manual topology file (continued) Line number Description 9-13 Manual connection between a manually added deice "aog.dom39.2" and interface [ GigabitEthernet0/1/0/1 ] on discoered deice Note: The deice does not appear within a <Deice> tag in this file; hence it is not a manually added deice and therefore must be a discoered deice Manual connection between interface [ Null0 ] on discoered deice to interface [ Nu0 ] on discoered deice Note: The deice does not appear within a <Deice> tag in this file; hence it is not a manually added deice and therefore must be a discoered deice Manually added deice aog.dom Manually added deice aog.dom Manually added deice aog.dom39.3. Perform the following steps to use the topology management wizards to add the deices and connections in the example XML code snippet to the topology. 1. Click Network Aailability > Network Hop View. 2. Select a network domain from the Domain drop-down list corresponding to line 2 in the example XML code aboe. 3. Add all the deices specified in the XML file by performing the following steps: a. Right click anywhere within Network Hop View and then click Topology Management > Add Deice. b. In the Add Deice wizard, add the deice aog.dom39.1 by specifying the attributes listed in lines 21 to 35 of the XML file. Note: Be aware of the following: Attributes in the XML file appear in alphabetical order. This is different to the order in which they are requested by the GUI. The XML file might not show all attributes requested by the GUI for a gien deice or connection. Where attributes are missing, do not enter any alues in the GUI. Complete all the wizard screens and click Finish, followed by Close. The deice you added appears in the Network Hop View. For more information on editing network topology using the topology management wizards, see the IBM Tioli Network Manager IP Edition Network Visualization Setup Guide c. Right click anywhere within Network Hop View, then click Topology Management > Add Deice and add the deice aog.dom39.2 by specifying the attributes listed in lines 36 to 42 of the XML file. Complete all the wizard screens and click Finish, followed by Close. The deice you added appears in the Network Hop View. d. Right click anywhere within Network Hop View, then click Topology Management > Add Deice and add the deice aog.dom39.3 by specifying the attributes listed in lines 43 to 48 of the XML file. Complete all the wizard screens and click Finish, followed by Close. The deice you added appears in the Network Hop View. 4. Add all the connections specified in the XML file by performing the following steps: 136 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

151 a. In the Network Hop View, naigate to a hop iew that contains the deice aog.dom39.1. For more information on finding deice in the Network Hop View, see the IBM Tioli Network Manager IP Edition Network Troubleshooting Guide b. Right click deice aog.dom39.1 and click Topology Management > Add Connection. c. In the Add Connection wizard, add a connection from deice aog.dom39.1 to deice aog.dom39.2 by specifying the attributes listed in lines 4 to 8 of the XML file. Complete all the wizard screens and click Finish, followed by Recenter & Close. The connection you added appears in the Network Hop View. For more information on editing network topology using the topology management wizards, see the IBM Tioli Network Manager IP Edition Network Visualization Setup Guide d. In the Network Hop View, ensure that you are in a hop iew that contains the deice aog.dom39.2, then right click deice aog.dom39.2 and click Topology Management > Add Connection. Add a connection from deice aog.dom39.2 to interface [ GigabitEthernet0/1/0/1 ] on deice by specifying the attributes listed in lines 9 to 13 of the XML file. Complete all the wizard screens and click Finish, followed by Recenter & Close. The connection you added appears in the Network Hop View. e. In the Network Hop View, ensure that you are in a hop iew that contains the deice , then right click deice and click Topology Management > Add Connection. Add a connection from interface [ Null0 ] on deice to interface [ Nu0 ] on deice by specifying the attributes listed in lines 14 to 20 of the XML file. Complete all the wizard screens and click Finish, followed by Recenter & Close. The connection you added appears in the Network Hop View. Reapplying managed status data to your discoered topology Once you hae performed a network discoery for a gien domain on your new installation, you must now reapply the managed status data from that domain on your preious system to this newly discoered topology. The managed status of a network entity indicates whether it is currently being managed by Network Manager; that is, whether the entity is polled by Network Manager and is considered for root-cause analysis. In order to reapply managed status data to your discoered topology, you must first retriee files from the export process that contain details of the managed status data. You must then reapply the changes to the network topology from your new discoery using the ManageNode.pl Perl script. The following directory contains files from the export process with details of the managed status data, one file for each domain: $NCHOME/ar/precision/export/managedstatus/ Each of these files contains a list of unmanaged entities, either main nodes or interfaces; these are entities that were placed into unmanaged status on your old system. The files are named using the following conention: UnmanagedEntities.DOMAIN.dat Where DOMAIN is the name of the releant directory. For each discoery domain, perform the following steps: Chapter 3. Upgrading and migrating 137

152 1. On your new installation, change to the following directory: cd $NCHOME/precision/bin. 2. Run the ManageNode.pl script for the domain you want to update with managed status data. Use a command similar to the following, and point the script to the domain-specific file: ncp_perl UnmanageNode.pl -domain DOMAIN_NAME -user ncim -pwd password -nomainnodelookup -file $NCHOME/ar/precision/export/managedstatus/UnmanagedEntities.DOMAIN_NAME. Where: DOMAIN_NAME is the domain you are updating with managed status data. password is the password for the ncim user. For more information on the UnmanageNode script, see the IBM Tioli Network Manager IP Edition Administration Guide. The script outputs the names of the main nodes and interfaces that were placed into unmanaged status. For example: aaa core.test.lab[ Lo0 ] unmanaged. bbb core.eu.test.lab unmanaged. Upgrading to latest Network Manager by reusing your existing Tioli Integrated Portal enironment Follow this procedure to reuse your existing Tioli Integrated Portal serer for the Network Manager GUI upgrades, and fully migrate all other serers in your installation to new serers. Important: You can only follow this procedure if the Tioli Integrated Portal serer on which you are performing the upgrade is on the latest supported ersion of Tioli Integrated Portal. In Network Manager terms this means you can only follow this procedure if you are upgrading from Network Manager V3.9 Fixpack 3, which is certified on Tioli Integrated Portal V Therefore if you want to follow this procedure, you must first ensure that: You hae upgraded your ersion of Network Manager V3.9 to Fixpack 3. You hae upgraded your ersion of Tioli Integrated Portal to V Note: You cannot follow this procedure if you are upgrading from Network Manager V3.8. Reusing an existing Tioli Integrated Portal enironment: oeriew Use this information as a step-by-step guide to upgrading Network Manager and migrating existing settings to the upgraded ersion. Upgrading and migrating steps Moing to the latest ersion of Network Manager inoles seeral steps. The process uses separate scripts for moing the core and the GUI component settings across to the new installation. Note: You can only perform this procedure on a distributed installation. The core components must be on a separate serer to the Tioli Integrated Portal serer. Core components must be migrated side by side to a new serer, while the GUI components can be migrated by reusing the existing Tioli Integrated Portal serer. 138 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

153 Table 35. Migrating core customization data This procedure is diided into two parts: 1. Migrate core customization data from all serers other than the Tioli Integrated Portal in your installation to new serers. This must be done using side-by-side migration. 2. Reuse your existing Tioli Integrated Portal serer and upgrade just the Network Manager GUI components on that serer to V41. Use the steps in the tables below to guide you through the procedure. Note: Many of the links in the tables below take you to topics within the Full side-by-side migration section. Make sure to follow the sequence of steps in these tables rather than the sequence of topics in the Full side-by-side migration section. Migrating core customization data The following table lists the steps to perform to migrate core customization data from all serers other than the Tioli Integrated Portal in your installation to new serers. Action 1. Install Network Manager V4.1 core components only. 2. Install IBM Tioli Netcool/OMNIbus Chapter 2, Installing, on page 41 Step Follow the instructions in the installer launchpad to install the core components only. You can install IBM Tioli Netcool/OMNIbus as part of your Network Manager installation. For information about upgrading and migrating IBM Tioli Netcool/OMNIbus, see the IBM Tioli Netcool/OMNIbus Installation and Deployment Guide. Note: If you installed a new instance of IBM Tioli Netcool/OMNIbus as part of the Network Manager installation, the ObjectSerer name you proided during the installation is stored in NCHOME/etc/precision/ ConfigItnm.Network_Manager_Domain_Name.cfg 3. Prepare your existing system. 4. Export core customization data. 5. Identify NCIM topology database customizations 6. Apply customizations from the source NCIM topology database 7. Import preious core configuration data into your new installation. 8. Due to changes in the product, some core configuration settings must be migrated manually to the new system. Preparing for upgrade: core serer on page 141 Exporting core customization data on page 114 Identifying NCIM topology database customizations on page 117 Applying customizations from the source database on page 118 Importing core customization data on page 119 Importing core customization data - manual steps on page 122 Chapter 3. Upgrading and migrating 139

154 Table 35. Migrating core customization data (continued) Action 9. Stop and start Network Manager back end processes Starting and stopping Network Manager Step This enables alidation of the back end Network Manager processes. Once you hae started up the back end processes, check the core process log files at the following location to ensure that there are no conflicts between the migrated files and the new system. Core log files are located at: $NCHOME/log/precision Upgrading Network Manager GUI components on an existing Tioli Integrated Portal serer The following tables lists all the steps to perform to reuse your existing Tioli Integrated Portal serer and upgrade just the Network Manager GUI components on that serer to V41. Table 36. Upgrading Network Manager GUI components on an existing Tioli Integrated Portal serer Action Step 1. Extract the Network Extracting the installation file on page 48 Manager V41 installation package. 2. Prepare your existing system. 3. Export GUI configuration data. 4. Uninstall Network Manager GUI components from the existing Tioli Integrated Portal serer. 5. Install Network Manager GUI components. 6. Import preious GUI configuration data into your new installation 7. Due to changes in the product, some GUI configuration settings must be migrated manually to the new system. Preparing for upgrade: existing Tioli Integrated Portal serer on page 142 Exporting GUI customization data on page 115 Uninstalling on UNIX on page 93 Specify the -t option when running the script. This remoes all Network Manager portlet content from the Tioli Integrated Portal serer. Installing Network Manager GUI components on page 142 Importing GUI customization data on page 130 Importing GUI customization data - manual steps on page 132 Reapplying custom topology data The following tables lists all the steps to perform to reapply custom topology data. Perform the following steps for each desired network domain. Table 37. Reapplying custom topology data Action Step 1. Run a network discoery. For more information, see the IBM Tioli Network Manager IP Edition Discoery Guide. 2. Reapply manually created Reapplying manually created topology to your discoered topology on page 134 topology to your discoered topology. 140 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

155 Table 37. Reapplying custom topology data (continued) Action 3. Reapply managed status data to your discoered topology. Step Reapplying managed status data to your discoered topology on page 137 Preparing for upgrade: core serer Prepare your existing core serer for upgrade by copying oer the files required for the upgrading and migrating process. The Network Manager installation package contains all files required. Prepare for the upgrade: 1. Go to the system where you installed the Web Applications (also referred to in the documentation as "GUI components") for Network Manager V4.1. In a single serer installation, this is the serer where you installed Network Manager V4.1. In a distributed installation, this is the Tioli Integrated Portal serer. 2. Locate the following file: $NCHOME/precision/install/data/ExportPackage.tar. 3. Copy the compressed file to the serer on your existing Network Manager installation that contains the core components. 4. Extract the file to a temporary location. Note: The temporary location must be a directory that is not the Netcool home directory $NCHOME and is not a subdirectory of $NCHOME. The files and utilities required for the upgrading and migrating process are aailable after extracting the compressed file. The main items that require attention are as follows: The launchpad utility: Use this utility to start the launchpad GUI from where you can run a data collection on your preious installation. The data collected then can be exported for applying to new installations. An import utility is also proided for use on your new installation. You can use a GUI or command line to start and use this utility. Note: You can use the export utility to collect data on Network Manager ersions 3.8, or 3.9 installations. The Preupgrade.tar: Contains utilities for exporting preious GUI settings on Network Manager V3.8 and then importing them into your new installation. Note: This file is only needed for the export-import of V3.8 GUI component data. 5. Ensure that poll policy names and poll definition names are unique. In preious releases of Network Manager, a known limitation allowed duplicate poll policy names or duplicate poll definition names to be created. In Network Manager V4.1, duplicate poll policy names or poll definition names are not allowed. If you hae created poll policies or poll definitions with the same name on your preious V3.8 installation, then you must rename one of each duplicate pair to make sure that each poll policy and each poll definition name is unique on your system. You must do this before performing any data export. Chapter 3. Upgrading and migrating 141

156 Preparing for upgrade: existing Tioli Integrated Portal serer Prepare your existing system for upgrade by copying oer the files required for the upgrading and migrating process. 1. On the Tioli Integrated Portal serer where you extracted the Network Manager V41 installation package, go to the directory where you extracted the package. 2. Run the UpdatePlugins script, as follows:./updateplugins -i location_of_extracted_install_package Where location_of_extracted_install_package is the directory where you extracted the Network Manager V41 installation package. 3. Locate the following file: $NCHOME/precision/install/data/ExportPackage.tar. 4. Extract the file to a temporary location. Installing Network Manager GUI components Install the Network Manager GUI components by running the launchpad.sh script and selecting the appropriate options 1. Go to the directory where you extracted the Network Manager V41 installation package 2. Start the installer wizard from the launchpad by running the launchpad.sh script. 3. Select the following options within the launchpad: a. In the Select Installation Location panel, set the Tioli Network Manager installation location to the same alue as in the V3.9 installation from which you are upgrading. The Tioli Network Manager installation location on the preious system corresponds to the directory path $NCHOME/precision. b. In the Select Installation Options panel, select the following options: Multi-serer installation Customize settings c. In the Select Components to Install panel, select the following option: Web Applications This option is another name for the Network Manager GUI components. d. In the Select Installation Directory for TIP panel, select the following option: Reuse an existing install folder, and select the directory path of an existing installation of the Tioli Integrated Portal. e. In the Collect Tioli Integrated Portal Reuse Details panel, specify required details for the existing Tioli Integrated Portal serer. 4. Complete the wizard panels and run the installation. Related reference: Values for a custom installation on page 56 Use this information to understand what alues to enter in the wizard panels for a custom installation. 142 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

157 Copying an existing V4.1 installation You can copy an existing V4.1 installation's customizations and data to another V4.1 installation. Using the export-import scripts proided with Network Manager you can make a copy of a V4.1 installation and use it recreate the same setup on a another system, restore settings later, or moe from test system to a production enironment. To copy an existing V4.1 installation: 1. Access the source system where you hae the Network Manager installation you want to make a copy of. If you hae a distributed setup, you need to access each system to collect all data. 2. Go to where you extracted the installation package. 3. Run the data export script using one of the following methods: To run the script from the installer launchpad, start the launchpad by running the UNIX launchpad.sh script on UNIX, select the Preinstallation and Migration menu item, expand the Upgrading from an existing Network Manager section, and click Export Network Manager Data. To run the script from the command line, run the UNIX nmexport script on UNIX from the scripts subdirectory. Note: You must run the script as the same user that installed the product. Proide the answers to the prompts. The export script extracts data and saes it to an export file in a location of your choice (.pkg on UNIX systems or.zip on Windows systems). Restriction: Historical polling data is not moed oer when copying between V4.1 releases. 4. Run the GUI data export: Note: You must run the GUI data export as the same user that installed the product. To run the script from the installer launchpad, start the launchpad by running the UNIX launchpad.sh script on UNIX, select the Preinstallation and Migration menu item, expand the Upgrading from an existing Network Manager section, and click Export Network Manager GUI Data. To run the script from the command line, change to the scripts subdirectory of the location where you extracted ExportPackage and run the UNIX nmguiexport: nmguiexport -u TIP_admin -p TIP_pass -d TIP_location -n netcool_location [-owebgui_location ] Where: TIP_admin is the Tioli Integrated Portal administrator user name. TIP_pass is the Tioli Integrated Portal administrator password. TIP_location is the location of the Tioli Integrated Portal installation to be migrated. netcool_location is the location of the Netcool home directory. Chapter 3. Upgrading and migrating 143

158 webgui_location is the location of the Web GUI home directory. Note: This alue is optional. If no alue is proided, then the script uses a default alue of $NCHOME/omnibus_webgui. Note: If no alues are proided, you are prompted to enter alues. If the directory locations listed in the table below are not proided, then the enironment ariables shown in the table are used. In all cases, if the enironment ariable does not exist, then you are prompted to enter a location. Table 38. Directory locations required by script Directory location Location of the Tioli Integrated Portal installation to be migrated Netcool home directory Location of the Tioli Netcool/OMNIbus Web GUI home directory Enironment ariable $TIPHOME $NCHOME $NCHOME/omnibus_webgui Data is extracted to the $TIPHOME/profiles/TIPProfile/output/data.zip export file. 5. If you made customizations to your source NCIM topology database, then run the ncp_ncim_diff.pl Perl script to identify the customizations. For more information, see Identifying NCIM topology database customizations on page Log in to the Network Manager installation where you want to copy the setup. 7. On your new installation, make sure that the Network Manager core components for each domain are running. To do this, use the following command on UNIX systems: itnm_start ncp -domain DOMAIN. For example, to start the NCOMS domain, type: itnm_start ncp -domain NCOMS. This ensures that Network Manager is fully initialized and the domain tables are populated. You must stop the core components again to do the import itself, as described in the next step. 8. Stop the Network Manager core components for each domain on your new installation using the following command on UNIX systems: itnm_stop ncp -domain DOMAIN. For example, to stop the NCOMS domain, type: itnm_stop ncp -domain NCOMS Note: If you do not specify a domain name with itnm_stop, it stops the default domain created at installation. 9. If you made customizations to your source NCIM database, then manually update the new NCIM topology database schema with any customizations. For more information, see Applying customizations from the source database on page On your new installation, go to the location $NCHOME/precision/install/data/ and extract the package ExportPackage.tar. 11. Run the data import script using one of the following methods: To run the script from the installer launchpad, start the launchpad by running the UNIX launchpad.sh script on UNIX, select the Postinstallation menu item, expand the Upgrading from an existing Network Manager section, and click Import Network Manager Data. 144 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

159 Note: The launchpad can be found in the directory where you extracted the Network Manager installation package. To run the script from the command line, run the UNIX nmimport script on UNIX from the scripts subdirectory. Note: You must run the script as the same user that installed the product. 12. When prompted, proide the path to the.pkg or.zip file that contains the customization data that you preiously exported. 13. Answer the arious other questions the import process asks to copy the data oer. Note: The following question requires special attention: Allocate new entityids during import [N] Each deice in the system has an entityid. The import process can allocate new entityids or presere the existing entityids. Presering the existing entityids is necessary when you hae links to external systems that use Network Manager data, for example, Tioli Data Warehouse. Howeer, to presere existing entityids, the target system needs to be empty. If the target system is not empty (for example, due to a preious data import or discoery), presering entityids might become a complex operation due to potential clashes between existing entityids and the entityids being imported, and the results may be unpredictable. Therefore, merging of domain data is not supported. Attention: If you hae a domain on the target system that has the same name as on your preious system, then make sure the domain on the target system does not contain data. Domain names cannot be changed during the migration process. Answer N[o] to this question to presere entityids ory[es] to allocate new entityids. If you answer N[o], then the data import script performs a check to determine whether entity data already exists in the database. Data will exist in the database in the case of a preious data import or discoery. If the check determines that entity data already exists in the database, then the script aborts with the message: System has entity data. Aborting. If this happens, rerun the data import script and answer Y[es] to this question. This will ensure that new entityids are allocated. If the check determines that no entity data exists in the database, then each deice in the new installation maintains the entityid from the preious installation. If you answer Y[es], then deices are allocated new entityids. The import process creates its own log files. Logs from the import process are saed to NCHOME/log/precision: ITNMDataImport.log get_policies.domain name.log ITNMImportNetworkViews.log The export-import process automatically detects and recreates the domains from a preious install. The import script detects the potential domains from Chapter 3. Upgrading and migrating 145

160 the preious system based on the data files. Using the domain_create.pl script, the process automatically creates domains on the new installation using the domain names from the preious system. After the domains hae been created, the main topology and policy data are imported for each. The domain_create.pl script creates the discoery configuration files for the new domains in NCHOME/etc/precision using the alues in the configuration files of the default domain. The import process saes the imported files in the NCHOME/etc/precision/migration directory as read-only files. You can use the imported files to manually update the newly created files in NCHOME/etc/precision. When copying from an existing V4.1 installation, the files can be copied directly into NCHOME/etc/precision, but they need to be gien write permissions to be able to be edited from the Discoery Configuration GUI. 14. Check whether there are any files in the NCHOME/etc/precision/migration directory. Any user changes made in the files listed here might need to be reiewed and applied again manually. 15. Run the GUI data import: To run the script from the installer launchpad, start the launchpad by running the UNIX launchpad.sh script on UNIX, select the Postinstallation menu item, expand the Upgrading from an existing Network Manager section, and click Import Network Manager GUI Data. To run the script from the command line, change to the scripts subdirectory of the location where you extracted ExportPackage.tar, and depending on your operating system, run the UNIX nmguiimport as follows: nmguiimport -u TIP_admin -p TIP_pass -f path_to_zip -d TIP_location -n netcool_location [-owebgui_location ] Where: TIP_admin is the Tioli Integrated Portal administrator user name. TIP_pass is the Tioli Integrated Portal administrator password. path_to_zip is the path to the GUI data export.zip file. TIP_location is the location of the Tioli Integrated Portal installation to be migrated. netcool_location is the location of the Netcool home directory. webgui_location is the location of the Web GUI home directory. Note: This alue is optional. If no alue is proided, then the script uses a default alue of $NCHOME/omnibus_webgui. Note: If no alues are proided, you are prompted to enter alues. If the directory locations listed in the table below are not proided, then the enironment ariables shown in the table are used. In all cases, if the enironment ariable does not exist, then you are prompted to enter a location. Table 39. Directory locations required by script Directory location Location of the Tioli Integrated Portal installation to be migrated Netcool home directory Enironment ariable $TIPHOME $NCHOME 146 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

161 Table 39. Directory locations required by script (continued) Directory location Location of the Tioli Netcool/OMNIbus Web GUI home directory Enironment ariable $NCHOME/omnibus_webgui Troubleshooting the upgrade Note: You must run the GUI data import as the same user that installed the product. The Tioli Integrated Portal serer must be running during the GUI data import. 16. You must manually reconcile the Tioli Integrated Portal files listed in ITNMHOME/profiles/TIPProfile/etc/tnm/migration and ITNMHOME/profiles/ TIPProfile/etc/tnm/*/migration. The archied files are saed by the export-import process. 17. Use the NCHOME/log/install/itnm_gui_migration.log migration report file to check what files require manual editing to be suitable for use on the new system. 18. Stop and start Network Manager, including the Tioli Integrated Portal, as described in Starting and stopping Network Manager. The default domain is started by the start process, but if you hae multiple domains then start each using the itnm_start ncp -domain DOMAIN command. Use this information to how to troubleshoot errors that might occur during the installation of Network Manager. Viewing the upgrade logs Viewing the upgrade logs can be useful for troubleshooting purposes. Information about the success of the upgrade process is recorded in different log files. To iew the upgrade log information, proceed as follows. Consult the appropriate upgrade log: Symptom The part of the upgrade that failed is the core data export. Action Examine the following logs on the source system: 1. Go to the home directory of the user that ran the script. For example, if the root user ran the script, then go to /root/itnmexportlogs/. 2. Examine the logs in this directory. These logs all proide information to support debugging of problems. get_policies_domain_name.log ITNMCompareSystems.log ITNMDataExport.log ITNMExportNetworkViews.log. This log also proides details of the network iews that were exported. Chapter 3. Upgrading and migrating 147

162 Symptom The part of the upgrade that failed is the GUI data export. The part of the upgrade that failed is the core data import. For information about core data files that might require manual modification following import to the target system. The part of the upgrade that failed is the GUI data import. For information about GUI data files that might require manual modification following import to the target system. Action Examine the following logs on the source system: 1. Go to the directory $TIPHOME/profiles/TIPProfile/ logs/ 2. Examine the logs in this directory: These logs all proide information to support debugging of problems. If upgrading from a V3.8 installation preupgrade.log tipexport.log If upgrading from a V3.9 installation tipcli.log Examine the following logs on the target system: 1. Go to the directory $NCHOME/log/precision/. 2. Examine the logs in this directory. These logs all proide information to support debugging of problems. get_policies_domain_name.log ITNMDataImport.log ITNMImportHistoricalData.log ITNMImportNetworkViews.log This log also proides details of the network iews that were imported. Examine the following file on the target system: 1. Go to the directory $NCHOME/log/precision/. 2. Examine the following file in this directory. ITNMCompareSystemsFinal.txt This file proides information on what manual changes might be required. Examine the following logs on the target system: 1. Go to the directory $TIPHOME/profiles/TIPProfile/ logs/. 2. Examine the following logs in this directory. These logs all proide information to support debugging of problems. tipcli.log upgrade.log Examine the following file on the target system: 1. Go to the directory $NCHOME/log/install/. 2. Examine the following log in this directory. itnm_gui_migration.log This file proides information about files that are imported, backed up, and require manual reconciliation steps on the new system. Use this file to check what files require manual editing to be suitable for use on the new system. 148 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

163 Harmless upgrade error messages The following error messages might appear during the upgrade but can be ignored. Exporting GUI data The following error message occurs wheneer exporting GUI data from a Tioli Integrated Portal 2.X enironment. This message can be ignored. SEVERE: An exception occurred when executing a remote binary. The executable /space/ats/tip2/profiles/tipprofile/upgrade/bin/exportldapconfig.sh /space/ats/tip2 /space/ats/tip2/profiles/tipprofile/output/configdata returned the following code 1. Network iews with duplicate names following import Following import you might find network iews with duplicate names in the network iew tree. When network iews are migrated from a preious release, the iews from the preious release are migrated, including domains with the same name. Consequently there might be multiple network iew container iews with the same name. You can delete duplicate iews, or moe sections of iews into the existing iews. Not all GUI components were exported During export of GUI component data, if customization data for any of the GUI components was not correctly exported then a warning is displayed. Symptoms During GUI component export, you might encounter the following combination of error and warning messages: ERROR: The TIP export of ITNMGUI did not complete successfully with error code : 5... Other lines of script output Other lines of script output Other lines of script output... WARNING: The script did not export all components [ OMNIbusWebGUI ] successfully. Consult TIPHOME/profiles/TIPProfile/logs/tipcli.log for more details This means that the export of GUI components has been partially successful. The script exported all GUI components to the $TIPHOME/profiles/TIPProfile/ upgrade/data/upgradedata.zip export file, except for the component or components specified in the warning message. In the example aboe, all GUI components were successfully exported except for Web GUI. Causes A common causes of these errors is the following: a configuration file required by the export script is named incorrectly in the file system. Diagnosis and resolution: incorrect file name To check whether a configuration file required by the export script is named incorrectly in the file system, perform the following steps: Chapter 3. Upgrading and migrating 149

164 1. Reiew the log file $TIPHOME/profiles/TIPProfile/logs/tipcli.log and look for any messages indicating that a file was not found. For example, the following message indicates that the ITNMGUIConfiguration.properties file was not found. INFO: /space/ats/netcool/precision/integration/plugins/itnmguiconfiguration. properties (No such file or directory) Throwable occurred: jaa.io.filenotfoundexception: /space/ats/netcool/precision /integration/plugins/itnmguiconfiguration.properties (No such file or directory) The ITNMGUIConfiguration.properties file is required by the ITNM GUI component. In this scenario the ITNM GUI component is installed on the current serer, so the expectation is that there is an error in file naming. 2. Check that the ITNMGUIConfiguration.properties file is named correctly on the filesystem. 3. If necessary, rename the file and run the GUI export script again. Poll definition classes not migrated correctly The custom data import also migrates custom poll definition data. Howeer, some of the class settings associated with custom poll definitions might not hae been migrated correctly. For example, a class might be enabled on the source system but is disabled on the target system. Symptoms Some of the class settings associated with custom poll definitions might not hae been migrated correctly. For example, a class might be enabled on the source system but is disabled on the target system. Note: This is only a problem when upgrading from an earlier system to Network Manager V4.1. This problem does not occur when copying one Network Manager V4.1 to another Network Manager V4.1 system. Resolution On the target system, check the class settings for each migrated custom poll definition using the Network Polling GUI, and correct where necessary. 150 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

165 Chapter 4. Configuring Network Manager After installing Network Manager, you must configure Network Manager for your enironment and your requirements. If your enironment or your requirements change at a later time, or if you want to integrate Network Manager with other products, you might need to perform additional configuration tasks. Click the following link to retriee technotes about known configuration issues in ersion 3.9 of Network Manager: &wfield=configure+configuration+configuring&rs=3118&tc=ssshrk &atrn=swversion&atr=3.9&ibm-go.x=18&ibm-go.y=12 Configuring integrations with other products You can set up Network Manager to work with a number of Tioli products. Read about necessary configuration tasks required to set up the aailable integrations. Related reference: Requirements for other products on page 30 Make sure that you meet the requirements for the products that are integrated with Network Manager. Configuring Tioli Netcool/OMNIbus for use with Network Manager If you hae installed Tioli Netcool/OMNIbus not using the Network Manager installation, then you must perform a number of configuration tasks. Tioli Netcool/OMNIbus handles eents proided by Network Manager and other eent sources, and can also be used as an authentication source. See Related information below for links to releant topics. To use Tioli Netcool/OMNIbus, you must modify a table in the ObjectSerer. If you are running Network Manager in a FIPS installation, you must make additional configuration to the Tioli Netcool/OMNIbus JRE. For detailed information about Tioli Netcool/OMNIbus, including post-installation configuration and FIPS considerations, see the Tioli Netcool/OMNIbus information centre at infocenter/tiihelp/8r1/topic/com.ibm.tioli.namomnibus.doc/welcome_ob.htm. For more information about Tioli Netcool/OMNIbus, including post-installation configuration and FIPS considerations, see the IBM Tioli Netcool/OMNIbus Installation and Deployment Guide and the IBM Tioli Netcool/OMNIbus Administration Guide. Copyright IBM Corp. 2006,

166 Related tasks: Configuring VMM for the ObjectSerer on page 200 When your Tioli Netcool/OMNIbus ObjectSerer is in a federated repository, use the script proided with Tioli Integrated Portal to configure the Virtual Member Manager adapter for the ObjectSerer. Configuring data source failoer for the Tioli Netcool/OMNIbus Web GUI on page 267 If you hae a failoer pair of ObjectSerers to which the Web GUI should connect, you can configure data source failoer by using the ncwdatasourcedefinitions.xml data source configuration file in your Web GUI installation. Configuring automation for SAEs You must follow additional post-installation steps to set up the automation that supports the generation of serice-affected eents (SAEs). If you hae a Tioli Netcool/OMNIbus installation that is more complex than a single ObjectSerer installed on the same serer as Network Manager, ensure that Tioli Netcool/OMNIbus is set up according to the Tioli Netcool/OMNIbus Best Practices Guide, aailable from the Tioli Netcool/OMNIbus Best Practices wiki. In particular, ensure that any SAE triggers only run on the acting primary aggregation ObjectSerers and are disabled on all other ObjectSerers. The default SAE triggers supplied with Network Manager are configured to run only on the primary aggregation Objectserers. Note: If you do not hae a multi-tiered architecture, configure your single ObjectSerer or ObjectSerer pair for SAE following the instructions gien here for aggregation layer ObjectSerers. Use the following steps to set up the automation and the SAE plug-in in the Eent Gateway (ncp_g_eent): 1. Log into the host where Tioli Netcool/OMNIbus is installed. Start the ObjectSerers if they are not already running. 2. Stop the ncp processes, as described in Starting and stopping processes. 3. Do not configure the collection layer ObjectSerers for SAE. 4. Configure the aggregation layer ObjectSerers: a. Run the NCHOME/precision/scripts/drop_sae_automation.sql script to remoe existing tables. To run the script, use a command line similar to the following: UNIX $NCHOME/omnibus/bin/nco_sql -serer objectserer_name -user user_name -password password < $NCHOME/precision/scripts/drop_sae_automation.sql b. Ensure that the SAE automation runs only on the acting primary ObjectSerer and not on the backup ObjectSerer. Edit the create_sae_automation.sql file and erify or add the following line: WHEN get_prop_alue( ActingPrimary ) %= TRUE c. Run the NCHOME/precision/scripts/create_sae_automation.sql script to install the SAE trigger and add the tables, including the NmosDomainName column. To run the script, use a command line similar to the following: UNIX $NCHOME/omnibus/bin/nco_sql -serer objectserer_name -user user_name -password password < $NCHOME/precision/scripts/create_sae_automation.sql d. Log on to the aggregation layer ObjectSerers and enable the SAE triggers using the following command: 152 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

167 ALTER TRIGGER GROUP sae SET ENABLED TRUE; e. Optional: If you hae an aggregation layer ObjectSerer failoer pair, update the mapping for the aggregation layer ObjectSerers by editing the NCHOME/omnibus/etc/AGG_GATE.map file and adding CREATE statements for the tables that were just created by the create_sae_automation.sql script at the bottom of the file. For example, the CREATE statement might look like the following (note that the exact table definitions should be copied from the script to aoid errors): CREATE MAPPING EntitySericeMap ( NmosEntityId ON INSERT ONLY, SericeEntityId ON INSERT ONLY, NmosDomainName ON INSERT ONLY ); CREATE MAPPING SericeDetailsMap ( SericeEntityId ON INSERT ONLY, Type ON INSERT ONLY, Name ON INSERT ONLY, Customer NmosDomainName ON INSERT ONLY ); f. Update the Gateway for the aggregation ObjectSerers. Edit the NCHOME/omnibus/etc/AGG_GATE.tblrep.def file and add the following REPLICATE statements for the tables that were just created by the create_sae_automation.sql script to the bottom of the file. REPLICATE ALL FROM TABLE precision.entity_serice USING MAP EntitySericeMap INTO precision.entity_serice ; REPLICATE ALL FROM TABLE precision.serice_details USING MAP SericeDetailsMap INTO precision.serice_details ; 5. Configure any display layer ObjectSerers: a. Run the NCHOME/precision/scripts/drop_sae_automation.sql script to remoe existing tables. To run the script, use a command line similar to the following: UNIX $NCHOME/omnibus/bin/nco_sql -serer objectserer_name -user user_name -password password < $NCHOME/precision/scripts/drop_sae_automation.sql b. Run the NCHOME/precision/scripts/create_sae_automation.sql script to install the SAE trigger and add the tables, including the NmosDomainName column. To run the script, use a command line similar to the following: UNIX $NCHOME/omnibus/bin/nco_sql -serer objectserer_name -user user_name -password password < $NCHOME/precision/scripts/create_sae_automation.sql c. Log on to the Display ObjectSerers and disable the SAE triggers to preent them running on the display layer using the following command: ALTER TRIGGER GROUP sae SET ENABLED FALSE; d. Ensure the precision.entity_serice and precision.serice_details tables in the display layer ObjectSerer hae the same schema as those in the aggregation layer ObjectSerers. e. Optional: If you hae a display layer ObjectSerer failoer pair, update the mapping for the display layer ObjectSerers. Edit the NCHOME/omnibus/etc/ A_TO_D_GATE.map files and add CREATE statements for the tables that were just created by the create_sae_automation.sql script at the bottom of the Chapter 4. Configuring 153

168 file. This mapping must be identical to the mapping in the aggregation layer gateway. If you later change the mapping in the bi-directional gateway for the aggregation layer ObjectSerers, you must replicate those changes here. CREATE MAPPING EntitySericeMap ( NmosEntityId ON INSERT ONLY, SericeEntityId ON INSERT ONLY, NmosDomainName ON INSERT ONLY ); CREATE MAPPING SericeDetailsMap ( SericeEntityId ON INSERT ONLY, Type ON INSERT ONLY, Name ON INSERT ONLY, Customer NmosDomainName ON INSERT ONLY ); f. Update the Gateway for the display layer ObjectSerers. Edit the NCHOME/omnibus/etc/A_TO_D_GATE.tblrep.def file and add the following REPLICATE statements for the tables that were just created by the create_sae_automation.sql script to the bottom of the file. This mapping must be identical to the mapping in the aggregation layer gateway. If you later change the mapping in the bi-directional gateway for the aggregation layer ObjectSerers, you must replicate those changes here. REPLICATE ALL FROM TABLE precision.entity_serice USING MAP EntitySericeMap INTO precision.entity_serice ; REPLICATE ALL FROM TABLE precision.serice_details USING MAP SericeDetailsMap INTO precision.serice_details ; 6. Delete all preious Network Manager eents from the alerts.status table in the ObjectSerers using the appropriate SQL command. 7. Restart the ObjectSerer Gateways. 8. Restart the ncp processes, as described in Starting and stopping processes. Changing the Tioli Netcool/OMNIbus Web GUI data source name To connect to a different Web GUI data source than the one specified during installation, change the data source name. To connect to a different data source than the one that you specified during installation: 1. Edit the NCHOME/etc/precision/ModelNcimDb.cfg file. 2. Change the WebTopDataSource property to the new data source name. 3. Restart the ncp_model process. 154 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

169 Tioli Netcool/OMNIbus Web GUI data sources: A data source is another term for an ObjectSerer or ObjectSerer failoer pair used by the Web GUI for eent information. The Tioli Netcool/OMNIbus Web GUI was known as Netcool/Webtop in ersions 2.2 and below. Some deployments contain many ObjectSerers, and the Web GUI can contain eents from seeral different ObjectSerers. You can configure the Web GUI for one data source during installation. After installation, you might need to change this data source, or add new data sources. Data sources and network topology To display deice status, the Network Views and the Hop View correlate the topology record for a deice with any eents on that deice. To perform this correlation, the Web applications must hae access to the name of each data source used by the Web GUI. Data sources and the NCIM database Information about the Web GUI data sources is held in the database table ncim.domainmgr in the NCIM topology database. For more information on configuring the Web GUI data sources, see the IBM Tioli Netcool/OMNIbus Web GUI Administration and User's Guide. Configuring topology eent types for the Actie Eent List (AEL) To integrate the topology iews and filtered AEL iews, the iew name and type must match. If you change the defaults in the AEL, you must configure the name and type in Network Manager. In a filtered AEL iew, you can configure the name and iew type. If you change the iew name and type from the default alues of Default and global, then the AEL cannot communicate with the Network Views and right-click tools. If the default alues hae been changed, you must change the alues on the Network Manager serer to match. To edit the iew name and type used for communicating with the AEL, complete the following steps: 1. Back up and edit the file topoiz.properties. 2. Change the alues of the following properties: # AEL iew descriptions. topoiz.webtop.iew.name=default topoiz.webtop.iew.type=global Chapter 4. Configuring 155

170 Adding eent fields To use Tioli Netcool/OMNIbus ersion 7.1, you must add additional database fields to the alerts.status table and to any Tioli Netcool/OMNIbus gateway map files. Tip: You do not need to perform this task if you are using Tioli Netcool/OMNIbus ersion 7.2 or later. The required fields are as follows: NmosDomainName The name of the Network Manager domain that is managing the eent. By default, this field is only populated for eents which are generated by Network Manager polls. To populate this field for other eent sources such as the ones from Tioli Netcool/OMNIbus probes, you hae to modify the rules files. NmosEntityId A unique numerical ID which identifies the topology entity that the eent has been associated with. This field is similar to the NmosObjInst field, but contains more detailed information. For example, it can include the ID of an interface within a deice. NmosManagedStatus The managed status of the network entity the eent was raised for. When a network entity is unmanaged, the Network Manager polls are suspended, and eents from other sources are tagged as unmanaged. This field allows you to filter out eents from unmanaged entities. BSM_Identity The unique identifier of the resource from where the eent originates, and is used to correlate the eent to that resource in IBM Tioli Business Serice Manager (TBSM). NmosEentMap The eent map name and optional precedence for the eent, which indicates how Network Manager should process the eent; for example, PrecisionMonitorEent.910. The optional precedence number can be concatenated to the end of the alue, following a period (.). If the precedence is not supplied, it is set to 0. Note: This alue can be oerridden by an explicit insertion into the Eent Gateway config.precedence table, which proides the same data. To add the fields to the alert.status database table, run the following SQL script against each ObjectSerer in your deployment: UNIX $NCHOME/omnibus/bin/nco_sql -serer objectserer_name -user username -password password < $NCHOME/precision/scripts/ncp_configure_omnibus.sql For more information about administering Tioli Netcool/OMNIbus, see the IBM Tioli Netcool/OMNIbus Administration Guide. 156 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

171 Configuring the JRE for FIPS mode (UNIX and Linux) To configure the Tioli Netcool/OMNIbus JRE for FIPS operation, change the configuration of the security properties file. You can also download and add policy files to use enhanced encryption algorithms. Configuration file changes Make the following configuration changes to the security properties file: 1. Open the $NCHOME/platform/arch/jre_1.6.7/jre/lib/security/jaa.security file for editing, where arch represents your operating system directory; for example, solaris2. 2. Edit the file as follows: In the List of proiders and their preference orders section, add the following lines: security.proider.1=com.ibm.fips.jsse.ibmjssefipsproider and security.proider.2=com.ibm.crypto.fips.proider.ibmjcefips. For all other proiders, increment the number by two, as shown in the following table, for your operating system: Operating system AIX and Linux Solaris and HP-UX Required entries security.proider.1=com.ibm.fips.jsse.ibmjssefipsproider security.proider.2=com.ibm.crypto.fips.proider.ibmjcefips security.proider.3=com.ibm.jsse2.ibmjsseproider2 security.proider.4=com.ibm.crypto.proider.ibmjce security.proider.5=com.ibm.security.jgss.ibmjgssproider security.proider.6=com.ibm.security.cert.ibmcertpath security.proider.7=com.ibm.security.sasl.ibmsasl security.proider.8=com.ibm.xml.crypto.ibmxmlcryptoproider security.proider.9=com.ibm.xml.enc.ibmxmlencproider security.proider.10=org.apache.harmony.security.proider.policyproider security.proider.11=com.ibm.security.jgss.mech.spnego.ibmspnego security.proider.12=com.ibm.security.cmskeystore.cmsproider security.proider.1=com.ibm.fips.jsse.ibmjssefipsproider security.proider.2=com.ibm.crypto.fips.proider.ibmjcefips security.proider.3=com.ibm.security.jgss.ibmjgssproider security.proider.4=sun.security.proider.sun security.proider.5=com.ibm.crypto.proider.ibmjce security.proider.6=com.ibm.jsse2.ibmjsseproider2 security.proider.7=com.ibm.security.cert.ibmcertpath security.proider.8=com.ibm.security.sasl.ibmsasl security.proider.9=com.ibm.xml.crypto.ibmxmlcryptoproider security.proider.10=com.ibm.xml.enc.ibmxmlencproider security.proider.11=com.ibm.security.jgss.mech.spnego.ibmspnego security.proider.12=com.ibm.security.cmskeystore.cmsproider Set the default key and trust manager factory algorithms for the jaax.net.ssl package: ssl.keymanagerfactory.algorithm=ibmx509 ssl.trustmanagerfactory.algorithm=ibmx509 Set the default SSLSocketFactory and SSLSererSocketFactory proider implementations for the jaax.net.ssl package: ssl.socketfactory.proider=com.ibm.jsse2.sslsocketfactoryimpl ssl.serersocketfactory.proider=com.ibm.jsse2.sslserersocketfactoryimpl 3. Sae and close the file. Chapter 4. Configuring 157

172 Enhanced encryption algorithms To enable strong encryption, you need to download and install policy files that allow this feature, from IBM deeloperworks. This inoles acceptance of licensing terms. The steps to enable strong encryption are as follows: 1. Go to the deeloperworks Jaa Technology Security Web page at 2. Click the Jaa SE 6 link. (The files are the same for JRE 1.5.n.) 3. Scroll down on the resulting page and click the IBM SDK Policy files link. 4. If you already hae an IBM ID and password, click the Sign in link. Otherwise, click the Register here link to create an ID. 5. On the "Sign in" page, supply your IBM ID and password. This takes you to the "Unrestricted JCE policy files for SDK 1.4" page. 6. Select Unrestricted JCE Policy files for SDK for all newer ersions and click Continue. 7. Scroll down to the License section of the resulting page and click the View license link to see the licensing terms for the download. 8. If the licensing terms are acceptable, select I agree and click the I confirm link. If the terms are not acceptable, you will not be able to enable strong encryption and should click I cancel. 9. Click the Download now link to download the unrestricted.zip file. 10. Extract the local_policy.jar and US_export_policy.jar files from the unrestricted.zip archie. 11. Sae these two files to the $NCHOME/platform/arch/jre_1.6.7/jre/lib/ security directory, replacing the existing files of the same names. 12. Update the policy files on each computer, and optionally run tests. Installing and configuring probes If you did not install Tioli Netcool/OMNIbus as part of the Network Manager installation, and you are using an existing Tioli Netcool/OMNIbus installation, you must configure certain probes. To ensure that your Tioli Netcool/OMNIbus installation receies eents from the network, you must configure the releant Tioli Netcool/OMNIbus probes. At a minimum you must install and configure the SNMP probe (also known as the mttrapd probe). You can use the ConfigOMNI script, for more information, see Configuring an existing Tioli Netcool/OMNIbus installation on a remote serer on page 41. For more information about probe installation and configuration, see the releant probe reference guide, aailable from the Information Center at com.ibm.tioli.namomnibus.doc/welcome_ptsm.htm. 158 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

173 Installing the Knowledge Library If you did not install Tioli Netcool/OMNIbus as part of the Network Manager installation, and you are using an existing Tioli Netcool/OMNIbus installation, you must install the Netcool/OMNIbus Knowledge Library. The Netcool/OMNIbus Knowledge Library is a set of rules files written to a common standard and is aailable with your Tioli Netcool/OMNIbus installation. You can use the ConfigOMNI script to install the library, see ConfigOMNI command-line options on page 43. For more information, see the Netcool/OMNIbus Knowledge Library Release Notes. Tioli Netcool/OMNIbus integration reference Read about settings for additional interaction between Network Manager and Tioli Netcool/OMNIbus. Network Manager eent categories: The eents that are raised by Network Manager fall into two categories: eents about the network being monitored and eents about Network Manager processes. These eents are stored in the Tioli Netcool/OMNIbus ObjectSerer. The Probe for Tioli Netcool/OMNIbus (nco_p_ncpmonitor) is used to process and forward the eent data to the alerts.status table in the ObjectSerer. The following figure shows the flow of eents from Network Manager to the ObjectSerer. Chapter 4. Configuring 159

174 Eent List ObjectSerer [alerts.status table] Web GUI Serer Actie Eent List Network eents Probe for Tioli Netcool/OMNIbus nco_p_ncpmonitor Network Manager status eents ncp_poller Network Manager processes Network Figure 8. Flow of eents from Network Manager to Tioli Netcool/OMNIbus Network Manager network eents: The Polling engine, ncp_poller, generates eents about the state of the network. These eents can be used to identify network problems, and are configurable by using the Network Polling GUI (go to Administration > Network > Network Polling). These eents are known as network eents and hae the alerts.status AlertGroup field alue of ITNM Monitor. Each network eent is raised on a single entity, such as an interface or a chassis, and the eent data is dependent on the type of poll. When network eents are forwarded to the ObjectSerer for insertion into the alerts.status table, they are allocated an AlertGroup alue of ITNM Monitor. An unlimited set of eent identifiers is aailable for network eents. Eents that are generated when an SNMP poll fails are specifically allocated an EentID alue of NmosSnmpPollFail in the alerts.status table. Network eents in the ObjectSerer are pulled back into Network Manager through the Eent Gateway to perform eent enrichment, including root cause analysis. Related reference: alerts.status fields used by Network Manager on page 172 The alerts.status table in the ObjectSerer contains status information about problems that hae been detected by probes. 160 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

175 Network Manager status eents: Network Manager can generate eents that show the status of arious Network Manager processes. These eents are known as Network Manager status eents and hae the alerts.status AlertGroup field alue of ITNM Status. When these status eents are forwarded to the ObjectSerer for insertion into the alerts.status table, they are allocated an AlertGroup alue of ITNM Status. Status eent types A set of eent identifiers is used to identify Network Manager status eents by type. The following list identifies the EentId alues that are inserted in the alerts.status table, and describes how each associated status eent is generated. ItnmDatabaseConnection This type of eent is generated to indicate loss of connection to NCIM. This eent is generated by the managed status polling thread in the ncp_model process. The raising of this eent depends on the time period configured in the managed status polling interal in model. A problem eent is raised if the connection is lost, and a corresponding resolution eent is raised if the connection is restored, or at startup to clear any failures from a preious operation. This eent type allows the backup domain to take oer when failoer is configured. The irtual domain process reacts to this eent as defined in the filter for NCIM in the NCHOME/etc/precision/VirtualDomainSchema.cfg file. ItnmDiscoAgentStatus This type of eent is generated by ncp_disco when a discoery agent transitions to a new state. At the end of a discoery, an information eent is forwarded to the ObjectSerer, for each agent that was used during the discoery. You can use this information to identify the state of each agent. In the alerts.status table, the LocalPriObj field is used to store the name of the agent. Discoery agent eents in the ObjectSerer are oerwritten when a subsequent discoery is run. ItnmDiscoFinderStatus This type of eent is generated by ncp_disco when a discoery finder transitions to a new state. At the end of a discoery, an information eent is forwarded to the ObjectSerer, for each finder that was used during the discoery. You can use this information to identify which finders are running and their state. In the alerts.status table, the LocalPriObj field is used to store the name of the finder. Discoery finder eents in the ObjectSerer are oerwritten when a subsequent discoery is run. ItnmDiscoPhase This type of eent is generated by ncp_disco when the discoery process transitions to a new phase. At the end of the discoery, fie information eents should be present in the ObjectSerer, to show the looped transitions from phase 0 (standby) to phases 1, 2, and 3 (data collection) to phase -1 (data processing). An eent is raised for each of the following phase changes in a single discoery: Chapter 4. Configuring 161

176 0to1 1to2 2to3 3to-1-1 to 0 You can use this information to determine the length of each phase. In the alerts.status table, the LocalPriObj field is used to store the phase to which the discoery is transitioning, and the LocalSecObj field stores the preious phase of the discoery. Tip: The string alues for the phases are also shown in the discoery log file when the ncp_disco process is run in debug mode. Discoery phase eents in the ObjectSerer are oerwritten when a subsequent discoery is run. ItnmDiscoStitcherStatus The discoery process is made up of a data collection stage and a data processing stage, during which the topology is created. ItnmDiscoStitcherStatus eents are generated by the Discoery engine, ncp_disco, when a major phase is reached in the data processing stage. At the end of the discoery, an information eent is forwarded to the ObjectSerer, for each major discoery stitcher that was used during the discoery. You can use this information to identify what phase in the data processing stage the discoery is in. In the alerts.status table, the LocalPriObj field is used to store the name of the stitcher corresponding to this phase. ItnmDiscoStitcherStatus eents are raised when the following stitchers begin executing: BuildFinalEntityTable BuildContainment BuildLayers MergeLayers PostLayerProcessing Subsequently eents are raised during the topology creation phase when the following stitchers are run. If ncp_disco is using the dncim database: PopulateDNCIM Discoery stitcher eents in the ObjectSerer are oerwritten when a subsequent discoery is run. ItnmEntityCreation If configured in the $NCHOME/etc/precision/ModelSchema.cfg file, this type of information eent is generated by ncp_model, for each new chassis or IP interface entity (EntityType = 1) that is inserted into the NCIM database. You can configure ModelSchema.cfg by setting the alue of the RaiseEntityEent column to 1 in the INSERT statement for the model.config table. For example: create table model.config ( LingerTime int not null primary key, // default alue 3 (discoeries) RaiseEntityEent int type boolean not null, // default alue 0 ( off ) DiscoeryUpdateMode int not null, // default alue 0 - full discoery, 162 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

177 unique(lingertime) ); insert into model.config alues (3, 1, 0); // 1 - partial Note: For the configuration changes to take effect and enable the eents, the ncp_model process must be restarted. The process reads the configuration settings at start-up. ItnmEntityDeletion If configured in the $NCHOME/etc/precision/ModelSchema.cfg file, this type of information eent is generated by ncp_model, for each chassis or IP interface entity (EntityType = 1) that is deleted from the NCIM database. You can configure ModelSchema.cfg by setting the alue of the RaiseEntityEent column to 1 in the INSERT statement for the model.config table, as shown in the preceding description for the ItnmEntityCreation EentId. ItnmFailoer This type of eent is generated by ncp_irtualdomain when a Network Manager domain within a failoer pair fails oer or fails back. A problem eent is generated when failoer occurs and a resolution eent is generated on failback. In the alerts.status table, the Summary field description indicates whether the domain is the primary or backup, and whether it is in an actie or a standby mode. ItnmFailoerConnection This type of eent is generated by ncp_irtualdomain to indicate when the backup domain in a failoer pair connects to, or disconnects from, the primary domain. When Network Manager runs in failoer mode, a resolution eent is generated when the primary and backup domains set up their TCP socket connection. This socket connection is required to transfer the topology updates from the primary domain because the discoery process (ncp_disco) does not run in the backup domain. If the connection is subsequently lost, a problem eent is generated. Note: The status of the connection does not determine whether failoer is triggered. Failoer is triggered only when health check eents are transferred (ia the ObjectSerer) across domains, and proided a socket connection has, at some point, been established. ItnmHealthChk Health check eents goern Network Manager failoer. Each domain in the failoer pair generates health check resolution eents while that domain is healthy. Health check problem eents for a domain can be generated in two ways: By the local domain: The local domain detects a failure of one of its processes, as configured in the $NCHOME/etc/precision/ VirtualDomainSchema.cfg file. By the remote domain: One domain detects that the other domain has not generated a health check resolution eent in the configured amount of time, and generates a synthetic health check problem eent on behalf of the remote domain. Chapter 4. Configuring 163

178 When a health check problem eent is generated for the primary domain, failoer is initiated, and the backup domain becomes actie. Health check eents were preiously allocated an EentID alue of NcpHealthChk. For compatibility with earlier ersions of Network Manager, you can substitute NcpHealthChk in place of ItnmHealthChk in the probe rules file. Note: Health check eents are handled by the Network Manager Eent Gateway, which requires the Node alue to be the domain to which the eent refers. This need not be the domain raising the eent, since one domain can raise failure eents on behalf of the other. ItnmMaintenanceState If configured in the $NCHOME/etc/precision/ModelSchema.cfg file, this type of eent is generated by the Topology manager, ncp_model, for maintenance status changes to a chassis or an IP interface. You can configure ModelSchema.cfg by setting the alue of the RaiseEntityEent column to 1 in the INSERT statement for the model.config table, as shown in the preceding description for the ItnmEntityCreation eent. A problem eent is generated when the chassis or IP interface entity is in maintenance, and a resolution eent is generated when the entity is out of maintenance. Note: An indiidual interface eent is sent only if the change does not apply at the chassis leel; when a deice changes, a chassis eent and a series of interface eents are not collectiely generated. ItnmSericeState This type of eent is generated when a process starts or ends, and signifies whether a process has failed to start or has stopped during runtime. (Note that process state eents are not generated when processes are stopped at system shutdown.) A resolution eent is generated when ncp_ctrl starts a process. If a process fails to start or if it stops during runtime, a problem eent is generated. In the alerts.status table, the Summary field description includes the process name, the PID, and an indication of whether the process has: Started (and successfully initialized) Stopped (that is, it has been deleted from the ncp_ctrl database table named serices.intray) Terminated (that is, it stopped, but will be restarted by ncp_ctrl) Failed to start Failed and will not be restarted (that is, it stopped and the number of retries configured for the process has been exceeded) ItnmTopologyUpdated This type of information eent is generated by ncp_model when the update of the NCIM topology database is completed at the end of a discoery cycle. This information is useful if you intend to program scripts or procedures to run after the NCIM database is updated. Note: If the feedback option is on, or large subnets are pinged, there might be multiple discoery cycles and thus multiple eents of this type, one 164 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

179 eent for each discoery cycle. To determine if discoery has finally finished, the following OQL query can be made to the Ping Finder serice: select * from pingfinder.status where m_completed <> 1; This query looks for any subnets that the Ping finder is still pinging. If there are no outstanding ping sweeps and the discoery is in phase 0, this means that the discoery is complete. Related concepts: About failoer on page 241 In your Network Manager enironment, a failoer architecture can be used to configure your system for high aailability, minimizing the impact of computer or network failure. Related tasks: Enabling failoer on page 241 You can enable failoer in your Network Manager enironment to ensure that the different components are kept running and aailable. Related reference: alerts.status fields used by Network Manager on page 172 The alerts.status table in the ObjectSerer contains status information about problems that hae been detected by probes. Configuration of the Probe for Tioli Netcool/OMNIbus: The Probe for Tioli Netcool/OMNIbus (nco_p_ncpmonitor) acquires and processes the eents that are generated by Network Manager polls and processes, and forwards these eents to the ObjectSerer. The Probe for Tioli Netcool/OMNIbus is installed in the $NCHOME/probes/arch directory, where arch represents an operating system directory. You can configure the probe by using its configuration files, which are as follows: Properties file: nco_p_ncpmonitor.props Rules file: nco_p_ncpmonitor.rules Note: The executable file (or nco_p_ncpmonitor command) for the probe is also installed in the $NCHOME/probes/arch directory. The probe is, howeer, configured to run under the domain process controller CTRL, by default, and the nco_p_ncpmonitor command should be run manually only for troubleshooting purposes. The eents raised in Network Manager are domain-specific. When Network Manager runs in failoer mode, the probe uses the irtual domain name by default, proided the name is configured in the $NCHOME/etc/precision/ ConfigItnm.cfg file. For more information about probe concepts, see the IBM Tioli Netcool/OMNIbus Probe and Gateway Guide in the Tioli Netcool/OMNIbus information centre at com.ibm.tioli.nam.doc/welcome_ob.htm. Chapter 4. Configuring 165

180 Related tasks: Configuring failoer using the ConfigItnm.cfg file on page 270 When you use the $NCHOME/etc/precision/ConfigItnm.DOMAIN.cfg file to configure failoer, the Network Manager processes will read the file on startup to identify whether they are running in the primary or backup domain. About the nco_p_ncpmonitor.props file: The $NCHOME/probes/arch/nco_p_ncpmonitor.props file defines the enironment in which the Probe for Tioli Netcool/OMNIbus runs. The properties file is formed of name-alue pairs that are separated by a colon. The default properties file lists a subset of the properties that the probe supports; these properties are commented out with a number sign (#) at the beginning of the line. The standard set of common probe properties, which are applicable for the ersion of Tioli Netcool/OMNIbus being run, can be specified for the Probe for Tioli Netcool/OMNIbus, where releant. A suggested practice for changing the default alues of the properties is that you add a name-alue line for each required property at the bottom of the file. To specify a property, ensure that the line is uncommented and then modify the alue as required. String alues must be enclosed in quotation marks; other alues do not require quotation marks. For example: Serer : "VIRTUAL" RulesFile : "$NCHOME/probes/solaris2/nco_p_ncpmonitor.rules" Buffering : 1 BufferSize : 15 For troubleshooting purposes, you can alternatiely configure probe properties from the command line by running the nco_p_ncpmonitor command with the releant command-line options. For information about the properties that are common to probes, see the IBM Tioli Netcool/OMNIbus Probe and Gateway Guide in the Tioli Netcool/OMNIbus information centre at topic/com.ibm.tioli.nam.doc/welcome_ob.htm. About the nco_p_ncpmonitor.rules file: The $NCHOME/probes/arch/nco_p_ncpmonitor.rules file defines how the Probe for Tioli Netcool/OMNIbus should process Network Manager eent data to create a meaningful Tioli Netcool/OMNIbus eent. nco_p_ncpmonitor.rules configuration reference: The rules file maps Network Manager eent data to ObjectSerer fields, and can be used to customize the behaior of the probe. Knowledge of the Tioli Netcool/OMNIbus probe rules syntax is required for rules file configuration. The probe uses tokens and elements, and applies rules, to transform Network Manager eent source data into a format that the ObjectSerer can recognize. The raw eent source data is conerted to tokens, which are then parsed into elements. The rules file is used to perform conditional processing on the elements, and to map them to ObjectSerer alerts.status fields. In the rules file, elements are 166 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

181 identified by the $ symbol and alerts.status fields are identified by symbol. The rules file configuration maps elements to fields, as shown in the following sample In this identifies the alerts.status field, and $Description identifies the Network Manager input field. Where the Network Manager ExtraInfo field is used with nested fields to store additional data on entities (for example, ExtraInfo->ifIndex), these fields are aailable in the following format in the rules file: $ExtraInfo_ariable Where ariable represents a Management Information Base (MIB) ariable (for example, ifindex), or other data (for example, column names in NCIM tables). MIB ariables are specified in mixed case characters, and other data, in uppercase characters. For example: $ExtraInfo_ifIndex $ExtraInfo_MONITOREDENTITYID To configure the rules file for the Probe for Tioli Netcool/OMNIbus, it is necessary to hae an understanding of: The Network Manager eent source data that is aailable for use in the probe rules file The set of alerts.status fields that can be populated with eent data from Network Manager The data mapping between the Network Manager and alerts.status fields For information about the syntax used in probe rules files, see the IBM Tioli Netcool/OMNIbus Probe and Gateway Guide in the Tioli Netcool/OMNIbus information centre at topic/com.ibm.tioli.nam.doc/welcome_ob.htm. Example of rules file processing: This example shows how source data from Network Manager is processed by the rules file to generate the output data that is inserted in the alerts.status table. The following sample code shows a Network Manager eent data record that is passed to the Probe for Tioli Netcool/OMNIbus for processing. In this record, a resolution eent was created when ncp_ctrl started the ncp_store process. { EentName= ItnmSericeState ; Seerity=1; EntityName= BACKUP ; Description= ncp_store process [15299] has started ; ExtraInfo={ EVENTTYPE=2; SOURCE= ncp_ctrl ; ALERTGROUP= ITNM Status ; EVENTMAP= ItnmStatus ; SERVICE= ncp_store ; PID=15299; }; } Chapter 4. Configuring 167

182 The following excerpt from the probe rules file shows the syntax used to process and map these input fields to alerts.status fields: # # populate some standard fields = = = = = = = $ExtraInfo_SOURCE if (exists($extrainfo_accessipaddress)) = $ExtraInfo_ACCESSIPADDRESS } else = $EntityName } # # Stamp the eent with the name of its originating domain = = = 8000 # # populate fields for RCA # # Now set the AlertKey and Identifier # if (match(@alertgroup, "ITNM Status")) { switch ($EentName) { case case = $ExtraInfo_SERVICE... case } } # # Both the Identifier and the AlertKey contain the domain name. This ensures # that in a multi-domain setup, eents are handled on a per-domain basis # # # Include the LocalPriObj in the AlertKey or the link-downs on # all interfaces will cleared by a link-up on any interface = $EntityName + "->" + $EentName } # # Set up deduplication identifier and include the LocalPriObj # so we can correctly handle de-duplication of eents raised on interfaces = $EntityName + "->" + $EentName When rules file processing is complete, the output data that is forwarded to the ObjectSerer takes the following form: 168 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

183 CMonitorProbeApp::ProcessStatusEent { AlertGroup= ITNM Status ; EentId= ItnmSericeState ; Type=2; Seerity=1; Summary= ncp_store process [15299] has started ; Node= BACKUP ; NmosDomainName= PRIMARY ; LocalNodeAlias= BACKUP ; LocalPriObj= ncp_store ; LocalRootObj= ; RemoteNodeAlias= ; AlertKey= BACKUPncp_store->ItnmSericeStateVIRTUAL ; Identifier= BACKUPncp_store->ItnmSericeState2VIRTUAL ; Class=8000; Agent= ncp_ctrl ; LastOccurrence= ; } Based on the rules file processing in this example, it can be seen that the Network Manager input fields map to the alerts.status fields as follows: Network Manager field EentName Seerity EntityName Description ExtraInfo->EVENTTYPE ExtraInfo->SOURCE ExtraInfo->ALERTGROUP ExtraInfo->EVENTMAP ExtraInfo->SERVICE alerts.status field EentId Seerity Node Summary Type Agent AlertGroup NmosEentMap LocalPriObj Related reference: alerts.status fields used by Network Manager on page 172 The alerts.status table in the ObjectSerer contains status information about problems that hae been detected by probes. Network Manager eent data fields: When eents are generated in Network Manager, the eent data is inserted into a number of fields (or columns) in the Network Manager tables. Although each eent uses only a subset of the possible fields, a number of fields are common to all eent types. The following table lists all the Network Manager field names that are aailable for use in the probe rules file, and describes the eent data stored in each field. The table also identifies which of the Network Manager fields are common to all eents, and therefore always aailable in the rules file. Table 40. Network Manager fields that populate eents Network Manager field name Field content Always aailable? Description A brief description of the eent. Yes Chapter 4. Configuring 169

184 Table 40. Network Manager fields that populate eents (continued) Network Manager field name Field content Always aailable? Domain The current domain. EntityName If Network Manager is configured for failoer mode, this will be the primary domain. For network eents, this is the entityname field from the NCIM entitydata table for the entity against which the eent is raised. Yes (proided the map file is not modified) Yes EentName ExtraInfo_ACCESSIPADDRESS ExtraInfo_AGENT ExtraInfo_ALERTGROUP ExtraInfo_ENTITYCLASS ExtraInfo_ENTITYTYPE ExtraInfo_LocalPriObj ExtraInfo_EVENTTYPE ExtraInfo_FINDER ExtraInfo_ifIndex For status eents, this is always the name of the domain about which the eent is generated. The eent identifier. For example, ItnmDiscoPhase. If the main node or interface entity identified by the EntityName input field has a directly-accessible IP address (the accessipaddress field from the NCIM interface or chassis tables), then it is supplied here. Applicable to network eents only. The agent responsible for a discoery agent (ItnmDiscoAgentStatus) eent. The alert group of the eent. For Network Manager status eents, the alert group is ITNM Status, and for network eents, the alue is ITNM Monitor. The name of class assigned to the entity, as identified the NCIM entityclass and classmembers tables. The type of the entity, as defined in the NCIM entitytype table. Proides a alue for the LocalPriObj field in the alerts.status record. This field has the same alue as the deprecated ExtraInfo_EentSnmpIndex field, except that it is prefixed by an identifier for the MIB entity being polled; for example ifentry, bgppeerentry. The type of the eent raised by Network Manager. The alues are as follows: 1: Problem 2: Resolution 13: Information The finder responsible for a discoery finder (ItnmDiscoFinderStatus) eent. For eents raised against an interface with an ifindex alue in the NCIM interface table, that alue is gien here. Applicable only to network eents against interfaces. Yes No Yes (for ItnmDiscoAgentStatus eents) Yes Yes (for network and ItnmEntityCreation eents) Yes (for network eents) Yes (for network eents) Yes Yes (for ItnmDiscoFinderStatus eents) No 170 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

185 Table 40. Network Manager fields that populate eents (continued) Network Manager field name Field content Always aailable? ExtraInfo_IFALIAS For eents raised against interfaces, this field contains the ifalias alue, if known. Applicable only to network interface polls. No ExtraInfo_IFDESCR ExtraInfo_IFNAME ExtraInfo_IFTYPESTRING ExtraInfo_MAINNODEADDRESS ExtraInfo_MAINNODEENTITYID ExtraInfo_MAINNODEENTITYNAME ExtraInfo_MONITOREDENTITYID ExtraInfo_MONITOREDINSTID ExtraInfo_NEWPHASE ExtraInfo_OLDPHASE ExtraInfo_POLICYNAME ExtraInfo_PID ExtraInfo_REMOTEDOMAIN ExtraInfo_sysContact ExtraInfo_sysLocation For eents raised against interfaces, this field contains the ifdescr alue, if known. Applicable only to network interface polls. For eents raised against interfaces, this field contains the ifname alue, if known. Applicable only to network interface polls. For eents raised against interfaces, this field contains the string representation of the iftype alue. Applicable only to network interface polls. The management interface of the main node containing the entity, as identified by the accessipaddress field of the NCIM chassis table. Applicable only to network and ItnmEntityCreation eents. The entityid field from the NCIM entitydata table for the main node, as identified by the accessipaddress field of the NCIM chassis table. Applicable only to network eents. The entityname field from the NCIM entitydata table for the main node, as identified in NCIM. Applicable only to network eents. The entityid field from the NCIM entitydata table for the entity against which the eent is raised. Applicable only to network and ItnmEntityCreation eents. A record in the ncpolldata.monitoredinstance table. The discoery phase that has started. Applicable only to discoery phase (ItnmDiscoPhase) eents. The discoery phase that has completed. Applicable only to discoery phase (ItnmDiscoPhase) eents. The name of the polling policy that resulted in the eent. The process ID of the affected Network Manager serice. Applicable only to ItnmSericeState eents. The name of the remote domain. Applicable only to ItnmFailoerConnection eents. If aailable, the syscontact alue is gien for ItnmEntityCreation eents only. If aailable, the syslocation alue is gien for ItnmEntityCreation eents only No No No Yes (for network eents) Yes (for network eents) Yes (for network eents) No No Yes (for discoery phase eents) Yes (for discoery phase eents) Yes (for network eents) Yes (for serice state eents) Yes (for failoer connection eents) No No Chapter 4. Configuring 171

186 Table 40. Network Manager fields that populate eents (continued) Network Manager field name Field content Always aailable? ExtraInfo_sysObjectId If aailable, the sysobjectid alue is gien No for ItnmEntityCreation eents only ExtraInfo_SERVICE The name of the affected Network Manager serice. Applicable only to ItnmSericeState eents. Yes (for serice state eents) ExtraInfo_SNMPSTATUS A numerical SNMP status code. Yes (for NmosSnmpPollFail eents) ExtraInfo_SNMPSTATUSSTRING ExtraInfo_SOURCE ExtraInfo_STITCHER Seerity A human-readable indication of the SNMP failure state. The name of the process from which the eent originated. The stitcher responsible for a discoery stitcher (ItnmDiscoStitcherStatus) eent. The seerity leel of the eent. The seerity is a non-zero alue. Yes (for NmosSnmpPollFail eents) Yes Yes (for ItnmDiscoStitcherStatus eents) Yes Related reference: Network Manager network eents on page 160 The Polling engine, ncp_poller, generates eents about the state of the network. These eents can be used to identify network problems, and are configurable by using the Network Polling GUI (go to Administration > Network > Network Polling). These eents are known as network eents and hae the alerts.status AlertGroup field alue of ITNM Monitor. Network Manager status eents on page 161 Network Manager can generate eents that show the status of arious Network Manager processes. These eents are known as Network Manager status eents and hae the alerts.status AlertGroup field alue of ITNM Status. alerts.status fields used by Network Manager: The alerts.status table in the ObjectSerer contains status information about problems that hae been detected by probes. A subset of the standard alerts.status fields is populated with Network Manager eent data. Additionally, a set of dedicated alerts.status fields are resered to hold data that is specific to Network Manager. The dedicated alerts.status field names are identifiable by the prefix Nmos. The following table describes the alerts.status fields that are populated by Network Manager fields. Some of these alerts.status fields are allocated default alues from within the probe rules file. (Aoid modifying these default alues.) 172 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

187 Table 41. alerts.status fields used by Network Manager alerts.status field Data type Description Agent archar(64) The name of the process that generated the eent. You can use this field to filter an AEL to display only eents of a specific type; for example, only discoery eents (with a alue of ncp_disco). AlertGroup archar(255) Used to group eents by type. Values supplied by default from Network Manager eents are either ITNM Monitor for network eents, or ITNM Status for status eents. AlertKey archar(255) A text string concatenating seeral elements relating to the eent. Elements can include the eent ID, domain, phase, and process name. Allows problem and resolution eents to be matched. Class integer The alert class asigned to the Probe for Tioli Netcool/OMNIbus. EentId archar(255) The type of eent (for example, SNMPTRAP-linkDown). The Eent Gateway uses this alue to look up the eent map, and to determine the precedence of eents. ExpireTime integer The expiry time of the eent in the database. Not currently used by Network Manager. FirstOccurrence time A timestamp indicating when the eent first occurred. Identifier archar(255) A unique alue for each type of eent on a gien entity (for example, a LinkDown eent on a specific deice interface). This identifier controls deduplication. LastOccurrence time A timestamp indicating when the eent last occurred. LocalNodeAlias archar(64) The IP or DNS address of the deice. This alue usually refers to the chassis, but for pingfails only, can correspond to the interface. Network Manager field name/default alue in rules file ExtraInfo_SOURCE ExtraInfo_ALERTGROUP This alue is generated from the input to ensure appropriate matching of problem and resolution eents within the ObjectSerer. A alue of 8000 is resered for eents generated by Network Manager. EentName This alue is generated from the input to ensure appropriate deduplication of eents in the ObjectSerer. In the rules file, the identifier is constructed as a concatenation of field alues. For network eents, this field is set to the same alue as the Node field. No alue is set for status eents, to ensure that they are not fed back into Network Manager through the Eent Gateway. Chapter 4. Configuring 173

188 Table 41. alerts.status fields used by Network Manager (continued) alerts.status field Data type Description LocalPriObj archar(255) The specific entity for which the eent is generated; for example, the ifindex, ifdescr, or ifphysaddress field alue. LocalRootObj archar(255) The container of the entity referenced in the LocalPriObj field. This need not be the chassis, but could, for example, be slot in a chassis. The chassis can still be identified using LocalNodeAlias. LocalSecObj archar(255) The secondary object referenced by the eent. Manager archar(64) A descriptie name that identifies the system that forwarded the eents. NmosCauseType integer The eent state. Populated by the NMOS gateway. The possible alues are as follows: 0: Unknown 1: Root Cause 2: Symptom NmosDomainName archar(64) The name of the Network Manager network domain that raised the eent. The name of the primary domain is used in failoer mode. Network Manager field name/default alue in rules file ExtraInfo_AGENT or ExtraInfo_FINDER or ExtraInfo_ifIndex or ExtraInfo_NEWPHASE or ExtraInfo_SERVICE or ExtraInfo_STITCHER The ExtraInfo_ifIndex alue is shown using the syntax ifentry.<ifindex>; for example, ifentry.12. ExtraInfo_OLDPHASE A alue of ITNM is used for eents generated by Network Manager V3.8, or later. A alue of Omnibus is used in earlier ersions. Domain By default, this field is populated only for eents that are generated by Network Manager. To populate this field for other eent sources, such as those from other probes, you must modify the rules files for those probes. This field is populated by the Eent Gateway if an eent is matched to an entity in a domain. 174 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

189 Table 41. alerts.status fields used by Network Manager (continued) alerts.status field Data type Description Network Manager field name/default alue in rules file NmosEntityId integer The unique Object ID that identifies the topology entity with which the eent is associated. This field is similar to the NmosObjInst field but contains more detailed information. For example, this field can include the ID of an interface within a deice. ExtraInfo_MONITOREDENTITYID For eents generated by the Polling engine, the NmosEntityId field is populated in the probe rules file. For all other eents, this field is populated by the gateway when the entity is identified. NmosEentMap archar(64) The eent map name and optional precedence for the eent, which indicates how Network Manager should process the eent; for example, PrecisionMonitorEent.910. The optional precedence number can be concatenated to the end of the alue, following a period (.). If the precedence is not supplied, it is set to 0. Note: This alue can be oerridden by an explicit insertion into the Eent Gateway config.precedence table, which proides the same data. NmosManagedStatus integer The managed status of the network entity for which the eent was raised. When a network entity is unmanaged, the Network Manager polls are suspended and eents from other sources are tagged as unmanaged. This field allows you to filter out eents from unmanaged entities. The possible alues for this field are as follows: 0: Managed 1: Operator unmanaged 2: System unmanaged 3: Out of scope NmosObjInst integer The unique Object ID that identifies the containing topology chassis entity with which the eent is associated. Populated by the NMOS gateway. Tip: This field can be used to detect whether the eent has been passed for eent enrichment. NmosSerial integer The serial number of the eent that is suppressing the current eent. Populated by the NMOS gateway. Chapter 4. Configuring 175

190 Table 41. alerts.status fields used by Network Manager (continued) alerts.status field Data type Description Network Manager field name/default alue in rules file Node archar(64) The deice from which the eent originated. If an eent is raised against an entity with an accessible IP address, the IP address is used. Otherwise, the entityname alue from NCIM is used. By default, Node has the same alue as LocalNodeAlias. ExtraInfo_ACCESSIPADDRESS or EntityName The EntityName alue maps to the Node field only if the ExtraInfo_ACCESSIPADDRESS input field is empty. NodeAlias archar(64) The IP address of the main node, if ExtraInfo_MAINNODEADDRESS aailable. RemoteNodeAlias archar(64) The network address of a remote node, where releant. For example: A blank alue (where an interface has gone down) A neighbouring address (where a connected interface has gone down) The polling station (for a ping failure eent) Serial incr A unique ID per eent per ObjectSerer instance. Where primary and backup ObjectSerers are configured, the ObjectSerers will hae different serial numbers for the same eent. SererName archar(64) The name of the originating ObjectSerer. SererSerial integer The Serial number of the eent in the originating ObjectSerer. Where primary and backup ObjectSerers are configured, the ObjectSerers will hae different serial numbers for the same eent. If the eent originated in the current ObjectSerer, the SererSerial alue is the same as the Serial alue. Seerity integer The seerity leel of the eent stored in the ObjectSerer. The default alues are as follows: 0: Clear (GREEN) 1: Indeterminate (PURPLE) 2: Warning (BLUE) 3: Minor (YELLOW) 4: Major (ORANGE) 5: Critical (RED) Seerity StateChange time A timestamp indicating when the eent was last modified. This field can be used to determine whether a process is modifying an eent after it has been added to the ObjectSerer. Summary archar(255) A textual description of the eent. Description 176 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

191 Table 41. alerts.status fields used by Network Manager (continued) alerts.status field Data type Description Tally integer A count of the number of times that an eent has occurred. This alue is displayed in the Count column in the eent list or AEL, and in the Occurred column in the mojo.eents table. Type integer The type of the alert. The alues of particular releance to Network Manager are 1: Problem 2: Resolution 13: Information Network Manager field name/default alue in rules file ExtraInfo_EVENTTYPE For more information about the alerts.status table, see the IBM Tioli Netcool/OMNIbus Administration Guide in the Tioli Netcool/OMNIbus information centre at com.ibm.tioli.nam.doc/welcome_ob.htm. Related reference: Network Manager network eents on page 160 The Polling engine, ncp_poller, generates eents about the state of the network. These eents can be used to identify network problems, and are configurable by using the Network Polling GUI (go to Administration > Network > Network Polling). These eents are known as network eents and hae the alerts.status AlertGroup field alue of ITNM Monitor. Network Manager status eents on page 161 Network Manager can generate eents that show the status of arious Network Manager processes. These eents are known as Network Manager status eents and hae the alerts.status AlertGroup field alue of ITNM Status. Tioli Netcool/OMNIbus automations added by Network Manager: Network Manager proides a number of Tioli Netcool/OMNIbus automations. Each automation performs different tasks within the Network Manager installation. To enable an automation, use the Tioli Netcool/OMNIbus Administrator GUI. The following table describes the Tioli Netcool/OMNIbus automations installed by Network Manager. Chapter 4. Configuring 177

192 Table 42. Tioli Netcool/OMNIbus automations added by Network Manager Automation seerity_from_ causetype suppress_cross_ domain_connections Description Sets the seerity of eents in the ObjectSerer alerts.status table based on the alue of NmosCauseType, an enumerated field that contains the results of the Network Manager root cause analysis (RCA) calculations. Possible alues for the NmosCauseType field are: 0 - Unknown 1 - Root Cause 2 - Symptom Suppresses eents from connected deices where the connected deice is in a different domain. This automation is triggered wheneer an eent is updated by the Eent Gateway. Restriction: Network Manager only models connections across network domains in MPLS networks between proider-edge and customer edge deices and in BGP networks between BGP peers. Added during installation? Yes Yes Default status Enabled Disabled In order for the automation to work, the two network deices must be connected at layer 3 on a /30 subnet, that is, a subnet with only two hosts. Each deice must also be discoered in a different network domain and the existence of its companion deice must hae been inferred during discoery. This means that in each domain an inferred customer-edge deice or an inferred BGP peer entity must hae been created. update_serice_ affecting_eents Generates serice-affected eents (SAEs) when it encounters network eents on serice-supporting entities. Following each discoery the SAE plugins to the Eent Gateway analyse the updated topology and update the ObjectSerer with the a list of entities that support serices. This information enables the automation to generate serice-affected eents when it encounters network eents on serice-supporting entities. No Not applicable 178 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

193 Configuring integration with Netcool Configuration Manager To add network configuration and policy management capabilities to your network management solution, set up Network Manager and Tioli Netcool/OMNIbus to work with IBM Tioli Netcool Configuration Manager. You can configure integration between Network Manager, Tioli Netcool/OMNIbus, and Netcool Configuration Manager. For more information, go to com.ibm.tioli.ncm.doc/welcome_itncm.htm, select your Netcool Configuration Manager ersion, and see the Integrating Netcool Configuration Manager with Network Manager and Tioli Netcool/OMNIbus topics. Alternatiely, you can download the PDF ersion, titled IBM Tioli Netcool Configuration Manager Integration Guide. Exporting discoery data to CCMDB, TADDM, and TBSM Configure and use the Discoery Library Adapter (DLA) to collect data on network resources and relationships from Network Manager for import into other systems. The DLA collects data from Network Manager and creates XML Discoery Library books (also known as Identity Markup Language, or IdML books) that contain data on the discoered resources and their relationships known to the system. The books conform to the Tioli Common Data Model (CDM) ersion For more information on the Tioli CDM, go to redp4389.html. The Discoery Library books can be imported into other systems for which a Discoery Library Reader exists. The DLA supports both IP4 and IP6. Note: To load Discoery Library (IdML) books containing information about irtual machines into TADDM, you must hae TADDM Fix Pack 1 or later. The DLA is installed by default with Network Manager on the GUI serer. It is installed into the following directory: $NCHOME/precision/adapters/ncp_dla. Prerequisites for use Before you configure and use the Discoery Library Adapter (DLA), make sure the prerequisites are met. A successful Network Manager network discoery has been performed and the Network Connectiity and Inentory Model (NCIM) database has been populated. The DLA uses the GUI serer connection pool by default. If you want to use a different NCIM database than the one proided during installation, then you must hae the access credentials for that NCIM database. You must hae a working knowledge of how the product you want to integrate with is deployed. For more information about IBM Tioli Application Dependency Discoery Manager, see the Information Center at the following Web address: %2Fcom.ibm.taddm.doc_7.2%2Fwelcome_page%2Fwelcome.html For more information about IBM Tioli Business Serice Manager, see the Information Center at the following Web address: com.ibm.tioli.itbsm.doc/welcome.htm Chapter 4. Configuring 179

194 For more information about IBM Tioli Change and Configuration Management Database, see the Information Center at the following Web address: com.ibm.ccmdb.doc_7.1.1/ccmdb_welcome.htm Configuring the DLA The Discoery Library Adapter (DLA) requires a configuration properties file in order to determine the data source to connect to, the domain to query, the target directory for Discoery Library books and logging parameters. You need to configure the DLA properties if you hae a separate GUI serer or if you want to use the DLA with a different NCIM instance than the default proided during installation. A preconfigured ncp_dla.properties configuration file is proided in the DLA installation directory at $NCHOME/precision/adapters/ncp_dla. The presence of 'XXXXXX' or <'word'> in the configuration file indicates that the parameter should be specified by the user. The configuration file proides useful defaults for most options but make sure to replace them with alues appropriate for your enironment. Note: By default, the NCIM access parameters required to use the DLA are deried from the Network Manager GUI access pool. This setting is specified by the ncp.dla.datasource.autoconnect parameter, where the default alue is true. If you change this alue to false, you must specify alues for the parameters listed in step 6 on page 181. Setting how to connect to the NCIM database manually is useful when the connection pool cannot be accessed or if you want to use a different NCIM instance than the default proided during installation. 1. Go to $NCHOME/precision/adapters/ncp_dla and copy the ncp_dla.properties file to a domain-specific ersion by appending the name of the file with the domain name, for example, ncp_dla.properties.ncoms. 2. Specify the Network Manager domain name by assigning a alue to the ncp.dla.precisiondomain property. The default domain name is NCOMS. 3. Optional: You can set the path to a temporary directory the DLA should use while generating the output if you do not want it to use the operating system's default temporary directory. Use the ncp.dla.scratchdirectory parameter to set the full path to a writable temporary directory, for example ncp.dla.scratchdirectory=/opt/space/temp. 4. Optional: You can set what CDM objects you want to hae data generated for. Use the ncp.dla.generationfilter parameter to specify the alues in a comma-separated list. The possible alues are as follows: ComputerSystem - generates the following data for deices: ComputerSystem SnmpSystemGroup OperatingSystem IpInterface for IpDeice, deices with no SNMP access Router Bridge Networking - generates the following data for networks: L2Interface IpInterface 180 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

195 IpV4Address IpV6Address IpNetwork Physical - generates the following data for physical classes: PowerSupply Fan Chassis Sensor PhysicalPackage Card For example, to generate system and network connectiity-related data, add the following alues to the parameter: ncp_dla.generationfilter=computersystem,networking 5. Optional: You can define the URL to use for the contextual launching into other systems. Set the ncp.dla.contextuallaunchurl parameter to the topology alue you want to launch into, and specify the host name and port for the Topoiz topology serer. The default is to launch into the Hop View. For example, to set up the contextual launch into the Structure Browser: ncp.dla.contextuallaunchurl= ncp_structureiew/launch.do?entityid= 6. Optional: If you change the alue of the ncp.dla.datasource.autoconnect to false, specify the RDBMS access details by editing the following parameters that define the database that the DLA connects to for generating Discoery Library books: ncp.dla.datasource.type Specify the RDBMS type, the default is DB2: DB2 DB2 ncp.dla.datasource.drier Specify the JDBC drier to use: DB2 com.ibm.db2.jcc.db2drier ncp.dla.datasource.url Specify the JDBC URL for connecting to the NCIM database: DB2 jdbc:db2://host_name:port_number/database_name ncp.dla.datasource.schema The database schema name, typically ncim ncp.dla.datasource.username The database username, typically ncim ncp.dla.datasource.password The database user password ncp.dla.datasource.encrypted Whether the database password is encrypted [true false] If set to true, you must specify a alid alue for ncp.dla.datasource.keyfile, and you must use the encrypted password referenced in your ITNMHOME/profiles/TIPProfile/etc/tnm/ tnm.properties file. Chapter 4. Configuring 181

196 ncp.dla.datasource.keyfile Specify the full path and name of the cryptographic key file that is used in the ITNMHOME/profiles/TIPProfile/etc/tnm/tnm.properties file. ncp.dla.datasource.logintimeout The login timeout, default 5 seconds 7. Optional: You can limit the scope of data collection to one or more network iews by setting the ncp.dla.network.iew parameter to filter the data of selected network iews only. Using standard SQL operators, define an SQL segment that is appended to the networkview.name field during the DLA query. The parameter must hae a alue starting with one of the following SQL operators: = <>!= IN NOT IN LIKE NOT LIKE For example, the following defines the scope to use only the BGP Networks network iew for the scope of the data collection: ncp.dla.network.iew== BGP Networks Note: The DLA does not support double quotation marks. Eerything after the initial equal sign in the preious example is part of the alue defined, een the second equal (=) sign. Another example is the following where the scope for the data collection is defined as any network iew containing the name Cisco (notice the standard SQL wildcard character % used): ncp.dla.network.iew=like Cisco% 8. Specify how the Discoery Library books generated by the DLA should be transferred by specifying the following parameter: ncp.dla.datasink.type How Discoery Library books are transferred. Options are as follows: FILE FTP The Discoery Library books are locally copied to the target directory /opt/ibm/tioli/netcool/ar/precision/ccmdb. If you specify this option, skip step 9 and proceed to step 10 on page 183. The Discoery Library books are transferred to a remote serer by FTP. If you specify this option, you must complete step 9 ncp.dla.datasink.targetdirectory The target directory for Discoery Library book files Note: If you are running the DLA on a serer other than the GUI serer and want to place the generated books that serer, you can specify the connection parameters in the ncp_dla.properties file by uncommenting and editing the parameters around ncp.dla.datasink.targetdirectory. 9. Optional: If you specified the option FTP for the ncp.dla.datasink.type property, specify the following additional parameters: 182 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

197 ncp.dla.datasink.serer The IP address or hostname of the remote FTP serer. ncp.dla.datasink.port The TCP port to use, default 21 ncp.dla.datasink.binary Whether binary FTP transfers should be used [true false] ncp.dla.datasink.passie Whether passie FTP transfers should be made [true false] ncp.dla.datasink.username The FTP username to use ncp.dla.datasink.password The FTP user password to use ncp.dla.datasink.encrypted Whether or not the FTP password is encrypted [true false] ncp.dla.datasink.keyfile Specify the full path and name of the cryptographic key file that is used in the $ITNMHOME/profiles/TIPProfile/etc/tnm/tnm.properties file. 10. Specify the debug leel of the DLA by specifying a alue for the log4j.rootlogger property. The following alues are permitted; the default alue is FATAL: DEBUG INFO WARN ERROR FATAL 11. Specify the full path and name of the DLA log file by specifying a alue for the log4j.appender.file.file property. The default is dla.log. The log file is written to the DLA installation directory. 12. Optional: The deprecated ncp.dla.alidatecomputersystemfqdn property defines whether to alidate the names of entities discoered by Network Manager as fully-qualified domain-names. CAUTION: Do not change alue. This property has been deprecated and is no longer used in Network Manager ersions 3.9 and later. This property can take one of the following alues: True This is the default alue. Entity names are alidated. The DLA adds Fqdn attributes to ComputerSystem instances only if the deice name is a alid fully-qualified domain-name. False No alidation takes place. The DLA adds Fqdn attributes to ComputerSystem instances irrespectie of whether the deice name is a alid fully-qualified domain-name. 13. Create a copy of the edited configuration file, giing the file a name of your choice. 14. Create a copy of the configuration for each Network Manager domain for which you want to create Discoery Library books. Chapter 4. Configuring 183

198 Remember: Create a configuration file for each Network Manager domain you want to generate Discoery Library books for, and append the name of the configuration file with the domain name (for example, ncp_dla.properties.ncoms). If you want to start the IBM Tioli Application Dependency Discoery Manager GUIs from the Network Manager, complete the additional configuration tasks to add a menu option to the Network Manager GUIs, and add the Network Manager JSP inentory report to TADDM. Related reference: Network Manager status eents on page 161 Network Manager can generate eents that show the status of arious Network Manager processes. These eents are known as Network Manager status eents and hae the alerts.status AlertGroup field alue of ITNM Status. Creating a Discoery Library book To create a Discoery Library book, run the Discoery Library Adapter (DLA) with the appropriate DLA properties file. Before you can run the DLA, the DLA properties file must hae been configured correctly The DLA has two modes of operation: Primary mode Generates Discoery Library books by querying the Network Connectiity and Inentory Model (NCIM) database for the domain identified in the specified configuration file. Import mode Proides a means of importing IBM Tioli Application Dependency Discoery Manager GUIDs back into the NCIM database, so that the TADDM UI can be opened from Network Manager. 1. Change to the DLA installation directory on the Network Manager GUI components serer; the default is $NCHOME/precision/adapters/ncp_dla. 2. Run the Discoery Library Adapter (DLA) and reference the appropriate DLA properties file for your domain to create a Discoery Library book: UNIX./ncp_dla.sh ncp_dla.properties.domain_name See Example for an example of running the command and the system response. Example The following example shows how to run the DLA, and the system response: [[email protected]]#./ncp_dla.sh ncp_dla.properties.ncoms ncp_dla ( IBM Tioli Network Manager IP Edition - Discoery Library Adapter ) Copyright (C) By IBM Corporation. All Rights Resered. See product license for details. [IDML Generation Mode] Initializing... WARNING: user.install.root not defined, using /opt/ibm/tioli/netcool /precision/profiles/tipprofile Loading properties from /opt/ibm/tioli/netcool/precision/profiles /TIPProfile/etc/tnm/tnm.properties FINE: database.type = db2 FINE: database.dbname = ITNM 184 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

199 FINE: database.jdbc.url = null FINE: database.host = abc.test.ibm.com FINE: database.port = FINE: database.username = ncim FINE: database.connection.defaultfetchsize = null FINE: database.connection.propertiesfile = null FINE: Getting encrypted password Jun 3, :15:09 AM DbConnectionPool getjdbcurl FINE: JDBC URL = jdbc:db2://abc.test.ibm.com:50000/itnm INFO: HNMXB0006I=JDBC Drier: com.ibm.db2.jcc.db2drier INFO: HNMXB0007I=JDBC URL : jdbc:db2://abc.test.ibm.com:50000/itnm INFO: HNMXB0007I=JDBC URL : jdbc:db2://abc.test.ibm.com:50000/itnm Jun 3, :15:10 AM DbConnectionPool getconnection FINEST: Connection Pool READ has size 0 Working on ITNM domain NCOMS... Processing 142 ComputerSystem(s)... % Complete: Writing IDML Book to /tmp/dla/itnmip t z. refresh.xml... Shutting down... Finished. Related tasks: Loading Discoery Library books and enabling bidirectional launch on page 190 You need to load the Discoery Library (IdML) book into TADDM to make the book information aailable to TADDM. Importing the book also enables bidirectional contextual launch. Fine-tuning the data export To proide a more consumable set of resources and relationships to other systems from Network Manager, you can fine-tune the DLA data collection and export. Fine-tuning of the Network Manager data export allows TADDM and other Discoery Library (IdML) book consumers to import only the resources and relationships needed to build the appropriate linkage between commonly managed resources. Also, haing only the required data can significantly expedite the export-import process. To set up a more fine-tuned data collection and export, perform the following steps: 1. Discoer the network using Network Manager, as described in Discoering the network. 2. Run the itnmtagnetworkedgeentities.pl tagging utility to identify network edge entities, as described in Identifying network edge entities on page Create a filtered network iew that only displays the edge of the network, as described in Creating a filtered network iew for the edge of the network on page Edit the DLA properties file ncp_dla.properties.domain_name to include the name of the filtered network iew you created, and to ensure you hae set the ncp.dla.generationfilter parameter as described in Editing the DLA properties file for edge entities on page Run the adaptor to create the Discoery Library book, as described in Creating a Discoery Library book for network edge data on page 189. Chapter 4. Configuring 185

200 Identifying network edge entities: Use the itnmtagnetworkedgeentities.pl utility to tag discoered entities such as ports and interfaces as being on the edge of the network. For most cases, you can run the utility to automatically tag entities considered to be on the network edge, which then identifies end-nodes such as hosts and serers that proide or consume serices. Ensure Network Manager has successfully discoered your network. End-nodes must be discoered before you can use the -autoendnodetags option with the itnmtagnetworkedgeentities.pl utility. To run the utility to automatically tag the entities considered as being on the edge of the network in a domain: 1. Go to NHCOME/precision/scripts/perl/scripts. 2. Run itnmtagnetworkedgeentities.pl with the -autoendnodetags command-line option for the domain in which you want entities to be tagged. This automatically includes end-nodes and the routers and switches directly connected to end-nodes. For example, to automatically tag interfaces considered to be on the edge of the network in the domain called NCOMS, enter: UNIX $NCHOME/precision/bin/ncp_perl itnmtagnetworkedgeentities.pl -domain NCOMS -autoendnodetags 3. Optional: You can use the -includenexthop option with the -autoendnodetags option to go one hop further from the edge entities. Using the -includenexthop option automatically includes the edge entities that are included when using only the -autoendnodetags, plus any routers or switches directly connected to the edge entities. For example, to automatically tag such interfaces, enter: UNIX $NCHOME/precision/bin/ncp_perl itnmtagnetworkedgeentities.pl -domain NCOMS -autoendnodetags -includenexthop 4. Optional: You can also determine what deices you want the utility to consider as a network edge deice based on the number of connections the deice has. Use the -autodegreetags option to tag deices as being on the network edge if they hae a certain number of connections. If you only use the -autodegreetags option on its own, the default is to consider all deices with one connection as being on the network edge. If you want to specify a larger connection number, use the -autodegreetags option and the -degree n option together, where n is the maximum number of connections. For example, running the following setting tags all deices with less than or equal to 2 connections: UNIX $NCHOME/precision/bin/ncp_perl itnmtagnetworkedgeentities.pl -domain NCOMS -autodegreetags -degree 2 Note: The -autodegreetags option cannot be used in conjunction with the -autoendnodetags option. The -autodegreetags option mode allows you to include deices as part of the edge of the network that are not considered end-node deices by the -autoendnodetags option. It also proides the flexibility to filter out and identify deices that hae up to a specific number of connections. 5. Optional: You can further refine the tagging by setting a number of options, such as excluding or including specific deices from being tagged or including deices that hae no SNMP access but hae Layer 2 connections. For further information on all the options aailable, iew the utility help by typing: 186 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

201 UNIX $NCHOME/precision/bin/ncp_perl itnmtagnetworkedgeentities.pl -help The utility adds an entitydetails->networkedge=1 attribute in the ncimcache.entitydata database. Now, you can create a filtered network iew that only displays the edge of your network. Creating a filtered network iew for the edge of the network: Create a filtered network iew that only displays the edge of the network in the domain based on the tagging performed by the itnmtagnetworkedgeentities.pl utility. Tip: You can also use this filtered network iew to isualize and monitor the edge of your network, and to see what data is exported using the DLA. To create a filtered iew of the edge of your network: 1. Click Aailability > Network Aailability > Network Views > Libraries. Click New View. 2. Complete the General tab as follows: Name Type a name for the network iew, dynamic iew, or network iew container. Important: It is best practice to use network iew names containing Latin characters only. Network iews names containing non-latin characters (for example Cyrillic characters) are not supported as they cannot be imported and exported when migrating to a new ersion of Network Manager. Parent Select the node under which the iew appears in the hierarchy in the Naigation Tree. To display the iew on the top leel, select NONE. Type Select Filtered. Layout Select Orthogonal, Circular, Symmetric, Hierarchical, ortabular layout. Map Icon If you want a different icon than the default icon to represent the iew, click Browse to browse for an icon. Tree Icon If you want a different icon than the default icon to represent the iew, click Browse Background Image to browse for an icon. Click Browse for the iew. to browse for an image to use as the background Chapter 4. Configuring 187

202 Background Style Specify whether the background image is to be centered or tiled. Line Status Specify how the lines that represent the links between deices should be rendered. You can choose not to display any status, or to display the system default. Alternatiely, lines can be colored based on the associated AEL eent with the highest seerity, and can appear with an additional seerity icon. 3. Set up the filter as follows: a. Click the Filter tab. b. From the Domain list, select the domain where you ran the tagging utility. c. In the Table column, select the entitydetails attribute d. In the Filter column, type keyname = 'NetworkEdge' and keyvalue = '1'. 4. Set End Nodes to Include 5. Set Connectiity to Layer Click Ok and then Sae. You now need to include the name of this network iew in the DLA properties file for the domain. Editing the DLA properties file for edge entities: Edit the ncp_dla.properties file for the domain to include the name of the filtered network iew you created and to make sure you hae set up the right data generation parameters. To edit the file: 1. Go to the default ncp_dla.properties configuration file in the DLA installation directory at $NCHOME/precision/adapters/ncp_dla, or to where your DLA properties file for the domain is. 2. Open the ncp_dla.properties.domain_name file. 3. Locate the ncp.dla.network.iew parameter and add the name of the filtered network iew you created. For example, the filtered iew called Edge would need to be added to this property as follows: ncp.dla.network.iew== Edge Note: The use of the double equality sign (==) as relational operator is intentional. 4. Set the ncp.dla.generationfilter parameter to ComputerSystem and Networking. Specify the alues in a comma-separated list as follows: ncp_dla.generationfilter=computersystem,networking 5. Sae and close the file. Now, you can run the DLA with the updated DLA properties file to export a subset of the Network Manager network data. Related tasks: Configuring the DLA on page 180 The Discoery Library Adapter (DLA) requires a configuration properties file in order to determine the data source to connect to, the domain to query, the target directory for Discoery Library books and logging parameters. 188 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

203 Creating a Discoery Library book for network edge data: You can use the Discoery Library Adapter (DLA) to create the Discoery Library book containing only the data for your network edge entities. Make sure you hae edited the ncp_dla.properties file for the domain to include the name of the filtered network iew containing the network edge entities. To create a DLA book containing network edge data: 1. Change to the DLA installation directory on the Network Manager GUI components serer; the default is $NCHOME/precision/adapters/ncp_dla. 2. Run the Discoery Library Adapter (DLA) to generate the book XML file with data on the tagged network edge entities: UNIX./ncp_dla.sh ncp_dla.properties.domain_name For example, to run the adaptor for the domain called NCOMS, enter the following:./ncp_dla.sh ncp_dla.properties.ncoms The following example shows the system response for running the adaptor for the NCOMS domain: ncp_dla ( IBM Tioli Network Manager IP Edition - Discoery Library Adapter ) Copyright (C) By IBM Corporation. All Rights Resered. See product license for details. [IDML Generation Mode] Initializing... Will use the following Network View(s) filter : = FILTER Working on ITNM domain NCOMS... Processing 1148 IP Network(s)... % Complete: Processing 772 ComputerSystem(s)... % Complete: Processing 1 Topology(s)... Processing 2535 Connection(s)... % Complete: Writing IDML Book to /opt/netcool/itnm39017/netcool/ar/precision/ccmdb /ITNMIP T Z.refresh.xml... Shutting down... Finished. The result is an XML file that contains the deices participating in the filtered network iew preiously created and specified in the ncp_dla.properties file for the domain. The content of the XML file depends on the configuration of the DLA properties file. The XML file contains Common Data Model (CDM) Segments that describe how deices are connected from the perspectie of a gien Network Manager port or interface. The process remoes duplicates and normalizes connection details. For more information on Segments, please refer to the Tioli Common Data Model (CDM) documentation aailable at redp4389.html. The following examples show parts of the XML file output. The interface chosen to be the segment identity is highlighted in bold, including each instance it is referenced. Example of a point-to-multipoint connection from the perspectie of the interface chosen to be the starting point for a segment: Chapter 4. Configuring 189

204 <cdm:net.segment id="segmentvia_359525_l2interface" > <cdm:name>layer 2 Segment ia _L2Interface</cdm:Name> <cdm:managedsystemname>itnmsgmnt:359525_l2interface </cdm:managedsystemname> </cdm:net.segment> <cdm:networks source="segmentvia_359525_l2interface" target="359525_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="358156_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="404607_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="358221_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="358185_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="404595_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="358107_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="357775_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="358232_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="404589_l2interface" /> <cdm:networks source="segmentvia_359525_l2interface" target="358300_l2interface" /> Example of a simple point-to-point connection: <cdm:net.segment id="segmentvia_355664_l2interface" > <cdm:name>layer 2 Segment ia _L2Interface</cdm:Name> <cdm:managedsystemname>itnmsgmnt:355664_l2interface </cdm:managedsystemname> </cdm:net.segment> <cdm:networks source="segmentvia_355664_l2interface" target="355664_l2interface" /> <cdm:networks source="segmentvia_355664_l2interface" target="357336_l2interface" /> Loading Discoery Library books and enabling bidirectional launch You need to load the Discoery Library (IdML) book into TADDM to make the book information aailable to TADDM. Importing the book also enables bidirectional contextual launch. As well as being able to launch the IBM Tioli Application Dependency Discoery Manager GUI from Network Manager, you can also configure TADDM to launch the Network Manager GUI. To load Discoery Library books into TADDM and set up bidirectional contextual launch: 1. Create a Discoery Library book. 2. If required, transfer the Discoery Library book file to your TADDM serer. 3. As the TADDM user, run the bulk load process to import the Discoery Library book. For example: user@host% cd $COLLATION_HOME/bin user@host%./loadidml.sh -x -f full path to and full name of discoery library book file Attention: You must include the full path to the discoery library book file, together with the full file name only if the book is in a different directory. 190 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

205 4. Import the TADDM GUIDs into the NCIM database (see related tasks later in this section). Related tasks: Creating a Discoery Library book on page 184 To create a Discoery Library book, run the Discoery Library Adapter (DLA) with the appropriate DLA properties file. Importing IBM Tioli Application Dependency Discoery Manager GUIDs into the NCIM database on page 193 Optional: To enable users to open the IBM Tioli Application Dependency Discoery Manager UI from Network Manager, import the TADDM GUIDs into the entityguidcache table of the Network Connectiity and Inentory Model (NCIM) database. Configuring IBM Tioli Application Dependency Discoery Manager to start Network Manager Optional: To iew a summary of the resources that Network Manager exports to IBM Tioli Application Dependency Discoery Manager and, from there, open Network Manager, you must add a JSP report. Important: If you are using an earlier ersion of TADDM than Fix Pack 1, follow these instructions to install and configure the JSP report. Howeer, if you are using ersion Fix Pack 1 or later, ignore these steps. In ersion Fix Pack 1 and later the report to show Network Manager inentory and proide the launch in context to Network Manager is installed (or updated if already exists) by the TADDM installation. For more information, see the TADDM documentation at com.ibm.taddm.doc_721fp1/welcome_page/welcome.html. The JSP report is proided; to use the report, the files must be copied to the correct location on your TADDM serer. 1. Log in to the TADDM serer. 2. Ensure the $COLLATION_HOME enironment ariable is set appropriately. 3. Copy the dla_install_directory/integration/itnm_inentory.jsp file from the Network Manager GUI components serer to the $COLLATION_HOME/deploytomcat/reports/WEB-INF/iew directory on the TADDM serer. 4. Copy the two GIF files (tioli.gif and ibm_logo.gif) in dla_install_directory/integration/itnm_images directory from the Network Manager GUI components serer to the $COLLATION_HOME/deploy-tomcat/ images directory on the TADDM serer. 5. Stop your TADDM serer. 6. Edit the $COLLATION_HOME/etc/cdm/xml/reports.xml file by adding the following section before the closing </beans> tag: <bean class="com.collation.cdm.reports.iewer.jspreportviewer" id="itnminentoryreport"> <property name="reportgroup"> <alue>inentory Reports </alue> </property> <property name="reportname"> <alue>itnm IP Inentory Report </alue> </property> <!-- START NON-TRANSLATABLE --> <property name="jsp"> Chapter 4. Configuring 191

206 <alue>/web-inf/iew/itnm_inentory.jsp</alue> </property> <!-- END NON-TRANSLATABLE --> </bean> 7. Restart your TADDM serer. The Network Manager Inentory Report is displayed in the TADDM Domain Manager console. The report has the following sections: Serer Summary: Proides information about the installed instances of the Network Manager product, including the Network Manager ersions installed, the host addresses of the serers where Network Manager is installed, and the URLs to access the Network Manager GUI. Resource Summary: Lists all Network Manager resources that hae a relationship to a ComputerSystem, including information on their IP address, manufacturer, type of resource (for example, router), and unique identifier in the Network Manager database. Configuring Network Manager to start IBM Tioli Application Dependency Discoery Manager Optional: To enable Network Operators to launch the IBM Tioli Application Dependency Discoery Manager GUI from Network Manager, you must add the TADDM menu options to Network Manager. The following steps assume that the Discoery Library Adapter (DLA) is installed on the same serer as Tioli Integrated Portal and the Network Manager GUI components. If the DLA is installed elsewhere, you must copy the DLA installation directory and its content to the serer where the Tioli Integrated Portal and the Network Manager GUI components are installed. For more information about the relationship between IBM Tioli Application Dependency Discoery Manager and IBM Tioli Change and Configuration Management Database, see the Information Center at the following Web address and search for "CCMDB oeriew": tiihelp/10r1/index.jsp?topic=/com.ibm.ccmdb.doc_7.1.1/ccmdb_welcome.htm 1. Configure the launch points from the menu to the TADDM installation: a. Change to the ITNMHOME/profiles/TIPProfile/etc/tnm/tools/ directory. b. Edit the following files: ncp_wt_ccmdb_details.xml ncp_wt_ccmdb_history.xml c. Specify the following parameters: TADDM_HOST The IP address or host name of your TADDM serer. TADDM_PORT The TCP port on which your TADDM serer is listening. The default is 9430, and this alue only needs to be changed if a different port number was proided when installing TADDM. TADDM_USER The user name to use to access your TADDM serer. TADDM_PASSWORD The password associated with the TADDM_USER parameter. d. Optional: To configure TADDM to start in the same window as Network Manager, edit the target field of the url property in each tool definition 192 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

207 file. By default, TADDM starts in a new window. For example, to display the CCMDB details in the same window, edit the property in the ncp_wt_ccmdb_details.xml file as follows: target="ccmdbdetails " 2. Verify that the TADDM submenu was added to Network Manager: a. Log into Network Manager. b. Click Network Aailability > Network Views c. Select a network iew and right-click a deice. In the context menu, the following TADDM menu items should be displayed under Launch To... > TADDM/CCDMB: View Details View History Note: It can take seeral minutes for the changes to take effect. If changes hae not taken effect after 5 minutes, log off, restart your browser, and log in again. You now need to import the TADDM GUIDs into the NCIM database. Related tasks: Importing IBM Tioli Application Dependency Discoery Manager GUIDs into the NCIM database Optional: To enable users to open the IBM Tioli Application Dependency Discoery Manager UI from Network Manager, import the TADDM GUIDs into the entityguidcache table of the Network Connectiity and Inentory Model (NCIM) database. Importing IBM Tioli Application Dependency Discoery Manager GUIDs into the NCIM database Optional: To enable users to open the IBM Tioli Application Dependency Discoery Manager UI from Network Manager, import the TADDM GUIDs into the entityguidcache table of the Network Connectiity and Inentory Model (NCIM) database. 1. Run the DLA so that the Network Manager resources and relationships are imported into TADDM. 2. Log in to the serer where your Network Manager GUI components are installed, and copy the DLA integration directory and content in ITNMHOME/adapters/ncp_dla/integration to your TADDM serer (for example, $COLLATION_HOME/sdk/dla/integration). Ensure that permissions are set so that the TADDM user can access the files. 3. On the TADDM serer, change to the directory where you copied the files to. 4. As the TADDM user, use the TADDM API to query the CCMDB for ComputerSystem data and pipe the results to an XML file called itnm_guids.xml. For example: user@host% $COLLATION_HOME/sdk/bin/api.sh -u user_name -p password find ComputerSystem > itnm_guids.xml 5. Make sure the itnm_guids.xsl and the itnm_guids.xml files exist in the current directory. 6. As the TADDM user, use the XLST processor to extract the entityid's and GUIDs, and pipe them to a CSV file called itnm_guids.cs. For example: user@host% $COLLATION_HOME/sdk/bin/xslt.sh -XSL $COLLATION_HOME/sdk/dla/ integration./itnm_guids.xsl > itnm_guids.cs 7. Copy the itnm_guids.cs file back to the Network Manager GUI serer into the home directory or the ITNMHOME/adapters/ncp_dla directory. Chapter 4. Configuring 193

208 8. Run the DLA in import mode to import the CSVs into the Network Manager NCIM database. See Example for an example of how to run in import mode, and the system response. Example The following example shows how to run the DLA in import mode, and how the system responds. cd /opt/ibm/discoerylibrary/itnm [./ncp_dla.sh ncp_dla.bat ] -import -file integration/itnm_guids.cs ncp_dla.properties.db2 ncp_dla ( IBM Tioli Network Manager IP Edition - Discoery Library Adapter ) Copyright (C) By IBM Corporation. All Rights Resered. See product license for details. [GUID Import Mode] Initializing... Importing GUIDs from integration/itnm_guids.cs Imported 15 GUID(s) into NCIM. Shutting down... Finished. user@host% Related tasks: Loading Discoery Library books and enabling bidirectional launch on page 190 You need to load the Discoery Library (IdML) book into TADDM to make the book information aailable to TADDM. Importing the book also enables bidirectional contextual launch. Integration with TBSM Network Manager is integrated with IBM Tioli Business Serice Manager by default using the Probe for Tioli Netcool/OMNIbus (nco_p_ncpmonitor). The probe proides IBM Tioli Business Serice Manager with BSM_Identity tokens for Network Manager. You must hae both IBM Tioli Network Manager IP Edition and IBM Tioli Business Serice Manager installed and configured. The BSM_Identity token is used by default by TBSM to associate eents with resources. Using the Network Manager DLA, TBSM becomes aware of the Network Manager resources. Network Manager eents will hae the BSM_Identity field added based on the following setting in the $NCHOME/probes/arch/ nco_p_ncpmonitor.rules = "ITNMIP:" + $ExtraInfo_MONITOREDENTITYID + "&domain=" + $Domain Related reference: Prerequisites for use on page 179 Before you configure and use the Discoery Library Adapter (DLA), make sure the prerequisites are met. 194 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

209 Configuring the Tioli Integrated Portal After installation, you might need to configure Tioli Integrated Portal security or single sign-on. Single sign-on The single sign-on (SSO) capability in Tioli products means that you can log on to one Tioli application and then launch to other Tioli Web-based or Web-enabled applications without haing to re-enter your user credentials. The repository for the user IDs can be the Tioli Netcool/OMNIbus ObjectSerer or a Lightweight Directory Access Protocol (LDAP) registry. A user logs on to one of the participating applications, at which time their credentials are authenticated at a central repository. With the credentials authenticated to a central location, the user can then launch from one application to another to iew related data or perform actions. Single sign-on can be achieed between applications deployed to Tioli Integrated Portal serers on multiple machines. Single sign-on capabilities require that the participating products use Lightweight Third Party Authentication (LTPA) as the authentication mechanism. When SSO is enabled, a cookie is created containing the LTPA token and inserted into the HTTP response. When the user accesses other Web resources (portlets) in any other application serer process in the same Domain Name Serice (DNS) domain, the cookie is sent with the request. The LTPA token is then extracted from the cookie and alidated. If the request is between different cells of application serers, you must share the LTPA keys and the user registry between the cells for SSO to work. The realm names on each system in the SSO domain are case sensitie and must match exactly. See Managing LTPA keys from multiple WebSphere Application Serer cells on the WebSphere Application Serer Information Center. Configuring single sign-on: Use these instructions to establish single sign-on support and configure a federated repository. Configuring SSO is a prerequisite to integrating products that are deployed on multiple serers. All Tioli Integrated Portal Serer instances must point to the central user registry (such as a Lightweight Directory Access Protocol serer). Attention: ITM single sign on (SSO) support is only aailable with ITM Version 6.2 Fix Pack 1 or higher. To configure the WebSphere federated repositories functionality for LDAP: 1. Log in to the administratie console. 2. In the Authentication area, expand Web security and click Single sign-on. 3. Click the Enabled option if SSO is disabled. 4. Click Requires SSL if all of the requests are expected to use HTTPS. 5. Enter the fully-qualified domain names in the Domain name field where SSO is effectie. If the domain name is not fully qualified, the Tioli Integrated Portal Serer does not set a domain name alue for the LtpaToken cookie and SSO is alid only for the serer that created the cookie. For SSO to work across Tioli applications, their application serers must be installed in same domain (use the same domain name). Chapter 4. Configuring 195

210 6. Optional: Enable the Interoperability Mode option if you want to support SSO connections in WebSphere Application Serer ersion or later to interoperate with preious ersions of the application serer. 7. Optional: Enable the Web inbound security attribute propagation option if you want information added during the login at a specific Tioli Enterprise Portal Serer to propagate to other application serer instances. 8. After clicking OK to sae your changes, stop and restart all the Tioli Integrated Portal Serer instances. Note: When you launch Network Manager, you must use a URL in the format protocol://host.domain:port /*. If you do not use a fully-qualified domain name, Network Manager cannot use SSO between Tioli products. Protecting the ault key file To keep the encryption key for the administrator password secure, establish strict read-only access to the ault key file. The Tioli Integrated Portal administrator ID (default is tipadmin) that was created during the installation needs access to the ault key file for Tioli Integrated Portal applications to work properly. The ault key is an encryption key that is used to encrypt the administrator password that was proided during installation and is stored locally for Tioli Integrated Portal applications. Use these steps to restrict access to the file. 1. On the computer where the application serer is installed, open the TIPHOME/_uninst/ITNM directory. 2. Use the method proided by your operating system to ensure that the.ault.key file has read-only access. On Windows, for example, the attributes for the ITNM directory are already set to read-only; those for the.ault.key file are set to read-only and hidden. Configuring access for HTTP and HTTPS By default, the application serer requires HTTPS (Hypertext Transfer Protocol Secure) access. If you want some users to be able to log in and use the console with no encryption of transferred data, including user ID and password, configure the enironment to support both HTTP and HTTPS modes. After installing Network Manager and before beginning this procedure, log in to the portal to ensure that it has connectiity and can start successfully. Configuring for HTTP and HTTPS console access inoles editing the web.xml file of Web components. Use this procedure to identify and edit the appropriate Web XML files. 1. Change to the following directory: TIPHOME/profiles/TIPProfile/config/ cells/tipcell/applications. 2. From this location, locate the web.xml files in the following directories: For the Integrated Solutions Console Web application archie: isclite.ear/deployments/isclite/isclite.war/web-inf For the Tioli Common Reporting: tcr.ear/deployments/tcr/ rptiewer_1.2.0.war/web-inf For the Tioli Common Reporting Web application archie: isclite.ear/deployments/isclite/rptwebui_1.2.0.war/web-inf 196 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

211 For the Tioli Integrated Portal Charts Web application archie: isclite.ear/deployments/isclite/tipchartportlet.war/web-inf For the Tioli Integrated Portal Change Password Web application archie: isclite.ear/deployments/isclite/tipchangepasswd.war/web-inf 3. Open one of the web.xml files using a text editor. 4. Find the <transport-guarantee> element. The initial alue of all <transport-guarantee> elements is CONFIDENTIAL, meaning that secure access is always required. 5. Change the setting to NONE to enable both HTTP and HTTPS requests. The element now reads: <transport-guarantee>none</transport-guarantee>. 6. Sae the file, and then repeat these steps for the other web.xml deployment files. 7. Stop and restart the application serer. The following example is a section of the web.xml file for TIPChangePasswd where the transport-guarantee parameter is set to NONE: <security-constraint> <display-name> ChangePasswdControllerSerletConstraint</display-name> <web-resource-collection> <web-resource-name>changepasswdcontrollerserlet</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <auth-constraint> <description>roles</description> <role-name>administrator</role-name> <role-name>operator</role-name> <role-name>configurator</role-name> <role-name>monitor</role-name> <role-name>iscadmins</role-name> </auth-constraint> <user-data-constraint> <transport-guarantee>none</transport-guarantee> </user-data-constraint> </security-constraint> Users must now specify a different port, depending on the mode of access. The default port numbers are as follows: Use the HTTP port for logging in to the Tioli Integrated Portal on the HTTP port. Use the HTTPS secure port for logging in to the Tioli Integrated Portal. Note: If you want to use single sign-on (SSO) then you must use the fully qualified domain name of the Tioli Integrated Portal host. Chapter 4. Configuring 197

212 Enabling FIPS You can configure the Tioli Integrated Portal Serer to use Federal Information Processing Standard Jaa Secure Socket Extension files. Follow these steps to enable FIPS for the Tioli Integrated Portal Serer. 1. Configure the application serer to use FIPS. a. In the portal, click Security > SSL certificate and key management. b. Select the Use the United States Federal Information Processing Standard (FIPS) algorithms option and click Apply. This option makes IBMJSSE2 and IBMJCEFIPS the actie proiders. 2. Configure the application serer to use FIPS algorithms for Jaa clients that must access enterprise beans: a. Open the install_dir/profiles/tipprofile/properties/ssl.client.props file in a text editor. b. Change the com.ibm.security.usefips property alue from false to true. 3. Configure the application serer to use FIPS algorithms for SOAP-based administratie clients that must access enterprise beans: a. Open the install_dir/profiles/tipprofile/properties/soap.client.props file in a text editor. b. Add this line:com.ibm.ssl.contextproider=ibmjssefips. 4. Configure jaa.security to enable IBMJCEFIPS: a. Open the install_dir/jaa/jre/lib/security/jaa.security file in a text editor. b. Insert the IBMJCEFIPS proider (com.ibm.crypto.fips.proider.ibmjcefips) before the IBMJCE proider, and also renumber the other proiders in the proider list. The IBMJCEFIPS proider must be in the jaa.security file proider list. See the example at the end of this topic. 5. Enable your browser to use Transport Layer Security (TLS) 1.0: a. Microsoft Internet Explorer: Open the Internet Explorer and click Tools > Internet Options. OntheAdanced tab, select the Use TLS 1.0 option. b. Firefox: TLS 1.0 is enabled by default. 6. Export Lightweight Third Party Authentication keys so applications that use these LTPA keys can be reconfigured. a. In the naigation pane, click Settings > Websphere Admin Console and click Launch Websphere Admin Console. b. In the WebSphere Application Serer administratie console, select Settings > Global security. c. In the Global security page, from the Authentication area, click the LTPA link. d. Under Cross-cell single sign-on, specify a key file and proide a filename and password for the file that will contain the exported LTPA keys. e. Click Export keys. 7. Reconfigure any applications that use Tioli Integrated Portal Serer LTPA keys: To reconfigure the Tioli SSO serice with the updated LTPA keys, run this script: TIPHOME/profiles/TIPProfile/bin/setAuthnScLTPAKeys.jacl. a. Change directory to TIPHOME/profiles/TIPProfile/bin/ b. Start the Tioli Integrated Portal Serer: UNIX Linux startserer.sh serer1 c. Run the following command: 198 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

213 wsadmin -username tipadmin -password tipadmin_password -f setauthnscltpakeys.jacl exported_key_path key_password Where: exported_key_path is name and full path to the key file that was exported. key_password is the password that was used to export the key. 8. For SSO, enable FIPS for any other application serers, then import the updated LTPA keys from the first serer into these serers: a. Copy the LTPA key file from step 4 aboe to another application serer computer. b. In the naigation pane, click Settings > Websphere Admin Console and click Launch Websphere Admin Console. c. In the WebSphere Application Serer administratie console, select Settings > Global security. d. In the Global security page, from the Authentication area, click the LTPA link. e. Under Cross-cell single sign-on, proide the filename and password from aboe for the file that contains the exported LTPA keys. f. Click Import keys. 9. Run the ConfigureCLI command: Linux UNIX TIPHOME/bin/tipcli.sh ConfigureCLI --usefips true The IBM SDK TIPHOME/jaa/jre/lib/security/jaa.security file looks like this when IBMJCEFIPS is enabled. security.proider.1=com.ibm.crypto.fips.proider.ibmjcefips security.proider.2=com.ibm.crypto.proider.ibmjce security.proider.3=com.ibm.jsse.ibmjsseproider security.proider.4=com.ibm.jsse2.ibmjsseproider2 security.proider.5=com.ibm.security.jgss.ibmjgssproider security.proider.6=com.ibm.security.cert.ibmcertpath security.proider.7=com.ibm.crypto.pkcs11.proider.ibmpkcs11 security.proider.8=com.ibm.security.cmskeystore.cmsproider security.proider.9=com.ibm.security.jgss.mech.spnego.ibmspnego Configuring the LPTA token timeout alue You can configure the Lightweight Third Party Authentication (LTPA) token timeout alue for Tioli Integrated Portal in the WebSphere Application Serer console. Tioli Integrated Portal is enabled for single sign-on. The default timeout for an LTPA token is 120 minutes. An LTPA timeout causes you to be logged out from Tioli Integrated Portal and can also cause an authentication popup message, if the first request after the timeout is an AJAX request from a portlet. To configure the LTPA token timeout: 1. In the Tioli Integrated Portal naigation pane, click Settings > WebSphere Admin Console. 2. Click Launch WebSphere Admin Console to start the WebSphere Application Serer console. 3. In the WebSphere Application Serer console naigation pane, click Security > Global security. 4. In the Authentication area of the Global security page, click the LTPA link. 5. In the LTPA timeout area of the LTPA page, edit the alue for the LTPA timeout and click OK. Chapter 4. Configuring 199

214 6. In the Messages area at the top of the Global security page, click the Sae link and log out of the WebSphere Application Serer console. In a load balanced enironment, you must set the LTPA token timeout alue on each of the Tioli Integrated Portal Serer instances. Configuring VMM for the ObjectSerer If you installed Tioli Netcool/OMNIbus using the Network Manager installer and selected to use the ObjectSerer for user authentication, the installer configures the Virtual Member Manager (VMM) adapter for the ObjectSerer. Otherwise, you must configure VMM manually if you want to use the ObjectSerer for user authentication. Hae the following ObjectSerer information at hand: administrator name and password, IP address, and port number. If you hae a second ObjectSerer for failoer support, you need the IP address and port number. The ObjectSerer must be running at the time of installing Network Manager, as the installation process attempts to connect to the ObjectSerer. The script assumes that the tip installation directory is the parent directory and that the profile and cell names are TIPProfile and TIPCell. Run the VMM configuration script on eery computer where the application serer is installed. 1. Change to the TIPHOME/bin directory. The directory contains a script to run: Linux confmm4ncos.sh UNIX confmm4ncos.sh 2. Enter the following command at the command line: confmm4ncos user password address port [address2 port2]where a. user is the ID of a user with administratie priileges for this ObjectSerer b. password is the password for the user ID c. address is the IP address of the ObjectSerer d. port is the port number used by the ObjectSerer e. Optional: address2 and port2, if there is a failoer serer, is the IP address and port number of the failoer ObjectSerer The VMM adapter is configured for the ObjectSerer. Thereafter, wheneer the user registry needs to be accessed, the VMM adapter is called for this information. Changing the default security registry The default security registry can be set at install time. Use this procedure to change the default registry after installation. These steps require that your user ID has the Administrator role and that you know the base entry alue of your repository. For LDAP or Microsoft Actie Directory, this is usually a string like ou=company,dc=country,dc=region. For the ObjectSerer, the base entry is o=netcoolobjectsererrepository. If you did not select a default user registry during installation or you would like to change the default to a different registry, complete these steps. 1. If you are not already logged in to the administratie console, log in now. Your ID must hae the Administrator role. 2. Click Security > Secure administration, applications, and infrastructure. 3. In the User account repositories area, select Federated repositories from the Aailable realm definitions, then click Configure. 200 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

215 4. Click Supported entity types under Additional Properties. 5. Click the entity type, then edit the Base entry for the default parent and Relatie Distinguished Name properties. 6. After you click OK to sae your changes, repeat the preious step to configure the other entity types. For Microsoft Actie Directory, the entity types (PersonAccount, Group, and OrgContainer) must be configured with a base DN and the RDN for PersonAccount should be cn instead of uid. 7. Stop and restart the Tioli Integrated Portal Serer: a. In the TIPHOME/profiles/TIPProfile/bin directory, depending on your operating system, enter one of the following commands: UNIX Linux stopserer.sh serer1 Note: On UNIX and Linux systems, you are prompted to proide an administrator username and password. b. In the TIPHOME/profiles/TIPProfile/bin directory, depending on your operating system, enter one of the following commands: UNIX Linux startserer.sh serer1 Integrating with IBM Tioli Monitoring You can install IBM Tioli Monitoring for IBM Tioli Network Manager IP Edition to monitor the health of your Network Manager installation. IBM Tioli Monitoring is included in the Network Manager package. You must hae installed Network Manager before installing IBM Tioli Monitoring for IBM Tioli Network Manager IP Edition. Restriction: UNIX The launchpad opens xterm windows to run the shell scripts for migration and installation of IBM Tioli Monitoring for IBM Tioli Network Manager IP Edition. If you want to paste non-ascii characters between the xterm windows started by the installer and other windows, you must set your locale to one that ends with UTF-8 before running the launchpad. Use a command similar to this example: export LANG=fr_FR.UTF-8. To install IBM Tioli Monitoring for IBM Tioli Network Manager IP Edition, perform the following tasks: 1. On the serer where Network Manager core components are installed, run the IBM Tioli Monitoring for IBM Tioli Network Manager IP Edition installation script. To run the installation script using the launchpad, start the launchpad using the launchpad.sh script on UNIX, and click Postinstallation > Install the Monitoring Agent > Start ITM Agent Installation. To run the installation script using the command line, run the ITMagent/install.sh script on UNIX from the scripts directory of the installation media. 2. For more installation steps, refer to the IBM Tioli Monitoring for IBM Tioli Network Manager IP Edition User's Guide. 3. Ensure you hae IBM Tioli Monitoring ersion Fix Pack 3 or later installed. For example, to upgrade to Fix Pack 3, go to the following site: Chapter 4. Configuring 201

216 Configuring integration with IBM Systems Director You can set up Network Manager to work with IBM Systems Director. After setting up the integration, you can launch IBM Systems Director from the Network Manager GUI and perform arious tasks on the selected deice in IBM Systems Director. Oeriew of integration with IBM Systems Director IBM Systems Director proides consolidated iews of your managed systems and a set of tasks for system management including discoery, inentory, configuration, system health, monitoring, updates, eent notification and automation across managed systems. After setting up the integration, you can open IBM Systems Director tasks from the Network Manager GUI using the right-click menu. You can launch IBM Systems Director to manage resources in your network by right-clicking a deice in any Network Manager topology iew and selecting the Launch to > Director menu option, followed by selecting the task you want to open in IBM Systems Director. The IBM Systems Director features you can launch for a deice from within Network Manager depend on the information shared about the discoered deice in both products. The following list identifies all IBM Systems Director tasks aailable when launching from Network Manager: Actie Status Configure Access Current Configuration Create Group Compliance Issues Configuration Manager Configuration Plans Compliance Policy Configuration Templates Distributed Command Deployment History Eent Log File Management Network Diagnostics Naigate Resource: Basic Topology Naigate Resources: Virtualization Topology Performance Summary Request Access Remote Command Line Verify Connection View and Collect Inentory Naigate Resources: Properties View Note: The list of features aailable to launch from the Network Manager right-click menu will ary and might be a subset of the preious list. 202 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

217 For more information about the features opened in IBM Systems Director and assistance using them, click the help button on the opened IBM Systems Director page. Alternatiely, go to the IBM Systems Director information center at com.ibm.director.main.helps.doc/fqm0_main.html and search for the name you clicked on in the right-click menu option (for example, search for "Configure Access"). Integration architecture The integration between Network Manager and IBM Systems Director requires a Jaa adapter process to run based on settings defined in the itnmsystemsdirector.properties configuration file. The configuration file is installed by default with Network Manager on the GUI serer, and it can be found in the NCHOME/precision/adapters/ itnm_systemsdirectorlic directory. The Jaa adapter process communicates with the IBM Systems Director serer using HTTPS to associate IBM Systems Director resources and launch-points with deices discoered by Network Manager for the domain defined in the properties file. The adapter determines the set of IBM Systems Director launch points related to a Network Manager deice, and stores them in the LiCmapping NCIM table. The LiCmapping table describes the IBM Systems Director resource, launch-point URL, and menu name for each task you can run against a Network Manager deice. Restriction: For the integration to be successful, both Network Manager and IBM Systems Director must discoer and manage the same resources. Downloading and installing the IBM Systems Director You must hae an IBM Systems Director installation running before configuring integration with Network Manager. To obtain IBM Systems Director, perform the following steps: 1. Go to 2. Go to the Management serers tab and download IBM Systems Director ersion 6.2 or later. 3. Go to the IBM Systems Director information center at publib.boulder.ibm.com/infocenter/director/6r2x/index.jsp?topic=/ com.ibm.director.main.helps.doc/fqm0_main.html, expand "IBM Systems Director V6.2.1", and then go to the "Planning" and "Installing" topic collections. 4. Follow the instructions proided to plan the installation and complete the installation of IBM Systems Director. Chapter 4. Configuring 203

218 Setting up integration with the IBM Systems Director Perform the following tasks to set up the integration between Network Manager and IBM Systems Director. Preparing the properties file: To set up the integration, you must create a copy of the itnmsystemsdirector.properties file for each Network Manager domain you want to run IBM Systems Director tasks against. Create a copy of the properties file for the domain against which you intend to run the adapter: 1. Go to the NCHOME/precision/adapters/itnm_systemsDirectorLiC directory. The configuration file is installed by default with Network Manager on the GUI serer. 2. Make a copy of the itnmsystemsdirector.properties file and append the file name with the name of the domain you want to set up integration for. For example, to create a copy of the properties file for the domain NCOMS, enter the following command on UNIX operating systems: cp itnmsystemsdirector.properties itnmsystemsdirector.properties.ncoms This creates a copy of the properties file and adds NCOMS to the end of the file. 3. Use the copy of the file to set up the integration as described in the following tasks. Exporting and importing the SSL certificate: The Jaa adapter process that communicates between Network Manager and IBM Systems Director requires the setup of a secure connection. You must import the SSL certificate from the IBM Systems Director serer into the trust store used by the Network Manager Jaa process running the adapter. To obtain the certificate, you must export it from IBM Systems Director and then import it into Network Manager: 1. Log into the IBM Systems Director serer. 2. Export the certificate using the keytool -export command: /opt/ibm/director/jre/bin/keytool -export -alias lwiks -keystore /opt/ibm/director/lwi/security/keystore/ibmjsse2.jks -file directorcert.arm 3. Copy the directorcert.arm file to the Network Manager serer where the adapter will run. For example, /tmp/directorcert.arm. 4. Import the directorcert.arm file into the local trust store using the keytool -import command: keytool -import -alias directorcert -file /path to file/directorcert.arm -keystore TIPHOME/jaa/jre/lib/security/cacerts Note: The default password is changeit. The following shows an example of importing the certificate: /opt/ibm/tioli/tip/jaa/bin/keytool -import -alias directorcert -file /tmp/directorcert.arm -keystore /opt/ibm/tioli/tip/jaa/jre/lib/ security/cacerts 204 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

219 Configuring connection properties: Edit the copy of the itnmsystemsdirector.properties file to specify the connection properties for the adapter linking Network Manager and IBM Systems Director. Make sure you hae created a copy of the itnmsystemsdirector.properties file and appended the file name with the name of the domain for which you want to set up the integration with IBM Systems Director; for example itnmsystemsdirector.properties.ncoms. To configure the connection properties: 1. Open the properties file itnmsystemsdirector.properties.name of domain. 2. Edit the following alues to set up the connection: a. Set the itnm.integration.ibm.systemsdirector.cryptographickeyfile parameter to reference the Network Manager cryptographic key file or a key file you generated using the./itnm_systemsdirectorlic.sh -generate -keyfile file name option. For example, set the path as follows to use the default key file: itnm.integration.ibm.systemsdirector.cryptographickeyfile=/opt/ibm/ tioli/netcool/precision/profiles/tipprofile/etc/tnm/ encryption/keys/crypt.key b. Set the itnm.integration.ibm.systemsdirector.serer parameter to reference the IP address or host name of the IBM Systems Director serer. For example: itnm.integration.ibm.systemsdirector.serer= c. Set the itnm.integration.ibm.systemsdirector.port parameter to the port number on which the IBM Systems Director serer is listening on. For example: itnm.integration.ibm.systemsdirector.port=4495 Note: The default port is d. Set the itnm.integration.ibm.systemsdirector.username parameter to reference the IBM Systems Director user name. For example: itnm.integration.ibm.systemsdirector.username=root 3. Encrypt and set the password for the IBM Systems Director user: a. Go to the NCHOME/precision/adapters/itnm_systemsDirectorLiC directory. b. Run the following command using the password for the IBM Systems Director user set in the itnm.integration.ibm.systemsdirector.username parameter:./itnm_systemsdirectorlic.sh -encrypt password -keyfile /full path to cryptographic key file/cryptographic key file name.key. This will create an encrypted text string for the password. For example, to encrypt the password Network1 using the default key file, enter:./itnm_systemsdirectorlic.sh -encrypt Network1 -keyfile /opt/ibm/tioli/netcool/precision/profiles/tipprofile/etc/tnm/ encryption/keys/crypt.key An example output of the encryption process is jr/ CjUmgRaYRF64Dsf37FGJxDxqmxcE3XybALZ7THo=. c. Set the itnm.integration.ibm.systemsdirector.password parameter to reference the encrypted password of the user. For example, to use the encrypted password from the preious step, enter: Chapter 4. Configuring 205

220 itnm.integration.ibm.systemsdirector.password= jr/cjumgrayrf64dsf37fgjxdxqmxce3xybalz7tho= 4. Set the itnm.integration.ibm.systemsdirector.jrekeystorefile parameter to reference the location of the Network Manager keystore you imported the SSL certificate into. For example: itnm.integration.ibm.systemsdirector.jrekeystorefile=/opt/ibm/tioli/tip/ jaa/jre/lib/security/cacerts 5. Encrypt and set the password for the keystore file: a. Go to the NCHOME/precision/adapters/itnm_systemsDirectorLiC directory. b. Run the following command using the password for the keystore file:./itnm_systemsdirectorlic.sh -encrypt password -keyfile /full path to cryptographic key file/cryptographic key file name.key. This will create an encrypted text string for the password. For example, to encrypt the password Crypto1 using the default key file, enter:./itnm_systemsdirectorlic.sh -encrypt Crypto1 -keyfile /opt/ibm/tioli/netcool/precision/profiles/tipprofile/etc/tnm/ encryption/keys/crypt.key An example output of the encryption process is i/y7aycv5looik3eroyepwjxdxqmxce3xybalz7tho=. c. Set the itnm.integration.ibm.systemsdirector.jrekeystorepassword parameter to reference the encrypted password for the keystore file. For example, to use the encrypted password from the preious step, enter: itnm.integration.ibm.systemsdirector.jrekeystorepassword= i/y7aycv5looik3eroyepwjxdxqmxce3xybalz7tho= 6. Sae the properties file. You can specify additional optional settings in the itnmsystemsdirector.properties file for the adapter. Related tasks: Additional adapter settings on page 208 Apart from setting the connection properties, you can modify the default parameters that control additional behaior and logging characteristics of the adapter. Edit the copy of the itnmsystemsdirector.properties file for the adapter linking the Network Manager domain and IBM Systems Director. Configuring connection to NCIM: You can configure the connection settings to the NCIM database where the adapter populates the LiCmapping table with data from IBM Systems Director. If the itnm.integration.ibm.systemsdirector.itnmdatabaseuseconnectionpool is set to true, then the default settings to NCIM are used, and you do not need to configure the database properties. The only mandatory parameter is itnmdomain which must be specified (see first step). To set the connection properties for the NCIM database: 1. In the itnm.integration.ibm.systemsdirector.itnmdomain property, specify the Network Manager domain against which the adapter runs. For example: itnm.integration.ibm.systemsdirector.itnmdomain=ncoms 206 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

221 2. Optional: If you do not want to use the default settings and hae itnm.integration.ibm.systemsdirector.itnmdatabaseuseconnectionpool set to false, you can specify alternatie database properties for the adapter to use: a. Remoe the hash from the beginning of the line and set the itnm.integration.ibm.systemsdirector.itnmdatabasetype property to the database type you want to use. The supported alues are DB2. b. Remoe the hash from the beginning of the line and set the itnm.integration.ibm.systemsdirector.itnmdatabasedrier property to the JDBC drier URL that specifies the type of JDBC drier to use. Use one of the following alues based on your selected database: For DB2: com.ibm.db2.jcc.db2drier c. Remoe the hash from the beginning of the line and set the itnm.integration.ibm.systemsdirector.itnmdatabaseurl property to the JDBC URL for connecting to the NCIM database. Use one of the following syntax based on your selected database: For DB2: jdbc:db2://host_name:port_number/database_name Tip: This setting depends on the database you use. Refer to ITNMHOME/profiles/TIPProfile/etc/tnm/tnm.properties for information about the database used and help with completing the platform-specific URL. The following example shows the settings for a DB2 database: itnm.integration.ibm.systemsdirector.itnmdatabasetype=db2 itnm.integration.ibm.systemsdirector.itnmdatabasedrier= com.ibm.db2.jcc.db2drier itnm.integration.ibm.systemsdirector.itnmdatabaseurl= jdbc:db2://abc123.ibm.com:50000/ncim 3. Optional: Set the itnm.integration.ibm.systemsdirector.itnmdatabaseusername property to reference the NCIM database user name. For example: itnm.integration.ibm.systemsdirector.itnmdatabaseusername=root 4. Optional: Encrypt and set the password for the NCIM user: a. Go to the NCHOME/precision/adapters/itnm_systemsDirectorLiC directory. b. Run the following command using the password for the NCIM user set in the itnm.integration.ibm.systemsdirector.itnmdatabaseusername property:./itnm_systemsdirectorlic.sh -encrypt password -keyfile /full path to cryptographic key file/cryptographic key file name.key. This will create an encrypted text string for the password. For example, to encrypt the password Database1 using the default key file, enter:./itnm_systemsdirectorlic.sh -encrypt Database1 -keyfile /opt/ibm/tioli/netcool/precision/profiles/tipprofile/etc/tnm/ encryption/keys/crypt.key An example output of the encryption process is DDlWqoRzRHAD9WpYzkI0mJxDxqmxcE3XybALZ7THo=. c. Set the itnm.integration.ibm.systemsdirector.itnmdatabasepassword property to reference the encrypted password. For example: itnm.integration.ibm.systemsdirector.itnmdatabasepassword= DDlWqoRzRHAD9WpYzkI0mJxDxqmxcE3XybALZ7THo= 5. Sae the properties file. Chapter 4. Configuring 207

222 Additional adapter settings: Apart from setting the connection properties, you can modify the default parameters that control additional behaior and logging characteristics of the adapter. Edit the copy of the itnmsystemsdirector.properties file for the adapter linking the Network Manager domain and IBM Systems Director. Make sure you edit the copy of the itnmsystemsdirector.properties file for the domain you set up the integration for. The configuration file is installed by default with Network Manager on the GUI serer, and it can be found in the NCHOME/precision/adapters/ itnm_systemsdirectorlic directory. To modify additional characteristics of the adapter: 1. Open the properties file itnmsystemsdirector.properties.name of domain. 2. Edit the following alues: a. Set the itnm.integration.ibm.systemsdirector.connecttimeout parameter to the amount of time during which the adapter attempts to connect to the IBM Systems Director serer. If the adapter cannot connect after the specified time elapses, it produces an error. The alue is in milliseconds and the default is (60 seconds). b. Set the itnm.integration.ibm.systemsdirector.readtimeout parameter to the amount of time the adapter waits to read data from the IBM Systems Director serer after connecting to it. If the adapter cannot read any data after the specified time elapses, it produces an error. The alue is in milliseconds and the default is (60 seconds). c. Use the itnm.integration.ibm.systemsdirector.erifysslhostnames parameter to set whether or not the adapter erifies the name of the IBM Systems Director serer stored in the certificate. Verification is performed if set to true, while no erification is performed if set to false. d. Use the itnm.integration.ibm.systemsdirector.usepasswordauthentication parameter to set whether or not password authentication is used. Password authentication turned on if set to true, while authentication is turned off if set to false. e. Use the itnm.integration.ibm.systemsdirector.ignoreipaddress.n parameter to instruct the adapter to ignore specific IP addresses in IBM Systems Director. Specify more than one IP address by repeating this parameter and incrementing n by 1 each time. For example, to set adapter to ignore IP addresses and , add the following lines: itnm.integration.ibm.systemsdirector.ignoreipaddress.1= itnm.integration.ibm.systemsdirector.ignoreipaddress.2= f. Use the itnm.integration.ibm.systemsdirector.ignorehostname.n parameter to instruct the adapter to ignore specific host names. Specify more than one host name by repeating this parameter and incrementing n by 1 each time. For example, to set adapter to ignore host names mymachine and ball.company.com, add the following lines: itnm.integration.ibm.systemsdirector.ignorehostname.1=mymachine itnm.integration.ibm.systemsdirector.ignorehostname.2=ball.company.com 208 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

223 g. The adapter creates a table in NCIM associating IBM Systems Director resources with deices discoered by Network Manager for the domain defined in the properties file. You can oerride the indiidual IBM Systems Director resource to Network Manager deice mapping by manually specifying which IBM Systems Director OID corresponds to what Network Manager main node IP address or host name. Use the itnm.integration.ibm.systemsdirector. mapoidtoitnmipaddressorhostname.n parameter to instruct the adapter to oerride the automatic resource association. Specify more than one resource by repeating this parameter and incrementing n by 1 each time. The format is mapoidtoitnmipaddressorhostname.n=oid:ipaddress or mapoidtoitnmipaddressorhostname.n+1=oid:hostname. For example, to set adapter to take the OID 2292 and associate it with IP address , and take OID 2286 and associate it with host name mymachine, add the following lines: itnm.integration.ibm.systemsdirector.mapoidtoitnmipaddressorhostname.1= 2292: itnm.integration.ibm.systemsdirector.mapoidtoitnmipaddressorhostname.1= 2286:mymachine h. You can set the adapter to ignore specific IBM Systems Director tasks. Use the itnm.integration.ibm.systemsdirector.ignoretask.n parameter to set tasks that are ignored by the adapter and are not aailable to run on a deice. Specify more than one task by repeating this parameter and incrementing n by 1 each time. For example, to set adapter to ignore the Network Diagnostics task, add the following line: itnm.integration.ibm.systemsdirector.ignoretask.1=network Diagnostics 3. Sae the properties file. You can also set the logging properties for the adapter process. Related tasks: Setting logging properties for adapter You can specify logging properties for the adapter used to link IBM Systems Director and Network Manager. Setting logging properties for adapter: You can specify logging properties for the adapter used to link IBM Systems Director and Network Manager. Make sure you edit the copy of the itnmsystemsdirector.properties file for the domain you set up the integration for. To set the logging properties for the adapter: 1. Open the properties file itnmsystemsdirector.properties.name of domain. 2. Edit the following alues: a. Set the oerall logging leel using the.leel parameter. The default is WARNING and the following leels can be set: CONFIG: Logs all eents up to and including configuration changes. INFO: Logs only system state changes. This is the default setting. WARNING: Chapter 4. Configuring 209

224 Logs recoerable system errors. SEVERE: Logs unrecoerable system errors. FINE: Minimum leel of tracing. The majority of stack traces appear at this leel already and are written to the trace file. The trace file also includes all log messages. FINER: Medium leel of tracing that proides more detailed debug messages. FINEST: Maximum leel of tracing that produces ery detailed technical information. b. Set the logging leel for the file handler using the jaa.util.logging.filehandler.leel parameter. The possible leels are the same as for the.leel parameter. c. If used, set the logging leel for the console handler using the jaa.util.logging.consolehandler.leel parameter. The possible leels are the same as for the.leel parameter. d. Modify where the log file is saed to using the jaa.util.logging.filehandler.pattern parameter. 3. Sae the properties file. Logging for the adapter process uses the same logic as other logging in Network Manager. Check the log files to pinpoint any potential issues. Running the adapter to populate NCIM After setting the adapter properties, you can run the adapter to populate the NCIM database with information on the resources that can be managed in IBM Systems Director for the Network Manager domain defined in the properties file. Make sure you hae set all the required parameters in the adapter properties file for the domain. To run the adapter: 1. Change to the NCHOME/precision/adapters/itnm_systemsDirectorLiC directory. 2. Run the adapter using the./itnm_systemsdirectorlic.sh command and reference the properties file for the domain you set up the adapter for. For example, to run the adapter for the NCOMS domain, enter the following command:./itnm_systemsdirectorlic.sh itnmsystemsdirector.properties.ncoms Based on the settings in the properties file, the adapter populates the LiCmapping table in the NCIM database with launch-point information from IBM Systems Director. 3. Right-click deices in any Network Manager topology iew after running the adapter. A set of IBM Systems Director tasks are aailable to be launched from Network Manager for the deice if the deice is managed by both products. The following list identifies all IBM Systems Director tasks aailable when launching from Network Manager: Actie Status Configure Access 210 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

225 Current Configuration Create Group Compliance Issues Configuration Manager Configuration Plans Compliance Policy Configuration Templates Distributed Command Deployment History Eent Log File Management Network Diagnostics Naigate Resource: Basic Topology Naigate Resources: Virtualization Topology Performance Summary Request Access Remote Command Line Verify Connection View and Collect Inentory Naigate Resources: Properties View Note: The list of features aailable to launch from the Network Manager right-click menu will ary and might be a subset of the preious list. Troubleshooting the integration with IBM Systems Director If the launch in context from Network Manager to IBM Systems Director does not work, you might need to check your IBM Systems Director integration settings. If the integration with IBM Systems Director does not work, it is likely that the adapter did not run and populate the launch-point data in the LiCmapping table. To check the integration settings: 1. The first step when an error occurs is to check all of the configuration settings and check that both Network Manager and IBM Systems Director are managing the same set of resources. 2. Check the following items: Option The SSL certificate was not imported from IBM Systems Director into Network Manager. The IBM Systems Director configuration is not correct. The Network Manager NCIM database configuration is not correct. Description Export the certificate and then import it into Network Manager as described in Exporting and importing the SSL certificate on page 204. Make sure you set the connection properties to the IBM Systems Director properly, as described in Configuring connection properties on page 205. Check the NCIM settings as described in Configuring connection to NCIM on page 206. Chapter 4. Configuring 211

226 Option There is a firewall blocking access to the IBM Systems Director API. The specified Network Manager domain does not hae deices managed by IBM Systems Director. The IBM Systems Director serer is not running. The Network Manager NCIM database is not running. The specified passwords hae been encrypted using a different cryptographic key file to the one specified in the properties file. Description Check your firewall settings and allow access to the IBM Systems Director host. Make sure that the same deices are discoered by both products. Make sure the IBM Systems Director serer is running and you can log on. For more information about IBM Systems Director, see the information center at director/6r1x/index.jsp?topic=/ director_6.1/fqm0_main.html and search for "Management serer and agent commands." Make sure all processes are running in Network Manager, as described in. Make sure you encrypt the passwords with the file you reference in the adapter properties file, as described in Configuring connection properties on page If the error requires more detailed information to understand its cause, set the logging leel to FINEST and examine the log file for error messages. Related tasks: Setting logging properties for adapter on page 209 You can specify logging properties for the adapter used to link IBM Systems Director and Network Manager. Accessing discoery data from dncim You can take adantage of post-discoery dncim broadcasts to retriee updates to the network topology after each discoery completes. Internal Network Manager processes read this information on completion of a discoery. You can also configure third-party systems (Tioli-based or external) to access this topology data so that they hae the latest topology updates. Examples of such third-party systems that you might want to configure to read dncim data include the following: TADDM can use this data in order to feed its application discoery. The data from dncim tells TADDM which hosts are present on the network, which is a first step to discoering the applications on those hosts. IBM Director can use this data to support the discoery of storage deices An asset database can use this data to upload its asset information. A security system can use the data to identify possible intrusions. Getting data from dncim rather than using the DLA differs in the following ways. The data is in a different format to the DLA. The dncim data has not yet been sent to the Topology Manager, ncp_model, so the data is not consolidated with preious discoeries: The data is lighter weight than the data that can be retrieed using the DLA. The dncim broadcasts hae the same format as the NCIM broadcasts transmitted by ncp_model, and the NCIM cache files. 212 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

227 To configure third-party systems to access discoery data from dncim, you must write a script to configure the Jaa or Perl API to listen for messages with the DNCIM2NCIM subject on the message bus. For information on the format of dncim broadcasts, see the IBM Tioli Network Manager Topology Database Guide. By default DNCIM is set up so that the soliddb database that is s embedded in the Discoery engine, ncp_disco, is accessible only from the local machine. If you want to query this database, you might need to change the configuration so that the database is accessible from other machines. Perform the following steps to configure the database so that is accessible from other machines 1. Edit the following file: $ITNMHOME/embeddedDb/solid/ncp_disco.DOMAIN/ solid.ini. 2. Change the following line: Listen=tcpip -i port_number ; DB_PORT_NUM Where port_number is a TCP/IP port number to read. 3. Restart Discoery engine, ncp_disco. Configuring Network Manager for UNIX operating systems On UNIX systems, you might need to perform extra configuration tasks before using the product. Configuring root/non-root permissions On UNIX, if you installed Network Manager as a non-root user, you must perform additional configuration. Certain components of Network Manager require root permissions to run. You must perform different actions depending on whether you want to run Network Manager as a root user or a non-root user. Root and non-root installation On UNIX Network Manager can be installed as either the root user or a non-root user. If you hae installed any other IBM Tioli products into the same installation directory, you must install Network Manager as the same user that installed the other products. The Network Manager web applications must always be run as the user who installed the product. After installation, you can configure the Network Manager core components to be run as a different user. For example, if you installed as the root user, you can configure the core components to be run as a non-root user. Restriction: When Network Manager is installed and run as root, scripts are installed that restart Network Manager and Tioli Netcool/OMNIbus processes when the serer is rebooted. When Network Manager is installed and run as a non-root user, Network Manager and Tioli Netcool/OMNIbus processes are not restarted automatically when the serer is rebooted. Howeer, as a post-installation Chapter 4. Configuring 213

228 task for non-root installations, you can configure the processes to start automatically when your system is rebooted, as described in Non-root installation: Configuring processes to start automatically on page 215. Restriction: IBM Tioli Business Serice Manager must run as non-root. When installing Network Manager and IBM Tioli Business Serice Manager on the same serer, make sure you install and run both as a non-root user. Configuring the core components to run as root On UNIX, if you installed Network Manager as a non-root user, you must perform additional configuration to run the core components as the root user. The Network Manager Web applications must always be run as the user who installed the product. You must run a script that updates file permissions to ensure that the root user has access to all necessary files. If you installed Network Manager as the root user, you do not need to perform any configuration in order to run the core components as the root user. 1. Log in to the serer where the Network Manager core components are installed. Log in as the root user. 2. Run the script either from the installer launchpad or the command line: Option From the launchpad From the command line Description 1. Go to the directory where you extracted the Network Manager installation package. 2. Start the launchpad as root using the./launchpad.sh command. 3. Select the Postinstallation menu. 4. Expand Non-root postinstallation tasks (UNIX only) and click Run IBM Tioli Network Manager IP Edition 3.9 as root. 1. Go to the NCHOME/precision/scripts directory. 2. Run the setup_run_as_root.sh script. Configuring the core components to run as non-root On UNIX, if you installed Network Manager as a non-root user, and you want to allow that user permissions to run the core components, you must log in as root and perform additional configuration. Attention: Only install and run as a non-root user on serers where trusted users are the only users who can log in. The Network Manager Web applications must always be run as the user who installed the product. To gie a non-root user these permissions, you must run a script. It is not possible to install and run Network Manager without eer logging in as the root user. At a minimum you must log in as root temporarily to run this script. 214 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

229 Complete the following configuration steps in order to run the core components as a non-root user: 1. Log in as the root user. 2. Run the script either from the installer launchpad or the command line: Option From the launchpad From the command line Description 1. Go to the directory where you extracted the Network Manager installation package. 2. Start the launchpad as root using the./launchpad.sh command. 3. Select the Postinstallation menu. 4. Expand Non-root postinstallation tasks (UNIX only) and click Run IBM Tioli Network Manager IP Edition 4.1 as installing user. 1. Go to the NCHOME/precision/scripts directory. 2. Run the following script: setup_run_as_setuid_root.sh. 3. Optional: If you want to run the mttrapd probe (also known as the SNMP probe) as non-root, perform additional configuration: Configure the probe to run as a non-root user using the instructions on Running the mttrapd probe as suid root in the IBM Tioli Netcool/OMNIbus Probe for SNMP Reference Guide. After this script has completed, the user who performed the Network Manager installation can log in and run the Network Manager core components. Non-root installation: Configuring processes to start automatically On UNIX systems, as a post-installation task for non-root installations you can configure your Network Manager processes to start automatically when your system is started or restarted. Your Network Manager installation must hae completed successfully before performing the following steps. Note: You do not need to configure this if you installed Network Manager as the root user. The automatic restart is set up as part of a root installation without the need for this post-installation step. To configure the Network Manager processes to start automatically: 1. Log in to the serer where the Network Manager core components are installed. Log in as the root user. 2. Run the script to set the processes either from the installer launchpad or the command line: Chapter 4. Configuring 215

230 Option From the launchpad From the command line Description 1. Go to the directory where you extracted the Network Manager installation package. 2. Start the launchpad as root using the./launchpad.sh command. 3. Select the Postinstallation menu. 4. Expand Non-root postinstallation tasks (UNIX only) and click Start Network Manager processes on system start/restart. 1. Go to the NCHOME/precision/install/ scripts directory. 2. Run the create_all_control.sh -auto_only script. Installing and configuring DB2 after a non-root installation DB2 can only be installed by the root user. If you installed Network Manager as non-root and you also selected DB2 to be installed on the same serer to use as your topology database, you must log in as root after completing the Network Manager installation and complete the DB2 installation on the system. Make sure the Network Manager installation has completed successfully. Check the installation log files for information on the post-installation work required for the database installation. To set up DB2 after a non-root installation: 1. Log in as root. 2. You can use the GUI (launchpad) or the command line interface: Option Configuring DB2 using the GUI (launchpad) Configuring DB2 using the command line interface Description 1. Go to the directory where you extracted the Network Manager installation package. 2. Start the launchpad as root using the./launchpad.sh command. 3. Select the Postinstallation menu. 4. Expand Non-root postinstallation tasks (UNIX only) and click Finish installing DB2 as topology database. 5. Proide the location where you installed Network Manager (the $NCHOME enironment ariable alue), and wait for the command window to complete. This might take a few minutes. 1. Go to NCHOME/precision/install/ scripts 2. Run the installdb2.sh command as follows:./installdb2.sh -f db2.properties 3. Wait for the script to complete. 216 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

231 Note: To start and stop your DB2 database, log in as the DB2 database administrator and run the db2stop command to stop the DB2 database, and the db2start command to start the database. For more information, go to the IBM DB Information Center at Related tasks: Viewing the installation logs on page 84 Viewing the installation logs can be useful for troubleshooting purposes. Configuring connection to existing DB2 You must install a DB2 runtime client when using an existing DB2 serer for your topology database, regardless of whether the database is on the same serer as Network Manager or an a different serer. You must install the DB2 runtime client on the serer where Network Manager core components are installed. The runtime client is required to set up communication between Network Manager and the database. You do not need to install a DB2 runtime client if you installed the DB2 serer using the Network Manager installer. To configure the connection to an existing DB2 database: 1. Log in to the serer as root where you installed the core components. 2. Install the DB2 runtime client using the GUI (launchpad) or the command line interface: Option Install DB2 runtime client using the GUI (launchpad) Install DB2 runtime client using the command line interface Description 1. Go to the directory where you extracted the Network Manager installation package. 2. Start the launchpad as root using the./launchpad.sh command. 3. Select the Postinstallation menu. 4. Expand Non-root postinstallation tasks (UNIX only) and click Install DB2 runtime client. 5. Proide the location where you installed Network Manager (the $NCHOME enironment ariable alue), and wait for the command window to complete. This might take a few minutes. 1. Go to NCHOME/precision/install/ scripts 2. Run the installdb2.sh command as follows:./installdb2.sh -f db2.properties 3. Wait for the script to complete. Chapter 4. Configuring 217

232 Configuring GUIs You can change the appearance and functionality of the Hop Views; update MIB information; and configure the presentation of eents from unmanaged deices. Administering the TopoViz client You can customize the operations of the TopoViz client. This includes the display settings, for example deice icons, the frequency of topology updates, and alert settings. Changing Tioli Integrated Portal timeouts When you are working in the Tioli Integrated Portal, your GUI session is subject to timeouts. You can change the timeout settings. The Tioli Integrated Portal proides the following default timeout settings: Inalidation timeout If a user is logged into Network Manager using Tioli Integrated Portal and closes the Tioli Integrated Portal window, then the user session automatically times out after 30 minutes. Lightweight Third Party Authentication (LTPA) timeout After a user is logged in for 24 hours, the Tioli Integrated Portal login session is automatically closed down and the user is forced to log in again. Changing the inalidation timeout setting: If a user is logged into Network Manager using Tioli Integrated Portal and closes the Tioli Integrated Portal window, then, by default, the user session automatically times out after 30 minutes. This is known as the inalidation timeout. You can modify the inalidation timeout setting. To change the inalidation timeout setting: 1. Log in to the serer where the Network Manager GUI components are installed and edit the following file: UNIX $TIPHOME/profiles/TIPProfile/config/cells/TIPCell/ applications/isclite.ear/deployments/isclite/deployment.xml 2. Within this file find the inalidationtimeout alue. By default, this alue is set to 30 minutes. 3. Set the inalidationtimeout to the required alue in minutes. 4. Sae the deployment.xml file. 5. Restart the Tioli Integrated Portal. Changing the Lightweight Third Party Authentication (LTPA) timeout setting: After a user is logged in for a certain amount of time, by default 24 hours, the Tioli Integrated Portal login session is automatically closed down and the user is forced to log in again. This is known as the Lightweight Third Party Authentication (LTPA) timeout. You can modify the LTPA timeout setting. To change the LTPA timeout setting: 1. Click Security > Secure administration, applications, and infrastructure. 2. In the Secure administration, applications, and infrastructure window, click Authentication mechanisms and expiration. 218 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

233 3. Set the Timeout alue for forwarded credentials between serers alue as required. The default alue is 1440 minutes (24 hours). 4. Click OK. 5. Restart the Tioli Integrated Portal. Features of the TopoViz client Use this information to understand the features of the TopoViz client that can be customized. TopoViz icons: In a topology map, icons represent types of deice or network elements. You can customize these icons. The following icons can be customized: Deice icons Tree and map icons The following figure shows a representation of the tree and map icons: 1 2 Figure 9. Tree and map icons 1 Tree icon Used to represent iews in the Naigation Panel. The default tree and map icons take the form of a cloud. Network operators can customize these icons when defining a new network iew in the Network Views GUI. To do this, they choose from a list of predefined icons. 2 Map icons Used to represent iews in the Topology Display Panel. Chapter 4. Configuring 219

234 Related tasks: Adding icons on page 221 Make extra, custom icons aailable for network operators to choose from if they want to change the icons that they use in the Network Views and Network Hop View GUIs. Related reference: Configuring the display of extra information associated with a deice on page 226 Information such as alert status and maintenance state of a deice is displayed in a colored border around the deice. You can configure the colors, icons, and positioning of the elements used to display this information. Deice class types: All deice class are automatically categorized by class type. In topology maps, each class type is represented by a different icon, whereas each deice class is not. Class types are stored in the NCIM topology database, in the classtype field of the entitytype table. The following class types apply: Core End Node Network Deice Router Switch All the class types consist of deice classes. For example, the Network Deice class type contains the Alcatel and Cisco deice classes. Deice ToolTips: Deice ToolTips appear when you roll your mouse oer deices in topology maps. Deice ToolTips are defined by HTML entries in the ITNMHOME/profiles/ TIPProfile/etc/tnm/topoiz.properties configuration file on the serer where the Network Manager GUI components are installed. You can specify the content of ToolTips associated with deices, subnets and links. By default, the domain of a deice is displayed in the ToolTip. The topoiz.properties file is monitored eery 60 seconds for changes, so that any changes are automatically detected by Topoiz. Entries in the topoiz.properties file that control deice ToolTips The default settings for controlling deice ToolTips are as follows: topoiz.tooltip.map_item.entitytype=html_statement Where: map_item Takes one of the following alues: deice: For a chassis (main node deice) or subnet ToolTip 220 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

235 link: for a link ToolTip entitytype Is the entitytype number for a deice, subnet, or link. It takes one of the following alues: 1: For a chassis (main node deice) ToolTip 15: For a subnet ToolTip 2: For a link ToolTip HTML_statement Is any alid HTML code that is used to define the content and format of the ToolTip. To insert the alue from an NCIM topology database field use the following syntax: {table.field} Example The following example statement defines a chassis ToolTip: topoiz.tooltip.deice.1=<b>{entitydata.displaylabel}</b><br><b>sysdescr:</b> {chassis.sysdescr}<br><b>syscontact:</b> {chassis.syscontact} <br><b>syslocation:</b> {chassis.syslocation}<br><b>{i18n.netiew_props.domain}</b> {mainnodedetails.domainname} Note: The {i18n.netiew_props.domain} entry will be replaced with the appropriate language ersion at runtime, read from the i18n properties file. Changing icons in the Network Views and Network Hop View GUIs You can change the icons that represent deice classes, class types, trees, and maps to make them more recognizable to users when users iew topology maps within the Network Views and the Network Hop View. Adding icons: Make extra, custom icons aailable for network operators to choose from if they want to change the icons that they use in the Network Views and Network Hop View GUIs. To make custom tree and map icons aailable to network operators: 1. Create your icon. For best results, use the following formats: For the tree icon: 16 by 16 pixel PNG, GIF, or JPG image For the map icon: PNG, GIF, JPG, or SVG image of any size You need only supply one image, because Topoiz scales the icon as appropriate. 2. Copy your icon to the ITNMHOME/profiles/TIPProfile/etc/tnm/resource/ directory on the serer where the Web Applications are installed. Related concepts: TopoViz icons on page 219 In a topology map, icons represent types of deice or network elements. You can customize these icons. Chapter 4. Configuring 221

236 Assigning icons to deices: You can change the icons for deices and other entities used in topology maps displayed within the Network Views and Network Hop View GUIs.. Assigning icons to deice classes: To represent different deice classes with different icons, assign each deice class its own icon. This helps operators distinguish between deice classes in topology maps, for example between Cisco and Alcatel deices. Make custom icons aailable by adding icons as described in the related link. To assign a custom icon to a deice class: 1. Assign the icon prepared earlier to a class type by modifying the line that describes the icon to the topoiz.properties file, as follows: a. Edit the ITNMHOME/profiles/TIPProfile/etc/tnm/topoiz.properties file. b. Find the section that specifies icon names for deice types. c. Modify the releant line of code as follows: topoiz.deiceicon.classname=iconname.extension Where classname is the name of the deice class. This must correspond to the actie object parameter within the AOC file that defines the class. AOC files are contained in the ITNMHOME/precision/aoc/ directory. iconname is the name of your icon. extension is the file extension. 2. Sae the topoiz.properties file. Related tasks: Adding icons on page 221 Make extra, custom icons aailable for network operators to choose from if they want to change the icons that they use in the Network Views and Network Hop View GUIs. Assigning icons to entity types: Some network entities that display in the GUI are not deices and therefore do not hae an associated class name. In order to be able to display an icon for these entities in the GUI, you can associate an icon to the related entity type to an icon. Make custom icons aailable by adding icons as described in the related link. To assign a custom icon to an entity type: 1. Assign the icon prepared earlier to a class type by adding a line that describes the icon to the topoiz.properties file, as follows: a. Edit the ITNMHOME/profiles/TIPProfile/etc/tnm/topoiz.properties file. b. Find the section that specifies icon names for deice types. c. Add the releant line of code as follows: topoiz.image.entitytype=iconname.extension Where 222 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

237 entitytype is the entity type. This must exactly match the entity type name as listed in the NCIM entitytype table. For more information on the entitytype table, see the IBM Tioli Network Manager IP Edition Topology Database Reference. iconname is the name of your icon. extension is the file extension. 2. Sae the topoiz.properties file. RAN GSM Cell An example of a network entity that displays in the GUI but is not a deice and therefore does not hae an associated class name is the entity type 130: RAN GSM Cell. A RAN GSM Cell is a collection of elements, but does not hae a class type or class name. To associate the cloud icon for the RAN GSM cell in the GUI, the following line was added to the topoiz.properties file: topoiz.image.ran\ GSM\ Cell=cloud.sg Note: The spaces in the entity name RAN GSM Cellmust be escaped with a backslash (\). Related tasks: Adding icons on page 221 Make extra, custom icons aailable for network operators to choose from if they want to change the icons that they use in the Network Views and Network Hop View GUIs. Assigning icons to class types: Change the icons that are used to represent class types to make it easier for network operators to identify the class types in topology maps. Class types group together more than one class. For example, you might want a single icon that represents the class type CiscoSwitch, where the CiscoSwitch class type groups together multiple Cisco switch class icons. Make custom icons aailable by adding icons as described in the related link. To assign a custom icon to a class type: 1. Identify the classes that make up your class type. For example, if you want a single icon for all Cisco switches (the Cisco switch class type), then identify each of the AOC files that represent indiidual Cisco switch classes. 2. Go to the directory that contains the actie object class (AOC) files. AOC files define the deice classes. cd $NCHOME/precision/aoc/ 3. For each AOC file in your class type, modify the isual_icon parameter as follows: isual_icon = classtype; For example, in each Cisco switch AOC file, modify the isual_icon parameter as follows: isual_icon = CiscoSwitch; 4. Assign the icon prepared earlier to a class type. For example, if you want to use a single icon for all Cisco switches (the Cisco switch class type), then edit Chapter 4. Configuring 223

238 the ITNMHOME/profiles/TIPProfile/etc/tnm/topoiz.properties file, find the section that specifies icon names for deice types and modify the releant line of code as follows: topoiz.image.ciscoswitch=my_icon.sg Where my_icon is the name of your custom icon file for the Cisco switch class type. 5. Sae the topoiz.properties file. Assigning an icon for the RAN transmitter class type An existing example is the class type for radio area network (RAN) transmitters. A number of RAN deice classes fall into the transmitter type. For example, the RANBaseStation and RANNodeB classes both fall into the transmitter class type and are represented by a single transmitter icon. This is implemented using the following file settings: AOC file for RANBaseStation In this file, the isual_icon parameter is set to the generic class type Transmitter. //************************************************************* // // File : RANBaseStation.aoc // //************************************************************* actie object RANBaseStation { super_class = NetworkDeice ; instantiate_rule = "ExtraInfo->ranBaseStation!= NULL"; isual_icon = Transmitter ; }; AOC file for RANNodeB In this file, the isual_icon parameter is also set to the generic class type Transmitter. //************************************************************* // // File : RANNodeB.aoc // //************************************************************* actie object RANNodeB { super_class = NetworkDeice ; instantiate_rule = "ExtraInfo->ranNodeB!= NULL"; isual_icon = Transmitter ; }; topoiz.properties file In this file, the icon transmitter.sg is assigned to any class that has the isual_icon = Transmitter ; setting in its AOC file. topoiz.image.transmitter = transmitter.sg 224 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

239 Related tasks: Adding icons on page 221 Make extra, custom icons aailable for network operators to choose from if they want to change the icons that they use in the Network Views and Network Hop View GUIs. Configuring topology map updates and appearance You can change the way deices and alert status are displayed in the topology maps. You can also modify frequency of updates to topology and alert status. Appearance of nodes and lines in topology maps: By default nodes, representing, for example, deices, and other network entities, always appear before the lines showing connections between the nodes. You can change this default setting, but this can make it difficult to iew and interact with the nodes. By default nodes oerlay lines in a topology map. The setting that controls this option can be found in the following file: ITNMHOME/profiles/TIPProfile/etc/tnm/ topoiz.properties. To locate this settings, search for the releant section that begins with the comment # Specifies whether nodes are drawn before edges. # Specifies whether nodes are drawn before edges # true => Edges oerlay nodes # false => Nodes oerlay edges topoiz.graph.nodesbeforeedges=false By default the setting topoiz.graph.nodesbeforeedges is set to false, which means that nodes always oerlay lines in a topology map. Changing the frequency of topology update checks: TopoViz checks at regular interals whether the topology shown in a network iew has been updated. To change this frequency, change the topoiz.topologyupdateperiod alue of the topoiz.properties file. Any new nodes appear automatically in the topology maps; the new nodes are highlighted using handles. The default frequency is 3600 seconds (60 minutes). You can change this to any alue in seconds. If you set the topoiz.topologyupdateperiod alue to 0, Topoiz stops checking for updates to the topology. To change the check frequency: 1. Open the ITNMHOME/profiles/TIPProfile/etc/tnm/topoiz.properties configuration file and identify the following line: topoiz.topologyupdateperiod= Change the frequency to the required alue in seconds. Sae and close the topoiz.properties file. Chapter 4. Configuring 225

240 Configuring the display of extra information associated with a deice: Information such as alert status and maintenance state of a deice is displayed in a colored border around the deice. You can configure the colors, icons, and positioning of the elements used to display this information. You control the display of extra information associated with a deice using the settings in the following files: ITNMHOME/profiles/TIPProfile/etc/tnm/topoiz.properties ITNMHOME/profiles/TIPProfile/etc/tnm/status.properties The settings that you can configure using these files include the following: Managed status of deice Icons that displays unmanaged and partially unmanaged status, position, and size of the icons. Manually added deice indication Icon to indicate that this is a manually added deice, position, and size of the icon. Alert status of deice Whether to display an alert status icon, and if displayed, position of the alert status icon. Frame around the deice Roundness of the corners of the frame around the deice, height and width of the frame. Deice label text Typeface, font size and font style of the deice label text. Example The following figure shows a representation of a deice display, showing a manually added deice in unmanaged mode. 1 2 manually_added Figure 10. Representation of a deice display, showing a manually added deice in unmanaged mode 226 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

241 Configure the settings for the unmanaged status and manually added deice icons as follows: 1 Unmanaged status icon, position, and size The settings are specified in the topoiz.properties file. To locate these settings, search for the releant section that begins with the comment # Oerlay definitions.. 1] 2] 3] 4] 5] 6] 7] # Oerlay definitions. topoiz.oerlay.image.unmanaged=unmanaged.sg topoiz.oerlay.position.unmanaged=c topoiz.oerlay.size.unmanaged=25 topoiz.oerlay.image.partialmanaged=partial_managed.sg topoiz.oerlay.position.partialmanaged=c topoiz.oerlay.size.partialmanaged=25 Table 43. Description of settings for the unmanaged status icons Line Description 2 Specifies the icon to use to indicate unmanaged status. 3 Specifies the position of the unmanaged status icon. The letter C means centered. 4 Specifies the size of the unmanaged status icon. The number is a relatie alue. 5 Specifies the icon to use to indicate partially unmanaged status. 6 Specifies the position of the partially unmanaged status icon. The letter C indicated centered. 7 Specifies the size of the partially unmanaged status icon. The number is a relatie alue. 2 Manually added deice icon, position, and size The settings are specified in the topoiz.properties file. To locate these settings, search for the releant section that begins with the comment # Oerlay definitions.. 1] 2] 3] 4] 5] # Oerlay definitions - Manual deice topoiz.oerlay.image.manual=manualoerlay.sg topoiz.oerlay.position.manual=e topoiz.oerlay.size.manual=10 topoiz.oerlay.xoffset.manual=-2 Table 44. Description of settings for the manually added deice status icon Line Description 2 Specifies the icon to use to indicate a manually added deice. 3 Specifies the position of the manually added deice icon. The letter E means east of center. 4 Specifies the size of the manually added deice icon. The number is a relatie alue. 5 Specifies x-axis offset of the icon. The East of center positioning in line 2 would place the icon so that it is touching the frame surrounding the deice. The -2 offset alue moes the icon slightly to the left, so that it is positioned just inside the frame. Example The following figure shows a representation of a deice display, showing an associated critical alert. Chapter 4. Configuring 227

242 1 2 tacoma-cr-2800t... 3 Figure 11. Representation of a deice display, showing an associated critical alert Configure the settings for the alert status icon, the deice frame, and deice label text as follows: 1 Alert status icon The settings that control whether and where to display alert status icons in topology maps are as follows. Some settings are in the topoiz.properties file and others are in the status.properties file. Whether to display alert status icons in the topology maps The setting in the status.properties file that instructs the system to display alert status is status.enabled=true. Position The setting in the topoiz.properties file that specifies the position of the alert status icon.is topoiz.status.position=ne. This instructs the system to place the alert status icon in the north east (top right) corner of the frame containing the deice. 2 Deice frame The settings are specified in the topoiz.properties file. To locate these settings, search for the sections that begins with the comment # Node dimensions and # Corner arc. 1] 2] 3] 4] 5] 6] 7] 8] 9] 10] 11] # Node dimensions (not used in legacy mode). topoiz.node.height=60 topoiz.node.width=100 # Node resizability # Options: LOCKED (Fixed height and width) # TIGHT_HEIGHT (Fixed height, ariable width) topoiz.node.resizeability=tight_height # Corner arc (not used in legacy mode). topoiz.node.arc=10 Table 45. Description of settings for the deice frame Line Description 2 Specifies the height of the frame. 3 Specifies the width of the frame. Note: There is no wrapping of text for the deice label, so if you want to show all of the deice label text you must either increase this width alue or decrease the text font size using the topoiz.node.fontsize setting. 228 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

243 Table 45. Description of settings for the deice frame (continued) Line Description 8 Specifies how the topoiz.node.height and topoiz.node.width settings are handled. The default is TIGHT_HEIGHT. Using LOCKED means the alues set in the topoiz.node.height and topoiz.node.width parameters are used for the deice frame. Using TIGHT_HEIGHT maintains the topoiz.node.height setting, but does not maintain the topoiz.node.width setting, which means the deice frame is automatically widened as necessary to accommodate the deice label while keeping the width to the minimum. 11 Specifies the roundness of the corners of the frame. The higher the alue, the more rounded the corners. 3 Deice label The settings are specified in the topoiz.properties file. To locate these settings, search for the releant section that begins with the comment # Font settings. 1] 2] 3] 4] # Font settings topoiz.node.font=arial,heletica topoiz.node.fontsize=10 topoiz.node.fontstyle=0 Table 46. Description of settings for the deice label text Line Description 2 Specifies the typeface to use for the deice label text. 3 Specifies the font size to use for the deice label text. 4 Specifies the font style to use for the deice label text. Related concepts: TopoViz icons on page 219 In a topology map, icons represent types of deice or network elements. You can customize these icons. Related tasks: Changing alert settings on page 230 If required, you can change the settings for alerts. You can change the frequency of updates to alert seerity information, replace the default icons that represent alert seerity, configure how alert status is retrieed, and configure other alert settings. Configuring position of nodes in Network Views after rediscoery: You can configure how newly discoered and existing nodes are positioned in the network iews after a rediscoery of the network. By default, the TopoViz client changes the layout of a network iew map as newly discoered nodes are added to the map. The position of existing nodes is not guaranteed when the map layout is updated because the layout is goerned by factors such as connectiity information obtained during the discoery. To change the default behaior and configure Network Manager to maintain the position of existing nodes and isually separate new nodes from nodes already present in the network iews, edit the following parameters. Chapter 4. Configuring 229

244 Note: This behaior works best with the Symmetric Layout. Other layout options take other factors into account which can affect the position of existing nodes. For example, the Circular Layout places greater emphasis on presenting nodes in a circular layout than maintaining node positions, while the Hierarchical and Orthogonal layouts place greater emphasis on routing the connections between nodes using orthogonal lines than maintaining exact node positions. 1. Go to NCHOME/precision/profiles/TIPProfile/etc/tnm and open the topoiz.properties file. 2. Locate the topoiz.node.freezeold parameter and change the alue to true (the default alue is false). The true setting maintains the position of existing nodes, while new nodes are placed in a row at the top of the map, clearly separating the new nodes from nodes not added during the last rediscoery. The new nodes are placed in one or more rows at the top of the map with a horizontal and ertical spacing of 20 pixels by default. 3. Log out of the Network Manager GUI and restart the browser. This is required for the true setting to take effect. 4. Optional: You can further adjust the positioning of new nodes using the following parameters in the topoiz.properties: You can set whether the new nodes are placed at the top or bottom of the map using the topoiz.node.new.placement parameter. The default setting is top, change it to bottom to hae the new nodes placed at the bottom of the network iew map. You can set the horizontal spacing between new nodes in pixels using the topoiz.node.new.spacing.horizontal parameter. The default setting is 20 pixels, change it to a different pixel count to position each new node closer to each other or further apart horizontally. You can set the ertical spacing between new nodes in pixels using the topoiz.node.new.spacing.ertical parameter. The default setting is 20 pixels, change it to a different pixel count to position each new node closer to each other or further apart ertically. Note: All additional settings discussed in this step only take effect if the topoiz.node.freezeold is set to true. Changing alert settings: If required, you can change the settings for alerts. You can change the frequency of updates to alert seerity information, replace the default icons that represent alert seerity, configure how alert status is retrieed, and configure other alert settings. Related reference: Configuring the display of extra information associated with a deice on page 226 Information such as alert status and maintenance state of a deice is displayed in a colored border around the deice. You can configure the colors, icons, and positioning of the elements used to display this information. 230 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

245 Changing the frequency of alert seerity updates: If required, change how often the alert seerity information is updated from the Tioli Netcool/OMNIbus Web GUI. To change the frequency with which the alert seerity is updated: 1. On the serer where the Web Applications are installed, open the ITNMHOME/profiles/TIPProfile/etc/tnm/status.properties file. 2. Make the following changes: To change the frequency of alert seerity updates in the network iew tree, change the alue of the status.tree.updateperiod property. The alue is in seconds. For example: status.tree.updateperiod=60 To change the frequency of alert seerity updates in the topology map, change the alue of the status.map.updateperiod property. The alue is in seconds. For example: status.map.updateperiod=60 3. Sae and close the file. Changing the icons for alert seerity leels: You can change the alert status icons used to represent alert seerity leels in the Network Views GUI. Changing icons for alert seerity leels in the network iews: If you want different alert status icons to represent alert seerity leels in the Network View GUI, replace the default icons. The required formats for replacement icons are as follows: For the network iew tree: GIF or PNG files. For the topology map: GIF, PNG, or SVG files. GIF or SVG files. To replace a default icon: 1. Create the image for the security icon that you want to replace and copy the image to ITNMHOME/profiles/TIPProfile/etc/tnm/resource/. 2. Open the ITNMHOME/profiles/TIPProfile/etc/tnm/status.properties file and make the following changes. a. In the Tree status images section of the files, point the property for the required seerity to the new image. For example, to replace the default critical.gif file for seerity leel 5 with your own new image: status.tree.image.5=status/<filename for new critical icon>.gif b. In the Map status images section of the files, point the property for the required seerity to the new image. For example, to replace the default critical.gif file for seerity leel 5 with your own new image: status.map.image.5=status/<filename for new critical icon>.gif 3. Repeat the steps for each default icon that you want to replace. 4. Sae and close the file. Chapter 4. Configuring 231

246 Changing icons for alert seerity leels in topology map tabular layout: If you want different alert status icons to represent alert seerity leels in the topology map tabular layout option, replace the default icons. The required formats for replacement icons for the topology map table iew are GIF or PNG files. To replace a default icon: 1. Create the image for the security icon that you want to replace and copy the image to ITNMHOME/profiles/TIPProfile/etc/tnm/resource/. 2. Open the ITNMHOME/profiles/TIPProfile/etc/tnm/status.properties file and in the Net View Table status images section of the files, point the property for the required seerity to the new image. For example, to replace the default ac16_critical04_24.gif file for seerity leel 5 with your own new image: status.table.image.5=status/<filename for new critical icon>.gif 3. Repeat the steps for each default icon that you want to replace. 4. Sae and close the file. Configuring on-demand AEL filters for the Network View tree: When you click on an alert status icon in the Network View tree, a filtered AEL is displayed. You can configure the Network View tree to define these filters on demand, which uses less memory. Configuring AEL filters to be defined for all Network Views in the Network View Tree uses a large amount of heap memory, especially with deep, highly structured naigation trees with a large number of parent iews, and might cause performance issues. You can configure the Network View tree to define AEL filters for only the Network View that is currently displayed. Defining filters on demand uses less memory. By default, on-demand filtering is disabled and filters are created for all iews when the Network View tree is displayed. Filters are always created for the leaf nodes in the Network View Tree. Leaf nodes are Network Views (not containers) that do not themseles contain other Network Views. Aggregated alert status is shown for all nodes in the Network View tree regardless of whether on-demand AEL filters are enabled or not. To configure on-demand AEL filters in the Network View tree, complete the following steps: 1. On the serer where the Web Applications are installed, back up and edit the ITNMHOME/profiles/TIPProfile/etc/tnm/status.properties file. 2. Make the following changes: To enable on-demand AEL filters in the Network View tree, change the alue of the status.tree.filterael property to false. AEL filters are created only when you open a Network View. When you open an AEL from a parent Network View in the Network View tree that has not been opened in the topology display pane, the AEL shows eents for all deices. If you click on the Network View, and then launch an AEL from that iew, the AEL is filtered to show eents on only those deices in that iew. To disable on-demand AEL filters in the Network View tree, change the alue of the status.tree.filterael property to true. AEL filters are created for 232 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

247 Table 47. Alert status settings eery iew in adance. When you open an AEL from any Network View, the AEL is filtered to show eents on only those deices in that iew. 3. Sae and close the file. Alert status settings: The alert status settings control whether and how deices are displayed in topology maps, and the frequency with which the settings are updated. The alert status settings are contained in the ITNMHOME/profiles/TIPProfile/etc/ tnm/status.properties file. You can control the following settings: Setting status.color. background. seerity status.color. foreground. seerity status. globalfilter status. hopiew. linestyle status.map. updateperiod status.map. maxnodes status.map. image.seerity status.map. image.size. seerity status.map. image.xoffset. seerity status.map. image.yoffset. seerity Description Specifies background status color for each alert seerity leel. Specifies the color of the deice label text for each alert seerity leel. Filters out certain types of alerts from being displayed in the status of deices in the topology maps. For example status.globalfilter= NmosPingFail would preent ping fail eents from affecting the displayed status of deices in the topology iews. This property filters on the alerts.status ObjectSerer table. Indicates whether to display the alert status on links between nodes in the Hop View. Specifies how often the system updates the alerts status settings in the topology maps. Indicates the maximum number of nodes for which alert status can be displayed in a single topology map. Specifies the icons that are used to represent deice alert status in the topology map. To customize these icons, create a GIF or SVG icon with the releant name and sae it to the following location: ITNMHOME/profiles/TIPProfile/etc/tnm/resource/. Specifies the size of the icons to use to represent deice alert status in topology maps. Specifies x-axis and y-axis offset of the icon. The NE (northeast) positioning specified in the ITNMHOME/profiles/TIPProfile/etc/tnm/topoiz.properties file would place the icon so that it is touching the frame surrounding the deice. The offset alues moes the icon slightly down and to the left, so that it is positioned just inside the frame. Chapter 4. Configuring 233

248 Table 47. Alert status settings (continued) Setting Description status.map. topcolor. saturation. seerity status.map. bottomcolor. saturation. seerity status.map. topcolor. brightness. seerity Specify saturation and brightness adjustment controls that control the gradient of the background status color for each alert seerity leel. status.map. bottomcolor. brightness. seerity status.netiew. linestyle status.none. enabled status. registration. deicealert status. registration. threadscalefactor status. registration. threadlimit status.table. image.seerity status.table. image.sortup status.table. image.sort Down status.tree. bookmarks. enabled status.tree. libraries. enabled Indicates whether to display the alert status on links between nodes in the Network Views. Indicates whether the none status for a deice is represented in the same way as the clear status. Tip: none status means that no eents hae been receied for the deice. clear status means that earlier eents of seerity leel 1 or more hae now been cleared on the deice. Set this property to true to include alerts from deices in the alert status of iews that are based on deice components. For example, if you hae an MPLS iew that includes only interfaces, you might want to exclude alerts from the chassis of the deices containing those interfaces. To exclude alerts from the main nodes, set this property to false. Defines how many threads are used to register alert status. For example, if the status.registration.threadlimit property is set to 200 (the default), then one extra thread is used for each additional 200 iews that a user has. This setting applies to all users. Increase the default setting if alert status takes a long time to appear on maps and in the Network View tree. More threads use more resources. Ensure that you hae enough resources on the serer to run the extra threads, based on your total number of users and iews. Threads are increased up to the maximum defined by the status.registration.threadlimit property. The upper limit of the number of threads allowed per user to register alert status. Sets a limit for the scaling of threads defined by the status.registration.threadlimit property. Specifies the icons that are used to represent deice alert status in the topology map tabular layout. To customize these icons, create a GIF or SVG icon with the releant name and sae it to the following location: ITNMHOME/profiles/TIPProfile/etc/tnm/resource/. Specify how to sort alert seerity icons in the topology map tabular layout. Specifies whether deice status is displayed in the Network View Bookmark tree. Set to true to enable and false to disable. Specifies whether deice status is displayed in the Network View Library tree. Set to true to enable and false to disable. 234 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

249 Table 47. Alert status settings (continued) Setting status.tree. maxiews status.tree. registration. ondemand Description Specifies the maximum number of iews that a Network View tree can contain and still display alert status. To enable on-demand AEL filters in the Network View tree, change the alue of the status.tree.registration.ondemand property to true. When you open an AEL from a parent Network View in the Network View tree that has not been opened in the topology display pane, the AEL shows eents for all deices. If you click on the Network View, and then launch an AEL from that iew, the AEL is filtered to show eents on only those deices in that iew. Enabling on-demand filters uses less heap memory. To disable on-demand AEL filters in the Network View tree, change the alue of the status.tree.registration.ondemand property to false. When you open an AEL from any Network View, the AEL is filtered to show eents on only those deices in that iew. status.tree. updateperiod status.tree. image.seerity Where seerity is a string or number specifying alert status seerity status.iew. enabled Specifies how often the system updates the alerts status settings in the Network Views and Structure Browser Naigation Panel. Specifies the icons that are used to represent deice alert status in the network iew tree. To customize these icons, create a GIF or SVG icon with the releant name and sae it to the following location: ITNMHOME/profiles/TIPProfile/etc/tnm/resource/. Specifies whether deice status is displayed in Network Views and in table iews. Set to true to enable and false to disable. Configuring isual differentiation between manually added and discoered deices: You can configure the topology iews to highlight manually added deices in the topology map using an oerlay icon. To configure the system to highlight manually added deices: 1. Edit the following file: ITNMHOME/profiles/TIPProfile/etc/tnm/ topoiz.properties. 2. Within this file check the topoiz.topologymanagement.differentiate_manual alue. topoiz.topologymanagement.differentiate_manual=true: configures manually added deices and connections to be differentiated from discoered deices and connections. topoiz.topologymanagement.differentiate_manual=false: manually added deices and connections are not differentiated from discoered deices and connections. By default, this alue is set to true. 3. If the setting is topoiz.topologymanagement.differentiate_manual=true, then check the oerlay image configuration for differentiation of manually added nodes. # Oerlay definitions - Manual deice topoiz.oerlay.image.manual=manualoerlay.sg topoiz.oerlay.position.manual=e topoiz.oerlay.size.manual=10 topoiz.oerlay.xoffset.manual=-2 This configuration snippet contains the following settings: Chapter 4. Configuring 235

250 The oerlay image used for is called manualoerlay.sg. This file is located at ITNMHOME/profiles/TIPProfile/etc/tnm/resource/. You can change the oerlay image used by copying a different.sg icon to ITNMHOME/profiles/ TIPProfile/etc/tnm/resource/manualoerlay.sg. By default, the icon appears to the right (E stands for east) of the manually added deice. Other options are N, S, W, NE, NW, SW, SEand C, where C means centred on the deice. 4. Sae the topoiz.properties file. Switching to V3.8 isualization mode: Topology icons and the way they are presented hae changed from preious ersions. Use this information if you want to switch back to the V3.8 mode of topology presentation. To switch back to the V3.8 mode of topology presentation you must edit the following configuration files: ITNMHOME/profiles/TIPProfile/etc/tnm/topoiz.properties ITNMHOME/profiles/TIPProfile/etc/tnm/status.properties 1. Open the file ITNMHOME/profiles/TIPProfile/etc/tnm/topoiz.properties. 2. Search for the text legacy. 3. Each time the text legacy is found, follow the instructions in the comments. 4. Sae the ITNMHOME/profiles/TIPProfile/etc/tnm/topoiz.properties file. 5. Open the file ITNMHOME/profiles/TIPProfile/etc/tnm/status.properties. 6. Search for the text legacy. 7. Each time the text legacy is found, follow the instructions in the comments. 8. Sae the ITNMHOME/profiles/TIPProfile/etc/tnm/status.properties file. Configuring the AEL in composite topology iews You can configure the type of Actie Eent List (AEL) iew that is opened when a network node is clicked in one of the default iews that combine network iews and AELs. The Network Health View and the Fault-Finding View are composite topology iews, that is, they combine a network iews and an AEL. When you click a node in the network iew or a node in the network iew tree, the AEL refreshes to show any eents for that node. You can configure the type of AEL that is displayed. You might want to configure the type of AEL if you want to display an AEL iew that contains a subset of columns. You can also use this procedure to troubleshoot errors with AELs not appearing in composite iews, if the error states that a particular AEL iew cannot be found. To configure the AEL iew, complete the following steps: 1. Back up and edit the ITNMHOME/profiles/TIPProfile/etc/tnm/ topoiz.properties configuration file and identify the following section: # AEL iew descriptions. topoiz.webtop.iew.name=default topoiz.webtop.iew.type=global 2. Change the alues to correspond to the type and name of the AEL that you want to use. 3. Sae and close the file. 236 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

251 Loading updated MIB information To ensure that the MIB browser reflects the most up-to-date MIB information, load updated MIB information by running the ncp_mib command-line application. You need to run the ncp_mib command-line application only when new MIBs are added to the NCHOME/precision/mibs directory. It is run once during installation, so if you do not add new MIBs, you do not need run it again. Important: All MIBs must be alid in order to be parsed correctly. The ncp_mib command is case-sensitie and expects a suffix of.mib (not.mib). The prefix can be a combination of upper or lower case. When run, ncp_mib populates the ncmib schema in the NCIM database to proide a central store of all MIB information that Network Manager can query. The ncmib schema within the NCIM database is defined in NCHOME/etc/precision/ MibDbLogin.cfg; the default alue is MIB. There is only one ncp_mib process for all domains. So, there is no -domain option for ncp_mib. There are also no process dependencies for this command. In a distributed installation, ncp_mib is installed on the Tioli Integrated Portal serer, that is, on the same serer as the Network Manager Web applications. If your MIB database gets corrupted or if you want to import a new MIB that conflicts with one that was imported preiously, note the arious command-line options by running ncp_mib -help. Tip: If you are uncertain what the result will be of running ncp_mib, run it with the -dryrun option. You can see the results, but the database will not be altered. To update the MIB information, complete the following steps on the serer where the Tioli Integrated Portal is installed. 1. Copy any new MIB files to the NCHOME/precision/mibss directory. 2. Ensure that the database login credentials are correct. The only configuration parameters required for the ncp_mib command-line application are the database login credentials for the ncim database. These are stored in a configuration file, NCHOME/etc/precision/MibDbLogin.cfg. Note that because ncp_mib is domain-independent, this file does not hae domain-specific ariants as other configuration files do. 3. Start the ncp_mib process by issuing the ncp_mib command. To erify that a MIB has successfully loaded, query the database table ncmib.mib_modules by entering the following command from the NCIM database prompt (this example assumes that NCIM is running on DB2): select * from ncmib.mib_modules where modulename = RFC1213-MIB ; If the MIB loaded, a table is displayed containing a modulename of RFC1213-MIB. You can also erify that MIBs are loaded by running the ncp_mib command with the -messageleel info option. A message similar to the following informs you that the MIBs are being processed: 09/10/08 12:41:08: Information: I-MIB : [ t] Resoling references for module RFC1213-MIB Chapter 4. Configuring 237

252 When processing completes, a message states that the MIBs hae been committed to the database. Tip: For information on using the SNMP MIB Browser and graphing MIB ariables, see the IBM Tioli Network Manager IP Edition Network Troubleshooting Guide. Configuring the presentation of eents from unmanaged deices You can configure the way eents from unmanaged deices (deices that are not polled by Network Manager) are presented to network operators. You can configure Network Manager to present unmanaged eents in the AEL in the following ways: Filtering out the unmanaged eents so that they do not appear at all in the AEL, or tagging these eents in the AEL so that you know that they come from unmanaged deices. Tagging these eents in the AEL so that the network operator knows that they come from unmanaged deices. In this case, the NmosManagedStatus field associated with an unmanaged eent in the AEL displays the alue 1 (Operator unmanaged) or 2 (System unmanaged). Tioli Netcool/OMNIbus probes and eent sources from other network management systems can generate eents on deices or interfaces that hae been marked as Unmanaged in Network Manager. An unmanaged deice is usually marked Unmanaged because it is undergoing maintenance and may therefore generate unnecessary network eents. The following topics describe how to manage network eents from an unmanaged deice. Remember: Unmanaged deices are shown in the network map with an oerlaid double-ended wrench icon. Partially unmanaged deices (deices in which only certain interfaces are unmanaged) are shown in the network map using an oerlaid single-ended wrench icon. Filtering out eents from unmanaged deices You can filter eents from unmanaged deices so that they do not appear in the AEL. 1. In the AEL, select the Filter Builder. 2. Create a new filter or edit the existing filter to filter out all eents where the NmosManagedStatus field is equal to 1 (Operator unmanaged) or 2 (System unmanaged). Once you hae completed this operation and applied the filter to the AEL, eents from unmanaged deices no longer appear in the AEL. 238 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

253 Tagging eents from unmanaged deices You can tag eents in the AEL so that you know that these eents come from unmanaged deices. 1. In the AEL, select the View Builder. 2. Create a new iew or edit the existing iew to display the NmosManagedStatus field associated with an eent. This field displays the managed status of the deice or interface the eent was raised for. For unmanaged deices, this field displays the alue 1 (Operator unmanaged) or 2 (System unmanaged). Once you hae completed this operation and applied the iew to the AEL, each eent in the AEL will display the managed status of the associated network deice or interface. Configuring reports for existing installations You can configure the network management reports proided by Network Manager to use with Tioli Common Reporting. To enable network management reports, you must hae Tioli Common Reporting installed. If you installed Network Manager GUI components on a machine where Tioli Common Reporting was already present, then you do not need to complete these steps. To configure network management reports: 1. Log into the machine where you hae Network Manager GUI components and Tioli Common Reporting installed. 2. Run the script to configure network management reports either from the installer launchpad or the command line: Option From the launchpad From the command line Description 1. Go to the directory where you extracted the Network Manager installation package. 2. Start the launchpad as the user that installed Network Manager by entering the./launchpad.sh command. 3. Select the Postinstallation menu. 4. Expand Install Network Manager reports to use with TCR and click Install Network Manager reports. 1. Go to the NCHOME/precision/products/ tnm/bin directory. 2. Run the configtcr.sh -d NCIM_database_password -p TIP_administrator_password -i install script. Chapter 4. Configuring 239

254 Migrating the Cognos content store from Derby to DB2 The default content store database that is used by Cognos is suitable for demonstration purposes, but it is not to be used as the content store database in a production enironment. If you use network management reports with Tioli Common Reporting, you hae the option of migrating the content store database from the default Derby database to DB2. Network Manager uses the database set up in Tioli Common Reporting for the Cognos content store. If you hae already changed your Tioli Common Reporting setup to use another database other than the default Derby database, you might not need to perform this task. For more information about the default Derby database and the alternatie content store databases for Tioli Common Reporting, see the following technote: You need to perform the following steps to switch to DB2 for the Cognos content store regardless of whether you are installing Network Manager on a serer with an existing Tioli Common Reporting installation, or you are installing Tioli Common Reporting on a serer with existing Network Manager GUI and Tioli Integrated Portal components already installed. This is because any installation of Tioli Common Reporting uses Derby by default, and you need to change to DB2 manually. To migrate the Cognos content store from the default Derby database to DB2: 1. Log in to the Network Manager GUI as the itnmadmin user and export the content store data as described in c8bi/8r4m0/index.jsp?topic=/com.ibm.swg.im.cognos.inst_cr_winux doc/ inst_cr_winux_id3024c8bi_createanexportdeploymentspecif.html. Note: When clicking Select the entire content store to export the entire content store, ensure you select to include user account information. 2. Log in as the user that created the Network Manager database. In this example 'db2inst1': su - db2inst1 3. Source the DB2 enironment ariables:. sqllib/db2profile 4. Create the Cognos database using the following Network Manager script, calling out the database user, in this case 'ncim': a. Go to $NCHOME/precision/scripts/sql/db2. b. Type./create_db2_cognos_database.sh database_name user_name, where database_name is the required name of the Cognos content store database, and user_name is the DB2 user that is used to connect to the database. For example, to create a database called ITNMCM for the DB2 user ncim, type./create_db2_cognos_database.sh ITNMCM ncim. Note: If your DB2 database is on a different serer to Network Manager, then copy the script to the serer where your database is located and run the script there. 5. As the user who installed Network Manager, configure the content store data source access using the following Network Manager script: a. Source the enironment ariables:. /opt/ibm/tioli/netcool/en.sh b. Go to $NCHOME/precision/products/tnm/bin. 240 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

255 Enabling failoer c. Type./modify_cognos_cm -filename full path to file -dbname database_name -dbport port_number -dbhost host_name -dbtype db2 -username user_name -password password. For example, use a command line similar to the following: UNIX $NCHOME/precision/products/tnm/bin/modify_cognos_cm -filename TCR_installation_directory/cognos/configuration/cogstartup.xml -dbname ITNMCM -dbport dbhost abc -dbtype db2 -username db2inst1 -password password 6. As the user who installed Network Manager, restart the Tioli Integrated Portal serer: go to $NCHOME/precision/bin and issue itnm_stop tip and then itnm_start tip. Note: If your enironment ariables are set, you can run the stop / start command from any directory. 7. Import the content store as described in infocenter/c8bi/8r4m0/index.jsp?topic=/ com.ibm.swg.im.cognos.ug_cra doc/ug_cra_i_importdata.html Note the following for the import procedure: a. In the Deployment archie box, select the archie you preiously created during the export procedure. b. When selecting the options you want, ensure you select Reports should be upgraded for your conflict resolution choice. 8. After migrating the Cognos content store from Derby to DB2, uninstall the Derby content database as described in the 'Uninstall Cognos Content Database' topic in the IBM Cognos 8 Business Intelligence Installation and Configuration Guide on the IBM Cognos information center: com.ibm.swg.im.cognos.inst_cr_winux doc/ inst_cr_winux_id7376uninstallcognoscontentdatabase.html Important: Note the following for the Derby uninstall procedure: When using Tioli Common Reporting the cmd is tcr_cogconfig.sh (instead of cogconfig.sh). You can enable failoer in your Network Manager enironment to ensure that the different components are kept running and aailable. About failoer In your Network Manager enironment, a failoer architecture can be used to configure your system for high aailability, minimizing the impact of computer or network failure. Failoer can be implemented for each of the following products and components, which can be installed when you run the Network Manager installer: The Network Manager core components, including the Polling engine and Eent Gateway (which embeds the root cause analysis component) The NCIM topology database Tioli Netcool/OMNIbus, including the ObjectSerer (for eent management) The Tioli Netcool/OMNIbus Web GUI, which is installed within the Tioli Integrated Portal serer framework Chapter 4. Configuring 241

256 Restriction: Network Manager does not support the Tioli Integrated Portal load balancing feature that the Tioli Netcool/OMNIbus Web GUI does. You must decide for which components you want to implement failoer, and the number of computers required for high aailability. About NCIM topology database high aailability Network Manager allows you to configure the NCIM topology database for high aailability, minimizing the impact of computer or network failure. The following sections proide an oeriew of NCIM topology database high aailability and explain how to configure it. High aailability refers to a computing enironment in which the hardware and software components remain operational during planned outages (for example, regular maintenance operations) and unplanned outages (for example, unexpected hardware, network, and software failures). One component that needs to be operational all of the time is the NCIM topology database. Note: In preious Network Manager releases, users could include an NCIM topology database failoer configuration by using NCIM replication (also referred to as NCIM topology database replication). The NCIM replication feature has been replaced by an NCIM topology database high aailability feature that is proided by the supported database. For example, DB2 proides a feature called high aailability disaster recoery (HADR) that you use to configure a failoer configuration for the NCIM topology database. To configure a failoer configuration for the NCIM topology database and thus proide users a high aailability enironment for running database applications and accessing information stored in the NCIM topology database, you need to become familiar with the following background topics and tasks: High aailability strategies proided by the database, in this case DB2 Failoer architecture for NCIM topology database and Network Manager core processes Tasks associated with installing the database, in this case DB2 Note: DB2 proides the tools necessary for installing and configuring the NCIM topology database (and core processes) to use the DB2 HADR feature. For information on how to install and configure DB2, see Related information below for links to your DB2 Information Center. High aailability strategies that DB2 proides DB2 proides a number of strategies for improing the aailability of your database solution, including: Redundancy An important strategy for maintaining high aailability is haing redundant components. If a component fails, a secondary or backup copy of that component can take oer, enabling the database to remain aailable to user applications. You can create redundancy at the database leel, by haing two databases: a primary database that normally processes all or most of the application workload; and a secondary database that can take oer the workload if the primary database fails. In a DB2 High Aailability Disaster Recoer (HADR) enironment, this secondary database is called the standby database. Failoer Failoer is the transfer of workload from a primary system to a secondary system in the eent of a failure on the primary system. When 242 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

257 workload has been transferred like this, the secondary system is said to hae taken oer the workload of the failed primary system. Clustering A cluster is a group of connected machines that work together as a single system. When one machine in a cluster fails, cluster managing software transfers the workload of the failed machine onto other machines. The DB2 High Aailability Feature enables integration between IBM DB2 serer and cluster managing software. The DB2 documentation proides information and examples on each of these strategies. See Related information below for links to your DB2 Iinformation Center. Failoer architecture for NCIM topology database and Network Manager core processes Failoer of the Network Manager core processes can be implemented by setting up primary and backup Network Manager installations that run on different serers and domains. Both installations can either connect to a single Tioli Netcool/OMNIbus ObjectSerer or to a irtual pair of ObjectSerers. Network Manager failoer can be implemented with NCIM topology database high aailability or without NCIM topology database high aailability. If you choose to implement failoer with NCIM topology database high aailability, you will do so through the high aailability feature that is proided by the supported database. For example, DB2 proides the High Aailability Disaster Recoer (HADR) feature that you use to configure a failoer configuration for the NCIM topology database. Tasks associated with installing the DB2 database To use an existing DB2 database as the NCIM topology database on UNIX, you must install DB2, configure an instance, and create a database before Network Manager is installed. Chapter 4. Configuring 243

258 Related concepts: Network Manager failoer architecture (core processes) on page 247 Failoer of the Network Manager core processes can be implemented by setting up primary and backup Network Manager installations that run on different serers and domains. Both installations can either connect to a single Tioli Netcool/OMNIbus ObjectSerer or to a irtual pair of ObjectSerers. Example failoer hosting with NCIM topology database high aailability on page 253 This is an example of failoer hosting where the failoer configuration includes a copy of the NCIM topology database on the backup installation. Related tasks: Setting up existing DB2 databases on UNIX on page 44 To use an existing DB2 database as the topology database on UNIX, you must install DB2, configure an instance, and create a database before Network Manager is installed. Related information: IBM DB2 Version 10.1 Information Center For more information on DB HADR, search the IBM DB2 Version 10.1 Information Center. Suggested search terms inlcude "high aailability". IBM DB2 Version 9.7 Information Center For more information on DB2 9.7 HADR, search the IBM DB2 Version 9.7 Information Center. Suggested search terms inlcude "high aailability". Failoer architectures Network Manager failoer is implemented independently of failoer in the products and components with which it integrates. Before configuring failoer, you must understand the failoer architectures that can be implemented to help ensure high aailability of your Network Manager installation. A Network Manager failoer installation contains a primary and a backup Network Manager serer on which the core components are installed. If the primary serer fails due to problems with the hardware or software, the backup serer assumes the role of the primary serer. For a more robust enironment, you can additionally include one or more of the following failoer configurations: A primary and a backup Tioli Netcool/OMNIbus ObjectSerer Tioli Netcool/OMNIbus Web GUI data source failoer An NCIM topology database high aailability configuration Note: In preious Network Manager releases, users could include an NCIM topology database failoer configuration by using NCIM replication (also referred to as NCIM topology database replication). The NCIM replication feature has been replaced by an NCIM topology database high aailability feature that is proided by the supported database. For example, DB2 proides a feature called high aailability disaster recoery (HADR) that you use to configure a failoer configuration for the NCIM topology database. This NCIM topology database high aailability configuration ensures that network polling can continue on the backup installation, and topology iews replicated. To accommodate either hardware or software failure, and for optimum performance of your enironment, implement your failoer solution on more than one computer. 244 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

259 Related information: IBM DB2 Version 10.1 Information Center For more information on DB HADR, search the IBM DB2 Version 10.1 Information Center. Suggested search terms inlcude "high aailability". IBM DB2 Version 9.7 Information Center For more information on DB2 9.7 HADR, search the IBM DB2 Version 9.7 Information Center. Suggested search terms inlcude "high aailability". ObjectSerer failoer architecture You can deploy Tioli Netcool/OMNIbus by using a scalable multitiered architecture, so that the system can continue to operate to full capacity (and with minimal eent loss) in the eent of ObjectSerer, ObjectSerer Gateway, or proxy serer failure. The components in the architecture sit within three tiers (or layers): collection, aggregation, and display. The basic failoer configuration consists of a primary ObjectSerer and a backup ObjectSerer that are connected by a bidirectional ObjectSerer Gateway in the aggregation layer, with no collection or display layers connected. The modular design of the multitiered architecture means that any system can start with a single pair of aggregation ObjectSerers, and then hae collection or display components added at any time in the future. The following figure shows an example of the basic failoer configuration in the aggregation layer. Chapter 4. Configuring 245

260 Web GUI client Helpdesk/CRM (Gateway client) RDBMS (Gateway client) Desktop client Other Gateway Other Gateway ObjectSerer AGG_P AGG_GATE ObjectSerer AGG_B Aggregation layer (AGG_V) Probes Probes ObjectSerer Host Computer Unidirectional Gateway Bidirectional Gateway Figure 12. ObjectSerer failoer architecture To minimize the impact of computer failure, the primary ObjectSerer (AGG_P) and backup ObjectSerer (AGG_B) run on two separate computers. The bidirectional ObjectSerer Gateway (AGG_GATE) runs on the backup ObjectSerer computer, and synchronizes the ObjectSerers. The primary and backup ObjectSerers are configured as a irtual aggregation pair (AGG_V) to which probes, and other clients such as the Eent Gateway, can directly connect. The concept of a irtual pair helps to facilitate seamless fail oer to the backup ObjectSerer if the primary ObjectSerer becomes unaailable, and fail back when the primary ObjectSerer is actie again. In the figure, example targets to which alerts can be forwarded from the aggregation layer are also shown. For full information about setting up ObjectSerer failoer in the collection, aggregation, and display layers of the multitiered architecture, see the IBM Tioli Netcool/OMNIbus Installation and Deployment Guide at publib.boulder.ibm.com/infocenter/tiihelp/8r1/topic/com.ibm.tioli.nam.doc/ welcome_ob.htm. 246 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

261 Related concepts: Network Manager failoer architecture (core processes) Failoer of the Network Manager core processes can be implemented by setting up primary and backup Network Manager installations that run on different serers and domains. Both installations can either connect to a single Tioli Netcool/OMNIbus ObjectSerer or to a irtual pair of ObjectSerers. Related tasks: Configuring ObjectSerer failoer on page 263 The way in which you configure ObjectSerer failoer is dependent on the Tioli Netcool/OMNIbus ersion. About the Tioli Netcool/OMNIbus failoer configuration files: Tioli Netcool/OMNIbus V7.3 or later, proides a set of configuration files that you can apply to ObjectSerers and ObjectSerer Gateways in order to implement the multitiered architecture. These files are aailable in the $NCHOME/omnibus/extensions/multitier directory, and include: SQL import files that can be applied to each ObjectSerer, in order to update the database schema with the required configuration; for example, additional columns, conersions, and automations ObjectSerer Gateway files that can be used to configure the gateways in the architecture Important: When using the configuration files supplied in Tioli Netcool/OMNIbus V7.3 or later, you must adhere to the defined naming conention for the components in each layer of the multitiered architecture. To implement failoer in the aggregation layer, use the naming conentions depicted in Figure 12 on page 246; that is, AGG_P for the primary ObjectSerer, AGG_B for the backup ObjectSerer, AGG_V for the irtual pair, and AGG_GATE for the bidirectional ObjectSerer Gateway. In earlier ersions of Tioli Netcool/OMNIbus, no configuration files are proided, and it is not mandatory to comply with these naming conentions. For further information about the multitiered configuration files, and the naming conentions for the components in the multitiered architecture, see the IBM Tioli Netcool/OMNIbus Installation and Deployment Guide at publib.boulder.ibm.com/infocenter/tiihelp/8r1/topic/com.ibm.tioli.nam.doc/ welcome_ob.htm. Network Manager failoer architecture (core processes) Failoer of the Network Manager core processes can be implemented by setting up primary and backup Network Manager installations that run on different serers and domains. Both installations can either connect to a single Tioli Netcool/OMNIbus ObjectSerer or to a irtual pair of ObjectSerers. When you connect to a Network Manager serer, the associated domain under which the processes run needs to be identified. Network Manager proides a irtual domain that can be used when running in failoer mode. Any connection to this irtual domain is routed to the Network Manager installation that is running as the primary serer in the failoer architecture. This routing capability is proided by the Virtual Domain component. Chapter 4. Configuring 247

262 The following figure shows the high-leel failoer architecture for the primary and backup Network Manager core processes, which are set up in two separate domains. ObjectSerer AGG_P Aggregation layer (AGG_V) AGG_GATE ObjectSerer AGG_B Eent Gateway Eent Gateway nco_p_ncpmonitor nco_p_ncpmonitor TCP connection Virtual Domain Virtual Domain Primary Network Manager installation Backup Network Manager installation Figure 13. Network Manager failoer architecture In the figure, both the primary and backup installations connect to a irtual pair of ObjectSerers. In each domain: The Virtual Domain component (ncp_irtualdomain) manages failoer, and raises health check eents to indicate whether the domain is healthy. The Probe for Tioli Netcool/OMNIbus (nco_p_ncpmonitor) connects to the irtual ObjectSerer pair, and forwards the health check eents. The Eent Gateway (ncp_g_eent) connects to the irtual ObjectSerer pair, reads in all health check eents, and then passes the eents to the Virtual Domain component. These health check eents are used to trigger failoer. A TCP socket connection is required between the Virtual Domain processes, to copy data from the primary domain to the backup domain. This ensures that the topology is in sync when failoer occurs. Note: If you implement failoer, then you must ensure that both the primary and backup installations are using identical encryption keys. If the encryption keys are not identical, then the backup poller does not function correctly during failoer. To ensure that both the primary and backup installations are using identical encryption keys, copy the following file from the primary serer to the same location on the backup serer: $NCHOME/etc/security/keys/conf.key. If you enter all SNMP community strings on the command line and do not encrypt them, you do not need to do this task. For more information on changing the encryption key, see the IBM Tioli Network Manager IP Edition Administration Guide. 248 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

263 NCIM implementations for failoer Network Manager failoer can be implemented with the following options: Without NCIM topology database high aailability: In this failoer configuration, a single NCIM topology database is shared by the two Network Manager domains. With NCIM topology database high aailability: This failoer configuration protects against data loss by replicating data changes from the source NCIM topology database in the primary Network Manager domain to one or more target NCIM topology databases in the backup Network Manager domain. The source NCIM topology database is referred to as the primary database and the target NCIM topology database is referred to as the standby database. This approach remoes the single point of failure because both the primary and backup Network Manager domains connect to whicheer database is acting as the primary database. Note: In preious Network Manager releases, users could include an NCIM topology database failoer configuration by using NCIM replication (also referred to as NCIM topology database replication). The NCIM replication feature has been replaced by an NCIM topology database high aailability feature that is proided by the supported database. For example, DB2 proides a feature called high aailability disaster recoery (HADR) that you use to configure a failoer configuration for the NCIM topology database. In either of these cases, all entities in the topology are stored under the primary domain name, and all poll policies are configured for the primary domain. There is no entry in the domainmgr table for the backup domain. As a result, the NmosDomainName field for an eent in the alerts.status table will always be populated with the primary domain name when failoer is configured. Note: To configure NCIM topology database high aailability using DB2 HADR, you set up the HADR enironment by following the instructions proided in the DB2 documentation. See Related information below for links to your DB2 Information Center. You also perform tasks to configure Network Manager to work with DB2 HADR. Chapter 4. Configuring 249

264 Related concepts: ObjectSerer failoer architecture on page 245 You can deploy Tioli Netcool/OMNIbus by using a scalable multitiered architecture, so that the system can continue to operate to full capacity (and with minimal eent loss) in the eent of ObjectSerer, ObjectSerer Gateway, or proxy serer failure. Failoer on the backup installation on page 258 All processes on the backup installation point to the NCIM topology database on the primary installation and the NCIM topology database on the primary can be a stand alone database or one configured for high aailability. About NCIM topology database high aailability on page 242 Network Manager allows you to configure the NCIM topology database for high aailability, minimizing the impact of computer or network failure. The following sections proide an oeriew of NCIM topology database high aailability and explain how to configure it. Example failoer hosting with NCIM topology database high aailability on page 253 This is an example of failoer hosting where the failoer configuration includes a copy of the NCIM topology database on the backup installation. Related tasks: Configuring failoer of the Network Manager core processes on page 270 You can configure failoer of the Network Manager core processes by using the $NCHOME/etc/precision/ConfigItnm.cfg file to enable failoer. Setting up existing DB2 databases on UNIX on page 44 To use an existing DB2 database as the topology database on UNIX, you must install DB2, configure an instance, and create a database before Network Manager is installed. Configuring Network Manager to work with DB2 HADR on page 274 You can configure Network Manager core processes to use the DB2 catalog and the Network Manager GUI to operate in the DB2 HADR (high aailability disaster recoery) enironment by editing seeral properties and configuration related files. Related information: IBM DB2 Version 10.1 Information Center For more information on DB HADR, search the IBM DB2 Version 10.1 Information Center. Suggested search terms inlcude "high aailability". IBM DB2 Version 9.7 Information Center For more information on DB2 9.7 HADR, search the IBM DB2 Version 9.7 Information Center. Suggested search terms inlcude "high aailability". Tioli Netcool/OMNIbus Web GUI data source failoer The Web GUI implements data source failoer. If a primary and a backup ObjectSerer are aailable, you can set up connections to both ObjectSerers so that if the primary ObjectSerer fails, the Web GUI will fail oer and use the backup ObjectSerer as the source of its eents. 250 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

265 Related concepts: Tioli Netcool/OMNIbus Web GUI data sources on page 155 A data source is another term for an ObjectSerer or ObjectSerer failoer pair used by the Web GUI for eent information. Related tasks: Configuring data source failoer for the Tioli Netcool/OMNIbus Web GUI on page 267 If you hae a failoer pair of ObjectSerers to which the Web GUI should connect, you can configure data source failoer by using the ncwdatasourcedefinitions.xml data source configuration file in your Web GUI installation. Serer allocation for failoer Any primary system must be installed on a separate host to a backup system, so that if the primary host fails, the backup host is unaffected. Ideally, the primary ObjectSerer, backup ObjectSerer, primary Network Manager serer, backup Network Manager serer and Tioli Integrated Portal serer would each be installed on separate hosts. Howeer, this might not be practical. Related reference: Constraints for installing and starting components on page 14 Some components must be installed and started before others. Use this information as well as the installation examples to understand the order in which you must install and start components. Example failoer hosting without NCIM topology database high aailability: This is an example of failoer hosting where the failoer configuration does not include a copy of the NCIM topology database on the backup installation. Note: In preious Network Manager releases, users could include an NCIM topology database failoer configuration by using NCIM replication (also referred to as NCIM topology database replication). The NCIM replication feature has been replaced by an NCIM topology database high aailability feature that is proided by the supported database. For example, DB2 proides a feature called high aailability disaster recoery (HADR) that you use to configure a failoer configuration for the NCIM topology database. The following figure shows an example of hosting ObjectSerer and Network Manager failoer using four host machines. Chapter 4. Configuring 251

266 Host Machine 1 Host Machine 2 Backup ObjectSerer Primary Network Manager Backup Network Manager Primary ObjectSerer Host Machine 3 Host Machine 4 Tioli Integrated Portal NCIM topology database Figure 14. Example failoer hosting For performance reasons, the NCIM topology database requires a high bandwidth connection to the Tioli Integrated Portal serer. If host machine 3 has multiple CPUs and sufficient memory, you can install NCIM on host machine 3. Install the core components on both host machines 1 and 2, and install the Web applications on host machine 3. Install the NCIM topology database on host machine 4. Note: If you implement failoer, then you must ensure that both the primary and backup installations are using identical encryption keys. If the encryption keys are not identical, then the backup poller does not function correctly during failoer. To ensure that both the primary and backup installations are using identical encryption keys, copy the following file from the primary serer to the same location on the backup serer: $NCHOME/etc/security/keys/conf.key. If you enter all SNMP community strings on the command line and do not encrypt them, you do not need to do this task. For more information on changing the encryption key, see the IBM Tioli Network Manager IP Edition Administration Guide. Related concepts: About NCIM topology database high aailability on page 242 Network Manager allows you to configure the NCIM topology database for high aailability, minimizing the impact of computer or network failure. The following sections proide an oeriew of NCIM topology database high aailability and explain how to configure it. Example failoer hosting with NCIM topology database high aailability on page 253 This is an example of failoer hosting where the failoer configuration includes a copy of the NCIM topology database on the backup installation. 252 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

267 Example failoer hosting with NCIM topology database high aailability: This is an example of failoer hosting where the failoer configuration includes a copy of the NCIM topology database on the backup installation. Note: In preious Network Manager releases, users could include an NCIM topology database failoer configuration by using NCIM replication (also referred to as NCIM topology database replication). The NCIM replication feature has been replaced by an NCIM topology database high aailability feature that is proided by the supported database. For example, DB2 proides a feature called high aailability disaster recoery (HADR) that you use to configure a failoer configuration for the NCIM topology database. The following figure shows an example of hosting ObjectSerer and Network Manager failoer using fie host machines. Host Machine 1 Host Machine 2 Backup ObjectSerer Primary Network Manager Backup Network Manager Primary ObjectSerer Host Machine 4 Host Machine 3 Host Machine 5 NCIM topology database Tioli Integrated Portal NCIM topology database Figure 15. Example failoer hosting with backup NCIM topology database For performance reasons, the NCIM topology database requires a high bandwidth connection to the Tioli Integrated Portal serer. If host machine 3 has multiple CPUs and sufficient memory, you can install the primary NCIM on host machine 3. Install the core components on both host machines 1 and 2, and install the Web applications on host machine 3. Install the primary NCIM topology database on host machine 4 and the backup NCIM topology database on host machine 5. Chapter 4. Configuring 253

268 Related concepts: Failoer on the backup installation on page 258 All processes on the backup installation point to the NCIM topology database on the primary installation and the NCIM topology database on the primary can be a stand alone database or one configured for high aailability. Example failoer hosting without NCIM topology database high aailability on page 251 This is an example of failoer hosting where the failoer configuration does not include a copy of the NCIM topology database on the backup installation. Network Manager failoer architecture (core processes) on page 247 Failoer of the Network Manager core processes can be implemented by setting up primary and backup Network Manager installations that run on different serers and domains. Both installations can either connect to a single Tioli Netcool/OMNIbus ObjectSerer or to a irtual pair of ObjectSerers. About NCIM topology database high aailability on page 242 Network Manager allows you to configure the NCIM topology database for high aailability, minimizing the impact of computer or network failure. The following sections proide an oeriew of NCIM topology database high aailability and explain how to configure it. Failoer operation of the Network Manager core processes Failoer of the Network Manager core processes is managed by the Virtual Domain process, ncp_irtualdomain. Use this information to understand how Network Manager failoer and failback are triggered. Health check eents and failoer Failoer is goerned by health checks, which are configured to run periodically to assess the health of the primary and backup Network Manager domains. In the failoer enironment, all the processes in the primary and backup domains are started by the master process controller, ncp_ctrl. In each domain, ncp_ctrl also regularly monitors the processes that are under its control, and stores their status in the state.serices table. The Virtual Domain process applies filters (which are defined in the state.filters table) against the status records of some of the processes, and generates health check eents to indicate whether a domain is healthy. The filters are applied to: ncp_poller, the Polling engine Multiple filters can be defined for the Polling engine, one for each poller defined in the CtrlSerices.cfg file. ncp_g_eent, the Eent Gateway ncp_model, the topology manager Health check eents are generated locally within each domain, and can also be generated remotely by one domain on behalf of the other: Local domain: If eery status record passes the filters, the Network Manager serer is deemed healthy, and Virtual Domain generates a health check resolution eent for that domain. Each domain indicates to the other that it is healthy, by sending a resolution eent, which is routed ia the ObjectSerer. A domain expects to receie a resolution eent at an interal configured in the Virtual Domain process schema file ($NCHOME/etc/precision/ VirtualDomainSchema.cfg). 254 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

269 If one or more filters fail, indicating the failure of one or more local processes, Virtual Domain generates a health check problem eent, and additionally routes the problem eent to the other domain. Remote domain: If a local domain detects that its remote counterpart has not generated a health check resolution eent in the configured interal, the local domain generates a synthetic health check problem eent for the remote domain. For example, if the backup domain does not receie a health check resolution eent from the primary domain, the backup domain generates a health check problem eent for the primary domain. Health check eents are also generated when connectiity to the NCIM database is lost. Health check eents hae the eent identifier "ItnmHealthChk" in the EentId field of the alerts.status table. Related concepts: Network Manager failoer and failback on page 257 Failoer can be initiated by either the primary or backup domain, and is triggered when a health check problem eent is generated for the primary domain. Failback is triggered by a subsequent health check resolution eent for the primary domain. Related tasks: Configuring parameters for health checks on page 277 If required, you can configure preferred conditions under which health check eents are generated, by specifying identical OQL inserts to the Virtual Domain process schema file (VirtualDomainSchema.cfg) on both the primary and backup serers. Related reference: Network Manager status eents on page 161 Network Manager can generate eents that show the status of arious Network Manager processes. These eents are known as Network Manager status eents and hae the alerts.status AlertGroup field alue of ITNM Status. Process flow for health check eents: Health check resolution eents are generated by each Network Manager serer to indicate that it is in good health. A health check problem eent is one of the triggers for Network Manager failoer. The following figure shows the progression through the system of a health check eent that is generated by the primary Network Manager serer. Chapter 4. Configuring 255

270 ObjectSerer AGG_P Aggregation layer (AGG_V) AGG_GATE ObjectSerer AGG_B Eent Gateway Eent Gateway nco_p_ncpmonitor 9 9 nco_p_ncpmonitor Virtual Domain Virtual Domain 1 Primary Network Manager installation Backup Network Manager installation Figure 16. Process flow of a health check eent 1 Status report The ncp_ctrl process reports on the status of its managed serices. 2 Health diagnosis The Virtual Domain process uses its filters to perform a health check diagnosis: If the system is in good health, Virtual Domain generates a health check resolution eent and sends it to the Probe for Tioli Netcool/OMNIbus. By default, health check eents are sent to the probe eery 60 seconds. If the system is in poor health, Virtual Domain generates a health check problem eent and sends it to the Probe for Tioli Netcool/OMNIbus. 3 Health check eent forwarded to the ObjectSerer The Probe for Tioli Netcool/OMNIbus forwards the health check eent to the ObjectSerer. 4 Health check eent forwarded to the primary and backup Eent Gateway The ObjectSerer sends the health check eent to the Eent Gateway of the primary and backup serers. 5 Health check eent sent back to the primary and backup Virtual Domain The primary Eent Gateway sends the health check eent back to the Virtual Domain on the primary serer. The backup Eent Gateway also sends the health check eent to the Virtual Domain on the backup serer. For a health check resolution eent, Virtual Domain checks the time stamp on the eent to ensure the eent is not older than 5 minutes, and updates its state.domains table to show that the primary serer is in good health. 256 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

271 (The Eent Gateway also listens for health check eents from the backup serer. The state.domains table records the current state of both primary and backup serers.) For a health check problem eent, Virtual Domain updates its state.domains table to show that the primary serer is in poor health. Virtual Domain switches the backup serer to actie mode, and the primary serer goes on standby. 6 Health check failure generated on behalf of primary domain If the backup serer does not receie a health check resolution eent from the primary serer within the configured interal of 5 minutes, this indicates that the primary serer is not functioning properly or not communicating properly with the ObjectSerer. The backup Virtual Domain sends a health check problem eent to the Probe for Tioli Netcool/OMNIbus on behalf of the primary serer. Virtual Domain updates its state.domains table to show that the primary serer is in poor health. 7, 8, and 9 Failoer triggered The probe sends the health check problem eent to the ObjectSerer, which then forwards the health check problem eent to the Eent Gateway on both the primary and backup Network Manager serers: The Eent Gateway on the backup serer sends the health check problem eent to the Virtual Domain, which then switches the backup serer to actie mode. If the primary Eent Gateway is operational, it forwards the health check problem eent to the primary Virtual Domain. If Virtual Domain is operational, it switches the primary serer to standby mode. When the backup serer generates a health check resolution eent, the process flow is identical to that for the primary serer. Regularly-updated health check resolution eents for both primary and backup serers are held in the ObjectSerer and can be iewed using, for example, the Actie Eent List (AEL). If the health check problem eent is generated by the backup serer to indicate that the backup serer is in poor health, the same processes apply, except that the primary serer is not put on standby, and the backup serer is not switched to actie mode. The health check problem eent for the backup serer is present in the ObjectSerer and can be iewed using, for example, the Actie Eent List. Note: The Probe for Tioli Netcool/OMNIbus and Eent Gateway in both domains must be configured to access the same ObjectSerer, in order for health check eents to be successfully routed around the system. Network Manager failoer and failback Failoer can be initiated by either the primary or backup domain, and is triggered when a health check problem eent is generated for the primary domain. Failback is triggered by a subsequent health check resolution eent for the primary domain. An ItnmFailoer eent is generated by ncp_irtualdomain when a Network Manager domain fails oer or fails back. Failing oer When failoer occurs, the primary Network Manager domain goes into standby mode (if it is still running), and the backup domain becomes actie. Chapter 4. Configuring 257

272 The following changes occur when the backup domain becomes actie: The Eent Gateway synchronizes the eents with the ObjectSerer. The ncp_poller process resumes polling. The Eent Gateway switches from the standby filter (StandbyEentFilter) to the incoming eent filter (EentFilter). Network Manager continues to monitor the network and perform RCA. Howeer, network discoery is not performed, and the network topology remains static. When a primary Network Manager serer goes into standby mode, the following changes occur: The Eent Gateway switches from the incoming eent filter (EentFilter) to the standby filter (StandbyEentFilter). The ncp_poller process suspends all polls. For further information about the standby filter and incoming eent filter, see the IBM Tioli Network Manager IP Edition Eent Management Guide. Failing back When a primary Network Manager serer in standby mode resumes normal operation, it generates a health check resolution eent. The health check resolution eent passes through the system, and the recoered Network Manager serer becomes actie again. When the Virtual Domain process on the backup Network Manager serer receies the health check resolution eent, Virtual Domain switches the backup serer back to standby mode. The GenericClear automation in the ObjectSerer is triggered by the health check resolution eent, and clears the existing health check problem eent. Related concepts: Health check eents and failoer on page 254 Failoer is goerned by health checks, which are configured to run periodically to assess the health of the primary and backup Network Manager domains. Failoer on the backup installation: All processes on the backup installation point to the NCIM topology database on the primary installation and the NCIM topology database on the primary can be a stand alone database or one configured for high aailability. Note: In preious Network Manager releases, users could include an NCIM topology database failoer configuration by using NCIM replication (also referred to as NCIM topology database replication). The NCIM replication feature has been replaced by an NCIM topology database high aailability feature that is proided by the supported database. For example, DB2 proides a feature called high aailability disaster recoery (HADR) that you use to configure a failoer configuration for the NCIM topology database. The following figure shows an example Network Manager failoer architecture, where the NCIM topology database is configured for high aailability. 258 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

273 ObjectSerer AGG_P Aggregation layer (AGG_V) AGG_GATE ObjectSerer AGG_B nco_p_ncpmonitor Eent Gateway Failoer plug-in and other plug-ins Probes Failoer plug-in and other plug-ins Eent Gateway nco_p_ncpmonitor Virtual Domain TCP connection Virtual Domain ncp_ctrl Network ncp_ctrl ncp_disco ncp_model Primary Network Manager installation Primary NCIM database NCIM database Backup NCIM database ncp_model Backup Network Manager installation Figure 17. Example failoer architecture with NCIM high aailability The following figure differs from the preious one in that the NCIM topology database is not configured for high aailability. Chapter 4. Configuring 259

274 ObjectSerer AGG_P Aggregation layer (AGG_V) AGG_GATE ObjectSerer AGG_B nco_p_ncpmonitor Eent Gateway Failoer plug-in and other plug-ins Probes Failoer plug-in and other plug-ins Eent Gateway nco_p_ncpmonitor Virtual Domain TCP connection Virtual Domain ncp_ctrl Network ncp_ctrl ncp_disco ncp_model Primary Network Manager installation NCIM database ncp_model Backup Network Manager installation Figure 18. Example failoer architecture without NCIM high aailability Discoery Although the Discoery engine (ncp_disco) and the SNMP Helper Serer (ncp_d_helpser) are run, the backup Network Manager serer is not used for network discoery. When the backup domain is actie, the topology does not change. NCIM The backup ncp_model process does not update the NCIM topology database. Howeer, the ncp_model process continues to proide topology serices to processes such as the Eent Gateway. The NCIM topology database used by the Network Views and the Hop View continues to hold the most current ersion of the network topology until the primary Network Manager serer is restored and the system fails back. Polling When the backup domain is in standby mode, the Polling engine runs, but with polls suspended. When the backup domain becomes actie, its ncp_poller process starts polling, and uses the SNMP target details and poll policies from the primary domain. The ncp_poller process reads the SNMP configuration directly from its configuration file rather than relying on the discoery SNMP helper to read this file. 260 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

275 Virtual Domain The Virtual Domain component opens a socket connection to the Virtual Domain of the primary Network Manager serer. The topology data and any subsequent topology updates are copied from the ncp_model process on the primary serer to the ncp_model process on the backup serer. Eent Gateway When the backup domain is in standby mode, the Eent Gateway does not perform eent enrichment on the ObjectSerer. When the backup domain becomes actie, the Eent Gateway switches from the standby filter (StandbyEentFilter) to the incoming eent filter (EentFilter). Related concepts: Network Manager failoer architecture (core processes) on page 247 Failoer of the Network Manager core processes can be implemented by setting up primary and backup Network Manager installations that run on different serers and domains. Both installations can either connect to a single Tioli Netcool/OMNIbus ObjectSerer or to a irtual pair of ObjectSerers. About NCIM topology database high aailability on page 242 Network Manager allows you to configure the NCIM topology database for high aailability, minimizing the impact of computer or network failure. The following sections proide an oeriew of NCIM topology database high aailability and explain how to configure it. Example failoer hosting with NCIM topology database high aailability on page 253 This is an example of failoer hosting where the failoer configuration includes a copy of the NCIM topology database on the backup installation. Related reference: Limitations of the Network Manager failoer process A number of limitations apply for the failoer process. Limitations of the Network Manager failoer process A number of limitations apply for the failoer process. The discoery process (ncp_disco) performs network discoery only in the primary domain; the backup domain is not used for network discoery. The Network Manager Web applications do not implement failoer. When the backup domain becomes actie during failoer, the Web applications do not automatically connect to it. You can configure the Web applications to access the NCIM topology database on the backup domain as follows: 1. On the Tioli Integrated Portal serer where the Network Manager Web applications are installed, click Administration > Network > Database Access Configuration. 2. From the Configure NCIM Database Access portlet, enter the host, port, and authentication credentials for the NCIM topology database on the backup domain. Restrictions: When the backup domain is actie (with NCIM topology database high aailability): Do not attempt to configure discoery. Do not create or modify any polls or network iews. Do not attempt to manage or unmanage network deices. Chapter 4. Configuring 261

276 Restriction: Network Manager does not support the Tioli Integrated Portal load balancing feature that the Tioli Netcool/OMNIbus Web GUI does. If you are running more than one Tioli Integrated Portal serer, they each run independently. If one of the Tioli Integrated Portal serers fails, any remaining serers continue to run as indiidual entities. To minimize the effect of a serer failing: Set up each Tioli Integrated Portal serer with its own unique URL for authentication. Ensure that each of the serers is configured with the same set of users, roles, groups, preference profiles, and resources such as pages, iews, portlets, and reports. Configure the serers to whateer the database high aailability requires. For example, for DB2 you would configure the serers according the requirements of the DB2 HADR feature. Note: Failoer is not supported for the ITM monitoring agents in the Network Manager failoer architecture. Related tasks: Configuring failoer of the Network Manager core processes on page 270 You can configure failoer of the Network Manager core processes by using the $NCHOME/etc/precision/ConfigItnm.cfg file to enable failoer. Related information: IBM DB2 Version 10.1 Information Center For more information on DB HADR, search the IBM DB2 Version 10.1 Information Center. Suggested search terms inlcude "high aailability". IBM DB2 Version 9.7 Information Center For more information on DB2 9.7 HADR, search the IBM DB2 Version 9.7 Information Center. Suggested search terms inlcude "high aailability". Configuring failoer Use this information to configure failoer in your primary and backup Network Manager installations. Guidelines are also proided to optionally configure failoer of the integrating products and components. You must use the documentation for these products and components as the first point of reference. Before you begin to configure failoer, determine whether you want to implement a complete failoer solution for all the components, or failoer for Network Manager and a subset of components. Also decide on the number of computers and the deployment options. As a prerequisite to configuring failoer: You must hae installed and configured IBM Tioli Netcool/OMNIbus. If you intend to run a primary and backup ObjectSerer in failoer mode, you require two ObjectSerer installations. Tip: If you are using IBM Tioli Netcool/OMNIbus V7.3 or later, with the supplied failoer configuration files, be sure to adhere to the naming conentions for your ObjectSerers and ObjectSerer Gateways. You must hae installed a topology database. For NCIM topology database high aailability, you require two topology databases. 262 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

277 Note: In preious Network Manager releases, users could include an NCIM topology database failoer configuration by using NCIM replication (also referred to as NCIM topology database replication). The NCIM replication feature has been replaced by an NCIM topology database high aailability feature that is proided by the supported database. For example, DB2 proides a feature called high aailability disaster recoery (HADR) that you use to configure a failoer configuration for the NCIM topology database. You must hae installed and configured the Web GUI and the Network Manager Web applications within the Tioli Integrated Portal serer framework. You must hae installed the Network Manager core processes on the designated primary and backup serers, under two separate domains. Related concepts: About the Tioli Netcool/OMNIbus failoer configuration files on page 247 Tioli Netcool/OMNIbus V7.3 or later, proides a set of configuration files that you can apply to ObjectSerers and ObjectSerer Gateways in order to implement the multitiered architecture. Related reference: Constraints for installing and starting components on page 14 Some components must be installed and started before others. Use this information as well as the installation examples to understand the order in which you must install and start components. Configuring ObjectSerer failoer The way in which you configure ObjectSerer failoer is dependent on the Tioli Netcool/OMNIbus ersion. In a Tioli Netcool/OMNIbus installation, each computer on which the Tioli Netcool/OMNIbus components run must be configured with serer communication information that enables the components in the architecture to run and communicate with one another. Configure the connections data file with all the component details, as follows: UNIX Linux Update the communication information for all the Tioli Netcool/OMNIbus serer components in your deployment by manually editing the connections data file $NCHOME/etc/omni.dat, which is used to create the interfaces file. A suggested good practice is to add all the components in the entire deployment to a single omni.dat file, which can then be distributed to the $NCHOME/etc directory in all the computers in the deployment. You can then generate the interfaces file from each computer by running the $NCHOME/bin/nco_igen command. (Interfaces files are named $NCHOME/etc/interfaces.arch, where arch is the operating system name.) Sample configuration for the basic failoer architecture (aggregation layer only) The following sample configuration shows the serer communications details for the basic failoer architecture in the $NCHOME/etc/omni.dat file, where: AGG_P is the name of the primary ObjectSerer. AGG_B is the name of the backup ObjectSerer. AGG_V is the name of the irtual ObjectSerer pair. AGG_GATE is the name of the birdirectional ObjectSerer Gateway. NCO_PA represents the default name for the process agent. (If you hae configured process agents to manage the Tioli Netcool/OMNIbus processes and Chapter 4. Configuring 263

278 run external procedures, each uniquely-named process agent must be added with the appropriate host name and port number.) NCO_PROXY represents the default name for the proxy serer. (If you hae configured one or more proxy serers to reduce the number of direct probe connections to the ObjectSerers, each uniquely-named proxy serer must be added with the appropriate host name and port number.) [AGG_P] { Primary: primary_host.ibm.com 4100 } [AGG_B] { } Primary: backup_host.ibm.com 4150 [AGG_V] { } Primary: primary_host.ibm.com 4100 Backup: backup_host.ibm.com 4150 [AGG_GATE] { Primary: backup_host.ibm.com 4105 } [NCO_PA] { Primary: primary_host.ibm.com 4200 } [NCO_PROXY] { Primary: primary_host.ibm.com 4400 } For further details about configuring serer communication information, process agents, and proxy serers, see the Tioli Netcool/OMNIbus documentation at com.ibm.tioli.nam.doc/welcome_ob.htm. Related concepts: ObjectSerer failoer architecture on page 245 You can deploy Tioli Netcool/OMNIbus by using a scalable multitiered architecture, so that the system can continue to operate to full capacity (and with minimal eent loss) in the eent of ObjectSerer, ObjectSerer Gateway, or proxy serer failure. Configuring ObjectSerers and gateways for failoer: The following procedures proide guidance for setting up ObjectSerer failoer in Tioli Netcool/OMNIbus. Tioli Netcool/OMNIbus V7.3 or later on page 265: Configuring failoer Tioli Netcool/OMNIbus V7.2.1 or earlier on page 265: Configuring failoer For the most recent and complete information about ObjectSerer failoer, see the Tioli Netcool/OMNIbus documentation at infocenter/tiihelp/8r1/topic/com.ibm.tioli.namomnibus.doc/welcome_ob.htm. The Tioli Netcool/OMNIbus documentation should always be the first point of 264 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

279 reference, and takes precedence oer the information shown in the Network Manager documentation. Tioli Netcool/OMNIbus V7.3 or later: To configure failoer: 1. If not yet done, create the primary aggregation ObjectSerer AGG_P on the designated computer, and apply the SQL customization by running the nco_dbinit command with the supplied aggregation.sql import file: $NCHOME/omnibus/bin/nco_dbinit -serer AGG_P -customconfigfile $NCHOME/omnibus/extensions/multitier/objectserer/aggregation.sql If the ObjectSerer is already installed and running, apply the aggregation.sql import file against the ObjectSerer, as follows: UNIX Linux $NCHOME/omnibus/bin/nco_sql -serer AGG_P -user user_name password password < $NCHOME/omnibus/extensions/multitier/ objectserer/aggregation.sql 2. Start the primary ObjectSerer (if necessary): $NCHOME/omnibus/bin/nco_objser -name AGG_P & If you installed Tioli Netcool/OMNIbus using the Network Manager installer, you can, as an alternatie, run the itnm_start command in the $NCHOME/precision/bin directory: UNIX Linux itnm_start nco 3. Create (or update) the backup aggregation ObjectSerer AGG_B on another computer, and apply the SQL customization, as described in step 1. When you apply the SQL customization, the BackupObjectSerer property is automatically set to TRUE and the automations required by the backup ObjectSerer are enabled. 4. Start the backup ObjectSerer (if necessary), as described in step On the computer where the backup ObjectSerer is installed, configure the bidirectional aggregation ObjectSerer Gateway AGG_GATE: a. Copy the multitiered property files for the gateway from the $NCHOME/omnibus/extensions/multitier/gateway location, to the default location ($NCHOME/omnibus/etc) where configuration and properties files are held: AGG_GATE.map AGG_GATE.props AGG_GATE.tblrep.def b. Start the gateway AGG_GATE: $NCHOME/omnibus/bin/nco_g_objser_bi -propsfile $NCHOME/omnibus/etc/ AGG_GATE.props & Tioli Netcool/OMNIbus V7.2.1 or earlier: To configure failoer: 1. If not yet done, create the primary ObjectSerer on the designated computer by running the nco_dbinit command: $NCHOME/omnibus/bin/nco_dbinit -serer serer_name Where serer_name is the designated name; for example, NETCOOLPRI. 2. Start the primary ObjectSerer (if necessary): $NCHOME/omnibus/bin/nco_objser -name serer_name & 3. If not yet done, create the backup ObjectSerer on another computer, as described in step 1. Chapter 4. Configuring 265

280 4. Configure the backup ObjectSerer by editing its properties file ($NCHOME/omnibus/etc/serer_name.props), and set the BackupObjectSerer property to True. 5. Start the backup ObjectSerer, as described in step 2 on page On the computer where the backup ObjectSerer is installed, configure the bidirectional ObjectSerer Gateway to exchange alert data between the primary and backup ObjectSerers: a. Create the directory $NCHOME/omnibus/gates/gateway_name, for the gateway configuration files. b. Copy all of the files in $NCHOME/omnibus/gates/objser_bi to the $NCHOME/omnibus/gates/gateway_name directory. c. Rename the $NCHOME/omnibus/gates/gateway_name/objser_bi.map file to gateway_name.map. d. Rename the $NCHOME/omnibus/gates/gateway_name/objser_bi.props file to gateway_name.props. e. Edit the following entries in the gateway_name.props file: # Common Netcool/OMNIbus Properties. MessageLog : $OMNIHOME/log/gateway_name.log # Common Gateway Properties. Gate.MapFile : $OMNIHOME/gates/gateway_name/gateway_name.map Gate.StartupCmdFile : $OMNIHOME/gates/gateway_name/objser_bi.startup.cmd # Bidirectional ObjectSerer Gateway Properties. Gate.ObjectSererA.Serer : primary_objectserer Gate.ObjectSererA.Username : user_name Gate.ObjectSererA.Password : password Gate.ObjectSererA.TblReplicateDefFile: $OMNIHOME/gates/gateway_name/objser_bi.objectserera.tblrep.def Gate.ObjectSererB.Serer : backup_objectserer Gate.ObjectSererB.Username : user_name Gate.ObjectSererB.Password : password Gate.ObjectSererB.TblReplicateDefFile: $OMNIHOME/gates/gateway_name/objser_bi.objectsererb.tblrep.def Substitute gateway_name with the name assigned to the gateway, primary_objectserer and backup_objectserer with the ObjectSerer names, and specify the user name and password for connecting to the ObjectSerers. f. Copy the $NCHOME/omnibus/gates/gateway_name/gateway_name.props file to $NCHOME/omnibus/etc/gateway_name.props. g. Start the gateway: $NCHOME/omnibus/bin/nco_g_objser_bi & Connecting to an ObjectSerer failoer pair Each Network Manager installation that connects to an ObjectSerer needs a copy of the Tioli Netcool/OMNIbus interfaces file (on UNIX or Linux), or connections data file (on Windows). Assuming that serer communication information has been configured in your Tioli Netcool/OMNIbus installations, the $NCHOME/etc/interfaces.arch file (where arch represents the operating system name), or %NCHOME%\ini\sql.ini file should be aailable in the NCHOME installation location. 266 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

281 To ensure that Network Manager processes can connect to an ObjectSerer failoer pair, perform either of the following steps on the primary and backup Network Manager serers: If Network Manager and Tioli Netcool/OMNIbus are installed on the same computer, but in different NCHOME locations, copy the $NCHOME/etc/ interfaces.arch file or %NCHOME%\ini\sql.ini file from the Tioli Netcool/OMNIbus NCHOME location to the NCHOME installation location for Network Manager. If the two products are installed in the same NCHOME location, no action needs to be taken. If Network Manager and Tioli Netcool/OMNIbus are installed on different computers, copy the $NCHOME/etc/interfaces.arch file or %NCHOME%\ini\sql.ini file from the Tioli Netcool/OMNIbus NCHOME location to the NCHOME installation location on the computer where Network Manager is installed. For more information about configuring serer communication information and generating the Tioli Netcool/OMNIbus interfaces.arch file or sql.ini file, see the Tioli Netcool/OMNIbus documentation at infocenter/tiihelp/8r1/topic/com.ibm.tioli.namomnibus.doc/ welcome_ob.htm. Note: The name of the irtual ObjectSerer pair should be specified in the ConfigItnm.cfg file. Related tasks: Configuring ObjectSerer failoer on page 263 The way in which you configure ObjectSerer failoer is dependent on the Tioli Netcool/OMNIbus ersion. Configuring failoer using the ConfigItnm.cfg file on page 270 When you use the $NCHOME/etc/precision/ConfigItnm.DOMAIN.cfg file to configure failoer, the Network Manager processes will read the file on startup to identify whether they are running in the primary or backup domain. Configuring data source failoer for the Tioli Netcool/OMNIbus Web GUI If you hae a failoer pair of ObjectSerers to which the Web GUI should connect, you can configure data source failoer by using the ncwdatasourcedefinitions.xml data source configuration file in your Web GUI installation. This file is located in webgui_home_dir/etc/datasources, where webgui_home_dir is the installation directory for the Web GUI V7.3.1; for example, $NCHOME/omnibus_webgui. To configure data source failoer: 1. On the Tioli Integrated Portal serer where the Web GUI is installed, edit the data source configuration file as follows: a. Use the name attribute of the <ncwdatasourceentry> element to specify a label for the failoer pair of ObjectSerers; for example, VirtualObjectSererPair. b. Define the connection details for the primary and backup ObjectSerers by using the <ncwdatasourcedefinition> element and its child elements. Note: The name attribute alues of both the <ncwdatasourceentry> and <ncwdatasourcedefinition> elements must be identical. You must also define the ObjectSerer connections by using the ObjectSerer host names and port numbers, rather than the ObjectSerer names that are configured in the omni.dat or sql.ini file. Chapter 4. Configuring 267

282 For an example of the configuration required, see the sample code in Sample ncwdatasourcedefinitions.xml configuration for data source failoer on page 269. c. Restart the Tioli Integrated Portal serer for the changes to take effect. Use one of the following commands or methods: UNIX Linux itnm_start tip UNIX Linux startserer.sh serer1 For the most recent and complete information about configuring data source failoer in the Web GUI, see the Tioli Netcool/OMNIbus Web GUI documentation at topic/com.ibm.tioli.namomnibus.doc/welcome_ob.htm. The Web GUI documentation should always be the first point of reference, and takes precedence oer the information shown in the Network Manager documentation. 2. You must also set WebTopDataSource alue in ModelNcimDb.domain_name.cfg file to the same alue as the <ncwdatasourceentry> is set to in the ncwdatasourcedefinitions.xml file. Using the settings in the Sample ncwdatasourcedefinitions.xml configuration for data source failoer on page 269, the following example shows what changes you need to make: a. Go to NCHOME/etc/precision/ModelNcimDb.domain_name.cfg file and open it for editing. b. Find the insert that defines the WebTopDataSource: insert into dbmodel.access ( EnumGroupFilter, TransactionLength, ValidateCacheFile, WebTopDataSource ) alues ( "enumgroup in ( ifadminstatus, ifoperstatus, sysserices, iftype, cefcfrupoweradminstatus, cefcfrupoweroperstatus, TruthValue, entsensortype, entsensorscale, entsensorstatus, cefcmoduleadminstatus, cefcmoduleoperstatus, ipforwarding, cefcpowerredundancymode, EntityType, ospfifstate, ospfiftype, dot3statsduplexstatus, accessprotocol )", 500, 0, "OS" ); c. Change the WebTopDataSource alue in the following insert query to match the data source configured in the <ncwdatasourceentry> (in this case, change the alue OS to VirtualObjectSererPair): insert into dbmodel.access ( EnumGroupFilter, TransactionLength, ValidateCacheFile, WebTopDataSource ) alues ( "enumgroup in ( ifadminstatus, ifoperstatus, sysserices, iftype, cefcfrupoweradminstatus, cefcfrupoweroperstatus, TruthValue, entsensortype, entsensorscale, entsensorstatus, cefcmoduleadminstatus, cefcmoduleoperstatus, ipforwarding, cefcpowerredundancymode, EntityType, ospfifstate, ospfiftype, 268 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

283 <ncwdefaultdatasourcelist> <ncwdatasourceentry name="virtualobjectsererpair"/> </ncwdefaultdatasourcelist>... dot3statsduplexstatus, accessprotocol )", 500, 0, "VirtualObjectSererPair" ); Note: The Web GUI data source name is the name for the connection, and it has to be the same as what is set in the Web GUI. The name might not always be the same as the ObjectSerer name. d. Make this change on both the primary and backup core Network Manager serers. e. Restart ncp_ctrl. Sample ncwdatasourcedefinitions.xml configuration for data source failoer In the following sample code, the bold text identifies the alues that are applicable to data source failoer. <ncwdatasourcedefinition type="singlesererosdatasource" name="virtualobjectsererpair" enabled="true"> <ncwfailoerpairdefinition> <!--! The primary ObjectSerer to connect to.! - host : The hostname or IP address of the serer the ObjectSerer is installed on.! - port : The port number the ObjectSerer is listening on.! - ssl : Enables SSL connection to the ObjectSerer. [false true]! - minpoolsize : Specifies the minimum number of connections that will be added to the connection pool. Default alue is 5.! - maxpoolsize : Specifies the maximum number of connections that will be added to the connection pool. Default alue is 10.!--> <ncwprimaryserer> <ncwosconnection host="agg_p_hostname" port="agg_p_port" ssl="false" minpoolsize="5" maxpoolsize="10"/> </ncwprimaryserer> <!--! The optional failoer ObjectSerer to connect to.!--> <ncwbackupserer> <ncwosconnection host="agg_b_hostname" port="agg_b_port" ssl="false" minpoolsize="5" maxpoolsize="10"/> </ncwbackupserer> </ncwfailoerpairdefinition> </ncwdatasourcedefinition> Configuring ObjectSerer authentication If you are using an ObjectSerer as the central user registry for user management and authentication, and you want the ObjectSerer to be in a federated repository, you must use the script proided with Tioli Integrated Portal to configure the Virtual Member Manager adapter for the ObjectSerer. Configure the adapter for both of the ObjectSerers in the failoer pair. On each Tioli Integrated Portal serer where the Network Manager Web applications and the Web GUI are installed: 1. Go to the tip_home_dir/bin directory. 2. Enter the following command at the command line: confmm4ncos user password address port address2 port2 Where: user is the ID of a user with administratie priileges for the ObjectSerers. password is the password for the user ID. address is the IP address of the primary ObjectSerer. port is the port number used by the primary ObjectSerer. Chapter 4. Configuring 269

284 address2 is the IP address of the backup ObjectSerer. port2 is the port number used by the backup ObjectSerer. 3. Restart the Tioli Integrated Portal serer by using one of the following commands or methods: UNIX Linux itnm_start tip UNIX Linux startserer.sh serer1 Configuring failoer of the Network Manager core processes You can configure failoer of the Network Manager core processes by using the $NCHOME/etc/precision/ConfigItnm.cfg file to enable failoer. You must also use the $NCHOME/etc/precision/SericeData.cfg file to set up a TCP socket connection between the primary and backup Network Manager domains. Related concepts: Network Manager failoer architecture (core processes) on page 247 Failoer of the Network Manager core processes can be implemented by setting up primary and backup Network Manager installations that run on different serers and domains. Both installations can either connect to a single Tioli Netcool/OMNIbus ObjectSerer or to a irtual pair of ObjectSerers. Configuring failoer using the ConfigItnm.cfg file: When you use the $NCHOME/etc/precision/ConfigItnm.DOMAIN.cfg file to configure failoer, the Network Manager processes will read the file on startup to identify whether they are running in the primary or backup domain. The ConfigItnm.DOMAIN.cfg file contents must be identical on both the primary and backup domain serers. To configure failoer by using the ConfigItnm.DOMAIN.cfg file: 1. On the primary Network Manager serer, edit the $NCHOME/etc/precision/ ConfigItnm.PRIMARY_DOMAIN.cfg file as follows: a. Enable failoer and specify the primary, backup, and irtual domain names for the Network Manager processes. You can insert the required alues in the itnmdomain.failoer table by editing the following section in the file: insert into itnmdomain.failoer ( FailoerEnabled, PrimaryDomainName, BackupDomainName, VirtualDomainName ) alues ( 0, "NCOMS_P", "NCOMS_B", "NCOMS_V" ); Complete the alues section as follows, in the order listed: 270 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

285 Column FailoerEnabled Required alue Specify 1 to enable failoer for the defined primary and backup domains. The default alue of 0 means that failoer is disabled. PrimaryDomainName BackupDomainName VirtualDomainName Replace NCOMS_P with the actual name of the Network Manager primary domain in the failoer pair. Replace NCOMS_B with the actual name of the Network Manager backup domain in the failoer pair. Replace NCOMS_V with a designated name for the Network Manager irtual domain in the failoer pair. b. Specify the name of the ObjectSerer to which the Probe for Tioli Netcool/OMNIbus and the Eent Gateway will connect. Insert the required alue in the itnmdomain.objectserer table by editing the following section in the file: insert into itnmdomain.objectserer ( SererName ) alues ( "NCOMS" ); Complete the alues section as follows: Column SererName Required alue If you are using Tioli Netcool/OMNIbus V7.3 or later, and hae configured ObjectSerer failoer using the supplied multitiered configuration files and naming conentions for the multitiered configuration, specify AGG_V as the name of the irtual aggregation pair. The initial alue shown is either the name of the ObjectSerer that was installed by the Network Manager installer, or NCOMS if no ObjectSerer was installed. For earlier ersions of Tioli Netcool/OMNIbus, specify the alternatie name defined for the ObjectSerer irtual pair. If ObjectSerer failoer is not configured, specify the name of the single ObjectSerer being used. Note: No additional failoer configuration is required in the probe properties file. The default probe property settings proide adequate support for failoer when the probe runs. 2. Sae the file. 3. Copy the entire contents of the $NCHOME/etc/precision/ ConfigItnm.PRIMARY_DOMAIN.cfg file on the primary serer to the $NCHOME/etc/precision/ConfigItnm.BACKUP_DOMAIN.cfg file on the backup serer. Chapter 4. Configuring 271

286 Configuring the TCP socket connection between the domains: A TCP socket connection is required between the Virtual Domain processes in the primary and backup domains so that the topology data and topology updates can be copied to the backup domain. To configure the TCP connection: 1. On the primary Network Manager serer, manually start the ncp_irtualdomain process from the $NCHOME/precision/bin directory: ncp_irtualdomain -domain PRIMARYDOMAIN_NAME When the ncp_irtualdomain process starts for the first time, it writes a line to the $NCHOME/etc/precision/SericeData.cfg file, which lists TCP and multicast connection information for Network Manager processes. This line references ncp_irtualdomain, and includes the port on which the Virtual Domain component on the primary serer accepts TCP connections from the backup serer. For example: SERVICE: ncp_irtualdomain DOMAIN: VIRTUAL ADDRESS: PORT: 1234 SERVERNAME: myhostname DYNAMIC: NO Tip: The DYNAMIC:NO setting forces the ncp_irtualdomain process to use the same address and port the next time that it starts. 2. Sae the file. 3. Stop the ncp_irtualdomain process. 4. Copy the SERVICE: ncp_irtualdomain DOMAIN: VIRTUAL... line from the $NCHOME/etc/precision/SericeData.cfg file on the primary serer into the $NCHOME/etc/precision/SericeData.cfg file on the backup serer. Ensure that only a single SERVICE: ncp_irtualdomain DOMAIN: VIRTUAL... line is present in the file. Important: The SERVICE: ncp_irtualdomain DOMAIN: VIRTUAL... line must be identical in the $NCHOME/etc/precision/SericeData.cfg file in both domains. For further information about inter-process communication and the SericeData.cfg file, see the IBM Tioli Network Manager IP Edition Administration Guide. Related tasks: Defining a fixed port for the TCP socket connection To aoid firewall issues or port conflicts, you can define a fixed port for the TCP socket connection that enables the Virtual Domain process on the backup serer to connect to the process on the primary serer. Defining a fixed port for the TCP socket connection: To aoid firewall issues or port conflicts, you can define a fixed port for the TCP socket connection that enables the Virtual Domain process on the backup serer to connect to the process on the primary serer. On initial startup, the ncp_irtualdomain process on the primary serer adds a line to the NCHOME/etc/precision/SericeData.cfg file, with information about its connection details, including the port number. To define a fixed port, you must replace the initial port number with your required alue. To configure a fixed port for failoer: 272 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

287 1. Edit the $NCHOME/etc/precision/SericeData.cfg file on the primary serer as follows: a. Locate the line that references ncp_irtualdomain. For example: SERVICE: ncp_irtualdomain DOMAIN: VIRTUAL ADDRESS: PORT: 1234 SERVERNAME: myhostname DYNAMIC: NO In this example, the primary ncp_irtualdomain process accepts connections from the backup on port b. Change the PORT setting to the required alue. c. Make a note of the port number, and sae and close the SericeData.cfg file. 2. On the backup serer, edit the $NCHOME/etc/precision/SericeData.cfg file by updating the port number specified on the line that references ncp_irtualdomain. Important: This line must be identical in the $NCHOME/etc/precision/ SericeData.cfg file in both domains. For further information about the SericeData.cfg file, see the IBM Tioli Network Manager IP Edition Administration Guide. Related tasks: Configuring the TCP socket connection between the domains on page 272 A TCP socket connection is required between the Virtual Domain processes in the primary and backup domains so that the topology data and topology updates can be copied to the backup domain. Switching to failoer configuration with NCIM topology database high aailability: You can modify an existing failoer architecture to include NCIM topology database high aailability. Note: In preious Network Manager releases, users could include an NCIM topology database failoer configuration by using NCIM replication (also referred to as NCIM topology database replication). The NCIM replication feature has been replaced by an NCIM topology database high aailability feature that is proided by the supported database. For example, DB2 proides a feature called high aailability disaster recoery (HADR) that you use to configure a failoer configuration for the NCIM topology database. To configure NCIM topology database high aailability: 1. Set up NCIM topology database high aailability by using the high aailability feature that is proided by the supported database. In the case of DB2, you follow the procedures described in the DB2 documentation to configure a failoer configuration for the NCIM topology database using the HADR feature. See Related information below for links to your DB2 Information Center. 2. Configure Network Manager to work with the supported database. For example, perform the configuration tasks required to configure Network Manager to work with DB2 HADR. Chapter 4. Configuring 273

288 Related concepts: About NCIM topology database high aailability on page 242 Network Manager allows you to configure the NCIM topology database for high aailability, minimizing the impact of computer or network failure. The following sections proide an oeriew of NCIM topology database high aailability and explain how to configure it. Related tasks: Configuring failoer using the ConfigItnm.cfg file on page 270 When you use the $NCHOME/etc/precision/ConfigItnm.DOMAIN.cfg file to configure failoer, the Network Manager processes will read the file on startup to identify whether they are running in the primary or backup domain. Configuring Network Manager to work with DB2 HADR You can configure Network Manager core processes to use the DB2 catalog and the Network Manager GUI to operate in the DB2 HADR (high aailability disaster recoery) enironment by editing seeral properties and configuration related files. Related information: IBM DB2 Version 10.1 Information Center For more information on DB HADR, search the IBM DB2 Version 10.1 Information Center. Suggested search terms inlcude "high aailability". IBM DB2 Version 9.7 Information Center For more information on DB2 9.7 HADR, search the IBM DB2 Version 9.7 Information Center. Suggested search terms inlcude "high aailability". Configuring Network Manager to work with DB2 HADR You can configure Network Manager core processes to use the DB2 catalog and the Network Manager GUI to operate in the DB2 HADR (high aailability disaster recoery) enironment by editing seeral properties and configuration related files. Related concepts: About NCIM topology database high aailability on page 242 Network Manager allows you to configure the NCIM topology database for high aailability, minimizing the impact of computer or network failure. The following sections proide an oeriew of NCIM topology database high aailability and explain how to configure it. Network Manager failoer architecture (core processes) on page 247 Failoer of the Network Manager core processes can be implemented by setting up primary and backup Network Manager installations that run on different serers and domains. Both installations can either connect to a single Tioli Netcool/OMNIbus ObjectSerer or to a irtual pair of ObjectSerers. Related information: IBM DB2 Version 10.1 Information Center For more information on DB HADR, search the IBM DB2 Version 10.1 Information Center. Suggested search terms inlcude "high aailability". IBM DB2 Version 9.7 Information Center For more information on DB2 9.7 HADR, search the IBM DB2 Version 9.7 Information Center. Suggested search terms inlcude "high aailability". 274 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

289 Forcing Network Manager core processes to use the DB2 catalog: Use this information to force the Network Manager core processes to use the DB2 catalog. The Network Manager core processes need to use the DB2 catalog to obtain information about the alternate DB2 serer. To force the Network Manager core processes to use the DB2 catalog, you edit two configuration files and run the DB2 UPDATE ALTERNATE SERVER FOR DATABASE command. For information on DB2 commands, see Related information below for links to your DB2 Information Center. The two properties files DbLogins.Domaincfg and MibDbLogin.cfg that you need to edit are part of the Network Manager core installation. Thus, these configuration files reside on the serer on which Network Manager is installed. If you hae Network Manager failoer configured, then you would edit these configuration files on the primary and backup Network Manager serers. You run the UPDATE ALTERNATE SERVER FOR DATABASE command from the primary and secondary serers on which DB2 is installed. For details on this command, including the authorities required to run it, see Related information below for links to your DB2 Information Center. 1. On the Network Manager primary serer, open the $NCHOME/etc/precision/ DbLogins.Domaincfg file for editing and do the following: a. Search for the attribute called m_portnum. b. Set the alue of the m_portnum attribute to the alue 0 (zero). c. Write and quit the configuration file. Perform the same steps on the Network Manager secondary serer, if necessary. 2. On the Network Manager primary serer, open the $NCHOME/etc/precision/ MibDbLogin.cfg file for editing and do the following: a. Search for the attribute called m_portnum. b. Set the alue of the m_portnum attribute to the alue 0 (zero). c. Write and quit the configuration file. Perform the same steps on the Network Manager secondary serer, if necessary. 3. On the primary DB2 serer, run the UPDATE ALTERNATE SERVER FOR DATABASE command to update the alternate DB2 serer as follows: db2 update alternate serer for database database-alias using hostname hostname port port-number where: database-alias Specifies the alias of the database where the alternate serer is to be updated. hostname Specifies a fully qualified host name or the IP address of the node where the alternate serer for the database resides. port Specifies the port number of the alternate serer of the database manager instance. Perform the same steps on the secondary DB2 serer. The following example shows the UPDATE ALTERNATE SERVER FOR DATABASE command executed on the primary DB2 serer: db2 update alternate serer for database TAURUS using hostname co port Chapter 4. Configuring 275

290 The following example shows the UPDATE ALTERNATE SERVER FOR DATABASE command executed on the secondary DB2 serer: db2 update alternate serer for database TAURUS using hostname co port Related tasks: Setting a custom connection URL to identify the DB2 serers Use this information to set a custom connection URL to identify the primary and secondary DB2 serers. This connection will allow the Network Manager GUI to work in the DB2 HADR enironment. Related information: IBM DB2 Version 10.1 Information Center For more information on DB HADR, search the IBM DB2 Version 10.1 Information Center. Suggested search terms inlcude "high aailability". IBM DB2 Version 9.7 Information Center For more information on DB2 9.7 HADR, search the IBM DB2 Version 9.7 Information Center. Suggested search terms inlcude "high aailability". Setting a custom connection URL to identify the DB2 serers: Use this information to set a custom connection URL to identify the primary and secondary DB2 serers. This connection will allow the Network Manager GUI to work in the DB2 HADR enironment. To set a custom connection URL to identify the primary and secondary DB2 serers, you edit three properties files and specify the URL connection to the primary and secondary DB2 serers. You specify the same URL connection in each of the properties files. Two of the properties files $NCHOME/precision/profiles/ TIPProfile/etc/tnm/tnm.properties and $NCHOME/precision/profiles/ TIPProfile/etc/tnm/ncpolldata.properties are applicable to the Network Manager GUI. The $NCHOME/precision/platform/jaa/lib/ncp_topoiz/etc/tnm/ tnm.properties file is part of the Network Manager core installation. The following is an example URL connection setting that applies to both tnm.properties files: tnm.database.jdbc.url=jdbc:db2://<primary_db2_serer>:<primary_db2_port_number>/ <dbname>:clientreroutealternateserername=<secondary_db2_serer>; clientreroutealternateportnumber=<secondary_db2_port>; The following is an example URL connection setting that applies to the ncpolldata.properties file: ncpolldata.database.jdbc.url=jdbc:db2://<primary_db2_serer>:<primary_db2_port_number>/ <dbname>:clientreroutealternateserername=<secondary_db2_serer>; clientreroutealternateportnumber=<secondary_db2_port>; where: primary_db2_serer Specifies the name of the primary serer on which the DB2 database is running. primary_db2_port_number Specifies the port number of the primary serer on which the DB2 database is running. secondary_db2_serer Specifies the name of the secondary serer on which the DB2 database is running. secondary_db2_port Specifies the port number of the secondary serer on which the DB2 database is running. 276 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

291 1. Open the $NCHOME/precision/profiles/TIPProfile/etc/tnm/tnm.properties file for editing and do the following: a. Specify the URL connection to the primary and secondary DB2 serers. Use the example as a guide to specifying the syntax for the URL connection. b. Write and quit the properties file. 2. Open the $NCHOME/precision/profiles/TIPProfile/etc/tnm/ ncpolldata.properties file for editing and do the following: a. Specify the URL connection to the primary and secondary DB2 serers. Use the example as a guide to specifying the syntax for the URL connection. b. Write and quit the properties file. 3. Open the $NCHOME/precision/platform/jaa/lib/ncp_topoiz/etc/tnm/ tnm.properties file for editing and do the following: a. Specify the URL connection to the primary and secondary DB2 serers. Use the example as a guide to specifying the syntax for the URL connection. b. Write and quit the properties file. Related tasks: Forcing Network Manager core processes to use the DB2 catalog on page 275 Use this information to force the Network Manager core processes to use the DB2 catalog. Related information: IBM DB2 Version 10.1 Information Center For more information on DB HADR, search the IBM DB2 Version 10.1 Information Center. Suggested search terms inlcude "high aailability". IBM DB2 Version 9.7 Information Center For more information on DB2 9.7 HADR, search the IBM DB2 Version 9.7 Information Center. Suggested search terms inlcude "high aailability". Configuring parameters for health checks If required, you can configure preferred conditions under which health check eents are generated, by specifying identical OQL inserts to the Virtual Domain process schema file (VirtualDomainSchema.cfg) on both the primary and backup serers. The Virtual Domain component uses two database tables (config and state) in the ncp_irtualdomain database to support Network Manager failoer. The health check status records and filters are stored in these tables, which can be updated using the VirtualDomainSchema.cfg file. For further information about the config and state database tables, see the IBM Tioli Network Manager IP Edition Management Database Reference. To change the default settings for the health check parameters: 1. On the primary Network Manager serer, edit the $NCHOME/etc/precision/ VirtualDomainSchema.cfg file by specifying the following OQL inserts: Update the column alues in the config.defaults table to specify different time periods for the failoer health checks. For example, you can use the m_healthcheckperiod column to change the time interal between each health check. Or you can use the m_failoertime column to change the interal after which failoer is triggered by the backup domain, when the primary domain is deemed to be in poor health. The default settings are as follows: Chapter 4. Configuring 277

292 insert into config.defaults ( m_healthcheckperiod, m_failoertime, m_autotopologydownload ) alues ( 60, 300, 1 ); If required, update the state.filters table to define indiidual filters for each poller configured in the $NCHOME/etc/precision/CtrlSerices.cfg file. For example, for an additionally configured poller, PingPoller: insert into state.filters ( m_sericename, m_filter, m_description ) alues ( "PingPoller", "m_changetime > eal(time, $TIME ) and m_ctrlstate <> 7", "The Poller has been running within the last 300 seconds" ); 2. Sae and close the file. 3. Make identical changes to the $NCHOME/etc/precision/ VirtualDomainSchema.cfg file on the backup serer. Related concepts: Health check eents and failoer on page 254 Failoer is goerned by health checks, which are configured to run periodically to assess the health of the primary and backup Network Manager domains. Configuring process dependencies for failoer When running Network Manager in failoer mode, you must start the Network Manager processes by using the ncp_ctrl process. The order in which the processes start is important, and is defined by the process dependencies that are configured in the $NCHOME/etc/precision/CtrlSerices.cfg file. The Virtual Domain component (ncp_irtualdomain), which manages failoer, depends on all the processes it is monitoring because it cannot correctly determine their health until the processes are running. In the CtrlSerices.cfg file in both the primary and backup domains, the entry for the ncp_irtualdomain process has the following default configuration: dependson=[ "ncp_poller(default)", "ncp_g_eent" ]; No further configuration is needed to set the process dependencies for failoer, proided this default setting is retained. For further information about managing process dependencies, see the IBM Tioli Network Manager IP Edition Administration Guide. 278 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

293 Troubleshooting failoer Reiew this information for help in resoling issues you might encounter with failoer. Verifying the failoer setup of the Tioli Netcool/OMNIbus ObjectSerers If ObjectSerer failoer is configured, you might find it useful to erify the failoer setup of the ObjectSerers. 1. After starting both ObjectSerers, check that eents forwarded to the primary ObjectSerer are being displayed in the Actie Eent List. 2. Stop the primary ObjectSerer and check the ObjectSerer log file ($NCHOME/omnibus/log/PRIMARY_NAME.log) for failoer messages. 3. Check the Actie Eent List to confirm that eents forwarded to the backup ObjectSerer are being displayed. 4. Restore the primary ObjectSerer to a running state and erify that failback has occurred by checking its log file. For information about using the Tioli Netcool/OMNIbus commands to start and stop the ObjectSerer, see the Tioli Netcool/OMNIbus documentation at com.ibm.tioli.nam.doc/welcome_ob.htm. For information about starting and stopping the ObjectSerer using Network Manager commands, see the IBM Tioli Network Manager IP Edition Administration Guide. Tracking failoer of the Network Manager core processes You can perform a number of actions and checks to erify whether failoer of the Network Manager core processes is operating as expected. Tracking failoer on startup To ensure that the primary domain starts running as the actie domain, start the primary domain and its Virtual Domain process before starting the backup domain. If the backup domain is started before the primary Virtual Domain process has started, the backup domain can become actie, start polling the network, and raise health check problem eents about the primary domain. This issue, howeer, resoles itself after the primary Virtual Domain starts and health check eents are transmitted between the domains. At startup, the topology and policies are copied from the primary domain to the backup domain. The backup domain, howeer, cannot become actie (on failoer) until it has initialized its topology. To erify that the topology has been initialized: Check for a non-zero size topology cache file (Store.Cache.ncimCache.entityData.domain) inthe$nchome/ar/precision directory in the backup domain, where domain is the name of the current domain. Eent generation for startup: Monitor the Actie Eent List for ItnmSericeState and ItnmFailoerConnection Network Manager eents, to erify that the Virtual Domain processes are running, and that the TCP socket connection has been established: After each local ncp_irtualdomain process starts, the ncp_ctrl process generates an ItnmSericeState resolution eent. When a TCP connection is established between the Virtual Domain processes, an ItnmFailoerConnection resolution eent is generated. Chapter 4. Configuring 279

294 Tracking failoer when the system is in a steady state Normal, steady-state failoer behaior can be achieed only after the Virtual Domain processes in the primary and backup domains hae started and connected. Steady-state behaior can be defined as follows: The primary domain is actie, and operating as if it is the sole domain. The discoery process discoers the network, which is monitored by the poller, and eents are enriched by the Eent Gateway. The backup domain is in standby mode. Discoery is not initiated, and the poller keeps track of the policies configured in the primary domain, but does not poll any deices. The Eent Gateway also does not update eents in the ObjectSerer. You can run OQL queries on each domain to check on the status of processes: You can check the status of indiidual Network Manager processes by querying the database of the ncp_ctrl process. All processes that are running without issue should hae the setting sericestate = 4 in the serices.intray database table, to indicate that the serice is alie and running. The ncp_poller and ncp_g_eent processes each hae an associated config.failoer database table, which identifies their current failoer state. When running successfully in a steady state, these processes hae the setting FailedOer = 0 in the config.failoer OQL table in both domains. (The Virtual Domain process periodically updates the FailedOer field.) Tip: The config database schema is defined in the following files: $NCHOME/etc/precision/NcPollerSchema.cfg and $NCHOME/etc/precision/ EentGatewaySchema.cfg. For further information about running OQL queries, see the IBM Tioli Network Manager IP Edition Language Reference. For further information about how to identify which processes are running, see the IBM Tioli Network Manager IP Edition Administration Guide. Eent generation while in a steady state: Each domain generates eents about its state, based on the filters in the $NCHOME/etc/precision/VirtualDomainSchema.cfg file. These eents are generated at an interal configured in the m_healthcheckinteral field. Monitor the Actie Eent List for ItnmHealthChk and ItnmDatabaseConnection Network Manager eents to check whether the primary and backup domains are in good health: Each domain generates ItnmHealthChk resolution eents while it is healthy. The primary domain generates an ItnmDatabaseConnection problem eent if connection to the primary NCIM database is lost. If the connection is not re-established within the time interal defined for the NCIM state.filters entry in the VirtualDomainSchema.cfg file, the primary domain generates an ItnmHealthChk problem eent, about the primary domain. If the backup domain does not receie an ItnmHealthChk resolution eent from the primary domain within the configured m_failoertime interal, the backup domain generates a synthetic ItnmHealthChk problem eent on behalf of the primary domain. If either the primary or backup domain generates an ItnmHealthChk problem eent for the primary domain, failoer is triggered, and the backup domain becomes actie. If the primary domain is still running, it goes into standby mode. 280 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

295 Tip: For health check eents, the Node field identifies the domain for which the health check eent is generated. Tracking failoer and failback When failoer occurs, the backup domain becomes actie, the backup poller monitors the network, and the Eent Gateway updates ObjectSerer eents. You can run OQL queries to check on the status of the ncp_poller and ncp_g_eent processes. These processes each hae an associated config.failoer database table, which identifies their current failoer state. When the backup domain is actie, these processes hae the setting FailedOer = 1 in the config.failoer table, to indicate that they are in a failoer state. (If the primary domain is still running, the associated processes are also assigned the alue of FailedOer = 1.) When failback occurs, the backup domain goes into standby, and the primary domain becomes actie again. This is analogous to startup. Eent generation on failoer and failback: Monitor the Actie Eent List for ItnmHealthChk and ItnmFailoer Network Manager eents, to confirm failoer and failback behaior: An ItnmHealthChk problem eent about the primary domain indicates that failoer has been triggered. A subsequent ItnmHealthChk resolution eent about the primary domain indicates that failback has been triggered. ItnmFailoer eents are generated to indicate when a Network Manager domain fails oer or fails back. The eent description states whether the domain is the primary or backup, and whether it has become actie or gone into standby mode. Related reference: Network Manager status eents on page 161 Network Manager can generate eents that show the status of arious Network Manager processes. These eents are known as Network Manager status eents and hae the alerts.status AlertGroup field alue of ITNM Status. Inestigating why failoer occurred Because failoer can be initiated by either the primary or the backup domain, it is important to identify which domain initiated failoer. Perform either of the following actions: Reiew the Virtual Domain log file ($NCHOME/log/precision/ ncp_irtualdomain.domain.log) and the Eent Gateway log file ($NCHOME/log/precision/ncp_g_eent.DOMAIN.log). Reiew the ItnmHealthChk and ItnmFailoer eents in the Actie Eent List. (This is the simpler approach.) If the primary domain initiated failoer, this indicates a failure of one of the primary domain processes. You can check the status of the processes by querying the database of the ncp_ctrl process. The sericestate field in the serices.intray database table shows the current operational state for each of the processes. For further information about how to identify which processes are running, see the IBM Tioli Network Manager IP Edition Administration Guide. If the backup domain initiated failoer, this indicates a failure to route health check eents through the system due to one of the following reasons: Chapter 4. Configuring 281

296 The primary domain did not raise a health check eent (for example, because the primary serer was down). The Probe for Tioli Netcool/OMNIbus or Eent Gateway processes in both domains are not configured to access the same ObjectSerer. The Eent Gateway Failoer plug-in is not enabled. The Probe for Tioli Netcool/OMNIbus rules file has been modified such that the health check eent does not contain the required information. The backup Eent Gateway is not letting health check eents through the nco2ncp filter. For further information about enabling the Failoer plug-in and about eent filters, see the IBM Tioli Network Manager IP Edition Eent Management Guide. Also ensure that Virtual Domain is configured (in the $NCHOME/etc/precision/ CtrlSerices.cfg file) to hae a dependency on all processes listed in the $NCHOME/etc/precision/VirtualDomainSchema.cfg file. Related tasks: Configuring failoer using the ConfigItnm.cfg file on page 270 When you use the $NCHOME/etc/precision/ConfigItnm.DOMAIN.cfg file to configure failoer, the Network Manager processes will read the file on startup to identify whether they are running in the primary or backup domain. Related reference: Network Manager status eents on page 161 Network Manager can generate eents that show the status of arious Network Manager processes. These eents are known as Network Manager status eents and hae the alerts.status AlertGroup field alue of ITNM Status. Inestigating TCP connection issues A TCP socket connection is required between the Virtual Domain processes in the primary and backup domains so that the topology data and topology updates can be copied from the primary domain to the backup domain. If the TCP connection is lost: Check that Virtual Domain is configured (in $NCHOME/etc/precision/ CtrlSerices.cfg) to hae a dependency on all processes listed in the $NCHOME/etc/precision/VirtualDomainSchema.cfg file. Check that the ncp_config process is running. You can check the status of ncp_config by querying the database of the ncp_ctrl process. If running without issue, ncp_config should hae the setting sericestate = 4 in the serices.intray database table. For further information about how to identify which processes are running, see the IBM Tioli Network Manager IP Edition Administration Guide. If the TCP connection is not being established: Check that the $NCHOME/etc/precision/SericeData.cfg files in both domains hae the same entry for the Virtual Domain process. Check that boundary firewalls between the domains allow the TCP connection on the defined serer port. Check that the defined port is aailable for use on the primary domain. 282 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

297 Related tasks: Configuring process dependencies for failoer on page 278 When running Network Manager in failoer mode, you must start the Network Manager processes by using the ncp_ctrl process. The order in which the processes start is important, and is defined by the process dependencies that are configured in the $NCHOME/etc/precision/CtrlSerices.cfg file. Configuring the TCP socket connection between the domains on page 272 A TCP socket connection is required between the Virtual Domain processes in the primary and backup domains so that the topology data and topology updates can be copied to the backup domain. Sequence for restarting the serer processes in a failoer configuration Use this information as a guide for restarting the serer processes if your Network Manager failoer enironment requires a reboot of all the serers. Start the processes in the following order: 1. Start the primary ObjectSerer. Depending on your installation and configuration setup, you can use one of the following methods: Tioli Netcool/OMNIbus process control on UNIX, Linux, and Windows Serices on Windows The Tioli Netcool/OMNIbus nco_objser command The Network Manager itnm_start command For information about using the Tioli Netcool/OMNIbus commands to start the ObjectSerer, see the Tioli Netcool/OMNIbus documentation at com.ibm.tioli.nam.doc/welcome_ob.htm. For information about starting the ObjectSerer using Network Manager commands, see the IBM Tioli Network Manager IP Edition Administration Guide. 2. Start the backup ObjectSerer. 3. Start the topology database if not already running. 4. Start the primary Network Manager serer on which the core processes are installed, by using the itnm_start command or by starting the master process controller, ncp_ctrl. Also erify that the Virtual Domain process in the primary domain has started, by running the itnm_status command in the $NCHOME/precision/bin directory. For information about starting the Network Manager serer and processes, see the IBM Tioli Network Manager IP Edition Administration Guide. 5. Start the backup Network Manager serer on which the core processes are installed. Tip: The Tioli Integrated Portal serer, on which the Network Manager Web applications and the Tioli Netcool/OMNIbus Web GUI are installed, starts automatically wheneer the computer is started. Chapter 4. Configuring 283

298 Changing the IP address and hostname of the Network Manager installation If you change the IP address and hostname of the serer where any of the components of Network Manager or integrated products are installed, you must configure Network Manager and associated components and products. Changing the IP address and hostname for Network Manager If you want to change the IP address and hostname for the serer where the Network Manager core components are installed, you must perform some configuration tasks. Complete the following steps to change the IP address and hostname on the Network Manager serer. 1. Change to the following directory: NCHOME/etc/. 2. Edit the configuration file: itnm.cfg. 3. Change the following parameter: ncp. Update this to the new hostname of the Network Manager serer; for example: ncp=myhost 4. Sae the itnm.cfg file. 5. Change to the following directory: NCHOME/etc/precision/. 6. Edit the file: SericeData.cfg. 7. Change the following line: SERVICE: ncp_config DOMAIN: NCOMS ADDRESS: Network_Manager_serer_IP_address PORT: port_number SERVERNAME: Network_Manager_serer_hostname DYNAMIC: NO Where: Network_Manager_serer_IP_address is the new IP address of the Network Manager serer. Network_Manager_serer_hostname is the new hostname of the Network Manager serer. 8. Sae the SericeData.cfg file. Changing the IP address and hostname on the Tioli Netcool/OMNIbus serer If you want to change the IP address and hostname on the Tioli Netcool/OMNIbus serer, you must perform some configuration tasks. Complete the following steps to change the IP address and hostname on the Tioli Netcool/OMNIbus serer: 1. Change to the following directory: NCHOME/etc/. 2. Edit the file: omni.dat. 3. Look for lines containing the Tioli Netcool/OMNIbus serer. These lines might be similar to the following lines: [NCOMS] { Primary: OMNIbus_serer_hostname 4100 } [NCO_PA] { Primary: OMNIbus_serer_hostname 4200 } 284 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

299 Where: OMNIbus_serer_hostname is the hostname of the Tioli Netcool/OMNIbus serer. Change the Tioli Netcool/OMNIbus serer hostname in each of these lines. 4. Run the NCHOME/bin/nco_igen utility to apply the changes. 5. Repeat the preious steps on each of the hosts that connect to the Tioli Netcool/OMNIbus serer; for example, make these changes on connected probes, gateways, and ObjectSerers. Updating Network Manager for a new Tioli Netcool/OMNIbus IP address and hostname If you update the IP address and hostname for the Tioli Netcool/OMNIbus serer, you must configure Network Manager to use the new IP address and hostname. Complete the following steps to update Network Manager to make it aware of the changes to the Tioli Netcool/OMNIbus serer hostname: 1. Update the Network Manager core components by editing the configuration file: NCHOME/etc/itnm.cfg. 2. Change the following parameter:nco. Update this to the new hostname of the Tioli Netcool/OMNIbus serer; for example:nco=omnihost. 3. Sae the itnm.cfg file. 4. Update the Network Manager GUI components by editing the file webgui_home_dir/etc/datasources, where webgui_home_dir is the installation directory for the Web GUI; for example, $NCHOME/omnibus_webgui. 5. Update the Network Manager web applications to configure them to use the changed Tioli Netcool/OMNIbus serer hostname: a. Edit the following file: NCHOME/omnibus_webgui/etc/datasources/ncwDataSourceDefinitions.xml b. Change the host and port alues in the following sections to match your updated configuration: <ncwprimaryserer> <ncwbackupserer> Note: Only change this section if a backup Tioli Netcool/OMNIbus ObjectSerer is configured. c. Sae the modified ncwdatasourcedefinitions.xml file. d. Restart the Tioli Integrated Portal serer to apply the changes. Updating the Tioli Integrated Portal for a new Tioli Netcool/OMNIbus IP address and hostname If the Tioli Integrated Portal serer was originally configured to use the Tioli Netcool/OMNIbus ObjectSerer as its primary user repository, and you update the IP address and hostname for the Tioli Netcool/OMNIbus serer, you must configure the Tioli Integrated Portal to use the new IP address and hostname. Complete the following steps to configure the Tioli Integrated Portal to use the new Tioli Netcool/OMNIbus serer hostname: 1. Edit the following file: Chapter 4. Configuring 285

300 TIPHOME/profiles/TIPProfile/config/cells/TIPCell/wim/config/ wimconfig.xml 2. Change the host1 and port1 properties to match your updated configuration in the following file: config:repositories adapterclassname= "com.ibm.tioli.tip.mm4ncos.objectsereradapter" 3. Sae the modified wimconfig.xml file. 4. Restart the Tioli Integrated Portal serer to apply the changes. Changing the IP address and hostname on the Tioli Integrated Portal serer If you want to change the IP address and hostname of the Tioli Integrated Portal, you must configure the Tioli Integrated Portal. Follow these steps to change the IP address and hostname on the Tioli Integrated Portal serer: 1. Change to the following directory: TIPHOME/profiles/TIPProfile/bin/. 2. Use the wsadmin command to change the Tioli Integrated Portal serer hostname and IP address: wsadmin.sh -user tipadmin -password password -c "\$AdminTask changehostname {-hostname new_hostname -nodename new_node}" -c "\$AdminConfig sae" This proides output similar to the following: WASX7209I: Connected to process "serer1" on node TIPNode using SOAP connector;the type of process is: UnManagedProcess 3. Restart the Tioli Integrated Portal serer. Updating Network Manager for changed hostname of the Tioli Integrated Portal serer If you change the hostname of the Tioli Integrated Portal serer, you must configure Network Manager to use the new hostname. To configure Network Manager to use the new hostname, complete the following steps: 1. Update the Network Manager core components by editing the configuration file: NCHOME/etc/itnm.cfg. 2. Change the following parameter: tip Update this to the new hostname of the Tioli Integrated Portal serer; for example: tip=tiphost 3. Sae the itnm.cfg file. 286 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

301 Changing the IP address and hostname on the Deployment Engine serer If you hae changed the IP address and hostname on serers where components of Network Manager are installed, you must reconfigure the IP address and hostname for the IBM Autonomic Deployment Engine (DE). The Deployment Engine is present on any host where Network Manager components (GUI or core) are installed. If you hae more than one host with Network Manager components installed, and you change the IP address or hostname of any of those serers, ensure you update the Deployment Engine settings on each host that changes. Follow these steps to change the IP address and hostname for IBM Autonomic Deployment Engine (DE): 1. Change to the following directory: $DE_HOME/bin/, where DE_HOME is as follows: /usr/ibm/common/acsi/ for a root installation. $HOME/.acsi_$LOGNAME/ for a non-root installation. 2. Use the de_chghostname command to change the DE serer hostname:./de_chghostname.sh -name DE_serer_hostname Where DE_serer_hostname is the new hostname of the DE serer. Changing the IP address for Tioli Common Reporting If you want to change the IP address and hostname on the Tioli Common Reporting serer, you must perform some configuration tasks. Follow these steps to change the IP address and hostname on the Tioli Common Reporting serer: 1. On the serer where Tioli Common Reporting is installed, Export the Tioli Common Reporting configuration using the following command: $TCR_HOME/cognos/bin/tcr_cogconfig -e cogstartup.xml.exported 2. Update the file cogstartup.xml.exported by changing all instances of the old hostname with new hostname. 3. Replace the original $TCR_HOME/cognos/configuration/cogstartup.xml file with the cogstartup.xml.exported file. 4. Update the file $TCR_HOME/cognos/configuration/cogconfig.prefs by changing all instances of old hostname with new hostname. 5. Update the connection string by first changing to the directory /opt/ibm/tioli/tip2components/tcrcomponent/bin/ and then issuing the following command:./trcmd.sh -user user -password password -datasource -add serletinentory -connectionname serletinentory -dbtype database_type -connectionstring connection_string -force Where: user is the database user name. password is the database user password database_type is the database type. connection_string is the connection string to use, including the new hostname. For example: Chapter 4. Configuring 287

302 ./trcmd.sh -user tipadmin -password passw0rd -datasource -add serletinentory -connectionname serletinentory -dbtype XML -connectionstring " %2f%2a + &CAMpassport= + CAMPassport() #" -force 6. Restart the Tioli Integrated Portal serer and the Tioli Common Reporting serer. Configuring Network Manager for a changed IP address of the DB2 NCIM serer If you change the IP address or hostname of the DB2 serer hosting the NCIM topology database, you must configure Network Manager to use the new details. 1. On the serer where the Network Manager are installed, edit the following file: NCHOME/etc/precision/DbLogins.DOMAIN.cfg 2. Change the hostname settings in this file and sae the file. 3. Edit the following file: NCHOME/etc/precision/MibDbLogins.cfg 4. Change the hostname settings in this file and sae the file. 5. On the serer where the Network Manager web applications are installed, edit the following file: NCHOME/precision/profiles/TIPProfile/etc/tnm/tnm.properties 6. Change the hostname settings in this file and sae the file. 7. Edit the following file: Setting enironment ariables NCHOME/precision/profiles/TIPProfile/etc/tnm/ncpolldata.properties 8. Change the hostname settings in this file and sae the file. Before starting any components or working with any configuration files, set the Network Manager enironment ariables by running the enironment script. The enironment script sets the following required enironment ariables. Other enironment ariables are set automatically when necessary by Network Manager components. NCHOME The Netcool home location that defaults to netcool directory under the installation directory: UNIX /opt/ibm/tioli/netcool ITNMHOME and PRECISION_HOME The Network Manager home location that defaults to NCHOME/precision directory under the installation directory: UNIX /opt/ibm/tioli/netcool/precision Note: The script also sets PRECISION_HOME. By default, PRECISION_HOME is set to the same location as ITNMHOME, but is used by other parts of the product. TIPHOME The Tioli Integrated Portal home location that defaults to the tip directory under the installation directory: UNIX /opt/ibm/tioli/tip2 288 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

303 To set the enironment ariables, run the appropriate script for your operating system. UNIX Run the Installation directory/netcool/en.sh script. Default directory structure After you hae set the enironment ariables, start Network Manager and make sure it is running correctly. Use this information to understand the Network Manager directory structure. Top leel directory structure Within the directory that Network Manager is installed into, the following subdirectories are created: netcool, tip2, and tip2components. The netcool directory contains Network Manager configuration files. The tip2 directory contains WebSphere Application Serer and Tioli Integrated Portal customizations. The tip2 directory is the default directory suggested by the installer for the Tioli Integrated Portal and can be set independently to the Network Manager installation directory. If you are installing Network Manager into an existing installation of the Tioli Integrated Portal, the Tioli Integrated Portal files are installed into the existing Tioli Integrated Portal directory. The tip2components directory contains Enterprise Storage Serer (ESS) serer, Business Intelligence and Reporting Tools (BIRT) extensions, and Tioli Common Reporting files. For information about the installation directories for Tioli Netcool/OMNIbus and Tioli Netcool/OMNIbus Web GUI, see the IBM Tioli Netcool/OMNIbus Installation and Deployment Guide. Directories used by the installer The installer installs files in NCHOME, TIPHOME, and in other directories, depending on the operating system being installed on and the user performing the installation. The following table lists the extra directories used by the installer. Table 48. Directories used by the installer Installation Directories used for installation files UNIX UNIX operating systems, root user UNIX UNIX operating systems, non-root user /usr/ibm/common/acsi /ar/ibm/common/acsi ~/.acsi_$hostname ~/tioli ~/.cit (that is, in the user's home directory) C:\Program Files (x86)\ibm\common\acsi C:\Program Files\IBM\Common\acsi Chapter 4. Configuring 289

304 Contents of the netcool directory The following table describes the contents of the netcool directory. All paths are shown relatie to NCHOME. In this table, arch denotes an operating system directory. The name of this directory aries according to the operating system on which the software is installed: Linux linux2x86 Windows win32 If you hae installed other IBM Tioli products, such as IBM Tioli Business Serice Manager, on the same serer as Network Manager, there might be extra directories and files present. See the documentation for any other products you hae installed for more information on their directories and files. Table 49. Directories in NCHOME Directory bin etc etc/precision ini install license locales log log/install log/precision omnibus omnibus_webgui PD/precision platform/arch precision probes _uninst ar ar/install ar/precision Description Contains wrapper scripts that set the enironment and execute/run the binary files for product or components supplied with Network Manager. Contains configuration files for products or components supplied with Network Manager. Configuration files for all the Network Manager components. Only on Windows operating systems. Contains files specific to IBM Tioli Netcool/OMNIbus. Contains files used by the installation process. You should not need to alter the contents of this directory. Contains the text of the product license agreement in arious languages. Only on Windows operating systems. Contains lookup files for internationalization of arious components. Contains log files. Contains log files for the installation. Contains log files created by Network Manager processes. If present, contains IBM Tioli Netcool/OMNIbus files. If present, contains Tioli Netcool/OMNIbus Web GUI files. Contains FFDC scripts. Contains the Jaa Deelopment Kit (JDK) and Jaa Runtime Enironment (JRE) used by the Tioli Integrated Portal. Contains files for Network Manager. See later in this topic. Contains files for the Probe for IBM Tioli Netcool/OMNIbus, the nco_p_ncpmonitor process. Contains files for uninstallation. Contains persistent application data. Contains database files for the installation process. Used by the ncp_store process to hold cached information that can be used to restore the databases should a process terminate unexpectedly. 290 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

305 Contents of the precision directory The following table describes the contents of the NCHOME/precision directory. All paths are shown relatie to NCHOME/precision. In this table, arch denotes an operating system directory. The name of this directory aries according to the operating system on which the software is installed: Linux linux2x86 Windows win32 Note: NCHOME/precision is the path set by default for PRECISION_HOME and ITNMHOME. Table 50. Directories in NCHOME/precision Directory adapters/ncp_dla adapters/ itnm_systemsdirector LiC aoc bin collectors/ perlcollectors contrib cshrc disco embeddeddb eentgateway integration install jaa_api locales mibs PD perl platform/arch Description Contains files for the library adapter used for integration with products such as IBM Tioli Application Dependency Discoery Manager. Contains files for integration with IBM Systems Director. Contains the Actie Object Class (AOC) files used by the dynamic class management and distribution system, CLASS. Contains wrapper scripts for all executable files. The executable files are held at the following location:platform/arch/bin Contains files for Element Management System integrations. Contains unsupported utilities for managing Network Manager. Also used by the Netcool for Asset Management solution to contain example SQL*Plus reports. Only on UNIX operating systems. Used for setting up the enironment for your C shell. Contains files used by DISCO. Contains the agent definition files, discoery agents, finder, helper files, and the stitchers. Contains files for dncim. Contains stitchers for eent gateway and RCA. Contains files for component GUI integration. Contains files used by the installation process. Contains the JAVA API for deeloping Jaa applications that integrate with Network Manager components. Only on Windows operating systems. Contains lookup files for internationalization of arious components. Contains Management Information Base (MIB) files. Any core files generated by Network Manager are written into subdirectories of the PD directory. The core files can be used to help diagnose the cause of a problem. Contains perl files used in Network Manager. Contains subdirectories particular to the operating system on which you installed Network Manager. Chapter 4. Configuring 291

306 Table 50. Directories in NCHOME/precision (continued) Directory platform/arch/bin Description Contains executable files for the Network Manager components. The files are appended to your PATH enironment. Wrapper scripts for all of these executable files are held in the following location: NCHOME/precision/bin. platform/arch/jre platform/arch/lib platform/jaa/lib Contains the JAVA Run-Time Enironment used by Network Manager. Contains the object libraries used by all Network Manager components. The Monitor Configuration GUI installation. The User Configuration Tool installation. products profile profiles scripts system systemapps Contains GUI files for integrated products. Only on UNIX operating systems. Used for setting up the enironment for your Bash shell. Contains GUI-related files. Note: All Network Manager-specific files preiously located in TIPHOME/profiles are now located in ITNMHOME/profiles. Contains scripts supplied with the Network Manager products. It is adisable to keep any user-defined scripts in this directory so that they can easily be managed. Contains files for product operation. Contains files for Web applications. Related reference: Installation directory requirements on page 37 The directory where you install Network Manager must fulfill certain requirements. Configuring Juniper PE Deices One of the deice polls enabled by default is the Juniper Remote Ping poll. To ensure that this poll is able to retriee data, you must configure each Juniper PE deice to proide access to certain tables within the deice. Remote ping poll operations on Juniper deices require access to the pingctltable and jnxpingctltable tables in the Juniper PE deices. This is achieed using the SNMP View-Based Access Control Model (VACM) for iew PrecisionIP. Make sure you set up each Juniper PE deice to proide access to these tables for iew PrecisionIP before enabling the Juniper Remote Ping poll policy. The following example shows how a Juniper PE deice can be configured to proide access for iew PrecisionIP to the tables required for remote ping polling. Setting Up Access using VACM To proide access to the pingctltable and jnxpingctltable tables for iew PrecisionIP on a Juniper PE deice, do the following: 1. Use the telnet command to log into the PE deice. 2. Enter configure to launch the editing command line. 292 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

307 3. Type edit snmp and press Enter. 4. Type edit iew PrecisionIP and press Enter. 5. Type set oid include and press Enter. 6. Type set oid include and press Enter. 7. Type up and press Enter. 8. Type edit community watermelon and press Enter, where watermelon is the new write community string. 9. Type set iew PrecisionIP and press Enter. 10. Type set authorization read-write and press Enter. 11. Type commit and press Enter. 12. Type exit and press Enter. New entries are created for iew PrecisionIP in the acmviewtreefamilytable MIB table on the PE deice. To iew the summary of the inserted section, you can type show configuration snmp and press Enter. The following screen is displayed: iew PrecisionIP { oid include; oid include; } community watermelon { iew PrecisionIP; authorization read-write; } The settings aboe proide access to the tables required for remote ping poll operations using the community string watermelon. Proiding support for legacy deices in a FIPS installation If you hae installed a FIPS installation, you can still install non-fips compliant algorithms such as DES and MD5 to enable you to access legacy equipment on your network. 1. Go to the directory where you extracted the Network Manager installation package. 2. Change to the following subdirectory of the extracted installation package: COI/PackageSteps/Non-FIPS_back_end/FILES 3. Depending on your operating system, erify that the following file is present: UNIX Non-FIPS_back_end-arch-.r.f.m.tar.gz where:.r.f.m is the ersion number. arch is the name of the operating system architecture on which the product is installed, for example, solaris2. 4. Depending on your operating system, perform the following step: UNIX On UNIX systems, run the following command: tar -xzf Non-FIPS_back_end-arch-.r.f.m.tar.gz -C $NCHOME *libncp* As a result, you should hae the two shared libraries in the right location, for example: UNIX On UNIX systems: $NCHOME/precision/platform/solaris2/lib/libNcpSnmpPriDES.so $NCHOME/precision/platform/solaris2/lib/libNcpSnmpAuthMD5.so Chapter 4. Configuring 293

308 These libraries allow the Network Manager Polling engine, ncp_poller, to use the DES and MD5 encryption algorithms. 5. Edit the following configuration file: ITNMHOME/profiles/TIPProfile/etc/tnm/ tnm.properties 6. Change the following property to false: tnm.fips.mode=false This allows configuration of the DES and MD5 encryption algorithms for SNMP3 using the Discoery Configuration GUI. Related tasks: Extracting the installation file on page 48 If you hae downloaded the installation file, you must extract the installation package before installing the product. Creating and configuring extra network domains If your deployment requires additional network domains, you must configure process control for the domains and register the domains with the NCIM topology database. You can also migrate the configuration and network polls from an existing domain to the new domains. You must use one instance of ncp_ctrl to run and manage each domain. The ncp_ctrl process must be running on a domain, otherwise that domain cannot be configured from the GUI. You can run the domain_create.pl script to copy configuration data from an existing domain. The script does not migrate the topology from the original domain.for guidelines on the number of network domains required for a gien deployment, see the IBM Tioli Network Manager IP Edition Product Oeriew. To set up a Network Manager domain: 1. Back up the NCHOME\etc\precision\CtrlSerices.cfg file for the domain you set up during installation. 2. Make a domain-specific CtrlSerices.cfg file: a. Make a copy of the CtrlSerices.cfg file. b. Rename the file to CtrlSerices.domain_name.cfg where domain_name is the required domain. For example, CtrlSerices.MASTER.cfg. Restriction: Only alphanumeric characters and the underscore (_) character may be used for domain names. Any other characters, for example the hyphen (-) are forbidden. 3. Optional: Edit the copied and appended file. 4. Optional: Configure discoery for the domain by making changes to the discoery configuration files: a. Back up the configuration file that you want to change. b. Rename the file by appending the name of the domain. For example DiscoPingFinderSeeds.MASTER.cfg c. Make the required changes and sae the file. 5. Make a domain-specific ConfigItnm.cfg file: a. Make a copy of the ConfigItnm.cfg file. b. Rename the file to ConfigItnm.domain_name.cfg where domain_name is the required domain. For example, ConfigItnm.MASTER.cfg. c. Edit the file and add the ObjectSerer connection details. 294 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

309 6. Register the new domain with the NCIM topology database, and migrate the configuration and network polls from an existing domain: a. Back up the DbLogins.cfg file, and create a domain-specific ersion of the file. For example, DbLogins.MASTER.cfg b. Edit the domain-specific DbLogins.cfg file to proide the database connection details. Restriction: For the SolidDB (dncim) database, the port number must be unique. c. Run the domain_create.pl script, as shown in the following example: UNIX $NCHOME/precision/bin/ncp_perl NCHOME/precision/scripts/perl/scripts/domain_create.pl -domain newdomain -password password -help Where: newdomain Is the name of the domain you hae created, for example MASTER. password Is the password for the domain. - help Is an optional argument that proides further options. 7. Start the Network Manager processes on the domain using a command line similar to the following: itnm_start ncp -domain MASTER 8. Repeat the steps to set up all the required domains. After ncp_ctrl to is started on the domain, you can configure the domain. For example, you can configure the discoery by using the Network Discoery GUI or the configuration files, or configure network polling. You select the required domain before you start configuring the discoery or poll. Because network discoery is a resource-intensie process, discoeries are usually run one domain at a time. If you want to run discoeries for more than one domain at the same time, ensure that you hae enough resources aailable. For example, ensure that enough database connections are configured, and that network deices are not oerloaded with traffic. Check the memory usage of Network Manager processes to ensure that enough memory is aailable on the serer to run the discoeries efficiently. For more information about configuring discoery, see the IBM Tioli Network Manager IP Edition Discoery Guide. For more information about configuring network polling, see the IBM Tioli Network Manager IP Edition Eent Management Guide. Related concepts: Network domains on page 20 Before installing, you need to consider whether to partition your network into domains, or hae a single domain for the entire network. A network domain is a collection of network entities to be discoered and managed. Chapter 4. Configuring 295

310 Configuring OQL Serice Proider authentication Queries against Network Manager component databases can be run from the command line using the OQL Serice Proider process, ncp_oql. You can configure ncp_oql to authenticate against the NCIM database or against the Tioli Netcool/OMNIbus ObjectSerer. Alternatiely you can configure ncp_oql to allow queries to run without authentication. The OQL Serice Proider authentication engine, ncp_auth is no longer used in Network Manager ersions 3.9 and later. By default, there is no authentication for ncp_oql queries from the command line. You can configure the OQL Serice Proider to authenticate against the NCIM database or against the ObjectSerer, as follows: Authentication against the NCIM database: this forces the OQL Serice Proider to authenticate using the username and password of the NCIM database, as specified at installation time and configured in the DbLogins.cfg configuration file. Authentication against the ObjectSerer: this forces the OQL Serice Proider to authenticate using the administrator account name and password of Tioli Netcool/OMNIbus, as specified at installation time. OQL Serice Proider authentication is controlled by the alue of the m_oqlauthenticationmode within the config.settings table. The field takes the following alues: 0: No authentication. Username and password are not required, and if specified in the command line, are ignored. 1: Authentication against NCIM database. 2: Authentication against the Tioli Netcool/OMNIbus ObjectSerer. To set up OQL Serice Proider authentication: 1. Edit the ncp_config configuration file, $NCHOME/etc/precision/ ConfigSchema.cfg. 2. Configure one of the following inserts to the config.settings table: Configure authentication against the NCIM database. insert into config.settings ( m_oqlauthenticationmode, ) alues ( 1, ); Configure authentication against the ObjectSerer. insert into config.settings ( m_oqlauthenticationmode, ) alues ( 2, ); 296 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

311 Configuring the SNMP Helper The SNMP Helper is used by discoery and polling to issue SNMP requests to network deices. You can configure how the SNMP Helper issues SNMP requests and how it processes the results of SNMP requests. For information on where the SNMP Helper is used in discoery and polling, see the following guides: For discoery, see the IBM Tioli Network Manager IP Edition Discoery Guide. For polling, see the IBM Tioli Network Manager IP Edition Eent Management Guide. Configuring SNMP Helper throttling You can actiate throttling in the SNMP Helper. Actiating throttling increases the delay between Network Manager SNMP requests to a network deice. This decreases the load on the network deice. By default, throttling is switched off in the SNMP Helper. About SNMP Helper throttling Throttling the SNMP Helper establishes a delay between SNMP requests sent by the SNMP Helper using a formula that uses the GeneralSlowdown, GetNextBoundary, and GetNextSlowdown parameters. Here is how the SNMP Helper sends requests without throttling (default) and with throttling: When throttling is inactiate, then SNMP GetNext operations work as follows: the SNMP Helper sends the first SNMP Get request and once Network Manager obtains a response then the SNMP Helper immediately sends the GetNext request. When throttling is actiated, a delay is introduced between GetNext requests. The delay can be a shorter, generally defined delay or a longer delay. The system keeps track of the number of GetNext requests being sent to a network deice and once that number exceeds a certain alue, then the longer delay is applied; otherwise the shorter delay is applied. The system uses the GeneralSlowdown, GetNextBoundary, and GetNextSlowdown parameters defined in the snmpstack.accessparameters database table to determine which delay to apply. For more information on the snmpstack.accessparameters database table, see the IBM Tioli Network Manager IP Edition Discoery Guide. Actiating SNMP Helper throttling You can actiate SNMP Helper throttling. To actiate SNMP Helper throttling, perform the following steps: 1. Edit the following configuration file: NCHOME/etc/precision/ NcPollerSchema.cfg. Note: You can make the NcPollerSchema.cfg file domain specific by copying it to NCHOME/etc/precision/NcPollerSchema.DOMAIN_NAME.cfg, where DOMAIN_NAME is the name of the domain. 2. Add the following line at the end of the file: update config.properties set EnableThrottling = 1; 3. Sae the file NCHOME/etc/precision/NcPollerSchema.cfg. 4. Actiate the changes by performing one or both of the following: Chapter 4. Configuring 297

312 Start or schedule a new full discoery. Discoery will now make use of throttling. Restart the Polling engine, ncp_poller, with the -readsnmpconfig command-line option specified. Configuring GetBulk support for SNMP 2 and 3 You can configure the SNMP Helper to use the GetBulk operation when SNMP 2 or 3 is used. Use of the GetBulk operation improes discoery speed and polling efficiency. By default, the SNMP helper does not use GetBulk. About GetBulk The SNMP 2 and SNMP 3 GetBulk command enables more efficient data transfer. When the SNMP Helper is enabled to use GetBulk, this decreases the time taken for the discoery data collection phases. Use of GetBulk also increases polling efficiency. Configuring the SNMP Helper to use GetBulk reduces the resource footprint of Network Manager in the following ways: It reduces the impact on management network because fewer SNMP packets are exchanged. It reduces the impact on managed deices because fewer SNMP packets are processed. It reduces the CPU time required by the Network Manager processes such as the Discoery engine, ncp_disco, and the Polling engine, ncp_poller, due to reduced oerheads. Use of GetBulk decreases the time taken for the discoery data collection phases as a large percentage of the time required for data collection is taken up waiting for packets to traerse the network. This significantly reduces the time taken to collect data for large tables, such as interface and routing tables. Configuring Network Manager to use GetBulk You can configure the SNMP Helper to use GetBulk. You can also exclude specific deices from GetBulk support. If you configure the SNMP Helper to use GetBulk, then this will apply to all pollers in the current domain. The SNMP Helper will also use GetBulk for all deices in the domain accessed using SNMP 2 or SNMP 3, unless you exclude specific deices as described in the following steps. Note: When GetBulk is enabled, then for each GetBulk-capable deice, a GetBulk request is always sent instead of a GetNext request. To configure the SNMP Helper to use GetBulk, perform the following steps. 1. Edit the following configuration file: NCHOME/etc/precision/ NcPollerSchema.cfg. Note: You can make the NcPollerSchema.cfg file domain specific by copying it to NCHOME/etc/precision/NcPollerSchema.DOMAIN_NAME.cfg, where DOMAIN_NAME is the name of the domain. 2. Find the insert into the config.properties database and set the alue for the UseGetBulk property to Sae the file NCHOME/etc/precision/NcPollerSchema.cfg. 298 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

313 4. Optional: If you hae network deices that do not support GetBulk, then you can exclude these network deices on a deice-by-deice basis by performing the following steps: a. Edit the following configuration file: NCHOME/etc/precision/ SnmpStackSecurityInfo.cfg. Note: You can make the SnmpStackSecurityInfo.cfg file domain-specific by copying it to NCHOME/etc/precision/ SnmpStackSecurityInfo.DOMAIN_NAME.cfg, where DOMAIN_NAME is the name of the domain. b. For each deice that you want to exclude from GetBulk support, add an insert into the SnmpStackSecurityInfo.cfg configuration file, similar to the following example. The following example insert excludes the deice from GetBulk support. insert into snmpstack.accessparameters ( m_netaddress, m_usegetbulk ) alues ( , 0 ); c. Once you hae added inserts for each of the deices to exclude, sae the file NCHOME/etc/precision/ SnmpStackSecurityInfo.cfg. 5. Actiate the changes by performing one or both of the following: Start or schedule a new full discoery. Discoery will now make use of GetBulk. Restart the Polling engine, ncp_poller, with the -readsnmpconfig command-line option specified. Configuring maximum number of repetitions for GetBulk requests The GetBulk command is used to retriee all the rows of a table from a network resource, for example, to retriee all the rows in a routing table from a router. The max-repetitions parameter indicates how many rows of the table are to be retrieed in a single GetBulk operation. You can adjust the GetBulk configuration settings to minimize the number of packets exchanged as part of the GetBulk operation. The SNMP Helper determines the alue of the maximum number of repetitions for GetBulk requests (the max-repetitions parameter) based on the following calculation: max-repetitions = DefaultGetBulkMaxReps / #arbinds Where: The DefaultGetBulkMaxReps property is defined in the $NCHOME/etc/precision/ NcPollerSchema.cfg file. The default alue is 20. This property defines the number assigned to the max-repetitions field in GetBulk requests issued by Network Manager processes. The alue 20 is used when the GetBulk request contains a single arbind. If multiple arbinds are included, then the alue is adjusted accordingly (diided by the number of arbinds), so that responses always contain a similar number of arbinds. #arbinds is the number of ariable bindings being requested. In the SNMP Helper, this alue is usually 1. Howeer, the alue can ary depending on where the SNMP Helper is being deployed and on the following factors: In the Discoery engine, ncp_disco, the #arbinds alue can ary depending on the code in the discoery agent. Chapter 4. Configuring 299

314 In the Polling engine, ncp_poller, the #arbinds alue can ary depending on which MIB objects are included in the poll definition. 1. Edit the following configuration file: $NCHOME/etc/precision/ NcPollerSchema.cfg. Note: You can make the NcPollerSchema.cfg file domain specific by copying it to $NCHOME/etc/precision/NcPollerSchema.DOMAIN_NAME.cfg, where DOMAIN_NAME is the name of the domain. 2. Find the line that defines the alue of the DefaultGetBulkMaxReps property. 3. Change the alue assignment for the DefaultGetBulkMaxReps property. 4. Sae the file $NCHOME/etc/precision/NcPollerSchema.cfg. 5. Restart the Polling engine, ncp_poller to actiate the configuration changes. Configuring SSO between Charting and Tioli Monitoring The instructions below describe how to configure IBM Tioli Monitoring and Charting for single sign on (SSO) using the ITMWebSerice. At the bottom are also instructions for how to configure Tioli Integrated Portal to communicate with a remote Tioli Monitoring Web Serice, which only works in an SSO enironment. Install Tioli Monitoring You must configure Tioli Monitoring Tioli Enterprise Portal Serer to use LDAP and SSO during the configuration step. Refer to Tioli Monitoring documentation, but essentially you need to do the following: During the Tioli Enterprise Portal Serer configuration, check the LDAP and SSO check boxes. Enter the information to connect to LDAP. When the SSO configuration is displayed, enter TIPRealm for the realm name and your network domain for your domain name (for example, raleigh.ibm.com). Export the LTPA keys to disk. For more information, see: com.ibm.websphere.express.doc/info/exp/ae/tsec_altpaexp.html. Take a note of the password. Copy the \ibm\itm\cnps\sqllib\kfwtipewas.properties file to the \ibm\itm\cnps directory and run reconfigure for the Tioli Enterprise Portal Serer. Once the reconfigure is complete, the web serice feature is actiated. Install and configure Tioli Integrated Portal to include the charting component. To configure SSO for the charting component and Tioli Monitoring: 1. Configure Lightweight Directory Access Protocol (LDAP) security in Tioli Integrated Portal: a. Add and configure an LDAP repository. b. Configure Tioli Integrated Portal to allow you to manage LDAP users in the portal. 2. Configure Tioli Integrated Portal for SSO. Make sure both Tioli Monitoring and the embedded application serer for Tioli Integrated Portal use the same LTPA keys (import the LTPA keys you exported from Tioli Monitoring), Realm names, and exchange SSL certificates. For more information, see: com.ibm.websphere.express.doc/info/exp/ae/tsec_altpaimp.html 3. On the Tioli Integrated Portal Serer, change to tip_home_dir/profiles/ TIPProfile/bin and run the following command to configure Tioli Integrated Portal to use SSO when communication with Tioli Monitoring: 300 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

315 Linux UNIX tipcli.sh ITMLogin -hostname <TEPS_hostname> -port Stop and restart the Tioli Integrated Portal Serer: a. In the TIPHOME/profiles/TIPProfile/bin directory, depending on your operating system, enter one of the following commands: UNIX Linux stopserer.sh serer1 Note: On UNIX and Linux systems, you are prompted to proide an administrator username and password. b. In the TIPHOME/profiles/TIPProfile/bin directory, depending on your operating system, enter one of the following commands: UNIX Linux startserer.sh serer1 5. Create the users in Tioli Integrated Portal and assign them to a role that has priileges to iew the charts from Tioli Monitoring, such as chartadministrator. 6. Associate the same users that you created with a Tioli Enterprise Portal user. a. Log into the Tioli Enterprise Portal and associate that same user from LDAP with a Tioli Enterprise Portal user. b. In Tioli Enterprise Portal, select Edit --> Manage Users. c. Click the button to create a new user and enterr the user ID and user name. To be consistent, you can use the same user ID as in Tioli Integrated Portal. d. Enter the distinguised name. You can get this from the Tioli Integrated Portal Manage Users panel. You may be able to find it using the Find button in the Tioli Enterprise Portal. If you do not locate it with the Find button, copy and paste it from the Tioli Integrated Portal Manage Users panel. It should look like this: uid=userid,o=ibm,c=us e. Gie the user Workspace Administration Mode permission. Note: When you log into the Tioli Integrated Portal, you cannot use sysadmin which is the default Tioli Monitoring user or tipadmin which is the default Tioli Integrated Portal user because neither of these users are in stored in the LDAP. 7. When you hae finished, follow these steps to test the configuration: a. Log into he Tioli Integrated Portal as one of the users that you created with chart access. b. Create a new page using Settings > Page Management > New Page. c. Select the Charting portlet and click OK. d. Gie the page a name and sae it. e. Naigate to the charting portlet and select Tioli Charts. f. In the table toolbar, click New to create a new connection and proide the necessary information to connect to the remote Tioli Monitoring web serice and click OK. For example: Name: ITM Protocol: http. This can be later changed to https if required but for testing purposes http is sufficient. Hostname: TEPS_serer_name.raleigh.ibm.com. This is the hostname of the Tioli Enterprise Portal serer, for example, ti-isc09.ibm.com. Port: If you use https, the default port is Chapter 4. Configuring 301

316 Serice name: TIPWebSericeHttpRouter. g. Select one of these groups. It will populate the table with the charts and tables from that Tioli Monitoring workspace. h. Select a chart and click Finish. The chart is imported, which can take some time initially. When processing is complete, the chart is rendered in the portlet. If you do not see the chart, reiew any error messages and make sure you followed these steps correctly. Related tasks: Configuring single sign-on on page 195 Use these instructions to establish single sign-on support and configure a federated repository. The IBM Support Assistant (ISA) The IBM Support Assistant is a tool which helps you to search and find product support and education information. If a Problem Management Record (PMR) needs to be opened, IBM Support Assistant can sae you time by automatically gathering support information. The IBM Support Assistant proides the following serices: Improed access to IBM support information, IBM newsgroups, and other resources through a federated search interface (one search across multiple resources) Easy access to IBM educational materials and product education roadmaps Easy access to IBM product home pages, product support pages, and product forums or newsgroups through conenient links Improed PMR time to resolution by collecting key system information and sending the data to IBM through electronic creation of a PMR A Network Manager plug-in is aailable for the IBM Support Assistant. The plug-in is needed by the IBM Support Assistant so that it can diagnose Network Manager problems. For more information about the IBM Support Assistant, refer to the following IBM Web site: Installing the IBM Support Assistant Lite collector The IBM Support Assistant (ISA) Lite collector for Network Manager proides automated data collection on systems where Network Manager is installed. It can collect the information about logs, rules files, configuration data, and so on. To install the ISA Lite collector, perform the following steps: 1. Install Network Manager. 2. Open the following technote: dociew.wss?uid=swg Follow the steps in the technote to set up and use the ISA Lite collector for Network Manager. 302 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

317 Appendix. Network Manager glossary Use this information to understand terminology releant to the Network Manager product. The following list proides explanations for Network Manager terminology. AOC files Files used by the Actie Object Class manager, ncp_class to classify network deices following a discoery. Deice classification is defined in AOC files by using a set of filters on the object ID and other deice MIB parameters. actie object class (AOC) An element in the predefined hierarchical topology of network deices used by the Actie Object Class manager, ncp_class, to classify discoered deices following a discoery. agent See, discoery agent. bookmark See, network iew bookmark. class hierarchy Predefined hierarchical topology of network deices used by the Actie Object Class manager, ncp_class, to classify discoered deices following a discoery. configuration files Each Network Manager process has one or more configuration files used to control process behaiour by setting alues in the process databases. Configuration files can also be made domain-specific. discoery agent Piece of code that runs during a discoery and retriees detailed information from discoered deices. Discoery Configuration GUI GUI used to configure discoery parameters. Discoery engine (ncp_disco) Network Manager process that performs network discoery. discoery phase A network discoery is diided into four phases: Interrogating deices, Resoling addresses, Downloading connections, and Correlating connectiity. discoery seed One or more deices from which the discoery starts. discoery scope The boundaries of a discoery, expressed as one or more subnets and netmasks. Discoery Status GUI GUI used to launch and monitor a running discoery. discoery stitcher Piece of code used during the discoery process. There are arious Copyright IBM Corp. 2006,

318 discoery stitchers, and they can be grouped into two types: data collection stitchers, which transfer data between databases during the data collection phases of a discoery, and data processing stitchers, which build the network topology during the data processing phase. dncim database The dncim is a relational database embedded into the Discoery engine, ncp_disco, and it stores the containment model that is deried from the fulltopology database (and created by stitchers). This is the ersion of the topology that is sent to the Topology manager, ncp_model. The dncim database performs the same function as the scratchtopology database did in preious ersions of Network Manager. domain See, network domain. entity A topology database concept. All deices and deice components discoered by Network Manager are entities. Also deice collections such as VPNs and VLANs, as well as pieces of topology that form a complex connection, are entities. eent enrichment The process of adding topology information to the eent. Eent Gateway (ncp_g_eent) Network Manager process that performs eent enrichment. Eent Gateway stitcher Stitchers that perform topology lookup as part of the eent enrichment process. failoer In your Network Manager enironment, a failoer architecture can be used to configure your system for high aailability, minimizing the impact of computer or network failure. Failoer plug-in Receies Network Manager health check eents from the Eent Gateway and passes these eents to the Virtual Domain process, which decides whether or not to initiate failoer based on the eent. Fault Finding View Composite GUI iew consisting of an Actie Eent List (AEL) portlet aboe and a Network Hop View portlet below. Use the Fault Finding View to monitor network eents. full discoery A discoery run with a large scope, intended to discoer all of the network deices that you want to manage. Full discoeries are usually just called discoeries, unless they are being contrasted with partial discoeries. See also, partial discoery. message broker Component that manages communication between Network Manager processes. The message broker used bynetwork Manager is called Really Small Message Broker. To ensure correct operation of Network Manager, Really Small Message Broker must be running at all times. NCIM database Relational database that stores topology data, as well as administratie data such as data associated with poll policies and definitions, and performance data from deices. 304 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

319 ncp_disco See, Discoery engine. ncp_g_eent See, Eent Gateway. ncp_model See, Topology manager. ncp_poller See, Polling engine. network domain A collection of network entities to be discoered and managed. A single Network Manager installation can manage multiple network domains. Network Health View Composite GUI iew consisting of a Network Views portlet aboe and an Actie Eent List (AEL) portlet below. Use the Network Health View to display eents on network deices. Network Hop View Network isualization GUI. Use the Network Hop View to search the network for a specific deice and display a specified network deice. You can also use the Network Hop View as a starting point for network troubleshooting. Formerly known as the Hop View. Network Polling GUI Administrator GUI. Enables definition of poll policies and poll definitions. Network Views Network isualization GUI that shows hierarchically organized iews of a discoered network. Use the Network Views to iew the results of a discoery and to troubleshoot network problems. network iew bookmark Network iew bookmarks group together just those network iews that you or your team need to monitor. Create new bookmarks or change existing bookmarks to help network operators isualize just those deices that they need to monitor. OQL databases Network Manager processes store configuration, management and operational information in OQL databases. OQL language Version of the Structured Query Language (SQL) that has been designed for use in Network Manager. Network Manager processes create and interact with their databases using OQL. partial discoery A subsequent rediscoery of a section of the preiously discoered network. The section of the network is usually defined using a discoery scope consisting of either an address range, a single deice, or a group of deices. A partial discoery relies on the results of the last full discoery, and can only be run if the Discoery engine, ncp_disco, has not been stopped since the last full discoery. See also, full discoery. Path Views Network isualization GUI that displays deices and links that make up a Appendix. Network Manager glossary 305

320 network path between two selected deices. Create new path iews or change existing path iews to help network operators isualize network paths. performance data Performance data can be gathered using performance reports. These reports allow you to iew any historical performance data that has been collected by the monitoring system for diagnostic purposes. Polling engine (ncp_poller) Network Manager process that polls target deices and interfaces. The Polling engine also collects performance data from polled deices. poll definition Defines how to poll a network deice or interface and further filter the target deices or interfaces. poll policy Defines which deices to poll. Also defines other attributes of a poll such as poll frequency. Probe for Tioli Netcool/OMNIbus (nco_p_ncpmonitor) Acquires and processes the eents that are generated by Network Manager polls and processes, and forwards these eents to the ObjectSerer. RCA plug-in Based on data in the eent and based on the discoered topology, attempts to identify eents that are caused by or cause other eents using rules coded in RCA stitchers. RCA stitcher Stitchers that process a trigger eent as it passes through the RCA plug-in. root-cause analysis (RCA) The process of determining the root cause of one or more deice alerts. SNMP MIB Browser GUI that retriees MIB ariable information from network deices to support diagnosis of network problems. SNMP MIB Grapher GUI that displays a real-time graph of MIB ariables for a deice and usse the graph for fault analysis and resolution of network problems. stitcher Code used in the following processes: discoery, eent enrichment, and root-cause analysis. See also, discoery stitcher, Eent Gateway stitcher, and RCA stitcher. Structure Browser GUI that enables you to inestigate the health of deice components in order to isolate faults within a network deice. Topology Manager (ncp_model) Stores the topology data following a discoery and sends the topology data to the NCIM topology database where it can be queried using SQL. WebTools Specialized data retrieal tools that retriee data from network deices and can be launched from the network isualization GUIs, Network Views and Network Hop View, or by specifying a URL in a web browser. 306 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

321 Notices This information applies to the PDF documentation set for IBM Tioli Network Manager IP Edition. This information was deeloped for products and serices offered in the U.S.A. IBM may not offer the products, serices, or features discussed in this document in other countries. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user's responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drie Armonk, NY U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd , Nihonbashi-Hakozakicho, Chuo-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such proisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are proided for conenience only and do not in any manner sere as an endorsement of those Web Copyright IBM Corp. 2006,

322 sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it beliees appropriate without incurring any obligation to you. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 958/NH04 IBM Centre, St Leonards 601 Pacific Hwy St Leonards, NSW, 2069 Australia IBM Corporation /H128B 76 Upper Ground London SE1 9PZ United Kingdom IBM Corporation JBF1/SOM1 294 Route 100 Somers, NY, United States of America Such information may be aailable, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material aailable for it are proided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurements may hae been estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly aailable sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the 308 IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

323 names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on arious operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of deeloping, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, or function of these programs. Trademarks The terms in Table 51 are trademarks of International Business Machines Corporation in the United States, other countries, or both: Table 51. IBM trademarks AIX Informix RDN BNT iseries soliddb ClearQuest Lotus System p Cognos Netcool System z DB2 NetView Tioli DB2 Uniersal Notes WebSphere Database deeloperworks OMEGAMON z/os DS8000 PowerPC z/vm Enterprise PowerVM zseries Storage Serer IBM PR/SM Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Notices 309

324 Linux is a registered trademark of Linus Toralds in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Priacy policy considerations IBM Software products, including software as a serice solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improe the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering's use of cookies is set forth below. This Software Offering may collect IP addresses, user names and passwords for the purpose of performing network discoery. Failure to enable the collection of this information would likely eliminate important functionality proided by this Software Offering. You as customer should seek your own legal adice about any laws applicable to such data collection, including any requirements for notice and consent. For more information about the use of arious technologies, including cookies, for these purposes, See IBM's Priacy Policy at and IBM's Online Priacy Statement at the section entitled "Cookies, Web Beacons and Other Technologies" and the "IBM Software Products and Software-as-a-Serice Priacy Statement" at IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

325 Index Numerics 3.8 isualization mode switching back to 236 A about DNCIM 39 accessibility ix actiating SNMP Helper throttling 297 AEL configuring default iew 236 configuring topology eent types 155 troubleshooting 236 alert status associated with a deice configuring display of 226 alert status settings 233 alerts.status table fields used for Network Manager 172 application serer FIPS enablement 198 architecture failoer 247 large deployment 17 simple deployment 15 audience B base charting 38 bidirectional 190 browsers supported for installer launchpad 36 supported for Web applications 34 BSM_Identity token 194 C charting SSO and ITM 300 class types assigning icons for 223 classes assigning icons for 222 cloning 143 Common Data Model (CDM) 179 compatibility 31 ConfigItnm.cfg file 270 ConfigOMNI options 43 configuring GetBulk for SNMP 2 and JRE for FIPS maximum number of repetitions for GetBulk requests 299 Network Manager to use GetBulk 298 probes 158 configuring (continued) SNMP Helper 297 SNMP Helper throttling 297 topology map appearance 225 topology map updates 225 configuring automation for SAEs 152 configuring existing DB2 217 configuring reports 239 configuring VMM 200 contextual launch 190 conentions, typeface xi copying existing installation 143 customization data importing 119 D data source changing, Web GUI 154 data sources NCIM database 155 network topology 155 database additional fields, Tioli Netcool/OMNIbus 156 database setup 44 DB2 on UNIX 44 databases topology data 32 DB2 configuring 216 configuring connection to existing instance 217 root and non-root 216 DB2 HADR configuring Network Manager to work with 274 deployment domain requirements 20 large, architecture 17 simple architecture 15 Deployment Engine managing 90 DES 293 deices highlighting manually added 235 Juniper PE 292 directory installation requirements 37 directory structure default 289 discoery bandwidth requirements 29 memory requirements 29 discoery data accessing from dncim 212 Discoery Library Adapter configuration 191, 192, 193 network edge data 189 running 184 Discoery Library Adapter (DLA) configuration 180 default installation location 179 prerequisites 179 Discoery Library book 184 disk space eents and interfaces 28 DLA fine-tuning data export 185 DLA properties for filtered iew 188 dncim accessing discoery data from 212 DNCIM 39 DNS prerequisites 36 domains additional 294 multiple per ObjectSerer 22 partition 20 single per ObjectSerer 21 iewing multiple 23 E education see Tioli technical training ix entity types assigning icons for 222 enironment ariables 288 enironment ariables, notation xi eent categories 159 eent fields 169 eents filtering unmanaged deices 238 health check 254 health check problem 255 health check resolution 255 network 160 status information 161 tagging unmanaged deices 239 unmanaged deices 238 existing DB2 setup 217 exporting discoery data 179 exporting GUI customization data 115 extra information associated with a deice configuring display of 226 F failoer architectures 244 configuring ConfigItnm.cfg file 270 configuring health check parameters 277 configuring Network Manager 270 configuring Network Manager to work with DB2 HADR 274 Copyright IBM Corp. 2006,

326 failoer (continued) configuring ObjectSerers 263, 264 configuring process dependencies 278 configuring Tioli Integrated Portal serers 261 failing back 257 failing oer 257 fixed port for TCP connections 272 health check eents 254 health check problem eents 255 health check resolution eents 255 Network Manager architecture 247 ObjectSerer 245 ObjectSerer pair connection 262, 266 oeriew 241 restrictions 261 serer allocation 251 TCP connection 272 Tioli Netcool/OMNIbus configuration files 247 tracking 279 irtual domains 247 Web GUI 251, 267 federated repositories VMM for ObjectSerer 200 field mappings Network Manager to alerts.status 172 filtered network iew for edge of network 187 filtered iews 155 FIPS installation 51 legacy deices. support 293 non-compliant algorithms 293 FIPS configuration 157 FIPS support 198 fix pack installation 96 G GetBulk about 298 configuring for SNMP 2 and configuring for use by SNMP Helper 298 GetBulk requests configuring maximum number of repetitions 299 glossary 303 H handling multibyte characters 47 health check eents 254 configuring parameters 277 health check problem eents 255 health check resolution eents 255 HTTP and HTTPS 196 I IBM Support Assistant 302 IBM Support Assistant Lite installation 302 IBM Systems Director adapter logging 209 connection properties 205 database configuration 206 download 203 install 203 optional adapter settings 208 properties file 204 running adapter 210 SSL certificate 204 troubleshooting 211 IBM Systems Director oeriew 202 IBM Tioli Application Dependency Discoery Manager access parameters 180 configuration NCIM database 193 properties file 180 GUIs Network Manager context menus 192 TADDM UI 191 Information Center 179 prerequisites 179 IBM Tioli Change and Configuration Management Database Information Center 179 integration with Network Manager 179 prerequisites 179 IBM Tioli Monitoring installation 201 IBM Tioli Netcool/OMNIbus Knowledge Library installing 159 icons assigning by class 219 assigning to class types 223 assigning to classes 222 assigning to entity types 222 changing, alert seerity 231 IdML 179 importing customization data 119 installation bandwidth, discoery process 29 basic, alues 52 browsers for installer launchpad 36 browsers for Web applications 34 configure auto start 215 console mode 72 core components installation requirements 26 custom, alues 56 database setup 44 DB2 database, UNIX 44 default and custom 50 deployment engine failure after upgrade 92 directory 37 disk space, eents and interfaces 28 distributed deployment 14 errors 91 failoer, serer allocation 251 failure after DE upgrade 92 installation (continued) file, uncompressing 48 FIPS fix pack 96 for single sign-on 195 GUI components 27 hardware, core components 26 hardware, topology database 27 harmless messages 91 IBM Support Assistant 302 IBM Support Assistant Lite 302 IBM Tioli Monitoring 201 launchpad 51 log files 91 logs 84 memory, discoery process 29 non-root user, additional configuration 214 operating system tools 36 operating systems 32 order of components 14 prerequisite check 48 processor requirements 25 requirements for installer 25 root user, additional configuration 214 root/non-root user, UNIX 213 silent mode 73 silent mode, parameters 75 software requirements, other products 30 supported topology databases 32 swap space 28 Tioli Integrated Portal 27 topology database installation requirements 27 topology database setup 44 troubleshooting console mode error 89 dependency error messages 89 disk space 89 installation errors 91 root/non-root users 89 uninstalling oeriew 93 UNIX user restrictions 37 upgrading 110 wizard 51 installation prerequisites DNS 36 installation requirements file handles 38 installing IBM Tioli Netcool/OMNIbus Knowledge Library 159 postinstallation tasks 81 preinstallation tasks 41 configuring OMNIbus 41 probes 158 Tioli Common Reporting 47 upgrading polling files 128 integrating with Netcool Configuration Manager 179 integration 31, 151 Netcool/OMNIbus 151 additional database fields IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

327 J JRE configuration FIPS Juniper PE deice configuration 292 K Knowledge Library 159 L launchpad supported browsers 36 legacy deices FIPS legacy V3.8 isualization mode switching back to 236 lines appearance of in topology maps 225 Linux disable SELinux 49 loading Discoery Library into TADDM 190 loading MIB information 237 log TIPProfile_create 86 log files 87 login configure for HTTP and HTTPS 196 M maintenance state associated with a deice configuring display of 226 manually added deices highlighting 235 manuals i maximum number of repetitions for GetBulk requests configuring 299 MD5 293 MIB information how to load new information 237 updating with ncp_mib 237 migrating 111, 138 copying same ersion 143 core configuration settings 122 DLA properties 127 eent enrichment and correlation 128 exporting GUI customization data 115 GUI configuration settings 132 reports, topology database customizations 117 migrating Cognos content store to DB2 240 multibyte characters handling in the NCIM database 47 N NCHOME 288 NCIM database handling multibyte characters 47 NCIM topology database oeriew of high aailability method for 242 nco_p_ncpmonitor probe for TBSM 194 ncp_mib loading 237 ncp_oql authentication configuring for OQL Serice Proider 296 configuring authentication 296 configuring authentication for OQL Serice Proider 296 Netcool Configuration Manager 179 network domains additional 294 network edge identification 186 network eents 160 Network Manager eent categories 159 Network Manager eent fields 169 Network Manager glossary 303 Network Manager to alerts.status mappings 172 network maps appearance of nodes and lines 225 network iews 229 nodes appearance of in topology maps 225 number of repetitions for GetBulk requests configuring maximum 299 O Objectserer multitier 152 SEA 152 ObjectSerer 200 aggregation 21 collection 21 failoer 245 multiple domains 22 single domain 21 iewing multiple domains 23 irtual pair 245 OMNIbus probes 158 online publications i operating system tools 36 operating systems installation 32 OQL Serice Proider configuring authentication 296 ordering publications i oerlay icon for manually added deices 235 P partition domains 20 password encryption 196 permissions root/non-root, UNIX 213 poll Juniper Remote Ping 292 position of nodes 229 postinstallation 81 prerequisite automated check 48 Probe for Tioli Netcool/OMNIbus configuring 165 properties file 166 rules file 166 probes configuring 158 installing 158 processes eents generated 161 publications i R rediscoery 229 registry default security 200 remoing reporting 93 reports 93 repetitions for GetBulk requests configuring maximum number 299 reporting migrate Cognos content store to DB2 240 reports configuring 239 rules file processing example 167 S SAE configuring automation for 152 scripts ConfigOMNI 43 security default registry 200 ault key 196 serice x serice management connect x serice-affected eents configuring automation for 152 settings in the status.properties file 233 silent mode creating file with launchpad 74 editing sample file 75 example parameters 73 installation 73 response file parameters 75 single sign-on 195 configuring 195 SMC x SNMP Helper actiating throttling 297 configuring 297 configuring throttling 297 configuring to use GetBulk 298 Index 313

328 SNMP 2 and 3 configuring GetBulk 298 SSL certificate 204 status information eents 161 status.properties settings 233 support x IBM Support Assistant 302 support information x swap space, requirements 28 switching to legacy V3.8 topology isualization mode 236 T TBSM eents 194 TCP connection Virtual Domain 272 throttling actiating on SNMP Helper 297 TIPHOME 288 TIPProfile_create.log 86 Tioli Common Reporting 47 Tioli Integrated Portal configuration 195 installation requirements 27 Tioli Netcool/OMNIbus additional database fields 156 configuration 151 UNIX 157 Tioli Netcool/OMNIbus probes 158 Tioli software information center i Tioli technical training ix topology database setup 44 topology map appearance configuring 225 topology map updates configuring 225 topology maps appearance of nodes and lines 225 topology iews configuring default type 155 topology isualization switching to legacy V3.8 mode 236 topoiz.node.freezeold 229 topoiz.node.new.placement 229 topoiz.node.new.spacing.horizontal 229 topoiz.node.new.spacing.ertical 229 tracking failoer 279 training, Tioli technical ix troubleshooting console mode error 89 default ports 88 dependency error messages 89 disk space 89 root/non-root users 89 troubleshooting installation 84 typeface conentions xi uninstalling (continued) reports 93 UNIX DB2 database 44 directory requirements 37 root/non-root permissions 213 root/non-root user installation 213 user restrictions, installation 37 unset DISPLAY 89 upgrade logs 147 upgrading 111, 138 exporting core customization data 114 exporting customization GUI data 115 importing customization data 119 importing GUI customization data 130 installation 110 preparing for 112 user registry default 200 V V3.8 isualization mode switching back to 236 VACM access for Juniper Remote Ping poll 292 ariables, notation for xi ault key file 196 iewing edge of network 187 isualization switching to legacy V3.8 mode 236 VMM for ObjectSerer 200 W Web GUI data source failoer 251, 267 Windows directory requirements 37 U uninstalling on UNIX 93 oeriew 93 reporting IBM Tioli Network Manager IP Edition: Installation and Configuration Guide

329

330 Printed in the Republic of Ireland