IBM Tivoli Netcool Performance Manager Wireline Component Document Revision R2E1. Installing and Using Tivoli Monitoring Agent IBM

Transcription

1 IBM Tivoli Netcool Performance Manager Wireline Component Document Revision R2E1 Installing and Using Tivoli Monitoring Agent IBM

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

3 Contents About this information v Audience v What this information contains v Service Management Connect v Tivoli Netcool Performance Manager technical training v Support information vi Conventions used in this publication vi Typeface conventions vi Chapter 1. Installation IBM Tivoli Monitoring architecture Tivoli Enterprise Monitoring Server Tivoli Enterprise Portal Tivoli Enterprise Monitoring Agents Requirements Installation process Installing Tivoli Monitoring components Configuring Tivoli Monitoring Installing the Tivoli Netcool Performance Manager Monitoring Agent (pw) Starting the Tivoli Netcool Performance Manager Monitoring Agent Installing OS agent on Tivoli Netcool Performance Manager DataChannel server Deploying Tivoli Netcool Performance Manager Monitoring Agent Deploying Integrated Virtual Ethernet (IVE).. 16 Renaming workspaces Chapter 2. Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring Top level view Navigating to monitored Tivoli Netcool Performance Manager Installations Dashboard view Normal processing Data processing Tabular view of dashboard Configuration workspace Oracle Data Load Workspace Channel performance workspace Flow control workspace Self-monitoring Topology view Chapter 3. Troubleshooting Checking IVE status Checking the status of the application with Manage Tivoli Enterprise Monitoring Services console.. 37 Log of clean Tivoli Monitoring Installation Installing additional agents to TEMS depot Chapter 4. Known problems and solutions No data in KPW1001 and KPW1005 workspace.. 51 Topology not populated in KPW1007 workspace despite all the DataChannel components running.. 51 rootdirectory and inputdirectory is empty in KPW1009 workspace PW agent deployment status is showing Failed 51 Notices Trademarks Terms and conditions for product documentation.. 56 Copyright IBM Corp. 2007, 2016 iii

4 iv IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

5 About this information Audience IBM Tivoli Monitoring monitors and manages system and network applications on a variety of operating systems, tracks the availability and performance of your enterprise system, and provides reports to track trends and troubleshoot problems. The IBM Tivoli Monitoring application operates by deploying agents to monitor the performance of target systems and to relay the data back to the IBM Tivoli Monitoring system, where it can be stored and reported on. This information provides details of installing IBM Tivoli Monitoring agents and using them with IBM Tivoli Netcool Performance Manager. This information is intended for administrators or operations specialists responsible for installing and administrating IBM Tivoli Monitoring and Tivoli Netcool Performance Manager. What this information contains This information contains the following sections: v Chapter 1, Installation, on page 1 Service Management Connect v Chapter 2, Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring, on page 21 v Chapter 3, Troubleshooting, on page 37 Connect, learn, and share with Service Management professionals: product support technical experts who provide their perspectives and expertise. Access Network and Service Assurance community at developerworks/servicemanagement/nsa/index.html. Use Service Management Connect in the following ways: v Become involved with transparent development, an ongoing, open engagement between other users and IBM developers of Tivoli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code. v Connect one-on-one with the experts to collaborate and network about Tivoli and the Network and Service Assurance community. v Read blogs to benefit from the expertise and experience of others. v Use wikis and forums to collaborate with the broader user community. Related information: Tivoli Netcool Performance Manager 1.4 community on developerworks Tivoli Netcool Performance Manager technical training For Tivoli Netcool Performance Manager technical training information, see the following Tivoli Netcool Performance Manager Training website at: Copyright IBM Corp. 2007, 2016 v

6 Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: Online Access the IBM Software Support site at support/probsub.html. IBM Support Assistant The IBM Support Assistant is a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. The Support Assistant provides quick access to support-related information and serviceability tools for problem determination. To install the Support Assistant software, go to support/isa. Troubleshooting Guide For more information about resolving problems, see the problem determination information for this product. Conventions used in this publication Several conventions are used in this publication for special terms, actions, commands, and paths that are dependent on your operating system. Typeface conventions This publication uses the following typeface conventions: Bold Italic Monospace v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text v Citations (examples: titles of publications, diskettes, and CDs) v Words defined in text (example: a nonswitched line is called a point-to-point line) v Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictive clause."; letters as letters example: "The LUN address must start with the letter L.") v New terms in text (except in a definition list): a view is a frame in a workspace that contains data. v Variables and values you must provide:... where myname represents... v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type vi IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

7 v Values for arguments or command options Bold monospace v Command names, and names of macros and utilities that you can type as commands v Environment variable names in text v Keywords v Parameter names in text: API structure parameters, command parameters and arguments, and configuration parameters v Process names v Registry variable names in text v Script names About this information vii

8 viii IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

9 Chapter 1. Installation Use this information to install IBM Tivoli Monitoring package before you integrate with IBM Tivoli Netcool Performance Manager. Use Tivoli Monitoring, version 6.3, Fix Pack 6. For step-by-step installation and setup instructions, see IBM Knowledge Center. Related information: IBM Tivoli Monitoring V6.3 Fix Pack 2 documentation on IBM Knowledge Center IBM Tivoli Monitoring architecture IBM Tivoli Monitoring Version Fix Pack 6 README Describes the architecture of the IBM Tivoli Monitoring products and provides information to help you plan your deployment and prepare to install or upgrade the base components of the product. Related information: Components of the monitoring architecture Tivoli Enterprise Monitoring Server The Tivoli Enterprise Monitoring Server is the key component on which all other architectural components directly depend. The monitoring server collects and controls all data and alerts received from monitoring agents. The Tivoli Enterprise Monitoring Server that is referred to as the monitoring server is the first component to install to begin building the Tivoli Management Services foundation. The monitoring server is the collection and control point for performance and availability data and alerts received from monitoring agents. It is also responsible for tracking the online or offline status of monitoring agents. Tivoli Enterprise Portal Tivoli Enterprise Portal is the interface to your monitoring products. The Tivoli Enterprise Portal consists of the Tivoli Enterprise Portal Server and one or more clients. The Tivoli Enterprise Portal Server is referred to as the portal server manages data access through user workspace consoles (the portal clients). The portal server connects to a monitoring server; it retrieves data from the hub in response to user actions at a portal client, and sends the data back to the portal client for presentation. The portal server also provides presentation information to the portal client so that it can render the user interface views suitably. Copyright IBM Corp. 2007,

