IBM Tivoli Netcool Performance Manager 1.4 Wireline Component Document Revision R2E1. DataMart Configuration and Operation Guide

Transcription

1 IBM Tivoli Netcool Performance Manager 1.4 Wireline Component Document Revision R2E1 DataMart Configuration and Operation Guide

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

3 Contents Preface vii Intended audience vii Tivoli Netcool Performance Manager - Wireline Component vii Service Management Connect viii Tivoli technical training ix Support information ix Conventions used in this publication ix Typeface conventions ix Chapter 1. Introduction Configuring DataMart GUI Opening DataMart GUI The Tivoli Netcool Performance Manager DataMart tabs and utilities Configuration Data Manager Metric Monitor Resource Where to go from here Chapter 2. Configuring users and groups Creating a user Deleting a user Creating a group of users Deleting a group Granting rights to groups Understanding the DataMart modules Chapter 3. Configuring inventory Before you begin Configuring your network inventory Using the Inventory Tool Creating an inventory profile Configuring your discovery Selecting your network discovery method Specifying IP addresses Defining an SNMP configuration Specifying SNMP community names Specifying an ICMP configuration Configuring labels for subelements Specifying synchronization Inserting resources Specifying automatic grouping Specifying repository group rules Selecting modules Running an inventory profile Viewing the log file Reloading collectors Deleting a profile SNMP bandwidth control and collection smoothing 29 Bandwidth control Collection smoothing Understanding file formats Element file Subelement file Managing dynamic changes Guidelines CME formula command template Example based on process illustration Example for 2233_IF family CME processing Discovery server responsibilities Logging policy Configuring a bulk collector inventory Understanding a bulk collector inventory Importing bulk files Bulk collector inventory file sets pollinv and pollprofile commands Inventory polling and the cron table Directories and files (location, naming, and format) 44 Bulk file format examples Element resources Subelement resources Inventory arguments Chapter 4. Creating grouping rules.. 47 Before you begin Creating grouping rules Using operators and functions Using conditions Using grouping rules Testing grouping rules Saving test results Copying grouping rules Moving grouping rules Deleting Grouping Rules Understanding the file format Viewing rule database information Viewing properties Using syntax for grouping rules Using static text Creating variables Using a text editor to create grouping rules Exporting grouping rules Importing grouping rules Understanding the file format Grouping rule example Name with static text Name with a variable Nested variable Condition Example of nested conditions Condition Nested condition Second nested condition Variable Copyright IBM Corp. 2012, 2014 iii

4 Example of combining text, a variable, and a condition Chapter 5. Collection and aggregation 65 Before you begin Configuring data collection requests Setting the collection period Configuring aggregation requests Configuring a percentile value Filtering requests Sorting columns Validating the requests Chapter 6. Configuring calendars Using the Calendar Configuration Tool Creating customized calendars Creating a one-time calendar Creating a daily calendar Creating a weekly calendar Creating a monthly calendar Deleting a calendar Using the Calendar Selector Chapter 7. Writing custom formulas.. 75 Before you begin What is a formula? Merging discovery results Creating formulas Editing the inventory_subelement.txt file Testing formulas Saving formulas Modifying a custom formula Standard rules for writing formulas Dim declaration OIDVAL expression line OIDINST instruction Example Types of variables Instance variables Temporary variables Host variable Returning a result Comments in formulas Syntax for functions Mathematical functions Other functions SNMP-specific functions Aggregate functions Filter functions Distribution function AddForMissing() operator Example Using the Formula Selector Creating a formula group Finding a formula Copying formulas Deleting a formula Renaming a formula Discovery formula for a Redback Ethernet interface Collection formula example Merge formulas example inventory_sub-element.txt _IF _IF _HCOctets_Support _HCPackets_Support _IF_Invariant _IF_Invariant <CustomerSpecific>_KEY Formula error messages Understanding the inventory_subelements.txt file 102 SysObjId FilterFormulaName SubElementFamilyName to cancel Chapter 8. Configuring thresholds 107 About thresholds Threshold types User profiles and threshold types Basic computation Statistic used for processing Exceeding a threshold level Interpolation Threshold deployment Examples TRAP generation rules Using the threshold definition period setting Processing traps Launching the threshold tool Adding a threshold Selecting metrics Applying thresholds to a group of subelements 117 Specifying subelements Configuring burst or period thresholds Configuring thresholds Configuring mode Configuring maximum percent over for burst and period thresholds Configuring burst values Configuring period values Configuring baseline thresholds Trapping threshold violations Trapping threshold violations to the log file Sending trapped threshold violations to specified hosts Chapter 9. Managing MIBs MIB groups Compiling a MIB Printing or saving trace information Deleting a MIB Viewing MIB file source Browsing MIB files Viewing compiled MIB files Chapter 10. Editing resources Filtering elements and subelements Viewing resource information Viewing elements iv IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

5 Viewing subelements Viewing subelement groups Viewing property details Viewing reports Viewing thresholds Exporting resources Importing resources Adding resources Adding elements Adding subelements Adding composite subelement relations Adding reports Adding thresholds Creating a property Modifying resources Modifying an element Modifying a subelement Modifying a report Modifying Thresholds Deleting resources Deleting elements or subelements Deleting subelement groups Deleting resources within groups Deleting properties Deleting composite Subelement relations Deploying reports Chapter 11. Viewing collected data 163 Viewing graphical charts for files Viewing graphical charts for subelements Viewing graphical charts for subelement groups 165 Saving a graph Printing a graph Configuring graphs Displaying crosshairs Displaying a grid Configuring a title Configuring the X-Axis Customizing the Y-Axis Configuring curves Configuring a graph legend Viewing scheduler information Viewing data manager information Viewing target information Viewing detailed technical information Stopping and restarting a local collector Restarting a local collector Configuring watchdog for collector memory checking Parameters Activation of memory checking Setting lower and upper limits Setting inflation limit Chapter 13. Viewing status Viewing DataMart status Removing a lock from the database Chapter 14. Viewing database information Viewing database free space status Viewing database parameters Viewing database statistics Viewing the Tivoli Netcool Performance Manager version information Viewing MetaData Viewing MetricData Viewing client information Viewing database status Viewing disk information Chapter 15. Exporting or Importing Metadata Exporting data Export files Importing data Glossary Notices Chapter 12. Viewing the list of collectors Viewing collector information Contents v

6 vi IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

7 Preface Intended audience The purpose of this guide is to help you work with Tivoli Netcool Performance Manager DataMart. lbm Tivoli Netcool Performance Manager 1.4 is a bundled product consisting of a wireline component and a wireless component. The audience for this guide is the Tivoli Netcool Performance Manager administrators who assign permissions, create groups, associate users with reports, and manage Tivoli Netcool Performanc Manager DataMart. Tivoli Netcool Performance Manager - Wireline Component IBM Tivoli Netcool Performance Manager consists of a wireline component (formerly Netcool/Proviso) and a wireless component (formerly Tivoli Netcool Performance Manager for Wireless). Tivoli Netcool Performance Manager - Wireline Component consists of the following subcomponents: v v v v v DataMart is a set of management, configuration, and troubleshooting GUIs. The Tivoli Netcool Performance Manager System Administrator uses the GUIs to define policies and configuration, and to verify and troubleshoot operations. DataLoad provides flexible, distributed data collection and data import of SNMP and non-snmp data to a centralized database. DataChannel aggregates the data collected through Tivoli Netcool Performance Manager DataLoad for use by the Tivoli Netcool Performance Manager DataView reporting functions. It also processes online calculations and detects real-time threshold violations. DataView is a reliable application server for on-demand, web-based network reports. Technology Packs extend the Tivoli Netcool Performance Manager system with service-ready reports for network operations, business development, and customer viewing. The following figure shows the different Tivoli Netcool Performance Manager modules. Copyright IBM Corp. 2012, 2014 vii

8 Tivoli Netcool Performance Manager documentation consists of the following: v Release notes v Configuration recommendations v Installation and upgrade information v User guides v Technical notes v Online help The documentation is available for viewing and downloading on the information center at com.ibm.tnpm.doc/welcome_tnpm.html. Service Management Connect 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 Community on developerworks viii IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

