Tivoli IBM Wireline Component - INPM · Netcool Performance Manager 1.3.1 IBM Wireline Component ... Chapter 4: Managing Tivoli ... 134 Working with ...

IBMNetcool Performance Manager 1.3.1Tivoli
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 273.

Copyright IBM Corp. 1997, 2011US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

The Tivoli Netcool Performance Manager Product Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Tivoli Netcool Performance Manager Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Special Characters and Command-Line Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Accessing CLI Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2: Using the inventory Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

inventory Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3: Using the dccmd Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Running the dccmd Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

The dccmd command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Example dccmd Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Start Individual Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15View DataChannel Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 4: Managing Tivoli Netcool Performance Manager Objects . . . . . . . . . . . . . . . . . 17

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Understanding Tivoli Netcool Performance Manager Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

About Tivoli Netcool Performance Manager Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18About Tivoli Netcool Performance Manager Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Understanding Tivoli Netcool Performance Manager Object IDs . . . . . . . . . . . . . . . . . . . . . . . . 23

Working with resmgr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Displaying Resource Manager Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Using Column Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Resource Column Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

IBM Tivoli Netcool Performance Manager: Command Line Interface Guide iii

Contents

Design Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Report Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Application Column Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Administration Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Using Functions with Column Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Using the DECODE Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Using the UPPER Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Using the LOWER Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Using the TIME Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Using the DATE Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Using COUNT, MIN, MAX, SUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 5: Exporting and Importing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

The Export Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Mandatory Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Using -filterRule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Using Mandatory Links with Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Dividing Results into Multiple Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Including Field Separators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Including Record Separators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Specifying a File Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Specifying Path Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Removing the Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

The Import Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Mandatory Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Using -colNames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Including Field Separators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Including Record Separators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Specifying File Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Specifying Path Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Specifying Input Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Forcing the Creation Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Reloading Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Analyzing Tivoli Netcool Performance Manager Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Using a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Line-by-Line Explanation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

iv IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Contents

Chapter 6: Managing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Working with Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Exporting Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Importing Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Deleting Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Working with Subelements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Exporting Subelements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Importing Subelements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Deleting Subelements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Working with Groups or Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Subelement Group Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Exporting Groups and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Importing Groups and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Working with Composite Subelement Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Exporting composite subelement rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Importing or updating composite subelement rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Deleting composite subelement rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Working with Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Exporting Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Importing Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Deleting Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Using Mandatory Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Using Manadatory Links with Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Using Manadatory Links with Subelements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Using Manadatory Links with Subelement Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Using Mandatory Links with Inventory Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Using Mandatory Links with Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Chapter 7: Managing Design Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Working with Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Exporting Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Importing Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Deleting Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Working with Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Subelement Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Exporting Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

IBM Tivoli Netcool Performance Manager: Command Line Interface Guide v

Contents

Exporting Property Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Trouble Ticket Pack Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Properties Used by the Tivoli Netcool Performance Manager-enabled SAA Probes . . . . . . . . . 130Importing Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Working with Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Importing Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Deleting Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Working with Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Importing Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Deleting Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Working with Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Exporting Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Importing Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Deleting Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Working with Timezones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Exporting Timezones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Working with Inventory Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Duplicating an Inventory Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Importing Inventory Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Deleting Inventory Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Chapter 8: Managing Administration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Working with Tivoli Netcool Performance Manager DataMart Users and Groups . . . . . . . . . . . . . 146

Exporting Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Importing Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Deleting User and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Working with Registries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Exporting Registry Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Importing Registries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Deleting Registries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Working with Miscellaneous Tivoli Netcool Performance Manager Objects . . . . . . . . . . . . . . . . . . 162

Working with chnl (information about Collector). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Working with reg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Working with dbi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164For Limited Use (checking for problems after installation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Chapter 9:Managing Report Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

vi IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Contents

Working with Web Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Exporting Web User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Importing Web User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Deleting Web User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Working with Reporters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Exporting Reporters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Importing Reporters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Deleting Reporters and Reporter Stylesheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Working with Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Exporting Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Importing Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Deleting Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter 10: Managing History Table and Sequence Objects . . . . . . . . . . . . . . . . . . . . . . . . . 183

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Working with History Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Exporting History Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Importing and Deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Working with Sequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Chapter 11: Configuring Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Threshold Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Deploying Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Threshold Deployment Against Groups and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Deploying "Non-differentiated" Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Deploying Differentiated Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Working with Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Exporting Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Deleting Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Importing Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Setting Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Identifying Formula Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Setting a Threshold against a Group (dbIndex) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Setting a Threshold against a Group (name). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Setting a Threshold against a Resource (dbIndex) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Setting a Threshold against a Resource (name). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Setting a Future Threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

IBM Tivoli Netcool Performance Manager: Command Line Interface Guide vii

Contents

Setting Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Setting Burst Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Setting Period Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Threshold Troubleshooting Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Export Scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Export Scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Export Scenario 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Export Scenario 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Chapter 12: Configuring Timezones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Working with Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Exporting Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Deleting Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Importing, Modifying, and Creating Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Grouping Links of Sub-elements, Calendars,and Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Exporting Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Deleting Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Importing, Modifying or Creating Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Appendix A: Supported resmgr Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Appendix B: Common resmgr Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Working With SAA Probes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Exporting or Importing an SAA Probe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Exporting or Importing an SAA Probe With Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Exporting or Importing SAA Probe Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Deleting SAA Probes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Argument Descriptions for SAA Probe Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Listing subelement groups without resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Finding and Fixing Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Listing devices not assigned to a nomenclature group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Correctly classifying a Tivoli Netcool Performance Manager object . . . . . . . . . . . . . . . . . . . . . . 232Filtering subelements using the underscore (_) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Cutting and Pasting in Subelement Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Finding the subelement group index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Cutting the subelement group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Pasting the subelement group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Finding subelement groups without a parent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

viii IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Contents

Finding subelment groups with more than one parent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Finding number of child groups for a subelement group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Checking subelement group request history tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Checking the number of groups to which a subelement belongs . . . . . . . . . . . . . . . . . . . . . . . . 236Listing elements with empty SysName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Finding number of collection requests per subelement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Filtering without case filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Finding the number of subelements in a family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Grouping all the subelements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Displaying the classification of the xevice name dhcp200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Inserting in the past . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Appendix C: CLI Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

snmpconf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Standard Output Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

reqedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Return Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Standard Output Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

resmgr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249


inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251


impexp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253


Appendix D: Sample Inventory Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Sample Inventory Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Appendix E: Using Prerequisite Check Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Using the check_os Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Running the check_os Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Using the check_db Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Tasks Performed by the check_db Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

IBM Tivoli Netcool Performance Manager: Command Line Interface Guide ix

Contents

Running the check_db Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Additional Copyright Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3 . . . . . . . . . . . . . . . . . . . 277SCOTTY Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277BLT 2.4u . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279CMU-SNMP 1.14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Scotty 2.8, incrTCL 3.0, [incr TCL] 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279UCD SNMP 4.2.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280JDOM 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Regex 1.1a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

x IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Preface

IBM Tivoli Netcool Performance Manager 1.3.1 consists of two main components. A wireline component (formerly Tivoli Netcool/Proviso), and a wireless component (formerly Tivoli Netcool Performance Manager for Wireless).

The purpose of this guide is to help you use the inventory and resmgr commands.

Audience

The audience for this guide is the following:

• Tivoli Netcool Performance Manager Administrators

• Content Designers

Organization

This guide has the following organization:

• Chapter 1, Introduction on page 1– Provides a brief overview of the inventory and resmgr commands, and explains how to access them.

• Chapter 2, Using the inventory Command on page 5 –Explains how to manage inventory with the inventory command.

• Chapter 3, Using the dccmd Command on page 13 –Explains how to use the dccmd utility.

• Chapter 4, Managing Tivoli Netcool Performance Manager Objects on page 17 –Explains how to use resmgr to manage Tivoli Netcool Performance Manager objects.

• Chapter 5, Exporting and Importing Objects on page 53 – Explains how to use resmgr to export and import objects.

• Chapter 6, Managing Resources on page 79– Explains how to use resmgr to manage resources.

• Chapter 7, Managing Design Objects on page 121 – Explains how to use resmgr to manage design objects.

• Chapter 8, Managing Administration Objects on page 145 – Explains how to use resmgr to manage administrative objects.

• Chapter 9, Managing Report Objects on page 169 – Explains how to use resmgr to manage

• Chapter 10, Managing History Table and Sequence Objects on page 183 – Explains how to use resmgr to manage history table and sequence objects.

• Chapter 11, Configuring Thresholds on page 189 – Explains how to use resmgr to configure thresholds.

• Chapter 12, Configuring Timezones on page 213 – Explains how to use resmgr to configure timezones.

• Appendix A, Supported resmgr Options – Lists all the options supported by resmgr.

• Appendix B, Common resmgr Commands – Lists the more common uses for resmgr, with detailed examples.

• Appendix C, CLI Return Codes – Lists the return codes for all supported CLI commands.

IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Preface

The Tivoli Netcool Performance Manager Product Suite

Tivoli Netcool Performance Manager is made up of the following components:

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

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

• 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 on-line calculations and detects real-time threshold violations.

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

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

Figure 1: Tivoli Netcool Performance Manager Modules

DataLoadcollects network data.

DataChannelcomputesaggregationsand stores datain DataMart.

DataMartprovides datamanagement

DataViewproduces andmanages reports.

and applications.

Tivoli Netcool Performance Manager Documentation

Tivoli Netcool Performance Manager documentation consists of the following:

• release notes

• configuration recommendations

• user guides

• technical notes

• online help

The documentation is available for viewing and downloading on the infocenter at:

xii IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Preface

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

IBM Tivoli Netcool Performance Manager: Command Line Interface Guide xiii

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

Preface

xiv IBM Tivoli Netcool Performance Manager: Command Line Interface Guide

Chapter 1: Introduction

This chapter introduces you to the CLI commands, and is made up of the following topics:

Overview

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 a variety of CLI utilities, these are the most commonly used and are therefore the focus of this manual.

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:

• [ ]

• { }

• ‘

• "

• \

• $

Accessing CLI Utilities

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

To access the CLI utilities, follow these steps:

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 login as pvuser.

Topic Page

Overview 1

Accessing CLI Utilities 1

IBM Tivoli Netcool Performance Manager: Command Line Interface Guide 1


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:

../dataLoad.env

5. The CLI commands are located 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:

— Tivoli Netcool Performance Manager DataMart

/opt/datamart/bin

— Tivoli Netcool Performance Manager DataLoad

/opt/dataload/bin

The following types of executable reside in these bin directories:

— Basic Utilities — CLI commands like resgmr and inventory that perform basic Tivoli Netcool Performance Manager administrative tasks.

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

2 IBM Tivoli Netcool Performance Manager: Command Line Interface Guide


NOTES




Chapter 2: Using the inventory Command

This chapter explains how to use the inventory command to manage inventory, and is made up of the following topics:

Overview

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

You typically use the DataMart Inventory Tool to:

• Run inventories against profiles newly created with the Inventory Wizard to ensure that they work as expected.

• 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 contains a sample Korn Shell script that calls the inventory command. You can use this as a model for your own inventory wrapper programs.

Topic Page

Overview 5

inventory Command 6



inventory Command

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]] [-mode subProfile] [-?][-DList [CodeTracingModesList]][-DFile DebugOutputFile]]

Description

The inventory command (which resides in the $PVMHOME/bin directory) 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 Guide.

The inventory command is intended to be run from crontab, either called directly or from within a wrapper program.

Note the following:

• If run without options, the inventory command invokes the DataMart Inventory Tool.

• 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 sub-directory 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 -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 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.



inventory (cont)

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:

— Pre-synchronization

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

— Synchronization

Tivoli Netcool Performance Manager compares either the set of elements and sub-elements 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.

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.

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

4-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]/ProfileName directory:

* grouping – Contains the successful results of the grouping process that are then written to the database.

* groupingWait – Contains a list of files that for a 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.

4-b. 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.

Note: 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_history parameter 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.



inventory (cont)

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.


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.


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



inventory (cont)

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

— Without options

— With the -action “all” arguments

— With the -action “pregrouping grouping” arguments

-ruleFile ruleFile

Specifies a text file that contains definitions for each of the rule subsets. The default file name and location is: $PVMHOME/conf/cseRuleSubSets.conf. Specifying this option without specifying the -ruleSubSet option runs all of the rule subsets in the rule file.

-ruleSubSet ruleSubset

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

-date

Deprecated.

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

Note: 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 subProfile option. For example, to specify 5 IP addresses:

-ip 11.11.11.11,22.22.22.22,33.33.33.33,44.44.44.44,55.55.55.55

The IP addresses must belong to the set of included IP addresses defined within the associated 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.



inventory (cont)

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

-name profileName

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

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

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

Lists version information for the inventory command.

elt inventory slowwanexclude ipaddress snmpconf

fastlan lan subelt

filestoinsert mode subeltinvgrouping objectfilter synchro

icmp objectfilter wan

include rulefilter ||ROOTROOT||



inventory (cont)

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

This chapter explains how to use the dccmd utility, and consists of the following topics:

Overview

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

Run the dccmd command as follows:

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

Topic Page

Running the dccmd Command 13

Example dccmd Commands 15



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.

forget

Remove the selected components from the list of components that should 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_pattern identifies a set of components by their name. If the -x option is specified, matching is performed using regular expressions, otherwise simple pattern matching is used. In addition to normal pattern matching, the special word all is interpreted to match any name (it is functionally 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

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

This chapter explains how to use resmgr to manage Tivoli Netcool Performance Manager objects, and is made up of the following topics:

Overview

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:

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

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

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

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

Topic Page

Overview 17

Understanding Tivoli Netcool Performance Manager Objects 18

Working with resmgr 23

Using Functions with Column Names 45



Understanding Tivoli Netcool Performance Manager Objects

This section 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 sub-components 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.

About Tivoli Netcool Performance Manager Object Categories

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

• Resources

– elements and element groups

– subelements and subelement groups

– nomenclature

• Design

– formulas

– properties

– thresholds

– requests

– calendars

– timezones

– inventory profiles

• Administration

– Tivoli Netcool Performance Manager DataMart users and groups

– registry

– miscellaneous

• 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 • elt: element

• scf: SNMP configuration

• eprp: element property

• encl: nomenclature

• chnl: channel

• elt: element

• scf: SNMP configuration

• eprp: element property

• encl: nomenclature

subelement • se: subelement

• seprp: subelement property

• fam: family

• se: subelement

• seprp: subelement property value

• fam: family

• seproperty: subelement property description

group • segp: subelement group

• egp: element group

• segp: subelement group

• egp: element group

• linkGroupSE: link between group of subelements and subelement

• linkGroupSE_APP: link between group of subelements and report

• linkGroupSE_RU: link between group of subelements and report user

• linkGroupSE_TCZ: link between group of subelements and timezone and Calendar

• linkGroupE: link between group of elements and element

nomenclature • ngp: nomenclature group

• ncl: nomenclature

• vendor: vendor

• ngp: nomenclature group

• ncl: nomenclature

• vendor: vendor

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

Report

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


formulas • frm: formula

• fgp: formula

• mib: MIB

• frm: formula

• fgp: formula

• mib: MIB

property • propertyE: property of element

• propertySE: property of subelement

• propertyRU: property of report user

• propertyE: property of element

• propertySE: property of subelement

• propertyRU: property of report user

threshold • thrdv: threshold definition • thrdv: threshold definition

request • segpreq: request on subelement group

• pctile: percentile

• segpreq: request on subelement group

• pctile: percentile

calendar • cal: Calendar • cal: Calendar

timezone • tz: timezone • tz: timezone

inventory profile • ogp: group of inventory profiles

• opt: option of the inventory profile. Use with ogp value.

• ogp: group of inventory profiles

• opt: option of the inventory profile. Use with ogp value.

• linkGroupO: link between group and options of the profile


web user • rusr: report (Web) user

• ruprp: report (Web) user property

• rugp: report (Web) user group

• rusr: report (Web) user

• ruprp: report (Web) user property

• rugp: report (Web) user group

• linkGroupRU: link between group and the report (Web) user



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

application • app: reporter

• agp: group of reporters

• appS: reporter style sheet

• app: reporter

• agp: group of reporters

• appS: reporter style sheet

• linkGroupAPP: link between group and reporter

• linkGroupAPPS: link between group and reporters; group and style sheets

scheduler • sched: Scheduler • sched: Scheduler


DM user • usr: Tivoli Netcool Performance Manager DataMart user

• usr: Tivoli Netcool Performance Manager DataMart user

registry • regisDM: Tivoli Netcool Performance Manager DataMart registry

• regisDC: Tivoli Netcool Performance Manager DataChannel registry

• regisDB: Tivoli Netcool Performance Manager database registry

• regisDV: Tivoli Netcool Performance Manager DataView registry

• regisMG: Tivoli Netcool Performance Manager DataChannel Manager registry

• regDesc: list of all registries

• regInst: instances of all registries

• regisDM: Tivoli Netcool Performance Manager DataMart registry

• regisDC: Tivoli Netcool Performance Manager DataChannel registry

• regisDB: Tivoli Netcool Performance Manager database registry

• regisDV: Tivoli Netcool Performance Manager DataView registry

• regisMG: Tivoli Netcool Performance Manager DataChannel Manager registry




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

others • pkg: all package tables

• reg: information about component that are running (similar to pvmstart)

• chnl: information about channel

• client: registration information about Tivoli Netcool Performance Manager clients

• dbi: export Tivoli Netcool Performance Manager GUI information into CSV format

• err: list of Oracle errors tracked by Tivoli Netcool Performance Manager

• orausr: list of Oracle users

• pkg: all package tables

• reg: information about component that are running (similar to pvmstart)




• err: list of Oracle errors tracked by Tivoli Netcool Performance Manager



history table • calH: Calendar history

• frmH: formula history

• thrdvH: threshold definition history

• eltH: element history

• seH: subelement history

• segpreqH: subelement group request history

• appH: reporter history

• segpH: subelement group history

• egpH: element group history

• calH: Calendar history

• frmH: formula history

• thrdvH: threshold definition history

• eltH: element history

• seH: subelement history

• segpreqH: subelement group request history

• appH: reporter history

• segpH: subelement group history

• egpH: element group history




Sequences

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

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:

• From 0 to 50,000,000 - IDs of objects delivered by IBM as Technology Packs.

• From 50,000,000 to 100,000,000 - IDs of objects delivered by IBM.

• 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

This section 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.


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

• ResourcesIndex: sequence of indexes used for resources (elements, subelements, and groups)

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

• ResourcesIndex: sequence of indexes used for resources (elements, subelements, and groups)



Displaying Resource Manager Options

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

resmgr -?

Note: The command options that appear for your display might differ from the following examples because options are sometimes added and/or 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:

• snmp - defines an element for SNMP collections

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

• star_snmp - used for SnmpConf (@IPrange)

• import - defines a host with imported data. No SNMP collections are available.

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.

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:

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

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

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

• LastSee: "date" - Specifies the date when the resource was last detected in the inventory.

• LastMissing: "missingNumber" - Specifies the number of times inventory has failed to detect the resource.

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

• on

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

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

• 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).

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

• on

• 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 the discovery formula.)

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:

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

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



Group or Rule Column Names

The following table lists the group or rule column names:

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:

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

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

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

• LastSee: "date" - Specifies the date when the resource was last detected in the inventory.

• LastMissing: "missingNumber" - Specifies the number of times inventory has failed to detect the resource.

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


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:

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:


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~NetscoutThe 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)



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



Formula Group Column Names

The following table lists the formula group column names:

Property Column Names

The following table lists the property column names.

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



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


dbIndex Oracle unique internal database index.

name Name of property (do not use spaces.)



Threshold Column Names

The following table lists the threshold column names.

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.


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

• 1 = Under

• 2 = Over

• 3 = Band

thrStat Define which statistic will be used by the CME to calculate the threshold information:

• 0=raw(default)

• 1=min

• 2=max

• 3=avg

• 4=sum

• 5=count

• 6=squality

• 7=percentile

thrCalc The calculation mode to be used to determine percentage over/under the threshold. Values for this field include:

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

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

• 2=scaled means: abs(Value-Level)/scale where scale = thrCalcValue



thrCalcValue The value used for calculating the percentage over/under threshold in scaled mode.


brstCrtclLevel Level of the critical threshold for burst thresholds. Null implies that the threshold isn't 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 the metric exceeds the threshold.

brstWrnngTime Time limit for the warning period threshold in seconds

brstGenEvent Indicates if Tivoli Netcool Performance Manager has to generate events for the period 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 in seconds

prdPeriod Define the period:

• 1 = Day

• 2 = Week

• 3 = Month

• 4 = All means that the CME will use the period of the aggregation tables

prdGenEvent Whether Tivoli Netcool Performance Manager has to generate events for the burst threshold.

• 0=no

• 1=yes

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



Requests

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

Subelement Group Requests

The following table lists the subelement group request column names.

Percentile Column Names

The following table lists the percentile column names.

Request Column Names

The following table lists the column names for all requests.



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 Request Editor.)

user User who has created the request.

date Request creation date





state Request state, which can be on or off

status Request status, which can be active or idle

value Value of percentile parameter




Calendar Column Names

The following table lists the Calendar column names:




state Request state:

• on

• off

storage Request storage:

• always

• never

status Request status:

• active

• idle

period Period of collection in seconds

idxCal Calendar used for the request

origin Request origin:

• resmgr

• Request Editor

user User who has created the request

date Date of creation of the request

type Type of the request

• collection

• aggregation

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



name Calendar name

period Polling period (for collection calendar obsolete)

state State of the Calendar:

• on

• off

origin Origin of the Calendar

user User who created the Calendar.



Timezone Column Names

The following table lists the timezone column names:

date Creation or last update date. Use instead of date_DATE to convert it to the following format:

MM/DD/YYYY HH:mm

type Type of Calendar line Available values include:

• 1 for daily

• 2 for monthly

• 3 for weekly

• 4 for once

subType Subtype value available for each kind of Calendar. For example, available values for daily calendar include:

• 1 for all days

• 2 for working days

• 3 for weekend days

comment Description

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

• 0 for off

• 1 for on

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

fromDay Number for the first day of a monthly Calendar

fromTime Define Calendar beginning time

toDay Number of the last day of a monthly Calendar

toTime Define Calendar ending time


dbIndex Unique Oracle internal database index number

name Unique timezone name (in this table)

offset Time lag from GMT in seconds

status Aggregation set (aggset) database representation status:

• 0: configured

• 1: created

• 2 active

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

comment Optional description of the aggregation set



Inventory Profile Column Names

The following table lists the Inventory profile column names:

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


dbIndex Unique Oracle internal database index of the group

npath Path for this group as defined by the name of the profile, followed by the step name and 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, else 0 = n. Required when an option has multiple values

opt.value Value of the option.



Report Objects

The following tables list the column names used for the Tivoli Netcool Performance 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

type Type of report user:

• Tivoli Netcool Performance Manager USER

• EMAIL RECIPIENT

• DV SUPER USER

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

user Name of the user who created this report user.

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

ruprp.propertyname:value The value of a specific property of the report user. For example, "ruprp.IpAddress:value" is the value of the ipAddress property of the report user. Do not use spaces in property names.

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

ruprp.value List of all properties

ruprp.dataType Datatype of the property of the report user. Available values include:

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

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

Application Column Names

The following table lists the application column names.

app can be grouped in agp (report group)



npath Complete path of the group (including the group name)

name Name of the group

owner rusr with type=EMAIL RECIPIENT



name Application name

url URL of the page that defines the visual characteristics of the report

comment Comment

type Report type:

• 0 for ByResource

• 1 for ByGroup

typeR Type of application

• Reporter(Report)

• DVCR(template)

• DVRS(scheduler)

data Binary stream that holds the report properties

owner Used by the scheduler

alias Used by the scheduler

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

user Name of the user who created this application.



Report Style Column Names

The following table lists the report style column names.

appS can be grouped in agp (report group)

Application Group Column Names

The following table lists the application group column names.

Scheduler Column Names

The following table lists the scheduler column names.



definition Report style definition

comment Report style comment

name Report style name

type Report style type. (Default value is 0)



npath Complete path of the group (including the group name)

name Group name


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

date Date when the latest change occurred

idxTarget Target index. For example, reporter

idxShed Scheduled task index.

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

state State of the DVCR task:

• ACTIVE

• SUSPENDED



Administration Objects

DM User Column Names

The following table lists the DM user column names.

Registry Column Names

The following table lists the registry column names.

status Current status of the scheduled task:

• SUSPEND

• STOP

• IDLE

Server_name>

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

end Timestamp that indicates the effective end date when an ACTIVE task will no longer run

success Timestamp that indicates the last time this DVCR successfully ran

next Timestamp that indicates the next time this schedule will run

failNb Parameter that indicates the number of times the schedule failed to successfully complete component processes

tuser Name of the latest user that changes the application

tdate Date when the latest change occurred



name User name, which must match the UNIX login name

fullname User full name (description field)

gpname Group user name. Users belonging to that group automatically inherit the group's rights.

gpcomment Group description

module Module names

perms Access rights


path Path of the registry



Collector Information Column Names

The following table lists Collector information column names.

name Name of the registry

value Value for the registry

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

type • 0=NUMBER

• 1=STRING

• 2=DATE

• 3=BOOLEAN

flag • 0=CONSTANT

• 1=VARIABLE


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

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

collector Collector number to which this channel is assigned.

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

name Name of the registered module. For example, pvmd_1

pid Protocol identifier (pid) of the registered module

user User who launches the registered module.

date Date of the launching of the registered module. Use instead date_DATE to convert it to the following format MM/DD/YYYY HH:mm

display Display host where the registered module is running.

status Status of the registered module.

instDir Home directory path

comment Description of the module

hostReg Host name in the registry



conds into xxd

nd since 1970 in /DD/YYYY

subelements he columns that

Registration Column Names

The following table lists the registration column names.

Using Functions with Column Names

This chapter explains how to use functions with column names. These functions extend the use of column names, providing additional actions on the data sets.

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

Using the DECODE Function

The following examples of the DECODE function convert enumeration integer values into strings. You can use DECODE to make a file easier to review.


name Name of the registered module.

host Host that is running the registered module

pid Protocol identifier (pid) of the registered module

user User who launches the registered module.

date Date of the launching of the registered module. Use instead date_DATE to convert it to the following format MM/DD/YYYY HH:mm

display Display host where the registered module is running.

port Used only for the server (pvmd or provisoinfod).

lock Name of the locked module

mode 1 for r/w

Function Description

DECODE Converts an enumeration integer value into a string

UPPER Converts string types into upper case

LOWER Converts string types into lower case

TIME Use only on time values to transform the number of sexxh xxm xxs (day, hour, minute, second)

DATE Use only on a date value to transform a number of secoreadable format. convert it to the following format MMHH:mm

COUNT, MAX, MIN, SUM Use with numerics. For example, count the number of belonging to an element. Another example, sum of all tdo not have aggregation values.



Example 1

The following command shows the output without the use of the DECODE function:

resmgr -export app -colNames "name type"

generates the following output:

Host-Site with CoS - DC - specific protocol OUT|_|0|_|<E>Top N_Hosts|_|1|_|<E>Top N Host Conversations with CoS.|_|1|_|<E>Top N Host Conversations with No CoS|_|1|_|<E>

Example 2

The following example shows the use of the DECODE function along with the export command:

resmgr -export app -colNames "name type_DECODE"


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>

Example 3

The following command:

resmgr -export app -colNames "name type" -file $DIR/DECODE_NO.dat


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

Example 4


resmgr -export app -colNames "name type_DECODE" -file $DIR/DECODE_YES.dat


# type = app# col = name type_DECODE# filter =# order =



# sep = |_|# sepRec = <E>## cmdLine = -export app -colNames "name type_DECODE"Interface Volume Resource Detail Chart|_|ByResource|_|<E>Interface Volume Resource|_|ByGroup|_|<E>Interface Volume Resource Threshold - Inbound Volume (octets)|_|ByGroup|_|<E>Interface Volume Resource Threshold - Inbound Throughput (bps)|_|ByGroup|_|<E>Interface Volume Resource Threshold - Outbound Volume (octets)|_|ByGroup|_|<E>Interface Volume Resource Threshold - Outbound Throughput (bps)|_|ByGroup|_|<E>

Using the UPPER Function

You can use the UPPER function with any string type to convert results into upper case.

Example 1


resmgr -export elt -colNames "name" -filter "name_UPPER(*BOSTON*)"


bulk100-boston_100,12|_|bulk100-boston_0|_|bulk100-boston_100,13|_|

Example 2


resmgr -export elt -colNames "name" -filter "name_UPPER(*BOSTON*)" -file $DIR/UPPER_YES.dat


# type = elt# col = name# filter = name_UPPER(*BOSTON*)# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name" -filter "name_UPPER(*BOSTON*)"123_Boston|_|

Example 3


resmgr -export elt -colNames "name" -filter "name(*BOSTON*)" -file $DIR/UPPER_NO.dat


# type = elt# col = name



# filter = name(*BOSTON*)# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name" -filter "name(*BOSTON*)"

Using the LOWER Function

You can use the LOWER function with any string type to convert results into lower case.

Using the TIME Function

You can use the TIME function on time values to transform the number of seconds into xxd xxh xxm xxs (day, hour, minute, second)

Example 1


resmgr -export thrdv -colNames "fgp.nName segp.npath brstCrtclLevel brstCrtclTime" -filter "brstCrtclTime(!='0 ')"


~AP~Generic~Universal~Other~Inbound Loss (percent)|_|~NOC Reporting|_|14|_|-1|_|~AP~Generic~Universal~Utilization~Storage Utilization (per-cent)|_||_|99|_|7200|_|~AP~Generic~Universal~Utilization~Storage Free (bytes)|_||_|160000|_|3600|_|

Example 2


resmgr -export thrdv -colNames "fgp.nName segp.npath brstCrtclLevel brstCrtclTime_TIME" -filter "brstCrtclTime(!='0')"


~AP~Generic~Universal~Other~Inbound Loss (percent)|_|~NOC Report-ing|_|14|_|RESERVED|_|~AP~Generic~Universal~Utilization~Storage Utilization (percent)|_||_|99|_|2h|_|~AP~Generic~Universal~Utilization~Storage Free (bytes)|_||_|160000|_|1h 2m|_|

Example 3


resmgr -export thrdv -colNames "fgp.nName segp.npath brstCrtclLevel brstCrtclTime" -filter "brstCrtclTime(!=’0’)" -file $DIR/TIME_NO.dat


# type = thrdv# col = fgp.nName segp.npath brstCrtclLevel brstCrtclTime



# filter = brstCrtclTime(!=’0’)# order =# sep = |_|# sepRec =## cmdLine = -export thrdv -colNames "fgp.nName segp.npath brstCrtclLevel brst-CrtclTime" -filter "brstCrtclTime(!=’0’)"~AP~Generic~Universal~Utilization~Inbound Utilization (percent)|_|~Customer Fac-ing Reporting|_|10|_|900|_|~AP~Generic~Universal~Utilization~Outbound Utilization (percent)|_|~Customer Facing Reporting|_|10|_|900|_|~AP~Generic~Universal~Utilization~Storage Utilization (percent)|_|~Tivoli Net-cool Performance Manager System Monitoring|_|99|_|7200|_|~AP~Generic~Universal~Utilization~Storage Free (bytes)|_|~Tivoli Netcool Perfor-mance 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 Report-ing|_|1|_|900|_|~AP~Generic~Universal~Other~Outbound Loss (percent)|_|~Customer Facing Report-ing|_|1|_|900|_|


resmgr -export thrdv -colNames "fgp.nName segp.npath brstCrtclLevel brstCrtclTime_TIME" -filter "brstCrtclTime(!=’0’)" -file $DIR/TIME_YES.dat


# 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 Fac-ing Reporting|_|10|_|15m|_|~AP~Generic~Universal~Utilization~Outbound Utilization (percent)|_|~Customer Facing Reporting|_|10|_|15m|_|~AP~Generic~Universal~Utilization~Storage Utilization (percent)|_|~Tivoli Net-cool Performance Manager System Monitoring|_|99|_|2h|_|~AP~Generic~Universal~Utilization~Storage Free (bytes)|_|~Tivoli Netcool Perfor-mance 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 Report-ing|_|1|_|15m|_|~AP~Generic~Universal~Other~Outbound Loss (percent)|_|~Customer Facing Report-ing|_|1|_|15m|_|

Using the DATE Function

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



Example 1


resmgr -export elt -colNames "name date"


bulk100-boston_1000,19|_|1055363091|_|192.168.69.245|_|1057019303|_|192.168.69.243|_|1057019303|_|resmgr -export elt -colNames "name date_DATE"bulk100-boston_1000,19|_|06/11/2003 22:24|_|192.168.69.245|_|07/01/2003 02:28|_|192.168.69.243|_|07/01/2003 02:28|_|