10 Requirements Tivoli Enterprise Monitoring Agents Monitoring agents are data collectors. Agents monitor systems, subsystems, or applications, collect data, and pass the data to the Tivoli Enterprise Portal through the monitoring server. Installation process An agent interacts with a single system or application and, in most cases, is located on the same computer where the system or application is running. There are two types of monitoring agents: v Operating system (OS) agents that monitor the availability and performance of the computers in your monitoring environment. An example of an OS agent is the Monitoring Agent for Windows OS, which monitors Windows XP and Windows 2003 operating systems. v Other agents are referred to as application agents or non-os agents that monitor the availability and performance of systems, subsystems, and applications. Supported Tivoli Monitoring version in Tivoli Netcool Performance Manager v1.4.2 is IBM Tivoli Monitoring 6.3 Fix Pack 6. It is important to ensure that your system meets these requirements before you install IBM Tivoli Monitoring. Related information: IBM Tivoli Monitoring V Hardware and software requirements The installation process consists of these steps. 1. Install Tivoli Monitoring server as root user. 2. Tivoli Monitoring base configuration as root user. 3. Deploy a remote monitoring agent. 4. Start Tivoli Monitoring components. 5. Install and configure Tivoli Netcool Performance Manager Monitoring Agent as root user. 6. Deploy IVE as pvuser. Installing Tivoli Monitoring components Install Tivoli Monitoring components that are needed for the integration. About this task Follow these steps to install the monitoring components on a Linux or UNIX computer. Procedure 1. In the directory where you extracted the installation files, run the following command:./install.sh 2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to accept the default directory,/opt/ibm/itm. 2 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

11 3. Follow the prompts and install the product. See the Log of clean Tivoli Monitoring Installation on page 38 section for appropriate options to select for the installation. Results The following components are installed: v Tivoli Enterprise Monitoring Automation Server v Tivoli Enterprise Monitoring Server v Tivoli Enterprise Portal Desktop Client v Tivoli Enterprise Portal Server v Tivoli Enterprise Services User Interface Extensions v Tivoli Performance Analyzer v Warehouse Proxy Related information: Installing the monitoring server Configuring Tivoli Monitoring The base configuration includes configuring Tivoli Enterprise Monitoring server and Tivoli Enterprise Portal server. Configuring Tivoli Enterprise Monitoring Server You can configure the monitoring server by using the command line or GUI. About this task If you want to configure user security, login as root user. Follow these steps to configure the Tivoli Enterprise Monitoring Server by using command line: Procedure 1. At the command line, change to the /opt/ibm/itm/bin directory or the directory where you installed IBM Tivoli Monitoring. 2. Run the following command:./itmcmd config -S -t <tems_name> Where <tems_name> is the name of your monitoring server. For example, HUB_itmdev Use the default values in the prompts that appear as follows: Chapter 1. Installation 3

12 Configuring TEMS... Hub or Remote [1=*LOCAL, 2=*REMOTE] (Default is: 1): Network Protocol 1 [ip, sna, ip.pipe, ip.spipe, ip6, ip6.pipe, ip6.spipe] (Default is: ip.pipe): Now choose the next protocol from one of these: - ip - sna - ip.spipe - ip6 - ip6.pipe - ip6.spipe - 0 for none Network Protocol 2 (Default is: 0): TEMS Host Name for IPv4 (Default is: tnpmuslnx0107): IP.PIPE Port Number (Default is: 1918): Enter name of KDC_PARTITION (Default is: null): Enter path and name of KDC_PARTITIONFILE (Default is: /opt/ibm/itm/tables/tems/partition.txt): Configuration Auditing? [1=YES, 2=NO] (Default is: 1): Specify Hot Standby? [1=YES, 2=NO] (Default is: 2): Enter Optional Primary Network Name or type 0 for "none" :(Default is: 0): Security: Validate User? [1=YES, 2=NO] (Default is: 2): Tivoli Event Integration Facility? [1=YES, 2=NO] (Default is: 2): Disable Workflow Policy/Tivoli Emitter Agent Event Forwarding? [1=YES, 2=NO] (Default is: 2): Enable TEMS Security Compatibility Mode? [1=YES, 2=NO](Default is: 1):... Writing to database file for ms. Hubs ## CMS_Name 1 ip.pipe:tnpmuslnx0107[1918] 1)Add, 2)Remove ##, 3)Modify Hub ##, 4)UserAccess ##, 5)Cancel, 6)Save/exit: 6... created SOAP file "/opt/ibm/itm/tables/tems/html/kshxhubs.xml"... creating config file "/opt/ibm/itm/config/ms.config"... creating file "/opt/ibm/itm/tables/tems/glb_site.txt."... updating "/opt/ibm/itm/config/kbbenv"... verifying Hot Standby. TEMS configuration completed... Results The monitoring server is now configured. A configuration file is generated in the install_dir/config directory with the name ms.config. Related information: Configuring the hub monitoring server Configuring Tivoli Enterprise Portal Server You can configure the portal server by using either the command line or GUI. About this task This configuration accomplishes the following tasks: v Automatically enables application support on the portal server for the base monitoring agents. v Includes steps for configuring the connection between the portal server and the following components: The hub monitoring server The portal server database The Tivoli Data Warehouse database Follow these steps to configure the server by using command line: 4 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