9 Tivoli technical training Support information For Tivoli technical training information, see the following IBM Tivoli Education website at 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 v v v v v 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 Citations (examples: titles of publications, diskettes, and CDs 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... Monospace v Examples and code examples Preface ix

10 v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options 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 x IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

11 Chapter 1. Introduction Configuring DataMart GUI Tivoli Netcool Performance Manager DataMart supports a graphical user interface that lets you perform various administrative tasks. You can also manage, and review information about the resources and metrics being collected and stored in the Oracle or IBM DB2 database. In Tivoli Netcool Performance Manager 1.4, IBM DB2 is also supported along with Oracle database. The DataMart initial startup steps vary depending on whether you installed a minimal deployment or a distributed environment deployment. For a distributed environment deployment, the $PVHOME variable is defined as /opt/datamart by default. For a minimal deployment, the default is /opt/proviso/datamart. Explains how to configure DataMart GUI after a Tivoli Netcool Performance Manager installation. About this task The $PVMHOME variable is defined as /opt/datamart by default. For minimal deployment, the default is /opt/proviso/datamart. To configure DataMart GUI, follow these steps: 1. Log in as pvuser (or the user name that you specified during installation) on the system where DataMart is installed. Note: When you run the pvm command to access the DataMart for the first time, you must log in as pvuser. 2. On Linux systems only, create a softlink for the libcrypto.so file for the DataMart GUI to start by using the following command: ln -s libcrypto.so libcrypto.so.6 For information about the required linux packages, see Installing Tivoli Netcool Performance Manager - Wireline Component. 3. Ensure that the database is running. If you are using Oracle database, ensure that Oracle listener is also running. For more information, see Installing Tivoli Netcool Performance Manager - Wireline Component. 4. Source the DataMart environment by using the following command:. /opt/datamart/datamart.env 5. Run the following command: pvm The following information and prompt is displayed: Copyright IBM Corp. 2012,

12 Tivoli Netcool/Proviso - Wed Apr 7 09:34:34 IST 2010 Licensed Materials - Property of IBM 5724-P55, 5724-P57, 5724-P58, 5724-P59 Copyright IBM Corporation All Rights Reserved. US Government Users Restricted Rights- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Script revision DataMart configuration - Default Association Enter password for PV_ADMIN: Note: The DB_USER_ROOT password is required to connect to the database by using SQL*Plus. 6. Enter the password for DB_USER_ROOT (in this example, PV) and press Enter. 7. Confirm the password. The setup prompt for the Time Zone in the database appears. ==> Press <Enter> to continue... The following Time Zones are defined into the Database : id Date (in GMT) offset in Name Aggset status seconds /01/01 00:00:00 0 Greenwich Mean Time Aggset created ==> Press <Enter> to continue Press Enter to continue. The list of available Time Zones appears. Num OffSet Time zone Name Short Long Hours Description Description [ 1] : 0:00 Europe/London BST Greenwich Mean Time [ 2] : -10:00 America/Adak HADT Hawaii-Aleutian Standard Time [ 3] : -10:00 Pacific/Rarotonga CKT Cook Is. Time [ 4] : -9:00 AST AKDT Alaska Standard Time [ 5] : -9:00 America/Anchorage AKDT Alaska Standard Time [ 6] : -8:00 PST8PDT PDT Pacific Standard Time [ 7] : -7:00 MST7MDT MDT Mountain Standard Time [ 8] : -6:00 America/Mexico_City CDT Central Standard Time [ 9] : -6:00 CST6CDT CDT Central Standard Time [10] : -5:00 EST5EDT EDT Eastern Standard Time [11] : -4:00 America/Santiago CLST Chile Time [12] : -3:00 America/Sao_Paulo BRST Brasilia Time [13] : -1:00 Atlantic/Azores AZOST Azores Time [14] : 1:00 ECT CEST Central European Time [15] : 1:00 Europe/Paris CEST Central European Time [16] : 2:00 Africa/Cairo EEST Eastern European Time [17] : 2:00 Europe/Bucharest EEST Eastern European Time [18] : 2:00 Europe/Helsinki EEST Eastern European Time [19] : 3:00 Asia/Baghdad ADT Arabia Standard Time [20] : 3:00 Europe/Moscow MSD Moscow Standard Time [21] : 4:00 Asia/Baku AZST Azerbaijan Time [22] : 5:00 Asia/Yekaterinburg YEKST Yekaterinburg Time [23] : 6:00 Asia/Novosibirsk NOVST Novosibirsk Time [24] : 7:00 Asia/Krasnoyarsk KRAST Krasnoyarsk Time [25] : 8:00 Asia/Irkutsk IRKST Irkutsk Time [26] : 9:00 Asia/Yakutsk YAKST Yakutsk Time [27] : 10:00 Australia/Sydney EST Eastern Standard Time (New South Wales) 2 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

13 [28] : 11:00 Pacific/Noumea NCT New Caledonia Time [29] : 12:00 Asia/Anadyr ANAST Anadyr Time [30] : 12:00 Pacific/Auckland NZDT New Zealand Standard Time ==> Select Time Zone number [1-30 ] (E : Exit) : 1 ==> Select an Aggset ID to add/modify (E: Exit) : 1 ==> Does your Time Zone manage DST [Y/N] : Y 9. Select and enter your Time Zone number. For example, 1, for Greenwich mean time (GMT). 10. Select and enter your Time Zone number 1 again to confirm the Aggregation set (the offset hours in your GMT timezone) is associated with GMT 0: Enter Y if the Time Zone you selected manages Daylight Saving. 12. The following output shows that the process to start the DataMart is completed successfully. Complete with Success... The following Time Zone has been modified : id Date (in GMT) offset in Name Aggset status seconds /04/07 08:42: Greenwich Mean Time_2010_DST Aggset not created /10/31 01:00:00 0 Greenwich Mean Time_2010 Aggset not created /03/27 01:00: Greenwich Mean Time_2011_DST Aggset not created /10/30 01:00:00 0 Greenwich Mean Time_2011 Aggset not created /03/25 01:00: Greenwich Mean Time_2012_DST Aggset not created /10/28 01:00:00 0 Greenwich Mean Time_2012 Aggset not created /03/31 01:00: Greenwich Mean Time_2013_DST Aggset not created /10/27 01:00:00 0 Greenwich Mean Time_2013 Aggset not created /03/30 01:00: Greenwich Mean Time_2014_DST Aggset not created /10/26 01:00:00 0 Greenwich Mean Time_2014 Aggset not created /03/29 01:00: Greenwich Mean Time_2015_DST Aggset not created /10/25 01:00:00 0 Greenwich Mean Time_2015 Aggset not created /03/27 01:00: Greenwich Mean Time_2016_DST Aggset not created /10/30 01:00:00 0 Greenwich Mean Time_2016 Aggset not created /03/26 01:00: Greenwich Mean Time_2017_DST Aggset not created /10/29 01:00:00 0 Greenwich Mean Time_2017 Aggset not created /03/25 01:00: Greenwich Mean Time_2018_DST Aggset not created /10/28 01:00:00 0 Greenwich Mean Time_2018 Aggset not created /03/31 01:00: Greenwich Mean Time_2019_DST Aggset not created /10/27 01:00:00 0 Greenwich Mean Time_2019 Aggset not created /03/29 01:00: Greenwich Mean Time_2020_DST Aggset not created /10/25 01:00:00 0 Greenwich Mean Time_2020 Aggset not created /03/28 01:00: Greenwich Mean Time_2021_DST Aggset not created /10/31 01:00:00 0 Greenwich Mean Time_2021 Aggset not created /03/27 01:00: Greenwich Mean Time_2022_DST Aggset not created /10/30 01:00:00 0 Greenwich Mean Time_2022 Aggset not created /03/26 01:00: Greenwich Mean Time_2023_DST Aggset not created /10/29 01:00:00 0 Greenwich Mean Time_2023 Aggset not created /03/31 01:00: Greenwich Mean Time_2024_DST Aggset not created /10/27 01:00:00 0 Greenwich Mean Time_2024 Aggset not created /03/30 01:00: Greenwich Mean Time_2025_DST Aggset not created /10/26 01:00:00 0 Greenwich Mean Time_2025 Aggset not created /03/29 01:00: Greenwich Mean Time_2026_DST Aggset not created /10/25 01:00:00 0 Greenwich Mean Time_2026 Aggset not created /03/28 01:00: Greenwich Mean Time_2027_DST Aggset not created /10/31 01:00:00 0 Greenwich Mean Time_2027 Aggset not created /03/26 01:00: Greenwich Mean Time_2028_DST Aggset not created /10/29 01:00:00 0 Greenwich Mean Time_2028 Aggset not created /03/25 01:00: Greenwich Mean Time_2029_DST Aggset not created /10/28 01:00:00 0 Greenwich Mean Time_2029 Aggset not created Chapter 1. Introduction 3

14 1 2030/03/31 01:00: Greenwich Mean Time_2030_DST Aggset not created /10/27 01:00:00 0 Greenwich Mean Time_2030 Aggset not created ==> Press <Enter> to continue Press Enter. The DataMart GUI appears. Opening DataMart GUI Explains how to start and open DataMart GUI after it has been configured About this task To start Datamart GUI after it has been configured, follow these steps: Note: The $PVMHOME variable is defined as /opt/datamart by default. For minimal deployment, the default is /opt/proviso/datamart. If the main toolbar appears gray, the database is not running. 1. Log in as pvuser (or the user name that you specified during installation) on the system where DataMart is installed. 2. Ensure that the database is running. If you are using Oracle database, ensure that Oracle listener is also running. For more information, see Installing Tivoli Netcool Performance Manager - Wireline Component. 3. Source the DataMart environment using the following command:. /opt/datamart/datamart.env 4. Enter the following command: $PVMHOME/bin/pvm 4 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

15 The Tivoli Netcool Performance Manager DataMart tabs and utilities The Tivoli Netcool Performance Manager DataMart GUI supports the following tabs: v Configuration v Metric v Resource v Monitor v Data Manager Note: Each tab contains various graphical utilities that allow you to perform administrative tasks. Note: Tivoli Netcool Performance Manager DataMart supports an Adobe Acrobat PDF help system. You can access the online help system by selecting Tivoli Netcool Performance Manager DataMart Help... from the Help menu. Configuration The Configuration tab supports the following utilities: v v v v Import-Export Configuration - lets you import and export metadata (configuration data), such as requests, elements, and formulas between two Tivoli Netcool Performance Manager DataMart systems. For example, you can share information with other Tivoli Netcool Performance Manager DataMart users in different locations. Users Configuration - lets you create, modify, or delete user and group accounts and assign access privileges. Calendar Configuration - lets you define time ranges for data collection. Request Editor - lets you manage data collection parameters such as frequency and storage. Data Manager The Data Manager tab supports the following utility: Metric v Data Viewer - lets you view and verify collected data in the database in graphical charts. The Metric tab supports the following utilities: v Formula Editor - lets you create, modify, or delete formulas, which are a series of operations applied to one or more MIB objects. v MIB Browser - lets you browse a MIB-tree structure. You can test a specific OID before using it in a new formula or a request. You can drag an OID to another application where you want it to be used (such as Formula Editor, Request Editor, or Dashboard Editor). v MIB Compiler - lets you convert a management information base (MIB) file in Structure of Management Information (SMI) format to the Tivoli Netcool Performance Manager DataMart internal format. You can also add new MIBs in addition to the MIBs provided with Tivoli Netcool Performance Manager DataMart. Chapter 1. Introduction 5

16 Monitor The Monitor tab supports the following utilities: v v v Collector Information - provides information about collector parameters and activities. DataMart Status - lets you browse through a list of Tivoli Netcool Performance Manager DataMart modules that are registered in the current database, and the modules that are locked. Lets you unlock modules when necessary. Database Information - provides detailed statistical and graphical information about the Tivoli Netcool Performance Manager DataMart database. Resource The Resource tab supports the following utilities: Where to go from here v v v v Inventory Tool - lets you import, analyze, and discover elements and subelements in your network. Rule Editor - lets you create and edit grouping rules. SNMP Configuration - lets you define and maintain Simple Network Management Protocol (SNMP) parameters such as community names, port number, timeout value, and retry values. Resource Editor - lets you add, modify, export, and import elements, subelements, element groups, subelement groups, reports, and thresholds. The following chapters explain how to use the various DataMart utilities to administer Tivoli Netcool Performance Manager. 6 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

17 Chapter 2. Configuring users and groups Creating a user Explains how to create users and groups so that customers can access Tivoli Netcool Performance Manager DataMart. It also explains how to grant access rights. Explains how to create one or more user accounts for end-users that need access to Tivoli Netcool Performance Manager DataMart. You can specify whether a user account has read-only or full access rights to the Tivoli Netcool Performance Manager DataMart modules. About this task To create a user, follow these steps: 1. Click Users Configuration in the Configuration tab. The User Configuration Tool window appears. By default, the following users appears in the Users tab: v pvuser - an anonymous user account that you can provide to any authorized person for access to Tivoli Netcool Performance Manager DataMart. By default, the pvuser user account belongs to the admin group and has read and write access rights to all modules. You can modify the pvuser user account. v Note: You can choose the name for this user account during installation. For example, instead of pvuser, you can choose Jerry or operations. See the Installing Tivoli Netcool Performance Manager - Wireline Component for more details. root - the user account for the person(s) responsible for managing the Tivoli Netcool Performance Manager DataMart system on a network. By default, the root user account belongs to the admingroup and has read and write access rights to all modules. You cannot modify the root user account. Note: The daemon user is a special account used by database. You cannot modify this account. 2. Click New from the File menu. The New User window appears. 3. Enter the end user's operating system login name (in alphanumeric characters only) in the Login name box. 4. Optionally, enter the user's full name in the Full Name box. 5. Click on a group name in the Not member of box. For example, admin. 6. Click the left arrow button to add the user to that group. The group name you selected appears in the Member of box. 7. Click OK to accept your selections. 8. Repeat steps 2 through 6 to create as many user accounts as needed. 9. Grant the required user access rights to Tivoli Netcool Performance Manager DataMart modules. Copyright IBM Corp. 2012,

18 Deleting a user Creating a group of users See the section entitled Granting rights to groups on page 9 for instructions on granting user access rights to Tivoli Netcool Performance Manager DataMart modules. 1. Select the user name from the Users tab. 2. Click Delete from the Edit menu. A message box appears, asking you to confirm your choice. 3. Click Yes to confirm the deletion. The user is removed. Explains how to create a group for users that need access to Tivoli Netcool Performance Manager DataMart. When you add users to a group, the users belonging to that group automatically inherit the rights from the group. About this task To create a group, follow these steps: 1. Click Users Configuration in the Configuration tab. 2. Click the Groups tab. The following groups appear in the Groups tab by default: v admin - this group has write access privileges to all Tivoli Netcool Performance Manager DataMart modules. At least one user account must be a member of this group. You cannot modify or delete this group. v default - this group has read-only access to the Data Viewer module (by default), which can be used to view data that is collected for verification purposes. v pvusers - this group has read-only access to all Tivoli Netcool Performance Manager DataMart modules (by default). 3. Click New from the File menu. The New Group window appears. 4. Enter the name of the group in the Group name box. For example, Operations. Note: The group name must consist of only alphanumeric characters. 5. Optionally, enter a unique description for the group in the Description box. 6. Click a user name in the Are not members box. You can make multiple selections. 7. Click the left arrow button to add a user or users to the group. The user name appears in the Are members box. 8. Click OK to accept your selections. 9. Repeat steps 3 through 7 to add as many users to the group as needed. 8 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

19 Deleting a group About this task You must ensure that you do not delete the following DataMart user groups: Group Name default admin pvmusers Description Default users. Tivoli Netcool Performance Manager DataMart Administrators. Tivoli Netcool Performance Manager DataMart users. Granting rights to groups To delete a group, follow these steps: 1. Select the group name from the Group tab. 2. Click Delete from the Edit menu. Confirm your choice. 3. Click Yes to confirm the deletion. The group is removed. About this task After you create groups, you can assign rights to specific Tivoli Netcool Performance Manager DataMart modules for that group. To grant rights to groups, follow these steps: 1. Create a group Or 2. Double-click an existing group to edit it. 3. Click the Permissions at the bottom of the dialog box. The dialog box expands and displays the Permissions group. 4. Click in the Read or Write column to grant access for the wanted module. An "X" appears signifying that the module is selected. If you select Write access for a module, Read access is automatically included. For example, you might want to give full access rights for all modules to network operators and read-only rights to corporate executives. Note: Click again in a column if you must remove an "X." 5. Click OK when you are finished. 6. Repeat steps 2 through 4 until you granted all necessary rights to all groups. Chapter 2. Configuring users and groups 9

20 Understanding the DataMart modules About this task The following tables list the Tivoli Netcool Performance Manager DataMart modules for which you can grant access rights. Table 1. Configuration tools Module Import/Export Configuration Users Configuration Calendar Configuration Request Editor Description Lets you transfer hosts, subelements, dashboards, requests, formulas, calendars, and thresholds between two Tivoli Netcool Performance Manager DataMart systems. Lets you create user and group accounts and assign access privileges. Lets you define and modify time ranges for data collection. Lets you manage data collection parameters such as frequency and storage. Table 2. Metric tools Module Formula Editor MIB Browser MIB Compiler Description Lets you create formulas, which are a series of operations applied to one or more MIB objects. Lets you browse a MIB tree structure. Lets you convert a management information base (MIB) file in Structure of Management Information (SMI) format to the Tivoli Netcool Performance Manager DataMart internal format. Table 3. Resource tools Module Inventory Tool Rule Editor SNMP Configuration Resource Editor Description Lets you search for all SNMP hosts on a network and discover elements and subelements. Lets you create and edit grouping rules. Lets you define and maintain Simple Network Management Protocol (SNMP) community names. Lets view resource information, import resources, export resources, and to delete resources. Table 4. Monitor tools Module Collector Information DataMart Status Tool Description Provides information about collector activity. Lists all modules that are currently active. Lets you unlock modules when necessary. 10 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

21 Table 4. Monitor tools (continued) Database Information Lets you view information on DataMart database, instance and status. Table 5. Data Manager tools Module Data Viewer Description Lets you use view and verify collected data in the database. Table 6. Selector tools Module Formula Selector Calendar Selector Description Lets you select a formula from the formula library. Lets you designate a time to automatically launch one or more requests. Table 7. Command Line Interfaces Module Resource Manager (resmgr) Database Manager (dbmgr) Description Lets you import, export, modify, and delete objects in the database. These objects include elements, subelements, element and subelement groups, properties, thresholds, inventory profiles, Tivoli Netcool Performance Manager DataMart users and groups, web users, web reports, and web access. A utility that lets you create a database channel. Chapter 2. Configuring users and groups 11

22 12 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

23 Chapter 3. Configuring inventory Before you begin Explains how to import, analyze, and discover elements and subelements in your network using Resource Manager or the Inventory Tool. Before you configure your network inventory, ensure that: v Your computer is connected to a Internet Protocol network and has a valid IP address. v The default collector is running. For more information, see the Chapter 12, Viewing the list of collectors, on page 171. v You have installed Tivoli Netcool Performance Manager Technology Packs if you want to use default grouping rules. For instructions on installing Tivoli Netcool Performance Manager Technology Packs, see the Installing Tivoli Netcool Performance Manager - Wireline Component. Note: The Discovery Server uses the dig command from your operating system to interact with a DNS server. If the system is not configured correctly and the command does not work, then Tivoli Netcool Performance Manager fails in discovery from DNS. Consult your operating system configuration guide for troubleshooting information. The dig command with the axfr option uses an insecure method of retrieving the entire contents of a DNS server. For safety reasons, many DNS servers are now configured to reject such a command. For a secure DNS server, the dig command does not return anything. For such DNS servers, the Discovery Server with DNS import does not work. Either reconfigure the DNS to allow the axfr option, or try another import mechanism, such as files or /etc/hosts. Configuring your network inventory Explains how to gather information about elements and subelements in your network using the Inventory Tool. When you execute an inventory, the discovery phase searches for SNMP and non-snmp elements and subelements (known as resources). As these resources respond, their addresses are stored in the database for use in the analysis phase. The analysis phase stores the addresses of associated subelements. You can also configure an inventory using the inventory and resmgr commands. For more information, see the Command Line Interface Reference. Note: The Inventory Tool can find only operational elements. If an element is down, it is not detected. Copyright IBM Corp. 2012,

24 Using the Inventory Tool Click Inventory Tool in the Resource tab. The Inventory Tool window appears. A list of defined profiles appears. An example profile called default also appears, but it is not functional. Important: The Tivoli Netcool Performance Manager default inventory profile settings are used as examples. You must supply settings that are valid for your network. The following information is provided in the Configuration tab: Item Name Mode Collector ID Information Status Module to Run Description The name that you specify for the profile. The discovery mode. The collector identifier. Elements and subelements discovered while running the profile are assigned to this collector. To view the status on collectors, see Viewing collector information on page 171. Additional information about the profile, such as the IP addresses you are including or excluding. If you are importing data from a file, the file name is displayed. Provides the following information: v Ready appears after you create or edit a profile. v EndDiscovery appears after you complete a discovery. v SynchroReady appears after pre-synchronization when you run the profile from the command line (see note). v EndSynchro appears after synchronization. v GroupingReady appears after pre-grouping when you run the profile from the command line (see note). v EndGrouping appears after grouping. Indicates the modules that are enabled within the selected profile. A module can be enabled or disabled by clicking its name. Note: The inventory command-line interface (CLI) command launches the Inventory Tool from the command line. See the Command Line Interface Reference for instructions on using this CLI. 14 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

25 Creating an inventory profile The Inventory Tool Wizard lets you create and modify one or more profiles. A profile lets you define your network inventory. You can create different profiles for different resources in your network. About this task You can create a profile to do the following: v Divide your network between different SNMP community names. Grouping resources using alternative SNMP community names improves performance by providing collectors with multiple community names that limit the number of timeouts. v Separate resources with invariants that require editing during synchronization from those that require no editing. v Separate requests that you want to run at different times or different intervals. v Have one profile for each collector. CAUTION: If you include the same resource in two profiles, running the second profile overwrites the results of the first profile. To use the Inventory Tool Wizard, follow these steps: 1. Select New profile from the Edit menu. Note: Select Edit profile from the Edit menu if you want to edit an existing profile. 2. Enter a name for the profile in the Profile name field. If you are editing an existing profile, this field is automatically populated with the name of the profile. Important: You must not use any of the following reserved terms in the name of your profile: elt inventory slowwan exclude ipaddress snmpconf fastlan lan subelt filestoinsert mode subeltinv grouping objectfilter synchro icmp objectfilter wan include rulefilter ROOTROOT 3. If you are managing multiple networks where there is a possibility of duplicate IP addresses, select the Use duplicate IP addresses option. This option indexes a subelement name with a collector number so that identical IP addresses can be differentiated. 4. If you want to check invariants assigned to new resources against only other sub-elements that belong to the same element, select the Enforce Sub-element invariant uniqueness per element option. Chapter 3. Configuring inventory 15

26 5. If you want to poll or collect SNMP data from a network where the IP address is dynamic, select Target devices use dynamic DNS. Typically, residential cable modems use the dynamic IP address assignment. 6. Select an identifier for the collector in the Collector number and Discovery SNMP collector number lists. All elements and subelements discovered while running this profile are assigned to this collector. If you are importing a bulk file for a Bulk Collector inventory, ensure that you select a valid Bulk Collector number. For more information, see Installing Tivoli Netcool Performance Manager - Wireline Component. A network discovery is performed using the default collector that can later be assigned to a secondary collector. Ensure that the default collector can reach all nodes in the inventory. 7. In the Directory Configuration field, click Browse to go to the directory where you want to write the files generated by the inventory process. The default is the importexport directory where you installed Tivoli Netcool Performance Manager DataMart. 8. Click Next to proceed. 9. Select the modules that you want to configure for this profile. By default, all modules are selected. If you are editing an existing profile, modules that you do not configure retain the existing values. If you are creating a profile, modules that you do not configure retain the default values. The following table lists the supported modules: Module Discovery Synchronization Automatic Grouping Description Lets you specify the parts of your network to include in the profile. Lets you synchronize new data for your profile with existing data. Lets you specify grouping rules for this profile (default or custom). 10. Click Next. Configuring your discovery Explains how to use the Discovery Tool Wizard to specify what resources are included in your network inventory profile. To fully configure your profile, you must complete the tasks detailed in the following sections. Note: The window sequences displayed in the Discovery Tool Wizard might differ according to the selections you made. 16 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

27 Selecting your network discovery method Explains how to specify the discovery method for your network. You can choose to either discover network elements using SNMP requests, or import network elements from a Domain Name Server (DNS), Network Information Service (NIS), or host file. Note: Ensure that a running collector is available in your environment before selecting either the Discover elements & Analyze or Import elements & Analyze options. No running collector is required for the import from ASCII file option as the element and subelement files are produced by the bulk collector or an external provisioning system. Discovering network resources About this task To discover network resources, follow these steps: 1. Click the Discover elements & Analyze check box. Important: IBM recommends that you use this option only for small networks, since the length of time required to run might make it impractical to use on a large network. This network discovery method uses SNMP Get commands to retrieve MIB OIDs from target devices that are used to identify device types and their characteristics. 2. Click Next. Importing network resources About this task To import network resources, follow these steps: 1. Click the Import elements & Analyze check box. This option allows you to import resources from a domain-based (for example, DNS or NIS) or file-based (for example, /etc/host, HP OpenView, or elements list) source. This mode is recommended for large networks. If you import network resources and also list specific IP addresses, Tivoli Netcool Performance Manager discovers only elements that appear in both the imported list and the list of specific IP addresses. Note: The Import elements & Analyze mode must be used if you plan to run the inventory profile using the subprofile option. 2. To import resources from a domain-based source, select one of the following options: From DNS lets you import elements by specifying a valid Domain Name Server (DNS). Specify the DNS in the box to the right. The Inventory Tool displays the DNS in /etc/resolv.conf. From NIS lets you import elements by specifying a valid Network Information Chapter 3. Configuring inventory 17

28 Service (NIS) domain name. Specify the NIS domain name in the box to the right. The Inventory Tool displays the result of the UNIX command domainname if it is valid. 3. To import resources from a file-based source, select one of the following options: From /etc/hosts file format lets you import elements by specifying a file in the same format as the /etc/hosts file. For example: IP address HostName UNIX alias Cisco24 Cisco2500_BOSTON Cisco25 Cisco2500_NEWYORK Click Browse to specify the path and file name of the input file. From HP OpenView file format lets you import elements by specifying a file in the HPOpenView format. This file can be created by the command: $OV_BIN/ovtopodump -r Redirect the output to a file, then click Browse to specify the path and file name of the input file. From elements list lets you import elements by specifying a file. The file contains a list of IP addresses with one address on each line. This file can be a.txt file. Note: The From elements list option must be used if you plan to run the inventory profile using the subprofile option. Click Browse to specify the path and file name of the input file. 4. Click Next. Specifying IP addresses Explains how to include or exclude IP addresses from your network inventory profile. The IP address options are displayed. 1. Enter the IP addresses you want to include or exclude from your network discovery in the IP address entry box. Note: The Discovery Tool Wizard supports both IPv4 and IPv6 address formats. 2. Click <<Add to add it to the list of IP addresses to include in the discovery, or click Add>> to add it to the list of IP addresses to exclude from the discovery. 3. To modify an existing IP address: highlight the entry, so that it appears in the IP address entry box. Modify the entry in the IP address entry box, then click Modify. 4. To delete an IP address: highlight it and click Delete. To delete all the entries in the IP address include area, click <<Clear. To delete all the entries in the IP address exclude area, click Clear>>. 5. Click the ARP Query (Address Resolution Protocol) option if you want to use ARP tables to discover the elements specified in the IP address include area. 6. Click Next. 18 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

29 Defining an SNMP configuration Explains how to use the SNMP Configuration Tool to define general parameters for SNMP requests. The SNMP Configuration Tool is launched. 1. Click Open for the SNMP Configuration Tool. Note: You can also launch the SNMP Configuration tool from the command line using the snmpconf command-line interface (CLI) command. See the Command Line Interface Reference for instructions on using this CLI. 2. Click Apply Filter to list all of the elements currently in the SNMP configuration database. The following information is displayed for each entry: Item Name IP Address Type Read community Collector ID Write Community Timeout Retries Port Bandwidth Version Description Specifies the name of the device associated with this SNMP configuration. Specifies the IP address, mask, subnets, or address list for the device. Both IPv4 or IPv6 address formats are acceptable. Specifies the type of the device. Specifies the name of the SNMP read community. Identifies the collector associated with this SNMP configuration. A setting of 0 applies the SNMP configuration to all collectors. Specifies the name of the SNMP write community. Specifies the length of time (in seconds) to wait for a response from a request. Specifies the number of times that a request is tried again in the event of a request failure. Specifies the number of the port associated with this SNMP configuration. Specifies the maximum amount of traffic (in Kbps) permitted for the corresponding IP address. Specifies the SNMP version associated with this SNMP configuration. 3. To add or modify an entry, click Add or Update as appropriate. 4. Specify the name of the device associated with this SNMP configuration in the Element field. v Click Browse to launch the Resource Editor, where you can drag entries from the Resource Editor Elements tab to the Element field of the SNMP Configuration: Add/Update Configuration window. v Click Resolve to attempt to resolve the name in the Element field, and if possible, update the IP Address fields accordingly. 5. Specify the IP address, mask, subnets, or address list in the IP Address field. You can either drag entries from the addresses listed in the Range Defined on Profile field, or you can enter address information manually. Chapter 3. Configuring inventory 19

30 v v To specify an individual IP address, enter the address in the IP Address field. For example: (IPv4 address format) Or abcd:ef01:2345:6789:abcd:ef01:2345:6789 (IPv6 address format) To specify a mask of IP addresses, enter the mask information in the IP address field. Entering a range in IPv4 format: : Indicates an address list of , , and * : Indicates an address range of to ,16.* : Indicates two address ranges, one from to , and another from to Entering a range in IPv6 format: Note: IPv6 ranges can be specified using the CIDR notation. The characters '*' and '-' are not accepted. To specify a CIDR subnet, enter the subnet information in the IP address field. For example: /24 : Indicates an address range of to /25 : Indicates an address range of to :0:860:2::/64: Indicates an address range of 2620:0:860:2:: to 2620:0:860:2:FFFF:FFFF:FFFF:FFFF To specify several IP entries for the same SNMP configuration, enter the address information in the IP Address field with each entry separated by semi-colon characters. For example: ; ; *; /24 6. Specify the SNMP version used for this configuration from the Version list. Selecting a specific SNMP version inserts a corresponding version prefix at the beginning of the Read Community field, while selecting Auto omits the version prefix. Note: The ReadCommunity field is automatically populated for the following Version options and does not need updating: SnmpV3-No-Auth SnmpV3-Auth-MD5 SnmpV3-Auth-SHA SnmpV3-Auth-MD5-Priv-DES SnmpV3-Auth-SHA-Priv-DES SnmpV3-Auth-MD5-Priv-AES, SnmpV3-Auth-SHA-Priv-AES 7. Specify the name of the SNMP read community in the Read Community field. If you selected a specific SNMP version from the Version list, the corresponding version prefix must be used in the SNMP read community name. The Read Community field takes the parameters from the following controls and uses them to build the Read Community string: v v v Security Name: Specifies the user name to be used for this SNMP V3 element Auth. Password: Specifies the password to be used for authentication (MD5) for this SNMP V3 element. Priv. Password: Specifies the private password to be used with the following Version options: 20 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

31 SnmpV3-Auth-MD5-Priv-DES SnmpV3-Auth-SHA-Priv-DES SnmpV3-Auth-MD5-Priv-AES SnmpV3-Auth-SHA-Priv-AES v Context Name: Specifies the context name to be used for this SNMP V3 element. 8. Specify the name of the SNMP write community in the Write Community field. 9. Specify the length of time (in seconds) to wait for a response from a request in the TimeOut field. 10. Specify the number of times that a request must be tried again in the event of a request failure in the Retries field. 11. Specify the number of the port associated with this SNMP configuration in the Port field. A setting of 0 indicates that this SNMP configuration applies to all ports. 12. Specify the bandwidth limit for traffic (in Kbps) permitted for this SNMP configuration IP addresses in the Bandwidth field. 13. Specify the collector associated with this SNMP configuration from the Collector ID list. A setting of 0 indicates that this SNMP configuration is applicable to all collectors. 14. After specifying the SNMP configuration, click OK. Specifying SNMP community names Explains how to specify alternative community names, and determine if the SNMP configuration database must be updated if alternative community names are used. The SNMP community name options are displayed About this task To specify an SNMP community name, follow these steps: 1. To add a community name, type the name in the Alternative community names box, then click Add. You also use the Alternative community names box to specify an SNMP V3 community name, using the following syntax: &V3[{separator}{option}={value}...] where: v &V3 - Specifies a required string that indicates that this entry is an SNMP V3 community name. v separator - Specifies a character used to separate options specified in the community name. The separator can be any character, but the same separator character must be used to separate all of the options specified in the community name. Typically, you use a,(comma) character as the separator. However, if the, (comma) character is used in any of the passwords, you can substitute the comma with any other separator character (for example, -, and so on). v option - Specifies one or more option keywords that define an SNMP V3 community string. Each option keyword is followed by an = (equals sign). v value - Specifies a valid value for the specified option. The following table lists the option keywords along with their associated valid values: Chapter 3. Configuring inventory 21

32 Option SecurityName ContextName AuthPasswd EngineId AccessMode Values Specifies the user name to be used for this SNMP V3 community name. Specifies the context name to be used for this SNMP V3 community name. Specifies the password to be used for authentication (MD5) for this SNMP V3 community name. Specifies the value for the engine ID for this SNMP V3 community name. This option keyword is optional. Specifies the level of security required for this SNMP V3 community name. The following are the valid values for this option: v v No-Auth - Indicates that this SNMP V3 community name is no more secure than the community string provided in SNMP V1 or SNMP V2c. Auth-MD5 - Indicates that this SNMP V3 community name security level corresponds to an unencrypted traffic, authenticated with MD5 hash. Specifying this value means that you must also specify the SecurityName, ContextName, and AuthPasswd options. The following example specifies an SNMP V3 community name that uses an MD5 authentication: &V3,AccessMode=Auth-MD5 SecurityName=user2 ContextName=context2 AuthPasswd= abcdef 2. To modify an existing entry, highlight the entry so that it appears in the Alternative community names box. Modify the entry in the Alternative community names box, then click Modify. 3. To delete an entry, highlight the entry and click Delete. To delete all the entries, click Clear. 4. Click Update SNMP configuration tool with new matching community name to update the community names in the SNMP configuration database with the alternative community name for elements queried. 5. Click Next to proceed. You can specify which types of elements to include in the discovery. The left pane displays all the known element types. The right pane displays the element types currently included in the discovery. Note: By default, all known element types are included in the discovery. Important: Ensure that you have installed Tivoli Netcool Performance Manager Technology Packs; otherwise the Groups folder does not display any element type subfolder. See Installing Tivoli Netcool Performance Manager - Wireline Component and Installing and Configuring Technology Packs - Wireline Component for instructions on installing Tivoli Netcool Performance Manager Technology 22 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

33 Packs. To filter the objects included in the discovery do the following tasks: a. To exclude a specific type of object, drag the object type from the right pane to the left pane. b. To add a specific type of object, click Unselect All, then drag a specific object type from the left pane to the right pane. Important: You can include only those objects that you want to run discovery against and not the entire tree. c. Clear the Insert unknown elements option so that unknown element types are excluded from the inventory. If you select this option, unknown elements are included in the discovery and are added to a folder called NONE. 6. Click Next to proceed. Specifying an ICMP configuration Explains how to specify Internet Control Message Protocol (ICMP) parameters for your inventory profile. 1. Choose a network type from the Network type group. Each network type has different defaults. 2. Specify the ICMP parameters, either by accepting the defaults or by modifying them. The following options are available: Option Message data size Tries Time out Description Data size of the ICMP packet. The entry can be 1-64,000 bytes. Number of times to ping specific IP addresses if no response is received from the ping. Your entry can be Length of time (in seconds) to wait for a response to a ping before sending another ping. The length doubles for each additional ping. For example, if the Timeout value is 5 seconds: v After the first ping, wait 5 seconds. v After the second ping, wait 10 seconds. v After the third ping, wait 20 seconds. Ping interval Length of time (in milliseconds) between pings. Chapter 3. Configuring inventory 23

34 Option Ping Window Configuration Description Allows you to configure a pause when sending pings to avoid congestion on the network. If you do not select this option, pings are sent equally spaced, without pause, as specified by the Ping Interval. v v Window interval: Length of time (in seconds) to pause in sending pings. Your entry can be from 0.1 to 100 seconds. Window size: Number of pings to send before pausing. Your entry can be from 2 to 65,000 pings. It can also be 0, which disables the window. Using 0 is the same as clearing Ping Window Configuration option. 3. Click Next to proceed. Configuring labels for subelements Explains how to configure labels (naming conventions) for subelements in your inventory profile. 1. Choose the type of element name you want to use. The following options are available Option Description Example Subelement file and formulas configuration Do not use element names Use element names Use DNS element names Specifies which discovery file and formulas are used to perform the inventory process. Name of the subelement is used alone. Name of the element is concatenated with the name of the subelement. This option is enabled by default. Full DNS name of the element is concatenated with the name of the subelement. If a DNS name is not found then the IP address is used. /opt/datamart/conf/ inventory_subelements.txt Dlci 10 (Cir 0 b/s) bost_dlci 10 (Cir 0 b/s) bost.forxh001.sample.fr_dlci 10 (Cir 0 b/s) 2. Click Next to proceed. Option Description Example Sub-element file and formulas configuration Do not use element names Specifies which discovery file and formulas are used to perform the inventory process. Name of the sub-element is used alone. /opt/datamart/conf/.inventory_subelements.txt Dlci 10 (Cir 0 b/s) 24 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

35 Use element names Use DNS element names Name of the element is concatenated with the name of the sub-element. This option is enabled by default. Full DNS name of the element is concatenated with the name of the sub-element. If a DNS name is not found then the IP address is used. bost_dlci 10 (Cir 0 b/s) bost.forxh001.sample.fr_dlci 10.(Cir 0 b/s) 3. Click the Next button to proceed. Specifying synchronization Explains how to specify the data source for the synchronization of your inventory profile. 1. In the Select Datasource area, select the source of the data to be synchronized with the results of this discovery from one of the following options: v From database (default) - Tivoli Netcool Performance Manager DataMart synchronizes the results of this discovery with the data currently in the database. v From file - Tivoli Netcool Performance Manager DataMart synchronizes the results of this discovery with the data in the files you specify. Click Browse to specify the path and file name for each of the files. 2. Click Next to proceed. Inserting resources Explains how to add, remove, or update resources in your network inventory that you created or changed since the last network discovery operation. 1. In the Resources table, select the resources you want to add, update, or delete. You can select each type of resource and action separately by clicking the appropriate columns. The following actions are supported: Selection New Update Delete Description Add resources found during the discovery that do not exist in the current data. Update the existing resource data with data found during the discovery. Delete the existing resource data that is not found during the discovery. The grouping files for your profile are created in the $PVMHOME/importexport/ profilename/grouping directory. 2. In the Specify the retry count... area of the window, specify the number of times previously existing resources that are not discovered are retried before they are deleted from the network inventory. 3. In the Specify the age for resources... area of the window, specify how long previously existing resources that are not discovered are retained before they are deleted from the network inventory. Chapter 3. Configuring inventory 25

36 Note: If the creation date or date of the last update for this resource is older than the date specified, the resource is deleted. If the creation date or date of the last update for this resource is more recent than the date specified, the resource is not deleted. 4. Click Next to proceed. Specifying automatic grouping Explains how to group resources together automatically. When you use automatic grouping, a link is created in the database for each resource that is included in a group. About this task Regrouping the resources modifies these links; however, database changes for the resources are not made. Default grouping rules are only provided if you installed Tivoli Netcool Performance Manager Technology Packs. See the Installing Tivoli Netcool Performance Manager - Wireline Component for instructions on installing Tivoli Netcool Performance Manager Technology Packs. You need to create custom grouping rules by using the Rule Editor in Tivoli Netcool Performance Manager DataMart. To specify automatic grouping, follow these steps: 1. In the Resource table, select the resources you want to add, update, or delete. You can select each type of resource and action separately by clicking the appropriate columns. The following actions are supported: Item New Update Delete Description Adds links between resources and groups, which adds the resources to the groups. Updates links between resources and groups. Does not add or delete any links, but only updates existing links. Deletes links between resources and groups, which removes the resources from the groups. The grouping files for your profile are created in the $PVMHOME/importexport/ profilename/grouping directory. 2. Click Next to proceed. Specifying repository group rules Explains how to set rules for groups in your network inventory. About this task The Repository group rules side of the window displays all of the grouping rules that can be applied during the grouping operation. The Rules to be used for this profile side of the window displays the grouping rules selected for the specified profile. By default, Tivoli Netcool Performance Manager DataMart executes all of the grouping rules during the grouping operation. 26 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

37 To specify repository group rules, follow these steps: 1. Under the Repository group rules side of the window, click Unselect All. Tivoli Netcool Performance Manager DataMart removes all of the grouping rules from the Rules to be used for this profile side of the window. 2. To apply selected grouping rules to your inventory profile, drag the grouping rules you want to apply from the Repository group rules side of the window to the Rules to be used for this profile side of the window. Tivoli Netcool Performance Manager DataMart refreshes the window to display the grouping rules you selected. 3. To apply all grouping rules to your inventory profile, under the Repository group rules side of the window, click Select All. Tivoli Netcool Performance Manager DataMart refreshes the window to display all of the grouping rules for the specified profile. 4. Click Next to proceed. Selecting modules Explains how to specify the modules that are run with your inventory profile. Running an inventory profile 1. Select one or all of the following: v Discovery - gathers information about your network as specified in the profile. v Synchronization - synchronizes the new data for this profile with the existing information. v Automatic Grouping - applies default or custom grouping rules for this profile. To apply custom grouping rules, you must create them and set their status to "active." 2. Click Next to proceed. This window displays a summary of the profile that you created. Ensure that the profile contains the correct values. If you want to change any of the values, click Previous to return to the appropriate window. 3. Click Finish to complete your profile. After you configure an inventory profile, you need to run it to perform a discovery. About this task To run an inventory profile, follow these steps: 1. Open the Inventory Tool window. 2. Click the name of the inventory profile to be run to select it. 3. Specify which modules are to be used with the inventory profile by clicking the appropriate check boxes in the Module to run field. The module options include the following: Note: You can select or clear these check boxes to make immediate and permanent changes to the database. For example, you might want to run just a Chapter 3. Configuring inventory 27

38 discovery for a bulk inventory. These options are also available when you create a profile in the Inventory Tool Wizard. v v v Discovery - Gathers information about your network as specified in the profile. Synchronization - Synchronizes the new data for this profile with the existing information. Automatic Grouping - Applies default or custom grouping rules for this profile. To apply custom grouping rules, you must create them and set their status to active. v v Note: If you plan to use custom grouping rules, they must be created before running the profile. subprofile option - Gathers information about listed network resources that are imported from a file. The subprofile option is typically used to run a discovery on a subset of the entire profile. This option can be used with inventory profiles configured. Reload collectors - Reloads the collectors at the same time that the inventory profile is run. Important: The Tivoli Netcool Performance Manager default inventory profile settings are used as examples. You must supply settings that are valid for your network. 4. Select Run profile from the Actions menu. The Live information tab displays messages about the status of the profile. The messages are color coded as follows: v Red - Error messages v Blue - Warning messages v Black - Informational messages Viewing the log file The last line in the Live Information tab provides the path to the TraceInventory.log file, which you can view and print with a text editor. Note: This file can be long depending on the size of your network discovery Reloading collectors Each profile is assigned to a collector. If the resources included in the profile change, you need to reload the collector, which updates the collector with the changes. For optimal performance, you must always reload the collector after you modify a profile. About this task To reload a collector, follow these steps: 1. Select a profile. 2. Select Reload collectors at the bottom of the window, along with the modules you want to run for this profile. 3. Select Run profile from the Actions menu. The profile runs and the collector is reloaded. Or 28 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

39 4. Click Reload collector at the top of the window. The collector is reloaded but profile is not run. Deleting a profile To delete a profile, follow these steps: 1. Open the Inventory Tool. 2. Highlight the profile you want to delete. To delete more than one profile simultaneously, hold down the Ctrl key while selecting the profiles. 3. Select Delete profile from the Edit menu. A confirmation dialog box appears. 4. Click Yes. SNMP bandwidth control and collection smoothing The Bandwidth Control and Collection Smoothing features are used to optimize the performance of SNMP collectors in your environment. Before using Bandwidth Control and Collection Smoothing, you must consider how these features function and how that might impact the operation of your network. Bandwidth control SNMP Bandwidth Control is used to prevent SNMP collectors from consuming excessive bandwidth during periods of heavy network activity. The SNMP bandwidth control feature defines a bandwidth limitation that allows you to maximize the performance of the collectors without requiring an overly cautious approach to collection management. Bandwidth Control is configured by defining an SNMP configuration in Tivoli Netcool Performance Manager DataMart. An SNMP configuration primarily consists of a bandwidth limitation that is imposed on the specified collector for the target IP addresses listed within the definition. Once defined, SNMP configurations are propagated to the collectors during the Tivoli Netcool Performance Manager processing cycle. After the SNMP configurations are loaded, Bandwidth Control monitors outbound traffic originating from the specified target IP addresses. Any collection request destined for these target IP addresses is queried to determine if there is sufficient bandwidth available to allow the collection to take place without exceeding the defined bandwidth limit. If sufficient bandwidth is available, the collection request, along with any similarly grouped requests, is permitted to take place. While permitting grouped collection activity can cause a spike that exceeds the bandwidth limitation for a short time (for example, 5-30 seconds), the bandwidth limitation is enforced based on the average traffic monitored at the collector. Once the bandwidth limit is reached, no collections are permitted to take place on that portion of the network until the bandwidth utilization falls below the defined threshold. If collection activity is suspended on any portion of the network due to excessive bandwidth consumption, Bandwidth Control attempts to begin collection on the next portion of the network. Note: If several SNMP configurations and bandwidth limits apply to a set of IP addresses, the lowest defined limit is used to control collection activity for the collector. For example, if a bandwidth limit of 256 Kbps applies to the IP address range *.*, but another limit of 64 Kbps is defined for *, then collection activity on the collector is suspended if the network bandwidth exceeds 64 Kbps. Chapter 3. Configuring inventory 29

40 Configuring SNMP bandwidth control in DataMart You can configure bandwidth control in DataMart using the SNMP Configuration Tool. Note: You can also configure SNMP Bandwidth Control using the CLI Utility. See the Command Line Interface Reference for instructions on using this CLI. Collection smoothing Collection smoothing is used to prevent spikes in collector activity that occur at the beginning of the polling period. Typically, the collector attempts to execute as many collection requests as it can in the shortest time possible, which leads to a pattern of a brief period of intense activity followed by an extended period of sparse collection activity. When enabled, collection smoothing imposes a bandwidth limit on the collector that is based on monitored network activity. This bandwidth limit is dynamically adjusted and serves to constrain the collector so that collection activity is performed throughout the polling interval. Defining a collection smoothing period directs the collector to distribute collection activity across a percentage of the polling period, which leaves the remaining time available for other network tasks such as discovery activity. Care must be exercised in defining this value as specifying too long of a collection smoothing period might leave insufficient time to recover from unexpected issues and ultimately result in lost collections. Similarly, as collection smoothing essentially delays collector activity, you must consider that any network issues such as unexpected latency, high traffic volume, or heavy processor bandwidth utilization might result in slips in the collection schedule. Note: If you intend on using collection smoothing with bandwidth control, the lowest bandwidth limitation is used to control collection activity for the collector. For example, if the bandwidth control limit is 64 Kbps and the dynamically calculated collection smoothing limit is 100 Kbps, then collection activity on the collector is suspended if network bandwidth exceeds 64 Kbps. To avoid collection loss, ensure that bandwidth collection limits are not lower than the range of bandwidth limits that are expected for collection smoothing activity. Configuring collection smoothing in DataLoad About this task To configure collection smoothing in DataLoad, follow these steps: 1. Log in as root on the server where the Topology Editor is installed. 2. Set and export your DISPLAY variable. 3. Change your working directory to the directory where the Topology Editor is installed. For example: # cd /opt/ibm/proviso/topologyeditor 4. Start the Topology Editor using the following command: #./topologyeditor 5. In the Topology Editor, select Topology > Open existing topology. The Open Topology window is displayed. 6. For the topology source, select From database and click Next. 30 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

41 7. Verify that all of the fields for the database connection have the correct values: v Database hostname - The name of the database host. The default value is localhost. v Port - The port number used for communication with the database. The default value is v Database user - The user name used to access the database. The default value is pv_admin. v Database Password - The password for the database user account. For example, pv. v SID - The SID for the database. The default value is PV. Click Finish. 8. In the Logical View, click the DataChannels folder. 9. Click the Global DataChannel properties component, then click the Advanced Properties tab. 10. Search for the following parameters: SNMP.BANDWIDTHCONTROL.parameter=value Where: Parameter/Value Description Recommended Value AUTOSMOOTHING=false SMOOTHINGSAFETYRATIO=75 The AUTOSMOOTHING parameter enables Collection Smoothing on SNMP collectors. The parameter must be set to true to activate the feature. The SMOOTHINGSAFETYRATIO parameter determines how collection activity is distributed (in percentage of time) throughout the polling interval. The default, and recommended, value of 75 specifies that collection activity occurs over 75% of the polling interval, leaving 25% of the time available for other network tasks, unexpected network problems, and so on. Using too high a setting (for example, 95), might not leave sufficient time for other network events and might result in lost collections. true 75 Chapter 3. Configuring inventory 31

42 Parameter/Value Description Recommended Value SMOOTHINGCHECKFREQUENCY=60 DISCINITIALQUOTA=512 The SMOOTHINGCHECKFREQUENCY parameter determines how often (in seconds) dynamic collection smoothing requirements are recalculated. The default, and recommended, value of 60 specifies that the dynamic collection smoothing requirements are recalculated every 60 seconds. This value is used to achieve the greatest precision in the calculation. If less precision in dynamic bandwidth control values is required or processor usage is too high, adjust the value to a higher setting (for example, 90 seconds). The DISCINITIALQUOTA parameter determines the initial value (in Kbps) for the dynamic bandwidth control limitation (in Kbps) for discovery activity. The default, and recommended, value of 512 specifies that the initial bandwidth limitation for discovery is 512 Kbps. If collections proceed smoothly and there is a high level of discovery activity, the discovery limit is automatically increased. If collections are blocked, the discovery limit is automatically decreased or put on hold until collection activity is improved When you are satisfied with your settings, select Topology > Save topology to save the topology. 12. Select Run > Run Installer and pass it the newly configured topology. 13. After the updated configuration is stored in the database, you must restart the SNMP DataLoad server to initialize the SNMP collectors by issuing the dccmd from a command line. See Command Line Interface Reference for more information. 32 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

43 Understanding file formats Explains the formats required for the discovery files and the synchronization files. The following files are required for a discovery: v element file - contains information about the elements that are imported and then analyzed. v sub-element file - contains information about the subelements that are imported and then analyzed. The following files are required for synchronization: v element file - contains information about the elements that are synchronized with the results of the current discovery. v sub-element file with invariants - contains information about the subelements that are synchronized with the results of the current discovery. It contains only subelements that have invariants. An invariant is a constant; it does not change. v sub-element file without invariants - contains information about the subelements that are synchronized with the results of the current discovery. It contains only subelements that do not have invariants. An invariant is a constant; it does not change. Element file The fields for each element are separated by _. If a field has no value it must be left empty: _ _. An example of the correct format: Note: The width of this page forces this example to wrap onto several lines. The information for each element must be on one line in the file. The fields to be included for each element are listed in the following table: Field Value in Example Smallest IP address of any interface for the element. Resolution of the largest IP address of any intranet.sample.fr interface for the element. sysname for the element. intranet Name of the element. intranet.sample.fr Date of discovery, as the number of seconds since 1 January State of the element. on sysobjectid of the element IP address of the element Community name of the element. public sysdescr of the element. 4BSD/ISODE SNMP Identifier of the collector. 1 Chapter 3. Configuring inventory 33

44 Field Name of the profile. Value in Example example Subelement file The fields for each subelement are separated by _. If a field has no value it must be left empty: _ _. An example of the correct format: Note: The width of this page forces this example to wrap onto several lines. The information for each element must be on one line in the file. The fields to be included for each subelement are listed in the following table: Field Value in Example Invariant of the subelement. If the Interface<1>DLCI<0>CIR<0> subelement does not have an invariant, this field is the instance of the subelement. Name of the subelement. forxh001.sample.fr_interface<1>dlci<0>cir <0> Date of discovery, as the number of seconds since 1 January Instance of the subelement. Interface<1>DLCI<0>CIR<0> Label of the subelement. Dlci 10 (Cir 0 b/s) Name of the element to which the forxh001.sample.fr subelement is attached. State of the subelement. on Name of the family of the subelement. Generic_PVC_FrameRelay The properties of the subelement are after these fields. The properties form a list of the form "name _ value". Name of the property of the subelement. State Value of the property with the name in the active previous field. Name of the property of the subelement. Interface Value of the property with the name in the 1 previous field. Name of the property of the subelement. DLCI Value of the property with the name in the 0 previous field. Name of the property of the subelement. CIR Value of the property with the name in the 0 previous field. 34 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

45 Managing dynamic changes Explains how to ensure that Tivoli Netcool Performance Manager detects dynamic changes, such as index shifting, and updates its state in real time. Doing so prevents unreliable and incorrect information from being stored and minimizes data loss. Tivoli Netcool Performance Manager provides a method to automatically detect and reconcile processing when resource invariants change in near real time. This method, implemented in the CME, includes triggering inventory for the element and updating a running system after information about that element is refreshed. You can enable/disable collection on a subelement using a CME formula. You can also start the Inventory for the element, to which the subelement belongs, when that subelement becomes disabled. You do so by starting a CME formula designed as an invariant check formula. This formula is based on the SNMP-collected invariant for the subelement. When the invariant formula determines that a property is changed (the index for example,) it disables the subelement. The CME then determines to which element the subelement belongs and passes the element to the appropriate Discovery server. This Discover server is co-located with the Inventory process running the element Inventory profile. The Discovery server requests the Inventory to do a full reinventory for the specified element. After the reinventory of the element is complete and the database is updated, the SNMP Collector is reloaded and the subsequent flow of data to the CME corrects itself. From this point on, invariant properties stop triggering reinventory requests. Guidelines You can associate a CME formula with an invariant property to create a formula with two inputs: v SNMP-collected invariant metric v Invariant property The formula needs to compare its two input arguments. About the process The following example illustrates the process by which the invariant management occurs: Chapter 3. Configuring inventory 35

46 v v v v v v v v v v v v As a result of Inventory, the subelement is assigned instance IF<1> and invariant property foo. Inventory stores the Invariant property for the subelement in the database. SNMP Collector is reloaded and starts collecting for the subelement using instance IF<1>. collectedinvariant metric is also foo. InventoryCheck formula compares collectedinventory metric and Inventory property. If they do not match, gate for all other formulas is closed. Reinventory request is sent to the correct Discovery server. Discovery server starts reinventory for the element. Inventory updates subelement and replaces instance with IF<3>. Inventory reloads SNMP Collector. SNMP Collector starts using IF<3> for data collection for the subelement. collectedinventory becomes foo again. InventoryCheck formula succeeds. Gates for all the subelement formulas are open again. 36 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

47 CME formula command template The following template: ^self checkinvariant: (collectedinvariant ~= invariant) old: <anoldvalue> new: <anewvalue> Example based on process illustration The following example includes a formula called InvariantCheck that takes the following two arguments: v v SNMP collectedinvariant metric (for example, value of ifname) Invariant property The Invariant property is set by the inventory and is not changed by the CME. The CME uses this value to check for invariant shift (change) condition. The formula returns a number (0 or 1). If output is 1, the invariant is valid, otherwise it is invalid. The built-in method checkinvariant: has an argument which is either true or false. If the argument is true, the subelement invariant is valid, otherwise it is invalid. When an index shifts, the stored value of the Invariant property for a resource was foo. Until this value is updated in the database, the value of the Invariant argument for the formula for this subelement remains foo. At the same time, the SNMP Collector keeps collecting collectedinvariant metric for this resource and gets foo every time. When the CME processes this string record, the Invariant formula compares its first and second arguments and uses the result of this comparison to call checkinvariant. Until the collected invariant changes, this argument remains true. When an index shift occurs, the SNMP Collector (still using the old index) collects a different value for the invariant (for example, bar.) When this string metric record is processed by the CME, the first argument is now bar and the second (stored invariant) will still be foo. When checkinvariant: is called, the argument is false. A sequence of corrective actions occurs. First, the CME marks this subelement internal state as DISABLED. While disabled, no deployed CME formulas for this subelement are evaluated and the metrics are dropped. The subelement locks out all its formulas. Also, no thresholding activity occurs and metrics are not produced. All delta formulas are reset and their stored values are erased. To turn it back to ENABLED and to unlock the formulas, checkinvariant: with true must be called; which occurs when either the Invariant property is changed in the database to bar, or if the collectedinvariant property becomes foo once more. The CME requests the inventory for this subelement element to be performed immediately (only when the subelement internal state changes from ENABLED to DISABLED.) The CME locates the appropriate Discovery server and requests a reinventory of the element. It also marks the internal status of element as DISABLED. Once reinventory of the element is complete and the database is updated, the SNMP Collector is reloaded. It now uses the correct instance to collect data from the device, and the value of collected invariant metric becomes foo again. When invariantcheck is evaluated, both collectedinvariant and Invariant arguments are foo, so checkinvariant: is started with true. This switches the internal Chapter 3. Configuring inventory 37

48 subelement state to ENABLED, thus unlocking all the subelement formulas. This also switches the internal state of the element to ENABLED. From that point on, if a subelement of this element is disabled, it triggers another reinventory request. Example for 2233_IF family The following example is based on a profile called invtest, a property named ifalias, an SNMP Collection formula ifalias, and a change in the value of the ifalias property. Discovery formula The discovery formula is for the 2233_IF family, standard (Extended MIB-II) interfaces: Dim I1 AS Integer Default * NAME If; V1 = OIDVAL(ifType.%I1 format clean, once); V2 = OIDVAL(sysLocation.0, once); V3 = OIDVAL(ifSpeed.%I1, once); V4 = OIDVAL(int(%V3/ ), once); V5 = OIDVAL(ifName.%I1 format clean, once); V6 = OIDVAL(ifAdminStatus.%I1 format clean, once); V7= OIDVAL(ifAlias.%I1 format clean, once); %V1 index "If<%I1> IF: %I1 (%V5) (%V4Mbps) type<%v1>location<%v2>physicalcapacity<%v3>name <%V5>status<%V6>siteID<IP:%H1ifIndex:%I1>ifAlias<%V7> %V7"; SNMP Formula SNMP formula: Name: ifalias Source: ifalias.%i1 SNMP collection requests: Formula Group Interval in Minutes Storage ifalias Sub-Element Collect~RFC- 2233~Frequent 5 No ifalias Sub-Element Collect~RFC- 2233~Normal 15 No CME Formula Use the CME invariant metric as the CME invariant formula input argument. The formula must be associated with subelement invariant property and return either 0 or 1. The formula code must include the following statement: self checkinvariant: <true or false> The formula uses the current input argument. If the argument is false, the subelement invariant is changed and it must be reinventoried. If the value is true, the subelement is not changed. CME formula for invariant check: Name: invcheck Input bindings: collectedinvariant - String bound to ifalias formula invariantproperty - Property bound to ifalias property Source: ^self 38 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

49 checkinvariant: (collectedinvariant = invariantproperty) old: invariantproperty new: collectedinvariant XML Source: <formula genericid=" "><inputbinding localname="collectedinvariant" metricid=" " type="string"></inputbinding><inputbinding localname="invariantproperty" metricid=" " type="property"></inputbinding><source> ^self checkinvariant: (collectedinvariant = invariantproperty) old: invariantproperty new: collectedinvariant</source></formula> Requests for invariant check: Formula Group Interval in Minutes Storage invcheck invcheck Sub-Element Collect~RFC- 2233~Frequent Sub-Element Collect~RFC- 2233~Normal 5 No 15 No CME processing The results of starting checkinvariant include: v v v Disables subelement if enabled Obtains subelement element Acts according to the following table The following table lists the supported arguments: Argument Value Internal Element State Action false ENABLED Obtain remote reference to associated discovery server Request reinventory of specified element Set element internal state to DISABLED false DISABLED No action true DISABLED Set element internal state to ENABLED true ENABLED No action In addition, the CME uses a timeout to periodically send reinventory requests to the Discovery Server. This allows the Discovery Server to be relatively lax with the requests. If a request was missed for any reason and reinventory did not happen (for example, Discovery Server restarted), the request is repeated a few minutes later. Chapter 3. Configuring inventory 39

50 Discovery server responsibilities When the Discovery server receives reinventory request, it must run inventory processing for that element. The processing occurs as follows: v v v Runs discovery for this address or addresses. Runs synchronization. Returns result to the sender. No persistent state is needed. Logging policy The logging messages perform the following functions: v v Documents the flow or reinventory requests, including origination, any failures and retries, arrival at Discovery server, attempts to start inventory and outcome of every attempt. Change in the element internal state (between ENABLED and DISABLED) are also logged. Target element is listed with each of these messages. Sends a log message for each element reinventory with the following information: Date, time, element name, following ENABLED log message conventions Success or delay/ retry/ failure due to other Inventory lock Identification of the subelement that triggered the reinventory, with the last property and new property Time/date of last reinventory triggered by shift Time and date of Inventory finished Confirmation the subelement was put back in collection with reconciled property Configuring a bulk collector inventory Explains how to configure a bulk collector inventory. Bulk collector inventory profiles run automatically by default using the pollinv command; however, profiles can be edited and default parameters can be changed. About this task Important: IBM does not recommend changing the profile name or file names and locations. To configure a bulk collector inventory, follow these steps: 1. Click Inventory Tool in the Resource tab. Note: The Tivoli Netcool Performance Manager default inventory profile settings are used as examples. You must supply settings that are valid for your network. 2. Select New Profile... from the Edit menu. 3. Click Next to proceed. Discovery of files, synchronization of the database, and automatic (out-of-the-box) grouping is selected by default. 40 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

51 If you want to changes, clear a box. For example, you might want to discover files only and insert new subelement from the bulk files into the Tivoli Netcool Performance Manager database. 4. Click Next to proceed. 5. Click Next to proceed. 6. Click Next to proceed. Modify as needed. For example, you can choose not to delete any elements from the database during the inventory by clearing all the X symbols from the Delete column. 7. Click Next to proceed Modify as needed. For example, you can choose not to update any existing grouping links by clearing all the X symbols from the Update column. 8. Click Next to proceed 9. Click Next to proceed 10. Click Finish. Understanding a bulk collector inventory This section explains the following: v Importing files to a bulk collector v Bulk collector inventory file sets v pollinv and pollprofile commands v Inventory polling and the cron table v Directories and files Importing bulk files When bulk files are imported to the bulk collector, the collector creates resource files that are sent to the $PVMHOME/importExportBulk/bulk_N/Do directory on the DataMart machine, where N indicates the bulk collector number. Once the resource files arrive in the directory, DataMart starts an inventory based on the gathered data and transfers the resource files to the $PVMHOME/importExportBulk/bulk_N/ Done directory when processing is complete. About this task To import files to the Bulk Collector, follow these steps: 1. Log in as pvuser to the server where the DataChannel is installed. 2. Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default), as follows: cd /opt/datachannel/bin 3. Enter the following command to start the Bulk Collector:./dccmd -action start -channel N -application BCOL -collector N For more information about using the dccmd command, see the Command Line Interface Reference. 4. Copy the bulk files to a valid poll directory path. For example: $DCHOME/bcolN/do Chapter 3. Configuring inventory 41

