command line interface guide · ibmtivoli netcool performance manager 1.3.3 wireline component...

IBM Tivoli Netcool Performance Manager 1.3.3Wireline ComponentDocument Revision R2E1

Command Line Interface Guide

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 233.

© Copyright IBM Corporation 2006, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this information . . . . . . . . viiIntended audience . . . . . . . . . . . . viiThe Tivoli Netcool Performance Manager productsuite . . . . . . . . . . . . . . . . viiNetwork and Service Assurance community onService Management Connect . . . . . . . . viiiTivoli technical training . . . . . . . . . . ixSupport information . . . . . . . . . . . ixConventions used in this publication . . . . . . ix

Typeface conventions . . . . . . . . . . ix

Chapter 1. Introduction . . . . . . . . 1Special characters and command-line utilities . . . 1Accessing CLI utilities . . . . . . . . . . . 1

Chapter 2. Using the inventorycommand . . . . . . . . . . . . . . 3Function . . . . . . . . . . . . . . . . 3Synopsis . . . . . . . . . . . . . . . . 3Description . . . . . . . . . . . . . . . 4Options . . . . . . . . . . . . . . . . 6Examples . . . . . . . . . . . . . . . 9

Chapter 3. The dccmd command . . . 11Running the dccmd command . . . . . . . . 11The dccmd command syntax . . . . . . . . 11Example dccmd commands . . . . . . . . . 13

Chapter 4. Managing Tivoli NetcoolPerformance Manager objects. . . . . 15Understanding Tivoli Netcool Performance Managerobjects . . . . . . . . . . . . . . . . 16

About Tivoli Netcool Performance Managerobjects . . . . . . . . . . . . . . . 16

Understanding Tivoli Netcool Performance Managerobject IDs . . . . . . . . . . . . . . . 21Working with resmgr . . . . . . . . . . . 22

Displaying resource manager options . . . . . 22Using column names . . . . . . . . . . 24Resource column names . . . . . . . . . 24Design objects . . . . . . . . . . . . 30Requests . . . . . . . . . . . . . . 33Report objects . . . . . . . . . . . . 36Application column names . . . . . . . . 38Administration objects. . . . . . . . . . 40Using functions with column names . . . . . 41

Chapter 5. Exporting and importingobjects. . . . . . . . . . . . . . . 47The export syntax . . . . . . . . . . . . 47

Mandatory options . . . . . . . . . . . 47Additional options . . . . . . . . . . . 48Using mandatory links with elements . . . . 51Dividing results into multiple lines . . . . . 51

Including field separators. . . . . . . . . 52Including record separators . . . . . . . . 52Specifying a file name . . . . . . . . . . 53Specifying path locations . . . . . . . . . 53Removing the header . . . . . . . . . . 53

The import syntax . . . . . . . . . . . . 54Mandatory options . . . . . . . . . . . 55Using -colNames . . . . . . . . . . . . 55Including field separators. . . . . . . . . 56Including record separators . . . . . . . . 56Specifying file names . . . . . . . . . . 56Specifying path locations . . . . . . . . . 56Specifying input data . . . . . . . . . . 56Forcing the creation date . . . . . . . . . 57Reloading collectors . . . . . . . . . . 57Analyzing Tivoli Netcool Performance Managerobject . . . . . . . . . . . . . . . 57

Using a configuration file. . . . . . . . . . 58Line-by-Line explanation . . . . . . . . . 59

Chapter 6. Managing resources . . . . 71Working with elements . . . . . . . . . . 71

Exporting elements . . . . . . . . . . . 71Importing elements . . . . . . . . . . . 75Deleting elements . . . . . . . . . . . 78Working with subelements . . . . . . . . 78Exporting subelements . . . . . . . . . 78Importing subelements . . . . . . . . . 80Deleting subelements . . . . . . . . . . 83Working with groups or rules . . . . . . . 84Subelement group links . . . . . . . . . 84Exporting groups and rules . . . . . . . . 84Importing groups and rules . . . . . . . . 89Deleting . . . . . . . . . . . . . . 92Working with composite subelement rules . . . 93Working with nomenclature . . . . . . . . 93Using mandatory links . . . . . . . . . 97Using mandatory links with subelements . . . 100Using mandatory links with subelement groups 101Using mandatory links with inventory profiles 103Using mandatory links with nomenclature . . 104

Chapter 7. Managing design objects 105Working with formulas . . . . . . . . . . 105

Exporting formulas . . . . . . . . . . 105Importing formulas . . . . . . . . . . 107Deleting formulas . . . . . . . . . . . 108

Working with properties. . . . . . . . . . 108Subelement properties . . . . . . . . . 108Exporting properties . . . . . . . . . . 111Exporting property default values . . . . . 112Trouble Ticket pack properties . . . . . . . 113Properties used by the Tivoli NetcoolPerformance Manager-enabled SAA probes . . 113

Importing properties . . . . . . . . . . . 117

© Copyright IBM Corp. 2006, 2013 iii

Importing subelement properties . . . . . . 117Deleting subelement property . . . . . . . 118

Working with thresholds . . . . . . . . . 118Exporting thresholds . . . . . . . . . . 118Importing thresholds . . . . . . . . . . 119Deleting thresholds . . . . . . . . . . 119

Working with requests . . . . . . . . . . 119Exporting all requests . . . . . . . . . 119Exporting subelement group requests . . . . 120Exporting percentiles . . . . . . . . . . 121Importing requests . . . . . . . . . . 121Deleting requests . . . . . . . . . . . 122

Working with calendars . . . . . . . . . . 122Exporting calendars . . . . . . . . . . 122Importing calendars . . . . . . . . . . 123Deleting calendars. . . . . . . . . . . 123

Working with timezones. . . . . . . . . . 124Exporting timezones . . . . . . . . . . 124

Working with inventory profiles . . . . . . . 125Duplicating an inventory profile . . . . . . 125Importing inventory profiles . . . . . . . 126Deleting inventory profiles . . . . . . . . 126

Chapter 8. Managing administrationobjects . . . . . . . . . . . . . . 127Working with Tivoli Netcool Performance ManagerDataMart users and groups. . . . . . . . . 127

Exporting users and groups . . . . . . . 127Importing users and groups . . . . . . . 128Deleting users and groups . . . . . . . . 130

Working with registries . . . . . . . . . . 130Exporting registry objects . . . . . . . . 130Importing registries . . . . . . . . . . 137Deleting registries . . . . . . . . . . . 137

Working with miscellaneous Tivoli NetcoolPerformance Manager objects . . . . . . . . 137

Working with chnl (information about collector) 138Working with reg . . . . . . . . . . . 138Working with dbi . . . . . . . . . . . 139For limited use (checking for problems afterinstallation) . . . . . . . . . . . . . 140

Chapter 9. Managing report objects 143Working with web users. . . . . . . . . . 143

Exporting web user . . . . . . . . . . 143Importing web user . . . . . . . . . . 146Deleting web user . . . . . . . . . . . 147

Working with reporters . . . . . . . . . . 147Exporting reporters . . . . . . . . . . 147Importing reporters . . . . . . . . . . 153Deleting reporters and reporter stylesheets . . 154

Working with scheduler . . . . . . . . . . 155Exporting scheduler . . . . . . . . . . 155Importing scheduler . . . . . . . . . . 158Deleting scheduler. . . . . . . . . . . 158

Chapter 10. Managing history tableand sequence objects. . . . . . . . 159Working with history tables . . . . . . . . 159

Exporting history tables . . . . . . . . . 159

Importing and deleting . . . . . . . . . 162Working with sequences. . . . . . . . . . 162

Find and modify the start of indexes forformulas . . . . . . . . . . . . . . 162Find and modify the start of indexes forresources . . . . . . . . . . . . . . 162

Chapter 11. Configuring thresholds 163Thresholds . . . . . . . . . . . . . . 163

Threshold options . . . . . . . . . . . 163Deploying thresholds. . . . . . . . . . . 165

Threshold deployment against groups andresources . . . . . . . . . . . . . . 165Deploying "Non-differentiated" thresholds. . . 167Deploying differentiated thresholds . . . . . 169

Working with thresholds . . . . . . . . . 171Exporting thresholds . . . . . . . . . . 171Deleting thresholds . . . . . . . . . . 172Importing thresholds . . . . . . . . . . 173

Setting thresholds . . . . . . . . . . . . 175Identifying formula indexes . . . . . . . 175Setting a threshold against a group (dbIndex) 175Setting a threshold against a group (name) . . 176Setting a threshold against a resource (dbIndex) 176Setting a threshold against a resource (name) 177Setting a future threshold . . . . . . . . 177

Setting traps. . . . . . . . . . . . . . 178Setting burst traps . . . . . . . . . . . 178Setting period traps . . . . . . . . . . 180

Threshold troubleshooting scenarios . . . . . . 180Export scenario 1 . . . . . . . . . . . 180Export scenario 2 . . . . . . . . . . . 181Export scenario 3 . . . . . . . . . . . 182Export scenario 4 . . . . . . . . . . . 182

Chapter 12. Configuring timezones 185Working with timezones. . . . . . . . . . 185

Exporting timezones . . . . . . . . . . 185Deleting timezones . . . . . . . . . . 186Importing modifying,and creating timezones 186

Grouping links of subelements, calendars, andtimezones . . . . . . . . . . . . . . 187

Exporting links . . . . . . . . . . . . 187Deleting links . . . . . . . . . . . . 187Importing, modifying or creating links . . . . 188

Appendix A. Supported resmgroptions . . . . . . . . . . . . . . 191

Appendix B. Working with SAAprobes . . . . . . . . . . . . . . 195Exporting or importing an SAA probe . . . . . 195Exporting or importing an SAA probe with types 195Exporting or importing SAA probe attributes . . . 195Deleting SAA probes . . . . . . . . . . . 196Argument descriptions for SAA probe operations 196Listing subelement groups without resources . . . 198Finding and fixing nomenclature . . . . . . . 198

Listing devices not assigned to a nomenclaturegroup . . . . . . . . . . . . . . . 198

iv IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Correctly classifying a Tivoli NetcoolPerformance Manager object . . . . . . . 199Filtering subelements using the underscore (_) 199

Cutting and pasting in subelement group . . . . 199Finding the subelement group index . . . . 199Cutting the subelement group . . . . . . . 199Pasting the subelement group . . . . . . . 199Finding subelement groups without a parent 200Finding subelement groups with more than oneparent . . . . . . . . . . . . . . . 200Finding number of child groups for asubelement group . . . . . . . . . . . 201Checking subelement group request historytables . . . . . . . . . . . . . . . 201Checking the number of groups to which asubelement belongs . . . . . . . . . . 202Listing elements with empty SysName . . . . 203Finding number of collection requests persubelement . . . . . . . . . . . . . 203Filtering without case filter . . . . . . . . 204Finding the number of subelements in a family 204Grouping all the subelements . . . . . . . 204Displaying the classification of the xevice namedhcp200 . . . . . . . . . . . . . . 204Inserting in the past . . . . . . . . . . 205

Appendix C. CLI return codes . . . . 207snmpconf. . . . . . . . . . . . . . . 207

Standard output error messages . . . . . . 207reqedit. . . . . . . . . . . . . . . . 211

Return code . . . . . . . . . . . . . 211Standard output error messages . . . . . . 211

resmgr . . . . . . . . . . . . . . . 213Return code . . . . . . . . . . . . . 213Standard output error messages . . . . . . 213

inventory. . . . . . . . . . . . . . . 214Return code . . . . . . . . . . . . . 214Standard output error messages . . . . . . 215

impexp . . . . . . . . . . . . . . . 216Return code . . . . . . . . . . . . . 216Standard output error messages . . . . . . 217

Appendix D. Sample inventory script 219Sample inventory script . . . . . . . . . . 219

Appendix E. Using prerequisite checkscripts . . . . . . . . . . . . . . 225Using the check_os script . . . . . . . . . 225

Running the check_os script . . . . . . . 225Error messages . . . . . . . . . . . . 226

Using the check_db script . . . . . . . . . 227Tasks performed by the check_db script . . . 227Running the check_db script . . . . . . . 228

Notices . . . . . . . . . . . . . . 233

Contents v

vi IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

About this information

TheIBM Tivoli Netcool Performance Manager: Command Line Interface Guide help youuse the inventory and resmgr commands.

Intended audienceThe audience for this guide is as follows:v Tivoli Netcool Performance Manager Administratorsv Content designers

The Tivoli Netcool Performance Manager product suiteTivoli® Netcool® Performance Manager is made up of the following components:v Tivoli Netcool Performance Manager DataMart is a set of management,

configuration, and troubleshooting GUIs that the Tivoli Netcool PerformanceManager System Administrator uses to define policies and configuration, as wellas verify and troubleshoot operations.

v Tivoli Netcool Performance Manager DataLoad provides flexible, distributeddata collection and data import of SNMP and non-SNMP data to a centralizeddatabase.

v Tivoli Netcool Performance Manager DataChannel aggregates the data collectedthrough Tivoli Netcool Performance Manager DataLoad for use by the TivoliNetcool Performance Manager DataView reporting functions. It also processesonline calculations and detects real-time threshold violations.

v Tivoli Netcool Performance Manager DataView is a reliable application serverfor on-demand, web-based network reports.

v Tivoli Netcool Performance Manager Technology Packs extend the Tivoli NetcoolPerformance Manager system with service-ready reports for network operations,business development, and customer viewing.

© Copyright IBM Corp. 2006, 2013 vii

The following figure shows the different Tivoli Netcool Performance Managermodules.

Tivoli Netcool Performance Manager documentations consists of the following:v Release notesv Configuration recommendationsv User guidesv Technical notesv Online help

The documentation is available for viewing and downloading on the infocenter athttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.htm.

Network and Service Assurance community on Service ManagementConnect

Connect, learn, and share with Service Management professionals: product supporttechnical experts who provide their perspectives and expertise.

Access Service Management Connect at https://www.ibm.com/developerworks/servicemanagement/nsa/index.html. Use Service Management Connect in thefollowing ways:v Become involved with transparent development, an ongoing, open engagement

between other users and IBM developers of Tivoli products. You can access earlydesigns, sprint demonstrations, product roadmaps, and prerelease code.

v Connect one-on-one with the experts to collaborate and network about Tivoliand the Network and Service Assurance community.

viii IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.htm

https://www.ibm.com/developerworks/servicemanagement/nsa/index.html

https://www.ibm.com/developerworks/servicemanagement/nsa/index.html

v Read blogs to benefit from the expertise and experience of others.v Use wikis and forums to collaborate with the broader user community.

Tivoli technical trainingFor Tivoli technical training information, see the following IBM Tivoli Educationwebsite at http://www.ibm.com/software/tivoli/education.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineAccess the IBM Software Support site at http://www.ibm.com/software/support/probsub.html .

IBM Support AssistantThe IBM Support Assistant is a free local software serviceability workbenchthat helps you resolve questions and problems with IBM softwareproducts. The Support Assistant provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe Support Assistant software, go to http://www.ibm.com/software/support/isa.

Troubleshooting GuideFor more information about resolving problems, see the problemdetermination information for this product.

Conventions used in this publicationSeveral conventions are used in this publication for special terms, actions,commands, and paths that are dependent on your operating system

Typeface conventionsThis publication uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip:, and Operating system considerations:)

v Keywords and parameters in text

Italic