13 Procedure 1. Log in to the computer where the Tivoli Enterprise Portal Server is installed as root user. 2. Change to the <install_dir>/bin directory from command line, where <install_dir> is the directory where you installed the product. 3. Run the following command to start configuring the Tivoli Enterprise Portal Server:./itmcmd config -A cq Where cq is the product code for the portal server. 4. Use the default values in the prompts that appear as follows: Agent configuration started... Edit "Common event console for IBM Tivoli Monitoring" settings? [ 1=Yes, 2=No ] (default is: 1): Edit ITM Connector settings? [ 1=Yes, 2=No ] (default is: 1): Enable this connector [ 1=Yes, 2=No ] (default is: 1): Connector name (default is: ITM1): Maximum number of events for this connector (default is: 100): View closed events [ 1=Yes, 2=No ] (default is: 2): Edit TEC Connector settings? [ 1=Yes, 2=No ] (default is: 1): No TEC Connector settings available. Edit TEC Connector settings, [1=Add, 2=Edit, 3=Del, 4=Next, 5=Exit] (default is: 5): Edit OMNIbus Connector settings? [ 1=Yes, 2=No ] (default is: 1): No OMNIbus Connector settings available. Edit OMNIbus Connector settings, [1=Add, 2=Edit, 3=Del, 4=Next, 5=Exit] (default is: 5): Edit Names of Extra Columns settings? [ 1=Yes, 2=No ] (default is: 1): Name of extra column 1 (default is: ): Name of extra column 2 (default is: ): Name of extra column 3 (default is: ): Name of extra column 4 (default is: ): Name of extra column 5 (default is: ): Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): Network Protocol [ip, sna, ip.pipe, ip.spipe, ip6, ip6.pipe or ip6.spipe] (Default is: ip.pipe): Now choose the next protocol from one of these: - ip - sna - ip.spipe - ip6 - ip6.pipe - ip6.spipe - 0 for none Network Protocol 2 (Default is: 0): TEMS Host Name for IPv4 (Default is: tnpmuslnx0107): IP.PIPE Port Number (Default is: 1918): Enter name of KDC_PARTITION [type 0 for null] (Default is: 0): Enter Optional Primary Network Name or 0 for "none" (Default is: 0): Enable SSL for TEP Clients (1=Yes, 2=No)(Default is: 2): Notice: Embedded TEPS DB is not supported for distributed cluster configurations. Which database would you like to use for TEPS (1=Embedded, 2=DB2)(Default is: 2): 1 Notice: The Warehouse DB must be an existing database, no new database will be created automatically. Are you using DB2, Oracle or None for Warehouse? [1=DB2, 2=Oracle, 3=None] (Default is: 1): 3 LDAP Security: Validate User with LDAP? (1=Yes, 2=No)(Default is: 2): Enable the dashboard data provider? (1=Yes, 2=No)(Default is: 2): Tivoli Enterprise Portal server configuration was updated to reflect Eclipse Help Server configuration changes.... running InstallPresentation.sh... InstallPresentation.sh completed Agent configuration completed... Related information: Configuring the portal server on Linux or AIX: command-line procedure Deploying a remote monitoring agent These steps add bundles to Tivoli Monitoring depot for remote agent deployment. Chapter 1. Installation 5

14 Before you begin IBM Tivoli Monitoring version 6.3 introduces a number of platform improvements that might require operating system updates. Ensure that the system meets these requirements before you install or update your installation. For more information, see the technical note: IBM Tivoli Monitoring V6.3 Supported Operating Systems About this task Use the following steps to add bundles for the remote agent deployment on a Linux or UNIX computer. Procedure 1. In the directory where you extracted the installation files, run the following command:./install.sh 2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to accept the default directory (/opt/ibm/itm) or type the full path to a different directory. Note: Do not use the number sign (#) or exclamation mark (!) characters anywhere in your installation directory path. 3. If the installation directory does not exist, you are asked if you want to create it. Type Y to create this directory and press Enter. The following prompt is displayed: Select one of the following: 1) Install products to the local host. 2) Install products to depot for remote deployment (requires TEMS). 3) Install TEMS support for remote seeding 4) Exit install. Please enter a valid number: 4. Type 2 to start the installation and display the software license agreement as follows: Initializing... International Program License Agreement Part 1 - General Terms BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, CLICKING ON AN "ACCEPT" BUTTON, OR OTHERWISE USING THE PROGRAM, LICENSEE AGREES TO THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF LICENSEE, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND LICENSEE TO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS, * DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, CLICK ON AN "ACCEPT" BUTTON, OR USE THE PROGRAM; AND * PROMPTLY RETURN THE UNUSED MEDIA, DOCUMENTATION, AND Press Enter to continue viewing the license agreement, or enter "1" to accept the agreement, "2" to decline it, "3" to print it, "4" to read non-ibm terms, or "99" to go back to the previous screen. 1 The following product packages are available for depot installation: Code Decription(version) [base platform:supported platforms] 1) ax IBM Tivoli Monitoring Shared Libraries( ) [li6263:li6263,li6265,li6266] 2) ax IBM Tivoli Monitoring Shared Libraries( ) [lx8263:lx8263] 3) ax IBM Tivoli Monitoring Shared Libraries( ) [lx8266:lx8266] 4) ci IBM Tivoli Monitoring Product Installer( ) [unix:aix513,aix516,aix523, aix526,aix533,aix536,hp11,hp116,hpi113,hpi116,li6223,li6242,li6243,li6245,li6246,li6262,li6263,li6265, li6266,lia246,lia266,lpp246,lpp263,lpp266,ls3223,ls3226,ls3242,ls3243,ls3245,ls3246,ls3262,ls3263,ls3265, ls3266,lx8246,lx8263,lx8266,sol283,sol286,sol293,sol296,sol503,sol506,sol603,sol606,ta6046,tv6256] 5) gs IBM GSKit Security Interface( ) [li6243:li6243,li6263,lx8263] 6 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

15 6) gs IBM GSKit Security Interface( ) [lx8266:lx8266] 7) hd Warehouse Proxy( ) [lx8266:lx8266] 8) jr Tivoli Enterprise-supplied JRE( ) [li6263:li6263,lx8266] 9) jr Tivoli Enterprise-supplied JRE( ) [lx8266:lx8266] 10) la IBM Tivoli LAP tool( ) [unix:aix513,aix516,aix523,aix526,aix533,aix536,hp11, hp116,hpi113,hpi116,li6223,li6242,li6243,li6245,li6246,li6262,li6263,li6265,li6266,lia246,lia266,lpp246, lpp263,lpp266,ls3223,ls3226,ls3242,ls3243,ls3245,ls3246,ls3262,ls3263,ls3265,ls3266,lx8246,lx8263,lx8266, sol283,sol286,sol293,sol296,sol503,sol506,sol603,sol606,ta6046,tv6256] 11) sy Summarization and Pruning Agent( ) [lx8266:lx8266] 12) ue Tivoli Enterprise Services User Interface Extensions( ) [li6263:li6263,li6265,li6266] 13) ue Tivoli Enterprise Services User Interface Extensions( ) [lx8263:lx8263] 14) ue Tivoli Enterprise Services User Interface Extensions( ) [lx8266:lx8266] 15) ui Tivoli Enterprise Services User Interface( ) [li6263:li6263,li6265,li6266] 16) ui Tivoli Enterprise Services User Interface( ) [lx8263:lx8263] 17) ui Tivoli Enterprise Services User Interface( ) [lx8266:lx8266] Enter the numbers beside the products to install. If you enter more than one number separate them by commas or spaces. To deselect a selected product enter its number again. To flip the selection on all products type all and to flip the selection on a range ofproducts type the beginning and ending range numbers separated by a hypen. For example: 8-14 (Do not put any spaces to the immediate left or right of the hypen) Navigation: U)Up line D)Down line F)Forward page B)Back page E)Exit and process selections C)Cancel selections and quit. Type your selections here: 1-17 Code Decription(version) [base platform:supported platforms] 1) * ax IBM Tivoli Monitoring Shared Libraries( ) [li6263:li6263,li6265,li6266] 2) * ax IBM Tivoli Monitoring Shared Libraries( ) [lx8263:lx8263] 3) * ax IBM Tivoli Monitoring Shared Libraries( ) [lx8266:lx8266] 4) * ci IBM Tivoli Monitoring Product Installer( ) [unix:aix513,aix516,aix523,aix526, aix533,aix536,hp11,hp116,hpi113,hpi116,li6223,li6242,li6243,li6245,li6246,li6262,li6263,li6265,li6266,lia246, lia266,lpp246,lpp263,lpp266,ls3223,ls3226,ls3242,ls3243,ls3245,ls3246,ls3262,ls3263,ls3265,ls3266,lx8246,lx8263, lx8266,sol283,sol286,sol293,sol296,sol503,sol506,sol603,sol606,ta6046,tv6256] 5) * gs IBM GSKit Security Interface( ) [li6243:li6243,li6263,lx8263] 6) * gs IBM GSKit Security Interface( ) [lx8266:lx8266] 7) * hd Warehouse Proxy( ) [lx8266:lx8266] 8) * jr Tivoli Enterprise-supplied JRE( ) [li6263:li6263,lx8266] 9) * jr Tivoli Enterprise-supplied JRE( ) [lx8266:lx8266] 10) * la IBM Tivoli LAP tool( ) [unix:aix513,aix516,aix523,aix526,aix533,aix536,hp11,hp116, hpi113,hpi116,li6223,li6242,li6243,li6245,li6246,li6262,li6263,li6265,li6266,lia246,lia266,lpp246,lpp263,lpp266, ls3223,ls3226,ls3242,ls3243,ls3245,ls3246,ls3262,ls3263,ls3265,ls3266,lx8246,lx8263,lx8266,sol283,sol286,sol293, sol296,sol503,sol506,sol603,sol606,ta6046,tv6256] 11) * sy Summarization and Pruning Agent( ) [lx8266:lx8266] 12) * ue Tivoli Enterprise Services User Interface Extensions( ) [li6263:li6263,li6265,li6266] 13) * ue Tivoli Enterprise Services User Interface Extensions( ) [lx8263:lx8263] 14) * ue Tivoli Enterprise Services User Interface Extensions( ) [lx8266:lx8266] 15) * ui Tivoli Enterprise Services User Interface( ) [li6263:li6263,li6265,li6266] 16) * ui Tivoli Enterprise Services User Interface( ) [lx8263:lx8263] 17) * ui Tivoli Enterprise Services User Interface( ) [lx8266:lx8266] Enter the numbers beside the products to install. If you enter more than one number separate them by commas or spaces. To deselect a selected product enter its number again. To flip the selection on all products type all and to flip the selection on a range ofproducts type the beginning and ending range numbers separated by a hypen. For example: 8-14 (Do not put any spaces to the immediate left or right of the hypen) Navigation: U)Up line D)Down line F)Forward page B)Back page E)Exit and process selections C)Cancel selections and quit. Type your selections here: e copy files for package axli6263 [V ]... copy files for package axlx8263 [V ]... copy files for package axlx8266 [V ]... copy files for package ciunix [V ]... copy files for package gsli6243 [V ]... copy files for package gslx8266 [V ]... copy files for package hdlx8266 [V ]... Chapter 1. Installation 7