Example 2


resmgr -export elt -colNames "name date" -file $DIR/DATE_NO.dat


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

Example 3


resmgr -export elt -colNames "name date_DATE" -file $DIR/DATE_YES.dat


# 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

You can use these functions

Example 1


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


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



NOTES


Chapter 5: Exporting and Importing Objects

This chapter explains how to use the resmgr command to import and export objects, and is made up of the following topics:

The Export Syntax

This section explains the syntax used for the export option of the resmgr command. You must include the mandatory options with the resmgr -export command and add other options for additional

resmgr -export <object type> <mandatory options> <additional options>

Mandatory Options

You must use the following options when issuing a resmgr export command.

Example

The following example shows the use of the -rule option with a mix of text and variable to specify the format for the columns. This modifies the construction of the subelement labels for import.

resmgr -export elt -rule "the name of the element is : %(elt.name)"

the name of the element is : bulk100-boston_1000,19|_|the name of the element is : 192.168.69.245|_|

Topic Page

The Export Syntax 53

The Import Syntax 61

Using a Configuration File 65

Option Description

<object type> name(is null)name(not null)

-colNames a list of colNames. If no value is used with the CLI and a default value exists, the default value is used.If you do not want to use the -colName option because you want to format the columns, use -rule.

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



the name of the element is : 192.168.69.243|_|

Refer to the chapters containing specific commands for additional examples of mandatory options.

Additional Options

You can use the following additional options with the export option.

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 filter the results of a command.

The following table lists available -filter values:

Example

resmgr -export elt -colNames "name profil state missing" -filter "missing(between'0 and 3') name_UPPER(*BOST*)"

bulk100-boston_1000,18|_|bulk_100|_|on|_|0|_|bulk100-boston_100,11|_|bulk_100|_|on|_|0|_|

Option Description

-filter Filter the results of the export command

-filterRule Broaden your filtering capabilities by entering a string against which results are compared to find matches.

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

-order List columns in order

-distinct Eliminate duplicate lines

-ListForced Force columns to display values

Values Examples

is null, not null name(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,!=,>,<,..) 'any character'AND is made between filters

name(!='ddd')number(<='10')name(in'ddd','aaa','bbb')between('0 and 3')



bulk100-boston_1000,19|_|bulk_100|_|on|_|0|_|

Using -filterRule

You can use the following filter option if you need to broaden your filtering capabilities; for example if -filter is too restricted. You can enter a string against which results are compared to find matches.

-filterRule "string"

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

Example 1

resmgr -export elt -colNames "name profil state" -filterRule "%(elt.profil) LIKE ’%T%’ OR %(elt.state) = ’on’" -file $DIR/filterRule1.dat

marketing.quallaby.com|_|QuallabyNetwork|_|on|_|acacia.quallaby.com|_|QuallabyNetwork|_|on|_|eng1.quallaby.com|_|QuallabyNetwork|_|on|_|u440.quallaby.com|_|QuallabyNetwork|_|on|_|tadpole.quallaby.com|_|QuallabyNetwork|_|on|_|dhcp195.quallaby.com|_|QuallabyNetwork|_|on|_|192.168.127.254|_|Cisco_SAA|_|on|_|

Example 2

The percentage sign (%) is considered as any 0-n character and _ (underscore) is considered one character. If you need to use the underscore in your filter, you must include an escape character for it.

resmgr -export elt -colNames "name profil state" -filterRule "%(elt.profil) LIKE ’%T%’ OR %(elt.state) = ’on’" -file $DIR/filterRule1.dat

marketing.quallaby.com|_|QuallabyNetwork|_|on|_|acacia.quallaby.com|_|QuallabyNetwork|_|on|_|eng1.quallaby.com|_|QuallabyNetwork|_|on|_|u440.quallaby.com|_|QuallabyNetwork|_|on|_|tadpole.quallaby.com|_|QuallabyNetwork|_|on|_|dhcp195.quallaby.com|_|QuallabyNetwork|_|on|_|192.168.127.254|_|Cisco_SAA|_|on|_|

Example 3

In the following example the string %(xxx) LIKE '%@_%' ESCAPE '@' tells ORACLE that the escape character is @. If you need to use @ in your condition, you can choose another character.

resmgr -export se -colNames "name profil" -filterRule "%(elt.profil) LIKE’%@_protocol%’ ESCAPE ’@’" -file $DIR/filterRule2.dat



NF-iphost-site-flow-CoffeeBucks|_|NF_protocol|_|NF-site-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*"

Using -order

You can use the following command to list columns in order.

-order "colNames"

You use the same syntax used for all -colNames, except for those that are logical entities (npath, nName.)

resmgr -export elt -colNames "name profil state" -order "profil"

# type = elt# col = name profil state# filter = # order = profil# sep = |_|# sepRec = # rule = # filterRule = ## cmdLine = -export elt -colNames "name profil state" bulk100-boston_100,12|_|bulk_100|_|on|_|bulk100-boston_0|_|bulk_100|_|on|_|bulk100-boston_100,13|_|bulk_100|_|on|_|bulk100-boston_100,14|_|bulk_100|_|on|_|bulk100-boston_1000,10|_|bulk_100|_|on|_|bulk100-boston_1000,11|_|bulk_100|_|on|_|bulk100-boston_1000,12|_|bulk_100|_|on|_|bulk100-boston_1000,13|_|bulk_100|_|on|_|bulk100-boston_1000,15|_|bulk_100|_|on|_|bulk100-boston_1000,19|_|bulk_100|_|on|_|bulk100-boston_100,11|_|bulk_100|_|on|_|bulk100-boston_1000,18|_|bulk_100|_|on|_|bulk100-boston_100,10|_|bulk_100|_|on|_|bulk100-boston_1000,17|_|bulk_100|_|on|_|bulk100-boston_1000,16|_|bulk_100|_|on|_|bulk100-boston_1000,14|_|bulk_100|_|on|_|bulk100-boston|_|bulk_100|_|on|_|bulk100-boston_100,19|_|bulk_100|_|on|_|bulk100-boston_100,18|_|bulk_100|_|on|_|bulk100-boston_100,17|_|bulk_100|_|on|_|bulk100-boston_100,16|_|bulk_100|_|on|_|bulk100-boston_100,15|_|bulk_100|_|on|_|add_elt2|_|profil1|_|on|_|add_elt3|_|profil1|_|on|_|add_elt1|_|profil1|_|on|_|add_elt4|_|profil1|_|on|_|dber|_|test1|_|on|_|



Using -distinct

You can use the following command to eliminate duplicate result lines.

-distinct 1 (by default : 0)

resmgr -export elt -colNames "profil" -distinct 1

bulk_100|_|test2|_|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 object types:

• eprp

• seprp

• ruprp

• encl.name

• fam.name

Example

resmgr -ListForced "seprp.Customer:value \"\" seprp.Cos:value \"\"" -export se -colNames "elt.name name label seprp.Customer:value seprp.Cos:value"

router1|_|router1_interface<1>|_|Ethernet[1]|_|Coca Cola|_|Gold|_| router1|_|router1_interface<2>|_|Ethernet[3]|_||_||_| router2|_|router2_interface<1>|_|Ethernet[1]|_|Air France|_||_| router2|_|router2_interface<2>|_|Ethernet[2]|_||_|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 Elements

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

See Chapter 6, Managing Resources for information.



Dividing Results into Multiple Lines

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

-split

use only with eprp, seprp, ruprp

Divide results into multiple lines

resmgr -export elt -colNames "name eprp.name eprp.value" -split -file $DIR/split_elt.dat