52 where N equals the collector number you specified during Bulk Collector installation, and $DC_HOME is equal to the path where you installed Data Channel. Resource files related to a Bulk Collector profile are stored into the same profile directory on the DataMart machine. The name of the directory is the name of the profile, for example, bulk_65. Discovered resources are assigned to a profile of bulk_n and FTP to a subdirectory of the same name. The pollinv command automatically creates a profile with the same name. Bulk collector inventory file sets For each inventory session, a Bulk collector creates one or multiple resource file sets. Each file set contains a file containing the following files: Note: The files belonging to the same file set have a file name with a common <suffix> string. v element.<suffix>.dat - file containing the elements resources. v subelement.<suffix>.dat - file containing the subelements resources. v args.<suffix>.dat - file containing the special inventory arguments. This file contains a single line (no comments allowed). The content of the line is the options string to append in the inventory command. Where <suffix> equals a timestamp identifier with the format: <YYYYMMDD_H24mmSS>.[FileType] where: v YYYYMMDD is the year, month, and day v H24mmSS is the time (hour, minutes, and seconds) v [FileType] is either: full or delta Inside the bulk_n directory, a bulk collector creates two subdirectories called Do and Done. During transfer staging, a bulk collector first copies the files into the do directory. When the transfer is complete, the files are then moved from the Do directory into the Done directory. The following diagram illustrates the directory structure and data flow: 42 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

53 pollinv and pollprofile commands The inventory polling process uses the pollinv command, which is configured in the machine cron and runs once an hour on the DataMart machine. The pollinv command browses the importexportbulk directory for profiles, and launches the pollprofile command, one per profile. The inventory command then inserts the resources (metadata) from the file set into the Tivoli Netcool Performance Manager database. Each time the pollprofile command is run, it does the following: v Creates the corresponding inventory profile. v Browses all the file sets in the profile directory v Reduces the number of inventory processes to launch by reducing the number of file sets (one inventory command is launched for each file set). To reduce the number of file sets, all file sets that have the same arguments string are merged together. This makes the pollprofile run faster. The files that do not have special arguments files are assumed to have default arguments and are merged together. Log files for the pollinv command are located in $PVMHOME/log/ logfile.pollinventory. Inventory polling and the cron table The Tivoli Netcool Performance Manager DataMart setup program inserts the following line into the DataMart user (for example, pvuser) crontab during setup. 0 ****[-f/opt/datamart/datamart.env ] && [ -x /opt/datamart/bin/pollinv ] &&. /opt/datamart/datamart.env && pollinv -nox where /opt/datamart is the path where Tivoli Netcool Performance Manager DataMart is installed. < 0****> is where you can change the frequency. At every period configured, the system cron launches the pollinv command to implement the inventory polling. The default period string is "0 ****"(this specifies that pollinv is launched every hour). You can change the pollinv period in the cron table: 1. Ensure that you are logged in a pvuser as pollinv is configured in pvuser cron table. 2. Get the current content of the pvuser cron table (except the pollinv line) and save it into a temporary file (for example, tempcronfile): su pvuser -c crontab -l grep pollinv > tempcronfile 3. Edit the file tempcronfile and insert a new line containing the modified pollinv cron command with the suitable period. 4. Replace the current cron table of pvuser by the content of the file $tempcronfile: su pvuser -c " crontab tempcronfile " Chapter 3. Configuring inventory 43

54 Directories and files (location, naming, and format) The DataMart bulk resources directory has the following structure: $PVM_BULK_HOME (for example, this inventory FTP directory is /opt/datamart/ importexportbulk) root directory for the bulk collector file sets, which is created when you install Tivoli Netcool Performance Manager DataMart. It is the location where the Bulk Collector pushes its profile directories (and file sets inside the profile directories). This is also the source profile directory for the pollinv command. It defaults to $PVM_HOME/ importexportbulk. bulk_n all files related to a profile are stored in this directory (where N = the bulk collector number (ID) that you specified during Bulk Collector installation). All subelements created into the database using the current inventory profile are assigned to this collector. Do Done Dm temporary directory used by the Bulk Collector when transferring files to Tivoli Netcool Performance Manager DataMart. When the transfer is complete, the Bulk Collector moves the files from this directory to the done directory. This directory is created by the Bulk Collector. source file sets directory for the inventory polling process (pollprofile command). Each resources file set is composed of two types of files (element and subelement). An optional file containing the inventory command arguments (args) can be appended to the file set. After each successful inventory command is run by the pollprofile command, the associated file set is deleted from this directory. This directory and its file sets are created by the Bulk Collector. source file set directory for the inventory process (launched by the pollprofile command). Each inventory launched using this profile get its source files from this directory, and uses this directory as its working space. This is the case whether the inventory is launched automatically (pollprofile) or manually (by using the Inventory Tool or CLI). After each inventory (manual or automatic), the last file set used is not deleted. Since this directory working directory for the inventory command, it creates its 44 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

55 Bulk file format examples working files and working directories at <profilename>/grouping, <profilename>/ groupingwait, <profilename>/inventory, <profilename>/synchro, profilename>/synchrowait. These directories are created by the pollinv command. Some bulk file format examples: Element resources The following is an example of an element.<suffix>.dat file: # col = eprp.ipaddressmin:value eprp.ipname:value eprp.sysname:value name date state encl.oid eprp.ipaddress:value scf.rcommunity eprp.sysdescr:value collector profile # filter = # type = elt _ _ _ _ _ on _ _ <NULL> _ _ <NULL> _ 2 _ bulk_2 _ Subelement resources The following is an example of a subelement.<suffix>.dat file: # col = invariant elt.name name date instance label state fam.name seprp.name:name seprp.value:name# filter = #type=se LPort<66> _ _ _LPort<66> _ _ LPort<66> _ <NULL> _ on _ Cascade_ATM_LPort _ ifspeed _ _ portindex _ 4 _ slotindex _ 16 _ porttype _ UNI _ privatenetid _ 0 _ ifoperstatus _ 1 _ ifindex _ 66 _ hostipaddr _ _ msrmtperiod _ 900 _ customerid _ 0 _ Inventory arguments The following is an example of an args.<suffix>.dat. This file contains a single line (no comments allowed). The content of the line is the options string to append in the inventory command. Example: -reload 1 -action synchro This means that the inventory reloads the collectors and perform only the synchronization (no discovery or grouping). Chapter 3. Configuring inventory 45

56 46 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

57 Chapter 4. Creating grouping rules Before you begin Creating grouping rules Explains how to create custom grouping rules to group and edit resources on your network to use with your network inventory, data collection, and reporting. Note: You can also import resources from the command line. For more information, see the Command Line Interface Reference. Note: For instructions on creating grouping rules for composite subelements (CSEs), see the Composite Subelement Configuration. Before creating and testing grouping rules, you need to configure a network inventory to add elements and subelements to the database. Grouping acts like a taxonomy. The intent of grouping is to identify objects that have a common set of attribute and property values, and to organize the objects in a common place (by creating a group membership relation) expressing the circumstance of satisfying the criteria for selection. Grouping rules are organized hierarchically. Each level in the hierarchy is intended to represent an incremental refinement in categorization. The first rule in a grouping branch, which we call a root, typically selects a broad range of objects, for example: all active objects (that is, state = on). The next level of refinement in a branch intended to organize technologically would perhaps have rules to discriminate by type of device. For example, router or switch. And the next level might further classify in terms of device capacity, or capability. A grouping rule is evaluated by the conjunction of all rule conditions defined along a branch in the grouping hierarchy. Group membership is granted at the leaf level, the most precise taxonomic location, when the complete condition of a grouping rule (the aggregate of all conditions from root to leaf) is met. The "ruleconf" command-line interface (CLI) command launches the Rule Editor from the command line. About this task For more information, see the IBM Tivoli Netcool Performance Manager: Command Line Interface. To create rules, follow these steps: 1. Click Rule Editor in the Resource tab. The Rule Editor window is displayed. 2. Click the Rule Sub-Element tab to create a rule for a subelement. Copyright IBM Corp. 2012,

58 Note: For instructions on creating grouping rules for composite subelements (CSEs), see the IBM Tivoli Netcool Performance Manager: Composite Subelement Configuration. 3. Expand the tree in the left pane and click the name of a rule to select it. This rule must be at the level of the tree just above where you want to insert the new rule. 4. Right-click and select New. Tivoli Netcool Performance Manager DataMart inserts a new rule with a temporary name. For example, "NEW_GROUP_1." 5. Name the rule by entering up to 50 characters in the Name box. The name can be either static text or a variable. You can drag the properties from the Properties listbox to the Name box. Note: Conditions are not allowed in the Name box. 6. Optional: In the Label text box, assign a label to the group. Labels are used as an alias for group names, providing another level of abstraction. When creating reports, Tivoli Netcool Performance Manager DataView first looks for a label, and if one is not defined it displays the group name. 7. If the rule requires a condition, enter the condition in the Condition box. You can drag properties from the Properties list and operators from the Operator listbox to the Condition box. 8. Click an option in the Status group: Idle The rule remains in the database, but it is not used by the Inventory Tool during autogrouping. The rule appears in red within the tree. This rule (and each rule below it within the tree) is ignored by the Inventory Tool during autogrouping. Active The rule is used by the Inventory Tool during grouping. 9. Click Apply. The temporary name changes to the name of one or more of the properties you selected. Values for Type, Updated On, and Origin are filled automatically by Tivoli Netcool Performance Manager DataMart. Using operators and functions Operator or Function AND Description Joins two conditions. Resources are included in the results if they match both conditions. This operator has the same effect as creating nested conditions. For example: %(Element.PROFIL) = `public AND %(iftype) = `ethernetcsmacd Resources are included in the results if the profile name is public and the iftype is ethernetcsmacd. 48 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

59 OR Joins two conditions. Resources are included in the results if they match either condition. For example: %(Element.PROFIL) = `public OR %(iftype) = `ethernetcsmacd = Resources are included in the results if either the profile name is "public" or the iftype is ethernetcsmacd. Tests if the variable is equal to a value. Use this operator to test against only one value. For example: %(VENDOR) = `Cisco Resources with the vendor "Cisco" are included in the results.!= Use IN to test against a list of values. Use LIKE to test against a value with a wildcard (%). Tests if the variable is not equal to a value. Use this operator to test against only one value. For example: %(VENDOR)!= `Cisco Resources with any vendor except "Cisco" are included in the results. < Use NOT IN to test against a list of values. Use NOT LIKE to test against a value with a wildcard (%). Tests if the variable is less than the value. Use this operator to test against only one value. It does a comparison based on an ASCII sort, if the value is enclosed in double quotation marks. It does a comparison based on a numeric sort, if the value is not enclosed in double quotation marks. For example: %(Element.COLLECTOR) < 3 Resources with a collector number less than "3" are included in the results. Note: Do not use double quotation marks for the collector number. The collector number is an Int column in the database and must use a numeric comparison. It is also possible to use <=. Chapter 4. Creating grouping rules 49

60 > Tests if the variable is greater than the value. Use this operator to test against only one value. It does a comparison based on an ASCII sort, if the value is enclosed in double quotation marks. It does a comparison based on a numeric sort, if the value is not enclosed in double quotation marks. For example: %(Element.COLLECTOR) > 3 Resources with a collector number greater than "3" are included in the results. Note: Do not use double quotation marks for the collector number. The collector number is an Int column in the database and must use a numeric comparison. IS NULL IS NOT NULL LIKE It is also possible to use >=. Tests if the variable is NULL. For example: %(FAMILY) IS NULL Resources with the FAMILY property "NULL" are included in the results. Tests if the variable is not NULL. For example: %(FAMILY) IS NOT NULL Resources with the FAMILY property "not NULL" are included in the results. Tests if the variable is equal to a value containing a wildcard (%). For example: %(ipaddress) LIKE ` % Resources with IP address that begin with are included in the result. NOT LIKE Use IN to test against a list of values. Tests if the variable is equal to a value containing a wildcard (%). For example: %(ipaddress) NOT LIKE ` % Resources with IP address that begin with anything other than are included in the result. Use NOT IN to test against a list of values. 50 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

61 IN Tests if the variable is equal to the value. Use this operator to test against one value, or a list of values. For example: %(iftype) IN (`ppp, slip ) Resources with iftype PPP or SLIP are included in the result. NOT IN Use LIKE to test against a value with a wildcard (%). Tests if the variable is not equal to the value. Use this operator to test against one value, or a list of values. For example: %(iftype) NOT IN (`ppp, slip ) Resources with any iftype other than PPP or SLIP are included in the result. pub.pvm_to_number pub.formatip Use NOT LIKE to test against a value with a wildcard (%). Casts a string to a number. Use this function with operators such as < and > to perform a numeric comparison rather than a string comparison. Place the function before the variable. For example: pub.pvm_to_number(%(ifspeed)) > = Reformats an IP address so that each set of numbers in the address contains three digits. This is necessary to do an accurate comparison. It converts this IP address: to this IP address: For example, this is not correct: %(ipaddress) < ` AND %(ipaddress) > ` It is not correct, because this rule includes both the IP addresses and This is correct: pub.formatip(%(ipaddress)) < ` AND pub.formatip((%(ipaddress)) > ` This rule includes the IP address , but not Chapter 4. Creating grouping rules 51

62 Using conditions You can use any property in the database as a variable in a condition. A condition can test against any value that is valid for the property. To test against multiple values use the OR, IN, and LIKE operators. The syntax for conditions is similar to SQL syntax. A condition has the following format: %(property) operator`value Part of Condition Description Syntax Requirements % Creates a variable from a property. property Specifies the property to be tested. operator Defines the relationship between the variable and the value. No space between % and the property. Parenthesis are required. Spaces before and after the operator are recommended, but not always required. value Specifies the test. v Single Quotation marks are required around each value for a string comparison. v Double quotation marks around the values are not allowed for a numeric comparison. Note: Do not use double quotation marks for the collector number. The collector number is an Int column in the database and must use a numeric comparison. v v v If the condition tests against a list of values, parentheses are required around the list. If the condition tests against a list of values, each value needs to be separated by a comma. Spaces before and after the comma are optional. The value in the condition needs to match the value in the database. Capitalization and punctuation must be the same. You can nest conditions. For example: 52 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

63 Using grouping rules A resource must match all of the conditions to be included in the results. Explains how to use custom grouping rules after you create them. About this task To use grouping rules, follow these steps: Testing grouping rules 1. Ensure that you have performed an inventory of your network or imported resources from the command line. See Managing Resources in the Command Line Interface Reference for information about importing resources. 2. If you want to use properties that are not included with Tivoli Netcool Performance Manager DataMart, create properties and add them to the database. See Managing Resources in the Command Line Interface Reference for more information about adding properties to the database. Note: After you create properties, you must exit the Rule Editor and reopen it for the new properties to appear. 3. Create grouping rules. 4. Run the Autogrouping option in the Inventory Tool Wizard to execute the grouping rules. 5. Use the groups to create collection requests. After you create custom grouping rules, you can test them using database information. About this task To obtain database information configure an inventory to add elements and subelements to the database You can also import resources. See Managing Resources in the Command Line Interface Reference for details. When you test a grouping rule, the results are displayed in a tree structure in the Test Result tab. Grouping rules can contain the following: Static text Provides another level to the tree, but does not sort or filter the results. It lets you create meaningful names for your rules. Variables Used alone, sort the results according to the variable, but do not filter the Chapter 4. Creating grouping rules 53

64 results. If you use a variable to sort according to ifspeeds, all the resources are included in the result and are grouped according to the different ifspeeds of the resources. You can also nest variables. The results of nested variables are sorted according to each variable. Conditions Use variables to filter the results. Only resources that match the condition are included in the result. A condition does not sort the results. All the resources that match the condition are grouped together. If you use a condition to filter according to :ifspeed, only the resources that match the condition are included in the result. Unlike with variables, all the resources that match the condition are grouped together. They are not sorted according to the different ifspeeds. Conditions can also be nested. A nested condition filters the results again. Only resources that match all the conditions are included in the result. Only the result of the lowest level of the tree is used by the Inventory Tool to create groups. To test a grouping rule, follow these steps: 1. Open the Rule Editor. 2. Expand the tree in the left pane to display the rule that you want to test. 3. Select the rule by clicking the name of the rule. To select multiple rules, hold down the Shift key and click the names of the rules you want to select. Note: You must expand the tree to display all the rules you want to select. If the branch of the tree is not expanded, only the rule that is visible is selected. The rules below it in the tree are not selected and are not tested. 4. Right-click and select Test from the menu. The Test Result tab is displayed. 5. Display every resource included in the group by clicking the plus sign or the folder icon to expand the tree. Or Display only the number of resources included in the group by clicking the name of the group to select it, then holding down the Ctrl key and right-click. If a group is not created, check the syntax of the rule. Each property must have a default value. If an element has no value for a property, and there is no default value for the property, then the element is not included in the results for grouping rules that use that property. Saving test results This saves the test results in a file. It does not save the results in the database. To modify the groups in the database, run Automatic Grouping in the Inventory Tool. 1. Test the rule as explained in Testing grouping rules on page Click the Save result in file button. 3. Specify a path and file name. 4. Click Save. 54 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

65 Copying grouping rules 1. Open the Rule Editor. 2. Expand the tree in the left pane to display the rules that you want to copy. 3. Click the name of the rule to select it. To copy several rules, select the highest rule in the tree. 4. Right-click and select Copy from the menu. The rule changes to the color blue. 5. Expand the tree in the left pane to display the rule where you want to paste the rule. 6. Click the name of the rule to select it. 7. Right-click to open the menu. 8. Select Paste on the menu. 9. Expand the tree to display the rules you copied. Moving grouping rules About this task To move grouping rules, follow these steps: 1. Open the Rule Editor. 2. Expand the tree in the left pane to display the rules that you want to move. 3. Click the name of the rule to select it. To move several rules, select the highest rule in the tree. 4. Right-click and select Cut on the menu. The rule changes to the color blue. 5. Expand the tree in the left pane to display the rule where you want to paste the rule. 6. Click the name of the rule to select it. 7. Right-click to open the menu. 8. Select Paste from the menu. 9. Expand the tree to display the rules you moved. Deleting Grouping Rules 1. Open the Rule Editor. 2. Expand the tree in the left pane to display the rule that you want to delete. 3. Click the name of the rule to select it. 4. Right-click. 5. Select Delete from the menu. 6. Click Yes. The selected rule is deleted along with each rule below it in the tree. Chapter 4. Creating grouping rules 55

66 Understanding the file format About this task A file with the test results contains fields for the following: v Path and name for the rule v Identifier for the resource v Database index for the rule Each line of the file represents one resource. The fields are separated by _. For example: Viewing rule database information 1. Open the Rule Editor. 2. Expand the tree in the left pane to display the rule you want. 3. Click the name of the rule to select it. 4. Hold down the Ctrl key and right-click. A pop-up window containing the database information appears. The parameters in the pop-up window are as follows: Parameter Heading dbindex Name type cond Description Path and name for the rule. The path separator is a tilde (~). Database index for the rule. Name of the rule. Type of rule (static or rule). Condition for the rule. This is blank if the rule does not have a condition. 56 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

67 state date origin Indicates whether the rule is used by the Inventory Tool during grouping. v on - indicates that the rule is used. This corresponds to the Status: active in the graphical user interface. v off - indicates that the rule is not be used. This corresponds to the Status: idle in the graphical user interface. Modification date as the number of seconds since 1 January How the rule was created. Viewing properties Grouping rules are based on properties. About this task Properties are any attribute of an element or subelement, such as: v MIB attributes, such as sysdesc or ifspeed. These attributes must first be included in the discovery formulas. v Attributes from Tivoli Netcool Performance Manager DataMart, such as the collector number or the name of the profile. v Attributes created by your company, such as customer name, or location. In grouping rules, these properties become variables. For example, the property ifspeed becomes the variable %(ifspeed).you can use any property in the database as a variable. To view properties, follow these steps: 1. Open the Rule Editor. 2. Click the Rule Element tab if you want to view a description of a property for an element. Or Click the Rule Sub-Element tab if you want to view a description of a property for a subelement. 3. Click the Description tab. 4. Click the name of the property to select it. 5. Hold down the Ctrl key and click the right mouse button. A pop-up window containing a description of the property appears. You can create additional properties. They must be in the database before you can use them in a grouping rule. See Managing Tivoli Netcool Performance Manager Objects in the Command Line Interface Reference for details on adding properties to the database. Chapter 4. Creating grouping rules 57

68 Using syntax for grouping rules Explains the syntax to use when creating rules. See pages Grouping rule example on page 59, Example of nested conditions on page 62, and Example of combining text, a variable, and a condition on page 64 for examples. Using static text Do not use the percent sign (%) in static text. It is reserved for creating variables. You can use operators, which are treated as text. Creating variables You can create variables by using the percent sign (%) with the name of a property. For example: %(COLLECTOR) About this task You can create variables by dragging a property from the Properties listbox and dropping it in the Name box or the Condition box. Note: Parenthesis around the name of the property are recommended, but not required. You can use variables without conditions in the Name box, but not in the Condition box. You can nest variables. The results of nested variables are sorted according to each variable. See Chapter 4, Creating grouping rules, on page 47 for details. Only the result of the lowest level of the tree is used by the Inventory Tool to create groups. See Specifying automatic grouping on page 26 for more information. Using a text editor to create grouping rules You can use a text editor to create grouping rules. Using a text editor lets you create grouping rules quickly because you can export the existing rules from the Rule Editor, edit the file, then import the grouping rules back into the Rule Editor. Exporting grouping rules 1. Open the Rule Editor. 2. Select Export from the File menu. The Export dialog box appears. 3. Specify a path and file name for the export file. 4. Click Save to save the file. 58 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

69 Importing grouping rules Understanding the file format 1. Open the Rule Editor 2. Select Import from the File menu. The Import dialog box appears. 3. Select the file that you want to import. 4. Click Open to import the file. The file format for a grouping rule file is the same for an import file and an export file. You can export the rules from the Rule Editor, edit the file in a text editor, then import the rules back into the Rule Editor. About this task A file of the grouping rules contains parameters for: v Path and name for the rule - the path separator is a tilde (~). A tilde must be the first character for each line. v Condition - the condition in this file has the same syntax as the condition in the graphical user interface. If there is no condition, this is blank ( _ _ ). v Type - either static or rule. v Status - on (meaning it is used by the Inventory Tool during autogrouping) or off (meaning it is not used by the Inventory Tool during autogrouping). Each line of the file represents one rule. The fields are separated by _. For example: Grouping rule example This example illustrates grouping rules containing: v Name with static text v Name with a variable v Nested variable v Condition Chapter 4. Creating grouping rules 59

70 Name with static text To create this name with static text, the entry in the Name box is: "An Example". There is no entry in the Condition box. The test results for static text are based on the previous level of the tree. The results for this example are the ROOT. Name with a variable To create this name with a variable, the entry in the Name box is: "%(Element.COLLECTOR)". There is no entry in the Condition box. The test results are sorted according to the collector, but are not filtered. 60 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

71 Nested variable To create this variable the entry in the Name box is: %(iftype) T here is no entry in the Condition box. The test results are sorted according to a collector, and are then filtered according to interface speed. Those results are then sorted according to interface type. Only the result of this lowest level of the tree is used by the Inventory Tool to create groups. See Specifying automatic grouping on page 26 for more information. Condition To create this condition the entry in the Name box is: High Speed > 100Mbps The entry in the Condition box is: pub.pvm_to_number(%(ifspeed)) >= Because operators are not processed in the Name box, the greater than operator (>) in the name is text. Because operators are processed in the Condition box, the greater than or equal to operator (>=) in the condition filters the results. The function pub.pvm_to_number casts the string to a number to perform a numeric comparison rather than an ASCII comparison. The test results are sorted according to a collector and are then filtered according to interface speed. Resources are only included in the test results if the interface speed is more than 100 Mbps. Resources with a slower interface speed are ignored. Chapter 4. Creating grouping rules 61

72 Example of nested conditions This example illustrates nested conditions. Condition To create this condition the entry in the Name box is: Active state The entry in the Condition box is: %(State) = `active The test results are filtered according to the state of the subelement. Subelements are only included in the test results if they are active. Inactive subelements are ignored. Nested condition To create a nested condition, the entry in the Name box is: Speed The entry in the Condition box is: pub.pvm_to_number(%(ifspeed)) <= The function pub.pvm_to_number casts the string to a number to perform a numeric comparison rather than an ASCII comparison. 62 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