16 WARNING - KCIIN0317W...Additional prerequisites required for package hdlx8266 [V ]: Processsing prereq #1 Code: ci Version: 06 copy files for package ciunix [V ]... Processsing prereq #2 Code: ax Version: 06 copy files for package axlx8266 [V ]... Processsing prereq #3 Code: ui Version: 06 copy files for package uilx8266 [V ]... Processsing prereq #4 Code: jr Version: 07 copy files for package jrlx8266 [V ]... Processsing prereq #5 Code: gs Version: 08 copy files for package gslx8266 [V ]... copy files for package jrli6263 [V ]... copy files for package jrlx8266 [V ]... copy files for package launix [V ]... copy files for package sylx8266 [V ]... WARNING - KCIIN0317W...Additional prerequisites required for package sylx8266 [V ]: Processsing prereq #1 Code: ci Version: 06 copy files for package ciunix [V ]... Processsing prereq #2 Code: ax Version: 06 copy files for package axlx8266 [V ]... Processsing prereq #3 Code: ui Version: 06 copy files for package uilx8266 [V ]... Processsing prereq #4 Code: jr Version: 07 copy files for package jrlx8266 [V ]... Processsing prereq #5 Code: gs Version: 08 copy files for package gslx8266 [V ]... copy files for package ueli6263 [V ]... WARNING - KCIIN0317W...Additional prerequisites required for package ueli6263 [V ]: Processsing prereq #1 Code: ci Version: 06 copy files for package ciunix [V ]... Processsing prereq #2 Code: ax Version: 06 copy files for package axli6263 [V ]... Processsing prereq #3 Code: jr Version: 07 copy files for package jrli6263 [V ]... Processsing prereq #4 Code: gs Version: 08 copy files for package gsli6243 [V ]... copy files for package uelx8263 [V ]... WARNING - KCIIN0317W...Additional prerequisites required for package uelx8263 [V ]: Processsing prereq #1 Code: ci Version: 06 copy files for package ciunix [V ]... Processsing prereq #2 Code: ax Version: 06 copy files for package axlx8263 [V ]... Processsing prereq #3 Code: gs Version: 08 WARNING - KCIIN0320W unable to locate the package prerequisite. copy files for package uelx8266 [V ]... WARNING - KCIIN0317W...Additional prerequisites required for package uelx8266 [V ]: Processsing prereq #1 Code: ci Version: 06 8 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

17 copy files for package ciunix [V ]... Processsing prereq #2 Code: ax Version: 06 copy files for package axlx8266 [V ]... Processsing prereq #3 Code: jr Version: 07 copy files for package jrlx8266 [V ]... Processsing prereq #4 Code: gs Version: 08 copy files for package gslx8266 [V ]... copy files for package uili6263 [V ]... copy files for package uilx8263 [V ]... copy files for package uilx8266 [V ]... Related information: Linux or UNIX: Installing a remote monitoring server Starting the Tivoli Monitoring components You can use the Manage Tivoli Enterprise Monitoring Services tool to start and stop components. Procedure 1. Change to the bin directory: cd <install_dir>/bin 2. Run the following command by using the parameters described in the table:./itmcmd manage [-h install_dir] [-s] Option Description -h (Optional) An option that is used to specify the installation directory. install_dir The installation directory for IBM Tivoli Monitoring. -s (Optional) Option to specify safe mode operation. Safe mode starts the JRE with the -nojit option (no just-in-time compiler). If you encounter a Java failure error, try running the command as before, but also specifying the -s option. Entering the commands with -? displays the syntax for using the -s option. The Manage Tivoli Enterprise Monitoring Services utility is displayed. 3. From the UI, start the following components: v v Tivoli Enterprise Monitoring Server Tivoli Enterprise Portal Server 4. Open web client and make sure that local OS node is visible and the workspaces are present: Go to and click Tivoli Enterprise Portal Server Web Client. 5. Click the notification to see the new machine in the tree view. After a sometime, you see a notification of pending view update on your web client. Related information: Chapter 1. Installation 9