v Citations (examples: titles of publications, diskettes, and CDsv Words defined in text (example: a nonswitched line is called a

point-to-point line)v Emphasis of words and letters (words as words example: "Use the word

that to introduce a restrictive clause."; letters as letters example: "TheLUN address must start with the letter L.")

v New terms in text (except in a definition list): a view is a frame in aworkspace that contains data.

About this information ix

http://www.ibm.com/software/tivoli/education

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/isa

http://www.ibm.com/software/support/isa

v Variables and values you must provide: ... where myname represents....

Monospace

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Bold monospace

v Command names, and names of macros and utilities that you can typeas commands

v Environment variable names in textv Keywordsv Parameter names in text: API structure parameters, command

parameters and arguments, and configuration parametersv Process namesv Registry variable names in textv Script names

x IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Chapter 1. Introduction

The Tivoli Netcool Performance Manager Command Line Interface (CLI) helps youto manage Tivoli Netcool Performance Manager objects by using several utilities,including the Resource Manager (resmgr) and the inventory command.

Although Tivoli Netcool Performance Manager supports various CLI utilities, theseare the most commonly used and are therefore the focus of this information.

Special characters and command-line utilitiesWhen you use the command-line utilities (like resmgr, for example), make surethat you use a backslash (\) to escape characters that are special to the shell and tothe command line, especially the following chatacters:v [ ]v { }v `v "v \v $

Accessing CLI utilitiesThe CLI utilities reside in theTivoli Netcool Performance Manager DataMart andTivoli Netcool Performance Manager DataLoad bin directories.

Procedure1. On the system where DataMart is installed login as pvuser (or any user with

access rights to Tivoli Netcool Performance Manager)

Important: When you run the pvm command to access the DataMart for thefirst time, you must log in as pvuser.

2. Open a terminal window.3. For Tivoli Netcool Performance Manager DataMart command-line interfaces,

ensure that your environment is set by entering the following command:../dataMart.env

4. For DataLoad command-line interfaces, ensure that your environment is set byentering the following command:../dataMart.env

5. The CLI commands are in the bin directories where you installed DataMart andDataLoad.If you selected the defaults during the installation, the location of these bindirectories would be as follows:v DataMart

/opt/datamart/bin

v DataLoad/opt/dataload/bin

The following types of executable reside in these bin directories:

© Copyright IBM Corp. 2006, 2013 1

v Basic Utilities -- CLI commands like resgmr and inventory that perform basicTivoli Netcool Performance Manager administrative tasks.

v Conversion Utilities -- CLI commands that convert different database fileformats into the Tivoli Netcool Performance Manager DataMart format.

Note: The CLI utilities support a help option (-?) that explains how to use thecommand.

2 IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Chapter 2. Using the inventory command

Explains how to use the inventory command to manage inventory

Use the inventory command to manage your network inventory and performgrouping and debugging operations from the command line.

Invoked without arguments, the inventory command brings up the DataMartInventory Tool GUI, which is explained in detail in the IBM Tivoli NetcoolPerformance Manager: DataMart Configuration and Operation Guide .

You typically use the DataMart Inventory Tool to:v Run inventories against profiles newly created with the Inventory Wizard to

ensure that they work as expected.v Run an on-demand inventory.

The inventory command, by contrast, is typically placed in crontab to runcomplete or partial inventories or grouping operations on a regular basis as part ofa Tivoli Netcool Performance Manager deployment.

Thus, the best practice is first to create and debug an inventory profile using theDataMart Inventory Tool, and then to deploy the inventory and groupingoperations in crontab using the inventory command.

When a profile is run from the Inventory Tool GUI, the output goes to the UI andto the file PVMHOME/log/TraceInventory.log .

When a profile is run from the CLI, the output goes to the standard output device(terminal screen). If you want to save the inventory output, you must redirect theoutput to a file:inventory -noX ... > myInventory.log

Note: Appendix D, “Sample inventory script,” on page 219 contains a sample KornShell script that calls the inventory command. You can use this as a model foryour own inventory wrapper programs.

FunctionInventory Management Utility

Synopsisinventoryinventory [-D [DebugLevel]] [-U] [-name [profileName]][-action [operation]] [-reload [collectorNum]] [-noX] [-timeout] [-retry][-ip ipaddress] [-reportGrouping][cseEngine [-ruleFile ruleFile][-ruleSubSet ruleSubset]][-mode subProfile] [-?][-DList [CodeTracingModesList]][-DFile DebugOutputFile]]


DescriptionThe inventory command, which resides in the $PVMHOME/bin directory andsupports a number of inventory management operations, and is the command-lineequivalent of the DataMart Inventory Tool graphical utility.

For more information on using the DataMart Inventory Tool, see the IBM TivoliNetcool Performance Manager: DataMart Configuration and Operation Guide. Theinventory command is intended to be run from crontab, either called directly orfrom within a wrapper program.

Note the following:v If run without options, the inventory command invokes the DataMart Inventory

Tool.v If the -action option is not specified, the inventory command reads and

executes the settings saved by the DataMart Inventory Tool configuration file,$PVMHOME/res/C/inventory.res.

Important: Do not edit this file unless instructed to do so by IBM ProfessionalServices.

In very general terms, when a complete inventory is run, Tivoli NetcoolPerformance Manager does the following:1. Locks the specified inventory 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 inventory. If theinventory profile is already locked, inventory attempts to unlock the profile. Ifthe profile is running on the same host, inventory looks for the process. If theprocess does not exist, inventory removes the lock and proceeds. If the profileis running on a different host, inventory waits for the period specified by the-timeout option and then retries to remove the lock.

2. Initiates a discovery operation, and writes the results to the following directory:$PVMHOME/[importexport|importExportBulk]/ProfileName/inventory.An SNMP discovery operation consists of passing a list or range of IPaddresses and a set of specific discovery parameters (for example, timeout andnumber of retries) to the discovery server. The discovery server then executesthe discovery formulas against the specified devices, in collaboration with theSNMP collector, producing a set of files containing the list of discoveredresources and their attributes.

Note: If BULK mode (mode 3) is enabled, this discovery server only copies thediscovery files passed by the BULK collector.

3. Synchronizes the newly-discovered elements and sub-elements with theinformation stored in the database, then writes the newly synchronizedinformation to the database.The synchronization operation is broken up into the following two phases:v Pre-synchronization

Tivoli Netcool Performance Manager retrieves the list of elements andsubelements associated with the inventory profile from the database.

v SynchronizationTivoli Netcool Performance Manager compares either the set of elements andsubelements collected by the discovery operation (if SNMP) or the contentsof the bulk files (if BULK) to the set of elements and sub-elements in the


database. Several criteria are applied (such as invariants and the retirementpolicy) to determine if the discovered resources (and properties) are new,updated, or deleted.Tivoli Netcool Performance Manager retrieves the list of elements andsub-elements associated with the inventory profile from the database.The result of this comparison is then written back to the database.During the synchronization operation, the following two directories arecreated in the $PVMHOME/[importexport|importExportBulk]/ProfileNamedirectory:

synchroContains the successful results of the synchronization process that arethen written to the database.

synchroWaitContains a list of files that for a variety of reasons could not besynchronized and were not written to the database. If this directoryis populated, you should examine the files and determine the causeof failure.

v Tivoli Netcool Performance Manager compares the grouping of the files inthe synchro directory with the grouping rules specified in the inventoryprofile and writes the results to the following two directories in the$PVMHOME/[importexport|importExportBulk]/ProfileName directory:

v Tivoli Netcool Performance Manager extracts the information about thegroups for elements and sub-elements from the files in the groupingdirectory and inserts the information into the database.

4. Applies grouping rules to the synchronized elements and subelements, andwrites the results to the database.a. Tivoli Netcool Performance Manager compares the grouping of the files in

the synchro directory with the grouping rules specified in the inventoryprofile and writes the results to the following two directories in the$PVMHOME/[importexport|importExportBulk]/ProfileName directory:

groupingContains the successful results of the grouping process that are thenwritten to the database.

groupingWaitContains a list of files that for a variety of reasons could not begrouped and were not written to the database. If this directory ispopulated, you must examine the files and determine the cause offailure.

b. Tivoli Netcool Performance Manager changes the file extension on the filesas it processes them. If you want to re-run the grouping, change the fileextension back to .dat.

Note: By default, Tivoli Netcool Performance Manager saves the three mostcurrent versions of the grouped files. The number of copies saved isconfigurable. To change the number of copies saved, change thenumber_history parameter in $PVMHOME/res/C/inventory.res.

Note: By default, Tivoli Netcool Performance Manager saves the three mostcurrent versions of the grouped files. The number of copies saved isconfigurable. To change the number of copies saved, change thenumber_history parameter in $PVMHOME/res/C/inventory.res.

5. Unlocks the inventory profile.

Chapter 2. Using the inventory command 5

Note: When the inventory command runs, state information is constantlywritten to the file $PVMHOME/[importexport|importExportBulk]/ProfileName/state.

Options-? Prints a usage statement for the command.

-action [all|discovery|grouping|lock|pregrouping|presynchro|synchro]allSpecifies that the inventory command is to run all arguments to the -actionoption, executing a complete inventory and then grouping the results ofthe synchronized inventory.

Used in conjunction with the -name, -mode, -ip, or -cseEngine options.

discovery

Specifies that the inventory command is to run only the discovery phaseof the inventory process.

Used in conjunction with the -name, -mode, or -ip options.

grouping

Specifies that the inventory command is to run only the grouping phase ofthe inventory process.

Note: Before you can use this option, the results of a discovery must havebeen synchronized and pre-grouped.

lock Locks an inventory profile specified by the -name or -mode option. Unlessusing the all argument, you must manually lock an inventory profile.Note that you can use the lock argument in conjunction with the -retryand -timeout options when attempting to lock a profile that may alreadybe in locked by another process.

pregroupingSpecifies that the inventory command is to run only the pre-groupingphase of the inventory process.

presynchro

Specifies that the inventory command is to run the pre-synchronizationphase and partial sychronization of the inventory process.


Note: The presynchro option is useful for debuging or previewingpotential updates to the database. This option is not used to perform acomplete inventory process.'

synchro

Specifies that the inventory command is to run only the synchronizationphase of the inventory process.


Important: Before you can use either the synchro or the presychro options,the discovery option must be run.

-cseEngine [-rulefile ruleFile|-ruleSubSet ruleSubset]Runs the composite subelement (CSE) Engine to implement CSE rules andrule subsets. Pregrouping creates CSE groups and objects defined by CSE


rules. Grouping adds CSE groups and objects to the database. You can runthe pregrouping and grouping phases individually with the pregroupingand grouping options. You can implement both the pregrouping andgrouping phases together by running inventory cseEngine option asfollows:v Without optionsv With the -action "all" argumentsv With the -action "pregrouping grouping" arguments

-ruleFile ruleFileSpecifies 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 withoutspecifying the -ruleSubSet option runs all of the rule subsets in the rulefile.

-ruleSubSet ruleSubsetRuns a specified rule subset from the rule file. If you want to run morethan one rule subset, list each of the rule subsets separated only by acomma.

-date Deprecated.

-D DebuggingLevelTurns on debugging, with levels specified by DebuggingLevel. Supportedlevels are 1 to 10, with 10 outputting the most information. Default is towrite to standard error, unless the -DFile option is specified.

-DList string

Debugging option, used in conjunction with the -D option, that performscode execution traces. -DList sql, for example, returns only debuggingmessages related to SQL queries.

Do not use this option unless instructed to do so by IBM ProfessionalServices.

-DFile DebuggingFileInstructs the inventory command to write debugging information to thefile specified by DebuggingFile, rather than to standard error.

-ip IPAddressesSpecifies that the inventory command runs against up to five IP addressesin the command line, using a comma as a separator. If you want to specifymore than five IP addresses, list the addresses in a file and use the -modesubProfile 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 definedwithin the associated inventory profile.

-mode subProfileThe -mode subProfile option toggles the inventory command to run thediscovery on a subset of the entire inventory profile. The subset ofelements are listed in the file that is defined at the time of the creation ofthe inventory profile. This option is used by specifying -mode subProfilein the syntax of the inventory command.

This option allows you to reduce the time of the inventory by targetingonly those elements that are known to change frequently. A deployment


may, for example, elect to run an inventory against a subprofile once a day,while restricting a full inventory to once every month.

For more information on configuring profiles for use with the subProfileoption, see the Tivoli Netcool Performance Management DataMartConfiguration and Operation Guide.

-name profileName

Used in conjunction with the -action option. Instructs the inventorycommand to run against the profile specified by profileName.

You must not use any of the following reserved terms in the name of yourprofile:

elt inventory slowwan

exclude ipaddress snmpconf

fastlan lan subelt

filestoinsert mode subeltinv

grouping objectfilter synchro

icmp objectfilter wan

include rulefilter ||ROOTROOT||

-noX Instructs the inventory command to run as a command-line utility.

-reload CollectorNumber

Instructs the inventory command to reload the collector specified byCollectorNumber. The default is collector one (1). The inventory commandshould be called with this option set every time a profile or the resourcesin the profile have been changed. For more information, see the IBM TivoliNetcool Performance Manager: DataMart Configuration and Operation Guide .

You might, for example, write a wrapper that - among other things - waitsfor an event from the Discovery Server notifying it that a profile haschanged, and then calls the inventory command with the -reload optionset.

-reportGroupingInstructs the inventory command to run the report grouping rules andupdate the deployed reports stored in the database. Report grouping rulesmust first have been created before this option can be used. Forinformation on creating report grouping rules, see the IBM Tivoli NetcoolPerformance Manager: DataMart Configuration and Operation Guide .

-retry Used in conjunction with the -timeout option. Specifies the number oftimes to try to set a lock on a locked profile. The default is 1.

-timeoutUsed in conjunction with the -retry option. Specifies the length of time towait to try to lock a profile. The default is 60 seconds.

-U Deprecated

-versionLists version information for the inventory command.


ExamplesThe following example crontab entry illustrates how to use the inventorycommand in an actual Tivoli Netcool Performance Manager deployment.

The entry runs a full inventory (-all ) against a CBQoS profile after first reloadingSNMP collector 1.0 2,16 * * * [ -f /pv/dm/dataMart.env ] && [ -x/pv/dm/bin/inventory ] && \. /pv/dm/dataMart.env && inventory -name CBQoS -noX -actionall -reload 1 >> \/pv/dm/log/CBQoS.txt

Note: Appendix D, “Sample inventory script,” on page 219 contains a sampleKorn Shell script that calls the inventory command. You can use this as a modelfor your own inventory wrapper programs.


Chapter 3. The dccmd command

Use the dccmd command to stop and start DataChannel components, and to obtainstatus information about applications that are running on a DataChannel and itssubchannels.

Running the dccmd commandAbout this task

Run the dccmd command as follows:

Procedure1. Log in as pvuser to the server where the DataChannel is installed.2. Change your working directory to the DataChannel home directory (by default,

/opt/datachannel ), as follows:cd /opt/datachannel$

3. Set the DataChannel environment as follows:. ./dataChannel.env

4. Run the dccmd command.$ dccmd options

The dccmd command syntaxFunction

DataChannel Management Utility

Synopsisdccmd [-x] [-app pattern] [-host pattern] action [name_pattern] [parameters]

Description

The dccmd command is used to manage a DataChannel environment. Use the dccmdcommand to stop and start DataChannel components, and to obtain statusinformation about applications that are running on a DataChannel and itssubchannels.

Optionsaction [bounce|cstatus|forget|status|start|stop|usage|which]

bounce Stop and restart the selected components.

cstatusShow the cached status of the selected components. Each time the status isrequested for a component, that status is retained, and is reported by usingcstatus. The channel manager periodically requests the status of all runningcomponents. Such requests are normally issued about once per minute.Thus, requesting the cstatus generally shows the status of the selectedcomponents as of at most one minute in the past.

forget Remove the selected components from the list of components that must be


running maintained by Channel Manager. Components are removed fromthe list without stopping the component. If components on this list are notrunning, Channel Manager repeatedly attempts to restart them. ForcingChannel Manager to forget a component prevents Channel Manager fromautomatically restarting a component without actually stopping thecomponent.

status Report the status of the selected components. For each selected componentshow the component name, type (application), host name, status, andextended status (including the number of minutes since the extendedstatus was last updated).

start Starts the selected components. If the component ever fails, or is stoppedby any other means than the stop command, the Channel Managerattempts to restart it.

stop Stops the selected components.

usage Use without other arguments to print usage information for the command.

which name_patternLists the components that are selected by a specific pattern, applicationpattern, or host pattern. This action is useful for verifying the set ofcomponents that would be affected by some other action.

name_pattern identifies a set of components by their name. If the -x optionis specified, matching is performed by using regular expressions, otherwisesimple pattern matching is used. In addition to normal pattern matching,the special word all is interpreted to match any name (it is functionallyequivalent 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 reports an error).

If more than one pattern is specified, the set of components are thosecomponents that match all specified criteria. All pattern matching is notcase-sensitive.

Note: To prevent the shell from applying file name expansion, anypatterns that include special matching characters (such as "*", "?") must beenclosed in double quotation marks.

-x Use regular expressions for pattern matching (the syntax matches that ofthe Henry Spencer regex library). If specified, the application, host, andcomponent patterns use regular expression matching, otherwise, simplepattern matching is used. For simple matching, "*" matches any substringof characters and " #" matches any single character.

-app pattern -application patternRestricts the set of components to which the action applies to thoserunning an application that matches the pattern. For example, a pattern ofCME would apply the action to CME components only. Similarly,CME|LDR would match CME or LDR components (assuming the -xoption was specified). Components can be one of the following: BCOL,FTE, CME, LDR, DLDR, ALL, or *

Note: Users of certain Tivoli Netcool Performance Manager TechnologyPacks, including the Packs for the Alcatel 5620 NM and Cisco CWM, canalso control the Pack-specific modules with dccmd, by using the same start,stop, and other options. Pack-specific modules include the QCIF, CWMIF,BLB, and UBA applications.


-host pattern -hostname patternRestricts the set of components to which the action applies to thoserunning on a host whose name matches the pattern.

Example dccmd commandsShows how to perform more common DataChannel component management taskswith dccmd.

Start Individual Applications

The following table lists the DataChannel components and their start commands.

Application Command

CME dccmd start -app cme

Bulk Collector dccmd start -app bcol

FTE dccmd start -app fte

Hourly Loader dccmd start -app ldr

Daily Loader dccmd start -app dldr

View DataChannel Status

To view the status of a DataChannel, use the dccmd utility with the followingsyntax:$ ./dccmd status pattern

For example:$ dccmd status all$ dccmd status -app "disc"$ dccmd status cme.1.1$ dccmd status "*.1.*"

Chapter 3. The dccmd command 13

Chapter 4. Managing Tivoli Netcool Performance Managerobjects

Tivoli Netcool Performance Manager objects are the configuration data used by theTivoli Netcool Performance Manager system to define data collection andreporting. Resource Manager is a CLI tool that sits on top of the database and letsyou manage the configuration information contained in the database.

When you work with resmgr you are working from the command line, emulatingtasks you can perform using the Tivoli Netcool Performance Manager graphicaluser interface (GUI.) You can work from the command line to export and/orimport Tivoli Netcool Performance Manager objects to or from the database and toor from multiple Tivoli Netcool Performance Manager systems.

All Tivoli Netcool Performance Manager objects can be managed through resmgr.For example, you can use resmgr to manage the Tivoli Netcool PerformanceManager objects relating to a technology (MIBs, formulas, reports, grouping trees,thresholds and so on.)

Note: You can also use the Tivoli Netcool Performance Manager GUI to work withTivoli Netcool Performance Manager objects. Using the resgmr CLI lets you workwith Tivoli Netcool Performance Manager objects in bulk.

The resmgr command lets you work with resources (elements and subelements) aswell with the additional Tivoli Netcool Performance Manager objects described inthis chapter. With resmgr, you can:v Create resources when resources cannot be discovered from the network or

when resource information already exists in an inventory or provisioning systemand you do not need to rediscover this information.

v Delete resources from test systems. Deleting resources from production systemsis not recommended. Instead, resources are retired and historical informationpreviously collected remains in the database.

v Populate resources with additional properties. Tivoli Netcool PerformanceManager can work with both the technical properties discovered from thenetwork (MIBs) and the business properties generated by inventory andprovisioning. Business properties can include customer tagging, contract number,and a wide variety of organizational information.

v Manage Tivoli Netcool Performance Manager objects. You can replicateconfiguration information from system to system by using resmgr to exportTivoli Netcool Performance Manager objects to a file that you can then import toother Tivoli Netcool Performance Manager systems.


Understanding Tivoli Netcool Performance Manager objectsExplains the basics of Tivoli Netcool Performance Manager objects. It contains adescription of the objects, the categories to which they belong, and their databaseindex ranges.

About Tivoli Netcool Performance Manager objectsTivoli Netcool Performance Manager objects are the configuration data used by theTivoli Netcool Performance Manager system to define data collection andreporting.

The foundation of Tivoli Netcool Performance Manager objects are the resources.Resources are a type of physical or logical object managed by the Tivoli NetcoolPerformance Manager system. Any managed physical interface or port is aresource, any managed logical circuit is also a resource.

Resources include elements and subelements. Elements are managed nodes withaddresses or hosts, and subelements are subcomponents of an element, such as aport, interface, virtual circuits, user, or a DLCI.

Any object from which Tivoli Netcool Performance Manager can get identification(a name and a label) and related metrics can be modeled in the DataMart, usingthe resource concept.

Tivoli Netcool Performance Manager objects are grouped into the followingcategories:v Resources

– Elements and element groups– Subelements and subelement groups– Nomenclature

v Design– Formulas– Properties– Thresholds– Requests– Calendars– Timezones– Inventory profiles

v Administration– DataMart users and groups– Registry– Miscellaneous

v Report– Web users– Applications– Scheduler– History Table– Sequences


About Tivoli Netcool Performance Manager object typesEach Tivoli Netcool Performance Manager object includes multiple object types.The object types available for exporting and importing can sometimes differ.

Resource

The following table lists the different Tivoli Netcool Performance Manager objectsrelated to resources, along with the associated options for export and import.

Type Export Options Import Options

element v elt: element

v scf: SNMP configuration

v eprp: element property

v encl: nomenclature

v chnl: channel

v elt: element

v scf: SNMP configuration

v eprp: element property

v encl: nomenclature

subelement v se: subelement

v seprp: subelementproperty

v fam: family

v se: subelement

v seprp: subelementproperty value

v fam: family

v seproperty: subelementproperty description

group v segp: subelement group

v egp: element group

v segp: subelement group

v egp: element group

v linkGroupSE: link betweengroup of subelements andsubelement

v linkGroupSE_APP: linkbetween group ofsubelements and report

v linkGroupSE_RU: linkbetween group ofsubelements and reportuser

v linkGroupSE_TCZ: linkbetween group ofsubelements and timezoneand Calendar

v linkGroupE: link betweengroup of elements andelement

nomenclature v ngp: nomenclature group

v ncl: nomenclature

v vendor: vendor

v ngp: nomenclature group

v ncl: nomenclature

v vendor: vendor

v linkGroupN: link betweenthe group and thenomenclature

Design

Chapter 4. Managing Tivoli Netcool Performance Manager objects 17

The following table lists the different Tivoli Netcool Performance Manager objectsrelated to design components, along with the associated options for export andimport.


formulas v frm: formula

v fgp: formula

v mib: MIB

v frm: formula

v fgp: formula

v mib: MIB

property v propertyE: property ofelement

v propertySE: property ofsubelement

v propertyRU: property ofreport user

v propertyE: property ofelement

v propertySE: property ofsubelement

v propertyRU: property ofreport user

threshold v thrdv: threshold definition v thrdv: threshold definition

request v segpreq: request onsubelement group

v pctile: percentile

v segpreq: request onsubelement group

v pctile: percentile

calendar v cal: Calendar v cal: Calendar

timezone v tz: timezone v tz: timezone

inventory profile v ogp: group of inventoryprofiles

v opt: option of theinventory profile. Use withogp value.

v ogp: group of inventoryprofiles

v opt: option of theinventory profile. Use withogp value.

v linkGroupO: link betweengroup and options of theprofile

Report

The following table lists the different Tivoli Netcool Performance Manager objectsrelated to reports, along with the associated options for export and import.


web user v rusr: report (Web) user

v ruprp: report (Web) userproperty

v rugp: report (Web) usergroup

v rusr: report (Web) user

v ruprp: report (Web) userproperty

v rugp: report (Web) usergroup

v linkGroupRU: linkbetween group and thereport (Web) user



application v app: reporter

v agp: group of reporters

v appS: reporter style sheet

v app: reporter

v agp: group of reporters

v appS: reporter style sheet

v linkGroupAPP: linkbetween group andreporter

v linkGroupAPPS: linkbetween group andreporters; group and stylesheets

scheduler v sched: Scheduler v sched: Scheduler

Administration

The following table lists the different Tivoli Netcool Performance Manager objectsrelated to Administration components, along with the associated options for exportand import


DM user v usr: DataMart user v usr: Tivoli NetcoolPerformance ManagerDataMart user

registry v regisDM: DataMartregistry

v regisDC: DataChannelregistry

v regisDB: database registry

v regisDV: DataView registry

v regisMG: DataChannelManager registry

v regDesc: list of allregistries

v regInst: instances of allregistries

v regisDM: Tivoli NetcoolPerformance ManagerDataMart registry

v regisDC: Tivoli NetcoolPerformance ManagerDataChannel registry

v regisDB: Tivoli NetcoolPerformance Managerdatabase registry

v regisDV: Tivoli NetcoolPerformance ManagerDataView registry

v regisMG: Tivoli NetcoolPerformance ManagerDataChannel Managerregistry



others v pkg: all package tables

v reg: information aboutcomponent that arerunning (similar topvmstart)

v chnl: information aboutchannel

v client: registrationinformation about TivoliNetcool PerformanceManager clients

v dbi: export Tivoli TivoliNetcool PerformanceManager GUI informationinto CSV format

v err: list of Oracle errorstracked by TTivoli NetcoolPerformance Manager

v orausr: list of Oracle users

v pkg: all package tables

v reg: information aboutcomponent that arerunning (similar topvmstart)

v chnl: information aboutchannel

v client: registrationinformation about TivoliNetcool PerformanceManager clients

v dbi: export Tivoli NetcoolPerformance Manager GUIinformation into CSVformat

v err: list of Oracle errorstracked by Tivoli NetcoolPerformance Manager

v orausr: list of Oracle users

History Table

The following table lists the different Tivoli Netcool Performance Manager objectsrelated to history tables, along with the associated options for export and import


history table v calH: Calendar history

v frmH: formula history

v thrdvH: thresholddefinition history

v eltH: element history

v seH: subelement history

v segpreqH: subelementgroup request history

v appH: reporter history

v segpH: subelement grouphistory

v egpH: element grouphistory

v calH: Calendar history

v frmH: formula history

v thrdvH: thresholddefinition history

v eltH: element history

v seH: subelement history

v segpreqH: subelementgroup request history

v appH: reporter history

v segpH: subelement grouphistory

v egpH: element grouphistory

Sequences

The following table lists the different Tivoli Netcool Performance Manager objectsrelated to reports, along with the associated options for export and import



sequences v DesignIndex: sequence ofindexes used for TivoliNetcool PerformanceManager Design objectssuch as formulas,reporters, properties andso on.

v ResourcesIndex: sequenceof indexes used forresources (elements,subelements, and groups)

v DesignIndex: sequence ofindexes used for TivoliNetcool PerformanceManager Design objectssuch as formulas,reporters, properties andso on.

v ResourcesIndex: sequenceof indexes used forresources (elements,subelements, and groups)

Linking Among Tivoli Netcool Performance Manager objects

Links can exist among the Tivoli Netcool Performance Manager objects. The link isa logical link, most often between child and parent. However, links can also existbetween element and subelement, subelement and nomenclature.

Understanding Tivoli Netcool Performance Manager object IDsTivoli Netcool Performance Manager objects are internally identified by thedatabase by using numerical IDs.

You must review the following information about ranges before allocating databaseindexes. For example, database indexes are allocated when you install TivoliNetcool Performance Manager configuration objects that were created on onesystem onto a different system. Or when IBM delivers standard Technology Packsor customized reports and metrics.

The three ranges include:v From 0 to 50,000,000 - IDs of objects delivered by IBM as Technology Packs.v From 50,000,000 to 100,000,000 - IDs of objects delivered by IBM.v From 100,000,000 to 4,294,967,296 - IDs of objects created by each Tivoli Netcool

Performance Manager system when regular functions are used. For example,when using the Formula Editor to create new formulas, a new unique formulaID is created in that range. When using the Automatic Inventory module, newsub-elements and elements are created in that range. Resource Manager lets youcreate new objects and assign new database IDs to these new objects.

IBM does not support using resmgr to assign database IDs in the range from100,000,000 to 4,294,967,296. Creating database indexes in other areas such asranges from0 to 50,000,000 or from 50,000,000 to 100,000,000 should happen only with approvalof IBM support.


Working with resmgrExplains the basics of working with the resmgr CLI. Using resmgr lets you manageTivoli Netcool Performance Manager objects for automation and scripting purposeswithout interacting directly with the database schema.

It acts like an abstraction layer on top of the database schema, verifying andpreventing invalid interactions with the database.

Displaying resource manager optionsYou can display the command options available with resmgr by entering thefollowing command:resmgr -?

The command options that appear for your display might differ from the followingexamples because options are sometimes added and removed.

The following example shows a possible list of options that can appear.

Usage: resmgr [-D [DebugLevel]] [-noX] [-histoDate 1] [-noHead] [-ListForcedcol1 val1 ...] [-reloadCol] [-collectorList] [-sep separator] [-sepRec] [-fileFile Name] [-line] [-dirPath] [-filter filter ColNames] [-filterRule] [-colNames[col names list]] [-rule] [-order order ColNames] [-isMandat mandatory type][-split] [-isDefault] [-distinct] [-loadMemory] [-checkBeforeUpdate] [-modemode] [-config config Name] [-export type] [-import type] [-delete type][-analyze space] [-?] [-DList [CodeTracingModesList]] [-DFile [DebugOutputFile]][-version]-D : Output debugging information with optional debug level (1-10).-noX : Text mode.-histoDate : if 1 , use the date field for history-noHead : remove export header-ListForced : force the column1 ... to have a value-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(value) .." colname : same syntax as -colNames ;

value 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 valid only for export)

-colNames : list of col to export , import or delete. if empty give the list available 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


sub-elment : se, seprp, famgroup : segp, egpnomenclature : ngp, ncl, vendor* Design :formulas : frm fgp mibproperty : propertyE, propertySE, propertyRUthreshold : thrdvrequest : segpreq, pctilecalendar : caltimeZone : tzinventory profile : ogp optrule : rulegp, ruleprp* Report :web user : rusr, ruprp, rugpapplication : app agp appSscheduler : sched* Admin :DM user : usrregistry : regisDM regisDC regisDB regisDV regisMG regDesc regInstothers : pkg, reg, chnl dbmgr client dbi err orausr* History table :calH frmH thrdvH eltH seH segpreqH appH segpH egpH* Sequences :DesignIndex, ResourcesIndex.

-import : type =* Resources :elements : elt, scf, eprp, encl, epropertysub-elment : se, seprp, fam, sepropertygroup : segp, egp linkGroupSE linkGroupSE_APP linkGroupSE_RU

linkGroupSE_TZC linkGroupElinkGroupEGPnomenclature : ngp, ncl, vendor linkGroupN* Design :formulas : frm fgp linkGroupF linkMibFproperty : propertyE, propertySE, propertyRUthreshold : thrdvrequest : segpreq, pctilecalendar : caltimeZone : tzinventory profile : ogp opt linkGroupOrule : rulegp, ruleprp* Report :web user : rusr, ruprp, rugp linkGroupRUapplication : app agp appS linkGroupAPP linkGroupAPPSscheduler : sched* Admin :DM user : usr uLink uPermregistry : regisDM regisDC regisDB regisDV regisMGothers : pkg, reg, dbmgr* History table :calH frmH thrdvH 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-? : Give 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-version :

Example :. inventory profile :export : resmgr -export ogp -colNames "npath opt.name opt.instance opt.value" -file XXXimport : resmgr -import ogp -colNames "npath opt.name opt.instance opt.value" -file XXX


. report users :usersexport : resmgr -export rusr -colNames "name ruprp.name ruprp.value" -file XXXimport : resmgr -import rusr -colNames "name ruprp.name ruprp.value"

-line "users1|_|LongName|_|USERS 1|_|"group of usersexport : resmgr -export rugp -colNames "npath rusr.name" -file XXXimport : resmgr -import rugp -colNames "npath rusr.name" -line "~group1|_|users1|_|"users in group of Sub-Elementexport : resmgr -export groupSE -colNames "npath rusr.name" -file XXXimport : resmgr -import groupSE -colNames "npath rusr.name" -line

"~ cccccccc ~ddddd|_|users1|_|

Using column namesYou import and export detailed Tivoli Netcool Performance Manager objectinformation from the database in a format called column names (colNames).Columns names are fields that provide you with information about the TivoliNetcool Performance Manager objects. The column names used by resmgr arelogical 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 operationsperformed 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, theobject type for the action (-export) is used.

Resource column namesThe 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 Description

dbIndex Internal database index for the element.

name Name of the element (or new name).

typeThe element type. Available values include:

v snmp - defines an element for SNMPcollections

v default_snmp - used for SnmpConf (*.*.*.*)

v star_snmp - used for SnmpConf(@IPrange)

v import - defines a host with importeddata. No SNMP collections are available.

profil Name of the inventory profile used todiscover the element.

collector Number of the collector to which thiselement is assigned.

nclIdx Nomenclature index that allows link to encl,vendor.

missing Number of notFounds in the inventoryprocess.



commentDescription field.

The comment column name can also returninformation concerning resources that havebeen retired or deleted from inventory. Thereturned infomation for a retired resourceincludes the following:

"Action: Retired;Date: "dateOfDelete";Profile: "profileName";LastSee: "date";LastMissing: "missingNumber";Option: "missingCountInProfileLimiteDateInProfil"

Where:

v Action: Retired - Specifies that theresource has been retired.

v Date: "dateOfDelete" - Specifies whenthe resource was retired.

v Profile: "profileName" - Specifies thename of the inventory profile that wasused to discover the resource.

v LastSee: "date" - Specifies the date whenthe resource was last detected in theinventory.

v LastMissing: "missingNumber" - Specifiesthe number of times inventory has failedto detect the resource.

v Option: "missingCountInProfileLimiteDateInProfil" - Specifies the retrycount and age limit criteria defined in theinventory profile for deleting resources.

stateThe state of the element. Available valuesinclude:

v on

v off

The element is switched to off by theinventory process after a period of time anda number of retries defined in the inventoryprofile tool.

date Date that the element was inserted orupdated in the database, in number ofseconds since 1 January 1970.

user Name of the user who created this element.

origin The method used to add the element to thedatabase. (inventory, resmgr, and so on)

encl.name Name and generic type of the element.

encl.oid sysObjectID of the element

encl.gpname (only for export) Node type of the element

vendor.name (only for export) Vendor name of the element.

chnl.host only for export) Collector hostname



chnl.port (only for export) Collector port

chnl.type (only for export) Type of Collector (SNMP or Bulk)

eprp.name Name of the element property. Use thiscolumn name to export or import multipleproperties.

eprp.value Property value of the element. If thiscontains a value, "eprp.name" must containa value.

eprp.propertyname:valueThe value of a specific element property. Forexample, eprp.IpAddress:value is the valueof the ipAddress element property. Youcannot use spaces in the property name.

If you export using this column name, onlyelements that have a value for this columnare included in the output.

eprp.value Provides a list of all properties.

eprp.dataTypeData type of the property of the element.Available values are:

v string (default) - if this contains a value,eprp.name should also contain a value.

v float

eprp.prpIdx Property index

eprp.eltIdx Element index. Specifies the Database Indexfor the element associated with this SNMPconfiguration.

eprp.defValue Property default value

scf.ipaddress Specifies the IP address, mask, subnets, oraddress list for the device. This cannot beNULL if any of the other SNMPconfiguration (scf.) columns contain a value.

scf.wcommunity SNMP community name used for writing. Ifthis contains a value, "scf.ipaddress" mustcontain a value.

scf.rcommunity SNMP community name used for reading. Ifthis contains a value, "scf.ipaddress" mustcontain a value.

scf.timeout Length of time (in seconds) to wait for aresponse to a ping. If this contains a value,"scf.ipaddress" must contain a value.

scf.retries Number of times to re-try the request if itfails. If this contains a value, "scf.ipaddress"must contain a value

scf.port SNMP port for the element. If this contains avalue, "scf.ipaddress" must contain a value.

scf.version Specifies the SNMP version associated withthis SNMP configuration.

scf.vname Could classify the SNMP community name(use in internal for virtual router).



scf.colNb Identifies the collector associated with thisSNMP configuration. A setting of 0 appliesthe SNMP configuration to all collectors.

scf.bandwidth Specifies the maximum amount of traffic (inKbps) permitted for the corresponding IPaddress. For more information, see "SNMPBandwidth Control and CollectionSmoothing" in the IBM Tivoli NetcoolPerformance Manager: DataMartConfiguration and Operation Guide.

Subelement Column Names

The following table lists the subelement column names:


dbIndex Internal database index for the subelement

label Comment describing this subelement.(usually used in reports)

name Name of the subelement (or new name).

hostIdx element Index

instance String used for the requests (snmp get).

invariant Unique string value that defines thesubelement (can be a combination of severalproperties obtained in the MIB.)

missing Number of notFounds in the inventoryprocess

nclIdx Nomenclature index, which allows a link tofamily.

stateThe state of the subelement. Available valuesare:

v on

v off

The subelement is switched to off by theinventory process after a period of time anda number of retries defined in the inventoryprofile tool.

typeData Supply information on the invariant state,which is used in internal.

user UNIX name of the user who created thissubelement.

date Date that the element was inserted orupdated in the database, in number ofseconds since 1 January 1970.

origin The method used to add the sub-element tothe database. (inventory, resmgr, and so on.)

fam.name Description of the family name (Linked tothe discovery formula.)



seprp.name Name of the property of the subelement.Use this column name to export or importall (multiple) properties. Do not use spacesin the property name.

seprp.dataTypeSubelement property data type. Availablevalues are:

v string (default) - if this contains a value,seprp.name must contain a value.

v float

seprp.value Value of the subelement property. If thiscontains a value, "seprp.name" must alsocontain a value.

seprp.propertyname:value Value of a specific subelement property. Forexample, "seprp.Customer:value" is thevalue of the property Customer for thissub-element. Use this column name toexport or import a single property. If youexport using this column name, onlysubelements that have a value for thiscolumn are included in the output.

ulabelDescription field.

The ulabel column name can also returninformation concerning resources that havebeen retired or deleted from inventory. Thereturned infomation for a retired resourceincludes the following:

"Action: Retired;Date: "dateOfDelete";Profile:"profileName";LastSee: "date";LastMissing:"missingNumber";Option:"missingCountInProfile LimiteDateInProfil"

Where:

v Action: Retired - Specifies that theresource has been retired.

v Date: "dateOfDelete" - Specifies when theresource was retired.

v Profile: "profileName" - Specifies the nameof the inventory profile that was used todiscover the resource.

v LastSee: "date" - Specifies the date whenthe resource was last detected in theinventory.

v LastMissing: "missingNumber" - Specifiesthe number of times inventory has failedto detect the resource.

v Option: "missingCountInProfileLimiteDateInProfil" - Specifies the retrycount and age limit criteria defined in theinventory profile for deleting resources.


Group or Rule Column Names

The following table lists the group or rule column names:


dbIndex Oracle unique internal database index

npath Entire path of the group (including thegroup name)

name Group name

type Group type (rule, static, generated)

user User who has created the group or the rule

rule Index of a generated rule. (The Index rulethat has generated this group.)

cond Condition of the rule if it is a rule

state Either on or off for a rule. The rule is idlewhen off.

origin Group origin (imported, inventory)

date Group's creation date

lgParent Supplies only the parent group, not the leafgroup

lgChild Index of the child group

Nomenclature Column Names

The following table lists the nomenclature column names:


dbIndex Oracle's unique internal database index forthe nomenclature path.

npathThe path for this nomenclature.

For the vendor:

~Vendors~"vendorName"

For example, ~Vendors~3Com

For the node type:

~NodesType~"node type"~"Vendor"

For example, ~NodesType~Probe~Netscout

The nodeType must be the level -2.

Note: family is not grouped.

ncl.dbIndex Index of the nomenclature

ncl.name Name of the nomenclature

ncl.oid Object ID of the nomenclature, which mustbe unique for type SysObjectID



ncl.type Nomenclature type, which can includeSysObjectID (for encl), Vendor, ifType (forfamily)

Design objectsThe following tables list the column names used for the Tivoli NetcoolPerformance Manager objects related to design.

Formula Column Names

The following table lists the formula column names:



name Formula name

data Formula data

exprType Not used (included for compatibility with aprevious version)

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

curve Not used (included for compatibility with aprevious version)

nbHost Historic property, which must be set to 1

defValue Not used for formula

domaine Not used (included for compatibility with aprevious version)

invariant Not used for formula (only for property)

subType Not used (included for compatibility with aprevious version)

genericId Link to the generic formula Idx

user User who has created the formula (caninclude Apdev, pvuser and so on)

origin Origin of the formula. (can includeApinstall, resmgr, unknown, and so on.)

idxFrm Same index as dbIndex (link on the MIBtable)

mibPath Name of the MIB(s) used by the formula.

mibOrigin MIB origin. (can include Apinstall and soon.)

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:



npath Formula group path

nName Formula long name, which is thenpath~name

lgParent Supplies only the parent group (not the leafgroup)

LgChild Index of the child group

fgparent.name fgparent allowed to see the name or dbIndexof the parent group

Property Column Names

The following table lists the property column names.


dbIndex Oracle unique internal database index.

name Name of property (do not use spaces.)

dataType Type of properties (string/float.)

invariantDistinguishes among element, sub-element,and report user

When you use the keywords propertyE,propertySE, and propertyRU a filter isautomatically done respectively on type<E>,type<SE>, type<DVUser>.

state Not used (included for compatibility withprevious version.)

defValue Default value.

comment Description field.

Threshold Column Names

The following table lists the threshold column names.


IdxMetric | fgp.nName Metric Id (formula dbIndex) | Metric name(full path)

IdxGroup | segp.name Sub-Element Group Id (sub-element groupdbIndex) | Sub-Element Group name

IdxResource | se.name Sub-Element Resource Id (sub-elmentdbIndex) | Sub-Element Resource name


modeMode of the threshold

v 1 = Under

v 2 = Over

v 3 = Band

thrStatDefine which statistic will be used by theCME to calculate the threshold information:

v 0=raw(default)

v 1=min

v 2=max

v 3=avg

v 4=sum

v 5=count

v 6=squality

v 7=percentile

thrCalcThe calculation mode to be used todetermine percentage over/under thethreshold. Values for this field include:

v 0=standard means: abs(Value-Level)/abs(Level)

v 1=normalized means:abs(Value-Level)/(critical_level-warning_level)

v 2=scaled means: abs(Value-Level)/scalewhere scale = thrCalcValue

thrCalcValue The value used for calculating thepercentage over/under threshold in scaledmode.


brstCrtclLevel Level of the critical threshold for burstthresholds. Null implies that the thresholdisn't defined

brstWrnngLevel Level of the warning threshold for burstthresholds. Null implies that the threshold isnot defined.

brstCrtclTime Time limit for the critical period threshold inseconds. 0 indicates that the threshold isviolated when the metric exceeds thethreshold.

brstWrnngTime Time limit for the warning period thresholdin seconds

brstGenEventIndicates if Tivoli Netcool PerformanceManager has to generate events for theperiod threshold.

v 0=no

v 1=yes

prdCrtclLevel Level of the critical threshold for periodthresholds. Null implies that the threshold isnot defined


prdWrnngLevel Level of the warning threshold for periodthresholds. Null implies that the threshold isnot defined

prdCrtclTime Time limit for the critical period threshold inseconds

prdWrnngTime Time limit for the warning period thresholdin seconds

prdPeriodDefine the period:

v 1 = Day

v 2 = Week

v 3 = Month

v 4 = All means that the CME will use theperiod of the aggregation tables

prdGenEventWhether Tivoli Netcool PerformanceManager has to generate events for the burstthreshold.

v 0=no

v 1=yes

dteDate The date and time the action (STR_ACTION)takes effect. Actions cannot be applied in thepast and only take effect on the hour. Thevalue is in seconds since January 1, 1970GMT. Use instead of dteDate_DATE toconvert it to the following formatMM/DD/YYYY HH:mm.

RequestsThe following tables list the column names used for the Tivoli NetcoolPerformance Manager objects related to requests.

Subelement Group Requests

The following table lists the subelement group request column names.



idxRes Resource index or group index

idxFrm Formula index

state Request state (on or off.)

storage Request storage (always or never.)

status Request status (active or idle.)

period Collection period in seconds

idxCal Calendar used for the request

origin Request origin (can be resmgr or RequestEditor.)

user User who has created the request.

date Request creation date


Percentile Column Names

The following table lists the percentile column names.





state Request state, which can be on or off

status Request status, which can be active or idle

value Value of percentile parameter

Request Column Names

The following table lists the column names for all requests.





stateRequest state:

v on

v off

storageRequest storage:

v always

v never

statusRequest status:

v active

v idle

period Period of collection in seconds

idxCal Calendar used for the request

originRequest origin:

v resmgr

v Request Editor

user User who has created the request

date Date of creation of the request

typeType of the request

v collection

v aggregation

pctile Value of percentile parameter for the'aggregation' request type


Calendar Column Names

The following table lists the Calendar column names:



name Calendar name

period Polling period (for collection calendarobsolete)

stateState of the Calendar:

v on

v off

origin Origin of the Calendar

user User who created the Calendar.

dateCreation or last update date. Use instead ofdate_DATE to convert it to the followingformat:

MM/DD/YYYY HH:mm

typeType of Calendar line Available valuesinclude:

v 1 for daily

v 2 for monthly

v 3 for weekly

v 4 for once

subTypeSubtype value available for each kind ofCalendar. For example, available values fordaily calendar include:

v 1 for all days

v 2 for working days

v 3 for weekend days

week Define the days for the weekly calendar. Theseries begins on Sunday. Values include:

v 0 for off

v 1 for on

For example, a Calendar with Monday,Tuesday and Friday defined as on, displaysthe following field: 0 1 1 0 0 1 0.

fromDay Number for the first day of a monthlyCalendar

fromTime Define Calendar beginning time

toDay Number of the last day of a monthlyCalendar

toTime Define Calendar ending time


Timezone Column Names

The following table lists the timezone column names:


dbIndex Unique Oracle internal database indexnumber

name Unique timezone name (in this table)

offset Time lag from GMT in seconds

statusAggregation set (aggset) databaserepresentation status:

v 0: configured

v 1: created

v 2 active

Only active status (with all created in DB)can be used.

comment Optional description of the aggregation set

date Date when the aggset takes effect. Useinstead date_DATE to convert it to thefollowing format MM/DD/YYYY HH:mm

Inventory Profile Column Names

The following table lists the Inventory profile column names:


dbIndex Unique Oracle internal database index of thegroup

npath Path for this group as defined by the nameof the profile, followed by the step nameand the option group

opt.dbIndex Index of the inventory option

opt.name Name of the inventory option

opt.instance Instance of the option value, if one = 0, else0 = n. Required when an option has multiplevalues

opt.value Value of the option.

Report objectsThe following tables list the column names used for the Tivoli NetcoolPerformance Manager objects related to reports.

Web User Column Names

The following table lists the Web user column names:


dbIndex Unique Oracle internal database index


name Name of the report user

mail Email address of the user

typeType of report user:

v Tivoli Netcool Performance ManagerUSER

v EMAIL RECIPIENT

v DV SUPER USER

date Date that the report user was inserted orupdated in the database, in number ofseconds since 1 January 1970.

user Name of the user who created this reportuser.

ruprp.name Name of the property of the report user. Usethis column name to export or import all(multiple) properties. ruprp.value Propertyvalue of the report user. If this contains avalue, "ruprp.name" should also contain avalue.

ruprp.propertyname:valueThe value of a specific property of the reportuser. For example, "ruprp.IpAddress:value"is the value of the ipAddress property of thereport user. Do not use spaces in propertynames.

If you export using this column name, onlyreport users that have a value for thiscolumn are included in the output.

ruprp.value List of all properties

ruprp.dataTypeDatatype of the property of the report user.Available values include:

v string (default) - if this contains a value,ruprp.name should also contain a value.

v float

ruprp.prpIdx Property index

ruprp.ruIdx Report user index

ruprp.defValue Property default value

Report User Group Column Names

The following table lists the report user group column names:



npath Complete path of the group (including thegroup name)

name Name of the group

owner rusr with type=EMAIL RECIPIENT


Application column namesThe following table lists the application column names.



name Application name

url URL of the page that defines the visualcharacteristics of the report

comment Comment

typeReport type:

v 0 for ByResource

v 1 for ByGroup

typeRType of application

v Reporter(Report)

v DVCR(template)

v DVRS(scheduler)

data Binary stream that holds the reportproperties

owner Used by the scheduler

alias Used by the scheduler

date Date that the application was inserted orupdated in the database, in number ofseconds since 1 January 1970.

user Name of the user who created thisapplication.

app can be grouped in agp (report group)

Report Style Column Names

The following table lists the report style column names.



definition Report style definition

comment Report style comment

name Report style name

type Report style type. (Default value is 0)

appS can be grouped in agp (report group)

Application Group Column Names

The following table lists the application group column names.




npath Complete path of the group (including thegroup name)

name Group name

Scheduler Column Names

The following table lists the scheduler column names.


dbIndex ID of the scheduled task

name Name of the scheduled task

frequency Frequency of the scheduled task

user Name of the latest user who changed theapplication

date Date when the latest change occurred

idxTarget Target index. For example, reporter

idxShed Scheduled task index.

type Target type of the scheduled task. Forexample, DVCR for a reporter

stateState of the DVCR task:

v ACTIVE

v SUSPENDED

statusCurrent status of the scheduled task:

v SUSPEND

v STOP

v IDLE

Server_name>

start Timestamp that indicates the effective startdate when an ACTIVE task will run

end Timestamp that indicates the effective enddate when an ACTIVE task will no longerrun

success Timestamp that indicates the last time thisDVCR successfully ran

next Timestamp that indicates the next time thisschedule will run

failNb Parameter that indicates the number oftimes the schedule failed to successfullycomplete component processes

tuser Name of the latest user that changes theapplication

tdate Date when the latest change occurred


Administration objectsDM User Column Names

The following table lists the DM user column names.



name User name, which must match the UNIXlogin name

fullname User full name (description field)

gpname Group user name. Users belonging to thatgroup automatically inherit the group'srights.

gpcomment Group description

module Module names

perms Access rights

Registry Column Names

The following table lists the registry column names.


path Path of the registry

name Name of the registry

value Value for the registry

format Format (YYYY-MM-DD HH24:MI for a datefor example).

type v 0=NUMBER

v 1=STRING

v 2=DATE

v 3=BOOLEAN

flag v 0=CONSTANT

v 1=VARIABLE

Collector Information Column Names

The following table lists Collector information column names.


host The IP address or name of the Collectorassigned to collect data on the element.

port The TCP/IP port of the Collector assigned tocollect data on the element

collector Collector number to which this channel isassigned.

default Indicates whether the Collector is the default(yes or no).


name Name of the registered module. Forexample, pvmd_1

pid Protocol identifier (pid) of the registeredmodule

user User who launches the registered module.

date Date of the launching of the registeredmodule. Use instead date_DATE to convertit to the following format MM/DD/YYYYHH:mm

display Display host where the registered module isrunning.

status Status of the registered module.

instDir Home directory path

comment Description of the module

hostReg Host name in the registry

Registration Column Names

The following table lists the registration column names.


name Name of the registered module.

host Host that is running the registered module

pid Protocol identifier (pid) of the registeredmodule

user User who launches the registered module.

date Date of the launching of the registeredmodule. Use instead date_DATE to convertit to the following format MM/DD/YYYYHH:mm

display Display host where the registered module isrunning.

port Used only for the server (pvmd orprovisoinfod).

lock Name of the locked module

mode 1 for r/w

Using functions with column namesExplains how to use functions with column names. These functions extend the useof column names, providing additional actions on the data sets.

The following table lists the functions available for use with column names.

Function Description

DECODE Converts an enumeration integer value intoa string

UPPER Converts string types into upper case

LOWER Converts string types into lower case


TIME Use only on time values to transform thenumber of seconds into xxd xxh xxm xxs(day, hour, minute, second)

DATE Use only on a date value to transform anumber of second since 1970 in readableformat. convert it to the following formatMM/DD/YYYY HH:mm

COUNT, MAX, MIN, SUM Use with numerics. For example, count thenumber of subelements belonging to anelement. Another example, sum of all thecolumns that do not have aggregationvalues.

Using the DECODE functionThe following examples of the DECODE function convert enumeration integer valuesinto strings. You can use DECODE to make a file easier to review.

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 Conversations with CoS.|_|1|_|<E>Top N Host Conversations with No CoS|_|1|_|<E>

The following example shows the use of the DECODE function along with theexport 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 Conversations with CoS.|_|ByGroup|_|<E>Top N Host Conversations with No CoS|_|ByGroup|_|<E>

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>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>

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 functionYou can use the UPPER function with any string type to convert results into uppercase.

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|_|

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|_|

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 functionYou can use the LOWER function with any string type to convert results into lowercase.

Using the TIME functionYou can use the TIME function on time values to transform the number of secondsinto xxd xxh xxm xxs (day, hour, minute, second)

The following command:resmgr -export thrdv -colNames "fgp.nName segp.npathbrstCrtclLevel brstCrtclTime" -filter "brstCrtclTime(!=’0 ’)"

Generates the following output:~AP~Generic~Universal~Other~Inbound Loss (percent)|_|~NOC Reporting|_|14|_|-1|_|~AP~Generic~Universal~Utilization~Storage Utilization (percent)|_||_|99|_|7200|_|~AP~Generic~Universal~Utilization~Storage Free (bytes)|_||_|160000|_|3600|_|

The following command:resmgr -export thrdv -colNames "fgp.nName segp.npathbrstCrtclLevel brstCrtclTime_TIME" -filter "brstCrtclTime(!=’0’)"

Generates the following output:~AP~Generic~Universal~Other~Inbound Loss (percent)|_|~NOC Reporting|_|14|_|RESERVED|_|~AP~Generic~Universal~Utilization~Storage Utilization (percent)|_||_|99|_|2h|_|~AP~Generic~Universal~Utilization~Storage Free (bytes)|_||_|160000|_|1h 2m|_|

The following command:resmgr -export thrdv -colNames "fgp.nName segp.npathbrstCrtclLevel brstCrtclTime" -filter "brstCrtclTime(!=’0’)" -file$DIR/TIME_NO.dat

Generates the following output:# type = thrdv# col = fgp.nName segp.npath brstCrtclLevel brstCrtclTime# filter = brstCrtclTime(!='0')# order =# sep = |_|# sepRec =## cmdLine = -export thrdv -colNames "fgp.nName segp.npath brstCrtclLevel brstCrtclTime"-filter "brstCrtclTime(!='0')"~AP~Generic~Universal~Utilization~Inbound Utilization (percent)|_|~Customer Facing Reporting|_|10|_|900|_|~AP~Generic~Universal~Utilization~Outbound Utilization (percent)|_|~Customer Facing Reporting|_|10|_|900|_|~AP~Generic~Universal~Utilization~Storage Utilization (percent)|_|~Tivoli Netcool Performance Manager System Monitoring|_|99|_|7200|_|~AP~Generic~Universal~Utilization~Storage Free (bytes)|_|~Tivoli Netcool Performance Manager System Monitoring|_|160000|_|3600|_|~AP~Generic~Universal~Availability~Availability (percent)|_|~Customer Facing Reporting|_|90|_|900|_|~AP~Generic~Universal~Other~Inbound Loss (percent)|_|~Customer Facing Reporting|_|1|_|900|_|~AP~Generic~Universal~Other~Outbound Loss (percent)|_|~Customer Facing Reporting|_|1|_|900|_|

The following command:resmgr -export thrdv -colNames "fgp.nName segp.npathbrstCrtclLevel brstCrtclTime_TIME" -filter "brstCrtclTime(!=’0’)"-file $DIR/TIME_YES.dat


Generates the following output:# type = thrdv# col = fgp.nName segp.npath brstCrtclLevel brstCrtclTime_TIME# filter = brstCrtclTime(!='0')# order =# sep = |_|# sepRec =## cmdLine = -export thrdv -colNames "fgp.nName segp.npath brstCrtclLevel brstCrtclTime_TIME"-filter "brstCrtclTime(!='0')"~AP~Generic~Universal~Utilization~Inbound Utilization (percent)|_|~Customer Facing Reporting|_|10|_|15m|_|~AP~Generic~Universal~Utilization~Outbound Utilization (percent)|_|~Customer Facing Reporting|_|10|_|15m|_|~AP~Generic~Universal~Utilization~Storage Utilization (percent)|_|~Tivoli Netcool Performance Manager System Monitoring|_|99|_|2h|_|~AP~Generic~Universal~Utilization~Storage Free (bytes)|_|~Tivoli Netcool Performance Manager System Monitoring|_|160000|_|1h|_|~AP~Generic~Universal~Availability~Availability (percent)|_|~Customer Facing Reporting|_|90|_|15m|_|~AP~Generic~Universal~Other~Inbound Loss (percent)|_|~Customer Facing Reporting|_|1|_|15m|_|~AP~Generic~Universal~Other~Outbound Loss (percent)|_|~Customer Facing Reporting|_|1|_|15m|_|

Using the DATE functionYou can use the DATE function on a date value to transform the number of secondssince 1970 into the following, readable format: MM/DD/YYYY HH:mm

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|_|

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|_|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|_|testInv1|_|Cisco Catalyst|_|2|_|192.168.69.245|_|testInv1|_|Cisco Catalyst|_|2|_|bulk100-boston_0|_|bulk_100|_||_|10|_|

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 functionsYou can use these functions

The following command:resmgr -export se -colNames "elt.name elt.profil encl.gpname se.name_COUNT" -file $DIR/COUNT.dat

Generates the following output:

# 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 5. Exporting and importing objects

Explains how to use the resmgr command to import and export objects.

The export syntaxThis section explains the syntax used for the export option of the resmgr command.You must include the mandatory options with the resmgr -export command andadd other options for additionalresmgr -export <object type> <mandatory options><additional options>

Mandatory optionsYou must use the following options when issuing a resmgr -export command.

Option Description

<object type>name(is null)

name(not null)

-colNamesa list of colNames. If no value is used withthe CLI and a default value exists, thedefault value is used.

If you do not want to use the -colNameoption because you want to format thecolumns, use -rule.

-rule a string using the colNames with thesyntax%(colname). Use to format thecolumns (need to use if you do not use-colNames.)

The following example shows the use of the -rule option with a mix of text andvariable to specify the format for the columns. This modifies the construction ofthe 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 topics thatcontain specific commands for additional examples ofmandatory options.


Additional optionsYou can use the following additional options with the export option.

Option Description

-filter Filter the results of the export command

-filterRuleBroaden your filtering capabilities byentering a string against which results arecompared to find matches.

The syntax of the filter string is similar tothe syntax of an SQL WHERE clause, so thatyou can filter on common SQL keywordssuch as OR, AND, LIKE, IN, and so forth.

-order List columns in order

-distinct Eliminate duplicate lines

-ListForced Force columns to display values

Using -filter

The following option lets filter the results of the export command.-filter

List of filtered values "colname(value) ..", same syntax as -colNames. Lets you filterthe results of a command.

The following table lists available -filter values:

Values Examples

is null, not nullname(is null)

name(not null)

Any character with * (like operator is used) name(*ddd*)

Any character (= operator is used) name(ddddd)

Relational operator (in,between,!=,>,<,..) 'anycharacter'

AND is made between filters

name(!='ddd')

number(<='10')

name(in'ddd','aaa','bbb')

between('0 and 3')

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|_|




Using -filterRuleAbout this task

You can use the following filter option if you need to broaden your filteringcapabilities; for example if -filter is too restricted. You can enter a string againstwhich results are compared to find matches.-filterRule "string"

Note: The syntax of the filter string is similar to the syntax of an SQL WHEREclause, so that you can filter on common SQL keywords such as OR, AND, LIKE,IN, and so forth.

Example 1resmgr -export elt -colNames "name profil state" -filterRule"%(elt.profil) LIKE ’%T%’ OR %(elt.state) = ’on’" -file$DIR/filterRule1.datarketing.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) isconsidered one character. If you need to use the underscore in your filter, you mustinclude an escape character for it.resmgr -export elt -colNames "name profil state" -filterRule"%(elt.profil) LIKE ’%T%’ OR %(elt.state) = ’on’" -file$DIR/filterRule1.datmarketing.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 '@' tellsORACLE 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.datNF-iphost-site-flow-CoffeeBucks|_|NF_protocol|_|NF-site-Silver-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|_|NF-site-site-flow-CoffeeBucks|_|NF_protocol|_|NF-site-site-flow-Gold-CoffeeBucks|_|NF_protocol|_|NF-site-iphost-flow-Silver-CoffeeBucks|_|NF_protocol|_|NF-iphost-site-flow-Silver-CoffeeBucks|_|NF_protocol|_|

The name is filter in "*_protocol*"

Chapter 5. Exporting and importing objects 49

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 logicalentities (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|_|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 1bulk_100|_|test2|_|testInv1|_|testNoReload|_||_|

Using -ListForced

You can use the following option to force columns to display values.-ListForced "column1 value1 [column2 value2] ... [columnN valueN]"


Use this option with the following Tivoli Netcool Performance Manager objecttypes:v eprpv seprpv ruprpv encl.namev fam.name

Exampleresmgr -ListForced "seprp.Customer:value \"\" seprp.Cos:value \"\""-export se -colNames "elt.name name label seprp.Customer:valueseprp.Cos:value"router1|_|router1_interface<1>|_|Ethernet[1]|_|CocaCola|_|Gold|_|router1|_|router1_interface<2>|_|Ethernet[3]|_||_||_|router2|_|router2_interface<1>|_|Ethernet[1]|_|AirFrance|_||_|router2|_|router2_interface<2>|_|Ethernet[2]|_||_|Silver|_|router2|_|router2_interface<3>|_|Ethernet[3]|_||_||_|resmgr -export elt -colNames "name eprp.Contact:value" -ListForced"eprp.Contact:value \"\""192.168.69.245|_||_|Delete_200000092_192.168.127.1|_||_|Delete_200000098_192.168.127.7|_||_|192.168.69.243|_||_|

Using mandatory links with elementsAbout this task

You can use the following option to force a link to be mandatory (or not). Use forelt: scf,encl,eprp.

See Chapter 6, “Managing resources,” on page 71 for more information.

Dividing results into multiple linesAbout this task

You can divide results into multiple lines using the following option:-split

Use only with eprp, seprp, ruprp

Divide results into multiple linesresmgr -export elt -colNames "name eprp.name eprp.value" -split-file $DIR/split_elt.dat172.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.value" -file$DIR/splitno_elt.dat172.31.0.31|_|ipAddress|_|172.31.0.31|_|ipName|_|172.31.0.31|_|physAddress|_|6.0.3.227.233.33.160|_|sysDescr|_|Cisco

Internetwork Operating 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 Operating System Software \nIOS (tm) C2600 Software(C2600-T|_|sysName|_|"c2610-41-LSR"|_|

Including field separatorsAbout this task

You can include field separators between fields when you export data (and importas well.) The default separator value is an underscore (|_|.) When you use a fieldseparator from the command line, you need to enclose it in single (' ') or doublequotes (" ").

-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 separatorsAbout this task

You can include record separators when you export data. The default recordseparator value is "end of line." You can also use the is Mandatory value whencolNames such as app or frm could potentially include the end of line in theirfield.

-sepRecresmgr -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,;bulk100-boston_100,13,bulk_100,on,;bulk100-boston_100,14,bulk_100,on,;

Specifying a file nameAbout 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. Ifyou need to include a path, you can use the -dirPath option or set the entire pathenclosed in double quotes (" ".) You can also enter the entire path for a file togetherwith the filename.

-file

resmgr -export elt -colNames "name profil state" -file test1

Specifying path locationsAbout 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 ifyou also want to specify the name of the file. Remember to enclose the path insingle (' ') or double quotes (" ".)

-dirPath

resmgr -export elt -colNames "name profil state" -file test1-dirPath "/tmp"

Create the file:/tmp/test1.

Removing the headerAbout this task

useful when scripting and pipe to other tools

-noHead

Remove the header for exportresmgr -export elt -colNames "name" -noHead -file $DIR/noHead.dat172.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 with headersresmgr -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 headersresmgr -export elt -colNames "name" -noHead | wc -l23

The import syntaxImport (insert or update) metadata. This option lets you specify the type (objecttype) of data for importing.resmgr -import <object type> -mode [insert|update|Ifirst]


Mandatory optionsYou must use the following options when issuing a resmgr import command.

Option Description

<object type>name(is null)

name(not null)

-colNamesa 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 v insert - insert only. Use this value if youare importing a large amount of new datainto the database. If the resource alreadyhas a value for this column, it is notupdated.

v update - update only. If the resource doesnot have a value for this column, data isnot inserted.

v Ifirst - insert first (default). First attemptto insert. If the resource already has avalue for this column, the value isupdated.

Using -colNamesAbout this task

Use to display a list of colName or colName(value).

Example 1

The value 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.rgrImporBulk|_|aaaa|_|import_|_|on|_|.....

Example 2

The value of the colNames can be concatenation of multiple values taken in the file(the value given is take for all lines.)resmgr -import elt -colNames "name col1 col2 type stateprofil(myProf%(col1)_%(col2)) collector(3)" -file Test1.rgrImporBulk|_|val1|_|val2|_|import_|_|on|_|.....

Example 3

You can use the option OLD_colname when updating the colname used as anindex for finding the record.resmgr -import elt -colNames "OLD_name name" -line"NameNow|_|NewName"


Including field separatorsAbout this task

You can include field separators between fields when you import data (and exportas well.) The default separator value is an underscore (|_|.) When you use a fieldseparator from the command line, you need to enclose it in single (' ') or doublequotes (" ").-sep

Including record separatorsAbout this task

You can include record separators when you export data. The default recordseparator value is "end of line." You can also use the isMandatory value whencolNames 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 namesAbout 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 beUNIX 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 theentire path for a file together with the filename.-file

Specifying path locationsAbout 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 youalso want to specify the name of the file. Remember to enclose the path in single ('') or double quotes (" ".)-dirPath

Specifying input dataAbout this task

You can specify input data from the command line.-lineresmgr -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


Forcing the creation dateAbout this task

You can force the creation date stamped.-histoDate

v 0: current date (not forced default value)v 1: force the date to the value defined

Exampleresmgr -import se -colNames "name elt.name instancedate(1057015945)" -histoDate 1Import the se at : 07/01/2003 01:32

Reloading collectorsAbout this task

You can reload the collectors.-reloadCol val

Reload Collectors = on|off|forced (default = on ).

Available values are as follows:v on (default) - reload collectors to reread the database for changes or updatesv off - do not reload collectorsv forced - always reload collectors

Examplesresmgr -import ..... -reloadCol offresmgr -import ..... -reloadCol onresmgr -import ..... -reloadCol forced

You are only allowed to reload only the last time even if there were no changes inthe last import.

The resyncronization messages you see after entering this command will varyaccording to the exact metadata change that are made by the command.

Analyzing Tivoli Netcool Performance Manager objectAbout this task

You can generate an analysis of the resource tables for the following Tivoli NetcoolPerformance Manager objects:v eltv sev egpv segp-analyze <object type>

Exampleresmgr -analyze seInfo : === ANALYZE : ON se (Synchro)


Using a configuration fileAbout this task

You can create a configuration file with sets of commands and options that youwant to execute more than once. Many of the options in Resource Manager can beused in a configuration file.

You can specify different combination of commands and options in a configurationfile. You can specify multiple configurations by using keywords.

Note: If you specify an option both in a configuration file and from the commandline, the command line overrides the configuration file.

An example of a configuration file:

To run a configuration file, enter:


Line-by-Line explanation*exportAll_List: exportE exportSEL

This line specifies a list of configurations. When you specify exportAll on thecommand line for the -config option, the configurations are executed

Item Description Syntax Requirements

* Indicates the beginning of anoperative line.

Should be the first characteron the line. Spaces before arenot allowed and spaces afterare optional.

exportAll The name of theconfiguration. This is thename that should bespecified on the commandline with the -config option.All the lines that begin withthis configuration name arerun at the same time.

Letters and numbers areallowed.

Spaces are not allowed.

Using a meaningful name isrecommended.

_ Separates the configurationname from the commandline option or keyword.

Spaces are not allowedbefore or after.

List A keyword to indicate that alist of other configurations inthe file follows.

"L" must be capitalized.

: Separates the keyword fromthe list of configurationnames.

Spaces before and after areoptional.

exportE The name of anotherconfiguration in the file.

Multiple names are allowedand spaces between eachname are required.

exportSEL The name of anotherconfiguration in the file.

Multiple names are allowedand spaces between eachname 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 exportelements. The equivalent command line is as follows:-export elt

Since the exportE configuration is part of the list for the exportAll configuration onthe previous line, this configuration is run by specifying either exportAll orexportE for the -config option on the command line.



* Indicates the beginning of anoperative line. Should be the first character

on the line.

Spaces before are notallowed.

Spaces after are optional.

exportE The name of theconfiguration. This is thename that should bespecified on the commandline with the -config option.All the lines that begin withthis configuration name arerun at the same time.




_ Separates the configurationname from the commandline option or keyword


operation A keyword to indicate thatwhat follows is an operation.

Should be all lower case.

: Separates the keyword fromthe operation


export The operation, in this caseexport. Valid values areimport, export, and delete.

Spaces are required betweenthe operation and the type ofresource should be alllowercase.

elt The type of resource, in thiscase elements. Any valuesthat are valid on thecommand line are also validin a configuration file.

Spaces are required betweenthe operation and the type ofresource.

Capitalization must be thesame as on the commandline.

*exportE_colNames: name comment

This line specifies that the column names to be exported are "name" and"comment." The command line equivalent is:-colNames "name comment"



on the line.










colNames A command line option. Inthis case, -colNames.Command line options arelisted under “Displayingresource manager options”on page 22.

No hyphen before theoption.

Capitalization needs to bethe same as on the commandline.

: Separates the command lineoption from its value.


name A column nameCan be any valid columnname. See “Using columnnames” on page 24 for thelist of possible columnnames.

Multiple column names areallowed.

Spaces are required betweeneach of the column names inthe list.

comment A column nameCan be any valid columnname. See “Using columnnames” on page 24 for thelist of possible columnnames.



*exportE_file: elements

This line specifies that the name of the output file is "elements." The command lineequivalent is:-file elements




on the line.





Spaces are not allowed

using a meaningful name isrecommended.



file A command line option. Inthis case, -file. No hyphen before the

option.




elements The name of the file inwhich to place the exporteddata.

Should be only the file name.If a path is required use thedirPath option,

*exportE_dirPath: ./output

.

*exportE_dirPath: ./output

This line specifies that the path for the output file is "./output" The equivalentcommand line is:-dirPath "./output"


* Indicates the beginning of anoperative line.



Letters and numbers areallowed. Spaces are notallowed.



_ Separates the configurationname from the commandline option or keyword


dirPath A command line option. Inthis case, -dirPath. Commandline options are listed under“Working with resmgr” onpage 22.





./output The path for the file in whichto place the exported data. Specify only the path.

Specify the name of the filewith the file option.

The directory needs to existbefore executing thecommand. If the directorydoes not exist, the commandfails.

!-----------------------------------------

! 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 thecommand line for the -config option, all of the configurations listed on the rightare executed together.

Because the exportSEL configuration is part of the list for the exportAllconfiguration on the first line, this configuration is run by specifying eitherexportAll or exportSEL for the -config option on the command line.



on the line.



exportSELThe name of theconfiguration. This is thename that should bespecified on the commandline with the -config option.

All the lines that begin withthis configuration name arerun at the same time.







List A keyword to indicate thatwhat follows is a list of otherconfigurations in the file.

"L" must be capitalized.

: Separates the keyword fromthe list of configurationnames.


exportSE The name of anotherconfiguration in the file. Multiple names are allowed.

Spaces between each nameare required.

exportSEM The name of anotherconfiguration in the file. Multiple names are allowed.

Spaces between each nameare required.

*exportSE_operation: export se

This line specifies that the operation for the exportSE configuration is exportsub-elements. The equivalent command line is:-export se



on the line.



exportSE The name of theconfiguration. This is thename that should bespecified on the commandline with the -config option.All the lines that begin withthis configuration name arerun at the same time.








: Separates the keyword fromthe operation.


export The operation, in the caseexport. Valid values areimport, export, and delete.

Spaces are required betweenthe operation and the type ofresource must be alllowercase.


se The type of resource, in thiscase sub-elements. Anyvalues that are valid on thecommand line are also validin a configuration file.



*exportSE_colNames: name date

This line specifies that the column names to be exported are "name" and "date."The equivalent command line is:-colNames "name date"



on the line.









colNames A command line option. Inthis case, -colNames.Command line options arelisted in “Working withresmgr” on page 22.





name A column nameCan be any valid columnname. See “Using columnnames” on page 24 for thelist of possible columnnames.




date A column nameCan be any valid columnname. See “Resource columnnames” on page 24 for thelist of possible columnnames.



*exportSE_file: subel1

This line specifies that the name of the output file is "subel1." The equivalentcommand line is:-file subel1



on the line.









file A command line option. Inthis case, -file. Commandline options are listed in“Working with resmgr” onpage 22.





subel1 The name of the file inwhich to place the exporteddata.

Should be only the file name.If a path is required use thedirPath option.

*exportSEM_operation: export se

This line specifies that the operation for the exportSEM configuration is exportsub-elements. The equivalent command line is:-export subElt




on the line.



exportSEM The name of theconfiguration. This is thename that should bespecified on the commandline with the -config option.All the lines that begin withthis configuration name arerun at the same time.








: Separates the keyword fromthe operation.


export The operation, in the caseexport. Valid values areimport, export, and delete.


Needs to be all lowercase.

se The type of resource, in thiscase sub-elements. Anyvalues that are valid on thecommand line are also validin a configuration file.



*exportSEM_colNames: name instance

This line specifies that the column names to be exported are "name" and "instance."The equivalent command line is:-colNames "name instance"

Item Purpose Syntax Requirements

* Indicates the beginning of anoperative line




Letters and numbers areallowed. Spaces are notallowed.




colNames A command line option. Inthis case, -colNames.

No hyphen before theoption. Capitalization mustbe the same as on thecommand line.



name A column name.Can be any valid columnname. See “Using columnnames” on page 24 for thelist of column names.



instance A column name.Can be any valid columnname. See “Using columnnames” on page 24 for thelist of column names.

Multiple column names areallowed. Spaces are requiredbetween each of the columnnames in the list.

*exportSEM_file: subel2

This line specifies that the name of the output file is "subel2." The same thing onthe command line is:-file subel2



on the line.










file A command line option. Inthis case, -file. No hyphen before the

option.




subel2 The name of the file inwhich to place the exporteddata.

Should be only the file name.If a path is required use thedirPath option,*exportE_dirPath:./output .


Chapter 6. Managing resources

This chapter explains how to use resmgr to export, import, and manage differentTivoli Netcool Performance Manager object types that belong to the resourcecategory. Resources include the following object types:v Elementsv Subelements and subelement groupsv Composite subelementsv Nomenclature

Before using the commands in this chapter, review the information in Chapter 4,“Managing Tivoli Netcool Performance Manager objects,” on page 15.

Working with elementsThis section contains the commands you can use to manage elements. When youuse resgmr to work with the elements, you work with the following object types:v eltv scfv eprpv epropertyv enclv vendorv chnl

Links can exist among elements and the following Tivoli Netcool PerformanceManager object types:

Exporting elementsThe following examples of resmgr command used to export elements contain thecommand and the results of that command.

Exporting all elementsresmgr -export elt -colNames "dbIndex name type encl.name stateorigin profil collector missing comment" -file $DIR/elt_all.dat

# type = elt# col = dbIndex name type encl.name state origin profil collectormissing comment# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "dbIndex name type encl.namestate origin profil collector missing comment"

200000632|_|Delete_200000632_192.168.3.254|_|snmp|_|3Com Hub(SuperStack II PS Hub40)|_|off|_|inventory|_|Cisco_SAA|_|1|_||_||_|

200000788|_|Delete_200000788_192.168.3.37|_|snmp|_|BayStack350T|_|off|_|inventory|_|Cisco_SAA|_|1|_||_||_|


100000219|_|development.quallaby.com|_|snmp|_|HP Printer ETHERNETMULTI-ENVIRONMENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|

100000218|_|hpcolor.quallaby.com|_|snmp|_|HP Printer ETHERNETMULTI-ENVIRONMENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|

100000217|_|ps.quallaby.com|_|snmp|_|HP Printer ETHERNETMULTI-ENVIRONMENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|

100000214|_|finance.quallaby.com|_|snmp|_|HP Printer ETHERNETMULTI-ENVIRONMENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|

100000180|_|marketing.quallaby.com|_|snmp|_|HP Printer ETHERNETMULTI-ENVIRONMENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|100000165|_|Delete_100000165_192.168.3.238|_|snmp|_|HP PrinterETHERNETMULTI-ENVIRONMENT|_|off|_|inventory|_|Cisco_SAA|_|1|_||_||_|

100000220|_|192.168.66.2|_|snmp|_|Hardware: x86 Family 6 Model 1Stepping 9 COMPAQ SYMMETRICSYSTEMPRO|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|

100000215|_|dhcp65.quallaby.com|_|snmp|_|Hardware: x86 Family 6Model 1 Stepping 9 COMPAQ SYMMETRICSYSTEMPRO|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|

100000212|_|echidna.quallaby.com|_|snmp|_|Hardware: x86 Family 6Model 1 Stepping 9 COMPAQ SYMMETRICSYSTEMPRO|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|

Exporting elements with their propertiesresmgr -export elt -colNames "name eprp.name eprp.value" -file$DIR/elt_prp.dat

# type = elt# col = name eprp.name eprp.value# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name eprp.name eprp.value"172.31.0.31|_|ipAddress|_|172.31.0.31|_|ipName|_|172.31.0.31|_|physAddress|_|6.0.3.227.233.33.160|_|sysDescr|_|CiscoInternetwork Operating 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|_|CiscoInternetwork Operating 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 Operating 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-C6509\nCisco Catalyst Operating System Software, Version5.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|_|sysDescr|_|Cisco Internetwork Operating System Software \nIOS (tm)C3500XL Software (C3500|_|sysName|_|"PS-LAB"|_|

Exporting elements with sysName, ipAddress, and physAddressresmgr -export elt -colNames "name eprp.sysName:valueeprp.ipAddress:value eprp.physAddress:value" -file $DIR/elt_inv.dat

# type = elt# col = name eprp.sysName:value eprp.ipAddress:valueeprp.physAddress:value# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name eprp.sysName:valueeprp.ipAddress:value eprp.physAddress:value"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|_|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 informationresmgr -export elt -colNames "name encl.name encl.oid encl.gpnamevendor.name" -file $DIR/elt_encl.dat

# type = elt# col = name encl.name encl.oid encl.gpname vendor.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name encl.name encl.oidencl.gpname vendor.name"Delete_100000174_192.168.2.2|_|CiscoC2600-I|_|1.3.6.1.4.1.9.1.209|_|Cisco|_|Cisco|_|192.168.1.3|_|Cisco

Chapter 6. Managing resources 73

C2600-D|_|1.3.6.1.4.1.9.1.208|_|Cisco|_|Cisco|_|192.168.68.162|_|Cisco1600|_|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|_|Cisco1600|_|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|_|Cisco2611|_|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|_|Cisco3660|_|1.3.6.1.4.1.9.1.205|_|Cisco|_|Cisco|_|Delete_100001733_172.17.100.253|_|Cisco 7206VXR|_|1.3.6.1.4.1.9.1.222|_|Cisco|_|Cisco|_|172.31.0.51|_|Cisco 7204VXR|_|1.3.6.1.4.1.9.1.223|_|Cisco|_|Cisco|_|dhcp195.quallaby.com|_|Cisco 7204VXR|_|1.3.6.1.4.1.9.1.223|_|Cisco|_|Cisco|_|192.168.66.2|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQSYMMETRICSYSTEMPRO|_|1.3.6.1.4.1.311.1.1.3.1.2|_|Compaq|_|Microsoft|_|dhcp65.quallaby.com|_|Hardware: x86 Family 6 Model 1 Stepping 9COMPAQ SYMMETRICSYSTEMPRO|_|1.3.6.1.4.1.311.1.1.3.1.2|_|Compaq|_|Microsoft|_|

Exporting elements with collection informationresmgr -export elt -colNames "name collector chnl.host chnl.instDirchnl.type" -file $DIR/elt_chnl.dat

# type = elt# col = name collector chnl.host chnl.instDir chnl.type# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name collector chnl.hostchnl.instDir chnl.type"172.31.0.51|_|1|_|pvdemo3|_|/opt/dataload|_|SNMP|_|172.31.0.41|_|1|_|pvdemo3|_|/opt/dataload|_|SNMP|_|172.31.0.31|_|1|_|pvdemo3|_|/opt/dataload|_|SNMP|_|Delete_200000793_192.168.3.227|_|1|_|pvdemo3|_|/opt/dataload|_|SNMP|_|192.168.127.8|_|1|_|pvdemo3|_|/opt/dataload|_|SNMP|_|Delete_200000791_192.168.3.82|_|1|_|pvdemo3|_|/opt/dataload|_|SNMP|_|Delete_200000790_192.168.3.226|_|1|_|pvdemo3|_|/opt/dataload|_|SNMP|_|Delete_200000789_192.168.3.123|_|1|_|pvdemo3|_|/opt/dataload|_|SNMP|_|Delete_200000788_192.168.3.37|_|1|_|pvdemo3|_|/opt/dataload|_|SNMP|_|

Exporting elements with SNMP configuration informationresmgr -export elt -isMandat scf -colNames "name scf.rcommunityscf.timeout scf.retries scf.version scf.colNb" -file$DIR/elt_scf.dat

# type = elt# col = name scf.rcommunity scf.timeout scf.retries scf.versionscf.colNb# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name scf.rcommunity scf.timeoutscf.retries scf.version 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 collectorresmgr -export scf -colNames "colNb type ipaddress eltIdx versionbandwidth retries timeout wcommunity port rcommunity"

# type = scf# col = colNb type ipaddress eltIdx version bandwidth retriestimeout wcommunity port rcommunity# filter =# order =# sep = |_|# sepRec =# rule =# filterRule =## cmdLine = -export scf -colNames "colNb type ipaddress eltIdxversion bandwidth retries timeout wcommunity port rcommunity"0|_|default_snmp|_|*.*.*.*|_|5|_||_||_|3|_|2|_|private|_|161|_|public|_|

Exporting element state and comment informationresmgr -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 elementsYou must use the name column for a new element. By default, dbIndex is takenfrom the resourceSequences column, nclIdx is null , and the comment and profilcolumns are empty.

You can also include the following columns:v encl.name ( populate nclIdx )v profilv collector

When updating elements, you must use the dbIndex or name columns, and thecolumns to be modified.

Creating a new or updating an existing elementInput File:

add_elt1|_|3Com Hub (SuperStack II PS Hub40)|_|profil1|_|1|_|"element1"|_|172.31.128.51|_|6.0.4.109.221.236.0|_|add_elt2|_|3Com Hub (SuperStack II PS Hub40)|_|profil1|_|1|_|"element2"|_|172.31.128.41|_|6.0.48.25.95.152.192|_|


resmgr -import elt -colNames "name encl.name profil collectoreprp.sysName:value eprp.ipAddress:value eprp.physAddress:value"-file test1Info : === 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)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 propertiesInput File:192.168.69.243|_|Cisco Catalyst5000|_|testInv1|_|223|_|ipAddress|_|192.168.69.243|_|ipName|_|192.168.69.243|_|physAddress|_|"ff:d4:00:13:00:14"|_|sysDescr|_|"CiscoSystems WS-C5000"|_|sysName|_|"PMG_NETFIN2_MIMICagent#20"|_|192.168.69.245|_|Cisco Catalyst5000|_|testInv1|_|223|_|ipAddress|_|192.168.69.245|_|ipName|_|192.168.69.245|_|physAddress|_|"ff:d4:00:15:00:16"|_|sysDescr|_|"CiscoSystems WS-C5000"|_|sysName|_|"PMG_NETFIN2_MIMICagent#22"|_|

resmgr -import elt -colNames "name encl.name profil collectoreprp.name eprp.value" -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)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-existentelement (nothing is inserted)You can use this command when you need to just update an existing propertywithout creating a new one, for example in inventory.

Input File:NOTEXIST_192.168.69.243|_|Cisco Catalyst5000|_|testInv1|_|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 Catalyst5000|_|testInv1|_|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

Info : === insert : nothing ON property ( ipName ) (exists)eprp.name eprp.value" -file test1Info : === insert : nothing ON property ( ipAddress ) (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) eprpDInfo : === insert : nothing ON elt property (Depend not exist) eprpDInfo : === insert : nothing ON elt property (Depend not exist) eprpDInfo : === insert : nothing ON elt property (Depend not exist) eprpDInfo : === insert : nothing ON elt property (Depend not exist) eprpDInfo : === 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)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 collectorresmgr -import scf -colNames "colNb typeipaddress eltIdx version bandwidth retries timeout wcommunity portrcommunity" -import_source


Where import_source Specifies the source of the values that are to be imported tothe collector. The import source can include the following:v -file filename: Imports values from the specified file.v -line "value1|_|value2|_|value3": Imports the specified values directly from

the command line.

Deleting elementsYou must use the dbIndex or name columns when deleting elements.

Note: As the syntax lines indicate, the -file and -line options (with a validargument) 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 subelementsThis section contains the commands you can use to manage subelements. Whenyou work with subelement object types, you work with the following:v sev seprpv sepropertyv cse

Links can exist among elements and the following Tivoli Netcool PerformanceManager object types:v famv elt

Exporting subelementsThe following example of exporting subelements includes the command and thecommand output.

Exporting subelements with their propertiesresmgr -export se -colNames "dbIndex invariant elt.name name labelinstance state origin date_DATE fam.name seprp.name seprp.value"-file $DIR/se_seprp.dat

# type = se# col = dbIndex invariant elt.name name label instance state origindate_DATE fam.name seprp.name seprp.value# filter =# order =# sepRec =## cmdLine = -export se -colNames "dbIndex invariant elt.name namelabel instance state origin date_DATE fam.name seprp.nameseprp.value"200003278|_|Customer<C>|_|192.168.69.245|_|192.168.69.245_If<101>|_|192.168.69.245_IF:101 ("0") (100Mbps)|_|If<101>|_|on|_|inventory|_|


07/01/200302: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|_|inventory|_|07/01/200302: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|_|inventory|_|07/01/200302:28|_|2233_IF|_|name|_|"0"|_|siteID|_|IP:192.168.69.243ifIndex:100|_|If|_|100|_|customer|_|C1|_|physicalCapacity|_|100000000|_|status|_|up|_|location|_|"QALAB"|_|type|_|ethernetCsmacd|_|customer1|_|C4|_|200003446|_||_|Delete_200000133_pl2col6|_|Delete_200000831_pl2col6_DataChannel<dber>|_|Delete_200000831_pl2col6_DataChannel<dber>|_|Delete_200000831_DataChannel<dber>|_|on|_|resmgr|_|10/13/200314:52|_||_|200003448|_||_|dber|_|SE_dber|_|SE_dber|_|<NULL>|_|on|_|resmgr|_|10/13/200314:54|_||_|200003449|_||_|dber|_|SE_dber1|_|SE_dber1|_|<NULL1>|_|on|_|resmgr|_|10/13/200316:03|_|fam1|_|

Exporting composite subelementsresmgr -export cse -colNames "dbIndex name type invariant datacomment dataType defValue originr" -file cseDesc.rmg

# type = cse# col = dbIndex name type invariant data comment dataType defValueoriginr# filter =# order =# sep = |_|# sepRec =# rule =# filterRule =## cmdLine = -export cse -colNames "dbIndex name type invariant datacomment dataType defValue originr"1919|_|qcf5620_endPoint1|_|relation|_|type<SE>|_||_|Alcatel5620 Pack|_|string|_||_|APinstall|_|1920|_|qcf5620_endPoint2|_|relation|_|type<SE>|_||_|Alcatel5620 Pack|_|string|_||_|APinstall|_|1921|_|qcf5620_local|_|relation|_|type<SE>|_||_|Alcatel 5620Pack|_|string|_||_|APinstall|_|1922|_|qcf5620_remote|_|relation|_|type<SE>|_||_|Alcatel 5620Pack|_|string|_||_|APinstall|_|

Exporting composite subelements with composite linkresmgr -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 informationresmgr -export se -colNames "name state ulabel"

$ resmgr -export se -colNames "name state ulabel"# type = se# col = name state ulabel# filter =# order =# sep = |_|# sepRec =# rule =# filterRule =## cmdLine = -export se -colNames "name state ulabel"

DL.1_<NULL>|_|on|_||_|10.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 subelementsYou must use the following columns when importing new subelements:v namev hostIdx or elt.namev instance

By default, dbIndex is taken from the resourceSequences column, nclIdx is null ,and invariant and label are empty.

You can also include the following columns:v fam.name ( populate nclIdx )v label


v invariant 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 subelementInput 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|_|"

resmgr -import se -colNames "name fam.name label elt.name instanceseprp.Contact:value" -file test1Info : === 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 conctactA1 ) (does not exist)Title : === CHANGES : {1 Updated of se}Info : === Inform Collector On hebus:3002

Creating new or updating existing subelement and list ofpropertiesInput 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 instanceseprp.name seprp.value" -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 subEltproperty ( name "0" ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( type ethernetCsmacd ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( location "QALAB" ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( status up ) (exists)Info : === insert : nothing to do (update stopped) ON subElt


property ( physicalCapacity 100000000 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( If 100 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( customer1 C4 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( Contact conctact A1 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( siteID IP:192.168.69.243ifIndex:100 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( 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 subEltproperty ( name "0" ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( type ethernetCsmacd ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( location "QALAB" ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( physicalCapacity 100000000 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( customer1 C3 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( siteID IP:192.168.69.243ifIndex:101 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( If 101 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( customer C2 ) (exists)Info : === insert : nothing to do (update stopped) ON subEltproperty ( 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 anon-existent subelement (nothing is inserted)resmgr -import seproperty -colNames "name fam.name label elt.nameinstance seprp.name seprp.value" -file test1

Note: You must use datev to insert a property in the past.resmgr -import seproperty -colNames "name seprp.Contact:valueseprp.Contact:datev(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 conctactA1 ) (exists)

resmgr -import seproperty -colNames "name seprp.Contact:valueseprp.Contact:datev(1057015945)" -histoDate 1


Note: You need to use this command carefully. Check with IBM if you needassistance.

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, even if there is nochange in the seprp table.

Importing a composite subelementresmgr -import cse -colNames "name invariant" -line"relation1|_|type<SE>|_|"

Info : === insert : INSERT ON property ( relation1 ) (does notexist)

Importing composite subelementsresmgr -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_remotelabel3989_145_15509 ) (does not exist)

Deleting subelementsYou 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 validargument) are mandatory.

Deleting subelementsresmgr -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 have the indexresmgr -delete seprp -colNames "seIdx nop prpIdx" -line"200001183|_|bulk100-boston_1000,17_Interface<8>|_|1732|_|physicalCapacity|_|0|_|"

Info : === delete : DELETE ON subElt property (exists)

Deleting composite subelementsresmgr -delete cse -colNames "name" -line relation1

Info : === delete : DELETE ON property ( relation1 ) (exists)

Deleting composite subelements with composite linkresmgr -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_remotelabel3989_145_15509 ) (exists)

Working with groups or rulesThis section contains the commands you can use to manage groups or rules. Whenyou use resgmr to work with the elements, you work with the following objecttypes:v egpv segp

Subelement group linksLinks can exist among subelement groups and the following Tivoli NetcoolPerformance Manager object types:v sev appv rusrv tzv calv segparentv segchildv linkGroupSEv linkGroupSE_APPv linkGroupSE_RUv linkGroupSE_TZC

Exporting groups and rulesThe only difference between the export of the groups and the rule is the filterused.

Exporting subelement groups with a group labelresmgr -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 =## 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 rulesresmgr -export segp -colNames "npath name type cond state origindate" -order "dbIndex" -filter "type(!=’rule’)origin(=’inventory’)" -file $DIR/segp_generated.dat


# type = segp# col = npath name type cond state origin date# filter = type(!=’rule’) origin(=’inventory’)# order = dbIndex# sep = |_|# sepRec =## cmdLine = -export segp -colNames "npath name type cond stateorigin date" -filter "type(!=’rule’) origin(=’inventory’)"~NOC Reporting~Cisco SAA~Per Operation(raw)~Jitter~172.17.105.254|_|172.17.105.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~HourlyAggregate~Common~172.17.100.253|_|172.17.100.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Per Operation(raw)~HTTP~172.17.100.253|_|172.17.100.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~HourlyAggregate~Jitter~172.17.100.253|_|172.17.100.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~HourlyAggregate~Common~172.17.100.254|_|172.17.100.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~HourlyAggregate~Jitter~172.17.100.254|_|172.17.100.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Per Operation(raw)~HTTP~192.168.64.253|_|192.168.64.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~HourlyAggregate~Common~192.168.64.253|_|192.168.64.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~HourlyAggregate~Jitter~192.168.64.253|_|192.168.64.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Router~Interfaces~Location: "AP Lab, Lowell MAUS"~172.17.100.254|_|172.17.100.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Per Operation(raw)~Common~192.168.68.162|_|192.168.68.162|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~HourlyAggregate~Common~172.17.105.254|_|172.17.105.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Per Operation(raw)~Jitter~192.168.68.162|_|192.168.68.162|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~HourlyAggregate~Jitter~172.17.105.254|_|172.17.105.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Router~Interfaces~Location:""~192.168.68.162|_|192.168.68.162|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Per Operation(raw)~Common~172.17.100.253|_|172.17.100.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~CustomizationGroup~Coca-Cola|_|Coca-Cola|_|static|_|%(customer) =’Coca-Cola’|_|on|_|inventory|_|1018389887|_|~NOC Reporting~Cisco SAA~Per Operation(raw)~Common~172.17.105.254|_|172.17.105.254|_|generated|_||_|on|_|inventory|_|1025289790|_|

Exporting subelement groups that are rulesresmgr -export segp -colNames "npath name type cond state origindate" -order "dbIndex" -filterRule "(%(type) = ’rule’ OR %(cond) isnot 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 stateorigin date"~NOC Reporting|_|NOC Reporting|_|static|_|%(Element.STATE)=’on’ AND%(STATE)=’on’|_|on|_|APinstall|_|983650594|_|~Sub-Element Collect|_|Sub-ElementCollect|_|static|_|%(Element.STATE)=’on’ AND%(STATE)=’on’|_|on|_|APinstall|_|997993108|_|~NOC


Reporting~IPSec|_|IPSec|_|static|_|%(FAMILY)=’Cisco_IPSec’|_|on|_|APinstall|_|997993109|_|~NOCReporting~IPSec~Phase-1|_|Phase-1|_|static|_|%(FAMILY)=’Cisco_IPSec’|_|on|_|APinstall|_|997993109|_|~NOCReporting~IPSec~Phase-2|_|Phase-2|_|static|_|%(FAMILY)=’Cisco_IPSec’|_|on|_|APinstall|_|997993109|_|~NOCReporting~IPSec~Phase-1~%(customer)|_|%(customer)|_|rule|_||_|on|_|APinstall|_|993737950|_|~NOCReporting~IPSec~Phase-2~%(customer)|_|%(customer)|_|rule|_||_|on|_|APinstall|_|999637172|_|~Sub-ElementCollect~IPSec~Cisco|_|Cisco|_|static|_|%(FAMILY)=’Cisco_IPSec’|_|on|_|APinstall|_|999642720|_|~NOCReporting~IPSec~Phase-1~%(customer)~%(privateNetworkID)|_|%(privateNetworkID)|_|rule|_||_|on|_|APinstall|_|983650594|_|~NOCReporting~IPSec~Phase-2~%(customer)~%(privateNetworkID)|_|%(privateNetworkID)|_|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+|_|Cisco11.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~Devices|_|Devices|_|static|_|%(FAMILY)LIKE ’%Device%’|_|on|_|APinstall|_|999124865|_|~Sub-Element Collect~Router~Devices~Cisco 11.x|_|Cisco11.x|_|static|_|%(FAMILY) LIKE’Cisco%Router%Device%’|_|on|_|APinstall|_|1024082286|_|~NOC Reporting~Router|_|Router|_|static|_|%(Element.NODETYPE) =’Router’|_|on|_|APinstall|_|999044238|_|~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~Devices|_|Devices|_|static|_|%(FAMILY) LIKE’%Device%’ AND %(Element.VENDOR) !=’Unisphere’|_|on|_|APinstall|_|999126431|_|~NOC Reporting~Router~Devices~Location: %(location)|_|Location:%(location)|_|rule|_||_|on|_|APinstall|_|999641730|_|~Sub-ElementCollect~Router~Interfaces|_|Interfaces|_|static|_|%(FAMILY) LIKE’%_IF’|_|on|_|APinstall|_|997993110|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|Cisco11.x|_|static|_|%(Element.VENDOR)=’Cisco’|_|on|_|APinstall|_|1013400292|_|

Exporting subelement groups that are leaf, active rulesresmgr -export segp -colNames "dbIndex name type cond state origindate" -order "dbIndex" -filterRule "(%(type) = ’rule’ OR %(cond) isnot 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 stateorigin date" -filter "state(on) segchild.name(is null)"4191|_|Cisco|_|static|_|%(FAMILY)=’Cisco_IPSec’|_|on|_|APinstall|_|999642720|_|


4192|_|%(privateNetworkID)|_|rule|_||_|on|_|APinstall|_|983650594|_|4193|_|%(privateNetworkID)|_|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%Device%’|_|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|_|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)= ’JuniperNetworks’|_|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 Devices|_|static|_|%(FAMILY) = ’1213_Device’AND %(Element.VENDOR) =’Unisphere’|_|on|_|APinstall|_|1022018055|_|

Note: You can not currently use npath with segchild or segparent object types.

Exporting subelement groupsresmgr -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~IPInterfaces~default~10.8.7.18|_|192.168.127.2_If<23>|_|~NOC Reporting~Network Management~Bylocation~"Catalyst_PS_Lab"|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~By Customer and Location~Bristol-MyersSquibb bylocation~"Catalyst_PS_Lab"|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~WCOM Testgroup~Headquarters~Loreal~Bordeaux~testvalue2|_|192.168.127.2_If<23>|_|


~Customer Facing Reporting~IP VPN~By Customer and CoS~LorealCoS~Gold|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~By Customer and VPN~LorealVPN~Headquarters|_|192.168.127.2_If<23>|_|~NOC Reporting~IP VPN~By Class ofService~Gold|_|192.168.127.2_If<23>|_|~NOC Reporting~IP VPN~ByCity~Bordeaux|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~ByCoS~Gold|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~ByCoS~Standard|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~By Customer and Cos~Bristol-Myers Squibbby CoS~Standard|_|192.168.127.2_If<23>|_|~NOC Reporting~Network Management~ByCoS~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-ElementCollect~RFC-1213~Interfaces~Frequent|_|192.168.127.2_If<23>|_|

Exporting report user groupsresmgr -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 appresmgr -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"~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 timezonesYou use the option filter tzdate(%NOW) in the command because the Calendar tableis actually a history table. If you just need to see the line valid for "now," you usethis filter to avoid viewing 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~LindtVPN|_|EST_2003|_|4 AM to 8 PM restricted SLA|_|

Importing groups and rulesYou must use the following columns when importing new groups:v npathv typev rule if type=generated

And the following columns when importing new rules:v npathv condv type = rule


When updating existing groups and rules, you must use the dbIndex or npathcolumns, and the columns to be modified.

The following table lists the commands

Import Command

Insert or update group resmgr -import segp -colNames "npath name typestate origin" -line "~NOC Reporting~CustomerA|_|CustomerA|_|static|_|on|_|resgmr"

Insert group if it does not existand link subelement to it

resmgr -import segp -colNames "npath se.name"

Link subelement to group onlyif the group exists

resmgr -import linkGroupSE -colNames "npath se.name"

Insert group if it does notalready exist and link report toit

resmgr -import segp -colNames "npath app.name"

Link report to group only if thegroup exists

resmgr -import linkGroupSE_APP -colNames"npath app.name"

Insert group if it does not existand link report user to it

resmgr -import segp -colNames "npath rusr.name"

Link report user to group onlyif group exists

resmgr -import linkGroupSE_RU -colNames"npath rusr.name"

Insert group if it does not existand link timezone to it

resmgr -import segp -colNames"npath cal.name tz.name"

Link timezone to group only ifgroup exists

resmgr -import linkGroupSE_TZC -colNames"npath cal.name tz.name"

Inserting or updating groupsresmgr -import segp -colNames "npath name type state origin" -line"~NOC Reporting~CustomerA|_|CustomerA|_|static|_|on|_|resgmr"

Info : === insert : INSERT ON Sub-Elt Group ( ~NOCReporting~CustomerA ) (does not exist)Info : === Update Histo : 0Title : === CHANGES : {3 New of segp}Info : === Inform Collector On hebus:3002

Inserting group if non-existent and linking subelements to itresmgr -import segp -colNames "npath se.name " -line "~NOCReporting~CustomerA|_|192.168.69.243_If<100>|_|"

Info : === insert : nothing ON Sub-Elt Group ( ~NOCReporting~CustomerA ) (exists)Info : === insert : INSERT ON Link SE/G (192.168.69.243_If<100> CustomerA ) (does not exist)Info : === Update Histo : 0Title : === CHANGES : {1 New of se}Info : === Inform Collector On hebus:3002

Linking subelements to group only if group existsresmgr -import linkGroupSE -colNames "npath se.name " -line "~NOCReporting~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 I200003280 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 itresmgr -import segp -colNames "npath app.name " -line "~NOCReporting~CustomerA|_|Top N AS Details|_|"

Info : === insert : nothing ON Sub-Elt Group ( ~NOCReporting~CustomerA ) (exists)Info : === insert : nothing ON Application ( Top N AS Details )(exists)Info : === insert : INSERT ON Link App/SEGroup ( Top N AS DetailsCustomerA ) (does not exist)Info : === Update Histo : 0

Linking report to group only if group existsresmgr -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 DetailsCustomerB ) (does not exist)Info : === Update Histo : 0

Inserting group if non-existent and linking report user to itresmgr -import segp -colNames "npath rusr.name" -line "~NOCReporting~CustomerA|_|SSSW\\customer2|_|"

Info : === insert : nothing ON Sub-Elt Group ( ~NOCReporting~CustomerA ) (exists)Info : === insert : INSERT ON Report User ( SSSW\customer2 ) (doesnot exist)Info : === insert : INSERT ON Link RU/SEG ( SSSW\customer2CustomerA ) (does not exist)Info : === Update Histo : 0

Linking report user to group only if group existsresmgr -import linkGroupSE_RU -colNames "npath rusr.name" -line"~NOC Reporting~CustomerB|_|SSSW\\customer2|_|"

Info : === insert : INSERT ON Link RU/SEG ( SSSW\customer2CustomerB ) (does not exist)Info : === Update Histo : 0

Inserting group if non-existent and linking timezone to itresmgr -import segp -colNames "npath cal.name tz.name" -line "~NOCReporting~TestInsertTZC|_|CME Permanent|_|GMT|_|"

Info : === insert : INSERT ON Sub-Elt Group ( ~NOCReporting~TestInsertTZC ) (does not exist)

Info : === insert : INSERT ON Link SEGP/TZ ( GMT CME Permanent ) (does notexist)

Info : === Update Histo : 0

Title : === CHANGES : {3 New of segp}

Info : === Inform Collector On hebus:3002

Linking timezone to group only if group existsresmgr -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


DeletingAs the syntax lines indicate, the -file and -line options (with a valid argument)are mandatory.

The following table lists deletion commands:

Delete Command

group resmgr -delete segp -colNames "npath" -line"~NOC Reporting~CustomerA"

unlink subelement resmgr -delete linkGroupSE -colNames "npath se.name"

unlink report resmgr -delete linkGroupSE_APP -colNames "npath app.name"

unlink report user resmgr -delete linkGroupSE_RU -colNames "npath rusr.name"

unlink timezone resmgr -delete linkGroupSE_TZC -colNames"npath cal.name tz.name"

Deleting a groupresmgr -delete segp -colNames "npath" -line "~NOCReporting~CustomerA"

Info : === DELETE GROUP : ~NOC Reporting~CustomerA (index =200003479)Info : === delete : DELETE ON Sub-Elt Group ( ~NOCReporting~CustomerA ) (exists)Info : === Update Histo : 0Title : === CHANGES : {2 Deleted of segp}Info : === Inform Collector On hebus:3002

Unlinking subelementsresmgr -delete linkGroupSE -colNames "npath se.name" -line "~NOCReporting~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 : 0Title : === CHANGES : {1 Deleted of se}Info : === Inform Collector On hebus:3002

Unlinking reportsresmgr -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 DetailsCustomerB ) (exists)Info : === Update Histo : 0

Unlinking report usersresmgr -delete linkGroupSE_RU -colNames "npath rusr.name" -line"~NOC Reporting~CustomerB|_|SSSW\customer2|_|"

Info : === delete : DELETE ON Link RU/SEG ( SSSW\customer2CustomerB ) (exists)Info : === Update Histo : 0

Unlinking timezonesresmgr -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 rulesExporting composite subelement (CSE) rules is a two-stage process that must resultin two separate files being generated to be complete. You must always enter therule definitions command before the rule relations command. Only the options inthis section are supported.

Using the commands in this section ensures that multiple root groups are notcreated when importing composite subelement rules. Ensure that you never createadditional root groups using the resmgr command.

Exporting composite subelement rulesv Rule definitions

resmgr -export rulegp -colNames "dbIndex name type targetName labelcond ruleprp.name ruleprp.command ruleprp.value" -filerulesD.export.dat

v Rule relationsresmgr -export rulegp -colNames "lgParent lgChild relType relNamerelCond" -file rulesL.export.dat

Importing or updating composite subelement rulesv Rule definitions

resmgr -import rulegp -colNames "dbIndex name type targetName labelcond ruleprp.name ruleprp.command ruleprp.value" -filerulesD.import.dat

v Rule relationsresmgr -import rulegp -colNames "lgParent lgChild relType relNamerelCond" -file rulesL.import.dat

Deleting composite subelement rulesv 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 nomenclatureThis section contains the commands you can use to manage nomenclature. Whenyou use resgmr to work with the nomenclature, you work with the followingobject types:v ngpv ncl

Links can exist among elements and the following Tivoli Netcool PerformanceManager object types:v vendorv linkGroupN

Exporting all of the nomenclatureresmgr -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 C3262AServer|_|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 C3264AServer|_|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 NMM2813|_|1.3.6.1.4.1.45.3.12.1|_|SysObjectID|_|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, HWB.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 3000RMON2|_|1.3.6.1.4.1.217.1.3.3|_|SysObjectID|_|Sync Research Serial Frame Relay Access Probe WithPro-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 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 C3262AServer|_|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 C3264AServer|_|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 NMM2813|_|1.3.6.1.4.1.45.3.12.1|_|SysObjectID|_|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, HWB.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 3000RMON2|_|1.3.6.1.4.1.217.1.3.3|_|SysObjectID|_|Sync Research Serial Frame Relay Access Probe WithPro-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|_|Cisco2501|_|1.3.6.1.4.1.9.1.17|_|SysObjectID|_|~NodesType~Router~Cisco|_|CiscoLS1010|_|1.3.6.1.4.1.9.1.107|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco WSX5302|_|1.3.6.1.4.1.9.1.168|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco4700|_|1.3.6.1.4.1.9.1.50|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco4500|_|1.3.6.1.4.1.9.1.14|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco2513|_|1.3.6.1.4.1.9.1.29|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco2504|_|1.3.6.1.4.1.9.1.20|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco3640|_|1.3.6.1.4.1.9.1.110|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco7000|_|1.3.6.1.4.1.9.1.8|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco2507|_|1.3.6.1.4.1.9.1.23|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco4000|_|1.3.6.1.4.1.9.1.7|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco753|_|1.3.6.1.4.1.9.1.83|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco2524|_|1.3.6.1.4.1.9.1.74|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco2511|_|1.3.6.1.4.1.9.1.27|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco766|_|1.3.6.1.4.1.9.1.103|_|SysObjectID|_|~NodesType~Access~Redback|_|Redback SMS500|_|1.3.6.1.4.1.2352.1.2|_|SysObjectID|_|


~NodesType~Access~Paradyne|_|PARADYNE T1 FrameSaver SLV; Model:9124|_|1.3.6.1.4.1.1795.1.14.2.4.4.5|_|SysObjectID|_|~NodesType~Access~Paradyne|_|PARADYNE T1 FrameSaver SLV; Model:9124/NNI|_|1.3.6.1.4.1.1795.1.14.2.4.4.6|_|SysObjectID|_|~NodesType~Access~Paradyne|_|PARADYNE DDS FrameSaver SLV; Model:9624|_|1.3.6.1.4.1.1795.1.14.2.4.1.5|_|SysObjectID|_|~NodesType~Access~Unisphere|_|UnisphereC2100|_|1.3.6.1.4.1.2908.1|_|SysObjectID|_|~NodesType~Access~Unisphere|_|UnisphereC2100Rev1|_|1.3.6.1.4.1.2908.1.1|_|SysObjectID|_|~NodesType~Access~Unisphere|_|UnisphereRX1400|_|1.3.6.1.4.1.2773.1.2.1.1|_|SysObjectID|_|~NodesType~Access~Unisphere|_|UnisphereRX700|_|1.3.6.1.4.1.2773.1.2.1.2|_|SysObjectID|_|~NodesType~Access~Lucent|_|LucentPortMaster|_|1.3.6.1.4.1.307.2.1|_|SysObjectID|_|

Importing nomenclatureYou must use the following columns when importing new nomenclature:v type SysObjectID or Vendor : name oid typev type ifType : name type

When updating nomenclature, you must use the following columns:v dbIndex or name+typev 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 discovert |_|Cisco C7100-IS|_|"

Info : === insert : INSERT ON nomenclature ( Cisco As inserted bydiscovert ) (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

Deleting nomenclatureYou must use the following columns when importing new nomenclature:v dbIndexv 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 linksThis section explains how to use mandatory links with Tivoli Netcool PerformanceManager resources. You can use the following option to indicate whether or not alink is mandatory:-isMandat

Using mandatory links with elementsYou can use the following option to force a link to be mandatory (or not) betweenelements and the following object types:v scfv enclv eprp

For example:

Display Elements Command

With nomenclature resmgr -export elt -colNames "nameencl.name" -isMandat "encl"

With or without nomenclature resmgr -export elt -colNames "nameencl.name"

Without nomenclature resmgr -export elt -colNames "nameencl.name" -filter "encl.name(is null)"

With an SNMP configuration resmgr -export elt -colNames "namescf.ipaddress" -isMandat "scf"

With at least one property resmgr -export elt -colNames "nameeprp.name" -isMandat "elt.eprp"

With or without properties resmgr -export elt -colNames "nameeprp.name"

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 ETHERNETMULTI-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 SystemSoftware \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 Hub40)|_|Delete_200000788_192.168.3.37|_|BayStack 350T|_|development.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 ETHERNETMULTI-ENVIRONMENT|_|192.168.66.2|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQSYMMETRIC SYSTEMPRO|_|dhcp65.quallaby.com|_|Hardware: x86 Family 6 Model 1 Stepping 9COMPAQ SYMMETRIC SYSTEMPRO|_|echidna.quallaby.com|_|Hardware: x86 Family 6 Model 1 Stepping 9COMPAQ SYMMETRIC SYSTEMPRO|_|svrne01.quallaby.com|_|Hardware: x86 Family 6 Model 1 Stepping 9COMPAQ 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(isnull)" -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

# 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|_|




192.168.127.4|_|

192.168.127.5|_|ipAddress|_|ipAddressMin|_|ipName|_|physAddress|_|sysDescr|_|sysName|_|


Using mandatory links with subelementsYou can use the mandatory option to force a link to be mandatory (or not) betweensubelements and the following object types:v famv emptyfamv seprp

For example:

Display Subelements Command

With a family resmgr -export se -colNames "name fam.name"-isMandat "fam"

Without family resmgr -export se -colNames "name fam.name"-filter "fam.name(is null)"

With or without a family resmgr -export se -colNames "name fam.name"

All families without subelement links

Use emptyfam to display familieswithout subelements; not the opposite

resmgr -export se -colNames "name fam.name"-isMandat "emptyfam" -filter"se.name(is null)"

Displaying all subelements with a familyresmgr -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_Device|_|

Displaying all subelements without familyresmgr -export se -colNames "name fam.name" -filter "fam.name(isnull)" -file $DIR/isnull_fam.dat

# type = se


# 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


# filter =

# order =

# sep = |_|

# sepRec =

# cmdLine = -export se -colNames "name fam.name"

[email protected]|_|MLARS|_|

NF-iphost-site-flow-BestEffort-CoffeeBucks_srcIP[Engineering-cb]dstSite[Dallas]cos[BestEffort]|_|NetFlow|_|

NF-site-Bronze-CoffeeBucks_Site[Denver]cos[Bronze]|_|NetFlow|_|

cme222.quallaby.com_<NULL>|_||_|

Displaying all families without subelements linked to themUse 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


# 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 groupsYou can use the mandatory option to force a link to be mandatory (or not) betweensubelement groups and the following object types:v appv sev rusrv tzc

By default, the isMandat option for segp = "app se rusr segp", so the export onlyshows the path with child attached.

For example:

Display Subelement Groups Command

Only groups with timezones resmgr -export segp -colNames "npath cal.nametz.name"

All groups, including empty ones resmgr -export segp -colNames "npath se.name"-isMandat ""

Only empty groups generated resmgr -export segp -colNames "dbIndexname segchild.name se.name" -isMandat ""-filter "segchild.name(is null) se.name(is null) type(generated)"


Displaying only groups with timezonesresmgr -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 onesYou use the -isMandat option in this command to force it to empty, because bydefault -isMandat is not empty.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~IPInterfaces~default~10.8.7.18|_|192.168.127.2_If<23>|_|

~NOC Reporting~Network Management~Bylocation~"Catalyst_PS_Lab"|_|192.168.127.2_If<23>|_|

~Customer Facing Reporting~By Customer and Location~Bristol-MyersSquibb bylocation~"Catalyst_PS_Lab"|_|192.168.127.2_If<23>|_|

~Customer Facing Reporting~IP VPN~WCOM Testgroup~Headquarters~Loreal~Bordeaux~testvalue2|_|192.168.127.2_If<23>|_|

~Customer Facing Reporting~IP VPN~By Customer and CoS~LorealCoS~Gold|_|192.168.127.2_If<23>|_|

~Customer Facing Reporting~IP VPN~By Customer and VPN~LorealVPN~Headquarters|_|192.168.127.2_If<23>|_|

~NOC Reporting~IP VPN~By Class ofService~Gold|_|192.168.127.2_If<23>|_|

~NOC Reporting~IP VPN~ByCity~Bordeaux|_|192.168.127.2_If<23>|_|

~Customer Facing Reporting~IP VPN~ByCoS~Gold|_|192.168.127.2_If<23>|_|

~Customer Facing Reporting~ByCoS~Standard|_|192.168.127.2_If<23>|_|


~Customer Facing Reporting~IP VPN~WCOM Test group~Sales andMarketing~Volkswagen~Frankfurt|_||_|

~Customer Facing Reporting~IP VPN~WCOM Test group~Research andDevelopment~Chevron~San Francisco|_||_|

~NOC Reporting~Virtual Routers~IP AddressPools~%(Element.NAME)|_||_|

~Customer Facing Reporting~By Customer and Location~CVS bylocation~Denver|_||_|

~Customer Facing Reporting~IP VPN~WCOM Test group~Research andDevelopment~Fiat~Rome|_||_|

~Partner Section~Cisco~Netflow|_||_|

Displaying only empty groupsresmgr -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 =

#

# cmdLine = -export segp -colNames "dbIndex name segchild.namese.name" -filter "segchild.name(is null) se.name(is null)type(generated

)"

200000049|_|test value2|_||_||_|

100001001|_|Denver|_||_||_|

100010002|_|172.17.100.254|_||_||_|

100001078|_|Dallas|_||_||_|

100000990|_|Houston|_||_||_|

200000153|_|test value2|_||_||_|

Using mandatory links with inventory profilesYou can use the mandatory option to force a link to be mandatory (or not) betweeninventory profiles and the following object types:v opt

By default, the isMandat option for ogp = opt, so the opt needs to exist for thenpath.

Displaying the npath without optionsresmgr -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~inventory~ipaddress~exclude|_||_|

~PROVISO_MONITORING~inventory~ipaddress~exclude|_||_|

~Cisco_SAA~inventory~ipaddress~exclude|_||_|

~PROVISO_MONITORING~synchro~filestoinsert|_||_|

~default~synchro~filestoinsert|_||_|

~bulk_2~synchro~filestoinsert|_||_|

~|_||_|

~Cisco_SAA~synchro~filestoinsert|_||_|

~bulk_2~inventory~ipaddress~exclude|_||_|

Using mandatory links with nomenclatureYou can use the mandatory option to force a link to be mandatory (or not) betweennomenclature and the following object types:v node type

Displaying the number of nomenclature attached to a node typeresmgr -export ncl -colNames "name oid nliParent" -isMandat"nodetype" -noHead | wc -l

The output is a number.

Displaying a list of nomenclature without nodeType definedresmgr -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) C3500XLSoftware (C3500|_|1.3.6.1.4.1.9.1.278|_||_|

1213_Device|_||_||_|

Cisco Internetwork Operating System Software \nIOS (tm) C2600Software (C2600-I|_|1.3.6.1.4.1.9.1.209|_||_|

MLARS|_||_||_|

Cisco Internetwork Operating System Software \nIOS (tm) L3Switch/Router Softwa|_|1.3.6.1.4.1.9.1.275|_||_|

Cisco Internetwork Operating System Software \nIOS (tm) C2600Software (C2600-I|_|1.3.6.1.4.1.9.1.208|_||_|

1213_IF|_||_||_|

1315_FR_DLC_SNMP-CIR|_||_||_|


Chapter 7. Managing design objects

Explains how to use resmgr to manage design objects

This section explains how to use resmgr to export, import, and different TivoliNetcool Performance Manager object types that belong to the Design category.Design objects include the following types:v Formulasv Propertiesv Thresholdsv Requestsv Calendarsv Timezonesv Inventory profiles

Before using these commands, review the information in Chapter 4, “ManagingTivoli Netcool Performance Manager objects,” on page 15.

Working with formulasThis section contains the commands you can use to manage formulas. You shoulduse the Tivoli Netcool Performance Manager DataMart Formula Editor to createformulas. When you use resgmr to work with the elements, you work with thefollowing object types:v frmv fgpv linkGroupF (import only)

You need to use the -sepRec option because the formula data are not stored on asingle row. You need to define another separator other than the carriage return. Bydefault the -sepRec option used for formula is <E>.

Exporting formulasThe following examples of resmgr command used to export formulas contain thecommand and the results of that command.

Exporting formula groupsresmgr -export fgp -colNames "dbIndex nName frm.dbIndex frm.datafrm.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.commentfrm.date frm.state

# filter =

# order =

# sep = |_|

# sepRec = <E>

# rule =

# filterRule =


#

# cmdLine = -export fgp -colNames "dbIndex nName frm.dbIndexfrm.data frm.type frm.comment frm.date frm.state"

1932|_|~Alias Instance and LabelInventory~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 Discovery Formula forthe "Cisco_IPSec" Family - Cisc

o router-level IPSec agents|_|999640340|_|on|_|<E>

1932|_|~Alias Instance and LabelInventory~AP~Cisco_IPSec_match|_|4184|_|cipSecMibLevel.0|_|snmp|_|"Match"Formula for matching SubElements to the "Cisco_IPSec" Family, sincethey will also fulfill requirements for Family"1213_Device"|_|983650594|_|on|_|<E>

4353|_|~AP~Tivoli Netcool Performance Manager~DataManager~ElementAverage Response Time (ms)|_|4352|_|Stat( "Targets" , %H1 , "SNMPResponse Time (ms) [last hour]"

)|_|snmp|_|Uses internal Tivoli Netcool Performance ManagerStatistics to calculate an Elements SNMP ResponseTime.|_|983650594|_|on|_|<E>

4353|_|~AP~Tivoli Netcool Performance Manager~DataManager~ElementAvailability (percent)|_|4354|_|Stat( "Targets" , %H1 , "SNMPAvailability (%) [last hour]" )|_|snmp|_|Uses internal TivoliNetcool Performance Manager Statistics to calculate ElementsAvailability in percent|_|983650594|_|on|_|<E>

4353|_|~AP~Tivoli Netcool PerformanceManager~DataManager~detect_reboot|_|4355|_|distrib(delta(sysUpTime.0),"default:1");|_|snmp|_|An example of how to detect systemreboot.|_|983650594|_|on|_|<E>

Exporting formula MIBsresmgr -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 LabelInventory~AP~Disman_Ping_Test|_|rfc2925p.mi2|_|

~Alias Instance and LabelInventory~AP~Cisco_CBQoS_Action|_|CISCO-CLASS-BASED-QOS-MIB.my|_|

~Alias Instance and LabelInventory~AP~Cisco_CBQoS_Class|_|rfc1213-MIB-II|_|

~Alias Instance and LabelInventory~AP~Cisco_CBQoS_Class|_|CISCO-CLASS-BASED-QOS-MIB.my|_|

~Alias Instance and LabelInventory~AP~Cisco_Router_Device_SAA_Resp|_|rfc1213-MIB-II|_|


~Alias Instance and LabelInventory~AP~Cisco_Router_Device_SAA_Resp|_|CISCO-RTTMON-MIB.my|_|

~Alias Instance and LabelInventory~AP~Cisco_Router_Device_SAA_Resp_match|_|rfc1213-MIB-II|_|

~Alias Instance and LabelInventory~AP~Cisco_Router_Device_SAA_Resp_match|_|cisco-10-mib|_|

~Alias Instance and LabelInventory~AP~Cisco_Router_Device_SAA_Resp_match|_|CISCO-RTTMON-MIB.my|_|

~Alias Instance and LabelInventory~AP~Cisco_Router_Device_SAA_match|_|rfc1213-MIB-II|_|

~Alias Instance and LabelInventory~AP~Cisco_Router_Device_SAA_match|_|OLD-CISCO-SYSTEM-MIB.my|_|

~Alias Instance and LabelInventory~AP~Cisco_Router_Device_SAA_match|_|CISCO-RTTMON-MIB.my|_|

~Alias Instance and LabelInventory~AP~Cisco_Router_Device_SAA|_|rfc1213-MIB-II|_|

Importing formulasYou must use the following columns for a new formula. By default, dbIndex istaken from the designSequences column, type is import, dataType is float, nbHostis 1.v frmv fgpv linkGroupF

You can also include the following columns:v For fgp, use npathv For frm, use name data typev For type ifType, use name type

When updating formulas, you must use the following columns:v For fgp, use dbIndex or npath (or nNam) and the columns to be modifiedv For frm, use dbIndex and the columns to be modified

Input fileThe input file includes the following:~Alias Instance and Label Inventory~AP~NEWCisco_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 Discovery Formula forthe "Cisco_IPSec" Family - Cisco router-level IPSecagents|_|<E>

Importing formula groupsresmgr -import fgp -colNames "nName frm.data frm.type frm.comment"-file test1 -sepRec "<E>"

Info: === insert: nothing ON Formula Group (~Alias Instance andLabel Inventorially ) (exists)

Info : === insert : INSERT ON Formulas ( NEW Cisco_IPSec ) (doesnot exist)

Info : === insert : INSERT ON Link F/G ( NEW Cisco_IPSec ~AliasInstance and Label Inventory~AP ) (does not exist)

Chapter 7. Managing design objects 107


Deleting formulasYou must use the following columns when deleting formulas:v For fgp, use dbIndex or npath (or nName for a formula)v For frm, use dbIndex

Deleting a formula groupresmgr -delete fgp -colNames "npath" -line "~test1"

Info : === DELETE GROUP : ~test1 (index = 100001032)

Info : === delete : DELETE ON Formula Group ( ~test1 ) (exists)


Deleting a formularesmgr -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)


Working with propertiesThis section contains commands you can use when you manage properties. Whenyou work with property object types, you work withv propertyE for the element propertiesv propertySE for the subelement propertiesv propertyRU for the report user properties

Both the name and the invariant must be unique.

Three properties used by default for the element invariant include the following:v ipNamev sysNamev physAddress

Subelement propertiesThe following table lists the subelement properties supplied by a Tivoli NetcoolPerformance Manager installation:

Subelement Property Description

name A specific, textual name for this entitydefined by the user, most often duringgeneral network configuration.

hostIP Physical IP address of the host upon whichthis resource resides

hostURL URL address assigned to the host uponwhich this resource resides


hostName Textual name assigned to the host uponwhich this resource resides. Defined by theuser most often during general networkconfiguration

parent Open-format name or ID assigned to anentity considered as a "parent" containingthis resource. Is usually different from aphysical host (see 'hostName' property.)

hostType Open-format "type" classification of thedevice upon which this resource resides.


parentType Open-format "type" classification of theparent of this resource

description Open-format description text used ininstances when helpful for grouping(currently not displayed in the DataViewportal).

class Open-format name of the general class ofresource represented (for example, device,interface, logical port, end-to-endconnection, and so on.)

type Open-format name of the specific type ofresource represented (Ethernet, DS1, and soon.)

subType Additional specific type information for theresource (NNI, UNI, and so on.)

protocol Transmission protocol specific to theresource (ATM, Frame Relay, IP, IPSec, TCP,UDP, MPLS, and so on.)

protocolVersion Version of transmission protocol being used

model Open-format model name of the resource

modelID Open-format model ID string of the resource

version Open-format version identification of theresource

patchLevel Open-format patch level identification of theresource

country The country in which the resource resides

city The city, town, or municipality in which theresource resides

state The state in which the resource physicallyresides

province The province in which the resource resides

region Open-format region name at which theresource resides

regionID Open-format ID string assigned to theregion in which the resource resides

location Physical location of the resource

locationID Open-format ID string assigned to thephysical location at which the resourceresides



status Operational status of the resource ('active','initializing', 'maintenance', etc.)

priority Open-format priority name or code

physicalCapacity The maximum speed of this resource (bps)

committedCapacity The steady-rate bandwidth (bps) committedfor transfer over this resource.

committedBurstCapacity The transmission rate (bps) committed forshort traffic bursts (for a pre-agreedduration) over this resource.

committedPeakCapacity The maximum transmission rate (bps)committed for transfer over this resource.

owner Service provider employee name/ID towhich this resource belongs

ownerCustomTag User-definable property for custom resourceorganization attributes

department Service provider department to which thisresource belongs

departmentID ID of the service provider department towhich this resource belongs

networkArea Network area (for example, BackBone, CPE)of the entity

network The name of the network of which thisentity is a part.

networkID The ID of the network of which this entity isa part.

privateNetwork The name of the private (virtual) network ofwhich this entity is a part.

privateNetworkID The ID of the private (virtual) network ofwhich this entity is a part.

customer The name of the specific customer that thisresource services.

customerID The ID of the specific customer that thisresource services.

customerType The type of the customer that this resourceservices.


customerFacingName Alternate name to be used for this resourcein customer-facing reports, messages, and soon.

securityProfileMask Open-format string for definition of a textmask which can be generated for users by acustom user group control system and usedwithin rule conditions to organize usergroups' access to resource views.


Exporting propertiesThe following examples of resmgr command used to export properties contain thecommand and the results of that command.

Exporting element propertiesresmgr -export propertyE -colNames "name invariant defValue state"-file $DIR/propertyE.dat

# type = propertyE

# col = name invariant defValue state

# filter = invariant(type<E>) invariant(type<E>)

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export propertyE -colNames "name invariant defValuestate" -filter "invariant(type<E>) invariant(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 propertiesresmgr -export propertySE -colNames "name invariant defValue state"-file $DIR/propertySE.dat

# type = propertySE


# filter = invariant(type<SE>) invariant(type<SE>)

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export propertySE -colNames "name invariant defValuestate" -filter "invariant(type<SE>)invariant(type<SE>)"

customStringProperty01|_|type<SE>|_||_|on|_|





customNumericProperty01|_|type<SE>|_||_|on|_|





testActivationInterval|_|type<SE>|_||_|on|_|

testPacketInterval|_|type<SE>|_||_|on|_|

name|_|type<SE>|_|Undefined ’name’ Property|_|on|_|

hostIP|_|type<SE>|_|Undefined ’hostIP’ Property|_|on|_|


hostURL|_|type<SE>|_||_|on|_|

Exporting property default valuesYou can export the default value (DefVal) of the property (as defined in thedatabase) for a resource that does not yet exist by using the following option.-isDefault

You can use this option with the following object types:v eprpv seprpv ruprp

Exporting element property default valuesresmgr -export elt -colNames "name eprp.Contact:value" -isDefaulteprp -file $DIR/isdefault_eprp.dat

# type = elt

# col = name eprp.Contact:value

# filter =

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export elt -colNames "name eprp.Contact:value"

172.31.0.51|_|1|_|pvdemo1|_|

172.31.0.41|_|1|_|pvdemo2|_|

172.31.0.31|_|1|_|pvdemo3|_|

Delete_200000793_192.168.3.227|_|1|_|pvdemo3|_|

192.168.127.8|_|1|_|pvdemo2|_|

Displaying the defVal for properties that do not yet existresmgr -export propertyE -colNames "name dataType subType invariantstate defValue" -file $DIR/defVal.dat

# type = propertyE

# col = name dataType subType invariant state defValue

# filter = invariant(type<E>) invariant(type<E>)

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export propertyE -colNames "name dataType subTypeinvariant state defValue" -filter "invariant(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|_|pvdemo3|_|


Trouble Ticket pack propertiesThe following properties are a subset of Tivoli Netcool Performance ManagerTechnology Pack properties. See the Tivoli Netcool Performance ManagerTechnology Pack documentation for information.v ServiceContractv ServiceCityv ServiceEmailv ServiceFaxv ServiceFirstNamev ServiceFirmNamev ServiceMaxOutagev ServicePhonev ServiceRatev ServiceStatusv ServiceStreetv ServiceTypev ServiceZipv ServiceLevelv SupportLevelv StatusCodev ServiceMobilev ServiceLastNamev TicketIDv NetFlow Pack Propertyv NF_aggVIEWv NF_typev NF_srcv NF_dstv NF_cosv NF_customer

Properties used by the Tivoli Netcool PerformanceManager-enabled SAA probes

The following table lists the probe properties:

Probe Property Description

operation Test operation being executed for monitorprobes, RMON, and so on.

timeout Timeout duration (seconds) for targetresponse for monitor probes, RMON, and soon.

sourceIP IP address of the originating side forunidirectional entities (end-to-end simplexconnections, network test probes, and so on.)

sourceURL URL of the originating side forunidirectional entities (end-to-end simplexconnections, network test probes, etc.)


Probe Property Description

sourcePort IP port used on the originating side forunidirectional entities (end-to-end simplexconnections, network test probes, and so on.)

destIP IP address of the terminating side forunidirectional entities (end-to-end simplexconnections, network test probes, and so on.)

destURL URL of the terminating side forunidirectional entities (end-to-end simplexconnections, network test probes, and so on.)

destPort IP port used on the terminating side forunidirectional entities (End-to-end simplexconnections, network test probes, and so on.)

ProbeDefaultIPAddress IP address of probe

responderEnabled For latency probes, this identifies whether ornot a target will respond to the probe.

testActivationInterval Time between activations of a latency test. Alatency test does not run continuously. It isdormant for a period of time, activates, andsends one or more test packets/probes/requests.

testPacketInterval Interval between packets /probes/requestsfor a latency test that sends multiplepackets/probes/requests per test activation.

Exporting report user propertiesresmgr -export propertyRU -colNames "name invariant defValue state"-file $DIR/propertyRU.dat

# type = propertyRU


# filter = invariant(type<DVUser>)

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export propertyRU -colNames "name invariant defValuestate" -filter "invariant(type<DVUser>)"

DV_UserAccessScheduler|_|type<DVUser>|_||_|on|_|

DV_UserCSSFilename|_|type<DVUser>|_||_|on|_|

DV_UserCustomLogoFile|_|type<DVUser>|_||_|on|_|

DV_UserEnableFavoriteLink|_|type<DVUser>|_||_|on|_|

DV_UserFavoriteURL|_|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|_|


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 Description

DV_UserProfileDataView user-scope property defining thegeneral user type for control of certainsecurity options.

Valid settings:

v NOC - Network Operations Center user,few restrictions.

v PSLA - Proactive Service Level Agreementpersonnel, moderate restriction.

v SLA - End users, highest restriction.

DV_UserCustomLogoFile DataView user-scope property with a link toan image file statically defining a customgraphic for reporter summary headings.

DV_UserResourceNameDataView user-scope property that defineswhich sub-element name definitions shouldbe used for SE labels displayed to theparticular user.

Valid settings:

v 1 - Use the SEs' internal ALIAS fieldvalues (also dubbed "SE Labels").

v 2 - Use the SEs' internal NAME fieldvalues.

v 1771 - Use the value defined in the"customerFacingName" Property for eachSE.

DV_UserShowCurrentPeriodDataView user-scope property whichcontrols access to active-period reportviewing.

If equal to "true" or if undefined then theuser is allowed to view reports on thecurrent, active, possibly incomplete timeperiod.

Set to "false" for a user to disable the currentperiod view capability.



DV_UserEnableFavoriteLinkDataView user-scope property which enablesthe "Favorite Report" functionality (seeDV_UserFavoriteURL).

Valid settings are the strings 'true' and'false'. Any setting not equal to one of thesevalues is interpreted as 'false'. If 'true', the"Set Favorite Report" icon and the "GotoFavorite Report" icon are displayed on theportal. If 'false', then these icons are notdisplayed and the feature is disabled.

DV_UserFavoriteURL DataView user-scope property that specifiesa user's "Favorite" report. The value of thisproperty is a URL that generates a DataViewreport.

DV_UserWelcomeReporter DataView user-scope property that specifiesa Welcome Reporter, or a "home" page, for auser. The value of this user property is aDataView reporter ID. Immediatelyfollowing a user's initial Portal login, thisWelcome Reporter is generated, so long asfor that user no "Favorite Reporter"isdefined and active (seeDV_UserFavoriteURL andDV_UserEnableFavoriteLink).

DV_UserLoginName DataView user-scope property that can beset with the login name attributed to aDataView user. This Property is used forinformational display on Reporter summaryheadings only.

DV_UserName DataView user-scope property that can beset with the name attributed to a DataViewuser. This Property is used for informationaldisplay on Reporter summary headings only.

DV_UserProbeConfigAccessCan have 3 states

v read-write - the user has access to allprobe configuration/managementfunctionality.

v read-only - The user may access theconfiguration/management GUIs, butthey cannot save, modify or delete anyprobes via the GUI.

v null (or other value) - the user is restrictedfrom viewing either GUI. Null is the sameas not defining the property.



DV_UserProbeFileConfigAccessCan have 3 states

v read-write - the user has access to thefile-based probe configurationfunctionality.

v read-only - The user may access thefile-based probe configuration GUIs, butthey cannot save, modify or delete anyprobes via the GUI.

v null (or other value) - the user is restrictedfrom viewing the GUI.

DV_UserAccessScheduler Boolean that indicates if the user haspermission to configure the Scheduler."False" by default

DV_UserGranularitySetting Boolean that indicates if the user haspermission to set granularity. "False" bydefault (allows the user to access thegranularity setting section of his preferencepage.)

DV_UserGranularity_DAILY User granularity setting for daily time seriesreports. The default is "raw"

DV_UserGranularity_WEEKLY User granularity setting for weekly timeseries reports. The default is "30min"

DV_UserGranularity_MONTHLY User granularity setting for monthly timeseries reports. The default is "1day"

DV_UserGranularity_QUARTERLY User granularity setting for quarterly timeseries reports. The default is "1day"

DV_UserGranularity_YEARLY User granularity setting for yearly timeseries reports. The default is "1day"

DV_UserGranularity_14MONTHS User granularity setting for 14 months timeseries reports. The default is "1day"

Importing propertiesYou must use the name column for a new property. By default, dbIndex is takenfrom the DesignSequences column, comment is empty, state is on, and thedataType is string.

When updating properties, you must use the dbIndex or name columns, and thecolumns to be modified.

Importing subelement propertiesresmgr -import propertySE -colNames "name dataType defValuecomment" -sep "|" -line "ContactSE|string|none|property added fortest|"

Info : === insert : UPDATE ON property ( ContactSE ) (exists)

You must use the dbIndex or name column when deleting a property.


Deleting subelement propertyresmgr -delete propertySE -colNames "dbIndex" -line "100008275"

Info : === delete : DELETE ON property ( ContactSE ) (exists)

Working with thresholdsThis section contains the commands you can use to manage thresholds. When youuse resgmr to work with the thresholds, you work with the following object types:v thrdv

Exporting thresholdsresmgr -export thrdv -colNames "idxMetric idxGroup idxResourcefgp.nName segp.npath se.name mode_DECODE dteDate_DATEthrStat_DECODE thrCalc_DECODE thrCalcValue brstCrtclLevelbrstCrtclTime_TIME brstWrnngLevel brstWrnngTime_TIMEbrstGenEvent_DECODE prdCrtclLevel prdCrtclTime_TIME prdWrnngLevelprdWrnngTime_TIME prdGenEvent_DECODE prdPeriod_DECODE" -filter"mode_DECODE(Over)" -file $DIR/thrdv_over.dat

# type = thrdv

# col = idxMetric idxGroup idxResource fgp.nName segp.npath se.namemode_DECODE dteDate_DATE thrStat_DECODE thrCalc_DECODE thrCalcValuebrstCrtclLev

el brstCrtclTime_TIME brstWrnngLevel brstWrnngTime_TIMEbrstGenEvent_DECODE prdCrtclLevel prdCrtclTime_TIME prdWrnngLevelprdWrnngTime_TIME prdGenEv

ent_DECODE prdPeriod_DECODE

# filter = mode_DECODE(Over)

# order =

# sep = |_|

# sepRec =

# rule =

# filterRule =

#

# cmdLine = -export thrdv -colNames "idxMetric idxGroup idxResourcefgp.nName segp.npath se.name mode_DECODE dteDate_DATEthrStat_DECODE thrCalc_DEC

ODE thrCalcValue brstCrtclLevel brstCrtclTime_TIME brstWrnngLevelbrstWrnngTime_TIME brstGenEvent_DECODE prdCrtclLevelprdCrtclTime_TIME prdWrnngLev

el prdWrnngTime_TIME prdGenEvent_DECODE prdPeriod_DECODE" -filter"mode_DECODE(Over)"

2417|_|6397|_|0|_|~AP~Generic~Instrumentation~Other~Load OperationFailures (end of period)|_||_||_|Over|_|09/13/200121:35|_|sum|_|Standard|_||_|1.9|_|0s|_|.9|_|0s|_|no|_||_||_||_||_|no|_|All|_|

2416|_|6397|_|0|_|~AP~Generic~Instrumentation~Other~Load OperationFailures|_||_||_|Over|_|09/13/200121:35|_|sum|_|Standard|_||_|1.9|_|0s|_|.9|_|0s|_|no|_||_||_||_||_|no|_|All|_|

2415|_|6397|_|0|_|~AP~Generic~Instrumentation~Other~DatabaseFailures|_||_||_|Over|_|09/13/200121:35|_|sum|_|Standard|_||_|1.9|_|0s|_|.9|_|0s|_|no|_||_||_||_||_|no|_|All|_|

2264|_|6397|_|0|_|~AP~Generic~Universal~Utilization~StorageUtilization (percent)|_||_||_|Over|_|09/13/200121:35|_|raw|_|Standard|_||_|99|_|2h|_|98|_|2h|_|no|_||_||_||_||_|no|_|All|_|


Importing thresholdsYou must use the following columns for a new threshold. By default, idxGroupand idxResource = 0, all others are set to null.v fgp.nNamev mode

You can also include the following columns:v all

When updating thresholds, you must use the following columns:v (idxMetric or fgp.nName)+(idxGroup or segp.npath if not null)+(idxResource or

se.name if not null)v columns to be modifiedresmgr -import thrdv -colNames "fgp.nName segp.npath dteDate modethrStat thrCalc brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent prdPeriod prdGenEvent" -sep "|" -line"~AP~Specific~SNMP~RFC-1213~Interface~Outbound Utilization(percent) RFC-1213Interface|~test1|1025704759|2|0|0|3|2|60|120|1|1|0"

Info : === insert : INSERT ON Threshold ( 4741 0 ) (does notexist)


Deleting thresholdsYou must use the idx column to delete thresholds.resmgr -delete thrdv -colNames "idxMetric idxResource idxGroup"-sep "|" -line "4741|0|200003865|"

Info : === delete : DELETE ON Threshold ( 4741 0 ) (exists)

Working with requestsThese are the commands that you can use to manage requests. When you useresgmr to work with requests, you work with the following object types:v segpreq (collection requests)v pctile (aggregation requests)v allreq (all requests)

Exporting all requestsresmgr -export allreq -colNames "segp.npath fgp.nName period statestatus pctile type cal.name" -file $DIR/allreq.dat

# type = allreq

# col = segp.npath fgp.nName period state status pctile typecal.name

# filter =

# order =

# sep = |_|

# sepRec =

# cmdLine = -export allreq -colNames "segp.npath fgp.nName periodstate status pctile type cal.name"


~Sub-Element Collect~Router~Devices~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~CPU Utilization(percent) (avg last 5 minutes) Cisco 11. x RouterDevice|_|900|_|on|_|active|_||_|collection|_||_|

~Sub-Element Collect~Router~Devices~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~BufferUtilization (percent) Cisco 11.x RouterDevice|_|900|_|on|_|active|_||_|collection|_||_|

~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Restarts Cisco11.x Router RFC-1213Interface|_|900|_|on|_|active|_||_|collection|_||_|

~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Resets Cisco11.x Router RFC-1213Interface|_|900|_|on|_|active|_||_|collection|_||_|

~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound QueueDrops (PDUs) Cisco 11.x Router RFC-1213Interface|_|900|_|on|_|active|_||_|collection|_||_|

~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound QueueDrops (PDUs) Cisco 11.x Router RFC-1213Interface|_|900|_|on|_|active|_||_|collection|_||_|

~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound QueueDrops (percent) Cisco 11.x Router RFC-1213Interface|_|900|_|on|_|active|_||_|collection|_||_|

Exporting subelement group requestsresmgr -export segpreq -colNames "segp.npath fgp.nName period statestatus" -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 periodstate status"

~Sub-Element Collect~Router~Devices~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~BufferUtilization (percent) Cisco 11.x RouterDevice|_|900|_|on|_|active|_|

~Sub-Element Collect~Router~Devices~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~CPU Utilization(percent) (avg last 5 minutes) Cisco 11.x RouterDevice|_|900|_|on|_|active|_|

~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound QueueDrops (percent) Cisco 11.x Router RFC-1213Interface|_|900|_|on|_|active|_|

~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound QueueDrops (percent) Cisco 11.x Router RFC-1213Interface|_|900|_|on|_|active|_|


~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound QueueDrops (PDUs) Cisco 11.x Router RFC-1213Interface|_|900|_|on|_|active|_|

~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound QueueDrops (PDUs) Cisco 11.x Router RFC-1213Interface|_|900|_|on|_|active|_|

~Sub-Element Collect~Router~Interfaces~Cisco11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Resets Cisco11.x Router RFC-1213 Interface|_|900|_|on|_|active|_|

Exporting percentilesresmgr -export pctile -colNames "segp.npath fgp.nName state value"-file $DIR/pctile.dat

# type = pctile

# col = segp.npath fgp.nName state value

# filter =

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export pctile -colNames "segp.npath fgp.nName statevalue"

Importing requestsYou must use the following columns for new requests. By default, dbIndex is takenfrom the DesignSequences, period 900, idxCal is null, status idle, storage always,state = on, user = unix User, origin = resmgr, date = current date.v segp.npathv fgp.nName

You can also include the following columns:v periodv value for pctilev type+pctile for allreq

When updating requests, you must use the following columns:v segp.npathv fgp.nNamev columns to be modified

Importing percentilesresmgr -import "segpreq" -colNames "fgp.nName segp.npath statusstorage period cal.name" -line"~AP~Specific~SNMP~RFC-1213~Interface~Outbound Utilization(percent) RFC-1213 Interface|_|~Sub-ElementCollect|_|idle|_|always|_|900|_||_|"

Info : === insert : INSERT ON request ( 100008519 ) (does notexist)


Title : === CHANGES : {1 New of segpreq}

Info : === Inform Collector On hebus:3002


Deleting requestsYou must use the following columns when deleting requests.v segp.npathv fgp.nName

Deleting subelement group requestsresmgr -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)


Title : === CHANGES : {1 Deleted of segpreq}

Working with calendarsThis section contains the commands you can use to manage calendars. When youuse resgmr to work with calendars, you work with the cal object type.

Exporting calendarsThis command displays the list of calendars.resmgr -export cal -colNames "dbIndex name period state origin userdate_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 originuser date_DATE"

200|_|CME Permanent|_|900|_|on|_|APinstall|_|APdev|_|03/04/200100:16|_|

100006809|_|4 AM to 8 PM restrictedSLA|_|900|_|on|_|unknown|_||_||_|

Displaying list of calendarsresmgr -export cal -colNames "dbIndex name period state origin userdate_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 originuser date_DATE"

200|_|CME Permanent|_|900|_|on|_|APinstall|_|APdev|_|03/04/200100:16|_|

100006809|_|4 AM to 8 PM restrictedSLA|_|900|_|on|_|unknown|_||_||_|


Viewing calendar detailresmgr -export cal -colNames "comment type subType week fromDayfromTime 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 weekfromDay fromTime toDay toTime"

Daily, each day from 00:00 to04:00|_|1|_|1|_||_||_|00:00|_||_|04:00|_|

Daily, each day from 20:00 to23:59|_|1|_|1|_||_||_|20:00|_||_|23:59|_|

Importing calendarsUse the Tivoli Netcool Performance Manager DataMart GUI to create newcalendars and resmgr for Calendar deployment.

You must use the following columns for new Calendars. By default, dbIndex istaken from the DesignSequences, all other columns are empty.v namev period

When updating Calendars, you must use the following columns:v dbIndex or namev columns to be modified

Importing new calendar dataresmgr -import cal -colNames " name period state user origindate_DATE type subType comment week fromDay fromTime toDay toTime"-sep "|" -line "psmamoImport|300|on|pvuser|resmgr|09/15/200218:05|1|1|Daily, each day from 04:00 to 07:59|||04:00||07:59|"

Info : === insert : INSERT ON Calendar ( psmamoImport ) (does notexist)

Info : === insert : INSERT ON Calendar Contents ( psmamoImportDaily, each day from 04:00 to 07:59 ) (does not exist)

Deleting calendarsresmgr -delete cal -colNames " name" -line "psmamoImport"

Info : === delete : DELETE ON Calendar ( psmamoImport ) (exists)


Working with timezonesThis section contains the commands you can use to manage timezones. When youuse resgmr to work with timzones, you work with the following object type:v tz

Exporting timezonesExporting all the defined aggregation setsresmgr -export tz -colNames "dbIndex name date_DATE offset statuscomment" -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 offsetstatus comment"

0|_|GMT|_|04/09/2002 02:30|_|0|_|2|_|GMT|_|

0|_|EST_2002_DST|_|04/11/2002 17:00|_|-14400|_|2|_|Eastern StandardTime|_|

0|_|EST_2002|_|10/27/2002 10:00|_|-18000|_|2|_|Eastern StandardTime|_|





Exporting all the defined aggregation setsresmgr -export tz -colNames "dbIndex name date_DATE offset statuscomment" -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 offsetstatus comment"

0|_|GMT|_|04/09/2002 02:30|_|0|_|2|_|GMT|_|








Exporting only the currently active timezoneresmgr -export tz -colNames "dbIndex date_DATE offset statuscomment" -filter "date(%NOW%)" -file $DIR/tz_active.dat

# type = tz

# col = dbIndex date_DATE offset status comment

# filter = date(%NOW%)

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export tz -colNames "dbIndex date_DATE offset statuscomment" -filter "date(%NOW%)"

0|_|10/26/2003 10:00|_|-18000|_|2|_|Eastern Standard Time|_|

Working with inventory profilesThis section contains the commands you can use to manage Calendars. When youuse resgmr to work with calendars, you work with the following object types:v ogpv opt

Duplicating an inventory profileAbout this task

To duplicate an inventory profile, you need to export it and then import it. Forexample:

Procedure1. Enter the following command to export the profile quallaby:

resmgr -export ogp -isMandat "" -colNames "npath opt.nameopt.instance opt.value" -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.instanceopt.value" -file $DIR/ogp.dat

3. Import the profile.resmgr -import ogp -mode update -colNames "npath opt.nameopt.instance opt.value" -line"~prof1|_|100000115|_|duplicateIp|_|3|_|1|_|"

Info : === update : nothing ON Option Group ( ~prof1 ) (exists)

Info : === update : UPDATE ON Options ( 100000115 duplicateIp )(exists)

Info : === insert : nothing ON Link O/G ( 100000115 ~prof1 )(exists)



Importing inventory profilesYou must use the following columns for new inventory profiles.v npathv opt.namev opt.instancev opt.value

See an example of importing code in step 3 under “Duplicating an inventoryprofile” on page 125.

Deleting inventory profilesresmgr -delete ogp -colNames "npath" -line "~prof1"

Info : === DELETE GROUP : ~prof1 (index = 100008521)

Info : === delete : DELETE ON Option Group ( ~prof1 ) (exists)



Chapter 8. Managing administration objects

Explains how to use resmgr to manage administrative objects.

This chapter explains how to use resmgr to export, import, and different TivoliNetcool Performance Manager object types that belong to the Administrationcategory. Design objects include the following types:v Tivoli Netcool Performance Manager DataMart users and groupsv Registryv Miscellaneous Tivoli Netcool Performance Manager objects

Working with Tivoli Netcool Performance Manager DataMart users andgroups

This section contains the commands you can use to manage Tivoli NetcoolPerformance Manager DataMart users and groups. When you use resgmr to workwith the users and groups, you work with the following object types:v usrv uLinkv uPerm

Exporting users and groupsUse these commands to export users and groups.

Exporting usersresmgr -export usr -colNames "dbIndex name fullname gpnamegpcomment" -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|_|pvuser|_|Create for IBM integration|_|admin|_|Proviso DataMart Administrators|_|100008754|_|pvuser|_|Create for IBM integration|_|pvuser|_|Proviso DataMart Users|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|11|_|root|_|Proviso DataMart Administrator|_|admin|_|Proviso DataMart Administrators|_|100008755|_|vlad|_|User for IBM Integration|_|admin|_|Proviso DataMart Administrators|_|100008755|_|vlad|_|User for IBM Integration|_|pvuser|_|Proviso DataMart Users|_|

Exporting usersresmgr -export usr -colNames "dbIndex name fullname gpnamegpcomment module perms" -filter "name(pvuser)" -file$DIR/usr_perms.dat

# type = usr# col = dbIndex name fullname gpname gpcomment module perms# filter = name(pvuser)# order =# sep = |_|# sepRec =## cmdLine = -export usr -colNames "dbIndex name fullname gpname gpcomment module perms" -filter "name(pvuser)"

100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|calconf|_|w|_|


100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|calsel|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|cmdedit|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|collectinfo|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|collector|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|dabdedit|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|dabdmgr|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|dabdsel|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|dataviewer|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|dbmgr|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|formedit|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|formsel|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|impexp|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|inventory|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|mibbrow|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|mibcomp|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|pollinv|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|pollprofile|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|provisoinfo|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|pvmstat|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|reqedit|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|resedit|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|resmgr|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|ruleconf|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|snmpconf|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|threconf|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administrators|_|userconf|_|w|_|

Exporting groupsresmgr -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|_|dataviewer|_|w|_|default|_|Default Users|_|mibbrow|_|w|_|admin|_|Proviso DataMart Administrators|_|formedit|_|w|_|admin|_|Proviso DataMart Administrators|_|pollinv|_|w|_|admin|_|Proviso DataMart Administrators|_|pollprofile|_|w|_|admin|_|Proviso DataMart Administrators|_|reqedit|_|w|_|admin|_|Proviso DataMart Administrators|_|dabdedit|_|w|_|admin|_|Proviso DataMart Administrators|_|mibcomp|_|w|_|admin|_|Proviso DataMart Administrators|_|snmpconf|_|w|_|admin|_|Proviso DataMart Administrators|_|calconf|_|w|_|admin|_|Proviso DataMart Administrators|_|userconf|_|w|_|admin|_|Proviso DataMart Administrators|_|threconf|_|w|_|admin|_|Proviso DataMart Administrators|_|cmdedit|_|w|_|admin|_|Proviso DataMart Administrators|_|inventory|_|w|_|admin|_|Proviso DataMart Administrators|_|mibbrow|_|w|_|

Importing users and groupsUse these commands to import users and groups.

Creating a new user who belongs to an existing groupresmgr -import usr -colNames " name fullname gpname " -line"Paul|_|Paul Mc Cartney|_|Proviso DataMart Users|_|"

Info : === insert : INSERT ON User ( Paul ) (does not exist)Info : === insert : INSERT ON User Group ( Proviso DataMart Users ) (does not exist)Info : === insert : INSERT ON Link Group/User ( Paul Proviso DataMart Users ) (does not exist)

Creating a new groupIn this case we need to define access rights for each module.


resmgr -import usr -colNames "gpname gpcomment module perms"-file file.txt

with file.txt :new1|_|Proviso DataMart new1|_|formedit|_|w|_|new1|_|Proviso DataMart new1|_|pollinv|_|w|_|new1|_|Proviso 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|_|dataviewer|_|dbmgr|_|formedit|_|formsel|_|impexp|_|inventory|_|mibbrow|_|mibcomp|_|pollinv|_|pollprofile|_|provisoinfo|_|pvmstat|_|reqedit|_|resedit|_|resmgr|_|ruleconf|_|snmpconf|_|threconf|_|userconf|_|

Chapter 8. Managing administration objects 129

Deleting users and groupsUse these commands to delete users and groups.

Deleting usersresmgr -delete usr -colNames "name" -line "John"

Info : === delete : DELETE ON User ( John ) (exists)

Deleting groupsresmgr -delete usr -colNames "gpname" -line "group1"

You must ensure that you do not delete the following DataMart user groups:

Group Name Description

default Default Users.

admin Tivoli Netcool Performance ManagerDataMart Administrators.

pvuser Tivoli Netcool Performance ManagerDataMart Users.

Unlinking users from a groupresmgr -delete uLink -colNames "name gpname" -line"John|_|group1"

Working with registriesThis section contains the commands you can use to manage Tivoli NetcoolPerformance Manager registries.

When you use resgmr to work with the registries, you work with the followingobject types:v regisDMv regisDCv regisDCConfigv regisDBv regisDVv regisMG (regDesc)

Exporting registry objectsThis section contains the commands you can use to export Tivoli NetcoolPerformance Manager registries.

Exporting DataMart registryresmgr -export regisDM -colNames "path name value type" -file$DIR/regisDM.dat

# type = regisDM# col = path name value type# filter =# order =# sep = |_|# sepRec =## cmdLine = -export regisDM -colNames "path name value 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|_|Tivoli Netcool Performance Manager DataMart|_|1|_|DATAMART.1.VERSION|_|VERSION|_|V4.1_R2_E2 1245|_|1|_|DATAMART.1.HOST|_|HOST|_|pvdemo2|_|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|_|DATAMART.COMMON.Tivoli Netcool Performance ManagerINFO_SERVER.HOST|_|HOST|_|pvdemo2|_|1|_|DATAMART.COMMON.Tivoli Netcool Performance ManagerINFO_SERVER.RMI_URL|_|RMI_URL|_|//pvdemo2:3113/ProvisoInfoServer|_|1|_|DATAMART.COMMON.Tivoli Netcool Performance ManagerINFO_SERVER.PORT|_|PORT|_|3114|_|1|_|DATAMART.COMMON.Tivoli Netcool Performance ManagerINFO_SERVER.RMI_PORT|_|RMI_PORT|_|3113|_|1|_|DATAMART.COMMON.Tivoli Netcool Performance ManagerINFO_SERVER.SERVER_NAME|_|SERVER_NAME|_|ProvisoInfoServer|_|1|_|DATAMART.COMMON.Tivoli Netcool Performance ManagerINFO_SERVER.DATAMART_ID|_|DATAMART_ID|_|1|_|0|_|DATAMART.COMMON.TZCHECK|_|TZCHECK|_|TRUE|_|1|_|

Exporting DataChannel registryresmgr -export regisDC -colNames "path name value type" -file$DIR/regisDC.dat

# type = regisDC# col = path name value type# filter =# order =# sep = |_|# sepRec =## cmdLine = -export regisDC -colNames "path name value 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|_|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|_|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 registryresmgr -export regisDCConfig -colNames "path value" -file$DIR/regisDCConfig.dat

Exporting the configuration parameters for all CMEs:resmgr -noHead -export regisDCConfig -colNames "path value" -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 value" -filter"path(*SNMP.1.1*)"

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 registryresmgr -export regisDB -colNames "path name value type" -file$DIR/regisDB.dat

# type = regisDB# col = path name value type# filter =# order =# sep = |_|# sepRec =## cmdLine = -export regisDB -colNames "path name value 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/Proviso|_|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|_|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 recovering 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 version|_|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: Recovery 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 version|_|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 version|_|1|_|DATABASE.GENERAL.PATCHES.DB_PATCH1237_41.DATE|_|DATE|_|2003-10-02 18:06|_|2|_|

Exporting DataView registryresmgr -export regisDV -colNames "path name value type" -file$DIR/regisDV.dat

# type = regisDV# col = path name value type# filter =# order =# sep = |_|# sepRec =## cmdLine = -export regisDV -colNames "path name value 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|_|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|_|[email protected]|_|1|_|DATAVIEW.SCHEDULER.MASTER.DIRECTORY.NFS_BASE|_|NFS_BASE|_|/export/home/silverstream/SchedulerNFS|_|1|_|DATAVIEW.SCHEDULER.MASTER.FTP.BASE_DIRECTORY|_|BASE_DIRECTORY|_|/export/home/silverstream/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|_|<pvdemo1.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 registryresmgr -export regisMG -colNames "path name value type" -file$DIR/regisMG.dat

# type = regisMG# col = path name value type# filter =# order =# sep = |_|# sepRec =## cmdLine = -export regisMG -colNames "path name value 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 verificationresmgr -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|_|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|_|

Providing direct access to one registryresmgr -export regInst:CHANNELS -colNames "dbIndex IdxParent namenodeType value valType format" -DBUser ADMIN -file $DIR/regInst.dat


# type = regInst# col = dbIndex IdxParent name nodeType value valType format# filter =# order =# sep = |_|# sepRec =## cmdLine = -export regInst -colNames "dbIndex IdxParent name nodeType value valType 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 registriesDo not import to regisDCConfig as your import will be overwritten the next timeyou run the Topology Editor or Deployer.

Updating a registry value

Note: Only an administrator, DBUser ADMIN, can update this table.resmgr -import regisDM -colNames "path name value " -DBUser ADMIN-line "DATAMART.1.DESCRIPTION|_|DESCRIPTION|_|Test DBER ORA9|_|"

Info : === insert : UPDATE ON Registry ( DATAMART.1.DESCRIPTION ) (exists)

Deleting registriesRegistry does not have to be removed.

Working with miscellaneous Tivoli Netcool Performance Managerobjects

This section contains the commands you can use to manage the followingmiscellaneous Tivoli Netcool Performance Manager DataMart objects.v chnl: information about channelv reg: information about components that are runningv dbi: export Tivoli Netcool Performance Manager GUI information into CSV

formatv client: registration information about Tivoli Netcool Performance Manager

clientsv orausr: list of Oracle users


Working with chnl (information about collector)Use these commands to export channel information.resmgr -export chnl -colNames "collector default port host instDirname 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 commentdisplay pid user port status hostReg date_DATE"1|_|yes|_|3002|_|pvdemo3|_|/opt/dataload|_|pvmd_1|_|This module performsRequests and Real Time Queries|_|:0.0|_|1606|_|pvuser|_|3002|_|1|_|pvdemo3|_|10/02/2003 20:29|_|

Exporting channel informationresmgr -export chnl -colNames "collector default port host instDirname 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 namecomment display pid user port status hostReg date_DATE"1|_|yes|_|3002|_|pvdemo3|_|/opt/dataload|_|pvmd_1|_|This module performs Requestsand Real Time Queries|_|:0.0|_|1606|_|pvuser|_|3002|_|1|_|pvdemo3|_|10/02/2003 20:29|_|

Working with regUse these commands to Export all locks.resmgr -export reg -colNames "name host port comment display piduser 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"provisoinfod|_|pvdemo2.quallaby.com|_|3114|_|provisoinfo daemon|_|localhost:0.0|_|13288|_|pvuser|_|3114|_|1|_|10/02/2003 19:08|_|provisoinfod|_|1|_|pvmd_1|_|pvdemo3|_|3002|_|This module performs Requests and Real Time Queries|_|:0.0|_|1606|_|pvuser|_|3002|_|1|_|10/02/2003 20:29|_|pvmd_1|_|1|_|snmpconf|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|17561|_|pvuser|_|0|_|0|_|11/04/2003 00:12|_|snmpconf|_|1|_|

Exporting all locksresmgr -export reg -colNames "name host port comment display piduser 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"provisoinfod|_|pvdemo2.quallaby.com|_|3114|_|provisoinfo daemon|_|localhost:0.0|_|13288|_|pvuser|_|3114|_|1|_|10/02/2003 19:08|_|provisoinfod|_|1|_|pvmd_1|_|pvdemo3|_|3002|_|This module performs Requests and Real Time Queries|_|:0.0|_|1606|_|pvuser|_|3002|_|1|_|10/02/2003 20:29|_|pvmd_1|_|1|_|snmpconf|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|17561|_|pvuser|_|0|_|0|_|11/04/2003 00:12|_|snmpconf|_|1|_|


Exporting all registered modulesresmgr -export reg -colNames "name host port comment display piduser 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"provisoinfod|_|pvdemo2.quallaby.com|_|3114|_|provisoinfo daemon|_|localhost:0.0|_|13288|_|pvuser|_|3114|_|1|_|10/02/2003 19:08|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|14297|_|pvuser|_|0|_|0|_|10/06/2003 15:55|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|18508|_|pvuser|_|0|_|0|_|10/06/2003 19:37|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|12218|_|pvuser|_|0|_|0|_|10/17/2003 01:32|_|pvmd_1|_|pvdemo3|_|3002|_|This module performs Requests and Real Time Queries|_|:0.0|_|1606|_|pvuser|_|3002|_|1|_|10/02/2003 20:29|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|17388|_|pvuser|_|0|_|0|_|10/10/2003 23:39|_|resedit|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|17396|_|pvuser|_|0|_|0|_|10/10/2003 23:39|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|22016|_|pvuser|_|0|_|0|_|10/17/2003 17:50|_|resedit|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|12223|_|pvuser|_|0|_|0|_|10/17/2003 01:32|_|collectinfo|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|23256|_|pvuser|_|0|_|0|_|10/28/2003 20:04|_|resedit|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|22021|_|pvuser|_|0|_|0|_|10/17/2003 17:50|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|14576|_|pvuser|_|0|_|0|_|10/23/2003 18:51|_|resedit|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|14581|_|pvuser|_|0|_|0|_|10/23/2003 18:51|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|23111|_|pvuser|_|0|_|0|_|10/28/2003 19:46|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|6011|_|pvuser|_|0|_|0|_|10/01/2003 19:53|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|14810|_|pvuser|_|0|_|0|_|11/03/2003 19:18|_|pvm|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|6032|_|pvuser|_|0|_|0|_|10/01/2003 19:54|_|resedit|_|pvdemo2.quallaby.com|_|0|_|NONE|_|dhcp114:0.0|_|6038|_|pvuser|_|0|_|0|_|10/01/2003 19:54|_|

Removing a register or lock moduleresmgr -delete reg -colNames "name host" -line "pvm|_|host1"

Working with dbiUse these commands to export database information.resmgr -export dbi -colNames "dbIndex name type objId label desc"-DBUser ADMIN -file $DIR/dbi.dat-DBUser ADMIN -file $DIR/orausr.dat

# type = dbi# col = dbIndex name type objId label desc# filter =# order =# sep = |_|# sepRec =# rule =# filterRule =## cmdLine = -export dbi -colNames "dbIndex name type objId label desc"1|_|Identification|_|Identification|_|1|_|Database Server|_|Database Server Name = tnpminlnx0202.persistent.co.inDatabase Name= PVCurrent Database User = PV_ADMINDB2 v10.1.0.1

Total Database shared memory = 3033.58 M


- Buffer pools = 1360.97 M- Database heap = 18.4 M- Lock list memory = 64.13 M- Utility heap size = 302.44 M- Package cache size = 1121.03 M- Sort heap threshol = 166.61 M

|_|1|_|Identification|_|Identification|_|1|_|Description|_|Last Refresh Date= 2013-09-13 04:18:07Last Refresh Duration = 1,074.130 sec |_|6|_|Proviso Version|_|Information|_|10|_|Version Summary|_|

For limited use (checking for problems after installation)

Exporting registration information about Tivoli NetcoolPerformance Manager clients

Note: Give this command in a single line.resmgr -export client -colNames "login channelId type orausr.nameorausr.tempTS orausr.globTempTS" -DBUser ADMIN

# type = client# col = login channelId type orausr.name orausr.tempTS orausr.globTempTS# filter =# order =# sep = |_|# sepRec =# rule =# filterRule =## cmdLine = -export client -colNames "login channelId type orausr.name orausr.tempTS orausr.globTempTS"PV_ADMIN|_||_|ADMIN|_|PV_ADMIN|_|TEMPSPACE1|_|GTTTBSP|_|PV_METRIC|_||_|METRIC|_|PV_METRIC|_|TEMPSPACE1|_|GTTTBSP|_|PV_INSTALL|_||_|INSTALL|_|PV_INSTALL|_|TEMPSPACE1|_|GTTTBSP|_|PV_CHNL_MANAGER|_||_|CHNL_MANAGER|_|PV_CHNL_MANAGER|_|TEMPSPACE1|_|GTTTBSP|_|PV_GUI|_||_|GUI|_|PV_GUI|_|TEMPSPACE1|_|GTTTBSP|_|PV_INVENTORY|_||_|INVENTORY|_|PV_INVENTORY|_|TEMPSPACE1|_|GTTTBSP|_|PV_LOIS|_||_|LOIS|_|PV_LOIS|_|TEMPSPACE1|_|GTTTBSP|_|PV_REPORT|_||_|REPORT|_|PV_REPORT|_|TEMPSPACE1|_|GTTTBSP|_|PV_REPORTMASTER|_||_|REPORTMASTER|_|PV_REPORTMASTER|_|TEMPSPACE1|_|GTTTBSP|_|PV_RESMGR|_||_|RESMGR|_|PV_RESMGR|_|TEMPSPACE1|_|GTTTBSP|_|PV_BACKUP|_||_|BACKUP|_|PV_BACKUP|_|TEMPSPACE1|_|GTTTBSP|_|PV_CHNL_RECOMP|_||_|CHNL_RECOMP|_|PV_CHNL_RECOMP|_|TEMPSPACE1|_|GTTTBSP|_|PV_OPERATOR|_||_|OPERATOR|_|PV_OPERATOR|_|TEMPSPACE1|_|GTTTBSP|_|PV_LDR_01|_|1|_|LDR|_|PV_LDR_01|_|TEMPSPACE1|_|GTTTBSP|_|PV_LDR24_01|_|1|_|LDR24|_|PV_LDR24_01|_|TEMPSPACE1|_|GTTTBSP|_|PV_CHANNEL_01|_|1|_|CHANNEL|_|PV_CHANNEL_01|_|TEMPSPACE1|_|GTTTBSP|_|PV_COLL_01|_||_|COLL|_|PV_COLL|_|TEMPSPACE1|_|GTTTBSP|_|PV_LDR_02|_|2|_|LDR|_|PV_LDR_02|_|TEMPSPACE1|_|GTTTBSP|_|PV_LDR24_02|_|2|_|LDR24|_|PV_LDR24_02|_|TEMPSPACE1|_|GTTTBSP|_|PV_CHANNEL_02|_|2|_|CHANNEL|_|PV_CHANNEL_02|_|TEMPSPACE1|_|GTTTBSP|_|PV_COLL_03|_||_|COLL|_|PV_COLL|_|TEMPSPACE1|_|GTTTBSP|_|

Exporting list of DB2 usersresmgr -export orausr -colNames "name tempTS" -DBUser ADMIN

# type = orausr# col = name tempTS# filter =# order =# sep = |_|# sepRec =# rule =# filterRule =## cmdLine = -export orausr -colNames "name tempTS"DB2|_|TEMPSPACE1|_|PV|_|TEMPSPACE1|_|PV_ADMIN|_|TEMPSPACE1|_|PV_BACKUP|_|TEMPSPACE1|_|PV_CHANNEL_01|_|TEMPSPACE1|_|


PV_CHANNEL_02|_|TEMPSPACE1|_|PV_CHNL_MANAGER|_|TEMPSPACE1|_|PV_CHNL_RECOMP|_|TEMPSPACE1|_|PV_COLL|_|TEMPSPACE1|_|PV_GUI|_|TEMPSPACE1|_|PV_INSTALL|_|TEMPSPACE1|_|PV_INVENTORY|_|TEMPSPACE1|_|PV_LDR24_01|_|TEMPSPACE1|_|PV_LDR24_02|_|TEMPSPACE1|_|PV_LDR_01|_|TEMPSPACE1|_|PV_LDR_02|_|TEMPSPACE1|_|PV_LOIS|_|TEMPSPACE1|_|PV_METRIC|_|TEMPSPACE1|_|PV_OPERATOR|_|TEMPSPACE1|_|PV_REPORT|_|TEMPSPACE1|_|PV_REPORTMASTER|_|TEMPSPACE1|_|PV_RESMGR|_|TEMPSPACE1|_|


Chapter 9. Managing report objects

Explains how to use resmgr to manage report objects and to export, import, anddifferent Tivoli Netcool Performance Manager object types that belong to the reportcategory.

Report includes the following object types:v Web usersv Applicationsv Scheduler


Working with web usersThis section contains the commands you can use to manage web users. When youuse resgmr to work with web users, you work with the following object types:v rusrv ownerv ruprpv rupropertyv rugpv linkGroupRU

Exporting web userUse these commands to export report user name and properties.resmgr -export rusr -colNames "name ruprp.name ruprp.value" -file$DIR/rusr_ruprp.dat

# type = rusr

# col = name ruprp.name ruprp.value

# filter =

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export rusr -colNames "name ruprp.name ruprp.value"

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|_|


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_UserEnableFavoriteLink|_|true|_|DV_UserFavoriteURL|_|subElmtID%3Dnull%26subElmtGrpID%3D100001470%26timeSpan%3Dday%26reporterID%3D100001619%26startTime%3D2003.10.06.00.00.00%26relativePeriod%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|_|1day|_|DV_UserGranularity_WEEKLY|_|30minutes|_|DV_UserGranularity_YEARLY|_|1day|_|DV_UserPreferenceAccess|_|true|_|DV_UserProfile|_|SLA|_|DV_UserResourceName|_|100000919|_|DV_UserShowCurrentPeriod|_|true|_|DV_UserWelcomeReporter|_|100001619|_|customerlogin|_|bt|_|customerlogo|_|BT.gif|_|customerwelcome|_|BritishTelecom|_|

Exporting report user name and propertiesresmgr -export rusr -colNames "name ruprp.name ruprp.value" -file$DIR/rusr_ruprp.dat

# type = rusr

# col = name ruprp.name ruprp.value

# filter =

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export rusr -colNames "name ruprp.name ruprp.value"

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|_|

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_UserEnableFavoriteLink|_|true|_|DV_UserFavoriteURL|_|subElmtID%3Dnull%26subElmtGrpID%3D100001470%26timeSpan%3Dday%26reporterID%3D100001619%26startTime%3D2003.10.06.00.00.00%26relativePeriod%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|_|1day|_|DV_UserGranularity_WEEKLY|_|30minutes|_|DV_UserGranularity_YEARLY|_|1day|_|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 usersresmgr -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|_||_|Tivoli Netcool Performance ManagerUSER|_|

100000149|_|SSSW\\noc|_||_|Tivoli Netcool Performance ManagerUSER|_|

100000152|_|SSSW\\coca|_||_|Tivoli Netcool Performance ManagerUSER|_|

100000153|_|SSSW\\quallaby|_||_|Tivoli Netcool Performance ManagerUSER|_|

100000154|_|SSSW\\business|_||_|Tivoli Netcool Performance ManagerUSER|_|

100015938|_|SSSW\\cargill|_||_|Tivoli Netcool Performance ManagerUSER|_|

100007838|_|SSSW\\cisco|_||_|Tivoli Netcool Performance ManagerUSER|_|

100007863|_|SSSW\\ciscodemo|_||_|Tivoli Netcool Performance ManagerUSER|_|

100008522|_|SSSW\\design|_||_|Tivoli Netcool Performance ManagerUSER|_|

100008064|_|SSSW\\realtime|_||_|Tivoli Netcool Performance ManagerUSER|_|

100009714|_|SSSW\\tt2|_||_|Tivoli Netcool Performance ManagerUSER|_|

100009717|_|SSSW\\tt1|_||_|Tivoli Netcool Performance ManagerUSER|_|

100009991|_|SSSW\\xtra|_||_|Tivoli Netcool Performance ManagerUSER|_|

100009812|_|SSSW\\adminfcar|_||_|Tivoli Netcool Performance ManagerUSER|_|

100009843|_|SSSW\\juniper|_||_|Tivoli Netcool Performance ManagerUSER|_|

100020250|_|SSSW\\flagtelecom|_||_|Tivoli Netcool PerformanceManager USER|_|

100020666|_|Frankie|_|[email protected]|_|EMAIL RECIPIENT|_|

Exporting report users groupresmgr -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|_|

Chapter 9. Managing report objects 145

~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\\ciscodev|_|

~Users|_|SSSW\\timl|_|

~DV [Internal Use Do Not Remove]|_|SSSW\\SuperUser|_|

~Orphans|_|SSSW\\bt|_|

Importing web userUse these commands to import a new customer with a property.

If you want to import a new customer called customer1 with a property calledproperty1 you can use the following command.resmgr -import rusr -colNames "name ruprp.property1:value" -line"SSSW\\\\customer1|_|value_property1"

Info : === insert : nothing ON Report User ( SSSW\\customer1 )(exists)

Info : === insert : INSERT ON property ( property1 ) (does notexist)

Info : === insert : INSERT ON Ruser property ( 100000265 100008523value_property1 ) (does not exist)

Importing a new customer with a propertyIf you want to import a new customer called customer1 with a property calledproperty1 you can use the following command.resmgr -import rusr -colNames "name ruprp.property1:value" -line"SSSW\\\\customer1|_|value_property1"


Info : === insert : INSERT ON property ( property1 ) (does notexist)

Info : === insert : INSERT ON Ruser property ( 100000265 100008523value_property1 ) (does not exist)

Grouping this customerresmgr -import rugp -colNames "npath rusr.name" -line"~Group1|_|SSSW\\\\customer1"

Info : === insert : nothing ON Ruser Group ( ~Group1 ) (exists)


Info : === insert : INSERT ON Link RU/RUG ( SSSW\\customer1 Group1) (does not exist)


Deleting web userUse these command to delete a report user (name or index).resmgr -delete rusr -colNames "name" -line "SSSW\\\\customer1"

Info : === delete : DELETE ON Report User ( SSSW\\customer1 )(exists)

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 groupresmgr -delete linkGroupRU -colNames "npath rusr.name" -line"~Group1|_|SSSW\\\\customer1"

Info : === delete : DELETE ON Link RU/RUG ( SSSW\\customer1 Group1) (exists)


Deleting just the value of the property for a report userresmgr -delete ruproperty -colNames "name ruprp.name" -line"SSSW\\\\customer1|_|property1"

Info : === delete : DELETE ON Ruser property ( 100008524 100008523value_property1 ) (exists)

Deleting a group of report usersresmgr -delete rugp -colNames "npath" -line "~Group1"

Info : === DELETE GROUP : ~Group1 (index = 100007970)

Info : === delete : DELETE ON Ruser Group ( ~Group1 ) (exists)


Working with reportersThis section contains the commands you can use to manage reporters and reporterstylesheets. When you use resgmr to work with reporters, you work with thefollowing object types:v appv agpv appS (report Style)v linkGroupAPPv linkGroupAPPS

Exporting reportersUse these commands to exporting report styles.resmgr -export appS -sepRec "<E>" -colNames "dbIndexdefinition comment name type" -order "dbIndex" -filter "name(APTopN Chart Style - Bar - DD Details - min avg max)" -file$DIR/appS.dat

# type = appS

# col = dbIndex definition comment name type

# filter = name(AP TopN Chart Style - Bar - DD Details - min avgmax)

# order = dbIndex

# sep = |_|


# sepRec = <E>

#

# cmdLine = -export appS -colNames "dbIndex definition comment nametype" -filter "name(AP TopN Chart Style - Bar - DD Details - minavg 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 forDetails"/>

</appearance>

<threeDEffect depth="0" elevation="0" rotation="0"effect="false"/>

<views>

<view type="bar" legend="true" visible="true">

<serie>

<line size="1" style="">

<color r="150" g="150"b="255">line</color>

</line>

</serie>

<serie>



</line>

</serie>

<serie>



</line>

</serie>

<serie>



</line>

</serie>

<serie>



</line>

</serie>

<serie>




<text>

<font name="arial" size="9" style="plain"/>

<text-advanced alignment="center"orientation="horizontal" rotation="0"/>

</text>

<appearance opaque="false">


<color r="0" g="51"b="51">foreground</color>

<border type="empty"/>

</appearance>

<location visible="false" x="310" y="465" w="80" h="14"anchor=""/>

</footer>

<size width="700" height="500"/>

</chart> |_|Comment here|_|AP TopN Chart Style - Bar - DDDetails - min avg max|_|0|_|<E>

Exporting report stylesresmgr -export appS -sepRec "<E>" -colNames "dbIndexdefinition comment name type" -order "dbIndex" -filter "name(APTopN Chart Style - Bar - DD Details - min avg max)" -file$DIR/appS.dat

# type = appS

# col = dbIndex definition comment name type

# filter = name(AP TopN Chart Style - Bar - DD Details - min avgmax)

# order = dbIndex

# sep = |_|

# sepRec = <E>

#

# cmdLine = -export appS -colNames "dbIndex definition comment nametype" -filter "name(AP TopN Chart Style - Bar - DD Details - minavg max)"

6073|_|<chart>

<appearance opaque="true">


<color r="0" g="0" b="0">foreground</color>

<border type="titled" title="Click any bar forDetails"/>

</appearance>

<threeDEffect depth="0" elevation="0" rotation="0"effect="false"/>

<views>

<view type="bar" legend="true" visible="true">

<serie>



</line>

</serie>


<serie>



</line>

</serie>

<serie>



</line>

</serie>

<serie>



</line>

</serie>

<serie>



</line>

</serie>

<serie>



<text>

<font name="arial" size="9" style="plain"/>

<text-advanced alignment="center"orientation="horizontal" rotation="0"/>

</text>

<appearance opaque="false">


<color r="0" g="51"b="51">foreground</color>

<border type="empty"/>

</appearance>

<location visible="false" x="310" y="465" w="80" h="14"anchor=""/>

</footer>

<size width="700" height="500"/>

</chart> |_|Comment here|_|AP TopN Chart Style - Bar - DDDetails - min avg max|_|0|_|<E>

Exporting report group stylesheetsresmgr -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 avgmax|_|

~AP Styles|_|AP Baseline Chart Style - avg max|_|

~AP Styles|_|AP RV Chart Style - avg|_|

~AP Styles|_|AP TS Chart Style - Line - avg|_|

~AP Styles|_|AP TS Chart Style - Bar - min avg 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 avg max|_|

~AP Styles|_|AP TS Chart Style - Area - max avg|_|

~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 - avg|_|

~AP Styles|_|AP TS Chart Style - Bar 3-D - avg|_|

~AP Styles|_|AP TopN Chart Style - Bar - DD Details - avg max|_|

~AP Styles|_|AP TopN Chart Style - Bar - DD Details - avg|_|

Exporting report groupresmgr -export agp -colNames "dbIndex npath app.name" -file$DIR/agp_app.dat

# type = agp

# col = dbIndex npath app.name

# filter =

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export agp -colNames "dbIndex npath app.name"

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceVolume Resource Detail Chart|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceVolume Resource|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceVolume Resource Threshold - Inbound Volume (octets)|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceVolume Resource Threshold - Inbound Throughput (bps)|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceVolume Resource Threshold - Outbound Volume (octets)|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceVolume Resource Threshold - Outbound Throughput (bps)|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceUtilization Resource Detail Chart|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceUtilization Resource Threshold - Inbound Utilization (percent)|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceUtilization Resource Threshold - Inbound Throughput (bps)|_|


7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceUtilization Resource Threshold - Outbound Utilization (percent)|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceUtilization Resource Threshold - Outbound Throughput (bps)|_|

7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|InterfaceUtilization Group|_|

7396|_|~AP MIB-II Pack~Interface~Availability Metrics|_|InterfaceAvailability Resource Detail Chart|_|

7396|_|~AP MIB-II Pack~Interface~Availability Metrics|_|InterfaceAvailability Resource Threshold - Inbound Loss|_|

7396|_|~AP MIB-II Pack~Interface~Availability Metrics|_|InterfaceAvailability Resource Threshold - Availability|_|

Exporting reportresmgr -export app -sepRec "<E>" -colNames "dbIndex namecomment 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 typedata"

4250|_|GST - IPSec - Phase-1 Volume and Throughput (secondlevel)|_|AP IPSec generic pack memberreporter|_|PVLsGroupSummaryTable_centerTitle.html|_|1

|_|"UserLogin.text=$USERPROPERTY:DV_UserLoginName"

"UserWelcome.link="

"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="


"groupSummaryTable.formula6.stats.labels="

"UserWelcome.text=Welcome $USERPROPERTY:DV_UserName"


.....

"UserLogo.link="

"groupSummaryTableMediator.formula2.stats=sum"

"groupSummaryTableMediator.formula4.stats=avg max"

"groupSummaryTable.formula6.metrics.labels="

"groupSummaryTable.formula2.metrics.labels="

"UpScaleNav.monthly.enable=true"

"reportSummary.text=$REPORT_PERIOD Group Summary Report -$START_TIME"


"DownScaleNav.yearly.enable=true"

"reportTitle.link="

"groupSummaryTable.formula4.drilldown.reporter=4547"|_|<E>

Importing reporters

New appYou 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:v urlv data type

New appSYou must use the name column when importing new application style sheets. Bydefault, dbIndex is taken from the DesignSequences, comment, definition is null,and type =0.

You can also include the following columns:v definitionv commentv type

Updating app and appSWhen updating existing applications and application style sheets, you must use thedbIndex or name columns, and the columns to be modified.

Importing the file reportStyle.txt after modifying itresmgr -import appS -sepRec "<E>" -colNames "dbIndexdefinition 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 isreported 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 areport. Another method is to manually modify the dbIndex in the export file.resmgr -import app -sepRec "<E>" -colNames "nop name commenturl type data" -file /tmp/report.txt


Importing application groupresmgr -import agp -colNames "npath app.name" -line "~AP MIB-IIPack~Interface~TEST1|_|Interface Availability Resource Threshold -Availability|_|"

Info : === insert : INSERT ON Application Group ( ~AP MIB-IIPack~Interface~TEST1 ) (does not exist)

Info : === insert : nothing ON Application ( InterfaceAvailability Resource Threshold - Availability ) (exists)


Info : === insert : INSERT ON Link App/AppGroup ( InterfaceAvailability Resource Threshold - Availability TEST1 ) (does notexist)


Importing application group style sheetsresmgr -import agp -colNames "npath appS.name" -line "~AP MIB-IIPack~Interface~TEST1|_|AP TS Chart Style - Line - White - sum|_|"

Info : === insert : nothing ON Application Group ( ~AP MIB-IIPack~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)


Deleting reporters and reporter stylesheetsYou must use the name column when importing new applications. Mandatory colsfor app or appS : dbIndex or name

Mandatory cols for agp : dbIndex or npath

Deleting report stylesheetsresmgr -delete appS -colNames "name" -line "Import new reportstyle"

Info : === delete : nothing ON report style ( Import new reportstyle ) (does not exist)

Deleting reportresmgr -delete app -colNames "name" -line "New GST"

Info : === delete : nothing ON Application ( New GST ) (does notexist)

Deleting group reportresmgr -delete agp -colNames "npath" -line "~AP MIB-IIPack~Interface~TEST1"

Info : === DELETE GROUP : ~AP MIB-II Pack~Interface~TEST1 (index =100008525)

Info : === delete : DELETE ON Application Group ( ~AP MIB-IIPack~Interface~TEST1 ) (exists)


Unlinking a report from a report groupresmgr -delete linkGroupAPP -colNames "npath app.name" -line "~APMIB-II Pack~Interface~TEST1|_|Interface Availability ResourceThreshold - Availability"

Info : === delete : DELETE ON Link App/AppGroup ( InterfaceAvailability Resource Threshold - Availability TEST1 ) (exists)


Unlinking a report style from a report groupresmgr -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)



Working with schedulerThis section contains the commands you can use to manage scheduler. When youuse resgmr to work with scheduler, you work with the sched object type.

Exporting schedulerExporting general informationresmgr -export regisDV -colNames "path name value 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|_|

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|_|[email protected]|_|1|_|

DATAVIEW.SCHEDULER.MASTER.DIRECTORY.NFS_BASE|_|NFS_BASE|_|/export/home/silverstream/SchedulerNFS|_|1|_|

DATAVIEW.SCHEDULER.MASTER.FTP.BASE_DIRECTORY|_|BASE_DIRECTORY|_|/export/home/silverstream/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|_|<pvdemo1.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 general informationresmgr -export regisDV -colNames "path name value 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|_|

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|_|[email protected]|_|1|_|

DATAVIEW.SCHEDULER.MASTER.DIRECTORY.NFS_BASE|_|NFS_BASE|_|/export/home/silverstream/SchedulerNFS|_|1|_|

DATAVIEW.SCHEDULER.MASTER.FTP.BASE_DIRECTORY|_|BASE_DIRECTORY|_|/export/home/silverstream/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|_|<pvdemo1.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 informationresmgr -export sched -colNames "dbIndex name frequency state statusstart_DATE end_DATE type" -file $DIR/sched.dat# type = sched# col = dbIndex name frequency state status start_DATE end_DATEtype# filter =# order =# sep = |_|# sepRec = <E>## cmdLine = -export sched -colNames "dbIndex name frequency statestatus start_DATE end_DATE type"49000001|_|DAILY|_|DAILY|_|Assigned|_|http://pvdemo1.quallaby.com:8080/DV41|_|10/06/200304:00|_|01/01/1970 04:00|_|DVCR|_|<E>49000001|_|DAILY|_|DAILY|_|Suspended|_|Suspended|_|10/06/200304:00|_|01/01/1970 04:00|_|DVCR|_|<E>49000001|_|DAILY|_|DAILY|_|Suspended|_|Suspended|_|10/06/200304:00|_|01/01/1970 04:00|_|DVCR|_|<E>49000003|_|MONTHLY|_|MONTHLY|_|Suspended|_|Suspended|_|10/07/200304:00|_|01/01/1970 04:00|_|DVCR|_|<E>


49000001|_|DAILY|_|DAILY|_|Suspended|_|Suspended|_|10/08/200304:00|_|10/09/2003 04:00|_|DVCR|_|<E>49000001|_|DAILY|_|DAILY|_|Suspended|_|Suspended|_|10/09/200304:00|_|01/01/1970 04:00|_|DVCR|_|<E>49000002|_|WEEKLY|_|WEEKLY|_|Suspended|_|Suspended|_|10/17/200304:00|_|01/01/1970 04:00|_|DVCR|_|<E>

Exporting scheduler consolidated reportresmgr -export sched -colNames "name app.name" -file$DIR/sched_app.dat

# type = sched# col = name app.name# filter =

# order =

# sep = |_|

# sepRec = <E>

#

# cmdLine = -export sched -colNames "name app.name"

DAILY|_|Daily Business Summary|_|<E>

DAILY|_|Daily High Level Summary|_|<E>

MONTHLY|_|Monthly SLA Report whole customers|_|<E>

DAILY|_|Tims Test Task|_|<E>

DAILY|_|Essai devoteam|_|<E>

DAILY|_|Sales|_|<E>

WEEKLY|_|Mcer|_|<E>

Export scheduler email recipientresmgr -export sched -colNames "name app.name rusr.name rusr.mailrusr.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.namerusr.mail rusr.type"

DAILY|_|Daily BusinessSummary|_|Frankie|_|[email protected]|_|EMAILRECIPIENT|_|<E>

DAILY|_|Daily High LevelSummary|_|Frankie|_|[email protected]|_|EMAILRECIPIENT|_|<E>


DAILY|_|Tims Test Task|_|Tim|_|[email protected]|_|EMAILRECIPIENT|_|<E>

WEEKLY|_|Mcer|_|Marcus|_|[email protected]|_|EMAILRECIPIENT|_|<E>

MONTHLY|_|Monthly SLA Report wholecustomers|_|Marcus|_|[email protected]|_|EMAILRECIPIENT|_|<E>

DAILY|_|Essai devoteam|_|fama|_|[email protected]|_|EMAILRECIPIENT|_|<E>

DAILY|_|Sales|_|FAMA|_|[email protected]|_|EMAILRECIPIENT|_|<E>

DAILY|_|Sales|_|FDOU|_|[email protected]|_|EMAILRECIPIENT|_|<E>

Importing schedulerUse the export file , modify it and reimport it with the same column names.

Deleting schedulerresmgr -delete sched -colNames "name"


Chapter 10. Managing history table and sequence objects

Explains how to use resmgr to manage history table and sequence objects.


Note: IBM recommends you work with IBM Support when working with historytables.

Working with history tablesThis section contains the commands you can use to manage history tables. Whenyou use resgmr to work with history tables, you work with the following objecttypes:v calHv frmHv thrdvHv eltHv seHv segpreqHv appHv segpHv egpH

In addition, history tables includes the following object types:v dte: this object type, date of the modification, includes the same columns as the

dte found in non-historical tables.v action: this object type is specific to the history table and is only accessible with

the seH table. The available values include:v I for insertedv D for deletedv U for updated

Exporting history tablesYou cannot link from a history object type to a similar object type in a non-historytable.

Exporting subelement history tableresmgr -export seH -colNames "dbIndex invariant elt.name namelabel instance state origin date_DATE action dte_DATE" -file$DIR/seH.dat

# type = seH# col = dbIndex invariant elt.name name label instance stateorigin date_DATE action dte_DATE# filter =# order =# sep = |_|# sepRec =## cmdLine = -export seH -colNames "dbIndex invariant elt.name namelabel instance state origin date_DATE action dte_DATE"


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|_|inventory|_|04/10/200201: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/200220: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|_|inventory|_|11/20/200200: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|_|inventory|_|04/10/200201: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/200220: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|_|inventory|_|12/04/200223: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/200318:47|_|U|_|05/28/2003 18:47|_|100000224|_||_|dev3.quallaby.com|_|dev3.quallaby.com_If<1>|_|dev3_IF:1 (10Mbps)|_|If<1>|_|on|_|inventory|_|04/10/200201:16|_|I|_|04/10/2002 01:16|_|100000224|_||_|dev3.quallaby.com|_|dev3.quallaby.com_If<1>|_|dev3_IF:1 (10Mbps)|_|If<1>|_|on|_|resmgr|_|04/15/200220: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|_|inventory|_|04/10/200201: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/200220:10|_|U|_|04/15/2002 20:10|_|

Exporting subelement history table with link to element in thepastYou 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 elementhistory table (eltH.)resmgr -export seH -colNames "dbIndex invariant hostIdx name labelinstance state origin date_DATE action dte_DATE" -file$DIR/seH_elt.dat# type = seH# col = dbIndex invariant hostIdx name label instance state origindate_DATE action dte_DATE# filter =# order =# sep = |_|# sepRec =## cmdLine = -export seH -colNames "dbIndex invariant hostIdx namelabel 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|_|inventory|_|04/10/200201: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/200220: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|_|inventory|_|11/20/200200: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|_|inventory|_|04/10/200201: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/200220:10|_|U|_|04/15/2002 20:10|_|


100000223|_||_|100000167|_|192.168.127.2_If<23>|_|192.168.127.2_IF:23 (100Mbps)|_|If<23>|_|on|_|inventory|_|12/04/200223: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/200318:47|_|U|_|05/28/2003 18:47|_|100000224|_||_|100000196|_|dev3.quallaby.com_If<1>|_|dev3_IF:1 (10Mbps)|_|If<1>|_|on|_|inventory|_|04/10/200201:16|_|I|_|04/10/2002 01:16|_|100000224|_||_|100000196|_|dev3.quallaby.com_If<1>|_|dev3_IF:1 (10Mbps)|_|If<1>|_|on|_|resmgr|_|04/15/200220: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|_|inventory|_|04/10/200201: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/200220: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|_|inventory|_|11/20/200200: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|_|inventory|_|04/10/200201: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/200220: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|_|inventory|_|12/04/200223: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|_|inventory|_|04/10/200201:16|_|I|_|04/10/2002 01:16|_|

Exporting element state and comment historyresmgr -export eltH -colNames "name state comment date_DATE action"# resmgr -export eltH -colNames "name state comment date_DATEaction"

# type = eltH# col = name state comment date_DATE action# filter =# order =# sep = |_|# sepRec =# rule =# filterRule =## cmdLine = -export eltH -colNames "name state comment date_DATEaction"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 historyresmgr -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 161

# sepRec =# rule =# filterRule =## cmdLine = -export seH -colNames "name state ulabel date_DATEaction"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 deletingContact IBM Support for assistance with importing or deleting history tables.

Working with sequencesThis section contains the commands you can use to manage sequences. When youuse resgmr to work with sequences, you work with the following object types:v DesignIndexv ResourcesIndex

With these object types, you can find and modify the start of indexes for formulasand resources, using the following two resmgr options, only:v -export to debug optionsv -import for -line and debug options

Find and modify the start of indexes for formulasresmgr -export DesignIndex5000resmgr -import DesignIndex -line 500000

Find and modify the start of indexes for resourcesresmgr -export ResourcesIndex

200000000resmgr -import ResourcesIndex -line 1000000

Warnings:v Each time you export, one index number is used or increased.v For resources, the default start index is 200000000. In most cases it is not

necessary to modify it.


Chapter 11. Configuring thresholds

Explains how to use the resmgr command to configure thresholds.

This chapter explains how to use resmgr to configure thresholds. Thresholds areTivoli Netcool Performance Manager object types that belong to the designcategory.

Before using the commands in this chapter, review the information in Chapter 4,“Managing Tivoli Netcool Performance Manager objects,” on page 15. Additionalresmgr commands for managing thresholds can be found in “Working withthresholds” on page 171 of Chapter 7, “Managing design objects,” on page 105.

ThresholdsThis section defines thresholds and the threshold options. There are two types ofthresholds in Tivoli Netcool Performance Manager:

Default thresholdDeployed against a metric, for any group or resource.

Resource thresholdDeployed against a metric or resource, for any group.

Group thresholdDeployed against a metric or group, for any resource.

Group/resource thresholdDeployed against a specific metric, group or resource combination.

Threshold optionsThe 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) takeseffect. Actions cannot be applied in the past and onlytake effect on the hour. The value is in seconds sinceJanuary 1, 1970 GMT.Prop: Not null

mode Mode of the threshold: 1 = Under, 2 = Over, 3 =BandProp: Not null

thrStatDefine which statistic will be used by the CME tocalculate the threshold information:

0=raw(default), 1=min, 2=max, 3=avg, 4=sum,5=countProp: Not null


Name Definition

thrCalcThe calculation to be used to determine the value ofDBL_BRST_MAX_PCT_OVER andDBL_PRD_MAX_PCT_OVER.

Values for this field include: 0=standard=abs(Value-Level)/abs(Level), 1=normalized=abs(Value-Level)/(critical_level-warning_level), 2=scaled=abs(Value-Level)/scale

where scale = DBL_TRH_CALC_VALUE

thrCalcValue The value used for calculating the percentageover/under threshold.

brstCrtclLevel Level of the critical threshold for burst thresholds.Null implies that the threshold is not defined.

brstWrnngLevel Level of the warning threshold for burst thresholds.Null implies that the threshold is not defined.

brstCrtclTime Time limit for the critical period threshold in seconds.0 indicates that the threshold is violated when themetric exceeds the threshold.

brstWrnngTime Time limit for the warning period threshold inseconds

brstGenEvent Indicates if Tivoli Netcool Performance Manager hasto generate events for the burst threshold. 0=no, 1=yes

prdCrtclLevel Level of the critical threshold for period thresholds.Null implies that the threshold is not defined.

PrdWrnngLevel Level of the warning threshold for period thresholds.Null implies that the threshold is not defined.

PrdCrtclTime Time limit for the critical period threshold in seconds

PrdWrnngTime Time limit for the warning period threshold inseconds

PrdPeriodDefine the period for burst and period thresholds:

1 = Day / 2 =Week / 3 = Month / 4 = All

"All" period means that the CME will use the periodof the aggregation tables

PrdGenEvent Indicates if Tivoli Netcool Performance Manager hasto generate events for the period threshold. 0=no,1=yes


Deploying thresholdsThis section explains the different threshold deployment scenarios.

Threshold deployment against groups and resourcesThresholds can be deployed by Class of Service (CoS), before any other criteria.This means that for the same metric, resources in CoS=Platinum will have onethreshold value X, and resources in CoS=Gold will have one threshold value X.

This figure illustrates that deploying a latency threshold of 100 ms for Platinumand 150 ms for Gold is not possible by group

Chapter 11. Configuring thresholds 165

Two different values are required for the same metric (latency), based on onegrouping structure (CoS), and that it is required to have also a view of thresholdviolation following another grouping structure (Location).

Figure 1. Grouping Structure and Threshold Configuration


Deploying "Non-differentiated" thresholdsNon-differentiated thresholds is the preferred deployment method to followbecause it does not involve resources (only metrics;) therefore, it is less CPU andmemory intensive for the Tivoli Netcool Performance Manager Data Channel andis easier to provision.

If this method cannot be applied, you can apply the alternative method describedin section “Deploying differentiated thresholds” on page 169. This method is moreCPU and RAM intensive for Data Channel and requires usage of the CLI becauseof the number of thresholds to position.

You can have a uniform or non-differentiated threshold. For example, latency isdifferentiated by CoS (see “Threshold deployment against groups and resources”on page 165) but Inbound Loss threshold is not: 1% for every resource in thesystem.


IBM recommends deploying thresholds at the metric level only, with no link to anyresource. This means attaching thresholds to database metric identifier (mid)without any attachment to resource identifier (rid) or group identifier (gid).

Note: You can also use the Tivoli Netcool Performance Manager DataMartResource Editor to deploy non-differentiated thresholds. See Using Resource Editorin the IBM Tivoli Netcool Performance Manager: DataMart Configuration and OperationGuide for details.

Figure 2. Non-Differentiated Threshold Deployment


Enter the following command:resmgr -import thrdv -colNames "idxMetric(2201) mode(1) thrStat(0)thrCalc(0) thrCalcValue(0) brstCrtclLevel(1) brstWrnngLevel(0.5)brstCrtclTime(900) brstWrnngTime(1800) brstGenEvent(0)prdCrtclLevel(1) prdWrnngLevel(0.5) prdCrtclTime(7200)prdWrnngTime(3600) prdPeriod(1) prdGenEvent(0)"

Each time a new resource is provisioned by Resource Manager or an SNMP orBulk inventory, there is nothing to process because, as soon as the formula (forexample, Inbound Loss, percent) is collected/imported against that subelement,that threshold is attached to the formula. This configuration can be considered as adefault configuration for the "Inbound Loss" threshold.

In the Figure 2 on page 168 figure, R1 is moving from Boston to New York. ItsInbound Loss threshold is not supposed to change.

You can change the value of the threshold for only one resource. For example, R3becomes an exception to the rule/default value (to reflect a specific customercommitment) and Inbound Loss threshold is changed from 1 to percent.

In this case, IBM recommends to use the Resource Editor module (or ResourceManager) for creating a new threshold attached to the metric and the resource.

Threshold attached to metric identifier: "Inbound Loss" Thr = 1 percent (noresource attachment used) and threshold attached to (mid, rid): "Inbound Loss" Thr= 1 percent for R3, (no resource attachment used). The (mid, rid) setting overwritesthe default metric identifier setting.

Deploying differentiated thresholdsIf you cannot apply the non-differentiated threshold deployment, then you canapply the differentiated threshold deployment. This method is more CPU andRAM intensive for Tivoli Netcool Performance Manager Data Channel and requiresusage of the CLI because of the number of thresholds to position.


IBM recommends deploying threshold at the resource level vs. at the group level.This mean attaching thresholds to couples (mid and rid) without any attachment togid.

The Resource Editor module is not usable for deployment, but more for testingand prototyping, before deployment. This is due to the number of lines that are

Figure 3. Differentiated Threshold Deployment


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 thrdv -colNames "idxResource idxMetric(2201) mode(1)thrStat(0) thrCalc(0) thrCalcValue(0) brstCrtclLevel(1)brstWrnngLevel(0.5) brstCrtclTime(900) brstWrnngTime(1800)brstGenEvent(0) prdCrtclLevel(1) prdWrnngLevel(0.5)prdCrtclTime(7200) prdWrnngTime(3600) prdPeriod(1) prdGenEvent(0)"-file "./temp"

In the case of feeding resources in Tivoli Netcool Performance Manager withResource Manager (from a provisioning system): every time a new resource isprovisioned by Resource Manager, this command line should be launched, so thatthreshold is configured when the resource is provisioned.

Every time a threshold is attached or updated at a resource level, IBM recommendsto duplicate it as a property, storing the same value for the property. Thisovercomes any Tivoli Netcool Performance Manager DataView issues such as itbeing impossible to display a threshold value in RST/RTT/TOP N (as aproperty=column in the table) and it being impossible follow the history of thethreshold value within the Property History tables. It could also be impossible todisplay a threshold value as simple text (in PVRcLabels). Populating a shadowproperty replicating this threshold and its changes helps solve these issues.

Working with thresholdsThis section explains how to work with thresholds. It contains information aboutexporting, importing, and deleting thresholds.

Exporting thresholdsThe following are examples of exporting thresholds.

Example 1

Output appears. For example:# type = thrdv# 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 andthrsh_desc .idx_group columns have a value of 0.

Output appears. For example:


# type = thrdv# col = fgp.nName idxGroup idxResource mode thrStat# filter =# order =# sep = |_|# sepRec =~FORMULA|_|0|_|0|_|1|_|0|_|

Example 3Export of the segp.npath and se.name fields. The thrsh_desc.idx_resource andthrsh_desc .idx_group columns have a value of 0.

Output appears. For example:# type = thrdv# col = fgp.nName segp.npath se.name mode thrStat# filter =# order =# sep = |_|# sepRec =~FORMULA|_||_||_|1|_|0|_|

Deleting thresholdsTo delete a line of the threshold table, you need to provide the value of thecolumns in the table.

Deleting by indices

Output appears. For example:# type = thrdv# 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 indexOutput appears. For example:

Info : === delete : DELETE ON Threshold ( 1140 1000196 ) (exists)

Verifying the deletion



# type = thrdv# 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 thresholdsThe 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 = thrdv# 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 2Import without specifying resource or group:


Verifying the import in index formExport of the resource and group in index form.

Output appears. For example:# type = thrdv# col = idxMetric idxGroup idxResource mode thrStat# filter =# order =# sep = |_|# sepRec =1000401|_|0|_|0|_|1|_|0|_|


Verifying the import in name formExport of the resource and group in name form.

Output appears. For example:# type = thrdv# col = fgp.nName segp.npath se.name mode thrStat# filter =# order =# sep = |_|# sepRec =~FORMULA |_||_||_|1|_|0|_|

Import by specifying an empty resource and group value


Verifying the importExport of the resource and group in index form.

Output appears. For example:# type = thrdv# col = idxMetric idxGroup idxResource mode thrStat# filter =# order =# sep = |_|# sepRec =1000402|_|0|_|0|_|1|_|0|_|

Verifying the importExport of the resource and group in name form.

Output appears. For example:# type = thrdv# col = fgp.nName segp.npath se.name mode thrStat# filter =# order =# sep = |_|# sepRec =~FORMULA1|_||_||_|1|_|0|_|


Setting thresholdsThis section explains how to set and verify thresholds against groups andresources.

Identifying formula indexesAbout this task

You need to identify the index of the formula to be used as follows:

Procedure1. 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 thethreshold. Thresholds need to be applied to generic formulas because this is theproper 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 have been applied at or above 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 thrdv -colNames "idxMetric idxGroup mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTimeprdWrnngTime prdPeriod prdGenEvent" -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 thresholdTo verify the threshold you need to export the threshold as follows:resmgr -export thrdv -colNames "idxMetric idxGroup mode thrStat thrCalc thrCalcValuebrstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevelprdWrnngLevel prdCrtclTime prdWrnngTime prdPeriod prdGenEvent" -filter "idxMetric(2210)"

Output appears telling you that the threshold is in the database properly. Forexample:2210|_|1001033|_|2|_|0|_|0|_|1000000|_|2000000|_|1000000|_|0|_|0|_|0|_|2000|_|1000|_|900|_|900|_|1|_|0|_|


Setting a threshold against a group (name)Enter the following command:resmgr -import thrdv -colNames "idxMetric segp.npath mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTimeprdWrnngTime prdPeriod prdGenEvent" -line "2210|_|~NOCReporting~Network Management~Unknown_Area~AllTechs|_|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)


Verifying the thresholdTo verify the threshold you need to export the threshold:resmgr -export thrdv -colNames "idxMetric segp.npath mode thrStat thrCalc thrCalcValuebrstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevelprdWrnngLevel prdCrtclTime prdWrnngTime prdPeriod prdGenEvent" -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 thrdv -colNames "idxMetric idxResource mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTimeprdWrnngTime prdPeriod prdGenEvent" -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 databaseInfo : === insert : INSERT ON Threshold ( 2210 0 ) (does not exist)



Verifying the Thresholdv

To verify the threshold you need to export the threshold:resmgr -export thrdv -colNames "idxMetric idxResource mode thrStat thrCalcthrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTimebrstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime prdPeriodprdGenEvent" -filter "idxMetric(2210)"

v

Output appears. For example:2210|_|1000660|_|2|_|0|_|0|_|1000000|_|2000000|_|1000000|_|0|_|0|_|0|_|2000|_|1000|_|900|_|900|_|1|_|0|_|


Setting a threshold against a resource (name)Enter the following command:resmgr -import thrdv -colNames "idxMetric se.name mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTimeprdWrnngTime prdPeriod prdGenEvent" -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)



Verifying the thresholdEnter the following command:resmgr -export thrdv -colNames "idxMetric se.name mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTimeprdWrnngTime prdPeriod prdGenEvent" -filter "idxMetric(2210)"Either"su" to the oracle user, or use the $ORACLE_HOME/sqlplus utility.$ORACLEHOME/sqlplus pv_admin/<password>@PV(or other instancename)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. Forexample:2210|_|zelkona.quallaby.com_Interface<1>|_|2|_|0|_|0|_|1000000|_|2000000|_|1000000|_|0|_|0|_|0|_|2000|_|1000|_|900|_|900|_|1|_|0|_|

Setting a future thresholdThis section explains how to set a future threshold.1. Follow steps 1 to 5 as detailed in the section “Setting thresholds” on page 175.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. Convert this date to Epoch numerical time: 994867200.Epoch time is an exact specification of the date and time at which the Keplerianelement set is valid.

Setting a threshold against a group (dbIndex)Enter the following command to import a threshold for a group:Resmgr -import thrdv -colNames "idxMetric idxGroup dteDate modethrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevelbrstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevelprdWrnngLevel prdCrtclTime prdWrnngTime prdPeriod prdGenEvent"-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 thresholddoes exist in the database.



Verifying the thresholdVerify the threshold by exporting the threshold:Resmgr -export thrdv -colNames "idxMetric dteDate idxGroup modethrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevelbrstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevelprdWrnngLevel prdCrtclTime prdWrnngTime prdPeriod prdGenEvent"-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 verify 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 activated.After the date has been reached, a threshold appears in DataView reports. Timeis in Epoch time.

Tip: Consider installing an Epoch time converter 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 thetime has passed to verify that the threshold has taken effect.

Setting trapsThis section explains how to set burst and period traps.

Setting burst trapsEnter the following command to set a threshold for a metric:resmgr -import thrdv -colNames "idxMetric idxGroup mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTimeprdWrnngTime prdPeriod prdGenEvent" -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 of1001033. The Burst Generate Event flag has also been set.


Verifying the burst trapTo verify the burst trap:1. Log in as root on the server where the Topology Editor is installed.2. Set and export your DISPLAY variable.3. Change your working directory to the directory where the Topology Editor is

installed. For example:# cd /opt/IBM/proviso/topologyEditor

4. Start the Topology Editor using the following command:


# ./topologyEditor

5. In the Topology Editor, select Topology > Open existing topology. The OpenTopology window is displayed.

6. For the topology source, select From database (v. 443) and click Next.7. Verify that all of the fields for the database connection are filled in with the

correct values:v Database hostname -- The name of the database host. The default value is

localhost.v Port -- The port number used for communication with the database. The

default value is 1521.v Database user -- The username used to access the database. The default

value is pv_admin.v Database Password -- The password for the database user account. For

example, pv.v SID -- The SID for the database. The default value is PV.

8. Click Finish.9. In the Logical View, click the DataChannels folder.

10. Click the DataChanneln component, where n is the appropriate DataChannelnumber.

11. Click the Complex Metric Engine n.m component, where n.m is theappropriate DataChannel and sub-channel number.

12. In the Properties tab, search for the following parameter:Trap destination=value

13. Verify that the value is set to the IP address and port for your snmptrapdaemon (for example, Trap destination=192.168.69.30:162).

14. When you are satisfied with your settings, select Topology > Save topology tosave the topology.

15. Select Run > Run Installer and pass it to the newly configured topology.16. After the updated configuration has been stored in the database, you must

restart the CME server 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 totake effect.

About this task

To restart the CME, do the following:

Procedure1. 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:


dccmd -action status -channel 1 -application cme

Note: You can also use the ddcmd command with the bounce argument to stopand start the CME, as follows: dccmd -action bounce -channel 1 -applicationcme. Additionally, you can use a shorter version of the ddcmd command, asfollows:dccmd bounce cme.1

For more information on using the dccmd command, invoke thedccmd command with the -usage option.

Setting period trapsEnter the following command to set a threshold for a metric:Resmgr -import thrdv -colNames "idxMetric idxGroup mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTimeprdWrnngTime prdPeriod prdGenEvent" -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. ThePeriod Generate Event flag has also been set.


Verifying the period trapFollow the steps in the sections entitled “Restarting the Complex Metric Engine(CME)” on page 179.

Threshold troubleshooting scenariosThis section describes different threshold troubleshooting scenarios.

Export scenario 1

Export a threshold configured against mid (metric identifier) andgid (group identifier) and display metrics and group IDs (notname) - NO HISTORY (last values)resmgr -export thrdv -colNames "idxMetric idxGroup mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent"

ype = thrdvcol = idxMetric idxGroup mode thrStat thrCalc thrCalcValue brstCrtclLevelbrstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent# 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|_||_||_||_||_|


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) andgid (group identifier) and display metric and group name (notIDs) - NO HISTORY (last values)resmgr -export thrdv -colNames "fgp.nName segp.npath mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent"

# type = thrdv# col = fgp.nName segp.npath mode thrStat thrCalc thrCalcValue brstCrtclLevelbrstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent# filter =# order =# sep = |_|# sepRec =~AP~PROVISO~Targets~SNMP Availability (percent) (avg last hour)|_|~NOC Reporting|_|1|_|3|_|0|_||_|75|_||_||_||_||_|~AP~PROVISO~Targets~SNMP Response Time (ms) (avg 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~Universal~Outbound Queue Drops (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Inbound Queue Drops (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Resets|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Restarts|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Buffer Utilization (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~CPU Utilization (percent) (avg last 5 minutes)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Outbound Utilization (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Inbound Utilization (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Outbound Loss (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Inbound Loss (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~IP~IP Fragmentation (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|2|_||_||_||_||_|


Export scenario 3

Export a threshold configured against mid (metric identifier) andgid (group identifier) and display metric and group name (notIDs) - Filter on formula - NO HISTORY (last values)resmgr -export thrdv -colNames "fgp.nName segp.npath mode thrStatthrCalc thrCalcValue" -filter "fgp.nName(*Availability*)"

# type = thrdv# col = fgp.nName segp.npath mode thrStat thrCalc thrCalcValue# filter = fgp.nName(*Availability*)# order =# sep = |_|# sepRec =~AP~PROVISO~Targets~SNMP Availability (percent) (avg last hour)|_|~NOC Reporting|_|1|_|3|_|0|_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|2|_|3|_|0|_||_|

Export scenario 4In this scenario, you can troubleshoot an issue related to threshold detection. Forexample, thresholds might be correctly detected on the 17th of the month, but theymight not be detected on the 18th.

Export a threshold configured against mid(metric identifier) andgid(group identifier) and display metric and group name (notIds). Filter on formula Availability - WITH HISTORY (thrdvHinstead of thrdv) and ACTIONresmgr -export thrdvH -colNames "fgp.nName segp.npath dte_DATEaction mode thrStat thrCalc thrCalcValue brstCrtclLevelbrstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent" -filter"fgp.nName(*Availability*)"

# type = thrdvH# col = fgp.nName segp.npath dte_DATE action mode thrStat thrCalc thrCalcValuebrstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent# filter = fgp.nName(*Availability*)# order =# sep = |_|# sepRec =~AP~PROVISO~Targets~SNMP Availability (percent) (avg last hour)|_|~NOC Reporting|_|09/19/2001 01:08|_|I|_|1|_|3|_|0|_||_|75|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|65|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|10|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|09/08/2001 00:45|_|I|_|1|_|0|_|0|_|0|_|90|_|95|_|900|_|1800|_|0|_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|65|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|10|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|09/08/2001 00:36|_|I|_|1|_|0|_|0|_|0|_|90|_|95|_|900|_|1800|_|0|_|

The threshold on "Availability (percent)" has been created on 09/08/2001 00:45with correct values and has been overwritten with invaild values at a later date(09/19/2001 01:08). The result is that Tivoli Netcool Performance ManagerDataView will now be generating reports without the threshold violation.


The difference in dates is because of GMT time (09/19/2001 01:08), which isactually on the 18th in the evening. Date and Action (U=update - I=Insert) let youunderstand the history of actions that happened to the thresholds and troubleshootreport problems.

To correct the issue in the future (no re-computation of theprevious days)resmgr -import thrdv -colNames "idxMetric idxGroup mode thrStatthrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTimebrstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTimeprdWrnngTime prdPeriod prdGenEvent" -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 verify the recreation of the thresholds is correctly updatedresmgr -export thrdvH -colNames "fgp.nName segp.npath dte_DATEaction mode thrStat thrCalc thrCalcValue brstCrtclLevelbrstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent" -filter"fgp.nName(*Availability*)"

# type = thrdvH# col = fgp.nName segp.npath dte_DATE action mode thrStat thrCalc thrCalcValuebrstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent# filter = fgp.nName(*Availability*)# order =# sep = |_|# sepRec =~AP~PROVISO~Targets~SNMP Availability (percent) (avg last hour)|_|~NOC Reporting|_|09/19/2001 01:08|_|I|_|1|_|3|_|0|_||_|75|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|09/25/2001 20:44|_|U|_|1|_|0|_|0|_|0|_|90|_|95|_|900|_|1800|_|0|_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|65|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|10|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|09/08/2001 00:45|_|I|_|1|_|0|_|0|_|0|_|90|_|95|_|900|_|1800|_|0|_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|09/25/2001 20:41|_|U|_|1|_|0|_|0|_|0|_|90|_|95|_|900|_|1800|_|0|_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|65|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|10|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Reporting|_|09/08/2001 00:36|_|I|_|1|_|0|_|0|_|0|_|90|_|95|_|900|_|1800|_|0|_|


Chapter 12. Configuring timezones

Explains how to use resmgr to configure timezones,

Timezones are Tivoli Netcool Performance Manager object types that belong to theDesign category.

Before using the commands in this chapter, review the information in Chapter 4,“Managing Tivoli Netcool Performance Manager objects,” on page 15. Additionalresmgr commands for managing thresholds can be found in “Working withtimezones” of Chapter 7, “Managing design objects,” on page 105.

Working with timezonesThis section explains how to use resmgr to create, modify, or delete time zonedefinitions.

Tivoli Netcool Performance Manager displays times in customer-specific time zonesbecause service providers often have 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 relative todifferent time zones.

You can attach a timezone to a group and it is associated with all groups andresources below it. Because resources can exist in multiple groups, you can createdifferent time zone views of the same sets of resources by defining multiple groupswith different time zone settings. This approach minimizes the amount of duplicatetimezone processing that CME performs and the amount of redundant data that isloaded and retained in the database.

Exporting timezonesThis section explains how to export time zones.

Example


# type = tzc# col = tzdbIndex tzname tzoffset tzcomment tzstatus tzdate# filter =# order =# sep = |_|# sepRec =~NOC Reporting~|_|My Calendar|_|GMT|_|


Deleting timezonesThis section explains how to delete time zones.

Exampleresmgr -delete tz -colNames "dbIndex nop nop nop nop date" -file/tmp/temporary


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 deletionresmgr -export tz -colNames "dbIndex name offset comment statusdate" -file /tmp/temporary


# 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,remove all the links between the timezone and the groups. When you remove thelinks, no statistics are produced for the groups.

Importing modifying,and creating timezonesThis section explains how to import, modify, and create time zones.

Exampleresmgr -import tz -colNames "dbIndex name offset comment statusdate" -file /tmp/temporary


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 importresmgr -export tz -colNames "dbIndex name offset comment statusdate" -file /tmp/temporary



# 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 timezonesThis section explains how to create, modify, or delete links between groups ofsubelements, calendars, and timezones.

Exporting links

Example


Deleting linksThis section explains how to delete the links.

ExampleWhen you execute the following command, you delete all the links between agroup and a timezone. Ensure you want to do so, before entering the command.


Chapter 12. Configuring timezones 187

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 deletionIf a calendar or timezone is already defined at an upper branch for a given group,Tivoli Netcool Performance Manager returns an error indicating a calendar ortimezone cannot be created for this group.resmgr -noX -export tz -colNames "cliParent sename setypecliChild_Tz name tzcliChild_Cal calName cliState cliType cliOrigincliUser cliDate" -file /tmp/verifLinks.dat


# 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 linksThis section explains how to import, modify and create the links.

Exampleesmgr -noX -import tz -colNames "cliParent sename setypecliChild_Tz name cliChild_Cal calName cliState cliType cliOrigincliUser cliDate" -file /tmp/linkSeGrp_Calendars_Timezones.dat



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 associatedwith a link does not exist in the database, the import of this link fails.

Verifying the importresmgr -noX -export tz -colNames "cliParent sename setypecliChild_Tz name cliChild_Cal calName cliState cliType cliOrigintzcliUser cliDate" -file /tmp/verifLinks.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 189

Appendix A. Supported resmgr options

The following table lists in alphabetical order. all of the options you can use withthe resmgr command. It includes a brief description of each option, with whichobject type it is used, and whether you can use it with the import and exportcommands.

Option DefinitionUse with ObjectType Import Export

agp group ofreporters

application Y Y

app reporter application Y Y

appH reporter history history table Y Y

appS reporterstylesheet

application Y Y

cal Calendar calendar Y Y

calH Calendar history history table Y Y

chnl channelelement

others

N

Y

Y

Y

client registrationinformationabout TivoliNetcoolPerformanceManager clients

others Y Y

dbi export TivoliNetcoolPerformanceManager GUIinformation intoCSV format

others Y Y

DesignIndex sequence ofindexes used forTivoli NetcoolPerformanceManager Designobjects such asformulas,reporters,propterties andso on.

sequences Y Y

egp element group group Y Y

egpH element grouphistory

history table Y Y

elt element element Y Y

eltH element history history table Y Y

encl nomclature element Y Y

eprp element property element Y Y



err list of Oracleerrors tracked byTivoli NetcoolPerformanceManager

others Y Y

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 betweengroup andreporter

application Y N

linkGroupAPPS link betweengroup andreporters; groupand style sheets

application Y N

linkGroupE link betweengroup ofelements andelement

group Y N

linkGroupF link between thegroup and theformula

formula Y N

linkGroupN link between thegroup and thenomenclature

nomenclature Y N

linkGroupRU link betweengroup and thereport (Web)user

web user Y N

linkGroupSE link betweengroup ofsubelements andsubelement

group Y N

linkGroupSE_APP link betweengroup ofsubelements andreport

group Y N

linkGroupSE_RU link betweengroup ofsubelements andreport user

group Y N

linkGroupSE_TCZ link betweengroup ofsubelements andtimezone andCalendar

group Y Y

mib MIB formula Y Y

ncl nomenclature nomenclature Y Y



ngp nomenclaturegroup

nomenclature Y Y

ogp group ofinventoryprofiles

inventory profile Y Y

ogpt option of theinventoryprofile. Use withogp value,

inventory profile Y Y

orausr list of Oracleusers

others Y Y

pctile percentile request Y Y

pkg all packagetables

others Y Y

propertyE property ofelement

property Y Y

propertyRU property ofreport user

property Y Y

propertySE property ofsubelement

property Y Y

reg informationaboutcomponent thatare running(similar topvmstart)

others Y Y

regDesc list of allregistries

registry N Y

regInst instances of allregistries

registry N Y

regisDB Tivoli NetcoolPerformanceManagerdatabase registry

registry Y Y

regisDC Tivoli NetcoolPerformanceManagerDataChannelregistry

registry Y Y

regisDCConfig Tivoli NetcoolPerformanceManagerDataChannelregistryconfiguration

registry Y Y

regisDM Tivoli NetcoolPerformanceManagerDataMartregistry

registry Y Y

Appendix A. Supported resmgr options 193


regisMG Tivoli NetcoolPerformanceManagerDataChannelManager registry

registry Y Y

ResourcesIndex sequence ofindexes used forresources(elements,subelements,and groups)

sequences Y Y

rugp report (Web)user group

web user Y Y

ruprp report (Web)user property

web user Y Y

rusr report (Web) use web user Y Y

scf SNMPconfiguration

element Y Y

sched Scheduler scheduler Y Y

se subelement subelement Y Y

segp subelementgroup

group Y Y

segpH subelementgroup history

history table Y Y

segpreq request onsubelementgroup

request Y Y

segpreqH subelementgroup requesthistory

history table Y Y

seH subelementhistory

history table Y Y

seproperty subelementpropertydescription

subelement Y N

seprp subelementproperty

subelement Y Y

thrdv thresholddefinition

threshold Y Y

thrdvH thresholddefinitionhistory

history table Y Y

tz timezone timezone Y Y

usr Tivoli NetcoolPerformanceManagerDataMart user

DM user Y Y

vendor vendor nomenclature Y Y


Appendix B. Working with SAA probes

The following commands allow you to work with SAA probes. For a description ofsupported arguments to these commands, see “Argument descriptions for SAAprobe operations” on page 196.

For a list of SAA Probe properties, see “Properties used by the Tivoli NetcoolPerformance Manager-enabled SAA probes” on page 113.

Exporting or importing an SAA probev Configuration table

resmgr [-export|-import] probe -colNames "dbIndex invariant se.nameuser origin date pprop.name pprop.value"

v History tableresmgr [-export|-import] probeH -colNames "dbIndex invariantse.name pprop.name pprop.value"

Exporting or importing an SAA probe with typesv Configuration table

resmgr [-export|-import] probe -colNames "dbIndex invariant se.nameuser origin date probeType descriptionType invariantDefTypeclassType dateType originType userType"

v History tableresmgr [-export|-import] probeH -colNames "dbIndex invariant dateorigin user probeType descriptionType invariantDefType classTypedateType originType userType"

Exporting or importing SAA probe attributesv Configuration table

resmgr [-export|-import] pprop -colNames "dbIndex namesnmpDisplayFlag snmpCreateFlag snmpPersistFlag snmpControlFlag mibdefaultValue allowedValues order mandatory date origin usersnmpType probeType descriptionType invariantDefType classTypedateType originType userType"

v History tableresmgr [-export|-import] ppropH -colNames "dbIndex namesnmpDisplayFlag snmpCreateFlag snmpPersistFlag snmpControlFlag mibdefaultValue allowedValues order mandatory date origin usersnmpType probeType descriptionType invariantDefType classTypedateType originType userType"


Deleting SAA probesThe safest means to delete SAA probes is by database index. For probe typedefinitions, the database index field name is dbIndexType.v Importing a probe

resmgr -import probe -colNames "probeTypeclassType" -line "probeA|_|classA|_|" Info : === insert : INSERT ONprobe probeType ( probeA ) (does not exist)

v Exporting a proberesmgr -noHead -export probe -colNames"dbIndexType probeType classType" -filter "probeType(probeA)"100006468|_|probeA|_|classA|_|

v Deleting a probe by type and classresmgr -delete probetype -colNames "probeType classType" -line "probeA|_|classA|_|"Info : === delete : DELETE ON probe probeType ( probeA ) (exists)

v Deleting a probe by database indexresmgr -delete probetype -colNames "dbIndexType" -line "100006469|_|"Info : === delete : DELETE ON probe probeType ( probeA ) (exists)

v Deleting an instance of a probe deployed against a subelementresmgr -delete probe -colNames "dbIndex"-line "1234567890"

v Deleting a Proberesmgr -delete probe -colNames "name"

v Deleting a Typeresmgr -delete probe -colNames "type"

v Deleting an Attributeresmgr -delete pprop -colNames "name"

v Deleting an Attribute Valueresmgr -delete ppropvalue -colNames "invariant se.name pprop.name"

Argument descriptions for SAA probe operations

Argument Description

allowedValues Enables data checking in the DataViewportal.

classType The class of the SAA probe type.

date The timestamp of the SAA probe.

dateType The timestamp of the SAA probe,

dbIndex The database index.

defaultValue Specifies a default value to use when thereis no value.

descriptionType Description of the type of SAA probe.

invariant A string that uniquely identifies the SAAprobe.

invariantDefType The definition of the probe type invariant.

invariantType The invariant definition for the SAA probetype.


Argument Description

mandatory Indicates if the value for the attribute isrequired. Can be either 1 (TRUE) or 0(FALSE).

mib The MIB in which the attribute is defined.

name The name of the attribute.

order The order of the attribute within the type.

origin The name of the program performing thechange.

originType The program performing the change.

pprop.name The SAA probe attribute name.

pprop.value The SAA probe attribute value.

probeType The name of the type of SAA probe (jitter orecho).

se.name The ID of the sub-element router.

snmpControlGFlag Indicates if the attribute is an SNMP OIDused for control. Can be either 1 (TRUE) or0 (FALSE).

snmpCreateFlag Indicates if the attribute is an SNMP OIDused for creating. Can be either 1 (TRUE) or0 (FALSE).

snmpDisplayFlag Indicates if the attribute is an SNMP OIDused for display. Can be either 1 (TRUE) or0 (FALSE).

snmpPersistFlag Indicates if the attribute is an SNMP OIDused for persistance. Can be either 1 (TRUE)or 0 (FALSE).

snmpTypeSpecifies the type of SNMP data. Can be oneof the following:

v CNT

v C64

v GGE

v INT

v IP

v MAC

v OCT

v OID

v STR

v TIM

user The name of the user performing thechange.

userType The user performing the change.

Appendix B. Working with SAA probes 197

Listing subelement groups without resourcesresmgr -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 value2|_||_||_|100001001|_|Denver|_||_||_|100010002|_|172.17.100.254|_||_||_|100001078|_|Dallas|_||_||_|100000990|_|Houston|_||_||_|200000153|_|test value2|_||_||_|100000993|_|New York|_||_||_|200000117|_|test value5|_||_||_|200000065|_|test value2|_||_||_|100001052|_|Dallas|_||_||_|200000731|_|"LEs Ulis"|_||_||_|100001059|_|San Francisco|_||_||_|200000140|_|test value2|_||_||_|100002072|_|Gold|_||_||_|100001833|_|Remote Branch|_||_||_|100001779|_|Undefined private network ID|_||_||_|200000187|_|test value2|_||_||_|

Finding and fixing nomenclature

Listing devices not assigned to a nomenclature groupresmgr -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) = ’inventory’ " -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 InternetworkOperating 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-Silver-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|_|


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 Tivoli Netcool Performance Managerobject

resmgr -import ngp -colNames "npath ncl.name ncl.type(SysObjectID)"-line "~NodesType~Router~Cisco|_|Cisco C7100-IS|_|"


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 groupYou add a subelement group by using the Tivoli Netcool Performance ManagerDataMart GUI.

Finding the subelement group index# ~DBER~val3 ==> ~DBER~val2~val3

resmgr -export segp -colNames "npath dbIndex segparent.dbIndex"-filter "npath(~DBER~val3)" -file $DIR/

# ==> "~DBER~val3|_|200003365|_|20000091"

resmgr -export segp -colNames "npath dbIndex" -filter"npath(~DBER~val2)" -file $DIR/

==> "~DBER~val2|_|200003366|_|

Cutting the subelement groupresmgr -delete linkGroupSEGP -colNames "nop lgChild lgParent" -line"~DBER~val3|_|200003365|_|20000091"

Pasting the subelement groupresmgr -import linkGroupSEGP -colNames "nop lgChild lgParent" -line"~DBER~val3|_|200003365|_|200003366"


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.dbIndexdbIndex 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 have morethan one parent. If you find any groups using this command, you need to correctthe problem.resmgr -export segp -colNames "segparent.dbIndex_COUNT dbIndexname" -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|_|%(privateNetworkID)|_|1|_|4193|_|%(privateNetworkID)|_|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|_|Devices|_|1|_|4308|_|Cisco 11.x|_|1|_|4309|_|Router|_|1|_|4310|_|Interfaces|_|1|_|4311|_|Location: %(location)|_|1|_|4312|_|Devices|_|1|_|4313|_|Location: %(location)|_|1|_|4314|_|Interfaces|_|1|_|4315|_|Cisco 11.x|_|1|_|4316|_|%(Element.NAME)|_|


Finding number of child groups for a subelement groupresmgr -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|_|Devices|_|8|_|4309|_|Router|_|11|_|4310|_|Interfaces|_|1|_|4311|_|Location: %(location)|_|10|_|4312|_|Devices|_|2|_|4314|_|Interfaces|_|2|_|4315|_|Cisco 11.x|_|3|_|4317|_|All Technologies|_|8|_|4318|_|Devices|_|3|_|4322|_|MIB-II|_|6|_|4323|_|High Speed Interfaces (>=100Mbps)|_|13|_|4325|_|Low Speed Interfaces (<100Mbps)|_|8|_|4327|_|Devices|_|6|_|4329|_|High Speed Interfaces (>=100Mbps)|_|13|_|4331|_|Low Speed Interfaces (<100Mbps)|_|3|_|4750|_|Per Operation (raw)|_|

Checking subelement group request history tablesresmgr -export segpreqH -colNames "fgp.nName segp.npath perioddbIndex 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 dbIndexdte action dte_DATE"~AP~Specific~SNMP~Router~Cisco 11.x~Device~Buffer Utilization (percent)Cisco 11.x Router Device|_|~Sub-Element Collect~Router~Devices~Cisco 11.x|_|900|_|100001354|_|1065103662|_|U|_|10/02/2003 18:07|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~Buffer Utilization (percent)Cisco 11.x Router Device|_|~Sub-Element Collect~Router~Devices~Cisco 11.x|_|900|_|100001354|_|1018459127|_|I|_|04/10/2002 21:18|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~CPU Utilization (percent)(avg last 5 minutes) Cisco 11.x Router Device|_|~Sub-Element Collect~Router~Devices~Cisco 11.x|_|900|_|100001353|_|1065103662|_|U|_|10/02/2003 18:07|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~CPU Utilization (percent)(avg last 5 minutes) Cisco 11.x Router Device|_|~Sub-Element Collect~Router~Devices~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~


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-1213Interface|_|~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-1213Interface|_|~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-1213Interface|_|~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-1213Interface|_|~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 subelementbelongs

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|_|


Listing elements with empty SysNameresmgr -export elt -colNames "name encl.name" -filter "encl.name(isnull)" -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 subelementresmgr -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>|_|


Filtering without case filterresmgr -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 familyresmgr -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_Device|_|776|_|1213_IF|_|244|_|2233_IF|_|3|_|Cisco_11x_Router_Device|_|2|_|Cisco_FR_DLC_SNMP-CIR|_|1|_|Cisco_IPSec|_|6|_|Cisco_MPLS_LSP|_|3|_|Cisco_Router_Device_SAA|_|6|_|Cisco_Router_Device_SAA_Resp|_|19|_|MLARS|_|725|_|NetFlow|_|65|_|RTTMon_Common_Probe|_|13|_|RTTMon_HTTP_Probe|_|45|_|RTTMon_Jitter_Probe|_|

Grouping all the subelementsThe following resmgr command groups all the sub-elements which are attached tothe an element which IP address is between 192.168.64.40 and 192.168.64.60 in thesubelement group named "net40-60" within the NOC reporting groupresmgr -noHead -export se -rule "~NOC Reporting~net40-60,%(name),"-filterRule "pub.formatIP(%(eprp.ipAddress:value)) >’192.168.064.020’ and pub.formatIP(%(eprp.ipAddress:value)) <’192.168.064.025’" | resmgr -import segp -sep ’,’ -colNames "npathse.name"

Displaying the classification of the xevice name dhcp200resmgr -export elt -sep ’’ -noHead -colNames "encl.oid" -filter"name(dhcp200)" | xargs -I {} resmgr -export ngp -colNames "npathncl.name ncl.oid" -filter "ncl.oid({})" -noHead -file$DIR/Usage_device.dat


Inserting in the past

Note: Check with IBM Support before using this command. Inserting in the pasthas significant impact on the Tivoli Netcool Performance Manager system.resmgr -import seproperty -colNames "name seprp.Contact:valueseprp.Contact:datev(1057015945)" -histoDate 1 -mode "IFirst,forced"-file ....


Appendix C. CLI return codes

Provides information about the return codes for Tivoli Netcool PerformanceManager DataMart command line interfaces (CLI)

The following information about return codes for Tivoli Netcool PerformanceManager command line interfaces (CLI):v Binary/Version is the name of the CLI and the release number for DataMartv Language is the language that was used to build the CLI.v Usage tells you if the CLI is also available in GUI mode.v Success Return Code provides the code number for a successful CLI execution.v Failure Return Code provide the code number for a failed CLI execution.v Other Return Codes provides information on other return codes other than "0"

(if applicable).v Log File Name provides the name of the logging file.

A return code of "0" indicates the command was successful. A return code otherthan 0, indicates the command failed with errors.

CLIs are written in tclTk, C, C++, and Shell. You need to use the "-noX" option forCLIs written in tclTk.

If errors occur, a code number other than "0" is returned. Details about the errorare logged to standard output.

snmpconfReturn code details for the snmpconf command-line interface are as follows:

Binary Language Usage

SuccessReturnCode

FailureReturnCode

OtherReturnCodes

Log FileName

snmpconf tclTk CLI andGUI

0 1 stderr/stdout

Standard output error messagesThe following example error messages appear when launching snmpconf withoutusing the -verbose option (resulting in more output lines, including error andnon-errors).

The error messages are written in the standard output using the following format:ERROR in SNMPCONF : <short error message> : <detailederror message>

ExamplesERROR in SNMPCONF : UPDATE failed : No changed valueERROR in SNMPCONF : ADD failed : Element myHost already exists

Short and detailed error messages are listed in the following table.


Short Error Message Detailed Error Message Comments

ADD failed Element %s already exists ! %s: <name of the element>

Element name should notcontain space character !

Element name should notcontain "~" !

Element name should notcontain "|" !

Element name should notcontain "," !

Element must be specified !

IP address must be specified! (example: 123.123.123.123,123.123.123.* or123.123.123.1-10,33,44,50-77)

Bad value of option"-ipaddress" ! (example:123.123.123.123, 123.123.123.*or 123.123.123.1-10,33,44,50-77)

Bad value of option"-timeout" value must benumeric !

Bad value of option "-tries"value must be numeric !

Bad value of option "-port"value must be numeric !

Element "default" is reserved! You cannot add or delete it.

IP address *.*.*.* is reservedfor "default" element !

Database access error (%s). %s: <detailed error>

Cannot insert element intodatabase !

This message can befollowed by the SQL querythat has failed

snmpconf is in READ MODE!

Cannot perform operationwithout write permissions


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 value 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 notcontain space character !





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 value of option"-ipaddress" ! (for example,123.123.123.123, 123.123.123.*or 123.123.123.1-10,33,44,50-77)




Element %s doesn't exist ! %s : <name of the element>

Cannot get element fromdatabase !

This message can befollowed by the SQL querythat has failed.

Cannot read from database This message can befollowed by the SQL querythat has failed.

All fields of "default" mustbe specified !

Appendix C. CLI return codes 209

No option passed ! (possibleoptions are -ipaddress-rcommunity

-wcommunity -timeout -tries-port)

Missing some CLI options

No changed value !Can not update because ofunchanged parameters

This « error » can be ignored.It is a warning

Element "default" is reserved! You can't change its address(*.*.*.*).

IP address *.*.*.* is reservedfor "default" element !

Cannot update element indatabase !

This message can befollowed by the sql querythat has failed

Cannot save in database


Can not perform operationwithout write permissions

DELETE failed Element name should notcontain space character !





Bad value of option"-ipaddress" ! (example:123.123.123.123, 123.123.123.*or 123.123.123.1-10,33,44,50-77)





Element %s doesn't exist ! %s: <name of the element>

Cannot get element fromdatabase !

This message can befollowed by the sql querythat has failed

Cannot read from database This message can befollowed by the sql querythat has failed

Element "default" is reserved! You can't add or delete it.

Cannot delete element indatabase !


Can not perform operationwithout write permissions

Database Error Cannot get elementsinformation from database !

Unknown operation %s %s : the operation name thathave been passed to CLI

Unable to inform collectorabout modifications at %s !

%s: <Ipadress : port #>

Cannot continue withoutpermissions

Check the user permissionsfor the current CLI

reqedit

Return codeReturn code details for the reqedit command line interface is are as follows:

Binary/Version Language Usage

SuccessReturnCode

FailureReturnCode

OtherReturnCodes

Log FileName

reqedit v2.0and 2.2

tclTk CLI andGUI

0 1 stderr/stdout

Standard output error messagesThe following example error messages appear when launching the reqedit withoutusing the -verbose option (resulting in more information on the standard outputerrors and process information).

The error messages are written in the standard output using the following format:ERROR in REQEDIT : <short error message> <detailed errormessage>

Examples:

ERROR in REQEDIT : Bad period value. Period value range is from 1 minute to 24hours.

ERROR in REQEDIT : Missing parameters on request "formula target" aremandatory.


Short and detailed error messages are listed in the following table.


Unable to launch RequestEditor in write mode.

Unknown operation %s %s : the operation name thathave been passed to CLI.

Cannot read Databaserequests.

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 onrequest.

"%s" are mandatory. %s : CLI missing parameters

Period or Calendar must bespecified.

Bad period value. Periodvalue range is from %sminute to 24 hours.

%s : <minimum periodvalue>

Bad storage value.

Bad resource type.

Bad status value.

Cannot read from database This message can befollowed by the sql querythat has failed.

Cannot save in database This message can befollowed by the sql querythat 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 groupname:

%s %s : <element group name>

Unknown sub-element name: %s %s : <sub-element name>

Unknown sub-element groupname:

%s %s :<sub-element groupname>

Unknown calendar: %s %s : <calendar name>

Unknown threshold profile: %s %s : <threshold name>

Not a valid formula: %s : <formula name>

Request already exists.

Unable to inform collectorabout modifications at %s !

%s: <Ipadress : port #>

Cannot add request todatabase.


Cannot update request intodatabase.

Cannot remove request fromdatabase.

resmgr

Return codeReturn code details for the resmgr command line interface is are as follows:


SuccessReturnCode

FailureReturnCode

OtherReturnCodes

Log FileName

resmgr v2.0and 2.2

tclTk CLI andGUI

0 1X > 1 :where X =nbErrors +10

(nbErrors isthe numberof sqlrequeststhat havefailed)

stderr +stdout

Comments

Return code 1 = critical error

Return code >1 (X) means there are errors, but it is not critical.

Standard output error messagesThe following error messages appear when launching resmgr without using the-verbose option (resulting in more output lines, including non-errors information).

To check the errors, check log lines, looking for the string `Error'

<Log level> : < Short message> : <Detailed message>

where <Log level> is Error , or Warning , or Info

Example #1resmgr -import fgp -colNames "npath" -file ./t.txt

Info : === insert : INSERT ON Formula Group (~Fake_ProServices~MIBII ) (does not exist)

Info : === insert : UPDATE ON Formula Group (~ProServices~MIBII~Interface ) (exists)

Info : === insert : UPDATE ON Formula Group (~ProServices~Netware ) (exists)

Info : === insert : UPDATE ON Formula Group ( ~ProServices~LotusNotes ) (exists)


Example #2solar:/opt/PVM2.0/importexport> resmgr -noX

Error : === InvalidAction : must be export|import|delete|analyse

In case of critical errors, the return code is 1, you have the log on the standardoutput.

Short and detailed error message are listed in the following table.


Cannot connect to database.

Database access error (%s). %s : <message>.

Cannot disconnect fromdatabase.

Cannot continue withoutpermissions.

Cannot delete in database


Cannot read from database

inventory

Return codeReturn code details for the inventory command line interface is are as follows:

Binary Language Usage

SuccessReturnCode

FailureReturnCode

OtherReturnCodes

Log FileName

inventory tclTk CLI andGUI

0 12

The 2 returncodesignifies thattheinventoryprofile islocked. Thisreturn codeonlydisplays ifthePVM_ENHANCED_ERRORCODE=1 variableis set inyourDataMartenvironment.

stderr/stdout


Standard output error messagesThe following messages appear when launching inventory without using the-verbose 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

- or -

Warning : <short error message>

- or -

<short error message>

Examples

"-tutu" is not a known option

List of available options: -? -D -Parent -U -action -name -noX -reload-reportGrouping

Short and detailed error messages are listed in the following table:


Cannot connect to database.

Database access error (%s). %s : <message>.

Cannot disconnect fromdatabase.

Cannot continue withoutpermissions.

Cannot delete in database


Cannot read from database

Profile '%s' already exist !


File '%s' doesn't exist !

You must run discoverybefore runningsynchronization

%s %s : <message>.

Format Type 3

This type of log is produced while the module is using resmgr APIs. The logformat is the same as what is normally produced by resmgr.

<Log level> : < Short message> : <Detailed message>

where <Log level> is Error , or Warning , or Info

Exampleresmgr -import fgp -colNames "npath" -file ./t.txtInfo : === insert : INSERT ON Formula Group( ~Fake_ProServices~MIBII ) (does not exist)Info : === insert : UPDATE ON Formula Group (~ProServices~MIBII~Interface ) (exists)Info : === insert : UPDATE ON Formula Group (~ProServices~Netware ) (exists)Info : === insert : UPDATE ON Formula Group ( ~ProServices~LotusNotes ) (exists)

impexp

Return codeReturn code details for the impexp command line interface are as follows:


SuccessReturnCode

FailureReturnCode

OtherReturnCodes

Log FileName

impexpv2.0 and2.2

tclTk CLI andGUI

0 1X , where Xis anumber.

X=10 +nbSqlFailures

nbSqlFailuresis thenumber ofsql requeststhat havefailedduringoperation.

$PVMHOME/log/logFile.IMPEXP.

Comments

The return code 1 indicates that impexp encountered a critical error. If only a partof process worked. If not critical error, the return code is greater than 1.


Standard output error messagesOnly critical messages are logged in the standard outputs. In such cases, the returncode 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 D. Sample inventory script

Provides contains a sample Korn Shell wrapper program that calls the inventorycommand.

This appendix The command does the following:v Extracts all existing inventory profiles from the database.v Loops through the profiles, running a complete inventory on each one.v Reloads the collector after every five inventories (this is configurable).v After all the inventories have run, calls the inventory command with the

-reportGrouping option.

The script also allows you to invoke it with command-line options. For moreinformation, see your Tivoli Netcool Performance Manager Professional Servicesrepresentative.

Sample inventory script#!/bin/ksh#set -x#=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=## R U N I N V E N T O R Y##- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - -# FileName : runinventories.ksh# Author : ACOS# Date : 24/07/02# Subject : Run all inventory 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=0let VERBOSE=0

#-------------------------------------------------------------------------------# Command line keywords

#-------------------------------------------------------------------------------


KEY_ACTION="-action"KEY_PROFILE="-profile"KEY_SEP="-sep"KEY_VERBOSE="-v"; # Verbose modeKEY_YES="-Yes"; # Answer Yes to all questionsKEY_HELP="-?";

#-----------------------------------------------------------------------------# function Confirm#-----------------------------------------------------------------------------

function Confirm{

if (( ! ${YES} ))then

read IN?"${1}"if [[ $IN == @(y|Y) ]]then

return 0else

return -1fi

elsereturn 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#-----------------------------------------------------------------------------


function PrintLog{

if (( ${VERBOSE} ))then

echo "`date \"+%m/%d/%Y-%H:%M:%S\"` [${PROGNAME}] ${1}"

fi}

#-------------------------------------------------------------------------------# function PrintUsage#-------------------------------------------------------------------------------

function PrintUsage{cat << USAGEUsage : ${0##*/} [Options]

Where Options are

${KEY_ACTION} : Defines which modules to run[discovery|synchro|grouping|user]

(default all)

${KEY_PROFILE} : Profile name (by default all profiles except"default")

${KEY_SEP} : Set the field separator (default is "${SEP}")

${KEY_VERBOSE} : Verbose mode(disable by default)

${KEY_YES} : Answer Yes to all questions(disable by default)

${KEY_HELP} : Gives this help

Run Profiles, populate properties and perform a report grouping.USAGE}

#-------------------------------------------------------------------------------# Help#-------------------------------------------------------------------------------

if [[ ${1} = "-?" || ${1} = "-help" ]]then

PrintUsageexit 0

fi

#-------------------------------------------------------------------------------# Parsing parameters#-------------------------------------------------------------------------------

while [[ -n ${1} ]]do

case ${1} in

"${KEY_ACTION}")shiftif [[ -n ${1} ]]then

Appendix D. Sample inventory script 221

ACTION="${1}"else

PrintError "Missing mandatory parameter !"PrintUsageexit 3

fi;;

"${KEY_PROFILE}")shiftif [[ -n ${1} ]]then

PROFILE="${1}"else


fi;;

"${KEY_SEP}")shiftif [[ -n ${1} ]]then

SEP="${1}"else


fi;;

"${KEY_VERBOSE}")let VERBOSE=1;;