172.31.0.31|_|ipAddress|_|172.31.0.31|_|172.31.0.31|_|ipName|_|172.31.0.31|_|172.31.0.31|_|physAddress|_|6.0.3.227.233.33.160|_|172.31.0.31|_|Cisco Internetwork Operating System Software \nIOS (tm) C2600 Software (C2600-T|_|172.31.0.31|_|sysName|_|"c2610-31-LER"|_|172.31.0.41|_|ipAddress|_|172.31.0.41|_|172.31.0.41|_|ipName|_|172.31.0.41|_|

Display results on a single line

resmgr -export elt -colNames "name eprp.name eprp.value" -file $DIR/splitno_elt.dat

172.31.0.31|_|ipAddress|_|172.31.0.31|_|ipName|_|172.31.0.31|_|physAd-dress|_|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|_|physAd-dress|_|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 Separators

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

-sep

resmgr -export elt -colNames "name profil state" -sep ","

# type = elt# col = name profil state# filter = # order = # sep = ,# sepRec = # rule = # filterRule = ## cmdLine = -export elt -colNames "name profil state" default,,on,bulk100-boston_100,12,bulk_100,on,bulk100-boston_0,bulk_100,on,



bulk100-boston_100,13,bulk_100,on,bulk100-boston_100,14,bulk_100,on,

Including Record Separators

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

-sepRec

resmgr -export elt -colNames "name profil state" -sep "," -sepRec ";"

# type = elt# col = name profil state# filter = # order = # sep = ,# sepRec = ;# rule = # filterRule = ## cmdLine = -export elt -colNames "name profil state" default,,on,;bulk100-boston_100,12,bulk_100,on,;bulk100-boston_0,bulk_100,on,;bulk100-boston_100,13,bulk_100,on,;bulk100-boston_100,14,bulk_100,on,;

Specifying a File Name

You can specify a filename for exporting tasks. If you do not use the -file option (the default is that -file is not used,) the output will be UNIX standard output. If you need to include a path, you can use the "-dirPath" option or set the entire path enclosed in double quotes (" ".) You can also enter the entire path for a file together with the filename.

-file

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

Specifying Path Locations

You can specify a path location for exported (as well as imported) data files. Because this option specifies only the path, you need to use the "-file" option if you also want to specify the name of the file. Remember to enclose the path in single (' ') or double quotes (" ".)

-dirPath

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

Create the file : /tmp/test1.



Removing the Header

useful when scripting and pipe to other tools

-noHead

Remove the header for export

resmgr -export elt -colNames "name" -noHead -file $DIR/noHead.dat

172.31.0.31|_|172.31.0.41|_|172.31.0.51|_|172.31.1.2|_|192.168.1.3|_|192.168.127.1|_|192.168.127.2|_|192.168.127.254|_|192.168.127.3|_|192.168.127.4|_|192.168.127.5|_|192.168.127.6|_|192.168.127.7|_|192.168.127.8|_|192.168.127.9|_|192.168.64.253|_|192.168.66.2|_|192.168.68.162|_|APRouterforprobe|_|Burned_100008089_192.168.1.3|_|CoffeeBucks-192.168.1.1|_|Delete_100000165_192.168.3.238|_|Delete_100000174_192.168.2.2|_|

Display with headers

resmgr -export elt -colNames "name" -file $DIR/withHead.dat

# type = elt# col = name# filter =# order =# sep = |_|# sepRec =# cmdLine = -export elt -colNames "name"172.31.0.31|_|172.31.0.41|_|172.31.0.51|_|172.31.1.2|_|192.168.1.3|_|192.168.127.1|_|192.168.127.2|_|192.168.127.254|_|192.168.127.3|_|192.168.127.4|_|192.168.127.5|_|192.168.127.6|_|



192.168.127.7|_|192.168.127.8|_|192.168.127.9|_|192.168.64.253|_|192.168.66.2|_|192.168.68.162|_|APRouterforprobe|_|Burned_100008089_192.168.1.3|_|CoffeeBucks-192.168.1.1|_|Delete_100000165_192.168.3.238|_|Delete_100000174_192.168.2.2|_|

Display the number of columns without headers

resmgr -export elt -colNames "name" -noHead | wc -l

23

The Import Syntax

Import (insert or update) metadata. This option lets you specify the type (object type) of data for importing.

resmgr -import <object type> -mode [insert|update|Ifirst]

Mandatory Options

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

Using -colNames

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

Option Description

<object type> name(is null)name(not null)

-colNames a list of colNames is mandatory. If -file or -line is omitted, UNIX standard input (stdin) is used to let you pipe the standard import.

-mode • insert - insert only. Use this value if you are importing a large amount of new data into the database. If the resource already has a value for this column, it is not updated.

• update - update only. If the resource does not have a value for this column, data is not inserted.

• Ifirst - insert first (default). First attempt to insert. If the resource already has a value for this column, the value is updated.



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

ImporBulk|_|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 state profil(myProf%(col1)_%(col2)) collector(3)" -file Test1.rgr

ImporBulk|_|val1|_|val2|_|import_|_|on|_|.....

Example 3

You can use the option OLD_colname when updating the colname used as an index for finding the record.

resmgr -import elt -colNames "OLD_name name" -line "NameNow|_|NewName"

Including Field Separators

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

-sep

Including Record Separators

You can include record separators when you export data. The default record separator value is "end of line." You can also use the isMandatory value when colNames such as app or frm could potentially include the end of line in their field. (You must also use the same for the export.)

-sepRec

Specifying File Names

You can specify a filename for exporting tasks. If you do not use the -file option (the default is that neither -file nor -line option is used,) the output will be UNIX standard output. If you need to include a path, you can use the "-dirPath" option or set the entire path enclosed in double quotes (" ".) You can also enter the entire path for a file together with the filename.

-file



Specifying Path Locations

You can specify a path location for imported (as well as exported) data files. Because this option specifies only the path, you need to use the "-file" option if you also want to specify the name of the file. Remember to enclose the path in single (' ') or double quotes (" ".)

-dirPath

Specifying Input Data

You can specify input data from the command line.

-line

resmgr -delete elt -colNames "name" -line "bulk100-boston_0"

info : === delete : DELETE ON Element ( bulk100-boston_0 ) (exists)Title : === CHANGES : {1 Deleted of elt}Info : === Inform Collector On hebus:3002

Forcing the Creation Date

You can force the creation date stamped.

-histoDate

• 0: current date (not forced default value)

• 1: force the date to the value defined

Example

resmgr -import se -colNames "name elt.name instance date(1057015945)" -histoDate 1

Import the se at : 07/01/2003 01:32

Reloading Collectors

You can reload the Collectors.

-reloadCol val

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

Available values are as follows:

• on (default) - reload collectors to reread the database for changes or updates

• off - do not reload collectors

• forced - always reload collectors

Examples

resmgr -import ..... -reloadCol off



resmgr -import ..... -reloadCol on

resmgr -import ..... -reloadCol forced

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

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

Analyzing Tivoli Netcool Performance Manager Object

You can generate an analysis of the resource tables for the following Tivoli Netcool Performance Manager objects:

• elt

• se

• egp

• segp

-analyze <object type>

Example

resmgr -analyze se

Info : === ANALYZE : ON se (Synchro)



Using a Configuration File

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

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

Note: If you specify an option both in a configuration file and from the command line, the command line 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 the command line for the -config option, the configurations are executed



.

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

! export all elements with attributes

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

Lines beginning with an exclamation point (!) are comments.

*exportE_operation: export elt

This line specifies that the operation for the exportE configuration is export elements. The equivalent command line is as follows:

-export elt

Item Description Syntax Requirements

* Indicates the beginning of an operative line. Should be the first character on the line. Spaces before are not allowed and spaces after are optional.

exportAll The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time.

Letters and numbers are allowed.

Spaces are not allowed.

Using a meaningful name is recommended.

_ Separates the configuration name from the command line option or keyword.

Spaces are not allowed before or after.

List A keyword to indicate that a list of other configurations in the file follows.

“L” must be capitalized.

: Separates the keyword from the list of configuration names.

Spaces before and after are optional.

exportE The name of another configuration in the file. Multiple names are allowed and spaces between each name are required.

exportSEL The name of another configuration in the file. Multiple names are allowed and spaces between each name are required.



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

*exportE_colNames: name comment

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

-colNames “name comment”


* Indicates the beginning of an operative line. Should be the first character on the line.

Spaces before are not allowed.

Spaces after are optional.

exportE The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time.




_ Separates the configuration name from the command line option or keyword


operation A keyword to indicate that what follows is an operation.

Should be all lower case.

: Separates the keyword from the operation Spaces before and after are optional.

export The operation, in this case export. Valid values are import, export, and delete.

Spaces are required between the operation and the type of resource should be all lowercase.

elt The type of resource, in this case elements. Any values that are valid on the command line are also valid in a configuration file.

Spaces are required between the operation and the type of resource.

Capitalization must be the same as on the command line.













colNames A command line option. In this case, -colNames. Command line options are listed under Displaying Resource Manager Options on page 24.

No hyphen before the option.

Capitalization needs to be the same as on the command line.

: Separates the command line option from its value. Spaces before and after are optional.

name A column name Can be any valid column name. See Using Column Names on page 27 for the list of possible column names.

Multiple column names are allowed.

Spaces are required between each of the column names in the list.

comment A column name Can be any valid column name. See Using Column Names on page 27 for the list of possible column names.





*exportE_file: elements

This line specifies that the name of the output file is “elements.” The command line equivalent is:

-file elements







Spaces are not allowedusing a meaningful name is recommended.



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



elements The name of the file in which to place the exported data.

Should be only the file name. If a path is required use the dirPath option, as shown on 70.



*exportE_dirPath: ./output

This line specifies that the path for the output file is “./output” The equivalent command line is:

-dirPath “./output”

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

! export all sub-elements with attributes

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

Lines beginning with an exclamation point (!) are comments.

*exportSEL_List: exportSE exportSEM

This line specifies a list of configurations. When exportSEL is specified on the command line for the -config option, all of the configurations listed on the right are executed together.


* Indicates the beginning of an operative line. Should be the first character on the line. Spaces before are not allowed and spaces after are optional.


Letters and numbers are allowed. Spaces are not allowed.


_ Separates the configuration name from the command line option or keyword


dirPath A command line option. In this case, -dirPath. Command line options are listed under Working with resmgr on page 23.




./output The path for the file in which to place the exported data.

Specify only the path. Specify the name of the file with the file option.

The directory needs to exist before executing the command. If the directory does not exist, the command fails.



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

*exportSE_operation: export se

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

-export se





exportSEL The name of the configuration. This is the name that should be specified on the command line with the -config option.

All the lines that begin with this configuration name are run at the same time.






List A keyword to indicate that what follows is a list of other configurations in the file.

“L” must be capitalized.

: Separates the keyword from the list of configuration names.


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

Spaces between each name are required.

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

Spaces between each name are required.





exportSE The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time.








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

operation A keyword to indicate that what follows is an operation. Should be all lower case.

: Separates the keyword from the operation. Spaces before and after are optional.

export The operation, in the case export. Valid values are import, export, and delete.

Spaces are required between the operation and the type of resource must be all lowercase.

se The type of resource, in this case sub-elements. Any values that are valid on the command line are also valid in a configuration file.













colNames A command line option. In this case, -colNames. Command line options are listed in Working with resmgr on page 23.






name A column name Can be any valid column name. See Using Column Names on page 27 for the list of possible column names.



date A column name Can be any valid column name. See Resource Column Names on page 27 for the list of possible column names.





*exportSE_file: subel1

This line specifies that the name of the output file is “subel1.” The equivalent command line is:

-file subel1











file A command line option. In this case, -file. Command line options are listed in Working with resmgr on page 23.




subel1 The name of the file in which to place the exported data.

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



*exportSEM_operation: export se

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

-export subElt

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





exportSEM The name of the configuration. This is the name that should be specified on the command line with the -config option. All the lines that begin with this configuration name are run at the same time.






operation A keyword to indicate that what follows is an operation.

Should be all lower case.

: Separates the keyword from the operation. Spaces before and after are optional.

export The operation, in the case export. Valid values are import, export, and delete.


Needs to be all lowercase.

se The type of resource, in this case sub-elements. Any values that are valid on the command line are also valid in a configuration file.



Item Purpose Syntax Requirements

* Indicates the beginning of an operative line Should be the first character on the line. Spaces before are not allowed and spaces after are optional.



*exportSEM_file: subel2

This line specifies that the name of the output file is “subel2.” The same thing on the command line is:

-file subel2


Letters and numbers are allowed. Spaces are not allowed.




colNames A command line option. In this case, -colNames.

No hyphen before the option. Capitalization must be the same as on the command line.

: Separates the command line option from its value.


name A column name. Can be any valid column name. See Using Column Names on page 27 for the list of column names.



instance A column name. Can be any valid column name. See Using Column Names on page 27 for the list of column names.

Multiple column names are allowed. Spaces are required between each of the column names in the list.













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



subel2 The name of the file in which to place the exported data.

Should be only the file name. If a path is required use the dirPath option, as shown on 70.



NOTES


Chapter 6: Managing Resources

This chapter explains how to use resmgr to manage resources, and is made up of the following topics:

Overview

This chapter explains how to use resmgr to export, import, and manage different Tivoli Netcool Performance Manager object types that belong to the resource category. Resources include the following object types:

• elements

• subelements and subelement groups

• composite subelements

• nomenclature

Before using the commands in this chapter, review the information in Chapter 4, Managing Tivoli Netcool Performance Manager Objects.

Topic Page

Overview 79

Working with Elements 80

Working with Subelements 88

Working with Groups or Rules 95

Working with Nomenclature 107

Using Mandatory Links 110



Working with Elements

This section contains the commands you can use to manage elements. When you use resgmr to work with the elements, you work with the following object types:

• elt

• scf

• eprp

• eproperty

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

• encl

• vendor

• chnl

Exporting Elements

The following examples of resmgr command used to export elements contain the command and the results of that command.

Exporting all elements

resmgr -export elt -colNames "dbIndex name type encl.name state origin profil collector missing comment" -file $DIR/elt_all.dat

# type = elt# col = dbIndex name type encl.name state origin profil collector missing comment# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "dbIndex name type encl.name state origin profil collector missing comment"200000632|_|Delete_200000632_192.168.3.254|_|snmp|_|3Com Hub (SuperStack II PS Hub 40)|_|off|_|inventory|_|Cisco_SAA|_|1|_||_||_|200000788|_|Delete_200000788_192.168.3.37|_|snmp|_|BayStack 350T|_|off|_|inven-tory|_|Cisco_SAA|_|1|_||_||_|100000219|_|development.quallaby.com|_|snmp|_|HP Printer ETHERNET MULTI-ENVIRON-MENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|100000218|_|hpcolor.quallaby.com|_|snmp|_|HP Printer ETHERNET MULTI-ENVIRON-MENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|100000217|_|ps.quallaby.com|_|snmp|_|HP Printer ETHERNET MULTI-ENVIRON-MENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|100000214|_|finance.quallaby.com|_|snmp|_|HP Printer ETHERNET MULTI-ENVIRON-MENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|100000180|_|marketing.quallaby.com|_|snmp|_|HP Printer ETHERNET MULTI-ENVIRON-MENT|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|100000165|_|Delete_100000165_192.168.3.238|_|snmp|_|HP Printer ETHERNET MULTI-ENVI-RONMENT|_|off|_|inventory|_|Cisco_SAA|_|1|_||_||_|100000220|_|192.168.66.2|_|snmp|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO|_|on|_|inventory|_|QuallabyNetwor



k|_|1|_||_||_|100000215|_|dhcp65.quallaby.com|_|snmp|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|100000212|_|echidna.quallaby.com|_|snmp|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO|_|on|_|inventory|_|QuallabyNetwork|_|1|_||_||_|

Exporting elements with their properties

resmgr -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|_|physAd-dress|_|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|_|physAd-dress|_|6.0.48.25.95.152.192|_|sysDescr|_|Cisco Internetwork 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|_|physAd-dress|_|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|_|physAd-dress|_|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|_|physAd-dress|_|6.0.208.0.56.43.255|_|sysDescr|_|Cisco Systems WS-C65 09\nCisco Catalyst Operating System Software, Version 5.3(2|_|sysName|_|""|_|192.168.127.2|_|ipAddress|_|192.168.127.2|_|ipAddressMin|_|192.168.127.2|_|ipName|_|192.168.127.2|_|physAddress|_|6.0.48.25.88.220.0|_|s ysDescr|_|Cisco Internetwork Operating System Software \nIOS (tm) C3500XL Software (C3500|_|sysName|_|"PS-LAB"|_|

Exporting elements with sysName, ipAddress, and physAddress

resmgr -export elt -colNames "name eprp.sysName:value eprp.ipAddress:value eprp.physAddress:value" -file $DIR/elt_inv.dat

# type = elt# col = name eprp.sysName:value eprp.ipAddress:value eprp.physAddress:value# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name eprp.sysName:value eprp.ipAddress:value eprp.physAddress:value"



172.31.0.51|_|"c7204-51-LER.ap-lab.quall-aby.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-SpecificElec-tric|_|0.0.0.0|_|NF-site-site-flow-Gold-SpecificElectric|_|NF-site-iphost-flow-SpecificElectric|_|NF-site-iphost-flow-SpecificElec-tric|_|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.quall-aby.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 information

resmgr -export elt -colNames "name encl.name encl.oid encl.gpname vendor.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.oid encl.gpname vendor.name"Delete_100000174_192.168.2.2|_|Cisco C2600-I|_|1.3.6.1.4.1.9.1.209|_|Cisco|_|Cisco|_|192.168.1.3|_|Cisco C2600-D|_|1.3.6.1.4.1.9.1.208|_|Cisco|_|Cisco|_|192.168.68.162|_|Cisco 1600|_|1.3.6.1.4.1.9.1.172|_|Cisco|_|Cisco|_|172.31.1.2|_|Cisco 1600|_|1.3.6.1.4.1.9.1.172|_|Cisco|_|Cisco|_|Delete_100001732_172.17.100.254|_|Cisco 1600|_|1.3.6.1.4.1.9.1.172|_|Cisco|_|Cisco|_|172.31.0.31|_|Cisco 2611|_|1.3.6.1.4.1.9.1.186|_|Cisco|_|Cisco|_|Delete_100000176_192.168.3.253|_|Cisco 2611|_|1.3.6.1.4.1.9.1.186|_|Cisco|_|Cisco|_|172.31.0.41|_|Cisco 2610|_|1.3.6.1.4.1.9.1.185|_|Cisco|_|Cisco|_|192.168.64.253|_|Cisco 3660|_|1.3.6.1.4.1.9.1.205|_|Cisco|_|Cisco|_|Delete_100001733_172.17.100.253|_|Cisco 7206 VXR|_|1.3.6.1.4.1.9.1.222|_|Cisco|_|Cisco|_|172.31.0.51|_|Cisco 7204 VXR|_|1.3.6.1.4.1.9.1.223|_|Cisco|_|Cisco|_|dhcp195.quallaby.com|_|Cisco 7204 VXR|_|1.3.6.1.4.1.9.1.223|_|Cisco|_|Cisco|_|192.168.66.2|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEM-PRO|_|1.3.6.1.4.1.311.1.1.3.1.2|_|Compaq|_|Microsoft|_|dhcp65.quallaby.com|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO|_|1.3.6.1.4.1.311.1.1.3.1.2|_|Compaq|_|Microsoft|_|



Exporting elements with collection information

resmgr -export elt -colNames "name collector chnl.host chnl.instDir chnl.type" -file $DIR/elt_chnl.dat

# type = elt# col = name collector chnl.host chnl.instDir chnl.type# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name collector chnl.host chnl.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 information

resmgr -export elt -isMandat scf -colNames "name scf.rcommunity scf.timeout scf.retries scf.version scf.colNb" -file $DIR/elt_scf.dat

# type = elt# col = name scf.rcommunity scf.timeout scf.retries scf.version scf.colNb# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name scf.rcommunity scf.timeout scf.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 collector

resmgr -export scf -colNames "colNb type ipaddress eltIdx version bandwidth retries timeout wcommunity port rcommunity"

# type = scf# col = colNb type ipaddress eltIdx version bandwidth retries timeout wcommunity port rcommunity# filter =# order =# sep = |_|# sepRec =# rule = # filterRule =



## cmdLine = -export scf -colNames "colNb type ipaddress eltIdx version bandwidth retries timeout wcommunity port rcommunity"0|_|default_snmp|_|*.*.*.*|_|5|_||_||_|3|_|2|_|private|_|161|_|public|_|

Exporting element state and comment information

resmgr -export elt -colNames "name state comment"

# resmgr -export elt -colNames "name state comment"# type = elt# col = name state comment# filter = # order = # sep = |_|# sepRec = # rule = # filterRule = ## cmdLine = -export elt -colNames "name state comment" default|_|on|_||_|DL.1|_|on|_|PROVISO_MONITORING|_|10.127.78.2-1|_|on|_||_|10.127.78.3-1|_|on|_||_|10.127.77.7|_|on|_||_|10.127.77.6|_|on|_||_|

Importing Elements

You must use the name column for a new element. By default, dbIndex is taken from the resourceSequences column, nclIdx is null , and the comment and profil columns are empty.

You can also include the following columns:

• encl.name ( populate nclIdx )

• profil

• collector

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

Creating a new or updating an existing element

Input File:

add_elt1|_|3Com Hub (SuperStack II PS Hub 40)|_|profil1|_|1|_|"element1"|_|172.31.128.51|_|6.0.4.109.221.236.0|_|

add_elt2|_|3Com Hub (SuperStack II PS Hub 40)|_|profil1|_|1|_|"element2"|_|172.31.128.41|_|6.0.48.25.95.152.192|_|

resmgr -import elt -colNames "name encl.name profil collector eprp.sysName:value eprp.ipAddress:value eprp.physAddress:value" -file test1

Info : === insert : INSERT ON Element ( add_elt1 ) (does not exist)Info : === insert : nothing ON property ( sysName ) (exists)Info : === insert : nothing ON property ( ipAddress ) (exists)Info : === insert : nothing ON property ( physAddress ) (exists)



Info : === insert : INSERT ON elt property ( add_elt1 sysName ) (does not exist)Info : === insert : INSERT ON elt property ( add_elt1 ipAddress ) (does not exist)Info : === insert : INSERT ON elt property ( add_elt1 physAddress ) (does not exist)Info : === insert : INSERT ON Element ( add_elt2 ) (does not exist)Info : === insert : nothing ON property ( sysName ) (exists)Info : === insert : nothing ON property ( ipAddress ) (exists)Info : === insert : nothing ON property ( physAddress ) (exists)Info : === insert : INSERT ON elt property ( add_elt2 sysName ) (does not exist)Info : === insert : INSERT ON elt property ( add_elt2 ipAddress ) (does not exist)Info : === insert : INSERT ON elt property ( add_elt2 physAddress ) (does not exist)Title : === CHANGES : {2 New of elt}Info : === Inform Collector On hebus:3002

Creating or updating existing elements and list of properties

Input File:

192.168.69.243|_|Cisco Catalyst 5000|_|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"|_|


resmgr -import elt -colNames "name encl.name profil collector eprp.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-existent element (nothing is inserted)

You can use this command when you need to just update an existing property without creating a new one, for example in inventory.

Input File:

NOTEXIST_192.168.69.243|_|Cisco Catalyst 5000|_|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"|_|


resmgr -import eproperty -colNames "name encl.name profil collector eprp.name eprp.value" -file test1

Info : === insert : nothing ON property ( ipAddress ) (exists)Info : === insert : nothing ON property ( ipName ) (exists)Info : === insert : nothing ON property ( physAddress ) (exists)Info : === insert : nothing ON property ( sysDescr ) (exists)Info : === insert : nothing ON property ( sysName ) (exists)Info : === insert : nothing ON elt property (Depend not exist) eprp DInfo : === insert : nothing ON elt property (Depend not exist) eprp DInfo : === insert : nothing ON elt property (Depend not exist) eprp DInfo : === insert : nothing ON elt property (Depend not exist) eprp DInfo : === insert : nothing ON elt property (Depend not exist) eprp DInfo : === 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 collector

resmgr -import scf -colNames "colNb type ipaddress eltIdx version bandwidth retries timeout wcommunity port rcommunity" -import_source

Where import_source Specifies the source of the values that are to be imported to the collector. The import source can include the following:



• -file filename : Imports values from the specified file.

• -line “value1|_|value2|_|value3” : Imports the specified values directly from the command line.

Deleting Elements

You must use the dbIndex or name columns when deleting elements.

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

Deleting elements

resmgr -delete elt -colNames "nop nop dbIndex" -file test1

Info : === delete : DELETE ON Element ( NOTEXIST_192.168.69.243 ) (exists)Title : === CHANGES : {1 Deleted of elt}Info : === Inform Collector On hebus:3002

Delete a config snmp (without deleting the element)

resmgr -delete snmpConf -colNames "name" -line "network1"

Info : === delete : DELETE ON config SNMP ( 192.168.64.* ) (exists)

Deleting element properties (without deleting the element)

resmgr -delete eproperty -colNames "name eprp.name" -line "add_elt2|_|ContactElt|_|"

Info : === delete : DELETE ON elt property ( add_elt2 ContactElt ) (exists)



Working with Subelements

This section contains the commands you can use to manage subelements. When you work with subelement object types, you work with the following:

• se

• seprp

• seproperty

• cse


• fam

• elt

Exporting Subelements

The following example of exporting subelements includes the command and the command output.

Exporting subelements with their properties

resmgr -export se -colNames "dbIndex invariant elt.name name label instance 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 origin date_DATE fam.name seprp.name seprp.value# filter =# order =# sep = |_|# sepRec =## cmdLine = -export se -colNames "dbIndex invariant elt.name name label instance state origin date_DATE fam.name seprp.name seprp.value"

200003278|_|Cus-tomer<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/2003 02:28|_|2233_IF|_|name|_|"0"|_|physicalCapacity|_|100000000|_|sta-tus|_|up|_|If|_|101|_|siteID|_|IP:192.168.69.245ifIndex:101|_|location|_|"QALAB"|_|type|_|ethernetCsmacd|_|200003279|_|Cus-tomer<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/2003 02:28|_|2233_IF|_|name|_|"0"|_|siteID|_|IP:192.168.69.245ifIndex:100|_|If|_|100|_|physicalCapacity|_|100000000|_|status|_|up|_|location|_|"QALAB"|_|type|_|ethernetCsmacd|_|200003280|_|Cus-tomer<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/2003 02:28|_|2233_IF|_|name|_|"0"|_|siteID|_|IP:192.168.69.243ifIndex:100|_|If|_|100|_|customer|_|C1|_|physicalCapacity|_|10000000



0|_|status|_|up|_|location|_|"QALAB"|_|type|_|ethernetCsmacd|_|customer1|_|C4|_|200003446|_||_|Delete_200000133_pl2col6|_|Delete_200000831_pl2col6_DataChannel<dber>|_|Delete_200000831_pl2col6_DataChannel<dber>|_|Delete_200000831_DataChannel<dber>|_|on|_|resmgr|_|10/13/2003 14:52|_||_|200003448|_||_|dber|_|SE_dber|_|SE_dber|_|<NULL>|_|on|_|resmgr|_|10/13/2003 14:54|_||_|200003449|_||_|dber|_|SE_dber1|_|SE_dber1|_|<NULL1>|_|on|_|resmgr|_|10/13/2003 16:03|_|fam1|_|

Exporting composite subelements

resmgr -export cse -colNames "dbIndex name type invariant data comment dataType defValue originr" -file cseDesc.rmg

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

Exporting composite subelements with composite link

resmgr -export cse -colNames "name cse.name cse.coname"

# type = cse# col = name cse.name cse.coname# filter = # order = # sep = |_|# sepRec = # rule = # filterRule = ## cmdLine = -export cse -colNames "name cse.name cse.coname" Path From: label24078_145_29278 To: label26672_145_29277|_|qcf5620_remote|_|label26672_145_29277|_|Path From: label14263_145_29279 To: label34389_145_29280|_|qcf5620_local|_|label14263_145_29279|_|Path From: label34389_145_29280 To: label14263_145_29279|_|qcf5620_remote|_|label14263_145_29279|_|Path From: label10209_145_29290 To: label20854_145_29289|_|qcf5620_remote|_|label20854_145_29289|_|Path From: label31552_145_19020 To: label38212_145_19019|_|qcf5620_remote|_|label38212_145_19019|_|



Path From: label26699_145_19021 To: label17079_145_19022|_|qcf5620_local|_|label26699_145_19021|_|Path From: label32752_145_19023 To: label11719_145_19024|_|qcf5620_local|_|label32752_145_19023|_|Path From: label11719_145_19024 To: label32752_145_19023|_|qcf5620_remote|_|label32752_145_19023|_|Path From: label2413_145_19025 To: label13948_145_19026|_|qcf5620_local|_|label2413_145_19025|_|Path From: label13948_145_19026 To: label2413_145_19025|_|qcf5620_remote|_|label2413_145_19025|_|

Exporting subelement state and ulabel information

resmgr -export se -colNames "name state ulabel"

$ resmgr -export se -colNames "name state ulabel"# type = se# col = name state ulabel# 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 Subelements

You must use the following columns when importing new subelements:

• name

• hostIdx or elt.name

• instance

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




• fam.name ( populate nclIdx )

• label

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

Input File:

192.168.69.243_If<100>|_|2233_IF|_|192.168.69.243_IF: 100 ("0") (100Mbps)|_|192.168.69.243|_|If<100>|_|conctact A1|_|"

resmgr -import se -colNames "name fam.name label elt.name instance seprp.Contact: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 ( Contact ) (exists)Info : === insert : INSERT ON subElt property ( Contact conctact A1 ) (does not exist)Title : === CHANGES : {1 Updated of se}Info : === Inform Collector On hebus:3002

Creating new or updating existing subelement and list of properties

Input File:

192.168.69.243_If<100>|_|2233_IF|_|192.168.69.243_IF: 100 ("0") (100Mbps)|_|192.168.69.243|_|If<100>|_|name|_|"0"|_|type|_|ethernetCsmacd|_|location|_|"QALAB"|_|status|_|up|_|physicalCapacity|_|100000000|_|If|_|100|_|customer1|_|C4|_|Contact|_|conctact A1|_|siteID|_|IP:192.168.69.243ifIndex:100|_|customer|_|C1|_|

192.168.69.243_If<101>|_|2233_IF|_|192.168.69.243_IF: 101 ("0") (100Mbps)|_|192.168.69.243|_|If<101>|_|name|_|"0"|_|type|_|ethernetCsmacd|_|location|_|"QALAB"|_|physicalCapacity|_|100000000|_|customer1|_|C3|_|siteID|_|IP:192.168.69.243ifIndex:101|_|If|_|101|_|customer|_|C2|_|status|_|up|_|customer|_|C1|_|

resmgr -import se -colNames "name fam.name label elt.name instance seprp.name seprp.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 subElt property ( name "0" ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( type ether-netCsmacd ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( location "QALAB" ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( status up ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( physicalCa-pacity 100000000 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( If 100 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( customer1 C4 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( Contact conctact A1 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( siteID IP:192.168.69.243ifIndex:100 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( customer C1 ) (exists)Info : === insert : nothing ON Element ( 192.168.69.243 ) (exists)Info : === insert : nothing ON nomenclature1 ( 2233_IF ) (exists)Info : === insert : UPDATE ON Sub-Element ( 192.168.69.243_If<101> ) (exists)Info : === insert : nothing ON property ( name ) (exists)Info : === insert : nothing ON property ( type ) (exists)Info : === insert : nothing ON property ( location ) (exists)Info : === insert : nothing ON property ( physicalCapacity ) (exists)Info : === insert : nothing ON property ( customer1 ) (exists)Info : === insert : nothing ON property ( siteID ) (exists)Info : === insert : nothing ON property ( If ) (exists)Info : === insert : nothing ON property ( customer ) (exists)Info : === insert : nothing ON property ( status ) (exists)Info : === insert : nothing ON property ( customer ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( name "0" ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( type ether-netCsmacd ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( location "QALAB" ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( physicalCa-pacity 100000000 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( customer1 C3 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( siteID IP:192.168.69.243ifIndex:101 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( If 101 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( customer C2 ) (exists)Info : === insert : nothing to do (update stopped) ON subElt property ( status up ) (exists)Info : === insert : UPDATE ON subElt property ( customer C1 ) (exists)Title : === CHANGES : {2 Updated of se}Info : === Inform Collector On hebus:3002



Creating or updating a list of properties without creating a non-existent sub-element (nothing is inserted)

resmgr -import seproperty -colNames "name fam.name label elt.name instance 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:value seprp.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 conctact A1 ) (exists)

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

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

If there is no change in the no history table (for property,) no updates are made. Use "IFirst,forced" mode to force the insert into the history table, even if there is no change in the seprp table.

Importing a composite subelement

resmgr -import cse -colNames "name invariant" -line "relation1|_|type<SE>|_|"

Info : === insert : INSERT ON property ( relation1 ) (does not exist)

Importing composite subelements

resmgr -import secse -colNames "name cse.name cse.coname" -line "Path From: label27077_145_15510 To: label3989_145_15509|_|qcf5620_remote|_|label3989_145_15509|_|"

Info : === insert : nothing ON property ( qcf5620_remote ) (exists) Info : === insert : INSERT ON composite ( Path From: label27077_145_15510 To:

label3989_145_15509 qcf5620_remote label3989_145_15509 ) (does not exist)



Deleting Subelements

You must use the dbIndex or name columns; or elt.name plus instance.


Deleting subelements

resmgr -delete se -colNames "dbIndex" -line 200003446

Info : === delete : DELETE ON Sub-Element ( Delete_200000831_pl2col6_DataChannel<dber> ) (exists)Title : === CHANGES : {1 Deleted of se}Info : === Inform Collector On hebus:3002

Deleting subelement properties (without deleting the subelement)

resmgr -delete seproperty -colNames "name seprp.name" -line "bulk100-boston_1000,19_Interface<10>|_|type|_|"

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

or if you have the index

resmgr -delete seprp -colNames "seIdx nop prpIdx" -line "200001183|_|bulk100-boston_1000,17_Interface<8>|_|1732|_|physicalCapacity|_|0|_|"

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

Deleting composite subelements

resmgr -delete cse -colNames "name" -line relation1

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

Deleting composite subelements with composite link

resmgr -delete secse -colNames "name cse.name cse.coname" -line "Path From: label27077_145_15510 To: label3989_145_15509|_|qcf5620_remote|_|label3989_145_15509|_|"

Info : === delete : DELETE ON composite ( Path From: label27077_145_15510 To: label3989_145_15509 qcf5620_remote label3989_145_15509 ) (exists)



Working with Groups or Rules

This section contains the commands you can use to manage groups or rules. When you use resgmr to work with the elements, you work with the following object types:

• egp

• segp

Subelement Group Links

Links can exist among subelement groups and the following Tivoli Netcool Performance Manager object types:

• se

• app

• rusr

• tz

• cal

• segparent

• segchild

• linkGroupSE

• linkGroupSE_APP

• linkGroupSE_RU

• linkGroupSE_TZC



Exporting Groups and Rules

The only difference between the export of the groups and the rule is the filter used.

Exporting subelement groups with a group label

resmgr -export segp -colNames "name label" -filter "label(Customer*)" -file groups.txt

# type = segp# col = dbIndex name label# filter = label(PMG*)# order =# sep = |_|# sepRec =# rule =# filterRule =## cmdLine = -export segp -colNames "dbIndex name label" -filter "label(PMG*)"200017652|_|GPR0001|_|PMG Grouping|_|-export segp -colNames "dbIndex name label" -filter "label(PMG*)"200017652|_|GPR0001|_|PMG Grouping|_|

Exporting subelement groups created by rules

resmgr -export segp -colNames "npath name type cond state origin date" -order "dbIndex" -filter "type(!=’rule’) origin(=’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 state origin date" -filter "type(!=’rule’) origin(=’inventory’)"~NOC Reporting~Cisco SAA~Per Operation (raw)~Jit-ter~172.17.105.254|_|172.17.105.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Hourly Aggregate~Com-mon~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|_|inven-tory|_|1025288162|_|~NOC Reporting~Cisco SAA~Hourly Aggregate~Jit-ter~172.17.100.253|_|172.17.100.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Hourly Aggregate~Com-mon~172.17.100.254|_|172.17.100.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Hourly Aggregate~Jit-ter~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|_|inven-tory|_|1025288162|_|~NOC Reporting~Cisco SAA~Hourly Aggregate~Com-mon~192.168.64.253|_|192.168.64.253|_|generated|_||_|on|_|inventory|_|1025288162|_|



~NOC Reporting~Cisco SAA~Hourly Aggregate~Jit-ter~192.168.64.253|_|192.168.64.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Router~Interfaces~Location: "AP Lab, Lowell MA US"~172.17.100.254|_|172.17.100.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Per Operation (raw)~Com-mon~192.168.68.162|_|192.168.68.162|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Hourly Aggregate~Com-mon~172.17.105.254|_|172.17.105.254|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Per Operation (raw)~Jit-ter~192.168.68.162|_|192.168.68.162|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Cisco SAA~Hourly Aggregate~Jit-ter~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)~Com-mon~172.17.100.253|_|172.17.100.253|_|generated|_||_|on|_|inventory|_|1025288162|_|~NOC Reporting~Customization Group~Coca-Cola|_|Coca-Cola|_|static|_|%(customer) = ’Coca-Cola’|_|on|_|inventory|_|1018389887|_|~NOC Reporting~Cisco SAA~Per Operation (raw)~Com-mon~172.17.105.254|_|172.17.105.254|_|generated|_||_|on|_|inventory|_|1025289790|_|

Exporting subelement groups that are rules

resmgr -export segp -colNames "npath name type cond state origin date" -order "dbIndex" -filterRule "(%(type) = ’rule’ OR %(cond) is not null)" -file $DIR/segp_rule.dat

# type = segp# col = npath name type cond state origin date# filter = # order = dbIndex# sep = |_|# sepRec = ## cmdLine = -export segp -colNames "npath name type cond state origin date" ~NOC Reporting|_|NOC Reporting|_|static|_|%(Element.STATE)=’on’ AND %(STATE)=’on’|_|on|_|APinstall|_|983650594|_|~Sub-Element Collect|_|Sub-Element Collect|_|static|_|%(Element.STATE)=’on’ AND %(STATE)=’on’|_|on|_|APinstall|_|997993108|_|~NOC Reporting~IPSec|_|IPSec|_|static|_|%(FAMILY)=’Cisco_IPSec’|_|on|_|APin-stall|_|997993109|_|~NOC Reporting~IPSec~Phase-1|_|Phase-1|_|static|_|%(FAM-ILY)=’Cisco_IPSec’|_|on|_|APinstall|_|997993109|_|~NOC Reporting~IPSec~Phase-2|_|Phase-2|_|static|_|%(FAM-ILY)=’Cisco_IPSec’|_|on|_|APinstall|_|997993109|_|~NOC Reporting~IPSec~Phase-1~%(customer)|_|%(customer)|_|rule|_||_|on|_|APin-stall|_|993737950|_|~NOC Reporting~IPSec~Phase-2~%(customer)|_|%(customer)|_|rule|_||_|on|_|APin-stall|_|999637172|_|~Sub-Element Collect~IPSec~Cisco|_|Cisco|_|static|_|%(FAM-ILY)=’Cisco_IPSec’|_|on|_|APinstall|_|999642720|_|~NOC Reporting~IPSec~Phase-1~%(customer)~%(privateNetworkID)|_|%(privateNet-workID)|_|rule|_||_|on|_|APinstall|_|983650594|_|~NOC Reporting~IPSec~Phase-2~%(customer)~%(privateNetworkID)|_|%(privateNet-workID)|_|rule|_||_|on|_|APinstall|_|983650594|_|~Sub-Element Collect~Frame Relay~DLC~Cascade (Lucent)|_|Cascade (Lucent)|_|static|_|%(FAMILY) LIKE ’Cascade_FR_DLC%’|_|on|_|APin-stall|_|999787597|_|



~Sub-Element Collect~Frame Relay~DLC~Cisco 11.2F+|_|Cisco 11.2F+|_|static|_|%(FAM-ILY) 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|_|Cisco 11.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|_|APin-stall|_|999642515|_|~NOC Reporting~Router~Interfaces~Location: %(location)|_|Location: %(loca-tion)|_|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: %(loca-tion)|_|rule|_||_|on|_|APinstall|_|999641730|_|~Sub-Element Collect~Router~Interfaces|_|Interfaces|_|static|_|%(FAMILY) LIKE ’%_IF’|_|on|_|APinstall|_|997993110|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|Cisco 11.x|_|static|_|%(Ele-ment.VENDOR)= ’Cisco’|_|on|_|APinstall|_|1013400292|_|

Exporting subelement groups that are leaf, active rules

resmgr -export segp -colNames "dbIndex name type cond state origin date" -order "dbIndex" -filterRule "(%(type) = ’rule’ OR %(cond) is not null)" -filter "state(on) segchild.name(is null)" -file $DIR/segp_leafrule.dat

# type = segp# col = dbIndex name type cond state origin date# filter = state(on) segchild.name(is null)# order = dbIndex# sep = |_|# sepRec = ## cmdLine = -export segp -colNames "dbIndex name type cond state origin date" -fil-ter "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|_|APin-stall|_|999787597|_|4303|_|Cisco 11.2F+|_|static|_|%(FAMILY) LIKE ’Cisco_FR_DLC%’|_|on|_|APin-stall|_|1021329701|_|4308|_|Cisco 11.x|_|static|_|%(FAMILY) LIKE ’Cisco%Router%Device%’|_|on|_|APin-stall|_|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|_|APin-stall|_|1004367506|_|4940|_|HTTP|_|static|_|%(FAMILY) = ’RTTMon_HTTP_Probe’|_|on|_|APin-stall|_|1004367506|_|4941|_|Jitter|_|static|_|%(FAMILY) = ’RTTMon_Jitter_Probe’|_|on|_|APin-stall|_|1004367506|_|5137|_|%(Element.NAME)|_|rule|_||_|on|_|APinstall|_|994198030|_|5141|_|%(Element.NAME)|_|rule|_||_|on|_|APinstall|_|994198030|_|5142|_|If: %(parent)|_|rule|_||_|on|_|APinstall|_|999637193|_|5144|_|Juniper|_|static|_|%(Element.VENDOR)= ’Juniper Networks’|_|on|_|APin-stall|_|999641985|_|5146|_|Juniper|_|static|_|%(FAMILY)=’Juniper_Chassis’|_|on|_|APin-stall|_|999617814|_|5148|_|Juniper|_|static|_|%(FAMILY)=’Juniper_DCU’|_|on|_|APinstall|_|1004723965|_|5150|_|Juniper|_|static|_|%(FAMILY)=’Juniper_Firewall’|_|on|_|APin-stall|_|998661334|_|5153|_|Juniper|_|static|_|%(FAMILY)=’Juniper_MPLS_LSP’|_|on|_|APin-stall|_|999617814|_|5246|_|Unisphere ERX Devices|_|static|_|%(FAMILY) = ’1213_Device’ AND %(Element.VEN-DOR) = ’Unisphere’|_|on|_|APinstall|_|1022018055|_|

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

Exporting subelement groups

resmgr -export segp -colNames "npath se.name" -file $DIR/segp_se.dat

# type = segp# col = npath se.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export segp -colNames "npath se.name"~Partner Section~Juniper~Virtual Router~IP Inter-faces~default~10.8.7.18|_|192.168.127.2_If<23>|_|~NOC Reporting~Network Management~By loca-tion~"Catalyst_PS_Lab"|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~By Customer and Location~Bristol-Myers Squibb by loca-tion~"Catalyst_PS_Lab"|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~WCOM Test group~Headquarters~Loreal~Bordeaux~test value2|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~By Customer and CoS~Loreal CoS~Gold|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~By Customer and VPN~Loreal VPN~Headquar-ters|_|192.168.127.2_If<23>|_|~NOC Reporting~IP VPN~By Class of Service~Gold|_|192.168.127.2_If<23>|_|~NOC Reporting~IP VPN~By City~Bordeaux|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~By CoS~Gold|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~By CoS~Standard|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~By Customer and Cos~Bristol-Myers Squibb by CoS~Stan-dard|_|192.168.127.2_If<23>|_|



~NOC Reporting~Network Management~By CoS~Standard|_|192.168.127.2_If<23>|_|~NOC Reporting~All Technologies~High Speed Interfaces (>=100Mbps)~ethernetCs-macd|_|192.168.127.2_If<23>|_|~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps)~ethernetCs-macd|_|192.168.127.2_If<23>|_|~Sub-Element Collect~RFC-1213~Interfaces~Frequent|_|192.168.127.2_If<23>|_|

Exporting report user groups

resmgr -export segp -colNames "npath rusr.name" -file $DIR/segp_rusr.dat

# type = segp# col = npath rusr.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export segp -colNames "npath rusr.name"~NOC Reporting|_|SSSW\\jtho|_|~NOC Reporting|_|SSSW\\quallaby|_|~NOC Reporting|_|SSSW\\adminfcar|_|~NOC Reporting|_|SSSW\\nate|_|~PROVISO System Monitoring|_|SSSW\\adminfcar|_|~PROVISO System Monitoring|_|SSSW\\nate|_|~Customer Facing Reporting|_|SSSW\\jtho|_|~Customer Facing Reporting|_|SSSW\\business|_|~Customer Facing Reporting|_|SSSW\\cisco|_|~Customer Facing Reporting|_|SSSW\\adminfcar|_|~Customer Facing Reporting|_|SSSW\\nate|_|~Partner Section|_|SSSW\\jtho|_|~Partner Section|_|SSSW\\business|_|~Partner Section|_|SSSW\\adminfcar|_|~Partner Section|_|SSSW\\nate|_|

Exporting application groups with app

resmgr -export segp -colNames "npath app.name" -file $DIR/segp_app.dat

# type = segp# col = npath app.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export segp -colNames "npath app.name"~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~mplsTunnel|_|Inter-face 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)~softwareLoop-back|_|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)~propVir-tual|_|Interface Volume Resource|_|~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~propPointToPointSe-rial|_|Interface Volume Resource|_|~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~frameRelay|_|Inter-face Volume Resource|_|~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~ethernetCs-macd|_|Interface Volume Resource|_|~NOC Reporting~All Technologies~Low Speed Interfaces (<100Mbps)~ds1|_|Interface Vol-ume 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)~softwareLoop-back|_|Interface Volume Resource|_|~NOC Reporting~All Technologies~High Speed Interfaces (>=100Mbps)~propVir-tual|_|Interface Volume Resource|_|

Exporting subelement groups with timezones

You use the option filter tzdate(%NOW) in the command because the Calendar table is actually a history table. If you just need to see the line valid for “now,” you use this 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~Lindt VPN|_|EST_2003|_|4 AM to 8 PM restricted SLA|_|

Importing Groups and Rules

You must use the following columns when importing new groups:

• npath

• type

• rule if type=generated

And the following columns when importing new rules:

• npath



• cond

• type = rule

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

The following table lists the commands

Import Command

Insert or update group

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

Insert group if it does not exist and link subelement to it

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

Link subelement to group only if the group exists

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

Insert group if it does not already exist and link report to it

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

Link report to group only if the group exists

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

Insert group if it does not exist and link report user to it

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

Link report user to group only if group exists

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

Insert group if it does not exist and link timezone to it

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

Link timezone to group only if group exists

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



Inserting or updating groups

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

Info : === insert : INSERT ON Sub-Elt Group ( ~NOC Reporting~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 it

resmgr -import segp -colNames "npath se.name " -line "~NOC Reporting~CustomerA|_|192.168.69.243_If<100>|_|"

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

Linking subelements to group only if group exists

resmgr -import linkGroupSE -colNames "npath se.name " -line "~NOC Reporting~CustomerC|_|192.168.69.243_If<100>|_|"

Error : === insert : INSERT ON Link SE/G ( 192.168.69.243_If<100> CustomerC ) (does not exist) (error I 200003280 301 {ORA-01400: cannot insert NULL into ("PV_ADMIN"."SE_GRP_MEMBER"."IDX_GROUP") })

Info : === Update Histo : 0

Inserting group if non-existent and linking reports to it

resmgr -import segp -colNames "npath app.name " -line "~NOC Reporting~CustomerA|_|Top N AS Details|_|"

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

Linking report to group only if group exists

resmgr -import linkGroupSE_APP -colNames "npath app.name" -line "~NOC Reporting~CustomerB|_|Top N AS Details|_|"

Info : === insert : INSERT ON Link App/SEGroup ( Top N AS Details CustomerB ) (does not exist)Info : === Update Histo : 0



Inserting group if non-existent and linking report user to it

resmgr -import segp -colNames "npath rusr.name" -line "~NOC Reporting~CustomerA|_|SSSW\\customer2|_|"

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

Linking report user to group only if group exists

resmgr -import linkGroupSE_RU -colNames "npath rusr.name" -line "~NOC Reporting~CustomerB|_|SSSW\\customer2|_|"

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

Inserting group if non-existent and linking timezone to it

resmgr -import segp -colNames "npath cal.name tz.name" -line "~NOC Reporting~TestInsertTZC|_|CME Permanent|_|GMT|_|"

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

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


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

Info : === Inform Collector On hebus:3002

Linking timezone to group only if group exists

resmgr -import linkGroupSE_TZC -colNames "npath cal.name tz.name" -line "~NOC Reporting~TestInsertTZCBis|_|CME Permanent|_|GMT|_|"

Error : === insert : nothing ON Link SEGP/TZ (no enough info) (error select ORA-00936: missing expression)


Deleting


The following table lists deletion commands:



Deleting a group

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

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

Unlinking sub-elements

resmgr -delete linkGroupSE -colNames "npath se.name" -line "~NOC Reporting~CustomerB|_|192.168.69.243_If<100>|_|"

Info : === delete : DELETE ON Link SE/G ( 192.168.69.243_If<100> CustomerB ) (exists)Info : === Update Histo : 0Title : === CHANGES : {1 Deleted of se}Info : === Inform Collector On hebus:3002

Unlinking reports

resmgr -delete linkGroupSE_APP -colNames "npath app.name" -line "~NOC Reporting~CustomerB|_|Top N AS Details|_|"

Info : === delete : DELETE ON Link App/SEGroup ( Top N AS Details CustomerB ) (exists)Info : === Update Histo : 0

Unlinking report users

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

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

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"



Unlinking timezones

resmgr -delete linkGroupSE_TZC -colNames "npath cal.name tz.name" -line "~NOC Reporting~TestInsertTZC|_|CME Permanent|_|GMT|_|"

Info : === delete : DELETE ON Link SEGP/TZ ( GMT CME Permanent ) (exists)Info : === Update Histo : 0



Working with Composite Subelement Rules

Exporting composite subelement (CSE) rules is a two-stage process that must result in two separate files being generated to be complete. You must always enter the rule definitions command before the rule relations command. Only the options in this section are supported.

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

Exporting composite subelement rules

• rule definitions

resmgr -export rulegp -colNames "dbIndex name type targetName label cond ruleprp.name ruleprp.command ruleprp.value" -file rulesD.export.dat

• rule relations

resmgr -export rulegp -colNames "lgParent lgChild relType relName relCond" -file rulesL.export.dat

Importing or updating composite subelement rules

• rule definitions

resmgr -import rulegp -colNames "dbIndex name type targetName label cond ruleprp.name ruleprp.command ruleprp.value" -file rulesD.import.dat

• rule relations

resmgr -import rulegp -colNames "lgParent lgChild relType relName relCond" -file rulesL.import.dat

Deleting composite subelement rules

• find the dbIndex of the rule you wish to delete (by inspecting an export file), and use this command to delete the rule.

resmgr -delete rulegp -colNames "dbIndex" -line "1234567890|_|"

Working with Nomenclature

This section contains the commands you can use to manage nomenclature. When you use resgmr to work with the nomenclature, you work with the following object types:

• ngp

• ncl


• vendor



• linkGroupN

Exporting Nomenclature

Exporting all of the nomclature

resmgr -export ncl -colNames "name oid type" -file $DIR/ncl.dat

# type = ncl# col = name oid type# filter =# order =# sep = |_|# sepRec =## cmdLine = -export ncl -colNames "name oid type"Proteon|_|1.3.6.1.4.1.1|_|Vendor|_|IBM|_|1.3.6.1.4.1.2|_|Vendor|_|CMU|_|1.3.6.1.4.1.3|_|Vendor|_|Unix|_|1.3.6.1.4.1.4|_|Vendor|_|Cisco|_|1.3.6.1.4.1.9|_|Vendor|_|NSC|_|1.3.6.1.4.1.10|_|Vendor|_|Hewlett Packard|_|1.3.6.1.4.1.11|_|Vendor|_|Epilogue|_|1.3.6.1.4.1.12|_|Vendor|_|U of Tennessee|_|1.3.6.1.4.1.13|_|Vendor|_|BBN|_|1.3.6.1.4.1.14|_|Vendor|_|Xylogics, Inc.|_|1.3.6.1.4.1.15|_|Vendor|_|Timeplex|_|1.3.6.1.4.1.16|_|Vendor|_|BayStack 450-24T|_|1.3.6.1.4.1.45.3.35.1|_|SysObjectID|_|Hewlett-Packard ENTRIA Model C3262A Server|_|1.3.6.1.4.1.11.2.3.9.3.2.3.2.67.51.50.54.50.65|_|SysObjectID|_|Hewlett-Packard ENTRIA Model C3264A Server|_|1.3.6.1.4.1.11.2.3.9.3.2.3.2.67.51.50.54.52.65|_|SysObjectID|_|Bay Networks Ethernet Chassis NMM 2813|_|1.3.6.1.4.1.45.3.12.1|_|SysObjectID|_|Cabletron SEHI|_|1.3.6.1.4.1.52.3.9.3.4.11|_|SysObjectID|_|BayStack 301|_|1.3.6.1.4.1.930.1.3|_|SysObjectID|_|HPJ2603A Ethernet SNMP Module, ROM B.01.00, EEPROM A.03.01, HW B.01.00|_|1.3.6.1.4.1.11.2.3.7.8.1|_|SysObjectID|_|NAT EM/450|_|1.3.6.1.4.1.86.1.2|_|SysObjectID|_|Olicom MultiMeter 3000 RMON2|_|1.3.6.1.4.1.217.1.3.3|_|SysObjectID|_|Sync Research Serial Frame Relay Access Probe With Pro-Act|_|1.3.6.1.4.1.485.7|_|SysObjectID|_|XL 5 IP|_|1.3.6.1.4.1.133.1.6.8.8|_|SysObjectID|_|Accelar-1200 (1.1.1)|_|1.3.6.1.4.1.2272.8|_|SysObjectID|_|Cisco Catalyst 5000|_|1.3.6.1.4.1.9.5.7|_|SysObjectID|_|HP-UX B.10.10 E 9000/821|_|1.3.6.1.4.1.11.2.3.2.3|_|SysObjectID|_|Patrol Agent V3,1.9a9 (SCO)|_|1.3.6.1.4.1.1031.1.1|_|SysObjectID|_|4BSD/ISODE SNMP|_|1.3.6.1.4.1.4.1.2.5|_|SysObjectID|_|MLARS|_||_|ifType|_|MLARS|_|1.3.6.1.4.1.2929|_|SysObjectID|_|NetFlow|_||_|ifType|_|Cisco_MPLS_LSP|_||_|ifType|_|



Exporting the nodeType

resmgr -export ngp -colNames "npath ncl.name ncl.oid ncl.type" -filter "ncl.type(SysObjectID)" -file $DIR/ngp.dat

# type = ngp# col = npath ncl.name ncl.oid ncl.type# filter = ncl.type(SysObjectID)# order =# sep = |_|# sepRec =## cmdLine = -export ngp -colNames "npath ncl.name ncl.oid ncl.type" -filter "ncl.type(SysObjectID)"~NodesType~Router~Cisco|_|Cisco 2501|_|1.3.6.1.4.1.9.1.17|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco LS1010|_|1.3.6.1.4.1.9.1.107|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco WSX 5302|_|1.3.6.1.4.1.9.1.168|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 4700|_|1.3.6.1.4.1.9.1.50|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 4500|_|1.3.6.1.4.1.9.1.14|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 2513|_|1.3.6.1.4.1.9.1.29|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 2504|_|1.3.6.1.4.1.9.1.20|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 3640|_|1.3.6.1.4.1.9.1.110|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 7000|_|1.3.6.1.4.1.9.1.8|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 2507|_|1.3.6.1.4.1.9.1.23|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 4000|_|1.3.6.1.4.1.9.1.7|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 753|_|1.3.6.1.4.1.9.1.83|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 2524|_|1.3.6.1.4.1.9.1.74|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 2511|_|1.3.6.1.4.1.9.1.27|_|SysObjectID|_|~NodesType~Router~Cisco|_|Cisco 766|_|1.3.6.1.4.1.9.1.103|_|SysObjectID|_|~NodesType~Access~Redback|_|Redback SMS 500|_|1.3.6.1.4.1.2352.1.2|_|SysObjectID|_|~NodesType~Access~Paradyne|_|PARADYNE T1 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|_|Unisphere C2100|_|1.3.6.1.4.1.2908.1|_|SysObjectID|_|~NodesType~Access~Unisphere|_|Unisphere C2100Rev1|_|1.3.6.1.4.1.2908.1.1|_|SysOb-jectID|_|~NodesType~Access~Unisphere|_|Unisphere RX1400|_|1.3.6.1.4.1.2773.1.2.1.1|_|SysOb-jectID|_|~NodesType~Access~Unisphere|_|Unisphere RX700|_|1.3.6.1.4.1.2773.1.2.1.2|_|SysOb-jectID|_|~NodesType~Access~Lucent|_|Lucent PortMaster|_|1.3.6.1.4.1.307.2.1|_|SysObjectID|_|

Importing Nomenclature

You must use the following columns when importing new nomenclature:

• type SysObjectID or Vendor : name oid type

• type ifType : name type

When updating nomenclature, you must use the following columns:

• dbIndex or name+type

• columns to be modified



Updating the name of new equipment

resmgr -import ncl -colNames "type OLD_name name oid" -line "SysObjectID|_|Cisco As inserted by discovert |_|Cisco C7100-IS|_|"

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

You must use the following columns when importing new nomenclature:

• dbIndex

• name+type

Deleting a nomenclature

resmgr -delete ncl -colNames "dbIndex" -line "100008514"

Info : === delete : DELETE ON nomenclature ( Cisco C7100-IS ) (exists)# Unlink a nomclature to the nodeType :resmgr -delete linkGroupN -colNames "npath ncl.dbIndex" -line "~Nod-esType~Router~Cisco|_|100008514"Info : === delete : DELETE ON nomLink (exists)Info : === Update Histo : 0

Deleting a nodeType

resmgr -delete ngp -colNames "npath" -line "~NodesType~Router~Cisco"

Info : === DELETE GROUP : ~NodesType~Router~Cisco (index = 548) Info : === delete : DELETE ON Nomenc Group ( ~NodesType~Router~Cisco ) (exists)Info : === Update Histo : 0

Using Mandatory Links

This section explains how to use mandatory links with Tivoli Netcool Performance Manager resources. You can use the following option to indicate whether or not a link is mandatory:

-isMandat



Using Manadatory Links with Elements

You can use the following option to force a link to be mandatory (or not) between elements and the following object types:

• scf

• encl

• eprp

For example:

Display Elements Command

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

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

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

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

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

With or without properties resmgr -export elt -colNames "name eprp.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 ETHERNET MULTI-ENVIRONMENT|_|192.168.127.2|_|Cisco Catalyst 3524 XL|_|192.168.127.3|_|Cisco Catalyst 3524 XL|_|192.168.127.5|_|Cisco Catalyst 3524 XL|_|192.168.127.6|_|Cisco Catalyst 3524 XL|_|192.168.127.7|_|Cisco Internetwork Operating System Software \nIOS (tm) C3500XL Software (C3500|_|Delete_100000174_192.168.2.2|_|Cisco C2600-I|_|Delete_100000176_192.168.3.253|_|Cisco 2611|_|Delete_100000179_192.168.3.62|_|Cisco Internetwork Operating System Software \nIOS (tm) L3 Switch/Router Softwa|_|marketing.quallaby.com|_|HP Printer ETHERNET MULTI-ENVIRONMENT|_|

Displaying all elements (with or without a nomenclature)

resmgr -export elt -colNames "name encl.name" -file $DIR/isMandat_noencl.dat

# type = elt# col = name encl.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name encl.name"Delete_200000632_192.168.3.254|_|3Com Hub (SuperStack II PS Hub 40)|_|Delete_200000788_192.168.3.37|_|BayStack 350T|_|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 ETHERNET MULTI-ENVIRONMENT|_|192.168.66.2|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEM-PRO|_|dhcp65.quallaby.com|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO|_|echidna.quallaby.com|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO|_|svrne01.quallaby.com|_|Hardware: x86 Family 6 Model 1 Stepping 9 COMPAQ SYMMETRIC SYSTEMPRO|_|Delete_200000793_192.168.3.227|_|Sun SNMP Agent|_|Delete_200000791_192.168.3.82|_|Sun SNMP Agent|_|Delete_200000790_192.168.3.226|_|Sun SNMP Agent|_|



Displaying all elements without nomenclature

resmgr -export elt -colNames "name encl.name" -filter "encl.name(is null)" -file $DIR/isnull_encl.dat

# type = elt# col = name encl.name# filter = encl.name(is null)# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name encl.name" -filter "encl.name(is null)"Burned_100008089_192.168.1.3|_||_|192.168.127.4|_||_|APRouterforprobe|_||_|PROVISO|_||_|default|_||_|

Displaying all elements with a SNMP configuration

resmgr -export elt -colNames "name scf.ipaddress" -isMandat "scf" -file $DIR/isMandat_scf.dat

# type = elt# col = name scf.ipaddress# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name scf.ipaddress"default|_|*.*.*.*|_|192.168.1.3|_|192.168.2.1|_|192.168.127.254|_|192.168.127.254|_|192.168.64.253|_|192.168.64.253|_|192.168.127.9|_|192.168.127.9|_|APRouterforprobe|_|172.17.100.254|_|192.168.127.8|_|192.168.127.8|_|192.168.127.6|_|192.168.127.6|_|

Displaying all elements with at least one property

resmgr -export elt -colNames "name eprp.name" -isMandat "elt.eprp" -file $DIR/isMandat_eprp.dat

# type = elt# col = name eprp.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name eprp.name"u440.quallaby.com|_|ipAddress|_|ipAddressMin|_|ipName|_|sysDescr|_|sysName|_|unisphere.quallaby.com|_|ipAddress|_|ipAddressMin|_|ipName|_|sysDescr|_|sysName|_|



Displaying all elements with or without properties

resmgr -export elt -colNames "name eprp.name" -file $DIR/all_eprp.dat

# type = elt# col = name eprp.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name eprp.name"172.31.0.31|_|ipAddress|_|ipName|_|physAddress|_|sysDescr|_|sysName|_|172.31.0.41|_|ipAddress|_|ipName|_|physAddress|_|sysDescr|_|sysName|_|172.31.0.51|_|ipAddress|_|ipName|_|physAddress|_|sysDescr|_|sysName|_|172.31.1.2|_|ipAddress|_|ipName|_|physAddress|_|sysDescr|_|sysName|_|192.168.127.4|_|192.168.127.5|_|ipAddress|_|ipAddressMin|_|ipName|_|physAddress|_|sysDescr|_|sys-Name|_|

Using Manadatory Links with Subelements

You can use the mandatory option to force a link to be mandatory (or not) between subelements and the following object types:

• fam

• emptyfam

• seprp

For example:

Displaying all subelements with a family

resmgr -export se -colNames "name fam.name" -isMandat "fam" -file $DIR/isMandat_fam.dat

# type = se# col = name fam.name# filter =# order =# sep = |_|# sepRec =

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 families without subelements; not the opposite

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



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

resmgr -export se -colNames "name fam.name" -filter "fam.name(is null)" -file $DIR/isnull_fam.dat

# type = se# col = name fam.name# filter = fam.name(is null)# order =# sep = |_|# sepRec =## cmdLine = -export se -colNames "name fam.name" -filter "fam.name(is null)"cme222.quallaby.com_<NULL>|_||_|

Displaying all subelements (with or without a family)

resmgr -export se -colNames "name fam.name" -file $DIR/all_fam.dat

# type = se# col = name fam.name# filter =# order =# sep = |_|# sepRec =# cmdLine = -export se -colNames "name fam.name"[email protected]|_|MLARS|_|NF-iphost-site-flow-BestEffort-CoffeeBucks_srcIP[Engineering-cb]dstSite[Dal-las]cos[BestEffort]|_|NetFlow|_|NF-site-Bronze-CoffeeBucks_Site[Denver]cos[Bronze]|_|NetFlow|_|cme222.quallaby.com_<NULL>|_||_|

Displaying all families without subelements linked to them

Note: Use emptyfam for families with no subelements linked.

resmgr -export se -colNames "name fam.name" -isMandat "emptyfam" -filter "se.name(is null)" -file $DIR/emptyfam.dat

# type = se# col = name fam.name# filter = se.name(is null)# order =# sep = |_|# sepRec =# cmdLine = -export se -colNames "name fam.name" -filter "se.name(is null)"|_|1315_FR_DLC_SNMP-CIR|_|



Using Manadatory Links with Subelement Groups

You can use the mandatory option to force a link to be mandatory (or not) between subelement groups and the following object types:

• app

• se

• rusr

• tzc

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

For example:

Displaying only groups with timezones

resmgr -export segp -colNames "npath cal.name tz.name" -file $DIR/ismandat_tznull.dat

# type = segp# col = npath cal.name tz.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export segp -colNames "npath cal.name tz.name"~NOC Reporting|_|CME Permanent|_|EST_2010|_|~NOC Reporting|_|CME Permanent|_|EST_2010_DST|_|~NOC Reporting|_|CME Permanent|_|EST_2009|_|~NOC Reporting|_|CME Permanent|_|EST_2009_DST|_|

Display Subelement Groups Command

only groups with timezones resmgr -export segp -colNames "npath cal.name tz.name"

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

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



Displaying all groups, including empty ones

You use the -isMandat option in this command to force it to empty, because by default -isMandat is not empty.

resmgr -export segp -colNames "npath se.name" -isMandat "" -file $DIR/ismandat_senull.dat

# type = segp# col = npath se.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export segp -colNames "npath se.name"~Partner Section~Juniper~Virtual Router~IP Inter-faces~default~10.8.7.18|_|192.168.127.2_If<23>|_|~NOC Reporting~Network Management~By loca-tion~"Catalyst_PS_Lab"|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~By Customer and Location~Bristol-Myers Squibb by loca-tion~"Catalyst_PS_Lab"|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~WCOM Test group~Headquarters~Loreal~Bordeaux~test value2|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~By Customer and CoS~Loreal CoS~Gold|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~By Customer and VPN~Loreal VPN~Headquar-ters|_|192.168.127.2_If<23>|_|~NOC Reporting~IP VPN~By Class of Service~Gold|_|192.168.127.2_If<23>|_|~NOC Reporting~IP VPN~By City~Bordeaux|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~By CoS~Gold|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~By CoS~Standard|_|192.168.127.2_If<23>|_|~Customer Facing Reporting~IP VPN~WCOM Test group~Sales and Marketing~Volk-swagen~Frankfurt|_||_|~Customer Facing Reporting~IP VPN~WCOM Test group~Research and Development~Chev-ron~San Francisco|_||_|~NOC Reporting~Virtual Routers~IP Address Pools~%(Element.NAME)|_||_|~Customer Facing Reporting~By Customer and Location~CVS by location~Denver|_||_|~Customer Facing Reporting~IP VPN~WCOM Test group~Research and Develop-ment~Fiat~Rome|_||_|~Partner Section~Cisco~Netflow|_||_|

Displaying only empty groups

resmgr -export segp -colNames "dbIndex name segchild.name se.name" -isMandat "" -filter "segchild.name(is null) se.name(is null) type(generated)" -file $DIR/emptyGroup.dat

# type = segp# col = dbIndex name segchild.name se.name# filter = segchild.name(is null) se.name(is null) type(generated)# order =# sep = |_|# sepRec =## 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|_||_||_|

Using Mandatory Links with Inventory Profiles

You can use the mandatory option to force a link to be mandatory (or not) between inventory profiles and the following object types:

• opt

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

Displaying the npath without options

resmgr -export ogp -isMandat "" -colNames "npath opt.name" -filter "opt.name(is null)" -file $DIR/ogp_noOpt.dat

# type = ogp# col = npath opt.name# filter = opt.name(is null)# order =# sep = |_|# sepRec =## cmdLine = -export ogp -colNames "npath opt.name" -filter "opt.name(is null)"~SROB-Migration41-Test~synchro~filestoinsert|_||_|~QuallabyNetwork~synchro~filestoinsert|_||_|~default~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 Nomenclature

You can use the mandatory option to force a link to be mandatory (or not) between nomenclature and the following object types:

• node type

Displaying the number of nomenclature attached to a node type

resmgr -export ncl -colNames "name oid nliParent" -isMandat "nodetype" -noHead | wc -l

The output is a number.



Displaying a list of nomenclature without nodeType defined

resmgr -export ncl -colNames "name oid nliParent" -filter "nliParent(is null)" -file $DIR/ncl_noNT.dat

# type = ncl# col = name oid nliParent# filter = nliParent(is null)# order =# sep = |_|# sepRec =## cmdLine = -export ncl -colNames "name oid nliParent" -filter "nliParent(is null)"Cabletron MicroMMAC|_|1.3.6.1.4.1.52.3.9.3.4.3|_||_|Cisco IPsec|_|1.3.6.1.2.1.33|_||_|Cisco_IPSec|_||_||_|Cisco Internetwork Operating System Software \nIOS (tm) C3500XL Software (C3500|_|1.3.6.1.4.1.9.1.278|_||_|1213_Device|_||_||_|Cisco Internetwork Operating System Software \nIOS (tm) C2600 Software (C2600-I|_|1.3.6.1.4.1.9.1.209|_||_|MLARS|_||_||_|Cisco Internetwork Operating System Software \nIOS (tm) L3 Switch/Router Softwa|_|1.3.6.1.4.1.9.1.275|_||_|Cisco Internetwork Operating System Software \nIOS (tm) C2600 Software (C2600-I|_|1.3.6.1.4.1.9.1.208|_||_|1213_IF|_||_||_|1315_FR_DLC_SNMP-CIR|_||_||_|



NOTES


Chapter 7: Managing Design Objects

This chapter explains how to use resmgr to manage design objects, and is made up of the following topics:

Overview

This chapter explains how to use resmgr to export, import, and different Tivoli Netcool Performance Manager object types that belong to the Design category. Design objects include the following types:

• formulas

• properties

• thresholds

• requests

• Calendars

• timezones

• inventory profiles


Topic Page

Working with Formulas 122

Working with Properties 125

Working with Thresholds 135

Working with Requests 137

Working with Calendars 139

Working with Timezones 141

Working with Inventory Profiles 142



Working with Formulas

This section contains the commands you can use to manage formulas. You should use the Tivoli Netcool Performance Manager DataMart Formula Editor to create formulas. When you use resgmr to work with the elements, you work with the following object types:

• frm

• fgp

• linkGroupF (import only)

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

Exporting Formulas

The following examples of resmgr command used to export formulas contain the command and the results of that command.

Exporting formula groups

resmgr -export fgp -colNames "dbIndex nName frm.dbIndex frm.data frm.type frm.comment frm.date frm.state" -sepRec "<E>" -file $DIR/fgp.dat

# type = fgp# col = dbIndex nName frm.dbIndex frm.data frm.type frm.comment frm.date frm.state# filter =# order =# sep = |_|# sepRec = <E># rule =# filterRule =## cmdLine = -export fgp -colNames "dbIndex nName frm.dbIndex frm.data frm.type frm.comment frm.date frm.state"1932|_|~Alias Instance and Label Inventory~AP~Cisco_IPSec|_|4114|_|V1=OIDVAL(sysLo-cation.0,once);V2=OIDVAL(sysName.0);V3=OIDVAL(%H1);%V1 index "IPSec<NULL>||IPSec agent on: %V3 (%V2)||location<%V1>||";|_|snmp|_|SNMP Discovery Formula for the "Cisco_IPSec" Family - Cisco router-level IPSec agents|_|999640340|_|on|_|<E>1932|_|~Alias Instance and Label Inventory~AP~Cisco_IPSec_match|_|4184|_|cipSec-MibLevel.0|_|snmp|_|"Match" Formula for matching SubElements to the "Cisco_IPSec" Family, since they will also fulfill requirements for Family "1213_Device"|_|983650594|_|on|_|<E>4353|_|~AP~Tivoli Netcool Performance Manager~DataManager~Element Average Response Time (ms)|_|4352|_|Stat( "Targets" , %H1 , "SNMP Response Time (ms) [last hour]" )|_|snmp|_|Uses internal Tivoli Netcool Performance Manager Statistics to calculate an Elements SNMP Response Time.|_|983650594|_|on|_|<E> 4353|_|~AP~Tivoli Netcool Performance Manager~DataManager~Element Availability (percent)|_|4354|_|Stat( "Targets" , %H1 , "SNMP Availability (%) [last hour]" )|_|snmp|_|Uses internal Tivoli Netcool Performance Manager Statistics to calculate Elements Availability in percent|_|983650594|_|on|_|<E>



4353|_|~AP~Tivoli Netcool Performance Manager~DataMan-ager~detect_reboot|_|4355|_|distrib(delta(sysUpTime.0), "default:1");|_|snmp|_|An example of how to detect system reboot.|_|983650594|_|on|_|<E>

Exporting formula MIBs

resmgr -export fgp -colNames "nName frm.mibPath" -file $DIR/fgp_mibs.dat

# type = fgp# col = nName frm.mibPath# filter =# order =# sep = |_|# sepRec =## cmdLine = -export fgp -colNames "nName frm.mibPath"~Demo~Addressess Free|_|rfc1213-MIB-II|_|~Demo~Address Pool Utilization (percent)|_|rfc1213-MIB-II|_|~Alias Instance and Label Inventory~AP~Disman_Ping_Test|_|rfc2925p.mi2|_|~Alias Instance and Label Inventory~AP~Cisco_CBQoS_Action|_|CISCO-CLASS-BASED-QOS-MIB.my|_|~Alias Instance and Label Inventory~AP~Cisco_CBQoS_Class|_|rfc1213-MIB-II|_|~Alias Instance and Label Inventory~AP~Cisco_CBQoS_Class|_|CISCO-CLASS-BASED-QOS-MIB.my|_|~Alias Instance and Label Inventory~AP~Cisco_Router_Device_SAA_Resp|_|rfc1213-MIB-II|_|~Alias Instance and Label Inventory~AP~Cisco_Router_Device_SAA_Resp|_|CISCO-RTTMON-MIB.my|_|~Alias Instance and Label Inven-tory~AP~Cisco_Router_Device_SAA_Resp_match|_|rfc1213-MIB-II|_|~Alias Instance and Label Inventory~AP~Cisco_Router_Device_SAA_Resp_match|_|cisco-10-mib|_|~Alias Instance and Label Inventory~AP~Cisco_Router_Device_SAA_Resp_match|_|CISCO-RTTMON-MIB.my|_|~Alias Instance and Label Inventory~AP~Cisco_Router_Device_SAA_match|_|rfc1213-MIB-II|_|~Alias Instance and Label Inventory~AP~Cisco_Router_Device_SAA_match|_|OLD-CISCO-SYSTEM-MIB.my|_|~Alias Instance and Label Inventory~AP~Cisco_Router_Device_SAA_match|_|CISCO-RTT-MON-MIB.my|_|~Alias Instance and Label Inventory~AP~Cisco_Router_Device_SAA|_|rfc1213-MIB-II|_|

Importing Formulas

You must use the following columns for a new formula. By default, dbIndex is taken from the designSequences column, type is import, dataType is float, nbHost is 1.

• frm

• fgp

• linkGroupF


• for fgp, use npath

• for frm, use name data type



• for type ifType, use name type

When updating formulas, you must use the following columns:

• for fgp, use dbIndex or npath (or nNam) and the columns to be modified

• for frm, use dbIndex and the columns to be modified

Input File

The input file includes the following:

~Alias Instance and Label Inventory~AP~NEW Cisco_IPSec|_|V1=OIDVAL(sysLoca-tion.0,once);V2=OIDVAL(sysName.0);V3=OIDVAL(%H1);%V1 index "IPSec<NULL>||IPSec agent on: %V3 (%V2)||location<%V1>||";|_|snmp|_|SNMP Discovery Formula for the "Cisco_IPSec" Family - Cisco router-level IPSec agents|_|<E>

Importing formula groups

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

Info: === insert: nothing ON Formula Group (~Alias Instance and Label Inventorially ) (exists)Info : === insert : INSERT ON Formulas ( NEW Cisco_IPSec ) (does not exist)Info : === insert : INSERT ON Link F/G ( NEW Cisco_IPSec ~Alias Instance and Label Inventory~AP ) (does not exist)Info : === Update Histo : 0

Deleting Formulas

You must use the following columns when deleting formulas:

• for fgp, use dbIndex or npath (or nName for a formula)

• for frm, use dbIndex

Deleting a formula group

resmgr -delete fgp -colNames "npath" -line "~test1"

Info : === DELETE GROUP : ~test1 (index = 100001032) Info : === delete : DELETE ON Formula Group ( ~test1 ) (exists)Info : === Update Histo : 0

Deleting a formula

resmgr -delete frm -colNames "dbIndex" -line "100008516"

Info : === delete : DELETE ON Formulas ( NEW Cisco_IPSec ) (exists)



Unlinking a formula ( for example, for a cut and paste)

resmgr -delete linkGroupF -colNames "npath frm.name" -line "~test1|_|Cisco_MPLS_LSP"

Info : === delete : DELETE ON Link F/G ( Cisco_MPLS_LSP ~test1 ) (exists)Info : === Update Histo : 0

Working with Properties

This section contains commands you can use when you manage properties. When you work with property object types, you work with

• propertyE for the element properties

• propertySE for the sub-element properties

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

• ipName

• sysName

• physAddress

Subelement Properties

The following table lists the subelement properties supplied by a Tivoli Netcool Performance Manager installation:

Subelement Property Description

name A specific, textual name for this entity defined by the user, most often during general network configuration.

hostIP Physical IP address of the host upon which this resource resides

hostURL URL address assigned to the host upon which this resource resides

hostName Textual name assigned to the host upon which this resource resides. Defined by the user most often during general network configuration

parent Open-format name or ID assigned to an entity considered as a "parent" containing this resource. Is usually different from a physical host (see 'hostName' property.)

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


parentType Open-format "type" classification of the parent of this resource



description Open-format description text used in instances when helpful for grouping (currently not displayed in the DataView portal).

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

type Open-format name of the specific type of resource represented (Ethernet, DS1, and so on.)

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

protocol Transmission protocol specific to the resource (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 the resource

patchLevel Open-format patch level identification of the resource

country The country in which the resource resides

city The city, town, or municipality in which the resource resides

state The state in which the resource physically resides

province The province in which the resource resides

region Open-format region name at which the resource resides

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

location Physical location of the resource

locationID Open-format ID string assigned to the physical location at which the resource resides


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) committed for transfer over this resource.

committedBurstCapacity The transmission rate (bps) committed for short traffic bursts (for a pre-agreed duration) over this resource.

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

owner Service provider employee name/ID to which this resource belongs



Exporting Properties

The following examples of resmgr command used to export properties contain the command and the results of that command.

Exporting element properties

resmgr -export propertyE -colNames "name 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 defValue state" -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|_|

ownerCustomTag User-definable property for custom resource organization attributes

department Service provider department to which this resource belongs

departmentID ID of the service provider department to which this resource belongs

networkArea Network area (for example, BackBone, CPE) of the entity

network The name of the network of which this entity is a part.

networkID The ID of the network of which this entity is a part.

privateNetwork The name of the private (virtual) network of which this entity is a part.

privateNetworkID The ID of the private (virtual) network of which this entity is a part.

customer The name of the specific customer that this resource services.

customerID The ID of the specific customer that this resource services.

customerType The type of the customer that this resource services.


customerFacingName Alternate name to be used for this resource in customer-facing reports, messages, and so on.

securityProfileMask Open-format string for definition of a text mask which can be generated for users by a custom user group control system and used within rule conditions to organize user groups' access to resource views.



Exporting subelement properties

resmgr -export propertySE -colNames "name invariant defValue state" -file $DIR/propertySE.dat

# type = propertySE# col = name invariant defValue state# filter = invariant(type<SE>) invariant(type<SE>)# order =# sep = |_|# sepRec =## cmdLine = -export propertySE -colNames "name invariant defValue state" -filter "invariant(type<SE>) invariant(type<SE>)"customStringProperty01|_|type<SE>|_||_|on|_|customStringProperty02|_|type<SE>|_||_|on|_|customStringProperty03|_|type<SE>|_||_|on|_|customStringProperty04|_|type<SE>|_||_|on|_|customStringProperty05|_|type<SE>|_||_|on|_|customNumericProperty01|_|type<SE>|_||_|on|_|customNumericProperty02|_|type<SE>|_||_|on|_|customNumericProperty03|_|type<SE>|_||_|on|_|customNumericProperty04|_|type<SE>|_||_|on|_|customNumericProperty05|_|type<SE>|_||_|on|_|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 Values

You can export the default value (DefVal) of the property (as defined in the database) for a resource that does not yet exist by using the following option.

-isDefault

You can use this option with the following object types:

• eprp

• seprp

• ruprp

Exporting element property default values

resmgr -export elt -colNames "name eprp.Contact:value" -isDefault eprp -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 exist

resmgr -export propertyE -colNames "name dataType subType invariant state 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 subType invariant 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 Properties

The following properties are a subset of Tivoli Netcool Performance Manager Technology Pack properties. See the Tivoli Netcool Performance Manager Technology Pack documentation for information.

• ServiceContract

• ServiceCity

• ServiceEmail

• ServiceFax

• ServiceFirstName

• ServiceFirmName

• ServiceMaxOutage

• ServicePhone

• ServiceRate

• ServiceStatus

• ServiceStreet

• ServiceType

• ServiceZip

• ServiceLevel

• SupportLevel

• StatusCode

• ServiceMobile

• ServiceLastName

• TicketID

• NetFlow Pack Property

• NF_aggVIEW

• NF_type

• NF_src

• NF_dst

• NF_cos

• NF_customer

Properties Used by the Tivoli Netcool Performance Manager-enabled SAA Probes

The following table lists the probe properties:



Exporting report user properties

resmgr -export propertyRU -colNames "name invariant defValue state" -file $DIR/propertyRU.dat

# type = propertyRU# col = name invariant defValue state# filter = invariant(type<DVUser>)# order =# sep = |_|# sepRec =## cmdLine = -export propertyRU -colNames "name invariant defValue state" -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|_|

Probe Property Description

operation Test operation being executed for monitor probes, RMON, and so on.

timeout Timeout duration (seconds) for target response for monitor probes, RMON, and so on.

sourceIP IP address of the originating side for unidirectional entities (end-to-end simplex connections, network test probes, and so on.)

sourceURL URL of the originating side for unidirectional entities (end-to-end simplex connections, network test probes, etc.)

sourcePort IP port used on the originating side for unidirectional entities (end-to-end simplex connections, network test probes, and so on.)

destIP IP address of the terminating side for unidirectional entities (end-to-end simplex connections, network test probes, and so on.)

destURL URL of the terminating side for unidirectional entities (end-to-end simplex connections, network test probes, and so on.)

destPort IP port used on the terminating side for unidirectional entities (End-to-end simplex connections, network test probes, and so on.)

ProbeDefaultIPAddress IP address of probe

responderEnabled For latency probes, this identifies whether or not a target will respond to the probe.

testActivationInterval Time between activations of a latency test. A latency test does not run continuously. It is dormant for a period of time, activates, and sends one or more test packets/probes/requests.

testPacketInterval Interval between packets /probes/requests for a latency test that sends multiple packets/probes/requests per test activation.



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_UserProfile DataView user-scope property defining the general user type for control of certain security options.Valid settings:

• NOC - Network Operations Center user, few restrictions.

• PSLA - Proactive Service Level Agreement personnel, moderate restriction.

• SLA - End users, highest restriction.

DV_UserCustomLogoFile DataView user-scope property with a link to an image file statically defining a custom graphic for reporter summary headings.

DV_UserResourceName DataView user-scope property that defines which sub-element name definitions should be used for SE labels displayed to the particular user.Valid settings:

• 1 - Use the SEs' internal ALIAS field values (also dubbed "SE Labels").

• 2 - Use the SEs' internal NAME field values.

• 1771 - Use the value defined in the "customerFacingName" Property for each SE.

DV_UserShowCurrentPeriod DataView user-scope property which controls access to active-period report viewing.If equal to "true" or if undefined then the user is allowed to view reports on the current, active, possibly incomplete time period. Set to "false" for a user to disable the current period view capability.




DV_UserEnableFavoriteLink DataView user-scope property which enables the "Favorite Report" functionality (see DV_UserFavoriteURL).Valid settings are the strings 'true' and 'false'. Any setting not equal to one of these values is interpreted as 'false'. If 'true', the "Set Favorite Report" icon and the "Goto Favorite Report" icon are displayed on the portal. If 'false', then these icons are not displayed and the feature is disabled.

DV_UserFavoriteURL DataView user-scope property that specifies a user's "Favorite" report. The value of this property is a URL that generates a DataView report.

DV_UserWelcomeReporter DataView user-scope property that specifies a Welcome Reporter, or a "home" page, for a user. The value of this user property is a DataView reporter ID. Immediately following a user's initial Portal login, this Welcome Reporter is generated, so long as for that user no "Favorite Reporter"is defined and active (see DV_UserFavoriteURL and DV_UserEnableFavoriteLink).

DV_UserLoginName DataView user-scope property that can be set with the login name attributed to a DataView user. This Property is used for informational display on Reporter summary headings only.

DV_UserName DataView user-scope property that can be set with the name attributed to a DataView user. This Property is used for informational display on Reporter summary headings only.

DV_UserProbeConfigAccess Can have 3 states

• read-write - the user has access to all probe configuration/management functionality.

• read-only - The user may access the configuration/management GUIs, but they cannot save, modify or delete any probes via the GUI.

• null (or other value) - the user is restricted from viewing either GUI. Null is the same as not defining the property.



Importing Properties

You must use the name column for a new property. By default, dbIndex is taken from the DesignSequences column, comment is empty, state is on, and the dataType is string.

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

Importing subelement properties

resmgr -import propertySE -colNames "name dataType defValue comment" -sep "|" -line "ContactSE|string|none|property added for test|"

Info : === insert : UPDATE ON property ( ContactSE ) (exists)

You must use the dbIndex or name column when deleting a property.

Deleting subelement property

resmgr -delete propertySE -colNames "dbIndex" -line "100008275"


DV_UserProbeFileConfigAccess Can have 3 states

• read-write - the user has access to the file-based probe configuration functionality.

• read-only - The user may access the file-based probe configuration GUIs, but they cannot save, modify or delete any probes via the GUI.

• null (or other value) - the user is restricted from viewing the GUI.

DV_UserAccessScheduler Boolean that indicates if the user has permission to configure the Scheduler. "False" by default

DV_UserGranularitySetting Boolean that indicates if the user has permission to set granularity. "False" by default (allows the user to access the granularity setting section of his preference page.)

DV_UserGranularity_DAILY User granularity setting for daily time series reports. The default is "raw"

DV_UserGranularity_WEEKLY User granularity setting for weekly time series reports. The default is "30min"

DV_UserGranularity_MONTHLY User granularity setting for monthly time series reports. The default is "1day"

DV_UserGranularity_QUARTERLY User granularity setting for quarterly time series reports. The default is "1day"

DV_UserGranularity_YEARLY User granularity setting for yearly time series reports. The default is "1day"

DV_UserGranularity_14MONTHS User granularity setting for 14 months time series reports. The default is "1day"



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

Working with Thresholds

This section contains the commands you can use to manage thresholds. When you use resgmr to work with the thresholds, you work with the following object types:

• thrdv

Exporting thresholds

resmgr -export thrdv -colNames "idxMetric idxGroup idxResource fgp.nName segp.npath se.name mode_DECODE dteDate_DATE thrStat_DECODE thrCalc_DECODE thrCalcValue brstCrtclLevel brstCrtclTime_TIME brstWrnngLevel brstWrnngTime_TIME brstGenEvent_DECODE prdCrtclLevel prdCrtclTime_TIME prdWrnngLevel prdWrnngTime_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.name mode_DECODE dteDate_DATE thrStat_DECODE thrCalc_DECODE thrCalcValue brstCrtclLevel brstCrtclTime_TIME brstWrnngLevel brstWrnngTime_TIME brstGenEvent_DECODE prdCrt-clLevel prdCrtclTime_TIME prdWrnngLevel prdWrnngTime_TIME prdGenEvent_DECODE prdPeriod_DECODE# filter = mode_DECODE(Over)# order =# sep = |_|# sepRec =# rule =# filterRule =## cmdLine = -export thrdv -colNames "idxMetric idxGroup idxResource fgp.nName segp.npath se.name mode_DECODE dteDate_DATE thrStat_DECODE thrCalc_DECODE thrCalcValue brstCrtclLevel brstCrtclTime_TIME brstWrnngLevel brstWrnngTime_TIME brstGenEvent_DECODE prdCrtclLevel prdCrtclTime_TIME prdWrnngLevel prdWrnngTime_TIME prdGenEvent_DECODE prdPeriod_DECODE" -filter "mode_DECODE(Over)"2417|_|6397|_|0|_|~AP~Generic~Instrumentation~Other~Load Operation Failures (end of period)|_||_||_|Over|_|09/13/2001 21:35|_|sum|_|Stan-dard|_||_|1.9|_|0s|_|.9|_|0s|_|no|_||_||_||_||_|no|_|All|_|2416|_|6397|_|0|_|~AP~Generic~Instrumentation~Other~Load Operation Fail-ures|_||_||_|Over|_|09/13/2001 21:35|_|sum|_|Stan-dard|_||_|1.9|_|0s|_|.9|_|0s|_|no|_||_||_||_||_|no|_|All|_|2415|_|6397|_|0|_|~AP~Generic~Instrumentation~Other~Database Fail-ures|_||_||_|Over|_|09/13/2001 21:35|_|sum|_|Stan-dard|_||_|1.9|_|0s|_|.9|_|0s|_|no|_||_||_||_||_|no|_|All|_|2264|_|6397|_|0|_|~AP~Generic~Universal~Utilization~Storage Utilization (per-cent)|_||_||_|Over|_|09/13/2001 21:35|_|raw|_|Stan-dard|_||_|99|_|2h|_|98|_|2h|_|no|_||_||_||_||_|no|_|All|_|



Importing Thresholds

You must use the following columns for a new threshold. By default, idxGroup and idxResource = 0, all others are set to null.

• fgp.nName

• mode


• all

When updating thresholds, you must use the following columns:

• (idxMetric or fgp.nName)+(idxGroup or segp.npath if not null)+(idxResource or se.name if not null)


Importing thresholds

resmgr -import thrdv -colNames "fgp.nName segp.npath dteDate mode thrStat thrCalc brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdPeriod prdGenEvent" -sep "|" -line "~AP~Specific~SNMP~RFC-1213~Interface~Outbound Utilization (percent) RFC-1213 Interface|~test1|1025704759|2|0|0|3|2|60|120|1|1|0"

Info : === insert : INSERT ON Threshold ( 4741 0 ) (does not exist)Info : === Update Histo : 0

Deleting Thresholds

You must use the idx column to delete thresholds.

Deleting thresholds

resmgr -delete thrdv -colNames "idxMetric idxResource idxGroup" -sep "|" -line "4741|0|200003865|"

Info : === delete : DELETE ON Threshold ( 4741 0 ) (exists)



Working with Requests

This section contains the commands you can use to manage requests. When you use resgmr to work with requests, you work with the following object types:

• segpreq (collection requests)

• pctile (aggregation requests)

• allreq (all requests)

Exporting all requests

resmgr -export allreq -colNames "segp.npath fgp.nName period state status pctile type cal.name" -file $DIR/allreq.dat

# type = allreq# col = segp.npath fgp.nName period state status pctile type cal.name# filter =# order =# sep = |_|# sepRec =# cmdLine = -export allreq -colNames "segp.npath fgp.nName period state status pctile type cal.name"~Sub-Element Collect~Router~Devices~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~CPU Utilization (percent) (avg last 5 minutes) Cisco 11. x Router Device|_|900|_|on|_|active|_||_|collection|_||_|~Sub-Element Collect~Router~Devices~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~Buffer Utilization (percent) Cisco 11.x Router Device|_|900|_|on|_|active|_||_|collection|_||_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Restarts Cisco 11.x Router RFC-1213 Inter-face|_|900|_|on|_|active|_||_|collection|_||_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Resets Cisco 11.x Router RFC-1213 Inter-face|_|900|_|on|_|active|_||_|collection|_||_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Inter-face|_|900|_|on|_|active|_||_|collection|_||_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Inter-face|_|900|_|on|_|active|_||_|collection|_||_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Inter-face|_|900|_|on|_|active|_||_|collection|_||_|

Exporting subelement group requests

resmgr -export segpreq -colNames "segp.npath fgp.nName period state status" -file $DIR/segpreq.dat

# type = segpreq# col = segp.npath fgp.nName period state status# filter =# order =# sep = |_|# sepRec =#



# cmdLine = -export segpreq -colNames "segp.npath fgp.nName period state status"~Sub-Element Collect~Router~Devices~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~Buffer Utilization (percent) Cisco 11.x Router Device|_|900|_|on|_|active|_|~Sub-Element Collect~Router~Devices~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Device~CPU Utilization (percent) (avg last 5 minutes) Cisco 11.x Router Device|_|900|_|on|_|active|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Inter-face|_|900|_|on|_|active|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (percent) Cisco 11.x Router RFC-1213 Inter-face|_|900|_|on|_|active|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Outbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Inter-face|_|900|_|on|_|active|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Inbound Queue Drops (PDUs) Cisco 11.x Router RFC-1213 Inter-face|_|900|_|on|_|active|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Resets Cisco 11.x Router RFC-1213 Interface|_|900|_|on|_|active|_|

Exporting percentiles

resmgr -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 state value"

Importing Requests

You must use the following columns for new requests. By default, dbIndex is taken from the DesignSequences, period 900, idxCal is null, status idle, storage always, state = on, user = unix User, origin = resmgr, date = current date.

• segp.npath

• fgp.nName


• period

• value for pctile

• type+pctile for allreq

When updating requests, you must use the following columns:

• segp.npath

• fgp.nName




Importing percentiles

resmgr -import "segpreq" -colNames "fgp.nName segp.npath status storage period cal.name" -line "~AP~Specific~SNMP~RFC-1213~Interface~Outbound Utilization (percent) RFC-1213 Interface|_|~Sub-Element Collect|_|idle|_|always|_|900|_||_|"

Info : === insert : INSERT ON request ( 100008519 ) (does not exist)Info : === Update Histo : 0Title : === CHANGES : {1 New of segpreq}Info : === Inform Collector On hebus:3002

Deleting Requests

You must use the following columns when deleting requests.

• segp.npath

• fgp.nName

Deleting subelement group requests

resmgr -delete segpreq -colNames "fgp.nName segp.npath" -line "~AP~Specific~SNMP~RFC-1213~Interface~Outbound Utilization (percent) RFC-1213 Interface|_|~Sub-Element Collect|_|"

Info : === delete : DELETE ON request ( 100008519 ) (exists)Info : === Update Histo : 0Title : === CHANGES : {1 Deleted of segpreq}

Working with Calendars

This section contains the commands you can use to manage Calendars. When you use resgmr to work with Calendars, you work with the cal object type.

Exporting Calendars

Displaying list of Calendars

resmgr -export cal -colNames "dbIndex name period state origin user date_DATE" -file $DIR/cal.dat

# type = cal# col = dbIndex name period state origin user date_DATE# filter =# order =# sep = |_|# sepRec =#



# cmdLine = -export cal -colNames "dbIndex name period state origin user date_DATE"200|_|CME Permanent|_|900|_|on|_|APinstall|_|APdev|_|03/04/2001 00:16|_|100006809|_|4 AM to 8 PM restricted SLA|_|900|_|on|_|unknown|_||_||_|

Viewing Calendar detail

resmgr -export cal -colNames "comment type subType week fromDay fromTime toDay toTime" -filter "name(test1)" -file $DIR/cal_detail.dat

# type = cal# col = comment type subType week fromDay fromTime toDay toTime# filter =# order =# sep = |_|# sepRec =## cmdLine = -export cal -colNames "comment type subType week fromDay fromTime toDay toTime"Daily, each day from 00:00 to 04:00|_|1|_|1|_||_||_|00:00|_||_|04:00|_|Daily, each day from 20:00 to 23:59|_|1|_|1|_||_||_|20:00|_||_|23:59|_|

Importing Calendars

Use the Tivoli Netcool Performance Manager DataMart GUI to create new Calendars and resmgr for Calendar deployment.

You must use the following columns for new Calendars. By default, dbIndex is taken from the DesignSequences, all other columns are empty

• name

• period

When updating Calendars, you must use the following columns:

• dbIndex or name


Importing new Calendar data

resmgr -import cal -colNames " name period state user origin date_DATE type subType comment week fromDay fromTime toDay toTime" -sep "|" -line "psmamoImport|300|on|pvuser|resmgr|09/15/2002 18:05|1|1|Daily, each day from 04:00 to 07:59|||04:00||07:59|"

Info : === insert : INSERT ON Calendar ( psmamoImport ) (does not exist)Info : === insert : INSERT ON Calendar Contents ( psmamoImport Daily, each day from 04:00 to 07:59 ) (does not exist)



Deleting Calendars

resmgr -delete cal -colNames " name" -line "psmamoImport"

Info : === delete : DELETE ON Calendar ( psmamoImport ) (exists)

Working with Timezones

This section contains the commands you can use to manage timezones. When you use resgmr to work with timzones, you work with the following object type:

• tz

Exporting Timezones

Exporting all the defined aggregation sets

resmgr -export tz -colNames "dbIndex name date_DATE offset status comment" -file $DIR/tz_all.dat

# type = tz# col = dbIndex name date_DATE offset status comment# filter =# order =# sep = |_|# sepRec =## cmdLine = -export tz -colNames "dbIndex name date_DATE offset status comment"0|_|GMT|_|04/09/2002 02:30|_|0|_|2|_|GMT|_|0|_|EST_2002_DST|_|04/11/2002 17:00|_|-14400|_|2|_|Eastern Standard Time|_|0|_|EST_2002|_|10/27/2002 10:00|_|-18000|_|2|_|Eastern Standard Time|_|0|_|EST_2003_DST|_|04/06/2003 11:00|_|-14400|_|2|_|Eastern Standard Time|_|0|_|EST_2003|_|10/26/2003 10:00|_|-18000|_|2|_|Eastern Standard Time|_|0|_|EST_2004_DST|_|04/04/2004 11:00|_|-14400|_|2|_|Eastern Standard Time|_|0|_|EST_2004|_|10/31/2004 10:00|_|-18000|_|2|_|Eastern Standard Time|_|



Exporting only the currently active timezone

resmgr -export tz -colNames "dbIndex date_DATE offset status comment" -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 status comment" -filter "date(%NOW%)"0|_|10/26/2003 10:00|_|-18000|_|2|_|Eastern Standard Time|_|

Working with Inventory Profiles

This section contains the commands you can use to manage Calendars. When you use resgmr to work with Calendars, you work with the following object types:

• ogp

• opt

Duplicating an Inventory Profile

To duplicate an inventory profile, you need to export it and then import it. For example:

1. Enter the following command to export the profile quallaby:

resmgr -export ogp -isMandat "" -colNames "npath opt.name opt.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.instance opt.value" -file $DIR/ogp.dat

3. Import the profile.

resmgr -import ogp -mode update -colNames "npath opt.name opt.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)Info : === Update Histo : 0

Importing Inventory Profiles

You must use the following columns for new inventory profiles.

• npath

• opt.name

• opt.instance



• opt.value

See an example of importing code in step 3 under “Duplicating the Inventory Profile.”

Deleting Inventory Profiles

resmgr -delete ogp -colNames "npath" -line "~prof1"

Info : === DELETE GROUP : ~prof1 (index = 100008521) Info : === delete : DELETE ON Option Group ( ~prof1 ) (exists)Info : === Update Histo : 0



NOTES


Chapter 8: Managing Administration Objects

This chapter explains how to use resmgr to manage administrative objects, and is made up of the following topics:

Overview

This chapter explains how to use resmgr to export, import, and different Tivoli Netcool Performance Manager object types that belong to the Administration category. Design objects include the following types:

• Tivoli Netcool Performance Manager DataMart users and groups

• registry

• miscellaneous Tivoli Netcool Performance Manager objects

Topic Page

Overview 145

Working with Tivoli Netcool Performance Manager DataMart Users and Groups

146

Working with Registries 150

Working with Miscellaneous Tivoli Netcool Performance Manager Objects

162



Working with Tivoli Netcool Performance Manager DataMart Users and Groups

This section contains the commands you can use to manage Tivoli Netcool Performance Manager DataMart users and groups. When you use resgmr to work with the users and groups, you work with the following object types:

• usr

• uLink

• uPerm

Exporting Users and Groups

Exporting users

resmgr -export usr -colNames "dbIndex name fullname gpname gpcomment" -order "name" -file $DIR/usr.dat

# type = usr# col = dbIndex name fullname gpname gpcomment# filter =# order = name# sep = |_|# sepRec =## cmdLine = -export usr -colNames "dbIndex name fullname gpname gpcomment"100008754|_|pvuser|_|Create for IBM integration|_|admin|_|Proviso DataMart Adminis-trators|_|100008754|_|pvuser|_|Create for IBM integration|_|pvuser|_|Proviso DataMart Users|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|11|_|root|_|Proviso DataMart Administrator|_|admin|_|Proviso DataMart Administra-tors|_|100008755|_|vlad|_|User for IBM Integration|_|admin|_|Proviso DataMart Administra-tors|_|100008755|_|vlad|_|User for IBM Integration|_|pvuser|_|Proviso DataMart Users|_|



Exporting users

resmgr -export usr -colNames "dbIndex name fullname gpname gpcomment 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 Administra-tors|_|calconf|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|calsel|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|cmdedit|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|collectinfo|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|collector|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|dabdedit|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|dabdmgr|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|dabdsel|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|dataviewer|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|dbmgr|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|formedit|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|formsel|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|impexp|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|inventory|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|mibbrow|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|mibcomp|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|pollinv|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|pollprofile|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|provisoinfo|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|pvmstat|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|reqedit|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|resedit|_|w|_|



100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|resmgr|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|ruleconf|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|snmpconf|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|threconf|_|w|_|100000014|_|pvuser|_|Proviso Administrator|_|admin|_|Proviso DataMart Administra-tors|_|userconf|_|w|_|

Exporting groups

resmgr -export usr -colNames "gpname gpcomment module perms" -file $DIR/usr_gp.dat

# type = usr# col = gpname gpcomment module perms# filter =# order =# sep = |_|# sepRec =## cmdLine = -export usr -colNames "gpname gpcomment module perms"default|_|Default Users|_|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 Groups

Creating a new user who belongs to an existing group

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

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

Deleting User and Groups

Deleting users

resmgr -delete usr -colNames "name" -line "John"

Info : === delete : DELETE ON User ( John ) (exists)

Deleting groups

resmgr -delete usr -colNames "gpname" -line "group1"

You must ensure that you do not delete the following DataMart user groups:

Unlinking users from a group

resmgr -delete uLink -colNames "name gpname" -line "John|_|group1"

Working with Registries

This section contains the commands you can use to manage Tivoli Netcool Performance Manager registries. When you use resgmr to work with the registries, you work with the following object types:

• regisDM

• regisDC

• regisDCConfig

• regisDB

• regisDV

• regisMG (regDesc)

Group Name Description

default Default Users.

admin Tivoli Netcool Performance Manager DataMart Administrators.

pvuser Tivoli Netcool Performance Manager DataMart Users.



Exporting Registry Objects

Exporting DataMart registry

resmgr -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 Data-Mart|_|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 registry

resmgr -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.CUR-RENT.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.HIS-TORIC.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.CUR-RENT.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.HIS-TORIC.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.CUR-RENT.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.HIS-TORIC.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.CUR-RENT.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.HIS-TORIC.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.CUR-RENT.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.HIS-TORIC.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.CUR-RENT.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.HIS-TORIC.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.CUR-RENT.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.HIS-TORIC.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.CUR-RENT.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.NRAW.TABLE.HISTORIC.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.NRAW.TABLE.HIS-TORIC.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1DRA.TABLE.CURRENT.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.1DRA.TABLE.CUR-RENT.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1DRA.TABLE.HISTORIC.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.1DRA.TABLE.HIS-TORIC.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1WRA.TABLE.CURRENT.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.1WRA.TABLE.CUR-RENT.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1WRA.TABLE.HISTORIC.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.1WRA.TABLE.HIS-TORIC.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1MRA.TABLE.CURRENT.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.1MRA.TABLE.CUR-RENT.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1MRA.TABLE.HISTORIC.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.1MRA.TABLE.HIS-TORIC.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1DGA.TABLE.CURRENT.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.1DGA.TABLE.CUR-RENT.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1DGA.TABLE.HISTORIC.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.1WGA.TABLE.CUR-RENT.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1MGA.TABLE.HIS-TORIC.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.HIS-TORIC.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.HIS-TORIC.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1MGA.TABLE.CURRENT.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.DEFAULT.1MGA.TABLE.CUR-RENT.PARTITION_EXTENTS|_|PARTITION_EXTENTS|_|5|_|0|_|CHANNELS.DEFAULT.1MGA.TABLE.HISTORIC.PARTITION_SIZE|_|PARTITION_SIZE|_|100|_|0|_|CHANNELS.CLI-ENTS.LDR.TEMPORARY_TABLESPACE.CREATION_PATH|_|CREATION_PATH|_|/export/home0/orad-ata/PV30|_|1|_|CHANNELS.CLIENTS.LDR.TEMPORARY_TABLESPACE.EXTENT_SIZE|_|EXTENT_SIZE|_|1024|_|0|_|CHANNELS.CLI-ENTS.LDR24.TEMPORARY_TABLESPACE.CREATION_PATH|_|CREATION_PATH|_|/export/home0/orad-ata/PV30|_|1|_|CHANNELS.CLIENTS.LDR24.TEMPORARY_TABLESPACE.EXTENT_SIZE|_|EXTENT_SIZE|_|1024|_|0|_|CHANNELS.CLIENTS.CHAN-NEL.TEMPORARY_TABLESPACE.CREATION_PATH|_|CREATION_PATH|_|/export/home0/orad-ata/PV30|_|1|_|CHANNELS.CLIENTS.CHAN-NEL.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.CUR-RENT.CREATION_PATH|_|CREATION_PATH|_|/export/home0/oradata/PV30|_|1|_|CHANNELS.C01.NRAW.TABLESPACE.CURRENT.SIZE|_|SIZE|_|344|_|0|_|CHANNELS.C01.NRAW.TABLESPACE.HIS-TORIC.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.CUR-RENT.CREATION_PATH|_|CREATION_PATH|_|/export/home0/oradata/PV30|_|1|_|CHANNELS.C01.1DRA.TABLESPACE.CURRENT.SIZE|_|SIZE|_|22|_|0|_|CHANNELS.C01.1DRA.TABLESPACE.HIS-TORIC.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.CUR-RENT.CREATION_PATH|_|CREATION_PATH|_|/export/home0/oradata/PV30|_|1|_|CHANNELS.C01.1WRA.TABLESPACE.HIS-TORIC.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.CUR-RENT.CREATION_PATH|_|CREATION_PATH|_|/export/home0/oradata/PV30|_|1|_|CHANNELS.C01.1MRA.TABLESPACE.HIS-TORIC.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.CUR-RENT.CREATION_PATH|_|CREATION_PATH|_|/export/home0/oradata/PV30|_|1|_|CHANNELS.C01.1DGA.TABLESPACE.HIS-TORIC.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.CUR-RENT.CREATION_PATH|_|CREATION_PATH|_|/export/home0/oradata/PV30|_|1|_|CHANNELS.C01.1WGA.TABLESPACE.HIS-TORIC.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.CUR-RENT.CREATION_PATH|_|CREATION_PATH|_|/export/home0/oradata/PV30|_|1|_|CHANNELS.C01.1MGA.TABLESPACE.HIS-TORIC.CREATION_PATH|_|CREATION_PATH|_|/export/home0/oradata/PV30|_|1|_|CHANNELS.C01.1MGA.TABLESPACE.HISTORIC.SIZE|_|SIZE|_|10|_|0|_|CHANNELS.COMMON.1DRA.CURRENT_KEEP_DAYS|_|CURRENT_KEEP_DAYS|_|3|_|0|_|CHANNELS.COMMON.1DGA.CURRENT_KEEP_DAYS|_|CURRENT_KEEP_DAYS|_|3|_|0|_|CHANNELS.COMMON.1WGA.CURRENT_KEEP_WEEKS|_|CURRENT_KEEP_WEEKS|_|2|_|0|_|CHANNELS.COMMON.1MGA.CURRENT_KEEP_MONTHS|_|CURRENT_KEEP_MONTHS|_|2|_|0|_|CHANNELS.COMMON.AUTOEXTEND_TOLERANCE|_|AUTOEXTEND_TOLERANCE|_|100|_|0|_|CHANNELS.COMMON.RECORDSCHEMAS.NRAW.ID|_|ID|_|NRAW0303|_|1|_|CHANNELS.COMMON.RECORDSCHEMAS.RA.ID|_|ID|_|RAXX0401|_|1|_|CHANNELS.COMMON.RECORDSCHEMAS.GA.ID|_|ID|_|GAXX0401|_|1|_|

Exporting DataChannel Configuration registry

resmgr -export regisDCConfig -colNames "path value" -file $DIR/regisDCConfig.dat

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

To export 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 registry

resmgr -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 reload-ing 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 registry

resmgr -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.MAS-TER.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.LATE-DATA.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.MAS-TER.CHECK_HEARTBEAT_AFTER_N_CRCN|_|CHECK_HEARTBEAT_AFTER_N_CRCN|_|10|_|0|_|DATAVIEW.SCHEDULER.MASTER.EMAIL.HOST_SERVER|_|HOST_SERVER|_|mail2.quall-aby.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/silver-stream/SchedulerNFS|_|1|_|DATAVIEW.SCHEDULER.MASTER.FTP.BASE_DIRECTORY|_|BASE_DIRECTORY|_|/export/home/sil-verstream/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 registry

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

resmgr -export regDesc -colNames "registry table date comment" -DBUser ADMIN -file $DIR/regdesc.dat

# type = regDesc# col = registry table date comment# filter =# order =# sep = |_|# sepRec =## cmdLine = -export regDesc -colNames "registry table date comment"CHANNELS|_|REG_CHANNELS|_|2002/04/08 22:29:10|_|Channels management registry|_|DATABASE|_|REG_DATABASE|_|2002/04/08 22:29:39|_|General database configuration parameters|_|DATALOAD|_|REG_DATALOAD|_|2002/04/08 22:29:53|_|DataLoad management registry|_|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 registry

resmgr -export regInst:CHANNELS -colNames "dbIndex IdxParent name nodeType 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 Registries

Note: Do not not import to regisDCConfig as your inport will be overwritten the next time you run the Topology Editor/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 Registries

Registry does not have to be removed.



Working with Miscellaneous Tivoli Netcool Performance Manager Objects

This section contains the commands you can use to manage the following miscellaneous Tivoli Netcool Performance Manager DataMart objects.


• reg: information about components that are running




Working with chnl (information about Collector)

Exporting channel information

resmgr -export chnl -colNames "collector default port host instDir name comment display pid user port status hostReg date_DATE" -file $DIR/chnl.dat

# type = chnl# col = collector default port host instDir name comment display pid user port sta-tus hostReg date_DATE# filter =# order =# sep = |_|# sepRec =## cmdLine = -export chnl -colNames "collector default port host instDir name comment display pid user port status hostReg date_DATE"1|_|yes|_|3002|_|pvdemo3|_|/opt/dataload|_|pvmd_1|_|This module performs Requests and Real Time Queries|_|:0.0|_|1606|_|pvuser|_|3002|_|1|_|pvdemo3|_|10/02/2003 20:29|_|



Working with reg

Exporting all locks

resmgr -export reg -colNames "name host port comment display pid user port status date_DATE lock mode" -file $DIR/reg_lock.dat

# type = reg# col = name host port comment display pid user port status date_DATE lock mode# filter =# order =# sep = |_|# sepRec =# cmdLine = -export reg -colNames "name host port comment display pid user port sta-tus date_DATE lock mode"provisoinfod|_|pvdemo2.quallaby.com|_|3114|_|provisoinfo daemon|_|local-host:0.0|_|13288|_|pvuser|_|3114|_|1|_|10/02/2003 19:08|_|provisoinfod|_|1|_|pvmd_1|_|pvdemo3|_|3002|_|This module performs Requests and Real Time Que-ries|_|:0.0|_|1606|_|pvuser|_|3002|_|1|_|10/02/2003 20:29|_|pvmd_1|_|1|_|snmpconf|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|17561|_|pvuser|_|0|_|0|_|11/04/2003 00:12|_|snmpconf|_|1|_|

Exporting all registered modules

resmgr -export reg -colNames "name host port comment display pid user port status date_DATE" -file $DIR/reg_reg.dat

# type = reg# col = name host port comment display pid user port status date_DATE# filter =# order =# sep = |_|# sepRec =# cmdLine = -export reg -colNames "name host port comment display pid user port sta-tus date_DATE"provisoinfod|_|pvdemo2.quallaby.com|_|3114|_|provisoinfo daemon|_|local-host:0.0|_|13288|_|pvuser|_|3114|_|1|_|10/02/2003 19:08|_|pvm|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|14297|_|pvuser|_|0|_|0|_|10/06/2003 15:55|_|pvm|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|18508|_|pvuser|_|0|_|0|_|10/06/2003 19:37|_|pvm|_|pvdemo2.quall-aby.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 Que-ries|_|:0.0|_|1606|_|pvuser|_|3002|_|1|_|10/02/2003 20:29|_|pvm|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|17388|_|pvuser|_|0|_|0|_|10/10/2003 23:39|_|resedit|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|17396|_|pvuser|_|0|_|0|_|10/10/2003 23:39|_|pvm|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|22016|_|pvuser|_|0|_|0|_|10/17/2003 17:50|_|resedit|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|12223|_|pvuser|_|0|_|0|_|10/17/2003 01:32|_|collectinfo|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|23256|_|pvuser|_|0|_|0|_|10/28/2003 20:04|_|



resedit|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|22021|_|pvuser|_|0|_|0|_|10/17/2003 17:50|_|pvm|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|14576|_|pvuser|_|0|_|0|_|10/23/2003 18:51|_|resedit|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|14581|_|pvuser|_|0|_|0|_|10/23/2003 18:51|_|pvm|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|23111|_|pvuser|_|0|_|0|_|10/28/2003 19:46|_|pvm|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|6011|_|pvuser|_|0|_|0|_|10/01/2003 19:53|_|pvm|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|14810|_|pvuser|_|0|_|0|_|11/03/2003 19:18|_|pvm|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|6032|_|pvuser|_|0|_|0|_|10/01/2003 19:54|_|resedit|_|pvdemo2.quall-aby.com|_|0|_|NONE|_|dhcp114:0.0|_|6038|_|pvuser|_|0|_|0|_|10/01/2003 19:54|_|

Removing a register/lock module

resmgr -delete reg -colNames "name host" -line "pvm|_|host1”

Working with dbi

Exporting database information

resmgr -export dbi -colNames "dbIndex name type objId label desc" -DBUser ADMIN -file $DIR/dbi.dat

# type = dbi# col = dbIndex name type objId label desc# filter =# order =# sep = |_|# sepRec =## cmdLine = -export dbi -colNames "dbIndex name type objId label desc"1|_|Identification|_|Identification|_|1|_|Database Server|_|Database Server Name = pvdemo2Database Name = PV30Current Database User = PV_ADMIN

Oracle8i Enterprise Edition Release 8.1.7.4.0 - ProductionPL/SQL Release 8.1.7.4.0 - ProductionCORE 8.1.7.0.0 ProductionTNS for Solaris: Version 8.1.7.4.0 - ProductionNLSRTL Version 3.4.1.0.0 - Production

Total SGA = 248 M - Fixed Size = 72 K - Variable Size = 185 M - Database Buffers = 62 M - Redo Buffers = 528 K|_|1|_|Identification|_|Identification|_|1|_|Description|_|Last Refresh Date = 2003-11-04 04:17:51



Last Refresh Duration = 1,070.310 sec |_|110|_|Proviso Version|_|Information|_|10|_|Oracle 8.1.7, PVDEMO2, PV30|_|8i|_|

For Limited Use (checking for problems after installation)

Exporting registration information about Tivoli Netcool Performance Manager clients

resmgr -export client -colNames "login channelId type orausr.name orausr.profile orausr.defaultTS orausr.tempTS orausr.resGroup" -DBUser ADMIN -file $DIR/client.dat

# type = client# col = login channelId type orausr.name orausr.profile orausr.defaultTS orausr.tempTS orausr.resGroup# filter =# order =# sep = |_|# sepRec =## cmdLine = -export client -colNames "login channelId type orausr.name orausr.pro-file orausr.defaultTS orausr.tempTS orausr.resGroup"PV_ADMIN|_||_|ADMIN|_|PV_ADMIN|_|PV_ADMIN_PROFILE|_|PV_CFGD|_|PV_ADMIN_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_METRIC|_||_|MET-RIC|_|PV_METRIC|_|DEFAULT|_|PV_CFGD|_|PV_ADMIN_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_INSTALL|_||_|INSTALL|_|PV_INSTALL|_|DEFAULT|_|PV_CFGD|_|PV_ADMIN_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_CHNL_MANAGER|_||_|CHNL_MANAGER|_|PV_CHNL_MANAGER|_|DEFAULT|_|PV_CFGD|_|PV_CHNL_MANAGER_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_GUI|_||_|GUI|_|PV_GUI|_|DEFAULT|_|PV_CFGD|_|PV_GUI_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_INVENTORY|_||_|INVEN-TORY|_|PV_INVENTORY|_|DEFAULT|_|PV_CFGD|_|PV_INVENTORY_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_LOIS|_||_|LOIS|_|PV_LOIS|_|DEFAULT|_|PV_LOIS|_|PV_LOIS_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_REPORT|_||_|REPORT|_|PV_REPORT|_|DEFAULT|_|PV_REPT|_|PV_LOIS_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_REPORTMASTER|_||_|REPORTMAS-TER|_|PV_REPORTMASTER|_|DEFAULT|_|PV_REPM|_|PV_LOIS_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_RESMGR|_||_|RESMGR|_|PV_RESMGR|_|DEFAULT|_|PV_CFGD|_|PV_RESMGR_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_BACKUP|_||_|BACKUP|_|PV_BACKUP|_|DEFAULT|_|PV_CFGD|_|PV_BACKUP_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_LDR_01|_|1|_|LDR|_|PV_LDR_01|_|DEFAULT|_|PV_CFGD|_|PV_LDR_01_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_LDR24_01|_|1|_|LDR24|_|PV_LDR24_01|_|DEFAULT|_|PV_CFGD|_|PV_LDR24_01_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_CHANNEL_01|_|1|_|CHAN-NEL|_|PV_CHANNEL_01|_|DEFAULT|_|PV_CFGD|_|PV_CHNL01_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_COLL_01|_||_|COLL|_|PV_COLL|_|DEFAULT|_|PV_CFGD|_|PV_COLL_TEMP|_|DEFAULT_CONSUMER_GROUP|_|



Exporting list of Oracle users

resmgr -export orausr -colNames "name profile defaultTS tempTS resGroup" -DBUser ADMIN -file $DIR/orausr.dat

# type = orausr# col = name profile defaultTS tempTS resGroup# filter =# order =# sep = |_|# sepRec =## cmdLine = -export orausr -colNames "name profile defaultTS tempTS resGroup"SYS|_|DEFAULT|_|SYSTEM|_|SYSTEM|_|SYS_GROUP|_|SYSTEM|_|DEFAULT|_|SYSTEM|_|SYSTEM|_|SYS_GROUP|_|OUTLN|_|DEFAULT|_|SYSTEM|_|SYSTEM|_|DEFAULT_CONSUMER_GROUP|_|TRACESVR|_|DEFAULT|_|SYSTEM|_|SYSTEM|_|DEFAULT_CONSUMER_GROUP|_|PV_INSTALL|_|DEFAULT|_|PV_CFGD|_|PV_ADMIN_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_GUI|_|DEFAULT|_|PV_CFGD|_|PV_GUI_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_LOIS|_|DEFAULT|_|PV_LOIS|_|PV_LOIS_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_REPORTMASTER|_|DEFAULT|_|PV_REPM|_|PV_LOIS_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_COLL|_|DEFAULT|_|PV_CFGD|_|PV_COLL_TEMP|_|DEFAULT_CONSUMER_GROUP|_|DBSNMP|_|DEFAULT|_|SYSTEM|_|SYSTEM|_|DEFAULT_CONSUMER_GROUP|_|PV_CHANNEL_01|_|DEFAULT|_|PV_CFGD|_|PV_CHNL01_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_LDR24_01|_|DEFAULT|_|PV_CFGD|_|PV_LDR24_01_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_LDR_01|_|DEFAULT|_|PV_CFGD|_|PV_LDR_01_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_BACKUP|_|DEFAULT|_|PV_CFGD|_|PV_BACKUP_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_REPORT2|_|DEFAULT|_|PV_REPT2|_|PV_LOIS_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_RESMGR|_|DEFAULT|_|PV_CFGD|_|PV_RESMGR_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_REPORT|_|DEFAULT|_|PV_REPT|_|PV_LOIS_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_INVENTORY|_|DEFAULT|_|PV_CFGD|_|PV_INVENTORY_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_CHNL_MANAGER|_|DEFAULT|_|PV_CFGD|_|PV_CHNL_MANAGER_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_METRIC|_|DEFAULT|_|PV_CFGD|_|PV_ADMIN_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV|_|DEFAULT|_|PV_CFGD|_|PV_ADMIN_TEMP|_|DEFAULT_CONSUMER_GROUP|_|PV_ADMIN|_|PV_ADMIN_PROFILE|_|PV_CFGD|_|PV_ADMIN_TEMP|_|DEFAULT_CONSUMER_GROUP|_|



NOTES




Chapter 9: Managing Report Objects

This chapter explains how to use resmgr to manage report objects, and is made up of the following topics:

Overview

This chapter explains how to use resmgr to export, import, and different Tivoli Netcool Performance Manager object types that belong to the Report category. Report includes the following object types:

• Web users

• applications

• Scheduler


Topic Page

Overview 169

Working with Web Users 170

Working with Reporters 173

Working with Scheduler 179



Working with Web Users

This section contains the commands you can use to manage Web users. When you use resgmr to work with Web users, you work with the following object types:

• rusr

• owner

• ruprp

• ruproperty

• rugp

• linkGroupRU

Exporting Web User

Exporting report user name and properties

resmgr -export rusr -colNames "name ruprp.name ruprp.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\\Supe-rUser|_|DV_UserProfile|_|NOC|_|DV_UserResourceName|_|1|_|DV_UserShowCurrentPeriod|_|true|_|SSSW\\adminf-car|_|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|_|1 day|_|DV_UserGranularity_WEEKLY|_|30 minutes|_|DV_UserGranularity_YEARLY|_|1 day|_|DV_UserPreferenceAccess|_|true|_|DV_UserProfile|_|SLA|_|DV_UserResourceName|_|100000919|_|DV_UserShowCurrentPeriod|_|true|_|DV_UserWelcomeReporter|_|100001619|_|customerlogin|_|bt|_|customerlogo|_|BT.gif|_|customerwelcome|_|British Telecom|_|



Exporting all report users

resmgr -export rusr -colNames "dbIndex name mail type" -file $DIR/rusr.dat

# type = rusr# col = dbIndex name mail type# filter =# order =# sep = |_|# sepRec =## cmdLine = -export rusr -colNames "dbIndex name mail type"100000017|_|SSSW\\jtho|_||_|Tivoli Netcool Performance Manager USER|_|100000149|_|SSSW\\noc|_||_|Tivoli Netcool Performance Manager USER|_|100000152|_|SSSW\\coca|_||_|Tivoli Netcool Performance Manager USER|_|100000153|_|SSSW\\quallaby|_||_|Tivoli Netcool Performance Manager USER|_|100000154|_|SSSW\\business|_||_|Tivoli Netcool Performance Manager USER|_|100015938|_|SSSW\\cargill|_||_|Tivoli Netcool Performance Manager USER|_|100007838|_|SSSW\\cisco|_||_|Tivoli Netcool Performance Manager USER|_|100007863|_|SSSW\\ciscodemo|_||_|Tivoli Netcool Performance Manager USER|_|100008522|_|SSSW\\design|_||_|Tivoli Netcool Performance Manager USER|_|100008064|_|SSSW\\realtime|_||_|Tivoli Netcool Performance Manager USER|_|100009714|_|SSSW\\tt2|_||_|Tivoli Netcool Performance Manager USER|_|100009717|_|SSSW\\tt1|_||_|Tivoli Netcool Performance Manager USER|_|100009991|_|SSSW\\xtra|_||_|Tivoli Netcool Performance Manager USER|_|100009812|_|SSSW\\adminfcar|_||_|Tivoli Netcool Performance Manager USER|_|100009843|_|SSSW\\juniper|_||_|Tivoli Netcool Performance Manager USER|_|100020250|_|SSSW\\flagtelecom|_||_|Tivoli Netcool Performance Manager USER|_|100020666|_|Frankie|_|[email protected]|_|EMAIL RECIPIENT|_|

Exporting report users group

resmgr -export rugp -colNames "npath rusr.name" -file $DIR/rugp.dat

# type = rugp# col = npath rusr.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export rugp -colNames "npath rusr.name"~Users|_|SSSW\\jtho|_|~Orphans|_|SSSW\\cisco|_|~Orphans|_|SSSW\\ciscodemo|_|~Orphans|_|SSSW\\design|_|~Orphans|_|SSSW\\realtime|_|~ABC|_|SSSW\\xtra|_|~Admin Noc|_|SSSW\\adminfcar|_|~Orphans|_|SSSW\\juniper|_|~ABC|_|SSSW\\ihug|_|~ABC|_|SSSW\\tnz_noc|_|~Orphans|_|SSSW\\alcatel|_|~Orphans|_|SSSW\\ciscodev|_|~Users|_|SSSW\\timl|_|~DV [Internal Use Do Not Remove]|_|SSSW\\SuperUser|_|~Orphans|_|SSSW\\bt|_|



Importing Web User

Importing a new customer with a property

If you want to import a new customer called customer1 with a property called property1 you can use the following command.

resmgr -import rusr -colNames "name ruprp.property1:value" -line "SSSW\\\\customer1|_|value_property1"

Info : === insert : nothing ON Report User ( SSSW\\customer1 ) (exists)Info : === insert : INSERT ON property ( property1 ) (does not exist)Info : === insert : INSERT ON Ruser property ( 100000265 100008523 value_property1 ) (does not exist)

Grouping this customer

resmgr -import rugp -colNames "npath rusr.name" -line "~Group1|_|SSSW\\\\customer1"

Info : === insert : nothing ON Ruser Group ( ~Group1 ) (exists)Info : === insert : nothing ON Report User ( SSSW\\customer1 ) (exists)Info : === insert : INSERT ON Link RU/RUG ( SSSW\\customer1 Group1 ) (does not exist)

Deleting Web User

Deleting a report user (name or index)

resmgr -delete rusr -colNames "name" -line "SSSW\\\\customer1"

Info : === delete : DELETE ON Report User ( SSSW\\customer1 ) (exists)

Unlinking a report user from a group

resmgr -delete linkGroupRU -colNames "npath rusr.name" -line "~Group1|_|SSSW\\\\customer1"

Info : === delete : DELETE ON Link RU/RUG ( SSSW\\customer1 Group1 ) (exists)Info : === Update Histo : 0

Deleting just the value of the property for a report user

resmgr -delete ruproperty -colNames "name ruprp.name" -line "SSSW\\\\customer1|_|property1"

Info : === delete : DELETE ON Ruser property ( 100008524 100008523 value_property1 ) (exists)

Deleting a group of report users

resmgr -delete rugp -colNames "npath" -line "~Group1"



Info : === DELETE GROUP : ~Group1 (index = 100007970) Info : === delete : DELETE ON Ruser Group ( ~Group1 ) (exists)Info : === Update Histo : 0

Working with Reporters

This section contains the commands you can use to manage reporters and reporter stylesheets. When you use resgmr to work with reporters, you work with the following object types:

• app

• agp

• appS (report Style)

• linkGroupAPP

• linkGroupAPPS

Exporting Reporters

Exporting report styles

resmgr -export appS -sepRec "<E>" -colNames "dbIndex definition comment name type" -order "dbIndex" -filter "name(AP TopN Chart Style - Bar - DD Details - min avg max)" -file $DIR/appS.dat

# type = appS# col = dbIndex definition comment name type# filter = name(AP TopN Chart Style - Bar - DD Details - min avg max)# order = dbIndex# sep = |_|# sepRec = <E>## cmdLine = -export appS -colNames "dbIndex definition comment name type" -filter "name(AP TopN Chart Style - Bar - DD Details - min avg max)"6073|_|<chart> <appearance opaque="true"> <color r="254" g="254" b="230">background</color> <color r="0" g="0" b="0">foreground</color> <border type="titled" title="Click any bar for Details"/> </appearance> <threeDEffect depth="0" 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 size="1" style=""> <color r="0" g="170" b="255">line</color> </line> </serie>



<serie> <line size="1" style=""> <color r="0" g="0" b="255">line</color> </line> </serie> <serie> <line size="1" style=""> <color r="42" g="0" b="85">line</color> </line> </serie> <serie> <line size="1" style=""> <color r="31" g="34" b="255">line</color> </line> </serie> <serie> <line size="1" style=""> <color r="234" g="208" b="229">line</color><text> <font name="arial" size="9" style="plain"/> <text-advanced alignment="center" orientation="horizontal" rota-tion="0"/> </text> <appearance opaque="false"> <color r="102" g="255" b="255">background</color> <color r="0" g="51" b="51">foreground</color> <border type="empty"/> </appearance> <location 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 - DD Details - min avg max|_|0|_|<E>



Exporting report group stylesheets

resmgr -export agp -colNames "npath appS.name" -file $DIR/agp_appS.dat

# type = agp# col = npath appS.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export agp -colNames "npath appS.name"~AP Styles|_|AP TopN Chart Style - Bar - DD Details - min avg max|_|~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 group

resmgr -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|_|Interface Volume Resource Detail Chart|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Volume Resource|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Volume Resource Threshold - Inbound Volume (octets)|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Volume Resource Threshold - Inbound Throughput (bps)|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Volume Resource Threshold - Outbound Volume (octets)|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Volume Resource Threshold - Outbound Throughput (bps)|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Utilization Resource Detail Chart|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Utilization Resource Threshold - Inbound Utilization (percent)|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Utilization Resource Threshold - Inbound Throughput (bps)|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Utilization Resource Threshold - Outbound Utilization (percent)|_|



7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Utilization Resource Threshold - Outbound Throughput (bps)|_|7385|_|~AP MIB-II Pack~Interface~Utilization Metrics|_|Interface Utilization Group|_|7396|_|~AP MIB-II Pack~Interface~Availability Metrics|_|Interface Availability Resource Detail Chart|_|7396|_|~AP MIB-II Pack~Interface~Availability Metrics|_|Interface Availability Resource Threshold - Inbound Loss|_|7396|_|~AP MIB-II Pack~Interface~Availability Metrics|_|Interface Availability Resource Threshold - Availability|_|

Exporting report

resmgr -export app -sepRec "<E>" -colNames "dbIndex name comment url type data" -order "dbIndex" -file $DIR/app.dat

# type = app# col = dbIndex name comment url type data# filter =# order = dbIndex# sep = |_|# sepRec = <E>## cmdLine = -export app -colNames "dbIndex name comment url type data"4250|_|GST - IPSec - Phase-1 Volume and Throughput (second level)|_|AP IPSec generic pack member reporter|_|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=""groupSummaryTableMediator.formula5.metrics=2307""groupSummaryTable.formula6.stats.labels=""UserWelcome.text=Welcome $USERPROPERTY:DV_UserName""groupSummaryTableMediator.formula1.metrics=2301"....."UserLogo.link=""groupSummaryTableMediator.formula2.stats=sum""groupSummaryTableMediator.formula4.stats=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 app

You must use the name column when importing new applications. By default, dbIndex is taken from the DesignSequences, comment, data, owner, alias is null, type =0, typeR=Reporter, url = none, user=UNIX user, and date=current date.


• url

• data type

New appS

You must use the name column when importing new application style sheets. By default, dbIndex is taken from the DesignSequences, comment, definition is null, and type =0.


• definition

• comment

• type

Updating app and appS

When updating existing applications and application style sheets, you must use the dbIndex or name columns, and the columns to be modified.

Importing the file reportStyle.txt after modifying it

resmgr -import appS -sepRec "<E>" -colNames "dbIndex definition comment name type" -mode insert -file $DIR/appS.dat

Check the output for errors. If there is a major error, such as a corrupt file, it is reported on the last line of the output.

Copying a report (only the name is modified)

Use the nop keyword instead of dbIndex because dbIndex uniquely identifies a report. Another method is to manually modify the dbIndex in the export file.

resmgr -import app -sepRec "<E>" -colNames "nop name comment url type data" -file /tmp/report.txt




Importing application group

resmgr -import agp -colNames "npath app.name" -line "~AP MIB-II Pack~Interface~TEST1|_|Interface Availability Resource Threshold - Availability|_|"

Info : === insert : INSERT ON Application Group ( ~AP MIB-II Pack~Interface~TEST1 ) (does not exist)Info : === insert : nothing ON Application ( Interface Availability Resource Threshold - Availability ) (exists)Info : === insert : INSERT ON Link App/AppGroup ( Interface Availability Resource Threshold - Availability TEST1 ) (does not exist)Info : === Update Histo : 0

Importing application group style sheets

resmgr -import agp -colNames "npath appS.name" -line "~AP MIB-II Pack~Interface~TEST1|_|AP TS Chart Style - Line - White - sum|_|"

Info : === insert : nothing ON Application Group ( ~AP MIB-II Pack~Interface~TEST1 ) (exists)Info : === insert : nothing ON report style ( AP TS Chart Style - Line - White - sum ) (exists)Info : === insert : INSERT ON report style Link ( AP TS Chart Style - Line - White - sum TEST1 ) (does not exist)Info : === Update Histo : 0

Deleting Reporters and Reporter Stylesheets

You must use the name column when importing new applications. Mandatory cols for app or appS : dbIndex or name

Mandatory cols for agp : dbIndex or npath

Deleting report stylesheets

resmgr -delete appS -colNames "name" -line "Import new report style"

Info : === delete : nothing ON report style ( Import new report style ) (does not exist)

Deleting report

resmgr -delete app -colNames "name" -line "New GST"

Info : === delete : nothing ON Application ( New GST ) (does not exist)

Deleting group report

resmgr -delete agp -colNames "npath" -line "~AP MIB-II Pack~Interface~TEST1"

Info : === DELETE GROUP : ~AP MIB-II Pack~Interface~TEST1 (index = 100008525) Info : === delete : DELETE ON Application Group ( ~AP MIB-II Pack~Interface~TEST1 ) (exists)Info : === Update Histo : 0



Unlinking a report from a report group

resmgr -delete linkGroupAPP -colNames "npath app.name" -line "~AP MIB-II Pack~Interface~TEST1|_|Interface Availability Resource Threshold - Availability"

Info : === delete : DELETE ON Link App/AppGroup ( Interface Availability Resource Threshold - Availability TEST1 ) (exists)Info : === Update Histo : 0

Unlinking a report style from a report group

resmgr -delete linkGroupAPPS -colNames "npath appS.name" -line "~AP MIB-II Pack~Interface~TEST1|_|AP TS Chart Style - Line - White - sum|_|"

Info : === delete : DELETE ON report style Link ( AP TS Chart Style - Line - White - sum TEST1 ) (exists)Info : === Update Histo : 0

Working with Scheduler

This section contains the commands you can use to manage Scheduler. When you use resgmr to work with Scheduler, you work with the sched object type.

Exporting Scheduler

Exporting general information (see registry section)

resmgr -export regisDV -colNames "path name value type" -filter "path(DATAVIEW.SCHEDULER*)" -file $DIR/regisDV.dat

DATAVIEW.SCHEDULER.MAS-TER.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.LATE-DATA.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.MAS-TER.CHECK_HEARTBEAT_AFTER_N_CRCN|_|CHECK_HEARTBEAT_AFTER_N_CRCN|_|10|_|0|_|



DATAVIEW.SCHEDULER.MASTER.EMAIL.HOST_SERVER|_|HOST_SERVER|_|mail2.quall-aby.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/silver-stream/SchedulerNFS|_|1|_|DATAVIEW.SCHEDULER.MASTER.FTP.BASE_DIRECTORY|_|BASE_DIRECTORY|_|/export/home/sil-verstream/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 information

resmgr -export sched -colNames "dbIndex name frequency state status start_DATE end_DATE type" -file $DIR/sched.dat

# type = sched# col = dbIndex name frequency state status start_DATE end_DATE type# filter =# order =# sep = |_|# sepRec = <E>## cmdLine = -export sched -colNames "dbIndex name frequency state status start_DATE end_DATE type"49000001|_|DAILY|_|DAILY|_|Assigned|_|http://pvdemo1.quall-aby.com:8080/DV41|_|10/06/2003 04:00|_|01/01/1970 04:00|_|DVCR|_|<E>49000001|_|DAILY|_|DAILY|_|Suspended|_|Suspended|_|10/06/2003 04:00|_|01/01/1970 04:00|_|DVCR|_|<E>49000001|_|DAILY|_|DAILY|_|Suspended|_|Suspended|_|10/06/2003 04:00|_|01/01/1970 04:00|_|DVCR|_|<E>49000003|_|MONTHLY|_|MONTHLY|_|Suspended|_|Suspended|_|10/07/2003 04:00|_|01/01/1970 04:00|_|DVCR|_|<E>49000001|_|DAILY|_|DAILY|_|Suspended|_|Suspended|_|10/08/2003 04:00|_|10/09/2003 04:00|_|DVCR|_|<E>49000001|_|DAILY|_|DAILY|_|Suspended|_|Suspended|_|10/09/2003 04:00|_|01/01/1970 04:00|_|DVCR|_|<E>49000002|_|WEEKLY|_|WEEKLY|_|Suspended|_|Suspended|_|10/17/2003 04:00|_|01/01/1970 04:00|_|DVCR|_|<E>

Exporting Scheduler consolidated report

resmgr -export sched -colNames "name app.name" -file $DIR/sched_app.dat

# type = sched# col = name app.name# filter =# order =# sep = |_|# sepRec = <E>#



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

resmgr -export sched -colNames "name app.name rusr.name rusr.mail rusr.type" -file $DIR/sched_mail.dat

# type = sched# col = name app.name rusr.name rusr.mail rusr.type# filter =# order =# sep = |_|# sepRec = <E>## cmdLine = -export sched -colNames "name app.name rusr.name rusr.mail rusr.type"DAILY|_|Daily Business Summary|_|Frankie|_|[email protected]|_|EMAIL RECIPI-ENT|_|<E>DAILY|_|Daily High Level Summary|_|Frankie|_|[email protected]|_|EMAIL RECIPI-ENT|_|<E>DAILY|_|Tims Test Task|_|Tim|_|[email protected]|_|EMAIL RECIPIENT|_|<E>WEEKLY|_|Mcer|_|Marcus|_|[email protected]|_|EMAIL RECIPIENT|_|<E>MONTHLY|_|Monthly SLA Report whole customers|_|Marcus|_|[email protected]|_|EMAIL RECIPIENT|_|<E>DAILY|_|Essai devoteam|_|fama|_|[email protected]|_|EMAIL RECIPIENT|_|<E>DAILY|_|Sales|_|FAMA|_|[email protected]|_|EMAIL RECIPIENT|_|<E>DAILY|_|Sales|_|FDOU|_|[email protected]|_|EMAIL RECIPIENT|_|<E>

Importing Scheduler

Use the export file , modify it and reimport it with the same column names.

Deleting Scheduler

resmgr -delete sched -colNames "name"



NOTES


Chapter 10: Managing History Table and Sequence Objects

This chapter explains how to use resmgr to manage history table and sequence objects, and is made up of the following topics:

Overview


Important: IBM recommends you work with IBM Support when working with history tables.

Working with History Tables

This section contains the commands you can use to manage history tables. When you use resgmr to work with history tables, you work with the following object types:

• calH

• frmH

• thrdvH

• eltH

• seH

• segpreqH

• appH

• segpH

• egpH

In addition, history tables includes the following object types:

• dte: this object type, date of the modification, includes the same columns as the dte found in non-historical tables.

• action: this object type is specific to the history table and is only accessible with the seH table. The available values include:

Topic Page

Overview 183

Working with History Tables 183

Working with Sequences 187



– I for inserted

– D for deleted

– U for updated

Exporting History Tables

You cannot link from a history object type to a similar object type in a non-history table.

Exporting subelement history table

resmgr -export seH -colNames "dbIndex invariant elt.name name label instance state origin date_DATE action dte_DATE" -file $DIR/seH.dat

# type = seH# col = dbIndex invariant elt.name name label instance state origin date_DATE action dte_DATE# filter = # order = # sep = |_|# sepRec = ## cmdLine = -export seH -colNames "dbIndex invariant elt.name name label 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/2002 01:16|_|I|_|04/10/2002 01:16|_|100000222|_||_|Delete_100000165_192.168.3.238|_|192.168.127.1_If<6>|_|"192.168.127.1_IF: 6 (""16/1"") (1000Mbps)"|_|If<6>|_|on|_|resmgr|_|04/15/2002 20:10|_|U|_|04/15/2002 20:10|_|100000222|_||_|Delete_100000165_192.168.3.238|_|Delete_100000222_192.168.127.1_If<6>|_|"192.168.127.1_IF: 6 (""16/1"") (1000Mbps)"|_|Delete_100000222_If<6>|_|off|_|inventory|_|11/20/2002 00:58|_|U|_|11/20/2002 00:58|_|100000223|_||_|192.168.127.2|_|192.168.127.2_If<23>|_|192.168.127.2_IF: 23 ("Fa0/22") (0Mbps)|_|If<23>|_|on|_|inventory|_|04/10/2002 01:16|_|I|_|04/10/2002 01:16|_|100000223|_||_|192.168.127.2|_|192.168.127.2_If<23>|_|"192.168.127.2_IF: 23 (""Fa0/22"") (0Mbps)"|_|If<23>|_|on|_|resmgr|_|04/15/2002 20:10|_|U|_|04/15/2002 20:10|_|100000223|_||_|192.168.127.2|_|192.168.127.2_If<23>|_|192.168.127.2_IF: 23 (100Mbps)|_|If<23>|_|on|_|inventory|_|12/04/2002 23:38|_|U|_|12/04/2002 23:38|_|100000223|_||_|192.168.127.2|_|192.168.127.2_If<23>|_|192.168.127.2_IF: 23 (100Mbps)|_|If<23>|_|on|_|resmgr|_|05/28/2003 18:47|_|U|_|05/28/2003 18:47|_|100000224|_||_|dev3.quallaby.com|_|dev3.quallaby.com_If<1>|_|dev3_IF: 1 (10Mbps)|_|If<1>|_|on|_|inventory|_|04/10/2002 01: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/2002 20:10|_|U|_|04/15/2002 20:11|_|100000225|_||_|Delete_100000165_192.168.3.238|_|192.168.127.1_If<82>|_|192.168.127.1_IF: 82 ("4/28") (100Mbps)|_|If<82>|_|on|_|inventory|_|04/10/2002 01:16|_|I|_|04/10/2002 01:16|_|100000225|_||_|Delete_100000165_192.168.3.238|_|192.168.127.1_If<82>|_|"192.168.127.1_IF: 82 (""4/28"") (100Mbps)"|_|If<82>|_|on|_|resmgr|_|04/15/2002 20:10|_|U|_|04/15/2002 20:10|_|



Exporting subelement history table with link to element in the past

You need to manually locate the element within the output. You can also use the -histoDate 1 option to insert into or update a history table.

Note: The subelement history table (seH) is linked to element (elt) and not to the element history table (eltH.)

resmgr -export seH -colNames "dbIndex invariant hostIdx name label instance state origin date_DATE action dte_DATE" -file $DIR/seH_elt.dat

# type = seH# col = dbIndex invariant hostIdx name label instance state origin date_DATE action dte_DATE# filter = # order = # sep = |_|# sepRec = ## cmdLine = -export seH -colNames "dbIndex invariant hostIdx name label instance state origin date_DATE action dte_DATE" 100000222|_||_|100000165|_|192.168.127.1_If<6>|_|192.168.127.1_IF: 6 ("16/1") (1000Mbps)|_|If<6>|_|on|_|inventory|_|04/10/2002 01:16|_|I|_|04/10/2002 01:16|_|100000222|_||_|100000165|_|192.168.127.1_If<6>|_|"192.168.127.1_IF: 6 (""16/1"") (1000Mbps)"|_|If<6>|_|on|_|resmgr|_|04/15/2002 20:10|_|U|_|04/15/2002 20:10|_|100000222|_||_|100000165|_|Delete_100000222_192.168.127.1_If<6>|_|"192.168.127.1_IF: 6 (""16/1"") (1000Mbps)"|_|Delete_100000222_If<6>|_|off|_|inventory|_|11/20/2002 00:58|_|U|_|11/20/2002 00:58|_|100000223|_||_|100000167|_|192.168.127.2_If<23>|_|192.168.127.2_IF: 23 ("Fa0/22") (0Mbps)|_|If<23>|_|on|_|inventory|_|04/10/2002 01:16|_|I|_|04/10/2002 01:16|_|100000223|_||_|100000167|_|192.168.127.2_If<23>|_|"192.168.127.2_IF: 23 (""Fa0/22"") (0Mbps)"|_|If<23>|_|on|_|resmgr|_|04/15/2002 20:10|_|U|_|04/15/2002 20:10|_|100000223|_||_|100000167|_|192.168.127.2_If<23>|_|192.168.127.2_IF: 23 (100Mbps)|_|If<23>|_|on|_|inventory|_|12/04/2002 23:38|_|U|_|12/04/2002 23:38|_|100000223|_||_|100000167|_|192.168.127.2_If<23>|_|192.168.127.2_IF: 23 (100Mbps)|_|If<23>|_|on|_|resmgr|_|05/28/2003 18:47|_|U|_|05/28/2003 18:47|_|100000224|_||_|100000196|_|dev3.quallaby.com_If<1>|_|dev3_IF: 1 (10Mbps)|_|If<1>|_|on|_|inventory|_|04/10/2002 01:16|_|I|_|04/10/2002 01:16|_|100000224|_||_|100000196|_|dev3.quallaby.com_If<1>|_|dev3_IF: 1 (10Mbps)|_|If<1>|_|on|_|resmgr|_|04/15/2002 20:10|_|U|_|04/15/2002 20:11|_|100000225|_||_|100000165|_|192.168.127.1_If<82>|_|192.168.127.1_IF: 82 ("4/28") (100Mbps)|_|If<82>|_|on|_|inventory|_|04/10/2002 01:16|_|I|_|04/10/2002 01:16|_|100000225|_||_|100000165|_|192.168.127.1_If<82>|_|"192.168.127.1_IF: 82 (""4/28"") (100Mbps)"|_|If<82>|_|on|_|resmgr|_|04/15/2002 20:10|_|U|_|04/15/2002 20:10|_|100000225|_||_|100000165|_|Delete_100000225_192.168.127.1_If<82>|_|"192.168.127.1_IF: 82 (""4/28"") (100Mbps)"|_|Delete_100000225_If<82>|_|off|_|inven-tory|_|11/20/2002 00:58|_|U|_|11/20/2002 00:58|_|100000226|_||_|100000168|_|192.168.127.3_If<9>|_|192.168.127.3_IF: 9 ("Fa0/8") (0Mbps)|_|If<9>|_|on|_|inventory|_|04/10/2002 01:16|_|I|_|04/10/2002 01:16|_|100000226|_||_|100000168|_|192.168.127.3_If<9>|_|"192.168.127.3_IF: 9 (""Fa0/8"") (0Mbps)"|_|If<9>|_|on|_|resmgr|_|04/15/2002 20:10|_|U|_|04/15/2002 20:10|_|100000226|_||_|100000168|_|192.168.127.3_If<9>|_|192.168.127.3_IF: 9 (0Mbps)|_|If<9>|_|on|_|inventory|_|12/04/2002 23:38|_|U|_|12/04/2002 23:38|_|100000227|_||_|100000179|_|192.168.3.62_If<30>|_|192.168.3.62_IF: 30 ("Fa29") (100Mbps)|_|If<30>|_|on|_|inventory|_|04/10/2002 01:16|_|I|_|04/10/2002 01:16|_|



Exporting element state and comment history

resmgr -export eltH -colNames "name state comment date_DATE action"

# resmgr -export eltH -colNames "name state comment date_DATE action"# type = eltH# col = name state comment date_DATE action# filter = # order = # sep = |_|# sepRec = # rule = # filterRule = ## cmdLine = -export eltH -colNames "name state comment date_DATE action" default|_|on|_||_|05/29/2008 20:00|_|I|_|DL.1|_|on|_|PROVISO_MONITORING|_|05/30/2008 12:21|_|I|_|10.127.78.2-1|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.77.7|_|on|_||_|06/02/2008 11:21|_|I|_|10.127.77.6|_|on|_||_|06/02/2008 11:23|_|I|_|

Exporting subelement state and ulabel history

resmgr -export seH -colNames "name state ulabel date_DATE action"

# resmgr -export seH -colNames "name state ulabel date_DATE action"# type = seH# col = name state ulabel date_DATE action# filter = # order = # sep = |_|# sepRec = # rule = # filterRule = ## cmdLine = -export seH -colNames "name state ulabel date_DATE action" DL.1_<NULL>|_|on|_||_|05/30/2008 12:21|_|I|_|DL.1_<NULL>|_|on|_||_|05/30/2008 12:21|_|U|_|10.127.78.2-1_CSC<NULL>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<69>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<34>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<41>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.2-1_SLS<NULL>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<10>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<45>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<2>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<8>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<9>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<86>|_|on|_||_|06/01/2008 14:29|_|I|_|10.127.78.3-1_If<20>|_|on|_||_|06/01/2008 14:29|_|I|_|

Importing and Deleting

Contact IBM Support for assistance with importing or deleting history tables.



Working with Sequences

This section contains the commands you can use to manage sequences. When you use resgmr to work with sequences, you work with the following object types:

• DesignIndex

• ResourcesIndex

With these object types, you can find and modify the start of indexes for formulas and resources, using the following two resmgr options, only:

• -export to debug options

• -import for -line and debug options

Find and modify the start of indexes for formulas

resmgr -export DesignIndex

5000

resmgr -import DesignIndex -line 500000

Find and modify the start of indexes for resources

resmgr -export ResourcesIndex

200000000

resmgr -import ResourcesIndex -line 1000000

Warnings:

• Each time you export, one index number is used or increased.

• For resources, the default start index is 200000000. In most cases it is not necessary to modify it.



NOTES


Chapter 11: Configuring Thresholds

This chapter explains how to use the resmgr command to configure thresholds, and is made up of the following topics:

Overview

This chapter explains how to use resmgr to configure thresholds. Thresholds are Tivoli Netcool Performance Manager object types that belong to the Design category.

Before using the commands in this chapter, review the information in Chapter 4, Managing Tivoli Netcool Performance Manager Objects. Additional resmgr commands for managing thresholds can be found in Working with Thresholds on page 135 of Chapter 7, Managing Design Objects.

Thresholds

This section defines thresholds and the threshold options. There are two types of thresholds in Tivoli Netcool Performance Manager:

• Default threshold: is deployed against a metric, for any group or resource.

• Resource threshold: is deployed against a metric/resource, for any group.

• Group threshold: is deployed against a metric/group, for any resource.

• Group/resource threshold: is deployed against a specific metric/group/resource combination.

Topic Page

Overview 189

Thresholds 189

Deploying Thresholds 191

Working with Thresholds 195

Setting Thresholds 200

Setting Traps 204

Threshold Troubleshooting Scenarios 207



Threshold Options

The following table lists threshold options:

Name Definition

idxMetric|fgp.nName Metric Id. Prop: Not Null, not 0

idxGroup|segp.name Sub-Element Group Id.Prop: Not null, defaults to 0

idxResource|se.name Sub-Element Resource Id. Prop: Not null, defaults to 0

dteDate The date and time the action (STR_ACTION) takes effect. Actions cannot be applied in the past and only take effect on the hour. The value is in seconds since January 1, 1970 GMT.Prop: Not null

mode Mode of the threshold: 1 = Under, 2 = Over, 3 = BandProp: Not null

thrStat Define which statistic will be used by the CME to calculate the threshold information:

0=raw(default), 1=min, 2=max, 3=avg, 4=sum, 5=countProp: Not null

thrCalc The calculation to be used to determine the value of DBL_BRST_MAX_PCT_OVER and DBL_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 percentage over/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 the metric exceeds the threshold.

brstWrnngTime Time limit for the warning period threshold in seconds

brstGenEvent Indicates if Tivoli Netcool Performance Manager has to 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



Deploying Thresholds

This section explains the different threshold deployment scenarios.

Threshold Deployment Against Groups and Resources

Thresholds 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 one threshold value X, and resources in CoS=Gold will have one threshold value X.

Figure 2: illustrates that deploying a latency threshold of 100 ms for Platinum and 150 ms for Gold is not possible by group

PrdWrnngTime Time limit for the warning period threshold in seconds

PrdPeriod Define the period for burst and period thresholds:

1 = Day / 2 =Week / 3 = Month / 4 = All

“All" period means that the CME will use the period of the aggregation tables

PrdGenEvent Indicates if Tivoli Netcool Performance Manager has to generate events for the period threshold. 0=no, 1=yes

Name Definition



Figure 2: Grouping Structure and Threshold Configuration.

Two different values are required for the same metric (latency), based on one grouping structure (CoS), and that it is required to have also a view of threshold violation following another grouping structure (Location).

Deploying "Non-differentiated" Thresholds

Non-differentiated thresholds is the preferred deployment method to follow because it does not involve resources (only metrics;) therefore, it is less CPU and memory intensive for the Tivoli Netcool Performance Manager Data Channel and is easier to provision.

If this method cannot be applied, you can apply the alternative method described in section Deploying Differentiated Thresholds on page 194. This method is more CPU and RAM intensive for Data Channel and requires usage of the CLI because of the number of thresholds to position.

You can have a uniform or non-differentiated threshold. For example, latency is differentiated by CoS (see Figure 2:) but Inbound Loss threshold is not: 1% for every resource in the system.



Figure 3: Non-Differentiated Threshold Deployment

IBM recommends deploying thresholds at the metric level only, with no link to any resource. This means attaching thresholds to database metric identifier (mid) without any attachment to resource identifier (rid) or group identifier (gid).

Note: You can also use the Tivoli Netcool Performance Manager DataMart Resource Editor to deploy non-differentiated thresholds. See Chapter 1, “Using Resource Editor” in the IBM Tivoli Netcool Performance Manager: Operation Guide for details.

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 or Bulk inventory, there is nothing to process because, as soon as the formula (for example, Inbound Loss, percent) is collected/imported against that sub-element, that threshold is attached to the formula. This configuration can be considered as a default configuration for the "Inbound Loss" threshold.

In Figure 3:, R1 is moving from Boston to New York. Its Inbound Loss threshold is not supposed to change.



You can change the value of the threshold for only one resource. For example, R3 becomes an exception to the rule/default value (to reflect a specific customer commitment) and Inbound Loss threshold is changed from 1 to percent.

In this case, IBM recommends to use the Resource Editor module (or Resource Manager) for creating a new threshold attached to the metric and the resource.

Threshold attached to metric identifier: “Inbound Loss” Thr = 1 percent (no resource attachment used) and threshold attached to (mid, rid): “Inbound Loss” Thr = 1 percent for R3, (no resource attachment used). The (mid, rid) setting overwrites the default metric identifier setting.

Deploying Differentiated Thresholds

If you cannot apply the non-differentiated threshold deployment, then you can apply the differentiated threshold deployment. This method is more CPU and RAM intensive for Tivoli Netcool Performance Manager Data Channel and requires usage of the CLI because of the number of thresholds to position.

Figure 4: Differentiated Threshold Deployment

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 to gid.

The Resource Editor module is not usable for deployment, but more for testing and prototyping, before deployment. This is due to the number of lines that are required in this interface. Each resource (network interface) x metric (latency) generates one line in the GUI, which can be unmanageable.




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 with Resource Manager (from a provisioning system): every time a new resource is provisioned by Resource Manager, this command line should be launched, so that threshold is configured when the resource is provisioned.

Every time a threshold is attached or updated at a resource level, IBM recommends to duplicate it as a property, storing the same value for the property. This overcomes any Tivoli Netcool Performance Manager DataView issues such as it being impossible to display a threshold value in RST/RTT/TOP N (as a property=column in the table) and it being impossible follow the history of the threshold value within the Property History tables. It could also be impossible to display a threshold value as simple text (in PVRcLabels). Populating a shadow property replicating this threshold and its changes helps solve these issues.

Working with Thresholds

This section explains how to work with thresholds. It contains information about exporting, importing, and deleting thresholds.

Exporting Thresholds

The following are examples of exporting thresholds.

Example 1

Output appears. For example:

# type = thrdv# col = fgp.nName segp.npath se.name mode thrStat# filter = # order = # sep = |_|# sepRec = ~FORMULA|_|~NOC Reporting~Network Management~BasicInterface & ExtendedInter-face|_|192.168.3.252_<NULL>|_|1|_|0|_|

Example 2

Export of the idxGroup and idxResource fields. The thrsh_desc.idx_resource and thrsh_desc .idx_group columns have a value of 0.




# type = thrdv# col = fgp.nName idxGroup idxResource mode thrStat# filter = # order = # sep = |_|# sepRec = ~FORMULA|_|0|_|0|_|1|_|0|_|

Example 3

Export of the segp.npath and se.name fields. The thrsh_desc.idx_resource and thrsh_desc .idx_group columns have a value of 0.


# type = thrdv# col = fgp.nName segp.npath se.name mode thrStat# filter = # order = # sep = |_|# sepRec = ~FORMULA|_||_||_|1|_|0|_|

Deleting Thresholds

To delete a line of the threshold table, you need to provide the value of the columns in the table.

Deleting by Indices


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


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 Thresholds

The following are examples of importing thresholds.

Example 1


Info : === insert : INSERT ON Threshold (1000401 1000196 ) (does not exist)

Verifying the import




# type = thrdv# col = fgp.nName segp.npath se.name mode thrStat# filter = # order = # sep = |_|# sepRec = ~FORMULA|_|~NOC Reporting~Network Management~BasicInterface & ExtendedInter-face|_|192.168.3.62_<NULL>|_|1|_|0|_|

Example 2

Import without specifying resource or group:



Verifying the import in index form

Export of the resource and group in index form.


# type = thrdv# col = idxMetric idxGroup idxResource mode thrStat# filter = # order = # sep = |_|# sepRec = 1000401|_|0|_|0|_|1|_|0|_|

Verifying the import in name form

Export of the resource and group in name form




# 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




Export of the resource and group in index form.


# type = thrdv# col = idxMetric idxGroup idxResource mode thrStat# filter = # order = # sep = |_|# sepRec = 1000402|_|0|_|0|_|1|_|0|_|

Verifying the Import

Export of the resource and group in name form


# type = thrdv# col = fgp.nName segp.npath se.name mode thrStat# filter = # order = # sep = |_|# sepRec = ~FORMULA1|_||_||_|1|_|0|_|



Setting Thresholds

This section explains how to set and verify thresholds against groups and resources.

Identifying Formula Indexes

You need to identify the index of the formula to be used as follows:

1. Enter the following command to export the list of formulas and indexes:

resmgr -export frm -colNames "name dbIndex"

2. Choose the Generic formula for the metric to which you want to apply the threshold. Thresholds need to be applied to generic formulas because this is the proper database index under which the data will be stored.

3. Identify the index of the group or resource to be used in thresholding.

4. Enter the following command to export the list of sub-element 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 calendar and time zone have been applied at or above the group, to the specific sub-element, or to the group that a sub-element is in.

— The group, resource, or group the specific sub-element 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 thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime 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 Threshold

To verify the threshold you need to export the threshold as follows:

resmgr -export thrdv -colNames "idxMetric idxGroup mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime prdPeriod prdGenEvent" -filter "idxMetric(2210)"

Output appears telling you that the threshold is in the database properly. For example:



2210|_|1001033|_|2|_|0|_|0|_|1000000|_|2000000|_|1000000|_|0|_|0|_|0|_|2000|_|1000|_|900|_|900|_|1|_|0|_|

Setting a Threshold against a Group (name)


resmgr -import thrdv -colNames "idxMetric segp.npath mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime prdPeriod prdGenEvent" -line "2210|_|~NOC Reporting~Network Management~Unknown_Area~All Techs|_|2|_|0|_|0|_|1000000|_|2000000|_|1000000|_|0|_|0|_|0|_|2000|_|1000|_|900|_|900|_|1|_|0"

Output appears. For example, if the threshold does not exist in the database,

Info : === insert : INSERT ON Threshold ( 2210 0 ) (does not exist)

If the threshold does exist in the database:

Info : === insert : UPDATE ON Threshold ( 2210 0 ) (exists)



To verify the threshold you need to export the threshold:

resmgr -export thrdv -colNames "idxMetric segp.npath mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel 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)


resmgr -import thrdv -colNames "idxMetric idxResource mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime 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 database








To verify the threshold you need to export the threshold:

resmgr -export thrdv -colNames "idxMetric idxResource mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime prdPeriod prdGenEvent" -filter "idxMetric(2210)"


2210|_|1000660|_|2|_|0|_|0|_|1000000|_|2000000|_|1000000|_|0|_|0|_|0|_|2000|_|1000|_|900|_|900|_|1|_|0|_|

Setting a Threshold against a Resource (name)


resmgr -import thrdv -colNames "idxMetric se.name mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime 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.







resmgr -export thrdv -colNames "idxMetric se.name mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime 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 instance name)SQLPLUS> select * from thrsh_desc where idx_metric = '2210' and idx_resource = '1000245';

Output appears to tell you that the threshold is in the database properly. For example:

2210|_|zelkona.quallaby.com_Interface<1>|_|2|_|0|_|0|_|1000000|_|2000000|_|1000000|_|0|_|0|_|0|_|2000|_|1000|_|900|_|900|_|1|_|0|_|



Setting a Future Threshold

This section explains how to set a future threshold.

1. Follow steps 1 to 5 as detailed in the section Setting Thresholds on page 200.

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 Keplerian element 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 mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel 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):


If the threshold does exist:

Info : === insert : UPDATE ON Threshold ( 2210 0 ) (exists)If the threshold does exist in the database.



Verify the threshold by exporting the threshold:

Resmgr -export thrdv -colNames "idxMetric dteDate idxGroup mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime prdPeriod prdGenEvent" -filter "idxMetric(2210)"


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. Time is 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 sub-element group or specific sub-elements in the reports after the time has passed to verify that the threshold has taken effect.



Setting Traps

This section explains how to set burst and period traps.

Setting Burst Traps

Enter the following command to set a threshold for a metric:


In this example, a threshold is set for metric 2210 against the group with the ID of 1001033. The Burst Generate Event flag has also been set.


Verifying the Burst Trap

To 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 Open Topology 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:

* Database hostname — The name of the database host. The default value is localhost.

* Port — The port number used for communication with the database. The default value is 1521.

* Database user — The username used to access the database. The default value is pv_admin.

* Database Password — The password for the database user account. For example, pv.

* SID — The SID for the database. The default value is PV.

Click Finish.

8. In the Logical View, click the DataChannels folder.

9. Click the DataChanneln component, where n is the appropriate DataChannel number.

10. Click the Complex Metric Engine n.m component, where n.m is the appropriate DataChannel and sub-channel number.

11. In the Properties tab, search for the following parameter:



Trap destination=value

12. Verify that the value is set to the IP address and port for your snmptrap daemon (for example, "Trap destination=192.168.69.30:162").

13. When you are satisfied with your settings, select Topology > Save topology to save the topology.

14. Select Run > Run Installer and pass it the newly configured topology.

15. 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 to take effect. To restart the CME, do the following:

1. Change to the Data Channel home directory. For example, /opt/datachannel.

2. Enter the following command to change to the “bin” directory:

cd bin

3. Run the following command (for example, channel 1). For a different channel, change the channel number.

dccmd -action stop -channel 1 -application cme

4. Run the following command to start the CME for channel 1:

dccmd -action start -channel 1 -application cme

5. Ensure that the CME is running:

dccmd -action status -channel 1 -application cme

Note: You can also use the ddcmd command with the bounce argument to stop and start the CME, as follows: dccmd -action bounce -channel 1 -application cme. Additionally, you can use a shorter version of the dccmd command, as follows: dccmd bounce cme.1 For more information on using the dccmd command, invoke the dccmd command with the -usage option.

Setting Period Traps

Enter the following command to set a threshold for a metric:

Resmgr -import thrdv -colNames "idxMetric idxGroup mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent prdCrtclLevel prdWrnngLevel prdCrtclTime prdWrnngTime 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. The Period Generate Event flag has also been set.




Verifying the Period Trap

Follow the steps in the sections entitled Verifying the Burst Trap on page 204 and Restarting the Complex Metric Engine (CME) on page 205.



Threshold Troubleshooting Scenarios

This section describes different threshold troubleshooting scenarios.

Export Scenario 1

Export a threshold configured against mid (metric identifier) and gid (group identifier) and display metrics and group IDs (not name) - NO HISTORY (last values)

resmgr -export thrdv -colNames "idxMetric idxGroup mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent"

type = thrdvcol = idxMetric idxGroup mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrn-ngLevel 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) and gid (group identifier) and display metric and group name (not IDs) - NO HISTORY (last values)