18 Starting Manage Tivoli Enterprise Monitoring Services on Linux or UNIX computers Installing the Tivoli Netcool Performance Manager Monitoring Agent (pw) Use the agent installation wizard to install the pw monitoring agent and its support files on the Tivoli Enterprise Monitoring Server. This agent is referred to as Monitoring Agent for Proviso-Monitoring. About this task Perform these steps as root user. The kpw_itm_proviso_52.tar.gz file contains the monitoring agent for Tivoli Netcool Performance Manager. Note: pw is the product code for the monitoring agent that is associated with Tivoli Netcool Performance Manager Procedure 1. Transfer the KPW Solutions Install Image (kpw_itm_proviso_52.tar.gz) to a shared directory on the Tivoli Enterprise Monitoring Server. 2. Copy the compressed solutions image from a shared directory to some temp directory. For example, /tmp/kpw) and extract: tar xvf kpw_itm_proviso_52.tar.gz 3. Run the installation by using the following command:./setuplinux.bin Follow these steps to start the installation. The installation for each agent is the same. 4. Click Next to proceed to IBM Tivoli Monitoring installation directory and installable media locations. 5. Enter the IBM Tivoli Monitoring installation directory. By default, /opt/ibm/itm. 6. Enter the location of the installable media. The location where the Tivoli Netcool Performance Manager agent installer is copied. 7. Click Next to proceed to IBM Tivoli Monitoring components. 8. Select both options to perform a local installation and Tivoli Enterprise Monitoring Server depot installation. v Perform a local installation of the solution on this machine This option is used only if the IBM Tivoli Monitoring server is also used as one of the Tivoli Netcool Performance Manager servers to be monitored. For example, if the IBM Tivoli Monitoring server is also used as the Tivoli Netcool Performance Manager application server. The agent can be started and used to monitor its Tivoli Netcool Performance Manager component. v Perform a TEMS depot installation of the solution on this machine Install the Tivoli Netcool Performance Manager agent on the remote source depot of IBM Tivoli Monitoring. Selecting this option is recommended because it enables remote deployment of agents from the Tivoli Enterprise Portal GUI. 9. Click Next and enter the Tivoli Enterprise Monitoring Server User ID, Password, and host name. 10. Click Next. 10 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

19 11. Select Monitoring Agent for Proviso-Monitoring application. 12. Click Next. Confirm your choices, and click Next to proceed to install. 13. When the installation is complete, click Finish to close the wizard. Note: To install a newer version of the agent, run the installation with the new installation media Starting the Tivoli Netcool Performance Manager Monitoring Agent You can also use the Manage Tivoli Enterprise Monitoring Services tool to start and stop components. About this task Start the pw monitoring agent if it is monitoring Tivoli Netcool Performance Manager instances on the same host as the Tivoli Enterprise Monitoring Server. Procedure 1. Start the Manage Tivoli Enterprise Monitoring Services tool by using the following commands: cd <install_dir>/bin itmcmd manage 2. Optional: Check if Monitoring Agent for Proviso-Monitoring is configured. If the Configured column displays No, then you must configure by following these steps: a. Right-click the agent and click Configure. b. Type $DC_HOME in DataChannel Runtime Configuration. By default, /opt/proviso/datachannel. Chapter 1. Installation 11

20 3. Right-click Monitoring Agent for Proviso-Monitoring and select Start Service. Installing OS agent on Tivoli Netcool Performance Manager DataChannel server You have to manually install the OS agent on Tivoli Netcool Performance Manager cmgr host and configure it to connect to the Tivoli Enterprise Monitoring Server. About this task To create a node on Tivoli Netcool Performance Manager cmgr host which enables it to connect to the Tivoli Enterprise Monitoring Server. These steps are needed for pw agent remote deployment. Procedure 1. Extract the IBM Tivoli Monitoring (ITM) OS agent installer. 2. In the directory where you extracted the installation files, run the following command as root user:./install.sh 3. Follow the prompts and install the product. For example: Enter the name of the IBM Tivoli Monitoring directory [ default = /opt/ibm/itm ]: ITM home directory "/opt/ibm/itm" already exists. OK to use it [ 1-yes, 2-no; "1" is default ]? KCI1362W IBM Tivoli Monitoring version 6.3 introduces a number of platform improvements which may require operating system updates. It is important that you ensure this system meets these requirements prior to installing or updating your installation. Please refer to the following technote for more information: Select one of the following: 1) Install products to the local host. 2) Install products to depot for remote deployment (requires TEMS). 3) Install TEMS support for remote seeding 4) Exit install. Please enter a valid number: 1 Initializing... International Program License Agreement Part 1 - General Terms BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, CLICKING ON AN "ACCEPT" BUTTON, OR OTHERWISE USING THE PROGRAM, LICENSEE AGREES TO THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF LICENSEE, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND LICENSEE TO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS, * DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, CLICK ON AN "ACCEPT" BUTTON, OR USE THE PROGRAM; AND * PROMPTLY RETURN THE UNUSED MEDIA, DOCUMENTATION, AND Press Enter to continue viewing the license agreement, or enter "1" to accept the agreement, "2" to decline it, "3" to print it, "4" to read non-ibm terms, or "99" to go back to the previous screen IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