"${KEY_YES}")let YES=1;;

* )PrintError "Failed to parse arguments, unknown option:

\"${1}\"."PrintUsageexit 3;;

esacshift

done

#-------------------------------------------------------------------------------# run env#-------------------------------------------------------------------------------. $PVMHOME/dataMart.env

#-------------------------------------------------------------------------------# Retreive profiles list#-------------------------------------------------------------------------------

if [ -z "${PROFILE}" ]then

resmgr -export ogp -colNames "npath" | grep -v ’#’ | \nawk -F "|" \’{

n=split($1, TAB, "~")if (n > 1)


{PROFILE=TAB[2]if ( (PROFILE != "") && (PROFILE != "default")

&& (index(PROFILE,"inv_")>0))print PROFILE

}}’ | sort | uniq > ${PROGNAME}.profiles

elseecho ${PROFILE} > ${PROGNAME}.profiles

fi

#-------------------------------------------------------------------------------# Running inventory for each profiles#-------------------------------------------------------------------------------

typeset -i NBPROFILES=$(wc -l < ${PROGNAME}.profiles2>/dev/null)

typeset -i profCnt=1

cat ${PROGNAME}.profiles |&while read -p ido

PrintLog "Launching inventory profile \"${i}\"..."

LOGFILE="${DIRNAME}/${PROGNAME}_${i}.log"

