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

IBM Tivoli Netcool Performance Manager 1.3.2

Wireline Component

Document Revision R2E1

Command Line Interface Guide

Note

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

© Copyright IBM Corporation 1997, 2012.

Contents

About this information . . . vii

Intended audience . . . vii

The Tivoli Netcool Performance Manager product suite . . . vii

Chapter 1. Introduction . . . 1

Special characters and command-line utilities . . . 1

Accessing CLI utilities . . . 1

Chapter 2. Using the inventory

command . . . 3

Chapter 3. Using the dccmd command

11

The dccmd command . . . 11

Example dccmd commands . . . 13

Chapter 4. Managing Tivoli Netcool

Performance Manager objects. . . 15

Understanding Tivoli Netcool Performance Manager objects . . . 16

About Tivoli Netcool Performance Manager objects . . . 16

Understanding Tivoli Netcool Performance Manager object IDs . . . 21

Working with resmgr . . . 22

Displaying resource manager options . . . 22

Using column names . . . 24

Resource column names . . . 24

Design objects . . . 30

Requests . . . 33

Report objects . . . 36

Application column names . . . 38

Administration objects. . . 40

Using functions with column names . . . 41

Chapter 5. Exporting and importing

objects. . . 49

The export syntax . . . 49

Mandatory options . . . 49

Additional options . . . 50

Using mandatory links with elements . . . . 54

Dividing results into multiple lines . . . 54

Including field separators. . . 55

Including record separators . . . 55

Specifying a file name . . . 56

Specifying path locations . . . 56

Removing the header . . . 56

The import syntax . . . 58

Mandatory options . . . 58

Using -colNames . . . 58

Including field separators. . . 59

Including record separators . . . 59

Specifying file names . . . 59

Specifying path locations . . . 59

Specifying input data . . . 59

Forcing the creation date . . . 60

Reloading collectors . . . 60

Analyzing Tivoli Netcool Performance Manager object . . . 60

Using a configuration file. . . 61

Line-by-Line explanation . . . 62

Chapter 6. Managing resources . . . . 73

Working with elements . . . 73

Exporting elements . . . 73

Importing elements . . . 78

Deleting elements . . . 81

Working with subelements . . . 81

Exporting subelements . . . 82

Importing subelements . . . 84

Deleting subelements . . . 87

Working with groups or rules . . . 88

Subelement group links . . . 88

Exporting groups and rules . . . 88

Importing groups and rules . . . 95

Deleting . . . 97

Working with composite subelement rules . . . 98

Working with nomenclature . . . 99

Using mandatory links . . . 102

Using mandatory links with subelements . . . 105

Using mandatory links with subelement groups 107 Using mandatory links with inventory profiles 109 Using mandatory links with nomenclature. . . 110

Chapter 7. Managing design objects

111

Exporting formulas . . . 111

Importing formulas . . . 113

Deleting formulas . . . 114

Working with properties. . . 114

Subelement properties . . . 114

Exporting properties . . . 117

Exporting property default values . . . 118

Trouble Ticket pack properties . . . 119

Properties used by the Tivoli Netcool Performance Manager-enabled SAA probes . . 119

Importing properties . . . 123

Importing subelement properties . . . 123

Deleting subelement property . . . 124

Working with thresholds . . . 124

Exporting thresholds . . . 124

Importing thresholds . . . 125

Working with requests . . . 125

Exporting all requests . . . 125

Exporting subelement group requests . . . . 126

Exporting percentiles . . . 127

Importing requests . . . 127

Deleting requests . . . 128

Working with calendars . . . 128

Exporting calendars . . . 128

Importing calendars . . . 129

Deleting calendars. . . 129

Working with timezones. . . 129

Exporting timezones . . . 129

Working with inventory profiles . . . 130

Duplicating an inventory profile . . . 130

Importing inventory profiles . . . 131

Deleting inventory profiles . . . 131

Chapter 8. Managing administration

objects . . . 133

Working with Tivoli Netcool Performance Manager DataMart users and groups. . . 133

Exporting users and groups . . . 133

Importing users and groups . . . 134

Deleting user and groups . . . 136

Working with registries . . . 136

Exporting registry objects . . . 136

Importing registries . . . 143

Deleting registries . . . 143

Working with miscellaneous Tivoli Netcool Performance Manager objects . . . 143

Working with chnl (information about collector) 144 Working with reg . . . 144

Working with dbi . . . 145

For limited use (checking for problems after installation) . . . 145

Chapter 9. Managing report objects

147

Exporting web user . . . 147

Importing web user . . . 149

Deleting web user . . . 150

Working with reporters . . . 150

Exporting reporters . . . 150

Importing reporters . . . 154

Deleting reporters and reporter stylesheets . . 155

Working with scheduler . . . 156

Exporting scheduler . . . 156

Importing scheduler . . . 159

Deleting scheduler. . . 159

Chapter 10. Managing history table

and sequence objects. . . 161

Working with history tables . . . 161

Exporting history tables . . . 161

Importing and deleting . . . 164

Working with sequences. . . 164

Find and modify the start of indexes for formulas . . . 164

Find and modify the start of indexes for resources . . . 164

Chapter 11. Configuring thresholds

165

Threshold options . . . 165

Deploying thresholds . . . 167

Threshold deployment against groups and resources . . . 167

Deploying "Non-differentiated" thresholds. . . 169

Deploying differentiated thresholds . . . 171

Working with thresholds . . . 173

Exporting thresholds . . . 173