21 Product packages are available in /media/images/itm/630fp2/tmv630fp2-d3248a _all/tmv630fp2-d3248a agents.tar.gz/unix The following products are currently installed in "/opt/ibm/itm": IBM GSKit Security Interface Linux x86_64 R2.6, R3.0 (64 bit) Monitoring Agent for Proviso-Monitoring Linux x86_64 R2.6, R3.0 (64 bit) Tivoli Enterprise Services User Interface Extensions Linux x86_64 R2.6, R3.0 (64 bit) Tivoli Enterprise Services User Interface Linux x86_64 R2.6, R3.0 (64 bit) All agents require that application support files that contain agent-specific information be installed on the Tivoli Enterprise Monitoring Server that the agents will connect to, Tivoli Enterprise Portal Server and Tivoli Enterprise Portal desktop and browser client. Install application support before starting to install any Tivoli Enterprise Monitoring Agents. The following products are available for installation: 1) Agentless Monitoring for AIX Operating Systems V ) Agentless Monitoring for HP-UX Operating Systems V ) Agentless Monitoring for Linux Operating Systems V ) Agentless Monitoring for Solaris Operating Systems V ) Agentless Monitoring for Windows Operating Systems V ) Monitoring Agent for Linux OS V ) Tivoli Enterprise Services User Interface Extensions V ) all of the above Type the numbers that correspond to the products that you want to install. Type "b" to change operating system, or type "q" to quit selection. If you enter more than one number, separate the numbers by a comma or a space. Type your selections here: 6 The following products will be installed: Monitoring Agent for Linux OS V Are your selections correct [ 1=Yes, 2=No ; default is "1" ]? 1 Do you want to check prerequisites for the above components? [ 1=Yes, 2=No ; default is "1" ]? 1 Running Prerequisite Scanner. This may take a few minutes depending on the number of components being checked and the machine s performance. Prerequisite Scanner results for the selected components: PASS IBM Tivoli Monitoring Shared Libraries /opt/ibm/itm/logs/prereqscan/ /common/result.txt PASS IBM GSKit Security Interface /opt/ibm/itm/logs/prereqscan/ /common/result.txt PASS Tivoli Enterprise-supplied JRE /opt/ibm/itm/logs/prereqscan/ /common/result.txt PASS Monitoring Agent for Linux OS /opt/ibm/itm/logs/prereqscan/ /common/result.txt PASS Prerequisite Scanner Overall Result /opt/ibm/itm/logs/prereqscan/ /common/result.txt Do you want to continue with the installation [ 1=Yes, 2=No ; default is "1" ]? 1... installing "Monitoring Agent for Linux OS V for Linux x86_64 R2.6, R3.0 (64 bit)"; please wait. => installed "Monitoring Agent for Linux OS V for Linux x86_64 R2.6, R3.0 (64 bit)".... Initializing component Monitoring Agent for Linux OS V for Linux x86_64 R2.6, R3.0 (64 bit).... Monitoring Agent for Linux OS V for Linux x86_64 R2.6, R3.0 (64 bit) initialized. Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is "2" ]? 2... postprocessing; please wait.... finished postprocessing. Installation step complete. You may now configure any locally installed IBM Tivoli Monitoring product via the "/opt/ibm/itm/bin/itmcmd config" command. Automatic start at system initialization has been configured. Automatic stop at system shutdown has been configured. The install.sh command creates most of directories and files with world write permissions. IBM Tivoli Monitoring provides the securemain utility to helps you keep the monitoring environment secured. You can secure this installation now or manually execute the securemain utility later. For more information see Appendix G. Securing your IBM Tivoli Monitoring installation on Linux or UNIX in the IBM Tivoli Monitoring Installation and Setup Guide. Do you want to secure this IBM Tivoli Monitoring installation [ 1-yes, 2-no; "2" is default ]? 2 4. Verify the OS agent installation by running the following command: # cd <install_dir>/bin #./cinfo -t Chapter 1. Installation 13

22 Note: <install_dir> refers to the installation directory for IBM Tivoli Monitoring. For example: *********** Tue May 31 18:14:01 IST 2016 ****************** User: root Groups: root Host name : tnpminlnx0103 Installer Lvl: CandleHome: /opt/ibm/itm Version Format: VV.RM.FF.II (V: Version; R: Release; M: Modification; F: Fix; I: Interim Fix) ***********************************************************...Product inventory PC PRODUCT DESC PLAT VER BUILD INSTALL DATE ax IBM Tivoli Monitoring Shared Libraries lx d3248a gs IBM GSKit Security Interface lx d3221a - jr Tivoli Enterprise-supplied JRE lx lz Monitoring Agent for Linux OS lx pw Monitoring Agent for Proviso-Monitoring lx ue Tivoli Enterprise Services User Interface Extensions lx d3248a ui Tivoli Enterprise Services User Interface lx d3248a Run the following command to configure the OS agent: For example: # cd <install_dir>/bin #./itmcmd config -A lz Agent configuration started... Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): Network Protocol [ip, sna, ip.pipe, ip.spipe, ip6, ip6.pipe or ip6.spipe] (Default is: ip.pipe): Now choose the next protocol from one of these: - ip - sna - ip.spipe - ip6 - ip6.pipe - ip6.spipe - 0 for none Network Protocol 2 (Default is: 0): TEMS Host Name for IPv4 (Default is: tnpminlnx0103): IP.PIPE Port Number (Default is: 1918): Enter name of KDC_PARTITION (Default is: null): Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2): Enter Optional Primary Network Name or 0 for "none" (Default is: 0): Agent configuration completed... Note: lz is the product code for Linux OS agent. 6. Start the OS agent by using the following command: # <install_dir>/bin/itmcmd agent start lz Processing. Please wait...] Starting Monitoring Agent for Linux OS... Monitoring Agent for Linux OS started 14 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

23 Deploying Tivoli Netcool Performance Manager Monitoring Agent The Tivoli Netcool Performance Manager Monitoring Agent must be deployed on all Tivoli Netcool Performance Manager installations. About this task For each Tivoli Netcool Performance Manager installation, deploy the Monitoring Agent to monitor that Tivoli Netcool Performance Manager instance. Procedure 1. As user root, log in to Tivoli Enterprise Monitoring Server by using the tacmd command as follows: /opt/ibm/itm/bin/tacmd login -s <TEMS_IP> -u root 2. List available nodes with this command: /opt/ibm/itm/bin/tacmd listsystems You see a similar output: Managed System Name Product Code Version Status tnpminlnx0103:pw PW Y tnpminlnx0103:lz LZ Y TEMS EM Y tnpmkllnx0114:pw PW Y tnpmkllnx0114:teps CQ Y 3. Deploy the agent with this command: /opt/ibm/itm/bin/tacmd addsystem -t pw -n <cmgr_host>:<product_code> For example: /opt/ibm/itm/bin/tacmd addsystem -t pw -n tnpminlnx0103:lz 4. Configure the deployed monitoring agent by following these steps: /opt/ibm/itm/bin/itmcmd config -A pw Provide the DataChannel home directory and the correct TEMS_IP. Accept the default values for the rest of the prompts. Chapter 1. Installation 15