if ( (( profCnt % reloadFreq == 0 )) || (( profCnt ==NBPROFILES )) )

theninventory -noX -name "${i}" -action "${ACTION}" -reload 1

>> "${LOGFILE}" 2>&1else

inventory -noX -name "${i}" -action "${ACTION}" >>"${LOGFILE}" 2>&1

fi

if [ ${?} -ne 0 ]then

PrintError "Inventory failed for profile \"${i}\"."fi

sleep 60profCnt=$((profCnt+1))

done

#-------------------------------------------------------------------------------# Report autogrouping#-------------------------------------------------------------------------------PrintLog "running reportGrouping ...."inventory -noX -reportGrouping >> "${LOGFILE}" 2>&1#-------------------------------------------------------------------------------# Cleaning temporary files#-------------------------------------------------------------------------------

#rm -rf "${PROGNAME}.profiles" >/dev/null 2>&1

exit 0

#=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=# E N D O F F I L E#=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Appendix D. Sample inventory script 223

Appendix E. Using prerequisite check scripts

Provides information concerning how to use prerequisite check scripts that areincluded with Tivoli Netcool Performance Manager,

Tivoli Netcool Performance Manager includes the check_os and check_dbprerequisite checking scripts that are used to verify various host system and Oracledatabase requirements to ensure the successful operation of Tivoli NetcoolPerformance Manager. The sections below explain how to use these scripts toverify your Tivoli Netcool Performance Manager environment.