resmgr -export thrdv -colNames "fgp.nName segp.npath mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent"

# type = thrdv# col = fgp.nName segp.npath mode thrStat thrCalc thrCalcValue brstCrtclLevel brst-WrnngLevel brstCrtclTime brstWrnngTime brstGenEvent# filter = # order = # sep = |_|# sepRec = ~AP~PROVISO~Targets~SNMP Availability (percent) (avg last hour)|_|~NOC Report-ing|_|1|_|3|_|0|_||_|75|_||_||_||_||_|~AP~PROVISO~Targets~SNMP Response Time (ms) (avg last hour)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|5000|_||_||_||_||_|~AP~Generic~Frame Relay~Outbound CIR Utilization (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Frame Relay~Inbound CIR Utilization (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Frame Relay~Outbound Discard Eligible (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Frame Relay~Inbound Discard Eligible (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Outbound Queue Drops (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Inbound Queue Drops (percent)|_|~NOC Report-ing|_|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 Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~CPU Utilization (percent) (avg last 5 minutes)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Outbound Utilization (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Inbound Utilization (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Outbound Loss (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Inbound Loss (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~IP~IP Fragmentation (percent)|_|~NOC Report-ing|_|2|_|3|_|0|_||_|2|_||_||_||_||_|



Export Scenario 3