24 Agent configuration started... Edit "Monitoring Agent for Proviso-Monitoring" settings? [ 1=Yes, 2=No ] (default is: 1): Edit DC settings? [ 1=Yes, 2=No ] (default is: 1): DC_HOME (default is: /opt/proviso/datachannel): Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): Network Protocol [ip, sna, ip.pipe, ip.spipe, ip6, ip6.pipe or ip6.spipe] (Default is: ip.pipe): Now choose the next protocol from one of these: - ip - sna - ip.spipe - ip6 - ip6.pipe - ip6.spipe - 0 for none Network Protocol 2 (Default is: None): TEMS Host Name for IPv4 (Default is: tnpmuslnx0107.persistent.co.in): IP.PIPE Port Number (Default is: 1918): Enter name of KDC_PARTITION (Default is: null): Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2): Enter Optional Primary Network Name or 0 for "none" (Default is: 0): Agent configuration completed... Would you like to restart the component to allow new configuration to take effect? [1=Yes, 2=No] (Default is: 1): Stopping Monitoring Agent for Proviso-Monitoring Monitoring Agent for Proviso-Monitoring stopped Starting Monitoring Agent for Proviso-Monitoring Monitoring Agent for Proviso-Monitoring started 5. Restart the agent by using the following commands: /opt/ibm/itm/bin/itmcmd agent stop pw /opt/ibm/itm/bin/itmcmd agent start pw Deploying Integrated Virtual Ethernet (IVE) Instructions on how to deploy IVE. This step involves setting up IVE component that collects performance data from DataChannel and passes them to Tivoli Monitoring About this task Perform the following steps on Tivoli Netcool Performance Manager server, as pvuser. Procedure 1. Extract IVE media (ive-52.tar.gz) in the $DC_HOME directory: cd $DC_HOME../dataChannel.env gunzip ive-52.tar.gz tar xvf ive-52.tar 2. Run the following command to generate dc.cfg file into /opt/proviso/ datachannel/conf/ directory. dccmd debug CMGR "self dbcfgprint" egrep ^(AMGR CMGR CNS LOG CME FTE BCOL UBA LDR DLDR DISC PBL) >> $DC_HOME/conf/dc.cfg Note: The installive.sh script refers to the generated dc.cfg file to get the user name. By default, it is PV_LDR_ Run the install script and answer the prompts as follows: cd $DC_HOME/bin./installIVE.sh Enter the following data: 16 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

25 v Database user name and password. By default, PV_LDR_01. The ive.cfg file is generated in the $DC_HOME/conf/ directory. 4. Edit the ive.cfg file to change DB_USERNAME string from PV_LDR_01 to PV_ADMIN. The contents of ive.cfg file are as follows: #DC CFG #IVE IVE.1.1.ROOT_DIRECTORY=/opt/proviso/datachannel IVE.1.1.SCRIPTS_DIRECTORY=/opt/proviso/datachannel/scripts/IVE IVE.1.1.DB_USERNAME=PV_ADMIN IVE.1.1.DB_PASSWORD=AAAC 5. Check the IVE_visual execution to make sure that it is calling dc.im in startive.sh script that is available in $DC_HOME/bin folder by using this command: $DC_BIN_HOME/pvexec IVE_visual $DC_BIN_HOME/visual -nologo -noherald $DC_BIN_HOME/dc.im -headless -a IVE -f $DC_HOME/conf/ive.cfg -c 1 -l -name IVE.1.1 1& 6. Start IVE by using this command:./startive.sh Renaming workspaces Instructions on how to rename workspaces. About this task This task must be performed for each of the following: v Rename DC Flow Control or kpw1009 to Configuration v Rename DC Health or kpw1001 to Oracle Data Load v Rename DC LDR Tag or kpw1007 to Channel Performance v Rename DC Topology or kpw1003 to Not Configured v Rename DL Health or kpw1005 to Collector Dashboard v Rename Performance Object Status or kpw1011 to Flow Control Procedure 1. Select the workspace Chapter 1. Installation 17

26 Figure 1. Workspace selection 2. Select the workspace properties. 18 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

27 Figure 2. Workspace Properties 3. Rename the workspace. Chapter 1. Installation 19

28 20 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

29 Figure 3. Renaming workspace. Chapter 2. Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring A description of how to use IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring. Tivoli Netcool Performance Manager is a high-performance scalable network performance management solution. Monitoring Tivoli Netcool Performance Manager with IBM Tivoli Monitoring integration allows displaying status of Tivoli Netcool Performance Manager in the IBM Tivoli Monitoring management portal. This gives customers the support needed to view the state of the data flow, progress of individual components and tightly monitor the system for a range of performance and service-level indicators. Copyright IBM Corp. 2007,

30 Top level view The top level view is the enterprise status. The top level view provides an overview on all systems being monitored. If there any problems in components or servers, they will be shown in red, as illustrated in the figure below: Figure 4. Top level view This shows two components with critical issues. It shows what server is reporting the issue and what agent is reporting it. In the above, we are having problems with pl2app7 and cme6 as reported by the PW (Tivoli Netcool Performance Manager) agent. Notice the tree view on the left, there are x icons next to the agents reporting problems on their perspective servers. Drill down in the tree view to see the agents that are reporting the issues. The hierarchy of the tree is as follows: Enterprise, System Type, Server, Agent, Workspace. 22 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

31 Navigating to monitored Tivoli Netcool Performance Manager Installations Instructions how to navigate to monitored Tivoli Netcool Performance Manager Installations. Figure 5. Workspace Dashboard view Expand the tree view in the upper left till you reach the server and expand Proviso Monitoring. This will display the workspaces that show different aspects of the running Tivoli Netcool Performance Manager system. Contents of the Dashboard view. The Dashboard view contains the following Component Topology v Quick Component Status is Displayed by hovering your cursor over a component s icon (see below). v Shows the flow of data through the system. Quick Status (Component List/Status Tabular View) Shows health, lag time, last alarm, and is flow controlled for each component. Chapter 2. Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring 23

32 Laggards View (Components that are most behind in data processing) Shows the lag time in each of the components in an easy to see graph. Data Queue Utilization (buffering of data on component s ingress and egress) Shows the amount of buffered input and output data in each component. Oracle Data Load Status (Data types that are most out of date) Shows the load latency for each stream. Component Memory Utilization (10 largest memory consumers) Shows the amount of memory each component is using. Normal processing Contents of the Dashboard view. Figure 6. Normal processing Critical indicators: v Quick Status: No red flags, lagbehind (in minutes) is within 2 hours (120 minutes). v Data queue utilization: Both input and output queues for each component should be green. v 10 Least Recently Loaded DB Partitions: loadlag should be within 2 hours (120 minutes) 24 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