Deleting thresholds . . . 174

Importing thresholds . . . 175

Setting thresholds . . . 177

Identifying formula indexes . . . 177

Setting a threshold against a group (dbIndex) 177 Setting a threshold against a group (name) . . 178

Setting a threshold against a resource (dbIndex) 178 Setting a threshold against a resource (name) 179 Setting a future threshold . . . 179

Setting traps. . . 180

Setting burst traps . . . 180

Setting period traps . . . 182

Threshold troubleshooting scenarios . . . 182

Export scenario 1 . . . 182

Export scenario 2 . . . 183

Export scenario 3 . . . 184

Export scenario 4 . . . 184

Chapter 12. Configuring timezones

187

Exporting timezones . . . 187

Deleting timezones . . . 188

Importing, modifying, and creating timezones 188 Grouping links of subelements, calendars, and timezones . . . 189

Exporting links . . . 189

Deleting links . . . 189

Importing, modifying or creating links . . . . 190

Appendix A. Supported resmgr

options . . . 193

Appendix B. Working with SAA

probes . . . 197

Exporting or importing an SAA probe . . . 197

Exporting or importing an SAA probe with types 197 Exporting or importing SAA probe attributes . . . 197

Deleting SAA probes . . . 198

Argument descriptions for SAA probe operations 198 Listing subelement groups without resources . . . 200

Finding and fixing nomenclature . . . 200

Listing devices not assigned to a nomenclature group . . . 200

Correctly classifying a Tivoli Netcool Performance Manager object . . . 201

Filtering subelements using the underscore (_) 201 Cutting and pasting in subelement group . . . . 201

Finding the subelement group index . . . . 201

Cutting the subelement group . . . 201

Finding subelement groups without a parent 202 Finding subelement groups with more than one

parent . . . 202

Finding number of child groups for a subelement group . . . 203

Checking subelement group request history tables . . . 203

Checking the number of groups to which a subelement belongs . . . 204

Listing elements with empty SysName . . . . 205

Finding number of collection requests per subelement . . . 205

Filtering without case filter . . . 206

Finding the number of subelements in a family 206 Grouping all the subelements . . . 206

Displaying the classification of the xevice name dhcp200 . . . 206

Inserting in the past . . . 207

Appendix C. CLI return codes . . . . 209

snmpconf. . . 209

Standard output error messages . . . 209

reqedit . . . 213

Return code . . . 213

Standard output error messages . . . 213

resmgr . . . 215

Return code . . . 215

Standard output error messages . . . 215

inventory. . . 216

Return code . . . 216

Standard output error messages . . . 217

impexp . . . 218

Return code . . . 218

Standard output error messages . . . 219

Appendix D. Sample inventory script

221

Appendix E. Using prerequisite check

scripts . . . 227

Using the check_os script . . . 227

Running the check_os script . . . 227

Error messages . . . 228

Using the check_db script . . . 229

Tasks performed by the check_db script . . . 229

Running the check_db script . . . 230

Notices . . . 235

About this information

IBM®Tivoli®Netcool®Performance Manager, Version 1.3.2 is a bundled product consisting of two main components. A wireline component (formerly Tivoli Netcool/Proviso), and a wireless component (formerly Tivoli Netcool Performance Manager for Wireless).

TheIBM Tivoli(r) Netcool(r) Performance Manager: Command Line Interface Guide help you use the inventory and resmgr commands.

Intended audience

The audience for this guide is as follows:

v _{Tivoli Netcool Performance Manager Administrators} v _{Content Designers}

The Tivoli Netcool Performance Manager product suite

Tivoli 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 Performance Manager System Administrator uses to define policies and configuration, as well as verify and troubleshoot operations.

v _{Tivoli Netcool Performance Manager DataLoad provides flexible, distributed} data collection and data import of SNMP and non-SNMP data to a centralized database.

v _{Tivoli Netcool Performance Manager DataChannel aggregates the data collected} through Tivoli Netcool Performance Manager DataLoad for use by the Tivoli Netcool Performance Manager DataView reporting functions. It also processes online calculations and detects real-time threshold violations.

v _{Tivoli Netcool Performance Manager DataView is a reliable application server} for on-demand, web-based network reports.

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

The following figure shows the different Tivoli Netcool Performance Manager modules.

Tivoli Netcool Performance Manager documentations consists of the following: v _{Release notes}

v _{Configuration recommendations} v _{User guides}

v _{Technical notes} v _{Online help}

The documentation is available for viewing and downloading on the infocenter at http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/

Chapter 1. Introduction

The Tivoli Netcool Performance Manager Command Line Interface (CLI) lets you 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, these are the most commonly used and are therefore the focus of this guide.

Special characters and command-line utilities

When using the command-line utilities (like resmgr, for example) make sure that you use a backslash (\) to escape characters that are special to the shell and to the command line, especially the following:

v _{[ ]} v _{{ }} v _` v _" v _\ v _$

Accessing CLI utilities

The CLI utilities reside in the Tivoli Netcool Performance Manager DataMart and Tivoli Netcool Performance Manager DataLoad bin directories.

Procedure

1. 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 the first 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 Tivoli Netcool Performance Manager DataLoad command-line interfaces, ensure that your environment is set by entering the following command:

../dataMart.env

5. The CLI commands are in the bin directories where you installed Tivoli Netcool Performance Manager DataMart and Tivoli Netcool Performance Manager DataLoad.

If you selected the defaults during the installation, the location of these bin directories would be as follows:

v _{Tivoli Netcool Performance Manager DataMart}

/opt/datamart/bin

v _{Tivoli Netcool Performance Manager DataLoad}

The following types of executable reside in these bin directories:

v _{Basic Utilities -- CLI commands like resgmr and inventory that perform basic} Tivoli Netcool Performance Manager administrative tasks.

v _{Conversion Utilities -- CLI commands that convert different database file} formats into the Tivoli Netcool Performance Manager DataMart format. Note: The CLI utilities support a help option (-?) that explains how to use the command.

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 perform grouping and debugging operations from the command line.

Invoked without arguments, the inventory command brings up the DataMart Inventory Tool GUI, which is explained in detail in the IBM Tivoli Netcool

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

complete or partial inventories or grouping operations on a regular basis as part of a Tivoli Netcool Performance Manager deployment.

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

When a profile is run from the Inventory Tool GUI, the output goes to the UI and to 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 the output to a file:

inventory -noX ... > myInventory.log

Note that Appendix D, “Sample inventory script,” on page 221 contains a sample Korn Shell script that calls the inventory command. You can use this as a model for your own inventory wrapper programs.

Function

Inventory Management Utility

Synopsis

inventory

inventory [-D [DebugLevel]] [-U] [-name [profileName]]

[-action [operation]] [-reload [collectorNum]] [-noX] [-timeout] [-retry] [-ip ipaddress] [-reportGrouping]

[cseEngine [-ruleFile ruleFile][-ruleSubSet ruleSubset]]

Description

The inventory command, which resides in the $PVMHOME/bin directory and

supports a number of inventory management operations, and is the command-line equivalent of the DataMart Inventory Tool graphical utility.

For more information on using the DataMart Inventory Tool, see the IBM Tivoli

Netcool Performance Manager: DataMart Configuration and Operation Guide. The

inventory command is intended to be run from crontab, either called directly or from 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 Professional Services.

In very general terms, when a complete inventory is run, Tivoli Netcool Performance 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 the inventory profile is already locked, inventory attempts to unlock the profile. If the profile is running on the same host, inventory looks for the process. If the process does not exist, inventory removes the lock and proceeds. If the profile is running on a different host, inventory waits for the period specified by the -timeoutoption 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 IP

addresses and a set of specific discovery parameters (for example, timeout and number of retries) to the discovery server. The discovery server then executes the discovery formulas against the specified devices, in collaboration with the SNMP collector, producing a set of files containing the list of discovered resources and their attributes.

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

3. Synchronizes the newly-discovered elements and sub-elements with the information stored in the database, then writes the newly synchronized information to the database.

The synchronization operation is broken up into the following two phases: v _{Pre-synchronization}

Tivoli Netcool Performance Manager retrieves the list of elements and subelements associated with the inventory profile from the database. v _{Synchronization}

Tivoli Netcool Performance Manager compares either the set of elements and subelements collected by the discovery operation (if SNMP) or the contents of 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 retirement policy) to determine if the discovered resources (and properties) are new, updated, or deleted.

Tivoli Netcool Performance Manager retrieves the list of elements and sub-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 are created in the $PVMHOME/[importexport|importExportBulk]/ProfileName directory:

– synchro- Contains the successful results of the synchronization process that are then written to the database.

– synchroWait- Contains a list of files that for a variety of reasons could not be synchronized and were not written to the database. If this directory is populated, you should examine the files and determine the cause of failure.

v _{Tivoli Netcool Performance Manager compares the grouping of the files in} the synchro directory with the grouping rules specified in the inventory profile and writes the results to the following two directories in the $PVMHOME/[importexport|importExportBulk]/ProfileNamedirectory: v _{Tivoli Netcool Performance Manager extracts the information about the}

groups for elements and sub-elements from the files in the grouping directory and inserts the information into the database.

4. Applies grouping rules to the synchronized elements and subelements, and writes the results to the database.

a. Tivoli Netcool Performance Manager compares the grouping of the files in the synchro directory with the grouping rules specified in the inventory profile and writes the results to the following two directories in the $PVMHOME/[importexport|importExportBulk]/ProfileNamedirectory:

v _{grouping - Contains the successful results of the grouping process that are} then written to the database.

v _{groupingWait - Contains a list of files that for a variety of reasons could} not be grouped and were not written to the database. If this directory is populated, you should examine the files and determine the cause of failure.

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

Note: By default, Tivoli Netcool Performance Manager saves the three most current versions of the grouped files. The number of copies saved is

configurable. To change the number of copies saved, change the number_historyparameter in $PVMHOME/res/C/inventory.res.

Note: By default, Tivoli Netcool Performance Manager saves the three most current versions of the grouped files. The number of copies saved is

configurable. To change the number of copies saved, change the number_historyparameter in $PVMHOME/res/C/inventory.res. 5. Unlocks the inventory profile.

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

Options

-? Prints a usage statement for the command.

-action [all|discovery|grouping|lock|pregrouping|presynchro|synchro]all Specifies that the inventory command is to run all arguments to the -action option, executing a complete inventory and then grouping the results of the 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 phase of 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 of the inventory process.

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

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

pregrouping

Specifies that the inventory command is to run only the pre-grouping phase of the inventory process.

presynchro

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

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

Note: The presynchro option is useful for debuging or previewing potential updates to the database. This option is not used to perform a complete inventory process.'

synchro

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

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

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 and rule subsets. Pregrouping creates CSE groups and objects defined by CSE rules. Grouping adds CSE groups and objects to the database. You can run the pregrouping and grouping phases individually with the pregrouping

and grouping options. You can implement both the pregrouping and grouping phases together by running inventory cseEngine option as follows:

v _{Without options}

v _{With the -action "all" arguments}

v _{With the -action "pregrouping grouping" arguments} -ruleFile ruleFile

Specifies a text file that contains definitions for each of the rule subsets. The default file name and location is:

$PVMHOME/conf/cseRuleSubSets.conf. Specifying this option without specifying the -ruleSubSet option runs all of the rule subsets in the rule file.

-ruleSubSet ruleSubset

Runs a specified rule subset from the rule file. If you want to run more than one rule subset, list each of the rule subsets separated only by a comma.

-date Deprecated. -D DebuggingLevel

Turns on debugging, with levels specified by DebuggingLevel. Supported levels are 1 to 10, with 10 outputting the most information. Default is to write to standard error, unless the -DFile option is specified.

-DList string

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

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

-DFile DebuggingFile

Instructs the inventory command to write debugging information to the file specified by DebuggingFile, rather than to standard error.

-ip IPAddresses

Specifies that the inventory command runs against up to five IP addresses in the command line, using a comma as a separator. If you want to specify more than five IP addresses, list the addresses in a file and use the -mode subProfileoption. For example, to specify 5 IP addresses:

-ip 11.11.11.11,22.22.22.22,33.33.33.33,44.44.44.44,55.55.55.55

The IP addresses must belong to the set of included IP addresses defined within the associated inventory profile.

-mode subProfile

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

This option allows you to reduce the time of the inventory by targeting only 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 subProfile option, see the Tivoli Netcool Performance Management DataMart

Configuration and Operation Guide. -name profileName

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

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

elt inventory slowwan

exclude ipaddress snmpconf

fastlan lan subelt

filestoinsert mode subeltinv

grouping objectfilter synchro

icmp objectfilter wan

include rulefilter ||ROOTROOT||

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

Instructs the inventory command to reload the collector specified by CollectorNumber. The default is collector one (1). The inventory command should be called with this option set every time a profile or the resources in the profile have been changed. For more information, see the IBM Tivoli

Netcool Performance Manager: DataMart Configuration and Operation Guide .

You might, for example, write a wrapper that - among other things - waits for an event from the Discovery Server notifying it that a profile has changed, and then calls the inventory command with the -reload option set.

-reportGrouping

Instructs the inventory command to run the report grouping rules and update the deployed reports stored in the database. Report grouping rules must first have been created before this option can be used. For

information on creating report grouping rules, see the IBM Tivoli Netcool

Performance Manager: DataMart Configuration and Operation Guide . -retry Used in conjunction with the -timeout option. Specifies the number of

times to try to set a lock on a locked profile. The default is 1. -timeout

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

-U Deprecated -version

Examples

The following example crontab entry illustrates how to use the inventory command in an actual Tivoli Netcool Performance Manager deployment.

The entry runs a full inventory (-all ) against a CBQoS profile after first reloading SNMP collector 1.

0 2,16 * * * [ -f /pv/dm/dataMart.env ] && [ -x /pv/dm/bin/inventory ] && \

. /pv/dm/dataMart.env && inventory -name CBQoS -noX -action all -reload 1 >> \

/pv/dm/log/CBQoS.txt

Note: Appendix D, “Sample inventory script,” on page 221 contains a sample Korn Shell script that calls the inventory command. You can use this as a model for your own inventory wrapper programs.

Chapter 3. Using the dccmd command

Use the dccmd command to stop and start DataChannel components, and to obtain status information about applications running on a DataChannel and its

subchannels.

Running the dccmd command

About this task

Run the dccmd command as follows:

Procedure

1. Log in as pvuser to the server where the DataChannel is installed. 2. Change your working directory to the DataChannel home directory

(/opt/datachannel by default), as follows:

cd /opt/datachannel$

3. Set the DataChannel environment as follows:

. ./dataChannel.env

4. Run the dccmd command.

$ dccmd options

The dccmd command

Function

DataChannel Management Utility Synopsis

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

Description

The dccmd command is used to manage a DataChannel environment. Use the dccmd command to stop and start DataChannel components, and to obtain status

information about applications running on a DataChannel and its subchannels. Options

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

bounce

Stop and restart the selected components. cstatus

Show the cached status of the selected components. Each time the status is requested for a component, that status is retained and is reported using cstatus. The channel manager periodically requests the status of all running components. Such requests are normally issued about once per minute. Thus, requesting the cstatus will generally show the status of the selected components as of at most one minute in the past.

be running maintained by Channel Manager. Components are removed from the list without stopping the component. If components on this list are not running, Channel Manager repeatedly attempts to restart them. Forcing Channel Manager to forget a component prevents Channel Manager from automatically restarting a component without actually stopping the component.

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

start Starts the selected components. If the component ever fails, or is stopped by any other means than the stop command, the Channel Manager will attempt to restart it.

stop Stops the selected components.

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

Lists the components selected by the given pattern, application pattern or host pattern. This action is useful for verifying the set of components that would be affected by some other action.

name_patternidentifies a set of components by their name. If the -x option is specified, matching is performed using regular expressions, otherwise simple pattern matching is used. In addition to normal pattern matching, the special word all is interpreted to match any name (it is functionally equivalent to the pattern "" or the regex ".").

For all actions except usage, at least one instance of name_pattern, -app, and -host must be specified (if none are specified, dccmd will report an error).

If more than one pattern is specified, the set of components will be those that match all specified criteria. All pattern matching is case insensitive. Note: To prevent the shell from applying filename expansion, any patterns that include special matching characters (such as "*", "?") should be

enclosed in double quotes.

-x Use regular expressions for pattern matching (the syntax matches that of the Henry Spencer regex library). If specified, the application, host, and component patterns will use regular expression matching, otherwise, simple pattern matching will be used. For simple matching, * will match any substring of characters and # will match any single character. -app pattern -application pattern

Restricts the set of components to which the action will apply to those running an application that matches the pattern. For example, a pattern of CME would only apply the action to CME components. Similarly

CME|LDR would match CME or LDR components (assuming the -x option was specified). Components can be one of the following: BCOL, FTE, CME, LDR, DLDR, ALL, or *

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

-host pattern -hostname pattern

Restricts the set of components to which the action will apply to those running on a host whose name matches the pattern.

Example dccmd commands

Shows how to perform more common DataChannel component management tasks with 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 following syntax:

$ ./dccmd status pattern

For example:

$ dccmd status all

$ dccmd status -app "disc" $ dccmd status cme.1.1 $ dccmd status "*.1.*"

Chapter 4. Managing Tivoli Netcool Performance Manager

objects

Tivoli Netcool Performance Manager objects are the configuration data used by the Tivoli Netcool Performance Manager system to define data collection and

reporting. Resource Manager is a CLI tool that sits on top of the database and lets you manage the configuration information contained in the database.

When you work with resmgr you are working from the command line, emulating tasks you can perform using the Tivoli Netcool Performance Manager graphical user interface (GUI.) You can work from the command line to export and/or import Tivoli Netcool Performance Manager objects to or from the database and to or 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 Performance Manager 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 with Tivoli Netcool Performance Manager objects. Using the resgmr CLI lets you work with Tivoli Netcool Performance Manager objects in bulk.

The resmgr command lets you work with resources (elements and subelements) as well with the additional Tivoli Netcool Performance Manager objects described in this 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 system and you do not need to rediscover this information.

v _{Delete resources from test systems. Deleting resources from production systems} is not recommended. Instead, resources are retired and historical information previously collected remains in the database.

v _{Populate resources with additional properties. Tivoli Netcool Performance} Manager can work with both the technical properties discovered from the network (MIBs) and the business properties generated by inventory and

provisioning. Business properties can include customer tagging, contract number, and a wide variety of organizational information.

v _{Manage Tivoli Netcool Performance Manager objects. You can replicate} configuration information from system to system by using resmgr to export Tivoli Netcool Performance Manager objects to a file that you can then import to other Tivoli Netcool Performance Manager systems.

Understanding Tivoli Netcool Performance Manager objects

Explains the basics of Tivoli Netcool Performance Manager objects. It contains a description of Tivoli Netcool Performance Manager objects, the categories to which they belong, and their database index ranges.

About Tivoli Netcool Performance Manager objects

Tivoli Netcool Performance Manager objects are the configuration data used by the Tivoli Netcool Performance Manager system to define data collection and

reporting.

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

Resources include elements and subelements. Elements are managed nodes with addresses or hosts, and subelements are subcomponents of an element, such as a port, interface, 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, using the resource concept.

Tivoli Netcool Performance Manager objects are grouped into the following categories:

v _Resources

– elements and element groups – subelements and subelement groups – nomenclature v _Design – formulas – properties – thresholds – requests – calendars – timezones – inventory profiles v _{Administration}

– Tivoli Netcool Performance Manager DataMart users and groups – registry – miscellaneous v _Report – Web users – applications – scheduler – History Table – Sequences

About Tivoli Netcool Performance Manager object types

Each 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 objects related 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: subelement} property v _{fam: family} v _{se: subelement} v _{seprp: subelement} property value v _{fam: family} v _{seproperty: subelement} property description group v _{segp: subelement group}

v _{egp: element group}

v _{segp: subelement group} v _{egp: element group} v _{linkGroupSE: link between}

group of subelements and subelement

v _{linkGroupSE_APP: link} between group of subelements and report v _{linkGroupSE_RU: link}

between group of subelements and report user

v _{linkGroupSE_TCZ: link} between group of

subelements and timezone and Calendar

v _{linkGroupE: link between} group of elements and element

nomenclature v _{ngp: nomenclature group} v _{ncl: nomenclature} v _{vendor: vendor}

v _{ngp: nomenclature group} v _{ncl: nomenclature} v _{vendor: vendor}

v _{linkGroupN: link between} the group and the nomenclature

The following table lists the different Tivoli Netcool Performance Manager objects related to design components, along with the associated options for export and import.

Type Export Options Import Options

formulas v _{frm: formula} v _{fgp: formula} v _{mib: MIB} v _{frm: formula} v _{fgp: formula} v _{mib: MIB} property v _{propertyE: property of}

element v _{propertySE: property of} subelement v _{propertyRU: property of} report user v _{propertyE: property of} element v _{propertySE: property of} subelement v _{propertyRU: property of} report user

threshold v _{thrdv: threshold definition} v _{thrdv: threshold definition} request v _{segpreq: request on}

subelement group v _{pctile: percentile}

v _{segpreq: request on} subelement group v _{pctile: percentile} calendar v _{cal: Calendar} v _{cal: Calendar} timezone v _{tz: timezone} v _{tz: timezone} inventory profile v _{ogp: group of inventory}

profiles

v _{opt: option of the}

inventory profile. Use with ogp value.

v _{ogp: group of inventory} profiles

v _{opt: option of the}

inventory profile. Use with ogp value.

v _{linkGroupO: link between} group and options of the profile

Report

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

Type Export Options Import Options

web user v _{rusr: report (Web) user} v _{ruprp: report (Web) user}

property

v _{rugp: report (Web) user} group

v _{rusr: report (Web) user} v _{ruprp: report (Web) user}

property

v _{rugp: report (Web) user} group

v _{linkGroupRU: link} between group and the report (Web) user

Type Export Options Import Options

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: link}

between group and reporter

v _{linkGroupAPPS: link} between group and reporters; group and style sheets

scheduler v _{sched: Scheduler} v _{sched: Scheduler}

Administration

The following table lists the different Tivoli Netcool Performance Manager objects related to Administration components, along with the associated options for export and import

Type Export Options Import Options

DM user v _{usr: Tivoli Netcool} Performance Manager DataMart user

v _{usr: Tivoli Netcool} Performance Manager DataMart user registry v _{regisDM: Tivoli Netcool}

Performance Manager DataMart registry v _{regisDC: Tivoli Netcool}

Performance Manager DataChannel registry v _{regisDB: Tivoli Netcool}

Performance Manager database registry v _{regisDV: Tivoli Netcool}

Performance Manager DataView registry v _{regisMG: Tivoli Netcool}

Performance Manager DataChannel Manager registry

v _{regDesc: list of all} registries

v _{regInst: instances of all} registries

v _{regisDM: Tivoli Netcool} Performance Manager DataMart registry v _{regisDC: Tivoli Netcool}

Performance Manager DataChannel registry v _{regisDB: Tivoli Netcool}

Performance Manager database registry v _{regisDV: Tivoli Netcool}

Performance Manager DataView registry v _{regisMG: Tivoli Netcool}

Performance Manager DataChannel Manager registry

Type Export Options Import Options

others v _{pkg: all package tables} v _{reg: information about}

component that are running (similar to pvmstart)

v _{chnl: information about} channel

v _{client: registration} information about Tivoli Netcool Performance Manager clients

v _{dbi: export Tivoli Netcool} Performance Manager GUI information into CSV format

v _{err: list of Oracle errors} tracked by Tivoli Netcool Performance Manager v _{orausr: list of Oracle users}

v _{pkg: all package tables} v _{reg: information about}

component that are running (similar to pvmstart)

v _{chnl: information about} channel

v _{client: registration} information about Tivoli Netcool Performance Manager clients

v _{dbi: export Tivoli Netcool} Performance Manager GUI information into CSV format

v _{err: list of Oracle errors} tracked by Tivoli Netcool Performance Manager v _{orausr: list of Oracle users}

History Table

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

Type Export Options Import Options

history table v _{calH: Calendar history} v _{frmH: formula history} v _{thrdvH: threshold}

definition history v _{eltH: element history} v _{seH: subelement history} v _{segpreqH: subelement}

group request history v _{appH: reporter history} v _{segpH: subelement group}

history

v _{egpH: element group} history

v _{calH: Calendar history} v _{frmH: formula history} v _{thrdvH: threshold}

definition history v _{eltH: element history} v _{seH: subelement history} v _{segpreqH: subelement}

group request history v _{appH: reporter history} v _{segpH: subelement group}

history

v _{egpH: element group} history

Sequences

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

Type Export Options Import Options

sequences v _{DesignIndex: sequence of} indexes used for Tivoli Netcool Performance Manager Design objects such as formulas, reporters, properties and so on.

v _{ResourcesIndex: sequence} of indexes used for resources (elements, subelements, and groups)

v _{DesignIndex: sequence of} indexes used for Tivoli Netcool Performance Manager Design objects such as formulas, reporters, properties and so on.

v _{ResourcesIndex: sequence} of indexes used for resources (elements, subelements, and groups)

Linking Among Tivoli Netcool Performance Manager objects

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

Understanding Tivoli Netcool Performance Manager object IDs

Tivoli Netcool Performance Manager objects are internally identified by the database by using numerical IDs.

You should review the following information about ranges before allocating database indexes. For example, database indexes are allocated when you install Tivoli Netcool Performance Manager configuration objects that were created on one system onto a different system. Or when IBM delivers standard Technology Packs or 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 formula ID is created in that range. When using the Automatic Inventory module, new sub-elements and elements are created in that range. Resource Manager lets you create new objects and assign new database IDs to these new objects.

IBM does not support using resmgr to assign database IDs in the range from 100,000,000 to 4,294,967,296. Creating database indexes in other areas such as ranges from

0 to 50,000,000 or from 50,000,000 to 100,000,000 should happen only with approval of IBM support.

Working with resmgr

Explains the basics of working with the resmgr CLI. Using resmgr lets you manage Tivoli Netcool Performance Manager objects for automation and scripting purposes without interacting directly with the database schema.

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

Displaying resource manager options

You can display the command options available with resmgr by entering the following command:

resmgr -?

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

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

Usage: resmgr [-D [DebugLevel]] [-noX] [-histoDate 1] [-noHead] [-ListForced col1 val1 ...] [-reloadCol] [-collectorList] [-sep separator] [-sepRec] [-file File Name] [-line] [-dirPath] [-filter filter ColNames] [-filterRule] [-colNames [col names list]] [-rule] [-order order ColNames] [-isMandat mandatory type] [-split] [-isDefault] [-distinct] [-loadMemory] [-checkBeforeUpdate] [-mode mode] [-config config Name] [-export type] [-import type] [-delete type]

[-analyze space] [-?] [-DList [CodeTracingModesList]] [-DFile [DebugOutputFile]] [-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 :

sub-elment : se, seprp, fam group : segp, egp

nomenclature : ngp, ncl, vendor * Design :

formulas : frm fgp mib

property : propertyE, propertySE, propertyRU threshold : thrdv

request : segpreq, pctile calendar : cal

timeZone : tz

inventory profile : ogp opt rule : rulegp, ruleprp * Report :

web user : rusr, ruprp, rugp application : app agp appS scheduler : sched

* Admin : DM user : usr

registry : regisDM regisDC regisDB regisDV regisMG regDesc regInst others : pkg, reg, chnl dbmgr client dbi err orausr

* History table :

calH frmH thrdvH eltH seH segpreqH appH segpH egpH * Sequences :

DesignIndex, ResourcesIndex .

-import : type = * Resources :

elements : elt, scf, eprp, encl, eproperty sub-elment : se, seprp, fam, seproperty

group : segp, egp linkGroupSE linkGroupSE_APP linkGroupSE_RU linkGroupSE_TZC linkGroupE

linkGroupEGP

nomenclature : ngp, ncl, vendor linkGroupN * Design :

formulas : frm fgp linkGroupF linkMibF property : propertyE, propertySE, propertyRU threshold : thrdv

request : segpreq, pctile calendar : cal

timeZone : tz

inventory profile : ogp opt linkGroupO rule : rulegp, ruleprp

* Report :

web user : rusr, ruprp, rugp linkGroupRU

application : app agp appS linkGroupAPP linkGroupAPPS scheduler : sched

* Admin :

DM user : usr uLink uPerm

registry : regisDM regisDC regisDB regisDV regisMG others : pkg, reg, dbmgr

* History table :

calH frmH 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 XXX import : resmgr -import ogp -colNames "npath opt.name opt.instance opt.value" -file XXX

. report users : users

export : resmgr -export rusr -colNames "name ruprp.name ruprp.value" -file XXX import : resmgr -import rusr -colNames "name ruprp.name ruprp.value"

-line "users1|_|LongName|_|USERS 1|_|" group of users

export : resmgr -export rugp -colNames "npath rusr.name" -file XXX

import : resmgr -import rugp -colNames "npath rusr.name" -line "~group1|_|users1|_|" users in group of Sub-Element

export : resmgr -export groupSE -colNames "npath rusr.name" -file XXX import : resmgr -import groupSE -colNames "npath rusr.name" -line

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

Using column names

You import and export detailed Tivoli Netcool Performance Manager object information from the database in a format called column names (colNames). Columns names are fields that provide you with information about the Tivoli Netcool Performance Manager objects. The column names used by resmgr are logical mappings to the physical columns in the database.

This logical mapping can be a direct one-to-one mapping (for example, elt.name) or it can be a logical entity representing multiple columns or multiple operations performed on multiple tables to fulfill the requested operation (for example, segp.npath). The full name is object type.colName. If the object type is omitted, the object type for the action (-export) is used.

Resource column names

The following tables list the column names used for resources, elements, subelements, and subelement groups.

Element Column Names

The following table list the column names for elements:

Column Name Description

dbIndex Internal database index for the element. name Name of the element (or new name). type

The element type. Available values include: v _{snmp - defines an element for SNMP}

collections

v _{default_snmp - used for SnmpConf (*.*.*.*)} v _{star_snmp - used for SnmpConf}

(@IPrange)

v _{import - defines a host with imported} data. No SNMP collections are available. profil Name of the inventory profile used to

discover the element.

collector Number of the collector to which this element is assigned.

nclIdx Nomenclature index that allows link to encl, vendor.

missing Number of notFounds in the inventory process.

Column Name Description

comment

Description field.

The comment column name can also return information concerning resources that have been retired or deleted from inventory. The returned infomation for a retired resource includes the following:

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

Option: "missingCountInProfile LimiteDateInProfil"

Where:

v Action: Retired - Specifies that the resource has been retired.

v Date: "dateOfDelete"- Specifies when the resource was retired.

v Profile: "profileName" - Specifies the name of the inventory profile that was used to discover the resource.

v LastSee: "date"_{- Specifies the date when} the resource was last detected in the inventory.

v LastMissing: "missingNumber" _{- Specifies} the number of times inventory has failed to detect the resource.

v Option: "missingCountInProfile LimiteDateInProfil"- Specifies the retry count and age limit criteria defined in the inventory profile for deleting resources. state

The state of the element. Available values include:

v _on v _off

The element is switched to off by the inventory process after a period of time and a number of retries defined in the inventory profile tool.

date Date that the element was inserted or updated in the database, in number of seconds since 1 January 1970.

user Name of the user who created this element. origin The method used to add the element to the

database. (inventory, resmgr, and so on) encl.name Name and generic type of the element. encl.oid sysObjectIDof 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

Column Name Description

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 this

column name to export or import multiple properties.

eprp.value Property value of the element. If this contains a value, "eprp.name" must contain a value.

eprp.propertyname:value

The value of a specific element property. For example, eprp.IpAddress:value is the value of the ipAddress element property. You cannot use spaces in the property name. If you export using this column name, only elements that have a value for this column are included in the output.

eprp.value Provides a list of all properties. eprp.dataType

Data 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 Index for the element associated with this SNMP configuration.

eprp.defValue Property default value

scf.ipaddress Specifies the IP address, mask, subnets, or address list for the device. This cannot be NULL if any of the other SNMP

configuration (scf.) columns contain a value. scf.wcommunity SNMP community name used for writing. If

this contains a value, "scf.ipaddress" must contain a value.

scf.rcommunity SNMP community name used for reading. If this contains a value, "scf.ipaddress" must contain a value.

scf.timeout Length of time (in seconds) to wait for a response 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 it

fails. If this contains a value, "scf.ipaddress" must contain a value

scf.port SNMP port for the element. If this contains a value, "scf.ipaddress" must contain a value. scf.version Specifies the SNMP version associated with

this SNMP configuration.

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

Column Name Description

scf.colNb Identifies the collector associated with this SNMP configuration. A setting of 0 applies the SNMP configuration to all collectors. scf.bandwidth Specifies the maximum amount of traffic (in

Kbps) permitted for the corresponding IP address. For more information, see "SNMP Bandwidth Control and Collection

Smoothing" in the IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide.

Subelement Column Names

The following table lists the subelement column names:

Column Name Description

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 the

subelement (can be a combination of several properties obtained in the MIB.)

missing Number of notFounds in the inventory process

nclIdx Nomenclature index, which allows a link to family.

state

The state of the subelement. Available values are:

v _on v _off

The subelement is switched to off by the inventory process after a period of time and a number of retries defined in the inventory profile tool.

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

user UNIX name of the user who created this subelement.

date Date that the element was inserted or updated in the database, in number of seconds since 1 January 1970.

origin The method used to add the sub-element to the database. (inventory, resmgr, and so on.) fam.name Description of the family name (Linked to

Column Name Description

seprp.name Name of the property of the subelement. Use this column name to export or import all (multiple) properties. Do not use spaces in the property name.

seprp.dataType

Subelement property data type. Available values 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 this contains a value, "seprp.name" must also contain a value.

seprp.propertyname:value Value of a specific subelement property. For example, "seprp.Customer:value" is the value of the property Customer for this sub-element. Use this column name to export or import a single property. If you export using this column name, only subelements that have a value for this column are included in the output. ulabel

Description field.

The ulabel column name can also return information concerning resources that have been retired or deleted from inventory. The returned infomation for a retired resource includes the following:

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

"missingCountInProfile LimiteDateInProfil" Where:

v _{Action: Retired - Specifies that the} resource has been retired.

v _{Date: "dateOfDelete" - Specifies when the} resource was retired.

v _{Profile: "profileName" - Specifies the name} of the inventory profile that was used to discover the resource.

v _{LastSee: "date" - Specifies the date when} the resource was last detected in the inventory.

v _{LastMissing: "missingNumber" - Specifies} the number of times inventory has failed to detect the resource.

v _{Option: "missingCountInProfile} LimiteDateInProfil" - Specifies the retry count and age limit criteria defined in the inventory profile for deleting resources.

The following table lists the group or rule column names:

Column Name Description

dbIndex Oracle unique internal database index npath Entire path of the group (including the

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

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

when off.

origin Group origin (imported, inventory)

date Group's creation date

lgParent Supplies only the parent group, not the leaf group

lgChild Index of the child group

Nomenclature Column Names

The following table lists the nomenclature column names:

Column Name Description

dbIndex Oracle's unique internal database index for the nomenclature path.

npath

The 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 must be unique for type SysObjectID

ncl.type Nomenclature type, which can include SysObjectID (for encl), Vendor, ifType (for family)

Design objects

The following tables list the column names used for the Tivoli Netcool Performance Manager objects related to design.

Formula Column Names

The following table lists the formula column names:

Column Name Description

dbIndex Oracle unique internal database index

name Formula name

data Formula data

exprType Not used (included for compatibility with a previous 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 a previous version)

nbHost Historic property, which must be set to 1

defValue Not used for formula

domaine Not used (included for compatibility with a previous version)

invariant Not used for formula (only for property) subType Not used (included for compatibility with a

previous version)

genericId Link to the generic formula Idx user User who has created the formula (can

include Apdev, pvuser and so on) origin Origin of the formula. (can include

Apinstall, resmgr, unknown, and so on.) idxFrm Same index as dbIndex (link on the MIB

table)

mibPath Name of the MIB(s) used by the formula. mibOrigin MIB origin. (can include Apinstall and so

on.)

mibDate Date of last MIB update

mibUser User who has created the link to this MIB

Formula Group Column Names

The following table lists the formula group column names:

dbIndex Oracle unique internal database index

npath Formula group path

nName Formula long name, which is the

npath~name

lgParent Supplies only the parent group (not the leaf group)

LgChild Index of the child group

fgparent.name fgparent allowed to see the name or dbIndex of the parent group

Property Column Names

The following table lists the property column names.

Column Name Description

dbIndex Oracle unique internal database index. name Name of property (do not use spaces.) dataType Type of properties (string/float.) invariant

Distinguishes among element, sub-element, and report user

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

state Not used (included for compatibility with previous version.)

defValue Default value.

comment Description field.

Threshold Column Names

The following table lists the threshold column names.

Column Name Description

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

IdxGroup | segp.name Sub-Element Group Id (sub-element group dbIndex) | Sub-Element Group name IdxResource | se.name Sub-Element Resource Id (sub-elment

dbIndex) | Sub-Element Resource name mode

Mode of the threshold v _{1 = Under}

v _{2 = Over} v _{3 = Band}