Using the check_os scriptThe check_os script is used to verify platform version and patch requirements forSolaris, AIX, and Redhat Linux systems that host Tivoli Netcool PerformanceManager components.

Tasks Performed by the check_os script.

Once the script has been executed, check_os refers to values set in thecheck_os.ini file and performs the following tasks:v Verifies that an argument was passed to the script.v Verifies that the operating system is a supported platform for Tivoli Netcool

Performance Manager.v Verifies that the operating system is a supported version for Tivoli Netcool

Performance Manager.v Verifies that the specified Tivoli Netcool Performance Manager component is

valid and supported on the current operating system.v Verifies that the required patches have been applied to the operating system.

Running the check_os scriptTo 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/proviso/deployer/proviso/bin/Check

3. Start the check_os script using the following command:./check_os component_ID

Where component_ID specifies a Tivoli Netcool Performance Managercomponent. The following table lists the supported values:

Value Description

dm Tivoli Netcool Performance ManagerDataMart

dl Tivoli Netcool Performance ManagerDataLoad

dc Tivoli Netcool Performance ManagerDataChannel


Value Description

db Tivoli Netcool Performance ManagerDatabase

dv Tivoli Netcool Performance ManagerDataView

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 Tivoli Netcool Performance Manager: Installation Guide and IBM TivoliNetcool Performance Manager: Configuration Recommendations.