33 Data processing An example of a data Processing Issue. The example illustrates how the UI indicates that CME.1.1 is blocked. Figure 7. CME.1.1 is blocked The chart shows: Topology and Quick Status: CME.1.1 is unreachable (in reality it was down). This means data processing is blocked at CME.1.1. Data Queue Utilization: Since CME.1.1 is not capable of processing its stream of input data, data has piled up at the output of FTE Least Recently Loaded DB Partitions: Data from CME.1.1 is not loaded in the DB in timely manner. The chart shows the last data NRAW, DRA and DGA data from CME.1.1 hasn t been loaded almost minutes ago (normal latency should be less than 1.5 hour Chapter 2. Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring 25

34 Tabular view of dashboard The tabular view of dashboard. Figure 8. Tabular view 26 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

35 Figure 9. Flow Control by Statistics by Component More detailed view than Data Queue Utilization from Proviso Monitoring. Details in the table at the bottom (Flow Control by Statistics by Component). The details include: v Flow control state v Used Quota v Used Quota Percent - large percentages ie 90% should be looked at. v In Buffer Start the youngest data in the input buffer waiting to be processed v In Buffer Size Minutes amount of data waiting to be processed (anything more than 2 hours should be looked at) v Out Buffer Start the youngest data in the output buffer v Out Buffer Size Minutes amount of data processed v Output Data Minutes amount of data processed v FC Quota quota allowed for this component v FC LL v FC Retention Hours v Root Directory location of component on file system. It is where it places its input, output, and state files. Chapter 2. Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring 27

36 Configuration workspace The configuration workspace. Figure 10. Configuration Configured Components: v Details the channel/subchannel for each component along with any aliases. v Root directory and where the component gets its input from Metadata Details the number of elements, subelements, formulas, and requests Agent Collection Status Details status of the Tivoli Monitoring scripts and if the component is running or not. Deployed UBAs Details the UBA instance name and the design file for each running UBA component CME.1.1 Blocked In Configuration Workspace An example of how to use the UI to spot that a component is not processing. 28 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

37 Figure 11. CME.1.1 Blocked The configuration view can quickly point out if any components are down. In the above screenshot, you can see the empty entries for rootdirectory in the Configured Components view. Another thing to notice is the highlighted yellow numbers in the Metadata view. It shows no inventory for CME. This is a key indicator that the CME.1.1 component is not processing. Chapter 2. Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring 29

38 Oracle Data Load Workspace The Oracle Data Load workspace. Figure 12. Oracle Data Load workspace Report: v Database partition for each component v Load latency v Timestamps for most recent period and load v Computed in and by Least Recently Loaded v Graph to use to quickly see which partition has the largest latency in processing CME.1.1 down in Oracle Data Load An example of how to use the UI to spot that a component is not processing. 30 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

39 Figure 13. CME.1.1 down Notice the red values in the loadlag column. This means that the data on the 1.1 channel are far behind. Glance over to the right and you can see who computes the data. This can be used to find which component might be done or not processing data. The graph on the right helps to show where the problem areas are. Chapter 2. Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring 31

40 Channel performance workspace The channel performance workspace. Figure 14. Channel performance workspace Topology: v Shows how data flows through the system Report v Shows various statistics on state of each component v Be on the lookout for currenthourtimestampstring on each component and make sure none are falling behind. In the example above, CME.1.1 is behind by almost a month. CME.1.1 blocked in Channel Performance An example of how to use the UI to spot that a component is not processing. 32 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

41 Figure 15. CME.1.1 blocked Notice the yellow fields in the Report in the bottom pane. The health of 1 and 0 raw buckets are indicators of down component. Chapter 2. Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring 33

42 Flow control workspace More detailed view of data flow status. Figure 16. Flow control workspace More detailed view of data flow status. It specifically flags data pileup at FTE.1.1. The bottom chart shows there is 3119 minutes of data now buffered, the earliest unprocessed data going back to while the rest of the system processes data for This is a difference of over a three days, a sign that a component is down. 34 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

43 Self-monitoring Topology view Self-monitoring Topology view. Figure 17. Self-monitoring Topology Chapter 2. Using IBM Tivoli Monitoring Tivoli Netcool Performance Manager Monitoring 35

44 36 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent

45 Chapter 3. Troubleshooting Checking IVE status This section provides instructions on how to confirm Tivoli Netcool Performance Manager Tivoli Monitoring agents are producing data on your Tivoli Netcool Performance Manager installation. Use the log files to check that IVE is running. Procedure 1. Check the last modified time on IVE logs as follows: a. Change directory: ~]$ cd $DC_HOME/log b. Run the command: log]$ ls -lrt ITM*.log Output: -rw-r--r-- 1 pvuser staff 90 May 5 08:50 ITM_DC_flow_control.log -rw-r--r-- 1 pvuser staff 952 May 5 08:50 ITM_DC_health.log -rw-r--r-- 1 pvuser staff 765 May 5 08:50 ITM_DC_ldr_lag.log -rw-r--r-- 1 pvuser staff 180 May 5 08:50 ITM_DC_Topology.log If any of the logs are over an hour old, then IVE is possibly not running. 2. Check IVE process to make sure that it is running. a. Run the command: [cmedev@pl2app7 cmedev]$ ps -ef grep IVE grep -v grep Output: cmedev Oct 07 pts/5 1181:50 /opt/proviso/datachannel/bin/ive_visual -nologo -noherald /opt/proviso/datachan b. Optional: Run the startive.sh script in $DC_HOME/bin, if the ps-ef command does not return any value. Checking the status of the application with Manage Tivoli Enterprise Monitoring Services console Use the Manage Tivoli Enterprise Monitoring Services console to ensure that the correct applications are running. Procedure 1. Run the command:./itmcmd manage Copyright IBM Corp. 2007,

46 Figure 18. Tivoli Monitoring Management console 2. Make sure that the following services are started: v v v Monitoring Agent for Proviso-Monitoring Tivoli Enterprise Monitoring Server Tivoli Enterprise Portal Server Log of clean Tivoli Monitoring Installation./install.sh INSTALL Enter the name of the IBM Tivoli Monitoring directory [ default = /opt/ibm/itm ]: "/opt/ibm/itm" does not exist Try to create it [ 1-yes, 2-no; "1" is default ]? 1 This is a log of Tivoli Monitoring installation. KCI1362W IBM Tivoli Monitoring version 6.3 introduces a number of platform improvements which may require operating system updates. It is important that you ensure this system meets these requirements prior to installing or updating your installation. Please refer to the following technote for more information: Select one of the following: 1) Install products to the local host. 2) Install products to depot for remote deployment (requires TEMS). 3) Install TEMS support for remote seeding 4) Exit install. Please enter a valid number: 1 Initializing... International Program License Agreement Part 1 - General Terms 38 IBM Tivoli Netcool Performance Manager: Installing and Using Tivoli Monitoring Agent