Export a threshold configured against mid (metric identifier) and gid (group identifier) and display metric and group name (not IDs) - Filter on formula - NO HISTORY (last values)

resmgr -export thrdv -colNames "fgp.nName segp.npath mode thrStat thrCalc 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 Report-ing|_|1|_|3|_|0|_||_|~AP~Generic~Universal~Availability (percent)|_|~NOC Reporting|_|2|_|3|_|0|_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Report-ing|_|2|_|3|_|0|_||_|

Export Scenario 4

In this scenario, you can troubleshoot an issue related to threshold detection. For example, thresholds might be correctly detected on the 17th of the month, but they might not be detected on the 18th.

Export a threshold configured against mid(metric identifier) and gid(group identifier) and display metric and group name (not Ids). Filter on formula Availability - WITH HISTORY (thrdvH instead of thrdv) and ACTION

resmgr -export thrdvH -colNames "fgp.nName segp.npath dte_DATE action mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent" -filter "fgp.nName(*Availability*)"

# type = thrdvH# col = fgp.nName segp.npath dte_DATE action mode thrStat thrCalc thrCalcValue brst-CrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent# filter = fgp.nName(*Availability*)# order = # sep = |_|# sepRec = ~AP~PROVISO~Targets~SNMP Availability (percent) (avg last hour)|_|~NOC Report-ing|_|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 Report-ing|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|2|_||_||_||_||_|