Example outputThe following are examples of output returned by the config_os script:

Solaris# ./check_os db

-->OK. Version SunOS 5.9.-->OK. Proviso 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. Proviso 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 messagesThe check_os script can return the following error messages:

Error Message Description

Proviso Component Can Be: DL, DC, DM,DB, DV

No component_ID was specified in thescript command.

This version of operating system is notsupported!

The version of the current operating systemis not supported by Tivoli NetcoolPerformance Manager. Examine thecheck_os.ini file for supported versions ofoperating systems.



Proviso Component: component_ID isunknown or not supported for this OS!

Either an incorrect Tivoli NetcoolPerformance Manager component wasspecified in the script command, or theTivoli Netcool Performance Managercomponent is not supported on the currentoperating system. Examine the check_os.inifile for supported operating systems.

** ERROR ** Missing required patchpatch_name for this OS!

The current operating system is notsupported by Tivoli Netcool PerformanceManager. Examine the check_os.ini file forsupported operating systems.

This system's OS is not supported! The current operating system is notsupported by Tivoli Netcool PerformanceManager. Examine the check_os.ini file forsupported operating systems.

ERROR! The value of limit_name was notdetected in the /etc/security/limits file.Check that the minimum value is set.

AIX only. A value is missing from the/etc/security/limits file. Examine thecheck_os.ini file for supported/etc/security/limits values.