73 The test results are filtered according to the state, and are then filtered according to interface speed. Resources are only included in the test results if they are active, and the interface speed is less than 100 Mbps. Inactive resources are ignored. Resources with faster interface speeds are ignored. Second nested condition To create this condition, the entry in the Name box is: Type The entry in the Condition box is: %(iftype) IN (`ppp, frame-relay ) The test results are filtered according to the state, then filtered according to interface speed, and then filtered according to interface type. Resources are only included in the test results if they are active, and the interface speed is less than 100 Mbps, and the interface is either PPP or Frame Relay. Inactive resources are ignored. Resources with faster interface speeds are ignored. Resources with other types of interfaces are ignored. The results include resources that are either PPP or Frame Relay. The results do not specify the interface for each resource. Variable To create this variable, the entry in the Name box is: %(iftype) There is no entry in the Condition box. The test results are filtered according to the state, then filtered according to interface speed, then filtered according to interface type, and finally sorted according to interface type. The list of resources is the same as before, but are sorted according to interface type. Chapter 4. Creating grouping rules 63

74 Only the result of this lowest level of the tree is used by the Inventory Tool to create groups. Example of combining text, a variable, and a condition This example illustrates using text, a name with a variable, and a condition. To create this rule, the entry in the Name box is: Ethernet for Collector no.: %(Element.COLLECTOR) The entry in the Condition box is: %(iftype) = `ethernet-csmacd The test results are sorted according to the collector, then filtered according to interface type. The text is included in the display of the results. 64 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

75 Chapter 5. Collection and aggregation Before you begin Explains how to collect and store network performance and service analysis data for monitoring subelements on your network using SNMP, Bulk, and Complex Metric formulas. It also explains how to configure aggregation requests and percentile information for presentation in reports. After collection, and possibly aggregation, this data can be integrated into Tivoli Netcool Performance Manager DataView or the reporting tool of your choice. Before you request data collection, you need to: v Configure an inventory of elements and subelements in your network. v Group the elements and subelements automatically or manually. Configuring data collection requests Explains how to configure data collection requests for the subelements in your network. Results of the data collection are stored in the Tivoli Netcool Performance Manager database for use in reporting. About this task In addition to the Request Editor, you use the following Tivoli Netcool Performance Manager DataLoad modules to configure data collection: v Formula Selector to select a formula for collecting data. v Resource Editor to select resources, such as subelements and subelement groups. 1. Click Request Editor in the Configuration tab. 2. Click the + sign next to Sub-Element Collect in the Sub-Element Groups pane to expand it and display the collection groups. These groups do not have timezones attached to them. 3. Go to the collection group you want by expanding the top-level folders to locate the group. 4. Click the + sign next to AP in the Formulas pane to expand it and display the formula groups. 5. Go to the formulas you want to apply to the data collection, 6. Click New. The newly created requests appear in the list. 7. You can click Cancel to undo the requests created or click Save to save your requests. If you want to create additional requests, repeat steps 3 through 7 before clicking Save. Copyright IBM Corp. 2012,

76 Setting the collection period You can set the time you want data collection to run in the Details area of the Collection tab. 1. Select an existing request or create a new one. The selected request is highlighted in blue. 2. Enter a value in the Hours text box and press Enter or use the up and down arrows to increase or decrease the value. 3. Enter a value in the Minutes text box and press Enter or use the up and down arrows to increase or decrease the value. 4. Click Cancel to undo the changes you made to the data collection period or click Save to save your edits. If you want to create additional requests, repeat steps 1 through 3 before clicking Save. Configuring aggregation requests Explains how to configure aggregation requests and percentile values. 1. From the Request Editor, click the Aggregation tab. 2. Click the + sign next to NOC Reporting to expand it and display a list of report groups for aggregation. These groups have Calendars and timezones associated with them. 3. Go to the report group you want by expanding the top-level folders to locate the group. 4. Click the + sign next to AP in the Formulas pane to expand it and display the formula groups. 5. Go to the formulas you want to apply to the data collection. Aggregation is usually against generic formulas. 6. Select the formulas pressing Ctrl or Shift while clicking to select non-contiguous or a continuous block or formulas. 7. Click New. The newly created requests appear in the list. 8. Click Cancel to undo the requests created or click Save to save your requests. If you want to create additional requests, repeat steps 3 through 7 before clicking Save. Configuring a percentile value You can use a percentile value instead of the average or max statistics to better represent a metric that includes the occasional burst or spike. Occasional bursts or spikes render a min or max value meaningless, and throw off average and mean calculations. In these cases, using a percentile calculation allows you to see more accurately how the metric is performing over time. Percentile values are applied to raw data. 1. Select the requests to which you want to apply the percentile. 2. Enter the percentile value in the Percentile text box and press Enter or use the up and down arrows to increase and decrease the value. The percentile value you enter appears in the Percentile column in the request table. 66 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

77 Filtering requests 3. Click Cancel to undo the requests created or click Save to save your requests. If you want to create additional requests, repeat steps 3 through 7 before clicking Save. Explains how to filter the requests displayed in both the Collection and Aggregation tabs. The Request Editor displays a filtering toolbar that's the same on both tabs. The filter expressions are applied to the requests displayed in the table. The column heads effected by the expressions change to reflect the filter applied. Sorting columns You can click column headings to sort the contents. A single click to a column head changes the order which the line items in the request table are displayed. A second click reverses the order. Validating the requests Explains how to validate all the Collection and Aggregation requests. Click Save after creating or modifying a request to make the system validate all requests, even those populated by other tools. Chapter 5. Collection and aggregation 67

78 68 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

79 Chapter 6. Configuring calendars Explains how to configure calendars by using the Calendar Configuration Tool. You use this tool exclusively for SNMP collector data requests to restrict the SNMP collection time period. IBM recommends that you collect data on a 24 x 7 basis, which is the default collection period in the Request Editor. You use a calendar to define periods for SNMP data collection. For example, you can stop SNMP data collection times for a customer site that is closed for business and the network is not being used (no data collection before 8:00 a.m. or after 8 p.m.). This is known as planned outage for Service Level Agreement purposes. The Service Provider has no obligation to the customer during a planned outage. Using the Calendar Configuration Tool About this task The Calendar Configuration Tool provides calendars to use with Tivoli Netcool Performance Manager DataMart data collection requests. Note: The calsel command-line interface (CLI) command launches the Calendar Selector from the command line. The calconf CLI command launches the Calendar Selector from the command line. For more information, see the Command Line Interface Reference. To start the Calendar Configuration Tool, follow these steps: 1. Click Calendar Configuration in the Configuration tab. The Calendar Configuration Tool dialog box appears 2. TheCalendar Configuration Tool lets you create your own calendar from scratch. Creating customized calendars Explains how to create customized calendars for scheduling data collection. About this task When creating a custom calendar for an SNMP data collection request, be aware that if you apply to a CME formula data collection request using Resource Manager, it has the opposite affect. For example, if you create a calendar for a planned outage that collects data from 8 a.m. to 8 p.m. on Tuesday, if applied to the CME, it doesl not collect data from 8 a.m. to 8 p.m. on Tuesday. The CME expresses outages in this way. Copyright IBM Corp. 2012,

80 IBM recommends that you use the CME Permanent calendar for all Bulk file/cme formula data requests. The CME Permanent calendar is a 24 x 7 calendar that collects data every hour on a daily basis from 0:00 to 23:59 (12:00 a.m. to 11:59 p.m.) To create a custom calendar, follow these steps: 1. Select Add item from the Action menu. 2. Select one of the following options from the menu: v Once item - to configure a one-time schedule. v Daily item - to configure daily schedules. v Weekly item - to configure weekly schedules. v Monthly item - to configure monthly schedules. These options are explained in the next sections. Tivoli Netcool Performance Manager DataMart supports Greenwich Mean Time (GMT). When creating a calendar using GMT timezones, use this table as a guide. Value Location -12 Eniwetok, Kwajalein -11 Midway Island, Samao -10 Hawaii -9 Alaska -8 Pacific Time (U.S. and Canada); Tijuana -7 Mountain Time (U.S. and Canada) -6 Central Time (U.S. and Canada) -5 Eastern Time (U.S. and Canada) -4 Atlantic Time (U.S. and Canada) -3 Buenos Aires, Georgetown, Brasilia -2 Mid-Atlantic -1 Azores, Cape Verde +1 Amsterdam, Copenhagen, Madrid, Paris, Belgrade, Brussels, Berlin, Rome, Stockholm, Vienna, and so on. +2 Athens, Istanbul, Cairo, Israel, and so on. +3 Baghdad, Kuwait, Moscow, St. Petersburg, Nairobi, Tehran, and so on. +4 Abu Dhabi, Muscat, Baku, and Tbilisi +5 Ekaterinburg, Islamabad, Karachi, Tashkent +6 Almaty, Dhaka, Colombo +7 Bangkok, Hanoi, Jakarta +8 Beijing, Chongging, Hong Kong, Urumqi, Perth, Singapore, Taipei +9 Osaka, Sapporo, Tokyo, Seoul, Yakutsk +10 Brisbane, Canberra, Melbourne, Sydney, Guam, Port Moresby, Hobart, Vladivostok 70 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

81 +11 Magadan, Solomon Island, New Caledonia +12 Auckland, Wellington, Fiji, Kamchatka, Marshall Island Creating a one-time calendar Explains how to configure a calendar to run once within your local time zone. For example, you might want to schedule a planned outage to occur once only. About this task To configure a one-time calendar within your time zone, follow these steps: 1. Select Once item. The Add Once Item dialog box appears. 2. From the Date selector group, specify times for data collection in the From and To options in the Date selector group. Hours are in military time. For example, 06:00 to 17:00 schedules data collection from 6 a.m. to 5 p.m. 3. Click a date list to specify dates for the collection (day-month-year format). A calendar pop-up window appears. 4. Double-click a specific day. Note: The time and date are based on the date and time properties of your computer. 5. Click OK to accept your selections and close the Add Once Item dialog box. 6. Select Save from the File menu to save your calendar configuration. 7. Enter a unique name for your calendar in the Name box. You can also override the name of a pre-set calendar if you modified that calendar type. Creating a daily calendar You can schedule daily data collection. 1. Select Add item from the Action menu. 2. Select Daily item. The Add Daily Item dialog box appears. 3. Select one of the following options from the Daily item group: v All days - lets you schedule data collection for each day of the week. v Working days (Monday - Friday) - lets you schedule data collection from Monday through Friday. Excludes weekends. v Weekend days (Saturday - Sunday) - lets you schedule data collection for Saturday and Sunday. Excludes week days. 4. Click 24h a day to clear if you want to specify times in the From and To spin boxes. Hours are in military time. For example, 06:00 to 17:00 schedules data collection from 6 a.m. to 5 p.m. 5. Click OK to accept your selections. Chapter 6. Configuring calendars 71

82 Creating a weekly calendar Explains how to create a weekly calendar to use for SNMP and bulk file data collection. A calendar for a data request that uses a bulk file works inversely from a calendar for an SNMP data request. About this task To schedule weekly data collection, follow these steps: 1. Select Add item from the Action menu. 2. Select Weekly item, the Add Weekly Item dialog box appears. The default setting collects data every day of the week from 00:00 to 23:59 (12:00 a.m. to 11:59 p.m.) 3. From the Days selector group, select which days you want to collect data (on a weekly basis). For example, you can select Monday, Tuesday, and Thursday, and exclude Wednesday and Friday. 4. Specify a time range in the lists by clicking the 24h a day button. Clicking this button disables the default setting, which is to collect data every hour (12:00 a.m. to 11:59 a.m.) For example, you can choose to collect data from 8:00 a.m. to 8 p.m. (08:00 to 20:00). Or v Select the starting day from the Range day selector to select a range of days. For example, Monday to Friday. v Specify a time range in the lists. For example, from 8:00 a.m. to 8 p.m. (08:00 to 20:00). 5. Click OK to accept your selections. If you apply this calendar to an SNMP data collection request, it collects data every hour on Monday, Wednesday, and Friday (includes - ON). If you apply it to a bulk file/cme formula data collection request, it collects data on Tuesday, Thursday, Saturday, and Sunday. It does NOT collect data on Monday, Wednesday, and Friday (excludes - OFF). Creating a monthly calendar You can schedule monthly data collection. About this task To schedule monthly data collection, follow these steps: 1. Select Add item from the Action menu. 2. Select Monthly item. The Add Monthly Item dialog box appears. 3. From the Day range selector group, select the time and day of the month in which you want to start data collection, and the time and day of the month in which you want to end data collection. For example, from the first day of the month at 8:00 a.m. to the 15th day of the month at 8 p.m. Or 4. From the Week range selector, select the time in the From list. 5. Select the first, 2nd, 3rd, 4th or last week from the next list. 6. Select a day from the next list. 72 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

83 Deleting a calendar 7. Click OK to accept your selections. Using the Calendar Selector 1. Ensure the calendar is not being used for any data collection requests. 2. Select Load from the File menu to access available calendars. 3. Click Delete from the File menu. The calendar is deleted. You can load a calendar that already exists in the database from the Calendar Selector. About this task To select a calendar, follow these steps: 1. Click Calendar Selector > File > Selector The Calendar Selector window appears. 2. Select one or more calendars to use in the Request Editor. 3. Click Close to exit the Calendar Selector window. Chapter 6. Configuring calendars 73

84 74 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

85 Chapter 7. Writing custom formulas Before you begin What is a formula? Explains how to create and modify custom formulas. You use the following Tivoli Netcool Performance Manager DataMart modules to create or modify formulas: v Formula Selector to select a formula for editing. v Formula Editor to edit and test formulas. v MIB Browser to display a compiled MIB. v MIB Compiler (optional) to add a new MIB. Ensure the collector is running. A formula (sometimes called a metric) is a script, written in a proprietary language developed by IBM Corporation. A formula is a collection of object identifiers (OIDs,) functions, and standard mathematical operations applied to a subelement to perform a computation. A formula lets you customize the information gathered by Tivoli Netcool Performance Manager DataMart. There are two types of formulas: v Discovery formulas are used by the Inventory Tool during the process of discovering and analyzing the network. Discovery formulas are used against hosts only (not against subelements) and are designed to return a list of results. Discovery formulas collect information using OIDVAL()functions and store the values into Vxx vectors. The last lines in the Discovery formula are the ones that send results to the Inventory. Discovery formulas for most interfaces are already included with Tivoli Netcool Performance Manager DataMart. You can write a new discovery formula to include a device that is new to the market. v Collection formulas are used by the Request Editor to collect information about the status of various devices in the network. Collection formulas are applied against a subelement to produce a result (string or numeric) that is saved in the database. There are numerous collection formulas included with Tivoli Netcool Performance Manager DataMart; however, you can write additional formulas for a customized collection process. Copyright IBM Corp. 2012,

86 Merging discovery results You can create Discovery formulas that merge results to create a unique subelement. Instead of creating one large Discovery formula, you can create multiple smaller Discovery formulas that can run sequentially with the results being merged if a common key (formed by the pair of element name and subelement instance field) is detected. Creating formulas About this task The process of creating multiple Discovery formulas that can be used for the merge process includes creating one base formula and multiple expansion formulas to use with the base. v v base formula: the main formula that discovers the subelement along with basic properties expansion formula: additional formulas that define and populate additional properties for the subelement The merge process applies to the following three fields: v SubElement Label v Properties v Invariant The merge occurs between the version of a subelement produced by a Discovery formula (the base formula) and already stored in memory and the more current version of that subelement returned by a subsequent Discovery formula (expansion formula.). You add the merge capability to Discovery formulas by including one of the following characters as the initial character in the SubElement Label, Property, and Invariant fields. v v v * (asterisk) value of current version of the subelement always overwrites previous value + (plus sign) value of the current version of the subelement overwrites previous value if the previous value was empty or missing - value of the current version of the subelement overwrites the previous value if it is missing. Note: Do not use any of these characters as the initial character when naming a SubElement label, Property, or Invariant. The character is removed by the Discovery server before the production of the file for the Inventory process. You can create custom formulas to use for discovery and data collection in addition to the formula library included with Tivoli Netcool Performance Manager DataMart. For example, if you want to know the number of IP packets discarded on a host from MIB-II, you would use this formula: ipindiscards.0 + ipoutdiscards.0 76 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

87 where ipindiscards.0 is the number of incoming discarded IP packets and ipoutdiscards.0 is the number of outgoing discarded IP packets. A valid formula needs to have a MIB that is compiled in Tivoli Netcool Performance Manager DataMart. Without a valid MIB, the formula returns an error message to the request. Editing the inventory_subelement.txt file When you create a Discovery formula, you need to edit the Inventory_sublement.txt file to include the formula so it can be used by the Inventory tool. The Inventory_sublement.txt file lists the rules that Discovery uses and you need to create rules for any Discovery formulas you create. About this task To create a formula, follow these steps: 1. Click the Metric > Formula Editor. The Formula Editor window appears. 2. Select the following formula type from the Options menu: v SNMP (Simple Network Management Protocol) - a network management protocol that is used to monitor routers and attached networks. SNMP is an application layer protocol. Information about devices managed is defined and stored in the application's Management Information Base (MIB). Operates on several OIDs. 3. Click a function button in the calculator. Your choices are as follows: Function ABS MOD LN LOG Description Takes the absolute value of an expression or an object. Takes the modulus of an expression (remainder from the full division) or of an object. This function is typically used with the INT function. Takes the Naperian logarithm of an expression or an object. Takes the decimal logarithm of an expression or an object. e* Takes the exponential of an expression or an object. 10* Takes 10 to the power of an expression or an object. INT LAST (delta) Converts the value of an expression or an object into an integer value. Displays the previous measurement value. Displays the difference between the last measurement and the previous one (x - last(x)). Results are always positive. This function is used for data whose value increases after reaching a maximum peak. This function is typically used for "counter" type MIB data. Chapter 7. Writing custom formulas 77

88 Function DIFF Ô C Description Displays the difference between the last measurement and the previous one (x - last (x)). Results can be negative. This function is typically run on gauge type objects. Deletes the last operation. Clears the Data of Formula box. ( Open parenthesis. ) Closed parenthesis. 4. Alternatively, you can drag a function from the Functions listbox into the Data of Formula box to create a formula. Many of these functions are also available as buttons in the calculator. Or 5. Select a data type from the Type listbox. Your choices are: v float - a numerical value (floating point). v string - a character string. Enter a comment in the Comment box. The maximum character length is Select File > Save to save your formula in the database. Testing formulas You can test a formula after you create it. This step is important to ensure that the formula is valid. About this task Note: The Resource field accepts both IPv4 and IPv6 IP address formats. To test a formula, follow these steps: 1. Ensure that the default collector is started. 2. Click the Test tab. 3. Specify an element, subelements, or group of subelements for which to test the formula from the Target listbox. You must specify an appropriate target to test against. For example, an Ethernet formula requires a target with an ethernet interface. A token ring formula requires a target with a token ring interface. 4. Click the refresh button to update this listbox with available resources. 5. Specify an instance from the Instance box. For example, a single instance such as 1, or multiple instances such as 1,3, ,7.*,8.1.*,9-10. You can override the default instances specified in the formula by using the Instance field. For example, if the formula specifies all instances: Dim I1 AS Integer Default * NAME Interface You can use the Instance field to specify only instances 2 through 5: Interface<2-5> 78 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

89 If you do not specify any instances, Tivoli Netcool Performance Manager DataMart uses the default instances specified in the formula, and inserts them into the Instance field when testing the formula. 6. Enter a community name in the Community box. 7. Optional: You can select an SNMP Collector for the formula test from the SNMP Collector listbox. When you selected resources in step 3, the associated collector appears by default. 8. Click Test to test the validity of the formula. The selected target and community name are also tested. In a few moments, the results are displayed in the Trace box. If the test passed, the formula is correct and the element or subelement is active. The numerical results of the test are displayed. If the test failed, an error message is displayed. For example, the message might tell you that no data was found. 9. Right-click the Trace > Reset to clear the Trace box or select Save to print the results or save them to a file. Saving formulas When you save a formula, Tivoli Netcool Performance Manager DataMart searches all the MIBs that have been compiled. It creates a link from the formula to the compiled MIB containing the MIB objects used in the formula. If a MIB object occurs in only one compiled MIB, the link is created automatically. However, if the MIB object occurs in more than one compiled MIB, you must specify which MIB should be used. Tivoli Netcool Performance Manager DataMart automatically displays a list of MIBs in the MIB Selection window. Click on the desired MIB, then click OK. You can view the details of any of the MIBs by using the MIB Browser. For more information about the MIB Browser, see. When you save a discovery formula, you must save it under the "Alias Instance and Label Inventory" branch of the formula tree. Before the formula can be used automatically by the Inventory Tool, the path to the formula must be specified in theinventory_subelements.txt file. This file can only recognize a location within the "Alias Instance and Label Inventory" branch of the formula tree. Modifying a custom formula You can modify an existing formula by using the Formula Selector. 1. Select File > Load. The Formula Selector dialog box appears. 2. Expand the branches and select the formula you want to modify and click OK. Or 3. Drag a formula into the Data of Formula box. The contents of the formula are inserted rather than the name of the formula. 4. Modify as necessary. 5. If prompted when you save the formula, restart the collector. Chapter 7. Writing custom formulas 79

90 Standard rules for writing formulas Describes the standard rules you need to follow when writing formulas. Every line of a formula must end with a semi-colon(;). Each line of a formula must be on one line. Long lines cannot wrap. The lines of a formula are processed sequentially. There are no statements such as loops, switches, or cases. Dim declaration The Dim declaration defines the format of an input variable. If the formula requires more than one input variable, there must be a separate Dim declaration for each input variable. The syntax is: Dim <Var> As <Type> [Default <val>] [Name <label>]; Part of Formula Purpose Syntax Requirements Dim A keyword to indicate that an input variable is being declared. Not case-sensitive. Var As Type Default The input variable. A keyword to indicate that the data type of the input variable is being declared. The data type of the input variable. A keyword to indicate that default instances are being declared. Must be of the form "I1", "I" must be capitalized, and must be followed by a number. Not case-sensitive. Not case-sensitive. Optional, not case-sensitive. If both the Default and Name parameters are used, the Default parameter must come before the Name parameter. Part of Formula Purpose Syntax Requirements val The instances to use if no other instances are specified. Default instances can be a list of values -or- Name label A keyword to indicate that a name for the input variable is being declared. The name to use for this input variable in the instance field of the Formula Editor. * to indicate that all instances must be used. Optional, not case-sensitive. If both the Default and Name parameters are used, the Default parameter must come before the Name parameter. Can contain only letters and numbers; spaces are not allowed. 80 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

91 Part of Formula Purpose Syntax Requirements ; Indicates the end of the line. Required for every line of the formula, including comments. Every formula must begin with a Dim declaration. This allows the formula be used with subelements. A correct example: Dim I1 As Integer Default *; ifinoctets.%i1; An obsolete example: ifinoctets.*; Although the second example works in most cases, IBM Corporation recommends that you use the first method. There is only one type of formula that does not require a Dim declaration. If the formula is applied to a scalar object (which therefore has only one instance), the Dim declaration can be omitted. In this case, the instance is specified as "0". For example: sysname.0 OIDVAL expression line The OIDVAL expression line executes an expression based on OIDs or statistics variables and stores the results to temporary variables. The syntax is: Vn = OIDVAL(<Expression> [, Validity]); The OIDVAL expression evaluates the expression by retrieving a list of all the OIDs required for the execution of the <Expression>. It retrieves the list by replacing all variables contained in the <Expression> with their substitution values. All substitutions must be resolved in order for the <Expression> to be obtained. Depending on the validity settings, the different OIDs and stats variables are either restored from preceding executions or are queried from target devices. The following table lists the syntax requirements: Part of Formula Purpose Syntax Requirements Vn A temporary variable. Must be of the form "V1", "V" must be capitalized, and must be followed by a number. = Indicates that the result of the expression on the right must be assigned to the temporary variable on the left. Spaces before and after are optional. Chapter 7. Writing custom formulas 81

92 Part of Formula Purpose Syntax Requirements OIDVAL A keyword that indicates that the value of an expression is being assigned to a temporary variable. Not case-sensitive. Expression The expression; the calculation to be done. Contains at least one OID (MIB object with a fixed instance or MIB object with a variable instance) stat variable, or mathematical operation. The expression can be simple or complex, and can include more than one OID. The expression must be enclosed in parentheses. Part of Formula Purpose Syntax Requirements Validity Specifies how often to re-evaluate the expression. The choices include: v Once: evaluate the expression only at the first polling. v v Every, evaluate the expression at each polling. This is the default. xxp, evaluate the expression at a specified number of pollings. For example, 10P means re-evaluate the expression on each 10th polling. v ssss: a specific period, in seconds. For example, 3600 means re-evaluate the expression once each hour. ; Indicates the end of the line. Required for every line of the formula, including comments. Example Dim I1 as integer default * V1=OIDVAL (ifinoctets.%i1 / ifspeed.%i1 * 100.0, every) ; When executed with instance string = 2 and the list of required OID includes: ifinoctets.%i1 ; ifspeed.%i1 ; with I1 in { 2} forces the execution of SNMPGet : ifinoctets.2 ; ifspeed.2 Results from SNMPGet include: ifinoctets [I1 = (int) 2] Æ (int) 1000 ifspeed [I1 = (int) 2] Æ (int) IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

93 This produces the following result: result [I1 = (int) 2] Æ (int) OIDINST instruction Stored in V1 for future use. The OIDINST expression line stores the values of a key for which the expression is true (different from zero.) The instruction is primarily used for Discovery formulas to filter a subset of indexes from a large set, based on properties. If the filter is unsuccessful, the row is skipped. If the filter is successful, the value of the index for the row is assigned to the temporary variable, and processing continues with the next line of the formula. The syntax is: Vn = OIDINST(<Boolean Expression> [, Validity]); Part of Formula Purpose Syntax Requirements Vn A temporary variable. Must be of the form "V1", "V" must be capitalized, and must be followed by a number. = Spaces before and after are Indicates that the result of the expression on the right must be assigned to the temporary variable on the left. optional. OIDINST Expression A keyword to indicate that a conditional filter is being used. The expression to be filtered. Not case-sensitive. OID, stat variable, or mathematical operations with a Boolean result. Valid operators for filtering are: like, <, >, <=, >=, ==,!= Part of Formula Purpose Syntax Requirements Chapter 7. Writing custom formulas 83

94 Validity specifies how often to re-evaluate the expression ; Indicates the end of the line. The choices include: v Once, evaluate the expression only at the first polling. v Every, evaluate the expression at each polling. This is the default. v P, evaluate the expression at a specified number of pollings. For example, 10P means re-evaluate the expression on each10th polling. v A specific period, in seconds. For example, 3600 means re-evaluate the expression once each hour. Required for every line of the formula, including comments. Example V1=OIDINST (ifstatus.%1 like `up ) Based on substitutions of I1 and SNMP query, the SNMP stack returns the following: ifstatus [I1 = (int) 1] Æ (string) "up" [I1 = (int) 2] Æ (string) "down" [I1 = (int) 3] Æ (string) "up" The Boolean expression that compares the result of ifstatus to up produces following result: result [I1 = (int) 1] Æ (int) 1 [I1 = (int) 2] Æ (int) 0 [I1 = (int) 3] Æ (int) 1 OIDINST stores all keys of a result that point to a result different from 0 in the V1 vector, in the value field. Two keys (I1=1, and I1=3) are selected. V1 is constructed with no dimension and multiple values. V1 [] Æ { (int) 1 ; (int) 3 } Such a V1 variable can be used in another expression line, exactly in the same way as an Ix variable, because it has no dimension and that supports multiple possible substitutions. 84 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

95 This OIDINST operator only works when the index is composed of only one dimension. If the index comprises more than one dimension, all substitutions values are concatenated and separated by character dot. Types of each dimension are lost and the resulting type of V1 variables is string (this is default type, when no explicit type is declared). Not using explicit types has more side effects than benefits. Do not use this OIDINST operator when there is more than one dimension. The following illustrates a dlci status example: V1=OIDINST( dlcistatus.%i1.%i2 like "up" ) V1 [] Æ { (int) 1 ; (int) 3 } Such a V1 variable can be used in another expression line, exactly in the same way as an Ix variable, because it has no dimension and that supports multiple possible substitutions. This OIDINST operator only works when the index is composed of only one dimension. If the index comprises more than one dimension, all substitutions values are concatenated and separated by character dot. Types of each dimension are lost and the resulting type of V1 variables is string (this is default type, when no explicit type is declared). Not using explicit types has more side effects than benefits. Do not use this OIDINST operator when there is more than one dimension. The following illustrates a dlci status example: V1=OIDINST( dlcistatus.%i1.%i2 like "up" ) dlcistatus [I1 = (int) 1]; [I2 = (int) 101] [I1 = (int) 1]; [I2 = (int) 102] [I1 = (int) 2]; [I2 = (int) 103] Æ Æ Æ (string) "up" (string) "down" (string) "up" Two keys ( I1=1,I2=101 and I1=2,I2=103 ) are selected because more than one dimension involved, keys are transformed to and and V1 is set to: V1 [] Æ { (string) "1.101" ; (string) "2.103" } Types of variables On the next substitution using V1 values, the <interface>.<dlci> information is lost. Formulas can include the following three classes of variables: v instance v temporary v host In most cases, these variables are actually vectors. Chapter 7. Writing custom formulas 85

96 Instance variables Instance variables represent the input values for a formula. They are declared as a capital I, followed by a number (single digit) between 1 and 9. For example: I1, I2, I3, and so on. You can use the following two methods to set values for the instance variables: v Setting values in the Instance field of the Formula Editor v Assigning a subelement to a request using the Request Editor The instance field is an ASCII string, which must be constructed as the following sequence: [name]<values> The name is only used as a comment, for clarification of the formula syntax, expectations of the values. Values are exact strings that will be used for replacement of To use the value of the instance variable in a formula, add %: %I1, %I2, %I3, and so on. Only values whose responses do not return errors are retained for interpreting the remaining lines of the formula. The valid types for an instance variable correspond to SNMP types. They are: v Integer v IP address v Gauge v Counter v MacAddress v OctetString v DisplayString v Timeticks These names are not case-sensitive when used in a formula. Default instances can include a list of values or * to indicate that all instances must be used. Spaces are not allowed within a list of values for an instance variable. These are valid: v integer, for example: 3 v list of integers, for example: 1,3,6,9,8,109 v interval, for example: 4-59 v list of integers and intervals, for example: 1,3,6,9,8-96,109, v character string, enclosed in double quotation marks, for example: "this is a STRING" v pointer to a string, for example: v wildcard: * 86 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

97 Temporary variables Temporary variables hold an intermediate SNMP result or a partial result. You do not need to use temporary variables in a formula. Only use temporary variables in a collection formula when strictly required, because of the possible performance impact. These temporary variables can be used as parameters for subsequent queries. They are created with the OIDINST instruction or the OIDVAL instruction. The type of the result of the function on the right side of the equation is assigned automatically as the type of the variable. The previous contents of the variable are overwritten at each assignment. Temporary variables are declared as a capital V, followed by a number: v If fewer than nine variables are defined, numbering is 1-9. Forexample, V1, V2, V3, and so on. v If up to 99 variables are defined (even if less than 10 are used,) numbering is You must use two digits. For example, V09, V11, V34, and so on. To use the value of the variable in a formula, add %: %V1, %V2, %V3, and so on. Host variable The host variable (Hx) represents the current host name. Returning a result Comments in formulas Because multihost formulas are not supported, the only instance of this variable is H1. You can set the value by using the Formula Editor, by setting a target element or subelement for test, or by defining a target in the Request Editor table. Only the result of the last line of a formula is returned. This was illustrated in the example formulas. Prior lines made calculations, and manipulated variables, but only the last line returned a result. The MIB objects returned by the last line of a discovery formula become properties in the database, and can be used to create grouping rules with the Rule Editor. To add comments to a formula: v put each comment on a line by itself v start each line with the pound sign (#) v end each line with a semi-colon (;) # This is a comment; Do not include a comma (,) or semi-colon (;) within the body of the comment. Chapter 7. Writing custom formulas 87

98 Syntax for functions The Formula Editor includes the following function options. Mathematical functions Function Description + Addition The plus sign can also be used to indicate merging preference for a Discovery formula that the value will only overwrite previous content if the previous content was missing or empty. - Subtraction The minus sign can also be used to indicate merging preference for a Discovery formula that the value will only overwrite the previous content if the previous content was missing. * Multiplication - you need to add a space before each * (multiply star) for the formula to be correctly parsed. The asterisk, or multiply star, can also be used to indicate merging preference for a Discovery formula that the value will always overwrite the previous content. / Division % Returns the remainder of an integer division < Less than, the same as in the C programming language <= Less than or equal to, the same as in the C programming language > Greater than, the same as in the C programming language >= Greater than or equal to, the same as in the C programming language == Equal to, the same as in the C programming language!= Not equal to, the same as in the C programming language Int() Returns only the integer part of the expression Log() Returns the logarithm (log10) Ln() Returns the natural logarithm (loge) Abs() Returns the absolute value Exp() Returns the value of ex Round() Returns number rounded to the nearest multiple of significance 88 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

99 Other functions Function Description && Logical AND Logical OR like Performs an ASCII comparison of two arguments. Wildcards can be used in the right-hand argument. For example, to test the start of a sysobjectid compared to a vendor, without going into the model details. Not() Negates the expression; provides the opposite. SNMP-specific functions Function delta() Last() Diff() Description Calculates the difference between the value retrieved during this polling and the value retrieved during the previous polling for a single SNMP variable. This difference can only be positive because these variables must be counter variables. This function manages counter overflows and resets. Returns the value assigned to this expression during the previous polling. Returns the difference between the current value of this expression and its value for the previous polling. This value can be positive or negative. These functions cannot be nested. Aggregate functions For these functions, the expression defines an operation. The dimension specifies the variable used as an index for that operation. Function Sum (Dimension, Expression) Description Returns the total of all values. For example: Sum (*, ifinoctets.%i1) Max (Dimension, Expression) provides all octets entered on all the interfaces. Returns the highest value encountered. For example: Max (*, ifinoctets.%i1) provides the number of octets entered on the interface with the highest number of incoming octets. Chapter 7. Writing custom formulas 89

100 Function Min (Dimension, Expression) Description Returns the lowest value encountered. For example: Min (*, ifinoctets.%i1) Count (Dimension, Expression) Ave (Dimension, Expression) provides the number of octets entered on the interface with the lowest number of incoming octets. Returns a count. Calculates the average. Filter functions Function FirstN (Number of items, Expression) LastN (Number of items, Expression) Filter (Expression) Description Retains only the N lines with the highest result. Retains the N lines with the lowest results. Retains only the lines with a true result. In normal use, the expression is a Boolean that returns 1 (true) or 0 (false). Distribution function This function specifies the distribution of results within a formula. It provides a quantified, non-linear numerical result. For example, you can assign values such as: 5 for a load between 1% and 5% 4 for a load between 5% and 10% 1 for a load > 30%, and so on. The syntax is: distrib (Expression, Definition) The Definition string contains the list of tests to be performed, and the value of the result to be used if the comparison is positive. The Definition is a series of "condition: value" fields separated by commas. These are allowed in the condition: <, <=, >, >=, ==. They are compared to a numerical value, and the result is either the specified value, or * to keep the initial value. The Definition string must be enclosed in double quotation marks. It is evaluated from left to right. As soon as a condition is true, the corresponding value is returned. If no conditions are true at the end of the string, then no value is returned. Therefore, the distribution function can filter for specified values. For example: Dim I1 as Integer ; V1=OIDVAL(Distrib( (8*delta(ifInOctets.%I1)) /(delta(sysuptime.0)/100), <100:1,<1000:2,<100000:3, < :4,< :5,default:6 ), every); 90 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

101 AddForMissing() operator Note: Although the width of the page forces the second line of the formula to wrap onto three lines in this example, when using the Formula Editor each line of a formula must be on one line. Long lines cannot wrap. This operator allows extending the size of a result set and adding news results entries by using entries and dimensions from a reference vector. The only prerequisite is that both the expression, and the reference vector have the same dimensions set. addformissing ( Expression, reference Vector [, default replacement ] ) The result of the operator is an extension of Expression. For each dimension entry that is present in reference Vector only, a new dimension entry is added to Expression, using either the result in the reference vector, or the default replacement submitted Example Expression alone would result in the following results. Expression [I1 = (int) 1] Æ (int) 10 [I1 = (int) 3] Æ (int) 30 [I1 = (int) 4] Æ (int) 40 The reference vector, obtained with an OIDVAL operation (in a precedent line,) has the same Dimension set (I1), but with more replacement values (1, 2, 3, 4, 5, 6) Reference vector [I1 = (int) 1] Æ (int) 11 [I1 = (int) 2] Æ (int) 21 [I1 = (int) 3] Æ (int) 31 [I1 = (int) 4] Æ (int) 41 [I1 = (int) 5] Æ (int) 51 [I1 = (int) 6] Æ (int) 61 The addformissing operator detects that the replacement values (2, 5, and 6) were not defined in the original result set, and creates entries for them. If no default Replacement is provided, corresponding results from Reference vector are used. This generates the following result: result [I1 = (int) 1] Æ (int) 10 // from Expression [I1 = (int) 2] Æ (int) 21 // from reference vector [I1 = (int) 3] Æ (int) 30 // from Expression [I1 = (int) 4] Æ (int) 40 // from Expression [I1 = (int) 5] Æ (int) 51 // from reference vector Chapter 7. Writing custom formulas 91

102 [I1 = (int) 6] Æ (int) 61 // from reference vector If a default Replacement is provided, this default value is inserted for all new entries. This generates the following result: result [I1 = (int) 1] Æ (int) 10 // from Expression [I1 = (int) 2] Æ (int) default value [I1 = (int) 3] Æ (int) 30 // from Expression [I1 = (int) 4] Æ (int) 40 // from Expression [I1 = (int) 5] Æ (int) default value [I1 = (int) 6] Æ (int) default value Using the Formula Selector You can load an existing formula from the Formula Selector window. About this task To open the Formula Selector, follow these steps: Click File > Selectors > Formula Selector. Note: You can also use the formsel command-line interface (CLI) command to launch the Formulas Selector from the command line. Creating a formula group 1. Follow steps 1 in Using the Formula Selector. 2. Right-click and select New > Group. 3. Enter a unique name for the group and press the Enter. The new group is created. Finding a formula About this task To find a formula, follow these steps: 1. Follow step 1 in Using the Formula Selector. 2. Select a group or sub-group from the Formula branch. 3. Select Find from the menu. 4. Enter the group or formula name you want to find and click OK. To expand the search, you can use a "*" wildcard at the beginning, in the middle, or at the end of a character string. 92 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

103 For example: v CIS* - search for all the names beginning with CIS v *SCO - search for all the names ending with SCO v C*O - search for all the names beginning with C and ending with O. v *MIB* - search for all the names containing MIB. If more than one item is found, the Find Choices box appears. 5. Click OK to close the Find Choices box. Copying formulas About this task You can copy a single formula or a group/sub-group of formulas. To copy formulas, follow these steps: 1. Follow step 1 Using the Formula Selector on page Expand a group or subgroup. 3. Select a formula, group, or subgroup to copy. 4. Right-click and select Copy. 5. Alternatively, you can select Cut to remove the formula, group, or subgroup from its current location and paste it to another location. 6. The text for the items that you select turns blue to indicate that they are copied. 7. Paste the selection to the location of your choice. Deleting a formula About this task To delete a formula, follow these steps: 1. Follow step 1 in Using the Formula Selector on page Select a formula, group, or subgroup. 3. Right-click and select Delete. The items you select are deleted from view. 4. Click Apply to confirm the deletion. 5. Click Revert if you want to restore the deleted items. Renaming a formula 1. Follow step 1 in Using the Formula Selector on page Expand one of the directories. 3. Select a formula from the tree. 4. Select Rename from the menu. 5. Enter the new name. Formula examples This section contains three examples of formulas: v Discovery Chapter 7. Writing custom formulas 93

104 v v Collection Discovery merge Discovery formula for a Redback Ethernet interface The following example shows a Discovery formula that discovers all Redback Ethernet interfaces. For each interface, it reports the type, description, and speed. To use this formula automatically with the Inventory Tool, it must have an associated entry in the inventory_subelements.txt file. Dim I1 AS Integer Default * NAME Interface; V1=OIDINST(ifType.%I1 == 6, once); V2=OIDVAL(ifDescr.%V1, once); V3=OIDVAL(int(ifSpeed.%V1/ ), once); %V2 index "RedbackEthernet<%V1> %V2 %V3mbps Inst %V1 ifspeed<%v3mbps>ifdescr<%v2>"; Line-by-Line explanation Dim I1 AS Integer Default * NAME Interface This line declares the input variable I1. It specifies that it is an integer, that the default is all instances, and it is called Interface. Part of Formula Purpose Syntax Requirements Dim A keyword to indicate that an input variable is being declared. Not case-sensitive. I1 The input variable. "I" must be capitalized, and must be followed by a number. AS A keyword to indicate that the data type of the input variable is being declared. Not case-sensitive. Integer Default The data type of the input variable. A keyword to indicate that default instances are being declared. * The instances to use if no other instances are specified. In this case, * specifies that all instances must be used. Not case-sensitive. Optional, not case-sensitive. If both the Default and Name parameters are used, the Default parameter must come before the Name parameter. Default instances can be a list of values Or * to indicate that all instances must be used. Name Interface A keyword to indicate that a name for the input variable is being declared. The name to use for this input variable in the instance field of the Formula Editor. Optional, not case-sensitive. If both the Default and Name parameters are used, the Default parameter must come before the Name parameter. Must contain only letters and numbers; underscores and spaces are not allowed. 94 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

105 Part of Formula Purpose Syntax Requirements ; Indicates the end of the line. Required for every line of the formula, including comments. V1=OIDINST(ifType.%I1 == 6, once); This line restricts the type of row to which the formula is applied. It checks whether the value of iftype for each row is 6, which is defined in RFC1213 to mean ethernet-csmacd. If the value is not equal to 6, the row is skipped. If the value is equal to 6, the value of ifindex for this row is assigned to V1, and processing continues with the next line of the formula. Part of Formula Purpose Syntax Requirements V1 A temporary variable. "V" must be capitalized, and must be followed by a number. = Indicates that the result of the expression on the right must be assigned to the temporary variable on the left. OIDINST A keyword to indicate that a conditional filter is being used/ iftype A MIB object to which the filter is applied. In this case, iftype indicates the iftype column of the iftable.. Separates the MIB object from the instance. %I1 The instance of the MIB object. In this case, the values of the previously defined input variable is substituted. Spaces before and after are optional. Not case-sensitive. Case sensitive, must be a MIB object in a MIB compiled in Tivoli Netcool Performance Manager. Spaces are not allowed before or after. Must begin with %, and must: v match a previously defined input variable Or v be a constant == "equal to" the same as in the C programming language. 6 The value to be filtered. In this case 6, which isdefined in RFC1213 to mean ethernet-csmacd. once A keyword to indicate that the data must be retrieved only once, not polled repeatedly. Or v be the * wildcard Spaces before and after are optional. Valid operators for filtering are: like, <, >, <=, >=, ==,!= Can be any value that is valid for the MIB object being used Preceded by a comma; spaces before and after the comma are optional. Chapter 7. Writing custom formulas 95

106 Part of Formula Purpose Syntax Requirements ; Indicates the end of the line. Required for every line of the formula, including comments. V2=OIDVAL(ifDescr.%V1, once); This line retrieves the value of ifdescr for each value for V1 of the previous line. It assigns the value of ifdescr.%v1 to V2. Part of Formula Purpose Syntax Requirements V2 A temporary variable. "V" must be capitalized, and must be followed by a number. = Indicates that the result of the expression on the right must be assigned to the temporary variable on the left. Spaces before and after are optional. OIDVAL A keyword that indicates that the value of an expression is being assigned to a temporary variable. ifdescr A MIB object, the value of which is assigned to the temporary variable. In this case, ifdescr indicates the ifdescr column of the iftable.. Separates the MIB object from the instance. %V1 The instance of the MIB object. In this case, the values of the previously defined temporary variable is substituted. once A keyword to indicate that the data must be retrieved only once, not polled repeatedly. Not case-sensitive, the expression must be enclosed in parentheses. Case sensitive, must be a MIB object in a MIB compiled in Tivoli Netcool Performance Manager. Spaces are not allowed before or after. Must begin with %, and must match a previously defined temporary variable. Preceded by a comma; spaces before and after the comma are optional. ; Indicates the end of the line. Required for every line of the formula, including comments. V3=OIDVAL(int(ifSpeed.%V1/ ), once); This line retrieves the value of ifspeed for each value for V1 from the second line of the formula. It divides this value by 1,000,000, to convert from bits/second to megabits/second. It applies the int function to convert the result to an integer. It assigns that integer to V3. The result of a Discovery formula contains four parts: v First part must be a variable (%Vxxx) or an expression. The number of values of the variable or the number of returns of the expression drives how many results can be produced by the Discovery formula. 96 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

107 v Second part is the instance of the subelement. v Third part is prefaced with the host name and "_" to become the label field in both the Subelement and Host Selector, and in the Subelement Editor. v Fourth part (ifspeed<%v3mbps>ifdescr<%v2>) contains details about the interface. The MIB objects returned by the last line of the formula (ifspeed, ifdescr) become properties in the database, and can be used to create grouping rules with the Rule Editor. Collection formula example The following example shows a Collection formula for inbound bandwidth. To use this formula automatically with the Inventory Tool, it must have an associated entry in the inventory_subelements.txt file. Dim I1 AS Integer Default * Name Interface; delta(ifinoctets.%if)/delta(sysuptime.0/100); Line-by-Line explanation Dim I1 AS Integer Default * Name Interface; This line declares the input variable I1. It specifies that it is an integer, that the default is all instances, and it is called "Interface." Further information on the Dim statement is available in Dim declaration on page 80. Part of Formula Purpose Syntax Requirements Dim A keyword to indicate that an input variable is being declared. Not case-sensitive. I1 The input variable. "I" must be capitalized, and must be followed by a number. AS A keyword to indicate that the datatype of the input variable is being declared. Not case-sensitive. Integer Default The datatype of the input variable. A keyword to indicate that default instances are being declared. * The instances to use if no other instances are specified. In this case, * specifies that all instances should be used. Not case-sensitive. The valid types are listed in Instance variables on page 86. Optional, not case-sensitive. If both the Default and Name parameters are used, the Default parameter must come before the Name parameter. Default instances can be a list of values Or * to indicate that all instances should be used. See Instance variables on page 86 for more information about the format for default instances. Chapter 7. Writing custom formulas 97

108 Part of Formula Purpose Syntax Requirements Name A keyword to indicate that a name for the input variable is being declared. Optional, not case-sensitive. If both the Default and Name parameters are used, the Default parameter must come before the Name parameter. Interface The name to use for this input variable in the instance field of the Formula Editor. (This name will also appear in the Request Editor.) Can contain only letters and numbers; spaces are not allowed. ; Indicates the end of the line. Required for every line of the formula, including comments. delta(ifinoctets.%if)/delta(sysuptime.0/100); This line returns the final result. It calculates the number of incoming cells, as the number of octets divided by 53. It then divides this by the time period over which the collection was done. Part of Formula Purpose Syntax Requirements delta ifinoctets A function that calculates the difference between the value retrieved during this polling and the value retrieved during the previous polling for a single SNMP variable. A MIB object on which the calculation will be done. In this case, ifinoctets indicates the ifinoctets column of the iftable.. Separates the MIB object from the instance. %If The instance of the MIB object. In this case, inbound bandwidth Must be lower case. case-sensitive, must be a MIB object in a MIB compiled in Tivoli Netcool Performance Manager. Spaces are not allowed before or after. Must begin with %, and must match a previously defined temporary variable. / Division Spaces before and after are optional.. 53 Used to calculate the number of cells from the number of octets. delta A function that calculates the difference between the value retrieved during this polling and the value retrieved during the previous polling for a single SNMP variable. Spaces before and after are optional.. Must be lower case. 98 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

109 Part of Formula Purpose Syntax Requirements sysuptime A MIB object on which the calculation will be done. In this case, sysuptime indicates the time since the system was re-initialized. case-sensitive, must be a MIB object in a MIB compiled in Tivoli Netcool Performance Manager.. Separates the MIB object from the instance. 0 The instance of the MIB object. In this case, sysuptime is scalar, so "0" is used as the only instance. Spaces are not allowed before or after. Spaces before and after are optional. / Division 100 Used to calculate the number of seconds from the value of sysuptime, which is in hundredths of a second. ; Indicates the end of the line. Required for every line of the formula, including comments. Merge formulas example The following example implements the following on top of standard MIB II formula (1213_IF and 2233_IF): v v v v Octet capability detection: inbound and outbound, 64, 32, or undefined. Packets capability detection: 64 or 32 or undefined Custom invariant, either from MIB II ifdescr, or RFC2233 ifname Customer-specific key and properties inventory_sub-element.txt # File format: #{FAMILY} {Elem. FAMILY} {sysobjid Mask} {Match Formula} {I} {Discovery Formula} {I} {cancel FAMILY};[{...};] 1213_Device Generic~Agent NULL <*> AP~1213_Device <*> 1213_IF Generic~Agent NULL <*> AP~1213_IF <*> 2233_IF Generic~Agent AP~2233_IF_match <*> AP~2233_IF <*> 1213_IF; 2233_IF(Exp) Generic~Agent AP~2233_IF_match <*> AP~2233_HCOctets_Support <*> 2233_IF(Exp) Generic~Agent AP~2233_IF_match <*> AP~2233_HCPackets_Support <*> 1213_IF(Exp) Generic~Agent NULL <*> AP~1213_IF_Invariant <*> 2233_IF(Exp) Generic~Agent AP~2233_IF_match Chapter 7. Writing custom formulas 99

110 1213_IF 2233_IF <*> AP~2233_IF_Invariant <*> 1213_IF(Exp) Generic~Agent NULL <*> AP~TELUS_KEY Dim I1 AS Integer Default * NAME If; V1 = OIDVAL(ifType.%I1 format clean, once); V2 = OIDVAL(sysLocation.0, once); V3 = OIDVAL(ifSpeed.%I1, once); V4 = OIDVAL(int(%V3/ ), once); V5 = OIDVAL(ifAdminStatus.%I1 format clean, once); V6 = OIDVAL(ifDescr.%I1, once); %V1 index "If<%I1> IF %I1 (%V4Mbps) type<%v1>location <%V2>physicalCapacity<%V3>status<%V5> "; Dim I1 AS Integer Default * NAME If; V1 = OIDVAL(ifType.%I1 format clean, once); V2 = OIDVAL(sysLocation.0, once); V3 = OIDVAL(ifSpeed.%I1, once); V4 = OIDVAL(int(%V3/ ), once); V5 = OIDVAL(ifName.%I1 format clean, once); V6 = OIDVAL(ifAdminStatus.%I1 format clean, once); V7 = OIDVAL(ifAlias.%I1 format clean, once); V8 = OIDVAL(ifDescr.%I1, once); %V1 index "If<%I1> IF: %I1 (%V5) (%V4Mbps) type<%v1> location<%v2>physicalcapacity<%v3>name<%v5>status<%v6> "; 2233_HCOctets_Support Dim I1 AS Integer Default * NAME If; V1 = OIDVAL( ifindex.%i1 ); V2 = OIDVAL( filter( ifhcinoctets.%i1 >0) ); V3 = OIDVAL( filter( ifinoctets.%i1 >0) ); V5 = OIDVAL( filter( ifhcoutoctets.%i1 >0)); V6 = OIDVAL( filter( ifoutoctets.%i1 > 0) ); %V2+%V5 index "If<%I1> -UNSPECIFIED_LABEL Octets<in64.out64> "; %V2+%V6 index "If<%I1> -UNSPECIFIED_LABEL Octets<in64.out32> "; %V3+%V5 index "If<%I1> -UNSPECIFIED_LABEL Octets<in32.out64> "; %V3+%V6 index "If<%I1> -UNSPECIFIED_LABEL Octets<in32.out32> "; %V2 index "If<%I1> -UNSPECIFIED_LABEL Octets<in64.out0> "; %V3 index "If<%I1> -UNSPECIFIED_LABEL Octets<in32.out0> "; %V5 index "If<%I1> -UNSPECIFIED_LABEL Octets<in0.out64> "; %V6 index "If<%I1> -UNSPECIFIED_LABEL Octets<in0.out32> "; %V1 index "If<%I1> -UNSPECIFIED_LABEL Octets<in0.out0> "; 100 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

111 2233_HCPackets_Support Dim I1 AS Integer Default * NAME If; V1 = OIDVAL( ifspeed.%i1 ); V2 = OIDVAL( filter (( ifhcinucastpkts.%if + ifhcinmulticastpkts.%if + ifhcinbroadcastpkts.%if )> 0)); V3 = OIDVAL( filter (( ifinucastpkts.%if+ ifoutucastpkts.%if + ifinnucastpkts.%if + ifoutnucastpkts.%if )> 0)); %V2 index "If<%I1> -UNSPECIFIED_LABEL Packets<64> "; %V3 index "If<%I1> -UNSPECIFIED_LABEL Packets<32> "; %V1 index "If<%I1> -UNSPECIFIED_LABEL Packets<no> "; 1213_IF_Invariant # provide ifdescr and iftype as default invariant Dim I1 AS Integer Default * NAME If; V1 = OIDVAL(ifType.%I1 format clean, once); V2 = OIDVAL(ifDescr.%I1, once); %V1 index "If<%I1> -UNSPECIFIED_LABEL %V1-%V2"; 2233_IF_Invariant # provide invariant based on ifname, when non empty Dim I1 AS Integer Default * NAME If; V1 = OIDVAL( filter ( not (ifname.%i1 like "") ), once); V2 = OIDVAL( ifname.%i1, once); %V1 index "If<%I1> -UNSPECIFIED_LABEL *%V2"; <CustomerSpecific>_KEY The following example shows the <CustomerSpecific> key titled OurCustomer. Dim I1 AS IPAddress Default * NAME I1; V01=OIDVAL( ipadentaddr.%i1 ); V02=OIDVAL( ipadentifindex.%i1 ); V09=OIDVAL(expand(V02, ifdescr.%v02) ); %V09 index "If<%V02> -UNSPECIFIED_LABEL OurCustomerKEY<%V09>HPKEY<%V09>IP@<%V01> "; Formula error messages You might encounter one or more of the following error messages when editing and testing formulas. Error Message Initialization is not properly achieved. Description Error in formula. Chapter 7. Writing custom formulas 101

112 NO DATA Error in formula Or The formula is fine; however, there is nothing to collect Or The device does not respond as expected Or Error while casting variable Object identifier was not found in any of the compiled MIBs The formula timed out. This can happen if the formula includes more than one delta function and is launched against a target with a large number of sub-elements. Try launching the formula against a more specific target. Incorrect input variable. "I" (letter I) must be capitalized, and must be followed by a number. The MIB object used is invalid. Check that the name is correct. Names are case sensitive. Or ClientServices open Unable to connect to server at localhost Error Message "DATA at" with the date & time, but next line is "End" with no data Use the MIB Browser to check that the MIB has been compiled in Tivoli Netcool Performance Manager. If necessary, use the MIB Compiler to compile the MIB in Tivoli Netcool Performance Manager. Check that the collector is running. See Viewing collector information on page 171 for information about the collector. Description Inappropriate target Or Error in formula Understanding the inventory_subelements.txt file The inventory_subelements.txt file contains the list of rules the Discovery uses. It is located in the conf directory under the PVM directory. When you create new discovery formulas, you need to edit this file to create new rules. You must edit the file before the new Discovery formula can be used by the Inventory Tool. (You do not need to edit this file before a new collection formula can be used.) Discovery formulas are used only against elements, not against subelements. During Discovery, the Inventory Tool uses the sysobjectid field in the inventory_subelements.txt file to determine the correct formula to use for each element it encounters. The file already includes generic formulas that match any 102 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

113 sysobjectid, and numerous formulas for specific vendors and specific interfaces. The file only needs to be edited to add a new formula. Field Example Purpose SubElementFamilyName Redback_SMS_Ethernet Determines how sub-elements are grouped in the Subelement and Host Selector. FamilyName Router~Redback SysObjId The sysobjectid, or a part of the sysobjectid. FilterFormulaName NULL The path to the formula that is used to distinguish between different elements with the same sysobjectid. Instance <*> The instances to which the formula should be applied. This should correspond to the input variables in the formula listed under FilterFormulaName. If the formula contains more than one DIM declaration, there should be more than one Instance entry. If the formula only retrieves scalar objects, the instance can be empty. SubElementFormulaName PVL~Redback~Ethernet The path to the discovery formula for this subelement. The path is a location within the "Alias Instance and Label Inventory" directory, and is specified with tilde (~) as the path separator. Instance <*> The instances to which the formula should be applied. This should correspond to the input variables in the filter listed under SubElementFormulaName. SubElementFormulaName to cancel Generic_Lan_Ethernet10; Generic_Lan_Ethernet100; Generic_Lan_Ethernet1000 If the formula contains more than one DIM declaration, there should be more than one Instance entry. If the formula only retrieves scalar objects, the instance can be empty. A list of SubElementFormulaName that should not be used with this sysobjectid. Chapter 7. Writing custom formulas 103

114 SysObjId This field is the sysobjectid. The Inventory Tool checks to see if the sysobjectid of each element matches the sysobjectid listed here. If they match, it checks to see if there is an entry for FilterFormulaName. If the element matches both entries, the Inventory Tool runs the formula specified under SubElementFormulaName. Only a partial match for the sysobjectid is required. There are generic formulas included with Tivoli Netcool Performance Manager DataMart that specify as the sysobjectid. This is not an exact match for anything, but it is a partial match for everything. Since only a partial match for the sysobjectid is required, these generic formulas are used against every element encountered by the Inventory Tool. Any vendor-specific formula contains a more specific sysobjectid that matches only that vendor's sysobjectid. FilterFormulaName This field specifies the path to the formula that is used to distinguish between different elements with the same sysobjectid. The path is a location within the "Alias Instance and Label Inventory" directory, and is specified with tilde (~) as the path separator. For the Redback example, there is no such formula, so the entry is "NULL." Devices such as the Cisco Catalyst 3000 and Catalyst 5000 would have an entry in this field. They both have the same sysobjectid; however they can have different subelement types; therefore, they require different discovery formulas. For example, the FilterFormulaName for the Cisco Catalyst 3000 is PVL~Cisco~Catalyst~C3000~Match. Its discovery formula is PVL~Cisco~Catalyst~C3000~Port_HalfDuplex_10Mb. The FilterFormulaName for the Cisco Catalyst 5000 is PVL~Cisco~Catalyst~C5000~Match. Its discovery formula is PVL~Cisco~Catalyst~C5000~Port_HalfDuplex_10Mb. If the Inventory Tool finds a match on the sysobjectid, it checks for a FilterFormulaName. If a formula is specified, the element must match both the sysobjectid and the FilterFormulaName before the inventory tool runs the formula under SubElementFormulaName. SubElementFamilyName to cancel This field contains a list of any SubElementFamilyNames that must not be used with this sysobjectid. For the Redback example, the SubElementFamilyNames to be ignored are: Generic_Lan_Ethernet10, Generic_Lan_Ethernet100, and Generic_Lan_Ethernet1000. If you leave this blank, the same subelement can appear under two different groups, the vendor-specific group and a generic group. If you add information, the Inventory Tool ignores the canceled formulas not only for this type of subelement but for all subelements found on the element being processed. 104 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

115 If you cancel a generic rule that can be applied to more than one type of interface, and the Inventory Tool finds a subelement that does not match any of your device-specific rules but would have matched the canceled generic rule, that subelement is not discovered. For example, if Generic_Node is included in the SubElementFamilyName to cancel field for the Redback example, the Inventory Tool only discovers Redback ethernet interfaces. If the element contains other types of subelements, such as ATM, none of the other subelements are discovered. Chapter 7. Writing custom formulas 105

116 106 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

117 Chapter 8. Configuring thresholds About thresholds Threshold types Explains how to configure thresholds using the Resource Editor. Thresholds are values that are compared against metrics to determine if the metrics exceed or drop below a specific limit. Using thresholds as the measure against which data is evaluated lets you report on only those resources with pertinent data. A threshold is a value that is compared against metrics to determine if the metrics have violated a specific constraint. Using thresholds as the measure against which data is evaluated lets you report on only those resources with pertinent data. Threshold report capabilities exist at both the resource and group levels. The CME uses these threshold values to determine threshold violations and to generate SNMP traps. The information is stored in the database and is used by Tivoli Netcool Performance Manager DataView for on-demand and scheduled reports. Group thresholds are specified on a per formula basis within the Group Summary Table (GST) reporter parameters. The user specifies values for the critical or warning thresholds, the duration for which the threshold is in violation, the metrics, and statistics for which the threshold values apply, which user profile can view the thresholds in the report, and the reporter to drilldown to if the threshold is violated. You configure most of these thresholds (group threshold is the exception) using either the Resource Editor GUI or the resmgr command. Tivoli Netcool Performance Manager provides the following types of thresholds to supply report viewers with the information they want. burst Ignores the natural network bursts by evaluating how long in a row the violations occurred per resource. Burst thresholds can be set and reset multiple times. period Involves the concept of accumulated duration for which the threshold is violated. This duration is accumulated per resource until the end of the SLA period. The threshold is violated as soon as a data spike's accumulated duration by period exceeds a certain duration of time. Period thresholds, once violated are not reset until the end of the period. risk A proactive threshold that detects resources that are at risk of violating a period threshold before the end of the SLA period. baseline Provides a view into resource behavior outside the normal range. It uses a profiled deviation function to compare the current daily behavior with the baseline as data flows throughout the system (in real time.) What is normal is defined and what is not normal is flagged. Copyright IBM Corp. 2012,

118 Unlike burst, there is not a single threshold level to consider when determining duration. The duration determination scheme considers varying threshold levels. And unlike burst, period, and risk thresholds, you do not statically define the baseline, it dynamically adapts to historical data. User profiles and threshold types You need to decide what threshold information your report viewer needs to see, if any. You then grant access privileges to the threshold information to report viewers based on their user profile. For example, you might want report viewers with the NOC profile to have access to baseline threshold information to monitor the following: v v v Unusually high volumes at what is normally a "quiet" time (for example, night time) that might indicate a security issue. Unusually high volumes at "peak" time that might indicate that a new application has been deployed across the network and network capacity needs resizing. Unusually low volume at "peak" time that might indicate a potential issue with a router's forwarding mechanism, which continuously transmits data at a low level; impacting user perceived latency. The following matrix shows the threshold information that each type of audience probably wants to see. Violation Type Report Consumer Burst Period Risk Baseline User Profile for Reports Service Provider's NOC Yes Yes No Yes NOC Customer No Yes No No SLA Decisionmaker No Yes Yes Yes PSLA Basic computation The arrival of a metric record drives threshold computations. If a metric record does not arrive, no threshold computation occurs. Each incoming metric value is compared against a deployed threshold definition as part of the overall processing of the threshold record. All threshold statistics in the RA record are then updated appropriately. Statistic used for processing Threshold definition specifies the actual statistic to be used in the comparison (for example, raw or sum). As each metric value arrives, the statistic specified by this field is computed and this value is used for the subsequent threshold computations. 108 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

119 Exceeding a threshold level Determining whether a threshold is violated involves determining whether the metric exceeds a specified level. The actual comparison order depends on the type of metric (Over, Under, or Band). For example, the metric is considered to have exceeded the threshold level when the following occurs: v Threshold level is 10 v Metric value is 15 v Over metric type However, the metric would not be considered to have exceeded the threshold level if it was an Under. Determining whether the threshold is violated also involves the duration. Interpolation In order to determine how much time is spent `exceeding' a level, the system `interpolates' from the current value back to the previous one. If a previous value does not exist (at the very start of a metric stream) no interpolation is carried out, and a duration of zero is assumed. The following examples illustrate the linear interpolation process. Threshold deployment Explains the basics of threshold deployment. To understand threshold deployment, you need a basic knowledge of how thresholds are processed. Processing thresholds involves working with a metric, group, and resource (m/g/r) combination. (This m/g/r combination directly maps to Resource Aggregations (RAs) m/g/r combination.) Threshold deployment is the evaluation of thresholds to determine which threshold applies to which m/g/r combination. To make the determination, Tivoli Netcool Performance Manager examines each m/g/r combination and tries to find a matching threshold definition. Each threshold definition contains three key fields (Metric, Group, Resource) that are used to determine deployment. The examination involves comparing the m/g/r combination key values with the threshold key values. Chapter 8. Configuring thresholds 109

120 Note: Only one threshold definition can apply to a specific m/g/r combination. Tivoli Netcool Performance Manager looks for matches in the order defined in the following table: Configuration Metric Group Resource Priority group- and subelementspecific Defined Defined Defined 1 subelementspecific Defined No Defined 2 group-specific Defined Defined No 3 global Defined No No 4 Priority indicates which configuration takes precedence when multiple threshold definitions are available for a single resource. Also, multiple group-specific thresholds can be specified for a single branch of the subelement hierarchy. In this case, the definition closest to the resource (farthest from the root) takes precedence. Examples The following examples illustrate the different configurations. They use the groups, G0, G1, G2, G3, and G4 and the resources, R1, R2, R3. The runtime context (identified by m/g/r combination) is shown below each resource. The specific metric, `m' is considered, other metrics have their own runtime contexts. Group- specific and subelement-specific example The threshold definition T1(m/G3/R0) means that the key fields have values for metric, group, and resource set to `m', G3 and R0 respectively. Tivoli Netcool Performance Manager can match the m/g3/r0 combination with T1(m/G3/R0) - Group-specific and Subelement-specific. The threshold definition T1 is the only one in the system and it does not match either of the other m/g/r/ combinations. 110 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

121 Group-specific example A new threshold definition is defined, T2(m/G3/-.) This threshold differs from T1 because the resource is undefined. Tivoli Netcool Performance Manager cannot match the group- and subelement-specific or subelement-specific configurations, but can find a match for a group-specific configuration. The system determines that T2 is deployed against both m/g3/r0 and m/g3/r1. Chapter 8. Configuring thresholds 111

122 Group-specific and subelement-specific combined with groupspecific Thresholds T1(m, G3, R0) and T2(m, G3, -) are defined in the system. Both thresholds specify group G3; in addition T1 specifies the resource. The priority table is used to determine which threshold actually applies. The system deploys T1 against the m/g3/r0 combination (based on the groupand subelement-specific rule which is examined first) and T2 against the m/g3/r1 combination (based on the group-specific rule.) Now a third threshold T3(m, G1, -) is added. Because T1 and T2 have higher precedence, the runtime deployment state remains the same. The threshold T4(m, G0, -) is also added. Again, T1 and T2 are higher priority for the m/g3/r0 and m/g3/r1 groups respectively. The threshold deployments against those m/g/r groups remain the same. However, T4 does get deployed against m/g4/r IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

123 Resource in two groups example The following example shows R1 as a member of G3 and G4. A single threshold definition exists, T4 (m/g0/-.) Because R1 is a member of two groups, it belongs to two combinations, m/g3/r1 and m/g4/r1. Therefore, T4 is deployed against both these contexts. Chapter 8. Configuring thresholds 113

124 TRAP generation rules Provides a brief overview of trap generation rules. If Tivoli Netcool Performance Manager is configured to generate traps, trap generation input to a specific threshold occur when there is a change in the violation state. v burst, period (and proactive) thresholds Non-Violation <-> Warning Violation <-> Critical Violation v baseline thresholds Non-Violation <-> Violation The traps generated reflect the nature of the state transition. For example, when the system goes from burst non-violation to burst Warning violation for a particular m/g/r-threshold; a provisocmewarningviolationburstthr (see proviso.mib) is generated. The example illustrated in Resource in two groups example on page 113 shows resource R1 as a member of two groups. A threshold is deployed against the m/g/r combinations that result from that group membership. Therefore, it is possible for multiple traps to be generated (one for each m/g/r combination) when a single metric value is processed. Using the threshold definition period setting Provides a brief overview of the use of the period setting in the calculation of a period threshold. Threshold definitions have a period setting (different from a period threshold) that can have the following values: v Day v Week v Month v All (which means Day and Week and Month) In each m/g/r combination, threshold statistics can be calculated for Days, Weeks and/or Months. The period setting determines which of these time periods the threshold statistics is calculated for, when processing the type of threshold call a period threshold. Note: Statistics in these m/g/r combinations map directly to Daily, Weekly, and Monthly Aggregation records. Processing traps When processing an m/g/r combination, it is possible that a period threshold can be violated for each of the configured periods. If that occurs, the system can send three traps, one corresponding to each of the configured periods (one trap for the Day, one for the Week and one for the Month). However, when processing burst thresholds, a similar violation would lead to a single trap. 114 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

125 Launching the threshold tool Explains how to launch the Threshold tool from the Tivoli Netcool Performance Manager DataMart Resource Editor. The Threshold tool lets you configure thresholds. 1. Click Resource Editor in the Resource tab. 2. In the Resource Editor, click the Threshold tab. 3. Filter the listings by entering a filter value, and then clickapply Filter. The following table lists the possible columns that can appear in the window: Column Metric Group Resource Mode Date Stat Calc CalcVal BCrtL BCrtT BWrnL BwrnT BEvent Description Name of the metric Name of the subelement group Name of the resource Threshold mode Date and time the action takes effect. Actions cannot be applied to the past and take effect on the hour. Statistic the CME uses to calculate threshold information: v raw (default) v min v max v avg v sum v count Calculation used to determine the value of the following: v standard v normalized v scale Value used for calculating the percentage over or under the threshold. Level of the critical threshold for burst thresholds. Zero implies the threshold is not defined. The metric must be greater than this level to trigger a violation. Time limit for the burst critical threshold. Level of the warning threshold for burst thresholds. Zero implies the threshold is not defined. Duration of the burst critical threshold in seconds. Indicates whether Tivoli Netcool Performance Manager generates SNMP traps for the burst threshold. Chapter 8. Configuring thresholds 115

126 Column PCrtL PCrtT PWrnL PWrnT PEvent PDef MaxNbDay minnbday blcalcmode blmode bltime bltrap Description Level of the period critical threshold for period thresholds. Zero implies the threshold is not defined. Duration the period critical period threshold in seconds. Level of the warning threshold for period thresholds. Zero implies the threshold is not defined. Duration of the warning period threshold in seconds. Zero (0) indicates an immediate threshold violation. Indicates whether Tivoli Netcool Performance Manager generates SNMP traps for the period threshold. Defines the period for period and burst thresholds: v all v day v week v month If the period is day, week, or month, the GST and RST reports for the other periods do not show a violation. If the field is set to all, violations are reported for all periods. Number of days used as the maximum value for the computation of the upper control limit. The upper control limit is the top of what is considered the normal range and is used for the baseline threshold. Number of days used as the minimum value for the computation of the lower control limit. The lower control limit is the bottom of what is considered the normal range and is used for the baseline threshold Mode used in calculation of baseline data: v 0 = previous days, v 1= previous same day of the week Baseline mode v 1 = under v 2 = over v 3 = band Duration of baseline violation. Indicates whether the baseline threshold generates a trap. v 0=no v 1 = yes 116 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

127 Column blupper bllower Description Number of standard deviations used as the maximum value for the computation of the upper control limit. The upper control limit is the top of what is considered the normal range. Number of standard deviations used as the maximum value for the computation of the lower control limit. The lower control limit is the bottom of what is considered the normal range. Adding a threshold About this task This section explains how to add the following types of thresholds by using the Add Threshold window: v burst (static threshold because you set the value) v period (static threshold because you set the value) v baseline To add a threshold, follow these steps: 1. Click the Threshold tab in Resource Editor. 2. Click Add from the Edit menu. The Add Threshold window appears. Selecting metrics You need to choose the metric to which you want to apply the threshold. Use this for all three types of thresholds 1. Click Browse to access the Formula Selector. 2. Go to the metric (formula) you want to by expanding the folders in the left pane and clicking the folder name to display metrics (formulas) in the right pane. 3. Click the formula name to highlight it and while holding down the left mouse button, drag the formula name to the Metric text box. The formula name, along with the entire path, appears. Applying thresholds to a group of subelements You can choose to apply the threshold to a group of resources at different granularity levels. About this task You can apply the threshold to the top group in the grouping tree, to any of the leaves or subleaves. Or, you can choose not to apply the threshold to any group, by leaving the text box blank because you want to apply the threshold to any subelement containing the metric you have chosen or to just a specific subelement by adding its name to the subelement text box. Chapter 8. Configuring thresholds 117

128 If you are applying a group- and subelement-specific threshold, you need to identify the leaf-level group that contains the resource and apply the threshold to that group. To choose the group using the Resource Editor, follow these steps: 1. Put the focus on the Resource Editor window, while leaving the Add Threshold window open. 2. In the Resource Editor, click the Sub-Element Group tab. 3. Click the + sign next to SUB-ELEMENTS in the left pane to expand it. The list of all subelement groups appears in the left pane. 4. Go to the formula group you want to choose. For example, go to the High Speed Interfaces (>=100 Mbps) group under the All Technologies group. 5. Highlight the group name and hold down the left mouse button while dragging the group name to the Group text box in the Add Threshold window. From here, you can add a specific subelement name from the group or you can leave the Sub-Element text box blank to apply the threshold to all subelements belonging to the group, that contain the specified metric. Specifying subelements You can specify the subelement to which you want to apply a threshold. If you do not specify a group for that subelement, the threshold is applied to that subelement, in each group to which it belongs. About this task To choose a subelement using the Resource Editor: 1. Put the focus on the Resource Editor window, while leaving the Add Threshold window open. 2. In the Resource Editor, click the Sub-Element Group tab. 3. Click the + sign next to SUB-ELEMENTS in the left pane to expand it. The list of all subelement groups appears in the left pane. 4. Go to the subelement that you want to apply the threshold. For example, go to the list of subelements belonging to the subleaf group called ethernetcsmacd. 5. Click the subleaf group's name to display the list of subelements in the right pane. 6. Click the subelement name in the right pane to highlight it. 7. Holding down the right mouse button, drag the subelement name to the Sub-Element text box in the Add Thresholdwindow. 8. Release the right mouse button. The subelement name appears in the text box. 9. Click Apply to finalize your choices. 10. Click Close to clear the message or click Details to open the Details section of the message box From here, you can configure the static and baseline thresholds. 118 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

129 Configuring burst or period thresholds Explains how to configure burst and period thresholds. These thresholds are considered static thresholds because you set the value for them by using the configuration dialog box. You also define how you want the threshold to act. Configuring thresholds From the Add Threshold Window, click Static Threshold. Configuring mode You need to configure the mode you want to apply to your burst and/or period threshold. 1. Configure the mode you want to apply to the static threshold (burst or period.) The following table lists the configuration options: Option Definition Values Effective date Currently not used by Tivoli Netcool Performance Manager. Threshold is effective immediately after creation or update. Do not edit this value. Mode Mode of the threshold Click the down arrow to access the list of values: v v v Band: detect violations when they go outside a range (or band) between two threshold values Over: detect violations when they exceed threshold values Under: detect violations when they fall short of threshold values Statistic mode Calculation mode Calculation value Indicate which statistic you want used to calculate threshold information. Calculation method to use to determine the maximum percentage over burst and period threshold values. Activated when you select Scaled for the Calculation mode. Value used for calculating the percentage over or under the threshold. Click the down arrow to access the list of statistics. Click the down arrow to access the list of the three different ways of calculating this value. v Standard v Normalized v Scaled Enter the number you want to use for the calculation. Chapter 8. Configuring thresholds 119

130 2. Click Apply. Configuring maximum percent over for burst and period thresholds When configuring the burst and period thresholds, you need to enter a value that represents the maximum percent over a threshold level. This section provides a brief overview of the maximum percent over calculation. For both burst and period thresholds, the values of the maximum percent over fields (DBL_BRST_MAX_PCT_OVER and DBL_PRD_MAX_PCT_OVER) use the following algorithm: MAX_PCT_OVER = 0 For each metric, mi, If mi-lw /Lw > MAX_PCT_OVER then MAX_PCT_OVER = mi-lw /Lw If mi-lc /Lc > MAX_PCT_OVER then MAX_PCT_OVER = mi - Lc / Lc The algorithm differs from taking the maximum value of a metric and dividing it by the most severe threshold violation. Depending on the relative values of metrics and threshold levels, it is possible that the maximum percent over is obtained from a metric that is not the largest metric value. Configuring burst values About this task To configure burst values, follow these steps: 1. In Static Threshold, click the Burst tab. 2. Click Enabled Threshold to activate the configuration options. Note: You can disable a threshold but retain the configuration values by clearing the Enabled Threshold box and clicking Apply. The threshold is disabled immediately for all Tivoli Netcool Performance Manager modules except the CME. For the CME, the action takes effect with the hourly reload. If you want to reuse this threshold with the same values, you click Enabled Threshold, check the values, and click Apply. 3. Enter the values you want for the burst threshold. The following table lists the configuration options: Option Definition Values Warning Level Level of the warning threshold. The metric value must be greater than this value to trigger a threshold violation. Enter a double-precision floating point number with up to six digits to the right of the decimal point. 120 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

131 Critical Level Event generation Warning time Critical time Level of the critical threshold. The metric value must be greater than this value to trigger a threshold violation. Indicates whether Tivoli Netcool Performance Manager must generate an event when threshold violation occurs at warning and/or critical levels (if you entered a value in the Warning Level and Critical Level fields.) Maximum duration for exceeding Warning threshold level. Maximum duration for exceeding Critical threshold level. Enter a double-precision floating point number with up to six digits to the right of the decimal point. Click the down arrow to display the values. Choose yes if you want to generate an event when a threshold violation occurs. Enter the number of seconds as an integer. Enter the number of seconds as an integer. 4. Click Apply. Configuring period values About this task To configure period values, follow these steps: 1. In Static Threshold, click the Period tab. 2. Click Enabled Threshold to activate the configuration options. Note: You can disable a threshold but retain the configuration values by clearing the Enabled Threshold box and clicking Apply. The threshold is disabled immediately for all Tivoli Netcool Performance Manager modules except the CME. For the CME, the action takes effect with the hourly reload. If you want to reuse this threshold with the same values, you click Enabled Threshold, check the values, and click Apply. 3. Enter the values you want for the period threshold. The following table lists the configuration options: Option Definition Values Warning Level Critical Level Level of the warning threshold. The metric value must be greater than this value to trigger a threshold violation. Level of the warning threshold. The metric value must be greater than this value to trigger a threshold violation. Enter a double-precision floating point number with up to six digits to the right of the decimal point. Enter a double-precision floating point number with up to six digits to the right of the decimal point. Chapter 8. Configuring thresholds 121

132 Event generation Warning time Critical time Period Definition Indicates whether Tivoli Netcool Performance Manager should generate an event when threshold violation occurs at warning and/or critical levels (if you have entered a value in the Warning Level and Critical Level fields.) Maximum duration for exceeding Warning threshold level. Refer to Configuring maximum percent over for burst and period thresholds on page 120. Maximum duration for exceeding Critical threshold level. Refer to Configuring maximum percent over for burst and period thresholds on page 120. Defines the period for which you want threshold violations reported. Click the down arrow to display the values. Choose yes if you want to generate an event when a threshold violation occurs. Enter the number of seconds as an integer. Enter the number of seconds as an integer. Click the down arrow to display the values. Choose the period for which you want threshold violations reported. If you choose All, violations for all periods are reported. 4. Click Apply. Configuring baseline thresholds Explains how to configure baseline thresholds. Unlike burst and period thresholds, you do not statically define the baseline, it dynamically adapts to historical data. About this task To configure a baseline threshold, follow these steps: 1. From the Add Threshold window, click Baseline Threshold. 2. Click Enabled Threshold to activate the configuration options. Note: You can disable a threshold but retain the configuration values by clearing the Enabled Threshold box and clicking Apply. The threshold is disabled immediately for all Tivoli Netcool Performance Manager modules except the CME. For the CME, the action takes effect with the hourly reload. If you want to reuse this threshold with the same values, you click Enabled Threshold, check the values, and click Apply. 3. Enter the values you want for the baseline. The following table lists the configuration options: Option Definition Values 122 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

133 Max # of days Min # of days Calculation Maximum number of days you want to consider for the baseline. This value must be higher than the value you enter for the minimum number of days. Minimum number of days of data required before the baseline is calculated. This value must be less than or equal to the Maximum number of days. Indicate which calculation mode you want to use for the baseline. Enter an integer of up to three digits to indicate the maximum number of days. Enter an integer of up to three digits to indicate the minimum number of days. Click the down arrow to display the values: v PreviousDays: include the previous N days from the specified reporting period in the calculation. For example: If you specify 10 days for the reporting period of August 29; the PreviousDays calculation includes the 10 previous days: August 19, 20, 21, 22, 23, 24, 25, 26, 27, and 28. v PrevSameDay: include the N previous same days of the week from the specified reporting period in the calculation. For example: If you specify 10 days for the reporting period of Friday, August 29; the PrevSameDay calculation includes the same day from the 10 previous weeks: Friday June 20, Friday June 27, Friday July 4, Friday, July 11, Friday July 18, Friday July 25, Friday August 1, Friday August 8, Friday August 15, and Friday August Enter the values you want for the threshold. The following table lists the configuration options: Option Definition Values Sensitivity (upper) Number of standard deviations added to the mean to determine upper threshold level. Enter an integer with maximum of four digits, with a maximum of two digits to the right of the decimal point. Chapter 8. Configuring thresholds 123

134 Sensitivity (lower) Number of standard deviations added to the mean to determine lower threshold level. Enter an integer with maximum of four digits, with a maximum of two digits to the right of the decimal point. Permitted time outside baseline Baseline equivalent of duration for burst thresholds. Enter the time limit in minutes, hours, or days. You can use a combination of units such as 1 hour 25 minutes. Event generation Mode Indicates whether Tivoli Netcool Performance Manager must generate an event when threshold violation occurs. Mode of the baseline threshold. Click the down arrow to display the values. Choose yes if you want to generate an event when a threshold violation occurs. Click the down arrow to access the list of values: v v v Band: detect violations when they go outside a range (or band) between two threshold values Over: detect violations when they exceed threshold values Under: detect violations when they fall short of threshold values 5. Click Apply. Trapping threshold violations The following sections explain how to enable Tivoli Netcool Performance Manager to do the following: v Trap threshold violations to a log file. v Trap threshold violations and send them to a specified host or hosts. Trapping threshold violations to the log file Once you e configured thresholds, you can enable the trapping of threshold violations to the main log file, proviso.log. About this task To enable the trapping of threshold violations to the log file, follow these steps: 1. Open an existing Tivoli Netcool Performance Manager topology. 2. Go to the Logical View. 3. Browse to the Complex Metric Engine (CME) folder on the left pane as follows: Netcool/Proviso Topology > DataChannels > DataChannel 1 > Collector 1.1 > Complex Metric Engine Go to the Properties tab on the right pane and select the LOG_TRAPS property. 124 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

135 5. Set the value to true (default is false) by selecting the check box. This enables the trapping of threshold violations to the log file. 6. Repeat step 2-4foreach threshold violations trapping you want to enable for the DataChannels. 7. Save the topology. The following is an example of a threshold violation recorded in the proviso.log log file: UTC CME I THRSHEVENT trap log : ProvisoViolationAutoThr :: :: _If<1001>:: _IF: 1001 "340 Mbps" "RMON: VLAN 1"::undef::IETF_IF::AP~Generic~Universal~Throughput ~Outbound Throughput (bps) :: d:: d:: ::300::410::::3::15::undef::"3Com"::undef::undef ::undef::undef::undef:: ::2209 Sending trapped threshold violations to specified hosts About this task Once you configured thresholds, you can configure Tivoli Netcool Performance Manager to send trapped threshold violations to specified hosts, as follows: v Send trapped threshold violations to up to five hosts at a specified port. v Include in the trap header the IP address of the element where the violation occurred. SNMP traps are easily managed and decoded by almost any fault management system. Netcool/OMNIbus and Webtop, for example, allow a Webtop user to right-click on an alarm generated by Tivoli Netcool Performance Manager, launching the relevant Tivoli Netcool Performance Manager report. For more information about integrating Tivoli Netcool Performance Manager with OMNIbus and Webtop, see the IBM Tivoli Netcool Performance Manager: OMNIbus Web GUI Integration. To configure the sending of trapped threshold violations to specified hosts, follow these steps: 1. Open an existing Tivoli Netcool Performance Manager topology. 2. Go to the Logical View. 3. Browse to the Complex Metric Engine (CME) folder on the left pane as follows: Netcool/Proviso Topology > DataChannels > DataChannel 1 > Collector 1.1 > Complex Metric Engine Go to the Properties tab on the right pane and select the LOG_TRAPS property. 5. Specify the host name and port number combinations to receive trapped threshold violations. For example, v localhost:162 Or v : Select the corresponding TRAP_IPADDRESS_FROM_ELEMENT property. 7. The default value is set to true. This is to include in the trap header the IP address of the element where the threshold violation originated. If this parameter is set to false, the IP address of the CME system that sent the trap is included in the trap header. 8. Save the topology. Chapter 8. Configuring thresholds 125

136 126 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

137 Chapter 9. Managing MIBs MIB groups Compiling a MIB Explains how to use the MIB compiler to compile MIBs and how to use the MIB browser to view MIB files and verify object values..a MIB file consists of object definitions that manage TCP/IP-based networks. The variables in a MIB are organized in groups, such as System, Interface, or TCP. A MIB file contains object definitions, which are typically organized into the following groups: v System Group (1) v Interface Group (2) v AT Group (3) v IP Group (4) v ICMP Group (5) v TCP Group (6) v UDP Group (7) v EGP Group (8) v CMOT Group (9) v Transmission Group (10) v SNMP Group (11) Tivoli Netcool Performance Manager DataMart includes pre-compiled MIB files. You can include additional MIB files by importing them and compiling them into the required Tivoli Netcool Performance Manager DataMart format. About this task Compiling a MIB makes Tivoli Netcool Performance Manager aware of the MIB object identifiers and their values. The compile process occurs in three phases, all of which are not apparent to the user: v Phase one creates an intermediary frozen MIB format. v v Phase two creates the OID format required by Tivoli Netcool Performance Manager DataMart. Phase three compiles the MIB, as well as all dependant MIBs. The results of the compilation are stored in the $PVMHOME/mibs directory in the following subdirectories: v frozen v oid v src Important: A MIB is compiled only when both the frozen and OID formats exist. Copyright IBM Corp. 2012,

138 To compile a MIB, follow these steps: 1. On the server where DataMart is installed, enter the following command to open the DataMart application: $PVMHONE/bin/pvm & The DataMart application appears, as shown in the following figure: 2. Click Metric > Mib Compiler. 3. In the display pane, click the MIB directory to select an entire tree or branch, or drill-down to a specific MIB or MIBs that you want to compile. 4. Optional: If the MIB you want to compile is not in the list displayed in the MIB Compiler, you can copy it to the appropriate directory by selecting Import File... from the File menu. a. Go to where the MIB file is located. b. Highlight the MIB file name to select it and click Open. The file format for a MIB is typically.mib, asn, or.txt. If you want to compile more that one MIB file, do the following: v Select a directory name to compile all MIB files in the directory v Select several consecutive MIB files by clicking the file name for the first MIB file, then clicking the additional names while holding down the Shift key v Select several non-consecutive MIB files by clicking each name while holding down the Ctrl key c. Click Yes to continue the import process. The file is copied to the specified directory and the imported MIB appears in the navigation tree of MIB files in the left display pane of the MIB Compiler. 5. To begin the compilation, click Compile. A progress indicator displays the status of the compilation and a message appear in the Traces pane. Note: The Traces pane displays compilation warning messages in blue and error messages in red. 128 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

139 Printing or saving trace information 1. Right-click in the Traces area to access a menu with the following options v Reset - clears the Trace area v Save - lets you print the trace information or save it to a file. 2. Click Save. Printing trace information 1. Select a printer from the drop down list. 2. Edit the print command if you want to print in a specific format. 3. Increase or decrease number of copies by clicking the up and down arrows. 4. Click OK to print. Saving trace information 1. Click the To file: option. 2. Enter the path to where you want to store the file or click Browse. 3. Click OK to save the information. Deleting a MIB About this task If for whatever reason you decide to delete a MIB, you can do so by following these steps: 1. Log on as pvuser to the system where DataMart is installed. 2. Change your working directory to $PVMHOME/datamart/mibs. 3. Using the rm command, delete whatever MIB files you no longer want from the DataMart server file system. Note: In some cases, the MIB file might be located in the src subdirectory. 4. In order to permanently remove the MIB files, you must also delete them from the database by resyncing the database with the files on disk. 5. To resync the database with the MIB files on disk, enter the following command: $PVMHOME/bin/dbRep checkin mibs -r $PVMHOME/mibs -m "*" -dodelete t For example, if you removed the MIB agent-mib.mib from the $PVMHOME/datamart/mibs/src directory and then ran the $PVMHOME/bin/dbRep command, you would see output like the following: [pvuser@kafka.com:/opt/datamart/mibs/src] rm agent-mib.mib [pvuser@kafka.com:/opt/datamart/mibs/src] dbrep checkin mibs -r $PVMHOME/mibs -m "*" -dodelete t load cached catalog.catalog for /opt/datamart/mibs/... ok [catalog has 2713 entrie(s)]. update catalog from disk /opt/datamart/mibs/... ok, [catalog has 2712 entrie(s)]. deleting src/agent-mib.mib in database... ok. save cached catalog.catalog for /opt/datamart/mibs/... ok. [pvuser@kafka.com:/opt/datamart/mibs/src] Chapter 9. Managing MIBs 129

140 Viewing MIB file source 1. Click the MIB filename in the navigation and selection pane. 2. Choose View from the MIB menu to display the source. The contents of a sample MIB file appears. 3. Locate specific information by entering text in the Find text box and clicking Forward or Backward to search through the file. 4. Click Close to exit. Browsing MIB files You can view a list of compiled MIB files by accessing the MIB Browser. About this task To access the MIB Browser, follow these steps: 1. Click Browse to open the MIB Browser. 2. See Viewing compiled MIB files for detailed information. Viewing compiled MIB files The MIB Browser lets you view a list of compiled MIB files in either tree format or in group/table format. You can then choose files from the list to review element information or to verify object values. 1. Click MIB Browser in the Metric tab. The MIB Browser dialog box appears listing compiled MIB files in tree format 2. Select the Group/Table item from the Options menu to change the display. In this format, all MIB files link directly to the iso root and are separated into either objects contained in groups or objects contained in tables. Finding MIB files You can quickly locate a specific MIB object in the navigation and selection pane. About this task To find an item, follow these steps: 1. Place cursor in navigation and selection pane. 2. Right-click. A menu appears. 130 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

141 3. Enter the object name of the item you want to find and click OK. 4. If the search finds more than one item, the following dialog box appears. 5. Click the line containing item you want and click OK. The cursor moves to that item in the tree and the Find Choices dialog box closes. Loading MIB files You can temporarily load MIB files into the MIB Browser to review element information or to verify object values. About this task To load MIB files, follow these steps: 1. Select Load from the File menu. The MIB Selector dialog box appears. 2. Click a folder to display subfolders. 3. Click a subfolder to display a list of MIB files. 4. Click the name to select the MIB file and click OK. The selected MIB file, and all its dependencies, appears in the navigation and selection pane. When you exit the MIB Browser, the MIB file is removed from the display. Chapter 9. Managing MIBs 131

142 Viewing element information You can view specific element information about the MIB file. About this task To view element information, follow these steps: 1. Click the name of the MIB file you want to select. 2. Click the Element Info tab in the MIB Browser dialog box. The information for the selected object appears in the Element Info tab. v Name is the textual identifier of the object. v OID is the numeric identifier in dot-notation format. v Module name are the names of the modules that define the selected MIB node. A MIB can include other MIBs, either directly or indirectly. v Syntax identifies the abstract data structure corresponding to the object type, using ASN.1 constructs. v Access is one of the following: Read-only Read-Write Write-only non-accessible v Index is a list of MIB names that are used as a key in a conceptual table. No names appear if the MIB node does not correspond to a MIB table. v Description is a textual description of the meaning of the object type. Verifying object values If you want to verify the values of MIB objects, you can test them directly in the MIB Browser. 1. Click the name to select a MIB file. 2. Click the Test tab in the MIB Browser dialog box. 3. select the type of resource from the following list. v Element v Element_Group 4. Choose the name of the resource you want to test from the list. If the list is blank, click Refresh to update it. The Instance and Community text boxes are populated if included as part of the resource name. The associated SNMP Collector automatically appears in the SNMP Collector list. 5. Select a MIB file by clicking the name in the navigation and selection pane. The location of the MIB file in the tree affects what MIB files are included in the request if: v The MIB file is located in the final section of the tree, the request is executed on just that section. v The MIB file is located elsewhere in the tree, the request is executed on that section and all sections below it in the tree. The sections can include an entire MIB set, the entire MIB, or a MIB sub-set. 6. Click Test. The Trace area displays the results of the test request. 132 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

143 The results include: v Request parameters v MIB files selected v Results of request 7. Right-click in the Trace area to access a menu with the following options: v Reset - clears the Trace area v Save - lets you print the trace information or save it to a file. 8. Click Save. the following dialog box appears. Printing trace information: 1. Select a printer from the drop-down list. 2. Edit the print command if you want to print in a specific format. 3. Increase or decrease number of copies by clicking the up and down arrows. 4. Click OK to print. Saving trace information: 1. Click the To file: option. 2. Enter the path to where you want to store the file or click Browse. 3. Click OK to save the information. Chapter 9. Managing MIBs 133

144 134 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

145 Chapter 10. Editing resources Describes how to use the Resource Editor to edit the resources. You can perform the following tasks by using the Resource Editor: v View resource information v Export resources v Import resources v Add resources v Delete resources v Deploy reports For more information about managing resources from the command line, see the Command Line Interface Reference. Filtering elements and subelements Display specific subsets of information by filtering the elements, subelements, and composite subelements in your network. Displaying all resources in the Resource Editor can take a significant amount of time in large deployments. For large deployments, always use the filter to avoid displaying all resources. 1. Click Resource Editor in the Resource tab. The Resource Editor window opens. 2. Click the Element or Sub-Element tab in the Resource Editor. 3. Click Apply Filter to display all resources on your network. To filter the results to display specific resources, enter a unique value in any of the column headings then click Apply Filter. Use the following syntax to create your filters: Filter string string* *string *string*!='string' is null not null Result Displays all results that match the value of string. Displays all results that match the prefix value of string. Displays all results that match the suffix value of string. Displays all results that contain the value of string. Displays all results that have values other than the value of string. Displays all results that have no value defined. Displays all results that have any value defined. Copyright IBM Corp. 2012,

146 Viewing resource information Explains how to view information about elements, subelements, subelement groups, and element and subelement properties. Displaying all resources in the Resource Editor can take a significant amount of time in large deployments. For large deployments, always use the filter to avoid displaying all resources. Viewing elements 1. Click the Element tab in the Resource Editor. 2. Click Apply Filter to view all elements in the database, or enter filter information to limit the number of results. The following information is displayed. Note: Both IPv4 and IPv6 address formats are supported. Column Name Name Profile Collector Description Type Description Displays the name of the element. Displays the name of the inventory profile used to discover this element. For more information, see the Installing Tivoli Netcool Performance Manager - Wireline Component. Displays the collector number assigned to this element. Displays a descriptive textual name for the element. Displays the type of the element: snmp Defines an element for SNMP collections. default_snmp Used for SnmpConf. star_snmp Used for SnmpConf (@IPrange). import Defines a host with imported data. No SNMP collections are available. Origin State Displays the method used to add the element to the database. Displays the state of the element: on off Indicates that the element is visible in the graphical user interface. Indicates that data collection on the element is stopped and that the element is no longer visible in the graphical user interface. 136 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

147 Viewing subelements 1. Click the Sub-Element tab in the Resource Editor. 2. Click Apply Filter to view all subelements or composite subelements in the database, or enter filter information to limit the number of results. The following information is displayed: Column Name Name Date Label Profile Family Element Instance Description Displays the name of the subelement or composite subelement. Displays the date for the subelement or composite subelement. Displays a descriptive comment for the subelement or composite subelement. Displays the name of the inventory profile used to discover the subelement or composite subelement. For more information, see the Installing Tivoli Netcool Performance Manager - Wireline Component. Displays the name of the family for the subelement or composite subelement. Displays the name of the element for the subelement or composite subelement. Displays the name of the instance for the subelement or composite subelement. Viewing subelement groups 1. Click the Sub-Element Group tab in the Resource Editor. 2. Click a subelement or composite subelement group folder to expand it. 3. Select a subelement or composite subelement group name to display the elements it contains in the right pane. The following information is displayed: Column Name Name Label Family Element Instance Type Relation Description Displays the name of the subelement or composite subelement. Displays a descriptive comment for the subelement or composite subelement. Displays the name of the family for the subelement or composite subelement. Displays the name of the element for the subelement or composite subelement. Displays the name of the instance for the subelement or composite subelement. The type of the group member. Possible values are GROUP, SE, or CSE. The relation of each group member. Particularly important for composite subelements. Chapter 10. Editing resources 137

148 Column Name Name Label Description The name of the group member. The label of the group member. Viewing property details 1. Click the Element or the Sub-Element tab in the Resource Editor. 2. Click Apply Filter to view all resources in the database, or enter filter information to limit the number of results. 3. Locate an element, subelement, or composite subelement by scrolling through the list, or click the magnifying glass icon to open the Find dialog box. 4. Highlight the element, subelement, or composite subelement and click Detail. The Properties, Relation To, and Relation From tabs are displayed. 5. Optional: To hide the details, click Detail again. Property details The Detail tabs provide these information: Properties The properties and values associated with the selected subelement or composite subelement. Relation To The source subelements or composite subelements to which the selected composite subelement is linked. The Relation To tab contains: Relation The relationship between the selected composite subelement and each of the source subelements or composite subelements. A relation can be any string. Resource The source subelement or composite subelement. Relation From The destination subelements or composite subelements for the selected composite subelement and the relationship between them. The Relation From tab contains Relation The relationship between the selected composite subelement and each of the destination subelements or composite subelements. A relation can be any string. Resource The destination subelement or composite subelement. 138 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

149 Viewing reports 1. Click the Report tab in the Resource Editor. 2. Click Apply Filter to view all reports in the database, or enter filter information to limit the number of results. The following information is displayed: Column Name Name URL Type Comment Description Displays the name of the report. Displays the universal resource locator for the report. Displays the type of the report. Displays comments on the report. Viewing thresholds 1. Click the Threshold tab in the Resource Editor. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. The following columns are displayed: Column Name Metric Group Resource isbrst isprd isbl Mode Date Stat Calc CalcVal BCrtL BCrtT BWrnL BWrnT BEvent PCrtL PCrtT PWrnL PWnrT PEvent PDef Description Formula Metric Group Name Resource Name Burst Type Violation Period Type Violation Baseline Threshold Type Violation Threshold mode (Under, Over, or band) Date Statistic mode (raw, min, max, avg, sum, count) Calculation mode (Standard, Normalized, Scale) Threshold value (for Calculation Scale) Burst Critical Level Burst Critical Time Burst Warning Level Burst Warning Time Burst Event Generation Period Critical Level Period Critical Time Period Warning Level Period Time Period Event Generation Period Definition Chapter 10. Editing resources 139

150 Column Name MaxNbDay MinNbDay blcalcmode blmode bltime bltrap blupper bllower Description Baseline Threshold Maximum Number of Days Baseline Threshold Minimum Number of Days Baseline Calculation Mode (Previous Days, Previous Same Day of Week) Baseline Threshold Mode (Under, Over, Band) Baseline Threshold Time Limit Baseline Threshold Event Generation (No, Yes) Baseline Threshold Upper Limit Baseline Threshold Lower Limit Exporting resources Explains how to export resources for use with another Tivoli Netcool Performance Manager DataMart installation. You can export elements, subelements, composite subelements, and subelement groups. Displaying all resources in the Resource Editor can take a significant amount of time in large deployments. For large deployments, always use the filter to avoid displaying all resources. About this task To export resources, follow these steps: 1. Click the Element, Sub-Element, orsub-element Group tab in the Resource Editor. 2. Click Apply Filter to view all resources in the database, or enter filter information to limit the number of results. 3. Select the resources to export and choose Export from the File menu. The resources available for exporting are displayed according to their filters. 4. Click Folder to specify the destination location for the export files. 5. Enter a name for the export file in the File name text box. The file name extension is.elt for elements,.se for subelements, and.segp for subelement groups. 6. Click Save to export the file. A message box displays when the export process completes. 7. Click Close. 140 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

151 Importing resources Adding resources Explains how to import elements, subelements, composite subelements, and subelement groups. The file name extensions differ depending on the resource you are importing. Displaying all resources in the Resource Editor can take a significant amount of time in large deployments. For large deployments, always use the filter to avoid displaying all resources. About this task To import elements or subelements, follow these steps: 1. Click the Element tab or the Sub-Element tab. 2. Click Apply Filter to view all elements or subelements in the database, or enter filter information to limit the number of results. 3. Select Import from the File menu. The Import dialog box displays. 4. Click Folder to specify the source location for the import files. The file name extension is.elt for elements,.se for subelements, and.segp for subelement groups. 5. Click Open to import the file. 6. Click Details to view a detailed status on the import procedure. A message box opens when the import process completes. 7. Click Close. Explains how to add elements, subelements, reports, and thresholds. Displaying all resources in the Resource Editor can take a significant amount of time in large deployments. For large deployments, always use the filter to avoid displaying all resources. Adding elements 1. Click the Element tab. 2. Click Apply Filter to view all elements in the database, or enter filter information to limit the number of results. 3. Click an element name as a base for the new element. 4. Select Add from the Edit menu or right-click the element name and select Add from the menu. The Add Element dialog box opens. 5. Enter the following information for the new element: Field Name Profile Collector Description Specifies the name of the element. Select the name of the inventory profile used to discover this element. For more information, see the Installing Tivoli Netcool Performance Manager - Wireline Component. Select the collector number assigned to this element. Chapter 10. Editing resources 141

152 Field sysdesc Type Description Select a descriptive textual name for the element. Select the type of the element: snmp Defines an element for SNMP collections. default_snmp Used for SnmpConf. star_snmp Used for SnmpConf (@IPrange). import Defines a host with imported data. No SNMP collections are available. Comment Specifies descriptive comments about the element. 6. Click OK to accept your changes. 7. Click Close to exit the message box. Adding subelements 1. Click the Sub-Element tab. 2. Click Apply Filter to view all subelements and composite subelements in the database, or enter filter information to limit the number of results. 3. Click a subelement or composite subelement name. 4. Select Add from the Edit menu or right-click the element name and select Add from the menu. The Add Sub-Element dialog box opens. 5. Enter the following information for the new subelement: Field Name Label Family Element Instance Invariant Description Specifies the name of the subelement or composite subelement. Specifies a descriptive comment for the subelement or composite subelement. Select the name of the family for the subelement or composite subelement. Specifies the name of the element for the subelement or composite subelement. Specifies the name of the instance for the subelement or composite subelement. Specifies the invariant entity associated with the subelement or composite subelement. 6. Click OK to accept your changes. 7. Click Close to exit the message box. 142 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

153 Adding composite subelement relations 1. Click the Sub-Element tab. 2. Click Apply Filter to view all subelements in the database, or enter filter information to limit the number of results. 3. Click a composite subelement name. 4. Click Detail to display the list of properties associated with the selected composite subelement. 5. Click Relation To or Relation From tab to display the relation information. 6. Select Add from the Edit menu or right-click the element name and select Add from the menu. The Add Sub-Element dialog box opens. 7. Enter the following information for the new subelement or composite subelement: Field Relation Name Label Element Instance Invariant Family Description Specifies the name of the subelement or composite subelement relation. Specifies the name of the subelement or composite subelement. Specifies a descriptive comment for the subelement or composite subelement. Specifies the name of the element for the subelement or composite subelement. Specifies the name of the instance for the subelement or composite subelement. Specifies the invariant entity associated with the subelement or composite subelement. Select the name of the family for the subelement or composite subelement. 8. Click OK to accept your changes. 9. Click Close to exit the message box. Adding reports 1. Click the Report tab. 2. Click Apply Filter to view all reports in the database, or enter filter information to limit the number of results. 3. Click a report name. 4. Select Add from the Edit menu or right-click the report name and select Add from the menu. The Add Report dialog box opens. 5. Enter the following information for the new report: Field Name URL Type Data Description Specifies the name of the report. Specifies the universal resource locator for the report. Select the type of the report. Specifies the data displayed in the report. Chapter 10. Editing resources 143

154 Field Comment Description Specifies comments on the report. 6. Click OK to accept your changes. 7. Click Close to exit the message box. Adding thresholds Explains how to add new thresholds. A threshold is a value that is compared against metrics to determine if the metrics exceed or drop below a critical limit. Results appear in Tivoli Netcool Performance Manager DataView reports. You must enter values in several tabs to create a valid threshold. About this task Before you can add a threshold, you need to set thresholds. For more information, see Command Line Interface Reference. Adding resource and metric threshold parameters 1. Click the Threshold tab. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name. 4. Select Add from the Edit menu or right-click the threshold name and select Add from the menu. The Add Threshold dialog box opens. 5. Enter the following information for the new threshold: Field Metric Group Sub-Element Description Specifies the formula name associated with the threshold. Specifies the subelement group associated with the threshold. Specifies the subelement name associated with the threshold. 6. Click OK to accept your changes. Adding threshold mode parameters 1. Click the Threshold tab. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name. 4. Select Add from the Edit menu or right-click the threshold name and select Add from the menu. The Add Threshold dialog box opens. 5. Click the Static Threshold tab. 6. Click the Mode tab. Enter the following information for the new threshold: 144 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

155 Field Effective date Mode Description Specifies the effective date of action for the threshold. Setting the date in the past does not cause reprocessing of data but might cause thresholds to display on reports. Select a threshold mode for the threshold from the following: Under Over Violation if data value below threshold value (either warning or critical). Violation is data value is over threshold value (either warning or critical). Statistic mode band Violation if data is not between the values. Select a statistic mode for the threshold from the following: raw Raw data from collectors. min, max, avg, sum, count Data from aggregations. Calculation mode Calculation value Select a calculation mode for the threshold from either Standard, Normalized, or Scaled. Specifies the calculation value for the threshold if you selected Scaled as the Calculation mode. 7. Click OK to accept your changes. Adding threshold burst parameters A burst threshold removes the natural network bursts by evaluating how many times in a row the violations occurred over a certain period of time. 1. Click the Threshold tab. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name. 4. Select Add from the Edit menu or right-click the threshold name and select Add from the menu. The Add Threshold dialog box opens. 5. Click the Static Threshold tab. 6. Click the Burst tab. 7. Select the Enable Threshold check box. 8. Enter the following information for the new threshold: Field Warning level Critical level Description Specifies the level of the warning threshold for BURST thresholds. NULL indicates that the threshold is not defined. Specifies the level of the critical threshold for BURST thresholds. NULL indicates that the threshold is not defined. Chapter 10. Editing resources 145

156 Field Event generation Warning time Critical time Description Select whether to generate events for the BURST threshold. Specifies the time limit (in seconds) for warning BURST thresholds. NULL indicates that the threshold is not defined. "0s" indicates that the threshold is violated when the metric exceeds the threshold. For example, the input format: 1d 2h 3m 4s equals a duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Specifies the time limit (in seconds) for critical BURST thresholds. NULL indicates that the threshold is not defined. "0s" indicates that the threshold is violated when the metric exceeds the threshold. For example, the input format: 1d 2h 3m 4s equals a duration of 1 day, 2 hours, 3 minutes, and 4 seconds. 9. Click OK to accept your changes. Adding threshold period parameters A period threshold involved the concept of duration for which the threshold is violated. This duration is accumulated until the end of the expected service level period. 1. Click the Threshold tab. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name. 4. Select Add from the Edit menu or right-click the threshold name and select Add from the menu. The Add Threshold dialog box opens. 5. Click the Static Threshold tab. 6. Click the Period tab. 7. Select the Enable Threshold check box. 8. Enter the following information for the new threshold: Field Warning level Critical level Event generation Description Specifies the level of the warning threshold for PERIOD thresholds. NULL indicates that the threshold is not defined. Specifies the level of the critical threshold for PERIOD thresholds. NULL indicates that the threshold is not defined. Select whether to generate events for the PERIOD threshold. 146 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

157 Field Warning time Critical time Period Definition Description Specifies the time limit (in seconds) for warning PERIOD thresholds. NULL indicates that the threshold is not defined. "0s" indicates that the threshold is violated when the metric exceeds the threshold. For example, the input format: 1d 2h 3m 4s equals a duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Specifies the time limit (in seconds) for critical PERIOD thresholds. NULL indicates that the threshold is not defined. "0s" indicates that the threshold is violated when the metric exceeds the threshold. For example, the input format: 1d 2h 3m 4s equals a duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Select a period definition for the threshold as either Day, Week, Month, or All. All period indicates that the Complex Metrics Engine (CME) uses the period of the aggregation tables. 9. Click OK to accept your changes. Adding baseline threshold parameters 1. Click the Threshold tab. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name. 4. Select Add from the Edit menu or right-click the threshold name and select Add from the menu. The Add Threshold dialog box opens. 5. Click the Baseline Threshold tab. 6. Select the Enable Threshold check box. 7. Enter the following information for the new threshold: Field Max # of days Min # of days Calculation Sensitivity (upper) Sensitivity (lower) Description Specifies the maximum number of days used to calculate the baseline threshold. Specifies the minimum number of days used to calculate the baseline threshold. Select the baseline calculation mode from either PreviousDays or PrevSameDayofWeek. Enter the upper threshold limit (number of standard deviations above the baseline) that must be violated before generating an event. Enter the lower threshold limit (number of standard deviations below the baseline) that must be violated before generating an event. Chapter 10. Editing resources 147

158 Field Permitted time outside baseline Event generation Mode Description Enter the time limit (in minutes, hours, or days) that a threshold can be violated before generating an event. Select whether to generate events for baseline threshold violations. Select a violation mode for the threshold from the following: Under Over band Violation if data value below threshold value. Violation is data value is over threshold value. Violation if data is not between the values. 8. Click OK to accept your changes. Creating a property About this task Displaying all resources in the Resource Editor can take a significant amount of time in large deployments. For large deployments, always use the filter to avoid displaying all resources. To create a new property, follow these steps: 1. Click the Sub-Element tab. 2. Click Apply Filter to view all subelements in the database, or enter filter information to limit the number of results. 3. Select a subelement from the list. 4. Select Add Property from the Edit menu. The Add Property dialog box opens. 5. Select a name for the property in the Name field. See Property names for a description of property names. 6. Enter a value for the property in the Value field. 7. Click OK to accept your entries. Property names Properties are the attributes or characteristics of an element or subelement that defines its state, appearance, or value. These properties are installed by Tivoli Netcool Performance Manager Technology Packs. Property names for elements, subelements and report users are listed in the following tables. The Complex Metrics Engine (CME) uses numeric properties in calculations with raw data or other complex metrics. The CME determines which properties are required and loads them from the database at startup. The properties are kept in CME memory. When a property value changes in the database, the CME obtains the new value from the next database load. Table 8. Subelement Properties Property Description 148 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

159 Table 8. Subelement Properties (continued) hostname description name hostip networkarea type physicalcapacity hosturl parent hosttype parenttype class subtype protocol protocolversion model modelid version patch level country city state province A user-defined name assigned to the host upon which this resource resides. Provided during network configuration. Open-format description text used for grouping. A user-defined name that is user-defined for this entity during network configuration. This name is used only for grouping (it is not supported by DM or DV as a SE label). Physical IP address of the host upon which this resource resides. Network area (for example, BackBone, CPE) of the entity. Open-format name of the specific type of resource represented (for example, Ethernet, DS1). The maximum speed of this resource (bps). URL address assigned to the host upon which a resource resides. Open-format name or ID assigned to an entity, other than a physical host (see 'hostname' Property), that can be considered as a "parent" containing this resource. Open-format "type" classification of the device upon which this resource resides. Open-format type classification of the parent of this resource. Open-format name of the general class of resource represented (for example, device, interface, logical port, or end-to-end connection). If needed, more specific type information or the resource (NNI, UNI). Transmission protocol specific to the resource (ATM, Frame Relay, IP, IPSec, TCP, UDP, MPLS). Version of transmission protocol being used. Open-format model name of the resource. Open-format model ID string of the resource. Open-format version identification of the resource. Open-format patch level identification of the resource. The country in which the resource resides. The city, town, or municipality in which the resource resides. The state in which the resource resides. The province in which the resource resides. Chapter 10. Editing resources 149

160 Table 8. Subelement Properties (continued) region regionid location locationid status priority committedcapacity committedburstcapacity committedpeakcapacity owner ownercustomtag department departmentid network networkid privatenetwork privatenetworkid customer customerid customertype customerfacingname securityprofilemask Open-format region name in which the resource resides. Open-format ID string assigned to the region in which the resource resides. Open-format physical location name in which the resource resides. Open-format ID string assigned to the physical location in which the resource resides. Operational status of the resource (active, initializing, maintenance). Open-format priority name or code. The steady-rate bandwidth (bps) committed for transfer over a resource. The transmission rate (bps) committed for short traffic bursts (for a pre-agreed duration) over a resource. The maximum transmission rate committed for transfer over this resource. Service provider employee name/id to which this resource belongs. User-definable property for custom resource organization attributes. Service provider department to which a resource belongs. ID of the service provider department to which a resource belongs. The name of the network of which a resource is a part. The ID of the network of which a resource is a part. The name of the private (virtual) network of which this entity is a part. The ID of the private (virtual) network of which this entity is a part. The name of the specific customer that a resource services. The ID of the specific customer that this resource services. The type of customer that a resource services. Alternate name to be used for this resource in customer-facing reports, and messages. Open-format string for definition of a text mask which can be generated for SEs by a custom user group control system and used within rule conditions to organize user groups' access to resource views. 150 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

161 Table 8. Subelement Properties (continued) operation timeout sourceip sourceurl sourceport destip desturl destport corbaport targetdirectory path tablespace tablespaceclass aggregationset channel channeltablesettype measurementinterval For monitor probes, such as RMON. The test operation being executed. For monitor probes, such as RMON. The timeout duration (seconds) for target response. For unidirectional entities (end-to-end simplex connections, network test probes). The IP address of the originating side. For unidirectional entities (end-to-end simplex connections, network test probes) the URL of the originating side. For unidirectional entities (end-to-end simplex connections, network test probes). The IP port used on the originating side. For unidirectional entities (end-to-end simplex connections, network test probes). The IP address of the terminating side. For unidirectional entities (end-to-end simplex connections, network test probes). The URL of the terminating side. For unidirectional entities (end-to-end simplex connections, network test probes). The IP port used on the terminating side. The number identifying the CORBA port this entity uses. File system directory to which this entity delivers processed data. Directory path within which this entity resides. Name of the table space in which this table resides. Aggregation characteristics of the table space of which this table is part. For raw data: NRAW. For resource aggregations "1{D,WM}RA. For group aggregations: 1{D,W,M}GA. Timezone applied to this entity. ID of the Tivoli Netcool Performance Manager channel of which this entity is part. Type of Channel Table Set of which this table is part: Current-"H0"; Recent-"H1"; Ancient-"H2"; Current to Recent Staging-"S0"; Recent to Ancient Staging-"S1" The duration of time (seconds) over which raw statistics from this resource are computed and possibly pre-aggregated by that resource or by an intermediate management system. This property also can be used in network monitoring probe implementations to represent the configured amount of time wait between probe test executions. Chapter 10. Editing resources 151

162 Table 8. Subelement Properties (continued) measurementsubinterval The duration of time (seconds) over which raw statistics from this resource are subaggregated intra-period (for example, for peak values within the overall measurement interval). Also can be used to represent the duration that multi-sample network probes wait between each resend within a single probe execution. Table 9. DataView User Properties Property DV_UserTimeZone DV_UserShowCurrentPeriod DV_UserProfile DV_UserResourceName DV_UserLoginName DV_UserName DV_UserCustomLogoFile Description Defines the default time zone to be used for the user whenever a group that has not been assigned it's own time zone is viewed in the portal. Controls access to active-period report viewing. If undefined or set to "true:", the user is allowed to view reports for the current, active, time period. If set to "false", the user cannot view reports for the current period. Defines the general user type for control of certain security options. Valid settings include the following: v NOC - Network Operations Center user, few restrictions. v PSLA - Proactive Service Level Agreement personnel, moderate restriction. v SLA - users, highest restrictiveness. Defines which subelement name definitions must be used for SE labels displayed to the particular user. Valid settings include the following: v 1 - Use the SEs' internal ALIAS field values (also dubbed "SE Labels"). v 2 - Use the SEs' internal NAME field values. v Use the value defined in the "customerfacingname" Property for each SE. DataView user-scope property that can be set with the login name attributed to a DataView user. This property is used for informational display on reporter summary headings only. DataView user-scope property that can be set with the name attributed to a DataView user. This property is used for informational display on reporter summary headings only. DataView user-scope property that can be set with a link to an image file statically defining a custom graphic to be displayed on reporter summary headings. 152 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

163 Modifying resources Explains how to modify elements, subelements, reports, and thresholds by using Resource Editor. Note: Displaying all resources in the Resource Editor can take a significant amount of time in large deployments. For large deployments, always use the filter to avoid displaying all resources. Modifying an element 1. Click the Element tab. 2. Click Apply Filter to view all elements in the database, or enter filter information to limit the number of results. 3. Click an element name that you want to modify. 4. Select Update from the Edit menu or right click the element name and select Update from the popup menu. The Update Element dialog box opens. 5. Change the following information for the element: Field Name Profile Collector sysdesc Type Description Specifies the name of the element. Select the name of the inventory profile used to discover this element. For more information, see the Installing Tivoli Netcool Performance Manager - Wireline Component. Select the collector number assigned to this element. Select a descriptive textual name for the element. Select the type of the element: snmp Defines an element for SNMP collections. default_snmp Used for SnmpConf. star_snmp Used for SnmpConf (@IPrange). import Defines a host with imported data. No SNMP collections are available. Comment State Specifies descriptive comments about the element. Select the state of the element: on off Indicates that the element is visible in the graphical user interface. Indicates that data collection on the element is stopped and that the element is no longer visible in the graphical user interface. Origin User Specifies the method used to add the element to the database. Specifies the user who created the element. Chapter 10. Editing resources 153

164 Field Date Description Specifies when the element was created or modified. 6. Click OK to accept your modifications. Modifying a subelement About this task To modify a subelement or composite subelement, follow these steps: 1. Click the subelement tab. 2. Click Apply Filter to view all subelements and composite subelements in the database, or enter filter information to limit the number of results. 3. Click the name of the subelement or composite subelement that you want to modify. 4. Select Update from the Edit menu or right click the element name and select Update. The Update subelement dialog box opens. 5. Update the following information: Field Name Label Element Instance Invariant Family State Description Specifies the name of the subelement or composite subelement. Specifies a descriptive comment for the subelement or composite subelement. Specifies the name of the element for the subelement or composite subelement. Specifies the name of the instance for the subelement or composite subelement. Specifies the invariant entity associated with the subelement or composite subelement. Displays the name of the family for the subelement or composite subelement. Select the state of the subelement or composite subelement: on off the subelement or composite subelement is visible in the graphical user interface. data collection on the subelement or composite subelement is stopped and that the element is no longer visible in the graphical user interface. Origin User Date Specifies the method used to add the subelement or composite subelement to the database. Specifies the user who created the subelement or composite subelement. Specifies when the subelement was created or modified or composite subelement. 154 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

165 6. Click OK to accept your modifications. Modifying a report 1. Click the Report tab. 2. Click Apply Filter to view all reports in the database, or enter filter information to limit the number of results. 3. Click a report name that you want to modify. 4. Select Update from the Edit menu or right-click the element name and select Update from the menu. The Update Report dialog box opens. 5. Enter the following information for the new report: Field Name URL Type Data Comment Description Specifies the name of the report. Specifies the universal resource locator for the report. Select the type of the report. Specifies the data displayed in the report. Specifies comments on the report. 6. Click OK to accept your modifications. Modifying Thresholds About this task Resources and Metrics 1. Click the Threshold tab. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name that you want to modify. 4. Select Update from the Edit menu or right-click the threshold name and select Update from the popup menu. The Add Threshold dialog box opens. Change the following information for the threshold: Field Metric Group Sub-Element Description Specifies the formula name associated with the threshold. Specifies the subelement group associated with the threshold. Specifies the subelement name associated with the threshold. 5. Click OK to accept your changes. Chapter 10. Editing resources 155

166 Mode About this task The following thresholds are static thresholds: v Mode v Burst v Period v Baseline 1. Click the Threshold tab. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name that you want to modify. 4. Select Update from the Edit menu or right-click the threshold name and select Update from the menu. 5. Click the Static Threshold tab. 6. Click the Mode tab. The Add Threshold dialog box opens. Change the following information for the threshold: Field Effective date Mode Statistic mode Calculation mode Calculation value Description Specifies the effective date of action for the threshold. Setting the date in the past will not cause re-processing of data but may cause thresholds to display on reports. Select a threshold mode for the threshold from the following: v Under - Violation if data value below threshold value (either warning or critical). v Over - Violation is data value is over threshold value (either warning or critical). v band - Violation if data is not between the values. Select a statistic mode for the threshold from the following: v raw - Raw data from collectors. v min, max, avg, sum, count - Data from aggregations. Select a calculation mode for the threshold from either Standard, Normalized, or Scaled. Specifies the calculation value for the threshold if you selected Scaled as the Calculation mode. 7. Click OK to accept your changes. 156 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

167 Burst About this task A burst threshold removes the natural network bursts by evaluating how many times in a row the violations occurred over a certain period of time. To modify threshold burst parameters, follow these steps: 1. Click the Threshold tab. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name that you want to modify. 4. Select Update from the Edit menu or right-click the threshold name and select Update from the menu. 5. Click the Static Threshold tab. 6. Click the Burst tab. The Add Threshold dialog box opens. Change the following information for the threshold: Field Warning level Critical level Event generation Warning time Critical time Description Specifies the level of the warning threshold for BURST thresholds. NULL indicates that the threshold is not defined. Specifies the level of the critical threshold for BURST thresholds. NULL indicates that the threshold is not defined. Select whether to generate events for the BURST threshold. Specifies the time limit (in seconds) for warning BURST thresholds. NULL indicates that the threshold is not defined. "0s" indicates that the threshold is violated when the metric exceeds the threshold. For example, the input format: 1d 2h 3m 4s equals a duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Specifies the time limit (in seconds) for critical BURST thresholds. NULL indicates that the threshold is not defined. "0s" indicates that the threshold is violated when the metric exceeds the threshold. For example, the input format: 1d 2h 3m 4s equals a duration of 1 day, 2 hours, 3 minutes, and 4 seconds. 7. Click OK to accept your changes. Period About this task A period threshold involved the concept of duration for which the threshold is violated. This duration is accumulated until the end of the expected service level period. Chapter 10. Editing resources 157

168 To modify threshold burst parameters, follow these steps: 1. Click the Threshold tab. 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name that you want to modify. 4. Select Update from the Edit menu or right-click the threshold name and select Update from the menu. 5. Click the Static Threshold tab. 6. Click the Period tab. The Add Threshold dialog box opens. Change the following information for the threshold: Field Warning level Critical level Event generation Warning time Critical time Period Definition Description Specifies the level of the warning threshold for PERIOD thresholds. NULL indicates that the threshold is not defined. Specifies the level of the critical threshold for PERIOD thresholds. NULL indicates that the threshold is not defined. Select whether to generate events for the PERIOD threshold. Specifies the time limit (in seconds) for warning PERIOD thresholds. NULL indicates that the threshold is not defined. "0s" indicates that the threshold is violated when the metric exceeds the threshold. For example, the input format: 1d 2h 3m 4s equals a duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Specifies the time limit (in seconds) for critical PERIOD thresholds. NULL indicates that the threshold is not defined. "0s" indicates that the threshold is violated when the metric exceeds the threshold. For example, the input format: 1d 2h 3m 4s equals a duration of 1 day, 2 hours, 3 minutes, and 4 seconds. Select a period definition for the threshold as either Day, Week, Month, or All. All period indicates that the Complex Metrics Engine (CME) uses the period of the aggregation tables. 7. Click OK to accept your changes. Baseline Threshold About this task To modify baseline threshold parameters, follow these steps: 1. Click the Threshold tab. 158 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

169 2. Click Apply Filter to view all thresholds in the database, or enter filter information to limit the number of results. 3. Click a threshold name that you want to modify. 4. Select Update from the Edit menu or right-click the threshold name and select Update from the menu. 5. Click the Static Threshold tab. 6. Click the Baseline Threshold tab. The Add Threshold dialog box opens. Change the following information for the threshold: Field Max # of days Min # of days Calculation Sensitivity (upper) Sensitivity (lower) Permitted time outside baseline Event generation Mode Description Specifies the maximum number of days used to calculate the baseline threshold. Specifies the minimum number of days used to calculate the baseline threshold. Select the baseline calculation mode from either PreviousDays or PrevSameDayofWeek. Enter the upper threshold limit (number of standard deviations above the baseline) that must be violated before generating an event. Enter the lower threshold limit (number of standard deviations below the baseline) that must be violated before generating an event. Enter the time limit (in minutes, hours, or days) that a threshold can be violated before generating an event. Select whether to generate events for baseline threshold violations. Select a violation mode for the threshold from the following: v Under - Violation if data value below threshold value. v Over - Violation is data value is over threshold value. v band - Violation if data is not between the values. Deleting resources 7. Click OK to accept your changes. Explains how to delete the following resources from the database: v Elements and subelements v Sub-element groups v subelements within groups v Properties associated with elements and subelements Note: When you delete an element, you delete the associated subelements. When you delete a property, you delete only the property. Displaying all resources in the Resource Editor can take a significant amount of time in large deployments. For large deployments, always use the filter to avoid displaying all resources. Chapter 10. Editing resources 159

170 Deleting elements or subelements 1. Click the Element or the Sub-Element tab. 2. Click Apply Filter to view all resources in the database, or enter filter information to limit the number of results. 3. Click the resource names you want to delete. 4. Click the Delete icon in the toolbar. A confirmation message opens. 5. Click Yes to continue, or No to cancel. Deleting subelement groups 1. Click the Sub-Element Group tab in Resource Editor. 2. Click the subelement group to expand it and select the name of the group. The subelements contained in the group appear in the right pane. 3. Click the Delete icon in the toolbar. A confirmation message opens. 4. Click Yes to continue, or No to cancel. Deleting resources within groups 1. Click the Sub-Element Group tab in the Resource Editor. 2. Click the Sub-Element group name to expand it. 3. Click the group name in the left pane to display the subelements in the right pane. 4. Click a resource name to select it, or click the magnifying glass icon to open the Find dialog box to search by name. 5. Click the Delete icon in the toolbar. A confirmation message opens. 6. Click Yes to delete the resource, or No to cancel. Deleting properties 1. Click the Element or Sub-Element tab in the Resource Editor. 2. Click Apply Filter to view all resources in the database, or enter filter information to limit the number of results. 3. Select a resource whose properties you want to delete. 4. Click Detail to display the properties table. 5. Click the property name you want to delete. 6. Click the Delete icon in the toolbar. A confirmation message opens. 7. Click Yes to delete, or No to cancel. 160 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

171 Deleting composite Subelement relations Deploying reports 1. Click the Sub-Element tab. 2. Click Apply Filter to view all subelements in the database, or enter filter information to limit the number of results. 3. Click a composite subelement name. 4. Click Detail to display the list of properties associated with the selected composite subelement. 5. Click Relation To or Relation From tab to display the relation information. 6. Right-click a relation in the list and select Delete. 7. Click Yes to confirm your choice. Explains how to manually deploy reports using Resource Editor. 1. Click the Report tab. 2. Click Apply Filter to view all reports in the database, or enter filter information to limit the number of results. 3. Click the Report SE Group tab. 4. Expand a group to view a list of the rules applied to and select a rule to display any reports currently deployed against it. 5. Click the Report tab to display the list of reports again. 6. Click the report name you want to deploy to highlight it. 7. Copy the report by pressing Ctrl + C. 8. Click the Report SE Group tab to select it again. 9. Click the group name in the left pane to highlight it. 10. Press Ctrl + V to paste the report into the frame. You are prompted to confirm your choice. 11. Click Yes to continue. The copied report displays in the right pane. 12. Move the cursor to the left pane and scroll up to select SUB-ELEMENTS. 13. Right-click and select AutoGrouping from the pull down menu. A confirmation prompt opens. 14. Click Yes to continue. 15. Click Close to exit the message box or click Details to view a description of any errors or warnings. Chapter 10. Editing resources 161

172 162 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

173 Chapter 11. Viewing collected data Explains how to view various collected data. Viewing graphical charts for files Explains how to view a list of curves contained in a file, which you can then display in graphical form. About this task To view curves, follow these steps: 1. Click Data Viewer in the Data Manager tab. The following windows appears: The foreground window lets you select data to display. The background window displays the data in graphical form. 2. Select a file from the upper list. A list of curves appear in the bottom list. 3. Select one or more curves that you want to display in graphical form. 4. Click Apply to accept your selections. Copyright IBM Corp. 2012,

174 Viewing graphical charts for subelements Explains how to view graphical charts for subelements. About this task To view graphical charts for subelements, follow these steps: 1. Click Data Viewer in the Data Manager tab. 2. Click the Sub-elements tab. 3. Click Apply Filter to view all subelement names in the left pane, or enter filter information to limit the number of results. Note: You can sort columns by clicking on the column titles. 4. Select one or more subelements from the list in the left pane. Use the Ctrl key to make multiple selections. 5. Select one or more associated formulas from the list in the right pane. 6. Select a time range in the Data Range Selection group from the following: Current - Selects currently collected data. Recent - Select most recent collected data. History - Select historical data. 7. Select a data type in the Data Type group from the following: Raw - Provides raw collected data. Min - Provides minimum values of the raw data according to the aggregation type that you select. Max - Provides maximum values of the raw data according to the aggregation type that you select. Sum - Provides the sum of the raw data according to the aggregation type you select. Count - Provides the number of raw data according to the aggregation type you select. 8. Select an aggregation type in the Aggregation type list from the following: Per day - Aggregations per day Per week - Aggregations per week Per month - Aggregations per month 9. Select an aggregation set in the Aggregations Set list from the following: GMT - Greenwich Mean Time, which is the mean solar time of the meridian of Greenwich used as the prime basis of standard time throughout the world. AggSet 1 to AggSet 6 - An Aggregation Set defines an offset from GMT and is associated with groups. This feature can have a different name if customized. 10. Click Apply to accept your selections. One or more graphical charts appear in the Data Viewer window. What to do next See the next sections to save, print, and configure graphs. 164 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

175 Viewing graphical charts for subelement groups Saving a graph Explains how to view graphical charts for subelements groups. 1. Click Data Viewer in the Data Manager tab. 2. Click the Sub-Element Groups tab. 3. Select one or more subelement groups from the list in the left pane. 4. Select one or more formulas from the list in the right pane. 5. Select a time range in the Data Range Selection group from the following: Current - Selects currently collected data. Recent - Selects recently collected data. History - Select historical data. 6. Select one or more data types in the Data Type group from the following: Raw - Provides raw collected data. Min - Provides minimum values of the raw data according to the aggregation type that you select. Max - Provides maximum values of the raw data according to the aggregation type that you select. Sum - Provides the sum of the raw data according to the aggregation type you select. Count - Provides the number of raw data according to the aggregation type you select. 7. Select an aggregation type in the Aggregation type list from the following: Per day - aggregations per day Per week - aggregations per week Per month - aggregations per month 8. Select an aggregation set in the Aggregations Set list from the following: GMT - Greenwich Mean Time, which is the mean solar time of the meridian of Greenwich used as the prime basis of standard time throughout the world. AggSet1 to AggSet 6 - An Aggregation Set defines an offset from GMT and is associated with groups. Explains how to save a graph 1. Select Save from the File menu. 2. Select the timestamp from one of the following: GMT - Saves the data in Greenwich Mean Time, which is the mean solar time of the meridian of Greenwich used as the prime basis of standard time throughout the world. Local - Saves the graph in the local time for your location. 3. Select the file type in the Type list from one of the following: Bin format - Compacted ASCII format. Only the date and measure value are preserved in the data lines. Chapter 11. Viewing collected data 165

176 Printing a graph Configuring graphs BOF format - Binary Object Format provides an extensible, space and time efficient storage format for storing Tivoli Netcool Performance Manager objects in flat files. This format provides a high-performance format for transferring information between distributed Tivoli Netcool Performance Manager subsystems in a store and forward environment. 4. Specify where to save the graph in the File box or click Browse to find the location. 5. Click OK to accept your selections. Explains how to set up printing for graphical charts in the Data Viewer. About this task To set up printing, follow these steps: 1. Select Print from the File menu. 2. Select a paper format, width, and height. 3. Select an orientation (Portrait or Landscape). 4. Select where to position the graph on the sheet of paper (Center or Origin). 5. Click Apply or OK to accept your selections. Explains how to configure a graph. Displaying crosshairs 1. Right-click an area inside the graph and select the Configuration menu item. 2. Click Display CrossHair in the General tab. 3. Select a line width for the crosshairs from the Width list. 4. Select a dash format for the crosshairs from the Dash list. 5. Select a color for the crosshairs from the Color list menu. 6. Click OK to accept your selections. Crosshairs appears in the graph. For example: 166 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

177 Displaying a grid 1. Right-click an area inside the graph and select the Configuration menu item. 2. Click the General tab. 3. Click the Display Grid in the General tab. 4. Click Set Grid on minor ticks if you want the grid to display on minor axis marks. 5. Select the desired line width for the grid from the Width list. 6. Select a dash format for the grid from the Dash list. 7. Select a color for the grid from the Color list. 8. Click Apply or OK to accept your selection. A grid appears in the graph. Configuring a title 1. Right-click an area inside the graph and select the Configuration menu item. 2. Click the General tab. 3. Click Configure Title in the General tab. 4. Select a font style for the title from the Font list. 5. Select a weight for the title from the Weight list. 6. Select a slant for the title from the Slant list. 7. Select a point size for the title from the Size list. 8. Select a color for the title from the Color box. 9. Click OK to accept your selections. A title appears in the graph. Chapter 11. Viewing collected data 167

178 Configuring the X-Axis 1. Right-click an area inside the graph and select the Configuration menu item. 2. Click the Axis tab and select X axis. 3. Enter a title for the X axis in the Title box. 4. Select a line width for the X axis from the Width list. 5. Select a color for the X axis from the Color list. 6. Select a date format to be displayed in the X axis area of the graph from the Scale group. The default setting is "MM/dd/nhh:mm" (minute, day, hour minute). You can enter any character you desire such as forward slash (/) colons (:), semicolons (;). The following keypad options are available: Year = YYYY Month = MM Week=ww Day=dd Hour = hh Minute = mm CR = \n is carriage return to next line 7. Click OK to accept your selections. The X axis in the graph is configured accordingly. Customizing the Y-Axis 1. Right-click an area inside the graph and select the Configuration menu item. 2. Click the Axis tab and select Y axis. 3. Select Y Axis in the Axis tab. 4. Enter a title for the Y axis in the Title box. 5. Select a line width for the Y-axis from the Width list. 6. Select a color for the Y-axis from the Color list. 7. Select a scale type in the Scale group from the following: Linear - displays the graph using straight lines. Logarithmic - displays the graph in powers of ten (ten times more lines than the Linear option). 8. Click OK to accept your selection. The Y-axis in the graph is configured accordingly. Configuring curves 1. Right-click an area inside the graph and select the Configuration menu item. 2. Click the Curves tab. 3. Select a curve that you want to modify from the Curve list. 4. Select the desired line width for the curve from the Width list. 5. Select a dash format for the curve from the Dash list. 6. Select a symbol format from the Symbol list. 7. Select a color from the Color box to change the color of the graphical points. 168 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

179 8. Specify the legend by entering the appropriate label in the Legend field. 9. Select the curves displayed from the Curves to Display list. 10. Click Apply or OK to accept your selections. Configuring a graph legend 1. Right-click an area inside the graph and select the Configuration menu item. 2. Click the Legend tab. 3. Click Yes to display the legend. 4. Select the position for the legend in the Position list from the following: Top - Top of graph Bottom - Under graph Right - Right of graph Left - Left of graph Plot Area - In the graph 5. Select a font for the legend from the Font list to choose a font style for the title. 6. Select a weight for the legend from the Weight list. 7. Select a slant for the legend from the Slant list. 8. Select a point size for the legend from the Size list. 9. Select a color for the legend from the Color box 10. Click OK to accept your selections. A legend appears in the graph. Chapter 11. Viewing collected data 169

180 170 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

181 Chapter 12. Viewing the list of collectors Explains how to view information about both active and non-active collectors using the Collector Information Tool. About this task The collectinfo command-line interface (CLI) command launches the Collector Information Tool from the command line. For more information, see the Command Line Interface Reference. To view the collectors list, follow these steps: 1. Click Collector Information from the Monitor tab. This window lists all the collectors loaded from the database. 2. Select a collector from the list, then click the other tabs to review specific collector information. The following collector information is available: Column Number Status Server Port Type Installation Directory Description Indicates the collector identifier number. Indicates the collector status. For example, "Running" or "Not Running." Indicates the host name or IP address of the system on which the collector is installed. Indicates the communication port number for the collector. Indicates the collector type. Indicates the directory where the collector is installed. Viewing collector information Explains how to view detailed information about a collector. The GUI does not support start or stop and log path change for remote collectors. 1. Click Collector Information from the Monitor tab. 2. Select a collector from the list. 3. Click the Collector Information tab. The State group displays the following information: Item Green traffic light Yellow traffic light Description Indicates that the collector is active and operational. Indicates that the collector is in a transitory state between start-up and shutdown. This is a temporary state. Copyright IBM Corp. 2012,

182 Item Red traffic light Refresh Interval Current debug level Version Server Port Connections SysUpTime Current Time Description Indicates that the collector is not active or operational. Indicates the frequency in which the information displayed in the tabs is refreshed (in seconds). Indicates the current debug level of the collector. "0" indicates a minimal debug. The level should be set to "0"; a level of "1" or more is for troubleshooting purposes. Displays the version date and operating system for the collector. Displays the name of the computer on which the collector is running. Displays the port number that the collector uses to communicate with Tivoli Netcool Performance Manager DataMart. Displays the number of clients connected to the collector. Displays the amount of time that the collector has run without interruption (in days, hours, minutes, and seconds). Displays the day, month, year, and time of day as set on the server where the collector is running (dependent on your time zone). The time shown here can be different from local time. This is the time that Tivoli Netcool Performance Manager DataMart uses to schedule data collection, if you declare a calendar from 8 am to 8 pm. The Actions group displays the following information: Item Refresh interval Start/Stop button Description Modifies the current refresh value frequency. Launches or shuts down the local collector. 172 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

183 Item Current tab Description Displays the following options: Note: Tivoli Netcool Performance Manager DataMart does not permanently save your selections in the Current tab. v Debug level - Modifies the debug level of the collector. Contact technical support at IBM for more information about debugging. v Log Path - Saves the debug information file (ServReqDaemonxxxx.log) to a specific path. You can use the Directory Selection button to select the log path. The default log directory is $PVMHOME/log. v Date in file - Displays the creation date in the log file name. Select Yes to activate this option. For example, pvmd_ _16348.log. v Channel in file - Displays the request number in the log file name. Selecting this option creates one file per request ID. Select Yes to activate this option. Note: The Channel in file option creates multiple files (one for each request). Tivoli Netcool Performance Manager DataMart permanently saves and stores your selections in the configuration file. For example, in $PVMHOME/conf/pvmd.log on the server system. Viewing scheduler information The Scheduler maintains the internal list of the requests for data. The Scheduler regularly scans the list to determine whether requests are executed placed into a waiting queue. A task placed in a waiting queue is flagged as "READY." You can view statistics compiled by the collector about the planning of requests. 1. Click Collector Information from the Monitor tab. 2. Select a collector from the list. 3. Click the Scheduler tab. The Scheduler window displays the following information: Item Collections Priority Mode Description Indicates the number of Collections Priority Mode requests on the current collector. Chapter 12. Viewing the list of collectors 173

184 Item Execute requests Items Processed Items Scheduled Queue Max Size Description Indicates the number of requests being executed on the collector. v Execute external requests (Nb) [immediate] - Indicates the number of external requests being executed on the collector. v Execute internal requests (Nb) [immediate] - Indicates the number of internal requests being executed on the collector. Indicates the collector activity level. The activity level is measured in number of requests executed per second over a specific time period. v Items Processed Average (Nb) [last 24 hours] - Indicates the number of requests executed during the last 24 hours. v Items Processed Average (Nb) [last hour] - Indicates the number of requests executed during the last hour. v Items Processing Rate (Nb/s) [last 24 hours] - Indicates the request execution rate per second during the last 24 hours. You can compare this activity level with results on comparable systems to evaluate performance. v Items Processing Rate (Nb/s) [last hour] - Indicates the request execution rate per second during the last hour. This rate is similar to the rate for the last 24 hours but is more sensitive to variations during collections over longer periods (longer than one hour). Requests that need to be executed. The Scheduler scans the list to determine the requests to execute or to place in the waiting queue. v Items Scheduled (Nb) [immediate] indicates the number of requests generated in this list. v Max Items Scheduled (Nb) [immediate] indicates the maximum configuration value for the request list size. Third of the three waiting queues where a thread searches for a request number to execute. v Queue Max Size (Nb) [last 24 hours] indicates the maximum size attained by the queue during the last 24 hours. v Queue Max Size (Nb) [last hour] indicates the maximum size attained by the queue during the last hour. v Queue Size (Nb) [immediate] indicates the current size of the queue. 174 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

185 Item Threads internal errors (Nb) [cumul] Description Collector activity creates threads. The collector verifies it can activate a thread each time it executes a collection or launches a command. If it cannot activate a thread, no collector activity occurs and reliability is diminished. v Threads (Nb) [immediate] - Indicates the number of threads created through collector activity. This is a realtime counter. The value can change quickly from 1 to MaxThreadedItems. You can tune this value in the registry.conf file in the following location: $PVMHOME/conf/registry.conf v Threads Availability (%) [last 24 hours] - Indicates collector reliability during the last 24 hours. v Threads Availability (%) [last hour] - Indicates collector reliability during the last hour. Indicates the number of memory errors detected and corrected. This counter needs to remain at zero. If it is not at zero, restart the collector. Viewing data manager information The Data Manager manages the insertion of records (measures) into the record file. It accumulates data in an internal queue, then transfers the data to the record file when the queue reaches a specified size. Each time the Data Manager transfers data it stores information about the job. 1. Click Collector Information from the Monitor tab. 2. Select a collector from the list. 3. Click the Data Manager tab. The Data Manager window displays the following information: Item Description.dat files v dat files (nb) [immediate] - Indicates the number of.dat files located in the $PVMHOME/data directory. v dat files (KB) [immediate] - Indicates the size of the.dat file. Average Storage Time Specifies the average time to store a measure in a local file. v Average Storage Time (ms) [last 24 hours] - Indicates the average processing time for a measure during the last 24 hours. v Average Storage Time (ms) [last hour] - Indicates the average processing time for a measure during the last hour. Chapter 12. Viewing the list of collectors 175

186 Item Congestion State Filesystem Measures Description Indicates the Congestion State code. Indicates file system space information: v Filesystem FSLL (KB) [immediate] - Indicates the size of the FSLL for the file system. v Filesystem available (KB) [immediate] - Indicates the available size of the file system. v Filesystem free space (KB) [immediate] - Indicates the amount of free space on the file system. v Filesystem quota (KB) [immediate] - Indicates the size of the quota for the file system. v Filesystem used (KB) [immediate] - Indicates the amount of space used on the file system. A measure is a record inserted into the record file. Each insertion is measured in time and the median value is posted. v Measures Processed Average (Nb) [last 24 hours] - Indicates the number of measures processed during the last 24 hours. v Measures Processed Average (Nb) [last hour] - Indicates the number of measures processed during the last hour. v Measures Lost (Nb) [cumul] - Indicates the number of measures that have been lost since the start of the collector. These measures were collected but were not saved. v Measures Lost (Nb) [last 24 hours] - Indicates the number of measures lost during the last 24 hours. These measures were collected but were not saved. v Measures Lost (Nb) [last hour] - Indicates the number of measures lost during the last hour. These measures were collected but were not saved. v Measures Stored (Nb) [cumul] - Indicates the total number of measures stored. For example, total number of answers from metrics requested. v Measures Stored (Nb) [last 24 hours] indicates the total number of measures stored. For example, the total number of answers from metrics requested over the last 24 hours. v Measures Stored (Nb) [last hour] indicates the total number of measures stored. For example, the total number of answers from metrics requested over the last hour. 176 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

187 Item Save Availability Description Displays the reliability of data insertion. Reliability of 100% means that all measures are correctly inserted. A reliability rate of less than 100% does not necessarily indicate a loss of measures, but should be investigated. v Save Availability (%) [last 24 hours] - Indicates the calculated insertion reliability during the last 24 hours. v Save Availability (%) [last hour] - Indicates the calculated insertion reliability during the last hour. Viewing target information Each time the collector interacts with an SNMP agent, information about the interaction is recorded. 1. Click Collector Information from the Monitor tab. 2. Select a collector from the list. 3. Click the Targets tab. The Targets window displays the following information: Item Agent SNMP Version [immediate] Average SNMP Response Time (ms) [last hour] CALC Errors (Nb) [last hour] CPU Load (Nb OIDs) [last hour] Discovery Received PDU (Nb) [last hour] Discovery Received PDU Max Size (bytes) [last hour] Discovery Received PDU Total Size (bytes) [last hour] Discovery Sent PDU (Nb) [last hour] Description Indicates the SNMP Version of the agent for the collector. Indicates the average elapsed time between the sending of the first SNMP packet and its return. Time is not calculated on the exchanged packets during the MIB browse. Indicates the number of CALC errors that occurred in the last hour. Indicates the estimated CPU load needed by the collector to handle all requests relating to this target. This measurement integrates the number of OIDs handled to solve the requests, the number of requests necessary, and the frequency of each interrogation. Indicates the number of PDUs received as part of the discovery process in the last hour. Indicates the maximum size of PDUs received as part of the discovery process in the last hour. Indicates the total size of PDUs received as part of the discovery process in the last hour. Indicates the number of PDUs sent as part of the discovery process in the last hour. Chapter 12. Viewing the list of collectors 177

188 Item Discovery Sent PDU Max Size (bytes) [last hour] Discovery Sent PDU Total Size (bytes) [last hour] Expected Measures (Nb) [last hour] Max SNMP Response Time (ms) [last hour] OID Rate (Nb/s) [last hour] Produced Measures (Nb) [last hour] Received PDU (Nb) [last hour] Received PDU Max Size (bytes) [last hour] Received PDU Total Size (bytes) [last hour] SNMP Availability (%) [last hour] SNMP Errors (Nb) [last hour] SNMP Requests (Nb) [cumul] Sent PDU (Nb) [last hour] Sent PDU Max Size (bytes) [last hour] Sent PDU Total Size (bytes) [last hour] Description Indicates the maximum size of PDUs sent as part of the discovery process in the last hour. Indicates the total size of PDUs sent as part of the discovery process in the last hour. Indicates the number of measures expected in the last hour. Indicates the maximum amount of time for an SNMP response that occurred in the last hour. Indicates the OID rate that occurred in the last hour. Indicates the number of measures produced in the last hour. Indicates the number of PDUs received in the last hour. Indicates the maximum size of PDUs received in the last hour. Indicates the total size of PDUs received in the last hour. Indicates the reliability of the interaction with SNMP agents. A value of 0% can indicate a bad community name or that the timeout value is insufficient. A value more than 0% but less than 100% is often caused by timeouts during the SNMP interaction. Indicates the total amount of errors in the SNMP protocol encountered during the interaction. An error cannot occur when the community name is correct and the timeout is correctly configured. An error signifies either an agent problem in responding to a packet or an error between the collector MIB and the MIB supported by the agent. Most often it indicates a problem with a formula. Indicates the total number of executed requests on equipment since the start of the collector. You can identify the equipment with a high rate of requests. Indicates the number of PDUs sent in the last hour. Indicates the maximum size of PDUs sent in the last hour. Indicates the total size of PDUs sent in the last hour. 178 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

189 Viewing detailed technical information You can view detailed technical information about the collector that displays all current tasks managed by the collector. 1. Click Collector Information from the Monitor tab. 2. Select a collector from the list. 3. Click the Detail Information tab. The tasks use the following format: [<number>]id <Request ID>, {CAL <calendar definition>} (<priority>) (<state>)(<type>) Where: Item <Request ID> <calendar definition> <priority> Description The ID of the tasks in the Scheduler list of tasks. Definition (period optional calendar name) and the time of the next start Valid values include the following: v Realtime v High v Normal The priority chosen here is linked to the corresponding Scheduler priority queue. See Viewing scheduler information on page 173 for details. <state> Valid values include the following: v ASLEEP - indicates that the task is set for the next execution and does not use any resources. v ACTIVE - indicates that the task is currently running. This state appears and disappears as the task processes SNMP queries. v ZOMBIE - indicates that the task is about to disappear from view. v READY - indicates that the task has reached the time of the next start but is waiting for an available thread to be executed. The task has been place in a waiting queue according to its current priority value. As soon as the task is handled by a thread, the state changes to ACTIVE. Chapter 12. Viewing the list of collectors 179

190 Item <type> Description Name of the service for this task: v ServiceSTAT - displays a list of the tasks currently running. v ServiceCRON - executes commands at different preset times. v ServiceFORM and ServiceGet - execute SNMP queries v Trgt indicates that the target host that is being queried. A target can be one of the following types: element (Elmt) sub-element (SubElmt) group of elements (ElmtGrp) group of sub-elements (SubElmtGrp) v v Form indicates the formula used for the query. Inst lists the instances impacted during the query process. Note: Formulas (PVL-Tivoli Netcool Performance Manager-Statistics) are available that monitor collector statistics. Stopping and restarting a local collector You can stop the local collector from the Collector Information Tool window. 1. Click Collector Information from the Monitor tab. 2. Select a collector from the list. 3. Click the Collector Information tab. 4. Click the Stop button in the Actions group, then confirm your choice at the prompt. 5. Click Yes to confirm. Note: To stop a remote collector, you need to connect to the system on which the collector resides and launch the pvmdmgrscript with the stop option. For example: pvmdmgr stop Restarting a local collector You can restart the local collector from the Collector Information Tool window. 1. Click Start in the Actions group, then confirm your choice at the prompt. 2. Click Yes to restart the collector. Note: To restart a remote collector, you need to connect to the machine on which the collector resides and launch the pvmdmgr script with the start option. For example: pvmdmgr start 180 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

191 Configuring watchdog for collector memory checking The watchdog for Collector Memory Checking limits the amount of memory used by a collector and restarts collectors that exceed a threshold limit. Parameters The Watchdog parameters reside in the registry.conf file located in the conf directory where Tivoli Netcool Performance Manager DataMart is installed. The Watchdog default settings are as follows: [Quallaby\PROVISO-Daemon\WatchMgr] "ActivateWatchMgr"="1" "UseErrorsCount"="1" "UseMemoryChecking"="0" "UseWatchDog"="1" [Quallaby\PROVISO-Daemon\WatchMgr\ErrorsCount] "MaxErrorsCount"="10" [Quallaby\PROVISO-Daemon\WatchMgr\MemoryChecking] "MinimalWorkingSet"=" " "MaximalWorkingSet"=" " "WorkingSetInflation"="1000" [Quallaby\PROVISO-Daemon\WatchMgr\WatchDog] "MaxPulseInterval"="250" "PulseInterval"="80" Activation of memory checking About this task To activate memory checking, you need to set the following value to 1: [Quallaby\PROVISO-Daemon\WatchMgr] "UseMemoryChecking"="1" Setting lower and upper limits There are two settings for controlling the memory size of a collector. All values are in bytes. About this task The first value is the maximum upper limit. "MaximalWorkingSet"=" " You need to tune this limit, which depends on the size of the physical memory on your system and the number of processes running. For example, if your system configuration is comprised of one collector with a remote database, you can set the upper limit size to 75 percent of the total physical memory. This means that the collector process would never uses more that 75 percent of the memory. "MinimalWorkingSet"=" " The lower limit is the threshold under which there is no check of memory. This limit is important, and should not be configured to a small value because during the boot phase of a collector, the memory is increasing rapidly, and this increase can confuse the Watchdog. Ideally, this limit should be set up to the normal memory usage of a collector. Chapter 12. Viewing the list of collectors 181

192 1. To set up this value, start a Tivoli Netcool Performance Manager process, let it run for one hour, modify the registry.conf file 2. Get the process size using the ps command. 3. Restart the collector. Setting inflation limit Each time a collector reloads a new request, it calculates the amount of memory needed to manage those requests, and each time the Watchdog is contacted, it transmits information. About this task You can control memory usage. For example: "WorkingSetInflation"="1000" The amount of memory required is called the nominal value and the real amount of memory used is called real value. If the value is greater than the value contained in the WorkingSetInflation= than the nominal amount, then the Watchdog can restart a collector. By default, this setting is set to 1000, which means 1000 percent (that is, the real value greater than 10 times of the nominal value). If the minimal value is correctly set up, then the inflation factor can be set to 130 (30 %) or 150 (50%). A small value (110) is not recommended because this limit can be reached during normal operation. This setting is only useful, if there are several processes on the system, and if a collector has to share memory with database. In this case, the inflation is preferred to the upper limit. If only one collector is on the system by itself, the upper limit should be used instead, and the inflation setting should remain at IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

193 Chapter 13. Viewing status Viewing DataMart status The Tivoli Netcool Performance Manager DataMart Status tool displays which modules are currently in use, their host system, and displays locked instances of running modules. The pvmstat command line interface (CLI) command launches the Status Tool from the command line. For more information, see the Command Line Interface Reference. Explains how to use the Tivoli Netcool Performance Manager DataMart Status tool to view the status of individual modules. Click DataMart Status in the Applications tab. The Registered Modules group displays the following information: Item Name Pid Host Display Port User Date Status Comment Description Name of the module in use. Process identification number of UNIX. Name of the host machine on which the process is being run. Name of the graphical view from which Tivoli Netcool Performance Manager DataMart was launched. Port number of the software process. The collector default port is indicates that no port number is used. Name of a Tivoli Netcool Performance Manager DataMart user running the module. Date and time that the module was launched. Indicates either a status or progress level. Provides information on the module being run. The Locked Modules group displays the following information: Item Lock Mode Locked by Description Name of the locked module. Protection level that the lock provides. 0 = Read Only 1 = Read/Write Name of the application that has locked the module (usually the module is locked by itself). Copyright IBM Corp. 2012,

194 Item Pid Host Description Process identification number of UNIX. Name of the host system on which the process is being run. The following modules do not use a collector: Mibcompiler This module processes MIB from ASNI format to IBM format (understandable by the collector). No result testing is made; therefore, there is no need for a collector. Userconf There is no connection between a collector and the users descriptions. This part of the configuration is not loaded/reloaded by a collector. Removing a lock from the database Tivoli Netcool Performance Manager DataMart locks a module when it is in use by a user to prevent others from making any changes. A lock can be set on a running module's instance either by another module, or by the module itself. About this task You can run more than one instance of a module simultaneously. The first instance sets a lock in the database to indicate to the next instance that this it is already running. The lock causes the next instance to run in "Read-Only" mode so that critical operations (for example, changing resources in the database) are under the control of the original instance. If a module is abnormally terminated, and does not unregister or unlock itself from the database, then the instance module is still displayed by the Tivoli Netcool Performance Manager DataMart Status tool even following a refreshing. To remove a lock from the database, follow these steps: Note: You cannot remove a lock that is locked by another user using this module. Use the pvmstat command line interface to remove a lock set by another user 1. Click DataMart Status in the Applications tab. The Tivoli Netcool Performance Manager DataMart Status Tool dialog box appears. 2. Select Remove Locks from the File menu. The module changes to unlocked and disappears from the Locked Modules group. 184 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

195 Chapter 14. Viewing database information Explains how to view information on the Tivoli Netcool Performance Manager DataMart database, instance, and status. Before you begin Before you view database information, ensure that libpvmextc.so is running. 1. Click Database Information in the Monitor tab. A splash screen appears followed by the ProvisoInfo Browser. 2. Click Refresh objects from the database to globally update the window with the most recent database information. 3. Click the Identification tab. The Identification tab provides the following information: Item Database Server Name Database Name Current Database User Database Release Description Name of the server where the database is installed. Name of the database. The database is the data on disk (set of files), stored in operating system files. Tivoli Netcool Performance Manager DataMart uses only one database. Current user connected to the database. For example, PV_ADMIN. For example, Oracle 11g Enterprise Edition, Release bit Production DB For example, PL/SQL Release Production. PL/SQL Release CORE TNS for Operating System NLSRTL Version For example, Production. For example, Production. National Language Support Run-Time Library. This library is responsible for providing algorithms for internationalization. The information (NLSDATA) is read by the NLSRTL library during run-time. For example, Production. Copyright IBM Corp. 2012,

196 Item Total SGA Total Database shared memory Description System Global Area is the shared memory area used by the instance to store information shared between the database and the user processes. The following values are displayed (in MB): v Fixed Size - exact size. For example, 72K. v Variable Size - shared spool. For example, 291M. v v Database Buffers - part of the SGA that holds copies of blocks of data read from the Oracle datafiles on disk. For example, 125M. Redo Buffers - an area of memory within the SGA that holds information about recent changes to the database. For example, 528K. Total Database shared memory parameter specifies the amount of memory that is reserved for the database shared memory region. The following values are displayed (in MB): Buffer pools A buffer pool is an area of main memory that has been allocated by the database manager for the purpose of caching table and index data as it is read from disk. For example, M. Database heap There is one database heap per database, and the database manager uses it on behalf of all applications connected to the database. It contains control block information for tables, indexes, table spaces, and buffer pools. For example, M Lock list memory This parameter indicates the amount of storage that is allocated to the lock list. There is one lock list per database and it contains the locks held by all applications concurrently connected to the database. For example, 52 M. Utility heap size This parameter indicates the maximum amount of memory that can be used simultaneously by the backup, restore, and load (including load recovery) utilities. For example, M. Package cache size This parameter is allocated out of the database shared memory, and is used for caching of sections for static and dynamic SQL and XQuery statements on a database. For example, M. Sort heap threshol This parameter represents a soft limit on the total amount of database. 186 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

197 Viewing database free space status The Database Free Status is displayed at the bottom of the ProvisoInfo Browser. Free space is computed using metric data and metadata tablespaces. About this task The Database Free Space Status values include the following: Value NORMAL (green) WARNING (orange) CRITICAL (red) DEADZONE (maroon) Description Indicates that the database is functioning properly. More than or equal to 30 percent of free space is available. Indicates that database free space is minimal. Less than or equal to 30 percent of free space is available. Indicates that you need to purge part of the database. Less than or equal to 10 percent of free space is available Indicates that the database might not be functioning properly. Less than or equal to 5 percent of free space is available. Viewing database parameters Note: If a warning, critical, or deadzone status exists, the affected tab in the ProvisoInfo Browser displays the appropriate color code (orange, red, or maroon). A refresh is automatically started every day at 4 p.m. If the status is not normal, a message is sent to Tivoli Netcool Performance Manager user via the notifydbspace script (located in the bin directory of the DataMart installation path). 1. Click the Database folder. The Parameters and Statistics folders appear. 2. Click the Parameters folder to view database parameter information. This information lets you quickly identify all database level parameters and is useful for working with database technical support or IBM in troubleshooting issues. For example, you can verify that a parameter changes or if the init.ora file was modified. In case of DB2 database verify the database manager configuration file and database configuration file for parameter changes. A DB2 instance can contain multiple databases. Therefore, configuration parameters and their values are stored at both the instance level, in the database manager configuration file, and at the database level, in the database configuration file. You manage the database manager configuration file through the GET DBM CFG or UPDATE DBM CFG command. You manage the database configuration file through the GET DB CFG or UPDATE DB CFG command. Chapter 14. Viewing database information 187

198 Viewing database statistics 1. Click the Database folder. The Parameters and Statistics folders appear. 2. Click the Statistics folder to view database statistics. This information provides you with a quick look at performance of database memory areas, and displays the information in progression bars.for example, The Hit Ratio is a percentage indicating how well the catalog cache is helping to avoid actual accesses to the catalog on disk. A high ratio indicates it is successful in avoiding actual disk I/O accesses. Viewing the Tivoli Netcool Performance Manager version information Viewing MetaData Click the Proviso Version folder to display version information. This information lets you quickly identify the versions of Tivoli Netcool Performance Manager components in your environment and is useful for working with the specific Tivoli Netcool Performance Manager technical support or IBM in troubleshooting issues. The MetaData tab displays information about Tivoli Netcool Performance Manager configuration elements, metrics, and properties. Metadata represents data such as tablespace and table information, and is grouped by topic (for example, configuration, temporary tablespaces, system tablespaces, etc.). Tivoli Netcool Performance Manager describes each resource, collection and aggregation schedules, and MIBs. About this task To view Metadata information, follow these steps: 1. Click the MetaData tab. 2. Expand the Tablespaces item. 3. Expand the Metadata item. 4. Click a tablespace item. 5. Expand a tablespace item in the tree to display a list of files. 6. Click the directory path and file name to view the total space used (in megabytes) for this file. 7. Expand the Temporary tablespace item and the items beneath it to view sizing information in megabytes. 8. Expand the System & Rollback item. The SYSTEM item appears. 9. Click the SYSTEM item to display spacing information. 10. Expand the SYSTEM item to view only the total space used (in megabytes). 11. Expand the Meta Tables > Formulas items. 12. Click the FRML_DESC item in the Formulas tree. This information lets you quickly view table structures and provides a short description of the purpose of each column (if available). 13. Click the FRML_DESC_HIST > FRML_GRP_DESC > FRML_GRP_MEMBER > FRML_GRP_PATH > FRML_MIB > FMRL_MIB_HIST items. 188 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

199 Viewing MetricData 14. Click the Resources > Grouping - Inventory > Properties - Thresholds > Dataview > Nomenclature > Schedule - Collect > Schedule - Collect > Miscellaneous > Internal items to expand the branch. The MetricData tab displays channel information on aggregation sets, channel lists, and loaders. MetricData is data collected and optionally transformed by formulas, imported, or summarized by an aggregation policy. About this task To view metric data, follow these steps: Note: This information allows you to view current threshold database status for tables paces in current history (raw data). In the example above, the thresholds are in the critical stage, alerting you to potential problems. 1. Click the MetricData tab. 2. Click the Aggregation Sets tab. This information displays aggregation sets status. In the example above, GMT -5 (Boston) aggregation set is active and is being used by the Complex Metric Engine. The aggregation set s tables and views show a status of OK. 3. Click a GMT value in the tree to view the aggregation set status for that GMT. 4. Click a channel item to get additional partition information. 5. Click the Channels tab to display channel information. 6. Click the Working item to expand the branch. 7. Click an item to display file names. 8. Click a file name. 9. Click the Historic item to expand the branch. 10. Click a historic item. The number of rows, high date, and tablespace used is displayed for each partition. Partition information for recent and previous (ancient) history is also displayed. 11. Click the DataLoads tab to display a list of SNMP and Bulk collectors installed in your network. 12. Click a DataLoad collector number under the DataLoads navigation tree. 13. Click the Registry tab. The Registry stores parameter information. Each application creates a registry, which allows Tivoli Netcool Performance Manager parameters to be stored in a central location. 14. Click the Default item in the Registry navigation tree to expand the branch. 15. Click the Common item in the Registry navigation tree to expand the branch. 16. Click the Current folder. This information allows you to view current threshold database status for tablespaces in current history (raw data). In the example above, the thresholds are in the critical stage, alerting you to potential problems. 17. Click the Clients item in the Registry navigation tree to expand the branch. 18. Click the Channel (C01) item in the Registry navigation tree to expand the branch. Chapter 14. Viewing database information 189

200 Viewing client information Explains how to view database client status information on the Tivoli Netcool Performance Manager Database, DataMart, DataLoad, DataChannel, and DataView. About this task Viewing database status To view client information, follow these steps: 1. Click the Clients tab. 2. Click either Database, DataLoad, DataView, DataMart or Data Channel. Database IDs must be created in the database and displayed. Only one client is connected by PV_ADMIN. Explains how to view database status to help you troubleshoot problems. Click the Database Status tab. If the database is normal, the following information is displayed: If the status of the database is in the Warning, Critical, or Deadzone state, the following information is displayed: 190 IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

201 Viewing disk information Note: In the example above, only 7 percent of overall free space remains available, and the database is 90 percent full. 1. Click the Disk tab. 2. Click the / (forward slash) to display the amount of free disk space. 3. Click var to display the amount of free disk space. 4. Expand /export/home to expand the branch and view mount point disk space information. 5. Click an item. The following information is displayed: Chapter 14. Viewing database information 191