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
Design
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 :
elements : elt, scf, eprp, encl, chnl
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"
fails. If this contains a value, "scf.ipaddress"