ERROR! The value of limit_name is:limit_value. This is not equal or less thanwhat is set in the check_os.ini file.

AIX only. A value is incorrect in the/etc/security/limits file. Examine thecheck_os.ini file for supported/etc/security/limits values.

ERROR! Unknown OS Prefix The current operating system is notsupported by Tivoli Netcool PerformanceManager. Examine the check_os.ini file forsupported operating systems.

Using the check_db scriptThe check_db script is used to verify system settings and Oracle version and patchrequirements for Solaris, AIX, and Redhat Linux systems that host Tivoli NetcoolPerformance Manager components.

Tasks performed by the check_db scriptOnce the script has been executed, check_db refers to values set in thecheck_db.ini file and performs the following tasks:v Verifies that arguments were passed to the script.v Verifies that the operating system is a supported platform for Tivoli Netcool

Performance Manager.v Verifies that the operating system is a supported version for Tivoli Netcool

Performance Manager.v Verifies that the required Oracle environment variables are set.v Verifies that the installed Oracle version is a supported version for Tivoli

Netcool Performance Manager.v Verifies the Oracle home patch and checks that no symbolic links are used in the

Oracle home directory tree.v Verifies that the Oracle binary has the correct bit setting for the operating

system.v Runs the tnsping command to ensure that the Oracle server is accessible.