~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Report-ing|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|65|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Report-ing|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|10|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Report-ing|_|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:45 with 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 Manager DataView will now be generating reports without the threshold violation.

The difference in dates is because of GMT time (09/19/2001 01:08), which is actually on the 18th in the evening. Date and Action (U=update - I=Insert) let you understand the history of actions that happened to the thresholds and troubleshoot report problems.

To correct the issue in the future (no re-computation of the previous days):



To verify the recreaction of the thresholds is correctly updated

resmgr -export thrdvH -colNames "fgp.nName segp.npath dte_DATE action mode thrStat thrCalc thrCalcValue brstCrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent" -filter "fgp.nName(*Availability*)"

# type = thrdvH# col = fgp.nName segp.npath dte_DATE action mode thrStat thrCalc thrCalcValue brst-CrtclLevel brstWrnngLevel brstCrtclTime brstWrnngTime brstGenEvent# filter = fgp.nName(*Availability*)# order = # sep = |_|# sepRec = ~AP~PROVISO~Targets~SNMP Availability (percent) (avg last hour)|_|~NOC Report-ing|_|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 Report-ing|_|09/25/2001 20:41|_|U|_|1|_|0|_|0|_|0|_|90|_|95|_|900|_|1800|_|0|_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Report-ing|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|2|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Report-ing|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|65|_||_||_||_||_|



