IBM Tivoli Netcool Performance Manager 1.3.2 Wireline Component Document Revision R2E1. Command Line Interface Guide

IBM Tioli Netcool Performance Manager 1.3.2 Wireline Component Document Reision R2E1 Command Line Interface Guide

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

Contents About this information........ ii Intended audience............ ii The Tioli Netcool Performance Manager product suite................ ii Chapter 1. Introduction........ 1 Special characters and command-line utilities... 1 Accessing CLI utilities........... 1 Chapter 2. Using the inentory command.............. 3 Function................ 3 Synopsis................ 3 Description............... 4 Options................ 6 Examples............... 9 Chapter 3. Using the dccmd command 11 Running the dccmd command........ 11 The dccmd command........... 11 Example dccmd commands......... 13 Chapter 4. Managing Tioli Netcool Performance Manager objects..... 15 Understanding Tioli Netcool Performance Manager objects................ 16 About Tioli Netcool Performance Manager objects............... 16 Understanding Tioli Netcool Performance Manager object IDs............... 21 Working with resmgr........... 22 Displaying resource manager options..... 22 Using column names.......... 24 Resource column names......... 24 Design objects............ 30 Requests.............. 33 Report objects............ 36 Application column names........ 38 Administration objects.......... 40 Using functions with column names..... 41 Chapter 5. Exporting and importing objects............... 49 The export syntax............ 49 Mandatory options........... 49 Additional options........... 50 Using mandatory links with elements.... 54 Diiding results into multiple lines..... 54 Including field separators......... 55 Including record separators........ 55 Specifying a file name.......... 56 Specifying path locations......... 56 Remoing the header.......... 56 The import syntax............ 58 Mandatory options........... 58 Using -colnames........... 58 Including field separators......... 59 Including record separators........ 59 Specifying file names.......... 59 Specifying path locations......... 59 Specifying input data.......... 59 Forcing the creation date......... 60 Reloading collectors.......... 60 Analyzing Tioli Netcool Performance Manager object............... 60 Using a configuration file.......... 61 Line-by-Line explanation......... 62 Chapter 6. Managing resources.... 73 Working with elements.......... 73 Exporting elements........... 73 Importing elements........... 78 Deleting elements........... 81 Working with subelements........ 81 Exporting subelements......... 82 Importing subelements......... 84 Deleting subelements.......... 87 Working with groups or rules....... 88 Subelement group links......... 88 Exporting groups and rules........ 88 Importing groups and rules........ 95 Deleting.............. 97 Working with composite subelement rules... 98 Working with nomenclature........ 99 Using mandatory links......... 102 Using mandatory links with subelements... 105 Using mandatory links with subelement groups 107 Using mandatory links with inentory profiles 109 Using mandatory links with nomenclature... 110 Chapter 7. Managing design objects 111 Working with formulas.......... 111 Exporting formulas.......... 111 Importing formulas.......... 113 Deleting formulas........... 114 Working with properties.......... 114 Subelement properties......... 114 Exporting properties.......... 117 Exporting property default alues..... 118 Trouble Ticket pack properties....... 119 Properties used by the Tioli Netcool Performance Manager-enabled SAA probes.. 119 Importing properties........... 123 Importing subelement properties...... 123 Deleting subelement property....... 124 Working with thresholds......... 124 Exporting thresholds.......... 124 Importing thresholds.......... 125 Deleting thresholds.......... 125 Copyright IBM Corp. 1997, 2012 iii

Working with requests.......... 125 Exporting all requests......... 125 Exporting subelement group requests.... 126 Exporting percentiles.......... 127 Importing requests.......... 127 Deleting requests........... 128 Working with calendars.......... 128 Exporting calendars.......... 128 Importing calendars.......... 129 Deleting calendars........... 129 Working with timezones.......... 129 Exporting timezones.......... 129 Working with inentory profiles....... 130 Duplicating an inentory profile...... 130 Importing inentory profiles....... 131 Deleting inentory profiles........ 131 Chapter 8. Managing administration objects.............. 133 Working with Tioli Netcool Performance Manager DataMart users and groups......... 133 Exporting users and groups....... 133 Importing users and groups....... 134 Deleting user and groups........ 136 Working with registries.......... 136 Exporting registry objects........ 136 Importing registries.......... 143 Deleting registries........... 143 Working with miscellaneous Tioli Netcool Performance Manager objects........ 143 Working with chnl (information about collector) 144 Working with reg........... 144 Working with dbi........... 145 For limited use (checking for problems after installation)............. 145 Chapter 9. Managing report objects 147 Working with web users.......... 147 Exporting web user.......... 147 Importing web user.......... 149 Deleting web user........... 150 Working with reporters.......... 150 Exporting reporters.......... 150 Importing reporters.......... 154 Deleting reporters and reporter stylesheets.. 155 Working with scheduler.......... 156 Exporting scheduler.......... 156 Importing scheduler.......... 159 Deleting scheduler........... 159 Chapter 10. Managing history table and sequence objects........ 161 Working with history tables........ 161 Exporting history tables......... 161 Importing and deleting......... 164 Working with sequences.......... 164 Find and modify the start of indexes for formulas.............. 164 Find and modify the start of indexes for resources.............. 164 Chapter 11. Configuring thresholds 165 Thresholds.............. 165 Threshold options........... 165 Deploying thresholds........... 167 Threshold deployment against groups and resources.............. 167 Deploying "Non-differentiated" thresholds... 169 Deploying differentiated thresholds..... 171 Working with thresholds......... 173 Exporting thresholds.......... 173 Deleting thresholds.......... 174 Importing thresholds.......... 175 Setting thresholds............ 177 Identifying formula indexes....... 177 Setting a threshold against a group (dbindex) 177 Setting a threshold against a group (name).. 178 Setting a threshold against a resource (dbindex) 178 Setting a threshold against a resource (name) 179 Setting a future threshold........ 179 Setting traps.............. 180 Setting burst traps........... 180 Setting period traps.......... 182 Threshold troubleshooting scenarios...... 182 Export scenario 1........... 182 Export scenario 2........... 183 Export scenario 3........... 184 Export scenario 4........... 184 Chapter 12. Configuring timezones 187 Working with timezones.......... 187 Exporting timezones.......... 187 Deleting timezones.......... 188 Importing, modifying, and creating timezones 188 Grouping links of subelements, calendars, and timezones.............. 189 Exporting links............ 189 Deleting links............ 189 Importing, modifying or creating links.... 190 Appendix A. Supported resmgr options.............. 193 Appendix B. Working with SAA probes.............. 197 Exporting or importing an SAA probe..... 197 Exporting or importing an SAA probe with types 197 Exporting or importing SAA probe attributes... 197 Deleting SAA probes........... 198 Argument descriptions for SAA probe operations 198 Listing subelement groups without resources... 200 Finding and fixing nomenclature....... 200 Listing deices not assigned to a nomenclature group............... 200 Correctly classifying a Tioli Netcool Performance Manager object....... 201 Filtering subelements using the underscore (_) 201 Cutting and pasting in subelement group.... 201 Finding the subelement group index.... 201 Cutting the subelement group....... 201 Pasting the subelement group....... 201 i IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Finding subelement groups without a parent 202 Finding subelement groups with more than one parent............... 202 Finding number of child groups for a subelement group........... 203 Checking subelement group request history tables............... 203 Checking the number of groups to which a subelement belongs.......... 204 Listing elements with empty SysName.... 205 Finding number of collection requests per subelement............. 205 Filtering without case filter........ 206 Finding the number of subelements in a family 206 Grouping all the subelements....... 206 Displaying the classification of the xeice name dhcp200.............. 206 Inserting in the past.......... 207 Appendix C. CLI return codes.... 209 snmpconf............... 209 Standard output error messages...... 209 reqedit............... 213 Return code............. 213 Standard output error messages...... 213 resmgr............... 215 Return code............. 215 Standard output error messages...... 215 inentory............... 216 Return code............. 216 Standard output error messages...... 217 impexp............... 218 Return code............. 218 Standard output error messages...... 219 Appendix D. Sample inentory script 221 Sample inentory script.......... 221 Appendix E. Using prerequisite check scripts.............. 227 Using the check_os script......... 227 Running the check_os script....... 227 Error messages............ 228 Using the check_db script......... 229 Tasks performed by the check_db script... 229 Running the check_db script....... 230 Notices.............. 235 Trademarks............ 239 Contents

i IBM Tioli Netcool Performance Manager: Command Line Interface Guide

About this information Intended audience IBM Tioli Netcool Performance Manager, Version 1.3.2 is a bundled product consisting of two main components. A wireline component (formerly Tioli Netcool/Proiso), and a wireless component (formerly Tioli Netcool Performance Manager for Wireless). TheIBM Tioli(r) Netcool(r) Performance Manager: Command Line Interface Guide help you use the inentory and resmgr commands. The audience for this guide is as follows: Tioli Netcool Performance Manager Administrators Content Designers The Tioli Netcool Performance Manager product suite Tioli Netcool Performance Manager is made up of the following components: Tioli Netcool Performance Manager DataMart is a set of management, configuration, and troubleshooting GUIs that the Tioli Netcool Performance Manager System Administrator uses to define policies and configuration, as well as erify and troubleshoot operations. Tioli Netcool Performance Manager DataLoad proides flexible, distributed data collection and data import of SNMP and non-snmp data to a centralized database. Tioli Netcool Performance Manager DataChannel aggregates the data collected through Tioli Netcool Performance Manager DataLoad for use by the Tioli Netcool Performance Manager DataView reporting functions. It also processes online calculations and detects real-time threshold iolations. Tioli Netcool Performance Manager DataView is a reliable application serer for on-demand, web-based network reports. Tioli Netcool Performance Manager Technology Packs extend the Tioli Netcool Performance Manager system with serice-ready reports for network operations, business deelopment, and customer iewing. Copyright IBM Corp. 1997, 2012 ii

The following figure shows the different Tioli Netcool Performance Manager modules. Tioli Netcool Performance Manager documentations consists of the following: Release notes Configuration recommendations User guides Technical notes Online help The documentation is aailable for iewing and downloading on the infocenter at http://publib.boulder.ibm.com/infocenter/tiihelp/8r1/topic/ com.ibm.netcool_pm.doc/welcome_tnpm.htm. iii IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 1. Introduction The Tioli Netcool Performance Manager Command Line Interface (CLI) lets you manage Tioli Netcool Performance Manager objects by using seeral utilities, including the Resource Manager (resmgr) and the inentory command. Although Tioli Netcool Performance Manager supports arious CLI utilities, these are the most commonly used and are therefore the focus of this guide. Special characters and command-line utilities Accessing CLI utilities When using the command-line utilities (like resmgr, for example) make sure that you use a backslash (\) to escape characters that are special to the shell and to the command line, especially the following: [] {} ` " \ $ The CLI utilities reside in the Tioli Netcool Performance Manager DataMart and Tioli Netcool Performance Manager DataLoad bin directories. Procedure 1. On the system where DataMart is installed login as puser (or any user with access rights to Tioli Netcool Performance Manager) Important: When you run the pm command to access the DataMart for the first time, you must log in as puser. 2. Open a terminal window. 3. For Tioli Netcool Performance Manager DataMart command-line interfaces, ensure that your enironment is set by entering the following command:../datamart.en 4. For Tioli Netcool Performance Manager DataLoad command-line interfaces, ensure that your enironment is set by entering the following command:../datamart.en 5. The CLI commands are in the bin directories where you installed Tioli Netcool Performance Manager DataMart and Tioli Netcool Performance Manager DataLoad. If you selected the defaults during the installation, the location of these bin directories would be as follows: Tioli Netcool Performance Manager DataMart /opt/datamart/bin Tioli Netcool Performance Manager DataLoad /opt/dataload/bin Copyright IBM Corp. 1997, 2012 1

The following types of executable reside in these bin directories: Basic Utilities -- CLI commands like resgmr and inentory that perform basic Tioli Netcool Performance Manager administratie tasks. Conersion Utilities -- CLI commands that conert different database file formats into the Tioli Netcool Performance Manager DataMart format. Note: The CLI utilities support a help option (-?) that explains how to use the command. 2 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 2. Using the inentory command Function Explains how to use the inentory command to manage inentory Use the inentory command to manage your network inentory and perform grouping and debugging operations from the command line. Inoked without arguments, the inentory command brings up the DataMart Inentory Tool GUI, which is explained in detail in the IBM Tioli Netcool Performance Manager: DataMart Configuration and Operation Guide. You typically use the DataMart Inentory Tool to: Run inentories against profiles newly created with the Inentory Wizard to ensure that they work as expected. Run an on-demand inentory. The inentory command, by contrast, is typically placed in crontab to run complete or partial inentories or grouping operations on a regular basis as part of a Tioli Netcool Performance Manager deployment. Thus, the best practice is first to create and debug an inentory profile using the DataMart Inentory Tool, and then to deploy the inentory and grouping operations in crontab using the inentory command. When a profile is run from the Inentory Tool GUI, the output goes to the UI and to the file PVMHOME/log/TraceInentory.log. When a profile is run from the CLI, the output goes to the standard output deice (terminal screen). If you want to sae the inentory output, you must redirect the output to a file: inentory -nox... > myinentory.log Note that Appendix D, Sample inentory script, on page 221 contains a sample Korn Shell script that calls the inentory command. You can use this as a model for your own inentory wrapper programs. Inentory Management Utility Synopsis inentory inentory [-D [DebugLeel]] [-U] [-name [profilename]] [-action [operation]] [-reload [collectornum]] [-nox] [-timeout] [-retry] [-ip ipaddress] [-reportgrouping] [cseengine [-rulefile rulefile][-rulesubset rulesubset]] [-mode subprofile] [-?][-DList [CodeTracingModesList]][-DFile DebugOutputFile]] Copyright IBM Corp. 1997, 2012 3

Description The inentory command, which resides in the $PVMHOME/bin directory and supports a number of inentory management operations, and is the command-line equialent of the DataMart Inentory Tool graphical utility. For more information on using the DataMart Inentory Tool, see the IBM Tioli Netcool Performance Manager: DataMart Configuration and Operation Guide. The inentory command is intended to be run from crontab, either called directly or from within a wrapper program. Note the following: If run without options, the inentory command inokes the DataMart Inentory Tool. If the -action option is not specified, the inentory command reads and executes the settings saed by the DataMart Inentory Tool configuration file, $PVMHOME/res/C/inentory.res. Important: Do not edit this file unless instructed to do so by IBM Professional Serices. In ery general terms, when a complete inentory is run, Tioli Netcool Performance Manager does the following: 1. Locks the specified inentory profile and creates a subdirectory with the name of the profile in $PVMHOME/importexport (SNMP) and $PVMHOME/ importexportbulk (BULK) to hold the files created during the inentory. If the inentory profile is already locked, inentory attempts to unlock the profile. If the profile is running on the same host, inentory looks for the process. If the process does not exist, inentory remoes the lock and proceeds. If the profile is running on a different host, inentory waits for the period specified by the -timeout option and then retries to remoe the lock. 2. Initiates a discoery operation, and writes the results to the following directory: $PVMHOME/[importexport importexportbulk]/profilename/inentory. An SNMP discoery operation consists of passing a list or range of IP addresses and a set of specific discoery parameters (for example, timeout and number of retries) to the discoery serer. The discoery serer then executes the discoery formulas against the specified deices, in collaboration with the SNMP collector, producing a set of files containing the list of discoered resources and their attributes. Note: If BULK mode (mode 3) is enabled, this discoery serer only copies the discoery files passed by the BULK collector. 3. Synchronizes the newly-discoered elements and sub-elements with the information stored in the database, then writes the newly synchronized information to the database. The synchronization operation is broken up into the following two phases: Pre-synchronization Tioli Netcool Performance Manager retriees the list of elements and subelements associated with the inentory profile from the database. Synchronization Tioli Netcool Performance Manager compares either the set of elements and subelements collected by the discoery operation (if SNMP) or the contents of the bulk files (if BULK) to the set of elements and sub-elements in the 4 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

database. Seeral criteria are applied (such as inariants and the retirement policy) to determine if the discoered resources (and properties) are new, updated, or deleted. Tioli Netcool Performance Manager retriees the list of elements and sub-elements associated with the inentory profile from the database. The result of this comparison is then written back to the database. During the synchronization operation, the following two directories are created in the $PVMHOME/[importexport importexportbulk]/profilename directory: synchro - Contains the successful results of the synchronization process that are then written to the database. synchrowait - Contains a list of files that for a ariety of reasons could not be synchronized and were not written to the database. If this directory is populated, you should examine the files and determine the cause of failure. Tioli Netcool Performance Manager compares the grouping of the files in the synchro directory with the grouping rules specified in the inentory profile and writes the results to the following two directories in the $PVMHOME/[importexport importexportbulk]/profilename directory: Tioli Netcool Performance Manager extracts the information about the groups for elements and sub-elements from the files in the grouping directory and inserts the information into the database. 4. Applies grouping rules to the synchronized elements and subelements, and writes the results to the database. a. Tioli Netcool Performance Manager compares the grouping of the files in the synchro directory with the grouping rules specified in the inentory profile and writes the results to the following two directories in the $PVMHOME/[importexport importexportbulk]/profilename directory: grouping - Contains the successful results of the grouping process that are then written to the database. groupingwait - Contains a list of files that for a ariety of reasons could not be grouped and were not written to the database. If this directory is populated, you should examine the files and determine the cause of failure. b. Tioli Netcool Performance Manager changes the file extension on the files as it processes them. If you want to re-run the grouping, change the file extension back to.dat. Note: By default, Tioli Netcool Performance Manager saes the three most current ersions of the grouped files. The number of copies saed is configurable. To change the number of copies saed, change the number_history parameter in $PVMHOME/res/C/inentory.res. Note: By default, Tioli Netcool Performance Manager saes the three most current ersions of the grouped files. The number of copies saed is configurable. To change the number of copies saed, change the number_history parameter in $PVMHOME/res/C/inentory.res. 5. Unlocks the inentory profile. Note: When the inentory command runs, state information is constantly written to the file $PVMHOME/[importexport importexportbulk]/profilename/ state. Chapter 2. Using the inentory command 5

Options -? Prints a usage statement for the command. -action [all discoery grouping lock pregrouping presynchro synchro]all Specifies that the inentory command is to run all arguments to the -action option, executing a complete inentory and then grouping the results of the synchronized inentory. Used in conjunction with the -name, -mode, -ip, or-cseengine options. discoery Specifies that the inentory command is to run only the discoery phase of the inentory process. Used in conjunction with the -name, -mode, or-ip options. grouping Specifies that the inentory command is to run only the grouping phase of the inentory process. Note: Before you can use this option, the results of a discoery must hae been synchronized and pre-grouped. lock Locks an inentory profile specified by the -name or -mode option. Unless using the all argument, you must manually lock an inentory profile. Note that you can use the lock argument in conjunction with the -retry and -timeout options when attempting to lock a profile that may already be in locked by another process. pregrouping Specifies that the inentory command is to run only the pre-grouping phase of the inentory process. presynchro Specifies that the inentory command is to run the pre-synchronization phase and partial sychronization of the inentory process. Used in conjunction with the -name, -mode, or-ip options. Note: The presynchro option is useful for debuging or preiewing potential updates to the database. This option is not used to perform a complete inentory process.' synchro Specifies that the inentory command is to run only the synchronization phase of the inentory process. Used in conjunction with the -name, -mode, or-ip options. Important: Before you can use either the synchro or the presychro options, the discoery option must be run. -cseengine [-rulefile rulefile -rulesubset rulesubset] Runs the composite subelement (CSE) Engine to implement CSE rules and rule subsets. Pregrouping creates CSE groups and objects defined by CSE rules. Grouping adds CSE groups and objects to the database. You can run the pregrouping and grouping phases indiidually with the pregrouping 6 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

and grouping options. You can implement both the pregrouping and grouping phases together by running inentory cseengine option as follows: Without options With the -action "all" arguments With the -action "pregrouping grouping" arguments -rulefile rulefile Specifies a text file that contains definitions for each of the rule subsets. The default file name and location is: $PVMHOME/conf/cseRuleSubSets.conf. Specifying this option without specifying the -rulesubset option runs all of the rule subsets in the rule file. -rulesubset rulesubset Runs a specified rule subset from the rule file. If you want to run more than one rule subset, list each of the rule subsets separated only by a comma. -date Deprecated. -D DebuggingLeel Turns on debugging, with leels specified by DebuggingLeel. Supported leels are 1 to 10, with 10 outputting the most information. Default is to write to standard error, unless the -DFile option is specified. -DList string Debugging option, used in conjunction with the -D option, that performs code execution traces. -DList sql, for example, returns only debugging messages related to SQL queries. Do not use this option unless instructed to do so by IBM Professional Serices. -DFile DebuggingFile Instructs the inentory command to write debugging information to the file specified by DebuggingFile, rather than to standard error. -ip IPAddresses Specifies that the inentory command runs against up to fie IP addresses in the command line, using a comma as a separator. If you want to specify more than fie IP addresses, list the addresses in a file and use the -mode subprofile option. For example, to specify 5 IP addresses: -ip 11.11.11.11,22.22.22.22,33.33.33.33,44.44.44.44,55.55.55.55 The IP addresses must belong to the set of included IP addresses defined within the associated inentory profile. -mode subprofile The -mode subprofile option toggles the inentory command to run the discoery on a subset of the entire inentory profile. The subset of elements are listed in the file that is defined at the time of the creation of the inentory profile. This option is used by specifying -mode subprofile in the syntax of the inentory command. This option allows you to reduce the time of the inentory by targeting only those elements that are known to change frequently. A deployment may, for example, elect to run an inentory against a subprofile once a day, while restricting a full inentory to once eery month. Chapter 2. Using the inentory command 7

For more information on configuring profiles for use with the subprofile option, see the Tioli Netcool Performance Management DataMart Configuration and Operation Guide. -name profilename Used in conjunction with the -action option. Instructs the inentory command to run against the profile specified by profilename. You must not use any of the following resered terms in the name of your profile: elt inentory slowwan exclude ipaddress snmpconf fastlan lan subelt filestoinsert mode subeltin grouping objectfilter synchro icmp objectfilter wan include rulefilter ROOTROOT -nox Instructs the inentory command to run as a command-line utility. -reload CollectorNumber Instructs the inentory command to reload the collector specified by CollectorNumber. The default is collector one (1). The inentory command should be called with this option set eery time a profile or the resources in the profile hae been changed. For more information, see the IBM Tioli Netcool Performance Manager: DataMart Configuration and Operation Guide. You might, for example, write a wrapper that - among other things - waits for an eent from the Discoery Serer notifying it that a profile has changed, and then calls the inentory command with the -reload option set. -reportgrouping Instructs the inentory command to run the report grouping rules and update the deployed reports stored in the database. Report grouping rules must first hae been created before this option can be used. For information on creating report grouping rules, see the IBM Tioli Netcool Performance Manager: DataMart Configuration and Operation Guide. -retry Used in conjunction with the -timeout option. Specifies the number of times to try to set a lock on a locked profile. The default is 1. -timeout Used in conjunction with the -retry option. Specifies the length of time to wait to try to lock a profile. The default is 60 seconds. -U Deprecated -ersion Lists ersion information for the inentory command. 8 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Examples The following example crontab entry illustrates how to use the inentory command in an actual Tioli Netcool Performance Manager deployment. The entry runs a full inentory (-all ) against a CBQoS profile after first reloading SNMP collector 1. 02,16***[-f/p/dm/dataMart.en ] && [ -x /p/dm/bin/inentory ] && \. /p/dm/datamart.en && inentory -name CBQoS -nox -action all -reload 1 >> \ /p/dm/log/cbqos.txt Note: Appendix D, Sample inentory script, on page 221 contains a sample Korn Shell script that calls the inentory command. You can use this as a model for your own inentory wrapper programs. Chapter 2. Using the inentory command 9

10 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 3. Using the dccmd command Use the dccmd command to stop and start DataChannel components, and to obtain status information about applications running on a DataChannel and its subchannels. Running the dccmd command About this task The dccmd command Run the dccmd command as follows: Procedure 1. Log in as puser to the serer where the DataChannel is installed. 2. Change your working directory to the DataChannel home directory (/opt/datachannel by default), as follows: cd /opt/datachannel$ 3. Set the DataChannel enironment as follows:../datachannel.en 4. Run the dccmd command. $ dccmd options Function DataChannel Management Utility Synopsis dccmd [-x] [-app pattern] [-host pattern] action [name_pattern] [parameters] Description The dccmd command is used to manage a DataChannel enironment. Use the dccmd command to stop and start DataChannel components, and to obtain status information about applications running on a DataChannel and its subchannels. Options action [bounce cstatus forget status start stop usage which] bounce Stop and restart the selected components. cstatus Show the cached status of the selected components. Each time the status is requested for a component, that status is retained and is reported using cstatus. The channel manager periodically requests the status of all running components. Such requests are normally issued about once per minute. Thus, requesting the cstatus will generally show the status of the selected components as of at most one minute in the past. forget Remoe the selected components from the list of components that should Copyright IBM Corp. 1997, 2012 11

be running maintained by Channel Manager. Components are remoed from the list without stopping the component. If components on this list are not running, Channel Manager repeatedly attempts to restart them. Forcing Channel Manager to forget a component preents Channel Manager from automatically restarting a component without actually stopping the component. status Report the status of the selected components. For each selected component show the component name, type (application), host name, status, and extended status (including the number of minutes since the extended status was last updated). start Starts the selected components. If the component eer fails, or is stopped by any other means than the stop command, the Channel Manager will attempt to restart it. stop Stops the selected components. usage Use without other arguments to print usage information for the command. which name_pattern Lists the components selected by the gien pattern, application pattern or host pattern. This action is useful for erifying the set of components that would be affected by some other action. name_pattern identifies a set of components by their name. If the -x option is specified, matching is performed using regular expressions, otherwise simple pattern matching is used. In addition to normal pattern matching, the special word all is interpreted to match any name (it is functionally equialent to the pattern "" or the regex "."). For all actions except usage, at least one instance of name_pattern, -app, and -host must be specified (if none are specified, dccmd will report an error). If more than one pattern is specified, the set of components will be those that match all specified criteria. All pattern matching is case insensitie. Note: To preent the shell from applying filename expansion, any patterns that include special matching characters (such as "*", "?") should be enclosed in double quotes. -x Use regular expressions for pattern matching (the syntax matches that of the Henry Spencer regex library). If specified, the application, host, and component patterns will use regular expression matching, otherwise, simple pattern matching will be used. For simple matching, * will match any substring of characters and # will match any single character. -app pattern -application pattern Restricts the set of components to which the action will apply to those running an application that matches the pattern. For example, a pattern of CME would only apply the action to CME components. Similarly CME LDR would match CME or LDR components (assuming the -x option was specified). Components can be one of the following: BCOL, FTE, CME, LDR, DLDR, ALL, or * Note: Users of certain Tioli Netcool Performance Manager Technology Packs, including the Packs for the Alcatel 5620 NM and Cisco CWM, can also control the Pack-specific modules with dccmd, using the same start, stop, and other options. Pack-specific modules include the QCIF, CWMIF, BLB, and UBA applications. 12 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Example dccmd commands -host pattern -hostname pattern Restricts the set of components to which the action will apply to those running on a host whose name matches the pattern. Shows how to perform more common DataChannel component management tasks with dccmd. Start Indiidual Applications The following table lists the DataChannel components and their start commands. Application CME Bulk Collector FTE Hourly Loader Daily Loader Command dccmd start -app cme dccmd start -app bcol dccmd start -app fte dccmd start -app ldr dccmd start -app dldr View DataChannel Status To iew the status of a DataChannel, use the dccmd utility with the following syntax: $./dccmd status pattern For example: $ dccmd status all $ dccmd status -app "disc" $ dccmd status cme.1.1 $ dccmd status "*.1.*" Chapter 3. Using the dccmd command 13

14 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 4. Managing Tioli Netcool Performance Manager objects Tioli Netcool Performance Manager objects are the configuration data used by the Tioli Netcool Performance Manager system to define data collection and reporting. Resource Manager is a CLI tool that sits on top of the database and lets you manage the configuration information contained in the database. When you work with resmgr you are working from the command line, emulating tasks you can perform using the Tioli Netcool Performance Manager graphical user interface (GUI.) You can work from the command line to export and/or import Tioli Netcool Performance Manager objects to or from the database and to or from multiple Tioli Netcool Performance Manager systems. All Tioli Netcool Performance Manager objects can be managed through resmgr. For example, you can use resmgr to manage the Tioli Netcool Performance Manager objects relating to a technology (MIBs, formulas, reports, grouping trees, thresholds and so on.) Note: You can also use the Tioli Netcool Performance Manager GUI to work with Tioli Netcool Performance Manager objects. Using the resgmr CLI lets you work with Tioli Netcool Performance Manager objects in bulk. The resmgr command lets you work with resources (elements and subelements) as well with the additional Tioli Netcool Performance Manager objects described in this chapter. With resmgr, you can: Create resources when resources cannot be discoered from the network or when resource information already exists in an inentory or proisioning system and you do not need to rediscoer this information. Delete resources from test systems. Deleting resources from production systems is not recommended. Instead, resources are retired and historical information preiously collected remains in the database. Populate resources with additional properties. Tioli Netcool Performance Manager can work with both the technical properties discoered from the network (MIBs) and the business properties generated by inentory and proisioning. Business properties can include customer tagging, contract number, and a wide ariety of organizational information. Manage Tioli Netcool Performance Manager objects. You can replicate configuration information from system to system by using resmgr to export Tioli Netcool Performance Manager objects to a file that you can then import to other Tioli Netcool Performance Manager systems. Copyright IBM Corp. 1997, 2012 15

Understanding Tioli Netcool Performance Manager objects Explains the basics of Tioli Netcool Performance Manager objects. It contains a description of Tioli Netcool Performance Manager objects, the categories to which they belong, and their database index ranges. About Tioli Netcool Performance Manager objects Tioli Netcool Performance Manager objects are the configuration data used by the Tioli Netcool Performance Manager system to define data collection and reporting. The foundation of Tioli Netcool Performance Manager objects are the resources. Resources are a type of physical or logical object managed by the Tioli Netcool Performance Manager system. Any managed physical interface or port is a resource, any managed logical circuit is also a resource. Resources include elements and subelements. Elements are managed nodes with addresses or hosts, and subelements are subcomponents of an element, such as a port, interface, irtual circuits, user, or a DLCI. Any object from which Tioli Netcool Performance Manager can get identification (a name and a label) and related metrics can be modeled in the DataMart, using the resource concept. Tioli Netcool Performance Manager objects are grouped into the following categories: Resources elements and element groups subelements and subelement groups nomenclature Design formulas properties thresholds requests calendars timezones inentory profiles Administration Tioli Netcool Performance Manager DataMart users and groups registry miscellaneous Report Web users applications scheduler History Table Sequences 16 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

About Tioli Netcool Performance Manager object types Each Tioli Netcool Performance Manager object includes multiple object types. The object types aailable for exporting and importing can sometimes differ. Resource The following table lists the different Tioli Netcool Performance Manager objects related to resources, along with the associated options for export and import. Type Export Options Import Options element elt: element scf: SNMP configuration eprp: element property encl: nomenclature chnl: channel subelement se: subelement seprp: subelement property fam: family group segp: subelement group egp: element group nomenclature ngp: nomenclature group ncl: nomenclature endor: endor elt: element scf: SNMP configuration eprp: element property encl: nomenclature se: subelement seprp: subelement property alue fam: family seproperty: subelement property description segp: subelement group egp: element group linkgroupse: link between group of subelements and subelement linkgroupse_app: link between group of subelements and report linkgroupse_ru: link between group of subelements and report user linkgroupse_tcz: link between group of subelements and timezone and Calendar linkgroupe: link between group of elements and element ngp: nomenclature group ncl: nomenclature endor: endor linkgroupn: link between the group and the nomenclature Design Chapter 4. Managing Tioli Netcool Performance Manager objects 17

The following table lists the different Tioli Netcool Performance Manager objects related to design components, along with the associated options for export and import. Type Export Options Import Options formulas frm: formula fgp: formula mib: MIB property propertye: property of element propertyse: property of subelement propertyru: property of report user frm: formula fgp: formula mib: MIB propertye: property of element propertyse: property of subelement propertyru: property of report user threshold thrd: threshold definition thrd: threshold definition request segpreq: request on subelement group pctile: percentile segpreq: request on subelement group pctile: percentile calendar cal: Calendar cal: Calendar timezone tz: timezone tz: timezone inentory profile ogp: group of inentory profiles opt: option of the inentory profile. Use with ogp alue. ogp: group of inentory profiles opt: option of the inentory profile. Use with ogp alue. linkgroupo: link between group and options of the profile Report The following table lists the different Tioli Netcool Performance Manager objects related to reports, along with the associated options for export and import. Type Export Options Import Options web user rusr: report (Web) user ruprp: report (Web) user property rugp: report (Web) user group rusr: report (Web) user ruprp: report (Web) user property rugp: report (Web) user group linkgroupru: link between group and the report (Web) user 18 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Type Export Options Import Options application app: reporter agp: group of reporters apps: reporter style sheet app: reporter agp: group of reporters apps: reporter style sheet linkgroupapp: link between group and reporter linkgroupapps: link between group and reporters; group and style sheets scheduler sched: Scheduler sched: Scheduler Administration The following table lists the different Tioli Netcool Performance Manager objects related to Administration components, along with the associated options for export and import Type Export Options Import Options DM user usr: Tioli Netcool Performance Manager DataMart user registry regisdm: Tioli Netcool Performance Manager DataMart registry regisdc: Tioli Netcool Performance Manager DataChannel registry regisdb: Tioli Netcool Performance Manager database registry regisdv: Tioli Netcool Performance Manager DataView registry regismg: Tioli Netcool Performance Manager DataChannel Manager registry regdesc: list of all registries reginst: instances of all registries usr: Tioli Netcool Performance Manager DataMart user regisdm: Tioli Netcool Performance Manager DataMart registry regisdc: Tioli Netcool Performance Manager DataChannel registry regisdb: Tioli Netcool Performance Manager database registry regisdv: Tioli Netcool Performance Manager DataView registry regismg: Tioli Netcool Performance Manager DataChannel Manager registry Chapter 4. Managing Tioli Netcool Performance Manager objects 19

Type Export Options Import Options others pkg: all package tables reg: information about component that are running (similar to pmstart) chnl: information about channel client: registration information about Tioli Netcool Performance Manager clients dbi: export Tioli Netcool Performance Manager GUI information into CSV format err: list of Oracle errors tracked by Tioli Netcool Performance Manager orausr: list of Oracle users pkg: all package tables reg: information about component that are running (similar to pmstart) chnl: information about channel client: registration information about Tioli Netcool Performance Manager clients dbi: export Tioli Netcool Performance Manager GUI information into CSV format err: list of Oracle errors tracked by Tioli Netcool Performance Manager orausr: list of Oracle users History Table The following table lists the different Tioli Netcool Performance Manager objects related to history tables, along with the associated options for export and import Type Export Options Import Options history table calh: Calendar history frmh: formula history thrdh: threshold definition history elth: element history seh: subelement history segpreqh: subelement group request history apph: reporter history segph: subelement group history egph: element group history calh: Calendar history frmh: formula history thrdh: threshold definition history elth: element history seh: subelement history segpreqh: subelement group request history apph: reporter history segph: subelement group history egph: element group history Sequences The following table lists the different Tioli Netcool Performance Manager objects related to reports, along with the associated options for export and import 20 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Type Export Options Import Options sequences DesignIndex: sequence of indexes used for Tioli Netcool Performance Manager Design objects such as formulas, reporters, properties and so on. ResourcesIndex: sequence of indexes used for resources (elements, subelements, and groups) DesignIndex: sequence of indexes used for Tioli Netcool Performance Manager Design objects such as formulas, reporters, properties and so on. ResourcesIndex: sequence of indexes used for resources (elements, subelements, and groups) Linking Among Tioli Netcool Performance Manager objects Links can exist among the Tioli Netcool Performance Manager objects. The link is a logical link, most often between child and parent. Howeer, links can also exist between element and subelement, subelement and nomenclature. Understanding Tioli Netcool Performance Manager object IDs Tioli Netcool Performance Manager objects are internally identified by the database by using numerical IDs. You should reiew the following information about ranges before allocating database indexes. For example, database indexes are allocated when you install Tioli Netcool Performance Manager configuration objects that were created on one system onto a different system. Or when IBM deliers standard Technology Packs or customized reports and metrics. The three ranges include: From 0 to 50,000,000 - IDs of objects deliered by IBM as Technology Packs. From 50,000,000 to 100,000,000 - IDs of objects deliered by IBM. From 100,000,000 to 4,294,967,296 - IDs of objects created by each Tioli Netcool Performance Manager system when regular functions are used. For example, when using the Formula Editor to create new formulas, a new unique formula ID is created in that range. When using the Automatic Inentory module, new sub-elements and elements are created in that range. Resource Manager lets you create new objects and assign new database IDs to these new objects. IBM does not support using resmgr to assign database IDs in the range from 100,000,000 to 4,294,967,296. Creating database indexes in other areas such as ranges from 0 to 50,000,000 or from 50,000,000 to 100,000,000 should happen only with approal of IBM support. Chapter 4. Managing Tioli Netcool Performance Manager objects 21

Working with resmgr Explains the basics of working with the resmgr CLI. Using resmgr lets you manage Tioli Netcool Performance Manager objects for automation and scripting purposes without interacting directly with the database schema. It acts like an abstraction layer on top of the database schema, erifying and preenting inalid interactions with the database. Displaying resource manager options You can display the command options aailable with resmgr by entering the following command: resmgr -? The command options that appear for your display might differ from the following examples because options are sometimes added and remoed. The following example shows a possible list of options that can appear. Usage: resmgr [-D [DebugLeel]] [-nox] [-histodate 1] [-nohead] [-ListForced col1 al1...] [-reloadcol] [-collectorlist] [-sep separator] [-seprec] [-file File Name] [-line] [-dirpath] [-filter filter ColNames] [-filterrule] [-colnames [col names list]] [-rule] [-order order ColNames] [-ismandat mandatory type] [-split] [-isdefault] [-distinct] [-loadmemory] [-checkbeforeupdate] [-mode mode] [-config config Name] [-export type] [-import type] [-delete type] [-analyze space] [-?] [-DList [CodeTracingModesList]] [-DFile [DebugOutputFile]] [-ersion] -D : Output debugging information with optional debug leel (1-10). -nox : Text mode. -histodate : if 1, use the date field for history -nohead : remoe export header -ListForced : force the column1... to hae a alue -reloadcol : Reload Collectors = on off forced (default : on ) -collectorlist : list of collector number to reload -sep : separator -seprec : Record Separator -file : File Name output for export or input for insert,update -filter : list of "colname(alue).." colname : same syntax as -colnames ; alue can be :. is null. not null. any charact with * : like operator is used. any charact : = operator is used. relationnal operator(!=,>,<,..) any charact : example col1(!= 3 ) AND is made between filters (-filter is alid only for export) -colnames : list of col to export, import or delete. if empty gie the list aailable for the type specify in export,import or delete. nop to skip columns (only for import) -order : list of colname used in ORDER BY clause : same syntax as -colnames (only for export) -ismandat : list of mandatory type (only for export). for elt : snmpconf,nomenclature,property. for sub-elt : property, family -isdefault : use with eprp,seprp,ruprp -loadmemory : -checkbeforeupd: -mode : mode = insert update Ifirst -config : config entry in Config File -export : type = * Resources : elements : elt, scf, eprp, encl, chnl 22 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

sub-elment : se, seprp, fam group : segp, egp nomenclature : ngp, ncl, endor * Design : formulas : frm fgp mib property : propertye, propertyse, propertyru threshold : thrd request : segpreq, pctile calendar : cal timezone : tz inentory profile : ogp opt rule : rulegp, ruleprp * Report : web user : rusr, ruprp, rugp application : app agp apps scheduler : sched * Admin : DM user : usr registry : regisdm regisdc regisdb regisdv regismg regdesc reginst others : pkg, reg, chnl dbmgr client dbi err orausr * History table : calh frmh thrdh elth seh segpreqh apph segph egph * Sequences : DesignIndex, ResourcesIndex. -import : type = * Resources : elements : elt, scf, eprp, encl, eproperty sub-elment : se, seprp, fam, seproperty group : segp, egp linkgroupse linkgroupse_app linkgroupse_ru linkgroupse_tzc linkgroupe linkgroupegp nomenclature : ngp, ncl, endor linkgroupn * Design : formulas : frm fgp linkgroupf linkmibf property : propertye, propertyse, propertyru threshold : thrd request : segpreq, pctile calendar : cal timezone : tz inentory profile : ogp opt linkgroupo rule : rulegp, ruleprp * Report : web user : rusr, ruprp, rugp linkgroupru application : app agp apps linkgroupapp linkgroupapps scheduler : sched * Admin : DM user : usr ulink uperm registry : regisdm regisdc regisdb regisdv regismg others : pkg, reg, dbmgr * History table : calh frmh thrdh elth seh segpreqh apph segph egph * Sequences : DesignIndex, ResourcesIndex -delete : type = same than for import -analyze : launch analyze on resources tables, space could be : elt, se, egp, segp -? : Gie this help. -DList : Output code execution traces with optionnal tracing modes (sql) -DFile : Debug output filename (default to <moduleid>.dbg)the default file directory is $PVMHOME/log -ersion : Example :. inentory profile : export : resmgr -export ogp -colnames "npath opt.name opt.instance opt.alue" -file XXX import : resmgr -import ogp -colnames "npath opt.name opt.instance opt.alue" -file XXX Chapter 4. Managing Tioli Netcool Performance Manager objects 23

. report users : users export : resmgr -export rusr -colnames "name ruprp.name ruprp.alue" -file XXX import : resmgr -import rusr -colnames "name ruprp.name ruprp.alue" -line "users1 _ LongName _ USERS 1 _ " group of users export : resmgr -export rugp -colnames "npath rusr.name" -file XXX import : resmgr -import rugp -colnames "npath rusr.name" -line "~group1 _ users1 _ " users in group of Sub-Element export : resmgr -export groupse -colnames "npath rusr.name" -file XXX import : resmgr -import groupse -colnames "npath rusr.name" -line "~ cccccccc ~ddddd _ users1 _ Using column names You import and export detailed Tioli Netcool Performance Manager object information from the database in a format called column names (colnames). Columns names are fields that proide you with information about the Tioli Netcool Performance Manager objects. The column names used by resmgr are logical mappings to the physical columns in the database. This logical mapping can be a direct one-to-one mapping (for example, elt.name) or it can be a logical entity representing multiple columns or multiple operations performed on multiple tables to fulfill the requested operation (for example, segp.npath). The full name is object type.colname. If the object type is omitted, the object type for the action (-export) is used. Resource column names The following tables list the column names used for resources, elements, subelements, and subelement groups. Element Column Names The following table list the column names for elements: Column Name dbindex name type profil collector nclidx missing Description Internal database index for the element. Name of the element (or new name). The element type. Aailable alues include: 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 aailable. Name of the inentory profile used to discoer the element. Number of the collector to which this element is assigned. Nomenclature index that allows link to encl, endor. Number of notfounds in the inentory process. 24 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Column Name comment Description Description field. The comment column name can also return information concerning resources that hae been retired or deleted from inentory. The returned infomation for a retired resource includes the following: "Action: Retired;Date: "dateofdelete"; Profile: "profilename";lastsee: "date"; LastMissing: "missingnumber"; Option: "missingcountinprofile LimiteDateInProfil" state date user origin encl.name encl.oid encl.gpname (only for export) endor.name (only for export) chnl.host only for export) Where: Action: Retired - Specifies that the resource has been retired. Date: "dateofdelete" - Specifies when the resource was retired. Profile: "profilename" - Specifies the name of the inentory profile that was used to discoer the resource. LastSee: "date" - Specifies the date when the resource was last detected in the inentory. LastMissing: "missingnumber" - Specifies the number of times inentory has failed to detect the resource. Option: "missingcountinprofile LimiteDateInProfil" - Specifies the retry count and age limit criteria defined in the inentory profile for deleting resources. The state of the element. Aailable alues include: on off The element is switched to off by the inentory process after a period of time and a number of retries defined in the inentory profile tool. Date that the element was inserted or updated in the database, in number of seconds since 1 January 1970. Name of the user who created this element. The method used to add the element to the database. (inentory, resmgr, and so on) Name and generic type of the element. sysobjectid of the element Node type of the element Vendor name of the element. Collector hostname Chapter 4. Managing Tioli Netcool Performance Manager objects 25

Column Name chnl.port (only for export) chnl.type (only for export) eprp.name eprp.alue eprp.propertyname:alue eprp.alue eprp.datatype eprp.prpidx eprp.eltidx eprp.defvalue scf.ipaddress scf.wcommunity scf.rcommunity scf.timeout scf.retries scf.port scf.ersion scf.name Description Collector port Type of Collector (SNMP or Bulk) Name of the element property. Use this column name to export or import multiple properties. Property alue of the element. If this contains a alue, "eprp.name" must contain a alue. The alue of a specific element property. For example, eprp.ipaddress:alue is the alue of the ipaddress element property. You cannot use spaces in the property name. If you export using this column name, only elements that hae a alue for this column are included in the output. Proides a list of all properties. Data type of the property of the element. Aailable alues are: string (default) - if this contains a alue, eprp.name should also contain a alue. float Property index Element index. Specifies the Database Index for the element associated with this SNMP configuration. Property default alue Specifies the IP address, mask, subnets, or address list for the deice. This cannot be NULL if any of the other SNMP configuration (scf.) columns contain a alue. SNMP community name used for writing. If this contains a alue, "scf.ipaddress" must contain a alue. SNMP community name used for reading. If this contains a alue, "scf.ipaddress" must contain a alue. Length of time (in seconds) to wait for a response to a ping. If this contains a alue, "scf.ipaddress" must contain a alue. Number of times to re-try the request if it fails. If this contains a alue, "scf.ipaddress" must contain a alue SNMP port for the element. If this contains a alue, "scf.ipaddress" must contain a alue. Specifies the SNMP ersion associated with this SNMP configuration. Could classify the SNMP community name (use in internal for irtual router). 26 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Column Name scf.colnb scf.bandwidth Description Identifies the collector associated with this SNMP configuration. A setting of 0 applies the SNMP configuration to all collectors. Specifies the maximum amount of traffic (in Kbps) permitted for the corresponding IP address. For more information, see "SNMP Bandwidth Control and Collection Smoothing" in the IBM Tioli Netcool Performance Manager: DataMart Configuration and Operation Guide. Subelement Column Names The following table lists the subelement column names: Column Name dbindex label name hostidx instance inariant missing nclidx state typedata user date origin fam.name Description Internal database index for the subelement Comment describing this subelement. (usually used in reports) Name of the subelement (or new name). element Index String used for the requests (snmp get). Unique string alue that defines the subelement (can be a combination of seeral properties obtained in the MIB.) Number of notfounds in the inentory process Nomenclature index, which allows a link to family. The state of the subelement. Aailable alues are: on off The subelement is switched to off by the inentory process after a period of time and a number of retries defined in the inentory profile tool. Supply information on the inariant state, which is used in internal. UNIX name of the user who created this subelement. Date that the element was inserted or updated in the database, in number of seconds since 1 January 1970. The method used to add the sub-element to the database. (inentory, resmgr, and so on.) Description of the family name (Linked to the discoery formula.) Chapter 4. Managing Tioli Netcool Performance Manager objects 27

Column Name seprp.name seprp.datatype seprp.alue seprp.propertyname:alue ulabel Description Name of the property of the subelement. Use this column name to export or import all (multiple) properties. Do not use spaces in the property name. Subelement property data type. Aailable alues are: string (default) - if this contains a alue, seprp.name must contain a alue. float Value of the subelement property. If this contains a alue, "seprp.name" must also contain a alue. Value of a specific subelement property. For example, "seprp.customer:alue" is the alue of the property Customer for this sub-element. Use this column name to export or import a single property. If you export using this column name, only subelements that hae a alue for this column are included in the output. Description field. The ulabel column name can also return information concerning resources that hae been retired or deleted from inentory. The returned infomation for a retired resource includes the following: "Action: Retired;Date: "dateofdelete";profile: "profilename";lastsee: "date";lastmissing: "missingnumber";option: "missingcountinprofile LimiteDateInProfil" Where: Action: Retired - Specifies that the resource has been retired. Date: "dateofdelete" - Specifies when the resource was retired. Profile: "profilename" - Specifies the name of the inentory profile that was used to discoer the resource. LastSee: "date" - Specifies the date when the resource was last detected in the inentory. LastMissing: "missingnumber" - Specifies the number of times inentory has failed to detect the resource. Option: "missingcountinprofile LimiteDateInProfil" - Specifies the retry count and age limit criteria defined in the inentory profile for deleting resources. Group or Rule Column Names 28 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

The following table lists the group or rule column names: Column Name dbindex npath name type user rule cond state origin date lgparent lgchild Description Oracle unique internal database index Entire path of the group (including the group name) Group name Group type (rule, static, generated) User who has created the group or the rule Index of a generated rule. (The Index rule that has generated this group.) Condition of the rule if it is a rule Either on or off for a rule. The rule is idle when off. Group origin (imported, inentory) Group's creation date Supplies only the parent group, not the leaf group Index of the child group Nomenclature Column Names The following table lists the nomenclature column names: Column Name dbindex npath Description Oracle's unique internal database index for the nomenclature path. The path for this nomenclature. For the endor: ~Vendors~"endorName" For example, ~Vendors~3Com For the node type: ~NodesType~"node type"~"vendor" For example, ~NodesType~Probe~Netscout The nodetype must be the leel -2. ncl.dbindex ncl.name ncl.oid ncl.type Note: family is not grouped. Index of the nomenclature Name of the nomenclature Object ID of the nomenclature, which must be unique for type SysObjectID Nomenclature type, which can include SysObjectID (for encl), Vendor, iftype (for family) Chapter 4. Managing Tioli Netcool Performance Manager objects 29

Design objects The following tables list the column names used for the Tioli Netcool Performance Manager objects related to design. Formula Column Names The following table lists the formula column names: Column Name Description dbindex Oracle unique internal database index name Formula name data Formula data exprtype Not used (included for compatibility with a preious ersion) type Formula type, which includes import, snmp, oid, cfl, property and so on. comment Formula comment datatype Formula data type date Formula creation date state State of the formula cure Not used (included for compatibility with a preious ersion) nbhost Historic property, which must be set to 1 defvalue Not used for formula domaine Not used (included for compatibility with a preious ersion) inariant Not used for formula (only for property) subtype Not used (included for compatibility with a preious ersion) genericid Link to the generic formula Idx user User who has created the formula (can include Apde, puser and so on) origin Origin of the formula. (can include Apinstall, resmgr, unknown, and so on.) idxfrm Same index as dbindex (link on the MIB table) mibpath Name of the MIB(s) used by the formula. miborigin MIB origin. (can include Apinstall and so on.) mibdate Date of last MIB update mibuser User who has created the link to this MIB Formula Group Column Names The following table lists the formula group column names: Column Name Description 30 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

dbindex npath nname lgparent LgChild fgparent.name Oracle unique internal database index Formula group path Formula long name, which is the npath~name Supplies only the parent group (not the leaf group) Index of the child group fgparent allowed to see the name or dbindex of the parent group Property Column Names The following table lists the property column names. Column Name dbindex name datatype inariant state defvalue comment Description Oracle unique internal database index. Name of property (do not use spaces.) Type of properties (string/float.) Distinguishes among element, sub-element, and report user When you use the keywords propertye, propertyse, and propertyru a filter is automatically done respectiely on type<e>, type<se>, type<dvuser>. Not used (included for compatibility with preious ersion.) Default alue. Description field. Threshold Column Names The following table lists the threshold column names. Column Name IdxMetric fgp.nname IdxGroup segp.name IdxResource se.name mode Description Metric Id (formula dbindex) Metric name (full path) Sub-Element Group Id (sub-element group dbindex) Sub-Element Group name Sub-Element Resource Id (sub-elment dbindex) Sub-Element Resource name Mode of the threshold 1 = Under 2 = Oer 3 = Band Chapter 4. Managing Tioli Netcool Performance Manager objects 31

thrstat thrcalc thrcalcvalue Column Name brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime Define which statistic will be used by the CME to calculate the threshold information: 0=raw(default) 1=min 2=max 3=ag 4=sum 5=count 6=squality 7=percentile The calculation mode to be used to determine percentage oer/under the threshold. Values for this field include: 0=standard means: abs(value-leel)/ abs(leel) 1=normalized means: abs(value-leel)/(critical_leelwarning_leel) 2=scaled means: abs(value-leel)/scale where scale = thrcalcvalue The alue used for calculating the percentage oer/under threshold in scaled mode. Description Leel of the critical threshold for burst thresholds. Null implies that the threshold isn't defined Leel of the warning threshold for burst thresholds. Null implies that the threshold is not defined. Time limit for the critical period threshold in seconds. 0 indicates that the threshold is iolated when the metric exceeds the threshold. Time limit for the warning period threshold in seconds Indicates if Tioli Netcool Performance Manager has to generate eents for the period threshold. 0=no 1=yes Leel of the critical threshold for period thresholds. Null implies that the threshold is not defined Leel of the warning threshold for period thresholds. Null implies that the threshold is not defined Time limit for the critical period threshold in seconds 32 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

prdwrnngtime prdperiod prdgeneent dtedate Time limit for the warning period threshold in seconds Define the period: 1 = Day 2=Week 3 = Month 4 = All means that the CME will use the period of the aggregation tables Whether Tioli Netcool Performance Manager has to generate eents for the burst threshold. 0=no 1=yes The date and time the action (STR_ACTION) takes effect. Actions cannot be applied in the past and only take effect on the hour. The alue is in seconds since January 1, 1970 GMT. Use instead of dtedate_date to conert it to the following format MM/DD/YYYY HH:mm. Requests The following tables list the column names used for the Tioli Netcool Performance Manager objects related to requests. Subelement Group Requests The following table lists the subelement group request column names. Column Name dbindex idxres idxfrm state storage status period idxcal origin user date Description Oracle unique internal database index Resource index or group index Formula index Request state (on or off.) Request storage (always or neer.) Request status (actie or idle.) Collection period in seconds Calendar used for the request Request origin (can be resmgr or Request Editor.) User who has created the request. Request creation date Percentile Column Names The following table lists the percentile column names. Chapter 4. Managing Tioli Netcool Performance Manager objects 33

Column Name dbindex idxres idxfrm state status alue Description Oracle unique internal database index Resource index or group index Formula index Request state, which can be on or off Request status, which can be actie or idle Value of percentile parameter Request Column Names The following table lists the column names for all requests. Column Name dbindex idxres idxfrm state storage status period idxcal origin user date type pctile Description Oracle unique internal database index Resource index or group index Formula index Request state: on off Request storage: always neer Request status: actie idle Period of collection in seconds Calendar used for the request Request origin: resmgr Request Editor User who has created the request Date of creation of the request Type of the request collection aggregation Value of percentile parameter for the 'aggregation' request type Calendar Column Names The following table lists the Calendar column names: 34 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Column Name dbindex name period state origin user date type subtype week fromday fromtime today totime Description Oracle unique internal database index Calendar name Polling period (for collection calendar obsolete) State of the Calendar: on off Origin of the Calendar User who created the Calendar. Creation or last update date. Use instead of date_date to conert it to the following format: MM/DD/YYYY HH:mm Type of Calendar line Aailable alues include: 1 for daily 2 for monthly 3 for weekly 4 for once Subtype alue aailable for each kind of Calendar. For example, aailable alues for daily calendar include: 1 for all days 2 for working days 3 for weekend days Define the days for the weekly calendar. The series begins on Sunday. Values include: 0 for off 1 for on For example, a Calendar with Monday, Tuesday and Friday defined as on, displays the following field: 0110010. Number for the first day of a monthly Calendar Define Calendar beginning time Number of the last day of a monthly Calendar Define Calendar ending time Timezone Column Names The following table lists the timezone column names: Column Name Description Chapter 4. Managing Tioli Netcool Performance Manager objects 35

dbindex name offset status comment date Unique Oracle internal database index number Unique timezone name (in this table) Time lag from GMT in seconds Aggregation set (aggset) database representation status: 0: configured 1: created 2 actie Only actie status (with all created in DB) can be used. Optional description of the aggregation set Date when the aggset takes effect. Use instead date_date to conert it to the following format MM/DD/YYYY HH:mm Inentory Profile Column Names The following table lists the Inentory profile column names: Column Name dbindex npath opt.dbindex opt.name opt.instance opt.alue Description Unique Oracle internal database index of the group Path for this group as defined by the name of the profile, followed by the step name and the option group Index of the inentory option Name of the inentory option Instance of the option alue, if one = 0, else 0 = n. Required when an option has multiple alues Value of the option. Report objects The following tables list the column names used for the Tioli Netcool Performance Manager objects related to reports. Web User Column Names The following table lists the Web user column names: Column Name dbindex name mail Description Unique Oracle internal database index Name of the report user Email address of the user 36 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

type date user ruprp.name ruprp.propertyname:alue ruprp.alue ruprp.datatype ruprp.prpidx ruprp.ruidx ruprp.defvalue Type of report user: Tioli Netcool Performance Manager USER EMAIL RECIPIENT DV SUPER USER Date that the report user was inserted or updated in the database, in number of seconds since 1 January 1970. Name of the user who created this report user. Name of the property of the report user. Use this column name to export or import all (multiple) properties. ruprp.alue Property alue of the report user. If this contains a alue, "ruprp.name" should also contain a alue. The alue of a specific property of the report user. For example, "ruprp.ipaddress:alue" is the alue of the ipaddress property of the report user. Do not use spaces in property names. If you export using this column name, only report users that hae a alue for this column are included in the output. List of all properties Datatype of the property of the report user. Aailable alues include: string (default) - if this contains a alue, ruprp.name should also contain a alue. float Property index Report user index Property default alue Report User Group Column Names The following table lists the report user group column names: Column Name dbindex npath name owner Description Unique Oracle internal database index Complete path of the group (including the group name) Name of the group rusr with type=email RECIPIENT Chapter 4. Managing Tioli Netcool Performance Manager objects 37

Application column names The following table lists the application column names. Column Name dbindex name url comment type typer data owner alias date user Description Unique Oracle internal database index Application name URL of the page that defines the isual characteristics of the report Comment Report type: 0 for ByResource 1 for ByGroup Type of application Reporter(Report) DVCR(template) DVRS(scheduler) Binary stream that holds the report properties Used by the scheduler Used by the scheduler Date that the application was inserted or updated in the database, in number of seconds since 1 January 1970. Name of the user who created this application. app can be grouped in agp (report group) Report Style Column Names The following table lists the report style column names. Column Name Description dbindex Unique Oracle internal database index definition Report style definition comment Report style comment name Report style name type Report style type. (Default alue is 0) apps can be grouped in agp (report group) Application Group Column Names The following table lists the application group column names. Column Name Description 38 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

dbindex npath name Unique Oracle internal database index Complete path of the group (including the group name) Group name Scheduler Column Names The following table lists the scheduler column names. Column Name dbindex name frequency user date idxtarget idxshed type state status start end success next failnb tuser tdate Description ID of the scheduled task Name of the scheduled task Frequency of the scheduled task Name of the latest user who changed the application Date when the latest change occurred Target index. For example, reporter Scheduled task index. Target type of the scheduled task. For example, DVCR for a reporter State of the DVCR task: ACTIVE SUSPENDED Current status of the scheduled task: SUSPEND STOP IDLE Serer_name> Timestamp that indicates the effectie start date when an ACTIVE task will run Timestamp that indicates the effectie end date when an ACTIVE task will no longer run Timestamp that indicates the last time this DVCR successfully ran Timestamp that indicates the next time this schedule will run Parameter that indicates the number of times the schedule failed to successfully complete component processes Name of the latest user that changes the application Date when the latest change occurred Chapter 4. Managing Tioli Netcool Performance Manager objects 39

Administration objects DM User Column Names The following table lists the DM user column names. Column Name dbindex name fullname gpname gpcomment module perms Description Unique Oracle internal database index User name, which must match the UNIX login name User full name (description field) Group user name. Users belonging to that group automatically inherit the group's rights. Group description Module names Access rights Registry Column Names The following table lists the registry column names. Column Name path name alue format Description Path of the registry Name of the registry Value for the registry Format (YYYY-MM-DD HH24:MI for a date for example). type 0=NUMBER 1=STRING 2=DATE 3=BOOLEAN flag 0=CONSTANT 1=VARIABLE Collector Information Column Names The following table lists Collector information column names. Column Name host port collector default Description The IP address or name of the Collector assigned to collect data on the element. The TCP/IP port of the Collector assigned to collect data on the element Collector number to which this channel is assigned. Indicates whether the Collector is the default (yes or no). 40 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

name pid user date display status instdir comment hostreg Name of the registered module. For example, pmd_1 Protocol identifier (pid) of the registered module User who launches the registered module. Date of the launching of the registered module. Use instead date_date to conert it to the following format MM/DD/YYYY HH:mm Display host where the registered module is running. Status of the registered module. Home directory path Description of the module Host name in the registry Registration Column Names The following table lists the registration column names. Column Name name host pid user date display port lock mode Description Name of the registered module. Host that is running the registered module Protocol identifier (pid) of the registered module User who launches the registered module. Date of the launching of the registered module. Use instead date_date to conert it to the following format MM/DD/YYYY HH:mm Display host where the registered module is running. Used only for the serer (pmd or proisoinfod). Name of the locked module 1 for r/w Using functions with column names Explains how to use functions with column names. These functions extend the use of column names, proiding additional actions on the data sets. The following table lists the functions aailable for use with column names. Function DECODE UPPER LOWER Description Conerts an enumeration integer alue into a string Conerts string types into upper case Conerts string types into lower case Chapter 4. Managing Tioli Netcool Performance Manager objects 41

TIME DATE COUNT, MAX, MIN, SUM Use only on time alues to transform the number of seconds into xxd xxh xxm xxs (day, hour, minute, second) Use only on a date alue to transform a number of second since 1970 in readable format. conert it to the following format MM/DD/YYYY HH:mm Use with numerics. For example, count the number of subelements belonging to an element. Another example, sum of all the columns that do not hae aggregation alues. Using the DECODE function The following examples of the DECODE function conert enumeration integer alues into strings. You can use DECODE to make a file easier to reiew. Example 1 The following command shows the output without the use of the DECODE function: resmgr -export app -colnames "name type" generates the following output: Host-Site with CoS - DC - specific protocol OUT _ 0 _ <E> Top N_Hosts _ 1 _ <E> Top N Host Conersations with CoS. _ 1 _ <E> Top N Host Conersations with No CoS _ 1 _ <E> Example 2 The following example shows the use of the DECODE function along with the export command: resmgr -export app -colnames "name type_decode" generates the following output: Host-Site with CoS - DC - specific protocol OUT _ ByResource _ <E> Top N_Hosts _ ByGroup _ <E> Top N Host Conersations with CoS. _ ByGroup _ <E> Top N Host Conersations with No CoS _ ByGroup _ <E> Example 3 The following command: resmgr -export app -colnames "name type" -file $DIR/DECODE_NO.dat generates the following output: # type = app # col = name type # filter = # order = # sep = _ # seprec = <E> # # cmdline = -export app -colnames "name type" Interface Volume Resource Detail Chart _ 0 _ <E> 42 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Interface Volume Resource _ 1 _ <E> Interface Volume Resource Threshold - Inbound Volume (octets) _ 1 _ <E> Interface Volume Resource Threshold - Inbound Throughput (bps) _ 1 _ <E> Interface Volume Resource Threshold - Outbound Volume (octets) _ 1 _ <E> Interface Volume Resource Threshold - Outbound Throughput (bps) _ 1 _ <E> Example 4 The following command: resmgr -export app -colnames "name type_decode" -file $DIR/DECODE_YES.dat generates the following output: # type = app # col = name type_decode # filter = # order = # sep = _ # seprec = <E> # # cmdline = -export app -colnames "name type_decode" Interface Volume Resource Detail Chart _ ByResource _ <E> Interface Volume Resource _ ByGroup _ <E> Interface Volume Resource Threshold - Inbound Volume (octets) _ ByGroup _ <E> Interface Volume Resource Threshold - Inbound Throughput (bps) _ ByGroup _ <E> Interface Volume Resource Threshold - Outbound Volume (octets) _ ByGroup _ <E> Interface Volume Resource Threshold - Outbound Throughput (bps) _ ByGroup _ <E> Using the UPPER function You can use the UPPER function with any string type to conert results into upper case. Example 1 The following command: resmgr -export elt -colnames "name" -filter "name_upper(*boston*)" generates the following output: bulk100-boston_100,12 _ bulk100-boston_0 _ bulk100-boston_100,13 _ Example 2 The following command: resmgr -export elt -colnames "name" -filter "name_upper(*boston*)" -file $DIR/UPPER_YES.dat generates the following output: # type = elt # col = name # filter = name_upper(*boston*) # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name" -filter "name_upper(*boston*)" 123_Boston _ Example 3 Chapter 4. Managing Tioli Netcool Performance Manager objects 43

The following command: resmgr -export elt -colnames "name" -filter "name(*boston*)" -file $DIR/UPPER_NO.dat generates the following output: # type = elt # col = name # filter = name(*boston*) # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name" -filter "name(*boston*)" Using the LOWER function You can use the LOWER function with any string type to conert results into lower case. Using the TIME function You can use the TIME function on time alues to transform the number of seconds into xxd xxh xxm xxs (day, hour, minute, second) Example 1 The following command: resmgr -export thrd -colnames "fgp.nname segp.npath brstcrtclleel brstcrtcltime" -filter "brstcrtcltime(!= 0 )" generates the following output: ~AP~Generic~Uniersal~Other~Inbound Loss (percent) _ ~NOC Reporting _ 14 _ -1 _ ~AP~Generic~Uniersal~Utilization~Storage Utilization (percent) _ _ 99 _ 7200 _ ~AP~Generic~Uniersal~Utilization~Storage Free (bytes) _ _ 160000 _ 3600 _ Example 2 The following command: resmgr -export thrd -colnames "fgp.nname segp.npath brstcrtclleel brstcrtcltime_time" -filter "brstcrtcltime(!= 0 )" generates the following output: ~AP~Generic~Uniersal~Other~Inbound Loss (percent) _ ~NOC Reporting _ 14 _ RESERVED _ ~AP~Generic~Uniersal~Utilization~Storage Utilization (percent) _ _ 99 _ 2h _ ~AP~Generic~Uniersal~Utilization~Storage Free (bytes) _ _ 160000 _ 1h 2m _ Example 3 The following command: resmgr -export thrd -colnames "fgp.nname segp.npath brstcrtclleel brstcrtcltime" -filter "brstcrtcltime(!= 0 )" -file $DIR/TIME_NO.dat generates the following output: # type = thrd # col = fgp.nname segp.npath brstcrtclleel brstcrtcltime # filter = brstcrtcltime(!='0') # order = # sep = _ # seprec = # # cmdline = -export thrd -colnames "fgp.nname segp.npath brstcrtclleel brstcrtcltime" -filter "brstcrtcltime(!='0')" 44 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

~AP~Generic~Uniersal~Utilization~Inbound Utilization (percent) _ ~Customer Facing Reporting _ 10 _ 900 _ ~AP~Generic~Uniersal~Utilization~Outbound Utilization (percent) _ ~Customer Facing Reporting _ 10 _ 900 _ ~AP~Generic~Uniersal~Utilization~Storage Utilization (percent) _ ~Tioli Netcool Performance Manager System Monitori ~AP~Generic~Uniersal~Utilization~Storage Free (bytes) _ ~Tioli Netcool Performance Manager System Monitoring _ 1600 ~AP~Generic~Uniersal~Aailability~Aailability (percent) _ ~Customer Facing Reporting _ 90 _ 900 _ ~AP~Generic~Uniersal~Other~Inbound Loss (percent) _ ~Customer Facing Reporting _ 1 _ 900 _ ~AP~Generic~Uniersal~Other~Outbound Loss (percent) _ ~Customer Facing Reporting _ 1 _ 900 _ The following command: resmgr -export thrd -colnames "fgp.nname segp.npath brstcrtclleel brstcrtcltime_time" -filter "brstcrtcltime(!= 0 )" -file $DIR/TIME_YES.dat generates the following output: ~AP~Generic~Uniersal~Utilization~Storage Utilization (percent) _ ~Tioli Netcool Performance Manager System Monitori ~AP~Generic~Uniersal~Utilization~Storage Free (bytes) _ ~Tioli Netcool Performance Manager System Monitoring _ 1600 # type = thrd # col = fgp.nname segp.npath brstcrtclleel brstcrtcltime_time # filter = brstcrtcltime(!='0') # order = # sep = _ # seprec = # # cmdline = -export thrd -colnames "fgp.nname segp.npath brstcrtclleel brstcrtcltime_time" -filter "brstcrtcltime ~AP~Generic~Uniersal~Utilization~Inbound Utilization (percent) _ ~Customer Facing Reporting _ 10 _ 15m _ ~AP~Generic~Uniersal~Utilization~Outbound Utilization (percent) _ ~Customer Facing Reporting _ 10 _ 15m _ ~AP~Generic~Uniersal~Aailability~Aailability (percent) _ ~Customer Facing Reporting _ 90 _ 15m _ ~AP~Generic~Uniersal~Other~Inbound Loss (percent) _ ~Customer Facing Reporting _ 1 _ 15m _ ~AP~Generic~Uniersal~Other~Outbound Loss (percent) _ ~Customer Facing Reporting _ 1 _ 15m _ Using the DATE function You can use the DATE function on a date alue to transform the number of seconds since 1970 into the following, readable format: MM/DD/YYYY HH:mm Example 1 The following command: resmgr -export elt -colnames "name date" generates the following output: bulk100-boston_1000,19 _ 1055363091 _ 192.168.69.245 _ 1057019303 _ 192.168.69.243 _ 1057019303 _ resmgr -export elt -colnames "name date_date" bulk100-boston_1000,19 _ 06/11/2003 22:24 _ 192.168.69.245 _ 07/01/2003 02:28 _ 192.168.69.243 _ 07/01/2003 02:28 _ Example 2 The following command: resmgr -export elt -colnames "name date" -file $DIR/DATE_NO.dat generates the following output: # type = elt # col = name date # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name date" default _ 1018224000 _ 192.168.1.3 _ 1056577282 _ Chapter 4. Managing Tioli Netcool Performance Manager objects 45

Delete_100000165_192.168.3.238 _ 1048621801 _ 192.168.127.2 _ 1056577282 _ 192.168.127.3 _ 1056577282 _ 192.168.127.5 _ 1067931931 _ 192.168.127.6 _ 1067931931 _ 192.168.127.7 _ 1056577282 _ COUNT,MIN,MAX,SUM can be used with numerics. For example: resmgr -export se -colnames "elt.name elt.profil encl.gpname se.name_count" generates the following output: bewan-router _ test2 _ _ 5 _ 192.168.69.243 _ testin1 _ Cisco Catalyst _ 2 _ 192.168.69.245 _ testin1 _ Cisco Catalyst _ 2 _ bulk100-boston_0 _ bulk_100 _ _ 10 _ Example 3 The following command: resmgr -export elt -colnames "name date_date" -file $DIR/DATE_YES.dat generates the following output: # type = elt # col = name date_date # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name date_date" default _ 04/08/2002 04:00 _ 192.168.1.3 _ 06/26/2003 01:41 _ Delete_100000165_192.168.3.238 _ 03/25/2003 23:50 _ 192.168.127.2 _ 06/26/2003 01:41 _ 192.168.127.3 _ 06/26/2003 01:41 _ 192.168.127.5 _ 11/04/2003 11:45 _ 192.168.127.6 _ 11/04/2003 11:45 _ 192.168.127.7 _ 06/26/2003 01:41 _ Using COUNT, MIN, MAX, SUM functions You can use these functions Example 1 The following command: resmgr -export se -colnames "elt.name elt.profil encl.gpname se.name_count" -file $DIR/COUNT.dat generates the following output: 46 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

#type=se # col = elt.name elt.profil encl.gpname se.name_count # filter = # order = # sep = _ # seprec = # # cmdline = -export se -colnames "elt.name elt.profil encl.gpname se.name_count" 172.31.0.31 _ Cisco_SAA _ Cisco _ 8 _ 172.31.0.41 _ Cisco_SAA _ Cisco _ 10 _ 172.31.0.51 _ Cisco_SAA _ Cisco _ 28 _ 172.31.1.2 _ Cisco_SAA _ Cisco _ 18 _ 192.168.1.3 _ Cisco_SAA _ Cisco _ 8 _ 192.168.127.1 _ Cisco_SAA _ Cisco Catalyst _ 232 _ 192.168.127.2 _ Cisco_SAA _ Cisco Catalyst _ 29 _ 192.168.127.254 _ Cisco_SAA _ _ 21 _ 192.168.127.3 _ Cisco_SAA _ Cisco Catalyst _ 29 _ 192.168.127.5 _ Cisco_SAA _ Cisco Catalyst _ 29 _ 192.168.127.6 _ Cisco_SAA _ Cisco Catalyst _ 29 _ 192.168.127.7 _ Cisco_SAA _ _ 53 _ 192.168.127.8 _ Cisco_SAA _ _ 53 _ 192.168.127.9 _ Cisco_SAA _ _ 53 _ Chapter 4. Managing Tioli Netcool Performance Manager objects 47

48 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 5. Exporting and importing objects The export syntax Explains how to use the resmgr command to import and export objects This section explains the syntax used for the export option of the resmgr command. You must include the mandatory options with the resmgr -export command and add other options for additional resmgr -export <object type> <mandatory options> <additional options> Mandatory options You must use the following options when issuing a resmgr export command. Option <object type> -colnames -rule Description name(is null) name(not null) a list of colnames. If no alue is used with the CLI and a default alue exists, the default alue is used. If you do not want to use the -colname option because you want to format the columns, use -rule. a string using the colnames with the syntax%(colname). Use to format the columns (need to use if you do not use -colnames.) Example The following example shows the use of the -rule option with a mix of text and ariable to specify the format for the columns. This modifies the construction of the subelement labels for import. resmgr -export elt -rule "the name of the element is : %(elt.name)" the name of the element is : bulk100-boston_1000,19 _ the name of the element is : 192.168.69.245 _ the name of the element is : 192.168.69.243 _ Refer to the chapters containing specific commands for additional examples of mandatory options. Copyright IBM Corp. 1997, 2012 49

Additional options You can use the following additional options with the export option. Option -filter -filterrule -order -distinct -ListForced Description Filter the results of the export command Broaden your filtering capabilities by entering a string against which results are compared to find matches. The syntax of the filter string is similar to the syntax of an SQL WHERE clause, so that you can filter on common SQL keywords such as OR, AND, LIKE, IN, and so forth. List columns in order Eliminate duplicate lines Force columns to display alues Using -filter The following option lets filter the results of the export command. -filter List of filtered alues "colname(alue)..", same syntax as -colnames. Lets you filter the results of a command. The following table lists aailable -filter alues: Values is null, not null any character with * (like operator is used) any character (= operator is used) relational operator (in,between,!=,>,<,..) 'any character' AND is made between filters Examples name(is null) name(not null) name(*ddd*) name(ddddd) name(!='ddd') number(<='10') name(in'ddd','aaa','bbb') between('0 and 3') Example resmgr -export elt -colnames "name profil state missing" -filter "missing(between 0 and 3 ) name_upper(*bost*)" bulk100-boston_1000,18 _ bulk_100 _ on _ 0 _ bulk100-boston_100,11 _ bulk_100 _ on _ 0 _ bulk100-boston_1000,19 _ bulk_100 _ on _ 0 _ 50 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Using -filterrule About this task You can use the following filter option if you need to broaden your filtering capabilities; for example if -filter is too restricted. You can enter a string against which results are compared to find matches. -filterrule "string" Note: The syntax of the filter string is similar to the syntax of an SQL WHERE clause, so that you can filter on common SQL keywords such as OR, AND, LIKE, IN, and so forth. Example 1 resmgr -export elt -colnames "name profil state" -filterrule "%(elt.profil) LIKE %T% OR %(elt.state) = on " -file $DIR/filterRule1.dat marketing.quallaby.com _ QuallabyNetwork _ on _ acacia.quallaby.com _ QuallabyNetwork _ on _ eng1.quallaby.com _ QuallabyNetwork _ on _ u440.quallaby.com _ QuallabyNetwork _ on _ tadpole.quallaby.com _ QuallabyNetwork _ on _ dhcp195.quallaby.com _ QuallabyNetwork _ on _ 192.168.127.254 _ Cisco_SAA _ on _ Example 2 The percentage sign (%) is considered as any 0-n character and _ (underscore) is considered one character. If you need to use the underscore in your filter, you must include an escape character for it. resmgr -export elt -colnames "name profil state" -filterrule "%(elt.profil) LIKE %T% OR %(elt.state) = on " -file $DIR/filterRule1.dat marketing.quallaby.com _ QuallabyNetwork _ on _ acacia.quallaby.com _ QuallabyNetwork _ on _ eng1.quallaby.com _ QuallabyNetwork _ on _ u440.quallaby.com _ QuallabyNetwork _ on _ tadpole.quallaby.com _ QuallabyNetwork _ on _ dhcp195.quallaby.com _ QuallabyNetwork _ on _ 192.168.127.254 _ Cisco_SAA _ on _ Example 3 In the following example the string %(xxx) LIKE '%@_%' ESCAPE '@' tells ORACLE that the escape character is @. If you need to use @ in your condition, you can choose another character. resmgr -export se -colnames "name profil" -filterrule "%(elt.profil) LIKE %@_protocol% ESCAPE @ " -file $DIR/filterRule2.dat NF-iphost-site-flow-CoffeeBucks _ NF_protocol _ NF-site-Siler-CoffeeBucks _ NF_protocol _ NF-iphost-site-flow-Gold-CoffeeBucks _ NF_protocol _ NF-site-iphost-flow-Gold-CoffeeBucks _ NF_protocol _ NF-as-site-flow-CoffeeBucks _ NF_protocol _ Chapter 5. Exporting and importing objects 51

NF-site-site-flow-CoffeeBucks _ NF_protocol _ NF-site-site-flow-Gold-CoffeeBucks _ NF_protocol _ NF-site-iphost-flow-Siler-CoffeeBucks _ NF_protocol _ NF-iphost-site-flow-Siler-CoffeeBucks _ NF_protocol _ The name is filter in "*_protocol*" Using -order You can use the following command to list columns in order. -order "colnames" You use the same syntax used for all -colnames, except for those that are logical entities (npath, nname.) resmgr -export elt -colnames "name profil state" -order "profil" # type = elt # col = name profil state # filter = # order = profil # sep = _ # seprec = # rule = # filterrule = # # cmdline = -export elt -colnames "name profil state" bulk100-boston_100,12 _ bulk_100 _ on _ bulk100-boston_0 _ bulk_100 _ on _ bulk100-boston_100,13 _ bulk_100 _ on _ bulk100-boston_100,14 _ bulk_100 _ on _ bulk100-boston_1000,10 _ bulk_100 _ on _ bulk100-boston_1000,11 _ bulk_100 _ on _ bulk100-boston_1000,12 _ bulk_100 _ on _ bulk100-boston_1000,13 _ bulk_100 _ on _ bulk100-boston_1000,15 _ bulk_100 _ on _ bulk100-boston_1000,19 _ bulk_100 _ on _ bulk100-boston_100,11 _ bulk_100 _ on _ bulk100-boston_1000,18 _ bulk_100 _ on _ bulk100-boston_100,10 _ bulk_100 _ on _ bulk100-boston_1000,17 _ bulk_100 _ on _ bulk100-boston_1000,16 _ bulk_100 _ on _ bulk100-boston_1000,14 _ bulk_100 _ on _ bulk100-boston _ bulk_100 _ on _ bulk100-boston_100,19 _ bulk_100 _ on _ bulk100-boston_100,18 _ bulk_100 _ on _ bulk100-boston_100,17 _ bulk_100 _ on _ bulk100-boston_100,16 _ bulk_100 _ on _ bulk100-boston_100,15 _ bulk_100 _ on _ add_elt2 _ profil1 _ on _ add_elt3 _ profil1 _ on _ 52 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

add_elt1 _ profil1 _ on _ add_elt4 _ profil1 _ on _ dber _ test1 _ on _ Using -distinct You can use the following command to eliminate duplicate result lines. -distinct 1 (by default : 0) resmgr -export elt -colnames "profil" -distinct 1 bulk_100 _ test2 _ testin1 _ testnoreload _ _ Using -ListForced You can use the following option to force columns to display alues. -ListForced "column1 alue1 [column2 alue2]... [columnn aluen]" Use this option with the following Tioli Netcool Performance Manager object types: eprp seprp ruprp encl.name fam.name Example resmgr -ListForced "seprp.customer:alue \"\" seprp.cos:alue \"\"" -export se -colnames "elt.name name label seprp.customer:alue seprp.cos:alue" router1 _ router1_interface<1> _ Ethernet[1] _ Coca Cola _ Gold _ router1 _ router1_interface<2> _ Ethernet[3] _ _ _ router2 _ router2_interface<1> _ Ethernet[1] _ Air France _ _ router2 _ router2_interface<2> _ Ethernet[2] _ _ Siler _ router2 _ router2_interface<3> _ Ethernet[3] _ _ _ resmgr -export elt -colnames "name eprp.contact:alue" -ListForced "eprp.contact:alue \"\"" 192.168.69.245 _ _ Delete_200000092_192.168.127.1 _ _ Delete_200000098_192.168.127.7 _ _ 192.168.69.243 _ _ Chapter 5. Exporting and importing objects 53

Using mandatory links with elements About this task You can use the following option to force a link to be mandatory (or not). Use for elt: scf,encl,eprp. See Chapter 6, Managing resources, on page 73 for more information. Diiding results into multiple lines About this task You can diide results into multiple lines using the following option: -split use only with eprp, seprp, ruprp Diide results into multiple lines resmgr -export elt -colnames "name eprp.name eprp.alue" -split -file $DIR/split_elt.dat 172.31.0.31 _ ipaddress _ 172.31.0.31 _ 172.31.0.31 _ ipname _ 172.31.0.31 _ 172.31.0.31 _ physaddress _ 6.0.3.227.233.33.160 _ 172.31.0.31 _ Cisco Internetwork Operating System Software \nios (tm) C2600 Software (C2600-T _ 172.31.0.31 _ sysname _ "c2610-31-ler" _ 172.31.0.41 _ ipaddress _ 172.31.0.41 _ 172.31.0.41 _ ipname _ 172.31.0.41 _ Display results on a single line resmgr -export elt -colnames "name eprp.name eprp.alue" -file $DIR/splitno_elt.dat 172.31.0.31 _ ipaddress _ 172.31.0.31 _ ipname _ 172.31.0.31 _ physaddress _ 6.0.3.227.233.33.160 _ sysdescr _ Cisco Internetwork Operat ing System Software \nios (tm) C2600 Software (C2600-T _ sysname _ "c2610-31-ler" _ 172.31.0.41 _ ipaddress _ 172.31.0.41 _ ipname _ 172.31.0.41 _ physaddress _ 6.0.48.25.95.152.192 _ sysdescr _ Cisco Internetwork Operat ing System Software \nios (tm) C2600 Software (C2600-T _ sysname _ "c2610-41-lsr" _ 54 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Including field separators About this task You can include field separators between fields when you export data (and import as well.) The default separator alue is an underscore ( _.) When you use a field separator from the command line, you need to enclose it in single (' ') or double quotes (" "). -sep resmgr -export elt -colnames "name profil state" -sep "," # type = elt # col = name profil state # filter = # order = #sep=, # seprec = # rule = # filterrule = # # cmdline = -export elt -colnames "name profil state" default,,on, bulk100-boston_100,12,bulk_100,on, bulk100-boston_0,bulk_100,on, bulk100-boston_100,13,bulk_100,on, bulk100-boston_100,14,bulk_100,on, Including record separators About this task You can include record separators when you export data. The default record separator alue is "end of line." You can also use the is Mandatory alue when colnames such as app or frm could potentially include the end of line in their field. -seprec resmgr -export elt -colnames "name profil state" -sep "," -seprec ";" # type = elt # col = name profil state # filter = # order = #sep=, # seprec = ; # rule = # filterrule = # # cmdline = -export elt -colnames "name profil state" default,,on,; bulk100-boston_100,12,bulk_100,on,; bulk100-boston_0,bulk_100,on,; Chapter 5. Exporting and importing objects 55

bulk100-boston_100,13,bulk_100,on,; bulk100-boston_100,14,bulk_100,on,; Specifying a file name About this task You can specify a filename for exporting tasks. If you do not use the -file option (the default is that -file is not used) the output will be UNIX standard output. If you need to include a path, you can use the -dirpath option or set the entire path enclosed in double quotes (" ".) You can also enter the entire path for a file together with the filename. -file resmgr -export elt -colnames "name profil state" -file test1 Specifying path locations About this task You can specify a path location for exported (as well as imported) data files. Because this option specifies only the path, you need to use the "-file" option if you also want to specify the name of the file. Remember to enclose the path in single (' ') or double quotes (" ".) -dirpath resmgr -export elt -colnames "name profil state" -file test1 -dirpath "/tmp" Create the file : /tmp/test1. Remoing the header About this task useful when scripting and pipe to other tools -nohead Remoe the header for export resmgr -export elt -colnames "name" -nohead -file $DIR/noHead.dat 172.31.0.31 _ 172.31.0.41 _ 172.31.0.51 _ 172.31.1.2 _ 192.168.1.3 _ 192.168.127.1 _ 192.168.127.2 _ 192.168.127.254 _ 192.168.127.3 _ 192.168.127.4 _ 192.168.127.5 _ 192.168.127.6 _ 192.168.127.7 _ 192.168.127.8 _ 56 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

192.168.127.9 _ 192.168.64.253 _ 192.168.66.2 _ 192.168.68.162 _ APRouterforprobe _ Burned_100008089_192.168.1.3 _ CoffeeBucks-192.168.1.1 _ Delete_100000165_192.168.3.238 _ Delete_100000174_192.168.2.2 _ Display with headers resmgr -export elt -colnames "name" -file $DIR/withHead.dat # type = elt # col = name # filter = # order = # sep = _ # seprec = # cmdline = -export elt -colnames "name" 172.31.0.31 _ 172.31.0.41 _ 172.31.0.51 _ 172.31.1.2 _ 192.168.1.3 _ 192.168.127.1 _ 192.168.127.2 _ 192.168.127.254 _ 192.168.127.3 _ 192.168.127.4 _ 192.168.127.5 _ 192.168.127.6 _ 192.168.127.7 _ 192.168.127.8 _ 192.168.127.9 _ 192.168.64.253 _ 192.168.66.2 _ 192.168.68.162 _ APRouterforprobe _ Burned_100008089_192.168.1.3 _ CoffeeBucks-192.168.1.1 _ Delete_100000165_192.168.3.238 _ Delete_100000174_192.168.2.2 _ Display the number of columns without headers resmgr -export elt -colnames "name" -nohead wc -l 23 Chapter 5. Exporting and importing objects 57

The import syntax Import (insert or update) metadata. This option lets you specify the type (object type) of data for importing. resmgr -import <object type> -mode [insert update Ifirst] Mandatory options You must use the following options when issuing a resmgr import command. Option <object type> -colnames Description name(is null) name(not null) a list of colnames is mandatory. If -file or -line is omitted, UNIX standard input (stdin) is used to let you pipe the standard import. -mode insert - insert only. Use this alue if you are importing a large amount of new data into the database. If the resource already has a alue for this column, it is not updated. update - update only. If the resource does not hae a alue for this column, data is not inserted. Ifirst - insert first (default). First attempt to insert. If the resource already has a alue for this column, the alue is updated. Using -colnames About this task Use to display a list of colname or colname(alue). Example 1 The alue is taken from the file or line and the nop option is used to skip columns. resmgr -import elt -colnames "name nop type state profil(prof1) collector(3)" -file Test1.rgr ImporBulk _ aaaa _ import_ _ on _... Example 2 The alue of the colnames can be concatenation of multiple alues taken in the file (the alue gien is take for all lines.) resmgr -import elt -colnames "name col1 col2 type state profil(myprof%(col1)_%(col2)) collector(3)" -file Test1.rgr ImporBulk _ al1 _ al2 _ import_ _ on _... Example 3 58 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

You can use the option OLD_colname when updating the colname used as an index for finding the record. resmgr -import elt -colnames "OLD_name name" -line "NameNow _ NewName" Including field separators About this task You can include field separators between fields when you import data (and export as well.) The default separator alue is an underscore ( _.) When you use a field separator from the command line, you need to enclose it in single (' ') or double quotes (" "). -sep Including record separators About this task You can include record separators when you export data. The default record separator alue is "end of line." You can also use the ismandatory alue when colnames such as app or frm could potentially include the end of line in their field. (You must also use the same for the export.) -seprec Specifying file names About this task You can specify a filename for exporting tasks. If you do not use the -file option (the default is that neither -file nor -line option is used,) the output will be UNIX standard output. If you need to include a path, you can use the "-dirpath" option or set the entire path enclosed in double quotes (" ".) You can also enter the entire path for a file together with the filename. -file Specifying path locations About this task You can specify a path location for imported (as well as exported) data files. Because this option specifies only the path, you need to use the -file option if you also want to specify the name of the file. Remember to enclose the path in single (' ') or double quotes (" ".) -dirpath Specifying input data About this task You can specify input data from the command line. -line resmgr -delete elt -colnames "name" -line "bulk100-boston_0" info : === delete : DELETE ON Element ( bulk100-boston_0 ) (exists) Title : === CHANGES : {1 Deleted of elt} Info : === Inform Collector On hebus:3002 Chapter 5. Exporting and importing objects 59

Forcing the creation date About this task You can force the creation date stamped. -histodate 0: current date (not forced default alue) 1: force the date to the alue defined Example resmgr -import se -colnames "name elt.name instance date(1057015945)" -histodate 1 Import the se at : 07/01/2003 01:32 Reloading collectors About this task You can reload the Collectors. -reloadcol al Reload Collectors = on off forced (default = on ). Aailable alues are as follows: on (default) - reload collectors to reread the database for changes or updates off - do not reload collectors forced - always reload collectors Examples resmgr -import... -reloadcol off resmgr -import... -reloadcol on resmgr -import... -reloadcol forced You are only allowed to reload only the last time een if there were no changes in the last import. The resyncronization messages you see after entering this command will ary according to the exact metadata change that are made by the command. Analyzing Tioli Netcool Performance Manager object About this task You can generate an analysis of the resource tables for the following Tioli Netcool Performance Manager objects: elt se egp segp -analyze <object type> Example resmgr -analyze se Info : === ANALYZE : ON se (Synchro) 60 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Using a configuration file About this task You can create a configuration file with sets of commands and options that you want to execute more than once. Many of the options in Resource Manager can be used in a configuration file. You can specify different combination of commands and options in a configuration file. You can specify multiple configurations by using keywords. Note: If you specify an option both in a configuration file and from the command line, the command line oerrides the configuration file. An example of a configuration file: To run a configuration file, enter: Chapter 5. Exporting and importing objects 61

Line-by-Line explanation *exportall_list: exporte exportsel This line specifies a list of configurations. When you specify exportall on the command line for the -config option, the configurations are executed Item Description Syntax Requirements * Indicates the beginning of an operatie line. exportall _ List The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. Separates the configuration name from the command line option or keyword. A keyword to indicate that a list of other configurations in the file follows. : Separates the keyword from the list of configuration names. exporte The name of another configuration in the file. exportsel The name of another configuration in the file. Should be the first character on the line. Spaces before are not allowed and spaces after are optional. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. "L" must be capitalized. Spaces before and after are optional. Multiple names are allowed and spaces between each name are required. Multiple names are allowed and spaces between each name are required.!-----------------------------------------! export all elements with attributes!----------------------------------------- Lines beginning with an exclamation point (!) are comments. *exporte_operation: export elt This line specifies that the operation for the exporte configuration is export elements. The equialent command line is as follows: -export elt Since the exporte configuration is part of the list for the exportall configuration on the preious line, this configuration is run by specifying either exportall or exporte for the -config option on the command line. Item Description Syntax Requirements 62 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

* Indicates the beginning of an operatie line. Should be the first character on the line. exporte The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. _ Separates the configuration name from the command line option or keyword operation A keyword to indicate that what follows is an operation. : Separates the keyword from the operation export The operation, in this case export. Valid alues are import, export, and delete. elt The type of resource, in this case elements. Any alues that are alid on the command line are also alid in a configuration file. Spaces before are not allowed. Spaces after are optional. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. Should be all lower case. Spaces before and after are optional. Spaces are required between the operation and the type of resource should be all lowercase. Spaces are required between the operation and the type of resource. Capitalization must be the same as on the command line. *exporte_colnames: name comment This line specifies that the column names to be exported are "name" and "comment." The command line equialent is: -colnames "name comment" Item Description Syntax Requirements * Indicates the beginning of an operatie line. Should be the first character on the line. Spaces before are not allowed. Spaces after are optional. Chapter 5. Exporting and importing objects 63

exporte _ colnames The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. Separates the configuration name from the command line option or keyword. A command line option. In this case, -colnames. Command line options are listed under Displaying resource manager options on page 22. : Separates the command line option from its alue. name A column name Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. No hyphen before the option. Capitalization needs to be the same as on the command line. Spaces before and after are optional. Can be any alid column name. See Using column names on page 24 for the list of possible column names. comment A column name Multiple column names are allowed. Spaces are required between each of the column names in the list. Can be any alid column name. See Using column names on page 24 for the list of possible column names. Multiple column names are allowed. Spaces are required between each of the column names in the list. *exporte_file: elements This line specifies that the name of the output file is "elements." The command line equialent is: -file elements Item Description Syntax Requirements 64 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

* Indicates the beginning of an operatie line. Should be the first character on the line. exporte _ file The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. Separates the configuration name from the command line option or keyword. A command line option. In this case, -file. Spaces before are not allowed. Spaces after are optional. Letters and numbers are allowed. Spaces are not allowed using a meaningful name is recommended. Spaces are not allowed before or after. No hyphen before the option. : Separates the command line option from its alue. elements The name of the file in which to place the exported data. Capitalization must be the same as on the command line. Spaces before and after are optional. Should be only the file name. If a path is required use the dirpath option, *exporte_dirpath:./output. *exporte_dirpath:./output This line specifies that the path for the output file is "./output" The equialent command line is: -dirpath "./output" Item Description Syntax Requirements * Indicates the beginning of an operatie line. exporte _ The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. Separates the configuration name from the command line option or keyword Should be the first character on the line. Spaces before are not allowed and spaces after are optional. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. Chapter 5. Exporting and importing objects 65

dirpath A command line option. In this case, -dirpath. Command line options are listed under Working with resmgr on page 22. : Separates the command line option from its alue../output The path for the file in which to place the exported data. No hyphen before the option. Capitalization needs to be the same as on the command line. Spaces before and after are optional. Specify only the path. Specify the name of the file with the file option. The directory needs to exist before executing the command. If the directory does not exist, the command fails.!-----------------------------------------! export all sub-elements with attributes!----------------------------------------- Lines beginning with an exclamation point (!) are comments. *exportsel_list: exportse exportsem This line specifies a list of configurations. When exportsel is specified on the command line for the -config option, all of the configurations listed on the right are executed together. Because the exportsel configuration is part of the list for the exportall configuration on the first line, this configuration is run by specifying either exportall or exportsel for the -config option on the command line. Item Description Syntax Requirements * Indicates the beginning of an operatie line. Should be the first character on the line. Spaces before are not allowed. exportsel _ The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. Separates the configuration name from the command line option or keyword. Spaces after are optional. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. 66 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

List A keyword to indicate that what follows is a list of other configurations in the file. : Separates the keyword from the list of configuration names. exportse The name of another configuration in the file. "L" must be capitalized. Spaces before and after are optional. Multiple names are allowed. exportsem The name of another configuration in the file. Spaces between each name are required. Multiple names are allowed. Spaces between each name are required. *exportse_operation: export se This line specifies that the operation for the exportse configuration is export sub-elements. The equialent command line is: -export se Item Description Syntax Requirements * Indicates the beginning of an operatie line. exportse The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. _ Separates the configuration name from the command line option or keyword. operation A keyword to indicate that what follows is an operation. : Separates the keyword from the operation. export The operation, in the case export. Valid alues are import, export, and delete. Should be the first character on the line. Spaces before are not allowed. Spaces after are optional. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. Should be all lower case. Spaces before and after are optional. Spaces are required between the operation and the type of resource must be all lowercase. Chapter 5. Exporting and importing objects 67

se The type of resource, in this case sub-elements. Any alues that are alid on the command line are also alid in a configuration file. Spaces are required between the operation and the type of resource. Capitalization needs to be the same as on the command line. *exportse_colnames: name date This line specifies that the column names to be exported are "name" and "date." The equialent command line is: -colnames "name date" Item Description Syntax Requirements * Indicates the beginning of an operatie line. Should be the first character on the line. Spaces before are not allowed. exportse _ colnames The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. Separates the configuration name from the command line option or keyword. A command line option. In this case, -colnames. Command line options are listed in Working with resmgr on page 22. : Separates the command line option from its alue. name A column name Spaces after are optional. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. No hyphen before the option. Capitalization must be the same as on the command line. Spaces before and after are optional. Can be any alid column name. See Using column names on page 24 for the list of possible column names. Multiple column names are allowed. Spaces are required between each of the column names in the list. 68 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

date A column name Can be any alid column name. See Resource column names on page 24 for the list of possible column names. Multiple column names are allowed. Spaces are required between each of the column names in the list. *exportse_file: subel1 This line specifies that the name of the output file is "subel1." The equialent command line is: -file subel1 Item Description Syntax Requirements * Indicates the beginning of an operatie line. Should be the first character on the line. Spaces before are not allowed. exportse _ file The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. Separates the configuration name from the command line option or keyword. A command line option. In this case, -file. Command line options are listed in Working with resmgr on page 22. : Separates the command line option from its alue. subel1 The name of the file in which to place the exported data. Spaces after are optional. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. No hyphen before the option. Capitalization must be the same as on the command line. Spaces before and after are optional. Should be only the file name. If a path is required use the dirpath option. *exportsem_operation: export se This line specifies that the operation for the exportsem configuration is export sub-elements. The equialent command line is: -export subelt Chapter 5. Exporting and importing objects 69

Item Description Syntax Requirements * Indicates the beginning of an operatie line. exportsem The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. _ Separates the configuration name from the command line option or keyword. operation A keyword to indicate that what follows is an operation. : Separates the keyword from the operation. export The operation, in the case export. Valid alues are import, export, and delete. Should be the first character on the line. Spaces before are not allowed. Spaces after are optional. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. Should be all lower case. Spaces before and after are optional. Spaces are required between the operation and the type of resource. se The type of resource, in this case sub-elements. Any alues that are alid on the command line are also alid in a configuration file. Needs to be all lowercase. Spaces are required between the operation and the type of resource. Capitalization must be the same as on the command line. *exportsem_colnames: name instance This line specifies that the column names to be exported are "name" and "instance." The equialent command line is: -colnames "name instance" Item Purpose Syntax Requirements * Indicates the beginning of an operatie line Should be the first character on the line. Spaces before are not allowed and spaces after are optional. 70 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

exportsem _ colnames The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. Separates the configuration name from the command line option or keyword. A command line option. In this case, -colnames. : Separates the command line option from its alue. name A column name. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. No hyphen before the option. Capitalization must be the same as on the command line. Spaces before and after are optional. Can be any alid column name. See Using column names on page 24 for the list of column names. instance A column name. Multiple column names are allowed. Spaces are required between each of the column names in the list. Can be any alid column name. See Using column names on page 24 for the list of column names. Multiple column names are allowed. Spaces are required between each of the column names in the list. *exportsem_file: subel2 This line specifies that the name of the output file is "subel2." The same thing on the command line is: -file subel2 Item Description Syntax Requirements * Indicates the beginning of an operatie line. Should be the first character on the line. Spaces before are not allowed. Spaces after are optional. Chapter 5. Exporting and importing objects 71

exportsem _ file The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time. Separates the configuration name from the command line option or keyword. A command line option. In this case, -file. Letters and numbers are allowed. Spaces are not allowed. Using a meaningful name is recommended. Spaces are not allowed before or after. No hyphen before the option. : Separates the command line option from its alue. subel2 The name of the file in which to place the exported data. Capitalization must be the same as on the command line. Spaces before and after are optional. Should be only the file name. If a path is required use the dirpath option, *exporte_dirpath:./output. 72 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 6. Managing resources Working with elements This chapter explains how to use resmgr to export, import, and manage different Tioli Netcool Performance Manager object types that belong to the resource category. Resources include the following object types: Elements Subelements and subelement groups Composite subelements Nomenclature Before using the commands in this chapter, reiew the information in Chapter 4, Managing Tioli Netcool Performance Manager objects, on page 15. This section contains the commands you can use to manage elements. When you use resgmr to work with the elements, you work with the following object types: elt scf eprp eproperty encl endor chnl Links can exist among elements and the following Tioli Netcool Performance Manager object types: Exporting elements The following examples of resmgr command used to export elements contain the command and the results of that command. Exporting all elements resmgr -export elt -colnames "dbindex name type encl.name state origin profil collector missing comment" -file $DIR/elt_all.dat # type = elt # col = dbindex name type encl.name state origin profil collector missing comment # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "dbindex name type encl.name state origin profil collector missing comment" 200000632 _ Delete_200000632_192.168.3.254 _ snmp _ 3Com Hub (SuperStack II PS Hub 40) _ off _ inentory _ Cisco_SAA _ 1 _ _ _ Copyright IBM Corp. 1997, 2012 73

200000788 _ Delete_200000788_192.168.3.37 _ snmp _ BayStack 350T _ off _ inentory _ Cisco_SAA _ 1 _ _ _ 100000219 _ deelopment.quallaby.com _ snmp _ HP Printer ETHERNET MULTI-ENVIRONMENT _ on _ inentory _ QuallabyNetwork _ 1 _ _ _ 100000218 _ hpcolor.quallaby.com _ snmp _ HP Printer ETHERNET MULTI-ENVIRONMENT _ on _ inentory _ QuallabyNetwork _ 1 _ _ _ 100000217 _ ps.quallaby.com _ snmp _ HP Printer ETHERNET MULTI-ENVIRONMENT _ on _ inentory _ QuallabyNetwork _ 1 _ _ _ 100000214 _ finance.quallaby.com _ snmp _ HP Printer ETHERNET MULTI-ENVIRONMENT _ on _ inentory _ QuallabyNetwork _ 1 _ _ _ 100000180 _ marketing.quallaby.com _ snmp _ HP Printer ETHERNET MULTI-ENVIRONMENT _ on _ inentory _ QuallabyNetwork _ 1 _ _ _ 100000165 _ Delete_100000165_192.168.3.238 _ snmp _ HP Printer ETHERNET MULTI-ENVIRONMENT _ off _ inentory _ Cisco_SAA _ 1 _ _ _ 100000220 _ 192.168.66.2 _ snmp _ Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO _ on _ inentory _ QuallabyNetwor k _ 1 _ _ _ 100000215 _ dhcp65.quallaby.com _ snmp _ Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO _ on _ inentory _ Quallab ynetwork _ 1 _ _ _ 100000212 _ echidna.quallaby.com _ snmp _ Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO _ on _ inentory _ Qualla bynetwork _ 1 _ _ _ Exporting elements with their properties resmgr -export elt -colnames "name eprp.name eprp.alue" -file $DIR/elt_prp.dat # type = elt # col = name eprp.name eprp.alue # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name eprp.name eprp.alue" 172.31.0.31 _ ipaddress _ 172.31.0.31 _ ipname _ 172.31.0.31 _ physaddress _ 6.0.3.227.233.33.160 _ sysdescr _ Cisco Internetwork Operat ing System Software \nios (tm) C2600 Software (C2600-T _ sysname _ "c2610-31-ler" _ 172.31.0.41 _ ipaddress _ 172.31.0.41 _ ipname _ 172.31.0.41 _ physaddress _ 6.0.48.25.95.152.192 _ sysdescr _ Cisco Internetwork Operat ing System Software \nios (tm) C2600 Software (C2600-T _ sysname _ "c2610-41-lsr" _ 172.31.0.51 _ ipaddress _ 172.31.0.51 _ ipname _ 172.31.0.51 _ physaddress _ 6.0.4.109.221.236.0 _ sysdescr _ Cisco Internetwork Operati 74 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

ng System Software \nios (tm) 7200 Software (C7200-P- _ sysname _ "c7204-51-ler.ap-lab.quallaby.com" _ 172.31.1.2 _ ipaddress _ 172.31.1.2 _ ipname _ 172.31.1.2 _ physaddress _ 6.0.1.150.223.43.128 _ sysdescr _ Cisco Internetwork Operating System Software \nios (tm) 1600 Software (C1600-OS _ sysname _ "C1605-172.18" _ 192.168.1.3 _ ipaddress _ 192.168.1.3 _ ipaddressmin _ 192.168.1.3 _ ipname _ 192.168.1.3 _ physaddress _ 6.0.6.40.44.234.160 _ sysdescr _ Cisco Internetwork Operating System Software \nios (tm) C2600 Software (C2600-I _ sysname _ "Boulogne-C2620" _ 192.168.127.1 _ ipaddress _ 192.168.127.1 _ ipname _ 192.168.127.1 _ physaddress _ 6.0.208.0.56.43.255 _ sysdescr _ Cisco Systems WS-C65 09\nCisco Catalyst Operating System Software, Version 5.3(2 _ sysname _ "" _ 192.168.127.2 _ ipaddress _ 192.168.127.2 _ ipaddressmin _ 192.168.127.2 _ ipname _ 192.168.127.2 _ physaddress _ 6.0.48.25.88.220.0 _ s ysdescr _ Cisco Internetwork Operating System Software \nios (tm) C3500XL Software (C3500 _ sysname _ "PS-LAB" _ Exporting elements with sysname, ipaddress, and physaddress resmgr -export elt -colnames "name eprp.sysname:alue eprp.ipaddress:alue eprp.physaddress:alue" -file $DIR/elt_in.dat # type = elt # col = name eprp.sysname:alue eprp.ipaddress:alue eprp.physaddress:alue # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name eprp.sysname:alue eprp.ipaddress:alue eprp.physaddress:alue" 172.31.0.51 _ "c7204-51-ler.ap-lab.quallaby.com" _ 172.31.0.51 _ 6.0.4.109.221.236.0 _ 172.31.0.41 _ "c2610-41-lsr" _ 172.31.0.41 _ 6.0.48.25.95.152.192 _ 172.31.0.31 _ "c2610-31-ler" _ 172.31.0.31 _ 6.0.3.227.233.33.160 _ NF-site-site-flow-Gold-SpecificElectric _ NF-site-site-flow-Gold-SpecificElectric _ 0.0.0.0 _ NF-site-site-flow-Gold-SpecificElectric _ NF-site-iphost-flow-SpecificElectric _ NF-site-iphost-flow-SpecificElectric _ 0.0.0.0 _ NF-site-iphost-flow-SpecificElectric _ Delete_100000176_192.168.3.253 _ "LesUlis-C2611" _ 192.168.3.253 _ 6.0.48.148.145.80.0 _ 172.31.1.2 _ "C1605-172.18" _ 172.31.1.2 _ 6.0.1.150.223.43.128 _ 192.168.68.162 _ "Cisco1605-1" _ 192.168.68.162 _ 6.0.1.150.223.43.128 _ Delete_100001732_172.17.100.254 _ "C1605-172.16" _ 172.17.100.254 _ 6.0.2.75.91.52.236 _ Delete_100000174_192.168.2.2 _ "LesUlis-C2621.quallaby.com" _ 192.168.2.2 _ 6.0.5.50.232.149.192 _ 192.168.127.7 _ "DEV-LAB" _ 192.168.127.7 _ 6.0.4.77.216.194.64 _ 192.168.127.6 _ "SHARK3" _ 192.168.127.6 _ 6.0.1.66.35.75.64 _ 192.168.127.5 _ "SHARK2" _ 192.168.127.5 _ 6.0.1.66.35.76.128 _ Chapter 6. Managing resources 75

192.168.127.3 _ "QA-LAB" _ 192.168.127.3 _ 6.0.208.121.106.13.64 _ 192.168.127.2 _ "PS-LAB" _ 192.168.127.2 _ 6.0.48.25.88.220.0 _ Delete_100000165_192.168.3.238 _ "" _ 192.168.3.238 _ 6.8.0.9.93.82.17 _ 192.168.1.3 _ "Boulogne-C2620" _ 192.168.1.3 _ 6.0.6.40.44.234.160 _ Exporting elements with nomenclature information resmgr -export elt -colnames "name encl.name encl.oid encl.gpname endor.name" -file $DIR/elt_encl.dat # type = elt # col = name encl.name encl.oid encl.gpname endor.name # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name encl.name encl.oid encl.gpname endor.name" Delete_100000174_192.168.2.2 _ Cisco C2600-I _ 1.3.6.1.4.1.9.1.209 _ Cisco _ Cisco _ 192.168.1.3 _ Cisco C2600-D _ 1.3.6.1.4.1.9.1.208 _ Cisco _ Cisco _ 192.168.68.162 _ Cisco 1600 _ 1.3.6.1.4.1.9.1.172 _ Cisco _ Cisco _ 172.31.1.2 _ Cisco 1600 _ 1.3.6.1.4.1.9.1.172 _ Cisco _ Cisco _ Delete_100001732_172.17.100.254 _ Cisco 1600 _ 1.3.6.1.4.1.9.1.172 _ Cisco _ Cisco _ 172.31.0.31 _ Cisco 2611 _ 1.3.6.1.4.1.9.1.186 _ Cisco _ Cisco _ Delete_100000176_192.168.3.253 _ Cisco 2611 _ 1.3.6.1.4.1.9.1.186 _ Cisco _ Cisco _ 172.31.0.41 _ Cisco 2610 _ 1.3.6.1.4.1.9.1.185 _ Cisco _ Cisco _ 192.168.64.253 _ Cisco 3660 _ 1.3.6.1.4.1.9.1.205 _ Cisco _ Cisco _ Delete_100001733_172.17.100.253 _ Cisco 7206 VXR _ 1.3.6.1.4.1.9.1.222 _ Cisco _ Cisco _ 172.31.0.51 _ Cisco 7204 VXR _ 1.3.6.1.4.1.9.1.223 _ Cisco _ Cisco _ dhcp195.quallaby.com _ Cisco 7204 VXR _ 1.3.6.1.4.1.9.1.223 _ Cisco _ Cisco _ 192.168.66.2 _ Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO _ 1.3.6.1.4.1.311.1.1.3.1.2 _ Compaq _ Microsoft _ dhcp65.quallaby.com _ Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO _ 1.3.6.1.4.1.311.1.1.3.1.2 _ Compaq _ Micros oft _ Exporting elements with collection information resmgr -export elt -colnames "name collector chnl.host chnl.instdir chnl.type" -file $DIR/elt_chnl.dat # type = elt # col = name collector chnl.host chnl.instdir chnl.type # filter = # order = # sep = _ 76 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

# seprec = # # cmdline = -export elt -colnames "name collector chnl.host chnl.instdir chnl.type" 172.31.0.51 _ 1 _ pdemo3 _ /opt/dataload _ SNMP _ 172.31.0.41 _ 1 _ pdemo3 _ /opt/dataload _ SNMP _ 172.31.0.31 _ 1 _ pdemo3 _ /opt/dataload _ SNMP _ Delete_200000793_192.168.3.227 _ 1 _ pdemo3 _ /opt/dataload _ SNMP _ 192.168.127.8 _ 1 _ pdemo3 _ /opt/dataload _ SNMP _ Delete_200000791_192.168.3.82 _ 1 _ pdemo3 _ /opt/dataload _ SNMP _ Delete_200000790_192.168.3.226 _ 1 _ pdemo3 _ /opt/dataload _ SNMP _ Delete_200000789_192.168.3.123 _ 1 _ pdemo3 _ /opt/dataload _ SNMP _ Delete_200000788_192.168.3.37 _ 1 _ pdemo3 _ /opt/dataload _ SNMP _ Exporting elements with SNMP configuration information resmgr -export elt -ismandat scf -colnames "name scf.rcommunity scf.timeout scf.retries scf.ersion scf.colnb" -file $DIR/elt_scf.dat # type = elt # col = name scf.rcommunity scf.timeout scf.retries scf.ersion scf.colnb # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name scf.rcommunity scf.timeout scf.retries scf.ersion scf.colnb" default _ public _ 2 _ 3 _ _ 0 _ 192.168.1.3 _ internal _ 5 _ 3 _ _ 1 _ 192.168.127.254 _ internal _ _ _ _ 1 _ 192.168.64.253 _ internal _ _ _ _ 1 _ 192.168.127.9 _ internal _ _ _ _ 1 _ APRouterforprobe _ public _ 5 _ 2 _ _ 0 _ Exporting SNMP configuration settings for a collector resmgr -export scf -colnames "colnb type ipaddress eltidx ersion bandwidth retries timeout wcommunity port rcommunity" # type = scf # col = colnb type ipaddress eltidx ersion bandwidth retries timeout wcommunity port rcommunity # filter = # order = # sep = _ # seprec = # rule = # filterrule = # # cmdline = -export scf -colnames "colnb type ipaddress eltidx ersion bandwidth retries timeout wcommunity port rcommunity" 0 _ default_snmp _ *.*.*.* _ 5 _ _ _ 3 _ 2 _ priate _ 161 _ public _ Chapter 6. Managing resources 77

Exporting element state and comment information resmgr -export elt -colnames "name state comment" # resmgr -export elt -colnames "name state comment" # type = elt # col = name state comment # filter = # order = # sep = _ # seprec = # rule = # filterrule = # # cmdline = -export elt -colnames "name state comment" default _ on _ _ DL.1 _ on _ PROVISO_MONITORING _ 10.127.78.2-1 _ on _ _ 10.127.78.3-1 _ on _ _ 10.127.77.7 _ on _ _ 10.127.77.6 _ on _ _ Importing elements You must use the name column for a new element. By default, dbindex is taken from the resourcesequences column, nclidx is null, and the comment and profil columns are empty. You can also include the following columns: encl.name ( populate nclidx ) profil collector When updating elements, you must use the dbindex or name columns, and the columns to be modified. Creating a new or updating an existing element Input File: add_elt1 _ 3Com Hub (SuperStack II PS Hub 40) _ profil1 _ 1 _ "element1" _ 172.31.128.51 _ 6.0.4.109.221.236.0 _ add_elt2 _ 3Com Hub (SuperStack II PS Hub 40) _ profil1 _ 1 _ "element2" _ 172.31.128.41 _ 6.0.48.25.95.152.192 _ resmgr -import elt -colnames "name encl.name profil collector eprp.sysname:alue eprp.ipaddress:alue eprp.physaddress:alue" -file test1 Info : === insert : INSERT ON Element ( add_elt1 ) (does not exist) Info : === insert : nothing ON property ( sysname ) (exists) Info : === insert : nothing ON property ( ipaddress ) (exists) Info : === insert : nothing ON property ( physaddress ) (exists) Info : === insert : INSERT ON elt property ( add_elt1 sysname ) (does not exist) Info : === insert : INSERT ON elt property ( add_elt1 ipaddress ) (does not exist) 78 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Info : === insert : INSERT ON elt property ( add_elt1 physaddress ) (does not exist) Info : === insert : INSERT ON Element ( add_elt2 ) (does not exist) Info : === insert : nothing ON property ( sysname ) (exists) Info : === insert : nothing ON property ( ipaddress ) (exists) Info : === insert : nothing ON property ( physaddress ) (exists) Info : === insert : INSERT ON elt property ( add_elt2 sysname ) (does not exist) Info : === insert : INSERT ON elt property ( add_elt2 ipaddress ) (does not exist) Info : === insert : INSERT ON elt property ( add_elt2 physaddress ) (does not exist) Title : === CHANGES : {2 New of elt} Info : === Inform Collector On hebus:3002 Creating or updating existing elements and list of properties Input File: 192.168.69.243 _ Cisco Catalyst 5000 _ testin1 _ 223 _ ipaddress _ 192.168.69.243 _ ipname _ 192.168.69.243 _ physaddress _ "ff:d4:00:13:00:14" _ sysdescr _ "Cisco Systems WS-C5000" _ sysname _ "PMG_NETFIN2_MIMICagent#20" _ 192.168.69.245 _ Cisco Catalyst 5000 _ testin1 _ 223 _ ipaddress _ 192.168.69.245 _ ipname _ 192.168.69.245 _ physaddress _ "ff:d4:00:15:00:16" _ sysdescr _ "Cisco Systems WS-C5000" _ sysname _ "PMG_NETFIN2_MIMICagent#22" _ resmgr -import elt -colnames "name encl.name profil collector eprp.name eprp.alue" -file test1 Info : === insert : UPDATE ON Element ( 192.168.69.243 ) (exists) Info : === insert : nothing ON property ( ipaddress ) (exists) Info : === insert : nothing ON property ( ipname ) (exists) Info : === insert : nothing ON property ( physaddress ) (exists) Info : === insert : nothing ON property ( sysdescr ) (exists) Info : === insert : nothing ON property ( sysname ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.243 ipaddress ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.243 ipname ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.243 physaddress ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.243 sysdescr ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.243 sysname ) (exists) Info : === insert : UPDATE ON Element ( 192.168.69.245 ) (exists) Info : === insert : nothing ON property ( ipaddress ) (exists) Info : === insert : nothing ON property ( ipname ) (exists) Info : === insert : nothing ON property ( physaddress ) (exists) Info : === insert : nothing ON property ( sysdescr ) (exists) Info : === insert : nothing ON property ( sysname ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 ipaddress ) (exists) Chapter 6. Managing resources 79

Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 ipname ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 physaddress ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 sysdescr ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 sysname ) (exists) Title : === CHANGES : {2 Updated of elt} Info : === Inform Collector On hebus:3002 Creating or updating properties without creating non-existent element (nothing is inserted) You can use this command when you need to just update an existing property without creating a new one, for example in inentory. Input File: NOTEXIST_192.168.69.243 _ Cisco Catalyst 5000 _ testin1 _ 223 _ ipaddress _ 192.168.69.243 _ ipname _ 192.168.69.243 _ physaddress _ "ff:d4:00:13:00:14" _ sysdescr _ "Cisco Systems WS-C5000" _ sysname _ "PMG_NETFIN2_MIMICagent#20" _ 192.168.69.245 _ Cisco Catalyst 5000 _ testin1 _ 223 _ ipaddress _ 192.168.69.245 _ ipname _ 192.168.69.245 _ physaddress _ "ff:d4:00:15:00:16" _ sysdescr _ "Cisco Systems WS-C5000" _ sysname _ "PMG_NETFIN2_MIMICagent#22" _ resmgr -import eproperty -colnames "name encl.name profil collector eprp.name eprp.alue" -file test1 Info : === insert : nothing ON property ( ipaddress ) (exists) Info : === insert : nothing ON property ( ipname ) (exists) Info : === insert : nothing ON property ( physaddress ) (exists) Info : === insert : nothing ON property ( sysdescr ) (exists) Info : === insert : nothing ON property ( sysname ) (exists) Info : === insert : nothing ON elt property (Depend not exist) eprp D Info : === insert : nothing ON elt property (Depend not exist) eprp D Info : === insert : nothing ON elt property (Depend not exist) eprp D Info : === insert : nothing ON elt property (Depend not exist) eprp D Info : === insert : nothing ON elt property (Depend not exist) eprp D Info : === insert : nothing ON property ( ipaddress ) (exists) Info : === insert : nothing ON property ( ipname ) (exists) Info : === insert : nothing ON property ( physaddress ) (exists) Info : === insert : nothing ON property ( sysdescr ) (exists) Info : === insert : nothing ON property ( sysname ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 ipaddress ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 ipname ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 physaddress ) (exists) 80 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 sysdescr ) (exists) Info : === insert : nothing to do (update stopped) ON elt property ( 192.168.69.245 sysname ) (exists) Creating new or updating existing SNMP settings for a collector resmgr -import scf -colnames "colnb type ipaddress eltidx ersion bandwidth retries timeout wcommunity port rcommunity" -import_source Where import_source Specifies the source of the alues that are to be imported to the collector. The import source can include the following: -file filename: Imports alues from the specified file. -line "alue1 _ alue2 _ alue3": Imports the specified alues directly from the command line. Deleting elements You must use the dbindex or name columns when deleting elements. Note: As the syntax lines indicate, the -file and -line options (with a alid argument) are mandatory. Delete a config snmp (without deleting the element) resmgr -delete snmpconf -colnames "name" -line "network1" Info : === delete : DELETE ON config SNMP ( 192.168.64.* ) (exists) Deleting element properties (without deleting the element) resmgr -delete eproperty -colnames "name eprp.name" -line "add_elt2 _ ContactElt _ " Info : === delete : DELETE ON elt property ( add_elt2 ContactElt ) (exists) Working with subelements This section contains the commands you can use to manage subelements. When you work with subelement object types, you work with the following: se seprp seproperty cse Links can exist among elements and the following Tioli Netcool Performance Manager object types: fam elt Chapter 6. Managing resources 81

Exporting subelements The following example of exporting subelements includes the command and the command output. Exporting subelements with their properties resmgr -export se -colnames "dbindex inariant elt.name name label instance state origin date_date fam.name seprp.name seprp.alue" -file $DIR/se_seprp.dat #type=se # col = dbindex inariant elt.name name label instance state origin date_date fam.name seprp.name seprp.alue # filter = # order = # sep = _ # seprec = # # cmdline = -export se -colnames "dbindex inariant elt.name name label instance state origin date_date fam.name seprp.name seprp.alue" 200003278 _ Customer<C> _ 192.168.69.245 _ 192.168.69.245_If<101> _ 192.168.69.245_IF: 101 ("0") (100Mbps) _ If<101> _ on _ inentory _ 07/01/2003 02:28 _ 2233_IF _ name _ "0" _ physicalcapacity _ 100000000 _ status _ up _ If _ 101 _ siteid _ IP:192.168.69.245ifIndex:101 _ location _ "QALAB" _ type _ ethernetcsmacd _ 200003279 _ Customer<B> _ 192.168.69.245 _ 192.168.69.245_If<100> _ 192.168.69.245_IF: 100 ("0") (100Mbps) _ If<100> _ on _ inentory _ 07/01/2003 02:28 _ 2233_IF _ name _ "0" _ siteid _ IP:192.168.69.245ifIndex:100 _ If _ 100 _ physicalcapacity _ 100000000 _ status _ up _ location _ "QALAB" _ type _ ethernetcsmacd _ 200003280 _ Customer<A> _ 192.168.69.243 _ 192.168.69.243_If<100> _ 192.168.69.243_IF: 100 ("0") (100Mbps) _ If<100> _ on _ inentory _ 07/01/2003 02:28 _ 2233_IF _ name _ "0" _ siteid _ IP:192.168.69.243ifIndex:100 _ If _ 100 _ customer _ C1 _ physicalcapacity _ 10000000 0 _ status _ up _ location _ "QALAB" _ type _ ethernetcsmacd _ customer1 _ C4 _ 200003446 _ _ Delete_200000133_pl2col6 _ Delete_200000831_pl2col6_DataChannel<dber> _ Delete_200000831_pl2col6_DataChannel<dber> _ Dele te_200000831_datachannel<dber> _ on _ resmgr _ 10/13/2003 14:52 _ _ 200003448 _ _ dber _ SE_dber _ SE_dber _ <NULL> _ on _ resmgr _ 10/13/2003 14:54 _ _ 200003449 _ _ dber _ SE_dber1 _ SE_dber1 _ <NULL1> _ on _ resmgr _ 10/13/2003 16:03 _ fam1 _ Exporting composite subelements resmgr -export cse -colnames "dbindex name type inariant data comment datatype defvalue originr" -file csedesc.rmg # type = cse # col = dbindex name type inariant data comment datatype defvalue originr # filter = # order = # sep = _ 82 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

# seprec = # rule = # filterrule = # # cmdline = -export cse -colnames "dbindex name type inariant data comment datatype defvalue originr" 1919 _ qcf5620_endpoint1 _ relation _ type<se> _ _ Alcatel 5620 Pack _ string _ _ APinstall _ 1920 _ qcf5620_endpoint2 _ relation _ type<se> _ _ Alcatel 5620 Pack _ string _ _ APinstall _ 1921 _ qcf5620_local _ relation _ type<se> _ _ Alcatel 5620 Pack _ string _ _ APinstall _ 1922 _ qcf5620_remote _ relation _ type<se> _ _ Alcatel 5620 Pack _ string _ _ APinstall _ Exporting composite subelements with composite link resmgr -export cse -colnames "name cse.name cse.coname" # type = cse # col = name cse.name cse.coname # filter = # order = # sep = _ # seprec = # rule = # filterrule = # # cmdline = -export cse -colnames "name cse.name cse.coname" Path From: label24078_145_29278 To: label26672_145_29277 _ qcf5620_remote _ label26672_145_29277 _ Path From: label14263_145_29279 To: label34389_145_29280 _ qcf5620_local _ label14263_145_29279 _ Path From: label34389_145_29280 To: label14263_145_29279 _ qcf5620_remote _ label14263_145_29279 _ Path From: label10209_145_29290 To: label20854_145_29289 _ qcf5620_remote _ label20854_145_29289 _ Path From: label31552_145_19020 To: label38212_145_19019 _ qcf5620_remote _ label38212_145_19019 _ Path From: label26699_145_19021 To: label17079_145_19022 _ qcf5620_local _ label26699_145_19021 _ Path From: label32752_145_19023 To: label11719_145_19024 _ qcf5620_local _ label32752_145_19023 _ Path From: label11719_145_19024 To: label32752_145_19023 _ qcf5620_remote _ label32752_145_19023 _ Path From: label2413_145_19025 To: label13948_145_19026 _ qcf5620_local _ label2413_145_19025 _ Path From: label13948_145_19026 To: label2413_145_19025 _ qcf5620_remote _ label2413_145_19025 _ Exporting subelement state and ulabel information resmgr -export se -colnames "name state ulabel" $ resmgr -export se -colnames "name state ulabel" #type=se # col = name state ulabel Chapter 6. Managing resources 83

# filter = # order = # sep = _ # seprec = # rule = # filterrule = # # cmdline = -export se -colnames "name state ulabel" DL.1_<NULL> _ on _ _ 0.127.78.2-1_CSC<NULL> _ on _ _ 10.127.78.3-1_If<69> _ on _ _ 10.127.78.3-1_If<34> _ on _ _ 10.127.78.3-1_If<41> _ on _ _ 10.127.78.2-1_SLS<NULL> _ on _ _ 10.127.78.3-1_If<10> _ on _ _ 10.127.78.3-1_If<45> _ on _ _ 10.127.78.3-1_If<2> _ on _ _ 10.127.78.3-1_If<8> _ on _ _ 10.127.78.3-1_If<9> _ on _ _ 10.127.78.3-1_If<86> _ on _ _ 10.127.78.3-1_If<20> _ on _ _ 10.127.78.3-1_If<85> _ on _ _ 10.127.78.2-1_<NULL> _ on _ _ 10.127.78.3-1_If<87> _ on _ _ 10.127.78.3-1_If<14> _ on _ _ 10.127.78.3-1_If<19> _ on _ _ Importing subelements You must use the following columns when importing new subelements: name hostidx or elt.name instance By default, dbindex is taken from the resourcesequences column, nclidx is null, and inariant and label are empty. You can also include the following columns: fam.name ( populate nclidx ) label inariant if needed For an update: When updating existing subelements, you must use the dbindex or name columns; or (elt.name + instance ) and the columns to be modified. Creating new or updating existing subelement Input File: 192.168.69.243_If<100> _ 2233_IF _ 192.168.69.243_IF: 100 ("0") (100Mbps) _ 192.168.69.243 _ If<100> _ conctact A1 _ " 84 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

resmgr -import se -colnames "name fam.name label elt.name instance seprp.contact:alue" -file test1 Info : === insert : nothing ON Element ( 192.168.69.243 ) (exists) Info : === insert : nothing ON nomenclature1 ( 2233_IF ) (exists) Info : === insert : UPDATE ON Sub-Element ( 192.168.69.243_If<100> ) (exists) Info : === insert : nothing ON property ( Contact ) (exists) Info : === insert : INSERT ON subelt property ( Contact conctact A1 ) (does not exist) Title : === CHANGES : {1 Updated of se} Info : === Inform Collector On hebus:3002 Creating new or updating existing subelement and list of properties Input File: 192.168.69.243_If<100> _ 2233_IF _ 192.168.69.243_IF: 100 ("0") (100Mbps) _ 192.168.69.243 _ If<100> _ name _ "0" _ type _ ethernetcsmacd _ location _ "QALAB" _ status _ up _ physicalcapacity _ 100000000 _ If _ 100 _ customer1 _ C4 _ Contact _ conctact A1 _ siteid _ IP:192.168.69.243ifIndex:100 _ customer _ C1 _ 192.168.69.243_If<101> _ 2233_IF _ 192.168.69.243_IF: 101 ("0") (100Mbps) _ 192.168.69.243 _ If<101> _ name _ "0" _ type _ ethernetcsmacd _ location _ "QALAB" _ physicalcapacity _ 100000000 _ customer1 _ C3 _ siteid _ IP:192.168.69.243ifIndex:101 _ If _ 101 _ customer _ C2 _ status _ up _ customer _ C1 _ resmgr -import se -colnames "name fam.name label elt.name instance seprp.name seprp.alue" -file test1 Info : === insert : nothing ON Element ( 192.168.69.243 ) (exists) Info : === insert : nothing ON nomenclature1 ( 2233_IF ) (exists) Info : === insert : UPDATE ON Sub-Element ( 192.168.69.243_If<100> ) (exists) Info : === insert : nothing ON property ( name ) (exists) Info : === insert : nothing ON property ( type ) (exists) Info : === insert : nothing ON property ( location ) (exists) Info : === insert : nothing ON property ( status ) (exists) Info : === insert : nothing ON property ( physicalcapacity ) (exists) Info : === insert : nothing ON property ( If ) (exists) Info : === insert : nothing ON property ( customer1 ) (exists) Info : === insert : nothing ON property ( Contact ) (exists) Info : === insert : nothing ON property ( siteid ) (exists) Info : === insert : nothing ON property ( customer ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( name "0" ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( type ethernetcsmacd ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( location "QALAB" ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( status up ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( physicalcapacity 100000000 ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( If 100 ) (exists) Chapter 6. Managing resources 85

Info : === insert : nothing to do (update stopped) ON subelt property ( customer1 C4 ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( Contact conctact A1 ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( siteid IP:192.168.69.243ifIndex:100 ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( customer C1 ) (exists) Info : === insert : nothing ON Element ( 192.168.69.243 ) (exists) Info : === insert : nothing ON nomenclature1 ( 2233_IF ) (exists) Info : === insert : UPDATE ON Sub-Element ( 192.168.69.243_If<101> ) (exists) Info : === insert : nothing ON property ( name ) (exists) Info : === insert : nothing ON property ( type ) (exists) Info : === insert : nothing ON property ( location ) (exists) Info : === insert : nothing ON property ( physicalcapacity ) (exists) Info : === insert : nothing ON property ( customer1 ) (exists) Info : === insert : nothing ON property ( siteid ) (exists) Info : === insert : nothing ON property ( If ) (exists) Info : === insert : nothing ON property ( customer ) (exists) Info : === insert : nothing ON property ( status ) (exists) Info : === insert : nothing ON property ( customer ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( name "0" ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( type ethernetcsmacd ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( location "QALAB" ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( physicalcapacity 100000000 ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( customer1 C3 ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( siteid IP:192.168.69.243ifIndex:101 ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( If 101 ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( customer C2 ) (exists) Info : === insert : nothing to do (update stopped) ON subelt property ( status up ) (exists) Info : === insert : UPDATE ON subelt property ( customer C1 ) (exists) Title : === CHANGES : {2 Updated of se} Info : === Inform Collector On hebus:3002 Creating or updating a list of properties without creating a non-existent subelement (nothing is inserted) resmgr -import seproperty -colnames "name fam.name label elt.name instance seprp.name seprp.alue" -file test1 Note: You must use date to insert a property in the past. 86 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

resmgr -import seproperty -colnames "name seprp.contact:alue seprp.contact:date(1057015945)" -histodate 1 -line "192.168.69.243_If<100> _ conctact A1 _ " Info : === insert : nothing ON property ( Contact ) (exists) Info : === insert : UPDATE ON subelt property ( Contact conctact A1 ) (exists) resmgr -import seproperty -colnames "name seprp.contact:alue seprp.contact:date(1057015945)" -histodate 1 Note: You need to use this command carefully. Check with IBM if you need assistance. If there is no change in the no history table (for property,) no updates are made. Use "IFirst,forced" mode to force the insert into the history table, een if there is no change in the seprp table. Importing a composite subelement resmgr -import cse -colnames "name inariant" -line "relation1 _ type<se> _ " Info : === insert : INSERT ON property ( relation1 ) (does not exist) Importing composite subelements resmgr -import secse -colnames "name cse.name cse.coname" -line "Path From: label27077_145_15510 To: label3989_145_15509 _ qcf5620_remote _ label3989_145_15509 _ " Info : === insert : nothing ON property ( qcf5620_remote ) (exists) Info : === insert : INSERT ON composite ( Path From: label27077_145_15510 To: label3989_145_15509 qcf5620_remote label3989_145_15509 ) (does not exist) Deleting subelements You must use the dbindex or name columns; or elt.name plus instance. Note: As the syntax lines indicate, the -file and -line options (with a alid argument) are mandatory. Deleting subelements resmgr -delete se -colnames "dbindex" -line 200003446 Info : === delete : DELETE ON Sub-Element ( Delete_200000831_pl2col6_DataChannel<dber> ) (exists) Title : === CHANGES : {1 Deleted of se} Info : === Inform Collector On hebus:3002 Deleting subelement properties (without deleting the subelement) resmgr -delete seproperty -colnames "name seprp.name" -line "bulk100-boston_1000,19_interface<10> _ type _ " Info : === delete : DELETE ON subelt property ( type ip ) (exists) or if you hae the index resmgr -delete seprp -colnames "seidx nop prpidx" -line "200001183 _ bulk100-boston_1000,17_interface<8> _ 1732 _ physicalcapacity _ 0 _ " Info : === delete : DELETE ON subelt property (exists) Chapter 6. Managing resources 87

Deleting composite subelements resmgr -delete cse -colnames "name" -line relation1 Info : === delete : DELETE ON property ( relation1 ) (exists) Deleting composite subelements with composite link resmgr -delete secse -colnames "name cse.name cse.coname" -line "Path From: label27077_145_15510 To: label3989_145_15509 _ qcf5620_remote _ label3989_145_15509 _ " Info : === delete : DELETE ON composite ( Path From: label27077_145_15510 To: label3989_145_15509 qcf5620_remote label3989_145_15509 ) (exists) Working with groups or rules This section contains the commands you can use to manage groups or rules. When you use resgmr to work with the elements, you work with the following object types: egp segp Subelement group links Links can exist among subelement groups and the following Tioli Netcool Performance Manager object types: se app rusr tz cal segparent segchild linkgroupse linkgroupse_app linkgroupse_ru linkgroupse_tzc Exporting groups and rules The only difference between the export of the groups and the rule is the filter used. Exporting subelement groups with a group label resmgr -export segp -colnames "name label" -filter "label(customer*)" -file groups.txt # type = segp # col = dbindex name label # filter = label(pmg*) # order = # sep = _ # seprec = # rule = # filterrule = # 88 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

# cmdline = -export segp -colnames "dbindex name label" -filter "label(pmg*)" 200017652 _ GPR0001 _ PMG Grouping _ -export segp -colnames "dbindex name label" -filter "label(pmg*)" 200017652 _ GPR0001 _ PMG Grouping _ Exporting subelement groups created by rules resmgr -export segp -colnames "npath name type cond state origin date" -order "dbindex" -filter "type(!= rule ) origin(= inentory )" -file $DIR/segp_generated.dat # type = segp # col = npath name type cond state origin date # filter = type(!= rule ) origin(= inentory ) # order = dbindex # sep = _ # seprec = # # cmdline = -export segp -colnames "npath name type cond state origin date" -filter "type(!= rule ) origin(= inentory )" ~NOC Reporting~Cisco SAA~Per Operation (raw)~jitter~172.17.105.254 _ 172.17.105.254 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Hourly Aggregate~Common~172.17.100.253 _ 172.17.100.253 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Per Operation (raw)~http~172.17.100.253 _ 172.17.100.253 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Hourly Aggregate~Jitter~172.17.100.253 _ 172.17.100.253 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Hourly Aggregate~Common~172.17.100.254 _ 172.17.100.254 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Hourly Aggregate~Jitter~172.17.100.254 _ 172.17.100.254 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Per Operation (raw)~http~192.168.64.253 _ 192.168.64.253 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Hourly Aggregate~Common~192.168.64.253 _ 192.168.64.253 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Hourly Aggregate~Jitter~192.168.64.253 _ 192.168.64.253 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Router~Interfaces~Location: "AP Lab, Lowell MA US"~172.17.100.254 _ 172.17.100.254 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Per Operation (raw)~common~192.168.68.162 _ 192.168.68.162 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Hourly Aggregate~Common~172.17.105.254 _ 172.17.105.254 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Per Operation (raw)~jitter~192.168.68.162 _ 192.168.68.162 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Hourly Aggregate~Jitter~172.17.105.254 _ 172.17.105.254 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Router~Interfaces~Location: ""~192.168.68.162 _ 192.168.68.162 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Cisco SAA~Per Operation (raw)~common~172.17.100.253 _ 172.17.100.253 _ generated _ _ on _ inentory _ 1025288162 _ ~NOC Reporting~Customization Group~Coca-Cola _ Coca-Cola _ static _ %(customer) = Coca-Cola _ on _ inentory _ 1018389887 _ Chapter 6. Managing resources 89

~NOC Reporting~Cisco SAA~Per Operation (raw)~common~172.17.105.254 _ 172.17.105.254 _ generated _ _ on _ inentory _ 1025289790 _ Exporting subelement groups that are rules resmgr -export segp -colnames "npath name type cond state origin date" -order "dbindex" -filterrule "(%(type) = rule OR %(cond) is not null)" -file $DIR/segp_rule.dat # type = segp # col = npath name type cond state origin date # filter = # order = dbindex # sep = _ # seprec = # # cmdline = -export segp -colnames "npath name type cond state origin date" ~NOC Reporting _ NOC Reporting _ static _ %(Element.STATE)= on AND %(STATE)= on _ on _ APinstall _ 983650594 _ ~Sub-Element Collect _ Sub-Element Collect _ static _ %(Element.STATE)= on AND %(STATE)= on _ on _ APinstall _ 997993108 _ ~NOC Reporting~IPSec _ IPSec _ static _ %(FAMILY)= Cisco_IPSec _ on _ APinstall _ 997993109 _ ~NOC Reporting~IPSec~Phase-1 _ Phase-1 _ static _ %(FAMILY)= Cisco_IPSec _ on _ APinstall _ 997993109 _ ~NOC Reporting~IPSec~Phase-2 _ Phase-2 _ static _ %(FAMILY)= Cisco_IPSec _ on _ APinstall _ 997993109 _ ~NOC Reporting~IPSec~Phase-1~%(customer) _ %(customer) _ rule _ _ on _ APinstall _ 993737950 _ ~NOC Reporting~IPSec~Phase-2~%(customer) _ %(customer) _ rule _ _ on _ APinstall _ 999637172 _ ~Sub-Element Collect~IPSec~Cisco _ Cisco _ static _ %(FAMILY)= Cisco_IPSec _ on _ APinstall _ 999642720 _ ~NOC Reporting~IPSec~Phase-1~%(customer)~%(priateNetworkID) _ %(priatenetworkid) _ rule _ _ on _ APinstall _ 983650594 _ ~NOC Reporting~IPSec~Phase-2~%(customer)~%(priateNetworkID) _ %(priatenetworkid) _ rule _ _ on _ APinstall _ 983650594 _ ~Sub-Element Collect~Frame Relay~DLC~Cascade (Lucent) _ Cascade (Lucent) _ static _ %(FAMILY) LIKE Cascade_FR_DLC% _ on _ APinstall _ 999787597 _ ~Sub-Element Collect~Frame Relay~DLC~Cisco 11.2F+ _ Cisco 11.2F+ _ static _ %(FAMILY) LIKE Cisco_FR_DLC% _ on _ APinstall _ 1021329701 _ ~NOC Reporting~Frame Relay~DLC _ DLC _ static _ %(FAMILY) LIKE %_FR_DLC% _ on _ APinstall _ 1020810436 _ ~Sub-Element Collect~Router _ Router _ static _ %(Element.NODETYPE) = Router _ on _ APinstall _ 999044304 _ ~Sub-Element Collect~Router~Deices _ Deices _ static _ %(FAMILY) LIKE %Deice% _ on _ APinstall _ 999124865 _ ~Sub-Element Collect~Router~Deices~Cisco 11.x _ Cisco 11.x _ static _ %(FAMILY) LIKE Cisco%Router%Deice% _ on _ APinstall _ 1024082286 _ ~NOC Reporting~Router _ Router _ static _ %(Element.NODETYPE) = Router _ on _ APinstall _ 999044238 _ 90 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

~NOC Reporting~Router~Interfaces _ Interfaces _ static _ %(FAMILY) LIKE %_IF AND %(type) NOT IN ( atm, atmsubinterface, ds0, ds1 ) _ on _ APinstall _ 999642515 _ ~NOC Reporting~Router~Interfaces~Location: %(location) _ Location: %(location) _ rule _ _ on _ APinstall _ 999642495 _ ~NOC Reporting~Router~Deices _ Deices _ static _ %(FAMILY) LIKE %Deice% AND %(Element.VENDOR)!= Unisphere _ on _ APinstall _ 999126431 _ ~NOC Reporting~Router~Deices~Location: %(location) _ Location: %(location) _ rule _ _ on _ APinstall _ 999641730 _ ~Sub-Element Collect~Router~Interfaces _ Interfaces _ static _ %(FAMILY) LIKE %_IF _ on _ APinstall _ 997993110 _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ Cisco 11.x _ static _ %(Element.VENDOR)= Cisco _ on _ APinstall _ 1013400292 _ Exporting subelement groups that are leaf, actie rules resmgr -export segp -colnames "dbindex name type cond state origin date" -order "dbindex" -filterrule "(%(type) = rule OR %(cond) is not null)" -filter "state(on) segchild.name(is null)" -file $DIR/segp_leafrule.dat # type = segp # col = dbindex name type cond state origin date # filter = state(on) segchild.name(is null) # order = dbindex # sep = _ # seprec = # # cmdline = -export segp -colnames "dbindex name type cond state origin date" -filter "state(on) segchild.name(is null)" 4191 _ Cisco _ static _ %(FAMILY)= Cisco_IPSec _ on _ APinstall _ 999642720 _ 4192 _ %(priatenetworkid) _ rule _ _ on _ APinstall _ 983650594 _ 4193 _ %(priatenetworkid) _ rule _ _ on _ APinstall _ 983650594 _ 4302 _ Cascade (Lucent) _ static _ %(FAMILY) LIKE Cascade_FR_DLC% _ on _ APinstall _ 999787597 _ 4303 _ Cisco 11.2F+ _ static _ %(FAMILY) LIKE Cisco_FR_DLC% _ on _ APinstall _ 1021329701 _ 4308 _ Cisco 11.x _ static _ %(FAMILY) LIKE Cisco%Router%Deice% _ on _ APinstall _ 1024082286 _ 4313 _ Location: %(location) _ rule _ _ on _ APinstall _ 999641730 _ 4316 _ %(Element.NAME) _ rule _ _ on _ APinstall _ 983650594 _ 4319 _ Type: %(Element.NODETYPE) _ rule _ _ on _ APinstall _ 999641775 _ 4321 _ %(Element.NAME) _ rule _ _ on _ APinstall _ 983650594 _ 4324 _ %(type) _ rule _ _ on _ APinstall _ 983650594 _ 4326 _ %(type) _ rule _ _ on _ APinstall _ 983650594 _ 4328 _ Type: %(Element.NODETYPE) _ rule _ _ on _ APinstall _ 999641803 _ 4330 _ %(type) _ rule _ _ on _ APinstall _ 983650594 _ 4332 _ %(type) _ rule _ _ on _ APinstall _ 983650594 _ 4819 _ %(Element.NAME) _ rule _ _ on _ APinstall _ 989351374 _ 4820 _ %(Element.NAME) _ rule _ _ on _ APinstall _ 989351926 _ Chapter 6. Managing resources 91

4821 _ %(Element.NAME) _ rule _ _ on _ APinstall _ 989351926 _ 4915 _ %(Element.NAME) _ rule _ _ on _ APinstall _ 999124584 _ 4939 _ Common _ static _ %(FAMILY) = RTTMon_Common_Probe _ on _ APinstall _ 1004367506 _ 4940 _ HTTP _ static _ %(FAMILY) = RTTMon_HTTP_Probe _ on _ APinstall _ 1004367506 _ 4941 _ Jitter _ static _ %(FAMILY) = RTTMon_Jitter_Probe _ on _ APinstall _ 1004367506 _ 5137 _ %(Element.NAME) _ rule _ _ on _ APinstall _ 994198030 _ 5141 _ %(Element.NAME) _ rule _ _ on _ APinstall _ 994198030 _ 5142 _ If: %(parent) _ rule _ _ on _ APinstall _ 999637193 _ 5144 _ Juniper _ static _ %(Element.VENDOR)= Juniper Networks _ on _ APinstall _ 999641985 _ 5146 _ Juniper _ static _ %(FAMILY)= Juniper_Chassis _ on _ APinstall _ 999617814 _ 5148 _ Juniper _ static _ %(FAMILY)= Juniper_DCU _ on _ APinstall _ 1004723965 _ 5150 _ Juniper _ static _ %(FAMILY)= Juniper_Firewall _ on _ APinstall _ 998661334 _ 5153 _ Juniper _ static _ %(FAMILY)= Juniper_MPLS_LSP _ on _ APinstall _ 999617814 _ 5246 _ Unisphere ERX Deices _ static _ %(FAMILY) = 1213_Deice AND %(Element.VENDOR) = Unisphere _ on _ APinstall _ 1022018055 _ Note: You can not currently use npath with segchild or segparent object types. Exporting subelement groups resmgr -export segp -colnames "npath se.name" -file $DIR/segp_se.dat # type = segp # col = npath se.name # filter = # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "npath se.name" ~Partner Section~Juniper~Virtual Router~IP Interfaces~default~10.8.7.18 _ 192.168.127.2_If<23> _ ~NOC Reporting~Network Management~By location~"catalyst_ps_lab" _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~By Customer and Location~Bristol-Myers Squibb by location~"catalyst_ps_lab" _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~IP VPN~WCOM Test group~headquarters~loreal~bordeaux~test alue2 _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~IP VPN~By Customer and CoS~Loreal CoS~Gold _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~IP VPN~By Customer and VPN~Loreal VPN~Headquarters _ 192.168.127.2_If<23> _ ~NOC Reporting~IP VPN~By Class of Serice~Gold _ 192.168.127.2_If<23> _ ~NOC Reporting~IP VPN~By City~Bordeaux _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~IP VPN~By CoS~Gold _ 192.168.127.2_If<23> _ 92 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

~Customer Facing Reporting~By CoS~Standard _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~By Customer and Cos~Bristol-Myers Squibb by CoS~Standard _ 192.168.127.2_If<23> _ ~NOC Reporting~Network Management~By CoS~Standard _ 192.168.127.2_If<23> _ ~NOC Reporting~All Technologies~High Speed Interfaces (>=100Mbps)~ethernetCsmacd _ 192.168.127.2_If<23> _ ~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps)~ethernetCsmacd _ 192.168.127.2_If<23> _ ~Sub-Element Collect~RFC-1213~Interfaces~Frequent _ 192.168.127.2_If<23> _ Exporting report user groups resmgr -export segp -colnames "npath rusr.name" -file $DIR/segp_rusr.dat # type = segp # col = npath rusr.name # filter = # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "npath rusr.name" ~NOC Reporting _ SSSW\\jtho _ ~NOC Reporting _ SSSW\\quallaby _ ~NOC Reporting _ SSSW\\adminfcar _ ~NOC Reporting _ SSSW\\nate _ ~PROVISO System Monitoring _ SSSW\\adminfcar _ ~PROVISO System Monitoring _ SSSW\\nate _ ~Customer Facing Reporting _ SSSW\\jtho _ ~Customer Facing Reporting _ SSSW\\business _ ~Customer Facing Reporting _ SSSW\\cisco _ ~Customer Facing Reporting _ SSSW\\adminfcar _ ~Customer Facing Reporting _ SSSW\\nate _ ~Partner Section _ SSSW\\jtho _ ~Partner Section _ SSSW\\business _ ~Partner Section _ SSSW\\adminfcar _ ~Partner Section _ SSSW\\nate _ Exporting application groups with app resmgr -export segp -colnames "npath app.name" -file $DIR/segp_app.dat # type = segp # col = npath app.name # filter = # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "npath app.name" Chapter 6. Managing resources 93

~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~mplsTunnel _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~iso88023Csmacd _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~other _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~softwareLoopback _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~slip _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~rs232 _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~propVirtual _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~propPointToPointSerial _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~frameRelay _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~ethernetCsmacd _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~ds1 _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~0 _ Interface Volume Resource _ ~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~%(type) _ Interface Volume Resource _ ~NOC Reporting~All Technologies~High Speed Interfaces (>=100Mbps)~softwareLoopback _ Interface Volume Resource _ ~NOC Reporting~All Technologies~High Speed Interfaces (>=100Mbps)~propVirtual _ Interface Volume Resource _ Exporting subelement groups with timezones You use the option filter tzdate(%now) in the command because the Calendar table is actually a history table. If you just need to see the line alid for "now," you use this filter to aoid iewing the entire history. resmgr -export segp -colnames "npath tz.name cal.name" -filter "tz.date(%now%)" -file $DIR/segp_tz.dat # type = segp # col = npath tz.name cal.name # filter = tz.date(%now%) # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "npath tz.name cal.name" -filter "tz.date(%now%)" ~NOC Reporting _ EST_2003 _ CME Permanent _ ~PROVISO System Monitoring _ EST_2003 _ CME Permanent _ ~Customer Facing Reporting _ EST_2003 _ CME Permanent _ ~Partner Section _ EST_2003 _ CME Permanent _ ~Customer Facing Reporting~IP VPN~By Customer and VPN~Lindt VPN _ EST_2003 _ 4 AM to 8 PM restricted SLA _ 94 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Importing groups and rules You must use the following columns when importing new groups: npath type rule if type=generated And the following columns when importing new rules: npath cond type = rule When updating existing groups and rules, you must use the dbindex or npath columns, and the columns to be modified. The following table lists the commands Import Insert or update group Insert group if it does not exist and link subelement to it Link subelement to group only if the group exists Insert group if it does not already exist and link report to it Link report to group only if the group exists Insert group if it does not exist and link report user to it Link report user to group only if group exists Insert group if it does not exist and link timezone to it Link timezone to group only if group exists Command resmgr -import segp -colnames "npath name type state origin" -line "~NOC Reporting~ CustomerA _ CustomerA _ static _ on _ resgmr" resmgr -import segp -colnames "npath se.name" resmgr -import linkgroupse -colnames "npath se.name" resmgr -import segp -colnames "npath app.name" resmgr -import linkgroupse_app -colnames "npath app.name" resmgr -import segp -colnames "npath rusr.name" resmgr -import linkgroupse_ru -colnames "npath rusr.name" resmgr -import segp -colnames "npath cal.name tz.name" resmgr -import linkgroupse_tzc -colnames "npath cal.name tz.name" Inserting or updating groups resmgr -import segp -colnames "npath name type state origin" "~NOC Reporting~CustomerA _ CustomerA _ static _ on _ resgmr" Info : === insert : INSERT ON Sub-Elt Group ( ~NOC Reporting~CustomerA ) (does not exist) Info : === Update Histo : 0 Title : === CHANGES : {3 New of segp} Info : === Inform Collector On hebus:3002 -line Inserting group if non-existent and linking subelements to it resmgr -import segp -colnames "npath se.name " -line "~NOC Reporting~CustomerA _ 192.168.69.243_If<100> _ " Chapter 6. Managing resources 95

Info : === insert : nothing ON Sub-Elt Group ( ~NOC Reporting~CustomerA ) (exists) Info : === insert : INSERT ON Link SE/G ( 192.168.69.243_If<100> CustomerA ) (does not exist) Info : === Update Histo : 0 Title : === CHANGES : {1 New of se} Info : === Inform Collector On hebus:3002 Linking subelements to group only if group exists resmgr -import linkgroupse -colnames "npath se.name " -line "~NOC Reporting~CustomerC _ 192.168.69.243_If<100> _ " Error : === insert : INSERT ON Link SE/G ( 192.168.69.243_If<100> CustomerC ) (does not exist) (error I 200003280 301 {ORA-01400: cannot insert NULL into ("PV_ADMIN"."SE_GRP_MEMBER"."IDX_GROUP") }) Info : === Update Histo : 0 Inserting group if non-existent and linking reports to it resmgr -import segp -colnames "npath app.name " -line "~NOC Reporting~CustomerA _ Top N AS Details _ " Info : === insert : nothing ON Sub-Elt Group ( ~NOC Reporting~CustomerA ) (exists) Info : === insert : nothing ON Application ( Top N AS Details ) (exists) Info : === insert : INSERT ON Link App/SEGroup ( Top N AS Details CustomerA ) (does not exist) Info : === Update Histo : 0 Linking report to group only if group exists resmgr -import linkgroupse_app -colnames "npath app.name" -line "~NOC Reporting~CustomerB _ Top N AS Details _ " Info : === insert : INSERT ON Link App/SEGroup ( Top N AS Details CustomerB ) (does not exist) Info : === Update Histo : 0 Inserting group if non-existent and linking report user to it resmgr -import segp -colnames "npath rusr.name" -line "~NOC Reporting~CustomerA _ SSSW\\customer2 _ " Info : === insert : nothing ON Sub-Elt Group ( ~NOC Reporting~CustomerA ) (exists) Info : === insert : INSERT ON Report User ( SSSW\customer2 ) (does not exist) Info : === insert : INSERT ON Link RU/SEG ( SSSW\customer2 CustomerA ) (does not exist) Info : === Update Histo : 0 Linking report user to group only if group exists resmgr -import linkgroupse_ru -colnames "npath rusr.name" -line "~NOC Reporting~CustomerB _ SSSW\\customer2 _ " Info : === insert : INSERT ON Link RU/SEG ( SSSW\customer2 CustomerB ) (does not exist) Info : === Update Histo : 0 Inserting group if non-existent and linking timezone to it resmgr -import segp -colnames "npath cal.name tz.name" -line "~NOC Reporting~TestInsertTZC _ CME Permanent _ GMT _ " 96 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Info : === insert : INSERT ON Sub-Elt Group ( ~NOC Reporting~TestInsertTZC ) (does not exist) Info : === insert : INSERT ON Link SEGP/TZ ( GMT CME Permanent ) (does not exist) Info : === Update Histo : 0 Title : === CHANGES : {3 New of segp} Info : === Inform Collector On hebus:3002 Linking timezone to group only if group exists resmgr -import linkgroupse_tzc -colnames "npath cal.name tz.name" -line "~NOC Reporting~TestInsertTZCBis _ CME Permanent _ GMT _ " Error : === insert : nothing ON Link SEGP/TZ (no enough info) (error select ORA-00936: missing expression) Info : === Update Histo : 0 Deleting As the syntax lines indicate, the -file and -line options (with a alid argument) are mandatory. The following table lists deletion commands: Delete group unlink subelement unlink report unlink report user unlink timezone Command resmgr -delete segp -colnames "npath" -line "~NOC Reporting~CustomerA" resmgr -delete linkgroupse -colnames "npath se.name" resmgr -delete linkgroupse_app -colnames "npath app.name" resmgr -delete linkgroupse_ru -colnames "npath rusr.name" resmgr -delete linkgroupse_tzc -colnames "npath cal.name tz.name" Deleting a group resmgr -delete segp -colnames "npath" -line "~NOC Reporting~CustomerA" Info : === DELETE GROUP : ~NOC Reporting~CustomerA (index = 200003479) Info : === delete : DELETE ON Sub-Elt Group ( ~NOC Reporting~CustomerA ) (exists) Info : === Update Histo : 0 Title : === CHANGES : {2 Deleted of segp} Info : === Inform Collector On hebus:3002 Chapter 6. Managing resources 97

Unlinking subelements resmgr -delete linkgroupse -colnames "npath se.name" -line "~NOC Reporting~CustomerB _ 192.168.69.243_If<100> _ " Info : === delete : DELETE ON Link SE/G ( 192.168.69.243_If<100> CustomerB ) (exists) Info : === Update Histo : 0 Title : === CHANGES : {1 Deleted of se} Info : === Inform Collector On hebus:3002 Unlinking reports resmgr -delete linkgroupse_app -colnames "npath app.name" -line "~NOC Reporting~CustomerB _ Top N AS Details _ " Info : === delete : DELETE ON Link App/SEGroup ( Top N AS Details CustomerB ) (exists) Info : === Update Histo : 0 Unlinking report users resmgr -delete linkgroupse_ru -colnames "npath rusr.name" -line "~NOC Reporting~CustomerB _ SSSW\customer2 _ " Info : === delete : DELETE ON Link RU/SEG ( SSSW\customer2 CustomerB ) (exists) Info : === Update Histo : 0 Unlinking timezones resmgr -delete linkgroupse_tzc -colnames "npath cal.name tz.name" -line "~NOC Reporting~TestInsertTZC _ CME Permanent _ GMT _ " Info : === delete : DELETE ON Link SEGP/TZ ( GMT CME Permanent ) (exists) Info : === Update Histo : 0 Working with composite subelement rules Exporting composite subelement (CSE) rules is a two-stage process that must result in two separate files being generated to be complete. You must always enter the rule definitions command before the rule relations command. Only the options in this section are supported. Using the commands in this section ensures that multiple root groups are not created when importing composite subelement rules. Ensure that you neer create additional root groups using the resmgr command. Exporting composite subelement rules rule definitions resmgr -export rulegp -colnames "dbindex name type targetname label cond ruleprp.name ruleprp.command ruleprp.alue" -file rulesd.export.dat rule relations resmgr -export rulegp -colnames "lgparent lgchild reltype relname relcond" -file rulesl.export.dat Importing or updating composite subelement rules rule definitions resmgr -import rulegp -colnames "dbindex name type targetname label cond ruleprp.name ruleprp.command ruleprp.alue" -file rulesd.import.dat rule relations 98 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

resmgr -import rulegp -colnames "lgparent lgchild reltype relname relcond" -file rulesl.import.dat Deleting composite subelement rules find the dbindex of the rule you wish to delete (by inspecting an export file), and use this command to delete the rule. resmgr -delete rulegp -colnames "dbindex" -line "1234567890 _ " Working with nomenclature This section contains the commands you can use to manage nomenclature. When you use resgmr to work with the nomenclature, you work with the following object types: ngp ncl Links can exist among elements and the following Tioli Netcool Performance Manager object types: endor linkgroupn Exporting nomenclature Exporting all of the nomenclature: resmgr -export ncl -colnames "name oid type" -file $DIR/ncl.dat # type = ncl # col = name oid type # filter = # order = # sep = _ # seprec = # # cmdline = -export ncl -colnames "name oid type" Proteon _ 1.3.6.1.4.1.1 _ Vendor _ IBM _ 1.3.6.1.4.1.2 _ Vendor _ CMU _ 1.3.6.1.4.1.3 _ Vendor _ Unix _ 1.3.6.1.4.1.4 _ Vendor _ Cisco _ 1.3.6.1.4.1.9 _ Vendor _ NSC _ 1.3.6.1.4.1.10 _ Vendor _ Hewlett Packard _ 1.3.6.1.4.1.11 _ Vendor _ Epilogue _ 1.3.6.1.4.1.12 _ Vendor _ U of Tennessee _ 1.3.6.1.4.1.13 _ Vendor _ BBN _ 1.3.6.1.4.1.14 _ Vendor _ Xylogics, Inc. _ 1.3.6.1.4.1.15 _ Vendor _ Timeplex _ 1.3.6.1.4.1.16 _ Vendor _ BayStack 450-24T _ 1.3.6.1.4.1.45.3.35.1 _ SysObjectID _ Hewlett-Packard ENTRIA Model C3262A Serer _ 1.3.6.1.4.1.11.2.3.9.3.2.3.2.67.51.50.54.50.65 _ SysObjectID _ Hewlett-Packard ENTRIA Model C3264A Serer _ 1.3.6.1.4.1.11.2.3.9.3.2.3.2.67.51.50.54.52.65 _ SysObjectID _ Bay Networks Ethernet Chassis NMM 2813 _ 1.3.6.1.4.1.45.3.12.1 _ SysObjectID _ Chapter 6. Managing resources 99

Cabletron SEHI _ 1.3.6.1.4.1.52.3.9.3.4.11 _ SysObjectID _ BayStack 301 _ 1.3.6.1.4.1.930.1.3 _ SysObjectID _ HPJ2603A Ethernet SNMP Module, ROM B.01.00, EEPROM A.03.01, HW B.01.00 _ 1.3.6.1.4.1.11.2.3.7.8.1 _ SysObjectID _ NAT EM/450 _ 1.3.6.1.4.1.86.1.2 _ SysObjectID _ Olicom MultiMeter 3000 RMON2 _ 1.3.6.1.4.1.217.1.3.3 _ SysObjectID _ Sync Research Serial Frame Relay Access Probe With Pro-Act _ 1.3.6.1.4.1.485.7 _ SysObjectID _ XL 5 IP _ 1.3.6.1.4.1.133.1.6.8.8 _ SysObjectID _ Accelar-1200 (1.1.1) _ 1.3.6.1.4.1.2272.8 _ SysObjectID _ Cisco Catalyst 5000 _ 1.3.6.1.4.1.9.5.7 _ SysObjectID _ HP-UX B.10.10 E 9000/821 _ 1.3.6.1.4.1.11.2.3.2.3 _ SysObjectID _ Patrol Agent V3,1.9a9 (SCO) _ 1.3.6.1.4.1.1031.1.1 _ SysObjectID _ 4BSD/ISODE SNMP _ 1.3.6.1.4.1.4.1.2.5 _ SysObjectID _ MLARS _ _ iftype _ MLARS _ 1.3.6.1.4.1.2929 _ SysObjectID _ NetFlow _ _ iftype _ Cisco_MPLS_LSP _ _ iftype _ Exporting the nodetype: resmgr -export ngp -colnames "npath ncl.name ncl.oid ncl.type" -filter "ncl.type(sysobjectid)" -file $DIR/ngp.dat # type = ngp # col = npath ncl.name ncl.oid ncl.type # filter = ncl.type(sysobjectid) # order = # sep = _ # seprec = # # cmdline = -export ngp -colnames "npath ncl.name ncl.oid ncl.type" -filter "ncl.type(sysobjectid)" ~NodesType~Router~Cisco _ Cisco 2501 _ 1.3.6.1.4.1.9.1.17 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco LS1010 _ 1.3.6.1.4.1.9.1.107 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco WSX 5302 _ 1.3.6.1.4.1.9.1.168 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 4700 _ 1.3.6.1.4.1.9.1.50 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 4500 _ 1.3.6.1.4.1.9.1.14 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 2513 _ 1.3.6.1.4.1.9.1.29 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 2504 _ 1.3.6.1.4.1.9.1.20 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 3640 _ 1.3.6.1.4.1.9.1.110 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 7000 _ 1.3.6.1.4.1.9.1.8 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 2507 _ 1.3.6.1.4.1.9.1.23 _ SysObjectID _ 100 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

~NodesType~Router~Cisco _ Cisco 4000 _ 1.3.6.1.4.1.9.1.7 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 753 _ 1.3.6.1.4.1.9.1.83 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 2524 _ 1.3.6.1.4.1.9.1.74 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 2511 _ 1.3.6.1.4.1.9.1.27 _ SysObjectID _ ~NodesType~Router~Cisco _ Cisco 766 _ 1.3.6.1.4.1.9.1.103 _ SysObjectID _ ~NodesType~Access~Redback _ Redback SMS 500 _ 1.3.6.1.4.1.2352.1.2 _ SysObjectID _ ~NodesType~Access~Paradyne _ PARADYNE T1 FrameSaer SLV; Model: 9124 _ 1.3.6.1.4.1.1795.1.14.2.4.4.5 _ SysObjectID _ ~NodesType~Access~Paradyne _ PARADYNE T1 FrameSaer SLV; Model: 9124/NNI _ 1.3.6.1.4.1.1795.1.14.2.4.4.6 _ SysObjectID _ ~NodesType~Access~Paradyne _ PARADYNE DDS FrameSaer SLV; Model: 9624 _ 1.3.6.1.4.1.1795.1.14.2.4.1.5 _ SysObjectID _ ~NodesType~Access~Unisphere _ Unisphere C2100 _ 1.3.6.1.4.1.2908.1 _ SysObjectID _ ~NodesType~Access~Unisphere _ Unisphere C2100Re1 _ 1.3.6.1.4.1.2908.1.1 _ SysObjectID _ ~NodesType~Access~Unisphere _ Unisphere RX1400 _ 1.3.6.1.4.1.2773.1.2.1.1 _ SysObjectID _ ~NodesType~Access~Unisphere _ Unisphere RX700 _ 1.3.6.1.4.1.2773.1.2.1.2 _ SysObjectID _ ~NodesType~Access~Lucent _ Lucent PortMaster _ 1.3.6.1.4.1.307.2.1 _ SysObjectID _ Importing nomenclature You must use the following columns when importing new nomenclature: type SysObjectID or Vendor : name oid type type iftype : name type When updating nomenclature, you must use the following columns: dbindex or name+type columns to be modified Updating the name of new equipment: resmgr -import ncl -colnames "type OLD_name name oid" -line "SysObjectID _ Cisco As inserted by discoert _ Cisco C7100-IS _ " Info : === insert : INSERT ON nomenclature ( Cisco As inserted by discoert ) (does not exist) Inserting nomenclature in a nodetype: resmgr -import ngp -colnames "npath ncl.name ncl.type " -line "~NodesType~Router~Cisco _ Cisco C7100-IS _ SysObjectID" Info : === insert : nothing ON Nomenc Group ( ~NodesType~Router~Cisco ) (exists) Info : === insert : nothing ON nomenclature ( Cisco C7100-IS ) (exists) Info : === insert : INSERT ON nomlink ( Cisco C7100-IS Cisco ) (does not exist) Info : === Update Histo : 0 Chapter 6. Managing resources 101

Deleting nomenclature You must use the following columns when importing new nomenclature: dbindex name+type Deleting a nomenclature: resmgr -delete ncl -colnames "dbindex" -line "100008514" Info : === delete : DELETE ON nomenclature ( Cisco C7100-IS ) (exists) # Unlink a nomclature to the nodetype : resmgr -delete linkgroupn -colnames "npath ncl.dbindex" -line "~NodesType~Router~Cisco _ 100008514" Info : === delete : DELETE ON nomlink (exists) Info : === Update Histo : 0 Deleting a nodetype: resmgr -delete ngp -colnames "npath" -line "~NodesType~Router~Cisco" Info : === DELETE GROUP : ~NodesType~Router~Cisco (index = 548) Info : === delete : DELETE ON Nomenc Group ( ~NodesType~Router~Cisco ) (exists) Info : === Update Histo : 0 Using mandatory links This section explains how to use mandatory links with Tioli Netcool Performance Manager resources. You can use the following option to indicate whether or not a link is mandatory: -ismandat Using mandatory links with elements You can use the following option to force a link to be mandatory (or not) between elements and the following object types: scf encl eprp For example: Display Elements With nomenclature With or without nomenclature Without nomenclature With an SNMP configuration With at least one property With or without properties Command resmgr -export elt -colnames "name encl.name" -ismandat "encl" resmgr -export elt -colnames "name encl.name" resmgr -export elt -colnames "name encl.name" -filter "encl.name(is null)" resmgr -export elt -colnames "name scf.ipaddress" -ismandat "scf" resmgr -export elt -colnames "name eprp.name" -ismandat "elt.eprp" resmgr -export elt -colnames "name eprp.name" 102 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Displaying all elements with a nomenclature: resmgr -export elt -colnames "name encl.name" -ismandat "encl" -file $DIR/isMandat_encl.dat # type = elt # col = name encl.name # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name encl.name" 192.168.1.3 _ Cisco C2600-D _ Delete_100000165_192.168.3.238 _ HP Printer ETHERNET MULTI-ENVIRONMENT _ 192.168.127.2 _ Cisco Catalyst 3524 XL _ 192.168.127.3 _ Cisco Catalyst 3524 XL _ 192.168.127.5 _ Cisco Catalyst 3524 XL _ 192.168.127.6 _ Cisco Catalyst 3524 XL _ 192.168.127.7 _ Cisco Internetwork Operating System Software \nios (tm) C3500XL Software (C3500 _ Delete_100000174_192.168.2.2 _ Cisco C2600-I _ Delete_100000176_192.168.3.253 _ Cisco 2611 _ Delete_100000179_192.168.3.62 _ Cisco Internetwork Operating System Software \nios (tm) L3 Switch/Router Softwa _ marketing.quallaby.com _ HP Printer ETHERNET MULTI-ENVIRONMENT _ Displaying all elements (with or without a nomenclature): resmgr -export elt -colnames "name encl.name" -file $DIR/isMandat_noencl.dat # type = elt # col = name encl.name # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name encl.name" Delete_200000632_192.168.3.254 _ 3Com Hub (SuperStack II PS Hub 40) _ Delete_200000788_192.168.3.37 _ BayStack 350T _ deelopment.quallaby.com _ HP Printer ETHERNET MULTI-ENVIRONMENT _ hpcolor.quallaby.com _ HP Printer ETHERNET MULTI-ENVIRONMENT _ ps.quallaby.com _ HP Printer ETHERNET MULTI-ENVIRONMENT _ finance.quallaby.com _ HP Printer ETHERNET MULTI-ENVIRONMENT _ marketing.quallaby.com _ HP Printer ETHERNET MULTI-ENVIRONMENT _ Delete_100000165_192.168.3.238 _ HP Printer ETHERNET MULTI-ENVIRONMENT _ 192.168.66.2 _ Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO _ dhcp65.quallaby.com _ Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO _ Chapter 6. Managing resources 103

echidna.quallaby.com _ Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO _ srne01.quallaby.com _ Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO _ Delete_200000793_192.168.3.227 _ Sun SNMP Agent _ Delete_200000791_192.168.3.82 _ Sun SNMP Agent _ Delete_200000790_192.168.3.226 _ Sun SNMP Agent _ Displaying all elements without nomenclature: resmgr -export elt -colnames "name encl.name" -filter "encl.name(is null)" -file $DIR/isnull_encl.dat # type = elt # col = name encl.name # filter = encl.name(is null) # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name encl.name" -filter "encl.name(is null)" Burned_100008089_192.168.1.3 _ _ 192.168.127.4 _ _ APRouterforprobe _ _ PROVISO _ _ default _ _ Displaying all elements with a SNMP configuration: resmgr -export elt -colnames "name scf.ipaddress" -ismandat "scf" -file $DIR/isMandat_scf.dat # type = elt # col = name scf.ipaddress # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name scf.ipaddress" default _ *.*.*.* _ 192.168.1.3 _ 192.168.2.1 _ 192.168.127.254 _ 192.168.127.254 _ 192.168.64.253 _ 192.168.64.253 _ 192.168.127.9 _ 192.168.127.9 _ APRouterforprobe _ 172.17.100.254 _ 192.168.127.8 _ 192.168.127.8 _ 192.168.127.6 _ 192.168.127.6 _ Displaying all elements with at least one property: resmgr -export elt -colnames "name eprp.name" -ismandat "elt.eprp" -file $DIR/isMandat_eprp.dat # type = elt # col = name eprp.name 104 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

# filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name eprp.name" u440.quallaby.com _ ipaddress _ ipaddressmin _ ipname _ sysdescr _ sysname _ unisphere.quallaby.com _ ipaddress _ ipaddressmin _ ipname _ sysdescr _ sysname _ Displaying all elements with or without properties: resmgr -export elt -colnames "name eprp.name" -file $DIR/all_eprp.dat # type = elt # col = name eprp.name # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name eprp.name" 172.31.0.31 _ ipaddress _ ipname _ physaddress _ sysdescr _ sysname _ 172.31.0.41 _ ipaddress _ ipname _ physaddress _ sysdescr _ sysname _ 172.31.0.51 _ ipaddress _ ipname _ physaddress _ sysdescr _ sysname _ 172.31.1.2 _ ipaddress _ ipname _ physaddress _ sysdescr _ sysname _ 192.168.127.4 _ 192.168.127.5 _ ipaddress _ ipaddressmin _ ipname _ physaddress _ sysdescr _ sysname _ Using mandatory links with subelements You can use the mandatory option to force a link to be mandatory (or not) between subelements and the following object types: fam emptyfam seprp For example: Display Subelements with a family without family with or without a family all families without subelement links Use emptyfam to display families without subelements; not the opposite Command resmgr -export se -colnames "name fam.name" -ismandat "fam" resmgr -export se -colnames "name fam.name" -filter "fam.name(is null)" resmgr -export se -colnames "name fam.name" resmgr -export se -colnames "name fam.name" -ismandat "emptyfam" -filter "se.name(is null)" Chapter 6. Managing resources 105

Displaying all subelements with a family resmgr -export se -colnames "name fam.name" -ismandat "fam" -file $DIR/isMandat_fam.dat #type=se # col = name fam.name # filter = # order = # sep = _ # seprec = # cmdline = -export se -colnames "name fam.name" Delete_100000229_192.168.127.1_If<167> _ 2233_IF _ 192.168.127.254_If<9> _ 1213_IF _ 192.168.127.2_If<7> _ 1213_IF _ 192.168.127.7_If<30> _ 1213_IF _ 192.168.127.7_If<29> _ 1213_IF _ cme2.quallaby.com_<null> _ 1213_Deice _ Displaying all subelements without family resmgr -export se -colnames "name fam.name" -filter "fam.name(is null)" -file $DIR/isnull_fam.dat #type=se # col = name fam.name # filter = fam.name(is null) # order = # sep = _ # seprec = # # cmdline = -export se -colnames "name fam.name" -filter "fam.name(is null)" cme222.quallaby.com_<null> _ _ Displaying all subelements (with or without a family) resmgr -export se -colnames "name fam.name" -file $DIR/all_fam.dat #type=se # col = name fam.name # filter = # order = # sep = _ # seprec = # cmdline = -export se -colnames "name fam.name" TT-Element-1_NETSAP@120.1592882 _ MLARS _ NF-iphost-site-flow-BestEffort-CoffeeBucks_srcIP[Engineering-cb] dstsite[dallas]cos[besteffort] _ NetFlow _ NF-site-Bronze-CoffeeBucks_Site[Dener]cos[Bronze] _ NetFlow _ cme222.quallaby.com_<null> _ _ Displaying all families without subelements linked to them Use emptyfam for families with no subelements linked. resmgr -export se -colnames "name fam.name" -ismandat "emptyfam" -filter "se.name(is null)" -file $DIR/emptyfam.dat #type=se 106 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

# col = name fam.name # filter = se.name(is null) # order = # sep = _ # seprec = # cmdline = -export se -colnames "name fam.name" -filter "se.name(is null)" _ 1315_FR_DLC_SNMP-CIR _ Using mandatory links with subelement groups You can use the mandatory option to force a link to be mandatory (or not) between subelement groups and the following object types: app se rusr tzc By default, the ismandat option for segp = "app se rusr segp", so the export only shows the path with child attached. For example: Display Subelement Groups only groups with timezones all groups, including empty ones only empty groups generated Command resmgr -export segp -colnames "npath cal.name tz.name" resmgr -export segp -colnames "npath se.name" -ismandat "" resmgr -export segp -colnames "dbindex name segchild.name se.name" -ismandat "" -filter "segchild.name(is null) se.name (is null) type(generated)" Displaying only groups with timezones resmgr -export segp -colnames "npath cal.name tz.name" -file $DIR/ismandat_tznull.dat # type = segp # col = npath cal.name tz.name # filter = # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "npath cal.name tz.name" ~NOC Reporting _ CME Permanent _ EST_2010 _ ~NOC Reporting _ CME Permanent _ EST_2010_DST _ ~NOC Reporting _ CME Permanent _ EST_2009 _ ~NOC Reporting _ CME Permanent _ EST_2009_DST _ Displaying all groups, including empty ones You use the -ismandat option in this command to force it to empty, because by default -ismandat is not empty. Chapter 6. Managing resources 107

resmgr -export segp -colnames "npath se.name" -ismandat "" -file $DIR/ismandat_senull.dat # type = segp # col = npath se.name # filter = # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "npath se.name" ~Partner Section~Juniper~Virtual Router~IP Interfaces~default~10.8.7.18 _ 192.168.127.2_If<23> _ ~NOC Reporting~Network Management~By location~"catalyst_ps_lab" _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~By Customer and Location~Bristol-Myers Squibb by location~"catalyst_ps_lab" _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~IP VPN~WCOM Test group~headquarters~loreal~bordeaux~test alue2 _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~IP VPN~By Customer and CoS~Loreal CoS~Gold _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~IP VPN~By Customer and VPN~Loreal VPN~Headquarters _ 192.168.127.2_If<23> _ ~NOC Reporting~IP VPN~By Class of Serice~Gold _ 192.168.127.2_If<23> _ ~NOC Reporting~IP VPN~By City~Bordeaux _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~IP VPN~By CoS~Gold _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~By CoS~Standard _ 192.168.127.2_If<23> _ ~Customer Facing Reporting~IP VPN~WCOM Test group~sales and Marketing~Volkswagen~Frankfurt _ _ ~Customer Facing Reporting~IP VPN~WCOM Test group~research and Deelopment~Cheron~San Francisco _ _ ~NOC Reporting~Virtual Routers~IP Address Pools~%(Element.NAME) _ _ ~Customer Facing Reporting~By Customer and Location~CVS by location~dener _ _ ~Customer Facing Reporting~IP VPN~WCOM Test group~research and Deelopment~Fiat~Rome _ _ ~Partner Section~Cisco~Netflow _ _ Displaying only empty groups resmgr -export segp -colnames "dbindex name segchild.name se.name" -ismandat "" -filter "segchild.name(is null) se.name(is null) type(generated)" -file $DIR/emptyGroup.dat # type = segp # col = dbindex name segchild.name se.name # filter = segchild.name(is null) se.name(is null) type(generated) # order = # sep = _ # seprec = 108 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

# # cmdline = -export segp -colnames "dbindex name segchild.name se.name" -filter "segchild.name(is null) se.name(is null) type(generated )" 200000049 _ test alue2 _ _ _ 100001001 _ Dener _ _ _ 100010002 _ 172.17.100.254 _ _ _ 100001078 _ Dallas _ _ _ 100000990 _ Houston _ _ _ 200000153 _ test alue2 _ _ _ Using mandatory links with inentory profiles You can use the mandatory option to force a link to be mandatory (or not) between inentory profiles and the following object types: opt By default, the ismandat option for ogp = opt, so the opt needs to exist for the npath. Displaying the npath without options resmgr -export ogp -ismandat "" -colnames "npath opt.name" -filter "opt.name(is null)" -file $DIR/ogp_noOpt.dat # type = ogp # col = npath opt.name # filter = opt.name(is null) # order = # sep = _ # seprec = # # cmdline = -export ogp -colnames "npath opt.name" -filter "opt.name(is null)" ~SROB-Migration41-Test~synchro~filestoinsert _ _ ~QuallabyNetwork~synchro~filestoinsert _ _ ~default~inentory~ipaddress~exclude _ _ ~PROVISO_MONITORING~inentory~ipaddress~exclude _ _ ~Cisco_SAA~inentory~ipaddress~exclude _ _ ~PROVISO_MONITORING~synchro~filestoinsert _ _ ~default~synchro~filestoinsert _ _ ~bulk_2~synchro~filestoinsert _ _ ~ _ _ ~Cisco_SAA~synchro~filestoinsert _ _ ~bulk_2~inentory~ipaddress~exclude _ _ Chapter 6. Managing resources 109

Using mandatory links with nomenclature You can use the mandatory option to force a link to be mandatory (or not) between nomenclature and the following object types: node type Displaying the number of nomenclature attached to a node type resmgr -export ncl -colnames "name oid nliparent" -ismandat "nodetype" -nohead wc -l The output is a number. Displaying a list of nomenclature without nodetype defined resmgr -export ncl -colnames "name oid nliparent" -filter "nliparent(is null)" -file $DIR/ncl_noNT.dat # type = ncl # col = name oid nliparent # filter = nliparent(is null) # order = # sep = _ # seprec = # # cmdline = -export ncl -colnames "name oid nliparent" -filter "nliparent(is null)" Cabletron MicroMMAC _ 1.3.6.1.4.1.52.3.9.3.4.3 _ _ Cisco IPsec _ 1.3.6.1.2.1.33 _ _ Cisco_IPSec _ _ _ Cisco Internetwork Operating System Software \nios (tm) C3500XL Software (C3500 _ 1.3.6.1.4.1.9.1.278 _ _ 1213_Deice _ _ _ Cisco Internetwork Operating System Software \nios (tm) C2600 Software (C2600-I _ 1.3.6.1.4.1.9.1.209 _ _ MLARS _ _ _ Cisco Internetwork Operating System Software \nios (tm) L3 Switch/Router Softwa _ 1.3.6.1.4.1.9.1.275 _ _ Cisco Internetwork Operating System Software \nios (tm) C2600 Software (C2600-I _ 1.3.6.1.4.1.9.1.208 _ _ 1213_IF _ _ _ 1315_FR_DLC_SNMP-CIR _ _ _ 110 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 7. Managing design objects Working with formulas Explains how to use resmgr to manage design objects This section explains how to use resmgr to export, import, and different Tioli Netcool Performance Manager object types that belong to the Design category. Design objects include the following types: Formulas Properties Thresholds Requests Calendars Timezones Inentory profiles Before using the commands in this chapter, reiew the information inom Chapter 4, Managing Tioli Netcool Performance Manager objects, on page 15. This section contains the commands you can use to manage formulas. You should use the Tioli Netcool Performance Manager DataMart Formula Editor to create formulas. When you use resgmr to work with the elements, you work with the following object types: frm fgp linkgroupf (import only) You need to use the -seprec option because the formula data are not stored on a single row. You need to define another separator other than the carriage return. By default the -seprec option used for formula is <E>. Exporting formulas The following examples of resmgr command used to export formulas contain the command and the results of that command. Exporting formula groups resmgr -export fgp -colnames "dbindex nname frm.dbindex frm.data frm.type frm.comment frm.date frm.state" -seprec "<E>" -file $DIR/fgp.dat # type = fgp # col = dbindex nname frm.dbindex frm.data frm.type frm.comment frm.date frm.state # filter = # order = # sep = _ # seprec = <E> # rule = # filterrule = Copyright IBM Corp. 1997, 2012 111

# # cmdline = -export fgp -colnames "dbindex nname frm.dbindex frm.data frm.type frm.comment frm.date frm.state" 1932 _ ~Alias Instance and Label Inentory~AP~Cisco_IPSec _ 4114 _ V1=OIDVAL(sysLocation.0,once); V2=OIDVAL(sysName.0); V3=OIDVAL(%H1); %V1 index "IPSec<NULL> IPSec agent on: %V3 (%V2) location<%v1> "; _ snmp _ SNMP Discoery Formula for the "Cisco_IPSec" Family - Cisc o router-leel IPSec agents _ 999640340 _ on _ <E> 1932 _ ~Alias Instance and Label Inentory~AP~Cisco_IPSec_match _ 4184 _ cipsecmibleel.0 _ snmp _ "Match" Formula for matching SubElements to the "Cisco_IPSec" Family, since they will also fulfill requirements for Family "1213_Deice" _ 983650594 _ on _ <E> 4353 _ ~AP~Tioli Netcool Performance Manager~DataManager~Element Aerage Response Time (ms) _ 4352 _ Stat( "Targets", %H1, "SNMP Response Time (ms) [last hour]" ) _ snmp _ Uses internal Tioli Netcool Performance Manager Statistics to calculate an Elements SNMP Response Time. _ 983650594 _ on _ <E> 4353 _ ~AP~Tioli Netcool Performance Manager~DataManager~Element Aailability (percent) _ 4354 _ Stat( "Targets", %H1, "SNMP Aailability (%) [last hour]" ) _ snmp _ Uses internal Tioli Netcool Performance Manager Statistics to calculate Elements Aailability in percent _ 983650594 _ on _ <E> 4353 _ ~AP~Tioli Netcool Performance Manager~DataManager~detect_reboot _ 4355 _ distrib(delta(sysuptime.0), "default:1"); _ snmp _ An example of how to detect system reboot. _ 983650594 _ on _ <E> Exporting formula MIBs resmgr -export fgp -colnames "nname frm.mibpath" -file $DIR/fgp_mibs.dat # type = fgp # col = nname frm.mibpath # filter = # order = # sep = _ # seprec = # # cmdline = -export fgp -colnames "nname frm.mibpath" ~Demo~Addressess Free _ rfc1213-mib-ii _ ~Demo~Address Pool Utilization (percent) _ rfc1213-mib-ii _ ~Alias Instance and Label Inentory~AP~Disman_Ping_Test _ rfc2925p.mi2 _ ~Alias Instance and Label Inentory~AP~Cisco_CBQoS_Action _ CISCO-CLASS-BASED-QOS-MIB.my _ ~Alias Instance and Label Inentory~AP~Cisco_CBQoS_Class _ rfc1213-mib-ii _ ~Alias Instance and Label Inentory~AP~Cisco_CBQoS_Class _ CISCO-CLASS-BASED-QOS-MIB.my _ ~Alias Instance and Label Inentory~AP~Cisco_Router_Deice_SAA_Resp _ rfc1213-mib-ii _ 112 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

~Alias Instance and Label Inentory~AP~Cisco_Router_Deice_SAA_Resp _ CISCO-RTTMON-MIB.my _ ~Alias Instance and Label Inentory~AP~Cisco_Router_Deice_SAA_Resp_match _ rfc1213-mib-ii _ ~Alias Instance and Label Inentory~AP~Cisco_Router_Deice_SAA_Resp_match _ cisco-10-mib _ ~Alias Instance and Label Inentory~AP~Cisco_Router_Deice_SAA_Resp_match _ CISCO-RTTMON-MIB.my _ ~Alias Instance and Label Inentory~AP~Cisco_Router_Deice_SAA_match _ rfc1213-mib-ii _ ~Alias Instance and Label Inentory~AP~Cisco_Router_Deice_SAA_match _ OLD-CISCO-SYSTEM-MIB.my _ ~Alias Instance and Label Inentory~AP~Cisco_Router_Deice_SAA_match _ CISCO-RTTMON-MIB.my _ ~Alias Instance and Label Inentory~AP~Cisco_Router_Deice_SAA _ rfc1213-mib-ii _ Importing formulas You must use the following columns for a new formula. By default, dbindex is taken from the designsequences column, type is import, datatype is float, nbhost is 1. frm fgp linkgroupf You can also include the following columns: for fgp, use npath for frm, use name data type for type iftype, use name type When updating formulas, you must use the following columns: for fgp, use dbindex or npath (or nnam) and the columns to be modified for frm, use dbindex and the columns to be modified Input file The input file includes the following: ~Alias Instance and Label Inentory~AP~NEW Cisco_IPSec _ V1=OIDVAL(sysLocation.0,once); V2=OIDVAL(sysName.0); V3=OIDVAL(%H1); %V1 index "IPSec<NULL> IPSec agent on: %V3 (%V2) location<%v1> "; _ snmp _ SNMP Discoery Formula for the "Cisco_IPSec" Family - Cisco router-leel IPSec agents _ <E> Importing formula groups resmgr -import fgp -colnames "nname frm.data frm.type frm.comment" -file test1 -seprec "<E>" Info: === insert: nothing ON Formula Group (~Alias Instance and Label Inentorially ) (exists) Info : === insert : INSERT ON Formulas ( NEW Cisco_IPSec ) (does not exist) Info : === insert : INSERT ON Link F/G ( NEW Cisco_IPSec ~Alias Instance and Label Inentory~AP ) (does not exist) Chapter 7. Managing design objects 113

Info : === Update Histo : 0 Deleting formulas You must use the following columns when deleting formulas: for fgp, use dbindex or npath (or nname for a formula) for frm, use dbindex Working with properties Deleting a formula group resmgr -delete fgp -colnames "npath" -line "~test1" Info : === DELETE GROUP : ~test1 (index = 100001032) Info : === delete : DELETE ON Formula Group ( ~test1 ) (exists) Info : === Update Histo : 0 Deleting a formula resmgr -delete frm -colnames "dbindex" -line "100008516" Info : === delete : DELETE ON Formulas ( NEW Cisco_IPSec ) (exists) Unlinking a formula (for example, for a cut and paste) resmgr -delete linkgroupf -colnames "npath frm.name" -line "~test1 _ Cisco_MPLS_LSP" Info : === delete : DELETE ON Link F/G ( Cisco_MPLS_LSP ~test1 ) (exists) Info : === Update Histo : 0 This section contains commands you can use when you manage properties. When you work with property object types, you work with propertye for the element properties propertyse for the subelement properties propertyru for the report user properties Both the name and the inariant must be unique. Three properties used by default for the element inariant include the following: ipname sysname physaddress Subelement properties The following table lists the subelement properties supplied by a Tioli Netcool Performance Manager installation: Subelement Property name hostip hosturl Description A specific, textual name for this entity defined by the user, most often during general network configuration. Physical IP address of the host upon which this resource resides URL address assigned to the host upon which this resource resides 114 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

hostname parent hosttype Subelement Property parenttype description class type subtype protocol protocolversion model modelid ersion patchleel country city state proince region regionid location locationid Textual name assigned to the host upon which this resource resides. Defined by the user most often during general network configuration Open-format name or ID assigned to an entity considered as a "parent" containing this resource. Is usually different from a physical host (see 'hostname' property.) Open-format "type" classification of the deice upon which this resource resides. Description Open-format "type" classification of the parent of this resource Open-format description text used in instances when helpful for grouping (currently not displayed in the DataView portal). Open-format name of the general class of resource represented (for example, deice, interface, logical port, end-to-end connection, and so on.) Open-format name of the specific type of resource represented (Ethernet, DS1, and so on.) Additional specific type information for the resource (NNI, UNI, and so on.) Transmission protocol specific to the resource (ATM, Frame Relay, IP, IPSec, TCP, UDP, MPLS, and so on.) Version of transmission protocol being used Open-format model name of the resource Open-format model ID string of the resource Open-format ersion identification of the resource Open-format patch leel 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 physically resides The proince in which the resource resides Open-format region name at which the resource resides Open-format ID string assigned to the region in which the resource resides Physical location of the resource Open-format ID string assigned to the physical location at which the resource resides Chapter 7. Managing design objects 115

Subelement Property status priority physicalcapacity committedcapacity committedburstcapacity committedpeakcapacity owner ownercustomtag department departmentid networkarea network networkid priatenetwork priatenetworkid customer customerid customertype Subelement Property customerfacingname securityprofilemask Description Operational status of the resource ('actie', 'initializing', 'maintenance', etc.) Open-format priority name or code The maximum speed of this resource (bps) The steady-rate bandwidth (bps) committed for transfer oer this resource. The transmission rate (bps) committed for short traffic bursts (for a pre-agreed duration) oer this resource. The maximum transmission rate (bps) committed for transfer oer this resource. Serice proider employee name/id to which this resource belongs User-definable property for custom resource organization attributes Serice proider department to which this resource belongs ID of the serice proider department to which this resource belongs Network area (for example, BackBone, CPE) of the entity The name of the network of which this entity is a part. The ID of the network of which this entity is a part. The name of the priate (irtual) network of which this entity is a part. The ID of the priate (irtual) network of which this entity is a part. The name of the specific customer that this resource serices. The ID of the specific customer that this resource serices. The type of the customer that this resource serices. Description Alternate name to be used for this resource in customer-facing reports, messages, and so on. Open-format string for definition of a text mask which can be generated for users by a custom user group control system and used within rule conditions to organize user groups' access to resource iews. 116 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Exporting properties The following examples of resmgr command used to export properties contain the command and the results of that command. Exporting element properties resmgr -export propertye -colnames "name inariant defvalue state" -file $DIR/propertyE.dat # type = propertye # col = name inariant defvalue state # filter = inariant(type<e>) inariant(type<e>) # order = # sep = _ # seprec = # # cmdline = -export propertye -colnames "name inariant defvalue state" -filter "inariant(type<e>) inariant(type<e>)" ipaddress _ type<e> _ _ on _ ipaddressmin _ type<e> _ _ on _ ipname _ type<e> _ _ on _ physaddress _ type<e> _ _ on _ sysdescr _ type<e> _ _ on _ sysname _ type<e> _ _ on _ Exporting subelement properties resmgr -export propertyse -colnames "name inariant defvalue state" -file $DIR/propertySE.dat # type = propertyse # col = name inariant defvalue state # filter = inariant(type<se>) inariant(type<se>) # order = # sep = _ # seprec = # # cmdline = -export propertyse -colnames "name inariant defvalue state" -filter "inariant(type<se>) inariant(type<se>)" customstringproperty01 _ type<se> _ _ on _ customstringproperty02 _ type<se> _ _ on _ customstringproperty03 _ type<se> _ _ on _ customstringproperty04 _ type<se> _ _ on _ customstringproperty05 _ type<se> _ _ on _ customnumericproperty01 _ type<se> _ _ on _ customnumericproperty02 _ type<se> _ _ on _ customnumericproperty03 _ type<se> _ _ on _ customnumericproperty04 _ type<se> _ _ on _ customnumericproperty05 _ type<se> _ _ on _ testactiationinteral _ type<se> _ _ on _ testpacketinteral _ type<se> _ _ on _ name _ type<se> _ Undefined name Property _ on _ hostip _ type<se> _ Undefined hostip Property _ on _ Chapter 7. Managing design objects 117

hosturl _ type<se> _ _ on _ Exporting property default alues You can export the default alue (DefVal) of the property (as defined in the database) for a resource that does not yet exist by using the following option. -isdefault You can use this option with the following object types: eprp seprp ruprp Exporting element property default alues resmgr -export elt -colnames "name eprp.contact:alue" -isdefault eprp -file $DIR/isdefault_eprp.dat # type = elt # col = name eprp.contact:alue # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name eprp.contact:alue" 172.31.0.51 _ 1 _ pdemo1 _ 172.31.0.41 _ 1 _ pdemo2 _ 172.31.0.31 _ 1 _ pdemo3 _ Delete_200000793_192.168.3.227 _ 1 _ pdemo3 _ 192.168.127.8 _ 1 _ pdemo2 _ Displaying the defval for properties that do not yet exist resmgr -export propertye -colnames "name datatype subtype inariant state defvalue" -file $DIR/defVal.dat # type = propertye # col = name datatype subtype inariant state defvalue # filter = inariant(type<e>) inariant(type<e>) # order = # sep = _ # seprec = # # cmdline = -export propertye -colnames "name datatype subtype inariant state defvalue" -filter "inariant(type<e>)" " ipaddress _ string _ _ type<e> _ on _ _ ipaddressmin _ string _ _ type<e> _ on _ _ ipname _ string _ _ type<e> _ on _ _ physaddress _ string _ _ type<e> _ on _ _ sysdescr _ string _ _ type<e> _ on _ _ sysname _ string _ _ type<e> _ on _ _ Conctact _ string _ _ type<e> _ on _ pdemo3 _ 118 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Trouble Ticket pack properties The following properties are a subset of Tioli Netcool Performance Manager Technology Pack properties. See the Tioli Netcool Performance Manager Technology Pack documentation for information. SericeContract SericeCity SericeEmail SericeFax SericeFirstName SericeFirmName SericeMaxOutage SericePhone SericeRate SericeStatus SericeStreet SericeType SericeZip SericeLeel SupportLeel StatusCode SericeMobile SericeLastName TicketID NetFlow Pack Property NF_aggVIEW NF_type NF_src NF_dst NF_cos NF_customer Properties used by the Tioli Netcool Performance Manager-enabled SAA probes The following table lists the probe properties: Probe Property operation timeout sourceip sourceurl Description Test operation being executed for monitor probes, RMON, and so on. Timeout duration (seconds) for target response for monitor probes, RMON, and so on. IP address of the originating side for unidirectional entities (end-to-end simplex connections, network test probes, and so on.) URL of the originating side for unidirectional entities (end-to-end simplex connections, network test probes, etc.) Chapter 7. Managing design objects 119

Probe Property sourceport destip desturl destport ProbeDefaultIPAddress responderenabled testactiationinteral testpacketinteral Description IP port used on the originating side for unidirectional entities (end-to-end simplex connections, network test probes, and so on.) IP address of the terminating side for unidirectional entities (end-to-end simplex connections, network test probes, and so on.) URL of the terminating side for unidirectional entities (end-to-end simplex connections, network test probes, and so on.) IP port used on the terminating side for unidirectional entities (End-to-end simplex connections, network test probes, and so on.) IP address of probe For latency probes, this identifies whether or not a target will respond to the probe. Time between actiations of a latency test. A latency test does not run continuously. It is dormant for a period of time, actiates, and sends one or more test packets/probes/ requests. Interal between packets /probes/requests for a latency test that sends multiple packets/probes/requests per test actiation. Exporting report user properties resmgr -export propertyru -colnames "name inariant defvalue state" -file $DIR/propertyRU.dat # type = propertyru # col = name inariant defvalue state # filter = inariant(type<dvuser>) # order = # sep = _ # seprec = # # cmdline = -export propertyru -colnames "name inariant defvalue state" -filter "inariant(type<dvuser>)" DV_UserAccessScheduler _ type<dvuser> _ _ on _ DV_UserCSSFilename _ type<dvuser> _ _ on _ DV_UserCustomLogoFile _ type<dvuser> _ _ on _ DV_UserEnableFaoriteLink _ type<dvuser> _ _ on _ DV_UserFaoriteURL _ type<dvuser> _ _ on _ DV_UserGranularitySetting _ type<dvuser> _ _ on _ DV_UserGranularity_14MONTHS _ type<dvuser> _ _ on _ DV_UserGranularity_DAILY _ type<dvuser> _ _ on _ DV_UserGranularity_MONTHLY _ type<dvuser> _ _ on _ DV_UserGranularity_QUARTERLY _ type<dvuser> _ _ on _ DV_UserGranularity_WEEKLY _ type<dvuser> _ _ on _ DV_UserGranularity_YEARLY _ type<dvuser> _ _ on _ DV_UserLoginName _ type<dvuser> _ _ on _ 120 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

DV_UserName _ type<dvuser> _ _ on _ DV_UserPreferenceAccess _ type<dvuser> _ _ on _ # for propertyru : # DV_UserProfile : ("NOC","PSLA","SLA") # DV_UserCustomLogoFile : # DV_UserResourceName The following table list report user properties: Report User Property DV_UserProfile DV_UserCustomLogoFile DV_UserResourceName DV_UserShowCurrentPeriod Description DataView user-scope property defining the general user type for control of certain security options. Valid settings: NOC - Network Operations Center user, few restrictions. PSLA - Proactie Serice Leel Agreement personnel, moderate restriction. SLA - End users, highest restriction. DataView user-scope property with a link to an image file statically defining a custom graphic for reporter summary headings. DataView user-scope property that defines which sub-element name definitions should be used for SE labels displayed to the particular user. Valid settings: 1 - Use the SEs' internal ALIAS field alues (also dubbed "SE Labels"). 2 - Use the SEs' internal NAME field alues. 1771 - Use the alue defined in the "customerfacingname" Property for each SE. DataView user-scope property which controls access to actie-period report iewing. If equal to "true" or if undefined then the user is allowed to iew reports on the current, actie, possibly incomplete time period. Report User Property Set to "false" for a user to disable the current period iew capability. Description Chapter 7. Managing design objects 121

DV_UserEnableFaoriteLink DV_UserFaoriteURL DV_UserWelcomeReporter DV_UserLoginName DV_UserName DV_UserProbeConfigAccess Report User Property DataView user-scope property which enables the "Faorite Report" functionality (see DV_UserFaoriteURL). Valid settings are the strings 'true' and 'false'. Any setting not equal to one of these alues is interpreted as 'false'. If 'true', the "Set Faorite Report" icon and the "Goto Faorite Report" icon are displayed on the portal. If 'false', then these icons are not displayed and the feature is disabled. DataView user-scope property that specifies a user's "Faorite" report. The alue of this property is a URL that generates a DataView report. DataView user-scope property that specifies a Welcome Reporter, or a "home" page, for a user. The alue of this user property is a DataView reporter ID. Immediately following a user's initial Portal login, this Welcome Reporter is generated, so long as for that user no "Faorite Reporter"is defined and actie (see DV_UserFaoriteURL and DV_UserEnableFaoriteLink). 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. Can hae 3 states read-write - the user has access to all probe configuration/management functionality. read-only - The user may access the configuration/management GUIs, but they cannot sae, modify or delete any probes ia the GUI. null (or other alue) - the user is restricted from iewing either GUI. Null is the same as not defining the property. Description 122 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

DV_UserProbeFileConfigAccess DV_UserAccessScheduler DV_UserGranularitySetting DV_UserGranularity_DAILY DV_UserGranularity_WEEKLY DV_UserGranularity_MONTHLY DV_UserGranularity_QUARTERLY DV_UserGranularity_YEARLY DV_UserGranularity_14MONTHS Can hae 3 states read-write - the user has access to the file-based probe configuration functionality. read-only - The user may access the file-based probe configuration GUIs, but they cannot sae, modify or delete any probes ia the GUI. null (or other alue) - the user is restricted from iewing the GUI. Boolean that indicates if the user has permission to configure the Scheduler. "False" by default Boolean that indicates if the user has permission to set granularity. "False" by default (allows the user to access the granularity setting section of his preference page.) User granularity setting for daily time series reports. The default is "raw" User granularity setting for weekly time series reports. The default is "30min" User granularity setting for monthly time series reports. The default is "1day" User granularity setting for quarterly time series reports. The default is "1day" User granularity setting for yearly time series reports. The default is "1day" User granularity setting for 14 months time series reports. The default is "1day" Importing properties You must use the name column for a new property. By default, dbindex is taken from the DesignSequences column, comment is empty, state is on, and the datatype is string. When updating properties, you must use the dbindex or name columns, and the columns to be modified. Importing subelement properties resmgr -import propertyse -colnames "name datatype defvalue comment" -sep " " -line "ContactSE string none property added for test " Info : === insert : UPDATE ON property ( ContactSE ) (exists) You must use the dbindex or name column when deleting a property. Chapter 7. Managing design objects 123

Deleting subelement property Working with thresholds resmgr -delete propertyse -colnames "dbindex" -line "100008275" Info : === delete : DELETE ON property ( ContactSE ) (exists) This section contains the commands you can use to manage thresholds. When you use resgmr to work with the thresholds, you work with the following object types: thrd Exporting thresholds resmgr -export thrd -colnames "idxmetric idxgroup idxresource fgp.nname segp.npath se.name mode_decode dtedate_date thrstat_decode thrcalc_decode thrcalcvalue brstcrtclleel brstcrtcltime_time brstwrnngleel brstwrnngtime_time brstgeneent_decode prdcrtclleel prdcrtcltime_time prdwrnngleel prdwrnngtime_time prdgeneent_decode prdperiod_decode" -filter "mode_decode(oer)" -file $DIR/thrd_oer.dat # type = thrd # col = idxmetric idxgroup idxresource fgp.nname segp.npath se.name mode_decode dtedate_date thrstat_decode thrcalc_decode thrcalcvalue brstcrtclle el brstcrtcltime_time brstwrnngleel brstwrnngtime_time brstgeneent_decode prdcrtclleel prdcrtcltime_time prdwrnngleel prdwrnngtime_time prdgene ent_decode prdperiod_decode # filter = mode_decode(oer) # order = # sep = _ # seprec = # rule = # filterrule = # # cmdline = -export thrd -colnames "idxmetric idxgroup idxresource fgp.nname segp.npath se.name mode_decode dtedate_date thrstat_decode thrcalc_dec ODE thrcalcvalue brstcrtclleel brstcrtcltime_time brstwrnngleel brstwrnngtime_time brstgeneent_decode prdcrtclleel prdcrtcltime_time prdwrnngle el prdwrnngtime_time prdgeneent_decode prdperiod_decode" -filter "mode_decode(oer)" 2417 _ 6397 _ 0 _ ~AP~Generic~Instrumentation~Other~Load Operation Failures (end of period) _ _ _ Oer _ 09/13/2001 21:35 _ sum _ Standard _ _ 1.9 _ 0s _.9 _ 0s _ no _ _ _ _ _ no _ All _ 2416 _ 6397 _ 0 _ ~AP~Generic~Instrumentation~Other~Load Operation Failures _ _ _ Oer _ 09/13/2001 21:35 _ sum _ Standard _ _ 1.9 _ 0s _.9 _ 0s _ no _ _ _ _ _ no _ All _ 2415 _ 6397 _ 0 _ ~AP~Generic~Instrumentation~Other~Database Failures _ _ _ Oer _ 09/13/2001 21:35 _ sum _ Standard _ _ 1.9 _ 0s _.9 _ 0s _ no _ _ _ _ _ no _ All _ 2264 _ 6397 _ 0 _ ~AP~Generic~Uniersal~Utilization~Storage Utilization (percent) _ _ _ Oer _ 09/13/2001 21:35 _ raw _ Standard _ _ 99 _ 2h _ 98 _ 2h _ no _ _ _ _ _ no _ All _ 124 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Importing thresholds You must use the following columns for a new threshold. By default, idxgroup and idxresource = 0, all others are set to null. fgp.nname mode You can also include the following columns: all When updating thresholds, you must use the following columns: (idxmetric or fgp.nname)+(idxgroup or segp.npath if not null)+(idxresource or se.name if not null) columns to be modified resmgr -import thrd -colnames "fgp.nname segp.npath dtedate mode thrstat thrcalc brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdperiod prdgeneent" -sep " " -line "~AP~Specific~SNMP~RFC-1213~Interface~Outbound Utilization (percent) RFC-1213 Interface ~test1 1025704759 2 0 0 3 2 60 120 1 1 0" Info : === insert : INSERT ON Threshold ( 4741 0 ) (does not exist) Info : === Update Histo : 0 Deleting thresholds You must use the idx column to delete thresholds. Working with requests resmgr -delete thrd -colnames "idxmetric idxresource idxgroup" -sep " " -line "4741 0 200003865 " Info : === delete : DELETE ON Threshold ( 4741 0 ) (exists) This section contains the commands you can use to manage requests. When you use resgmr to work with requests, you work with the following object types: segpreq (collection requests) pctile (aggregation requests) allreq (all requests) Exporting all requests resmgr -export allreq -colnames "segp.npath fgp.nname period state status pctile type cal.name" -file $DIR/allreq.dat # type = allreq # col = segp.npath fgp.nname period state status pctile type cal.name # filter = # order = # sep = _ # seprec = # cmdline = -export allreq -colnames "segp.npath fgp.nname period state status pctile type cal.name" Chapter 7. Managing design objects 125

~Sub-Element Collect~Router~Deices~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Deice~CPU Utilization (percent) (ag last 5 minutes) Cisco 11. x Router Deice _ 900 _ on _ actie _ _ collection _ _ ~Sub-Element Collect~Router~Deices~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Deice~Buffer Utilization (percent) Cisco 11.x Router Deice _ 900 _ on _ actie _ _ collection _ _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Restarts Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ _ collection _ _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Resets Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ _ collection _ _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ _ collection _ _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ _ collection _ _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ _ collection _ _ Exporting subelement group requests resmgr -export segpreq -colnames "segp.npath fgp.nname period state status" -file $DIR/segpreq.dat # type = segpreq # col = segp.npath fgp.nname period state status # filter = # order = # sep = _ # seprec = # # cmdline = -export segpreq -colnames "segp.npath fgp.nname period state status" ~Sub-Element Collect~Router~Deices~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Deice~Buffer Utilization (percent) Cisco 11.x Router Deice _ 900 _ on _ actie _ ~Sub-Element Collect~Router~Deices~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Deice~CPU Utilization (percent) (ag last 5 minutes) Cisco 11.x Router Deice _ 900 _ on _ actie _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ 126 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Resets Cisco 11.x Router RFC-1213 Interface _ 900 _ on _ actie _ Exporting percentiles resmgr -export pctile -colnames "segp.npath fgp.nname state alue" -file $DIR/pctile.dat # type = pctile # col = segp.npath fgp.nname state alue # filter = # order = # sep = _ # seprec = # # cmdline = -export pctile -colnames "segp.npath fgp.nname state alue" Importing requests You must use the following columns for new requests. By default, dbindex is taken from the DesignSequences, period 900, idxcal is null, status idle, storage always, state = on, user = unix User, origin = resmgr, date = current date. segp.npath fgp.nname You can also include the following columns: period alue for pctile type+pctile for allreq When updating requests, you must use the following columns: segp.npath fgp.nname columns to be modified Importing percentiles resmgr -import "segpreq" -colnames "fgp.nname segp.npath status storage period cal.name" -line "~AP~Specific~SNMP~RFC-1213~Interface~Outbound Utilization (percent) RFC-1213 Interface _ ~Sub-Element Collect _ idle _ always _ 900 _ _ " Info : === insert : INSERT ON request ( 100008519 ) (does not exist) Info : === Update Histo : 0 Title : === CHANGES : {1 New of segpreq} Info : === Inform Collector On hebus:3002 Chapter 7. Managing design objects 127

Deleting requests You must use the following columns when deleting requests. segp.npath fgp.nname Working with calendars Deleting subelement group requests resmgr -delete segpreq -colnames "fgp.nname segp.npath" -line "~AP~Specific~SNMP~RFC-1213~Interface~Outbound Utilization (percent) RFC-1213 Interface _ ~Sub-Element Collect _ " Info : === delete : DELETE ON request ( 100008519 ) (exists) Info : === Update Histo : 0 Title : === CHANGES : {1 Deleted of segpreq} This section contains the commands you can use to manage calendars. When you use resgmr to work with calendars, you work with the cal object type. Exporting calendars Displaying list of calendars resmgr -export cal -colnames "dbindex name period state origin user date_date" -file $DIR/cal.dat # type = cal # col = dbindex name period state origin user date_date # filter = # order = # sep = _ # seprec = # # cmdline = -export cal -colnames "dbindex name period state origin user date_date" 200 _ CME Permanent _ 900 _ on _ APinstall _ APde _ 03/04/2001 00:16 _ 100006809 _ 4 AM to 8 PM restricted SLA _ 900 _ on _ unknown _ _ _ Viewing calendar detail resmgr -export cal -colnames "comment type subtype week fromday fromtime today totime" -filter "name(test1)" -file $DIR/cal_detail.dat # type = cal # col = comment type subtype week fromday fromtime today totime # filter = # order = # sep = _ # seprec = # # cmdline = -export cal -colnames "comment type subtype week fromday fromtime today totime" Daily, each day from 00:00 to 04:00 _ 1 _ 1 _ _ _ 00:00 _ _ 04:00 _ 128 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Daily, each day from 20:00 to 23:59 _ 1 _ 1 _ _ _ 20:00 _ _ 23:59 _ Importing calendars Use the Tioli Netcool Performance Manager DataMart GUI to create new calendars and resmgr for Calendar deployment. You must use the following columns for new Calendars. By default, dbindex is taken from the DesignSequences, all other columns are empty. name period When updating Calendars, you must use the following columns: dbindex or name columns to be modified Importing new calendar data resmgr -import cal -colnames " name period state user origin date_date type subtype comment week fromday fromtime today totime" -sep " " -line "psmamoimport 300 on puser resmgr 09/15/2002 18:05 1 1 Daily, each day from 04:00 to 07:59 04:00 07:59 " Info : === insert : INSERT ON Calendar ( psmamoimport ) (does not exist) Info : === insert : INSERT ON Calendar Contents ( psmamoimport Daily, each day from 04:00 to 07:59 ) (does not exist) Deleting calendars Working with timezones resmgr -delete cal -colnames " name" -line "psmamoimport" Info : === delete : DELETE ON Calendar ( psmamoimport ) (exists) This section contains the commands you can use to manage timezones. When you use resgmr to work with timzones, you work with the following object type: tz Exporting timezones Exporting all the defined aggregation sets resmgr -export tz -colnames "dbindex name date_date offset status comment" -file $DIR/tz_all.dat #type=tz # col = dbindex name date_date offset status comment # filter = # order = # sep = _ # seprec = # # cmdline = -export tz -colnames "dbindex name date_date offset status comment" 0 _ GMT _ 04/09/2002 02:30 _ 0 _ 2 _ GMT _ 0 _ EST_2002_DST _ 04/11/2002 17:00 _ -14400 _ 2 _ Eastern Standard Time _ Chapter 7. Managing design objects 129

0 _ EST_2002 _ 10/27/2002 10:00 _ -18000 _ 2 _ Eastern Standard Time _ 0 _ EST_2003_DST _ 04/06/2003 11:00 _ -14400 _ 2 _ Eastern Standard Time _ 0 _ EST_2003 _ 10/26/2003 10:00 _ -18000 _ 2 _ Eastern Standard Time _ 0 _ EST_2004_DST _ 04/04/2004 11:00 _ -14400 _ 2 _ Eastern Standard Time _ 0 _ EST_2004 _ 10/31/2004 10:00 _ -18000 _ 2 _ Eastern Standard Time _ Exporting only the currently actie timezone resmgr -export tz -colnames "dbindex date_date offset status comment" -filter "date(%now%)" -file $DIR/tz_actie.dat #type=tz # col = dbindex date_date offset status comment # filter = date(%now%) # order = # sep = _ # seprec = # # cmdline = -export tz -colnames "dbindex date_date offset status comment" -filter "date(%now%)" 0 _ 10/26/2003 10:00 _ -18000 _ 2 _ Eastern Standard Time _ Working with inentory profiles This section contains the commands you can use to manage Calendars. When you use resgmr to work with calendars, you work with the following object types: ogp opt Duplicating an inentory profile About this task To duplicate an inentory profile, you need to export it and then import it. For example: Procedure 1. Enter the following command to export the profile quallaby: resmgr -export ogp -ismandat "" -colnames "npath opt.name opt.instance opt.alue" -filter "npath(~quallaby*)" -file $DIR/ogp.dat 2. Modify the file ogp.dat by replacing quallaby with the name of the new profile. resmgr -import ogp -colnames "npath opt.name opt.instance opt.alue" -file $DIR/ogp.dat 3. Import the profile. resmgr -import ogp -mode update -colnames "npath opt.name opt.instance opt.alue" -line "~prof1 _ 100000115 _ duplicateip _ 3 _ 1 _ " Info : === update : nothing ON Option Group ( ~prof1 ) (exists) Info : === update : UPDATE ON Options ( 100000115 duplicateip ) (exists) 130 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Info : === insert : nothing ON Link O/G ( 100000115 ~prof1 ) (exists) Info : === Update Histo : 0 Importing inentory profiles You must use the following columns for new inentory profiles. npath opt.name opt.instance opt.alue See an example of importing code in step 3 under Duplicating an inentory profile on page 130. Deleting inentory profiles resmgr -delete ogp -colnames "npath" -line "~prof1" Info : === DELETE GROUP : ~prof1 (index = 100008521) Info : === delete : DELETE ON Option Group ( ~prof1 ) (exists) Info : === Update Histo : 0 Chapter 7. Managing design objects 131

132 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 8. Managing administration objects Explains how to use resmgr to manage administratie objects. This chapter explains how to use resmgr to export, import, and different Tioli Netcool Performance Manager object types that belong to the Administration category. Design objects include the following types: Tioli Netcool Performance Manager DataMart users and groups Registry Miscellaneous Tioli Netcool Performance Manager objects Working with Tioli Netcool Performance Manager DataMart users and groups This section contains the commands you can use to manage Tioli Netcool Performance Manager DataMart users and groups. When you use resgmr to work with the users and groups, you work with the following object types: usr ulink uperm Exporting users and groups Exporting users resmgr -export usr -colnames "dbindex name fullname gpname gpcomment" -order "name" -file $DIR/usr.dat # type = usr # col = dbindex name fullname gpname gpcomment # filter = # order = name # sep = _ # seprec = # # cmdline = -export usr -colnames "dbindex name fullname gpname gpcomment" 100008754 _ puser _ Create for IBM integration _ admin _ Proiso DataMart Administrators _ 100008754 _ puser _ Create for IBM integration _ puser _ Proiso DataMart Users _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ 11 _ root _ Proiso DataMart Administrator _ admin _ Proiso DataMart Administrators _ 100008755 _ lad _ User for IBM Integration _ admin _ Proiso DataMart Administrators _ 100008755 _ lad _ User for IBM Integration _ puser _ Proiso DataMart Users _ Exporting users resmgr -export usr -colnames "dbindex name fullname gpname gpcomment module perms" -filter "name(puser)" -file $DIR/usr_perms.dat # type = usr # col = dbindex name fullname gpname gpcomment module perms # filter = name(puser) # order = # sep = _ # seprec = # # cmdline = -export usr -colnames "dbindex name fullname gpname gpcomment module perms" -filter "name(puser)" 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ calconf _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ calsel _ w _ Copyright IBM Corp. 1997, 2012 133

100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ cmdedit _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ collectinfo _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ collector _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ dabdedit _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ dabdmgr _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ dabdsel _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ dataiewer _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ dbmgr _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ formedit _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ formsel _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ impexp _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ inentory _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ mibbrow _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ mibcomp _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ pollin _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ pollprofile _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ proisoinfo _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ pmstat _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ reqedit _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ resedit _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ resmgr _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ ruleconf _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ snmpconf _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ threconf _ w _ 100000014 _ puser _ Proiso Administrator _ admin _ Proiso DataMart Administrators _ userconf _ w _ Exporting groups resmgr -export usr -colnames "gpname gpcomment module perms" -file $DIR/usr_gp.dat # type = usr # col = gpname gpcomment module perms # filter = # order = # sep = _ # seprec = # # cmdline = -export usr -colnames "gpname gpcomment module perms" default _ Default Users _ dataiewer _ w _ default _ Default Users _ mibbrow _ w _ admin _ Proiso DataMart Administrators _ formedit _ w _ admin _ Proiso DataMart Administrators _ pollin _ w _ admin _ Proiso DataMart Administrators _ pollprofile _ w _ admin _ Proiso DataMart Administrators _ reqedit _ w _ admin _ Proiso DataMart Administrators _ dabdedit _ w _ admin _ Proiso DataMart Administrators _ mibcomp _ w _ admin _ Proiso DataMart Administrators _ snmpconf _ w _ admin _ Proiso DataMart Administrators _ calconf _ w _ admin _ Proiso DataMart Administrators _ userconf _ w _ admin _ Proiso DataMart Administrators _ threconf _ w _ admin _ Proiso DataMart Administrators _ cmdedit _ w _ admin _ Proiso DataMart Administrators _ inentory _ w _ admin _ Proiso DataMart Administrators _ mibbrow _ w _ Importing users and groups Creating a new user who belongs to an existing group resmgr -import usr -colnames " name fullname gpname " -line "Paul _ Paul Mc Cartney _ Proiso DataMart Users _ " Info : === insert : INSERT ON User ( Paul ) (does not exist) Info : === insert : INSERT ON User Group ( Proiso DataMart Users ) (does not exist) Info : === insert : INSERT ON Link Group/User ( Paul Proiso DataMart Users ) (does not exist) Creating a new group In this case we need to define access rights for each module. resmgr -import usr -colnames -file file.txt "gpname gpcomment module perms" 134 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

with file.txt : new1 _ Proiso DataMart new1 _ formedit _ w _ new1 _ Proiso DataMart new1 _ pollin _ w _ new1 _ Proiso DataMart new1 _ pollprofile _ w _ For a list of possible permission rights: resmgr -export usr -colnames perms -distinct 1 # type = usr # col = perms # filter = # order = # sep = _ # seprec = # rule = # filterrule = # # cmdline = -export usr -colnames "perms" r _ w _ resmgr -export usr -colnames module -distinct 1 # type = usr # col = module # filter = # order = # sep = _ # seprec = # rule = # filterrule = # # cmdline = -export usr -colnames "module" calconf _ calsel _ cmdedit _ collectinfo _ collector _ dabdedit _ dabdmgr _ dabdsel _ dataiewer _ dbmgr _ formedit _ formsel _ impexp _ inentory _ mibbrow _ mibcomp _ pollin _ pollprofile _ proisoinfo _ pmstat _ reqedit _ resedit _ resmgr _ ruleconf _ snmpconf _ threconf _ userconf _ Chapter 8. Managing administration objects 135

Deleting user and groups Deleting users resmgr -delete usr -colnames "name" -line "John" Info : === delete : DELETE ON User ( John ) (exists) Deleting groups resmgr -delete usr -colnames "gpname" -line "group1" You must ensure that you do not delete the following DataMart user groups: Group Name default admin puser Description Default Users. Tioli Netcool Performance Manager DataMart Administrators. Tioli Netcool Performance Manager DataMart Users. Working with registries Unlinking users from a group resmgr -delete ulink -colnames "name gpname" -line "John _ group1" This section contains the commands you can use to manage Tioli Netcool Performance Manager registries. When you use resgmr to work with the registries, you work with the following object types: regisdm regisdc regisdcconfig regisdb regisdv regismg (regdesc) Exporting registry objects Exporting DataMart registry resmgr -export regisdm -colnames "path name alue type" -file $DIR/regisDM.dat # type = regisdm # col = path name alue type # filter = # order = # sep = _ # seprec = # # cmdline = -export regisdm -colnames "path name alue type" DATAMART.COMMON.COUNT _ COUNT _ 1 _ 0 _ DATAMART.1.CREATION_DATE _ CREATION_DATE _ 2002-04-08 22:54 _ 2 _ DATAMART.1.PRODUCT_LABEL _ PRODUCT_LABEL _ Tioli Netcool Performance Manager DataMart _ 1 _ DATAMART.1.VERSION _ VERSION _ V4.1_R2_E2 1245 _ 1 _ DATAMART.1.HOST _ HOST _ pdemo2 _ 1 _ DATAMART.1.INSTALL_DIRECTORY _ INSTALL_DIRECTORY _ /export/home/datamart31 _ 1 _ DATAMART.1.DOC_DIRECTORY _ DOC_DIRECTORY _ /export/home/datamart31 _ 1 _ DATAMART.1.DESCRIPTION _ DESCRIPTION _ _ 1 _ 136 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

DATAMART.COMMON.Tioli Netcool Performance ManagerINFO_SERVER.HOST _ HOST _ pdemo2 _ 1 _ DATAMART.COMMON.Tioli Netcool Performance ManagerINFO_SERVER.RMI_URL _ RMI_URL _ //pdemo2:3113/proisoinfoserer _ 1 _ DATAMART.COMMON.Tioli Netcool Performance ManagerINFO_SERVER.PORT _ PORT _ 3114 _ 1 _ DATAMART.COMMON.Tioli Netcool Performance ManagerINFO_SERVER.RMI_PORT _ RMI_PORT _ 3113 _ 1 _ DATAMART.COMMON.Tioli Netcool Performance ManagerINFO_SERVER.SERVER_NAME _ SERVER_NAME _ ProisoInfoSerer _ 1 _ DATAMART.COMMON.Tioli Netcool Performance ManagerINFO_SERVER.DATAMART_ID _ DATAMART_ID _ 1 _ 0 _ DATAMART.COMMON.TZCHECK _ TZCHECK _ TRUE _ 1 _ Exporting DataChannel registry resmgr -export regisdc -colnames "path name alue type" -file $DIR/regisDC.dat # type = regisdc # col = path name alue type # filter = # order = # sep = _ # seprec = # # cmdline = -export regisdc -colnames "path name alue type" CHANNELS.DEFAULT.START_DATE _ START_DATE _ 2002-04-08 22:29 _ 2 _ CHANNELS.COMMON.FIRST_WEEK_DAY _ FIRST_WEEK_DAY _ MONDAY _ 1 _ CHANNELS.COMMON.NRAW.RECENT_KEEP_DAYS _ RECENT_KEEP_DAYS _ 32 _ 0 _ CHANNELS.COMMON.1DRA.RECENT_KEEP_DAYS _ RECENT_KEEP_DAYS _ 200 _ 0 _ CHANNELS.COMMON.1DGA.RECENT_KEEP_DAYS _ RECENT_KEEP_DAYS _ 200 _ 0 _ CHANNELS.COMMON.1WRA.RECENT_KEEP_WEEKS _ RECENT_KEEP_WEEKS _ 80 _ 0 _ CHANNELS.COMMON.1WGA.RECENT_KEEP_WEEKS _ RECENT_KEEP_WEEKS _ 80 _ 0 _ CHANNELS.COMMON.1MRA.RECENT_KEEP_MONTHS _ RECENT_KEEP_MONTHS _ 18 _ 0 _ CHANNELS.COMMON.1MGA.RECENT_KEEP_MONTHS _ RECENT_KEEP_MONTHS _ 18 _ 0 _ CHANNELS.DEFAULT.NRAW.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.NRAW.TABLESPACE.CURRENT.SIZE _ SIZE _ 344 _ 0 _ CHANNELS.DEFAULT.NRAW.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 256 _ 0 _ CHANNELS.DEFAULT.NRAW.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.NRAW.TABLESPACE.HISTORIC.SIZE _ SIZE _ 88 _ 0 _ CHANNELS.DEFAULT.NRAW.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 256 _ 0 _ CHANNELS.DEFAULT.1DRA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1DRA.TABLESPACE.CURRENT.SIZE _ SIZE _ 22 _ 0 _ CHANNELS.DEFAULT.1DRA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.DEFAULT.1DRA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1DRA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 51 _ 0 _ CHANNELS.DEFAULT.1DRA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.DEFAULT.1WRA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1WRA.TABLESPACE.CURRENT.SIZE _ SIZE _ 22 _ 0 _ CHANNELS.DEFAULT.1WRA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.DEFAULT.1WRA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1WRA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 8 _ 0 _ CHANNELS.DEFAULT.1WRA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.DEFAULT.1MRA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1MRA.TABLESPACE.CURRENT.SIZE _ SIZE _ 22 _ 0 _ CHANNELS.DEFAULT.1MRA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.DEFAULT.1MRA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1MRA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 8 _ 0 _ CHANNELS.DEFAULT.1MRA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.DEFAULT.1DGA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1DGA.TABLESPACE.CURRENT.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.DEFAULT.1DGA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.DEFAULT.1DGA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1DGA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 20 _ 0 _ CHANNELS.DEFAULT.1DGA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.DEFAULT.1WGA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1WGA.TABLESPACE.CURRENT.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.DEFAULT.1WGA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.DEFAULT.1WGA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1WGA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.DEFAULT.1WGA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.DEFAULT.1MGA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1MGA.TABLESPACE.CURRENT.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.DEFAULT.1MGA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.DEFAULT.1MGA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.DEFAULT.1MGA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.DEFAULT.1MGA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.DEFAULT.NRAW.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.NRAW.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ Chapter 8. Managing administration objects 137

CHANNELS.DEFAULT.NRAW.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.NRAW.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1DRA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1DRA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1DRA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1DRA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1WRA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1WRA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1WRA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1WRA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1MRA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1MRA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1MRA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1MRA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1DGA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1DGA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1DGA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1WGA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1MGA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.CLIENTS.LDR.TEMPORARY_TABLESPACE.SIZE _ SIZE _ 20 _ 0 _ CHANNELS.CLIENTS.LDR24.TEMPORARY_TABLESPACE.SIZE _ SIZE _ 20 _ 0 _ CHANNELS.CLIENTS.CHANNEL.TEMPORARY_TABLESPACE.SIZE _ SIZE _ 200 _ 0 _ CHANNELS.C01.START_DATE _ START_DATE _ 2002-04-08 22:29 _ 2 _ CHANNELS.C01.NRAW.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.NRAW.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.NRAW.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 256 _ 0 _ CHANNELS.C01.NRAW.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 256 _ 0 _ CHANNELS.C01.1DRA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1DRA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1DRA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.C01.1DRA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.C01.1WRA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1WRA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1WRA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.C01.1WRA.TABLESPACE.CURRENT.SIZE _ SIZE _ 22 _ 0 _ CHANNELS.C01.1WRA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.C01.1MRA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1MRA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1MRA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.C01.1MRA.TABLESPACE.CURRENT.SIZE _ SIZE _ 22 _ 0 _ CHANNELS.C01.1MRA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 512 _ 0 _ CHANNELS.C01.1DGA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1DGA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1DGA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.C01.1DGA.TABLESPACE.CURRENT.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.C01.1DGA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.C01.1WGA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1WGA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1WGA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.C01.1WGA.TABLESPACE.CURRENT.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.C01.1WGA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.C01.1MGA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1MGA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.C01.1MGA.TABLESPACE.CURRENT.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.C01.1MGA.TABLESPACE.CURRENT.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.C01.1MGA.TABLESPACE.HISTORIC.EXTENT_SIZE _ EXTENT_SIZE _ 64 _ 0 _ CHANNELS.COMMON.NRAW.CURRENT_KEEP_DAYS _ CURRENT_KEEP_DAYS _ 3 _ 0 _ CHANNELS.COMMON.1WRA.CURRENT_KEEP_WEEKS _ CURRENT_KEEP_WEEKS _ 2 _ 0 _ CHANNELS.COMMON.1MRA.CURRENT_KEEP_MONTHS _ CURRENT_KEEP_MONTHS _ 2 _ 0 _ CHANNELS.DEFAULT.1DGA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1WGA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1WGA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1WGA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1MGA.TABLE.CURRENT.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.DEFAULT.1MGA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.DEFAULT.1MGA.TABLE.HISTORIC.PARTITION_SIZE _ PARTITION_SIZE _ 100 _ 0 _ CHANNELS.CLIENTS.LDR.TEMPORARY_TABLESPACE.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.CLIENTS.LDR.TEMPORARY_TABLESPACE.EXTENT_SIZE _ EXTENT_SIZE _ 1024 _ 0 _ CHANNELS.CLIENTS.LDR24.TEMPORARY_TABLESPACE.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.CLIENTS.LDR24.TEMPORARY_TABLESPACE.EXTENT_SIZE _ EXTENT_SIZE _ 1024 _ 0 _ CHANNELS.CLIENTS.CHANNEL.TEMPORARY_TABLESPACE.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.CLIENTS.CHANNEL.TEMPORARY_TABLESPACE.EXTENT_SIZE _ EXTENT_SIZE _ 1024 _ 0 _ CHANNELS.C01.NRAW.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.NRAW.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.NRAW.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.NRAW.TABLESPACE.CURRENT.SIZE _ SIZE _ 344 _ 0 _ CHANNELS.C01.NRAW.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.NRAW.TABLESPACE.HISTORIC.SIZE _ SIZE _ 88 _ 0 _ CHANNELS.C01.1DRA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1DRA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ 138 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

CHANNELS.C01.1DRA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1DRA.TABLESPACE.CURRENT.SIZE _ SIZE _ 22 _ 0 _ CHANNELS.C01.1DRA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1DRA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 51 _ 0 _ CHANNELS.C01.1WRA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1WRA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1WRA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1WRA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1WRA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 8 _ 0 _ CHANNELS.C01.1MRA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1MRA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1MRA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1MRA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1MRA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 8 _ 0 _ CHANNELS.C01.1DGA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1DGA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1DGA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1DGA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1DGA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 20 _ 0 _ CHANNELS.C01.1WGA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1WGA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1WGA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1WGA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1WGA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.C01.1MGA.TABLE.CURRENT.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1MGA.TABLE.HISTORIC.PARTITION_EXTENTS _ PARTITION_EXTENTS _ 5 _ 0 _ CHANNELS.C01.1MGA.TABLESPACE.CURRENT.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1MGA.TABLESPACE.HISTORIC.CREATION_PATH _ CREATION_PATH _ /export/home0/oradata/pv30 _ 1 _ CHANNELS.C01.1MGA.TABLESPACE.HISTORIC.SIZE _ SIZE _ 10 _ 0 _ CHANNELS.COMMON.1DRA.CURRENT_KEEP_DAYS _ CURRENT_KEEP_DAYS _ 3 _ 0 _ CHANNELS.COMMON.1DGA.CURRENT_KEEP_DAYS _ CURRENT_KEEP_DAYS _ 3 _ 0 _ CHANNELS.COMMON.1WGA.CURRENT_KEEP_WEEKS _ CURRENT_KEEP_WEEKS _ 2 _ 0 _ CHANNELS.COMMON.1MGA.CURRENT_KEEP_MONTHS _ CURRENT_KEEP_MONTHS _ 2 _ 0 _ CHANNELS.COMMON.AUTOEXTEND_TOLERANCE _ AUTOEXTEND_TOLERANCE _ 100 _ 0 _ CHANNELS.COMMON.RECORDSCHEMAS.NRAW.ID _ ID _ NRAW0303 _ 1 _ CHANNELS.COMMON.RECORDSCHEMAS.RA.ID _ ID _ RAXX0401 _ 1 _ CHANNELS.COMMON.RECORDSCHEMAS.GA.ID _ ID _ GAXX0401 _ 1 _ Exporting DataChannel configuration registry resmgr -export regisdcconfig -colnames "path alue" -file $DIR/regisDCConfig.dat Exporting the configuration parameters for all CMEs: resmgr -nohead -export regisdcconfig -colnames "path alue" -filter "path(*cme*)" DCCONFIG.CME.1.1.COMPLETION_PERCENTAGE _ 100 _ DCCONFIG.CME.1.1.NEXT_HOUR_TIMEOUT _ 900 _ DCCONFIG.CME.1.1.COLLECTOR_ALIAS _ 1 _ DCCONFIG.CME.1.1.COMPRESS_OUTPUT _ FALSE _ DCCONFIG.CME.1.1.POLL_INTERVAL _ 60 _ DCCONFIG.CME.1.1.AGGREGATION_FIDELITY _ HIGH _ DCCONFIG.CME.1.1.LOG_TRAPS _ FALSE _ DCCONFIG.CME.1.1.IS_REMOTE _ FALSE _ DCCONFIG.CME.1.1.DUAL_LOGGING _ FALSE _ DCCONFIG.CME.1.1.COLLECTOR _ 1 _ DCCONFIG.CME.1.1.HOSTNAME _ POLAR _ DCCONFIG.CME.1.1.DB_PASSWORD _ AAAC _ DCCONFIG.CME.1.1.TRAP_DESTINATION _ localhost:162 _ DCCONFIG.CME.1.1.FC_RETENTION_HOURS _ 72 _ DCCONFIG.CME.1.1.TRAP_IPADDRESS_FROM_ELEMENT _ TRUE _ DCCONFIG.CME.1.1.DB_USERNAME _ PV_CHANNEL_01 _ DCCONFIG.CME.1.1.MAX_LOGS _ 3 _ DCCONFIG.CME.1.1.ROOT_DIRECTORY _ /opt/datachannel _ DCCONFIG.CME.1.1.IS_STATS_COLLECTOR _ FALSE _ DCCONFIG.CME.1.1.CHANNEL _ 1 _ DCCONFIG.CME.1.1.LOG_FILTER _ FEWI 123 _ Exporting the config parameters for SNMP collector 1 on channel 1: resmgr -nohead -export regisdcconfig -colnames "path alue" -filter "path(*snmp.1.1*)" Chapter 8. Managing administration objects 139

DCCONFIG.SNMP.1.1.DB_USERNAME _ PV_COLL _ DCCONFIG.SNMP.1.1.DUAL_LOGGING _ TRUE _ DCCONFIG.SNMP.1.1.MAX_LOGS _ 3 _ DCCONFIG.SNMP.1.1.DB_PASSWORD _ AAAC _ DCCONFIG.SNMP.1.1.FC_RETENTION_HOURS _ 72 _ DCCONFIG.SNMP.1.1.POLL_INTERVAL _ 60 _ DCCONFIG.SNMP.1.1.LOG_FILTER _ FEWI _ Exporting database registry resmgr -export regisdb -colnames "path name alue type" -file $DIR/regisDB.dat # type = regisdb # col = path name alue type # filter = # order = # sep = _ # seprec = # # cmdline = -export regisdb -colnames "path name alue type" DATABASE.SIZING.MAX_FILE_SIZE_MB _ MAX_FILE_SIZE_MB _ 65536 _ 0 _ DATABASE.SIZING.ROW_SIZE.RAW _ RAW _ 20 _ 0 _ DATABASE.SIZING.ROW_SIZE.RA _ RA _ 108 _ 0 _ DATABASE.SIZING.ROW_SIZE.GA _ GA _ 66 _ 0 _ DATABASE.BACKUP.READONLY_TIMEOUT _ READONLY_TIMEOUT _ 129600 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFGD.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFGD.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFGD.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFGI.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFGI.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFGI.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFHD.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFHD.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFHD.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFHI.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFHI.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.CFHI.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.PROH.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.PROH.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.PROH.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.THRH.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.THRH.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.THRH.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.REPT.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.REPT.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.REPT.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.REPM.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.REPM.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.REPM.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.LOIS.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.LOIS.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.LOIS.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.VOID.WARNING _ WARNING _ 70 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.VOID.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.TABLESPACE_THRESHOLD.VOID.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.GENERAL.PATCHES.DB_PATCH1180_32_1A.DESCRIPTION _ DESCRIPTION _ Patch loader installation _ 1 _ DATABASE.GENERAL.PATCHES.DB_PATCH1180_32_1A.DATE _ DATE _ 2002-06-27 18:48 _ 2 _ DATABASE.GENERAL.INSTALL_DIRECTORY _ INSTALL_DIRECTORY _ /opt/proiso _ 1 _ DATABASE.GENERAL.VERSION _ VERSION _ V3.1_R2_E1_1181, 1181 _ 1 _ DATABASE.GENERAL.VLN _ VLN _ DB411245000 _ 1 _ DATABASE.GENERAL.CHECKSUM _ CHECKSUM _ ##unknown## _ 1 _ DATABASE.GENERAL.PATCHES.PATCH31R2_E1_1181_1.DESCRIPTION _ DESCRIPTION _ Add Frml_Mib_Hist To Collector Id _ 1 _ DATABASE.GENERAL.PATCHES.PATCH31R2_E1_1181_1.DATE _ DATE _ 2002-04-11 17:57 _ 2 _ 140 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

DATABASE.GENERAL.PATCHES.DB_PATCH1180_32_2A.DESCRIPTION _ DESCRIPTION _ First half of sub-channels patch (clients may be connected) _ 1 _ DATABASE.GENERAL.PATCHES.DB_PATCH1180_32_2A.DATE _ DATE _ 2002-06-27 18:50 _ 2 _ DATABASE.GENERAL.PATCHES.DB_PATCH1180_32_1B.DESCRIPTION _ DESCRIPTION _ Add all 3.2 features except sub-channels to a 3.0 or 3.1 database _ 1 _ DATABASE.GENERAL.PATCHES.DB_PATCH1180_32_1B.DATE _ DATE _ 2002-06-27 20:04 _ 2 _ DATABASE.BACKUP.READONLY_DELAY _ READONLY_DELAY _ 7200 _ 0 _ DATABASE.GENERAL.PATCHES.DB_PATCH1180_32_2B.DESCRIPTION _ DESCRIPTION _ Second half of sub-channels patch (no connected client allowed) _ 1 _ DATABASE.GENERAL.PATCHES.DB_PATCH1180_32_2B.DATE _ DATE _ 2002-06-27 20:13 _ 2 _ DATABASE.GENERAL.PATCHES.DB_PATCH1190_32_BU.DESCRIPTION _ DESCRIPTION _ Fix reloading when recoering raw data working partitions _ 1 _ DATABASE.GENERAL.PATCHES.DB_PATCH1190_32_BU.DATE _ DATE _ 2002-06-28 21:47 _ 2 _ DATABASE.GENERAL.PATCHES.DB_PATCH1190_33.DESCRIPTION _ DESCRIPTION _ Upgrade from 3.2 + bu patch database to a 3.3-like ersion _ 1 _ DATABASE.GENERAL.PATCHES.DB_PATCH1190_33.DATE _ DATE _ 2002-11-11 20:20 _ 2 _ DATABASE.FILESYSTEM.THRESHOLD.WARNING _ WARNING _ 80 _ 0 _ DATABASE.FILESYSTEM.THRESHOLD.CRITICAL _ CRITICAL _ 90 _ 0 _ DATABASE.FILESYSTEM.THRESHOLD.DEADZONE _ DEADZONE _ 95 _ 0 _ DATABASE.GENERAL.PATCHES.DB_PATCH1200_33_BU.DESCRIPTION _ DESCRIPTION _ Fix RA 5615: Recoery issue after drop tablespace _ 1 _ DATABASE.GENERAL.PATCHES.DB_PATCH1200_33_BU.DATE _ DATE _ 2003-10-02 02:31 _ 2 _ DATABASE.GENERAL.PATCHES.DB_PATCH1205_40.DESCRIPTION _ DESCRIPTION _ Upgrade from 3.3 database to a 4.0 ersion _ 1 _ DATABASE.GENERAL.PATCHES.DB_PATCH1205_40.DATE _ DATE _ 2003-10-02 03:28 _ 2 _ DATABASE.GENERAL.PATCHES.DB_PATCH1237_41.DESCRIPTION _ DESCRIPTION _ Upgrade from 4.0 database to a 4.1 ersion _ 1 _ DATABASE.GENERAL.PATCHES.DB_PATCH1237_41.DATE _ DATE _ 2003-10-02 18:06 _ 2 _ Exporting DataView registry resmgr -export regisdv -colnames "path name alue type" -file $DIR/regisDV.dat # type = regisdv # col = path name alue type # filter = # order = # sep = _ # seprec = # # cmdline = -export regisdv -colnames "path name alue type" DATAVIEW.REALTIMECHARTS.PORT _ PORT _ 45105 _ 0 _ DATAVIEW.VERSION _ VERSION _ 1.15 _ 1 _ DATAVIEW.SCHEDULER.MASTER.LAST_UPDATE_TIME _ LAST_UPDATE_TIME _ 1065455270804 _ 0 _ DATAVIEW.SCHEDULER.MASTER.OFFPEAK.START_TIME _ START_TIME _ 79200000 _ 0 _ DATAVIEW.SCHEDULER.MASTER.OFFPEAK.END_TIME _ END_TIME _ 25200000 _ 0 _ DATAVIEW.SCHEDULER.MASTER.LATEDATA.COMPLETION_TIME _ COMPLETION_TIME _ 10800000 _ 0 _ DATAVIEW.SCHEDULER.MASTER.LATEDATA.WAIT_DAYS _ WAIT_DAYS _ 0 _ 0 _ DATAVIEW.SCHEDULER.MASTER.OFFPEAK.MAX_PROCESSES _ MAX_PROCESSES _ 20 _ 0 _ DATAVIEW.SCHEDULER.MASTER.PEAK.MAX_PROCESSES _ MAX_PROCESSES _ 5 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_RUN_ONCE _ MAX_RUN_ONCE _ 10 _ 0 _ DATAVIEW.SCHEDULER.MASTER.SLEEP_TIME _ SLEEP_TIME _ 30000 _ 0 _ DATAVIEW.SCHEDULER.MASTER.CHECK_AFTER_NO_CYCLES _ CHECK_AFTER_NO_CYCLES _ 5 _ 0 _ DATAVIEW.SCHEDULER.MASTER.QUEUE.MIN_SIZE_ALLOWED _ MIN_SIZE_ALLOWED _ 5 _ 0 _ DATAVIEW.SCHEDULER.MASTER.QUEUE.MAX_SIZE_ALLOWED _ MAX_SIZE_ALLOWED _ 40 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_PER_NOC _ MAX_PER_NOC _ 100 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_PER_PSLA _ MAX_PER_PSLA _ 50 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_PER_SLA _ MAX_PER_SLA _ 10 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_REPORTS_NOC _ MAX_REPORTS_NOC _ 100 _ 0 _ Chapter 8. Managing administration objects 141

DATAVIEW.SCHEDULER.MASTER.TASK.MAX_REPORTS_PSLA _ MAX_REPORTS_PSLA _ 50 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_REPORTS_SLA _ MAX_REPORTS_SLA _ 50 _ 0 _ DATAVIEW.SCHEDULER.MASTER.ACCEPT_WITHIN_DAYS _ ACCEPT_WITHIN_DAYS _ 1 _ 0 _ DATAVIEW.SCHEDULER.MASTER.CHECK_HEARTBEAT_AFTER_N_CRCN _ CHECK_HEARTBEAT_AFTER_N_CRCN _ 10 _ 0 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.HOST_SERVER _ HOST_SERVER _ mail2.quallaby.com _ 1 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.USER_NAME _ USER_NAME _ fcaron _ 1 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.USER_PWD _ USER_PWD _ change _ 1 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.ADMIN_ADDRESS _ ADMIN_ADDRESS _ fcaron@quallaby.com _ 1 _ DATAVIEW.SCHEDULER.MASTER.DIRECTORY.NFS_BASE _ NFS_BASE _ /export/home/silerstream/schedulernfs _ 1 _ DATAVIEW.SCHEDULER.MASTER.FTP.BASE_DIRECTORY _ BASE_DIRECTORY _ /export/home/silerstream/schedulerftp _ 1 _ DATAVIEW.SCHEDULER.MASTER.LOCK.GET_NEXT_ITEMS _ GET_NEXT_ITEMS _ No_Lock _ 1 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.NOTIFICATION_FILE _ NOTIFICATION_FILE _ _ 1 _ DATAVIEW.SCHEDULER.MASTER.FTP.LINK_INFO _ LINK_INFO _ ftp://reports _ 1 _ DATAVIEW.SCHEDULER.MASTER.REGISTER_SERVER_HEARTBEAT _ REGISTER_SERVER_HEARTBEAT _ <pdemo1.quallaby.com:8080/dv41>_<1067940609> _ 1 _ DATAVIEW.SCHEDULER.MASTER.LOCK.GET_HEARTBEAT _ GET_HEARTBEAT _ No_Lock _ 1 _ DATAVIEW.SCHEDULER.MASTER.USER.ACCESS_STR _ ACCESS_STR _ adminate _ 1 _ DATAVIEW.MASTER.GRANULARITY.DAILY _ DAILY _ null _ 1 _ DATAVIEW.MASTER.GRANULARITY.WEEKLY _ WEEKLY _ null _ 1 _ DATAVIEW.MASTER.GRANULARITY.MONTHLY _ MONTHLY _ null _ 1 _ DATAVIEW.MASTER.GRANULARITY.QUARTERLY _ QUARTERLY _ null _ 1 _ DATAVIEW.MASTER.GRANULARITY.YEARLY _ YEARLY _ null _ 1 _ DATAVIEW.MASTER.GRANULARITY.14MONTHS _ 14MONTHS _ null _ 1 _ DATAVIEW.BARWIDTH.GRP _ GRP _ 30 _ 0 _ DATAVIEW.BARWIDTH.RES _ RES _ 30 _ 0 _ Exporting DataChannel manager registry resmgr -export regismg -colnames "path name alue type" -file $DIR/regisMG.dat # type = regismg # col = path name alue type # filter = # order = # sep = _ # seprec = # # cmdline = -export regismg -colnames "path name alue type" CMGR.NAMINGSERVICE.HOST _ HOST _ PVDEMO3 _ 1 _ CMGR.NAMINGSERVICE.PORT _ PORT _ 45107 _ 0 _ CMGR.IORSERVER.HOST _ HOST _ PVDEMO3 _ 1 _ CMGR.IORSERVER.PORT _ PORT _ 2176 _ 0 _ CMGR.LOG.SERVER _ SERVER _ PVDEMO3 _ 1 _ CMGR.LOG.PORT _ PORT _ 25000 _ 0 _ CMGR.LOG.FILTER _ FILTER _ FEWI 123 _ 1 _ CMGR.LOG.SYSLOGFACILITY _ SYSLOGFACILITY _ 128 _ 0 _ Listing created registries for erification resmgr -export regdesc -colnames "registry table date comment" -DBUser ADMIN -file $DIR/regdesc.dat # type = regdesc # col = registry table date comment # filter = # order = # sep = _ # seprec = # # cmdline = -export regdesc -colnames "registry table date comment" CHANNELS _ REG_CHANNELS _ 2002/04/08 22:29:10 _ Channels management registry _ DATABASE _ REG_DATABASE _ 2002/04/08 22:29:39 _ General database configuration parameters _ DATALOAD _ REG_DATALOAD _ 2002/04/08 22:29:53 _ DataLoad management registry _ 142 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

DATAMART _ REG_DATAMART _ 2002/04/08 22:29:56 _ DataMart management registry _ DATAVIEW _ REG_DATAVIEW _ 2002/11/11 20:24:10 _ DataView management registry _ CMGR _ REG_CMGR _ 2002/06/27 20:11:02 _ Channel Manager for DataChannel _ Proiding direct access to one registry resmgr -export reginst:channels -colnames "dbindex IdxParent name nodetype alue altype format" -DBUser ADMIN -file $DIR/regInst.dat # type = reginst # col = dbindex IdxParent name nodetype alue altype format # filter = # order = # sep = _ # seprec = # # cmdline = -export reginst -colnames "dbindex IdxParent name nodetype alue altype format" 1 _ _ DEFAULT _ 0 _ _ _ _ 2 _ 1 _ START_DATE _ 1 _ 2002-04-08 22:29 _ 2 _ yyyy-mm-dd hh24:mi _ 3 _ _ COMMON _ 0 _ _ _ _ 4 _ 3 _ FIRST_WEEK_DAY _ 1 _ MONDAY _ 1 _ _ 5 _ 3 _ NRAW _ 0 _ _ _ _ 6 _ 5 _ RECENT_KEEP_DAYS _ 1 _ 32 _ 0 _ _ 7 _ 3 _ 1DRA _ 0 _ _ _ _ 8 _ 7 _ RECENT_KEEP_DAYS _ 1 _ 200 _ 0 _ _ 9 _ 3 _ 1DGA _ 0 _ _ _ _ 10 _ 9 _ RECENT_KEEP_DAYS _ 1 _ 200 _ 0 _ _ 11 _ 3 _ 1WRA _ 0 _ _ _ _ Importing registries Do not import to regisdcconfig as your import will be oerwritten the next time you run the Topology Editor or Deployer. Updating a registry alue Note: Only an administrator, DBUser ADMIN, can update this table. resmgr -import regisdm -colnames "path name alue " -DBUser ADMIN -line "DATAMART.1.DESCRIPTION _ DESCRIPTION _ Test DBER ORA9 _ " Info : === insert : UPDATE ON Registry ( DATAMART.1.DESCRIPTION ) (exists) Deleting registries Registry does not hae to be remoed. Working with miscellaneous Tioli Netcool Performance Manager objects This section contains the commands you can use to manage the following miscellaneous Tioli Netcool Performance Manager DataMart objects. chnl: information about channel reg: information about components that are running dbi: export Tioli Netcool Performance Manager GUI information into CSV format client: registration information about Tioli Netcool Performance Manager clients orausr: list of Oracle users Chapter 8. Managing administration objects 143

Working with chnl (information about collector) Exporting channel information resmgr -export chnl -colnames "collector default port host instdir name comment display pid user port status hostreg date_date" -file $DIR/chnl.dat # type = chnl # col = collector default port host instdir name comment display pid user port status hostreg date_date # filter = # order = # sep = _ # seprec = # # cmdline = -export chnl -colnames "collector default port host instdir name comment display pid user port status hostre 1 _ yes _ 3002 _ pdemo3 _ /opt/dataload _ pmd_1 _ This module performs Requests and Real Time Queries _ :0.0 _ 1606 _ Working with reg Exporting all locks resmgr -export reg -colnames "name host port comment display pid user port status date_date lock mode" -file $DIR/reg_lock.dat # type = reg # col = name host port comment display pid user port status date_date lock mode # filter = # order = # sep = _ # seprec = # cmdline = -export reg -colnames "name host port comment display pid user port status date_date lock mode" proisoinfod _ pdemo2.quallaby.com _ 3114 _ proisoinfo daemon _ localhost:0.0 _ 13288 _ puser _ 3114 _ 1 _ 10/02/2003 pmd_1 _ pdemo3 _ 3002 _ This module performs Requests and Real Time Queries _ :0.0 _ 1606 _ puser _ 3002 _ 1 _ 10/02/ snmpconf _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 17561 _ puser _ 0 _ 0 _ 11/04/2003 00:12 _ snmpconf _ 1 _ Exporting all registered modules resmgr -export reg -colnames "name host port comment display pid user port status date_date" -file $DIR/reg_reg.dat # type = reg # col = name host port comment display pid user port status date_date # filter = # order = # sep = _ # seprec = # cmdline = -export reg -colnames "name host port comment display pid user port status date_date" proisoinfod _ pdemo2.quallaby.com _ 3114 _ proisoinfo daemon _ localhost:0.0 _ 13288 _ puser _ 3114 _ 1 _ 10/02/2003 pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 14297 _ puser _ 0 _ 0 _ 10/06/2003 15:55 _ pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 18508 _ puser _ 0 _ 0 _ 10/06/2003 19:37 _ pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 12218 _ puser _ 0 _ 0 _ 10/17/2003 01:32 _ pmd_1 _ pdemo3 _ 3002 _ This module performs Requests and Real Time Queries _ :0.0 _ 1606 _ puser _ 3002 _ 1 _ 10/02/ pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 17388 _ puser _ 0 _ 0 _ 10/10/2003 23:39 _ resedit _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 17396 _ puser _ 0 _ 0 _ 10/10/2003 23:39 _ pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 22016 _ puser _ 0 _ 0 _ 10/17/2003 17:50 _ resedit _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 12223 _ puser _ 0 _ 0 _ 10/17/2003 01:32 _ collectinfo _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 23256 _ puser _ 0 _ 0 _ 10/28/2003 20:04 _ resedit _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 22021 _ puser _ 0 _ 0 _ 10/17/2003 17:50 _ pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 14576 _ puser _ 0 _ 0 _ 10/23/2003 18:51 _ resedit _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 14581 _ puser _ 0 _ 0 _ 10/23/2003 18:51 _ pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 23111 _ puser _ 0 _ 0 _ 10/28/2003 19:46 _ pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 6011 _ puser _ 0 _ 0 _ 10/01/2003 19:53 _ pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 14810 _ puser _ 0 _ 0 _ 11/03/2003 19:18 _ pm _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 6032 _ puser _ 0 _ 0 _ 10/01/2003 19:54 _ resedit _ pdemo2.quallaby.com _ 0 _ NONE _ dhcp114:0.0 _ 6038 _ puser _ 0 _ 0 _ 10/01/2003 19:54 _ Remoing a register or lock module resmgr -delete reg -colnames "name host" -line "pm _ host1" 144 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Working with dbi Exporting database information resmgr -export dbi -colnames "dbindex name type objid label desc" -DBUser ADMIN -file $DIR/dbi.dat # type = dbi # col = dbindex name type objid label desc # filter = # order = # sep = _ # seprec = # # cmdline = -export dbi -colnames "dbindex name type objid label desc" 1 _ Identification _ Identification _ 1 _ Database Serer _ Database Serer Name Database Name = PV30 Current Database User = PV_ADMIN = pdemo2 Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production PL/SQL Release 8.1.7.4.0 - Production CORE 8.1.7.0.0 Production TNS for Solaris: Version 8.1.7.4.0 - Production NLSRTL Version 3.4.1.0.0 - Production Total SGA = 248 M - Fixed Size = 72 K - Variable Size = 185 M - Database Buffers = 62 M - Redo Buffers = 528 K _ 1 _ Identification _ Identification _ 1 _ Description _ Last Refresh Date = 2003-11-04 04:17:51 Last Refresh Duration = 1,070.310 sec _ 110 _ Proiso Version _ Information _ 10 _ Oracle 8.1.7, PVDEMO2, PV30 _ 8i _ For limited use (checking for problems after installation) Exporting registration information about Tioli Netcool Performance Manager clients resmgr -export client -colnames "login channelid type orausr.name orausr.profile orausr.defaultts orausr.tempts orausr.resgroup" -DBUser ADMIN -file $DIR/client.dat # type = client # col = login channelid type orausr.name orausr.profile orausr.defaultts orausr.tempts orausr.resgroup # filter = # order = # sep = _ # seprec = # # cmdline = -export client -colnames "login channelid type orausr.name orausr.profile orausr.defaultts orausr.tempts PV_ADMIN _ _ ADMIN _ PV_ADMIN _ PV_ADMIN_PROFILE _ PV_CFGD _ PV_ADMIN_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_METRIC _ _ METRIC _ PV_METRIC _ DEFAULT _ PV_CFGD _ PV_ADMIN_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_INSTALL _ _ INSTALL _ PV_INSTALL _ DEFAULT _ PV_CFGD _ PV_ADMIN_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_CHNL_MANAGER _ _ CHNL_MANAGER _ PV_CHNL_MANAGER _ DEFAULT _ PV_CFGD _ PV_CHNL_MANAGER_TEMP _ DEFAULT_CONSUMER_GRO PV_GUI _ _ GUI _ PV_GUI _ DEFAULT _ PV_CFGD _ PV_GUI_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_INVENTORY _ _ INVENTORY _ PV_INVENTORY _ DEFAULT _ PV_CFGD _ PV_INVENTORY_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_LOIS _ _ LOIS _ PV_LOIS _ DEFAULT _ PV_LOIS _ PV_LOIS_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_REPORT _ _ REPORT _ PV_REPORT _ DEFAULT _ PV_REPT _ PV_LOIS_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_REPORTMASTER _ _ REPORTMASTER _ PV_REPORTMASTER _ DEFAULT _ PV_REPM _ PV_LOIS_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_RESMGR _ _ RESMGR _ PV_RESMGR _ DEFAULT _ PV_CFGD _ PV_RESMGR_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_BACKUP _ _ BACKUP _ PV_BACKUP _ DEFAULT _ PV_CFGD _ PV_BACKUP_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_LDR_01 _ 1 _ LDR _ PV_LDR_01 _ DEFAULT _ PV_CFGD _ PV_LDR_01_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_LDR24_01 _ 1 _ LDR24 _ PV_LDR24_01 _ DEFAULT _ PV_CFGD _ PV_LDR24_01_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_CHANNEL_01 _ 1 _ CHANNEL _ PV_CHANNEL_01 _ DEFAULT _ PV_CFGD _ PV_CHNL01_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_COLL_01 _ _ COLL _ PV_COLL _ DEFAULT _ PV_CFGD _ PV_COLL_TEMP _ DEFAULT_CONSUMER_GROUP _ Chapter 8. Managing administration objects 145

Exporting list of Oracle users resmgr -export orausr -colnames "name profile defaultts tempts resgroup" -DBUser ADMIN -file $DIR/orausr.dat # type = orausr # col = name profile defaultts tempts resgroup # filter = # order = # sep = _ # seprec = # # cmdline = -export orausr -colnames "name profile defaultts tempts resgroup" SYS _ DEFAULT _ SYSTEM _ SYSTEM _ SYS_GROUP _ SYSTEM _ DEFAULT _ SYSTEM _ SYSTEM _ SYS_GROUP _ OUTLN _ DEFAULT _ SYSTEM _ SYSTEM _ DEFAULT_CONSUMER_GROUP _ TRACESVR _ DEFAULT _ SYSTEM _ SYSTEM _ DEFAULT_CONSUMER_GROUP _ PV_INSTALL _ DEFAULT _ PV_CFGD _ PV_ADMIN_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_GUI _ DEFAULT _ PV_CFGD _ PV_GUI_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_LOIS _ DEFAULT _ PV_LOIS _ PV_LOIS_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_REPORTMASTER _ DEFAULT _ PV_REPM _ PV_LOIS_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_COLL _ DEFAULT _ PV_CFGD _ PV_COLL_TEMP _ DEFAULT_CONSUMER_GROUP _ DBSNMP _ DEFAULT _ SYSTEM _ SYSTEM _ DEFAULT_CONSUMER_GROUP _ PV_CHANNEL_01 _ DEFAULT _ PV_CFGD _ PV_CHNL01_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_LDR24_01 _ DEFAULT _ PV_CFGD _ PV_LDR24_01_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_LDR_01 _ DEFAULT _ PV_CFGD _ PV_LDR_01_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_BACKUP _ DEFAULT _ PV_CFGD _ PV_BACKUP_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_REPORT2 _ DEFAULT _ PV_REPT2 _ PV_LOIS_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_RESMGR _ DEFAULT _ PV_CFGD _ PV_RESMGR_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_REPORT _ DEFAULT _ PV_REPT _ PV_LOIS_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_INVENTORY _ DEFAULT _ PV_CFGD _ PV_INVENTORY_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_CHNL_MANAGER _ DEFAULT _ PV_CFGD _ PV_CHNL_MANAGER_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_METRIC _ DEFAULT _ PV_CFGD _ PV_ADMIN_TEMP _ DEFAULT_CONSUMER_GROUP _ PV _ DEFAULT _ PV_CFGD _ PV_ADMIN_TEMP _ DEFAULT_CONSUMER_GROUP _ PV_ADMIN _ PV_ADMIN_PROFILE _ PV_CFGD _ PV_ADMIN_TEMP _ DEFAULT_CONSUMER_GROUP _ 146 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 9. Managing report objects Working with web users Explains how to use resmgr to manage report objects and to export, import, and different Tioli Netcool Performance Manager object types that belong to the report category. Report includes the following object types: Web users Applications Scheduler Before using the commands in this chapter, reiew the information in Chapter 4, Managing Tioli Netcool Performance Manager objects, on page 15. This section contains the commands you can use to manage web users. When you use resgmr to work with web users, you work with the following object types: rusr owner ruprp ruproperty rugp linkgroupru Exporting web user Exporting report user name and properties resmgr -export rusr -colnames "name ruprp.name ruprp.alue" -file $DIR/rusr_ruprp.dat # type = rusr # col = name ruprp.name ruprp.alue # filter = # order = # sep = _ # seprec = # # cmdline = -export rusr -colnames "name ruprp.name ruprp.alue" FAMA _ FDOU _ Frankie _ _ _ Marcus _ SSSW\\SuperUser _ DV_UserProfile _ NOC _ DV_UserResourceName _ 1 _ DV_UserShowCurrentPeriod _ true _ SSSW\\adminfcar _ DV_UserProfile _ NOC _ DV_UserResourceName _ 1 _ DV_UserShowCurrentPeriod _ true _ Copyright IBM Corp. 1997, 2012 147

SSSW\\alcatel _ DV_UserProbeConfigAccess _ read-write _ DV_UserProfile _ SLA _ DV_UserResourceName _ 1771 _ DV_UserShowCurrentPeriod _ true _ DV_UserWelcomeReporter _ 100013323 _ customerlogin _ alcatel _ customerlogo _ ALCATEL1.gif _ customerwelcome _ Alcatel _ SSSW\\bt _ DV_UserAccessScheduler _ true _ DV_UserEnableFaoriteLink _ true _ DV_UserFaoriteURL _ subelmtid%3dnull%26subelmtgrpid%3d100001470%26timespan%3dday %26reporterID%3D100001619%26startTime%3D2003.10.06.00.00.00%26relatiePeriod %3Dtimeparam%26user%3DSLA%26gr%3Dtrue%26gdm%3Dtrue _ DV_UserGranularitySetting _ true _ DV_UserGranularity_14MONTHS _ null _ DV_UserGranularity_DAILY _ null _ DV_UserGranularity_MONTHLY _ null _ DV_UserGranularity_QUARTERLY _ 1 day _ DV_UserGranularity_WEEKLY _ 30 minutes _ DV_UserGranularity_YEARLY _ 1 day _ DV_UserPreferenceAccess _ true _ DV_UserProfile _ SLA _ DV_UserResourceName _ 100000919 _ DV_UserShowCurrentPeriod _ true _ DV_UserWelcomeReporter _ 100001619 _ customerlogin _ bt _ customerlogo _ BT.gif _ customerwelcome _ BritishTelecom _ Exporting all report users resmgr -export rusr -colnames "dbindex name mail type" -file $DIR/rusr.dat # type = rusr # col = dbindex name mail type # filter = # order = # sep = _ seprec = # # cmdline = -export rusr -colnames "dbindex name mail type" 100000017 _ SSSW\\jtho _ _ Tioli Netcool Performance Manager USER _ 100000149 _ SSSW\\noc _ _ Tioli Netcool Performance Manager USER _ 100000152 _ SSSW\\coca _ _ Tioli Netcool Performance Manager USER _ 100000153 _ SSSW\\quallaby _ _ Tioli Netcool Performance Manager USER _ 100000154 _ SSSW\\business _ _ Tioli Netcool Performance Manager USER _ 100015938 _ SSSW\\cargill _ _ Tioli Netcool Performance Manager USER _ 100007838 _ SSSW\\cisco _ _ Tioli Netcool Performance Manager USER _ 100007863 _ SSSW\\ciscodemo _ _ Tioli Netcool Performance Manager USER _ 100008522 _ SSSW\\design _ _ Tioli Netcool Performance Manager USER _ 100008064 _ SSSW\\realtime _ _ Tioli Netcool Performance Manager USER _ 100009714 _ SSSW\\tt2 _ _ Tioli Netcool Performance Manager USER _ 100009717 _ SSSW\\tt1 _ _ Tioli Netcool Performance Manager USER _ 100009991 _ SSSW\\xtra _ _ Tioli Netcool Performance Manager USER _ 100009812 _ SSSW\\adminfcar _ _ Tioli Netcool Performance Manager USER _ 148 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

100009843 _ SSSW\\juniper _ _ Tioli Netcool Performance Manager USER _ 100020250 _ SSSW\\flagtelecom _ _ Tioli Netcool Performance Manager USER _ 100020666 _ Frankie _ fcaron@quallaby.com _ EMAIL RECIPIENT _ Exporting report users group resmgr -export rugp -colnames "npath rusr.name" -file $DIR/rugp.dat # type = rugp # col = npath rusr.name # filter = # order = # sep = _ # seprec = # # cmdline = -export rugp -colnames "npath rusr.name" ~Users _ SSSW\\jtho _ ~Orphans _ SSSW\\cisco _ ~Orphans _ SSSW\\ciscodemo _ ~Orphans _ SSSW\\design _ ~Orphans _ SSSW\\realtime _ ~ABC _ SSSW\\xtra _ ~Admin Noc _ SSSW\\adminfcar _ ~Orphans _ SSSW\\juniper _ ~ABC _ SSSW\\ihug _ ~ABC _ SSSW\\tnz_noc _ ~Orphans _ SSSW\\alcatel _ ~Orphans _ SSSW\\ciscode _ ~Users _ SSSW\\timl _ ~DV [Internal Use Do Not Remoe] _ SSSW\\SuperUser _ ~Orphans _ SSSW\\bt _ Importing web user Importing a new customer with a property If you want to import a new customer called customer1 with a property called property1 you can use the following command. resmgr -import rusr -colnames "name ruprp.property1:alue" -line "SSSW\\\\customer1 _ alue_property1" Info : === insert : nothing ON Report User ( SSSW\\customer1 ) (exists) Info : === insert : INSERT ON property ( property1 ) (does not exist) Info : === insert : INSERT ON Ruser property ( 100000265 100008523 alue_property1 ) (does not exist) Grouping this customer resmgr -import rugp -colnames "npath rusr.name" -line "~Group1 _ SSSW\\\\customer1" Info : === insert : nothing ON Ruser Group ( ~Group1 ) (exists) Info : === insert : nothing ON Report User ( SSSW\\customer1 ) (exists) Chapter 9. Managing report objects 149

Info : === insert : INSERT ON Link RU/RUG ( SSSW\\customer1 ) (does not exist) Group1 Deleting web user Working with reporters Deleting a report user (name or index) resmgr -delete rusr -colnames "name" -line "SSSW\\\\customer1" Info : === delete : DELETE ON Report User ( SSSW\\customer1 ) (exists) Unlinking a report user from a group resmgr -delete linkgroupru -colnames "npath rusr.name" -line "~Group1 _ SSSW\\\\customer1" Info : === delete : DELETE ON Link RU/RUG ( SSSW\\customer1 ) (exists) Info : === Update Histo : 0 Group1 Deleting just the alue of the property for a report user resmgr -delete ruproperty -colnames "name ruprp.name" -line "SSSW\\\\customer1 _ property1" Info : === delete : DELETE ON Ruser property ( 100008524 100008523 alue_property1 ) (exists) Deleting a group of report users resmgr -delete rugp -colnames "npath" -line "~Group1" Info : === DELETE GROUP : ~Group1 (index = 100007970) Info : === delete : DELETE ON Ruser Group ( ~Group1 ) (exists) Info : === Update Histo : 0 This section contains the commands you can use to manage reporters and reporter stylesheets. When you use resgmr to work with reporters, you work with the following object types: app agp apps (report Style) linkgroupapp linkgroupapps Exporting reporters Exporting report styles resmgr -export apps -seprec "<E>" -colnames "dbindex definition comment name type" -order "dbindex" -filter "name(ap TopN Chart Style - Bar - DD Details - min ag max)" -file $DIR/appS.dat # type = apps # col = dbindex definition comment name type # filter = name(ap TopN Chart Style - Bar - DD Details - min ag max) # order = dbindex # sep = _ # seprec = <E> 150 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

# # cmdline = -export apps -colnames "dbindex definition comment name type" -filter "name(ap TopN Chart Style - Bar - DD Details - min ag max)" 6073 _ <chart> <appearance opaque="true"> <color r="254" g="254" b="230">background</color> <color r="0" g="0" b="0">foreground</color> <border type="titled" title="click any bar for Details"/> </appearance> <threedeffect depth="0" eleation="0" rotation="0" effect="false"/> <iews> <iew type="bar" legend="true" isible="true"> <serie> <line size="1" style=""> <color r="150" g="150" b="255">line</color> </line> </serie> <serie> <line size="1" style=""> <color r="0" g="170" b="255">line</color> </line> </serie> <serie> <line size="1" style=""> <color r="0" g="0" b="255">line</color> </line> </serie> <serie> <line size="1" style=""> <color r="42" g="0" b="85">line</color> </line> </serie> <serie> <line size="1" style=""> <color r="31" g="34" b="255">line</color> </line> </serie> <serie> <line size="1" style=""> <color r="234" g="208" b="229">line</color> <text> Chapter 9. Managing report objects 151

<font name="arial" size="9" style="plain"/> <text-adanced alignment="center" orientation="horizontal" rotation="0"/> </text> <appearance opaque="false"> <color r="102" g="255" b="255">background</color> <color r="0" g="51" b="51">foreground</color> <border type="empty"/> </appearance> <location isible="false" x="310" y="465" w="80" h="14" anchor=""/> </footer> <size width="700" height="500"/> </chart> _ Comment here _ AP TopN Chart Style - Bar - DD Details - min ag max _ 0 _ <E> Exporting report group stylesheets resmgr -export agp -colnames "npath apps.name" -file $DIR/agp_appS.dat # type = agp # col = npath apps.name # filter = # order = # sep = _ # seprec = # # cmdline = -export agp -colnames "npath apps.name" ~AP Styles _ AP TopN Chart Style - Bar - DD Details - min ag max _ ~AP Styles _ AP Baseline Chart Style - ag max _ ~AP Styles _ AP RV Chart Style - ag _ ~AP Styles _ AP TS Chart Style - Line - ag _ ~AP Styles _ AP TS Chart Style - Bar - min ag max _ ~AP Styles _ AP TS Chart Style - Line (Y-axis 0-100) _ ~AP Styles _ AP TS Chart Style - Pie - Ratio _ ~AP Styles _ AP TS Chart Style - Bar 3-D - min ag max _ ~AP Styles _ AP TS Chart Style - Area - max ag _ ~AP Styles _ AP TS Chart Style - Bar 3-D - sum _ ~AP Styles _ AP TS Chart Style - Bar 3-D - max _ ~AP Styles _ AP TS Chart Style - Area - ag _ ~AP Styles _ AP TS Chart Style - Bar 3-D - ag _ ~AP Styles _ AP TopN Chart Style - Bar - DD Details - ag max _ ~AP Styles _ AP TopN Chart Style - Bar - DD Details - ag _ Exporting report group resmgr -export agp -colnames "dbindex npath app.name" -file $DIR/agp_app.dat # type = agp # col = dbindex npath app.name 152 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

# filter = # order = # sep = _ # seprec = # # cmdline = -export agp -colnames "dbindex npath app.name" 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Volume Resource Detail Chart _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Volume Resource _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Volume Resource Threshold - Inbound Volume (octets) _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Volume Resource Threshold - Inbound Throughput (bps) _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Volume Resource Threshold - Outbound Volume (octets) _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Volume Resource Threshold - Outbound Throughput (bps) _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Utilization Resource Detail Chart _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Utilization Resource Threshold - Inbound Utilization (percent) _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Utilization Resource Threshold - Inbound Throughput (bps) _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Utilization Resource Threshold - Outbound Utilization (percent) _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Utilization Resource Threshold - Outbound Throughput (bps) _ 7385 _ ~AP MIB-II Pack~Interface~Utilization Metrics _ Interface Utilization Group _ 7396 _ ~AP MIB-II Pack~Interface~Aailability Metrics _ Interface Aailability Resource Detail Chart _ 7396 _ ~AP MIB-II Pack~Interface~Aailability Metrics _ Interface Aailability Resource Threshold - Inbound Loss _ 7396 _ ~AP MIB-II Pack~Interface~Aailability Metrics _ Interface Aailability Resource Threshold - Aailability _ Exporting report resmgr -export app -seprec "<E>" -colnames "dbindex name comment url type data" -order "dbindex" -file $DIR/app.dat # type = app # col = dbindex name comment url type data # filter = # order = dbindex # sep = _ # seprec = <E> # # cmdline = -export app -colnames "dbindex name comment url type data" 4250 _ GST - IPSec - Phase-1 Volume and Throughput (second leel) _ AP IPSec generic pack member reporter _ PVLsGroupSummaryTable_centerTitle.html _ 1 _ "UserLogin.text=$USERPROPERTY:DV_UserLoginName" "UserWelcome.link=" Chapter 9. Managing report objects 153

"groupsummarytable.group.drilldown.reporter=4541" "CSVExport.text=Export CSV" "groupsummarytablemediator.formula3.metrics=2305" "reporterstyle=" "groupsummarytable.formula1.drilldown.reporter=4542" "reporttitle.text=ipsec - Phase-1 Volume and Throughput for $GROUP_NAME" "UserLogo.image=$USERPROPERTY:DV_UserCustomLogoFile" "UserLogo.default.link=" "groupsummarytablemediator.formula5.metrics=2307" "groupsummarytable.formula6.stats.labels=" "UserWelcome.text=Welcome $USERPROPERTY:DV_UserName" "groupsummarytablemediator.formula1.metrics=2301"... "UserLogo.link=" "groupsummarytablemediator.formula2.stats=sum" "groupsummarytablemediator.formula4.stats=ag max" "groupsummarytable.formula6.metrics.labels=" "groupsummarytable.formula2.metrics.labels=" "UpScaleNa.monthly.enable=true" "reportsummary.text=$report_period Group Summary Report - $START_TIME" "DownScaleNa.yearly.enable=true" "reporttitle.link=" "groupsummarytable.formula4.drilldown.reporter=4547" _ <E> Importing reporters New app You must use the name column when importing new applications. By default, dbindex is taken from the DesignSequences, comment, data, owner, alias is null, type =0, typer=reporter, url = none, user=unix user, and date=current date. You can also include the following columns: url data type New apps You must use the name column when importing new application style sheets. By default, dbindex is taken from the DesignSequences, comment, definition is null, and type =0. You can also include the following columns: definition comment type Updating app and apps When updating existing applications and application style sheets, you must use the dbindex or name columns, and the columns to be modified. 154 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Importing the file reportstyle.txt after modifying it resmgr -import apps -seprec "<E>" -colnames "dbindex definition comment name type" -mode insert -file $DIR/appS.dat Check the output for errors. If there is a major error, such as a corrupt file, it is reported on the last line of the output. Copying a report (only the name is modified) Use the nop keyword instead of dbindex because dbindex uniquely identifies a report. Another method is to manually modify the dbindex in the export file. resmgr -import app -seprec "<E>" -colnames "nop name comment url type data" -file /tmp/report.txt Check the output for errors. If there is a major error, such as a corrupt file, it is reported on the last line of the output. Importing application group resmgr -import agp -colnames "npath app.name" -line "~AP MIB-II Pack~Interface~TEST1 _ Interface Aailability Resource Threshold - Aailability _ " Info : === insert : INSERT ON Application Group ( ~AP MIB-II Pack~Interface~TEST1 ) (does not exist) Info : === insert : nothing ON Application ( Interface Aailability Resource Threshold - Aailability ) (exists) Info : === insert : INSERT ON Link App/AppGroup ( Interface Aailability Resource Threshold - Aailability TEST1 ) (does not exist) Info : === Update Histo : 0 Importing application group style sheets resmgr -import agp -colnames "npath apps.name" -line "~AP MIB-II Pack~Interface~TEST1 _ AP TS Chart Style - Line - White - sum _ " Info : === insert : nothing ON Application Group ( ~AP MIB-II Pack~Interface~TEST1 ) (exists) Info : === insert : nothing ON report style ( AP TS Chart Style - Line - White - sum ) (exists) Info : === insert : INSERT ON report style Link ( AP TS Chart Style - Line - White - sum TEST1 ) (does not exist) Info : === Update Histo : 0 Deleting reporters and reporter stylesheets You must use the name column when importing new applications. Mandatory cols for app or apps : dbindex or name Mandatory cols for agp : dbindex or npath Deleting report stylesheets resmgr -delete apps -colnames "name" -line "Import new report style" Info : === delete : nothing style ) (does not exist) ON report style ( Import new report Deleting report resmgr -delete app -colnames "name" -line "New GST" Info : === delete : nothing exist) ON Application ( New GST ) (does not Chapter 9. Managing report objects 155

Working with scheduler Deleting group report resmgr -delete agp -colnames "npath" -line "~AP MIB-II Pack~Interface~TEST1" Info : === DELETE GROUP : ~AP MIB-II Pack~Interface~TEST1 (index = 100008525) Info : === delete : DELETE ON Application Group ( ~AP MIB-II Pack~Interface~TEST1 ) (exists) Info : === Update Histo : 0 Unlinking a report from a report group resmgr -delete linkgroupapp -colnames "npath app.name" -line "~AP MIB-II Pack~Interface~TEST1 _ Interface Aailability Resource Threshold - Aailability" Info : === delete : DELETE ON Link App/AppGroup ( Interface Aailability Resource Threshold - Aailability TEST1 ) (exists) Info : === Update Histo : 0 Unlinking a report style from a report group resmgr -delete linkgroupapps -colnames "npath apps.name" -line "~AP MIB-II Pack~Interface~TEST1 _ AP TS Chart Style - Line - White - sum _ " Info : === delete : DELETE ON report style Link ( AP TS Chart Style - Line - White - sum TEST1 ) (exists) Info : === Update Histo : 0 This section contains the commands you can use to manage scheduler. When you use resgmr to work with scheduler, you work with the sched object type. Exporting scheduler Exporting general information resmgr -export regisdv -colnames "path name alue type" -filter "path(dataview.scheduler*)" -file $DIR/regisDV.dat DATAVIEW.SCHEDULER.MASTER.LAST_UPDATE_TIME _ LAST_UPDATE_TIME _ 1065455270804 _ 0 _ DATAVIEW.SCHEDULER.MASTER.OFFPEAK.START_TIME _ START_TIME _ 79200000 _ 0 _ DATAVIEW.SCHEDULER.MASTER.OFFPEAK.END_TIME _ END_TIME _ 25200000 _ 0 _ DATAVIEW.SCHEDULER.MASTER.LATEDATA.COMPLETION_TIME _ COMPLETION_TIME _ 10800000 _ 0 _ DATAVIEW.SCHEDULER.MASTER.LATEDATA.WAIT_DAYS _ WAIT_DAYS _ 0 _ 0 _ DATAVIEW.SCHEDULER.MASTER.OFFPEAK.MAX_PROCESSES _ MAX_PROCESSES _ 20 _ 0 _ DATAVIEW.SCHEDULER.MASTER.PEAK.MAX_PROCESSES _ MAX_PROCESSES _ 5 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_RUN_ONCE _ MAX_RUN_ONCE _ 10 _ 0 _ DATAVIEW.SCHEDULER.MASTER.SLEEP_TIME _ SLEEP_TIME _ 30000 _ 0 _ DATAVIEW.SCHEDULER.MASTER.CHECK_AFTER_NO_CYCLES _ CHECK_AFTER_NO_CYCLES _ 5 _ 0 _ DATAVIEW.SCHEDULER.MASTER.QUEUE.MIN_SIZE_ALLOWED _ MIN_SIZE_ALLOWED _ 5 _ 0 _ DATAVIEW.SCHEDULER.MASTER.QUEUE.MAX_SIZE_ALLOWED _ MAX_SIZE_ALLOWED _ 40 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_PER_NOC _ MAX_PER_NOC _ 100 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_PER_PSLA _ MAX_PER_PSLA _ 50 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_PER_SLA _ MAX_PER_SLA _ 10 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_REPORTS_NOC _ MAX_REPORTS_NOC _ 100 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_REPORTS_PSLA _ MAX_REPORTS_PSLA _ 50 _ 0 _ DATAVIEW.SCHEDULER.MASTER.TASK.MAX_REPORTS_SLA _ MAX_REPORTS_SLA _ 50 _ 0 _ 156 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

DATAVIEW.SCHEDULER.MASTER.ACCEPT_WITHIN_DAYS _ ACCEPT_WITHIN_DAYS _ 1 _ 0 _ DATAVIEW.SCHEDULER.MASTER.CHECK_HEARTBEAT_AFTER_N_CRCN _ CHECK_HEARTBEAT_AFTER_N_CRCN _ 10 _ 0 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.HOST_SERVER _ HOST_SERVER _ mail2.quallaby.com _ 1 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.USER_NAME _ USER_NAME _ fcaron _ 1 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.USER_PWD _ USER_PWD _ abcd _ 1 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.ADMIN_ADDRESS _ ADMIN_ADDRESS _ someone@quallaby.com _ 1 _ DATAVIEW.SCHEDULER.MASTER.DIRECTORY.NFS_BASE _ NFS_BASE _ / export/home/silerstream/schedulernfs _ 1 _ DATAVIEW.SCHEDULER.MASTER.FTP.BASE_DIRECTORY _ BASE_DIRECTORY _ /export/home/silerstream/schedulerftp _ 1 _ DATAVIEW.SCHEDULER.MASTER.LOCK.GET_NEXT_ITEMS _ GET_NEXT_ITEMS _ No_Lock _ 1 _ DATAVIEW.SCHEDULER.MASTER.EMAIL.NOTIFICATION_FILE _ NOTIFICATION_FILE _ _ 1 _ DATAVIEW.SCHEDULER.MASTER.FTP.LINK_INFO _ LINK_INFO _ ftp://reports _ 1 _ DATAVIEW.SCHEDULER.MASTER.REGISTER_SERVER_HEARTBEAT _ REGISTER_SERVER_HEARTBEAT _ <pdemo1.quallaby.com:8080/dv41>_<1067940609> _ 1 _ DATAVIEW.SCHEDULER.MASTER.LOCK.GET_HEARTBEAT _ GET_HEARTBEAT _ No_Lock _ 1 _ DATAVIEW.SCHEDULER.MASTER.USER.ACCESS_STR _ ACCESS_STR _ adminate _ 1 _ Exporting scheduler general information resmgr -export sched -colnames "dbindex name frequency state status start_date end_date type" -file $DIR/sched.dat # type = sched # col = dbindex name frequency state status start_date end_date type # filter = # order = # sep = _ # seprec = <E> # # cmdline = -export sched -colnames "dbindex name frequency state status start_date end_date type" 49000001 _ DAILY _ DAILY _ Assigned _ http://pdemo1.quallaby.com:8080/dv41 _ 10/06/2003 04:00 _ 01/01/1970 04:00 _ DVCR _ <E> 49000001 _ DAILY _ DAILY _ Suspended _ Suspended _ 10/06/2003 04:00 _ 01/01/1970 04:00 _ DVCR _ <E> 49000001 _ DAILY _ DAILY _ Suspended _ Suspended _ 10/06/2003 04:00 _ 01/01/1970 04:00 _ DVCR _ <E> 49000003 _ MONTHLY _ MONTHLY _ Suspended _ Suspended _ 10/07/2003 04:00 _ 01/01/1970 04:00 _ DVCR _ <E> 49000001 _ DAILY _ DAILY _ Suspended _ Suspended _ 10/08/2003 04:00 _ 10/09/2003 04:00 _ DVCR _ <E> 49000001 _ DAILY _ DAILY _ Suspended _ Suspended _ 10/09/2003 04:00 _ 01/01/1970 04:00 _ DVCR _ <E> 49000002 _ WEEKLY _ WEEKLY _ Suspended _ Suspended _ 10/17/2003 04:00 _ 01/01/1970 04:00 _ DVCR _ <E> Exporting scheduler consolidated report resmgr -export sched -colnames "name app.name" -file $DIR/sched_app.dat # type = sched # col = name app.name # filter = # order = # sep = _ # seprec = <E> # Chapter 9. Managing report objects 157

# cmdline = -export sched -colnames "name app.name" DAILY _ Daily Business Summary _ <E> DAILY _ Daily High Leel Summary _ <E> MONTHLY _ Monthly SLA Report whole customers _ <E> DAILY _ Tims Test Task _ <E> DAILY _ Essai deoteam _ <E> DAILY _ Sales _ <E> WEEKLY _ Mcer _ <E> Export scheduler email recipient resmgr -export sched -colnames "name app.name rusr.name rusr.mail rusr.type" -file $DIR/sched_mail.dat # type = sched # col = name app.name rusr.name rusr.mail rusr.type # filter = # order = # sep = _ # seprec = <E> # # cmdline = -export sched -colnames "name app.name rusr.name rusr.mail rusr.type" DAILY _ Daily Business Summary _ Frankie _ fcaron@quallaby.com _ EMAIL RECIPIENT _ <E> DAILY _ Daily High Leel Summary _ Frankie _ fcaron@quallaby.com _ EMAIL RECIPIENT _ <E> DAILY _ Tims Test Task _ Tim _ tlandon@quallaby.com _ EMAIL RECIPIENT _ <E> WEEKLY _ Mcer _ Marcus _ mcerli@quallaby.com _ EMAIL RECIPIENT _ <E> MONTHLY _ Monthly SLA Report whole customers _ Marcus _ mcerli@quallaby.com _ EMAIL RECIPIENT _ <E> DAILY _ Essai deoteam _ fama _ famadei@quallaby.com _ EMAIL RECIPIENT _ <E> DAILY _ Sales _ FAMA _ famadei@quallaby.com _ EMAIL RECIPIENT _ <E> DAILY _ Sales _ FDOU _ fdouphy@quallaby.com _ EMAIL RECIPIENT _ <E> 158 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Importing scheduler Use the export file, modify it and reimport it with the same column names. Deleting scheduler resmgr -delete sched -colnames "name" Chapter 9. Managing report objects 159

160 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 10. Managing history table and sequence objects Working with history tables Explains how to use resmgr to manage history table and sequence objects. Before using the commands in this chapter, reiew the information in Chapter 4, Managing Tioli Netcool Performance Manager objects, on page 15. Note: IBM recommends you work with IBM Support when working with history tables. This section contains the commands you can use to manage history tables. When you use resgmr to work with history tables, you work with the following object types: calh frmh thrdh elth seh segpreqh apph segph egph In addition, history tables includes the following object types: dte: this object type, date of the modification, includes the same columns as the dte found in non-historical tables. action: this object type is specific to the history table and is only accessible with the seh table. The aailable alues include: I for inserted D for deleted U for updated Exporting history tables You cannot link from a history object type to a similar object type in a non-history table. Exporting subelement history table resmgr -export seh -colnames "dbindex inariant elt.name name label instance state origin date_date action dte_date" -file $DIR/seH.dat # type = seh # col = dbindex inariant elt.name name label instance state origin date_date action dte_date # filter = # order = # sep = _ # seprec = # # cmdline = -export seh -colnames "dbindex inariant elt.name name label instance state origin date_date action dte_date" Copyright IBM Corp. 1997, 2012 161

100000222 _ _ Delete_100000165_192.168.3.238 _ 192.168.127.1_If<6> _ 192.168.127.1_IF: 6 ("16/1") (1000Mbps) _ If<6> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ 100000222 _ _ Delete_100000165_192.168.3.238 _ 192.168.127.1_If<6> _ "192.168.127.1_IF: 6 (""16/1"") (1000Mbps)" _ If<6> _ on _ resmgr _ 04/15/2002 20:10 _ U _ 04/15/2002 20:10 _ 100000222 _ _ Delete_100000165_192.168.3.238 _ Delete_100000222_192.168.127.1_If<6> _ "192.168.127.1_IF: 6 (""16/1"") (1000Mbps)" _ Delete_100000222_If<6> _ off _ inentory _ 11/20/2002 00:58 _ U _ 11/20/2002 00:58 _ 100000223 _ _ 192.168.127.2 _ 192.168.127.2_If<23> _ 192.168.127.2_IF: 23 ("Fa0/22") (0Mbps) _ If<23> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ 100000223 _ _ 192.168.127.2 _ 192.168.127.2_If<23> _ "192.168.127.2_IF: 23 (""Fa0/22"") (0Mbps)" _ If<23> _ on _ resmgr _ 04/15/2002 20:10 _ U _ 04/15/2002 20:10 _ 100000223 _ _ 192.168.127.2 _ 192.168.127.2_If<23> _ 192.168.127.2_IF: 23 (100Mbps) _ If<23> _ on _ inentory _ 12/04/2002 23:38 _ U _ 12/04/2002 23:38 _ 100000223 _ _ 192.168.127.2 _ 192.168.127.2_If<23> _ 192.168.127.2_IF: 23 (100Mbps) _ If<23> _ on _ resmgr _ 05/28/2003 18:47 _ U _ 05/28/2003 18:47 _ 100000224 _ _ de3.quallaby.com _ de3.quallaby.com_if<1> _ de3_if: 1 (10Mbps) _ If<1> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ 100000224 _ _ de3.quallaby.com _ de3.quallaby.com_if<1> _ de3_if: 1 (10Mbps) _ If<1> _ on _ resmgr _ 04/15/2002 20:10 _ U _ 04/15/2002 20:11 _ 100000225 _ _ Delete_100000165_192.168.3.238 _ 192.168.127.1_If<82> _ 192.168.127.1_IF: 82 ("4/28") (100Mbps) _ If<82> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ 100000225 _ _ Delete_100000165_192.168.3.238 _ 192.168.127.1_If<82> _ "192.168.127.1_IF: 82 (""4/28"") (100Mbps)" _ If<82> _ on _ resmgr _ 04/15/2002 20:10 _ U _ 04/15/2002 20:10 _ Exporting subelement history table with link to element in the past You need to manually locate the element within the output. You can also use the -histodate 1 option to insert into or update a history table. The subelement history table (seh) is linked to element (elt) and not to the element history table (elth.) resmgr -export seh -colnames "dbindex inariant hostidx name label instance state origin date_date action dte_date" -file $DIR/seH_elt.dat # type = seh # col = dbindex inariant hostidx name label instance state origin date_date action dte_date # filter = # order = # sep = _ # seprec = # # cmdline = -export seh -colnames "dbindex inariant hostidx name label instance state origin date_date action dte_date" 100000222 _ _ 100000165 _ 192.168.127.1_If<6> _ 192.168.127.1_IF: 6 ("16/1") (1000Mbps) _ If<6> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ 100000222 _ _ 100000165 _ 192.168.127.1_If<6> _ "192.168.127.1_IF: 6 (""16/1"") (1000Mbps)" _ If<6> _ on _ resmgr _ 04/15/2002 20:10 _ U _ 04/15/2002 20:10 _ 100000222 _ _ 100000165 _ Delete_100000222_192.168.127.1_If<6> _ "192.168.127.1_IF: 6 (""16/1"") (1000Mbps)" _ Delete_100000222_If<6> _ off _ inentory _ 11/20/2002 00:58 _ U _ 11/20/2002 00:58 _ 100000223 _ _ 100000167 _ 192.168.127.2_If<23> _ 192.168.127.2_IF: 23 ("Fa0/22") (0Mbps) _ If<23> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ 100000223 _ _ 100000167 _ 192.168.127.2_If<23> _ "192.168.127.2_IF: 23 (""Fa0/22"") (0Mbps)" _ If<23> _ on _ resmgr _ 04/15/2002 20:10 _ U _ 04/15/2002 20:10 _ 162 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

100000223 _ _ 100000167 _ 192.168.127.2_If<23> _ 192.168.127.2_IF: 23 (100Mbps) _ If<23> _ on _ inentory _ 12/04/2002 23:38 _ U _ 12/04/2002 23:38 _ 100000223 _ _ 100000167 _ 192.168.127.2_If<23> _ 192.168.127.2_IF: 23 (100Mbps) _ If<23> _ on _ resmgr _ 05/28/2003 18:47 _ U _ 05/28/2003 18:47 _ 100000224 _ _ 100000196 _ de3.quallaby.com_if<1> _ de3_if: 1 (10Mbps) _ If<1> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ 100000224 _ _ 100000196 _ de3.quallaby.com_if<1> _ de3_if: 1 (10Mbps) _ If<1> _ on _ resmgr _ 04/15/2002 20:10 _ U _ 04/15/2002 20:11 _ 100000225 _ _ 100000165 _ 192.168.127.1_If<82> _ 192.168.127.1_IF: 82 ("4/28") (100Mbps) _ If<82> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ 100000225 _ _ 100000165 _ 192.168.127.1_If<82> _ "192.168.127.1_IF: 82 (""4/28"") (100Mbps)" _ If<82> _ on _ resmgr _ 04/15/2002 20:10 _ U _ 04/15/2002 20:10 _ 100000225 _ _ 100000165 _ Delete_100000225_192.168.127.1_If<82> _ "192.168.127.1_IF: 82 (""4/28"") (100Mbps)" _ Delete_100000225_If<82> _ off _ inentory _ 11/20/2002 00:58 _ U _ 11/20/2002 00:58 _ 100000226 _ _ 100000168 _ 192.168.127.3_If<9> _ 192.168.127.3_IF: 9 ("Fa0/8") (0Mbps) _ If<9> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ 100000226 _ _ 100000168 _ 192.168.127.3_If<9> _ "192.168.127.3_IF: 9 (""Fa0/8"") (0Mbps)" _ If<9> _ on _ resmgr _ 04/15/2002 20:10 _ U _ 04/15/2002 20:10 _ 100000226 _ _ 100000168 _ 192.168.127.3_If<9> _ 192.168.127.3_IF: 9 (0Mbps) _ If<9> _ on _ inentory _ 12/04/2002 23:38 _ U _ 12/04/2002 23:38 _ 100000227 _ _ 100000179 _ 192.168.3.62_If<30> _ 192.168.3.62_IF: 30 ("Fa29") (100Mbps) _ If<30> _ on _ inentory _ 04/10/2002 01:16 _ I _ 04/10/2002 01:16 _ Exporting element state and comment history resmgr -export elth -colnames "name state comment date_date action" # resmgr -export elth -colnames "name state comment date_date action" # type = elth # col = name state comment date_date action # filter = # order = # sep = _ # seprec = # rule = # filterrule = # # cmdline = -export elth -colnames "name state comment date_date action" default _ on _ _ 05/29/2008 20:00 _ I _ L.1 _ on _ PROVISO_MONITORING _ 05/30/2008 12:21 _ I _ 10.127.78.2-1 _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1 _ on _ _ 06/01/2008 14:29 _ I _ 10.127.77.7 _ on _ _ 06/02/2008 11:21 _ I _ 10.127.77.6 _ on _ _ 06/02/2008 11:23 _ I _ Exporting subelement state and ulabel history resmgr -export seh -colnames "name state ulabel date_date action" # resmgr -export seh -colnames "name state ulabel date_date action" # type = seh # col = name state ulabel date_date action # filter = # order = # sep = _ Chapter 10. Managing history table and sequence objects 163

# seprec = # rule = # filterrule = # # cmdline = -export seh -colnames "name state ulabel date_date action" DL.1_<NULL> _ on _ _ 05/30/2008 12:21 _ I _ DL.1_<NULL> _ on _ _ 05/30/2008 12:21 _ U _ 10.127.78.2-1_CSC<NULL> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<69> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<34> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<41> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.2-1_SLS<NULL> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<10> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<45> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<2> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<8> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<9> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<86> _ on _ _ 06/01/2008 14:29 _ I _ 10.127.78.3-1_If<20> _ on _ _ 06/01/2008 14:29 _ I _ Importing and deleting Contact IBM Support for assistance with importing or deleting history tables. Working with sequences This section contains the commands you can use to manage sequences. When you use resgmr to work with sequences, you work with the following object types: DesignIndex ResourcesIndex With these object types, you can find and modify the start of indexes for formulas and resources, using the following two resmgr options, only: -export to debug options -import for -line and debug options Find and modify the start of indexes for formulas resmgr -export DesignIndex 5000 resmgr -import DesignIndex -line 500000 Find and modify the start of indexes for resources resmgr -export ResourcesIndex 200000000 resmgr -import ResourcesIndex -line 1000000 Warnings: Each time you export, one index number is used or increased. For resources, the default start index is 200000000. In most cases it is not necessary to modify it. 164 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 11. Configuring thresholds Thresholds Explains how to use the resmgr command to configure thresholds. This chapter explains how to use resmgr to configure thresholds. Thresholds are Tioli Netcool Performance Manager object types that belong to the design category. Before using the commands in this chapter, reiew the information in Chapter 4, Managing Tioli Netcool Performance Manager objects, on page 15. Additional resmgr commands for managing thresholds can be found in Working with thresholds on page 173 of Chapter 7, Managing design objects, on page 111. This section defines thresholds and the threshold options. There are two types of thresholds in Tioli Netcool Performance Manager: Default threshold: is deployed against a metric, for any group or resource. Resource threshold: is deployed against a metric or resource, for any group. Group threshold: is deployed against a metric or group, for any resource. Group/resource threshold: is deployed against a specific metric, group or resource combination. Threshold options The following table lists threshold options: Name Definition idxmetric fgp.nname Metric Id. Prop: Not Null, not 0 idxgroup segp.name Sub-Element Group Id.Prop: Not null, defaults to 0 idxresource se.name Sub-Element Resource Id. Prop: Not null, defaults to 0 dtedate The date and time the action (STR_ACTION) takes effect. Actions cannot be applied in the past and only take effect on the hour. The alue is in seconds since January 1, 1970 GMT.Prop: Not null mode Mode of the threshold: 1 = Under, 2 = Oer, 3 = BandProp: Not null thrstat Define which statistic will be used by the CME to calculate the threshold information: 0=raw(default), 1=min, 2=max, 3=ag, 4=sum, 5=countProp: Not null Copyright IBM Corp. 1997, 2012 165

Name thrcalc Definition The calculation to be used to determine the alue of DBL_BRST_MAX_PCT_OVER and DBL_PRD_MAX_PCT_OVER. Values for this field include: 0=standard=abs(Value-Leel)/abs(Leel), 1=normalized=abs(Value-Leel)/ (critical_leel-warning_leel), 2=scaled=abs(Value-Leel)/scale thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel PrdWrnngLeel PrdCrtclTime PrdWrnngTime PrdPeriod where scale = DBL_TRH_CALC_VALUE The alue used for calculating the percentage oer/under threshold. Leel of the critical threshold for burst thresholds. Null implies that the threshold is not defined. Leel of the warning threshold for burst thresholds. Null implies that the threshold is not defined. Time limit for the critical period threshold in seconds. 0 indicates that the threshold is iolated when the metric exceeds the threshold. Time limit for the warning period threshold in seconds Indicates if Tioli Netcool Performance Manager has to generate eents for the burst threshold. 0=no, 1=yes Leel of the critical threshold for period thresholds. Null implies that the threshold is not defined. Leel of the warning threshold for period thresholds. Null implies that the threshold is not defined. Time limit for the critical period threshold in seconds Time limit for the warning period threshold in seconds Define the period for burst and period thresholds: 1=Day/2=Week/3=Month /4=All PrdGenEent "All" period means that the CME will use the period of the aggregation tables Indicates if Tioli Netcool Performance Manager has to generate eents for the period threshold. 0=no, 1=yes 166 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Deploying thresholds This section explains the different threshold deployment scenarios. Threshold deployment against groups and resources Thresholds can be deployed by Class of Serice (CoS), before any other criteria. This means that for the same metric, resources in CoS=Platinum will hae one threshold alue X, and resources in CoS=Gold will hae one threshold alue X. This figure illustrates that deploying a latency threshold of 100 ms for Platinum and 150 ms for Gold is not possible by group Chapter 11. Configuring thresholds 167

Figure 1. Grouping Structure and Threshold Configuration Two different alues are required for the same metric (latency), based on one grouping structure (CoS), and that it is required to hae also a iew of threshold iolation following another grouping structure (Location). 168 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Deploying "Non-differentiated" thresholds Non-differentiated thresholds is the preferred deployment method to follow because it does not inole resources (only metrics;) therefore, it is less CPU and memory intensie for the Tioli Netcool Performance Manager Data Channel and is easier to proision. If this method cannot be applied, you can apply the alternatie method described in section Deploying differentiated thresholds on page 171. This method is more CPU and RAM intensie for Data Channel and requires usage of the CLI because of the number of thresholds to position. You can hae a uniform or non-differentiated threshold. For example, latency is differentiated by CoS (see Threshold deployment against groups and resources on page 167) but Inbound Loss threshold is not: 1% for eery resource in the system. Chapter 11. Configuring thresholds 169

Figure 2. Non-Differentiated Threshold Deployment IBM recommends deploying thresholds at the metric leel only, with no link to any resource. This means attaching thresholds to database metric identifier (mid) without any attachment to resource identifier (rid) or group identifier (gid). 170 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Note: You can also use the Tioli Netcool Performance Manager DataMart Resource Editor to deploy non-differentiated thresholds. See Using Resource Editor in the IBM Tioli Netcool Performance Manager: DataMart Configuration and Operation Guide for details. Enter the following command: resmgr -import thrd -colnames "idxmetric(2201) mode(1) thrstat(0) thrcalc(0) thrcalcvalue(0) brstcrtclleel(1) brstwrnngleel(0.5) brstcrtcltime(900) brstwrnngtime(1800) brstgeneent(0) prdcrtclleel(1) prdwrnngleel(0.5) prdcrtcltime(7200) prdwrnngtime(3600) prdperiod(1) prdgeneent(0)" Each time a new resource is proisioned by Resource Manager or an SNMP or Bulk inentory, there is nothing to process because, as soon as the formula (for example, Inbound Loss, percent) is collected/imported against that subelement, that threshold is attached to the formula. This configuration can be considered as a default configuration for the "Inbound Loss" threshold. In the Figure 2 on page 170 figure, R1 is moing from Boston to New York. Its Inbound Loss threshold is not supposed to change. You can change the alue of the threshold for only one resource. For example, R3 becomes an exception to the rule/default alue (to reflect a specific customer commitment) and Inbound Loss threshold is changed from 1 to percent. In this case, IBM recommends to use the Resource Editor module (or Resource Manager) for creating a new threshold attached to the metric and the resource. Threshold attached to metric identifier: "Inbound Loss" Thr = 1 percent (no resource attachment used) and threshold attached to (mid, rid): "Inbound Loss" Thr = 1 percent for R3, (no resource attachment used). The (mid, rid) setting oerwrites the default metric identifier setting. Deploying differentiated thresholds If you cannot apply the non-differentiated threshold deployment, then you can apply the differentiated threshold deployment. This method is more CPU and RAM intensie for Tioli Netcool Performance Manager Data Channel and requires usage of the CLI because of the number of thresholds to position. Chapter 11. Configuring thresholds 171

Figure 3. Differentiated Threshold Deployment IBM recommends deploying threshold at the resource leel s. at the group leel. This mean attaching thresholds to couples (mid and rid) without any attachment to gid. The Resource Editor module is not usable for deployment, but more for testing and prototyping, before deployment. This is due to the number of lines that are 172 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Working with thresholds required in this interface. Each resource (network interface) x metric (latency) generates one line in the GUI, which can be unmanageable. Enter the following command: resmgr -import thrd -colnames "idxresource idxmetric(2201) mode(1) thrstat(0) thrcalc(0) thrcalcvalue(0) brstcrtclleel(1) brstwrnngleel(0.5) brstcrtcltime(900) brstwrnngtime(1800) brstgeneent(0) prdcrtclleel(1) prdwrnngleel(0.5) prdcrtcltime(7200) prdwrnngtime(3600) prdperiod(1) prdgeneent(0)" -file "./temp" In the case of feeding resources in Tioli Netcool Performance Manager with Resource Manager (from a proisioning system): eery time a new resource is proisioned by Resource Manager, this command line should be launched, so that threshold is configured when the resource is proisioned. Eery time a threshold is attached or updated at a resource leel, IBM recommends to duplicate it as a property, storing the same alue for the property. This oercomes any Tioli Netcool Performance Manager DataView issues such as it being impossible to display a threshold alue in RST/RTT/TOP N (as a property=column in the table) and it being impossible follow the history of the threshold alue within the Property History tables. It could also be impossible to display a threshold alue as simple text (in PVRcLabels). Populating a shadow property replicating this threshold and its changes helps sole these issues. This section explains how to work with thresholds. It contains information about exporting, importing, and deleting thresholds. Exporting thresholds The following are examples of exporting thresholds. Example 1 Output appears. For example: # type = thrd # col = fgp.nname segp.npath se.name mode thrstat # filter = # order = # sep = _ # seprec = FORMULA _ ~NOC Reporting~Network Management~BasicInterface & ExtendedInterface _ 192.168.3.252_<NULL> _ 1 _ 0 _ Example 2 Export of the idxgroup and idxresource fields. The thrsh_desc.idx_resource and thrsh_desc.idx_group columns hae a alue of 0. Output appears. For example: Chapter 11. Configuring thresholds 173

# type = thrd # col = fgp.nname idxgroup idxresource mode thrstat # filter = # order = # sep = _ # seprec = ~FORMULA _ 0 _ 0 _ 1 _ 0 _ Example 3 Export of the segp.npath and se.name fields. The thrsh_desc.idx_resource and thrsh_desc.idx_group columns hae a alue of 0. Output appears. For example: # type = thrd # col = fgp.nname segp.npath se.name mode thrstat # filter = # order = # sep = _ # seprec = ~FORMULA _ _ _ 1 _ 0 _ Deleting thresholds To delete a line of the threshold table, you need to proide the alue of the columns in the table. Deleting by indices Output appears. For example: # type = thrd # col = idxmetric idxresource idxgroup mode thrstat # filter = # order = # sep = _ # seprec = 4065 _ 0 _ 0 _ 1 _ 0 _ 1000401 _ 0 _ 0 _ 1 _ 0 _ 1000401 _ 1000193 _ 1000292 _ 1 _ 0 _ 1000403 _ 0 _ 0 _ 1 _ 0 _ 1000403 _ 1000347 _ 1000292 _ 1 _ 0 _ 1000405 _ 1000347 _ 0 _ 1 _ 0 _ Deleting a line from the index Output appears. For example: Info : === delete : DELETE ON Threshold ( 1140 1000196 ) (exists) Verifying the deletion Output appears. For example: 174 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

# type = thrd # col = idxmetric idxresource idxgroup mode thrstat # filter = # order = # sep = _ # seprec = 4065 _ 0 _ 0 _ 1 _ 0 _ 1000401 _ 0 _ 0 _ 1 _ 0 _ 1000401 _ 1000193 _ 1000292 _ 1 _ 0 _ 1000403 _ 0 _ 0 _ 1 _ 0 _ 1000405 _ 1000347 _ 0 _ 1 _ 0 _ Importing thresholds The following are examples of importing thresholds. Example 1 Output appears. For example: Info : === insert : INSERT ON Threshold (1000401 1000196 ) (does not exist) Verifying the import Output appears. For example: # type = thrd # col = fgp.nname segp.npath se.name mode thrstat # filter = # order = # sep = _ # seprec = ~FORMULA _ ~NOC Reporting~Network Management~BasicInterface & ExtendedInterface _ 192.168.3.62_<NULL> _ 1 _ 0 _ Example 2 Import without specifying resource or group: Output appears. For example: Info : === insert : INSERT ON Threshold (1000401 1 ) (does not exist) Verifying the import in index form Export of the resource and group in index form. Output appears. For example: # type = thrd # col = idxmetric idxgroup idxresource mode thrstat # filter = # order = # sep = _ # seprec = 1000401 _ 0 _ 0 _ 1 _ 0 _ Chapter 11. Configuring thresholds 175

Verifying the import in name form Export of the resource and group in name form. Output appears. For example: # type = thrd # col = fgp.nname segp.npath se.name mode thrstat # filter = # order = # sep = _ # seprec = ~FORMULA _ _ _ 1 _ 0 _ Import by specifying an empty resource and group alue Output appears. For example: Info : === insert : INSERT ON Threshold (1000402 0 ) (does not exist) Verifying the import Export of the resource and group in index form. Output appears. For example: # type = thrd # col = idxmetric idxgroup idxresource mode thrstat # filter = # order = # sep = _ # seprec = 1000402 _ 0 _ 0 _ 1 _ 0 _ Verifying the import Export of the resource and group in name form Output appears. For example: # type = thrd # col = fgp.nname segp.npath se.name mode thrstat # filter = # order = # sep = _ # seprec = ~FORMULA1 _ _ _ 1 _ 0 _ 176 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Setting thresholds This section explains how to set and erify thresholds against groups and resources. Identifying formula indexes About this task You need to identify the index of the formula to be used as follows: Procedure 1. Enter the following command to export the list of formulas and indexes: resmgr -export frm -colnames "name dbindex" 2. Choose the Generic formula for the metric to which you want to apply the threshold. Thresholds need to be applied to generic formulas because this is the proper database index under which the data will be stored. 3. Identify the index of the group or resource to be used in thresholding. 4. Enter the following command to export the list of subelement groups and indexes (use the -filter option to filter the results of the export). resmgr -export segp -colnames "npath dbindex se.dbindex se.name" 5. Choose a group index that meets the following criteria: a. A calendar and time zone hae been applied at or aboe the group, to the specific subelement, or to the group that a subelement is in. b. The group, resource, or group the specific subelement is in, is one under the reporting tree, or on a branch where reporting is performed. Setting a threshold against a group (dbindex) To set a threshold against a group, enter the following command: resmgr -import thrd -colnames "idxmetric idxgroup mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -line "2210 _ 1001033 _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0" Output appears. For example, if the threshold does not exist in the database: Info : === insert : INSERT ON Threshold ( 2210 0 ) (does not exist) If the threshold does exist in the database: Info : === insert : UPDATE ON Threshold ( 2210 0 ) (exists) Note: prdperiod is mandatory for both burst and period thresholds. Verifying the threshold To erify the threshold you need to export the threshold as follows: resmgr -export thrd -colnames "idxmetric idxgroup mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -filter "idxmetric(2210)" Output appears telling you that the threshold is in the database properly. For example: 2210 _ 1001033 _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0 _ Chapter 11. Configuring thresholds 177

Setting a threshold against a group (name) Enter the following command: resmgr -import thrd -colnames "idxmetric segp.npath mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -line "2210 _ ~NOC Reporting~Network Management~Unknown_Area~All Techs _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0" Output appears. For example, if the threshold does not exist in the database, Info : === insert : INSERT ON Threshold ( 2210 0 ) (does not exist) If the threshold does exist in the database: Info : === insert : UPDATE ON Threshold ( 2210 0 ) (exists) Note: prdperiod is mandatory for both burst and period thresholds. Verifying the threshold To erify the threshold you need to export the threshold: resmgr -export thrd -colnames "idxmetric segp.npath mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -filter "idxmetric(2210)" Output appears if the threshold is in the database properly. For example: 2210 _ ~NOC Reporting~Network Management~Unknown_Area~All Techs _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0 _ Setting a threshold against a resource (dbindex) Enter the following command: resmgr -import thrd -colnames "idxmetric idxresource mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -line "2210 _ 1000660 _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0" Output appears. For example, if the threshold does not exist in the database Info : === insert : INSERT ON Threshold ( 2210 0 ) (does not exist) If the threshold does exist in the database: Info : === insert : UPDATE ON Threshold ( 2210 0 ) (exists) Note: prdperiod is mandatory for both burst and period thresholds. Verifying the Threshold To erify the threshold you need to export the threshold: resmgr -export thrd -colnames "idxmetric idxresource mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -filter "idxmetric(2210)" Output appears. For example: 2210 _ 1000660 _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0 _ 178 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Setting a threshold against a resource (name) Enter the following command: resmgr -import thrd -colnames "idxmetric se.name mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -line "2210 _ zelkona.quallaby.com_interface<1> _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0" Output appears. For example, if the threshold does not exist in the database. Info : === insert : INSERT ON Threshold ( 2210 0 ) (does not exist) If the threshold does exist in the database: Info : === insert : UPDATE ON Threshold ( 2210 0 ) (exists) Note: prdperiod is mandatory for both burst and period thresholds. Verifying the threshold Enter the following command: resmgr -export thrd -colnames "idxmetric se.name mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -filter "idxmetric(2210)"either "su" to the oracle user, or use the $ORACLE_HOME/sqlplus utility. $ORACLEHOME/sqlplus p_admin/<password>@pv(or other instance name)sqlplus> select * from thrsh_desc where idx_metric = 2210 and idx_resource = 1000245 ; Output appears to tell you that the threshold is in the database properly. For example: 2210 _ zelkona.quallaby.com_interface<1> _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0 _ Setting a future threshold This section explains how to set a future threshold. 1. Follow steps 1 to 5 as detailed in the section Setting thresholds on page 177. 2. Specify a future date. For example, if today's date is 7/10/01, then choose 7/11/01 at 12:00 a.m. Conert this date to Epoch numerical time: 994867200. Epoch time is an exact specification of the date and time at which the Keplerian element set is alid. Setting a threshold against a group (dbindex) Enter the following command to import a threshold for a group: Resmgr -import thrd -colnames "idxmetric idxgroup dtedate mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -line "2210 _ 1001033 _ 994867200 _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0" Output appears. For example (if the threshold does not exist in the database): Info : === insert : INSERT ON Threshold ( 2210 0 ) (does not exist) If the threshold does exist: Info : === insert : UPDATE ON Threshold ( 2210 0 ) (exists)if the threshold does exist in the database. Chapter 11. Configuring thresholds 179

Note: prdperiod is mandatory for both burst and period thresholds. Verifying the threshold Verify the threshold by exporting the threshold: Resmgr -export thrd -colnames "idxmetric dtedate idxgroup mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -filter "idxmetric(2210)" Output appears. For example: 2210 _ 1001033 _ 994867200 _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0 _ This means the threshold is in the database properly. You can erify if a future threshold has taken place properly as follows: 1. Set the date of the threshold to a date in the future. 2. Wait for the system time on the CME machine to reach that date for the threshold to be actiated. After the date has been reached, a threshold appears in DataView reports. Time is in Epoch time. Tip: Consider installing an Epoch time conerter on your system. CAUTION: Do not set the system time ahead as it can cause CME conflicts. 3. Check the subelement group or specific sub-elements in the reports after the time has passed to erify that the threshold has taken effect. Setting traps This section explains how to set burst and period traps. Setting burst traps Enter the following command to set a threshold for a metric: resmgr -import thrd -colnames "idxmetric idxgroup mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -line "2210 _ 1001033 _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 1 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 0" In this example, a threshold is set for metric 2210 against the group with the ID of 1001033. The Burst Generate Eent flag has also been set. Note: prdperiod is mandatory for both burst and period thresholds. Verifying the burst trap To erify the burst trap: 1. Log in as root on the serer where the Topology Editor is installed. 2. Set and export your DISPLAY ariable. 3. Change your working directory to the directory where the Topology Editor is installed. For example: # cd /opt/ibm/proiso/topologyeditor 4. Start the Topology Editor using the following command: 180 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

#./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 (. 443) and click Next. 7. Verify that all of the fields for the database connection are filled in with the correct alues: Database hostname -- The name of the database host. The default alue is localhost. Port -- The port number used for communication with the database. The default alue is 1521. Database user -- The username used to access the database. The default alue is p_admin. Database Password -- The password for the database user account. For example, p. SID -- The SID for the database. The default alue is PV. 8. Click Finish. 9. In the Logical View, click the DataChannels folder. 10. Click the DataChanneln component, where n is the appropriate DataChannel number. 11. Click the Complex Metric Engine n.m component, where n.m is the appropriate DataChannel and sub-channel number. 12. In the Properties tab, search for the following parameter: Trap destination=alue 13. Verify that the alue is set to the IP address and port for your snmptrap daemon (for example, Trap destination=192.168.69.30:162). 14. When you are satisfied with your settings, select Topology > Sae topology to sae the topology. 15. Select Run > Run Installer and pass it the newly configured topology. 16. After the updated configuration has been stored in the database, you must restart the CME serer as explained in Restarting the Complex Metric Engine (CME). Restarting the Complex Metric Engine (CME) When the topology is modified, you need to restart the CME for the changes to take effect. About this task To restart the CME, do the following: Procedure 1. Change to the Data Channel home directory. For example, /opt/datachannel. 2. Enter the following command to change to the bin directory: cd bin 3. Run the following command (for example, channel 1). For a different channel, change the channel number. dccmd -action stop -channel 1 -application cme 4. Run the following command to start the CME for channel 1: dccmd -action start -channel 1 -application cme 5. Ensure that the CME is running: Chapter 11. Configuring thresholds 181

dccmd -action status -channel 1 -application cme Note: You can also use the ddcmd command with the bounce argument to stop and start the CME, as follows: dccmd -action bounce -channel 1 -application cme. Additionally, you can use a shorter ersion of the ddcmd command, as follows: dccmd bounce cme.1 For more information on using the dccmd command, inoke the dccmd command with the -usage option. Setting period traps Enter the following command to set a threshold for a metric: Resmgr -import thrd -colnames "idxmetric idxgroup mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -line "2210 _ 1001033 _ 2 _ 0 _ 0 _ 1000000 _ 2000000 _ 1000000 _ 0 _ 0 _ 0 _ 2000 _ 1000 _ 900 _ 900 _ 1 _ 1" The threshold is set for metric 2210 against the group with the ID of 1001033. The Period Generate Eent flag has also been set. Note: prdperiod is mandatory for both burst and period thresholds. Verifying the period trap Follow the steps in the sections entitled Restarting the Complex Metric Engine (CME) on page 181. Threshold troubleshooting scenarios This section describes different threshold troubleshooting scenarios. Export scenario 1 Export a threshold configured against mid (metric identifier) and gid (group identifier) and display metrics and group IDs (not name) - NO HISTORY (last alues) resmgr -export thrd -colnames "idxmetric idxgroup mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent" ype = thrd col = idxmetric idxgroup mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent # filter = # order = # sep = _ # seprec = 2201 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2201 _ 1004214 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2202 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2202 _ 1004214 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2203 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2203 _ 1004214 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2204 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2205 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2206 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2206 _ 1004214 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2207 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 182 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

2207 _ 1004214 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2225 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2226 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2228 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2229 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2240 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2241 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2242 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2243 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2246 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2247 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2250 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2251 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ 2255 _ 663 _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ Export scenario 2 Export a threshold configured against mid (metric identifier) and gid (group identifier) and display metric and group name (not IDs) - NO HISTORY (last alues) resmgr -export thrd -colnames "fgp.nname segp.npath mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent" # type = thrd # col = fgp.nname segp.npath mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent # filter = # order = # sep = _ # seprec = ~AP~PROVISO~Targets~SNMP Aailability (percent) (ag last hour) _ ~NOC Reporting _ 1 _ 3 _ 0 _ _ 75 _ _ _ _ _ ~AP~PROVISO~Targets~SNMP Response Time (ms) (ag last hour) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 5000 _ _ _ _ _ ~AP~Generic~Frame Relay~Outbound CIR Utilization (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Frame Relay~Inbound CIR Utilization (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Frame Relay~Outbound Discard Eligible (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Frame Relay~Inbound Discard Eligible (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Outbound Queue Drops (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Inbound Queue Drops (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Resets _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Restarts _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Buffer Utilization (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~CPU Utilization (percent) (ag last 5 minutes) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Outbound Utilization (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Inbound Utilization (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Outbound Loss (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Inbound Loss (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~IP~IP Fragmentation (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ Chapter 11. Configuring thresholds 183

Export scenario 3 Export a threshold configured against mid (metric identifier) and gid (group identifier) and display metric and group name (not IDs) - Filter on formula - NO HISTORY (last alues) resmgr -export thrd -colnames "fgp.nname segp.npath mode thrstat thrcalc thrcalcvalue" -filter "fgp.nname(*aailability*)" # type = thrd # col = fgp.nname segp.npath mode thrstat thrcalc thrcalcvalue # filter = fgp.nname(*aailability*) # order = # sep = _ # seprec = ~AP~PROVISO~Targets~SNMP Aailability (percent) (ag last hour) _ ~NOC Reporting _ 1 _ 3 _ 0 _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 2 _ 3 _ 0 _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 2 _ 3 _ 0 _ _ Export scenario 4 In this scenario, you can troubleshoot an issue related to threshold detection. For example, thresholds might be correctly detected on the 17th of the month, but they might not be detected on the 18th. Export a threshold configured against mid(metric identifier) and gid(group identifier) and display metric and group name (not Ids). Filter on formula Aailability - WITH HISTORY (thrdh instead of thrd) and ACTION resmgr -export thrdh -colnames "fgp.nname segp.npath dte_date action mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent" -filter "fgp.nname(*aailability*)" # type = thrdh # col = fgp.nname segp.npath dte_date action mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtclti # filter = fgp.nname(*aailability*) # order = # sep = _ # seprec = ~AP~PROVISO~Targets~SNMP Aailability (percent) (ag last hour) _ ~NOC Reporting _ 09/19/2001 01:08 _ I _ 1 _ 3 _ 0 _ _ 75 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 65 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 10 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 09/08/2001 00:45 _ I _ 1 _ 0 _ 0 _ 0 _ 90 _ 95 _ 900 _ 1800 _ 0 _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 65 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 10 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 09/08/2001 00:36 _ I _ 1 _ 0 _ 0 _ 0 _ 90 _ 95 _ 900 _ 1800 _ 0 _ The threshold on "Aailability (percent)" has been created on 09/08/2001 00:45 with correct alues and has been oerwritten with inaild alues at a later date (09/19/2001 01:08). The result is that Tioli Netcool Performance Manager DataView will now be generating reports without the threshold iolation. 184 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

The difference in dates is because of GMT time (09/19/2001 01:08), which is actually on the 18th in the eening. Date and Action (U=update - I=Insert) let you understand the history of actions that happened to the thresholds and troubleshoot report problems. To correct the issue in the future (no re-computation of the preious days) resmgr -import thrd -colnames "idxmetric idxgroup mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent prdcrtclleel prdwrnngleel prdcrtcltime prdwrnngtime prdperiod prdgeneent" -line "2203 _ 1004214 _ 1 _ 0 _ 0 _ 0 _ 90 _ 95 _ 900 _ 1800 _ 0 _ 90 _ 95 _ 3600 _ 7200 _ 1 _ 0" Info : === insert : UPDATE ON Threshold ( 2203 0 ) (exists) To erify the recreation of the thresholds is correctly updated resmgr -export thrdh -colnames "fgp.nname segp.npath dte_date action mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent" -filter "fgp.nname(*aailability*)" # type = thrdh # col = fgp.nname segp.npath dte_date action mode thrstat thrcalc thrcalcvalue brstcrtclleel brstwrnngleel brstcrtcltime brstwrnngtime brstgeneent # filter = fgp.nname(*aailability*) # order = # sep = _ # seprec = ~AP~PROVISO~Targets~SNMP Aailability (percent) (ag last hour) _ ~NOC Reporting _ 09/19/2001 01:08 _ I _ 1 _ 3 _ 0 _ _ 75 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 09/25/2001 20:44 _ U _ 1 _ 0 _ 0 _ 0 _ 90 _ 95 _ 900 _ 1800 _ 0 _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 65 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 10 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~NOC Reporting _ 09/08/2001 00:45 _ I _ 1 _ 0 _ 0 _ 0 _ 90 _ 95 _ 900 _ 1800 _ 0 _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 09/25/2001 20:41 _ U _ 1 _ 0 _ 0 _ 0 _ 90 _ 95 _ 900 _ 1800 _ 0 _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 2 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 65 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 09/19/2001 01:08 _ U _ 2 _ 3 _ 0 _ _ 10 _ _ _ _ _ ~AP~Generic~Uniersal~Aailability (percent) _ ~Customer Facing Reporting _ 09/08/2001 00:36 _ I _ 1 _ 0 _ 0 _ 0 _ 90 _ 95 _ 900 _ 1800 _ 0 _ Chapter 11. Configuring thresholds 185

186 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Chapter 12. Configuring timezones Working with timezones Explains how to use resmgr to configure timezones, Timezones are Tioli Netcool Performance Manager object types that belong to the Design category. Before using the commands in this chapter, reiew the information in Chapter 4, Managing Tioli Netcool Performance Manager objects, on page 15. Additional resmgr commands for managing thresholds can be found in Working with timezones of Chapter 7, Managing design objects, on page 111. This section explains how to use resmgr to create, modify, or delete time zone definitions. Tioli Netcool Performance Manager displays times in customer-specific time zones because serice proiders often hae customer bases that span multiple time zones. Summary statistics are maintained in periods greater than the span of a time zone (typically one hour); therefore, the CME maintains summary statistics relatie to different time zones. You can attach a timezone to a group and it is associated with all groups and resources below it. Because resources can exist in multiple groups, you can create different time zone iews of the same sets of resources by defining multiple groups with different time zone settings. This approach minimizes the amount of duplicate timezone processing that CME performs and the amount of redundant data that is loaded and retained in the database. Exporting timezones This section explains how to export time zones. Example Output appears. For example: # type = tzc # col = tzdbindex tzname tzoffset tzcomment tzstatus tzdate # filter = # order = # sep = _ # seprec = ~NOC Reporting~ _ My Calendar _ GMT _ Copyright IBM Corp. 1997, 2012 187

Deleting timezones This section explains how to delete time zones. Example resmgr -delete tz -colnames "dbindex nop nop nop nop date" -file /tmp/temporary Output appears. For example: Info : === delete : DELETE ON Time Zones (1)(exists) Info : === delete : DELETE ON Time Zones (2)(exists) Info : === delete : DELETE ON Time Zones (3)(exists) Info : === delete : DELETE ON Time Zones (4)(exists) Info : === delete : DELETE ON Time Zones (5)(exists) Info : === delete : DELETE ON Time Zones (6)(exists) Info : === delete : DELETE ON Time Zones (1)(exists) Info : === delete : DELETE ON Time Zones (2)(exists) Verifying the deletion resmgr -export tz -colnames "dbindex name offset comment status date" -file /tmp/temporary Output appears. For example: #type=tz # col = dbindex name offset comment status date # filter = # order = # sep = _ # seprec = Note: To delete a timezone associated with a calendar or group of subelements, remoe all the links between the timezone and the groups. When you remoe the links, no statistics are produced for the groups. Importing, modifying, and creating timezones This section explains how to import, modify, and create time zones. Example resmgr -import tz -colnames "dbindex name offset comment status date" -file /tmp/temporary Output appears. For example: Info : === insert : INSERT ON Time Zones (1)(does not exist) Info : === insert : INSERT ON Time Zones (2)(does not exist) Info : === insert : INSERT ON Time Zones (3)(does not exist) Info : === insert : INSERT ON Time Zones (4)(does not exist) Info : === insert : INSERT ON Time Zones (5)(does not exist) Info : === insert : INSERT ON Time Zones (6)(does not exist) Info : === insert : INSERT ON Time Zones (1)(does not exist) Info : === insert : INSERT ON Time Zones (2)(does not exist) Verifying the import resmgr -export tz -colnames "dbindex name offset comment status date" -file /tmp/temporary Output appears. For example: 188 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

#type=tz # col = dbindex name offset comment status date # filter = # order = # sep = _ # seprec = 1 _ AggSet 1 _ 10800 _ AggSet 1 (+3) _ 0 _ 983464852 _ 2 _ AggSet 2 _ 10800 _ AggSet 2 (+3) _ 0 _ 983464853 _ 3 _ AggSet 3 _ 36000 _ AggSet 3 (+10) _ 0 _ 983464851 _ 4 _ AggSet 4 _ 18000 _ AggSet 4 (+5) _ 0 _ 983464851 _ 5 _ AggSet 5 _ -25200 _ AggSet 5 (-7) _ 0 _ 983464851 _ 6 _ AggSet 6 _ 14400 _ AggSet 6 (+4) _ 0 _ 983464851 _ 1 _ AggSet 1 _ 3600 _ AggSet 1 (+1) _ 0 _ 983464851 _ 2 _ AggSet 2 _ 10800 _ AggSet 2 (+3) _ 0 _ 983464851 _ Grouping links of subelements, calendars, and timezones This section explains how to create, modify, or delete links between groups of subelements, calendars, and timezones. Exporting links Example Output appears. For example: Deleting links Example When you execute the following command, you delete all the links between a group and a timezone. Ensure you want to do so, before entering the command. Output appears. For example: Chapter 12. Configuring timezones 189

Info : === delete : DELETE ON Sub_Element Groups ( abak static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( abak static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( abak static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( abak static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( abak static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( abak static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( 192.168.3.191 static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( 192.168.3.252 static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( 192.168.3.252 static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( 192.168.3.62 static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Info : === delete : DELETE ON Sub_Element Groups ( 192.168.3.62 static ) (exists) Info : === delete : nothing ON Link SEGP/TZ (does not exist) Verifying the deletion If a calendar or timezone is already defined at an upper branch for a gien group, Tioli Netcool Performance Manager returns an error indicating a calendar or timezone cannot be created for this group. resmgr -nox -export tz -colnames "cliparent sename setype clichild_tz name tzclichild_cal calname clistate clitype cliorigin cliuser clidate" -file /tmp/eriflinks.dat Output appears. For example: #type=tz # col = cliparent sename setype clichild_tz name clichild_cal calname clistate tzclitype cliorigin cliuser clidate # filter = # order = # sep = _ # seprec = Importing, modifying or creating links Example esmgr -nox -import tz -colnames "cliparent sename setype clichild_tz name clichild_cal calname clistate clitype cliorigin cliuser clidate" -file /tmp/linksegrp_calendars_timezones.dat Output appears. For example: 190 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Info : === insert : nothing ON Calendars ( Day Calendar ) (exists) Info : === insert : INSERT ON Sub_Element Groups ( abak static ) (does not exist) Info : === insert : INSERT ON Link SEGP/TZ (does not exist) Info : === insert : nothing ON Calendars ( Night Calendar ) (exists) Info : === insert : nothing ON Sub_Element Groups ( abak static ) (exists) Info : === insert : INSERT ON Link SEGP/TZ (does not exist) Info : === insert : nothing ON Calendars ( Permanent, each hour ) (exists) Info : === insert : INSERT ON Sub_Element Groups ( 192.168.3.191 static ) (does not exist) Info : === insert : INSERT ON Link SEGP/TZ (does not exist) Info : === insert : nothing ON Calendars ( Working days, each quarter ) (exists) Info : === insert : INSERT ON Sub_Element Groups ( 192.168.3.252 static ) (does not exist) Info : === insert : INSERT ON Link SEGP/TZ (does not exist) Info : === insert : nothing ON Calendars ( Working days, each quarter ) (exists) Info : === insert : nothing ON Sub_Element Groups ( 192.168.3.252 static ) (exists) Info : === insert : INSERT ON Link SEGP/TZ (does not exist) Info : === insert : nothing ON Calendars ( Permanent, each quarter ) (exists) Info : === insert : INSERT ON Sub_Element Groups ( 192.168.3.62 static ) (does not exist) Info : === insert : INSERT ON Link SEGP/TZ (does not exist) Info : === insert : nothing ON Calendars ( Permanent, each hour ) (exists) Info : === insert : nothing ON Sub_Element Groups ( abak static ) (exists) Info : === insert : INSERT ON Link SEGP/TZ (does not exist) Info : === insert : nothing ON Calendars ( Permanent, each hour ) (exists) Info : === insert : nothing ON Sub_Element Groups ( abak static ) (exists) Info : === insert : INSERT ON Link SEGP/TZ (does not exist) Info : === insert : nothing ON Calendars ( Permanent, each quarter ) (exists) Info : === insert : nothing ON Sub_Element Groups ( 192.168.3.62 static ) (exists) Info : === insert : INSERT ON Link SEGP/TZ (does not exist) Note: When the calendar or the sub-elements group, or the time zone associated with a link does not exist in the database, the import of this link fails. Verifying the import resmgr -nox -export tz -colnames "cliparent sename setype clichild_tz name clichild_cal calname clistate clitype cliorigin tzcliuser clidate" -file /tmp/eriflinks.dat Output appears. For example: #type=tz # col = cliparent tzsename setype clichild_tz tzname clichild_cal calname clistate clitype cliorigin cliuser clidate # filter = # order = # sep = _ # seprec = 1000321 _ abak _ static _ 2 _ AggSet 2 _ 1000101 _ Day Calendar _ on _ static _ impexp _ abak _ 983902406 _ 1000321 _ abak _ static _ 2 _ AggSet 2 _ 1000101 _ Day Calendar _ on _ static _ impexp _ abak _ 983902406 _ 1000321 _ abak _ static _ 2 _ AggSet 2 _ 1000102 _ Night Calendar _ of _ static _ impexp _ abak _ 983902406 _ 1000321 _ abak _ static _ 2 _ AggSet 2 _ 1000102 _ Night Calendar _ of _ static _ impexp _ abak _ 983902406 _ 1000321 _ abak _ static _ 3 _ AggSet 3 _ 1000103 _ Permanent, each hour _ on _ static _ impexp _ abak _ 983902406 _ 1000321 _ abak _ static _ 5 _ AggSet 5 _ 1000103 _ Permanent, each hour _ on _ static _ impexp _ abak _ 983902406 _ 1000322 _ 192.168.3.191 _ static _ 3 _ AggSet 3 _ 1000103 _ Permanent, each hour _ on _ static _ impexp _ abak _ 983902406 _ 1000323 _ 192.168.3.252 _ static _ 4 _ AggSet 4 _ 1000108 _ Working days, each quarter _ on _ static _ impexp _ abak _ 983902406 _ 1000323 _ 192.168.3.252 _ static _ 5 _ AggSet 5 _ 1000108 _ Working days, each quarter _ on _ static _ impexp _ abak _ 983902406 _ 1000324 _ 192.168.3.62 _ static _ 5 _ AggSet 5 _ 1000104 _ Permanent, each quarter _ on _ static _ impexp _ abak _ 983902406 _ 1000324 _ 192.168.3.62 _ static _ 6 _ AggSet 6 _ 1000104 _ Permanent, each quarter _ on _ static _ impexp _ abak _ 983902406 _ Chapter 12. Configuring timezones 191

192 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Appendix A. Supported resmgr options The following table lists in alphabetical order. all of the options you can use with the resmgr command. It includes a brief description of each option, with which object type it is used, and whether you can use it with the import and export commands. Option Definition Use with Object Type Import Export agp group of application Y Y reporters app reporter application Y Y apph reporter history history table Y Y apps reporter application Y Y stylesheet cal Calendar calendar Y Y calh Calendar history history table Y Y chnl channel element N Y client dbi DesignIndex registration information about Tioli Netcool Performance Manager clients export Tioli Netcool Performance Manager GUI information into CSV format sequence of indexes used for Tioli Netcool Performance Manager Design objects such as formulas, reporters, propterties and so on. others Y others Y Y others Y Y sequences Y Y egp element group group Y Y egph element group history table Y Y history elt element element Y Y elth element history history table Y Y encl nomclature element Y Y eprp element property element Y Y Y Copyright IBM Corp. 1997, 2012 193

Option err Definition Use with Object Type Import Export list of Oracle others Y Y errors tracked by Tioli Netcool Performance Manager fam family subelement Y Y fgp formula group formula Y Y frm formula formula Y Y frmh formula history history table Y Y linkgroupapp link between group and reporter application Y N linkgroupapps linkgroupe linkgroupf linkgroupn linkgroupru linkgroupse link between group and reporters; group and style sheets link between group of elements and element link between the group and the formula link between the group and the nomenclature link between group and the report (Web) user link between group of subelements and subelement linkgroupse_app link between group of subelements and report linkgroupse_ru link between group of subelements and report user linkgroupse_tcz link between group of subelements and timezone and Calendar application Y N group Y N formula Y N nomenclature Y N web user Y N group Y N group Y N group Y N group Y Y mib MIB formula Y Y ncl nomenclature nomenclature Y Y 194 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Option ngp ogp ogpt Definition nomenclature group group of inentory profiles option of the inentory profile. Use with ogp alue, Use with Object Type Import Export nomenclature Y Y inentory profile Y Y inentory profile Y Y orausr list of Oracle others Y Y users pctile percentile request Y Y pkg all package others Y Y tables propertye property of property Y Y element propertyru property of property Y Y report user propertyse property of property Y Y subelement reg information about component that are running (similar to pmstart) others Y Y regdesc reginst regisdb regisdc regisdcconfig regisdm list of all registries instances of all registries Tioli Netcool Performance Manager database registry Tioli Netcool Performance Manager DataChannel registry Tioli Netcool Performance Manager DataChannel registry configuration Tioli Netcool Performance Manager DataMart registry registry N Y registry N Y registry Y Y registry Y Y registry Y Y registry Y Y Appendix A. Supported resmgr options 195

Option regismg ResourcesIndex Definition Use with Object Type Import Export Tioli Netcool registry Y Y Performance Manager DataChannel Manager registry sequence of indexes used for resources (elements, subelements, and groups) sequences Y Y rugp report (Web) web user Y Y user group ruprp report (Web) web user Y Y user property rusr report (Web) use web user Y Y scf SNMP element Y Y configuration sched Scheduler scheduler Y Y se subelement subelement Y Y segp subelement group Y Y group segph subelement history table Y Y group history segpreq request on subelement group request Y Y segpreqh seh seproperty seprp thrd thrdh subelement group request history subelement history subelement property description subelement property threshold definition threshold definition history history table Y Y history table Y Y subelement Y N subelement Y Y threshold Y Y history table Y Y tz timezone timezone Y Y usr Tioli Netcool Performance Manager DataMart user DM user Y Y endor endor nomenclature Y Y 196 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Appendix B. Working with SAA probes The following commands allow you to work with SAA probes. For a description of supported arguments to these commands, see Argument descriptions for SAA probe operations on page 198. For a list of SAA Probe properties, see Properties used by the Tioli Netcool Performance Manager-enabled SAA probes on page 119. Exporting or importing an SAA probe Configuration table resmgr [-export -import] probe -colnames "dbindex inariant se.name user origin date pprop.name pprop.alue" History table resmgr [-export -import] probeh -colnames "dbindex inariant se.name pprop.name pprop.alue" Exporting or importing an SAA probe with types Configuration table resmgr [-export -import] probe -colnames "dbindex inariant se.name user origin date probetype descriptiontype inariantdeftype classtype datetype origintype usertype" History table resmgr [-export -import] probeh -colnames "dbindex inariant date origin user probetype descriptiontype inariantdeftype classtype datetype origintype usertype" Exporting or importing SAA probe attributes Configuration table resmgr [-export -import] pprop -colnames "dbindex name snmpdisplayflag snmpcreateflag snmppersistflag snmpcontrolflag mib defaultvalue allowedvalues order mandatory date origin user snmptype probetype descriptiontype inariantdeftype classtype datetype origintype usertype" History table resmgr [-export -import] pproph -colnames "dbindex name snmpdisplayflag snmpcreateflag snmppersistflag snmpcontrolflag mib defaultvalue allowedvalues order mandatory date origin user snmptype probetype descriptiontype inariantdeftype classtype datetype origintype usertype" Copyright IBM Corp. 1997, 2012 197

Deleting SAA probes The safest means to delete SAA probes is by database index. For probe type definitions, the database index field name is dbindextype. Importing a probe resmgr -import probe -colnames "probetype classtype" -line "probea _ classa _ " Info : === insert : INSERT ON probe probetype ( probea ) (does not exist) Exporting a probe resmgr -nohead -export probe -colnames "dbindextype probetype classtype" -filter "probetype(probea)" 100006468 _ probea _ classa _ Deleting a probe by type and class resmgr -delete probetype -colnames "probetype classtype" -line "probea _ classa _ " Info : === delete : DELETE ON probe probetype ( probea ) (exists) Deleting a probe by database index resmgr -delete probetype -colnames "dbindextype" -line "100006469 _ " Info : === delete : DELETE ON probe probetype ( probea ) (exists) Deleting an instance of a probe deployed against a subelement resmgr -delete probe -colnames "dbindex" -line "1234567890" Deleting a Probe resmgr -delete probe -colnames "name" Deleting a Type resmgr -delete probe -colnames "type" Deleting an Attribute resmgr -delete pprop -colnames "name" Deleting an Attribute Value resmgr -delete ppropalue -colnames "inariant se.name pprop.name" Argument descriptions for SAA probe operations Argument allowedvalues classtype date datetype dbindex defaultvalue descriptiontype inariant inariantdeftype inarianttype Description Enables data checking in the DataView portal. The class of the SAA probe type. The timestamp of the SAA probe. The timestamp of the SAA probe, The database index. Specifies a default alue to use when there is no alue. Description of the type of SAA probe. A string that uniquely identifies the SAA probe. The definition of the probe type inariant. The inariant definition for the SAA probe type. 198 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Argument mandatory mib name order origin origintype pprop.name pprop.alue probetype se.name snmpcontrolgflag snmpcreateflag snmpdisplayflag snmppersistflag snmptype user usertype Description Indicates if the alue for the attribute is required. Can be either 1 (TRUE) or 0 (FALSE). The MIB in which the attribute is defined. The name of the attribute. The order of the attribute within the type. The name of the program performing the change. The program performing the change. The SAA probe attribute name. The SAA probe attribute alue. The name of the type of SAA probe (jitter or echo). The ID of the sub-element router. Indicates if the attribute is an SNMP OID used for control. Can be either 1 (TRUE) or 0 (FALSE). Indicates if the attribute is an SNMP OID used for creating. Can be either 1 (TRUE) or 0 (FALSE). Indicates if the attribute is an SNMP OID used for display. Can be either 1 (TRUE) or 0 (FALSE). Indicates if the attribute is an SNMP OID used for persistance. Can be either 1 (TRUE) or 0 (FALSE). Specifies the type of SNMP data. Can be one of the following: CNT C64 GGE INT IP MAC OCT OID STR TIM The name of the user performing the change. The user performing the change. Appendix B. Working with SAA probes 199

Listing subelement groups without resources resmgr -export segp -colnames "dbindex name segchild.name se.name" -ismandat "" -filter "segchild.name(is null) se.name(is null) type(generated)" -file $DIR/Usage_emptyGrp.dat # type = segp # col = dbindex name segchild.name se.name # filter = segchild.name(is null) se.name(is null) type(generated) # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "dbindex name segchild.name se.name" -filter "segchild.name(is null) se.name(is null) type(generated)" 200000049 _ test alue2 _ _ _ 100001001 _ Dener _ _ _ 100010002 _ 172.17.100.254 _ _ _ 100001078 _ Dallas _ _ _ 100000990 _ Houston _ _ _ 200000153 _ test alue2 _ _ _ 100000993 _ New York _ _ _ 200000117 _ test alue5 _ _ _ 200000065 _ test alue2 _ _ _ 100001052 _ Dallas _ _ _ 200000731 _ "LEs Ulis" _ _ _ 100001059 _ San Francisco _ _ _ 200000140 _ test alue2 _ _ _ 100002072 _ Gold _ _ _ 100001833 _ Remote Branch _ _ _ 100001779 _ Undefined priate network ID _ _ _ 200000187 _ test alue2 _ _ _ Finding and fixing nomenclature Listing deices not assigned to a nomenclature group resmgr -export elt -colnames "name profil encl.oid encl.name" -filterrule "%(encl.gpname) IS NULL and %(elt.type) = snmp and %(elt.state) = on and %(elt.origin) = inentory " -file $DIR/Usage_enclList.dat # type = elt # col = name profil encl.oid encl.name # filter = # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name profil encl.oid encl.name" 192.168.127.254 _ Cisco_SAA _ 1.3.6.1.4.1.9.1.258 _ Cisco Internetwork Operating System Software \nios (tm) MSFC Software (C6MSFC-I _ NF-site-site-flow-BestEffort-CoffeeBucks _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-site-flow-Bronze-CoffeeBucks _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-iphost-flow-Bronze-CoffeeBucks _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-iphost-site-flow-BestEffort-CoffeeBucks _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-iphost-flow-BestEffort-CoffeeBucks _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-iphost-site-flow-Bronze-CoffeeBucks _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-Bronze-CoffeeBucks _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-BestEffort-CoffeeBucks _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-site-flow-Gold-SpecificElectric _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-iphost-flow-SpecificElectric _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-iphost-flow-MarcDonuts _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-as-as-flow-SpecificElectric _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-iphost-flow-Gold-SpecificElectric _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-as-as-flow-MarcDonuts _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-Gold-SpecificElectric _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-NexxonOil _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-iphost-site-flow-Siler-MarcDonuts _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-as-as-flow-NexxonOil _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ SpecificElectric-192.168.1.6 _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ 200 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

NF-site-site-flow-MarcDonuts _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-as-flow-MarcDonuts _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-iphost-site-flow-SpecificElectric _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-iphost-site-flow-MarcDonuts _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ NF-site-as-flow-FearedMotors _ bulk_2 _ 1.3.6.1.4.1.2929 _ MLARS _ Correctly classifying a Tioli Netcool Performance Manager object resmgr -import ngp -colnames "npath ncl.name ncl.type(sysobjectid)" -line "~NodesType~Router~Cisco _ Cisco C7100-IS _ " Check the output for errors. If there is a major error, such as a corrupt file, it is reported on the last line of the output. Filtering subelements using the underscore (_) resmgr -export se -colnames "name" -filterrule "%(name) LIKE %@_protocol% ESCAPE @ " -file $DIR/Usage_filter_.dat If the command is successful, no output is displayed. Cutting and pasting in subelement group You add a subelement group by using the Tioli Netcool Performance Manager DataMart GUI. Finding the subelement group index # ~DBER~al3 ==> ~DBER~al2~al3 resmgr -export segp -colnames "npath dbindex segparent.dbindex" -filter "npath(~dber~al3)" -file $DIR/ # ==> "~DBER~al3 _ 200003365 _ 20000091" resmgr -export segp -colnames "npath dbindex" -filter "npath(~dber~al2)" -file $DIR/ ==> "~DBER~al2 _ 200003366 _ Cutting the subelement group resmgr -delete linkgroupsegp -colnames "nop lgchild lgparent" -line "~DBER~al3 _ 200003365 _ 20000091" Pasting the subelement group resmgr -import linkgroupsegp -colnames "nop lgchild lgparent" -line "~DBER~al3 _ 200003365 _ 200003366" Appendix B. Working with SAA probes 201

Finding subelement groups without a parent Note: (Only root can be used in this case) resmgr -export segp -colnames "segparent.dbindex dbindex name" -filter "segparent.dbindex(is null)" -file $DIR/Usage.GrpWithNoParent.dat # type = segp # col = segparent.dbindex dbindex name # filter = segparent.dbindex(is null) # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "segparent.dbindex dbindex name" -filter "segparent.dbindex(is null)" _ 7699 _ IP VPN _ _ 3 _ ROOTROOT _ Finding subelement groups with more than one parent Note: You use this command for debugging purposes. A group cannot hae more than one parent. If you find any groups using this command, you need to correct the problem. resmgr -export segp -colnames "segparent.dbindex_count dbindex name" -file $DIR/Usage.GrpParent.dat # type = segp # col = segparent.dbindex_count dbindex name # filter = # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "segparent.dbindex_count dbindex name" 0 _ 3 _ ROOTROOT _ 1 _ 663 _ NOC Reporting _ 1 _ 677 _ Sub-Element Collect _ 1 _ 4185 _ IPSec _ 1 _ 4186 _ Phase-1 _ 1 _ 4187 _ Phase-2 _ 1 _ 4188 _ %(customer) _ 1 _ 4189 _ %(customer) _ 1 _ 4190 _ IPSec _ 1 _ 4191 _ Cisco _ 1 _ 4192 _ %(priatenetworkid) _ 1 _ 4193 _ %(priatenetworkid) _ 1 _ 4300 _ Frame Relay _ 1 _ 4301 _ DLC _ 1 _ 4302 _ Cascade (Lucent) _ 1 _ 4303 _ Cisco 11.2F+ _ 1 _ 4304 _ Frame Relay _ 1 _ 4305 _ DLC _ 1 _ 4306 _ Router _ 1 _ 4307 _ Deices _ 1 _ 4308 _ Cisco 11.x _ 1 _ 4309 _ Router _ 1 _ 4310 _ Interfaces _ 1 _ 4311 _ Location: %(location) _ 1 _ 4312 _ Deices _ 1 _ 4313 _ Location: %(location) _ 1 _ 4314 _ Interfaces _ 1 _ 4315 _ Cisco 11.x _ 1 _ 4316 _ %(Element.NAME) _ 202 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Finding number of child groups for a subelement group resmgr -export segp -colnames "lgchild_count dbindex name" -file $DIR/Usage_childNumber.dat # type = segp # col = lgchild_count dbindex name # filter = # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "lgchild_count dbindex name" 5 _ 3 _ ROOTROOT _ 16 _ 663 _ NOC Reporting _ 19 _ 677 _ Sub-Element Collect _ 2 _ 4185 _ IPSec _ 2 _ 4186 _ Phase-1 _ 2 _ 4187 _ Phase-2 _ 1 _ 4188 _ %(customer) _ 1 _ 4189 _ %(customer) _ 1 _ 4190 _ IPSec _ 1 _ 4300 _ Frame Relay _ 4 _ 4301 _ DLC _ 1 _ 4304 _ Frame Relay _ 4 _ 4305 _ DLC _ 6 _ 4306 _ Router _ 2 _ 4307 _ Deices _ 8 _ 4309 _ Router _ 11 _ 4310 _ Interfaces _ 1 _ 4311 _ Location: %(location) _ 10 _ 4312 _ Deices _ 2 _ 4314 _ Interfaces _ 2 _ 4315 _ Cisco 11.x _ 3 _ 4317 _ All Technologies _ 8 _ 4318 _ Deices _ 3 _ 4322 _ MIB-II _ 6 _ 4323 _ High Speed Interfaces (>=100Mbps) _ 13 _ 4325 _ Low Speed Interfaces (<100Mbps) _ 8 _ 4327 _ Deices _ 6 _ 4329 _ High Speed Interfaces (>=100Mbps) _ 13 _ 4331 _ Low Speed Interfaces (<100Mbps) _ 3 _ 4750 _ Per Operation (raw) _ Checking subelement group request history tables resmgr -export segpreqh -colnames "fgp.nname segp.npath period dbindex dte action dte_date" -file $DIR/Usage_segpreqH.dat # type = segpreqh # col = fgp.nname segp.npath period dbindex dte action dte_date # filter = # order = # sep = _ # seprec = # # cmdline = -export segpreqh -colnames "fgp.nname segp.npath period dbindex dte action dte_date" ~AP~Specific~SNMP~Router~Cisco 11.x~Deice~Buffer Utilization (percent) Cisco 11.x Router Deice _ ~Sub-Element Collect~Router~Deices~Cisco 11.x _ 900 _ 100001354 _ 1065103662 _ U _ 10/02/2003 18:07 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Deice~Buffer Utilization (percent) Cisco 11.x Router Deice _ ~Sub-Element Collect~Router~Deices~Cisco 11.x _ 900 _ 100001354 _ 1018459127 _ I _ 04/10/2002 21:18 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Deice~CPU Utilization (percent) (ag last 5 minutes) Cisco 11.x Router Deice _ ~Sub-Element Collect~Router~ Deices~Cisco 11.x _ 900 _ 100001353 _ 1065103662 _ U _ 10/02/2003 18:07 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Deice~CPU Utilization (percent) (ag last 5 minutes) Cisco 11.x Router Deice _ ~Sub-Element Collect~Router~Deices~ Cisco 11.x _ 900 _ 100001353 _ 1018459127 _ I _ 04/10/2002 21:18 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~ Cisco 11.x _ 900 _ 100001360 _ 1065103662 _ U _ 10/02/2003 18:07 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~ Cisco 11.x _ 900 _ 100001360 _ 1018459127 _ I _ 04/10/2002 21:18 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~ Appendix B. Working with SAA probes 203

Cisco 11.x _ 900 _ 100001359 _ 1065103662 _ U _ 10/02/2003 18:07 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~ Cisco 11.x _ 900 _ 100001359 _ 1018459127 _ I _ 04/10/2002 21:18 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~ Cisco 11.x _ 900 _ 100001358 _ 1065103662 _ U _ 10/02/2003 18:07 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~ Cisco 11.x _ 900 _ 100001358 _ 1018459127 _ I _ 04/10/2002 21:18 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~ Cisco 11.x _ 900 _ 100001357 _ 1065103662 _ U _ 10/02/2003 18:07 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~ Cisco 11.x _ 900 _ 100001357 _ 1018459127 _ I _ 04/10/2002 21:18 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Resets Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ 900 _ 100001356 _ 1065103662 _ U _ 10/02/2003 18:07 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Resets Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ 900 _ 100001356 _ 1018459127 _ I _ 04/10/2002 21:18 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Restarts Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ 900 _ 100001355 _ 1065103662 _ U _ 10/02/2003 18:07 _ ~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Restarts Cisco 11.x Router RFC-1213 Interface _ ~Sub-Element Collect~Router~Interfaces~Cisco 11.x _ 900 _ 100001355 _ 1018459127 _ I _ 04/10/2002 21:18 _ ~Demo~Addressess Free _ ~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps) _ 900 _ 100009867 _ 1065103663 _ U _ 10/02/2003 18:07 _ ~Demo~Addressess Free _ ~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps) _ 900 _ 100009867 _ 1050704504 _ I _ 04/19/2003 02:21 _ ~Demo~Address Pool Utilization (percent) _ ~Sub-Element Collect~MIB-II~ High Speed Interfaces (>=100Mbps) _ 900 _ 100009866 _ 1065103663 _ U _ 10/02/2003 18:07 _ ~Demo~Address Pool Utilization (percent) _ ~Sub-Element Collect~MIB-II~ High Speed Interfaces (>=100Mbps) _ 900 _ 100009866 _ 1050704504 _ I _ 04/19/2003 02:21 _ ~AP~Specific~SNMP~RFC-1213~Interface~Outbound Throughput (PDUs per second) RFC-1213 Interface _ ~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps) _ 900 _ 100009851 _ 1065103662 _ U _ 10/02/2003 18:07 _ ~AP~Specific~SNMP~RFC-1213~Interface~Outbound Throughput (PDUs per second) RFC-1213 Interface _ ~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps) _ 900 _ 100009851 _ 1050698751 _ I _ 04/19/2003 00:45 _ Checking the number of groups to which a subelement belongs resmgr -export segp -colnames "se.name dbindex_count" -file $DIR/Usage_seNbGroup.dat # type = segp # col = se.name dbindex_count # filter = # order = # sep = _ # seprec = # # cmdline = -export segp -colnames "se.name dbindex_count" 172.17.100.254_<NULL> _ 7 _ 172.31.0.31_<NULL> _ 9 _ 172.31.0.31_If<1> _ 9 _ 172.31.0.31_If<2> _ 9 _ 172.31.0.31_If<3> _ 9 _ 172.31.0.31_If<4> _ 9 _ 172.31.0.31_If<5> _ 9 _ 172.31.0.31_If<6> _ 9 _ 172.31.0.31_If<7> _ 9 _ 172.31.0.41_<NULL> _ 9 _ 172.31.0.41_If<1> _ 9 _ 172.31.0.41_If<2> _ 9 _ 172.31.0.41_If<3> _ 9 _ 172.31.0.41_If<4> _ 9 _ 172.31.0.41_If<5> _ 9 _ 172.31.0.41_If<8> _ 9 _ 172.31.0.41_RTTMon<NULL>Probe<1> _ 6 _ 172.31.0.41_RTTMon<NULL>Probe<2> _ 6 _ 172.31.0.41_RTTMon<NULL>Probe<3> _ 6 _ 172.31.0.51_<NULL> _ 9 _ 204 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Listing elements with empty SysName resmgr -export elt -colnames "name encl.name" -filter "encl.name(is null)" -file $DIR/Usage_eltEmptySysName.dat # type = elt # col = name encl.name # filter = encl.name(is null) # order = # sep = _ # seprec = # # cmdline = -export elt -colnames "name encl.name" -filter "encl.name(is null)" Burned_100008089_192.168.1.3 _ _ 192.168.127.4 _ _ APRouterforprobe _ _ PROVISO _ _ default _ _ Finding number of collection requests per subelement resmgr -export segpreq -colnames "segp.dbindex_count se.name" -file $DIR/Usage_seNbCollect.dat # type = segpreq # col = segp.dbindex_count se.name # filter = # order = # sep = _ # seprec = # # cmdline = -export segpreq -colnames "segp.dbindex_count se.name" 2 _ 172.31.0.31_<NULL> _ 2 _ 172.31.0.41_<NULL> _ 14 _ 172.31.0.41_RTTMon<NULL>Probe<1> _ 14 _ 172.31.0.41_RTTMon<NULL>Probe<2> _ 14 _ 172.31.0.41_RTTMon<NULL>Probe<3> _ 2 _ 172.31.0.51_<NULL> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<10097> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<10102> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<10107> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<10110> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<10113> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<10115> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<10116> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<10117> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<10119> _ 7 _ 172.31.0.51_RTTMon<NULL>Probe<10120> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<1969> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<7777> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<8888> _ 14 _ 172.31.0.51_RTTMon<NULL>Probe<9999> _ 2 _ 172.31.1.2_<NULL> _ 2 _ 192.168.1.3_<NULL> _ 2 _ 192.168.64.253_<NULL> _ Appendix B. Working with SAA probes 205

Filtering without case filter resmgr -export elt -colnames "name" -filter "name_upper(*boston*)" -file $DIR/Usage_filter2.dat If the command is successful, no output is displayed. Finding the number of subelements in a family resmgr -export se -colnames "name_count fam.name" -ismandat "fam" -file $DIR/Usage_seNbFamily.dat #type=se # col = name_count fam.name # filter = # order = # sep = _ # seprec = # # cmdline = -export se -colnames "name_count fam.name" 84 _ 1213_Deice _ 776 _ 1213_IF _ 244 _ 2233_IF _ 3 _ Cisco_11x_Router_Deice _ 2 _ Cisco_FR_DLC_SNMP-CIR _ 1 _ Cisco_IPSec _ 6 _ Cisco_MPLS_LSP _ 3 _ Cisco_Router_Deice_SAA _ 6 _ Cisco_Router_Deice_SAA_Resp _ 19 _ MLARS _ 725 _ NetFlow _ 65 _ RTTMon_Common_Probe _ 13 _ RTTMon_HTTP_Probe _ 45 _ RTTMon_Jitter_Probe _ Grouping all the subelements The following resmgr command groups all the sub-elements which are attached to the an element which IP address is between 192.168.64.40 and 192.168.64.60 in the subelement group named "net40-60" within the NOC reporting group resmgr -nohead -export se -rule "~NOC Reporting~net40-60,%(name)," -filterrule "pub.formatip(%(eprp.ipaddress:alue)) > 192.168.064.020 and pub.formatip(%(eprp.ipaddress:alue)) < 192.168.064.025 " resmgr -import segp -sep, -colnames "npath se.name" Displaying the classification of the xeice name dhcp200 resmgr -export elt -sep -nohead -colnames "encl.oid" -filter "name(dhcp200)" xargs -I {} resmgr -export ngp -colnames "npath ncl.name ncl.oid" -filter "ncl.oid({})" -nohead -file $DIR/Usage_deice.dat 206 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Inserting in the past Note: Check with IBM Support before using this command. Inserting in the past has significant impact on the Tioli Netcool Performance Manager system. resmgr -import seproperty -colnames "name seprp.contact:alue seprp.contact:date(1057015945)" -histodate 1 -mode "IFirst,forced" -file... Appendix B. Working with SAA probes 207

208 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Appendix C. CLI return codes snmpconf Proides information about the return codes for Tioli Netcool Performance Manager DataMart command line interfaces (CLI) The following information about return codes for Tioli Netcool Performance Manager command line interfaces (CLI): Binary/Version is the name of the CLI and the release number for DataMart Language is the language that was used to build the CLI. Usage tells you if the CLI is also aailable in GUI mode. Success Return Code proides the code number for a successful CLI execution. Failure Return Code proide the code number for a failed CLI execution. Other Return Codes proides information on other return codes other than "0" (if applicable). Log File Name proides the name of the logging file. A return code of "0" indicates the command was successful. A return code other than 0, indicates the command failed with errors. CLIs are written in tcltk, C, C++, and Shell. You need to use the "-nox" option for CLIs written in tcltk. If errors occur, a code number other than "0" is returned. Details about the error are logged to standard output. Return code details for the snmpconf command-line interface are as follows: Binary Language Usage snmpconf tcltk CLI and GUI Success Return Code Failure Return Code Other Return Codes Log File Name 0 1 stderr/ stdout Standard output error messages The following example error messages appear when launching snmpconf without using the -erbose option (resulting in more output lines, including error and non-errors). The error messages are written in the standard output using the following format: ERROR in SNMPCONF : <short error message> : <detailed error message> Examples ERROR in SNMPCONF : UPDATE failed : No changed alue ERROR in SNMPCONF : ADD failed : Element myhost already exists Short and detailed error messages are listed in the following table. Copyright IBM Corp. 1997, 2012 209

Short Error Message Detailed Error Message Comments ADD failed Element %s already exists! %s: <name of the element> Element name should not contain space character! Element name should not contain "~"! Element name should not contain " "! Element name should not contain ","! Element must be specified! IP address must be specified! (example: 123.123.123.123, 123.123.123.* or 123.123.123.1-10,33,44,50-77) Bad alue of option "-ipaddress"! (example: 123.123.123.123, 123.123.123.* or 123.123.123.1-10,33,44,50-77) Bad alue of option "-timeout" alue must be numeric! Bad alue of option "-tries" alue must be numeric! Bad alue of option "-port" alue must be numeric! Element "default" is resered! You cannot add or delete it. IP address *.*.*.* is resered for "default" element! Database access error (%s). %s: <detailed error> Cannot insert element into database! snmpconf is in READ MODE! This message can be followed by the SQL query that has failed Cannot perform operation without write permissions 210 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

UPDATE failed IP address must be specified! (for example, 123.123.123.123, 123.123.123.* or 123.123.123.1-10,33,44,50-77) Bad alue of option "-ipaddress"! (for example, 123.123.123.123, 123.123.123.* or 123.123.123.1-10,33,44,50-77) Element name should not contain space character! Element name should not contain "~"! Element name should not contain " "! Element name should not contain ","! Element must be specified! IP address must be specified! (for example, 123.123.123.123, 123.123.123.* or 123.123.123.1-10,33,44,50-77) Bad alue of option "-ipaddress"! (for example, 123.123.123.123, 123.123.123.* or 123.123.123.1-10,33,44,50-77) Bad alue of option "-timeout" alue must be numeric! Bad alue of option "-tries" alue must be numeric! Bad alue of option "-port" alue must be numeric! Element %s doesn't exist! Cannot get element from database! Cannot read from database All fields of "default" must be specified! %s : <name of the element> This message can be followed by the SQL query that has failed. This message can be followed by the SQL query that has failed. Appendix C. CLI return codes 211

No option passed! (possible options are -ipaddress -rcommunity -wcommunity -timeout -tries -port) No changed alue! Missing some CLI options Can not update because of unchanged parameters DELETE failed This «error» can be ignored. It is a warning Element "default" is resered! You can't change its address (*.*.*.*). IP address *.*.*.* is resered for "default" element! Cannot update element in database! Cannot sae in database snmpconf is in READ MODE! Element name should not contain space character! Element name should not contain "~"! Element name should not contain " "! Element name should not contain ","! Element must be specified! Bad alue of option "-ipaddress"! (example: 123.123.123.123, 123.123.123.* or 123.123.123.1-10,33,44,50-77) Bad alue of option "-timeout" alue must be numeric! This message can be followed by the sql query that has failed Can not perform operation without write permissions Bad alue of option "-tries" alue must be numeric! Bad alue of option "-port" alue must be numeric! 212 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Database Error Element %s doesn't exist! Cannot get element from database! Cannot read from database Element "default" is resered! You can't add or delete it. Cannot delete element in database! snmpconf is in READ MODE! Cannot get elements information from database! %s: <name of the element> This message can be followed by the sql query that has failed This message can be followed by the sql query that has failed Can not perform operation without write permissions Unknown operation %s %s : the operation name that hae been passed to CLI Unable to inform collector about modifications at %s! %s: <Ipadress : port #> Cannot continue without permissions Check the user permissions for the current CLI reqedit Return code Return code details for the reqedit command line interface is are as follows: Binary/ Version Language Usage reqedit 2.0 and 2.2 tcltk CLI and GUI Success Return Code Failure Return Code Other Return Codes Log File Name 0 1 stderr/ stdout Standard output error messages The following example error messages appear when launching the reqedit without using the -erbose option (resulting in more information on the standard output errors and process information). The error messages are written in the standard output using the following format: ERROR in REQEDIT : <short error message> <detailed error message> Examples: ERROR in REQEDIT : Bad period alue. Period alue range is from 1 minute to 24 hours. ERROR in REQEDIT : Missing parameters on request "formula target" are mandatory. Appendix C. CLI return codes 213

Short and detailed error messages are listed in the following table. Short Error Message Detailed Error Message Comments Unable to launch Request Editor in write mode. Unknown operation %s %s : the operation name that hae been passed to CLI. Cannot read Database requests. Database access error (%s). %s: <detailed error> Cannot read from database Cannot get index %s %s: formula's database index Cannot read from database %s %s : <detailed error>. Missing parameters on "%s" are mandatory. %s : CLI missing parameters request. Period or Calendar must be specified. Bad period alue. Period alue range is from %s minute to 24 hours. Bad storage alue. Bad resource type. Bad status alue. Cannot read from database Cannot sae in database %s : <minimum period alue> This message can be followed by the sql query that has failed. This message can be followed by the sql query that has failed. Unknown operation: %s %s : <operation string>. Valid operations are : add, update, and delete. Unknown request. Unknown formula: %s %s : <formula name> Unknown element name: %s %s : <element name> Unknown element group %s %s : <element group name> name: Unknown sub-element name: %s %s : <sub-element name> Unknown sub-element group name: %s %s :<sub-element group name> Unknown calendar: %s %s : <calendar name> Unknown threshold profile: %s %s : <threshold name> Not a alid formula: %s : <formula name> Request already exists. Unable to inform collector %s: <Ipadress : port #> about modifications at %s! Cannot add request to database. 214 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Cannot update request into database. Cannot remoe request from database. resmgr Return code Return code details for the resmgr command line interface is are as follows: Binary/ Version Language Usage Success Return Code Failure Return Code Other Return Codes Log File Name resmgr 2.0 and 2.2 tcltk CLI and GUI 0 1 X>1: where X = nberrors + 10 stderr + stdout (nberrors is the number of sql requests that hae failed) Comments Return code 1 = critical error Return code >1 (X) means there are errors, but it is not critical. Standard output error messages The following error messages appear when launching resmgr without using the -erbose option (resulting in more output lines, including non-errors information). To check the errors, check log lines, looking for the string `Error' <Log leel> : < Short message> : <Detailed message> where <Log leel> is Error, or Warning, or Info Example #1 resmgr -import fgp -colnames "npath" -file./t.txt Info : === insert : INSERT ON Formula Group ( ~Fake_ProSerices~MIBII ) (does not exist) Info : === insert : UPDATE ON Formula Group ( ~ProSerices~MIBII~Interface ) (exists) Info : === insert : UPDATE ON Formula Group ( ~ProSerices~Netware ) (exists) Info : === insert : UPDATE ON Formula Group ( ~ProSerices~Lotus Notes ) (exists) Appendix C. CLI return codes 215

Example #2 solar:/opt/pvm2.0/importexport> resmgr -nox Error : === InalidAction : must be export import delete analyse In case of critical errors, the return code is 1, you hae the log on the standard output. Short and detailed error message are listed in the following table. Short Error Message Detailed Error Message Comments Cannot connect to database. Database access error (%s). %s : <message>. Cannot disconnect from database. Cannot continue without permissions. Cannot delete in database Cannot sae in database Cannot read from database inentory Return code Return code details for the inentory command line interface is are as follows: Binary Language Usage Success Return Code Failure Return Code Other Return Codes Log File Name inentory tcltk CLI and GUI 0 1 2 stderr/ stdout The 2 return code signifies that the inentory profile is locked. This return code only displays if the PVM_ENHANCED_ERRORCODE =1 ariable is set in your DataMart enironment. 216 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Standard output error messages The following messages appear when launching inentory without using the -erbose option (resulting in more output lines, including non-errors information). The error messages are written in the standard output using different formats. Format Type 1 ERROR in INVENTORY : <short error message> : <detailed error message> Examples ERROR in INVENTORY : Cannot continue without permissions. Format Type 2 Error : <short error message> Examples Error: You must specified a profile name Error: Cannot read from database Warning : <short error message> -or- -or- <short error message> Examples "-tutu" is not a known option List of aailable options: -? -D -Parent -U -action -name -nox -reload -reportgrouping Short and detailed error messages are listed in the following table: Short Error Message Detailed Error Message Comments Cannot connect to database. Database access error (%s). %s : <message>. Cannot disconnect from database. Cannot continue without permissions. Cannot delete in database Cannot sae in database Cannot read from database Profile '%s' already exist! Appendix C. CLI return codes 217

File '%s' doesn't exist! You must run discoery before running synchronization %s %s : <message>. Format Type 3 This type of log is produced while the module is using resmgr APIs. The log format is the same as what is normally produced by resmgr. <Log leel> : < Short message> : <Detailed message> where <Log leel> is Error, or Warning, or Info Example resmgr -import fgp -colnames "npath" -file./t.txt Info : === insert : INSERT ON Formula Group ( ~Fake_ProSerices~MIBII ) (does not exist) Info : === insert : UPDATE ON Formula Group ( ~ProSerices~MIBII~Interface ) (exists) Info : === insert : UPDATE ON Formula Group ( ~ProSerices~Netware ) (exists) Info : === insert : UPDATE ON Formula Group ( ~ProSerices~Lotus Notes ) (exists) impexp Return code Return code details for the impexp command line interface are as follows: Binary/ Version Language Usage Success Return Code Failure Return Code Other Return Codes Log File Name impexp 2.0 and 2.2 tcltk CLI and GUI 0 1 X, where X is a number. $PVMHOME/ log/ logfile.impexp. X=10 + nbsqlfailures nbsqlfailures is the number of sql requests that hae failed during operation. Comments The return code 1 indicates that impexp encountered a critical error. If only a part of process worked. If not critical error, the return code is greater than 1. 218 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Standard output error messages Only critical messages are logged in the standard outputs. In such cases, the return code is 1, and the error is logged on the standard output. The following syntax is erroneous ("-" forgotten before "export") : impexp -nox export calendars /tmp/calendars You can get the following error on the standard output: Error : === BAD ARGUMENTS: At least one option required amog (-export, -import, -config). Appendix C. CLI return codes 219

220 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Appendix D. Sample inentory script Sample inentory script Proides contains a sample Korn Shell wrapper program that calls the inentory command. This appendix The command does the following: Extracts all existing inentory profiles from the database. Loops through the profiles, running a complete inentory on each one. Reloads the collector after eery fie inentories (this is configurable). After all the inentories hae run, calls the inentory command with the -reportgrouping option. The script also allows you to inoke it with command-line options. For more information, see your Tioli Netcool Performance Manager Professional Serices representatie. #!/bin/ksh #set -x #=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # # RUNINVENTORY # #--------------------------------- ------- # FileName : runinentories.ksh # Author : ACOS # Date : 24/07/02 # Subject : Run all inentory profiles #--------------------------------- ------- # Copyright(c) IBM 2005 PROVISO 4.4 #-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- THISFILE=`whence ${0}` DIRNAME=`dirname ${THISFILE}` PVMHOME="/opt/quallaby/datamart" ARGS="$@" PROGNAME="${0##*/}" PROGNAME="${PROGNAME%%.*}" LOGFILE="${DIRNAME}/${PROGNAME}.log" : ${LOGMAXL:=10000} : ${reloadfreq:=10} #------------------------------------------------------------------------------- # Default parameters #------------------------------------------------------------------------------- ACTION="all" SEP=" " let YES=0 let VERBOSE=0 #------------------------------------------------------------------------------- # Command line keywords #------------------------------------------------------------------------------- Copyright IBM Corp. 1997, 2012 221

KEY_ACTION="-action" KEY_PROFILE="-profile" KEY_SEP="-sep" KEY_VERBOSE="-"; KEY_YES="-Yes"; KEY_HELP="-?"; # Verbose mode # Answer Yes to all questions # ----------------------------------------------------------------------------- # function Confirm # ----------------------------------------------------------------------------- function Confirm { if ((! ${YES} )) then read IN?"${1}" if [[ $IN == @(y Y) ]] then return 0 else return -1 fi else return 0 fi } # ----------------------------------------------------------------------------- # function PrintError # ----------------------------------------------------------------------------- function PrintError { echo "`date \"+%m/%d/%y-%h:%m:%s\"` [${PROGNAME}] Error : ${1}" } # ----------------------------------------------------------------------------- # function PrintWarning # ----------------------------------------------------------------------------- function PrintWarning { echo "`date \"+%m/%d/%y-%h:%m:%s\"` [${PROGNAME}] Warning : ${1}" } # ----------------------------------------------------------------------------- # function PrintInfo # ----------------------------------------------------------------------------- function PrintInfo { echo "`date \"+%m/%d/%y-%h:%m:%s\"` [${PROGNAME}] Info : ${1}" } # ----------------------------------------------------------------------------- # function PrintLog # ----------------------------------------------------------------------------- 222 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

function PrintLog { if (( ${VERBOSE} )) then echo "`date \"+%m/%d/%y-%h:%m:%s\"` [${PROGNAME}] ${1}" } fi #------------------------------------------------------------------------------- # function PrintUsage #------------------------------------------------------------------------------- function PrintUsage { cat << USAGE Usage : ${0##*/} [Options] Where Options are ${KEY_ACTION} : Defines which modules to run [discoery synchro grouping user] (default all) ${KEY_PROFILE} "default") ${KEY_SEP} ${KEY_VERBOSE} ${KEY_YES} : Profile name (by default all profiles except : Set the field separator (default is "${SEP}") : Verbose mode (disable by default) : Answer Yes to all questions (disable by default) ${KEY_HELP} : Gies this help Run Profiles, populate properties and perform a report grouping. USAGE } #------------------------------------------------------------------------------- # Help #------------------------------------------------------------------------------- if [[ ${1} = "-?" ${1} = "-help" ]] then PrintUsage exit 0 fi #------------------------------------------------------------------------------- # Parsing parameters #------------------------------------------------------------------------------- while [[ -n ${1} ]] do case ${1} in "${KEY_ACTION}") shift if [[ -n ${1} ]] then Appendix D. Sample inentory script 223

ACTION="${1}" else PrintError "Missing mandatory parameter!" PrintUsage exit 3 fi ;; "${KEY_PROFILE}") shift if [[ -n ${1} ]] then PROFILE="${1}" else PrintError "Missing mandatory parameter!" PrintUsage exit 3 fi ;; "${KEY_SEP}") shift if [[ -n ${1} ]] then SEP="${1}" else PrintError "Missing mandatory parameter!" PrintUsage exit 3 fi ;; "${KEY_VERBOSE}") let VERBOSE=1 ;; "${KEY_YES}") let YES=1 ;; * ) PrintError "Failed to parse arguments, unknown option: \"${1}\"." PrintUsage exit 3 ;; esac shift done #------------------------------------------------------------------------------- # run en #-------------------------------------------------------------------------------. $PVMHOME/dataMart.en #------------------------------------------------------------------------------- # Retreie profiles list #------------------------------------------------------------------------------- if [ -z "${PROFILE}" ] then resmgr -export ogp -colnames "npath" grep - # \ nawk -F " " \ { n=split($1, TAB, "~") if (n > 1) 224 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

{ PROFILE=TAB[2] if ( (PROFILE!= "") && (PROFILE!= "default") && (index(profile,"in_")>0)) print PROFILE } } sort uniq > ${PROGNAME}.profiles else echo ${PROFILE} > ${PROGNAME}.profiles fi #------------------------------------------------------------------------------- # Running inentory for each profiles #------------------------------------------------------------------------------- typeset -i NBPROFILES=$(wc -l < ${PROGNAME}.profiles 2>/de/null) typeset -i profcnt=1 cat ${PROGNAME}.profiles & while read -p i do PrintLog "Launching inentory profile \"${i}\"..." LOGFILE="${DIRNAME}/${PROGNAME}_${i}.log" if ( (( profcnt % reloadfreq == 0 )) (( profcnt == NBPROFILES )) ) then inentory -nox -name "${i}" -action "${ACTION}" -reload 1 >> "${LOGFILE}" 2>&1 else inentory -nox -name "${i}" -action "${ACTION}" >> "${LOGFILE}" 2>&1 fi if [ ${?} -ne 0 ] then PrintError "Inentory failed for profile \"${i}\"." fi sleep 60 profcnt=$((profcnt+1)) done #------------------------------------------------------------------------------- # Report autogrouping #------------------------------------------------------------------------------- PrintLog "running reportgrouping..." inentory -nox -reportgrouping >> "${LOGFILE}" 2>&1 #------------------------------------------------------------------------------- # Cleaning temporary files #------------------------------------------------------------------------------- #rm -rf "${PROGNAME}.profiles" >/de/null 2>&1 exit 0 #=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # END OF FILE #=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Appendix D. Sample inentory script 225

226 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Appendix E. Using prerequisite check scripts Using the check_os script Proides information concerning how to use prerequisite check scripts that are included with Tioli Netcool Performance Manager, Tioli Netcool Performance Manager includes the check_os and check_db prerequisite checking scripts that are used to erify arious host system and Oracle database requirements to ensure the successful operation of Tioli Netcool Performance Manager. The sections below explain how to use these scripts to erify your Tioli Netcool Performance Manager enironment. The check_os script is used to erify platform ersion and patch requirements for Solaris, AIX, and Redhat Linux systems that host Tioli Netcool Performance Manager components. Tasks Performed by the check_os script Once the script has been executed, check_os refers to alues set in the check_os.ini file and performs the following tasks: Verfies that an argument was passed to the script. Verifies that the operating system is a supported platform for Tioli Netcool Performance Manager. Verifies that the operating system is a supported ersion for Tioli Netcool Performance Manager. Verifies that the specified Tioli Netcool Performance Manager component is alid and supported on the current operating system. Verifies that the required patches hae been applied to the operating system. Running the check_os script To use the check_os script, do the following: 1. Log in as root on the system where the Topology Editor has been installed. 2. Change your working directory to the directory that contains the check_os script. For example, using the default location: cd /opt/ibm/proiso/deployer/proiso/bin/check 3. Start the check_os script using the following command:./check_os component_id Where component_id specifies a Tioli Netcool Performance Manager component. The following table lists the supported alues: Value dm dl dc Description Tioli Netcool Performance Manager DataMart Tioli Netcool Performance Manager DataLoad Tioli Netcool Performance Manager DataChannel Copyright IBM Corp. 1997, 2012 227

Value db d Description Tioli Netcool Performance Manager Database Tioli Netcool Performance Manager DataView 4. If you need to examine the supported requirements for your operating system, open the check_os.ini file using the following command: more check_os.ini Use the check_os.ini file as a reference only. For more detailed information, see the IBM Tioli Netcool Performance Manager: Installation Guide and IBM Tioli Netcool Performance Manager: Configuration Recommendations. Example output The following are examples of output returned by the config_os script: Solaris #./check_os db -->OK. Version SunOS 5.9. -->OK. Proiso Component DB. -->OK. OS patch 112233-02 is applied. -->OK. OS patch 111711-15 is applied. AIX #./check_os db -->OK. Version AIX 5300-04. -->OK. Proiso Component DB. -->OK. OS patch xlc.aix50.rte is applied. -->OK. OS patch xlc.msg.en_us.rte is applied. -->OK. OS patch xlc.rte is applied. -->OK. Limit: FSIZE is set to: -1. -->OK. Limit: CORE is set to: -1. -->OK. Limit: CPU is set to: -1. -->OK. Limit: DATA is set to: -1. -->OK. Limit: RSS is set to: 65536. -->OK. Limit: STACK is set to: 65536. -->OK. Limit: NOFILES is set to: 2000. Error messages The check_os script can return the following error messages: Error Message Proiso Component Can Be: DL, DC, DM, DB, DV This ersion of operating system is not supported! Description No component_id was specified in the script command. The ersion of the current operating system is not supported by Tioli Netcool Performance Manager. Examine the check_os.ini file for supported ersions of operating systems. 228 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Error Message Proiso Component: component_id is unknown or not supported for this OS! ** ERROR ** Missing required patch patch_name for this OS! This system's OS is not supported! ERROR! The alue of limit_name was not detected in the /etc/security/limits file. Check that the minimum alue is set. ERROR! The alue of limit_name is: limit_alue. This is not equal or less than what is set in the check_os.ini file. ERROR! Unknown OS Prefix Description Either an incorrect Tioli Netcool Performance Manager component was specified in the script command, or the Tioli Netcool Performance Manager component is not supported on the current operating system. Examine the check_os.ini file for supported operating systems. The current operating system is not supported by Tioli Netcool Performance Manager. Examine the check_os.ini file for supported operating systems. The current operating system is not supported by Tioli Netcool Performance Manager. Examine the check_os.ini file for supported operating systems. AIX only. A alue is missing from the /etc/security/limits file. Examine the check_os.ini file for supported /etc/security/limits alues. AIX only. A alue is incorrect in the /etc/security/limits file. Examine the check_os.ini file for supported /etc/security/limits alues. The current operating system is not supported by Tioli Netcool Performance Manager. Examine the check_os.ini file for supported operating systems. Using the check_db script The check_db script is used to erify system settings and Oracle ersion and patch requirements for Solaris, AIX, and Redhat Linux systems that host Tioli Netcool Performance Manager components. Tasks performed by the check_db script Once the script has been executed, check_db refers to alues set in the check_db.ini file and performs the following tasks: Verifies that arguments were passed to the script. Verifies that the operating system is a supported platform for Tioli Netcool Performance Manager. Verifies that the operating system is a supported ersion for Tioli Netcool Performance Manager. Verifies that the required Oracle enironment ariables are set. Verifies that the installed Oracle ersion is a supported ersion for Tioli Netcool Performance Manager. Verifies the Oracle home patch and checks that no symbolic links are used in the Oracle home directory tree. Verifies that the Oracle binary has the correct bit setting for the operating system. Runs the tnsping command to ensure that the Oracle serer is accessible. Appendix E. Using prerequisite check scripts 229

Verifies that no Oracle background processes exists for Tioli Netcool Performance Manager. Verifies that no instance-specific configuration files exist for Tioli Netcool Performance Manager. Verifies that the Oracle database is running and accessible. Running the check_db script About this task To use the check_db script, do the following: Procedure 1. Log in as oracle on the system where the Topology Editor has been installed. 2. Change your working directory to the directory that contains the check_db script. For example, using the default location: cd /opt/ibm/proiso/deployer/proiso/bin/check 3. To erify Oracle database prerequisites, start the check_db script using the following command:./check_db install_type install_method ORACLE_SID Where: Variable install_type install_method Description Supported alues are serer or client. Specifies whether check_db is to erify the prerequisites for an Oracle serer or client installation. Supported alues are new or upgrade. Specifies whether check_db is to erify the prerequisites for a new or upgrade Oracle installation. ORACLE_SID Specifies the Oracle System Identifier used for Tioli Netcool Performance Manager in your enironment. For example, PV. 4. To erify that the Oracle database is running and accessible, start the check_db script using the following command:./check_db erifybase ORACLE_SID Where: Variable ORACLE_SID Description Specifies the Oracle System Identifier used for Tioli Netcool Performance Manager in your enironment. For example, PV. 5. If you need to examine the supported requirements for your operating system, open the check_db.ini file using the following command: more check_db.ini Use the check_db.ini file as a reference only. For more detailed information, see the IBM Tioli Netcool Performance Manager: Installation Guide and IBM Tioli Netcool Performance Manager: Configuration Recommendations. 230 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Examples The following are examples of output returned by the config_db script: Solaris $./check_db serer new PV -->OK. Version SunOS 5.9. -->OK. ORACLE_HOME does not contain symbolic links. -->OK. Oracle ersion 9.2.0.8.0 -->OK. 32 bit /opt/oracle/product/9.2.0/bin/oracle. $./check_db erifybase PV -->OK. Version SunOS 5.9. -->OK. ORACLE_HOME does not contain symbolic links. -->OK. TNSPING response is: Attempting to contact (DESCRIPTION = (ENABLE=BROKEN) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = pmgde3) (PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = PV.WORLD) (INSTANCE_NAME = PV))) OK (0 msec). -->OK. Instance PV is aailable. -->OK. The checkextc script succeeded. AIX $./check_db serer new PV -->OK. Version AIX 5300-04. -->OK. ORACLE_HOME does not contain symbolic links. -->OK. Oracle ersion 9.2.0.8.0 -->OK. 64 bit /opt/oracle/product/9.2.0/bin/oracle. $./check_db erifybase PV -->OK. Version AIX 5300-04. -->OK. ORACLE_HOME does not contain symbolic links. -->OK. TNSPING response is: Attempting to contact (DESCRIPTION = (ENABLE=BROKEN) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = qadb1) (PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = PV.WORLD) (INSTANCE_NAME = PV))) OK (120 msec). -->OK. Instance PV is aailable. -->OK. The checkextc script succeeded. Error messages The check_db script can return the following error messages: Error Message This script can be run in two ways: Prerequisite Usage: check_db <[client - serer] [new - upgrade] [ORACLE_SID or tnsnames.ora entry]> Verify_Base Usage: check_db <[erifybase] [ORACLE_SID or tnsnames.ora entry] ERROR! This systems OS is not supported! ERROR! This ersion of operating system is not defined in check_db.ini! Description Incorrect arguements were specified in the script command. The current operating system is not supported by Tioli Netcool Performance Manager. Examine the check_db.ini file for supported operating systems. The ersion of the current operating system is not supported by Tioli Netcool Performance Manager. Examine the check_db.ini file for supported ersions of operating systems. Appendix E. Using prerequisite check scripts 231

Error Message ORACLE_BASE Not defined. ORACLE_HOME Not defined. NLS_LANG Not defined. SHLIB_PATH_VAR Not defined. TNS_ADMIN Not defined. PATH Not defined. EXTPROC_DLLS Not defined. ERROR! Could not determine ersion of Oracle installed! ERROR! Checked for Oracle software. ERROR! Ensure Oracle software is installed. WARNING! Client Version does not match entry in check_db.ini ERROR! Oracle ersion: ersion not listed in check_db.ini. ERROR! Link is a symbolic link! ERROR! The binary: binary_name was not found. Check if Oracle is installed. ERROR! Bit_setting bit binary_name not listed in check_db.ini. WARNING! Did not get OK response from tnsping. Description The ORACLE_BASE parameter has not been set. Set this alue and run the script again. The ORACLE_HOME parameter has not been set. Set this alue and run the script again. The NLS_LANG parameter has not been set. Set this alue and run the script again. The SHLIB_PATH_VAR parameter has not been set. Set this alue and run the script again. The TNS_ADMIN parameter has not been set. Set this alue and run the script again. The PATH parameter has not been set. Set this alue and run the script again. The EXTPROC_DLLS parameter has not been set. Set this alue and run the script again. The Oracle ersion could not be found. Verify that a ersion of Oracle supported by Tioli Netcool Performance Manager has been installed on the system. The Oracle software could not be found. Verify that a ersion of Oracle supported by Tioli Netcool Performance Manager has been installed on the system. The Oracle software could not be found. Verify that Oracle has been installed on the system. The Oracle client ersion is not supported by Tioli Netcool Performance Manager. Examine the check_db.ini file for supported ersions of Oracle client. The Oracle ersion is not supported by Tioli Netcool Performance Manager. Examine the check_db.ini file for supported ersions of Oracle. The specified link is symbolic. No symbolic links can be used in the Oracle home directory tree. The specified Oracle binary could not be found. Verify that Oracle has been installed on the system. The specified bit setting does not match the correct bit setting for the operating system. Examine the check_db.ini file for supported bit settings. Oracle is not responding. Check that Oracle is running and aailable. 232 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Error Message WARNING! Cannot contact Oracle listener. ERROR! Found an Oracle instance running with PID: PID. ERROR! An init.ora file exists for gien SID. ERROR! The alue of parameter was not detected with the sysdef command and could not be found in the /etc/ system file. Description The Oracle listener is not responding. Check that the Oracle listener is running and aailable. An existing Oracle background process exists for Tioli Netcool Performance Manager on the system. Determine if you wish to reinstall or upgrade the Oracle serer. An existing instance-specific Oracle configuration file exists for Tioli Netcool Performance Manager on the system. Determine if you wish to reinstall or upgrade the Oracle serer. A alue is incorrect in the /etc/system file. Examine the check_db.ini file for supported /etc/system alues. ERROR! The alue of parameter is: alue, which is less than what is listed as the recommended minimum in the check_db.ini file. ERROR! The alue of SHMMAX was not detected with the sysdef command and coulnd not be found in the /etc/system file. ERROR! The alue of SHMMAX is: alue, which is less than the reccomended alue. ERROR! Could not find the file set name as COMMITTED. A alue is incorrect for parameter. Examine the check_db.ini file for supported alues for parameter. Check that the minimum alue is set. The alue for SHMMAX in the /etc/system file is missing. Examine the check_db.ini file for supported alues for SHMMAX. The alue for SHMMAX in the /etc/system file is incorrect. Examine the check_db.ini file for supported alues for SHMMAX. The specified file set could not be found. Verfiy that the file set has been installed on the system. ERROR! Could not find asyncio as Aailable. The specified file is not aailable. Check that Oracle is running and aailable. ERROR! Unknown OS Prefix. The current operating system is not supported by Tioli Netcool Performance Manager. Examine the check_db.ini file for supported operating systems. ERROR! Could not access the instance ORACLE_SID. ERROR! Check that the Oracle instance is running. ERROR! The checkextc script failed. ERROR! Inalid install method. ERROR! Must be New or Upgrade. The specified Oracle System Identifier is not accessible. Check that the instance has been defined. The Oracle instance is not running. Check that Oracle is running and aailable. The external procedure call check has failed. Verify the cause of the failure and re-run the script. An incorrect install_method was specified in the script command. Verify the command syntax and re-run the script. Appendix E. Using prerequisite check scripts 233

Error Message ERROR! Inalid Install Type. ERROR! Must be client or serer. Description An incorrect install_type was specified in the script command. Verify the command syntax and re-run the script. 234 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

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

IBM may use or distribute any of the information you supply in any way it beliees appropriate without incurring any obligation to you. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be aailable, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material aailable for it are proided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurement may hae been estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly aailable sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on arious operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of deeloping, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of deeloping, using, marketing, or distributing application programs conforming to IBM s application programming interfaces. 236 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

If you are iewing this information in softcopy form, the photographs and color illustrations might not be displayed. Notices 237

238 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and serice names might be trademarks of IBM or other companies. A current list of IBM trademarks is aailable on the Web at Copyright and trademark information at http://www.ibm.com/legal/copytrade.shtml. Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both. Cell Broadband Engine and Cell/B.E. are trademarks of Sony Computer Entertainment, Inc., in the United States, other countries, or both and is used under license therefrom. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Goernment Commerce. ITIL is a registered trademark, and a registered community trademark of the Office of Goernment Commerce, and is registered in the U.S. Patent and Trademark Office. Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Toralds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and serice names may be trademarks or serice marks of others. For trademark attribution, isit the IBM Terms of Use Web site: http://www.ibm.com/legal/us/. Copyright IBM Corp. 1997, 2012 239

240 IBM Tioli Netcool Performance Manager: Command Line Interface Guide

Printed in USA