Appendix E. Using prerequisite check scripts 227

v Verifies that no Oracle background processes exists for Tivoli NetcoolPerformance Manager.

v Verifies that no instance-specific configuration files exist for Tivoli NetcoolPerformance Manager.

v Verifies that the Oracle database is running and accessible.

Running the check_db scriptAbout this task

To use the check_db script, do the following:

Procedure1. 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/proviso/deployer/proviso/bin/Check

3. To verify Oracle database prerequisites, start the check_db script using thefollowing command:./check_db install_type install_method ORACLE_SID

Where:

Variable Description

install_type Supported values are server or client.Specifies whether check_db is to verify theprerequisites for an Oracle server or clientinstallation.

install_methodSupported values are new or upgrade.

Specifies whether check_db is to verify theprerequisites for a new or upgrade Oracleinstallation.

ORACLE_SID Specifies the Oracle System Identifier usedfor Tivoli Netcool Performance Manager inyour environment. For example, PV.

4. To verify that the Oracle database is running and accessible, start the check_dbscript using the following command:./check_db verifybase ORACLE_SID

Where:

Variable Description

ORACLE_SID Specifies the Oracle System Identifier usedfor Tivoli Netcool Performance Manager inyour environment. 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 Tivoli Netcool Performance Manager: Installation Guide and IBM TivoliNetcool Performance Manager: Configuration Recommendations.


ExamplesThe following are examples of output returned by the config_db script:

Solaris$ ./check_db server new PV

-->OK. Version SunOS 5.9.-->OK. ORACLE_HOME does not contain symbolic links.-->OK. Oracle version 9.2.0.8.0-->OK. 32 bit /opt/oracle/product/9.2.0/bin/oracle.$ ./check_db verifybase 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 = pmgdev3) (PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = PV.WORLD)(INSTANCE_NAME = PV)))OK (0 msec).-->OK. Instance PV is available.-->OK. The checkextc script succeeded.

AIX$ ./check_db server new PV

-->OK. Version AIX 5300-04.-->OK. ORACLE_HOME does not contain symbolic links.-->OK. Oracle version 9.2.0.8.0-->OK. 64 bit /opt/oracle/product/9.2.0/bin/oracle.

$ ./check_db verifybase 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 available.-->OK. The checkextc script succeeded.

Error messagesThe check_db script can return the following error messages:


This script can be run in two ways:Prerequisite Usage:

check_db <[client - server] [new - upgrade][ORACLE_SID or tnsnames.ora entry]>Verify_Base Usage: check_db <[verifybase][ORACLE_SID or tnsnames.ora entry]

Incorrect arguments were specified in thescript command.

ERROR! This systems OS is not supported! The current operating system is notsupported by Tivoli Netcool PerformanceManager. Examine the check_db.ini file forsupported operating systems.

ERROR! This version of operating system isnot defined in check_db.ini!

The version of the current operating systemis not supported by Tivoli NetcoolPerformance Manager. Examine thecheck_db.ini file for supported versions ofoperating systems.



ORACLE_BASE Not defined. The ORACLE_BASE parameter has not been set.Set this value and run the script again.

ORACLE_HOME Not defined. The ORACLE_HOME parameter has not been set.Set this value and run the script again.

NLS_LANG Not defined. The NLS_LANG parameter has not been set.Set this value and run the script again.

SHLIB_PATH_VAR Not defined. The SHLIB_PATH_VAR parameter has not beenset. Set this value and run the script again.

TNS_ADMIN Not defined. The TNS_ADMIN parameter has not been set.Set this value and run the script again.

PATH Not defined.The PATH parameter has not been set. Set thisvalue and run the script again.

EXTPROC_DLLS Not defined. The EXTPROC_DLLS parameter has not beenset. Set this value and run the script again.

ERROR! Could not determine version ofOracle installed!

The Oracle version could not be found.Verify that a version of Oracle supported byTivoli Netcool Performance Manager hasbeen installed on the system.

ERROR! Checked for Oracle software. The Oracle software could not be found.Verify that a version of Oracle supported byTivoli Netcool Performance Manager hasbeen installed on the system.

ERROR! Ensure Oracle software is installed. The Oracle software could not be found.Verify that Oracle has been installed on thesystem.

WARNING! Client Version does not matchentry in check_db.ini

The Oracle client version is not supportedby Tivoli Netcool Performance Manager.Examine the check_db.ini file for supportedversions of Oracle client.

ERROR! Oracle version: version not listed incheck_db.ini.

The Oracle version is not supported byTivoli Netcool Performance Manager.Examine the check_db.ini file for supportedversions of Oracle.

ERROR! Link is a symbolic link! The specified link is symbolic. No symboliclinks can be used in the Oracle homedirectory tree.

ERROR! The binary: binary_name was notfound. Check if Oracle is installed.

The specified Oracle binary could not befound. Verify that Oracle has been installedon the system.

ERROR! Bit_setting bit binary_name notlisted in check_db.ini.

The specified bit setting does not match thecorrect bit setting for the operating system.Examine the check_db.ini file for supportedbit settings.

WARNING! Did not get OK response fromtnsping.

Oracle is not responding. Check that Oracleis running and available.

WARNING! Cannot contact Oracle listener. The Oracle listener is not responding. Checkthat the Oracle listener is running andavailable.



ERROR! Found an Oracle instance runningwith PID: PID.

An existing Oracle background processexists for Tivoli Netcool PerformanceManager on the system. Determine if youwish to reinstall or upgrade the Oracleserver.

ERROR! An init.ora file exists for givenSID.

An existing instance-specific Oracleconfiguration file exists for Tivoli NetcoolPerformance Manager on the system.Determine if you wish to reinstall orupgrade the Oracle server.

ERROR! The value of parameter was notdetected with the sysdef command andcould not be found in the /etc/ system file.

A value is incorrect in the /etc/system file.Examine the check_db.ini file for supported/etc/system values.

ERROR! The value of parameter is: value,which is less than what is listed as therecommended minimum in the check_db.inifile.

A value is incorrect for parameter. Examinethe check_db.ini file for supported values forparameter.

ERROR! The value of SHMMAX was notdetected with the sysdef command andcoulnd not be found in the /etc/system file.

Check that the minimum value is set. Thevalue for SHMMAX in the /etc/system file ismissing. Examine the check_db.ini file forsupported values for SHMMAX.

ERROR! The value of SHMMAX is: value,which is less than the reccomended value.

The value for SHMMAX in the /etc/system fileis incorrect. Examine the check_db.ini filefor supported values for SHMMAX.

ERROR! Could not find the file set name asCOMMITTED.

The specified file set could not be found.Verfiy that the file set has been installed onthe system.

ERROR! Could not find asyncio as Available. The specified file is not available. Check thatOracle is running and available.

ERROR! Unknown OS Prefix. The current operating system is notsupported by Tivoli Netcool PerformanceManager. Examine the check_db.ini file forsupported operating systems.

ERROR! Could not access the instanceORACLE_SID.

The specified Oracle System Identifier is notaccessible. Check that the instance has beendefined.

ERROR! Check that the Oracle instance isrunning.

The Oracle instance is not running. Checkthat Oracle is running and available.

ERROR! The checkextc script failed. The external procedure call check has failed.Verify the cause of the failure and re-run thescript.

ERROR! Invalid install method.

ERROR! Must be New or Upgrade.

An incorrect install_method was specifiedin the script command. Verify the commandsyntax and re-run the script.

ERROR! Invalid Install Type.

ERROR! Must be client or server.

An incorrect install_type was specified inthe script command. Verify the commandsyntax and re-run the script.


Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law :

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, 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 beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment to


IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Notices 235

Java and all Java-based trademarks and logos are trademarks orregistered trademarks of Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.


��

Printed in USA

command line interface guide · ibmtivoli netcool performance manager 1.3.3 wireline component...

Documents