~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Report-ing|_|09/19/2001 01:08|_|U|_|2|_|3|_|0|_||_|10|_||_||_||_||_|~AP~Generic~Universal~Availability (percent)|_|~Customer Facing Report-ing|_|09/08/2001 00:36|_|I|_|1|_|0|_|0|_|0|_|90|_|95|_|900|_|1800|_|0|_|



NOTES


Chapter 12: Configuring Timezones

This chapter explains how to use resmgr to configure timezones, and is made up of the following topics:

Overview

Timezones are Tivoli Netcool Performance Manager object types that belong to the Design category.

Before using the commands in this chapter, review the information in Chapter 4, Managing Tivoli Netcool Performance Manager Objects. Additional resmgr commands for managing thresholds can be found in Working with Timezones on page 141 of Chapter 7, Managing Design Objects.

Working with Time Zones

This section explains how to use resmgr to create, modify, or delete time zone definitions.

Tivoli Netcool Performance Manager displays times in customer-specific time zones because 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 to different time zones.

You can attach a timezone to a group and it is associated with all groups and resources below it. Because resources can exist in multiple groups, you can create different time zone views of the same sets of resources by defining multiple groups with different time zone settings. This approach minimizes the amount of duplicate timezone processing that CME performs and the amount of redundant data that is loaded and retained in the database.

Topic Page

Overview 213

Working with Time Zones 213

Grouping Links of Sub-elements, Calendars,and Time Zones 216



Exporting Time Zones

This 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 Time Zones

This section explains how to delete time zones.

Example

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


resmgr -export tz -colNames "dbIndex name offset comment status date" -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/group of subelements, remove all the links between the timezone and the groups. When you remove the links, no statistics are produced for the groups.



Importing, Modifying, and Creating Time Zones

This section explains how to import, modify, and create time zones.

Example

resmgr -import tz -colNames "dbIndex name offset comment status date" -file /tmp/temporary


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)


resmgr -export tz -colNames "dbIndex name offset comment status date" -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 Sub-elements, Calendars,and Time Zones

This section explains how to create, modify, or delete links between groups of sub-elements, calendars, and time zones.

Exporting Links

Example


Deleting Links

Example

When you execute the following command, you delete all the links between a group and a timezone. Ensure you want to do so, before entering the command.


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)


If a Calendar/timezone is already defined at an upper branch for a given group, Tivoli Netcool Performance Manager returns an error indicating a Calendar/timezone cannot be created for this group.

resmgr -noX -export tz -colNames "cliParent sename setype cliChild_Tz name tzcliChild_Cal calName cliState cliType cliOrigin cliUser cliDate" -file /tmp/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 Links

Example

resmgr -noX -import tz -colNames "cliParent sename setype cliChild_Tz name cliChild_Cal calName cliState cliType cliOrigin cliUser 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 associated with a link does not exist in the database, the import of this link fails.


resmgr -noX -export tz -colNames "cliParent sename setype cliChild_Tz name cliChild_Cal calName cliState cliType cliOrigin tzcliUser cliDate" -file /tmp/verifLinks.dat


# 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 Calen-dar|_|on|_|static|_|impexp|_|abak|_|983902406|_|1000321|_|abak|_|static|_|2|_|AggSet 2|_|1000101|_|Day Calen-dar|_|on|_|static|_|impexp|_|abak|_|983902406|_|1000321|_|abak|_|static|_|2|_|AggSet 2|_|1000102|_|Night Calen-dar|_|of|_|static|_|impexp|_|abak|_|983902406|_|1000321|_|abak|_|static|_|2|_|AggSet 2|_|1000102|_|Night Calen-dar|_|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 quar-ter|_|on|_|static|_|impexp|_|abak|_|983902406|_|1000324|_|192.168.3.62|_|static|_|6|_|AggSet 6|_|1000104|_|Permanent, each quar-ter|_|on|_|static|_|impexp|_|abak|_|983902406|_|



NOTES


Appendix A: Supported resmgr Options

The following table lists in alphabetical order. all of the options you can use with the resmgr command It includes a brief description of each option, with which object type it is used, and whether you can use it with the import and export commands.

Option Definition Use with Object Type Import Export

agp group of reporters application Y Y

app reporter application Y Y

appH reporter history history table Y Y

appS reporter stylesheet application Y Y

cal Calendar calendar Y Y

calH Calendar history history table Y Y

chnl channel elementothers

NY

YY

client registration information about Tivoli Netcool Performance Manager clients

others Y Y

dbi export Tivoli Netcool Performance Manager GUI information into CSV format

others Y Y

DesignIndex sequence of indexes used for Tivoli Netcool Performance Manager Design objects such as formulas, reporters, propterties and so on.

sequences Y Y

egp element group group Y Y

egpH element group history 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 Oracle errors tracked by Tivoli Netcool Performance Manager

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 between group and reporter

application Y N

linkGroupAPPS link between group and reporters; group and style sheets

application Y N

linkGroupE link between group of elements and element

group Y N

linkGroupF link between the group and the formula

formula Y N

linkGroupN link between the group and the nomenclature

nomenclature Y N

linkGroupRU link between group and the report (Web) user

web user Y N

linkGroupSE link between group of subelements and subelement

group Y N

linkGroupSE_APP link between group of subelements and report

group Y N

linkGroupSE_RU link between group of subelements and report user

group Y N

linkGroupSE_TCZ link between group of subelements and timezone and Calendar

group Y Y

mib MIB formula Y Y

ncl nomenclature nomenclature Y Y

ngp nomenclature group nomenclature Y Y

ogp group of inventory profiles inventory profile Y Y

ogpt option of the inventory profile. Use with ogp value,

inventory profile Y Y

orausr list of Oracle users others Y Y

pctile percentile request Y Y

pkg all package tables others Y Y

propertyE property of element property Y Y

propertyRU property of report user property Y Y

propertySE property of subelement property Y Y




reg information about component that are running (similar to pvmstart)

others Y Y

regDesc list of all registries registry N Y

regInst instances of all registries registry N Y

regisDB Tivoli Netcool Performance Manager database registry

registry Y Y

regisDC Tivoli Netcool Performance Manager DataChannel registry

registry Y Y

regisDCConfig Tivoli Netcool Performance Manager DataChannel registry configuration

registry Y Y

regisDM Tivoli Netcool Performance Manager DataMart registry

registry Y Y

regisMG Tivoli Netcool Performance Manager DataChannel Manager registry

registry Y Y

ResourcesIndex sequence of indexes used for resources (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 SNMP configuration element Y Y

sched Scheduler scheduler Y Y

se subelement subelement Y Y

segp subelement group group Y Y

segpH subelement group history history table Y Y

segpreq request on subelement group

request Y Y

segpreqH subelement group request history

history table Y Y

seH subelement history history table Y Y

seproperty subelement property description

subelement Y N




seprp subelement property subelement Y Y

thrdv threshold definition threshold Y Y

thrdvH threshold definition history history table Y Y

tz timezone timezone Y Y

usr Tivoli Netcool Performance Manager DataMart user

DM user Y Y

vendor vendor nomenclature Y Y




NOTES




Appendix B: Common resmgr Commands

This appendix explains how to perform the following tasks using the resmgr command:

• Working With SAA Probes on page 228

• Listing subelement groups without resources on page 231

• Listing devices not assigned to a nomenclature group on page 231

• Correctly classifying a Tivoli Netcool Performance Manager object on page 232

• Filtering subelements using the underscore (_) on page 232

• Finding the subelement group index on page 232

• Cutting the subelement group on page 233

• Finding subelement groups without a parent on page 233

• Finding subelment groups with more than one parent on page 233

• Pasting the subelement group on page 233

• Finding number of child groups for a subelement group on page 234

• Checking subelement group request history tables on page 235

• Checking the number of groups to which a subelement belongs on page 236

• Listing elements with empty SysName on page 237

• Finding number of collection requests per subelement on page 238

• Filtering without case filter on page 238

• Finding the number of subelements in a family on page 238

• Displaying the classification of the xevice name dhcp200 on page 239

• Grouping all the subelements on page 239

• Inserting in the past on page 239



Working With SAA Probes

The following commands allow you to work with SAA probes. For a description of supported arguments to these commands, see Argument Descriptions for SAA Probe Operations on page 229.

For a list of SAA Probe properties, see Properties Used by the Tivoli Netcool Performance Manager-enabled SAA Probes on page 130.

Exporting or Importing an SAA Probe

• Configuration Table

resmgr [-export|-import] probe -colNames "dbIndex invariant se.name user origin date pprop.name pprop.value"

• History Table

resmgr [-export|-import] probeH -colNames "dbIndex invariant se.name pprop.name pprop.value"

Exporting or Importing an SAA Probe With Types


resmgr [-export|-import] probe -colNames "dbIndex invariant se.name user origin date probeType descriptionType invariantDefType classType dateType originType userType"

• History Table

resmgr [-export|-import] probeH -colNames "dbIndex invariant date origin user probeType descriptionType invariantDefType classType dateType originType userType"

Exporting or Importing SAA Probe Attributes


resmgr [-export|-import] pprop -colNames "dbIndex name snmpDisplayFlag snmpCreateFlag snmpPersistFlag snmpControlFlag mib defaultValue allowedValues order mandatory date origin user snmpType probeType descriptionType invariantDefType classType dateType originType userType"

• History Table

resmgr [-export|-import] ppropH -colNames "dbIndex name snmpDisplayFlag snmpCreateFlag snmpPersistFlag snmpControlFlag mib defaultValue allowedValues order mandatory date origin user snmpType probeType descriptionType invariantDefType classType dateType originType userType"



Deleting SAA Probes

The safest means to delete SAA probes is by database index. For probe type definitions, the database index field name is dbIndexType.

• Importing a probe

resmgr -import probe -colNames "probeType classType" -line "probeA|_|classA|_|" Info : === insert : INSERT ON probe probeType ( probeA ) (does not exist)

• Exporting a probe

resmgr -noHead -export probe -colNames "dbIndexType probeType classType" -filter "probeType(probeA)"

100006468|_|probeA|_|classA|_|

• Deleting a probe by type and class

resmgr -delete probetype -colNames "probeType classType" -line "probeA|_|classA|_|"

Info : === delete : DELETE ON probe probeType ( probeA ) (exists)

• Deleting a probe by database index

resmgr -delete probetype -colNames "dbIndexType" -line "100006469|_|"

Info : === delete : DELETE ON probe probeType ( probeA ) (exists)

• Deleting an instance of a probe deployed against a subelement

resmgr -delete probe -colNames "dbIndex" -line "1234567890"

• Deleting a Probe

resmgr -delete probe -colNames “name”

• Deleting a Type

resmgr -delete probe -colNames “type”

• Deleting an Attribute

resmgr -delete pprop -colNames “name”

• Deleting an Attribute Value

resmgr -delete ppropvalue -colNames “invariant se.name pprop.name”

Argument Descriptions for SAA Probe Operations

Argument Description

allowedValues Enables data checking in the DataView portal.

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 there is no value.

descriptionType Description of the type of SAA probe.

invariant A string that uniquely identifies the SAA probe.

invariantDefType The definition of the probe type invariant.

invariantType The invariant definition for the SAA probe type.

mandatory Indicates if the value for the attribute is required. 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 the change.

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 or echo).

se.name The ID of the sub-element router.

snmpControlGFlag Indicates if the attribute is an SNMP OID used for control. Can be either 1 (TRUE) or 0 (FALSE).

snmpCreateFlag Indicates if the attribute is an SNMP OID used for creating. Can be either 1 (TRUE) or 0 (FALSE).

snmpDisplayFlag Indicates if the attribute is an SNMP OID used for display. Can be either 1 (TRUE) or 0 (FALSE).

snmpPersistFlag Indicates if the attribute is an SNMP OID used for persistance. Can be either 1 (TRUE) or 0 (FALSE

snmpType Specifies the type of SNMP data. Can be one of the following:

• CNT

• C64

• GGE

• INT

• IP

• MAC

• OCT

• OID

• STR

• TIM

user The name of the user performing the change.

userType The user performing the change.

Argument Description



Listing subelement groups without resources

resmgr -export segp -colNames "dbIndex name segchild.name se.name" -isMandat "" -filter "segchild.name(is null) se.name(is null) type(generated)" -file $DIR/Usage_emptyGrp.dat

# type = segp# col = dbIndex name segchild.name se.name# filter = segchild.name(is null) se.name(is null) type(generated)# order =# sep = |_|# sepRec =## cmdLine = -export segp -colNames "dbIndex name segchild.name se.name" -filter "segchild.name(is null) se.name(is null) type(generated)"200000049|_|test 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 group

resmgr -export elt -colNames "name profil encl.oid encl.name" -filterRule "%(encl.gpname) IS NULL and %(elt.type) = ’snmp’ and %(elt.state) = ’on’ and %(elt.origin) = ’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 Internetwork Operating System Software \nIOS (tm) MSFC Software (C6MSFC-I|_|NF-site-site-flow-BestEffort-CoffeeBucks|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-site-flow-Bronze-CoffeeBucks|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-iphost-flow-Bronze-CoffeeBucks|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|



NF-iphost-site-flow-BestEffort-CoffeeBucks|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-iphost-flow-BestEffort-CoffeeBucks|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-iphost-site-flow-Bronze-CoffeeBucks|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-Bronze-CoffeeBucks|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-BestEffort-CoffeeBucks|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-site-flow-Gold-SpecificElectric|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-iphost-flow-SpecificElectric|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-iphost-flow-MarcDonuts|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-as-as-flow-SpecificElectric|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-iphost-flow-Gold-SpecificElectric|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-as-as-flow-MarcDonuts|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-Gold-SpecificElectric|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-site-NexxonOil|_|bulk_2|_|1.3.6.1.4.1.2929|_|MLARS|_|NF-iphost-site-flow-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 Manager object

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 sucessful, no output is displayed.

Cutting and Pasting in Subelement Group

You add a subelement group by using the Tivoli Netcool Performance Manager DataMart 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 group

resmgr -delete linkGroupSEGP -colNames "nop lgChild lgParent" -line "~DBER~val3|_|200003365|_|20000091"

Pasting the subelement group

resmgr -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.dbIndex dbIndex name" -filter "seg-parent.dbIndex(is null)"|_|7699|_|IP VPN|_||_|3|_|||ROOTROOT|||_|

Finding subelment groups with more than one parent

Note: You use this command for debugging purposes. A group cannot have more than one parent. If you find any groups using this command, you need to correct the problem.

resmgr -export segp -colNames "segparent.dbIndex_COUNT dbIndex name" -file $DIR/Usage.GrpParent.dat

Search this list for the count != 1

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

resmgr -export segp -colNames "lgChild_COUNT dbIndex name" -file $DIR/Usage_childNumber.dat

# type = segp# col = lgChild_COUNT dbIndex name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export segp -colNames "lgChild_COUNT dbIndex name"5|_|3|_|||ROOTROOT|||_|16|_|663|_|NOC Reporting|_|19|_|677|_|Sub-Element Collect|_|2|_|4185|_|IPSec|_|2|_|4186|_|Phase-1|_|2|_|4187|_|Phase-2|_|1|_|4188|_|%(customer)|_|1|_|4189|_|%(customer)|_|1|_|4190|_|IPSec|_|1|_|4300|_|Frame Relay|_|4|_|4301|_|DLC|_|1|_|4304|_|Frame Relay|_|4|_|4305|_|DLC|_|6|_|4306|_|Router|_|



2|_|4307|_|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 tables

resmgr -export segpreqH -colNames "fgp.nName segp.npath period dbIndex dte action dte_DATE" -file $DIR/Usage_segpreqH.dat

# type = segpreqH# col = fgp.nName segp.npath period dbIndex dte action dte_DATE# filter = # order = # sep = |_|# sepRec = ## cmdLine = -export segpreqH -colNames "fgp.nName segp.npath period dbIndex dte action dte_DATE" ~AP~Specific~SNMP~Router~Cisco 11.x~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-1213 Interface|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|900|_|100001356|_|1065103662|_|U|_|10/02/2003 18:07|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Resets Cisco 11.x Router RFC-1213 Interface|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|900|_|100001356|_|1018459127|_|I|_|04/10/2002 21:18|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Restarts Cisco 11.x Router RFC-1213 Interface|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|900|_|100001355|_|1065103662|_|U|_|10/02/2003 18:07|_|~AP~Specific~SNMP~Router~Cisco 11.x~Interface~Restarts Cisco 11.x Router RFC-1213 Interface|_|~Sub-Element Collect~Router~Interfaces~Cisco 11.x|_|900|_|100001355|_|1018459127|_|I|_|04/10/2002 21:18|_|~Demo~Addressess Free|_|~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps)|_|900|_|100009867|_|1065103663|_|U|_|10/02/2003 18:07|_|~Demo~Addressess Free|_|~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps)|_|900|_|100009867|_|1050704504|_|I|_|04/19/2003 02:21|_|~Demo~Address Pool Utilization (percent)|_|~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps)|_|900|_|100009866|_|1065103663|_|U|_|10/02/2003 18:07|_|~Demo~Address Pool Utilization (percent)|_|~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps)|_|900|_|100009866|_|1050704504|_|I|_|04/19/2003 02:21|_|~AP~Specific~SNMP~RFC-1213~Interface~Outbound Throughput (PDUs per second) RFC-1213 Interface|_|~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps)|_|900|_|100009851|_|1065103662|_|U|_|10/02/2003 18:07|_|~AP~Specific~SNMP~RFC-1213~Interface~Outbound Throughput (PDUs per second) RFC-1213 Interface|_|~Sub-Element Collect~MIB-II~High Speed Interfaces (>=100Mbps)|_|900|_|100009851|_|1050698751|_|I|_|04/19/2003 00:45|_|

Checking the number of groups to which a subelement belongs

resmgr -export segp -colNames "se.name dbIndex_COUNT" -file $DIR/Usage_seNbGroup.dat

# type = segp

# col = se.name dbIndex_COUNT

# filter =

# order =

# sep = |_|

# sepRec =

#

# cmdLine = -export segp -colNames "se.name dbIndex_COUNT"



172.17.100.254_<NULL>|_|7|_|

172.31.0.31_<NULL>|_|9|_|

172.31.0.31_If<1>|_|9|_|

172.31.0.31_If<2>|_|9|_|

172.31.0.31_If<3>|_|9|_|

172.31.0.31_If<4>|_|9|_|

172.31.0.31_If<5>|_|9|_|

172.31.0.31_If<6>|_|9|_|

172.31.0.31_If<7>|_|9|_|

172.31.0.41_<NULL>|_|9|_|

172.31.0.41_If<1>|_|9|_|

172.31.0.41_If<2>|_|9|_|

172.31.0.41_If<3>|_|9|_|

172.31.0.41_If<4>|_|9|_|

172.31.0.41_If<5>|_|9|_|

172.31.0.41_If<8>|_|9|_|

172.31.0.41_RTTMon<NULL>Probe<1>|_|6|_|



172.31.0.51_<NULL>|_|9|_|

Listing elements with empty SysName

resmgr -export elt -colNames "name encl.name" -filter "encl.name(is null)" -file $DIR/Usage_eltEmptySysName.dat

# type = elt# col = name encl.name# filter = encl.name(is null)# order =# sep = |_|# sepRec =## cmdLine = -export elt -colNames "name encl.name" -filter "encl.name(is null)"Burned_100008089_192.168.1.3|_||_|192.168.127.4|_||_|APRouterforprobe|_||_|PROVISO|_||_|default|_||_|



Finding number of collection requests per subelement

resmgr -export segpreq -colNames "segp.dbIndex_COUNT se.name" -file $DIR/Usage_seNbCollect.dat

# type = segpreq# col = segp.dbIndex_COUNT se.name# filter =# order =# sep = |_|# sepRec =## cmdLine = -export segpreq -colNames "segp.dbIndex_COUNT se.name"2|_|172.31.0.31_<NULL>|_|2|_|172.31.0.41_<NULL>|_|14|_|172.31.0.41_RTTMon<NULL>Probe<1>|_|14|_|172.31.0.41_RTTMon<NULL>Probe<2>|_|14|_|172.31.0.41_RTTMon<NULL>Probe<3>|_|2|_|172.31.0.51_<NULL>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<10097>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<10102>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<10107>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<10110>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<10113>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<10115>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<10116>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<10117>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<10119>|_|7|_|172.31.0.51_RTTMon<NULL>Probe<10120>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<1969>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<7777>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<8888>|_|14|_|172.31.0.51_RTTMon<NULL>Probe<9999>|_|2|_|172.31.1.2_<NULL>|_|2|_|192.168.1.3_<NULL>|_|2|_|192.168.64.253_<NULL>|_|

Filtering without case filter

resmgr -export elt -colNames "name" -filter "name_UPPER(*BOSTON*)" -file $DIR/Usage_filter2.dat

If the command is sucessful, no output is displayed.

Finding the number of subelements in a family

resmgr -export se -colNames "name_COUNT fam.name" -isMandat "fam" -file $DIR/Usage_seNbFamily.dat

# type = se# col = name_COUNT fam.name# filter =# order =# sep = |_|# sepRec =



## cmdLine = -export se -colNames "name_COUNT fam.name"84|_|1213_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 subelements

The following resmgr command groups all the sub-elements which are attached to the an element which IP address is between 192.168.64.40 and 192.168.64.60 in the sub-element group named "net40-60" within the NOC reporting group

resmgr -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 "npath se.name"

Displaying the classification of the xevice name dhcp200

resmgr -export elt -sep ’’ -noHead -colNames "encl.oid" -filter "name(dhcp200)" | xargs -I {} resmgr -export ngp -colNames "npath ncl.name ncl.oid" -filter "ncl.oid({})" -noHead -file $DIR/Usage_device.dat

Inserting in the past

Note: Check with IBM Support before using this command. Inserting in the past has significant impact on the Tivoli Netcool Performance Manager system.

resmgr -import seproperty -colNames "name seprp.Contact:value seprp.Contact:datev(1057015945)" -histoDate 1 -mode "IFirst,forced" -file ....



NOTES


Appendix C: CLI Return Codes

This appendix provides information about the return codes for Tivoli Netcool Performance Manager DataMart command line interfaces (CLI), and is made up of the following topics:

Overview

This appendix provides the following information about return codes for Tivoli Netcool Performance Manager command line interfaces (CLI):

• Binary/Version is the name of the CLI and the release number for DataMart

• Language is the language that was used to build the CLI.

• Usage tells you if the CLI is also available in GUI mode.

• Success Return Code provides the code number for a successful CLI execution.

• Failure Return Code provide the code number for a failed CLI execution.

• Other Return Codes provides information on other return codes other than “0” (if applicable).

• Log File Name provides the name of the logging file.

A return code of “0” indicates the command was successful. A return code other than 0, indicates the command failed with errors.

CLIs are written in tclTk, C, C++, and Shell. You need to use the “-noX” option for CLIs written in tclTk.

If errors occur, a code number other than “0” is returned. Details about the error are logged to standard output.

Topic Page

Overview 241

snmpconf 242

reqedit 247

resmgr 249

inventory 251

impexp 253



snmpconf

Return code details for the snmpconf command line interface are as follows:

Standard Output Error Messages

The following example error messages appear when launching snmpconf without using the “-verbose” option (resulting in more output lines, including error and non-errors).

The error messages are written in the standard output using the following format:

ERROR in SNMPCONF : <short error message> : <detailed error message>

Examples

ERROR in SNMPCONF : UPDATE failed : No changed value

ERROR in SNMPCONF : ADD failed : Element myHost already exists

Binary Language UsageSuccess Return Code

Failure Return Code

Other Return Codes

Log File Name

snmpconf tclTk CLI and GUI

0 1 stderr/ stdout



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 not contain space character !

Element name should not contain “~” !

Element name should not contain “|” !

Element name should not contain “,” !

Element must be specified !

IP address must be specified ! (example: 123.123.123.123, 123.123.123.* or 123.123.123.1-10,33,44,50-77)

Bad 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 be numeric !

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 reserved for “default” element !

Database access error (%s). %s: <detailed error>

Cannot insert element into database ! This message can be followed by the SQL query that has failed

snmpconf is in READ MODE ! Cannot perform operation without 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 not contain 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 from database ! This message can be followed by the SQL query that has failed.

Cannot read from database This message can be followed by the SQL query that has failed.

All fields of “default” must be specified !



No option passed ! (possible options are -ipaddress -rcommunity -wcommunity -timeout -tries -port)

Missing some CLI options

No changed value ! Can not update because of unchanged parametersThis « error » can be ignored. It is a warning

Element “default” is reserved ! You can't change its address (*.*.*.*).

IP address *.*.*.* is reserved for “default” element !

Cannot update element in database ! This message can be followed by the sql query that has failed

Cannot save in database

snmpconf is in READ MODE ! Can not perform operation without write permissions

DELETE failed Element name should not contain 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 from database ! This message can be followed by the sql query that has failed

Cannot read from database This message can be followed by the sql query that has failed

Element “default” is reserved ! You can't add or delete it.

Cannot delete element in database !

snmpconf is in READ MODE ! Can not perform operation without write permissions



Database Error Cannot get elements information from database !

Unknown operation

%s %s : the operation name that have been passed to CLI

Unable to inform collector about modifications at %s !

%s: <Ipadress : port #>

Cannot continue without permissions

Check the user permissions for the current CLI



reqedit

Return Code

Return code details for the reqedit command line interface is are as follows:


The following example error messages appear when launching the reqedit without using the “-verbose” option (resulting in more information on the standard output errors and process information).

The error messages are written in the standard output using the following format:

ERROR in REQEDIT : <short error message> <detailed error message>

Examples:

ERROR in REQEDIT : Bad period value. Period value range is from 1 minute to 24 hours.

ERROR in REQEDIT : Missing parameters on request “formula target” are mandatory.

Short and detailed error messages are listed in the following table.

Binary/Version Language UsageSuccess Return Code

Failure Return Code

Other Return Codes

Log File Name

reqedit v2.0 and 2.2

tclTk CLI and GUI

0 1 stderr/ stdout

Short Error Message Detailed Error Message Comments

Unable to launch Request Editor in write mode.

Unknown operation %s %s : the operation name that have been passed to CLI.

Cannot read Database requests.

Database access error (%s). %s: <detailed error>

Cannot read from database Cannot get index %s %s: formula’s database index

Cannot read from database %s %s : <detailed error>.

Missing parameters on request. “%s” are mandatory. %s : CLI missing parameters

Period or Calendar must be specified.

Bad period value. Period value range is from %s minute to 24 hours.

%s : <minimum period value>

Bad storage value.

Bad resource type.



Bad status value.

Cannot read from database This message can be followed by the sql query that has failed.

Cannot save in database This message can be followed by the sql query that has failed.

Unknown operation: %s %s : <operation string>. Valid operations are : add, update, and delete.

Unknown request.

Unknown formula: %s %s : <formula name>

Unknown element name: %s %s : <element name>

Unknown element group name: %s %s : <element group name>

Unknown sub-element name: %s %s : <sub-element name>

Unknown sub-element group name: %s %s :<sub-element group name>

Unknown calendar: %s %s : <calendar name>

Unknown threshold profile: %s %s : <threshold name>

Not a valid formula: %s : <formula name>

Request already exists.

Unable to inform collector about modifications at %s !

%s: <Ipadress : port #>

Cannot add request to database.

Cannot update request into database.

Cannot remove request from database.



resmgr

Return Code

Return code details for the resmgr command line interface is are as follows:

Comments

Return code 1 = critical error

Return code >1 (X) means there are errors, but it is not critical.


The 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 #1

resmgr -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~Lotus Notes ) (exists)

Example #2

solar:/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 standard output.

Binary/Version

Language UsageSuccess Return Code

Failure Return Code

Other Return CodesLog File Name

resmgr v2.0 and 2.2

tclTk CLI and GUI

0 1 X > 1 : where X = nbErrors + 10(nbErrors is the number of sql requests that have failed)

stderr + stdout



Short and detailed error message are listed in the following table.

Short Error MessageDetailed Error Message

Comments

Cannot connect to database.

Database access error (%s). %s : <message>.

Cannot disconnect from database.

Cannot continue without permissions.

Cannot delete in database


Cannot read from database



inventory

Return Code

Return code details for the inventory command line interface is are as follows:


The 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

Binary Language UsageSuccess Return Code

Failure Return Code

Other Return CodesLog File Name

inventory tclTk CLI and GUI

0 1 2

The 2 return code signifies that the inventory profile is locked. This return code only displays if the PVM_ENHANCED_ERRORCODE=1 variable is set in your DataMart environment.

stderr/ stdout



Short and detailed error messages are listed in the following table:

Format Type 3

This type of log is produced while the module is using resmgr APIs. The log format is the same as what is normally produced by resmgr.

<Log level> : < Short message> : <Detailed message>

where <Log level> is Error , or Warning , or Info

Example

resmgr -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~Lotus Notes ) (exists)

Short Error MessageDetailed Error Message

Comments

Cannot connect to database.

Database access error (%s). %s : <message>.

Cannot disconnect from database.

Cannot continue without permissions.

Cannot delete in database


Cannot read from database

Profile '%s' already exist !

File '%s' doesn't exist !

You must run discovery before running synchronization

%s %s : <message>.



impexp

Return Code

Return code details for the impexp command line interface are as follows:

Comments

The return code 1 indicates that impexp encountered a critical error. If only a part of process worked. If not critical error, the return code is greater than 1.


Only critical messages are logged in the standard outputs. In such cases, the return code is 1, and the error is logged on the standard output.

The following syntax is erroneous ("-" forgotten before "export") :

impexp -noX export calendars /tmp/calendars

You can get the following error on the standard output:

Error : === BAD ARGUMENTS: At least one option required amog (-export, -import, -config).

Binary/Version

Language UsageSuccess Return Code

Failure Return Code

Other Return Codes

Log File Name

impexp v2.0 and 2.2

tclTk CLI and GUI

0 1 X , where X is a number. X=10 + nbSqlFailuresnbSqlFailures is the number of sql requests that have failed during operation.

$PVMHOME/log/logFile.IMPEXP.



NOTES


Appendix D: Sample Inventory Script

This appendix provides contains a sample Korn Shell wrapper program that calls the inventory command. The command does the following:

• Extracts all existing inventory profiles from the database.

• Loops through the profiles, running a complete inventory on each one.

• Reloads the collector after every five inventories (this is configurable).

• 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 more information, see your Tivoli Netcool Performance Manager Professional Services representative.



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

let VERBOSE=0

#-------------------------------------------------------------------------------

# Command line keywords

#-------------------------------------------------------------------------------

KEY_ACTION="-action"

KEY_PROFILE="-profile"

KEY_SEP="-sep"

KEY_VERBOSE="-v"; # Verbose mode

KEY_YES="-Yes"; # Answer Yes to all questions

KEY_HELP="-?";



# -----------------------------------------------------------------------------

# function Confirm

# -----------------------------------------------------------------------------

function Confirm

{

if (( ! ${YES} ))

then

read IN?"${1}"

if [[ $IN == @(y|Y) ]]

then

return 0

else

return -1

fi

else

return 0

fi

}

# -----------------------------------------------------------------------------

# function PrintError

# -----------------------------------------------------------------------------

function PrintError

{

echo "`date \"+%m/%d/%Y-%H:%M:%S\"` [${PROGNAME}] Error : ${1}"

}

# -----------------------------------------------------------------------------

# function PrintWarning

# -----------------------------------------------------------------------------

function PrintWarning

{

echo "`date \"+%m/%d/%Y-%H:%M:%S\"` [${PROGNAME}] Warning : ${1}"

}

# -----------------------------------------------------------------------------

# function PrintInfo

# -----------------------------------------------------------------------------

function PrintInfo

{

echo "`date \"+%m/%d/%Y-%H:%M:%S\"` [${PROGNAME}] Info : ${1}"



}

# -----------------------------------------------------------------------------

# function PrintLog

# -----------------------------------------------------------------------------

function PrintLog

{

if (( ${VERBOSE} ))

then

echo "`date \"+%m/%d/%Y-%H:%M:%S\"` [${PROGNAME}] ${1}"

fi

}

#-------------------------------------------------------------------------------

# function PrintUsage

#-------------------------------------------------------------------------------

function PrintUsage

{

cat << USAGE

Usage : ${0##*/} [Options]

Where Options are

${KEY_ACTION} : Defines which modules to run [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

PrintUsage

exit 0

fi

#-------------------------------------------------------------------------------

# Parsing parameters

#-------------------------------------------------------------------------------

while [[ -n ${1} ]]

do

case ${1} in

"${KEY_ACTION}")

shift

if [[ -n ${1} ]]

then

ACTION="${1}"

else

PrintError "Missing mandatory parameter !"

PrintUsage

exit 3

fi

;;

"${KEY_PROFILE}")

shift

if [[ -n ${1} ]]

then

PROFILE="${1}"

else


PrintUsage

exit 3

fi

;;

"${KEY_SEP}")

shift

if [[ -n ${1} ]]

then



SEP="${1}"

else


PrintUsage

exit 3

fi

;;

"${KEY_VERBOSE}")

let VERBOSE=1

;;

"${KEY_YES}")

let YES=1

;;

* )

PrintError "Failed to parse arguments, unknown option: \"${1}\"."

PrintUsage

exit 3

;;

esac

shift

done

#-------------------------------------------------------------------------------

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

else

echo ${PROFILE} > ${PROGNAME}.profiles

fi

#-------------------------------------------------------------------------------

# Running inventory for each profiles

#-------------------------------------------------------------------------------

typeset -i NBPROFILES=$(wc -l < ${PROGNAME}.profiles 2>/dev/null)

typeset -i profCnt=1

cat ${PROGNAME}.profiles |&

while read -p i

do

PrintLog "Launching inventory profile \"${i}\"..."

LOGFILE="${DIRNAME}/${PROGNAME}_${i}.log"

if ( (( profCnt % reloadFreq == 0 )) || (( profCnt == NBPROFILES )) )

then

inventory -noX -name "${i}" -action "${ACTION}" -reload 1 >> "${LOGFILE}" 2>&1

else

inventory -noX -name "${i}" -action "${ACTION}" >> "${LOGFILE}" 2>&1

fi

if [ ${?} -ne 0 ]

then

PrintError "Inventory failed for profile \"${i}\"."

fi

sleep 60

profCnt=$((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 E: Using Prerequisite Check Scripts

This appendix provides information concerning how to use prerequisite check scripts that are included with Tivoli Netcool Performance Manager, and is made up of the following topics:

Overview

Tivoli Netcool Performance Manager includes the check_os and check_db prerequisite checking scripts that are used to verify various host system and Oracle database requirements to ensure the successful operation of Tivoli Netcool Performance Manager. The sections below explain how to use these scripts to verify your Tivoli Netcool Performance Manager environment.

Using the check_os Script

The check_os script is used to verify platform version and patch requirements for Solaris, AIX, and Redhat Linux systems that host Tivoli Netcool Performance Manager components.

Tasks Performed by the check_os Script

Once the script has been executed, check_os refers to values set in the check_os.ini file and performs the

following tasks:

• Verfies that an arguement was passed to the script.

• Verifies that the operating system is a supported platform for Tivoli Netcool Performance Manager.

• Verifies that the operating system is a supported version for Tivoli Netcool Performance Manager.

• Verifies that the specified Tivoli Netcool Performance Manager component is valid and supported on the current operating system.

• Verifies that the required patches have been applied to the operating system.

Topic Page

Overview 263

Using the check_os Script 263

Using the check_db Script 267



Running the check_os Script

To use the check_os script, do the following:

1. Log in as root on the system where the Topology Editor has been installed.

2. Change your working directory to the directory that contains the check_os script. For example, using the default location:

cd /opt/IBM/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 Manager component. The following table lists the supported values:

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 Tivoli Netcool Performance Manager: Configuration Recommendations.

Example Output

The following are examples of output returned by the config_os script:

Solaris

# ./check_os db-->OK. Version SunOS 5.9.-->OK. 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.

Value Description

dm Tivoli Netcool Performance Manager DataMart

dl Tivoli Netcool Performance Manager DataLoad

dc Tivoli Netcool Performance Manager DataChannel

db Tivoli Netcool Performance Manager Database

dv Tivoli Netcool Performance Manager DataView



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

The 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 the script command.

This version of operating system is not supported! The version of the current operating system is not supported by Tivoli Netcool Performance Manager. Examine the check_os.ini file for supported versions of operating systems.

Proviso Component: component_ID is unknown or not supported for this OS!

Either an incorrect Tivoli Netcool Performance Manager component was specified in the script command, or the Tivoli Netcool Performance Manager component is not supported on the current operating system. Examine the check_os.ini file for supported operating systems.

** ERROR ** Missing required patch patch_name for this OS!

The current operating system is not supported by Tivoli Netcool Performance Manager. Examine the check_os.ini file for supported operating systems.

This system’s OS is not supported! The current operating system is not supported by Tivoli Netcool Performance Manager. Examine the check_os.ini file for supported operating systems.

ERROR! The value of limit_name was not detected 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 the check_os.ini file for supported /etc/security/limits values.

ERROR! The value of limit_name is: limit_value. This is not equal or less than what is set in the check_os.ini file.

AIX only. A value is incorrect in the /etc/security/limits file. Examine the check_os.ini file for supported /etc/security/limits values.



ERROR! Unknown OS Prefix The current operating system is not supported by Tivoli Netcool Performance Manager. Examine the check_os.ini file for supported operating systems.




Using the check_db Script

The check_db script is used to verify system settings and Oracle version and patch requirements for Solaris, AIX, and Redhat Linux systems that host Tivoli Netcool Performance Manager components.

Tasks Performed by the check_db Script

Once the script has been executed, check_db refers to values set in the check_db.ini file and performs the following tasks:

• Verfies that arguements were passed to the script.

• Verifies that the operating system is a supported platform for Tivoli Netcool Performance Manager.

• Verifies that the operating system is a supported version for Tivoli Netcool Performance Manager.

• Verifies that the required Oracle environment variables are set.

• Verifies that the installed Oracle version is a supported version for Tivoli Netcool Performance Manager.

• Verifies the Oracle home patch and checks that no symbolic links are used in the Oracle home directory tree.

• Verifies that the Oracle binary has the correct bit setting for the operating system.

• Runs the tnsping command to ensure that the Oracle server is accessible.

• Verifies that no Oracle background processes exists for Tivoli Netcool Performance Manager.

• Verifies that no instance-specific configuration files exist for Tivoli Netcool Performance Manager.

• Verifies that the Oracle database is running and accessible.

Running the check_db Script

To use the check_db script, do the following:

1. Log in as oracle on the system where the Topology Editor has been installed.

2. Change your working directory to the directory that contains the check_db script. For example, using the default location:

cd /opt/IBM/proviso/deployer/proviso/bin/Check

3. To verify Oracle database prerequisites, start the check_db script using the following 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 the prerequisites for an Oracle server or client installation.



4. To verify that the Oracle database is running and accessible, start the check_db script using the following command:

./check_db verifybase ORACLE_SID

Where:

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 Tivoli Netcool Performance Manager: Configuration Recommendations.

Examples

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

install_method Supported values are new or upgrade. Specifies whether check_db is to verify the prerequisites for a new or upgrade Oracle installation.

ORACLE_SID Specifies the Oracle System Identifier used for Tivoli Netcool Performance Manager in your environment. For example, PV.


ORACLE_SID Specifies the Oracle System Identifier used for Tivoli Netcool Performance Manager in your environment. For example, PV.




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 Messages

The 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 arguements were specified in the script command.

ERROR! This systems OS is not supported! The current operating system is not supported by Tivoli Netcool Performance Manager. Examine the check_db.ini file for supported operating systems.

ERROR! This version of operating system is not defined in check_db.ini!

The version of the current operating system is not supported by Tivoli Netcool Performance Manager. Examine the check_db.ini file for supported versions of operating 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 been set. 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 this value and run the script again.



EXTPROC_DLLS Not defined. The EXTPROC_DLLS parameter has not been set. Set this value and run the script again.

ERROR! Could not determine version of Oracle installed!

The Oracle version could not be found. Verify that a version of Oracle supported by Tivoli Netcool Performance Manager has been installed on the system.

ERROR! Checked for Oracle software. The Oracle software could not be found. Verify that a version of Oracle supported by Tivoli Netcool Performance Manager has been installed on the system.

ERROR! Ensure Oracle software is installed. The Oracle software could not be found. Verify that Oracle has been installed on the system.

WARNING! Client Version does not match entry in check_db.ini

The Oracle client version is not supported by Tivoli Netcool Performance Manager. Examine the check_db.ini file for supported versions of Oracle client.

ERROR! Oracle version: version not listed in check_db.ini.

The Oracle version is not supported by Tivoli Netcool Performance Manager. Examine the check_db.ini file for supported versions of Oracle.

ERROR! Link is a symbolic link! The specified link is symbolic. No symbolic links can be used in the Oracle home directory tree.

ERROR! The binary: binary_name was not found. Check if Oracle is installed.

The specified Oracle binary could not be found. Verify that Oracle has been installed on the system.

ERROR! Bit_setting bit binary_name not listed in check_db.ini.

The specified bit setting does not match the correct bit setting for the operating system. Examine the check_db.ini file for supported bit settings.

WARNING! Did not get OK response from tnsping. Oracle is not responding. Check that Oracle is running and available.

WARNING! Cannot contact Oracle listener. The Oracle listener is not responding. Check that the Oracle listener is running and available.

ERROR! Found an Oracle instance running with PID: PID.

An existing Oracle background process exists for Tivoli Netcool Performance Manager on the system. Determine if you wish to reinstall or upgrade the Oracle server.

ERROR! An init.ora file exists for given SID. An existing instance-specific Oracle configuration file exists for Tivoli Netcool Performance Manager on the system. Determine if you wish to reinstall or upgrade the Oracle server.

ERROR! The value of parameter was not detected with the sysdef command and could 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 the recommended minimum in the check_db.ini file.

A value is incorrect for parameter. Examine the check_db.ini file for supported values for parameter.

ERROR! The value of SHMMAX was not detected with the sysdef command and coulnd not be found in the /etc/system file.

Check that the minimum value is set. The value for SHMMAX in the /etc/system file is missing. Examine the check_db.ini file for supported 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 file is incorrect. Examine the check_db.ini file for supported values for SHMMAX.

ERROR! Could not find the file set name as COMMITTED.

The specified file set could not be found. Verfiy that the file set has been installed on the system.

ERROR! Could not find asyncio as Available. The specified file is not available. Check that Oracle is running and available.

ERROR! Unknown OS Prefix. The current operating system is not supported by Tivoli Netcool Performance Manager. Examine the check_db.ini file for supported operating systems.

ERROR! Could not access the instance ORACLE_SID.

The specified Oracle System Identifier is not accessible. Check that the instance has been defined.

ERROR! Check that the Oracle instance is running. The Oracle instance is not running. Check that 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 the script.

ERROR! Invalid install method. ERROR! Must be New or Upgrade.

An incorrect install_method was specified in the script command. Verify the command syntax and re-run the script.

ERROR! Invalid Install Type. ERROR! Must be client or server.

An incorrect install_type was specified in the script command. Verify the command syntax 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 in other countries. Consult your local IBM representative for information about the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:


IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A.

Such information may be 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 material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating systems. 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 application programs conforming to the application programming interface for the operating system for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

If you are viewing this information in softcopy form, the photographs and color illustrations might not appear.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.


Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other product, and service names may be trademarks or service marks of others.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.



Additional Copyright Information

The following copyright information is for software used by Tivoli Netcool Performance Manager.

Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3

This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.

The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee is required for any of the authorized uses. Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply.

IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license.

SCOTTY Stack

This software is copyrighted by Juergen Schoenwaelder, the Technical University of Braunschweig, the University of Twente, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.



THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN “AS IS” BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.


Various copyrights apply to this package, listed in 3 separate parts below. Please make sure that you include all the parts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during this time. From 2001 onwards, the project has been based at SourceForge, and Networks Associates Technology, Inc hold the copyright on behalf of the wider Net-SNMP community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed by Cambridge Broadband Ltd. to the project since 2001.

Part 1: CMU/UCD copyright notice: (BSD like)

Copyright © 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000

Copyright © 1996, 1998-2000 The Regents of the University of California

All Rights Reserved

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.

CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Part 2: Networks Associates Technology, Inc copyright notice (BSD)

Copyright © 2001, Networks Associates Technology, Inc

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer

in the documentation and/or other materials provided with the distribution.• Neither the name of the NAI Labs nor the names of its contributors may be used to endorse or promote products derived

from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Part 3: Cambridge Broadband Ltd. copyright notice (BSD)

Portions of this code are copyright © 2001, Cambridge Broadband Ltd.

All rights reserved.


• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer

in the documentation and/or other materials provided with the distribution.• The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without

specific prior written permission.


THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

BLT 2.4u

Portions (c) 1993 AT&T, (c) 1993 - 1998 Lucent Technologies, (c) 1994-1998 Sun Microsystems, Inc., and (c) 1987-1993 The Regents of the University of California.

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the names of AT&T, Lucent Technologies Inc., Sun Microsystems, Inc. and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.

THE COPYRIGHT HOLDERS AND OTHER CONTRIBUTORS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR OTHER CONTRIBUTORS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

CMU-SNMP 1.14

CMU/UCD copyright notice: (BSD like) Copyright 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California

All Rights Reserved



Scotty 2.8, incrTCL 3.0, [incr TCL] 3.2

Portions Copyright (c) 1987-1994 The Regents of the University of California. Copyright (c) 1994-1995 Sun Microsystems, Inc.

This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.




THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

RESTRICTED RIGHTS: Use, duplication or disclosure by the government is subject to the restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software Clause as DFARS 252.227-7013 and FAR 52.227-19.

Portions Copyright (c) 1993-1998 Lucent Technologies, Inc.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that the copyright notice and warranty disclaimer appear in supporting documentation, and that the names of Lucent Technologies any of their entities not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

Lucent disclaims all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall Lucent be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortuous action, arising out of or in connection with the use or performance of this software.

UCD SNMP 4.2.5

Portions Copyright 1989, 1991, 1992 by Carnegie Mellon University. Derivative Work - 1996, 1998-2000, Copyright 1996, 1998-2000 The Regents of the University of California All Rights Reserved



Portions Copyright: (c) 2001-2003, Networks Associates Technology, Inc, (c) 2001-2003, Cambridge Broadband Ltd, (c) 2003-2005, Sparta, Inc., (c) 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications, (c) Fabasoft R&D Software GmbH & Co KG, 2003 [email protected]. All rights reserved.


1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. Neither the names of Networks Associates Technology, Inc, Cambridge Broadband Ltd., Sparta, Inc., Cisco, Inc, Beijing University of Posts and Telecommunications, Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product


names, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS `ÀS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

JDOM 1.0

Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.


1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution.

3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact <request_AT_jdom_DOT_org>.

4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management <request_AT_jdom_DOT_org>.

In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the software itself an acknowledgement equivalent to the following:

"This product includes software developed by the JDOM Project (http://www.jdom.org/)." Alternatively, the acknowledgment may be graphical using the logos available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>. For more information on the JDOM Project, please see <http://www.jdom.org/>.

Regex 1.1a

Copyright (C) 1996, 1999 Vassili Bykov. It is provided to the Smalltalk community in hope it will be useful.

1. This license applies to the package as a whole, as well as to any component of it. By performing any of the activities described below, you accept the terms of this agreement.

2. The software is provided free of charge, and `às is'', in hope that it will be useful, with ABSOLUTELY NO WARRANTY. The entire risk and all responsibility for the use of the software is with you. Under no circumstances the author may be held responsible


for loss of data, loss of profit, or any other damage resulting directly or indirectly from the use of the software, even if the damage is caused by defects in the software.

3. You may use this software in any applications you build.

4. You may distribute this software provided that the software documentation and copyright notices are included and intact.

5. You may create and distribute modified versions of the software, such as ports to other Smalltalk dialects or derived work, provided that:

a. any modified version is expressly marked as such and is not misrepresented as the original software;

b. credit is given to the original software in the source code and documentation of the derived work;

c. the copyright notice at the top of this document accompanies copyright notices of any modified version.



Printed in the USA.

IBM®

Tivoli IBM Wireline Component - INPM · Netcool Performance Manager 1.3.1 IBM Wireline Component ... Chapter 4: Managing Tivoli ... 134 Working with ...

Documents