Tivoli Netcool Performance Manager 1.3 IBM Wireline ... · Netcool Performance Manager 1.3 IBM Wireline Component (Netcool/Proviso 5.2 ... Chapter 4: Installing Netcool ... 134 How

IBMNetcool Performance Manager 1.3Tivoli
Wireline Component (Netcool/Proviso 5.2)
Document Revision R2E3

Installation Guide: 1.3

Note

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

Copyright IBM Corp. 1997, 2010

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

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

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

Netcool/Proviso Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Typical Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Configuring Your Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Netcool/Proviso Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2: Installing and Configuring the Prerequisite Software . . . . . . . . . . . . . . . . . . . . . . 7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Pre-Installation Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Deployer Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Downloading the Netcool/Proviso Distribution to Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

General Oracle Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Assumed Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Installing the Oracle Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Shut down of performance impacting Oracle jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installing the Oracle Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 3: The Graphical Installation Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

The Installation Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

The Launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

The Topology Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

The Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 4: Installing Netcool/Proviso in a Distributed Environment . . . . . . . . . . . . . . . . . 81

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Disk Usage Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Netcool/Proviso Installation Guide, Version 5.2 v

Contents

Starting the Launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Installing the Topology Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Starting the Topology Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Creating a New Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Adding and Configuring the Netcool/Proviso Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Saving the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Opening an Existing Topology File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Starting the Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Primary Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Secondary Deployers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Pre-Deployment Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Deploying the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Primary Versus Secondary Deployers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Resuming a Partially Successful First-Time Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 5: Installing Netcool/Proviso as a Minimal Deployment . . . . . . . . . . . . . . . . . . . . 105

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Special Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Do Not Override Default Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Installing a Minimal Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

The Post-Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Chapter 6: Introduction to Installing Netcool/Proviso Technology Packs. . . . . . . . . . . 113

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

4.3-U/4.3-V Technology Pack Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

4.3-W and higher Technology Pack Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Chapter 7: Modifying the Current Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Opening a Deployed Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Adding a New Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Changing Configuration Parameters of Existing Netcool/Proviso Components . . . . . . . . . . . . . . . 118

Moving Components to a Different Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Moving a Deployed Collector to a Different Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

vi Netcool/Proviso Installation Guide, Version 5.2

Contents

Moving a Deployed SNMP Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Moving a Deployed UBA Bulk Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Chapter 8: Using the High Availability Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

HAM Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

The Parts of a Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

HAM Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Types of Spare Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Types of HAM Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Example HAM Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Resource Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

How the SNMP Collector Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

How Failover Works With the HAM and the SNMP Collector. . . . . . . . . . . . . . . . . . . . . . . . . . 136Obtaining Collector Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Creating a HAM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Topology Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Creating an Additional HAM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Modifying a HAM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Removing HAM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Stopping and Restarting Modified Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Viewing the Current Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Show Collector Process... Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Show Managed Definition... Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Chapter 9: Uninstalling Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Removing a Component from the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Restrictions and Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Removing a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Uninstalling Entire Netcool/Proviso System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Order of Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Restrictions and Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Performing the Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Uninstalling the Topology Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Residual Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Netcool/Proviso Installation Guide, Version 5.2 vii

Contents

Appendix A: Installing 4.3-U/4.3-V Netcool/Proviso Technology Packs . . . . . . . . . . 155

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Pre-Installation Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Installing Technology Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Adding UBA Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Adding a UBA Collector for UBA Packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Adding UBA Collectors for the Nortel CS2000 Technology Pack . . . . . . . . . . . . . . . . . . . . . . . 162

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Appendix B: Installing the Starter Kit with 4.3-U/4.3-V Technology Packs . . . . . . . . 167

Installing the Starter Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Starter Kit Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Stand-alone Technology Packs that are part of the Starter Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Where to Obtain Starter Kit Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Backing Up SNMP Inventory Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Appendix C: Installing 4.3-W and higher Netcool/Proviso Technology Packs . . . . 171

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Pre-Installation Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Backing Up Inventory Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Preparing to Install Technology Pack Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Preparing the Pack Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Installing Technology Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Adding UBA Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Adding a UBA Collector for UBA Packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Adding UBA Collectors for the Nortel CS2000 Technology Pack . . . . . . . . . . . . . . . . . . . . . . . 179

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Appendix D:Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Co-Location Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Appendix E:DataChannels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

viii Netcool/Proviso Installation Guide, Version 5.2

Contents

Data Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Management Programs and Watchdog Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194DataChannel Application Program Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Starting the DataLoad SNMP Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

DataChannel Management Components in a Distributed Configuration . . . . . . . . . . . . . . . . . . . . . 197

Manually Starting the Channel Manager Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

SNMP Traps from Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Adding DataChannels to an existing system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

DataChannel Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Appendix F:Aggregation Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Configuring Aggregation Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Installing Aggregation Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Linking DataView Groups to Timezones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Appendix G:Secure File Transfer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

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

Enabling SFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Installing OpenSSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Solaris Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Configuring OpenSSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Configuring the OpenSSH Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Configuring OpenSSH Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Generating Public and Private Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Testing OpenSSH and SFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Netcool/Provisio SFTP Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Appendix H:LDAP Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

LDAP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Appendix I:Deployer CLI Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Using the -DTarget Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Appendix J:Using Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Netcool/Proviso Installation Guide, Version 5.2 ix

Contents

Sample Properties Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

The Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Running the Deployer in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

The Topology Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Appendix K:Installing an Interim Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Installation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Behavior and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Installing a Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Appendix L:Error Codes and Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Deployer Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Topology Editor Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254InstallAnywhere Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

COI Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Deployer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Eclipse Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Trace Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Appendix M:Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Deployment Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Saving Installation Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Netcool/Proviso Component Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Topology Editor Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Telnet Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Java Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Testing Connectivity to the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Testing External Procedure Call Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

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

x Netcool/Proviso Installation Guide, Version 5.2

Contents

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

Additional Copyright Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

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

Netcool/Proviso Installation Guide, Version 5.2 xi

Contents

xii Netcool/Proviso Installation Guide, Version 5.2

Preface

IBM® Tivoli® Netcool® Performance Manager 1.3 is a bundled product consisting of 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 install the Netcool/Proviso product suite and the Oracle database management system. This guide assumes you are a network administrator or operations specialist who has knowledge of network management and installing applications on operating systems. Tivoli Netcool/Proviso is a component of the Tivoli Netcool Performance Manager solution.

Audience

The audience for this manual is the network administrator or operations specialist responsible for installing the Netcool/Proviso product suite on an enterprise network. To install Netcool/Proviso successfully, you should have a thorough understanding of the following subjects:

• Basic principles of TCP/IP networks and network management

• SNMP concepts

• Administration of the Linux, Solaris or AIX operating environment

• Administration of the Oracle database management system

• Netcool/Proviso

Organization

This guide is organized as follows:

Section Page

Chapter 1, Introduction 1

Chapter 2, Installing and Configuring the Prerequisite Software 7

Chapter 3, The Graphical Installation Interface 59

Chapter 4, Installing Netcool/Proviso in a Distributed Environment 81

Chapter 5, Installing Netcool/Proviso as a Minimal Deployment 105

Chapter 6, Introduction to Installing Netcool/Proviso Technology Packs 113

Chapter 7, Modifying the Current Deployment 115

Chapter 8, Using the High Availability Manager 125

Chapter 9, Uninstalling Components 147

Netcool/Proviso Installation Guide, Version 5.2 xiii

Preface

The Default UNIX Shell

The installation scripts and procedures in this manual generally presume, but do not require, the use of the Korn or Bash shells, and only Korn shell syntax is shown in examples. If you are a user of the C shell or Tcsh, make the necessary adjustments in the commands shown as examples throughout this manual.

This guide uses the following shell prompts in the examples:

• # (pound sign) indicates commands you perform when logged in as root.

• $ (dollar sign) indicates commands you perform when logged in as oracle or pvuser.

• SQL> indicates commands you perform at the SQL*Plus prompt.

The Netcool/Proviso Product Suite

Netcool/Proviso is made up of the following components:

• Netcool/Proviso DataMart is a set of management, configuration and troubleshooting GUIs that the Netcool/Proviso System Administrator uses to define policies and configuration, as well as verify and troubleshoot operations.

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

• Netcool/Proviso DataChannel aggregates the data collected through Netcool/Proviso DataLoad for use by the Netcool/Proviso DataView reporting functions. It also processes on-line calculations and detects real-time threshold violations.

• Netcool/Proviso DataView is a reliable application server for on-demand, web-based network reports.

• Netcool/Proviso Technology Packs extend the Netcool/Proviso system with service-ready reports for network operations, business development, and customer viewing.

Appendix A, Installing 4.3-U/4.3-V Netcool/Proviso Technology Packs 155

Appendix B, Installing the Starter Kit with 4.3-U/4.3-V Technology Packs 169

Appendix C, Installing 4.3-W and higher Netcool/Proviso Technology Packs 167

Appendix D, Deployment Considerations 185

Appendix E, DataChannels 193

Appendix F, Aggregation Sets 201

Appendix G, Secure File Transfer Installation 213

Appendix H, LDAP Integration 225

Appendix I, Deployer CLI Options 229

Appendix J, Using Silent Mode 233

Appendix K, Installing an Interim Fix 239

Appendix L, Error Codes and Log Files 243

Appendix M, Troubleshooting 261

Section Page

xiv Netcool/Proviso Installation Guide, Version 5.2

Preface

The following figure shows the different Netcool/Proviso modules.

Figure 1: Netcool/Proviso Modules

DataLoadcollects network data.

DataChannelcomputesaggregationsand stores datain DataMart.

DataMartprovides datamanagement

DataViewproduces andmanages reports.

and applications.

Netcool/Proviso 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:

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

Netcool/Proviso Installation Guide, Version 5.2 xv

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

Preface

xvi Netcool/Proviso Installation Guide, Version 5.2

Chapter 1: Introduction

This chapter provides an overview of the Netcool/Proviso product suite and provides important pre-installation setup information. In addition, this chapter provides an overview of the installation interface introduced in Version 5.2. The topics are as follows:

Netcool/Proviso Architecture

The Netcool/Proviso components run on:

• SPARC-based servers from Sun Microsystems® that run the Solaris™ operating system

• AIX® servers from IBM®

• Linux® servers

Exact, release-specific requirements, prerequisites, and recommendations for hardware and software are described in detail in the Netcool/Proviso Configuration Recommendations document.

You can work with Professional Services to plan and size the deployment of Netcool/Proviso components in your environment.

The following diagram provides a high-level overview of the Netcool/Proviso architecture.

Topic Page

Netcool/Proviso Architecture 1

Configuring Your Deployment 5

Typical Installation Process 3

Netcool/Proviso Distribution 5

Netcool/Proviso Installation Guide, Version 5.2 1


The Netcool/Proviso system components are as follows:

• Netcool/Proviso database — The Netcool/Proviso database is hosted on Oracle.

• Netcool/Proviso DataMart — Netcool/Proviso DataMart is the user and administrative interface to the Netcool/Proviso database and to other Netcool/Proviso components.

• Netcool/Proviso DataLoad — Netcool/Proviso DataLoad consists of one or more components that collect network statistical raw data from network devices and from network management systems.

• Netcool/Proviso DataChannel — Netcool/Proviso DataChannel is a collection of components that collect data from DataLoad collectors, aggregate and process the data, and load the data into the Netcool/Proviso database. DataChannel components also serve as the escalation point for collected data that is determined to be over threshold limits.

• Netcool/Proviso DataView — Netcool/Proviso DataView is the Web server hosting and analysis platform. This platform is used to display Web-based management reports based on network data aggregated and placed in the Netcool/Proviso database.

• Netcool/Proviso Technology Packs — Each technology pack is a set of components that describes the format and structure of network statistical data generated by network devices. Each technology pack is specific for a particular device, or class of devices; or for a particular company’s devices; or for a protocol (such as standard SNMP values) common to many devices.

• Tivoli Integrated Portal — The Tivoli Integrated Portal application provides a database-aware Web server foundation for the Web-based management reports displayed by Netcool/Proviso DataView. The Tivoli Integrated Portal application server is an essential component of each DataView installation.

2 Netcool/Proviso Installation Guide, Version 5.2


Typical Installation Process

There are two installation types documented within this manual.

• Installation of the Netcool\Proviso Minimal Deployment, also known as a Proof of Concept installation.

• A real-world Installation of Netcool\Proviso on a distributed system.

Minimal Installation Process:

If you are setting up a demonstration or evaluation system, it is possible to install all Netcool/Proviso components on a single server for Linux, Solaris or AIX systems. In this case your installation process will go as follows:

Distributed Installation Process:

A production Netcool/Proviso system that generates and produces management reports for a real-world network is likely to be installed on several servers. Netcool/Proviso components can be installed to run on as few as two or three servers, up to dozens of servers.

Table 1: Minimal Installation Process

1. These tasks are covered in the Pre-Installation Setup Tasks on page 9. They include the setting up of a remote X Window display and the changing of ethernet characteristics.

2. It is important to make sure you have all required software readily available and all prerequisite software installed before you begin. All prerequisite software is listed in the Overview on page 7of chapter 2.

3. A minimal deployment requires only the installation of the Oracle server and not the client. Carry out the steps described in General Oracle Setup Tasks on page 23 and the install process Installing the Oracle Server on page 26.

4. Perform the installation of the Netcool/Proviso minimal deployment, as described in Installing Netcool/Proviso as a Minimal Deployment on page 105.

5. Install any required tech packs as described in Introduction to Installing Netcool/Proviso Technology Packs on page 113.

Carry out Pre-Installation setup tasks

Gather and install all prerequisite software

Carry out general Oracle setup and Oracle Server install

Install Netcool\Proviso minimal deployment

Install the required Technology Packs



Table 2: Distributed Installation

1. Decide on the set of host systems to be used and where each Netcool\Proviso component is to be deployed. Consult the previous section, Netcool/Proviso Architecture on page 1, and Appendix D, Deployment Considerations.

2. These tasks are covered in the Pre-Installation Setup Tasks on page 9. They include the setting up of a remote X Window display and the changing of ethernet characteristics.

3. It is important to make sure you have all required software readily available to all host machines, and all prerequisite software installed before you begin. All prerequisite software is listed in the Overview on page 7of chapter 2.

4. Carry out the tasks described in General Oracle Setup Tasks on page 23 for each host, and the install process Installing the Oracle Server on page 26.

8. Create your Netcool\Proviso Topology, as described in Adding and Configuring the Netcool/Proviso Components on page 87.

7. The Oracle Server host is a good candidate from which to remotely deploy your Netcool\Proviso installation. Install the Topology Editor on this host, as described in Installing the Topology Editor on page 85.

6. Each system that does not host the Oracle Server, but which does host a Netcool\Proviso component requires the installation of the Oracle client, as described in Installing the Oracle Client on page 47.

5. Install the Oracle server. Follow the install process as described in Installing the Oracle Server on page 26.

9. Perform the installation of the Netcool\Proviso distributed deployment, as described in Deploying the Topology on page 99.

10. Install any required technology packs as described in Introduction to Installing Netcool/Proviso Technology Packs on page 113.

Decide on your Netcool\Proviso Topology

Carry out Pre-Installation setup tasks

Gather and install all prerequisite software

General Oracle Setup Tasks

Create your Netcool\Proviso Topology

Install the Topology Editor

Oracle client installation

Oracle server installation

Deploy your Netcool\Proviso distributed Topology

Install the required Technology Packs



Table 3 provides an example of where to install Netcool/Proviso components, using four servers. Use this example as a guide to help you determine where to install the Netcool/Proviso components in your environment.

It should be noted that TNPM does not support hybrid installations, that is, TNPM and its components must be installed on one system type, which can be one of Linux, AIX or Solaris. The only exception to this is the TNPM component DataLoad, which can be installed on a system that is different from that of other components.

Configuring Your Deployment

This guide provides instructions for installing Netcool/Proviso components, but not necessarily for configuring the installed components into a finished system that produces management reports. After going through the steps in this guide, you will have a set of running Netcool/Proviso components ready to configure into a fully functional system.

The goal of this guide is to get each component installed and running in its barest form. The running component does not necessarily have network statistical data flowing into and out of it yet. In particular, at the end of this installation procedure, there are no or few management reports that can be viewed in DataView.

Configuring installed components into a working system is the subject of other manuals in the Netcool/Proviso documentation set. Before configuring your deployment, you should be familiar with the information in Appendix D, Deployment Considerations.

Netcool/Proviso Distribution

The Netcool/Proviso distribution is available as a DVD/CD and as an electronic image. The instructions in this guide assume that you are installing from an electronic image.

Table 3: Netcool/Proviso Components Installed on Four Servers

Server Name Netcool/Proviso Components Hosted Notes

delphi Oracle server Netcool/Proviso DatabaseNetcool/Proviso DataMart Netcool/Proviso Discovery Server

Install the Topology Editor and primary deployer on this system. For more information, see The Topology Editor on page 64.

corinth Oracle client Netcool/Proviso DataLoad, SNMP collector Netcool/Proviso DataLoad, Bulk Load collector

You could install Netcool/Proviso components remotely on this system.

sparta Oracle client DataChannel

You could install Netcool/Proviso components remotely on this system

athens Oracle client Tivoli Integrated PortalNetcool/Proviso DataView

You could install Netcool/Proviso components remotely on this system. Your configuration can use a pre-existing Tivoli Integrated Portal, or install and include a new instance.



If you install the product from an electronic image, be sure to keep a copy of the distribution image in a well-known directory, because you will need this image in the future to make any changes to the environment, including uninstalling Netcool/Proviso.


Chapter 2: Installing and Configuring the Prerequisite Software

This chapter describes how to install and configure the prerequisite software for Netcool/Proviso. The topics are as follows:

Overview

Before beginning the Netcool/Proviso installation, you must install the prerequisite software listed in the Netcool/Proviso Configuration Recommendations, including:

• Oracle server — To use Oracle with Netcool/Proviso, you must install Oracle as described in this chapter — do not use a separate Oracle installation method provided by Oracle Corporation.

Oracle client — You must install Oracle client software on each system where you plan to install a Netcool/Proviso component, except for the system where you installed the Oracle server.

When you complete the steps in this chapter, the Oracle server and client will be installed and running, with tablespaces sized and ready to accept the installation of a Netcool/Proviso DataMart database. You can communicate with Oracle using the SQLPlus command-line utility.

The steps in this chapter use IBM-provided installation scripts to install and configure the Oracle database from the Oracle distribution and patch. For use with Netcool/Proviso, you must install Oracle as described in this chapter. Do not use a separate Oracle installation method provided by Oracle Corporation. You should obtain the official Oracle distribution from your edelivery site (after purchase of an Oracle license). See the Netcool/Proviso Configuration Recommendations for recommendations when purchasing a license from Oracle.

Note: The Netcool/Proviso script used to install Oracle is platform-independent and can be used to install on Solaris, AIX, or Linux, regardless of the operating system distribution media.

• OpenSSH — You must install and configure OpenSSH before installing Netcool/Proviso. For details, see Appendix G: Secure File Transfer Installation on page 213. Linux systems require the installation of VSFTP (Very Secure FTP).

Topic Page

Overview 7

Pre-Installation Setup Tasks 9

General Oracle Setup Tasks 23

Installing the Oracle Server 26

Installing the Oracle Client 47

Next Steps 58



• Web browser — The launchpad requires a Web browser. IBM recommends using Mozilla with the launchpad. For the complete list of supported browsers, see the Netcool/Proviso Configuration Recommendations document.

• Java — Java is used by DataMart, DataLoad, and the technology packs. You must ensure you are using the IBM JRE and not the RHEL JRE. The IBM JRE is supplied with the Topology Editor or with TIP. To ensure you are using the right JRE you can either:

— Set the JRE path to conform to that used by the Topology Editor, do this using the following commands (using the default location for the primary deployer):

PATH=/opt/IBM/proviso/topologyEditor/jre/bin:$PATH

export $PATH

— For a remote server, that is one that does not host the primary deployer, you must download and install the required JRE, and set the correct JRE path. See the Netcool/Proviso Configuration Recommendations document for JRE download details.

• Acrobat Reader — Adobe® Acrobat Reader® is free software that enables you to read the Netcool/Proviso documentation delivered in Portable Document Format (PDF). Note that Acrobat Reader requires the GIMP Toolkit (GTK+) and several additional libraries. See the Netcool/Proviso Configuration Recommendations for more information.

You can download Adobe Reader from the Adobe Web site (http://www.adobe.com).

See the Netcool/Proviso Configuration Recommendations document for the complete list of prerequisite software and their supported versions.

Supported Platforms

Refer to the following table for platform requirement information.

Netcool/Proviso Component Required Oracle Software

All Netcool/Proviso Components:

• Database

• DataView

• DataChannel

• DataLoad

• DataMart

Solaris 10 64-bitAIX 5.3 64-bitAIX 6.1 64-bitRHEL 5.5, 64-bit



Pre-Installation Setup Tasks

Before installing the prerequisite software, perform the following setup tasks:

• Setting Up a Remote X Window Display

• Changing the Ethernet Characteristics

• Adding the pvuser Login Name

• Setting the Resource Limits (AIX Only)

• Set the System Parameters (Solaris Only)

• Enable FTP on Linux Systems (Linux Only)

Step 1: Setting Up a Remote X Window Display

For most installations, it does not matter whether you use a Telnet, rlogin, Xterm, or Terminal window to get to a shell prompt.

However, some installation steps must be performed from a window that supports the X Window server protocols. This means that the steps described in later chapters must be run from an Xterm window on a remote system or from a terminal window on the target system’s graphical display. See the Netcool/Proviso Configuration Recommendations document for the list of supported X emulators.

Specifying the DISPLAY Environment Variable

If you use an X Window System shell window such as Xterm, you must set the DISPLAY environment variable to point to the IP address and screen number of the system you are using. Command sequences in this manual do not remind you at every stage to set this variable.

If you use the su command to become different users, be especially vigilant to set DISPLAY before running X Window System-compliant programs.

In general, set DISPLAY as follows:

$ DISPLAY=Host_IP_Address:0.0 $ export DISPLAY

To make sure the DISPLAY environment variable is set, use the echo command:

$ echo $DISPLAY

Disabling Access Control to the Display

If you encounter error messages when trying to run X Window System-based programs, you might need to temporarily disable X Window System access control so an installation step can proceed.

To disable access control:

1. Set the DISPLAY environment variable.

2. Enter the following command when logged in as root:

# /usr/openwin/bin/xhost +

Note that disabling access control is what enables access to the current machine from X clients on other machines.



Step 2: Changing the Ethernet Characteristics

Before installing Netcool/Proviso, you must force both the ethernet adapter and the port on the switch to 100 full duplex mode — autonegotiate settings are not enough.

AIX Systems

To change the setting to full duplex:

1. Using the System Management Interface Tool (SMIT), navigate to Devices > Communication > Ethernet Adapter > Change/Show Characteristics of an Ethernet Adapter.

2. Select your ethernet adapter (the default is ent0).

3. Change the Media Speed setting to 100_Full_Duplex.

4. Change the setting Apply change to DATABASE only to yes.

5. Set the port on the switch or router that the AIX node is plugged into to 100_Full_Duplex.

6. Reboot your system.

Important: If the AIX node is a virtual partition, you must perform these steps on the virtual I/O server (including the reboot).



Solaris Systems

This section describes how to set a network interface card (NIC) and a BGE network driver to full duplex mode.

NIC

To change the NIC to full duplex mode:

1. Determine which type of adapter you have by running the following command:

ifconfig -a

2. To determine the current settings of the NIC, run the command ndd -get /dev/hme with one of the following parameters:

• 1 — Up

• 0 — Down

• 0 — 10Mb/sec

• 1 — 100Mb/sec

• 0 — Half duplex

• 1 — Full duplex

• 0 — Off

• 1 — On

For example:

ndd -get /dev/hme link_status

In these commands, /dev/hme is your NIC; you might need to substitute your own /dev/xxx.

3. To set your NIC to 100Mb/s with full duplex for the current session, run the following commands:

ndd -set /dev/hme adv_100hdx_cap 0

ndd -set /dev/hme adv_100fdx_cap 1

ndd -set /dev/hme adv_autoneg_cap 0

However, these commands change the NIC settings for the current session only. If you reboot, the settings will be lost.

To make the settings permanent, edit the /etc/system file and add the following entries:

set hme:hme_adv_autoneg_cap=0

set hme:hme_adv_100hdx_cap=0

set hme:hme_adv_100fdx_cap=1

4. Verify that your NIC is functioning as required by rerunning the commands listed in Step 2.

Command Parameter Description

link_status Determines whether the link is up

link_speed Determines the link speed

link_mode Determines the duplex mode

adv_autoneg_cap Determines whether auto negotiation is on



BGE Network Driver

To change a BGE network driver to full duplex mode:

1. To determine the link speed and current duplex setting, run the following command:

% kstat bge:0 | egrep 'speed|duplex'

The output is similar to the following:

duplex full

ifspeed 100000000

link_duplex 2

link_speed 100

The parameters are as follows:

• 1 — Half-duplex

• 2 — Full duplex

• 10 — 10 Mb/sec

• 100 — 100 Mb/sec

• 1000 — 1 Gb/sec

2. Create a file named bge.conf in the /platform/uname -i/kernel/drv directory (for example, /platform/SUNW,Sun-Fire-V210/kernel/drv/bge.conf).

3. Add the following lines to the file:

speed=100;

full duplex=1;

4. Reboot the machine to have your changes take effect.

Linux Systems

Use your primary network interface to enable 100 full duplex mode.

To check if full duplex is enabled:

1. Enter the following command:

# dmesg | grep -i duplex

This should result in output similar to the following:

eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

2. Confirm the output contains the words:

Full Duplex

If this is not contained within the output, you must enable full duplex mode. The example output resulting from the command executed in step 1:

Parameter Description

link_duplex Determines the duplex setting

link_speed Determines the link speed



eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

indicate that the primary network interface is eth0.

The actions specified in the following process presume that your primary network interface is eth0.

To enable full duplex mode:

1. Open the file ifcfg-eth0, which is contained in:

/etc/sysconfig/network-scripts/

2. Add the ETHTOOL_OPTS setting by adding the following text:

ETHTOOL_OPTS="speed 100 duplex full autoneg off"

Note: The ETHTOOL_OPTS speed setting can be set to either 100 or 1000 depending on speed of connection available 100Mbit/s or 1000Mbit/s (1Gbit/s).

Step 3: Adding the pvuser Login Name

pvuser is the default name used within this document to describe the required Netcool/Proviso Unix user. The required user can be given any name of your choosing. However, for the remainder of this document this user will be referred to as “pvuser”.

Decide in advance where to place the home directory of the pvuser login username. Use a standard home directory mounted on /home or /export/home, as available.

Note: Do not place the home directory in the same location as the Netcool/Proviso program files. That is, do not use /opt/proviso or any other directory in /opt for the home directory.

Add the pvuser login name to every system on which you install a Netcool/Proviso component, including the system hosting the Oracle server.

Adding pvuser to a Standalone Computer

Use the steps in this section to add the pvuser login name to each standalone computer. These steps add the login name only to the local system files on each computer (that is, to the local /etc/passwd and /etc/shadow files). If your network uses a network-wide database of login names such as Yellow Pages or Network Information Services (NIS or NIS+), see Adding pvuser on an NIS-Managed Network on page 15.

To add pvuser:

1. Log in as root.

2. Set and export the DISPLAY environment variable (seeStep 1: Setting Up a Remote X Window Display on page 9).

3. If one does not already exist, create a group to which you can add pvuser. You can create a group with the name of your choice using the following command:

groupadd <group>

where:

— <group> is the name of the new group, for example, staff.

4. At a shell prompt, run the following command: # useradd -g <group> -m -d <home_dir>/<username> -k /etc/skel -s /bin/ksh <username>

Where:



— <group> is the name of the group to which you want to add pvuser.

— <home_dir> is the home directory for the new user, for example, /export/home/ can be used as the example home directory.

— <username> is the name of the new user. This can be set to any string.

Note: For the remainder of this document this user will be referred to as pvuser.

5. Set a password for pvuser :

# passwd pvuser

The system prompts you to specify a new password twice. The default pvuser password assumed by the Netcool/Proviso installer is pv. This can be set to a password conforming to your organization’s standards.



6. Test logging in as pvuser, either by logging out and back in, or with the su command, such as:

# su - pvuser

Confirm that you are logged in as pvuser with the id command:

$ id

These instructions create a pvuser login name with the following attributes:

Note: The pvuser account must have write access to the /tmp directory.

Multiple Computer Considerations

If you are creating the pvuser login name on more than one computer in your network, avoid confusion by specifying the same user ID number for each pvuser login name on each computer.

When you have created the first pvuser login name, log in as pvuser and run the id command. The system responds with the user name and user ID number (and the group name and group ID number). For example:

$ id uid=1001(pvuser) gid=10(staff)

When you create the pvuser login name on the next computer, add the –u option to the useradd command to specify the same user ID number:

# useradd -g <group> -m -d <home_dir>/pvuser -k /etc/skel -s /bin/ksh -u 1001 pvuser Where:

• <group> is the name of the group to which you want to add pvuser.

• <home_dir> is the home directory for the new user, for example, /export/home/ can be used as the example home directory.

• <username> is the name of the new user. This can be set to any string.

Adding pvuser on an NIS-Managed Network

If your site’s network uses NIS or NIS+ to manage a distributed set of login names, see your network administrator to determine whether pvuser should be added to each Netcool/Proviso computer’s local setup files, or to the network login name database.

Attribute Value

login name pvuser

member of group staff

home directory /home/export/pvuser

login shell Korn shell (/bin/ksh)

copy skeleton setup files (.profile, and so on) from this directory

/etc/skel



Step 4: Setting the Resource Limits (AIX Only)

On AIX systems, it is possible that the default user process limits are not adequate for Netcool/Proviso. Should this be the case do the following.

To set the user process limits on AIX systems:

1. Log in as root.

2. Change your working directory to /etc/security by entering the following command:

# cd /etc/security

3. Make a backup copy of the limits file by entering the following command:

# cp limits limits.ORIG

4. Using a text editor, open the limits file and set the following values:

default: fsize = -1 core = -1 cpu = -1 data = -1 rss = 65536 stack = 65536 nofiles = 2000

totalProcesses = 800

Note: Apply these settings to every AIX system running a Netcool/Proviso program: the database server, DataLoad servers, DataChannel servers, and DataMart servers.

5. Write and quit the file.

6. After modifying the settings, log off every Netcool/Proviso user and then log in again for the changes to take effect.

Step 5: Set the System Parameters (Solaris Only)

Before you install the Oracle server, set the Solaris shared memory and semaphore parameters as described in this section.

If using Solaris 10 containers, typically the variable in /etc/system is set only in the root container, and project variables are set for each container. Refer to Solaris 10 container documentation for further information.

When you install Netcool/Proviso, you specify the size of the deployment - small, medium, or large. The value you select affects the Oracle PROCESSES parameter. You must set the appropriate kernel parameter level in order for the deployment to work properly.

Note: These entries are only for the system running the Oracle server, not the Oracle client.

To set Solaris system parameters:

1. Set the NOEXEC_USER_STACK parameter in the system file:

1-a. Log in as root.

1-b. Change to the /etc directory:

# cd /etc



1-c. Create a backup of the system file, then open the system file with a text editor.

1-d. Set the parameter NOEXEC_USER_STACK to 1, by adding the following line at the bottom of the file:

set NOEXEC_USER_STACK=1

1-e. Save and exit the system file.

2. Set resource controls correctly. The parameters affected by the deployment size are project.max-sem-ids, process.max-sem-nsems, project.max-shm-memory, and project.max-shm-ids. These parameters define the maximum size of a semaphore set and the maximum number of semaphores in the system.

2-a. In Solaris 10, kernel parameters are replaced by resource controls. See Oracle® Database Installation Guide 10g Release 2 (10.2) for Solaris Operating System (SPARC 64-Bit) Part Number B15690-02 (http://download.oracle.com/docs/cd/B19306_01/install.102/b15690/pre_install.htm#sthref259), section 2.6: Configuring Kernel Parameters. See also Oracle Metalink ID 169706.1, Oracle Database on Unix AIX, HP-UX, Linux, Mac OS X, Solaris, Tru64 Unix Operating Systems Installation and Configuration Requirements Quick Reference (8.0.5 to 11.2), which lists Solaris requirements.

2-b. Oracle recommends the following values, noting that they are guidelines and should be tuned for production database systems. If you use a custom configuration, you must change the values of the parameters to the appropriate level.

2-c. Log in as the Oracle user (for example, oracle).

Resource Control Recommended Value

project.max-sem-ids 100

process.max-sem-nsems 256

project.max-shm-memory 429496725

project.max-shm-ids 100



2-d. To find the current kernel parameter settings, check the project id, and then check the resource control settings for that project id:

2-e. To change values, check the Solaris documentation for complete information on projects. Here is one example, which sets the value of project.max-shm-memory to 4GB. Log in as root and add a project, attached to the dba group (assuming the oracle user is part of the dba group), and set the value:

2-f. Check by logging back in as oracle, checking with id -p that the projid is now the new project number 100, and run prctl again to check that the max-shm-memory value has been updated.

3. Reboot your system before continuing to the next step.

Step 6: Enable FTP on Linux Systems (Linux Only)

By default, FTP is not enabled on Linux systems.

To enable FTP on your Linux host:

$ id -p

uid=4074(oracle) gid=9999(dba) projid=3(default)

$ prctl -n project.max-shm-memory -i project 3

project: 3: default

NAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-memory

privileged 1.95GB - deny -

system 16.0EB max deny -

$ prctl -n project.max-sem-ids -i project 3

project: 1: user.rootNAME PRIVILEGE VALUE FLAG ACTION RECIPIENT

project.max-sem-ids

privileged 128 - deny - system 16.8M max deny -

$ prctl -n project.max-shm-ids -i project 3project: 3: default

NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT

project.max-shm-ids privileged 128 - deny -

system 16.8M max deny -

$ prctl -n process.max-sem-nsems $$process: 12134: bash

NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT

process.max-sem-nsems privileged 600 - deny -

system 32.8M max deny -

# projadd -p 100 -G dba -c "Oracle Project" \

-K "project.max-shm-memory=(privileged,4G,deny)" group.dba

$ id -p

uid=4074(oracle) gid=9999(dba) projid=100(group.dba)

bash-3.00$ prctl -n project.max-shm-memory -i project 100

project: 100: group.dba

NAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-memory

privileged 4.00GB - deny -

system 16.0EB max deny -



1. Log in as root:

2. Change to the following directory:

# /etc/init.d

3. Run the following command

# ./vsftpd start



Deployer Pre-requisites

Minimum filesystem specification and pre-requisites for the Deployer script. The Deployer will check the for the items described under the following headings. You should ensure that all elements are installed before running the deployer.

Step 1: Operating System Check

The Deployer will fail if the required patches listed in this file are not installed. The Deployer performs a check on the operating system versions and that the minimum required packages are installed.

For more information on the complete set of requirements for installation on Linux, AIX and Solaris, please consult the Netcool/Proviso Configuration Recommendations documentation.

Step 2: Mount Points Check

The Deployer assesses the available filesystem space for the defined mount point locations. The space requirements are calculated based on:

• The defined topology: The more components added to a single server the more space is required on that server.

• The component install location: Any directory set as the install location for a component will require sufficient space to store that component. The default install directory is /opt. You do not have to use the default. This can be set to any directory location that has sufficient space.

• Remote installation of components: If components are being installed remotely, sufficient space must be assigned in the /tmp directory to store the software before it can be transferred to the remote servers.

For a statement of minimum space requirements per server in a distributed install or for a single server in a proof of concept install, please consult the Netcool/Proviso Configuration Recommendations documentation.

Step 3: Authentication Between Distributed Servers.

If you are performing an installation that has a topology covering a set of distributed servers, ensure that RSA keys have been cached between servers for root and pvuser prior to installation. If there are new servers that form part of installation topology which have not been authenticated, the installation will fail.

Note: pvuser is the required Netcool/Proviso Unix user. Adding this user to your system is described in Step 3: Adding the pvuser Login Name on page 13.



Downloading the Netcool/Proviso Distribution to Disk

To download the Netcool/Proviso distribution to a directory on a target server’s hard disk:

1. On the target host, log in as the Netcool/Proviso user, such as pvuser.

2. Create a directory to hold the contents of your Netcool/Proviso distribution. For example:

$ mkdir /var/tmp/cdproviso

Note: Any further references to this directory within the install will be made using the token <DIST_DIR>.

You will run a variety of scripts and programs from directories residing in the directory created on the hard drive, including:

— Oracle configuration script

— Pre-installation script

— Installation script

— Netcool/Proviso setup program

3. Download the Netcool/Proviso distribution to the host directory created in the previous step and expand the contents of the distribution package.

4. If the current host is the primary deployer (for more information, see Primary Versus Secondary Deployers on page 102), do the following:

4-a. Change to the following directory:

On Solaris systems:$ cd <DIST_DIR>/proviso/SOLARIS/DataChannel/SOL10/sparc

On AIX systems:$ cd <DIST_DIR>/proviso/AIX/DataChannel/AIX/powerpc

On Linux systems:$ cd <DIST_DIR>/proviso/RHEL/DataChannel/RHEL5/i686/

4-b. Untar the dc.tar file. For example:

tar -xvf dc.tar

5. If your environment has:

— DataMart residing on a host other than the primary deployer, or several DataMart hosts.

Repeat Step 1 on page 21 through Step 3 on page 21 to download the distribution to the Database host, and to each DataMart host in your environment.

To download the TCR distribution to a directory on a target server’s hard disk:

The TCR driver must be untarred so it can be used by the Proviso Common Installer. The following process ensures the user is required to specify the TCR media location only once:

1. Create a folder named TCR as a peer to the other Proviso Components, that is, DataView, DataChannel, etc. For example:

<DIST_DIR>/proviso/SOLARIS/TCR

2. Extract the TCR 1.3 inside this folder.

Should the user decide not to extract the tar as a peer to the other components, a TCR folder must still be created having a path to the TCR install.sh the same as: ./TCR/TCR13Installer/install.sh



Note: If the user extracts the tar directly into the same root location as the Proviso Components then the TCR launchpad.sh will overwrite the Proviso Installer launchpad.sh, meaning the launchpad cannot be started for the installer.



General Oracle Setup Tasks

To install Oracle for use with Netcool/Proviso, you need:

• An appropriately sized server with the operating system installed and running (for the Oracle server).

Note: For a basic overview of the minimum CPU speed, memory size, and disk configuration requirements for your Netcool/Proviso installation, see the Netcool/Proviso Configuration Recommendations documentation. For more detailed information you can contact IBM Professional Services.

• The current version of Netcool/Proviso software.

• The downloaded files for the Oracle installation.

• Oracle server patch files.

• Oracle client patch files.

• If you are installing Oracle on an AIX system, follow the instructions in Asynchronous I/O Support (AIX Only) on page 27 before installing Oracle.

Before installing Oracle, read the setup and password information. The topics are as follows:

• Step 1: Specifying a Basename for DB_USER_ROOT on page 23

• Step 2: Specifying Oracle Login Passwords on page 24

• Assumed Values on page 24

Step 1: Specifying a Basename for DB_USER_ROOT

Netcool/Proviso components use distinct Oracle login names so that database access can be controlled separately by component, and for database troubleshooting clarity. The Netcool/Proviso installation generates the appropriate login names for each Netcool/Proviso subsystem. You provide a basename, which the installation retains as the variable DB_USER_ROOT.

Note: This is not an operating system environment variable, but a variable used internally by the installer.

The default DB_USER_ROOT value is PV. IBM strongly encourages you to retain the default value.

Oracle login names are generated from the DB_USER_ROOT basename by appending a function or subsystem identifier to the basename, as in the following examples:

• PV_ADMIN

• PV_INSTALL

• PV_LDR

• PV_CHANNEL

• PV_COLL

• PV_CHNL_MANAGER

• PV_GUI

In addition, separate Oracle login names are generated for each Netcool/Proviso DataChannel and subsystem, identified by an appended channel number, as in the following examples:

• PV_CHANNEL_01

• PV_CHANNEL_02

• PV_LDR_01

• PV_LDR_02



Step 2: Specifying Oracle Login Passwords

For each component that requires an Oracle login name, you must provide a password for that login name. In every case, the installer uses the default Oracle password, PV.

Oracle passwords are not case-sensitive, so PV and pv are the same password. The default password is usually shown in uppercase, but is sometimes shown in lowercase. In both cases, the same default password is intended.

You can retain the default password, or enter passwords of your own according to your site password standards. You should use the same password for all Netcool/Proviso subsystem Oracle login names. If you use different passwords for each login name, keep a record of the passwords you assign to each login name.

The Netcool/Proviso installer uses PV for three default values, as described in Table 4.

Important: If you use a non-default value, you must remember to use the same value in all installation stages. For example, if you set your Oracle TNS name to PROV instead of PV, you must override the default PV entry in all subsequent steps that call for the TNS name.

Assumed Values

The steps in this chapter assume the following default values:

Table 4: Uses of PV as Default Values

Installer Default Value

Used As Recommendation

PV Default value of the DB_USER_ROOT variable, the basename on which Oracle login names are generated

In all instances, use the default value PV, unless your site has an explicit naming standard or an explicit password policy. PV or pv Default password for all Oracle login names

PV Default Oracle database name, also called the Oracle TNS name

Setting Value Assumed in this Chapter

Hostname of the Oracle server delphi

Oracle server program files installed in /opt/oracle

ORACLE_BASE = /opt/oracle

Operating system login name for Oracle user oracleNote: The default name created is oracle. However, you can set another name for the Oracle user.

Password for Oracle user oracle

ORACLE_SID = PV

TNS name for Netcool/Proviso database instance PV



Note: If your site has established naming or password conventions, you can substitute site-specific values for these settings. However, IBM strongly recommends using the default values the first time you install Netcool/Proviso. See Step 1: Specifying a Basename for DB_USER_ROOT on page 23 for more information.

Oracle installed in (ORACLE_HOME =) /opt/oracle/product/n

Note: The value of ORACLE_HOME cannot contain soft links to other directories or filesystems. Be sure to specify the entire absolute path to Oracle.

Oracle login name for database administrator (DBA) system

Password for Oracle DBA login name manager

DB_USER_ROOT = PV

Path for Oracle data, mount point 1 /raid_2/oradata

Path for Oracle data, mount point 2 /raid_3/oradata

Setting Value Assumed in this Chapter



Installing the Oracle Server

This section documents the steps to install the Oracle server and verify the installation. Install the Oracle server on the same machine that hosts DataMart.

The instructions in this section contain information on installing the Oracle 10 server software with the version 10.2.0.4 patch.

Step 1: Ensure that the Oracle User is not in NIS

The oracle user must be created locally, and must not be part of Network Information Services (NIS). The configure_ora script does not support oracle users who are part of NIS.

If the oracle account is already in NIS, do the following:

1. On the system where the Oracle database is to be installed, disable NIS. For more information, see your operating system documentation.

2. Run the configure_ora script to create a local oracle account (see Step 4: Run the Oracle Server Configuration Script on page 28).

3. Re-enable NIS.

Important: The local Oracle account should be used before the NIS Oracle user.

Step 2: Download the Oracle Distribution and Patch to Disk

To download the Oracle installation files to your target server’s hard disk:

1. Log in as root.

2. Create a directory to hold the contents of the Oracle distribution. For example:

# mkdir /var/tmp/oracle10201


3. Download the Oracle files to the /var/tmp/oracle10201 directory.

4. Locate the appropriate upgrade patch file for your version of Oracle on the Oracle Web site and download it to your /var/tmp/oracle10204 directory.

5. Unzip the oracle distribution files that now reside in the /var/tmp/oracle10201 and /var/tmp/oracle10204 directories.

Before you proceed to the next step, make sure that you obtain the upgrade instructions provided by Oracle for the patch. The instructions contain information on performing steps required for the upgrade that are not documented in this guide.

Before you proceed to the next step, make sure that you obtain the upgrade instructions provided by Oracle for the patch. The instructions contain information on performing steps required for the upgrade that are not documented in this guide. If you are installing the Oracle patch on an AIX system, you might need to run the sbinclean command and execute the catpatch.sql and utlrp.sql SQL scripts as part of the upgrade procedure. Additional requirements might exist for other platforms.



Step 3: Verify the Required Operating System Packages

On Solaris Systems

Before installing the Oracle server, make sure all the required Solaris packages and patches are installed on your system. All required packages and patches are specified in the Netcool/Proviso Configuration Recommendations document.

On AIX Systems

Before you install Oracle on AIX systems, verify that your system meets the required release level, as specified in the Netcool/Proviso Configuration Recommendations document.

Before installing the Oracle server, make sure all the required AIX packages and patches are installed on your system. All required packages and patches are specified in the Netcool/Proviso Configuration Recommendations document.

Asynchronous I/O Support (AIX Only)

Before installing Oracle on AIX 5.3 systems, you must set up asynchronous I/O (AIO), or the installation might fail.

Note: Asynchronous I/O (AIO) is not required for AIX 6.1 or later.

To set up asynchronous I/O:

1. Log in as root.

2. Enter the following command to check the current status of AIO support:

# lsdev -Cc aio

The status should be Available.

3. If the status shown is Defined, change the STATE to be configured at system restart option to Available by entering the following command:

# smit chaio

4. Reboot the system.

5. Re-enter the following command to check the current status of AIO support:

# lsdev -Cc aio

Verify that the status is set to Available.

6. Continue with Step 4: Run the Oracle Server Configuration Script on page 28.

On Linux Systems

Before you install Oracle on Linux systems, verify that your system meets the required release level, and make sure all required Linux packages and patches are installed on your system. Release level and all required packages and patches are specified in the Netcool/Proviso Configuration Recommendations document.



Step 4: Run the Oracle Server Configuration Script

In this step, you set up the Oracle environment using the configure_ora script provided with the Netcool/Proviso DataMart files on the Netcool/Proviso distribution. This script automatically creates the following configuration:

• Adds the dba and oinstall groups to /etc/group

• Adds the login name oracle, the primary group membership of which is dba and secondary group membership is oinstall, plus:

— The default login name created is oracle; however, you can set this to be any name of your choosing.

— ORACLE_BASE is set as the user home directory. If you would prefer to use a different home directory for the oracle user, create the oracle user manually before running configure_ora.

Note: If .profile already exists and ORACLE_HOME has already been set, then the configure_ora script will not update it. If you are changing the value of ORACLE_BASE or ORACLE_HOME, you must edit .profile manually to make these changes.

Note: It is possible for you to create the oracle user manually, before running the configure_ora script, but this is not recommended. Oracle requires that certain attributes are set for the oracle user, if these attributes are not in place, errors may occur.

• Creates the Oracle directory structure

• Creates startup and shutdown scripts for Oracle server processes

To configure the Oracle installation environment using the configure_ora script:

1. Log in as root.

2. Set the ORACLE_BASE environment variable to point to the top-level directory where you want the Oracle server files installed. The default installation directory is /opt/oracle. This can be set to any directory required by your organization.

For example:

# ORACLE_BASE=/opt/oracle # export ORACLE_BASE

Note: The configure_ora script places this variable into the oracle login account’s .profile file.

To check that the variable is set correctly, enter the following command:

# env | grep ORA


Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance

AIX systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX/instance

Linux systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL5/instance

where:

— <DIST_DIR> is the directory on the hard drive where you copied the contents of the Netcool/Proviso distribution in Downloading the Netcool/Proviso Distribution to Disk on page 21.



4. Run the Oracle configuration script by entering the following command:

# ./configure_ora

The following screen is displayed:

5. (Optional) To create a different name for the Oracle user other than the default oracle, type 1 and follow the instructions.

Note: The Oracle user will be referred to as “oracle” for the remainder of this document. If you have set the username to be a non-default string, that is, something other than “oracle” , make sure to substitute your non-default string for each occurrence of “oracle” within any task description.

6. Type 3 at the Choice prompt and press Enter.

The script creates the dba and oinstall groups and the ORACLE_BASE directory, unless they already exist:

7. Type y and press Enter.

The script creates the /opt/oracle directory and continues as follows:

8. Type y and press Enter.

--------------------------------------------------

configure_ora

Setting the Oracle environment <Current Date>--------------------------------------------------

OS ........... : [ SunOS 5.10 Generic ] Host ......... : [ delphi ]

Logname ...... : [ root ]

ORACLE_BASE .. : [ /opt/oracle ]

DBA group ................. : [ dba ] OUI Inventory group ....... : [ oinstall ]

Oracle Software owner ..... : [ oracle ]

Configure Oracle release .. : [ 10.2.0 ]

Menu : 1. Modify Oracle software owner.

2. Next supported release

3. Check environment.

0. Exit

Choice:

Checking environment...

Checking for group [ dba ] --> Created.

Checking for group [ oinstall ] --> Created. Checking ORACLE_BASE

** WARNING

** ORACLE_BASE directory does not exist.** [ /opt/oracle ]

**

** Create it ? (n/y) y

Checking for user [ oracle ] ** WARNING

** User [ oracle ] does not exist.

**** Create it locally ? (n/y) y



The script creates the oracle user and continues as follows:

9. Press the Enter key to continue. The configure_ora main screen is refreshed.

10. Type 0 and press Enter to exit the configure_ora script.

Note: You must set a password for the oracle login name (see Step 5: Set a Password for the Oracle Login Name on page 31).

Structure Created by the configure_ora Script

The script creates the Oracle directory structure. The following example shows the directory structure created for Oracle, where ORACLE_BASE was set to /opt/oracle:

/opt/oracle/product /opt/oracle/product/10.2.0 /opt/oracle/product/10.2.0/dbs /opt/oracle/admin /opt/oracle/admin/skeleton /opt/oracle/admin/skeleton/bin /opt/oracle/local

The script creates the following setup files:

Solaris specific files:

• /etc/init.d/dbora, which starts the Oracle Listener and database server automatically on each system boot

• Symbolic links to /etc/init.d/dbora in /etc/rc0.d, /etc/rc1.d, and /etc/rc2.d

• Oracle configuration files /var/opt/oracle/oratab and lsnrtab.

AIX specific files:

• /etc/inittab is modified to contain the dbstart and lsnrctl startup calls.

• /etc/rc.shutdown is modified to contain the dbshut and lsnrctl stop commands.

• Oracle configuration files /etc/oratab and /etc/lsnrtab.

--> Created. Checking for oracle directory tree :

[ /opt/oracle/product ] --> Created.

[ /opt/oracle/product/10.2.0 ] --> Created. [ /opt/oracle/product/10.2.0/dbs ] --> Created.

[ /opt/oracle/admin ] --> Created.

[ /opt/oracle/admin/skeleton ] --> Created. [ /opt/oracle/admin/skeleton/lib ] --> Ok.

[ /opt/oracle/admin/skeleton/lib/libpvmextc.so ] --> Created.

[ /opt/oracle/admin/skeleton/lib/libmultiTask.so ] --> Created. [ /opt/oracle/admin/skeleton/lib/libcmu.so ] --> Created.

[ /opt/oracle/admin/skeleton/bin ] --> Ok.

[ /opt/oracle/admin/skeleton/bin/snmptrap ] --> Created. [ /opt/oracle/local ] --> Created.

Checking for oracle .profile file --> Created.

Checking for dbora file --> Created. /etc/rc0.d/K10dbora link --> Created.

/etc/rc1.d/K10dbora link --> Created.

/etc/rc2.d/S99dbora link --> Created. Checking for dbora configuration files :

/var/opt/oracle/oratab --> Created.

/var/opt/oracle/lsnrtab --> Created.

Press Enter to continue...



Note: AIX does not use init.d.

Common files:

• A .profile file for the oracle user containing the following lines:

Note the following:

• The value of ORACLE_HOME cannot contain soft links to other directories or filesystems. Be sure to specify the entire absolute path to Oracle.

• You will add the ORACLE_SID variable to this file later, in Step 13: Set the ORACLE_SID Variable on page 39.

Step 5: Set a Password for the Oracle Login Name

The configure_ora script you ran in the previous section creates the oracle login name. You must assign a password for the oracle login name to maintain system security, and because subsequent installation steps expect the password to be already set.

To set a password:

1. Log in as root.


# passwd oracle

3. Enter and re-enter the password (oracle, by default) as prompted. The password is set.

Step 6: Run the Pre-Installation Script

Note: If you are installing on a Solaris system, it is required that you have already completed the tasks as described in Step 5: Set the System Parameters (Solaris Only) on page 16 before continuing your Oracle server installation on Solaris.

Run the pre-installation script that verifies readiness to install Oracle:

1. Log in as root.


# -- Begin Oracle Settings --

umask 022

ORACLE_BASE=/opt/oracle

ORACLE_HOME=$ORACLE_BASE/product/10.2.0NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1

ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data

LD_LIBRARY_PATH=$ORACLE_HOME/libTNS_ADMIN=$ORACLE_HOME/network/admin

PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin

EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.so

export PATH ORACLE_BASE ORACLE_HOME NLS_LANG

export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMINexport EXTPROC_DLLS

# -- End Oracle Settings --



Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance/ora_installer

AIX systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX/instance/ora_installer

Linux systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL5/instance/ora_installer

where:


3. Set the ORACLE_BASE environment variable. For example:


You must use the same ORACLE_BASE setting that you specified in Step 4: Run the Oracle Server Configuration Script on page 28.


# ./pre_install_as_root

The following messages indicate success:

If the script shows an error, correct the situation causing the error before proceeding to the next step.

Step 7: Run the rootpre.sh Script (AIX only)

To run the rootpre.sh script:

1. Log in as root or become superuser.


3. Change to the directory /var/tmp/oracle10201/database/rootpre.

Note: The Oracle server distribution is downloaded to /var/tmp/oracle10201 as per the instructions in the section Downloading the Netcool/Proviso Distribution to Disk on page 21.

4. Run the following command:

./rootpre.sh

rootpre.sh may return an error like the following:

This error can safely be ignored.

Note: For more information on this Oracle error, see Oracle Metalink Article 282036.1.

Checking that you are logged in as root --> Ok.

Checking ORACLE_BASE --> Ok.Checking oraInst.loc file --> Ok.

Configuring Asynchronous I/O....

Asynchronous I/O is not installed on this system.



Step 8: Verify PATH and Environment for the Oracle Login Name

Before proceeding to install Oracle server files, make sure the /usr/ccs/bin directory is in the PATH environment variable for the oracle login name.

To verify the PATH and environment:

1. Log in as oracle.

2. Set and export the DISPLAY environment variable.

If you are using the su command to become oracle, use a hyphen as the second argument so the oracle name’s login environment is loaded:

# su - oracle

3. Verify that the environment variable ORACLE_BASE has been set by entering the following command:

$ env | grep ORA

If the response does not include ORACLE_BASE=/opt/oracle, stop and make sure the .profile file was set for the oracle user as described in Step 4: Run the Oracle Server Configuration Script on page 28.

4. To verify the path, enter the following command:

$ echo $PATH

The output should show that /usr/ccs/bin is part of the search path. For example:

4-a. If the directory does not appear in the path, add it by entering the following commands:

$ PATH=$PATH:/usr/ccs/bin $ export PATH

Step 9: Install Oracle

There are two ways to install the Oracle database files:

• Using the Menu-Based Script on page 33: The Oracle installation script provided by IBM is used to install Oracle server, Oracle client, and to install upgrade patches. You should follow this step if you are not familiar with the Oracle installation process.

• Using Batch Mode on page 35: If you understand and are very familiar with the Oracle installation process, use batch mode.

Note: Choose one method, either the menu based script or the batch mode, do not implement both.

Using the Menu-Based Script

To install the Oracle server using the menu-based script:



Solaris systems:$ cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance/ora_installer

AIX systems:

/usr/bin:/opt/oracle/product/10.2.0/bin:/usr/ccs/bin



# cd <DIST_DIR>/proviso/AIX/DataBase/AIX/instance/ora_installer


where:


3. Enter the following command to start the installer:

$ ./perform_oracle_inst

The installation menu is displayed:

4. Verify the following settings:

4-a. The Oracle release number should be 10.2.0.

4-b. The Installation type field should be set to Server.

This field cycles between three settings: Server, Client, and Patch. Type 2 at the Choice prompt and press Enter until Server is displayed.

5. Type f at the Choice prompt and press Enter.

6. At the Choice prompt, enter the full path to the directory containing the installation files. For example:

7. Edit other menu settings as required.

For example, if you used non-default values for ORACLE_BASE or ORACLE_HOME, enter your settings until the menu shows the correct information.

--------------------------------------------------

perform_oracle_inst Installation of oracle binaries

<Current Date>-------------------------------------------------- OS ........... : [ SunOS 5.10 Generic ]

Host ......... : [ delphi ]

Logname ...... : [ oracle ]

Install Oracle release .... : [ 10.2.0 ]

Installation type.......... : [ Server ]

Enter the appropriate letter to modify the entries below:

a) ORACLE_BASE .. : [ /opt/oracle ] b) ORACLE_HOME .. : [ /opt/oracle/product/10.2.0 ]

c) DBA group ..................... : [ dba ]

d) OUI Inventory group ........... : [ oinstall ] e) Oracle Software owner ......... : [ oracle ]

f) Directory where CDs were copied:

[ ]Menu :

1. Next supported release

2. Set install type to: Client 3. Perform install

0. Exit

Choice :

Choice: f

Enter new value for CD directory: /var/tmp/oracle10201



8. To begin the Oracle installation, type 3 at the Choice prompt and press Enter. The installation script checks the environment, then asks whether you want to perform the installation.

9. Type Y at the Choice prompt and press Enter. The installation script starts installing Oracle and displays a series of status messages.

Note: You can safely ignore any “font.properties not found” messages in the output.

When the installation reaches the In Summary Page stage, the installation slows down significantly while Oracle files are copied and linked.

10. When the installation is complete, messages similar to the following are displayed:

Note: Write down the log file location to aid in troubleshooting if there is an installation error.

11. Type C and press Enter to return to the installation menu.

12. Type 0 and press Enter to exit the installation menu.

Using Batch Mode

Note: The IBM-provided Oracle installation script is used to install Oracle server, Oracle client, and to install upgrade patches to an existing Oracle server or client installation. You should follow this step if you are familiar with the Oracle installation process because it is more efficient to install Oracle using batch mode. If you do not understand the Oracle installation process, use the menu-based script (see Step 9 on page 33). If you installed the Oracle server, Oracle client, or upgrade patches to the Oracle server or Oracle client using the menu-based script, skip this step.

Batch mode is the only Oracle installation method that lets you change the settings for the Oracle primary and secondary group names, and the name of the oracle user login, if you have not used the default settings.

To install Oracle using batch mode:






where:

In End of Installation PageThe installation of Oracle10 Database was successful.

Please check /opt/oracle/oraInventory/logs/silentInstall2004-09-28_04-23-53PM.log

for more details.

The Oracle installation has completed. Please check the

messages above to determine if the install completed successfully. If you do not see successful completion

messages, consult the install log at:

/opt/oracle/oraInventory/logs

Press C to continue...




3. Open the perform_oracle_inst.ini file with a text editor. This file contains a number of Oracle installation settings similar to the following:

4. Make the necessary edits to the installation values. You can uncomment lines already included in the file to use those values for the installation.

For example, uncomment the following line to install Oracle server:

ORA_TYPE=Server

5. Save your edits and close the file.

6. Run the installation script with the b flag:

$ ./perform_oracle_inst b

# You can install either a server install,# a client install or a patchset. To

# install in batch mode you must enter a

# value. Uncomment the appropriate value.#

#ORA_TYPE=Server

#ORA_TYPE=Client#ORA_TYPE=Patch

## What is the directory where you copied the

# Oracle install CD’s.

#INSTALL_DIRECTORY=

## Script will automatically use the

# ORACLE_BASE defined in you environment

# or you can define it below.#

#ORACLE_BASE=

## Script will automatically use the

# ORACLE_HOME defined in you environment

# or you can define it below.#

#ORACLE_HOME=

#

# What unix account is the oracle software

# owner? A typical default is supplied.#

ORA_USR_OWN=oracle

#

# What is the oracle dba unix group name?

# A typical default is supplied.#

ORA_GRP_DBA=dba

#

# What is the oracle oui unix group name?

# A typical default is supplied.#

ORA_GRP_OUI=oinstall



The installation program verifies the values and performs the installation as shown in the section for the menu-based installation (see Step 9: Install Oracle on page 33).

Step 10: Run the root.sh Script

After successfully running an Oracle server installation, you must run the root.sh script.

To run the root.sh script:


2. Change to the directory where Oracle server files were installed. (This is the value of the ORACLE_HOME environment variable as seen by the oracle login name.) For example:

# cd /opt/oracle/product/10.2.0


./root.sh

Messages similar to the following are displayed:

4. If the default entry, /usr/local/bin, is writable by root, press Enter to accept the default value.

The default entry might be NFS-mounted at your site so it can be shared among several workstations and therefore might be write-protected. If so, enter the location of a machine-specific alternate bin directory. (You might need to create this alternate directory at a shell prompt first.) For example, enter /usr/delphi/bin.

5. The script continues as follows:

6. The script runs to completion with no further prompts.

Running Oracle10 root.sh script...

The following environment variables are set as: ORACLE_OWNER= oracle

ORACLE_HOME= /opt/oracle/product/10.2.0

Enter the full pathname of the local bin directory: [/usr/local/bin]:

...Adding entry to /var/opt/oracle/oratab file...

Entries will be added to the /var/opt/oracle/oratab file as needed by

Database Configuration Assistant when a database is createdFinished running generic part of root.sh script.

Now product-specific root actions will be performed.

#



Step 11: Install Oracle Patches

After you install Oracle, you must install the patchset for your version of Oracle to bring the Oracle version up to the IBM-validated patch level. See the Netcool/Proviso Configuration Recommendations documentation for up-to-date information about the required patches.

The basic patch required for Oracle 10g is patch version 10.2.0.4

In the interests of keeping this manual as short as possible, instructions provided by Oracle on how to perform an installation are not replicated within this manual. It is, however, recommended that before you complete this step that you obtain and read the upgrade instructions provided by Oracle for the patch that you wish to install. Your specific system may require supplementary steps not covered in this document, but which the Oracle instructions cover in detail.

For example, if you are installing the Oracle patch on an AIX system, it is possible you may need to run the sbinclean command and execute the catpatch.sql and utlrp.sql SQL scripts as part of the upgrade procedure. Additional requirements might exist for other platforms.

Note: Do not skip this step. Upgrade the Oracle version before you install the Netcool/Proviso database structure.

To install the Oracle patchset:




AIX systems:$ cd <DIST_DIR>/proviso/AIX/DataBase/AIX/instance/ora_installer

Linux systems:$ cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL5/instance/ora_installer

where:




4. Verify the following settings:

— The Oracle release number should be 10.2.0.

— The Installation type field should be set to Patch.

This field cycles between three settings: Server, Client, and Patch. Type 2 at the Choice prompt and press Enter until Patch is displayed.

5. To specify the path, type f at the Choice prompt and press Enter.

6. At the Choice prompt, enter the full path to the patch directory you created to hold the contents of the patch release (see Step 2: Download the Oracle Distribution and Patch to Disk on page 26). For example:

7. To begin the upgrade installation, type 3 at the Choice prompt and press Enter. The installation script checks the environment, then asks whether you want to perform the installation.

Choice: f




8. Type y at the Choice prompt and press Enter. The script proceeds to install the patch release files, showing a long series of messages much like the ones shown during installation of the base release.


In the messages, look for “success” notifications. If the script shows unsuccessful installation messages, check the installation log file specified in the message. Correct the error conditions identified in the log file, then rerun the patch installation and double-check all menu settings.

9. When the installation is complete, type C and press Enter.

Note: The message telling you to press C might have already scrolled past, because messages from several installation threads are written to the same screen.

10. Exit from the menu.

Note: If you try to start Oracle as the database administrator (DBA) at this point, the startup will fail because the file initPV.ora does not yet exist. This file is created during the Netcool/Proviso installation.

11. Carry out the steps as described in Step 10: Run the root.sh Script on page 37. This step is also required after an Oracle patch installation.

Step 12: Relax Permissions on ORACLE_HOME

When the install has finished, you must change permissions on the directories under ORACLE_HOME. During the installation, Oracle sets very restrictive permissions on ORACLE_HOME. Oracle provides a script that can be run after the install to relax permissions. To run the script:



$ cd ORACLE_HOME/install.

3. Enter the following command to start the script:

$ ./changePerm.sh

Step 13: Set the ORACLE_SID Variable

A system identifier (SID) identifies each Oracle database instance for internal connectivity on the Oracle server itself. (Connectivity from Oracle Clients to the server is controlled by the TNS names system configured later.) The environment variable for the system identifier is ORACLE_SID.

Decide on an SID to use for your Netcool/Proviso database instance. The assumed default for the Netcool/Proviso installation is PV. IBM recommends using this default SID unless your site has established Oracle SID naming conventions.

To set the ORACLE_SID environment variable:


2. Open the .profile file with a text editor.

3. Add the following line anywhere between the Begin and End Oracle Settings comment lines:

ORACLE_SID=PV; export ORACLE_SID



For example:

4. Save and exit the .profile file.

5. Enter the following shell command to activate the change to your profile:

$ . ./.profile

6. Make sure the variable was set by entering the following command:

$ env | grep ORACLE_SID

Step 14: Set Automatic Startup of the Database Instance

In this step, you configure your Oracle host to automatically start the Netcool/Proviso database instance at system startup time.

To set up automatic startup:


2. Depending on your operating system, change to the following directory:

Solaris systems: $ cd /var/opt/oracle

AIX systems:$ cd /etc

Linux Systems:

$ cd /etc

# -- Begin Oracle Settings --

umask 022

ORACLE_BASE=/opt/oracle

ORACLE_HOME=$ORACLE_BASE/product/10.2.0

ORACLE_SID=PV; export ORACLE_SIDNLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1

ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data

LD_LIBRARY_PATH=$ORACLE_HOME/libTNS_ADMIN=$ORACLE_HOME/network/admin

PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/delphi/bin

EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.so

export PATH ORACLE_BASE ORACLE_HOME NLS_LANG

export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMINexport EXTPROC_DLLS

# -- End Oracle Settings --



3. Edit the oratab file with a text editor. The last line of this file looks like this example:

4. Make the following edits to this line:

— Replace * with $ORACLE_SID (PV by default).

— Replace N with Y.

The last line should now be:

5. Save and close the oratab file.

Step 15: Configure the Oracle Listener

Note: Instead of creating the listener.ora file manually, as described in the steps that follow, you can create it by running the Oracle Net Configuration Assistant utility. See the Oracle Corporation documentation for information about Net Configuration Assistant.

The Oracle Listener process manages database connection requests from Oracle clients to an Oracle server.

To configure the Oracle Listener:


2. Change to one of the following directories:

$ cd $TNS_ADMIN

or$ cd /opt/oracle/product/10.2.0/network/admin

3. Copy the sample listener.ora contained in the opt/oracle/admin/skeleton/bin directory:$ cp opt/oracle/admin/skeleton/bin/template.exmaple_tnpm.listener.ora listener.ora

*:/opt/oracle/product/10.2.0:N

PV:/opt/oracle/product/10.2.0:Y



Note that by Oracle convention, the keywords in this file are in uppercase but uppercase is not required.

4. Using a text editor, change the following:

4-a. Replace the string yourhost in the line (HOST = yourhost) with the name of your Oracle server.

Note: Specify the host using the hostname only, do not use the IP address.

4-b. (optional) Replace the default port number 1521 in the line (PORT = 1521) with your required port number.

4-c. Write and quit the file.

5. Depending on your operating system, change to the following directory:

Solaris systems:$ cd /var/opt/oracle

AIX systems:$ cd /etc

Linux systems:$ cd /etc

6. Edit the lsnrtab file and add a line in the following format to the end of the file (after the initial comments):

LISTENER:value_of_ORACLE-HOME:Y

For example:

LISTENER:/opt/oracle/product/10.2.0:Y

In this syntax, LISTENER is the name of the listener process.


8. Test that the listener process works correctly by starting it manually using the following command:

# listener.ora network configuration file in directory# /opt/oracle/product/10.2.0/network/admin

LISTENER= (DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = yourhost) (PORT = 1521))

)

(ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC))

)

) )

SID_LIST_LISTENER = (SID_LIST =

(SID_DESC =

(SID_NAME = PLSExtProc) (ORACLE_HOME = /opt/oracle/product/10.2.0)

(PROGRAM = extproc)

) (SID_DESC =

(GLOBAL_DBNAME = PV.WORLD)

(SID_NAME = PV)

(ORACLE_HOME = /opt/oracle/product/10.2.0) )

)



lsnrctl start

(The lsnrctl command also accepts the stop and status arguments.) Look for a successful completion message.



Step 16: Configure the Oracle Net Client

In this step, you configure an Oracle Net client by setting up the TNS (Transport Network Substrate) service names for your Netcool/Proviso database instance.

To set up the TNS service names:


2. Change to one of the following directories:

$ cd $TNS_ADMIN

or$ cd /opt/oracle/product/10.2.0/network/admin

3. Create the sqlnet.ora file, which will manage Oracle network operations. You must create an sqlnet.ora file for both Oracle server and Oracle client installations. Follow these steps:

3-a. Copy the sample sqlnet.ora file, template.example_tnpm.sqlnet.ora, contained in the opt/oracle/admin/skeleton/bin/ directory:$ cp opt/oracle/admin/skeleton/bin/template.example_tnpm.sqlnet.ora sqlnet.ora

3-b. Add the following lines to this file:

NAMES.DIRECTORY_PATH=(TNSNAMES) NAMES.DEFAULT_DOMAIN=WORLD

For example:

Note: If you do not use WORLD as the DEFAULT_DOMAIN value, make sure you enter the same value for DEFAULT_DOMAIN in both sqlnet.ora and tnsnames.ora.

3-c. Write and quit the file.

4. Create the tnsnames.ora file, which maintains the relationships between logical node names and physical locations of Oracle Servers in the network.

# sqlnet.ora network configuration file in

# /opt/oracle/product/10.2.0/network/admin

NAMES.DIRECTORY_PATH=(TNSNAMES)

NAMES.DEFAULT_DOMAIN=WORLD



Follow these steps:

4-a. Enter lines similar to the following example, using the actual name of your Oracle server in the HOST=delphi line.

Note: Indents in this file must be preserved.

# tnsnames.ora network configuration file in # /opt/oracle/product/10.2.0/network/admin

#

# The EXTPROC entry only needs to exist in the # tnsnames.ora file on the Oracle server.

# For Oracle client installations, tnsnames.ora

# only needs the PV.WORLD entry.

EXTPROC_CONNECTION_DATA.WORLD =

(DESCRIPTION = (ADDRESS_LIST =

(ADDRESS =

(PROTOCOL = IPC) (KEY = EXTPROC)

)

) (CONNECT_DATA = (SID = PLSExtProc)

(PRESENTATION = RO)

) )

PV.WORLD =

(DESCRIPTION = (ENABLE=BROKEN)

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)

(HOST = delphi)

(PORT = 1521) )

)

(CONNECT_DATA = (SERVICE_NAME = PV.WORLD)

(INSTANCE_NAME = PV)

) )



Note the following:

— You will use the value in the INSTANCE_NAME field as the TNS entry when installing Netcool/Proviso DataMart.

— IBM strongly recommends that you include the line (ENABLE=BROKEN) in the PV.WORLD entry, as shown in the example. This parameter setting prevents CME processes from hanging in the event that the CME is disconnected from the database before results are returned to the CME.

— If configuring tnsnames.ora for a server installation, be sure to append the same domain suffix to all entries including EXTPROC_CONNECTION_DATA that you specified for the NAMES.DEFAULT_DOMAIN entry in the sqlnet.ora file. That is, append.WORLD to each entry.

4-b. Write and quit the file.

5. Test the Oracle Net configuration by entering a command with the following syntax:

tnsping Net_service_name.domain 10

For example:

$ tnsping PV.WORLD 10

Look for successful completion messages (OK).

To test without using the domain suffix, enter a command with the following syntax:

tnsping Net_service_name 10

For example:

$ tnsping PV 10

Note: If either test is not successful, check your configuration and retest.

Shut down of performance impacting Oracle jobs

It should be noted that the following Oracle jobs are automatically disabled by the installation code in order to maintain an acceptable level of performance:

• GATHER_STATS_JOB: statistics gathering job.

• AUTO_SPACE_ADVISOR_JOB: auto space advisor maintenance job

• MGMT_CONFIG_JOB: Configuration collection job.

• MGMT_STATS_CONFIG_JOB: OCM Statistics collection job.

It is recommended that these jobs should remain shut down. Should you discern any impact to performance, please confirm that these jobs are not in operation.



Installing the Oracle Client

You must install Oracle client software on each system where you plan to install a Netcool/Proviso component, with the exception of the system where you installed the Oracle server.

The instructions in this section contain information on installing the Oracle client software with the version 10.2.0.4 patch.

Step 1: Ensure that the Oracle User is not in NIS

The oracle user must be created locally, and must not be part of Network Information Services (NIS). The configure_ora script does not support oracle users who are part of NIS.

If the oracle account is already in NIS, do the following:

1. On the system where the Oracle database is to be installed, disable NIS. For more information, see your operating system documentation.

2. Run the configure_client script to create a local oracle account (see Step 4: Run the Oracle Server Configuration Script on page 28).

3. Re-enable NIS.

Important: The local Oracle account should be used before the NIS oracle user.

Step 2: Download the Oracle Distribution and Patch to Disk

Download each Oracle installation file to a separate directory on your target server’s hard disk or to a network-accessible shared disk.

To download the files to disk:



3. Create a directory to hold the contents of the Oracle distribution. For example:



4. Download the Oracle 10.2.0.1 files to the /var/tmp/oracle10201 directory.

5. Locate the appropriate upgrade patch file for your version of Oracle on the Oracle Web site and download it to your /var/tmp/oracle10204 directory.

6. Unzip the oracle distribution files that now reside in the /var/tmp/oracle10201 and /var/tmp/oracle10204 directories.

See your database administrator to determine whether there are any company-specific requirements for installing Oracle in your environment.



Step 3: Run the Oracle Client Configuration Script

The Oracle client configuration script is a shell script that creates the environment for the client software installation on the local system. This script is named configure_client and is located with the Netcool/Proviso files that you obtained in Downloading the Netcool/Proviso Distribution to Disk on page 21. If you are performing this step as part of an upgrade procedure, make sure that you run the configuration script provided with the target version of Netcool/Proviso.

The client configuration script makes the following changes to the local system:

• Adds the dba and oinstall groups to /etc/group.

• Adds the Solaris login name oracle, whose primary group membership is dba, and secondary group membership is oinstall.

• Creates the Oracle client directory structure. When you create the environment for patch version 10.2.0.4, the default location for this directory structure is $ORACLE_BASE/product/10.2.0. You specify this directory as the target location when you install the Oracle client.

To configure the Oracle installation environment:

1. Log in as root.

2. Set the ORACLE_BASE environment variable to point to the top-level directory where you want the Oracle client files installed. The default installation directory is /opt/oracle.

For example:


Note: The configure_client script places this variable into the oracle login name’s .profile file.

To check that the variable is set correctly, enter the following command:

# env | grep ORA


Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance

AIX systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX/instance

Linux systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL5/instance/

where:


4. Run the Oracle configuration script using the following command:

# ./configure_client



The following screen is displayed:

5. (Optional) To create a different name for the Oracle user other than the default oracle, type 1 and follow the instructions.

Note: The Oracle user will be referred to as “oracle” for the remainder of this document. If you have set the username to be a non-default string, that is, something other than “oracle” , make sure to substitute your non-default string for each occurance of “oracle” within any task description.

6. Type 3 at the Choice prompt and press Enter.

The script creates the dba and oinstall groups, and the ORACLE_BASE directory, unless they already exist.

If prompted, type y and press Enter.

The script creates the /opt/oracle directory and continues as follows:

If prompted, type y to create the oracle user and press Enter.

--------------------------------------------------configure_client

Setting the Oracle client environment

<Current Date>--------------------------------------------------

OS ........... : [ SunOS 5.10 Generic ]

Host ......... : [ corinth ] Logname ...... : [ root ]

ORACLE_BASE .. : [ /opt/oracle ]

DBA group ................. : [ dba ]

OUI Inventory group ....... : [ oinstall ] Oracle Software owner ..... : [ oracle ]

Configure Oracle release .. : [ 10.2.0 ]

Menu :

1. Modify Oracle software owner. 2. Next supported release.

3. Check environment.

4. Add 10.2.0.4 client support. 0. Exit

Choice:

Checking environment...

Checking for group [ dba ] --> Created.

Checking for group [ oinstall ] --> Created. Checking ORACLE_BASE

** WARNING

** ORACLE_BASE directory does not exist.** [ /opt/oracle ]

**

** Create it ? (n/y) y

Checking for user [ oracle ] ** WARNING

** User [ oracle ] does not exist.

**** Create it locally ? (n/y) y



The script creates the oracle user and continues as follows:

7. Press Enter to continue. The configure_client main screen is displayed.

8. Type 0 and press Enter to exit the script.

Step 4: Set a Password for the Oracle Login Name

The configure_client script you ran in the previous section creates the oracle login name. You must assign a password for the oracle login name to maintain system security, and because upcoming installation scripts expect a password to be already set.

To set the password:

1. Log in as root,

2. Enter the command:

# passwd oracle

3. Enter and re-enter the password (oracle, by default) as prompted. The password is set.

--> Created. Checking for oracle directory tree :

[ /opt/oracle/product ] --> Created.

[ /opt/oracle/product ] --> Created. [ /opt/oracle/product/9.2.0 ] --> Created.

Checking for oracle .profile file --> Created.

Press Enter to continue...



Step 5: Run the Pre-Installation Script

Run the pre-installation script that verifies readiness to install Oracle:

1. Log in as root.


Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance/ora_installer



where:


3. Set the ORACLE_BASE environment variable. For example:


You must use the same ORACLE_BASE setting that you specified in Step 3: Run the Oracle Client Configuration Script on page 48.


# ./pre_install_as_root

The following messages indicate success:

If the script shows an error, correct the situation causing the error before proceeding to the next step.

Step 6: Verify the PATH and Environment for the Oracle Login Name

Before proceeding to install Oracle client files, make sure the /usr/ccs/bin directory is in the PATH environment variable for the oracle login name.

To verify the PATH and environment:



If you are using the su command to become oracle, use a hyphen as the second argument so the oracle name’s login environment is loaded:

$ su - oracle

3. Verify that the environment variable ORACLE_BASE is set by entering the following command:

$ env | grep ORA

If the response does not include ORACLE_BASE=/opt/oracle, stop and make sure the .profile file was set for the oracle user as described in Step 4: Run the Oracle Server Configuration Script on page 28.

Checking that you are logged in as root --> Ok.

Checking ORACLE_BASE --> Ok.Checking oraInst.loc file --> Ok.



4. To verify the path, enter the following command:

$ echo $PATH

The output should show that /usr/ccs/bin is part of the search path. For example:

5. If the directory does not appear in the path, add it by entering the following commands:

$ PATH=$PATH:/usr/ccs/bin $ export PATH

Step 7: Install the Oracle Client

The Oracle installation script is a shell script that you can use to install the Oracle server, Oracle client software, or patches to existing installations of the Oracle server and client. This script is named perform_oracle_inst and is located with the Netcool/Proviso files that you obtained in Downloading the Netcool/Proviso Distribution to Disk on page 21. This script is provided by IBM as part of the Netcool/Proviso installation package.

An Oracle client installation is not usable until the following Net configuration files are configured and installed:

• tnsnames.ora

• sqlnet.ora

You will configure these files in later steps.

To install the Oracle client:






where:




/usr/bin:/opt/oracle/product/10.2.0/bin:/usr/ccs/bin



The installation menu is displayed:

4. Enter f at the Choice prompt and press Enter.

5. Enter the full path to the directory you created to hold the Oracle distribution in Step 2: Download the Oracle Distribution and Patch to Disk on page 26. For example:

6. Edit any other menu settings as necessary. Make sure that the values for ORACLE_BASE and ORACLE_HOME correspond to the locations you specified when you ran the Oracle client configuration script.

7. To start the Oracle installation, type 3 at the Choice prompt and press Enter.

8. The installation script checks the environment, then asks whether you want to perform the installation. Type Y at the Choice prompt and press Enter. The installation script starts installing Oracle and displays a series of status messages.


When the installation reaches the In Summary Page stage, the installation slows down significantly while Oracle files are copied and linked.

9. When the installation process completes, the installation displays a success message. Write down the log file location to aid in troubleshooting if there is an installation error.

10. Type C and press Enter to return to the installation menu.

11. Type 0 and press Enter to exit the installation menu.

12. Perform the steps in Step 8: Run the root.sh Script on page 54.

--------------------------------------------------perform_oracle_inst

Installation of oracle binaries

<Current Date>--------------------------------------------------

OS ........... : [ SunOS 5.10 Generic ]

Host ......... : [ delphi ] Logname ...... : [ oracle ]

Install Oracle release .... : [ 10.2.0 ] Installation type.......... : [ Client ]

Enter the appropriate letter to modify the entries below:

a) ORACLE_BASE .. : [ /opt/oracle ]

b) ORACLE_HOME .. : [ /opt/oracle/product/10.2.0 ] c) DBA group ..................... : [ dba ]

d) OUI Inventory group ........... : [ oinstall ]

e) Oracle Software owner ......... : [ oracle ] f) Directory where CDs were copied:

[ ]

Menu : 1. Next supported release

2. Set install type to: Client

3. Perform install

0. Exit

Choice :

Choice: f




Step 8: Run the root.sh Script

After successfully running an Oracle client installation, you must run the root.sh script.

Note: To view the messages and screens that are displayed by the script, see the corresponding step in the Oracle server installation (page 37).

To run the root.sh script:

1. Log in as root.


3. Change to the directory where Oracle client files were installed. (This is the value of the ORACLE_HOME environment variable as seen by the oracle login name.) For example:

# cd /opt/oracle/product/10.2.0


./root.sh

5. If the default entry, /usr/local/bin, is writable by root, press Enter to accept the default value.

The default entry may be NFS-mounted at your site so that it can be shared among several Sun workstations and may thereby be write-protected. If so, enter the location of a machine-specific alternate bin directory. (You may have to create this alternate directory first at a shell prompt.) For example, enter: /usr/corinth/bin.

6. The script displays a series of informational messages and runs to completion with no further prompts.

Step 9: Install Oracle Patches

After you install the Oracle client software, you must install patch version 10.2.0.4.

Note: Do not skip this step. Upgrade the Oracle version before you install the Netcool/Proviso database structure.

To install the Oracle patchset:

1. Follow the instructions to run the perform_oracle_inst script, as shown in Step 11: Install Oracle Patches on page 38. Go through the menus as described in that section, with the following changes:

1-a. Enter 2 at the Choice prompt and press Enter until the Installation type field is set to Patch.

1-b. Type f at the Choice prompt and press Enter.

1-c. At the Choice prompt, type the full path to the patch directory you created in Download the Oracle Distribution and Patch to Disk to hold the client patch 10.2.0.4 contents. For example:

2. Type 3 at the Choice prompt and press Enter. The script checks the environment and displays a series of messages.

3. Type y at the Choice prompt and press Enter to begin the patch installation. The script proceeds to install the patch release files, showing a series of messages much like the ones shown during installation of the base release.


Choice: fEnter new value for CD directory: /var/tmp/oracle10204



4. Watch the script’s messages for success entries.

Note: If the script shows unsuccessful installation messages, check the installation log file named in the message. Correct the error conditions identified in the log file, then rerun the patch installation and double-check all menu settings.

5. At the Choice prompt, type C and press Enter to continue.

The message telling you to press C may have already scrolled past, because messages from several installation threads are written to the same screen. If the installation has paused, type C to continue.Relax Permissions on ORACLE_HOME






$ ./changePerm.sh

Step 10: Relax Permissions on ORACLE_HOME






$ ./changePerm.sh

Step 11: Configure the Oracle Net Client

Next, you configure the Oracle Net client by setting up the TNS (Transport Network Substrate) service names for your Netcool/Proviso database instance. You must perform this step for each instance of the Oracle client software that you installed on the system.

You must configure sqlnet.ora and tnsnames.ora files for both Oracle server and Oracle client installations. However, the tnsnames.ora file for client installations should not have the EXTPROC_CONNECTION_DATA section.

If you are installing DataView and one or more other Netcool/Proviso components on the same system, you must make sure that the tnsnames.ora and sqlnet.ora files for each set of client software are identical. The easiest way to do this is to create these files when you are configuring the first client instance for Net and then to copy it to the corresponding directory when you configure the second instance.



Create the sqlnet.ora File

The sqlnet.ora file manages Oracle network operations. You can create a new sqlnet.ora file, or FTP the file from your Oracle server.

To set up the TNS service names:



$ cd $ORACLE_HOME/network/admin

3. To create the sqlnet.ora file:

— copying the template file from opt/oracle/admin/skeleton/bin/.$ cp opt/oracle/admin/skeleton/bin/template.exmaple_tnpm.sqlnet.ora sqlnet.ora

— FTP the file from your Oracle server.

4. Add the following lines to it:

NAMES.DIRECTORY_PATH=(TNSNAMES) NAMES.DEFAULT_DOMAIN=WORLD

For example:

Note: If you do not use WORLD as the DEFAULT_DOMAIN value, make sure you enter the same value for DEFAULT_DOMAIN in both sqlnet.ora and tnsnames.ora.

5. Write and quit the sqlnet.ora file.

Create the tnsnames.ora File

The tnsnames.ora file maintains the relationships between logical node names and physical locations of Oracle servers in the network. You can create a new tnsnames.ora file, or FTP the file from your Oracle server.

1. To create the tnsnames.ora file:

— copying the template file from opt/oracle/admin/skeleton/bin/.$ cp opt/oracle/admin/skeleton/bin/template.exmaple_tnpm.tnsnames.ora tnsnames.ora

— FTP the file from your Oracle server.

2. Add the following lines:

# sqlnet.ora network configuration file in

# /opt/oracle/product/10.2.0/network/admin

NAMES.DIRECTORY_PATH=(TNSNAMES)

NAMES.DEFAULT_DOMAIN=WORLD



Note: Indents in this file must be preserved.

3. Replace the string yourhost in the line (HOST = yourhost) with the name of your Oracle server.

Note the following:

— You will use the value in the INSTANCE_NAME field as the TNS entry when installing DataMart.

— If you reconfigure the Oracle client to connect to a different Oracle database in another Netcool/Proviso installation, be sure you update the HOST entry in the tnsnames.ora file, then restart the Oracle client.

— Specify the host using the hostname only, do not use the IP address.

4. (optional) Replace the default port number 1521 in the line (PORT = 1521) with your required port number.


# tnsnames.ora network configuration file in # /opt/oracle/product/10.2.0/network/admin

#

# For Oracle client installations, tnsnames.ora# only needs the PV.WORLD entry.

PV.WORLD = (DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)

(HOST = yourhost)

(PORT = 1521) )

)

(CONNECT_DATA = (SERVICE_NAME = PV.WORLD)

(INSTANCE_NAME = PV)

) )



Test the Oracle Net Configuration

To test the Oracle Net configuration:


2. Enter a command with the following syntax:

tnsping Net_service_name 10

For example:

tnsping PV.WORLD 10

3. Test again, using the same Net instance name without the domain suffix:

tnsping PV 10

Look for successful completion messages (OK).

Next Steps

Once you have installed the prerequisite software, you are ready to begin the actual installation of Netcool/Proviso. Depending on the type of installation you require, follow the directions in the appropriate chapter:

• Chapter 4, Installing Netcool/Proviso in a Distributed Environment — Describes how to install Netcool/Proviso in a distributed production environment.

• Chapter 5, Installing Netcool/Proviso as a Minimal Deployment — Describes how to install Netcool/Proviso as a minimal deployment, which is used primarily for demonstration or evaluation purposes.

• If you are planning on Installing Netcool/Proviso as a distributed environment that uses clustering for high availability, please review the Netcool/Proviso HA (High Availability) documentation, which is available for download by going to http://www-01.ibm.com/software/brandcatalog/opal/ and searching for “Netcool Proviso HA Documentation“.


http://www-01.ibm.com/software/brandcatalog/opal/

Chapter 3: The Graphical Installation Interface

This chapter provides an overview of the Netcool/Proviso graphical tools that are used to describe and install the product. This chapter does not describe the installation procedure, only the tools used to perform it. The topics are as follows:

Topic Page

The Installation Tools 60

The Launchpad 62

The Topology Editor 64

The Deployer 76



The Installation Tools

Netcool/Proviso Version 5.2 provides a graphical installation interface that enables you to easily configure the infrastructure and then install the Netcool/Proviso components. This graphical interface has the following components:

• Launchpad — This front-end panel provides a common starting point for installing and configuring Netcool/Proviso. From this Web page, you can perform operations such as launching the Topology Editor, running the deployer, and so on.

• Topology Editor — This interface enables you to define the Netcool/Proviso component layout and configuration and view it in tree form. The Topology Editor offers several different graphical views, including the Logical, Physical, and Technology Pack views. When you are done creating the installation plan (the topology), you save it to an XML file.

• Deployer — This wizard presents a series of pages to guide you through each step of the installation. The deployer runs a series of installation scripts to install the Netcool/Proviso components according to the topology XML file.

• Technology Pack Installer — This installer presents a series of pages to guide you through each step of the technology pack installation. See Chapter 6, Installing Technology Packs for more information about this installer.

Previous versions stored configuration information in files named dc.cfg and dl.cfg. This information is now located in the Netcool/Proviso database. You specify these configuration settings using the Topology Editor. For more information, see Changing Configuration Parameters of Existing Netcool/Proviso Components on page 118.

Figure 2 shows how the installation interfaces communicate with each other.

Figure 2: Installation Interfaces

As shown in the figure, the launchpad provides a common starting point for installing and configuring Netcool/Proviso. You can use it to install and then open the Topology Editor.

When you install Netcool/Proviso in a distributed environment, you must first create the topology file using the Topology Editor. If you are performing a minimal deployment installation, the deployer uses a predefined topology file.



The deployer installs the Netcool/Proviso components according to the topology file supplied to it, then saves the file in the database.

For detailed information about how to use each interface, see the following topics:

• The Launchpad on page 62

• The Topology Editor on page 64

• The Deployer on page 76



The Launchpad

The launchpad provides an easy-to-use starting point for the different interfaces that perform common Netcool/Proviso operations. For example, the launchpad provides access to the Topology Editor, the Deployer, and the Technology Pack Installer.

You must have a Web browser installed in order to run the launchpad. Mozilla is the recommended browser.

The launchpad has two sections: the left side of the page lists the available operations and the right side displays information, links, and instructions for the selected operation, as shown in Figure 3.

Figure 3: Netcool/Proviso Launchpad



The available operations are as follows:

• Product Information — Provides an overview of Netcool/Proviso, including a link to the Information Center.

• Prerequisite Information — Lists the Oracle version required for this release.

• Install Topology Editor — Enables you to install or start the Topology Editor. The Topology Editor enables you to create or modify the Netcool/Proviso topology, which describes the Netcool/Proviso product layout and configuration. For information about how to use the Topology Editor, see The Topology Editor on page 64; for procedural instructions on creating a topology, see Chapter 4, Installing Netcool/Proviso in a Distributed Environment.

• Install Technology Pack — Launches the Technology Pack Installer. For detailed information about installing technology packs, see Chapter 6, Installing Technology Packs.

• Upgrade Preparation — Currently, this functionality is not supported.

• Netcool/Proviso Configuration Update — Launches a tool that enables you to perform configuration changes to the Netcool/Proviso database.

• Install Tivoli Netcool/Proviso 5.2 for Minimal Deployment — Installs a minimal deployment version of Netcool/Proviso. A minimal deployment installation is used primarily for demonstration or evaluation purposes. For detailed information, see Chapter 5, Installing Netcool/Proviso as a Minimal Deployment.

• Start Tivoli Netcool/Proviso 5.2 Maintenance Deployer — Starts the wizard that enables you to install a patch release of Netcool/Proviso. For detailed information, see Appendix K, Installing an Interim Fix.

• Start Deployer — Starts a secondary deployer. For information about how to use the deployer, see The Deployer on page 76; for procedural instructions on installing Netcool/Proviso, see Starting the Deployer on page 98.

• Exit — Closes the launchpad. Alternatively, click the X in the upper, right-hand corner of the launchpad.

To perform an operation:

• Click an option to display the corresponding information or instructions on the right side of the page.

For information about starting the launchpad, see Starting the Launchpad on page 83.



The Topology Editor

The Topology Editor enables you to graphically set up the Netcool/Proviso infrastructure; the infrastructure is then saved to an XML file (named topology.xml by default). The deployer uses this XML file as input to install the Netcool/Proviso components according to the specified structure.

The following sections describe how to use the Topology Editor. The topics are as follows:

• Topology Editor Views on page 65

• The topology.xml File on page 71

• Topology Editor Tools on page 71

• Topology Editor Menus on page 74

For information about installing the Topology Editor, see Installing the Topology Editor on page 85. For information about starting the Topology Editor, see Starting the Topology Editor on page 86.



Topology Editor Views

The Topology Editor provides a set of views to describe the deployed topology and that enable you to configure the component properties. Figure 4 shows the layout of the Topology Editor, with no topology defined.

Figure 4: Topology Editor Views

There are three main views:

• Logical View — Displays the logical components of the Netcool/Proviso infrastructure (Database, DataView, DataMart, DataChannels, and so on) in the form of a tree. For more information, see Logical View on page 66.

• Physical View — Displays all the hosts that are part of the Netcool/Proviso infrastructure. For more information, see Physical View on page 67.

• Technology Pack View — Lists the technology packs that can be used to configure DataLoaders. To add a technology pack to this view, you must first load it. For more information, see Technology Pack View on page 68.

The Topology Editor provides the following additional views:

• Properties and Advanced Properties views — When you select an object in either the Logical or Physical view, the basic properties of the object are displayed in the Properties view; any advanced properties are listed in the second tab. For more information, see Properties and Advanced Properties Views on page 68.

• Problems View — Lists all the errors generated when the Topology Editor validates the defined topology (such as missing parameters). For more information, see Problems View on page 70.



Logical View

The Logical view of the Topology Editor displays the logical components using a tree structure similar to the following:

The top of the tree is the Netcool/Proviso Topology node, which corresponds to the XML file created by the Topology Editor. Only one topology can be handled during a Topology Editor session. This tree is created automatically when you create a new topology (see Creating a New Topology on page 87).



Physical View

The Physical view displays a list of defined hosts; under each host, the view shows all the Netcool/Proviso components installed on that host. The following figure shows the Physical View with a single host.

When you add a new host, you must specify basic information about the host, such as the operating system, version, login account, and password. The host also contains parameters related to the Oracle client installed on it.

The Status for each component is set to one of the following values:

• Configured — The component has been installed, but has not been started.

If you remove a Configured component, that component is automatically removed from the Topology Editor and is not saved in the topology file.

• Installed — The component has been started. You cannot remove a component from a deployed topology until it has been started.

If you remove an Installed component, the component’s status changes to “To Be Removed”. Once you run the topology file through the deployer in uninstallation mode, the component is physically uninstalled and removed from the topology.

• To Be Removed — The component will be removed from the topology when you run the deployer in uninstallation mode.

For more information about removing components, see Chapter 9, Uninstalling Components.



Technology Pack View

The Technology Pack view, shown in the following figure, lists the technology packs for which you have loaded the corresponding XSD metadata files.

Once a DataLoader has been configured for an technology pack, the technology pack is shown in the Technology Pack view. Expand the technology pack to see the collectors used by that technology pack.

For information about loading the metadata files, see Chapter 6, Installing Technology Packs.

Properties and Advanced Properties Views

When you select a component in the Logical view, or select a host in the Physical view, the Properties view displays a table of basic parameters for that object, as shown in the following figure. If the selected component has additional properties, they are listed in the Advanced Properties view. If there are no additional properties, the Advanced Properties table is empty.



For each property, the table lists the name, description, current value, default value, and whether the property is inherited from another component. In addition, the table displays an icon that describes the status of the property. There are three different icons:

• Green check mark — The property value is valid.

• Yellow exclamation point — This value is inherited from upstream components (for example, from the host, from the DataChannel if the property is on a collector, or from the Global DataChannel configuration). In addition, the Is Inherited column includes a check mark for these properties.

Note that if you accept the default value, the value will change when you change the parameter value from which this property is inherited.

• Red X — The property value is missing or is incorrect. Any red Xs must be resolved before you can install the product. Note that when any property values are in error, the property includes a red X icon and the problem is listed in the Problems view.

Changing Column Widths

To see the complete property names and their descriptions, you must resize the table columns in the property views.

To change the width of a column in the properties table:

1. Place the cursor on the column separator that you want to move. The cursor changes to a dual-headed arrow.

2. Drag the column separator to the new location, then release the mouse button.

Changing a Property Value

If you change the value of a property, the Topology Editor verifies that the new value complies with any restrictions for that property and marks the value with the appropriate icon (for example, valid or error). You must resolve any properties that are marked with red X icons.

To change a property value:

1. In the Properties view, click the table cell in the Value column that you want to change. A text box is displayed. For example:

2. Type the new value, then press Enter.

The Topology Editor verifies the new value. If it complies with all present restrictions, the red X icon is changed to a green check mark, and the error is removed from the Problems view.

Note the following restrictions:

• Once you have installed Netcool/Proviso, not all the components allow you to modify the property values. For those that do allow you to change the values, you must redeploy the topology to propagate the change. For more information, see Chapter 7, Modifying the Current Deployment.

• Although the Topology Editor allows you to change the database account prefix (DB_USER_ROOT), the change is not propagated to all the related properties. Therefore, you should not change this value.



Restoring the Default Values

If you change the value of a property and want to roll back to its default value, highlight the property and click the Restore Default icon .

To roll back all the component properties to their default values, click the Restore All Default icon .

Problems View

The Problems view warns you about:

• Missing values for required properties

• Values that do not pass the validation test

For example:

In addition, all the components that have errors are marked with a red X icon in the Logical view. See Changing a Property Value on page 69 for information about resolving these errors.

The Problems view contains two additional tabs:

• Events — Lists the code, its description, and the time an event occurred

• Help — Displays information about the selected property



The topology.xml File

The topology describes the Netcool/Proviso infrastructure that you want to create.

Using the Topology Editor, you create an XML file that describes the topology to be deployed. By default, this file is named topology.xml, but you can rename it. Once the topology is ready to deploy (you have specified all the components and configurations, and resolved any errors), you pass the topology file to the deployer. When the installation is complete, the deployer stores the topology file in the Netcool/Proviso database.

The topology file has three main sections that map the information from the three main views of the Topology Editor:

• Logical view (see page 66)

• Physical view (see page 67)

• Technology Pack view (see page 68)

For detailed instructions about creating the topology.xml file, see Creating a New Topology on page 87.

Topology Editor Tools

Because the Topology Editor contains several different views, display “real estate” might be at a premium. The editor enables you to easily close, enlarge, and restore the views, and provides tools to help accomplish these tasks.

Window Tools

Every view in the Topology Editor contains the following tools to enable you to manipulate the window:

Table 5: Tools for Property Values

Tool Description

Displays the editor tools for the current view in menu format

Minimizes the view

Maximizes the view so it fills the entire display area

White X in the tab Closes the view



Restores all the views in this group

Properties view

Restores the Logical view

Logical view

Advanced Properties view

Minimizing Views

If you minimize a view, its corresponding icon is displayed in the right margin, along with an icon to restore the view to its previous state. For example:

To restore a view, click the Restore tool for that group. If there are multiple views in the group (for example, the Properties and Advanced Properties views), you can restore an individual view by clicking the corresponding view’s icon.

Maximizing Views

Click the Maximize icon to display the view in the entire display area. If you maximize a view, all the other views are automatically minimized and their icons are displayed in the right margin. Note that the maximized view includes a new Restore icon in its window banner to restore the previous display settings.

Restoring the Original View

To restore the original layout of the Topology Editor views:

1. Select Window > Reset Perspective.

2. The Topology Editor asks for confirmation to restore the default views. Click OK.

The display is refreshed to show the default view of the Topology Editor, as shown in Figure 4 on page 65.

Note: If you completely close a view, this is the only way to redisplay the closed view.



Tools for the Main Editor Views

Table 6 lists the available tools for the main Topology Editor views — the Logical, Physical, and Technology Pack views.

Properties and Advanced Properties Views

Table 7 lists the editor tools that enable you to manipulate property values.

Table 6: Main View Tools

Tool Description

Home returns to the original tree view.By default, the Logical view displays a tree of components and subcomponents. If you use the Go Into tool to view only a certain component and its subcomponents, click Home to return to the original view.

Returns to the previous display.

Go Into displays the subcomponents for the current component. For example, if you highlight DataChannels in the Logical view and click Go Into, only the DataChannel subcomponents are displayed in the view. Click Home to return to the original view.

Displays the editor tools for the current view in menu format.

Table 7: Tools for Property Values

Tool Description

Adds a user-defined property

Removes the selected user-defined property

Restores the default value of the current property

Restores the default values for all the properties for the current component

Displays the editor tools for the current view in menu format



Topology Editor Menus

The Topology Editor provides the following menus:

• Topology Menu

• Run Menu

• Window Menu

• Help Menu

Topology Menu

The Topology menu enables you to create, modify, and save the topology you create using the editor. The options are as follows:

• Create new topology — Creates a new topology, which describes the Netcool/Proviso infrastructure. For detailed instructions, see Creating a New Topology on page 87.

• Open existing topology — Opens an existing topology so you can make changes to it. See Opening an Existing Topology File on page 97 and Opening a Deployed Topology on page 116 for more information.

Note: After your initial deployment, always load the topology file from the database to make any additional changes (such as adding or removing a component), because it reflects the current status of your environment. Once you have made your changes, you must deploy the updated topology so that it is propagated to the database. To make any subsequent changes following this deployment, you must load the topology file from the database again.

• Save topology — Saves the current topology under the default name, topology.xml. See The topology.xml File on page 71 for more information about this file.

• Save topology as — Saves the current topology with the name you specify.

• Exit — Closes the Topology Editor. Alternatively, click the X in the upper, right-hand corner.

Run Menu

The Run menu runs the primary deployer in installation or uninstallation mode. The options are as follows:

• Run Deployer for Installation — Runs the deployer in installation mode to install the Netcool/Proviso components according to the specified topology. See The Deployer on page 76 for general information about the wizard; for detailed information about the actual installation, see Starting the Deployer on page 98.

• Run Deployer for Uninstallation — Runs the deployer in uninstallation mode to remove the Netcool/Proviso components. For more information, see Uninstalling Entire Netcool/Proviso System on page 150.

Note: When you use the Run menu options (install or uninstall), the deployer uses the last saved topology file, not the current one. Be sure to save the topology file before using a Run command.

Window Menu

The Window menu controls the overall display of the Topology Editor window. The options are as follows:

• Reset Perspective — Displays the default view of the Topology Editor. Use this option to redisplay a view that you completely closed.

• Preferences — Lists the logging preferences. By default, the log level is set to FINE and the messages are written to the file trace.log.

See Trace Log File on page 260 for instructions on renaming the log file and changing the log level.



Help Menu

The Help menu offers a single option, About IBM Tivoli Netcool Proviso - Topology Editor, which enables you to access the following information about the Topology Editor:

• Plug-in Details — Lists information about all the plug-ins used by the editor, including the name, provider, ID, and whether the plug-in is signed. Two buttons enable you to view more detailed information about a plug-in:

• Legal info — Opens a Web browser that displays the legal information for the plug-in.

• Show Signing Info — Expands the Plug-ins dialog box to display the signing certificate for the plug-in. Click Hide Signing Info to hide this information.

Click OK to close the Plug-ins dialog box.

• Configuration Details — Displays the configuration details for the editor. Click Copy to Clipboard to copy this information to a text file so you can edit it. Click Close to close this dialog box.

Click OK to close the window.



The Deployer

When you are satisfied with the topology and have resolved any problems, save it to an XML file (see Saving the Topology on page 97). You are now ready to install Netcool/Proviso using the Deployer.

The Deployer displays a series of pages to guide you through the Netcool/Proviso installation. The installation steps are displayed in a table, which enables you to run each step individually or to run all the steps at once. For more information, see Installation Steps on page 78.

This section provides an overview of the Deployer. The topics are as follows:

• Node Selection on page 77

• Installation Steps on page 78

• Step Properties on page 79

• Step Status Values on page 80

• Resuming a Partially Successful First-Time Installation on page 104

In addition, you can run the Deployer in silent mode. See Appendix J, Using Silent Mode for detailed information.



Node Selection

The node selection window shows the target systems and how the files will be transferred. The table has one row for each machine where at least one Netcool/Proviso component will be installed, as shown in the following figure:

The fields are as follows:

• Enable — Determines whether the Deployer should perform actions on the target machine.

• Check prerequisites — Runs scripts to verify that the prerequisite software has been installed.

• Remote Command Execution — Specifies whether you can run commands on the remote machine, and whether you can use RSH, OpenSSH, or both RSH and OpenSSH.

Remote installation is not supported for the DataMart and database components. If you are installing the components on multiple servers, the remote host for these components will not be selectable: you must start the Deployer locally on that host to install those components. For more information, see Remote Installation on page 187 and Primary Versus Secondary Deployers on page 102.

• File Transfer — Specifies whether you can transfer files to the remote machine, and which transfer method to use (FTP or SCP/SFTP).

Note that the settings for the Remote Command Execution and File Transfer fields apply to all the selected (checked) nodes. However, different machines could have different access levels.

For example, suppose that you have two machines, Host A and Host B. Host A can do remote command execution, but cannot transfer files to other machines. Host B can do both remote command execution and file transfers. To deploy Netcool/Proviso on these two machines:

1. Disable Host A and enable Host B.

2. Enable the Remote Command Execution and File Transfer. options for Host B.

3. Install the components on Host B.

4. Run the Deployer again, disabling Host B and enabling Host A.

5. Enable Remote Command Execution and disable File Transfer. for Host A.



6. Install the components on Host A.

Installation Steps

When you run the Deployer, it displays a page that lists all the installation steps needed to install the Netcool/Proviso components. Each step is a separate line in the table, and the steps are numbered beginning with 0. Each step includes a status value, which is initially set to Ready. Note that you must run all the steps in sequence.

Each component to be installed might require more than one step to be performed; the last step of the installation sequence is always a step named “Register componentName”. This step registers in the database that the specified component was installed on the given host.

The following figure shows a sample steps page:

To run each installation step separately:

1. Click Run Next to run the first step with status of Ready.

2. The status changes from Ready to Running. If the step is successful, the status changes to Success. If it fails, it changes to Error and you must resolve the problem. For more information about troubleshooting installation errors, see Step Properties on page 79.

3. If that step is successful, continue processing each step in turn.

To run all installation steps at the same time:

1. Verify that Stop on Error is enabled. This option stops the installation if it encounters an error with a step.

Note: If the status for a step is set to Fail by the user, the Stop on error option will not cause the Deployer to stop when that step is reached. The Stop on error option will only have an effect if it is the Deployer that sets a step’s status to Fail.

2. Click Run All. All the installation steps are processed sequentially.



Note that the Stop button is enabled only when you select Run All. Use Stop to stop the Deployer after the current step has completed.

Note: If you are installing DataLoad and DataChannel remotely, the steps Load Channel Configuration and Load Collector Configuration might be duplicated in the list of installation steps. This duplication is both normal and necessary. These steps verify that: – The necessary configuration data is stored in the database. – The configuration stored in the database is consistent with the one loaded at the beginning of the deployment. – The DataLoad and DataChannel components are installed correctly.

When you close the steps page, the deployer stores the current step status in the /tmp/ProvisoConsumer directory. You can retrieve the step status using the following command:

./deployer.bin –Daction=resume

The step status persists until you start the deployer again and generate a new list of steps. For more information, see Resuming a Partially Successful First-Time Installation on page 104.

Important: If you modify a deployed topology such that only the database configuration (CFG component) is changed, do not select the Check Prerequisites option. Otherwise, when you pass the updated topology to the deployer, the Check OS step will fail. One example of a database configuration-only change is adding another UBA to a DataChannel that has already been deployed.

Step Properties

The deployer enables you to view property values and change them on-the-fly. If an installation step fails, you can use the details window to view detailed information about the step to help you resolve the problem, or to change the value of a property.

To view the step’s properties:

1. In the table of steps, right-click the step and select Properties. The deployer displays a window with several tabs, depending on the actual step.

2. Click the Properties tab.

3. Change the values as necessary, then click Apply. The new value is written to the topology file.

4. Click OK to close the details window.



Tabs of the Step Details Window

The step details window is made up of several tabs, which vary according to the actual installation step. The tabs include the following:

• Status — Displays read-only information about the step, including its description, target node, and current status. Use the Change Status field to change the step’s status from Error to Ready after you have fixed the problem that caused this step to fail.

• Properties — Displays the properties of the current step. The number of properties listed depends on that step.

• Output — Displays status and error messages (if any) that result from running the step. If there is an error, use these messages to help diagnose the problem. For example:

Step Status Values

There are four possible status values for an installation step:

• Ready — The step is ready to run. This is the initial value of a step.

• Success — The step ran and completed successfully.

• Error — The step ran, but failed.

• Held — The step was not run because a step that preceded it failed.

When a step runs, its status changes from Ready, to Running, then to Success or Error. If an installation step fails, correct the problem, then change the step’s status from Error to Ready to run the step again.

To change the status of a step:

1. In the table of steps, right-click the step and select Set Status from the pop-up menu.

2. Select the appropriate status from the menu.

or

1. In the table of steps, right-click the step and select Properties from the pop-up menu.

2. Click the Status tab.

3. Set the Change Status field to the appropriate value.


Chapter 4: Installing Netcool/Proviso in a Distributed Environment

This chapter describes how to install Netcool/Proviso for the first time in a fresh, distributed environment. For information about installing the Netcool/Proviso components using a minimal deployment, see Chapter 5, Installing Netcool/Proviso as a Minimal Deployment. For an overview of the graphical user interfaces (GUIs) used to install Netcool/Proviso, see The Graphical Installation Interface on page 59.

The topics are as follows:

Before You Begin

Before installing Netcool/Proviso, you must have installed the prerequisite software. For detailed information, see Chapter 2, Installing and Configuring the Prerequisite Software.

In addition, you must have decided how you want to configure your system. Refer to the following sections:

• Configuring Your Deployment on page 5

• Appendix D, Deployment Considerations on page 185

The general steps used to install Netcool/Proviso are as follows:

1. Start the launchpad.

Topic Page

Before You Begin 81

Starting the Launchpad 83

Installing the Topology Editor 85

Starting the Topology Editor 86

Creating a New Topology 87

Adding and Configuring the Netcool/Proviso Components 87

Saving the Topology 97

Starting the Deployer 98

Deploying the Topology 99

Next Steps 101

Primary Versus Secondary Deployers 102

Resuming a Partially Successful First-Time Installation 104



2. Install the Topology Editor.

3. Start the Topology Editor.

4. Create the topology.

5. Add the Netcool/Proviso components.

6. Save the topology to an XML file.

7. Start the deployer.

8. Install Netcool/Proviso using the deployer.

The following sections describe each of these steps in detail.

Note: Before you start the installation, verify that all the database tests have been performed. Otherwise, the installation might fail. See Installing and Configuring the Prerequisite Software on page 7 for information about tnsping.

Disk Usage Server

Netcool/Proviso 5.2 has a new DataChannel component, the Disk Usage Server. This component is responsible for maintaining the properties necessary for quota management (flow control) of DataChannel. DataChannel components can only be added to hosts that include a Disk Usage Server.

Multiple Disk Usage Servers can be configured per host; therefore, allowing multiple DataChannel directories to exist on a single host. There are two major reasons why a user may want to configure multiple Disk Usage Servers:

• Disk space is running low: Disk space may be impacted by the addition of a new DataChannel component. In which case, the user may want to add a new file system managed by a new Disk Usage Server.

• Separate disk quota management: The user may want to separately manage the quotas assigned to discrete DataChannel components. For more information, see Disk Quota Management on page 83.

The user can assign the management of a new file system to a Disk Usage Server by editing the local_root_directory property of that Disk Usage Server using the Topology Editor. The user can then add DataChannel components to the host, and can assign the component to a Disk Usage Server, either in the creation wizard or by editing the DUS_NUMBER property inside the component.

Adding a Disk Usage Server

Should more space be required on a system, an additional Disk Usage Server can be added. Each Disk Usage Server gets its own root directory, so it makes it easy to add storage at this point, and put new components on the Disk Usage Server.

Moving an existing component to a different Disk Usage Server is achieved by:

1. Shut down the component or components you would like to move.

2. Move the directories for those components to the DataChannel root directory that will be managed by the new Disk Usage Server.

3. Use the Topology Editor to Create the new Disk Usage Server.

4. Update the topology to change the Disk Usage Server used by the component or components.

5. Run the Deployer to update DataChannel configuration.

6. Restart the components. If you have added a component or changed the host a component lives on, you will need to restart the CMGR before restarting the new/changed components.



Note: For information on how a Disk Usage Server is added and set for a component using the Topology Editor, see Add the Hosts.

Disk Quota Management

The addition of a Disk Usage Server endeavors to make the process of assigning space to a component much easier than it has been previously. No longer is a user required to calculate the requirements of each component and assign that space individually, but components now work together to more effectively utilize the space they have under the Disk Usage Server. Also, the user is relieved of trying to figure out which component needs extra space and then changing the quota for that component. Now, the user can just change the quota of the DUS and all components on that Disk Usage Server will get the update and share the space on an as needed basis.

Good judgement of space requirements is still needed. However, the estimating of space requirements is being made at a higher level; and should an estimate be incorrect, only one number needs to be changed instead of potentially updating the quota for each component separately.

Flow Control

Optimized flow control further eliminates problems with component level quotas. Each component holds on to only a five hours of input and output, and once it has reached this limit, it stops processing until the downstream component picks up some of the data. This avoids the cascading scenario where one component stops processing and the components feeding it begin to stockpile files, which results in the quota being filled and causes all components to shut down because they have run out of file space.

Starting the Launchpad

For an overview of the launchpad interface, see The Launchpad on page 62.

To start the launchpad:

1. Log in as root.

2. Set and export the DISPLAY variable (see Setting Up a Remote X Window Display on page 9).

3. Set and export the BROWSER variable to point to your Web browser. For example:

On Solaris systems:# BROWSER=/opt/mozilla/mozilla

# export BROWSER

On AIX systems:# BROWSER=/usr/mozilla/firefox/firefox

# export BROWSER

On Linux systems:# BROWSER=/usr/bin/firefox

# export BROWSER

Note: The BROWSER command cannot include any spaces around the equal sign.

4. Change directory to the directory where the launchpad resides.



On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS

On AIX systems:# cd <DIST_DIR>/proviso/AIX

On Linux systems:# cd <DIST_DIR>/proviso/RHEL

<DIST_DIR> is the directory on the hard drive where you copied the contents of the Netcool/Proviso distribution in Downloading the Netcool/Proviso Distribution to Disk on page 21.

5. Enter the following command to start the launchpad:

# ./launchpad.sh



Installing the Topology Editor

Only one instance of the Topology Editor can exist in the Netcool/Proviso environment. Install the Topology Editor on the same system that will host database server.

You can install the Topology Editor from the launchpad or from the command line.

To install the Topology Editor:

1. From the launchpad:

1-a. On the launchpad, click the Install Topology Editor option in the list of tasks.

1-b. On the Install Topology Editor page, click the Install Topology Editor link.

From the command line:


1-b. Change directory to the directory that contains the Topology Editor installation script:

On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/topologyEditor/Disk1/InstData/VM

On AIX systems:# cd <DIST_DIR>/proviso/AIX/Install/topologyEditor/Disk1/InstData/VM

On Linux systems:# cd <DIST_DIR>/proviso/RHEL/Install/topologyEditor/Disk1/InstData/VM


1-c. Enter the following command:

# ./installer.bin

2. The installation wizard opens in a separate window, displaying a welcome page. Click Next.

3. Review and accept the license agreement, then click Next.

4. Confirm the wizard is pointing to the correct installation directory (the default is /opt/IBM/proviso). If you have previously installed the Topology Editor on this system, the installer does not prompt you for an installation directory and instead uses the directory where you last installed the application. Click Next to continue.

5. Confirm the wizard is pointing to the correct base installation directory of the Oracle JDBC driver (/opt/oracle/product/version/jdbc/lib), or click Choose to navigate to another directory.

The Topology Editor uses this location for all components in the topology. You might need to manually change the directory associated with DataView or other components to accommodate requirements for different versions of the client software patch. For more information, see Chapter 2, Installing and Configuring the Prerequisite Software on page 7.

Click Next to continue.

6. Review the installation information, then click Install.

7. When the installation is complete, click Done to close the wizard.



The installation wizard installs the Topology Editor and an instance of the deployer in the following directories:

The combination of the Topology Editor and the deployer is referred to as the primary deployer. For more information, see Primary Versus Secondary Deployers on page 102.

Note: To uninstall the Topology Editor, follow the instructions in Uninstalling the Topology Editor on page 152. Do not simply delete the /opt/IBM directory! Doing so will cause problems when you try to reinstall the Topology Editor. If the /opt/IBM directory is accidentally deleted, perform the following steps: 1. Change to the /var directory. 2. Rename the hidden file .com.zerog.registry.xml (for example, rename it to .com.zerog.registry.xml.backup). 3. Reinstall the Topology Editor. 4. Rename the backup file to the original name (.com.zerog.registry.xml).

Starting the Topology Editor

After you have installed the Topology Editor, you can invoke it from either the launchpad or from the command line.

To start the Topology Editor from the launchpad:

1. If the Install Topology Editor page is not already open, click the Install Topology Editor option in the list of tasks to open it.

2. On the Install Topology Editor page, click the Start Topology Editor link.

To start the Topology Editor from the command line:

1. Log in as root.

2. Change directory to the directory in which you installed the Topology Editor. For example:

# cd /opt/IBM/proviso/topologyEditor


# ./topologyEditor

Note: If your DISPLAY environment variable is not set, the Topology Editor will fail with a Java assertion message (core dump).

Interface Directory

Topology Editor install_dir/topologyEditor

For example:

/opt/IBM/proviso/topologyEditor

Deployer install_dir/deployer

For example:

/opt/IBM/proviso/deployer



Creating a New Topology

To create a new topology:

1. In the Topology Editor, select Topology > Create new topology. The New Topology window is displayed.

2. Enter the number of resources to be monitored by Netcool/Proviso. The default value is 10000.

3. Click Finish.

The Topology Editor creates the following entities:

• In the Logical view, five items are listed: Netcool/Proviso Topology, Cross Collector CMEs, DataChannels, DataMarts and Tivoli Integrated Portals.

• In the Physical view, there is a new Hosts folder.

The size of your deployment affects the database sizing. .

Adding and Configuring the Netcool/Proviso Components

Next, you must add and configure the individual Netcool/Proviso components:

• Step 1,Add the Hosts

• Step 2,Add a Database Configurations Component

• Step 3,Add a DataMart

• Step 4,Add a Discovery Server

• Step 5,Add a Tivoli Integrated Portal

• Step 6,Add a DataView

• Step 7,Add the DataChannel Administrative Components

• Step 8,Add a DataChannel

• Step 9,Add a Collector

Step 1: Add the Hosts

The first step is to specify all the servers that will host Netcool/Proviso components. Specify the server that hosts the Oracle server as the first host, then add other hosts as needed.

Each host that you define has an associated property named PV user that specifies the default operating system user for all Netcool/Proviso components installed on the system. You can override this setting in the Advanced Properties tab when you set the deployment properties for individual components (for example, DataMart and DataView). This allows you to install and run different components on the same system as different users. DataChannel components always use the default user associated with the host.

The user account used to transfer files using FTP or SCP/SFTP during installation is always the PV user defined at the host level, rather than component level.



To add a host to the topology:

1. In the Physical view, right-click the Hosts folder and select Add Host from the menu. The Add Host window opens.

2. Specify the details for the host machine. The first host you specify must be the machine on which the database is located.


— Host name — Enter the name of the host (for example, delphi).

— Operating system — Specifies the operating system (for example, SOLARIS). This field is filled in for you.

Note: The Netcool/Proviso deployer does not support hybrid configurations. For example, if the database host is a Solaris system, the entire topology must be deployed on the Solaris platform. The Topology Editor will enforce this rule, by forcing all the other components to be targeted to the same operating system as the database component. The only exception to this is DataLoad; DataLoad can be placed on a system running a different operating system to that of the database host.

— Oracle home — Specifies the default ORACLE_HOME directory for all Netcool/Proviso components installed on the system (by default, /opt/oracle/product/10.2.0).

You specified this directory when you installed Oracle server or client components on the system. If you installed Oracle components in more than one directory (for example, if you installed two instances of the client software to accommodate DataView and another Netcool/Proviso component on the same system), you must override this value when you set deployment properties for the DataView component. See Add a DataView on page 92 for more information.

— PV user — Specifies the default Netcool/Proviso Unix user (for example, pvuser) for all Netcool/Proviso components installed on the system.

— PV user password — Specifies the password for the default Netcool/Proviso user (for example, PV).

— Create Disk Usage Server for this Host? — Selecting this check box creates a DataChannel subcomponent to handle disk quota and flow control.

If you have not chosen to create a Disk Usage Server, Click Finish to create the host. The Topology Editor adds the host under the Hosts folder in the Physical view. If you have chosen to create a Disk Usage Server, click Next and the Add Host window will allow you to add details for your Disk Usage Server.

3. Specify the details for the Disk Usage Server.


— Local Root Directory — The local DataChannel root directory. This property allows you to differentiate between a local directory and a remote directory mounted to allow for FTP access.

— Remote Root Directory — Remote directory mounted for FTP access. This property allows you to differentiate between a local directory and a remote directory mounted to allow for FTP access.

— FC FSLL — This is the Flow Control Free Space Low Limit property. When this set limit is reached the Disk Usage Server will contact all components who reside in this root directory and tell them to free up all space possible.

— FC QUOTA — This is the Flow Control Quota property. This property allows you to set the amount of disk space in bytes available to Netcool/Proviso components on this file system.

— Remote User — User account used when attempting to access this Disk Usage Server remotely.

— Remote User Password — User account password used when attempting to access this Disk Usage Server remotely.

— Secure file transfer to be used — Boolean indicator identifying if ssh should be used when attempting to access this directory remotely.



— Port Number — Port number to use for remote access (sftp) in case it is a non default port.

Click Finish to create the host. The Topology Editor adds the host under the Hosts folder in the Physical view.

4. In the Physical view, select the new host to view its properties in the Properties view. You must enter values for any properties that have red Xs (for missing or incorrect values). See the Netcool/Proviso Properties Reference for the complete list of properties for this component. For information about changing the value of a property, see Changing a Property Value on page 69.

5. Repeat for all the hosts needed for your deployment (for example, athens, corinth, and sparta).

Note: The DataChannel properties will be filled in automatically at a later stage.

Step 2: Add a Database Configurations Component

The Database Configurations component hosts all the database-specific parameters. You define the parameters once, and their values are propagated as needed to the underlying installation scripts.

To add a Database Configurations component:

1. In the Logical view, right-click the Netcool/Proviso Topology component and select Add Database Configurations from the menu. The host selection window opens.

2. You must add the Database Configuration component to the same server that hosts the Oracle server (for example, delphi). Select the appropriate host using the drop-down list.

Note: The operating system of the host where you configure the Database Configurations component determines the main platform for the entire Netcool/Proviso deployment. This means that you should install all the other main components (DataView, DataMart, DataChannel and Tivoli Integrated Portal) on machines with the same operating system. The Topology Editor enforces this constraint by listing only those hosts with the same operating system used to host the database.

3. Click Finish to create the component, or click Next to configure the mount points for the database.

To configure the mount points:

3-a. In the mount points window, verify the information that the editor has filled in for you:

* Mount Point Directory Name (for example, /raid_2/oradata)

Note: The mount point directories can be named using any string as required by your organizations naming standards.

* Used for Metadata Tablespaces? (A check mark indicates True.)

* Used for Temporary Tablespaces? (A check mark indicates True.)

* Used for Metric Tablespaces? (A check mark indicates True.)

* Used for System Tablespaces and Redo? (A check mark indicates True.)

3-b. To add a new mount point, click Add Mount Point. A new, blank row is added to the window. Fill in the fields as appropriate for the new mount point.

3-c. Click Back to return to the original page.

3-d. Click Finish to create the component.

The Topology Editor adds the new Database Configurations component to the Logical view.



4. Highlight the Database Configurations component to display its properties. Review the property values to make sure they are valid. For the complete list of properties for this component, see the Netcool/Proviso Properties Reference.

The Database Configurations component has the following subelements:

• Channel tablespace configurations

• Database Channels

• Database Clients configurations

• Tablespace configurations

• Temporary tablespace configurations

Note: Before you actually install Netcool/Proviso, verify that both the raid_2/oradata and raid_3/oradata directory structures have been created, and that the oradata subdirectories are owned by oracle:dba.

Step 3: Add a DataMart

Netcool/Proviso DataMart is normally installed on the same server on which you installed Oracle server and the Netcool/Proviso database configuration. However, there is no requirement that forces DataMart to reside on the database server.

Note the following:

• DataMart components cannot be installed remotely. To install DataMart on a server that does not host the primary deployer, you must run a secondary deployer on that server. For more information, see Primary Versus Secondary Deployers on page 102.

• If you are installing DataMart on an AIX system or any remote AIX, Linux or Solaris system, you must add the IBM JRE to the PATH environment variable for the Netcool/Proviso Unix user, pvuser.

• You must ensure you are using the IBM JRE and not the RHEL JRE. The IBM JRE is supplied with the Topology Editor or with Tivoli Integrated Portal. To ensure you are using the right JRE you can either:

— Set the JRE path to conform to that used by the Topology Editor, do this using the following commands (using the default location for the primary deployer):

PATH=/opt/IBM/proviso/topologyEditor/jre/bin:$PATH

export $PATH

— For a remote server, that is one that does not host the primary deployer, you must download and install the required JRE, and set the correct JRE path. See the Netcool/Proviso Configuration Recommendations document for JRE download details.

To add a DataMart component:

1. In the Logical view, right-click the DataMarts folder and select Add DataMart from the menu. The host selection host window is displayed.

2. Using the drop-down list of available hosts, select the machine on which DataMart should be installed (for example, delphi).

3. Click Finish.

The Topology Editor adds the new DataMart x component (for example, DataMart 1) under the DataMarts folder in the Logical view.

4. Highlight the DataMart x component to display its properties. Review the property values to make sure they are valid. You can specify an alternate installation user for the DataMart component by changing the values



of the USER_LOGIN and USER_PASSWORD properties in the Advanced Properties tab. For the complete list of properties for this component, see the Netcool/Proviso Properties Reference.

Event Notification Scripts

When you install the DataMart component, two event notification scripts are installed. The scripts are called as needed by tablespace size checking routines in Oracle and in Netcool/Proviso, if either routine detects low disk space conditions on a disk partition hosting a portion of the Netcool/Proviso database. Both scripts by default send their notifications by e-mail to a local login name.

The two files and their installation locations are as follows:

• The script installed as $ORACLE_BASE/admin/$ORACLE_SID/bin/notifyDBSpace notifies the login name oracle by e-mail of impending database space problems. This script is called as needed by an Oracle routine that periodically checks for available disk space.

• The script installed as /opt/datamart/bin/notifyDBSpace notifies the login name pvuser of the same condition. This script is called as needed by the Hourly Loader component of Netcool/Proviso DataChannel. The loader checks for available disk space before attempting its hourly upload of data to the database.

Either file can be customized to send its warnings to a different e-mail address on the local machine, to an SMTP server for transmission to a remote machine, or to send the notices to the local network’s SNMP fault management system (that is, to an SNMP trap manager). You can modify either script to send notifications to an SNMP trap, instead of, or in addition to its default e-mail notification.

Step 4: Add a Discovery Server

The Discovery Server is the Netcool/Proviso component responsible for SNMP discovery. You can add a discovery server for each DataMart defined in the topology.

To add a Discovery Server:

• In the Logical view, right-click the DataMart x folder and select Add Discovery server from the menu.

The Topology Editor displays the new Discovery Server under the DataMart n folder in the Logical view.

Adding Multiple Discovery Servers

If you want to run multiple Discovery Servers on multiple hosts in your environment, you must perform additional steps at deployment to make sure that each host system contains identical inventory files and identical copies of the inventory hook script. IBM recommends that you only use identically-configured instances of the Discovery Server.

The inventory files used by the Discovery Server are configuration files named inventory_elements.txt and inventory_subelements.txt. These files are located in the $PVMHOME/conf directory of the system where you install the DataMart component. Some technology packs provide custom sub-elements inventory files with names different from inventory_subelements.txt that are also used by the Discovery Server.

To add multiple Discovery Servers, do the following:

• Install the primary instance of DataMart and the Discovery Server on one target host system.

• Install and configure any required technology packs on the primary host. You modify the contents of the inventory files during this step.

• Install secondary instances of DataMart and the Discovery Server on corresponding target host systems.



• Replicate the inventory files from the system where the primary instance of DataMart is running to the $PVMHOME/conf directory on the secondary hosts. You must also replicate the InventoryHook.sh script that is located in the $PVMHOME/bin directory and any other files that this script requires.

Step 5: Add a Tivoli Integrated Portal

The Tivoli Integrated Portal (TIP) provides an integrated console for users to log on and view information contained on the DataView server.

To add a Tivoli Integrated Portal:

1. In the Logical view, right-click on the Tivoli Integrated Portals folder and select Add TIP from the menu. The Configure TIP Wizard is displayed.

2. The Topology Editor gives you the choice of adding an already existing Tivoli Integrated Portal to the topology or to create a new Tivoli Integrated Portal. To create a new TIP, select the Create a new TIP radio button. To import an already existing Tivoli Integrated Portal into the topology, select the Import existing TIPs from host radio button.

3. Using the drop-down list of available hosts, select the machine on which Tivoli Integrated Portal should be installed (for example, delphi).

Note: The hostname of the host selected for the TCR install must not contain underscores. Underscores in the hostname will cause the installation of TCR to fail.

4. (Optional) Select the LDAP Configuration check box and configure LDAP options.

Note: For details on how you can configure LDAP as the default authentication/authorization mechanism for Netcool/Proviso, see LDAP Integration on page 225.

5. Click Finish.

The Topology Editor adds the new Tivoli Integrated Portal component to the Logical view.

6. Highlight the Tivoli Integrated Portal component to display its properties.

7. Review the other property values to make sure they are valid. For the complete list of properties for this component, see the Netcool/Proviso Properties Reference.

Step 6: Add a DataView

Note: To display DataView real-time charts, you must have the Java runtime environment (JRE) installed on the browser where the charts are to be displayed. You can download the JRE from the Sun download page at http://www.sun.com.

To add a DataView component:

In the Logical view, right-click on a Tivoli Integrated Portal and select Add DataView from the menu. The DataView is automatically added inheriting its properties from the Tivoli Integrated Portal instance.



Step 7: Add the DataChannel Administrative Components

To add DataChannel Administrative components:

1. In the Logical view, right-click the DataChannels folder and select Add Administrative Components from the menu. The host selection window opens.

2. Using the drop-down list of available hosts, select the machine that you want to be the Channel Manager host for your DataChannel configuration (for example, corinth).

3. Click Finish.

The Topology Editor adds a set of new components to the Logical view:

• Channel Manager — Enables you to start and stop individual DataChannels and monitor the state of various DataChannel programs. There is one Channel Manager for the entire DataChannel configuration. The Channel Manager components are installed on the first host you specify

• Corba Naming Server — Provides near real-time data to DataView.

• High Availability Managers — This is mainly used for large installations that want to use redundant SNMP collection paths. The HAM constantly monitors the availability of one or more SNMP collection hosts, and switches collection to a backup host (called a spare) if a primary host becomes unavailable.

• Log Server — Used to store user, debug, and error information.

• Plan Builder — Creates the metric data routing and processing plan for the other components in the DataChannel.

• Custom DataChannel properties — These are the custom property values that apply to all DataChannel components.

• Global DataChannel properties — These are the global property values that apply to all DataChannel components.

Step 8: Add a DataChannel

A DataChannel is a software module that receives and processes network statistical information from both SNMP and non-SNMP (BULK) sources. This statistical information is then loaded into a database where it can be queried by SQL applications and captured as raw data or displayed on a portal in a variety of reports.

Typically, collectors are associated with technology packs, a suite of Netcool/Proviso programs specific to a particular network device or technology. A technology pack tells the collector what kind of data to collect on target devices and how to process that data. See Chapter 6, Introduction to Installing Netcool/Proviso Technology Packs for detailed information about technology packs.

To add a DataChannel:

1. In the Logical view, right-click the DataChannels folder and select Add DataChannel from the menu. The Configure the DataChannel window is displayed.

2. Using the drop-down list of available hosts, select the machine that will host the DataChannel (for example, corinth).

3. Accept the default channel number (for example, 1).

4. Click Finish.

The Topology Editor adds the new DataChannel (for example, DataChannel 1) to the Logical view.

5. Highlight the DataChannel to display its properties. Note that the DataChannel always installs and runs as the default user for the host (the Netcool/Proviso Unix username, pvuser). Review the other property values



to make sure they are valid. For the complete list of properties for this component, see the Netcool/Proviso Properties Reference.

The DataChannel has the following subelements:

• Daily Loader x — Processes 24 hours of raw data every day, merges it together, then loads it into the database. The loader process provides statistics on metric channel tables and metric tablespaces.

• Hourly Loader x — Reads files output by the Complex Metric Engine (CME) and loads the data into the database every hour. The loader process provides statistics on metric channel tables and metric tablespaces.

The Topology Editor includes the channel number in the element names. For example, DataChannel 1 would have Daily Loader 1 and File Transfer Engine 1.

Note: When you add DataChannel x, the Problems view shows that the Input_Components property for the Hourly Loader is blank. This missing value will automatically be filled in when you add a DataLoad collector (as described in the next section) and the error will be resolved.

Separating the data and executable directories

If you wish to separate the data and executable directories for your DataChannel, do the following:

1. Create two directories on the DataChannel host, for example, DATA_DIR to hold the data and EXE_DIR to hold the executable.

2. Change the LOCAL_ROOT_DIRECTORY value on that host's Disk Usage Server to the data root folder DATA_DIR. In the Host advanced properties you will see the DATA_DIR value propagated to all DC folder values for the host.

3. Change DC_ROOT_EXE_DIRECTORY to the executable directory EXE_DIR. This change will propagate to the DC conf directory, the DataChannel Bin Directory and the Datachannel executable file name.

Note: For advanced information about DataChannels, see Appendix E, DataChannels on page 193.

Step 9: Add a Collector

Collectors collect and process raw statistical data about network devices obtained from various network resources. The collectors send the received data through a DataChannel for loading into the Netcool/Proviso database. Note that collectors do not need to be on the same machine as the Oracle server and DataMart.

Collector Types

There are two basic types of collectors:

• SNMP collector — Collects data using SNMP polling directly to network services. Specify this collector type if you plan to install a Netcool/Proviso SNMP technology pack. These technology packs operate in networking environments where the associated devices on which they operate use an SNMP protocol.

• Bulk DataLoad collector — Imports data from files. The files can have multiple origins, including log files generated by network devices, files generated by SNMP collectors on remote networks, or files generated by a non-Netcool/Proviso network management database.

There are two types of bulk collectors:



— UBA. A Universal Bulk Adapter (UBA) Collector that handles bulk input files generated by non-SNMP devices. Specify this collector type if you plan to install a Netcool/Proviso UBA technology pack, including Alcatel 5620 NM, Alcatel 5620 SAM, and Cisco CWM.

— BCOL. A bulk Collector that retrieves and interprets the flat file output of network devices or network management systems. This collector type is not recommended for Netcool/Proviso UBA technology packs, and is used in custom technology packs.

If you are creating a UBA collector, you must associate it with a specific technology pack. For this reason, IBM recommends that you install the relevant technology pack before creating the UBA collector. Therefore, you would perform the following sequence of steps:

1. Install Netcool/Proviso, without creating the UBA collector.

2. Download and install the technology pack.

3. Open the deployed topology file to load the technology pack and add the UBA collector for it.

For detailed information about UBA technology packs and the installation process, see Chapter 6, Introduction to Installing Netcool/Proviso Technology Packs. Configure the installed pack by following the instructions in the pack-specific user's guide. More specifically, the process of adding a UBA collector is covered in each of the appendices documenting version-specific technology pack installation. Links to the relevant appendices are contained in Chapter 6, Introduction to Installing Netcool/Proviso Technology Packs.



Restrictions


• The maximum collector identification number is 999.

• There is no relationship between the channel number and the collector number (that is, there is no predefined range for collector numbers based on channel number). Therefore, collector 555 could be attached to DataChannel 7.

• Each database channel can have a maximum of 40 subchannels (and therefore, 40 collectors).

Creating an SNMP Collector

To add an SNMP collector:

1. In the Logical view, right-click the DataChannel x folder. The pop-up menu lists the following options:

— Add Collector SNMP — Creates an SNMP collector.

— Add Collector UBA — Creates a UBA collector. See Chapter 6, Introduction to Installing Netcool/Proviso Technology Packs for information about creating this type of collector.

— Add Collector BCOL — Creates a BCOL collector. This collector type is used in custom technology packs. DataMart must be added to the topology before a BCOL collector can be added.

Select Add Collector SNMP. The Configure Collector window opens.

2. Using the drop-down list of available hosts on the Configure Collector window, select the machine that will host the collector (for example, corinth).

3. Accept the default collector number (for example, 1).

4. Click Finish.

The Topology Editor displays the new collector under the DataChannel x folder in the Logical view.

5. Highlight the collector to view its properties. The Topology Editor displays both the SNMP collector core parameters and the SNMP technology pack-specific parameters. The core parameters are configured with all SNMP technology packs. You can specify an alternate installation user for the SNMP collector by changing the values of the pv_user, pv_user_group and pv_user_password properties in the Advanced Properties tab. Review the values for the parameters to make sure they are valid.

For information about the core parameters, see the Netcool/Proviso Properties Reference. For information about the pack-specific parameters, see the Topology Editor Help (described in Problems View on page 70).

The collector has two components:

• Complex Metric Engine x — Perform calculations on the collected data.

• File Transfer Engine (FTE) x — Transfers files from the collector’s output directories and places them in the input directory of the CME.

The FTE writes data to the file /var/adm/wtmpx on each system that hosts a collector. As part of routine maintenance, check the size of this file to prevent it from growing too large.

Note: Your Solaris version can be configured with strict access default settings for secure environments. Strict FTP access settings might interfere with automatic transfers between a DataChannel subchannel and the DataLoad server. Check for FTP lockouts in /etc/ftpd/ftpusers, and check for strict FTP rules in /etc/ftpd/ftpaccess.

Note that the Topology Editor includes the channel and collector numbers in the element names. For example, DataChannel 1 could have Collector SNMP 1.1, with Complex Metric Engine 1.1 and File Transfer Engine 1.1.



Saving the Topology

When you are satisfied with the infrastructure, verify that all the property values are correct and that any problems have been resolved, then save the topology to an XML file.

To save the topology as an XML file:

1. In the Topology Editor, select Topology then either Save Topology As or Save Topology.

Click Browse to navigate to the directory in which to save the file. By default, the topology is saved as topology.xml file in the topologyEditor directory.

2. Accept the default value or choose another name or location, then click OK to close the file browser window.

3. The file name and path is displayed in the original window. Click Finish to save the file and close the window.

You are now ready to deploy the topology file (see Starting the Deployer on page 98).

Note that until you actually deploy the topology file, you can continue making changes to it as needed by following the directions in Opening an Existing Topology File.

See Chapter 7, Modifying the Current Deployment for more information about making changes to a deployed topology file.

Note: Only when you begin the process of deploying a topology is it saved to the database. For more information, see the section Deploying the Topology.

Opening an Existing Topology File

As you create the topology, you can save the file and update it as needed.

To open a topology file that exists but that has not yet been deployed:

1. If it is not already open, open the Topology Editor (see Starting the Topology Editor on page 86).

2. In the Topology Editor, select Topology > Open existing topology. The Open Topology window is displayed.

3. For the topology source, click local then use Browse to navigate to the correct directory and file. Once you have selected the file, click OK. The selected file is displayed in the Open Topology window.

Click Finish.

The topology is displayed in the Topology Editor.

4. Change the topology as needed.



Starting the Deployer

The primary deployer is installed on the same machine as the Topology Editor. You first run the topology file on the primary deployer, and then run secondary installers on the other machines in the distributed environment. See Primary Versus Secondary Deployers on page 102 for more information about the difference between primary and secondary deployers.

Note: Before you start the deployer, verify that all the database tests have been performed. Otherwise, the installation might fail. See Chapter 2, Installing and Configuring the Prerequisite Software for more information.

Primary Deployer

To run the primary deployer from the Topology Editor:

• Click Run > Run Deployer for Installation.

Note: When you use the Run menu options (install or uninstall), the deployer uses the last saved topology file, not the current one. Be sure to save the topology file before using a Run command.

Secondary Deployers

To run a secondary deployer from the launchpad:

1. On the launchpad, click Start the Deployer.

2. On the Start Deployer page, click the Start Deployer link.

To run a secondary deployer from the command line:

1. Log in as root.

2. Change to the directory containing the deployer within the downloaded Netcool/Proviso distribution:

On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/deployer/

On AIX systems:# cd <DIST_DIR>/proviso/AIX/Install/deployer/

On Linux systems:# cd <DIST_DIR>/proviso/RHEL/Install/deployer/



# ./deployer.bin

See Appendix I, Deployer CLI Options for the list of supported command-line options.



Pre-Deployment Check

The Deployer will fail if the required patches listed in this file are not installed. The Deployer performs a check on the operating system versions and that the minimum required packages are installed. The Deployer checks for the files as listed in the relevant check_os.ini file.

The check_os.ini can be found at:

• The check_os.ini file detailing Solaris requirements can be found at:

/SOLARIS/Install/SOL10/deployer/proviso/bin/Check/check_os.ini

• The check_os.ini file detailing AIX requirements can be found at:

/AIX/Install/deployer/proviso/bin/Check/check_os.ini

• The check_os.ini file detailing Linux requirements can be found at:

/RHEL/Install/deployer/proviso/bin/Check/check_os.ini

To check if the required packages are installed:

1. Click Run > Run Deployer for Installation to start the Deployer.

2. Select the Check prerequisites check box.

3. Click Next.

The check will return a failure if any of the required files are missing.

To repair a failure:

1. Log in as root.

2. Install the packages listed as missing.

3. (Linux only) If any openmotif package is listed as missing:

3-a. Install the missing openmotif package.

3-b. Update the package DB using the command:

# updatedb

4. Rerun the check prerequisites step.

Deploying the Topology

The deployer displays a series of pages to guide you through the Netcool/Proviso installation. The installation steps are displayed in a table, which enables you to run each step individually or to run all the steps at once. For more information about the deployer interface, see The Deployer on page 76.

Important: By default, Netcool/Proviso uses Monday to determine when a new week begins. If you wish to specify a different day, you must change the FIRST_WEEK_DAY parameter in the Database Registry using the dbRegEdit utility. This parameter can only be changed when you first deploy the topology that installs your Netcool/Proviso environment, and it must be changed BEFORE the Database Channel is installed. For more information, see the Netcool/Proviso Registry and Space Management Tech Note.

If you need to stop the installation, you can resume it at a later time. For more information, see Resuming a Partially Successful First-Time Installation on page 104.

To deploy the Netcool/Proviso topology:



1. The deployer opens, displaying a welcome page. Click Next to continue.

2. If you started the deployer from the launchpad or from the command line, enter the full path to your topology file, or click Choose to navigate to the correct location. Click Next to continue.

Note: If you start the deployer from within the Topology Editor, this step is skipped.

3. The database access window prompts for the security credentials. Enter the host name (for example, delphi) and database administrator password (for example, PV), and verify the other values (port number, SID, and user name). Note that if the database does not yet exist, these parameters must match the values you specified when you created the database configuration component (see Add a Database Configurations Component on page 89). Click Next to continue.

4. The node selection window shows the target systems and how the files will be transferred (see Node Selection on page 77 for an explanation of this window). The table has one row for each machine where at least one Netcool/Proviso component will be installed.

The default settings are as follows:

— The Enable checkbox is selected. If this option is not selected, no actions will be performed on that machine.

— The Check prerequisites checkbox is not selected, if selected scripts are run to verify that the prerequisite software has been installed.

— Remote execution is enabled, using both RSH and SSH.

Remote installation is not supported for the DataMart and database components. If you are installing the components on multiple servers, the remote host for these components will not be selectable: you must start the deployer locally on that host to install those components. For more information, see Remote Installation on page 187 and Primary Versus Secondary Deployers on page 102.

— File transfer using FTP is enabled.

If desired, reset the values as appropriate for your deployment.


5. The deployer displays summary information about the installation. Review the information, then click Next.

The deployer displays the table of installation steps (see Installation Steps on page 78 for an overview of the steps table). Note the following:

— Regardless of whether the steps are run, or if they pass or fail, closing the wizard will result in the topology being posted to the Proviso Database, assuming it exists.

— If an installation step fails, see Step Status Values on page 80 for debugging information. Continue the installation by following the instructions in Resuming a Partially Successful First-Time Installation on page 104.

— If the TCR installation step fails, which can happen when there is not enough space available in /usr and /tmp or directory cleanup has not been carried out, run the tcrClean.sh script. To run this script:

5-a. Copy the tcrClean.sh script from the Primary Deployer (host where the Topology Editor is installed) to the server where the TCR installation step fails. The tcrClean.sh script can be found on the Primary Deployer in the directory:

/opt/IBM/proviso/deployer/proviso/bin/Util/

5-b. Run tcrClean.sh.

5-c. When prompted, enter the install location of TCR.

5-d. Continue the installation by following the instructions in Resuming a Partially Successful First-Time Installation on page 104

6. Click Run All to run all the steps in sequence.

7. The deployer prompts you for the location of the setup files. Use the file selection window to navigate to the top-level directory for your operating system to avoid further prompts.



For example:

<DIST_DIR>/RHEL/


Note: This assumes that the Netcool/Proviso distribution was downloaded to the folder /var/tmp/cdproviso as per the instructions in Downloading the Netcool/Proviso Distribution to Disk on page 21.

If Tivoli Integrated Portal is configured to install on a remote host, the Run Remote TIP Install step is included. This step will prompt the user to enter the root password. The deployer requires this information in order to run as root on the remote host and perform the Tivoli Integrated Portal installation.

8. When all the steps have completed successfully, click Done to close the wizard.

9. Stop and start TCR by navigating to the /tip_install_dir/products/tcr/bin/ directory and running the following scripts:

— stopTCRserver.sh <username> <password>

— startTCRserver.sh

Note: These scripts must be run every time Tivoli Integrated Portal is restarted.

Next Steps

The next step is to install the technology packs, as described in Chapter 6, Introduction to Installing Netcool/Proviso Technology Packs.

Once you have created the topology and installed Netcool/Proviso, it is very easy to make changes to the environment. Simply open the deployed topology file (loading it from the database), make your changes, and run the deployer with the updated topology file as input. For more information about performing incremental installations, see Chapter 7, Modifying the Current Deployment.

Note: After your initial deployment, always load the topology file from the database to make any additional changes (such as adding or removing a component), because it reflects the current status of your environment. Once you have made your changes, you must deploy the updated topology so that it is propagated to the database. To make any subsequent changes following this deployment, you must load the topology file from the database again.

To improve performance, IBM recommends that you regularly compute the statistics on metadata tables. You can compute these statistics by creating a cron entry that executes the dbMgr (Database Manager Utility) analyzeMetaDataTables command at intervals.

The following example shows a cron entry that checks statistics every hour at 30 minutes past the hour. Note that the ForceCollection option is set to N, so that statistics will only be calculated when the internal calendar determines that it is necessary, and not every hour:

0 5 * * * [ -f /opt/DM/dataMart.env ] && [ -x /opt/DM/bin/dbMgr ] && . /opt/DM/dataMart.env && dbMgr analyzeMetaDataTables A N

For more information on dbMgr and the analyzeMetaDataTables command, see the Netcool/Proviso dbMgr Reference Guide.



Primary Versus Secondary Deployers

Only one instance of the Topology Editor can exist in the Netcool/Proviso environment. The Topology Editor includes an embedded copy of the deployer. The combination of the Topology Editor and the embedded instance of the deployer is called the primary deployer. The primary deployer should run on the system hosting the database server.

Note: If you are making changes to the Netcool/Proviso system configuration, use the primary deployer to make those changes.

Once you have completed the topology definition, you can start the primary deployer from within the Topology Editor, by selecting Run > Run Deployer for Installation. When the primary deployer has completed the Netcool/Proviso installation, it stores the topology data and the channel configuration (DataChannel and DataLoad) in the database. The primary deployer must complete before other operations can occur.

A secondary deployer is used to install DataMart on any server in the Netcool/Proviso topology where the Topology Editor is not installed. A secondary deployer does this by retrieving the topology data from the database and installing the component based on the topology definition.

Netcool/Proviso Version 5.2 supports remote installation of DataLoad, DataChannel and DataView, but not of DataMart. You must use a secondary deployer to install DataMart on a server that does not host the primary deployer.

To install DataMart using a secondary deployer:

The following steps describe how to install DataMart using a secondary deployer. To illustrate we will name the primary deployer host delphi, and the host on which we want to install Datamart using the secondary deployer we will name corinth.

1. Copy the Netcool/Proviso distribution to the server on which you would like to set up the secondary deployer, that is, copy the distribution to corinth. For more information on copying the Netcool/Proviso distribution to a server, see Downloading the Netcool/Proviso Distribution to Disk on page 21.

2. Open the Topology Editor on delphi, and add the remote DataMart to the topology definition. You may have completed this task already when creating your original topology definition. If you have already added DataMart to your topology, skip to the next step.

3. Deploy the new topology containing the added DataMart component using the Topology Editor. This is done by clicking Run > Run Deployer for Installation. This will push the edited topology to the database.

4. Open the Deployer on corinth by doing the following:

4-a. Connect to corinth, change to the directory where you have downloaded the product distribution, and launch the deployer either in graphical mode (by starting the Launchpad and clicking Start Deployer) or CLI mode (by navigating to the directory containing the deployer and entering the command ./deployer.bin).

4-b. Enter the database credentials when prompted. The deployer connects to the database.

For more information on how to run a secondary deployer, see Secondary Deployers on page 98.

Note: Due to Step 3, the secondary deployer sees the topology data and knows that the DataMart is still to be installed on corinth.

5. Follow the on screen instructions to install DataMart.

Note: You cannot launch the deployer simultaneously from two different hosts. Only one deployer can be active at any given time.



Note the following:

• Any system that runs a secondary deployer must have Java and X Window support. See the Netcool/Proviso Configuration Recommendations document for version requirements.

Note: For more information on remote deployment, see Remote Installation on page 187.



Resuming a Partially Successful First-Time Installation

In this scenario, you try deploying a Netcool/Proviso topology for the first time. You define the topology and start the installation. Although some of the components of the Netcool/Proviso topology are installed successfully, the overall installation does not complete successfully.

It addition, it is possible to skip a section of the installation. For example, a remote node might not be accessible for some reason. After skipping this portion of the installation, resume the installation to continue with the remaining steps. The deployer will list only those steps needed to complete the installation on the missing node.

For example, suppose that during the first installation, Oracle wasn’t running, so the database check failed. Stop the installation, start Oracle, then resume the installation.

To resume a partial installation:

1. After correcting the problem, restart the deployer from the command line using the following command:

./deployer.bin -Daction=resume

Using the resume switch enables you to resume the installation exactly where you left off.

Note: If you are asked to select a topology file in order to resume your installation, select the topology file you saved before beginning the install.


3. Accept the default location of the base installation directory of the Oracle JDBC driver (/opt/oracle/product/version/jdbc/lib), or click Choose to navigate to another directory. Click Next to continue.

4. The steps page shows the installation steps in the very same state they were in when you stopped the installation (with the completed steps marked Success, the failed step marked Error, and the remaining steps marked Held).

5. Select the step that previously failed, reset it to Ready, then click Run Next. Verify that this installation step now completes successfully.

6. Run any remaining installation steps, verifying that they complete successfully.

7. At the end of the installation, the deployer loads the updated topology information into the database.


Chapter 5: Installing Netcool/Proviso as a Minimal Deployment

This chapter describes how to install Netcool/Proviso as a minimal deployment. The topics are as follows:

Overview

A minimal deployment installation is used primarily for demonstration or evaluation purposes, and installs the product on the smallest number of machines possible, with minimal user input. This installation type installs all the Netcool/Proviso components on the local host using a predefined topology file to define the infrastructure. The minimal deployment installation also installs the MIB-II SNMP technology pack.

When you perform a minimal deployment installation, the Netcool/Proviso components are installed on the server you are running the deployer from.

Before You Begin

Before installing Netcool/Proviso, you must have installed the prerequisite software.

For detailed information, see Chapter 2, Installing and Configuring the Prerequisite Software.

Note: Before you start the installation, verify that all the database tests have been performed. Otherwise, the installation might fail. See Installing and Configuring the Prerequisite Software on page 7 for information about tnsping.

Topic Page

Overview 105

Before You Begin 105

Installing a Minimal Deployment 107

The Post-Installation Script 110

The Post-Installation Script 110

Next Steps 111



Special Consideration

By default, Netcool/Proviso uses Monday to determine when a new week begins. If you wish to specify a different day, you must change the FIRST_WEEK_DAY parameter in the Database Registry using the dbRegEdit utility. This parameter can only be changed when you first deploy the topology that installs your Netcool/Proviso environment, and it must be changed BEFORE the Database Channel is installed. For more information, see the Netcool/Proviso Registry and Space Management Tech Note.

No resume of partial install available

There is no resume functionality available to a minimal deployment installation. As a result a minimal deployment installation must be carried out in full if it is to be attempted

Do Not Override Default Values

When performing a minimal deployment installation you must accept all default values. This is the case for all default values. This includes, installation directory, oracle location and database location.



Installing a Minimal Deployment

This section provides step-by-step instructions for installing Netcool/Proviso on a single Solaris, AIX or Linux server.

Step 1: Download the MIB-II Files

The minimal deployment version installs the MIB-II Technology Pack. Before beginning the installation, you must download both the Technology Pack Installer and the MIB-II jar files.

To download these files, access either of the following distributions:

• The product distribution site:

https://www-112.ibm.com/software/howtobuy/softwareandservices

Located on the product distribution site are the ProvisoPackInstaller.jar file, the bundled jar file, and individual stand-alone technology pack jar files.

• (Optional) The Netcool/Proviso CD distribution, which contains the ProvisoPackInstaller.jar file and the jar files for the Starter Kit components.

See your IBM customer representative for more information about obtaining software.

Note: Both files must be in the same directory (for example, AP), and no other application jar files should be present. In addition, you must add the AP directory to the Netcool/Proviso distribution’s directory structure.

Step 2: Start the Launchpad

For an overview of the launchpad interface, see The Launchpad on page 62.

To start the launchpad:

1. Log in as root.

2. Set and export the DISPLAY variable (see Setting Up a Remote X Window Display on page 9).

3. Set and export the BROWSER variable to point to your Web browser. For example:

On Solaris systems:# BROWSER=/opt/mozilla/mozilla

# export BROWSER

On AIX systems:# BROWSER=/usr/mozilla/firefox/firefox

# export BROWSER

On Linux systems:# BROWSER=/usr/bin/firefox

# export BROWSER

Note: The BROWSER command cannot include any spaces around the equal sign.

4. Change directory to the directory where the launchpad resides.

On Solaris systems:




# cd <DIST_DIR>/proviso/SOLARIS

On AIX systems:# cd <DIST_DIR>/proviso/AIX

On Linux systems:# cd <DIST_DIR>/proviso/RHEL


5. Enter the following command to start the launchpad:

# ./launchpad.sh



Step 3: Start the Installation

A minimal deployment installation uses a predefined topology file.

To start the installation:

1. On the launchpad, click the Install Tivoli Netcool/Proviso 5.2 for Minimal Deployment option in the list of tasks, then click the Install Tivoli Netcool/Proviso 5.2 for Minimal Deployment link to start the deployer.

Alternatively, you can start the deployer from the command line, as follows:


1-b. Set and export your DISPLAY variable (see Setting Up a Remote X Window Display on page 9).

1-c. Change directory to the directory that contains the deployer:

On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/deployer

On AIX systems:# cd <DIST_DIR>/proviso/AIX/Install/deployer

On Linux systems:# cd <DIST_DIR>/proviso/RHEL/Install/deployer

1-d. Enter the following command:

# ./deployer.bin -Daction=poc -DPrimary=true


3. Accept the terms of the license agreement, then click Next.


5. The deployer prompts for the directory in which to install Netcool/Proviso. Accept the default value (/opt/proviso) or click Choose to navigate to another directory. Click Next to continue.

6. Verify the following additional information about the Oracle database:

— Oracle Base. The base directory for the Oracle installation (for example, /opt/oracle). Accept the provided path or click Choose to navigate to another directory.

— Oracle Home. The root directory of the Oracle database (for example, /opt/oracle/product/10.2.0). Accept the provided path or click Choose to navigate to another directory.

— Oracle Port. The port used for Oracle communications. The default value is 1521.


7. The node selection window shows the target system and how the files will be transferred. These settings are ignored for a minimal deployment installation because all the components are installed on a single server.




8. The deployer displays summary information about the installation. Review the information, then click Next to begin the installation.

The deployer displays the table of installation steps (see Installation Steps on page 78 for an overview of the steps table). Note the following:

— If an installation step fails, see Step Status Values on page 80 for debugging information. Continue the installation by following the instructions in Resuming a Partially Successful First-Time Installation on page 104

— Some of the installation steps can take a long time to complete. However, if an installation step fails, it will fail in a short amount of time.

9. Click Run All to run all the steps in sequence.

10. The deployer prompts you for the location of the setup files. Use the file selection window to navigate to the top-level directory for your operating system to avoid further prompts:

On Solaris systems:<DIST_DIR>/proviso/SOLARIS

On AIX systems:<DIST_DIR>/proviso/AIX

On Linux systems:<DIST_DIR>/proviso/RHEL



12. Run chmod -R 777 on /opt/IBM/tivoli in order to make all files in the TIP directory structure accessible.

Your installation is complete. See The Post-Installation Script on page 110 for information about the post-installation script, or Next Steps on page 111 for what to do next.

The Post-Installation Script

The post-installation script is run automatically when installation is complete. For a minimal deployment the script performs four actions:

1. Starts the DataChannel.

2. Starts the DataLoad SNMP Collector, if it is not already running.

3. Creates a DataView user named tnpm.

4. Gives the poc user permission to view reports under the NOC Reporting group, with the default password of tnpm.

The script writes a detailed log to the file /var/tmp/poc-post-install.${TIMESTAMP}.log.



Next Steps

When the installation is complete, you are ready to perform the final configuration tasks that enable you to view reports on the health of your network. These steps are documented in detail in the Netcool/Proviso documentation set.

For information about the MIB-II Technology Pack, see the MIB-II Technology Pack User’s Guide.

For information about installing additional technology packs, see Chapter 6, Introduction to Installing Netcool/Proviso Technology Packs




Chapter 6: Introduction to Installing Netcool/Proviso Technology Packs

This chapter provides an introduction to installing technology packs, and consists of the following topics:

Overview

Netcool/Proviso supports the following technology pack installation procedures:

• 4.3-U/4.3-V technology pack installation

• 4.3-W and higher technology pack installation

Note: The Topology Editor was introduced at the same time as the 4.3-U technology pack release. All 4.3-U and higher bulk technology pack installations require the Topology Editor to configure the technology pack. Configuration details are described in the technology pack’s User’ Guide.

Note: All technology packs, both legacy bundle and standlone, require the Technology Pack installer. Always use the latest Technology Pack installer, regardless of the version of the technology pack.

Note: Since the 4.3W technology pack release the former Starter Kit has been renamed to Pack Bundle Preruisites Preq pack. It is contained in the legacy bundle and is only required to be installed with a legacy pack that is also contained in the legacy bundle.

4.3-U/4.3-V Technology Pack Installation

The installation of 4.3-U/4.3-V technology packs requires the use of the Technology Pack installer. All technology packs also require that the Starter Kit be installed. The Starter Kit is contained in the legacy bundle.

To install 4.3-U/4.3-V technology packs, follow the instructions provided in Appendix A, Installing 4.3-U/4.3-V Netcool/Proviso Technology Packs on page 157.

Topic Page

Overview 113

4.3-U/4.3-V Technology Pack Installation 113

4.3-W and higher Technology Pack Installation 114

Netcool/Proviso Installation Guide, Version 4.4.3 113

Chapter 6: Introduction to Installing Netcool/Proviso Technology Packs

4.3-W and higher Technology Pack Installation

The installation of 4.3-W and higher technology pack requires the use of the Technology Pack installer. If a legacy bundle pack is being installed then the Pack Bundle Prerequisites are also required to be installed. The Pack Bundle Prerequisites are contained in the legacy bundle.

To install 4.3-W and higher technology packs, follow the instructions provided in Appendix C, Installing 4.3-W and higher Netcool/Proviso Technology Packs on page 173.

114 Netcool/Proviso Installation Guide, Version 4.4.3

Chapter 7: Modifying the Current Deployment

It is possible to modify Netcool/Proviso after it has been installed. To add, delete or upgrade components, load the deployed topology from the database, make your changes, and run the deployer with the updated topology as input.

Note: You must run the updated topology through the deployer in order for your changes to take effect.

This chapter describes how to modify an installation of Netcool/Proviso. The topics are as follows:

Note the following:

• After your initial deployment, always load the topology from the database to make any additional changes (such as adding or removing a component), because it reflects the current status of your environment. Once you have made your changes, you must deploy the updated topology so that it is propagated to the database. To make any subsequent changes following this deployment, you must load the topology from the database again.

• You might have a situation where you have modified a topology by both adding new components and removing components (marking them “To Be Removed”). However, the deployer can work in only one mode at a time — installation mode or uninstallation mode. In this situation, first run the deployer in uninstallation mode, then run it again in installation mode.

For information about deleting components from an existing topology, see Removing a Component from the Topology on page 147.

Topic Page

Opening a Deployed Topology 116

Adding a New Component 116

Example: 117

Changing Configuration Parameters of Existing Netcool/Proviso Components

118

Moving Components to a Different Host 119

Moving a Deployed Collector to a Different Host 119



Opening a Deployed Topology

Once you have installed Netcool/Proviso, you can perform incremental installations by modifying the topology that is stored in the database. You retrieve the topology, modify it, then pass the updated data to the deployer. When the installation is complete, the deployer stores the revised topology data in the database.

To open a deployed topology:


2. In the Topology Editor, select Topology > Open existing topology. The Open Topology window is displayed.

3. For the topology source, select From database (v. 443) and click Next.

4. 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 user name used to access the database. The default value is PV_INSTALL.

— Database Password — The password for the database user account. For example, PV.

— SID — The SID for the database. The default value is PV.

If desired, click Save as defaults to save these values for future incremental installations.

Click Finish.

The topology is retrieved from the database and is displayed in the Topology Editor.

Adding a New Component

After you have deployed your topology, you might need to make changes to it. For example, you might want to add another SNMP collector.

To add a new component to the topology:


2. Open the existing topology (see Opening a Deployed Topology on page 116).

3. In the Logical view of the Topology Editor, right-click the folder for the component you want to add.

4. Select Add XXX from the pop-up menu, where XXX is the name of the component you want to add.

5. The Topology Editor prompts for whatever information is needed to create the component. See the appropriate section for the component you want to add:

— Add the Hosts on page 87

— Add a Database Configurations Component on page 89

— Add a DataMart on page 90

— Add a Discovery Server on page 91

— Add a Tivoli Integrated Portal on page 92

— Add a DataView on page 92

— Add the DataChannel Administrative Components on page 93



— Add a DataChannel on page 93

— Add a Collector on page 94

Note that if you add a collector to a topology that has already been deployed, you must manually bounce the DataChannel management components (cnsw, logw, cmgrw, amgrw). For more information, see Manually Starting the Channel Manager Programs on page 198.

— Add a Discovery Server on page 91

6. The new component is displayed in the Logical view of the Topology Editor.

7. Save the updated topology. You must save the topology after you add the component and before you run the deployer. This step is not optional.

8. Run the deployer (see Starting the Deployer on page 98), passing the updated topology as input.

The deployer can determine that most of the components described in the topology are already installed, and installs only the new component.

9. When the installation ends successfully, the deployer uploads the updated topology into the database.

For information about removing a component from the Netcool/Proviso environment, see Removing a Component from the Topology on page 147.

Example:

In this example, you update the installed version of Netcool/Proviso to add a new DataChannel and two SNMP DataLoaders to the existing system.

To update the Netcool/Proviso installation:



3. In the Logical view of the Topology Editor, right-click the DataChannels folder.

4. Select Add Data Channel from the pop-up menu. Following the directions in Add a DataChannel on page 93, add the following components:

4-a. Add a new DataChannel (Data Channel 2) with two different SNMP DataLoaders to the topology. The Topology Editor creates the new DataChannel.

4-b. Add two SNMP collectors to the channel structure created by the Topology Editor. The editor automatically creates a Daily Loader component, an Hourly Loader component, and two Sub Channels with an FTE component and a CME component.

5. Save the updated topology.

6. Run the deployer (see Starting the Deployer on page 98), passing the updated topology as input.

The deployer can determine that most of the components described in the topology are already installed, and installs only the new components (in the example, DataChannel 5 with two new subchannels and DataLoaders).

7. When the installation ends, successful or not, the deployer uploads the updated topology into the database.



Changing Configuration Parameters of Existing Netcool/Proviso Components

Configuration information is stored in the database. This enables the DataChannel-related components to retrieve the configuration from the database at run time.

You set the configuration information using the Topology Editor, described in The Topology Editor on page 64. As with the other components, if you make changes to the configuration values, you must pass the updated topology data to the deployer to have the changes propagated to both the environment and the database.

Note: After the updated configuration has been stored in the database, you must manually start, stop, or bounce the affected DataChannel component to have your changes take effect.



Moving Components to a Different Host

You can use the Topology Editor to move components between hosts. You can move all components between hosts when they have not yet been installed and are in the configured state. You can move SNMP and UBA collectors when they are in the configured state or after they have been deployed and are in the installed state.

If the component in the topology has not yet been deployed and is in the configured state, the Topology Editor provides a Change Host option in the pop-up menu when you click the component name in the Logical view. This option allows you to change the host associated with the component prior to deployment.

If the component is an SNMP or UBA collector that was previously deployed and is in the installed state, the Topology Editor provides a Migrate option in the pop-up menu. This option instructs the deployer to uninstall the component from the previous host and re-install it on the new system.

For instructions on moving deployed SNMP and UBA collectors after deployment, see Moving a Deployed Collector to a Different Host on page 119. For instructions on moving components that have not yet been deployed, see the information below.

Note: The Movement of installed DataChannel Remote components is not supported. All other components can be moved.

To change the host associated with a component before deployment:

1. Start the Topology Editor (if it is not already running) and open the topology that includes the component’s current host (see Starting the Topology Editor on page 86 and Opening a Deployed Topology on page 116).

2. In the Logical view, navigate to the name of the component to move.

3. Right-click the component name, then click Change Host from the pop-up menu.

The Migrate Component dialog appears, containing a drop-down list of hosts where you can move the component.

4. Select the name of the new host from the list, then click Finish.

The name of the new host appears in the Properties tab.

Moving a Deployed Collector to a Different Host

You can move a deployed SNMP or UBA collector to a different host. The instructions for doing so differ for SNMP collectors and UBA collectors.

After you move a collector to a new host, it may take several hours for the change to be registered in the database.

Moving a Deployed SNMP Collector

Note: To avoid the loss of collected data, leave the collector running on the original host until you complete Step 7 on page 120.

To move a deployed SNMP collector to a different host:

1. Start the Topology Editor (if it is not already running) and open the topology that includes the collector’s current host (see Starting the Topology Editor on page 86 and Opening a Deployed Topology on page 116).

2. In the Logical view, navigate to the name of the collector to move. For example if moving SNMP 1.1, navigate as follows:



DataChannels > DataChannel 1 > Collector 1.1 > Collector SNMP.1.1

3. Right-click the collector name (for example, Collector SNMP 1.1), then click Migrate from the pop-up menu.

The Migrate Collector dialog appears, containing a drop-down list of hosts where you can move the collector.

Note: If you are moving a collector that has not been deployed, select Change host from the pop-up menu (Migrate is grayed out). After the Migrate Collector dialog appears, continue with the steps below.


In the Physical view, the status of the collector on the new host is Configured. The status of the collector on the original host is To be uninstalled. You will remove the collector from the original host in Step 9.

Note: If you are migrating a collector that has not been deployed, the name of the original host is automatically removed from the Physical view.

5. Click Topology > Save Topology to save the topology data.

6. Click Run > Run Deployer for Installation to run the deployer, passing the updated topology as input. For more information on running the deployer, see Starting the Deployer on page 98.

The deployer installs the collector on the new host and starts it.

Note: Both collectors are now collecting data — the original collector on the original host, and the new collector on the new host.

7. Before continuing with the steps below, note the current time, and wait until a time period equivalent to two of the collector’s collection periods elapses. Doing so guards against data loss between collections on the original host and the start of collections on the new host.

Because data collection on the new host is likely to begin sometime after the first collection period begins, the data collected during the first collection period will likely be incomplete. By waiting for two collection time periods to elapse, you can be confident that data for one full collection period will be collected.

The default collection period is 15 minutes. You can find the collection period for the sub-element, sub-element group, or collection formula associated with the collector in the DataMart Request Editor. For information on viewing and setting a collection period, see the Netcool/Proviso DataMart Configuration Guide.

8. Bounce the FTE for the collector on the collector’s new host, as in the following example:

./dccmd bounce FTE.1.1

The FTE now recognizes the collector’s configuration on the new host, and will begin retrieving data from the collector’s output directory on the new host.

9. In the current Topology Editor session, click Run > Run Deployer for Uninstallation to remove the collector from the original host, passing the updated topology as input. For more information, see Removing a Component from the Topology on page 147.

Note: This step is not necessary if you are moving a collector that has not been deployed.



Moving a Deployed SNMP Collector to or from a HAM Environment

If you move a deployed SNMP collector into or out of a High Availability Manager (HAM) environment, you must perform the steps in this section.

To move a deployed SNMP collector to or from a HAM environment:

1. Move the collector as described in Moving a Deployed SNMP Collector on page 119.

Note: If you are moving a spare collector out of the HAM environment, the navigation path is different than the path shown in Step 2 of the above instructions. For example, suppose you have a single HAM environment with a cluster MyCluster on host MyHost, and you are moving the second SNMP spare out of the HAM. The navigation path to the spare would be as follows:

DataChannels > Administrative Components > High Availability Managers > HAM MyServer.1 > MyCluster > Collector Processes > Collection Process SNMP Spare 2

2. Log in as Netcool/Proviso Unix user, pvuser, on the collector’s new host.

3. Change to the directory where DataLoad is installed. For example:

cd /opt/dataload

4. Source the DataLoad environment:

. ./dataLoad.env

5. Stop the SNMP collector:

pvmdmgr stop

6. Edit the file dataLoad.env and set the field DL_HA_MODE as follows:

— Set DL_HA_MODE=true if you moved the collector onto a HAM host.

— Set DL_HA_MODE=false if you moved the collector off of a HAM host.

7. Source the DataLoad environment again:

. ./dataLoad.env

8. Start the SNMP collector:

pvmdmgr start

Note: If you move an SNMP collector to or from a HAM host, you must bounce the HAM. For information, see Stopping and Restarting Modified Components on page 144.

Moving a Deployed UBA Bulk Collector

Note: You cannot move BCOL collectors, or UBA collectors that have a BLB or QCIF subcomponent. If you want to move a UBA collector that has these subcomponents, you must manually remove it from the old host in the topology and then add it to the new host.

To move a deployed UBA collector to a different host:

1. Log in as pvuser to the DataChannel host where the UBA collector is running.

2. Change to the directory where DataChannel is installed. For example:

cd /opt/datachannel

3. Source the DataChannel environment:

. dataChannel.env



4. Stop the collector’s UBA and FTE components. For example, to stop these components for UBA collector 1.1, run the following commands:

dccmd stop UBA.1.1

and...dccmd stop FTE.1.1

For information on the dccmd command, see the Netcool/Proviso Command Line Interface Guide.

Note: Some technology packs have additional pack-specific components that must be shut down — namely, BLB (bulk load balancer) and IF (inventory file) components. IF component names have the format xxxIF, where xxx is a pack-specific name. For example, Cisco CWM packs have a CWMIF component, Alcatel 5620 SAM packs have a SAMIF component, and Alcatel 5620 NM packs have a QCIF component. Other packs do not use these technology-specific components.

5. Tar up the UBA collector’s UBA directory. You will copy this directory to the collector’s new host later in the procedure (Step 13).

Note: This step is not necessary if the collector’s current host and the new host share a file system.

For example, to tar up a UBA directory for UBA collector 1.1, run the following command:

tar -cvf UBA_1_1.tar ./UBA.1.1/*

Note: Some technology packs have additional pack-specific directories that need to be moved. These directories have the same names as the corresponding pack-specific components described in Step 4.

6. Start the Topology Editor (if it is not already running) and open the topology that includes the collector’s current host (see Starting the Topology Editor on page 86 and Opening a Deployed Topology on page 116).

7. In the Logical view, navigate to the name of the collector to move — for example, Collector UBA.1.1.

8. Right-click the collector name and select Migrate from the pop-up menu.

The Migrate Collector dialog appears, containing a drop-down list of hosts where you can move the collector.


In the Physical view, the status of the collector on the new host is Configured. The collector is no longer listed under the original host.

Note: If the UBA collector was the only DataChannel component on the original host, the collector will be listed under that host, and its status will be “To be uninstalled.” You can remove the DataChannel installation from the original host after you finish the steps below. For information on removing DataChannel from the host, see Removing a Component from the Topology on page 147.

10. Click Topology > Save Topology to save the topology.

11. Click Run > Run Deployer for Installation to run the deployer, passing the updated topology as input. For more information on running the deployer, see Starting the Deployer on page 98.

If DataChannel is not already installed on the new host, this step installs it.

12. Click Run > Run Deployer for Uninstallation to remove the collector from the original host, passing the updated topology as input. For more information, see Removing a Component from the Topology on page 147.

13. Copy any directory you tarred in Step 5 and the associated JavaScript files to the new host.

Note: This step is not necessary if the collector’s original host and the new host share a file system.



For example, to copy UBA_1_1.tar and the JavaScript files from the collector’s original host:

13-a. Log in as pvuser to the UBA collector’s new host.

13-b. Change to the directory where DataChannel is installed. For example:

cd /opt/datachannel

13-c. FTP to the collector’s original host.

13-d. Run the following commands to copy the tar file to the new host. For example:

cd /opt/datachannel get UBA_1_1.tar bye tar -xvf UBA_1_1.tar

13-e. Change to the directory where the JavaScript files for the technology pack associated with the collector are located:

cd /opt/datachannel/scripts

13-f. FTP the JavaScript files from the /opt/datachannel/scripts directory on the original host to the /opt/datachannel/scripts directory on the new host.

14. Log in as pvuser to the Channel Manager host where the Administrator Components (including CMGR) are running.

15. Stop and restart the Channel Manager by performing the following steps:

15-a. Change to the $DC_HOME directory (typically, /opt/datachannel).

15-b. Source the DataChannel environment:

. dataChannel.env

15-c. Get the CMGR process ID by running the following command:

ps -ef | grep CMGR

The process ID appears in the output immediately after the user ID, as shown below in bold:pvuser 6561 6560 0 Aug 21 ? 3:04 /opt/datachannel/bin/CMGR_visual -nologo /opt/datachannel/bin/dc.im -a CMGR pvuser 25976 24244 0 11:39:38 pts/7 0:00 grep CMGR

15-d. Stop the CMGR process. For example, if 6561 is the CMGR process ID:

kill -9 6561

15-e. Change to the $DC_HOME/bin directory (typically, /opt/datachannel/bin).

15-f. Restart CMGR by running the following command:

./cmgrw

16. Log in as pvuser to the UBA collector’s new host and change to the $DC_HOME/bin directory (typically, /opt/datachannel/bin).



17. Run the following command to verify that Application Manager (AMGR) is running on the new host:

./findvisual

If the AMGR process is running, you will see output that includes an entry like the following:

pvuser 6684 6683 0 Aug 21 ? 3:43 /opt/datachannel/bin/AMGR_visual -nologo /opt/datachannel/bin/dc.im -a AMGR -lo

Note: If AMGR is not running on the new host, do not continue. Verify that you have performed the preceding steps correctly.

18. Start the collector’s UBA and FTE components on the new host. For example, to start these components for collector 1.1, run the following commands:

./dccmd start UBA.1.1

and..../dccmd start FTE.1.1

Note: If any pack-specific components were shut down on the old host (see Step 4), you must also start those components on the new host.


Chapter 8: Using the High Availability Manager

This chapter describes the optional Netcool/Proviso High Availability Manager (HAM), including how to set up a HAM environment. The topics are as follows:

Overview

The High Availability Manager (HAM) is an optional component for large installations that want to use redundant SNMP collection paths. The HAM constantly monitors the availability of one or more SNMP collection hosts, and switches collection to a backup host (called a spare) if a primary host becomes unavailable.

The following figure shows a simple HAM configuration with one primary host and one spare. In the panel on the left, the primary host is operating normally. SNMP data is being collected from the network and channeled to the primary host. In the panel on the right, the HAM has detected that the primary host is unavailable, so it dynamically unbinds the collection path from the primary host and binds it to the spare.

Topic Page

Overview 125

HAM Basics 126

HAM Cluster Configuration 127

Resource Pools 134

How the SNMP Collector Works 134

Creating a HAM Environment 138

Modifying a HAM Environment 144

Viewing the Current Configuration 145

S p a re

Network withSNMP devices

CollectorHosts

P rim a ry


CollectorHosts

P r im a r y

S pa r e



HAM Basics

An SNMP collector collects data from a specific set of network resources according to a set of configuration properties. A collector has two basic parts: the collector process running on the host computer, and the collector profile that defines the collector’s properties.

Note: Do not confuse a “collector profile” with an “inventory profile.” A collector profile contains properties used in the collection of data from network resources — properties such as collector number, polling interval, and output directory for the collected data. An inventory profile contains information used to discover network resources — properties such as the addresses of the resources to look for and the mode of discovery.

A collector that is not part of a HAM environment is static — that is, the collector process and the collector profile are inseparable. But in a HAM environment, the collector process and collector profile are managed as separate entities. This means that if a collector process is unavailable (due to a collector process crash or a host machine outage), the HAM can dynamically reconfigure the collector, allowing data collection to continue. The HAM does so by unbinding the collector profile from the unavailable collector process on the primary host, and then binding the collector profile to a collector process on a backup (spare) host.

Note: It may take several minutes for the HAM to reconfigure a collector, depending on the amount of data being collected.

The Parts of a Collector

When you set up a HAM configuration in the Topology Editor, you manage the two parts of a collector — the collector process and the collector profile — through the following folders in the Logical view:

• Collector Processes. A collector process is a Unix process representing a runtime instance of a collector. A collector process is identified by the name of the host where the process is running and by the collector process port (typically 3002).

A host can have just one SNMP collector process.

• Managed Definitions. A managed definition identifies a collector profile through the unique collector number defined in the profile.

Every managed definition has a default binding to a host and to the collector process on that host. The default host and collector process are called the managed definition’s primary host and collector process.

A host that you designate as a spare host has a collector process but no default managed definition.

The following figure shows the parts of a collector that you manage through the Collector Process and Managed Definition folders. In the figure, the HAM dynamically unbinds the collector profile from the collector process on the primary host, and then binds the profile to the collector process on the spare. This dynamic re-binding of



the collector is accomplished when the HAM binds the managed definition — in this case, represented by the unique collector ID, Collector 1 — to the collector process on the spare.

Clusters

A HAM environment can consist of a single set of hosts or multiple sets of hosts. Each set of hosts in a HAM environment is called a cluster.

A cluster is a logical grouping of hosts and collector processes that are managed by a HAM.

The use of multiple clusters is optional. Whether you use multiple clusters or just one has no affect on the operation of the HAM. Clusters simply give you a way to separate one group of collectors from another, so that you can better deploy and manage your primary and spare collectors in a way that is appropriate for your needs.

Multiple clusters may be useful if you have a large number of SNMP collector hosts to manage, or if the hosts are located in various geographic areas.

The clusters in a given HAM environment are distinct from one another. In other words, the HAM cannot bind a managed definition in one cluster to a collector process in another.

HAM Cluster Configuration

For host failover to occur, a HAM cluster must have at least one available spare host.

The cluster can have as few as two hosts — one primary and one spare. Or, it can have multiple primary hosts with one or more spares ready to replace primary hosts that become unavailable.

The ratio of primary hosts to spare hosts is expressed as p + s. For example, a HAM cluster with four primary hosts and two spares is referred to as a 4+2 cluster.

S p a re


Collector 1Hosts

P rim a ry


Collector 1Hosts

P r im a r y

S pa r e

ManagedDefinition

ManagedDefinition

CollectorProcess

CollectorProcess



Types of Spare Hosts

There are two types of spare hosts:

• Designated spare. The sole purpose of this type of spare in a HAM cluster is to act as a backup host.

A designated spare has a collector process, but no default managed definition. Its collector process remains idle until the HAM detects an outage on one of the active hosts, and binds that host’s managed definition to the spare’s collector process.

A HAM cluster must have at least one designated spare.

• Floating spare. This type of spare is a primary host that can also act as a backup host for one or more managed definitions.

Types of HAM Clusters

When the HAM binds a managed definition to a spare (either a designated spare or a floating spare), the spare becomes an active component of the collector. It remains so unless you explicitly reassign the managed definition back to its primary host or to another available host in the HAM cluster. This is an important fact to consider when you plan the hosts to include in a HAM cluster.

There are two types of HAM clusters:

• Fixed spare cluster. In this type of cluster, failover can occur only to designated spares. There are no floating spares in this type of cluster.

When the HAM binds a managed definition to the spare, the spare temporarily takes the place of the primary that has become unavailable. When the primary becomes available again, you must reassign the managed definition back to the primary (or to another available host). The primary then resumes its data collection operations, and the spare resumes its role as backup host.

If you do not reassign the managed definition back to the primary, the primary cannot participate in further collection operations. Since the primary is not configured as a floating spare, it also cannot act as a spare now that its collector process is idle. As a result, the HAM cluster loses its failover capabilities if no other spare is available.

Note: A primary host cannot act as a spare unless it is configured as a floating spare.

• Floating spare cluster. This type of cluster has one or more primary hosts that can also act as a spare. Failover can occur to a floating spare or to a designated spare.

You do not need to reassign the managed definition back to this type of primary, as you do with primaries in a fixed spare cluster. When a floating spare primary becomes available again, it assumes the role of a spare.

You can designate some or all of the primaries in a HAM cluster as floating spares. If all the primaries in a HAM cluster are floating spares, you should never have to reassign a managed definition to another available host in order to maintain failover capability.

Note: IBM recommends that all the primaries in a cluster be of the same type — either all floating spares or no floating spares.



Example HAM Clusters

The Netcool/Proviso High Availability Manager feature is designed to provide great flexibility in setting up a HAM cluster. The following illustrations show just a few of the possible variations.

1 + 1, Fixed Spare

The figure below shows a fixed spare cluster with one primary host and one designated spare:

• In the panel on the left, Primary1 is functioning normally. The designated spare is idle.

• In the panel on the right, Primary1 experiences an outage. The HAM unbinds the collector from Primary1 and binds it to the designated spare.

• With the spare in use and no other spares in the HAM cluster, failover can no longer occur — even after Primary1 returns to service. For failover to be possible again, you must reassign Collector 1 to Primary1. This idles the collector process on the spare, making it available for the next failover operation if Primary 1 fails again.

D e s ig n a te dS p a re


Collector 1

Hosts

P r im a r y 1

ManagedDefinitions


Collector 1

Hosts

P r im a ry 1

ManagedDefinitions

Outage

D e s ig n a te dS p a r e

Note: When a designated spare serves as the only spare for a single primary, as in a 1+1 fixed spare cluster, the HAM pre-loads the primary’s collector definition on the spare. This results in a fast failover with a likely loss of no more than one collection cycle.

The following table shows the bindings that the HAM can and cannot make in this cluster:

Collector Possible Host Bindings Host Bindings Not Possible

Collector 1 Primary1 (default binding) Designated spare

—



2 + 1, Fixed Spare

The figure below shows a fixed spare cluster with two primary hosts and one designated spare:

• In the panel on the left, Primary1 and Primary2 are functioning normally. The designated spare is idle.


• With the spare in use and no other spares in the HAM cluster, failover can no longer occur — even after Primary2 returns to service. For failover to be possible again, you must reassign Collector 2 to Primary2. This idles the collector process on the spare, making it available for the next failover operation.



Collector 1

Hosts

P r im a r y 1

P r im a r y 2

ManagedDefinitions

Collector 2


Collector 1

Hosts

P r im a r y 1

P r im a ry 2

ManagedDefinitions

Collector 2 Outage





Primary2


Primary1



2 + 1, Both Primaries are Floating Spares

The figure below shows a floating spare cluster with two primary hosts and one designated spare, with each primary configured as a floating spare:

• In the panel on the left, Primary1 and Primary2 are functioning normally. The designated spare is idle.


• When Primary2 returns to service, it will assume the role of spare, meaning its collector process remains idle. The host originally defined as the dedicated spare continues as the active platform for Collector 2.


Collector 1

Hosts

P r im a r y 1 /F lo a t in g

S p a r e

ManagedDefinitions

Collector 2


Collector 1

HostsManagedDefinitions

Collector 2 OutageP r im a r y 2 /F lo a t in g

S p a r e

P r im a ry 2 /F l o a tin g

S p a re


S p a r e



• The following figure shows the same cluster after Primary2 has returned to service. In the panel on the left, Primary2 is idle, prepared to act as backup if needed.

• In the panel on the right, Primary1 experiences an outage. The HAM unbinds the collector from Primary1 and binds it to the floating spare, Primary2.

P r im a ry 1 /F l o a tin g

S p a re


Collector 1

Hosts


S p a r e

ManagedDefinitions

Collector 2


Collector 1


Collector 2

Outage



P r i m a ry 2 /F lo a ti n g

S p a re


S p a r e



Collector 1 Primary1 (default binding) Primary2 Designated spare

—

Collector 2 Primary1 Primary2 (default binding) Designated spare

—



3+ 2, Fixed Spares

The figure below shows a fixed spare cluster with three primary hosts and two designated spares:

• In the panel on the left, all three primaries are functioning normally. The designated spares are idle.

• In the panel on the right, Primary3 experiences an outage. The HAM unbinds the collector from Primary3 and binds it to Designated Spare 2. The HAM chose Designated Spare 2 over Designated Spare 1 because the managed definition for Collector 3 set the failover priority in that order.

Note: Each managed definition sets its own failover priority. Failover priority can be defined differently in different managed definitions.

• With one spare in use and one other spare available (Designated Spare 1), failover is now limited to the one available spare — even after Primary3 returns to service. For dual failover to be possible again, you must reassign Collector 3 to Primary3.

D e s ig n a te dS p a re 1


Collector 1

Hosts

P r im a r y 1

P r im a r y 2

ManagedDefinitions

Collector 2

OutageP r im a r y 3

Collector 3




Collector 1

Hosts

P r im a r y 1

P r im a r y 2

ManagedDefinitions

Collector 2

P r im a ry 3Collector 3

D e s ig n a te dS p a r e 2



Collector 1 Primary1 (default binding) Designated Spare 1 Designated Spare 2

Primary2 Primary3


Primary1 Primary3


Primary1 Primary2



3+ 2, All Primaries are Floating Spares

The figure below shows a floating spare cluster with three primary hosts and two designated spares, with each primary configured as a floating spare:

• In the panel on the left, Primary3 had previously experienced an outage. The HAM unbound its default collector (Collector 3) from Primary3, and bound the collector to the first available spare in the managed definition’s priority list, which happened to be Designated Spare 2. Now that Primary3 is available again, it is acting as a spare, while Designated Spare 2 remains the active collector process for Collector 3.

• In the panel on the right, Primary2 experiences an outage. The HAM unbinds Collector 2 from Primary2, and binds it to the first available spare in the managed definition’s priority list. This happens to be the floating spare Primary3.

• When Primary2 becomes available again, there will once more be two spares available — Primary2 and Designated Spare 1.



Collector 1


Collector 2

P r im a ry 3 /F lo a ti n g

S p a re

Collector 3



S p a r e

Outage



Collector 1


Collector 2


S p a r eCollector 3



S p a r e

P r i m a r y 2 /F l o a ti n g

S p a r e


S p a r e



Collector 1 Primary1 (default binding) Primary2 Primary3 Designated Spare 1 Designated Spare 2

—

Collector 2 Primary1 Primary2 (default binding) Primary3 Designated Spare 1 Designated Spare 2

—

Collector 3 Primary1 Primary2 Primary3 (default binding) Designated Spare 1 Designated Spare 2

—



Resource Pools

When you configure a managed definition in the Topology Editor, you specify the hosts that the HAM can bind to the managed definition, and also the priority order in which the hosts are to be bound. This list of hosts is called the resource pool for the managed definition.

A resource pool includes:

• The managed definition’s primary host and collector process (that is, the host and collector process that are bound to the managed definition by default).

• Zero or more other primary hosts in the cluster.

If you add a primary host to a managed definition’s resource pool, that primary host becomes a floating spare for the managed definition.

• Zero or more designated spares in the cluster.

Typically, each managed definition includes one or more designated spares in its resource pool.

Note: If no managed definitions include a designated spare in their resource pools, there will be no available spares in the cluster, and therefore failover cannot occur in the cluster.

How the SNMP Collector Works

The SNMP collector is state-based and designed both to perform initialization and termination actions, and to “change state” in response to events generated by the HAM or as a result of internally-generated events (like a timeout, for example).

The following table lists the events that the SNMP collector understands and indicates whether they can be generated by the HAM.

Event HAM-Generated Description

Load Yes Load collection profile, do not begin scheduling collections.

Pause Yes Stop scheduling collections; do not unload profile.

Reset Yes Reset expiration timer.

Start Yes Start scheduling collections.

Stop Yes Stop scheduling collections; unload profile

Timeout No Expiration timer expires; start scheduling collections.



The SNMP collector can reside in one of the following states, as shown in the following table:

The following state diagram shows how the SNMP collector transitions through its various states depending upon events or time-outs:

SNMP Collector State Event Description

Idle N/A Initial state; a collector number may or may not be assigned; the collection profile has not been loaded.

Loading Load Intermediate state between Idle and Ready. Occurs after a Load event. Collector number is assigned, and the collection profile is being loaded.

Ready N/A Collector number assigned, profile loaded, but not scheduling requests or performing collections.

Starting Start Intermediate state between Idle and Running. Occurs after a Start event. Collector number assigned, and profile is being loaded.

Running N/A Actively performing requests and collections.

Stopping Stop/Pause Intermediate state between Running and Idle.



How Failover Works With the HAM and the SNMP Collector

The following tables illustrate how the HAM communicates with the SNMP collectors during failover for a 1+1 cluster and a 2+1 cluster.

Because more than one physical system may produce SNMP collections, the File Transfer Engine (FTE) must check every capable system for a specific profile. The FTE retrieves all output for the specific profile. Any duplicated collections are reconciled by the Complex Metrics Engine (CME).

Table 8: HAM and SNMP Collector in a 1+1 Cluster

State of Primary State of Spare Events and Actions

Running Idle The HAM sends the spare the Load event for the specified collection profile.

Running Ready The HAM sends a Pause event to the spare to extend the timeout.

Note: If the timeout expires, the spare will perform start actions and transition to a Running state.

Running Running The HAM sends a Pause event to the collector process that has been in a Running state for a shorter amount of time.

No response Ready The HAM sends a Start event to the spare.

Table 9: HAM and SNMP Collector in a 2+1 Cluster

State of Primary State of Spare Events and Actions

Running Idle No action

Running Ready No action

Running Running The HAM sends a Stop event to the collector process that has been in Running state for the shorter amount of time.

No Response Idle The HAM sends a Start event to the spare.

No Response Ready The HAM sends a Start event to the spare.



Obtaining Collector Status

To obtain status on the SNMP collectors managed by the HAM, enter the following command on the command line:

$ dccmd status HAM.<hostname>.1

The dccmd command returns output similar to the following:COMPONENT APPLICATION HOST STATUS ES DURATION EXTENDED STATUS

HAM.DCAIX2.1 HAM DCAIX2 running 10010 1.1 Ok: (box1:3012 -> Running 1.1 for 5h2m26s); No avail spare; Check: dcaix2:3002, birdnestb:3002

1.2 Ok: (box2:3002 -> Running 1.2 for 5h9m36s); No avail spare; Check: box4:3002, box5:3002

1.3 Not Running; No avail spare; Check: box4:3002, box5:3002

The following list describes EXTENDED STATUS information:

• 1.1 - Load # Collection profile 1.1

• Ok: - Status of the load. Ok means it is properly collected, Not Running indicates a severe problem (data losses)

• (box1:3012 -> Running 1.1 for 5h2m26s)- The collector that is currently performing the load, with its status and uptime.

• No avail spare - List of possible spare, if something happens to the collector currently working. In this example there is no spare available, a failover would fail. A list of host:port would indicate the possible spare machines.

• Check: box4:3002, box5:3002 - Indicates what is currently wrong with the system/configuration. Machines box4:3002 and box5:3002 should be spare but are either not running, or not reachable. The user is instructed to check these machines.

For a 1-to-1 failover configuration, the dccmd command might return output like the following:

$ dccmd status HAM.SERVER.1

COMPONENT APPLICATION HOST STATUS ES DURATION EXTENDED STATUS

HAM.SERVER.1 HAM SERVER running 10010 1.1 Ok: (box1:3002 -> Running 1.1 for 5h2m26s); 1 avail spare: (box2:3002 -> Ready 1.1)

This preceding output shows that Collector 1.1 is in a Running state on Box1, and that the Collector on Box2 is in a Ready state, with the profile for Collector 1.1 loaded.



Creating a HAM Environment

This section describes the steps required to create a 3+1 HAM environment with a single cluster, and with all three primaries configured as floating spares.

This is just one of the many variations a HAM environment can have. The procedures described in the following sections indicate the specific steps where you can vary the configuration.

Note: If you are setting up a new Netcool/Proviso environment and plan to use a HAM in that environment, perform the following tasks in the following order:

1. Install all collectors.

2. Configure and start the HAM.

3. Install all technology packs.

4. Perform the discovery.

Topology Prerequisites

A 3+1 HAM cluster requires that you have a topology with the following minimum components:

• Three hosts, each bound to an SNMP collector. These will act as the primary hosts. You will create a managed definition for each of the primary hosts.

• One additional host that is not bound to an SNMP collector. This will act as the designated spare.

For information on installing these components, see Adding a New Component on page 116.

Procedures

The general procedures for creating a single-cluster HAM with one designated spare and three floating spares are as follows:

1. Create the HAM and a HAM Cluster

2. Add the Designated Spare

3. Add the Managed Definitions

4. Define the Resource Pools

5. Save and Start the HAM

The following sections describe these procedures in detail.

Step 1: Create the HAM and a HAM Cluster

To create a High Availability Manager with a single cluster:

1. Start the Topology Editor (if it is not already running) and open the topology where you want to add the HAM (see Starting the Topology Editor on page 86 and Opening a Deployed Topology on page 116).

2. In the Logical view, right-click High Availability Managers, located as follows:

DataChannels > Administrative Components



3. Select Add High Availability Manager from the pop-up menu.

The Add High Availability Manager Wizard appears.

4. In the Available hosts field, select the host where you want to add the HAM.

Note: You can install the HAM on a host where a collector process is installed, but you cannot install more than one HAM on a host.

5. In the Identifier field, accept the default identifier.

The identifier has the following format:

HAM.<HostName>.<n>

where HostName is the name of the host you selected in Step 4, and n is a HAM-assigned sequential number, beginning with 1, that uniquely identifies this HAM from others that may be defined on other hosts.

6. Click Finish.

The HAM identifier appears under the High Availability Managers folder.

7. Right-click the identifier of the HAM you just created.

8. Select Add Cluster from the pop-up menu.

The Add Cluster Monitor Wizard appears.

9. In the Identifier field, type a name for the cluster and click Finish.

The cluster name appears under the HAM identifier folder you added in Step 6. The following folders appear under the cluster name:

— Collector Processes

— Managed Definitions

Note: To add additional clusters to the environment, repeat Step 7 through Step 9.

Step 2: Add the Designated Spare

To create a designated spare, you must have a host defined in the Physical view with no SNMP collector assigned to it. For information on adding a host to a topology, see Step 1: Add the Hosts on page 87.

To add a designated spare to a cluster:

1. In the Logical view, right-click the Collector Processes folder that you created in Step 9 of the previous section, Step 1: Create the HAM and a HAM Cluster.

2. Select Add Collection Process SNMP Spare from the pop-up menu.

The Add Collection Process SNMP Spare — Configure Collector Process SNMP Spare dialog appears.

3. In the Available hosts field, select the host that you want to make the designated spare.

This field contains the names of hosts in the Physical view that do not have SNMP collectors assigned to them.

4. In the Port field, specify the default port number, 3002, for the spare’s collector process, then click Finish.

Under the cluster’s Collector Processes folder, the entry Collection Process SNMP Spare <n> appears, where n is a HAM-assigned sequential number, beginning with 1, that uniquely identifies this designated spare from others that may be defined in this cluster.

Note: Repeat Step 1 through Step 4 to add an additional designated spare to the cluster.



Should you be making changes to an already existing configuration, please make sure the dataLoad.env file contains all the right settings:

1. Change to the directory where DataLoad is installed. For example:

cd /opt/dataload

2. Source the DataLoad environment:

. ./dataLoad.env

3. Make sure that DL_HA_MODE field in the dataLoad.env file and set to DL_HA_MODE=true.

4. Source the DataLoad environment again:

. ./dataLoad.env

Step 3: Add the Managed Definitions

A managed definition allows the HAM to bind a collector profile to a collector process.

Note: When you add a managed definition to a HAM cluster, the associated collector process is automatically added to the cluster’s Collector Processes folder.

To add a managed definition to a HAM cluster:

1. In the Logical view, right-click the Managed Definitions folder that you created in Step 9 of the section Step 1: Create the HAM and a HAM Cluster on page 139.

2. Select Add Managed Definition from the pop-up menu.

The Add Managed Definition — Choose Managed Definition dialog appears.

3. In the Collector number field, select the unique collector number to associate with this managed definition.

4. Click Finish.

The following entries now appear for the cluster:

— Under the cluster’s Managed Definitions folder, the entry Managed Definition <n> appears, where n is the collector number you selected in Step 3.

— Under the cluster’s Collector Processes folder, the entry Collector Process [HostName] appears, where HostName is the host that will be bound to the SNMP collector you selected in Step 3. This host is the managed definition’s primary host.

Note: Repeat Step 1 through Step 4 to add another managed definition to the cluster.



When you finish adding managed definitions for a 3+1 HAM cluster, the Logical and Physical views might look like the following:

In this example, the hosts dcsol1a, dcsol1b, and docserver1 are the primaries, and docserver2 is the designated spare.

Step 4: Define the Resource Pools

A resource pool is a list of the spares, in priority order, that the HAM can bind to a particular managed definition.

When you create a managed definition, the managed definition’s primary host is the only host in its resource pool. To enable the HAM to bind a managed definition to other hosts, you must add more hosts to the managed definition’s resource pool.

To add hosts to a managed definition’s resource pool:

1. Right-click a managed definition in the cluster’s Managed Definitions folder.

2. Select Configure Managed Definition from the pop-up menu.



The Configure Managed Definition — Collector Process Selection dialog appears, as shown below. In this example, the resource pool being configured is for Managed Definition 1 (that is, the managed definition associated with Collector 1).

3. In the Additional Collector Processes list, check the box next to each host to add to the managed definition’s resource pool.

Typically, you will add at least the designated spare (in this example, docserver2) to the resource pool. If you add a primary host to the resource pool, that host becomes a floating spare for the managed definition.

Note: You must add at least one of the hosts in the Additional Collector Processes list to the resource pool

Since the goal in this example is to configure all primaries as floating spares, the designated spare and the two primaries (docserver1 and dcsol1a) will be added to the resource pool.

4. When finished checking the hosts to add to the resource pool, click Next.

Note: If you add just one host to the resource pool, the Next button is not enabled. Click Finish to complete the definition of this resource pool. Return to Step 1 to define a resource pool for the next managed definition in the cluster, or skip to Step 5: Save and Start the HAM if you are finished defining resource pools.

The Configure Managed Definition — Collector Process Order dialog appears, as shown below:



5. Specify the failover priority order for this managed definition. To do so:

5-a. Select a host to move up or down in the priority list, then click the Up or Down button until the host is positioned where you want.

5-b. Continue moving hosts until the priority list is ordered as you want.

5-c. Click Finish.

In this example, if the primary associated with Managed Definition 1 fails, the HAM will attempt to bind the managed definition to the floating spare dcsol1a. If dcsol1a is in use or otherwise unavailable, the HAM attempts to bind the managed definition to docserver1. The designated spare docserver2 is last in priority.

6. Return to Step 1 to define a resource pool for the next managed definition in the cluster, or continue with the next section if you are finished defining resource pools.

Step 5: Save and Start the HAM

When you finish configuring the HAM as described in the previous sections, you are ready to save the configuration and start the HAM.

To save and start the HAM:

1. Click Topology > Save Topology to save the topology file containing the HAM configuration.

2. Run the deployer (see Starting the Deployer on page 98), passing the updated topology file as input.

3. Open a terminal window on the DataChannel host.

4. Log in as pvuser.

5. Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default), as follows:

cd /opt/datachannel/bin

6. Bounce (stop and restart) the Channel Manager. For instructions, see Step 15 on page 123.


dccmd start ham

Monitoring of the HAM environment begins.

For information on using dccmd, see the Netcool/Proviso Command Line Interface Guide.

Creating an Additional HAM Environment

Typically, one HAM is sufficient to manage all the collectors you require in your HAM environment. But for performance reasons, very large Proviso deployments involving dozens or hundreds of collector processes might benefit from more than one HAM environment.

HAM environments are completely separate from one another. A host in one HAM environment cannot fail over to a host in another HAM environment.

To create an additional HAM environment, perform all of the procedures described in Creating a HAM Environment on page 138.



Modifying a HAM Environment

You can modify a HAM environment by performing any of the procedures in Creating a HAM Environment on page 138. For example, you can add collectors, add clusters, configure a primary host as a floating spare, change the failover priority order of a resource pool, and make a number of other changes to the environment, including moving collectors into or out of a HAM environment.

For information on moving a deployed SNMP collector into or out of a HAM environment, see Moving a Deployed SNMP Collector to or from a HAM Environment on page 121.

You can also modify the configuration parameters of the HAM components that are writable. For information on modifying configuration parameters, see Changing Configuration Parameters of Existing Netcool/Proviso Components on page 118.

Removing HAM Components

You can remove HAM components from the environment by right-clicking the component name and selecting Remove from the pop-up menu. The selected component and any subcomponents will be removed.

Before you can remove a designated spare (Collection Process SNMP Spare), you must remove the spare from any resource pools it may belong to. To remove a designated spare from a resource pool, open the managed definition that contains the resource pool, and clear the check box next to the name of the designated spare to remove. For information about managing resource pools, see Step 4: Define the Resource Pools on page 141.

Stopping and Restarting Modified Components

If you change the configuration of a HAM or any HAM components, or if you add or remove an existing collector to or from a HAM environment, you must bounce (stop and restart) the Netcool/Proviso components you changed The is generally true for all Netcool/Proviso components that you change, not just HAM.

To bounce a component:

1. Open a terminal window on the DataChannel host.

2. Log in as pvuser.

3. Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default), as follows:

cd /opt/datachannel/bin

4. Run the bounce command in the following format:

dccmd bounce <component>

For example:

— To bounce the HAM with the identifier HAM.dcsol1b.1, run:

dccmd bounce ham.dcsol1b.1

— To bounce all HAMs in the topology, run:

dccmd bounce ham.*.*

— To bounce the FTE for collector 1.1 that is managed by a HAM, run:

dccmd bounce fte.1.1

You do not need to bounce the HAM that the FTE and collector are in.



For information on using dccmd, see the Netcool/Proviso Command Line Interface Guide.

5. Bounce the Channel Manager. For instructions, see Step 15 on page 123.

Viewing the Current Configuration

During the process of creating or modifying a HAM cluster, you may find it useful to check how the individual collector processes and managed definitions are currently configured.

To view the current configuration of a collector process or managed definition:

1. Right-click the collector process or managed definition to view.

2. Select Show from the pop-up menu.

The Show Collector Process... or Show Managed Definition... dialog appears. The following sections describe the contents of these dialogs.

Show Collector Process... Dialog

The following figure shows a collector process configured with three managed definitions.

The configuration values are described as follows:

• dcsol1a. The primary host where this collector process runs.

• 3002. The port through which the collector process receives SNMP data.

• 3 2 (Primary) 1. The managed definitions that the HAM can bind to this collector process. The values have the following meanings:

— 3. The managed definition for Collector 3.

— 2 (Primary). The managed definition for Collector 2. This is the default managed definition for the collector process.

— 1. The managed definition for Collector 1.

Show Managed Definition... Dialog

The Show Managed Definition... dialog contains the resource pool for a particular managed definition.



This dialog contains the same information that appears in the Show Collector Process... dialog, but for multiple hosts instead of just one. As such, this dialog gives you a broader view of the cluster’s configuration than a Show Managed Definition... dialog.

The following figure shows a managed definition’s resource pool configured with four hosts:

Note the following about this managed definition’s resource pool:

• The priority order of the hosts is from top to bottom — therefore, the first collector process that the HAM will attempt to bind to this managed definition is the one on host dcsol1a. The collector process on host docserver2 is last in the priority list.

• The first three hosts are floating spares. They are flagged as such by each having a primary managed definition.

• The host docserver2 is the only designated spare in the resource pool. It is flagged as such by not having a primary managed definition.


Chapter 9: Uninstalling Components

This chapter provides information about uninstalling components. When you perform an uninstall, the “uninstaller” is the same deployer used to install Netcool/Proviso.


Note: The uninstall feature does not uninstall technology packs.

Removing a Component from the Topology

This section describes how to remove an installed component from the topology. It contains the following topics:

• Restrictions and Behavior on page 147

• Removing a Component on page 148

You might have a situation where you have modified a topology by both adding new components and removing components (marking them “To Be Removed”). However, the deployer can work in only one mode at a time — installation mode or uninstallation mode. In this situation, first run the deployer in uninstallation mode, then run it again in installation mode.

Important: After the deployer has completed an uninstall, you must open the topology (loaded from the database) in the Topology Editor before performing any additional operations.

Restrictions and Behavior

Before you remove a component, note the following:

• You can remove a host only if no components are configured or installed on it.

• If you remove a component and redeploy the file, the Topology Editor view is not refreshed automatically. Reload the topology file from the database to view the updated topology.

Note: Once components are marked for deletion, the topology must be consumed by the deployer to propagate the required changes and load the updated file in the database. When you open the database version of the topology, the “removed” component will disappear from the topology.

To remove one or more components from the topology where the host system no longer exists or is unreachable on the network, do the following:

Topic Page

Removing a Component from the Topology 147

Uninstalling Entire Netcool/Proviso System 150

Uninstalling the Topology Editor 152

Residual Files 153



1. Open the Topology Editor and remove all components related to the host system

2. Remove the host system from the topology

3. Redeploy the topology, ignoring any messages related to the non-existent or unreachable host.

4. At deployment, the modified topology is saved to the database without the components that were previously installed on the host system.

DataChannel restrictions:

• You can remove the DataChannel Administrative Component only after all the DataChannels have been removed.

• If you are uninstalling a DataChannel component, the component should first be stopped. If you are uninstalling all DataChannel components on a host, then you should remove the DataChannel entries from the crontab.

• If you delete a DataChannel or collector, the working directories (such as the FTE and CME) are not removed; you must delete these directories manually.

DataView restrictions:

Uninstall DataView manually if other products are installed in the same Tivoli Integrated Portal instance. If other products are installed in the same Tivoli Integrated Portal instance, you must use the following procedure to uninstall a DataView component:

1. Run the uninstall command:

<tip_location>/products/tnpm/dataview/bin/uninstall.sh <tip_location> <tip_administrator_username> <tip_administrator_password>

2. Remove the DataView directory:

rm -rf <tip_location>/products/tnpm/dataview

3. In the Topology Editor:

3-a. Remove the DataView component.

3-b. Save the topology.

3-c. Run the deployer for uninstallation.

3-d. Mark the DataView step successful.

3-e. Run the unregister DataView step.

Note: Once this manual un-install is completed, the DataView instance will remain in the topology after the un-install operation completes, this is not usually the case for un-installed components.

Removing a Component

To remove component from the topology:



3. In the Logical view of the Topology Editor, right-click the component you want to delete and select Remove from the pop-up menu.

4. The editor marks the component as “To Be Removed” and removes it from the display.

5. Save the updated topology.



6. Run the deployer (see Starting the Deployer on page 98).

Note: If you forgot to save the modified topology, the deployer will prompt you to save it first.

The deployer can determine that most of the components described in the topology file are already installed, and removes the component that is no longer part of the topology.

7. The deployer displays the installation steps page, which lists the steps required to remove the component. Note that the name of the component to be removed includes the suffix “R” (for “Remove”). For example, if you are deleting a DataChannel, the listed component is DCR.

8. Click Run All to run the steps needed to delete the component.

9. When the installation ends successfully, the deployer uploads the updated topology file into the database. Click Done to close the wizard.

Note: If you remove a component and redeploy the file, the Topology Editor view is not refreshed automatically. Reload the topology file from the database to view the updated topology.

If you have uninstalled DataChannel Components, you will need to bounce CMGR after you have run the deployer, so it will pick up the updated configuration and realize the components have been removed. If you do not bounce CMGR after the deployer runs then you may get errors when you the components are restarted.

To remove a remote DataMart from the topology:

1. Remove remote DataMart from the topology using the Topology Editor and run for uninstallation.

2. Run all steps for component uninstallation, that is, Step 1 to Step 9 as described above.

3. From the remote machine invoke the deployer via the CLI as follows:

./deployer.bin -Daction=uninstall

Note: The CLI option to run the deployer for Uninstallation allows you to provide a parameter pointing to the topology xml. If you choose not to include the parameter, you are prompted to download the topology from the DataBase. If you choose not to download the topology from the DataBase, the deployer will have no topology to work with and will exit.

4. Allow the deployer to download the current topology from the primary server, and run all steps successfully.



Uninstalling Entire Netcool/Proviso System

Note: To uninstall Netcool/Proviso, you must have the CD or the original electronic image. The uninstaller will prompt you for the location of the image.

This section contains the following topics:

• Order of Uninstall on page 150

• Restrictions and Behavior on page 147

• Performing the Uninstall on page 151

• Uninstalling the Topology Editor on page 152

Order of Uninstall

For all deployments, you must use the Topology Editor to uninstall the Netcool/Proviso components in the following order:

1. DataLoad and DataChannel

When uninstalling DataChannel from a host, you must run ./dccmd stop all, disable or delete the dataload cron processes and manually stop (kill -9) any running channel processes (identified by running findvisual). See Chapter E, DataChannels for more information about the findvisual command.

2. DataMart

3. DataChannel Administrative Components and any remaining DataChannel components.

4. DataView Also remove Tivoli Integrated Portal/Tivoli Common Reporting.

5. Netcool/Proviso Database (remove only after all the other components have been removed). The database determines the operating platform of the Netcool/Proviso environment.

Restrictions and Behavior

Before you uninstall Netcool/Proviso, note the following restrictions and behavior:

• If you need to stop the uninstallation before it is complete, you can resume it. The uninstaller relies on the /tmp/ProvisoConsumer directory to store the information needed to resume an uninstall. However, if the ProvisoConsumer directory is removed for any reason, the -Daction=resume command will not work.

Note: When you reboot your server, the contents of /tmp might get cleaned out.

• When you run the uninstaller, it finds the components that are marked as “Installed”, marks them as “To Be Removed”, then deletes them in order. The deployer is able to determine the correct steps to be performed. However, if the component is not in the Installed state (for example, the component was not started), the Topology Editor deletes the component from the topology — not the uninstaller.

• When the uninstallation is complete, some data files still remain on the disk. You must remove these files manually. See Residual Files on page 153 for the list of files that must be deleted manually.



Performing the Uninstall

To remove a Netcool/Proviso installation:

1. You can start the uninstaller from within the Topology Editor or from the command line.

To start the uninstaller from the Topology Editor:

— Select Run > Run Deployer for Uninstallation.

To start the uninstaller from the command line:


1-b. Set and export your DISPLAY variable (see Setting Up a Remote X Window Display on page 9).

1-c. Change directory to the directory that contains the deployer. For example:

# cd /opt/IBM/proviso/deployer

1-d. Enter the following command:

# ./deployer.bin -Daction=uninstall

2. The uninstaller opens, displaying a welcome page. Click Next to continue.


4. A pop-up opens, asking whether you want to download the topology from the database. Click Yes.

5. The database access window prompts for the security credentials. Enter the host name (for example, delphi) and database administrator password (for example, PV), and verify the other values (port number, SID, and user name). Click Next to continue.

6. The uninstaller displays a message stating that the topology download was successful and saved to the file /tmp/ProvisoConsumer/Topology.xml. Click Next to continue.

7. The uninstaller displays several status messages, then displays a message stating that the environment status was successfully downloaded and saved to the file /tmp/ProvisoConsumer/Discovery.xml. Click Next to continue.

8. A pop-up opens, stating that no operations need to be executed on your nodes. The uninstaller closes.

9. Repeat the process on each machine in the deployment.

Note: After the removal of each Component using the Topology Editor, the Topology Editor should reload the topology from the Database.



Uninstalling the Topology Editor

To uninstall the Topology Editor, follow the instructions in this section. Do not simply delete the /opt/IBM directory! Doing so will cause problems when you try to reinstall the Topology Editor. If the /opt/IBM directory is accidentally deleted, perform the workaround documented in Installing the Topology Editor on page 85.

Note: Uninstall Netcool/Proviso before uninstalling the Topology Editor.

To uninstall the Topology Editor:

1. Log in as root.

2. Set and export your DISPLAY variable (see Setting Up a Remote X Window Display on page 9).

3. Change directory to the install_dir/uninstall directory. For example:

# cd /opt/IBM/proviso/uninstall


#./Uninstall_Topology_Editor

5. The Uninstall wizard opens. Click Uninstall to uninstall the Topology Editor.

6. When the script is finished, click Done.



Residual Files

When you uninstall Netcool/Proviso, some of the files remain on the disk and must be removed manually. After you exit from the deployer (in uninstall mode), you must delete these residual files and directories manually.

Perform the following steps:


2. Enter the following commands to stop Oracle:

sqlplus "/ as sysdba"

shutdown abort

exit

lsnrctl stop

3. As root, enter the following commands to delete these files and directories:

rm -fR /tmp/PvInstall

rm -fR /var/tmp/PvInstall

rm -fR /opt/Proviso

rm -fR /opt/proviso

rm -fR $ORACLE_BASE/admin/PV

rm -fR $ORACLE_BASE/admin/skeleton

rm -fR $ORACLE_HOME/dbs/initPV.ora

rm -fR $ORACLE_HOME/dbs/lkPV

rm -fR $ORACLE_HOME/dbs/orapwPV

rm -fR $ORACLE_HOME/lib/libpvmextc.so

rm -fR $ORACLE_HOME/lib/libmultiTask.so

rm -fR $ORACLE_HOME/lib/libcmu.so

rm -fR $ORACLE_HOME/bin/snmptrap

rm -fR $ORACLE_HOME/bin/notifyDBSpace

rm -fR $ORACLE_HOME/bin/notifyConnection

where $ORACLE_BASE is /opt/oracle and $ORACLE_HOME is /opt/oracle/product/10.2.0.

4. Enter the following commands to clear your Oracle mount points and remove any files in those directories:

rm -r /raid_2/oradata/*

rm -r /raid_3/oradata/*

5. Enter the following command to delete the temporary area used by the deployer:

rm -fr /tmp/ProvisoConsumer

6. Delete the installer file using the following command:

rm /var/.com*

7. Delete the startup file, netpvmd.

— For Solaris, use the command:

rm /etc/init.d/netpvmd



— For AIX, use the command:

rm /etc/rc.d/init.d/netpvmd

— For Linux, use the command:

rm /etc/init.d/netpvmd

Following TCR uninstallation:

To prevent any possible system instability caused by residual processes post-uninstall of TCR, run the tcrClean.sh script on all systems where TCR has been uninstalled:

1. On the host where the TCR installation failed, change to the directory containing tcrClean.sh:

cd /opt/IBM/proviso/deployer/proviso/bin/Util/

2. Run tcrClean.sh

3. When prompted, enter the location where TCR was installed.

Note: If you have uninstalled TCR on a remote host, the tcrClean.sh file will need to be sent using ftp to the remote host for execution.


Appendix A: Installing 4.3-U/4.3-V Netcool/Proviso Technology Packs

This appendix discusses how to install 4.3-U/4.3-V technology packs, and consists of the following topics:

Overview

This appendix explains how to install 4.3-U/4.3-V technology packs on your Netcool/Proviso system. Netcool/Proviso supports the following types of technology packs:

• Bundled — Multiple technology packs that are contained in a single, "bundled" jar file.

• Stand-alone — Individual technology packs that are contained in separate jar files, one for each stand-alone technology pack.

Both types of packs are installed with a common installer, with slightly different screens depending on the type of pack you are installing.

In all likelihood, you will be installing a combination of bundled and stand-alone packs. As a result, the installation instructions cover the following user-case scenarios:

• Bundled only

• Stand-alone only

• Bundled and stand-alone

WARNING: Following a new installation of Netcool/Proviso, you MUST install the Starter Kit base packages, which are included in the bundled jar file and checked by default in the Feature Selection screen of the Technology Pack Installer. The Starter Kit base packages contain critical dependencies that all technology packs require. For more information see Installing the Starter Kit on page 167.

Topic Page

Overview 155



Installing Technology Packs 158

Adding UBA Collectors 161

Log Files 165



Before You Begin

Before installing a 4.3-U/4.3-V technology pack, ensure that you have or have done the following:

• Completed the Netcool/Proviso installation.

• Added an SNMP Collector, as described in Add a Collector on page 94. You added an SNMP Collector as part of installing Netcool/Proviso.

Note: For UBA technology packs, you will add a UBA Collector and associate it with a UBA pack as part of this technology pack installation.

• Access to the Netcool/Proviso DataMart server that is running an X Window server.

Note: If there is no graphics card on the DataMart server, the Xvfb virtual frame buffer package that provides X Window services is automatically installed. For more information, see Setting Up a Remote X Window Display on page 9.

• The Oracle TNS name of the server on which you installed Oracle Server with the Netcool/Proviso database configuration. See Specifying a Basename for DB_USER_ROOT on page 23 for more information.

• The correct version of Java. See the Netcool/Proviso Configuration Recommendations for more information.

• Access to the following distributions:

— The product distribution site:


Located on the product distribution site are the ProvisoPackInstaller.jar file, the bundled jar file, and individual stand-alone technology pack jar files.

— (Optional) The Netcool/Proviso CD distribution, which contains the ProvisoPackInstaller.jar file and the jar files for the Starter Kit components.

See Pre-Installation Setup Tasks on page 157 for more information about the Starter Kit.


• Access to the following site to check for interim fixes or fix packs that might apply to your technology pack:

http://www-306.ibm.com/software/sysmgmt/products/support/NetcoolProviso.html

• The Netcool/Proviso documentation and technology pack release notes, which are available at the following site:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/ com.ibm.netcool_proviso.doc/welcome.htm

Always check the release notes before installing an technology pack to determine:

— If the pack is bundled or stand-alone.

— If the pack has any dependencies. For example, some packs require that the MIB-II Technology Pack be installed.

— If the pack is an SNMP or UBA pack. UBA packs must be associated with a UBA collector as part of the pack installation.

— If the pack is upgradeable.




http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_proviso.doc/welcome.htm


Appendix A: Installing 4.3-U/4.3-V Netcool/Proviso Technology


Before starting a 4.3-U/4.3-V technology pack installation, perform the following setup tasks:

1. Determine which technology packs you want to install, then refer to the release notes to determine whether the pack is bundled or stand-alone.

Note: If you are installing multiple packs, plan to download all the jar files and install all the packs at the same time.

2. Open a terminal emulator and log in to the DataMart server as pvuser.

3. Change your working directory to the DataMart home directory (/opt/datamart, by default).

4. Load the shell with the DataMart environment by sourcing the dataMart.env file, as follows:

. /opt/datamart/dataMart.env

Note: After you load the DataMart environment into the shell, the PVMHOME variable is set to the DataMart home directory, /opt/datamart by default. These instructions assume that this variable has been set.

5. Set and export the DISPLAY environment variable (see Setting Up a Remote X Window Display on page 9), so that the Technology Pack Installer GUI will display back on your system.

6. On the DataMart server, create an app-packs directory to hold the technology pack jar files and the ProvisoPackInstaller.jar file, by executing the following command:

mkdir -p $PVMHOME/version/app-packs

7. Download the jar files to the directory you created in Step 6 by following these steps:

7-a. Change your working directory to the app-packs directory that you created in Step 6, using the following command:

cd $PVMHOME/version/app-packs

7-b. Download the following from this URL:


— The ProvisoPackInstaller.jar file

— Any stand-alone jar files

— The bundled jar file

Note: You will need the bundled jar file to install the Starter Kit base packages. See Starter Kit Components on page 167 for descriptions of the base packages.

7-c. After you finish downloading the jar files, verify that the files are in this directory by entering the following command:

ls -l

8. (Optional) Copy the Starter Kit component jar files from the Netcool/Proviso CD by following these steps:

8-a. Mount the CD using a command such as, /mnt/cdrom/path.

8-b. Using the directory information specified in Where to Obtain Starter Kit Components on page 168, copy the ProvisoPackInstaller.jar file, the bundled jar file, and the MIB-II and Cisco Device technology pack stand-alone jar files to the app-packs directory that you created in Step 6.

8-c. After you finish copying the jar files, verify that the files are in this directory by entering the following command:

ls -l




8-d. Unmount the CD.

9. Begin the installation, as explained in Installing Technology Packs on page 158.

Installing Technology Packs

This section explains how to install 4.3-U/4.3-V Netcool/Proviso technology packs.

To install 4.3-U/4.3-V Netcool/Proviso technology packs, follow these steps:

1. Invoke the installer as follows:

From the launchpad (preferred method):

1-a. If it is not already open, open the launchpad (see Starting the Launchpad on page 83).

Note: You can use the terminal emulator you opened in Step 2 on page 157 to start the launchpad. You must, however, su to root. Otherwise, the launchpad will fail to start.

1-b. On the launchpad, click the Install Technology Pack option.

1-c. On the Install Technology Pack screen, enter the following information:

* The DataMart home directory (/opt/datamart, by default)

* The Java run-time home directory, as follows:

— For Solaris 10, specify the default location /opt/IBM/proviso/jvm/jre/bin.

— For other operating systems, specify the location of the supported JRE (for example, /usr/java).

Note: For information on supported JRE versions, see the Netcool/Proviso Configuration Recommendations.

* The Proviso user (for example, pvuser)

1-d. Click the Install Technology Pack link.

1-e. A window prompts you to select the technology pack installation setup directory. Click Browse to locate the directory that you created in Step 6 on page 157:

$PVMHOME/version/app-packs

Important: You cannot install technology packsfrom the Netcool/Proviso CD.

1-f. Click the directory, then click Select to display the specified directory in the window, and then click OK.


Note: The preferred method for installing technology packs is from the launchpad.

1-a. Change your working directory to the technology packs directory that you created in Step 6 on page 157, by entering the following command:


1-b. To invoke the Technology Pack Installer, enter the following command:

java -Xmx256M -jar ProvisoPackInstaller.jar

Note: The -Xmx256M option is required to allocate sufficient memory for the Technology Pack Installer to successfully install multiple bundled and stand-alone technology packs.



2. When the Technology Pack Installer starts up, it displays a Netcool/Proviso Technology Packs screen. Click Next.

3. The Technology Pack Installer displays a Feature Selection screen, which lists in the left panel all the packs you downloaded to the directory created in Step 6 on page 157. All of the packs are automatically selected for installation. Deselect any technology packs in the list that you do not want to install, then click Next.

Note: You must install the Starter Kit base packages (which are included in the bundle) as the first technology pack following a new installation of Netcool/Proviso. See Pre-Installation Setup Tasks on page 157 for more information.

Note: The prerequisites for technology packs item in the Feature Selection screen is always installed. You cannot deselect this item, and the Starter Kit is not included in this item.

4. The Technology Pack Installer displays a warning that tells you the Starter Kit must be the first technology pack to install following a new installation of Netcool/Proviso.

Note: This warning message displays every time you invoke the Technology Pack Installer, whether or not the Starter Kit base packages are installed.

If you have already installed or are about to install the Starter Kit base packages, click Yes to continue. Otherwise, click No, then download the bundle (Step 7 on page 157) and restart the installation.

5. Accept the license agreement by clicking on the accept the terms button, then click Next.

6. The Technology Pack Installer displays the Database Connection screen with the parameter values that you specified when installing and configuring Oracle, the Netcool/Proviso database, and Netcool/Proviso DataMart (see Chapter 2, Installing and Configuring the Prerequisite Software and Chapter 4, Installing Netcool/Proviso in a Distributed Environment).

Re-enter the password of the database user, which is PV by default.

7. Click Next to continue.

8. Technology Pack Installer displays the Tip access paramter values that you specified when installing and configuring Netcool/Proviso DataView as described in Chapter 4, Installing Netcool/Proviso in a Distributed Environment.

Re-enter the password of the TIP user, which is admin by default.

9. Depending on the type of packs you are installing, you will be presented with slightly different screens:

— Stand-alone packs only:

9-a. Click Next to start the installation. As the stand-alone packs are installed, the Technology Pack Installer displays the name of each pack and indicates the progress.

When the installation completes, the Technology Pack Install Complete screen is displayed.

9-b. Click Finish to exit the Technology Pack Installer.

9-c. Go to Step 10 on page 160 to perform post-installation tasks.

— Bundled and stand-alone packs:

— The Technology Pack Installer installs all of the stand-alone technology packs and displays the name of each pack and indicates progress. When the installation of the stand-alone packs completes, the Netcool/Proviso Technology Packs screen appears, and the installation of bundled packs begins.

For more information, see Step 9-a under Bundled packs only.

— Bundled packs only:

9-a. An Update Proviso Database message box displays briefly, followed by a Netcool/Proviso Technology Packs screen. Click Next to continue.



9-b. The Technology Pack Installer displays the Database Details screen with the parameter values that you specified when installing and configuring Oracle, the Netcool/Proviso database, and Netcool/Proviso DataMart as described in previous chapters of this installation guide (see Chapter 2, Installing and Configuring the Prerequisite Software and Chapter 4, Installing Netcool/Proviso in a Distributed Environment).


9-c. Click Next to continue. The Select Packages screen appears.

9-d. On the Select Packages screen, do the following:

— Install the Starter Kit base packages.

Note: The Starter Kit base packages are checked by default if they have not yet been installed.

— Select any additional bundled technology packs that you want to install.

9-e. Click Next to continue.

9-f. Confirm your bundled pack selections on the Install Options Selected screen or click Back to return to the Select Packages screen to remove or add technology packsto the list.

9-g. When you are satisfied with your selections, click Next.

The Technology Pack Installer begins copying files associated with the bundled packs, displaying several status windows.

Note: The Technology Pack Installer might display Replace File windows if it detects existing files, for example, inventory_elements.txt and inventory_subelements.txt. See Backing Up SNMP Inventory Files on page 169 for more information about backing up these files.

9-h. When the Technology Pack Installer finishes copying all the necessary files for the bundled packs and updates the database, it displays the ReadMe File screen. By default, the checkbox for reviewing the README file is selected. The README file tells you to download the pack Release Notes from the information center. Click Finish.

9-i. The Technology Pack Installer displays a series of messages in the terminal emulator as it uploads style sheets and other pack-related files to the database. Upon completion, the Technology Pack Installer displays an Technology Pack Install Complete screen. Click Finish to exit the Technology Pack Installer.

10. After the installation completes, do the following, depending upon the types of packs (SNMP or UBA) you installed:

Note: As explained in the Before You Begin on page 156, refer to the technology pack release notes to determine the pack type (SNMP or UBA).

— UBA packs

* Add a UBA Collector, as follows:

— All UBA packs except CS2K, see Adding a UBA Collector for UBA Packs on page 161

— Nortel CS2000 Technology Pack, see Adding UBA Collectors for the Nortel CS2000 Technology Pack on page 162

* Configure the technology pack, as described in the associated technology pack user’s guide.

— SNMP packs

— Configure the pack, as described in the associated technology pack user’s guide.

Important: Technology packs will not work unless they are configured.



Adding UBA Collectors

UBA technology packs require that you add a UBA Collector as follows:

• For all UBA technology packs except for Nortel CS2000, follow the instructions in Adding a UBA Collector for UBA Packs on page 161.

• For the Nortel CS2000 Technology Pack, follow the instructions in Adding UBA Collectors for the Nortel CS2000 Technology Pack on page 162. This technology pack has some specific requirements beyond those of the typical UBA pack and requires some additional steps.

Adding a UBA Collector for UBA Packs

To add a UBA Collector for a UBA technology pack, follow these steps:

1. Load the pack’s XSD file into an existing topology, as follows:

1-a. If it is not already open, open the Topology Editor (see Starting the Topology Editor on page 86).

1-b. Open a deployed topology (a topology.xml file) (see Opening a Deployed Topology on page 116).

1-c. In the Technology Pack view, right-click the Technology Packs folder and select Load Technology Pack from the pop-up menu.

1-d. The Load the Technology pack configuration metadata window displays. There are two radio buttons: XSD file and JAR file.

1-e. Click the JAR file radio button and select Browse.

Note: The JAR file radio button is selected by default.

1-f. Using the Directory: field, the up and down arrows, and the Folders pane on the configuration metadata window, navigate to the $PVMHOME/version/app-packs directory where the technology pack jar files reside.

1-g. For bundled UBA packs:

— Select the bundled jar file, then click OK. The bundled jar file displays in the Load the technology pack configuration metadata window.

— Click Next. The Topology Editor displays the list of XSD files for the bundled packs you installed.

— Select one or more XSD files to import into the topology. Click Select all to select all of the XSD files.

Note: You can also click on a single XSD file and press the CTRL key to select any number of other XSD files.

— Click Finish. The Topology Editor adds the selected bundled technology pack or packs to the list of technology packs displayed in the Technology Packs view.

1-h. For stand-alone UBA packs:

— Select an technology pack jar file, then click OK. The pack jar file displays in the configuration metadata window.

— Click Finish. The Topology Editor adds the selected stand-alone technology pack to the list of technology packs displayed in the Technology Packs view.

2. After loading a UBA pack’s XSD file, you must add a UBA Collector and associate it with a UBA technology pack, as follows:

2-a. In the Logical view, right-click the DataChannel x folder and select the Add Collector UBA from the menu.



2-b. The Configure Collector window opens. Select the appropriate technology pack (for example, Alcatel 8920 SQM) from the drop-down list of technology packs, then click Next.

2-c. Using the drop-down list of available hosts on the Configure Collector window, select the machine that will host the collector (for example, corinth).

2-d. Accept the default collector number (for example, 2).

2-e. Click Finish.


2-f. Highlight the collector to view its properties. The Topology Editor displays both the UBA collector core parameters and the UBA technology pack-specific parameters. The core parameters are configured with all UBA technology packs. Review the values for the parameters to make sure they are valid. For information about the core parameters, see the Netcool/Proviso Properties Reference. For information about the pack-specific parameters, see the Topology Editor Help.

The UBA collector is associated with two DataChannel components:

— Complex Metric Engine (CME) x.x — Performs calculations on the collected data.

— File Transfer Engine (FTE) x.x — Transfers files from the collector’s output directories and places them in the input directory of the CME.

Note that the Topology Editor includes the channel and collector numbers in the component names. For example, Data Channel 1 could have Collector UBA 1.1, with Complex Metric Engine 1.1 and File Transfer Engine 1.1.The FTE writes data to the file /var/adm/wtmpx on each system that hosts a collector. As part of routine maintenance, check the size of this file to prevent it from growing too large.


Note: To add additional UBA collectors for a UBA technology pack, repeat Step 2-a through Step 2-f.

2-g. Redeploy the updated topology (see Starting the Deployer on page 98).

3. Configure the UBA technology packs you have installed, by referring to the configuration appendix of the appropriate technology pack user’s guide.


Adding UBA Collectors for the Nortel CS2000 Technology Pack

The Nortel CS2000 Technology Pack requires you to add one UBA collector for each of the following devices running in the network:

• Passport Packet Voice Gateway (PVG) — The UBA executing on this subchannel retrieves Bulk input files generated by the PVG device.

• Universal Signaling Point (USP) — The UBA executing on this subchannel retrieves Bulk input files generated by the USP device.

• Nortel CS2K Performance — The UBA executing on this subchannel retrieves Bulk input files generated by the Nortel CS2K Performance device.

• Nortel Integrated Element Management System (IEMS) — The UBA executing on this subchannel retrieves Bulk input files generated by the Nortel CS2K IEMS system.



For example, if there are two PVG devices you would add two UBA collectors, one for each PVG device operating in the network. If there are two USP devices you would add two UBA collectors, one for each USP device operating in the network, and so forth.

The Nortel CS2000 Technology Pack also requires you to add multiple UBA collectors for the following call records:

• Nortel Succession Communication Server 2000 (CS2K) CDR call records — The UBAs executing on this subchannel retrieve Bulk input files generated by the cs2kcdr.pl pre-processor.

For example, if you expect the UBA to process a large amount of CS2K CDR call records you would add multiple (for example, three) UBA collectors, each with a unique collector number. Each of these UBA collectors is then mapped to a Master UBA. The Topology Editor displays the appropriate windows for you to add multiple UBA collectors and add the Master UBA.

The Topology Editor simplifies the task of adding UBA collectors for each of these devices and the CS2K CDR call records by associating each with a "technology pack" that displays in the Technology Packs view after you load the XSD file. Table 10 maps each device to its associated "technology pack".

Table 10: Nortel CS2000 Devices Mapped to Technology Packs

To add a UBA Collector for the Nortel CS2K - PVG, Nortel CS2K - USP, Nortel CS2K - CS2K Performance, and Nortel CS2K - IEMS packs listed in Table 10, follow these steps:

1. Load the Nortel CS2000 pack’s XSD file into an existing topology, as described in Step 1-a on page 161 through Step 1-f on page 161 and Step 1-h on page 161. After you load the XSD file for the Nortel CS2000 Technology Pack, the “technology packs” listed in Table 8 display in the Technology Packs view.

In effect, the Nortel CS2000 Technology Pack is organized into five “technology packs”, one for each of the supported devices. You will add a UBA Collector for each of these four “technology packs”.

2. To add a UBA Collector and associate it with the Nortel CS2K - PVG technology pack:


2-b. The Configure Collector window opens. Select the Nortel CS2K - PVG technology pack from the drop-down list of technology packs, then click Next.



2-e. Click Finish.

The Topology Editor displays the new collector under the DataChannel x folder in the Logical view. See Step 2-f on page 163 for information related to the CME and FTE DataChannel components.

2-f. Highlight the collector to view its properties. The Topology Editor displays both the UBA collector core parameters and the UBA technology pack-specific parameters. The core parameters are

CS2000 Device/System/Calls Records Pack Displayed in Technology Packs view

PVG Nortel CS2K - PVG

Nortel CS2K CDR Nortel CS2K - CDR

USP Nortel CS2K - USP

Nortel CS2K Performance Nortel CS2K - CS2K Performance

IEMS Nortel CS2K - IEMS



configured with all UBA technology packs. Review the values for the parameters to make sure they are valid. For information about the core parameters, see the Netcool/Proviso Properties Reference. For information about the pack-specific parameters, see the Topology Editor Help.

3. To add a UBA Collector for each of the Nortel CS2K - USP, Nortel CS2K - CS2K Performance, and Nortel CS2K - IEMS technology packs, repeat Step 2-a on page 163 through Step 2-f on page 163 making sure to select the appropriate pack from the drop-down list of technology packs displayed in the Configure Collector window.

Note: To add additional UBA collectors for any of these UBA technology packs, repeat Step 2-a through Step 2-f.

To add multiple UBA Collectors and specify a Master ID for the Nortel CS2K - CDR pack listed in Table 10, follow these steps:

1. In the Logical view, right-click the DataChannel x folder and select the Add Collector UBA from the menu.

2. The Configure Collector window opens. Select the Nortel CS2K - CDR technology pack from the drop-down list of technology packs, then click Next.

3. The Configure Collector window requests you enter the number of UBA collectors. The number you enter here depends on the volume of records the UBA collectors need to process. If there are large volumes of records, consider adding three or four UBA collectors. Specify the value in the Number of UBA Collectors field.

4. Click Next.

5. The Configure Collector window requests that you enter the basic settings for the master UBA of this multiple in-line inventory technology pack.

Using the drop-down list of available hosts on the Configure Collector window, select the machine that will host the collector (for example, corinth) of the master UBA. This, by default, will be designated UBA instance 1.

6. Click Finish.

7. The Configure Collector window requests that you enter the basic settings for the number of UBA collectors you specified in Step 3 as follows:

— UBA instance 2 — Using the drop-down list of available hosts on the Configure Collector window, select the machine that will host the collector (for example, corinth) of UBA instance 2 for this Nortel CS2K - CDR pack. Accept the default collector number (for example, 5). Click Next.


— UBA instance x — Using the drop-down list of available hosts on the Configure Collector window, select the machine that will host the collector (for example, corinth) of UBA instance x for this Nortel CS2K - CDR pack. Accept the default collector number (for example, x). Click Next.

8. The Topology Editor displays the new collectors under the DataChannel x folder in the Logical view. See Step 2-f on page 163 for information related to the CME and FTE DataChannel components.

8-a. Highlight the collectors to view their properties. The Topology Editor displays both the UBA collector core parameters and the UBA technology pack-specific parameters. The core parameters are configured with all UBA technology packs. Review the values for the parameters to make sure they are valid. The following properties are of particular interest:

* COLLECTOR_ALIAS — This is the collector number specified for the Master UBA. You should not modify this parameter.

* INPUT_ID — Specifies an ID to be mapped to one of the output streams associated with the cs2kcdr.pl pre-processor. The cs2kcdr.pl pre-processor can be configured to output files in multiple streams every run interval.



Note: See the Netcool/Proviso Nortel CS2K Carrier VoIP Application Pack User’s Guide for information on configuring the cs2kcdr.pl pre-processor. You configure the cs2kcdr.pl pre-processor by editing variables defined in the cs2kcdr-config.pl configuration file. For example, you specify the number of output streams the pre-processor should create by editing the $numberOfOutputs variable. The number specified for this variable should match the number of UBA Collectors that you add for the Nortel CS2K - CDR pack. Thus, if you added five UBA Collectors, you must specify the value 5 for $numberOfOutputs.

For example, a cs2kcdr.pl pre-processor that is configured for five output streams will write five different output files, as in the following example:

example-file.0.csv

example-file.1.csv

example-file.2.csv

example-file.3.csv

example-file.4.csv

Thus, each of the UBA Collectors you added for the Nortel CS2K - CDR pack must be associated with an output stream. Using the five output streams as an example, you might specify the INPUT_ID parameters for the UBA Collectors as follows:

— UBA instance 1 — Specify the value 0 (zero) so that UBA instance 1 processes example-file.0.csv output files.

— UBA instance 2 — Specify the value 1 so that UBA instance 2 processes example-file.1.csv output files.




9. Redeploy the updated topology (see Starting the Deployer on page 98).

10. Configure the Nortel CS2000 Technology Pack, as explained in the user’s guide.


Log Files

The Technology Pack Installer writes a log file to the /usr/tmp directory. This log file contains a detailed history of the tasks the Technology Pack Installer performs as it installs technology packs. You can check this log file to help solve any issues that might occur during technology pack installation. For example, the log file might contain a message that indicates that the Technology Pack Installer GUI could not display back on your system because the DISPLAY environment variable was not set. Log file names have the format APInstallnumber.log. For example:

APInstall1213136138386.log




Appendix B: Installing the Starter Kit with 4.3-U/4.3-V Technology Packs

This appendix discusses how to install the Starter Kit, and consists of the following topics:

Installing the Starter Kit

The Starter Kit is available as part of the Netcool/Proviso distribution. The Starter Kit contains a number of base packages required by all technology packs. In addition, the Starter Kit includes two SNMP technology packs: MIB-II and Cisco Device. You should understand the following topics related to the Starter Kit:

• Starter Kit Components

• Where to Obtain Starter Kit Components

• Backing Up SNMP Inventory Files

Important: Installation of the Starter Kit is only required as part of a 4.3-U/4.3-V technology pack installation.

Starter Kit Components

The Starter Kit consists of the following discrete components:

• Starter Kit base packages — The following Starter Kit base packages are contained in the bundled jar file, and are checked by default in the Feature Selection screen of the Technology Pack Installer:

— MIBs, StyleSheets, and config files release_number — Includes MIBs, stylesheets, and configuration files. Also includes the localization utility (APLocalizeInstall.jar) that the Technology Pack Installer copies to the DataMart config directory (/opt/datamart/conf, by default).

— Bundle Preq release_number — Includes device sub-element properties, Discovery formulas, and default Calendar definitions.

Note: Prior to the 4.3-X Technology Pack release the Bundle Preq component was called AP Base DB Content.

— Generic Metrics release_number — Includes a global set of generic metrics.

Topic Page

Installing the Starter Kit 167

Starter Kit Components 167

Where to Obtain Starter Kit Components 168

Backing Up SNMP Inventory Files 169



— Standard Thresholds release_number — Includes the defined thresholds.

— DV Navigator Reporter Set Wizard Pack release_number — Includes the Reporter Set Wizard tool that enables pack developers to define a template that generates a set of reporters.

WARNING: Following a new installation of Netcool/Proviso, you MUST install the Starter Kit base packages, which are included in the bundled jar file and checked by default in the Feature Selection screen of the Technology Pack Installer. The Starter Kit base packages contain critical dependencies that all technology packs require. You MUST also install the Stand-alone Technology Packs, see below.

Stand-alone Technology Packs that are part of the Starter Kit

The following components are contained in their own stand-alone jar files.

• Frame Relay Technology Pack

• MIB-II Technology Pack

• Cisco Device Technology Pack

Installing these components is optional, unless required by other technology packs. See the technology pack release notes for more information.

Where to Obtain Starter Kit Components

You obtain the Starter Kit components from the following distributions:

• The product distribution site:


• The Netcool/Proviso CD

You download from the product distribution site or copy from the CD the following jar files:

• ProvisoPackInstaller.jar file — Contains the Technology Pack Installer, which installs all of the components that make up the Starter Kit, as well as all other bundled and stand-alone packs.

• Bundled jar file — Contains the Starter Kit base packages and bundled packs.

• Stand-alone jar files for the MIB-II and Cisco Device technology packs.

The previously listed jar files are located in the following directories on the CD:

Proviso/AP

Proviso/AP/jar

The procedure for downloading the bundled jar and stand-alone jar files and installing the Starter Kit base packages are described in Step 7 on page 159 and Step 9-d on page 162, respectively.



Appendix B: Installing the Starter Kit with 4.3-U/4.3-V Technology

Backing Up SNMP Inventory Files

During the installation of a technology pack, many files are overwritten by design — for example, Netcool/Proviso configuration files, reports files, MIBs, and stylesheets. You must manually back up any such files that you have customized, or the changes will be lost.

At a minimum, the following SNMP inventory files should be backed up prior to the installation of any bundled technology pack:

• inventory_elements.txt

• inventory_subelements.txt

To create backup copies, do the following:

Note: Do not perform the following backup steps if you are installing an SNMP standalone technology pack. For information on managing the inventory control files for an SNMP technology pack, see the configuration appendix of the technology pack user's guide.

1. Change your working directory to the DataMart conf directory (/opt/datamart/conf, by default) using the following command:

cd $PVMHOME/conf

2. Make backup copies of the inventory control files by entering the following commands:

cp inventory_elements.txt inventory_elements.txt.ORIG

cp inventory_subelements.txt inventory_subelements.txt.ORIG




Appendix C: Installing 4.3-W and higher Netcool/Proviso Technology Packs

This chapter describes how to install 4.3-W and higher technology packs, and consists of the following topics:

Overview

This appendix explains how to install 4.3-W and higher technology packs on your Netcool/Proviso system. Netcool/Proviso supports the following types of technology packs:

• Bundled — Multiple technology packs that are contained in a single, “bundled” jar file.

• Stand-alone — Individual technology packs that are contained in separate jar files, one for each stand-alone technology pack.

Both types of packs are installed with a common installer, with slightly different screens depending on the type of pack you are installing.

In all likelihood, you will be installing a combination of bundled and stand-alone packs. As a result, the installation instructions cover the following user-case scenarios:

• Bundled only

• Stand-alone only

• Bundled and stand-alone

Topic Page

Overview 171



Backing Up Inventory Files 173

Preparing to Install Technology Pack Patches 173

Preparing the Pack Installation Directory 174

Installing Technology Packs 174

Adding UBA Collectors 178

Log Files 183



Before You Begin

Before installing a 4.3-W or higher technology pack, ensure that you have or have done the following:

• Completed the Netcool/Proviso installation.

• Added an SNMP Collector, as described in Add a Collector on page 94. You added an SNMP Collector as part of installing Netcool/Proviso.

Note: For UBA technology packs you will add a UBA Collector and associate it with a UBA pack as part of this technology pack installation.

• Access to the Netcool/Proviso DataMart server that is running an X Window server.

Note: If there is no graphics card on the DataMart server, the Xvfb virtual frame buffer package that provides X Window services is automatically installed. For more information, see Setting Up a Remote X Window Display on page 9.

• The Oracle TNS name of the server on which you installed Oracle server with the Netcool/Proviso database configuration. See Specifying a Basename for DB_USER_ROOT on page 23 for more information.

• The correct version of Java. See the Netcool/Proviso Configuration Recommendations for more information.

• Access to the technology pack installation files on one of the following:

— Product distribution site:


Located on the product distribution site are the ProvisoPackInstaller.jar file and technology pack jar files.

— Netcool/Proviso CD distribution, which contains the ProvisoPackInstaller.jar file and technology pack jar files.


• Access to the following site to check for interim fixes or fix packs that might apply to your technology pack:


• The Netcool/Proviso documentation and technology pack release notes, which are available at the following site:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/ com.ibm.netcool_proviso.doc/welcome.htm

Always check the release notes before installing a technology pack to determine:

— If the pack is bundled or stand-alone.

— If the pack has any dependencies. For example, some packs require that the MIB-II Technology Pack be installed.

— If the pack is an SNMP or UBA pack. UBA packs must be associated with a UBA collector as part of the pack installation.

— If the pack is upgradeable.






Appendix C: Installing 4.3-W and higher Netcool/Proviso


Before starting a 4.3-W or higher technology pack installation, perform the following setup tasks:

1. Determine which technology packs you want to install, then refer to the release notes to determine whether the pack is bundled or stand-alone.

2. Open a terminal emulator and log in to the DataMart server as pvuser.

3. Change your working directory to the DataMart home directory (/opt/datamart, by default).

4. Load the shell with the DataMart environment by sourcing the dataMart.env file, as follows:

. /opt/datamart/dataMart.env

Note: After you load the DataMart environment into the shell, the PVMHOME variable is set to the DataMart home directory, /opt/datamart by default. These instructions assume that this variable has been set.

5. Set and export the DISPLAY environment variable (see Setting Up a Remote X Window Display on page 9), so that the Technology Pack Installer GUI will display back on your system.

Backing Up Inventory Files

Before you install a new technology pack from the Technology Pack Bundle, or from a stand-alone pack, you must 1) create backup copies of the inventory control files prior to the installation of the technology pack, and then 2) perform a diff on the files.

To create backup copies:

1. Change your working directory to the conf directory using the following command:

cd $PVMHOME/conf

2. Make backup copies of the inventory control files by entering the following commands:

cp inventory_elements.txt inventory_elements.txt.ORIG

cp inventory_subelements.txt inventory_subelements.txt.ORIG

To perform a diff on the files:

1. After the installation of the technology pack is complete, you must next follow the configuration steps in the Technology Pack’s User Guide.

2. After the configuration of the technology pack is complete, you must then perform a diff between the inventory control files and the .ORIG versions of the files, and merge back any differences.

3. This complete the backing up process.

Preparing to Install Technology Pack Patches

To prepare to install technology pack patches:

1. For the latest patch information for Netcool/Proviso, see Appendix K, Installing an Interim Fix on page 239.

2. For the latest patch information for Technology Packs, download the release notes of the required technology pack release from the infocenter.



2-a. Review the appendix that deals with interim fixes and fix packs in the release notes and note the patches required, if any, for each technology pack that you intend to install.

2-b. Download the required patches, if any, for each technology pack that you intend to install.

2-c. Install the required patches, if any, for each technology pack that you intend to install.

Preparing the Pack Installation Directory

You can obtain technology pack installation files from the IBM product distribution website, or from the Netcool/Proviso technology pack CD.

If you are installing the packs using an instance of the Netcool/Proviso launchpad located on the local file system, you can install directly from the CD. Otherwise, you must create a temporary directory and copy the technology pack files to the local system before you begin the installation.

You cannot run the launchpad from the Netcool/Proviso DVD and then install technology packs directly from the CD distribution.

Note: If you are using a local instance of the launchpad and you want to install directly from the technology pack CD, you can skip this step and proceed to Installing Technology Packs on page 174.

To prepare the pack installation directory:

1. On the system where DataMart is located, use the mkdir command to create an app-packs directory to hold the technology pack jar files and the ProvisoPackInstaller.jar file, for example:

mkdir -p $PVMHOME/version/app-packs

2. If you want to use technology packs from the IBM product distribution website, download the jar files by following these steps:

2-a. Use the cd command to change your working directory to the app-packs directory that you created in Step 1, for example:


2-b. Download the following from this URL:


— ProvisoPackInstaller.jar file

— Jar files for technology packs you want to install (the bundled jar file for bundled packs and/or individual jar files for standalone packs)

3. If you want to use technology packs from the Netcool/Proviso technology pack CD, browse to the /Proviso/AP/jar location on the CD and copy the following files to the temporary directory:

— ProvisoPackInstaller.jar file

— Jar files for technology packs you want to install (the bundled jar file for bundled packs and/or individual jar files for standalone packs)

4. Begin the installation, as explained in Installing Technology Packs on page 174.

Installing Technology Packs

This section explains how to install 4.3-W and higher Netcool/Proviso technology packs.

You must first check the version of java running on your system by entering the following command:




java -version

You may need to upgrade your version of java depending on the Technology Pack release, see below.

For 4.3-W and 4.3-X Technology Packs the launchpad requires you to enter the path to supported Java runtime binaries. Only versions 1.4.2_b(17+) and 1.5.0_b(14+) are supported. The Netcool/Proviso topology editor provides a supported version of the Java binaries.

For 4.3-Y and 4.3-Z Technology Packs the launchpad requires you to enter the path to supported Java runtime binaries. Only version 1.5.0_b(14+) is supported. The Netcool/Proviso topology editor provides a supported version of the Java binaries. Using Java version 1.4 will result in an error detailing that it is not possible to proceed with the install.

To install a 4.3-W or higher Netcool/Proviso technology packs, follow these steps:

1. Invoke the installer as follows:

From the launchpad (preferred method):

1-a. If it is not already open, open the launchpad (see Starting the Launchpad on page 83).

Note: You can use the terminal emulator you opened in Step 2 on page 173 to start the launchpad. You must, however, su to root. Otherwise, the launchpad will fail to start.

1-b. On the launchpad, click the Install Technology Pack option.

1-c. On the Install Technology Pack screen, enter the following information:

* The DataMart home directory (/opt/datamart, by default)

* The Java run-time environment home directory (for example, /opt/IBM/proviso/topologyEditor/jre/bin).

* The Proviso user (for example, pvuser)

1-d. Click the Install Technology Pack link.

1-e. A window prompts you to select the technology pack installation setup directory. Click Browse to locate the temporary directory that you created in Step 1 on page 174, or the directory on the Netcool/Proviso CD where the pack jar files are located (by default, /Proviso/AP/jar).

1-f. Click the directory, then click Select to display the specified directory in the window, and then click OK.


Note: The preferred method for installing technology packs is from the launchpad.

1-a. Use the cd command to change your working directory to the temporary directory that you created in Step 1 on page 174, or to the directory on the Netcool/Proviso CD where the pack jar files are located.

1-b. To invoke the Technology Pack Installer, enter the following command:


Note: The -Xmx256M option is required to allocate sufficient memory for the Technology Pack Installer to successfully install multiple bundled and stand-alone technology packs.

WARNING: The following command is only applicable for 4.3-X and higher Technology Packs.



Important: To invoke the Technology Pack Installer for Alcatel Lucent 5620 SAM technology pack, enter the following command:


2. When the Technology Pack Installer starts up, it displays a Netcool/Proviso Technology Packs Welcome screen. Click Next.

3. Accept the license agreement by clicking on the accept the terms button, then click Next.

4. The Technology Pack Installer displays the Database Access Parameters screen with the parameter values that you specified when installing and configuring Oracle, the Netcool/Proviso database, and Netcool/Proviso DataMart (see Chapter 2, Installing and Configuring the Prerequisite Software and Chapter 4, Installing Netcool/Proviso in a Distributed Environment).


5. Click Next to continue.

6. The Technology Pack Installer displays the SilverStream access parameter values that you specified when installing and configuring Netcool/Proviso DataView as described in Chapter 4, Installing Netcool/Proviso in a Distributed Environment.

7. Re-enter the password of the SilverStream user, which is admin by default.

8. The Technology Pack Installer displays a Feature Selection screen, which lists in the left panel all the packs you downloaded to the directory created in Step 1 on page 174. All of the packs are automatically selected for installation. Deselect any technology packs in the list that you do not want to install, then click Next.

Note: The prerequisites for technology packs item in the Feature Selection screen is always installed.

9. Depending on the type of packs you are installing, you will be presented with slightly different screens:

Stand-alone packs only:

9-a. Click Next to start the installation. As the stand-alone packs are installed, the Technology Pack Installer displays the name of each pack and indicates the progress.

When the installation completes, the Technology Pack Install Complete screen is displayed.

9-b. Click Finish to exit the Technology Pack Installer.

9-c. Go to Step 10 on page 177 to perform post-installation tasks.

Bundled and stand-alone packs:

— The Technology Pack Installer installs all of the stand-alone technology packs and displays the name of each pack and indicates progress. When the installation of the stand-alone packs completes, the Netcool/Proviso Technology Packs screen appears, and the installation of bundled packs begins.

For more information, see Step 9-a below.

Bundled packs:

WARNING: For 4.3-Y and 4.3-Z Technology Packs Only. Before installing Bundled packs the Installer will look for an environment variable named PROVISO_JAVA. This will point to the directory that contains the approved 1.5 IBM jvm. If PROVISO_JAVA is not set, the installer will attempt to use the default system java and will cause an issue when installing Bundled packs.

9-a. An Update Proviso Database message box displays briefly, followed by a Netcool/Proviso Technology Packs screen. Click Next to continue.



9-b. The Technology Pack Installer displays the Database Details screen with the parameter values that you specified when installing and configuring Oracle, the Netcool/Proviso database, and Netcool/Proviso DataMart as described in previous chapters of this installation guide (see Chapter 2, Installing and Configuring the Prerequisite Software and Chapter 4, Installing Netcool/Proviso in a Distributed Environment).


9-c. Click Next to continue. The Select Packages screen appears.

9-d. On the Select Packages screen, do the following:

— If not previously installed, select the Pack Bundle Prerequisites.

— Select individual bundled technology packs that you want to install.

9-e. Click Next to continue.

9-f. Confirm your bundled pack selections on the Install Options Selected screen or click Back to return to the Select Packages screen to remove or add technology packs to the list.

9-g. When you are satisfied with your selections, click Next.

The Technology Pack Installer begins copying files associated with the bundled packs, displaying several status windows.

Note: The Technology Pack Installer might display Replace File windows if it detects existing files, for example, inventory_elements.txt and inventory_subelements.txt. See Backing Up Inventory Files on page 173 for more information about backing up these files.

9-h. When the Technology Pack Installer finishes copying all the necessary files for the bundled packs and updates the database, it displays the ReadMe File screen. By default, the checkbox for reviewing the README file is selected. The README file tells you to download the pack Release Notes from the information center. Click Finish.

9-i. The Technology Pack Installer displays a series of messages in the terminal emulator as it uploads style sheets and other pack-related files to the database. Upon completion, the Technology Pack Installer displays a Technology Pack Install Complete screen. Click Finish to exit the Technology Pack Installer.

10. After the installation completes, do the following, depending upon the types of packs (SNMP or UBA) you installed:

Note: As explained in the Before You Begin on page 172, refer to the technology pack release notes to determine the pack type (SNMP or UBA).

Important: A technology pack will not work until it is configured. Once configured data will be collected and reports will be populated.

— SNMP packs:


* After the technology pack is configured, this completes the installation of the SNMP technology pack.

— UBA packs:

* Add a UBA Collector, as follows:

— All UBA packs except the Nortel CS2000 Technology Pack, see Adding a UBA Collector for UBA Packs on page 178

— The Nortel CS2000 Technology Pack, see Adding UBA Collectors for the Nortel CS2000 Technology Pack on page 179


* After the technology pack is configured, this completes the installation of the UBA technology pack.



Adding UBA Collectors

UBA technology packs require that you add a UBA Collector as follows:

• For all UBA technology packs except for the Nortel CS2000 Technology Pack, follow the instructions in Adding a UBA Collector for UBA Packs on page 178.

• For the Nortel CS2000 Technology Pack, follow the instructions in Adding UBA Collectors for the Nortel CS2000 Technology Pack on page 179. This technology pack has some specific requirements beyond those of the typical UBA pack and requires some additional steps.

Adding a UBA Collector for UBA Packs

To add a UBA Collector for a UBA technology pack, follow these steps:

1. Load the pack’s XSD file into an existing topology, as follows:

1-a. If it is not already open, open the Topology Editor (see Starting the Topology Editor on page 86).

1-b. Open a deployed topology (a topology.xml file) (see Opening an Existing Topology File on page 97).

1-c. In the Technology Pack view, right-click the Technology Packs folder and select Load Technology Pack from the pop-up menu.

1-d. The Load the technology pack configuration metadata window displays. There are two radio buttons: XSD file and JAR file.

1-e. Click the JAR file radio button and select Browse.

Note: The JAR file radio button is selected by default.

1-f. Using the Directory: field, the up and down arrows, and the Folders pane on the configuration metadata window, navigate to the directory where the technology pack jar files reside (for example, $PVMHOME/version/app-packs or a directory on the Netcool/Proviso CD).

1-g. For bundled UBA packs:

— Select the bundled jar file, then click OK. The bundled jar file displays in the Load the technology pack configuration metadata window.

— Click Next. The Topology Editor displays the list of XSD files for the bundled packs you installed.

— Select one or more XSD files to import into the topology. Click Select all to select all of the XSD files.

Note: You can also click on a single XSD file and press the CTRL key to select any number of other XSD files.

— Click Finish. The Topology Editor adds the selected bundled technology pack or packs to the list of technology packs displayed in the Technology Packs view.

1-h. For stand-alone UBA packs:

— Select a technology pack jar file, then click OK. The pack jar file displays in the configuration metadata window.

— Click Finish. The Topology Editor adds the selected stand-alone technology pack to the list of technology packs displayed in the Technology Packs view.

2. After loading a UBA pack’s XSD file, you must add a UBA Collector and associate it with a UBA technology pack, as follows:




2-b. The Configure Collector window opens. Select the appropriate technology pack (for example, Alcatel 8920 SQM) from the drop-down list of technology packs, then click Next.



2-e. Click Finish.



The UBA collector is associated with two DataChannel components:

— Complex Metric Engine (CME) x.x — Performs calculations on the collected data.

— File Transfer Engine (FTE) x.x — Transfers files from the collector’s output directories and places them in the input directory of the CME.

Note that the Topology Editor includes the channel and collector numbers in the component names. For example, Data Channel 1 could have Collector UBA 1.1, with Complex Metric Engine 1.1 and File Transfer Engine 1.1.The FTE writes data to the file /var/adm/wtmpx on each system that hosts a collector. As part of routine maintenance, check the size of this file to prevent it from growing too large.


Note: To add additional UBA collectors for a UBA technology pack, repeat Step 2-a through Step 2-f.

2-g. Redeploy the updated topology (see Starting the Deployer on page 98).

3. Configure the UBA technology packs you have installed, by referring to the configuration appendix of the appropriate technology pack user’s guide.


Adding UBA Collectors for the Nortel CS2000 Technology Pack

The Nortel CS2000 Technology Pack requires you to add one UBA collector for each of the following devices running in the network:

• Passport Packet Voice Gateway (PVG) — The UBA executing on this subchannel retrieves Bulk input files generated by the PVG device.

• Universal Signaling Point (USP) — The UBA executing on this subchannel retrieves Bulk input files generated by the USP device.

• Nortel CS2K Performance — The UBA executing on this subchannel retrieves Bulk input files generated by the Nortel CS2K Performance device.

• Nortel Integrated Element Management System (IEMS) — The UBA executing on this subchannel retrieves Bulk input files generated by the Nortel CS2K IEMS system.



• Nortel Server Session Lines (SSL) — The UBA executing on this subchannel retrieves Bulk input files generated by a Nortel CS2K SSL device.

WARNING: The following two UBA Collectors, SST and CPR, are only applicable for 4.3-X and higher Technology Packs.

• Nortel Session Server Trunk (SST) — The UBA executing on this subchannel retrieves Bulk input files generated by a Nortel CS2K SST device.

• Nortel Common Performance Reporting (CPR) — CPR is a log format. The bulk input files generated by the PVG device are manipulated by the IEMS system and converted into CPR format. Nortel recommends that the CPR log format be manipulated via the IEMS system, instead of directly from the MDM. So this is facilitated by the CPR Adaptor.

* The CPR Adaptor is also somewhat of a generic adaptor as it can be used to support SST data in CPR format. One instance of the CPR Adaptor can simultaneously support both CPR and SST formats.

For example, if there are two PVG devices you would add two UBA collectors, one for each PVG device operating in the network. If there are two USP devices you would add two UBA collectors, one for each USP device operating in the network, and so forth.

The Nortel CS2000 Technology Pack also requires you to add multiple UBA collectors for the following call records:

• Nortel Succession Communication Server 2000 (CS2K) CDR call records — The UBAs executing on this subchannel retrieve Bulk input files generated by the cs2kcdr.pl pre-processor.

For example, if you expect the UBA to process a large amount of CS2K CDR call records you would add multiple (for example, three) UBA collectors, each with a unique collector number. Each of these UBA collectors is then mapped to a Master UBA. The Topology Editor displays the appropriate windows for you to add multiple UBA collectors and add the Master UBA.

The Topology Editor simplifies the task of adding UBA collectors for each of these devices and the CS2K CDR call records by associating each with a “technology pack” that displays in the Technology Packs view after you load the XSD file. Table 11 maps each device to its associated “technology pack”.

Table 11: Nortel CS2000 Devices Mapped to Technology Packs

To add a UBA Collector for one of the packs listed in Table 11, follow these steps:

CS2000 Device/System/Calls Records Pack Displayed in Technology Packs view

PVG Nortel CS2K - PVG

Nortel CS2K CDR Nortel CS2K - CDR

USP Nortel CS2K - USP

Nortel CS2K Performance Nortel CS2K - CS2K Performance

IEMS Nortel CS2K - IEMS

SSL Nortel CS2K - SSL

SST Nortel CS2K - SST

CPR Nortel CS2K - CPR



1. Load the Nortel CS2000 pack’s XSD file into an existing topology, as described in Step 1-a on page 178 through Step 1-f on page 178 and Step 1-h on page 178. After you load the XSD file for the Nortel CS2000 Technology Pack, the “technology packs” listed in Table 8 display in the Technology Packs view.

In effect, the Nortel CS2000 Technology Pack is organized into five “technology packs”, one for each of the supported devices. You will add a UBA Collector for each of these four “technology packs”.

2. To add a UBA Collector and associate it with the Nortel CS2K - PVG technology pack:


2-b. The Configure Collector window opens. Select the Nortel CS2K - PVG technology pack from the drop-down list of technology packs, then click Next.



2-e. Click Finish.

The Topology Editor displays the new collector under the DataChannel x folder in the Logical view. See Step 2-f on page 181 for information related to the CME and FTE DataChannel components.


3. To add a UBA Collector for each of the Nortel CS2K - USP, Nortel CS2K - CS2K Performance, Nortel CS2K - SSL and Nortel CS2K - IEMS technology packs, repeat Step 2-a on page 181 through Step 2-f on page 181 making sure to select the appropriate pack from the drop-down list of technology packs displayed in the Configure Collector window.

Note: To add additional UBA collectors for any of these UBA technology packs, repeat Step 2-a through Step 2-f.

To add multiple UBA Collectors and specify a Master ID for the Nortel CS2K - CDR pack listed in Table 11, follow these steps:

1. In the Logical view, right-click the DataChannel x folder and select the Add Collector UBA from the menu.

2. The Configure Collector window opens. Select the Nortel CS2K - CDR technology pack from the drop-down list of technology packs, then click Next.

3. The Configure Collector window requests that you enter the number of UBA collectors. The number you enter here depends on the volume of records the UBA collectors need to process. If there are large volumes of records, consider adding three or four UBA collectors. Specify the value in the Number of UBA Collectors field.

4. Click Next.

5. The Configure Collector window requests that you enter the basic settings for the number of UBA collectors you specified in Step 3 as follows:





— UBA instance x — Using the drop-down list of available hosts on the Configure Collector window, select the machine that will host the collector (for example, corinth) of UBA instance x for this Nortel CS2K - CDR pack. Accept the default collector number (for example, x). Click Next.

6. The Configure Collector window requests that you enter the basic settings for the master UBA of this multiple in-line inventory technology pack.

6-a. Using the drop-down list of available hosts on the Configure Collector window, select the machine that will host the collector (for example, corinth) of the master UBA.

6-b. Accept the default collector number (for example, 21).

WARNING: If you do not accept the default and specify a collector number, make sure this number has not been assigned to an existing collector.

6-c. Click Finish.

The Topology Editor displays the new collectors under the DataChannel x folder in the Logical view. See Step 2-f on page 181 for information related to the CME and FTE DataChannel components.

6-d. Highlight the collectors to view their properties. The Topology Editor displays both the UBA collector core parameters and the UBA technology pack-specific parameters. The core parameters are configured with all UBA technology packs. Review the values for the parameters to make sure they are valid. The following properties are of particular interest:

* COLLECTOR_ALIAS — This is the collector number specified for the Master UBA. You should not modify this parameter.

* INPUT_ID — Specifies an ID to be mapped to one of the output streams associated with the cs2kcdr.pl pre-processor. The cs2kcdr.pl pre-processor can be configured to output files in multiple streams every run interval.

Note: See the Netcool/Proviso Nortel CS2K Carrier VoIP Application Pack User’s Guide for information on configuring the cs2kcdr.pl pre-processor. You configure the cs2kcdr.pl pre-processor by editing variables defined in the cs2kcdr-config.pl configuration file. For example, you specify the number of output streams the pre-processor should create by editing the $numberOfOutputs variable. The number specified for this variable should match the number of UBA Collectors that you add for the Nortel CS2K - CDR pack. Thus, if you added five UBA Collectors, you must specify the value 5 for $numberOfOutputs.

For example, a cs2kcdr.pl pre-processor that is configured for five output streams will write five different output files, as in the following example:

example-file.0.csv

example-file.1.csv

example-file.2.csv

example-file.3.csv

example-file.4.csv

Thus, each of the UBA Collectors you added for the Nortel CS2K - CDR pack must be associated with an output stream. Using the five output streams as an example, you might specify the INPUT_ID parameters for the UBA Collectors as follows:

— UBA instance 1 — Specify the value 0 (zero) so that UBA instance 1 processes example-file.0.csv output files.







7. Redeploy the updated topology (see Starting the Deployer on page 98).

8. Configure the Nortel CS2000 Technology Pack, as explained in the user’s guide.


Log Files

The Technology Pack Installer writes log files to the /usr/tmp directory. Log files in this directory contain a detailed history of the tasks the Technology Pack Installer performs as it installs technology packs. You can check these files to help solve any issues that might occur during technology pack installation. For example, a log file might contain a message that indicates that the Technology Pack Installer GUI could not display back on your system because the DISPLAY environment variable was not set.

Log files for bulk technology packs are named installertimestamp.log, where timestamp is the time the file was created in seconds since the UNIX epoch. Log files for standalone packs are named APInstalltimestamp.log.




Appendix D: Deployment Considerations

Before configuring your deployment, you must be familiar with the information in this appendix. The topics are as follows:

Co-Location Rules

Table 12 lists how many of each component can be deployed per Netcool/Proviso system and whether multiple instances can be installed on the same server.

In this table:

• N — Depends on how many subchannels there are per channel, and how many channels there are per system. For example, if there are 40 subchannels per channel and 8 channels, theoretically N=320. However, the practical limit is probably much lower.

• System — The entire Netcool/Proviso system.

• Per host — A single physical host can be partitioned using zones, which effectively gives you multiple hosts.

Note that all CME, DLDR, FTE, and LDR components within a channel must share the same filesystem.

Topic Page

Co-Location Rules 185

Remote Installation 187

Table 12: Co-Location Rules

Component Number of Instances AllowedCo-Location Constraints

Co-Location Constraints Supported by Deployer?

AMGR One per host that supports DataChannel components

Yes

BCOL • N per system

• One per corresponding subchannel

Yes

CME One per subchannel Filesystem Yes

CMGR One per system Yes

Database One per system Yes

Database channel

One per DataChannel; maximum of 8

Yes



In the Logical view of the Topology Editor, the DataChannel component contains the subchannels, LDR, and DLDR components, with a maximum of 8 channels per system. The subchannel contains the collector, FTE, and CME, with a maximum of 40 subchannels per channel.

DataLoad (SNMP collector)

• N per system


• One per host

Yes

DataMart • N per system

• One per host

Yes

DataView • N per system

• One per host

One per system.

Discovery Server • N per system

• One per host

Co-locate with corresponding DataMart

Yes

DLDR One per channel Filesystem Yes

FTE One per subchannel Filesystem Yes

HAM N+M per system, where N is the number of collectors that HAM is monitoring, and M is the number of standby collectors

Yes

LDR One per channel Filesystem Yes

Log One per system Yes

UBA (simple) • N per system


Yes

UBA (complex) Pack-dependent Pack-dependent Pack-dependent

Table 12: Co-Location Rules

Component Number of Instances AllowedCo-Location Constraints

Co-Location Constraints Supported by Deployer?



Remote Installation

Netcool/Proviso 5.2 supports remote installations for the DataChannel, DataLoad and DataView components only. To illustrate if we two servers in our topology, the host containing the Topology Editor and Deployer, that is, the primary deployer, which we name delphi, and another server that we call corinth. Any actions carried out by the primary deployer on corinth can be referred to as “remote”.

If the topology for corinth is configured so there is a mixture of components — some that support remote installation and some that do not — the deployer treats corinth as not supporting remote installation. To overcome this, you must run the deployer locally on corinth to install the components (as in column 3 of DataMart or column 3, point 2 of DataChannel in the table).

Table 13 provides remote installation information for each component.



Table 13: Remote Installation Details

Component to be Installed Remotely

If FTP and REXEC/RSH are Possible

If FTP is Possible, But REXEC/RSH are not Possible

Neither FTP Nor REXEC/RSH is Possible

DataLoad SNMP

Supported Option 1:

1. Unselect the Remote Command Execution option during the installation.

The deployer creates and transfers the directory with the DataLoad SNMP package in it.

2. As root, log in to the remote system and manually run the run.sh script.

Option 2:

1. Connect to the remote machine, change to the directory where you have downloaded the product distribution, and launch the deployer either in graphical mode (by starting the Launchpad and clicking Start Deployer) or CLI mode (by navigating to the directory containing the deployer and entering the command ./deployer.bin).

If the product distribution is not available, you can FTP or NFS the DataLoad SNMP directory and deployer package to the remote machine.

2. The deployer connects to the database.

3. Install the DataLoad component.

Option 1:

1. Unselect the FTP option during the installation.

The deployer creates a directory with the DataLoad SNMP package in it.

2. Copy the directory to the target system.


Option2:


If the product distribution is not available, you can FTP or NFS the DataLoad SNMP directory and deployer package to the remote machine.

2. The deployer connects to the database, then installs the DataLoad component on this machine.



DataChannel Supported Option 1:


The deployer creates and transfers the directory with the DataChannel in it.


Option 2:


If the product distribution is not available, you can FTP or NFS the DataChannel directory and deployer package to the remote machine.


3. Install the DataChannel component.

Option 1:

1. Unselect the FTP option during the installation.

The deployer creates a directory with the DataChannel package in it.

2. Copy the DataChannel directory to the target system.


Option2:


If the product distribution is not available, you can FTP or NFS the DataChannel directory and deployer package to the remote machine.

2. The deployer connects to the database, then installs the DataChannel component on this machine.








DataMart Not supported Not supported 1. Connect to the remote machine, change to the directory where you have downloaded the product distribution, and launch the deployer either in graphical mode (by starting the Launchpad and clicking Start Deployer) or CLI mode (by navigating to the directory containing the deployer and entering the command ./deployer.bin).

If the product distribution is not available, you can FTP or NFS the DataMart and deployer package to the remote machine.

2. The deployer connects to the database, then installs the DataMart component on this machine.








DataView Supported Option 1:


The deployer creates and transfers the directory with the DataView in it.


Option 2:


If the product distribution is not available, you can FTP or NFS the DataView directory and deployer package to the remote machine.


3. Install the DataView component.


If the product distribution is not available, you can FTP or NFS the DataView and deployer package to the remote machine.

2. The deployer connects to the database, then installs the DataView component on this machine.








Database Not supported Not supported 1. Copy the topology.xml file to the remote machine.


If the product distribution is not available, you can FTP or NFS the Database directory and deployer package to the remote machine.







Appendix E: DataChannels

This chapter provides detailed information about the DataChannel architecture.


Data Collection

A Netcool/Proviso DataChannel consists of a number of components, including the following:

• File Transfer Engine (FTE)

• Complex Metric Engine (CME)

• Daily Database Loader (DLDR)

• Hourly Database Loader (LDR)

• Plan Builder (PBL)

• Channel Manager

The FTE, DLDR, LDR, and PBL components are assigned to each configured DataChannel. The FTE and CME components are assigned to one or more Collector subchannels.

Data is produced by Netcool/Proviso DataLoad Collectors. Both SNMP and BULK Collectors are fed into a subchannel’s channel processor. Data moves through the CME and is synchronized in the Hourly Loader. The Hourly Loader computes group aggregations from resource aggregation records. The Daily Loader provides statistics on metric channel tables and metric tablespaces and inserts data into the database.

Data is moved from one channel component to another as files. These files are written to and read from staging directories between each component. Within each staging directory there are subdirectories named do, output, and done. The do subdirectory contains files that are waiting to be processed by a channel component. The output subdirectory stores data for the next channel component to work on. After files are processed, they are moved to the done directory. All file movement is accomplished by the FTE component.

Topic Page

Data Collection 193

Starting the DataLoad SNMP Collector 196

DataChannel Management Components in a Distributed Configuration 197

SNMP Traps from Logs 198

DataChannel Terminology 199



Data Aggregation

A DataChannel aggregates data collected by collectors for eventual use by DataView reports. The DataChannel provides online statistical calculations of raw collected data, and detects real-time threshold violations.

Aggregations include:

• Resource aggregation for every metric and resource

• Group aggregation for every group

• User-defined aggregation computed from raw data

Threshold detections in real time include:

• Raw data violating configured thresholds

• Raw data violating configured thresholds and exceeding the threshold during a specific duration of time

• Averaged data violating configured thresholds

Management Programs and Watchdog Scripts

The following table lists the names and corresponding watchdog scripts for the DataChannel management programs running on different DataChannel hosts.

The watchdog scripts run every few minutes from cron. Their function is to monitor their corresponding management component, and to restart it, if necessary. You can add watchdog scripts for the Channel Manager programs to the crontab for the pvuser on each host on which you installed a DataChannel component.

To add watchdog scripts to the crontab:

1. Log in as pvuser. Make sure this login occurs on the server running the Channel Manager components.

2. At a shell prompt, go to the DataChannel conf subdirectory. For example:

$ cd /opt/datachannel/conf

Table 14: Programs and Scripts

Component Program Executable1

1. The actual component’s executable file seen in the output of ps -ef is named XXX_visual, where XXX is an entry in this column. For example, the file running for CMGR is seen as CMGR_visual.

Corresponding Watchdog Script

Notes

Channel Name Server CNS cnswRuns on the host running the Channel Manager. Log Server LOG logw

Channel Manager CMGR cmgrw

Application Manager AMGR amgrw One per subchannel host and one on the Channel Manager host.



3. Open the file dc.cron with a text editor. (The dc.cron files differ for different hosts running different DataChannel programs. The following example shows the dc.cron file for the host running the Channel Manager programs.)

4. Copy the lines in the dc.cron file to the clipboard.

5. At another shell prompt, edit the crontab for the current user.

crontab -e

A text editor session opens, showing the current crontab settings.

6. Paste the lines from the dc.cron tab into the crontab file. For example:

7. Save and exit the crontab file.

8. Repeat steps 1 to 8 on each DataChannel host, with this difference:

The dc.cron file on collector and loader hosts will have only one line, like this example:

On such hosts, this is the only line you need to add to the pvuser crontab.

DataChannel Application Program Names

The DataChannel subchannel application programs are listed in Table 15.

0,5,10,15,20,25,30,35,40,45,50,55 1-31 1-12 0-6 /opt/datachannel/bin/cnsw > /dev/null

2>&1

1,6,11,16,21.26,31,36,41,46,51,56 1-31 1-12 0-6 /opt/datachannel/bin/logw > /dev/null 2>&1

2,7,12,17,22.27,32,37,42,47,52,57 1-31 1-12 0-6 /opt/datachannel/bin/cmgrw >

/dev/null 2>&13,8,13,18,23.28,33,38,43,48,53,58 1-31 1-12 0-6 /opt/datachannel/bin/amgrw >

/dev/null 2>&1

0 * * * * [ -f /opt/datamart/dataMart.env ] && [ -x /opt/datamart/bin/pollinv ] && ....

0,5,10,15,20,25,30,35,40,45,50,55 1-31 1-12 0-6 /opt/datachannel/bin/cnsw > /dev/null 2>&1

1,6,11,16,21,26,31,36,41,46,51,56 1-31 1-12 0-6 /opt/datachannel/bin/logw > /dev/null

2>&1

2,7,12,17,22,27,32,37,42,47,52,57 1-31 1-12 0-6 /opt/datachannel/bin/cmgrw > /dev/null 2>&1

3,8,13,18,23,28,33,38,43,48,53,58 1-31 1-12 0-6 /opt/datachannel/bin/amgrw >

/dev/null 2>&1

0,5,10,15,20,25,30,35,40,45,50,55 1-31 1-12 0-6 /opt/datachannel/bin/amgrw >

/dev/null 2>&1

Table 15: DataChannel Subchannel Application Program Names

DataChannel Program1 Description Example

BCOL.n.c Bulk Collector process for channel n, with Collector number c BCOL.1.2

UBA.n.c UBA Bulk Collector process for channel n, with Collector number c UBA.1.100

CME.n.s Complex Metric Engine for channel n, Collector number s CME.2.1

DLDR.n Daily Loader for channel n DLDR.1

LDR.n Hourly Loader for channel n LDR.2



Note: For historical reasons, the SNMP DataLoad collector is managed by Netcool/Proviso DataMart, and does not appear in Table 15.

Starting the DataChannel Management Programs

Verify that the DataChannel management programs are running:

1. Log in as pvuser on each DataChannel host.

2. Change to the DataChannel installation’s bin subdirectory. For example:

$ cd /opt/datachannel/bin

3. Run the findvisual command:

$ ./findvisual

In the resulting output, look for:

— The AMGR process on every DataChannel host

— The CNS, CMGR, LOG, and AMGR processes on the Channel Manager host

If the DataChannel management programs are running on all DataChannel hosts, start the application programs on all DataChannel hosts by following these steps:

1. Log in as pvuser. Make sure this login occurs on the host running the Channel Manager programs.

2. Change to the DataChannel installation’s bin subdirectory. For example:


3. Run the following command to start all DataChannel applications on all configured DataChannel hosts:

./dccmd start all

The command shows a success message like the following example.

See the Netcool/Proviso Command Line Interface Guide for information about the dccmd command.

Starting the DataLoad SNMP Collector

Once you have started the DataChannel components, check every server that hosts a DataLoad SNMP collector. to make sure the collectors are running. To check whether a collector is running, run the following command:

ps -ef | grep -i pvmd

FTE.n. File Transfer Engine for channel n FTE.1.1

PBL.n. Plan Builder for channel n PBL.1

1. The actual application’s executable file visible in the output of ps -ef is named XXX_visual, where XXX is an entry in this column.

Table 15: DataChannel Subchannel Application Program Names

DataChannel Program1 Description Example

Done: 12 components started, 0 components already running



If the collector is running, you will see output similar to the following:

pvuser 27118 1 15 10:03:27 pts/4 0:06 /opt/dataload/bin/pvmd -nologo -noherald /opt/dataload/bin/dc.im -headless -a S

If a collector is not running, perform the following steps:

1. Log into the server that is running Netcool/Proviso SNMP DataLoad by entering the username and password you specified when installing SNMP DataLoad.

2. Source the DataLoad environment file by entering the following command:

./$DLHOME/dataLoad.env

where $DLHOME is the location where SNMP DataLoad is installed on the system (/opt/dataload, by default).

Note: If DataLoad shares the same server as DataMart, make sure you unset the environment variable by issuing the following command from a BASH shell command line: unset PV_PRODUCT

3. Change to the DataLoad bin directory by entering the following command:

cd $PVMHOME/bin

4. Start the DataLoad SNMP collector using the following command:

pvmdmgr start

The command displays the following message when the SNMP collector has been successfully started:

The script controlling the starting and stopping of SNMP collectors, pvmdmgr, prevents the possibility that multiple collector instances can be running simultaneously.

If a user starts a second instance, that second instance will die by itself in under two minutes without ever contacting or confusing the relevant watchdog script.

DataChannel Management Components in a Distributed Configuration

Two channels running on the same system share a common Application Manager (AMGR) that has a watchdog script, amgrw. The AMGR is responsible for starting, monitoring through watchdog scripts, and gathering status for each application server process for the system it runs on. Application programs include the FTE, CME, LDR, and DLDR programs.

An example of multiple processes running on the same host is:

• 1 Application Manager (AMGR)

• 2 Complex Metric Engines (CME)

• 2 File Transfer Engines (FTE)

• 2 Hourly Data Loaders (LDR)

• 2 Daily Data Loaders (DLDR)

Each program has its own set of program and staging directories.

PVM Collecting Daemon is running.



Manually Starting the Channel Manager Programs

If you need to manually start the Channel Manager programs, you must do so in a certain order. After a manual start, the program’s watchdog script restarts the program as required.

To start the Channel Manager programs manually:

1. Log in as pvuser on the host running the Channel Manager programs.

2. At a shell prompt, change to the DataChannel bin subdirectory. For example:


3. Enter the following commands at a shell prompt, in this order:

For the Channel Name Server, enter:

./cnsw

For the Log Server, enter:

./logw

For the Channel Manager, enter:

./cmgrw

For the Application Manager, enter:

./amgrw

To manually start the DataChannel programs on all hosts in your DataChannel configuration:

1. Start the Channel Manager programs, as described in the previous section.

2. On each DataChannel host, start the amgrw script.

3. On the Channel Manager host, start the application programs as described in Starting the DataChannel Management Programs on page 196.

SNMP Traps from Logs

The log-to-traps feature scans the DataChannel log file (by default, proviso.log) for the specified messages. If matching messages are found, the feature sends an SNMP trap to the specified host and port.

You enable the log-to-traps feature by setting up one or more rules files that describe the log file messages you want to convert to SNMP traps.

For more information, see the Technical Note entitled Setting SNMP Traps for Log Messages.

Adding DataChannels to an existing system

If you add and configure a new remote DataChannel using the Topology Editor after the initial deployment of your topology, the system will not pick up these changes, unless the user manually stop starts the relevant processes, as explained in Chapter 7, Modifying the Current Deployment on page 115.

To shut down the DataChannel:



Note: The DataChannel CMGR, CNS, AMGR, and LOG visual processes must remain running until you have gathered the DataChannel parameters from your environment.

1. On the DataChannel host, log in as the component user, such as pvuser.

2. Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default) using the following command:


3. Shut down the DataChannel FTE. Prior to shutting down all DataChannel components, some DataChannel work queues must be emptied. To shut down the DataChannel FTE and empty the work queues: $ ./dccmd stop FTE.*

4. Let all DataChannel components continue to process until the …/do directories for the FTE and CME components contain no files. The …/do directories are located in the subdirectories of $DCHOME (typically, /opt/datachannel) that contain the DataChannel components – for example, FTE.1.1, CME.1.1.

5. Shut down all CMEs on the same hour (So the operator state files will be in synch with each other). To accomplish this:

5-a. Identify the leading CME by either looking at the do and done directories in each CME and the DAT files inside there; or using dccmd status all to see which CME is reporting the latest hour in its processing status.

5-b. All CMEs on that hour must be stopped and then continue using the same approach to finding the hour being processed and stop each CME as it reaches the same hour until all CMEs are stopped. CMEs are stopped using the command:

$ ./dccmd stop CME

6. Use the following dccmd commands to stop the DataChannel applications:

$ ./dccmd stop DLDR

$ ./dccmd stop LDR

$ ./dccmd stop FTE

$ ./dccmd stop DISC

$ ./dccmd stop UBA (if required)

For details on how to restart a DataChannel, see Manually Starting the Channel Manager Programs on page 198.

DataChannel Terminology

The following terms are used throughout the Netcool/Proviso DataChannel installation procedure.

• Collector Subchannel: A subdivision of a DataChannel, with each Collector subchannel associated with a single Collector and CME. The division into Collector subchannels helps eliminate latency or loss of data caused by delayed Collectors. If a Collector subchannel disconnects for a period of time, only that Collector is affected, and all other Collector subchannels continue processing. The number of Collector subchannels per DataChannel differs according to the needs of a particular deployment. See the Netcool/Proviso Configuration Recommendations for information related to system configuration requirements. The terms Collector and Collectors are used to refer to Collector subchannel and Collector subchannels.

• Complex Metric Engine (CME): A DataChannel program that performs on-the-fly calculations on raw metrics data for a DataChannel. These calculations include time aggregations for resources, as well as statistical calculations using raw data, thresholds, properties, and constants as inputs. If CME formulas are defined for the incoming metrics data, the values are processed by those formulas. The CME synchronizes metadata at the beginning of each hour, and only processes the metadata that exists for the hour.



• CORBA (Common Object Request Broker Architecture): An industry-standard programming architecture that enables pieces of programs, called objects, to communicate with one another regardless of the programming language that they were written in or the operating system they are running on.

• Daily Database Loader (DLDR): A DataChannel program that gathers statistical data processed by a DataChannel’s CME and inserts it into the Netcool/Proviso database. There is one Daily Loader for each DataChannel; it is part of the channel processor component of the DataChannel.

• DataChannel Remote (DCR): A DataChannel installation configuration in which the subchannel, CME and FTE components are installed and run on one host, while the Loader components are installed and run on another host. In this configuration, the subchannel hosts can continue processing data and detecting threshold violations, even while disconnected from the Channel Manager server.

• DataChannel Standard: A DataChannel installation configuration in which all component programs of each subchannel are installed and run on the same server. DataChannel Standard installation is described in this chapter.

• DataLoad Bulk Collector: A DataLoad program that processes different data formats and resource files supplied by network devices, network management platforms, network probes, and other types of resources such as BMC Patrol. The Bulk Collector translates bulk statistics provided in flat files into Netcool/Proviso metadata and data. If operating in synchronized inventory mode, the Bulk Collector passes the resources and properties to the Netcool/Proviso DataMart Inventory application.

• DataLoad SNMP Collector: A DataLoad program that collects data from network resources via SNMP polling. The SNMP Collector provides raw data files to the DataChannel for processing by the CME.

• DataLoad UBA Bulk Collector: A DataLoad program that imports data from files (referred to as Bulk input files) generated by non-SNMP devices, including Alcatel 5620 NM, Alcatel SAM, and Cisco CWM. These Bulk input files contain formats that the Bulk Collector is unable to handle.

• Discovery Server (DISC): A DataChannel program that runs as a daemon to perform an inventory of SNMP network devices from which to gather statistical data.

• Hourly Database Loader (LDR): A DataChannel program that serves as the point of data synchronization and merging, and of late data processing, for each DataChannel. The Hourly Loader gathers files generated by the CME, computes group aggregations from the individual resource aggregation records, and loads the data into the Netcool/Proviso database.

• File Transfer Engine (FTE): A DataChannel program that periodically scans the Collector output directories, examines the global execution plan to determine which computation requests require the data, then sorts the incoming data for storage.

• Next-Hour Policy: Specifies the number of seconds to wait past the hour for files to arrive before the next hourly directory is created. The default value causes the DataChannel to wait until 15 minutes after the hour before it starts processing data for the next hour. To avoid losing data, you need to set a percentage and a time-out period during the configuration of the CME.

• Plan Builder (PBL): A DataChannel program that creates the metric data routing and processing plan for the other components in the DataChannel.


Appendix F: Aggregation Sets

This appendix describes how to configure and install aggregation sets. The topics are as follows:

Overview

An aggregation set is a grouping of network management raw data and computed statistical information stored in the Netcool/Proviso database for a single timezone. For example, if your company provides network services to customers in both the Eastern and Central US timezones, you must configure two aggregation sets.

Because each aggregation set is closely linked with a timezone, aggregation sets are sometimes referred to as timezones in the in Netcool/Proviso documentation. However, the two concepts are separate.

Note: “Aggregation set” is abbreviated to “Aggset” in some setup program menus.

Configuring Aggregation Sets

When you configure an aggregation set, the following information is stored in the database:

• The timezone ID number associated with this aggregation set.

• The timezone offset from GMT, in seconds.

• Optionally, the dates that Daylight Savings Time (DST) begins and ends in the associated timezone for each year from the present through 2010. (Or you can configure an aggregation set to ignore DST transitions.)

You configure an aggregation set either by creating a new set or by modifying an existing set. The first aggregation set is installed by default when you install Netcool/Proviso Datamart, so if your network will monitor only one timezone, you need only to configure the existing set.

To configure an aggregation set:

1. Log in as root. (Remain logged in as root for the remainder of this appendix.)

2. At a shell prompt, change to the directory where Netcool/Proviso DataMart program files are installed. For example:

# cd /opt/datamart

Topic Page

Overview 201

Configuring Aggregation Sets 201

Installing Aggregation Sets 205

Linking DataView Groups to Timezones 210



3. Load the DataMart environment variables into your current shell’s environment using the following command:

# . ./dataMart.env

4. Change to the bin directory:

# cd bin


# ./create_modify_aggset_def

The following menu is displayed:

6. Type 1 at the Choice prompt and press Enter to enter the password for PV_ADMIN. The script prompts twice for the password you set up for PV_ADMIN.

==> Enter password for PV_ADMIN : PV==> Re-enter password : PV

Note: The script obtains the DB_USER_ROOT setting from the Netcool/Proviso database configured in previous chapters, and constructs the name of the Netcool/Proviso database administrative login name, PV_ADMIN, from that base. If you set a different DB_USER_ROOT setting, the “Database user” entry reflects your settings. For example, if you previously set DB_USER_ROOT=PROV, this script would generate the administrative login name PROV_ADMIN.

7. To configure the first aggregation set, type 2 at the Choice prompt and press Enter twice.

The script shows the current settings for the aggregation set with ID 0 (configured by default):

You can use this aggregation set as-is, or modify it to create a new timezone.

--------------------------------------------------

Netcool/Proviso DatabaseDate: <Current Date> <Current Time> Script name: create_modify_aggset_def

Script revision: <revision_number> - Aggregation set creation

- Aggregation set modification

- DST configuration for an aggregation set --------------------------------------------------

Database user................. : [ PV_ADMIN ] Database user password........ : [ ]

Menu :

1. Input password for PV_ADMIN.

2. Configure an aggset.

0. Exit

Choice : 1

____

The following Time Zones are defined into the Database : ___________________________________________________________________________________

id | Date (in GMT) | offset in | Name | Aggset status | | seconds | |

___________________________________________________________________________________

0 | 1970/01/01 00:00:00 | 0 | GMT | Aggset created

==> Press <Enter> to continue ....



8. Press Enter. A list of predefined timezones and their timezone numbers is displayed:

9. Type the number of the timezone you want to associate with aggregation set 0. For example, type 9 for Eastern Standard Time.

The script prompts:

==> Select an Aggset ID to add/modify (E: Exit) : 0To associate the specified timezone, EST, with the database’s default aggregation set, type 0.

10. The script asks whether you want your aggregation set to include Daylight Saving Time (DST) transition dates:

Does your Time Zone manage DST [Y/N] : Y For most time zones, type Y and press Enter.

Num | OffSet | Time zone Name | Short | Long | Hours | | Description | Description

___________________________________________________________________________________

[ 1] : -10:00 | America/Adak | HAST | Hawaii-Aleutian Standard Time [ 2] : -10:00 | Pacific/Rarotonga | CKT | Cook Is. Time

[ 3] : -09:00 | America/Anchorage | AKST | Alaska Standard Time

[ 4] : -09:00 | AST | AKST | Alaska Standard Time [ 5] : -08:00 | PST | PST | Pacific Standard Time

[ 6] : -07:00 | MST | MST | Mountain Standard Time

[ 7] : -06:00 | America/Mexico_City| CST | Central Standard Time [ 8] : -06:00 | CST | CST | Central Standard Time

[ 9] : -05:00 | EST | EST | Eastern Standard Time

[10] : -04:00 | America/Santiago | CLT | Chile Time [11] : -03:00 | America/Sao_Paulo | BRT | Brazil Time

[12] : -01:00 | Atlantic/Azores | AZOT | Azores Time

[13] : 000:00 | Europe/London | GMT | Greenwich Mean Time [14] : +01:00 | Europe/Paris | CET | Central European Time

[15] : +01:00 | ECT | CET | Central European Time

[16] : +02:00 | Africa/Cairo | EET | Eastern European Time [17] : +02:00 | Europe/Helsinki | EET | Eastern European Time

[18] : +02:00 | Europe/Bucharest | EET | Eastern European Time

[19] : +03:00 | Asia/Baghdad | AST | Arabia Standard Time [20] : +03:00 | Europe/Moscow | MSK | Moscow Standard Time

[21] : +04:00 | Asia/Baku | AZT | Azerbaijan Time

[22] : +05:00 | Asia/Yekaterinburg | YEKT | Yekaterinburg Time

[23] : +06:00 | Asia/Novosibirsk | NOVT | Novosibirsk Time [24] : +07:00 | Asia/Krasnoyarsk | KRAT | Krasnoyarsk Time

[25] : +08:00 | Asia/Irkutsk | IRKT | Irkutsk Time

[26] : +09:00 | Asia/Yakutsk | YAKT | Yakutsk Time [27] : +10:00 | Australia/Sydney | EST | Eastern Standard Time (New

South Wales)

[28] : +11:00 | Pacific/Noumea | NCT | New Caledonia Time [29] : +12:00 | Pacific/Auckland | NZST | New Zealand Standard Time

[30] : +12:00 | Asia/Anadyr | ANAT | Anadyr Time

==> Select Time Zone number [1-30 ] (E : Exit) : 9



11. The script displays the results:

Note: The dates that appear in your output will most likely be different from the dates that appear in the example.

12. Press Enter to return to the script’s main menu.

13. To configure a second aggregation set, type 2 at the Choice prompt and press Enter three times.

14. Specify the timezone number of your second timezone. For example, type 8 to specify Central Standard Time.

The script prompts:

==> Select an Aggset ID to add/modify (E: Exit) : 1If you enter a set number that does not exist in the database, the script creates a new aggregation set with that number. Type the next available set number, 1.

Complete with Success ...

The following Time Zone has been modified:

___________________________________________________________________________________id | Date (in GMT) | offset in | Name | Aggset status

| | seconds | |

___________________________________________________________________________________

0 | 1970/01/01 00:00:00 | 0 | GMT | Aggset created

0 | 2004/09/29 22:00:00 | -14400 | EST_2004_DST | Aggset created 0 | 2004/10/31 06:00:00 | -18000 | EST_2004 | Aggset created

0 | 2005/04/03 07:00:00 | -14400 | EST_2005_DST | Aggset created

0 | 2005/10/30 06:00:00 | -18000 | EST_2005 | Aggset created 0 | 2006/04/02 07:00:00 | -14400 | EST_2006_DST | Aggset created

0 | 2006/10/29 06:00:00 | -18000 | EST_2006 | Aggset created


0 | 2008/04/06 07:00:00 | -14400 | EST_2008_DST | Aggset created

0 | 2008/10/26 06:00:00 | -18000 | EST_2008 | Aggset created 0 | 2009/04/05 07:00:00 | -14400 | EST_2009_DST | Aggset created

0 | 2009/10/25 06:00:00 | -18000 | EST_2009 | Aggset created





15. Respond Y to the timezone management query.

The script shows the results of creating the second aggregation set:

16. Press Enter to return to the main menu, where you can add more aggregation sets, or type 0 to exit.

The next step is to install the aggregation sets on the server on which you installed Netcool/Proviso DataMart.

Installing Aggregation Sets

When you install DataMart, aggregation set 0 is automatically installed. If you configured only the default aggregation set (in Configuring Aggregation Sets on page 201), you can skip this section. However, f you configured timezones for additional aggregation sets, you must install the non-zero sets using the steps in this section.

Step 1: Start the Netcool/Proviso Setup Program

Start the setup program by following these steps:

1. Make sure your EDITOR environment variable is set.

2. Change to the /opt/Proviso directory:

cd /opt/Proviso

3. Start the setup program:

./setup

____________

The following Time Zone has been modified : ___________________________________________________________________________________

______________

id | Date (in GMT) | offset in | Name | Aggset status

| | seconds | |

_________________________________________________________________________________________________

1 | 2004/09/29 23:00:00 | -18000 | CST_2004_DST | Aggset created 1 | 2004/10/31 07:00:00 | -21600 | CST_2004 | Aggset created

1 | 2005/04/03 08:00:00 | -18000 | CST_2005_DST | Aggset created

1 | 2005/10/30 07:00:00 | -21600 | CST_2005 | Aggset created 1 | 2006/04/02 08:00:00 | -18000 | CST_2006_DST | Aggset created

1 | 2006/10/29 07:00:00 | -21600 | CST_2006 | Aggset created

1 | 2007/04/01 08:00:00 | -18000 | CST_2007_DST | Aggset created 1 | 2007/10/28 07:00:00 | -21600 | CST_2007 | Aggset created


1 | 2008/10/26 07:00:00 | -21600 | CST_2008 | Aggset created 1 | 2009/04/05 08:00:00 | -18000 | CST_2009_DST | Aggset created







The setup program’s main menu is displayed:

4. Type 1 at the Choice prompt and press Enter. The Install menu is displayed:

Step 2: Set Aggregation Set Installation Parameters

5. Type 1 at the Choice prompt and press Enter. Setup displays the installation environment menu:

Note: Menu options 2, 3, and 4 are used later in the installation process.

6. Make sure the value for PROVISO_HOME is the same one you used when you installed the database configuration. If it is not, type 1 at the Choice prompt and correct the directory location.

7. The script displays the component installation menu:

Netcool/Proviso <version number> - [Main Menu]

1. Install

2. Upgrade 3. Uninstall

0. Exit

Choice [1]> 1

Netcool/Proviso <version number> - [Install]

1. Netcool/Proviso Database Configuration

0. Previous Menu

Choice [1]> 1

Netcool/Proviso Database Configuration <version number> - [installation environment]

1. PROVISO_HOME : /opt/Proviso

2. DATABASE_DEF_HOME : -

3. CHANNELS_DEF_HOME : - 4. AGGRSETS_DEF_HOME : -

5. Continue 0. Exit

Choice [5]> 5

Netcool/Proviso Database Configuration <version number> - [component installation]

1. Database 2. Channel

3. Aggregation set

0. Exit

Choice [1]> 3



8. Type 3 at the Choice prompt and press Enter. The script displays the installation environment menu:

9. Type 4 at the Choice prompt and press Enter to specify the same value for DB_USER_ROOT that you specified in previous chapters. This manual’s default value is PV.

Enter value for DB_USER_ROOT [] : PV 10. Make sure that the values for PROVISO_HOME, ORACLE_HOME, and ORACLE_SID are the same

ones you entered in previous chapters. Correct the values if necessary.

11. Type 5 at the Choice prompt and press Enter. Setup displays the Aggregation Set installation options menu:

Note: Do not change the value for option 4. Retain the default value, “all.”

12. The first time you use any menu option, the script prompts for the password for PV_ADMIN:

Enter password for PV_ADMIN : PV

Netcool/Proviso Aggregation Set <version number> - [installation environment]

1. PROVISO_HOME : /opt/Proviso

2. ORACLE_HOME : /opt/oracle/product/10.2.0 3. ORACLE_SID : PV

4. DB_USER_ROOT : -

5. Continue

0. Previous Menu

Choice [5]> 4

Netcool/Proviso Aggregation Set <version number> - [installation options]

1. List of configured aggregation sets

2. List of installed aggregation sets

3. Number of the aggregation set to install : - 4. Channel where to install aggregation set : (all)

5. Start date of aggregation set : <Current Date>

6. Continue

0. Back to options menu

Choice [6]>



13. Use menu option 1 to list the aggregation sets you configured in Configuring Aggregation Sets on page 201. The script displays a list similar to the following:

14. Select option 2 to list the aggregation sets already installed. The output is similar to the following:

Remember that aggregation set 0 is automatically installed when you install the database channel, and continues to be installed even if you modified set 0 by assigning a different timezone.

15. Select option 3 to designate the aggregation set to install. In the examples above, set 0 is already installed, but set 1 is waiting to be installed. Thus, enter 1 at the prompt:

Enter Aggregation Set number between 1 and 998 : 1

============= LIST OF CONFIGURED AGGREGATION SETS ============

Num Effect Time Name Time lag

---- --------------------- ------------------------------------------- --------

0 01-01-1970 00:00:00 GMT +0h 04-01-2007 07:00:00 EST_2007_DST -4h

04-02-2006 07:00:00 EST_2006_DST -4h

04-03-2005 07:00:00 EST_2005_DST -4h 04-04-2010 07:00:00 EST_2010_DST -4h

04-05-2009 07:00:00 EST_2009_DST -4h

04-06-2008 07:00:00 EST_2008_DST -4h 09-29-2004 22:00:00 EST_2004_DST -4h

10-25-2009 06:00:00 EST_2009 -5h

10-26-2008 06:00:00 EST_2008 -5h 10-28-2007 06:00:00 EST_2007 -5h

10-29-2006 06:00:00 EST_2006 -5h

10-30-2005 06:00:00 EST_2005 -5h 10-31-2004 06:00:00 EST_2004 -5h

10-31-2010 06:00:00 EST_2010 -5h

1 04-01-2007 08:00:00 CST_2007_DST -5h 04-02-2006 08:00:00 CST_2006_DST -5h

04-03-2005 08:00:00 CST_2005_DST -5h

04-04-2010 08:00:00 CST_2010_DST -5h

04-05-2009 08:00:00 CST_2009_DST -5h 04-06-2008 08:00:00 CST_2008_DST -5h

09-29-2004 23:00:00 CST_2004_DST -5h

10-25-2009 07:00:00 CST_2009 -6h 10-26-2008 07:00:00 CST_2008 -6h

10-28-2007 07:00:00 CST_2007 -6h

10-29-2006 07:00:00 CST_2006 -6h 10-30-2005 07:00:00 CST_2005 -6h

10-31-2004 07:00:00 CST_2004 -6h

10-31-2010 07:00:00 CST_2010 -6h

2 aggregation sets configured

Press enter...

============== LIST OF CREATED AGGREGATION SETS ==============

============ X: created ==== #: partially created ============

Channels 0

| 1AggSets -----------------------------------------------------------------------

| 0 X

Press enter...



16. By default, the date to start collecting data on the designated aggregation set is today’s date. You can instead use menu option 5 to designate a future date to start collecting data. Set an appropriate future date for your installation.

17. When all menu parameters are set, type 6 at the Choice prompt and press Enter.

Step 3: Edit Aggregation Set Parameters File

18. The script prompts that it will start the editor specified in the EDITOR environment variable and open the aggregation set parameters file. Press Enter. An editing session opens containing the aggsetreg.udef configuration file, as shown in this example:

19. Do not make changes to this file unless you have explicit instructions from Professional Services.

Only if you have guidelines from Professional Services for advanced configuration of your aggregation sets, make the suggested edits.

Save and close the file.

Enter start date (GMT) using Oracle format 'yyyy.mm.dd-hh24' : 2009.08.31-00

WARNING! Start date is set in the future.

No loading is allowed until start date (GMT) is reached.Do you confirm the start date (Y/N) [N] ? y

#

# Netcool/Proviso Datamart# <Current Date>#

#

# Channel C01: GROUPS DAILY aggregates storage#

[AGGSETREG/C01/1DGA/TABLE/CURRENT]

PARTITION_EXTENTS=5PARTITION_SIZE=100K

#

[AGGSETREG/C01/1DGA/TABLE/HISTORIC]PARTITION_EXTENTS=5

PARTITION_SIZE=100K

#[AGGSETREG/C01/1DGA/TABLESPACE/CURRENT]

CREATION_PATH=/raid_2/oradata

EXTENT_SIZE=64KSIZE=10M

#

[AGGSETREG/C01/1DGA/TABLESPACE/HISTORIC]CREATION_PATH=/raid_3/oradata

EXTENT_SIZE=64K

SIZE=10M#

# Channel C01: RESOURCES DAILY aggregates storage

#[AGGSETREG/C01/1DRA/TABLE/CURRENT]

PARTITION_EXTENTS=5

PARTITION_SIZE=100K#

...



20. When you close the configuration file, the script checks the file parameters and starts installing the aggregation set. The installation takes three to ten minutes, depending on the speed of your server.

A message like the following is displayed when the installation completes:

Linking DataView Groups to Timezones

Once you have configured and installed the aggregation sets, you must link DataView groups to a timezone. You can link a defined timezone to a calendar you create in the DataView GUI, or the CME Permanent calendar (a 24-hour calendar).

When you link a group to a specific timezone and calendar, all subgroups inherit the same timezone and calendar.

Best practice:

Use a separate calendar for each timezone. If you link multiple timezones to the same calendar, a change to one timezone calendar setting will affect all the timezones linked to that calendar.

To link a group to a timezone:

1. Create a calendar with the DataView GUI, or use the default CME Permanent calendar.

2. Create a text file (for example, linkGroupTZ.txt) with the following format:

— Each line has three fields separated by |_|.

— The first field is a DataView group name.

— The second field is a timezone name from the Netcool/Proviso internal timezone list. See Configuring Aggregation Sets on page 201 for a list of timezone names.

— The third field is the name of the calendar you create, or CME Permanent.

The following example line demonstrates the file format:

~Group~USEast|_|EST_2005_DST|_|CME Permanent|_|

Enter as many lines as you have timezone entries in your aggregation set configuration.

3. At a shell prompt, enter a command similar to the following, which uses the Resource Manager’s CLI to link the group to the timezone:

To unlink a timezone:

• Use the resmgr command. For example:

P R O V I S O A g g r e g a t i o n S e t <version number>

||||||||||||||||||||||||

AggregationSet installed

Netcool/Proviso Aggregation Set 1 on Channel 1 successfully installed !

Press Enter...

resmgr -import segp -colNames “npath tz.name cal.name” -file linkGroupTZ.txt

resmgr -delete linkGroupSE_TZC -colNames “npath tz.name cal.name” -file linkGroupTZ.txt



To review timezone to group associations:

• Use the resmgr command. For example:

resmgr -export segp -colNames “name tz.name cal.name” -file link.txt




Appendix G: Secure File Transfer Installation

This appendix describes the OpenSSH installation, configuration, and testing process in detail for each platform. The topics are as follows:

Overview

This document explains how to install OpenSSH for Secure File Transfer (SFTP) among Netcool/Proviso components. You must be proficient in your operating system and have a basic understanding of public/private key encryption when working with SFTP. For the purposes of this document, an SFTP “client” is the node that initiates the SFTP connection and login attempt, while the SFTP “server” is the node that accepts the connection and permits the login attempt. This distinction is important for generating public/private keys and authorization, as the SFTP server should have the public key of the SFTP client in its authorized hosts file. This process is described in more detail later.

For Netcool/Proviso to use SFTP for the remote execution of components and file transfer, OpenSSH must be configured for key-based authentication when connecting from the Proviso account on the client (the host running the Netcool/Proviso process that needs to use SFTP) to the account on the server. In addition, the host keys must be established such that the host key confirmation prompt is not displayed during the connection.

Topic Page

Overview 213

Enabling SFTP 214

Installing OpenSSH 214

Configuring OpenSSH 219

Testing OpenSSH and SFTP 222

Troubleshooting 223

Netcool/Provisio SFTP Errors 224



Enabling SFTP

The use of SFTP is supported in Netcool/Proviso. Netcool/Proviso SFTP can be enabled for a single component, set of components, or all components as needed. This table shows the Netcool/Proviso components that support SFTP:

Note: This document is intended only as a guideline to installing OpenSSH. Netcool/Proviso calls the ssh binary file directly and uses the SFTP protocol to transfer files, so the essential Netcool/Proviso requirement is that OpenSSH is used and public key authentication is enabled. The following procedures are examples of one method of installing and configuring OpenSSH. The precise method and final configuration for your site should be decided by your local operating system security administrator.

For detailed information about OpenSSH and its command syntax, visit the following URL:

http://www.openssh.com/manual.html

Installing OpenSSH

This section describes the steps necessary to install OpenSSH on the following platforms:

• AIX Systems on page 214

• Solaris Systems on page 216

• Linux Systems on page 219

Note: The following sections refer to the earliest supported version of the required packages. Refer to the OpenSSH documentation for information about updated versions.

AIX Systems

To install OpenSSH on AIX systems, follow these steps:

• Step 1: Download the Required Software Packages on page 215.

• Step 2: Install the Required Packages on page 215.

• Step 3: Configure OpenSSH Server to Start Up on System Boot on page 215.

Client Server Description

Node on which DataChannel resides.

All other DataChannel nodes to be installed.

Installer can use SFTP to install Netcool/Proviso software to remote locations.

Bulk Collector DataMart Inventory Transfer of inventory files.

FTE Bulk Collector FTE transfers files from BCOL to CME.

FTE DataLoad SNMP collector Transfer of SNMP data.

CME/LDR Remote CME Downstream CME and LDR both transfer files from remote CME.



Step 1: Download the Required Software Packages

To download the required packages:

1. In your browser, enter the following URL:

http://www-03.ibm.com/servers/aix/products/aixos/linux/download.html

2. From the AIX Toolbox for Linux Applications page, download the following files according to the instructions to each Netcool/Proviso system where SFTP is to be used:

— prngd — Pseudo Random Number Generation Daemon (prngd-0.9.29-1.aix5.1.ppc.rpm or later).

— zlib — zlib compression and decompression library (zlib-1.2.2-4.aix5.1.ppc.rpm or later).

3. From the AIX Toolbox for Linux Applications page, click the AIX Toolbox Cryptographic Content link.

4. Download the following files to each Netcool/Proviso system where SFTP is to be used:

— openssl-0.9.7g-1.aix5.1.ppc.rpm or later


http://sourceforge.net/projects/openssh-aix

6. From the OpenSSH on AIX page, search for and download the following files according to the instructions to each Netcool/Proviso system where SFTP is to be used:

— openssh-4.1p1_53.tar.Z or later

Step 2: Install the Required Packages

To install the required packages on each Netcool/Proviso system where SFTP is to be used:

1. Log in to the system as root.

2. Change your working directory to the location where the software packages have been downloaded by using the following command:

# cd /download/location

3. Run the RPM Packaging Manager for each package, in the specified order, using the following commands:

# rpm -i zlib

# rpm -i prndg

# rpm -i openssl

4. Uncompress and untar the openssh tar file by entering the following commands:

$ uncompress openssh-4.1p1_53.tar.Z

$ tar xvf openssh-4.1p1_53.tar

5. Using the System Management Interface Tool (SMIT), install the openssh package.

6. Exit from SMIT.

Step 3: Configure OpenSSH Server to Start Up on System Boot

After installing the OpenSSH server and client, you must configure the OpenSSH server to start up on system boot. To configure the server to start on system boot, modify the /etc/rc.d/rc2.d/Ssshd init script as follows:



#! /usr/bin/sh # # start/stop the secure shell daemon

case "$1" in 'start') # Start the ssh daemon if [ -x /usr/local/sbin/sshd ]; then echo "starting SSHD daemon" /usr/local/sbin/sshd & fi ;;

'stop') # Stop the ssh daemon kill -9 `ps -eaf | grep /usr/local/sbin/sshd | grep -v grep | awk '{print $2}' | xargs` ;; *) echo "usage: sshd {start|stop}" ;;

Solaris Systems

OpenSSH is required for SFTP to work with Netcool/Proviso. The version of SSH installed with the Solaris 10 operating system is not supported.

Note: The following sections refer to the current version of the required packages. Refer to the OpenSSH documentation for information about updated versions.

To install OpenSSH on Solaris systems, follow these steps:

• Step 1: Download the Required Software Packages on page 216.

• Step 2: Install the Required Software Packages on page 217.

• Step 3: Configure OpenSSH Server to Start Up on System Boot on page 218.

Step 1: Download the Required Software Packages

To download the required packages:


http://www.sunfreeware.com

2. From the Freeware for Solaris page, follow the instructions to download the following files to each Netcool/Proviso system where SFTP is to be used. Ensure that you download the correct files for your version of Solaris.

— gcc — Compiler. Ensure that you download the full Solaris package and not just the source code (gcc-3.2.3-sol9-sparc-local.gz or later).

— openssh — SSH client (openssh-4.5p1-sol-sparc-local.gz or later).

— openssl — SSL executable files and libraries (openssl-0.9.8d-sol9-sparc-local.gz or later).

— zlib — zlib compression and decompression library (zlib-1.2.3-sol9-sparc-local.gz or later).



Step 2: Install the Required Software Packages

To install the required packages, do the following on each Netcool/Proviso system where SFTP is to be used:


2. Change your working directory to the location where the software packages have been downloaded using the following command:

# cd /download/location

3. Copy the downloaded software packages to /usr/local/src, or a similar location, using the following commands:

# cp gcc-version-sparc-local.gz /usr/local/src

# cp zlib-version-sparc-local.gz /usr/local/src

# cp openssl-version-sparc-local.gz /usr/local/src

# cp openssh-version-sparc-local.gz /usr/local/src

4. Change your working directory to /usr/local/src using the following command:

# cd /usr/local/src

5. Install the gcc compiler:

5-a. Uncompress gcc using the following command:

gunzip gcc-version-sparc-local.gz

5-b. Add the gcc package using the following command:

pkgadd -d gcc-version-sparc-local

6. Install the zlib compression library:

6-a. Uncompress zlib using the following command:

gunzip zlib-version-sparc-local.gz

6-b. Add the zlib package using the following command:

pkgadd -d zlib-version-sparc-local

7. Install the OpenSSL executable and binary files:

7-a. Uncompress OpenSSL using the following command:

gunzip openssl-version-sparc-local.gz

7-b. Add the OpenSSL package using the following command:

pkgadd -d openssl-version-sparc-local

8. Install the OpenSSH client:

8-a. Uncompress OpenSSH using the following command:

gunzip openssh-version-sparc-local.gz

8-b. Add the OpenSSH package using the following command:

pkgadd -d openssh-version-sparc-local

8-c. Create a group and user for sshd using the following commands:

groupadd sshd

useradd -g sshd sshd

9. Optional: Remove Sun SSH from the path and link OpenSSH:



9-a. Change your working directory to /usr/bin using the following command:

cd /usr/bin

9-b. Move the Sun SSH files and link the OpenSSH files using the following commands:

# mv ssh ssh.sun

# mv ssh-add ssh-add.sun

# mv ssh-agent ssh-agent.sun

# mv ssh-keygen ssh-keygen.sun

# mv ssh-keyscan ssh-keyscan.sun

# ln -s /usr/local/bin/ssh ssh

# ln -s /usr/local/bin/ssh-add ssh-add

# ln -s /usr/local/bin/ssh-agent ssh-agent

# ln -s /usr/local/bin/ssh-keygen ssh-keygen

# ln -s /usr/local/bin/ssh-keyscan ssh-keyscan

Step 3: Configure OpenSSH Server to Start Up on System Boot

After installing the OpenSSH server and client, you must configure the OpenSSH server to start up on system boot. To configure the server to start on system boot:

1. Create or modify the /etc/init.d/sshd init script as follows:

#! /bin/sh # # start/stop the secure shell daemon

case "$1" in 'start') # Start the ssh daemon if [ -x /usr/sbin/sshd ]; then echo "starting SSHD daemon" /usr/sbin/sshd & fi ;;

'stop') # Stop the ssh daemon /usr/bin/pkill -x sshd ;;

*) echo "usage: /etc/init.d/sshd {start|stop}" ;;

2. Check that /etc/rc3.d/S89sshd exists (or any sshd startup script exists) and is a soft link to /etc/init.d/sshd.

If not, create it using the following command:

ln -s /etc/init.d/sshd /etc/rc3.d/S89sshd



Linux Systems

OpenSSH is required for VSFTP to work with Netcool/Proviso.OpenSSH is installed by default on any RHEL system.

Configuring OpenSSH

This section describes how to configure the OpenSSH server and client.

Configuring the OpenSSH Server

To configure the OpenSSH Server, follow these steps on each Netcool/Proviso system where SFTP is to be used:


2. Change your working directory to the location where the OpenSSH Server was installed (/usr/local/etc/sshd_config by default) using the following command:

# cd /usr/local/etc

3. Using the text editor of your choice, open the sshd_config file. This is an example of a sshd_config file:

#***************************************************************************

# sshd_config

# This is the sshd server system-wide configuration file. See sshd(8)

# for more information.

# The strategy used for options in the default sshd_config shipped with

# OpenSSH is to specify options with their default value where

# possible, but leave them commented. Uncommented options change a

# default value.

Port 22

Protocol 2

ListenAddress 0.0.0.0

HostKey /usr/local/etc/ssh_host_dsa_key

SyslogFacility AUTH

LogLevel INFO

PubkeyAuthentication yes

AuthorizedKeysFile .ssh/authorized_keys

RhostsAuthentication no

RhostsRSAAuthentication no

HostbasedAuthentication no

PasswordAuthentication yes

ChallengeResponseAuthentication no

Subsystem sftp /usr/local/libexec/sftp-server



#****************************************************************

4. Locate the Protocol parameter. For security purposes, it is recommended that this parameter is set to Protcol 2 as follows:

Protocol 2

5. Locate the HostKeys for protocol version 2 parameter and ensure that it is set as follows:

HostKey /usr/local/etc/ssh_host_dsa_key

6. Locate the PubkeyAuthentication parameter and ensure that it is set as follows:

PubkeyAuthentication yes

7. Locate the PasswordAuthentication parameter and ensure that it is set as follows:

PasswordAuthentication yes

8. Locate the Subsystem parameter and ensure that the SFTP subsystem and path are correct. Using defaults, the Subsystem parameter appears as follows:

Subsystem sftp /usr/local/libexec/sftp-server

Configuring OpenSSH Client

The OpenSSH client requires no configuration if it used in its default form. The default location for the OpenSSH client file is /usr/local/etc/ssh_config.

Generating Public and Private Keys

By default, OpenSSH generates public and private keys for the root user. You must generate public and private keys with the Netcool/Proviso user for the SFTP functions to work in Netcool/Proviso.

To generate public and private keys:

1. Log in as pvuser on the node that will be the SFTP client. This node is referred to as SFTPclient in these instructions, but you must replace SFTPclient with the name of your node.

2. Create an .ssh directory in the home directory of the Netcool/Proviso user, set permissions to x/r/w for owner (700), then change to the directory using the following commands:

$ mkdir ~/.ssh $ chmod 700 ~/.ssh $ cd ~/.ssh

3. Generate a DSA public and private key with no passphrase (DSA encryption is used as an example). The following example shows a UNIX server called SFTPclient:

$ /usr/local/bin/ssh-keygen -t dsa -f SFTPclient -P ""

Generating public/private dsa key pair. Your identification has been saved in SFTPclient. Your public key has been saved in SFTPclient.pub. The key fingerprint is: 77:67:2f:34:d4:2c:66:db:9b:1f:9a:36:fe:c7:07:c6 pvuser@SFTPclient

4. The previous command generates two files, SFTPclient (the private key) and SFTPclient.pub (the public key). Copy the private key to id_dsa in the ~/.ssh directory by entering the following command:

$ cp -p ~/.ssh/SFTPclient ~/.ssh/id_dsa

id_dsa identifies the node when it contacts other nodes.



5. To permit Netcool/Proviso components on SFTPclient to communicate, you must append the contents of the SFTPclient.pub key file to the file authorized_keys in the ~/.ssh directory by using the following commands:

cd ~/.ssh

cat SFTPclient.pub >> authorized_keys

6. Log on to the other node that will be the SFTP server. This node is referred to as SFTPserver in these instructions, but you must replace SFTPserver with the name of your node.

7. Repeat Step 1 through Step 5 on the SFTPserver node, replacing SFTPclient with SFTPserver.

8. Copy (with FTP, scp, or a similar utility) the public key from SFTPclient to SFTPserver and append the contents of the key file to the file authorized_keys in the ~/.ssh directory. If you cut and paste lines, be careful not to introduce carriage returns.

Use the following FTP session as an example:

SFTPserver:~/.ssh> ftp SFTPclient Connected to SFTPclient. 220 SFTPclient FTP server (SunOS 5.8) ready. Name (SFTPclient:pvuser): pvuser 331 Password required for pvuser. Password:

230 User pvuser logged in. ftp> bin 200 Type set to I. ftp> get .ssh/SFTPclient.pub 200 PORT command successful. 150 Binary data connection for .ssh/SFTPclient.pub 226 Binary Transfer complete. local: .ssh/SFTPclient.pub remote: .ssh/SFTPclient.pub ftp> quit 221 Goodbye. SFTPserver:~/.ssh> cat SFTPclient.pub >> authorized_keys

9. Optional: If you want to set up bidirectional SFTP, repeat Step 8, but from the SFTserver node to the SFTPclient node.

Note: This step is not needed for Netcool/Proviso.

Use the following FTP session as an example:

SFTPclient:~/.ssh> ftp SFTPserver Connected to SFTPserver. 220 SFTPserver FTP server (SunOS 5.8) ready. Name (SFTPserver:pvuser): pvuser 331 Password required for pvuser. Password: 230 User pvuser logged in. ftp> bin 200 Type set to I. ftp> get .ssh/SFTPserver.pub 200 PORT command successful. 150 Binary data connection for .ssh/SFTPserver.pub 226 Binary Transfer complete. local: .ssh/SFTPserver.pub remote: .ssh/SFTPserver.pub ftp> quit 221 Goodbye. SFTPclient:~/.ssh> cat SFTPserver.pub >> authorized_keys

10. When finished, the SFTPclient and SFTPserver should look similar to the following:



SFTPclient:~/.ssh> ls -al ~/.ssh total 10

drwx------ 2 pvuser pvuser 512 Nov 25 16:56 . drwxr-xr-x 28 pvuser pvuser 1024 Nov 25 15:25 .. -rw------- 1 pvuser pvuser 883 Nov 25 15:21 id_dsa -rw-r--r-- 1 pvuser pvuser 836 Nov 25 16:33 known_hosts

SFTPserver:~/.ssh> ls -al ~/.ssh total 10

drwx------ 2 pvuser pvuser 512 Nov 25 16:56 . drwxr-xr-x 28 pvuser pvuser 1024 Nov 25 15:25 .. -rw------- 1 pvuser pvuser 883 Nov 25 15:21 id_dsa -rw-r--r-- 1 pvuser pvuser 836 Nov 25 16:33 known_hosts

The important files are:

— authorized_keys, which contains the public keys of the nodes that are authorized to connect to this node

— id_dsa, which contains the private key of the node it is on

— known_hosts, which contains the public keys of the node that you want to connect to

For security, the private key (id_dsa) should be -rw------. Likewise, the public key Node<number>.pub, authorized_keys, and known_hosts should be -rw-r--r--.

The directory itself should be -rwx-----.

Note: The directory that contains the .ssh directory might also need to be writable by owner.

11. The first time you connect using SSH or SFTP to the other node, it will ask if the public key fingerprint is correct, and then save that fingerprint in known_hosts. Optionally, you can manually populate the client’s known_hosts file with the server’s public host key (by default, /usr/local/etc/ssh_host_dsa_key.pub).

For large-scale deployments, a more efficient and reliable procedure is:

11-a. From one host, ssh to each SFTP server and accept the fingerprint. This builds a master known_hosts file with all the necessary hosts.

11-b. Copy that master file to every other SFTP client.

Note: If the known_hosts file has not been populated and secure file transfer (SFTP) is attempted through Netcool/Proviso, SFTP fails with vague errors.

Testing OpenSSH and SFTP

For the following tests, the commands normally work without asking for a password. If you are prompted for a password, public/private key encryption is not working.

Ensure that you specify the full path to the ssh and sshd binary files. Otherwise, you might use another previously installed SSH client or server.

To test OpenSSH and SFTP:

1. On both nodes, kill any existing sshd processes and start the sshd process from the packages you installed, by entering the following commands:



pkill -9 sshd /usr/local/sbin/sshd &

The path can be different depending on the installation.

2. From SFTPclient, run the following command:

/usr/local/bin/ssh SFTPserver

3. From SFTPclient, run the following command:

/usr/local/bin/sftp SFTPserver

4. Optional: If you set up bidirectional SFTP, run the following command from SFTPserver:

/usr/local/bin/ssh SFTPclient

5. Optional: If you set up bidirectional SFTP, run the following command from SFTPserver:

/usr/local/bin/sftp SFTPclient

6. If all tests allow you to log in without specifying a password, follow the Netcool/Proviso instructions on how to enable SFTP in each Netcool/Proviso component. Make sure to specify the full path to SSH in the Netcool/Proviso configuration files. In addition, make sure the user that Netcool/Proviso is run as is the same as the user that you used to generate keys.

Troubleshooting

If you find that OpenSSH is not working properly with public keys:

1. Check the ~/known_hosts file on the node acting as the SSH client and make sure the client host name and IP information is present and correct.

2. Check the ~/authorized_keys file on the node acting as the SSH server and make sure that the client public key is present and correct. Ensure that the permissions are -rw-r--r--.

3. Check the ~/id.dsa file on the node acting as the SSH client and make sure that the client’s private key is present and correct. Ensure that the permissions are -rw-------.

4. Check the ~/.ssh directory on both nodes to ensure that the permissions on the directories are -rwx------.

5. Check for syntax errors (common ones are misspelling authorized_keys and known_hosts without the “s” at the end). In addition, if you copied and pasted keys into known hosts or authorized keys files, you probably have introduced carriage returns in the middle of a single, very long line.

6. Check the ~ (home directory) permissions to ensure that they are only writable by owner.

7. If the permissions are correct, kill the sshd process and restart in debug mode as follows:

pkill -9 sshd /usr/local/sbin/sshd -d

8. Test SSH again in verbose mode on the other node by entering the following command:

/usr/local/bin/ssh -v SFTPserver

9. Read the debugging information about both client and server and troubleshoot from there.

10. Check the log file /var/adm/messages for additional troubleshooting information.



Netcool/Provisio SFTP Errors

In the Netcool/Proviso log files, you might see the following errors:

• [DC10120] FTPERR error: incompatible version, result: sftp status: SSH2_FX_FAILURE:: incompatible version, log:

This error indicates that the SSH server (sshd) is SSH2 rather than OpenSSH. OpenSSH is required for Netcool/Proviso to function correctly.

• [DC10120] FTPERR error: bad version msg, result: sftp status: SSH2_FX_NO_CONNECTION:: connection not established - check ssh configuration, log:

This error indicates that the SSH configuration is incorrect or the wrong version of the SSH server (sshd) is running. OpenSSH is required for Netcool/Proviso to function correctly.


Appendix H: LDAP Integration

This chapter provides detailed information on how to configure LDAP (Lightweight Directory Access Protocol) as a default authentication/authorization mechanism for Netcool/Proviso. The topics are as follows:

LDAP Configuration

The configuration of LDAP as a default authentication and authorization mechanism for Netcool/Proviso is achieved using the topology editor.

Step 1: Enable LDAP Configuration

The LDAP configuration option becomes available when adding a Tivoli Integrated Portal to your topology using the Topology Editor.

Note: The process of adding a Tivoli Integrated Portal to the topology using the Topology Editor is described in Add a Tivoli Integrated Portal on page 92.

To enable LDAP configuration:

1. When editing the Add New TIP Wizard Page, select the LDAP Configuration check box, as described in Step 4, of Add a Tivoli Integrated Portal on page 92.

2. Click Next. This displays the LDAP Properties Page.

3. In the LDAP Properties Page dialog, enter the LDAP connection details. This requires that you populate the following fields:

— Administrative User Name: This is the name you have registered as the Tivoli Integrated Portal user. For example, “tipadmin”.

— Bind Distinguished Name: This username specified must have read and write permissions in LDAP 3. Typically this will be an LDAP administrator username. For example “cn=Directory Manager”.

— Bind Password: This is the password for the Bind Distinguished Name specified.

— LDAP Server Hostname: This is the LDAP server host name. Should this LDAP server exist behind a firewall, make sure that this host has been authenticated.

— LDAP Server Port Number: For example, “1389”.

— LDAP Repository Identifier: This is a string used to identify the LDAP repository, which can be set to the string of your choice.

Topic Page

LDAP Configuration 225



4. Click Finish.

Step 2: Setting LDAP Properties in the Topology Editor

In the Logical view of the Topology Editor:

1. Select the Tivoli Integrated Portal on which you have enabled LDAP.

2. Select the Properties tab.

3. Make sure CHOSEN_INSTALL_SET is set to advance.

Step 3: Setting LDAP Advanced Properties in the Topology Editor

At this point you need to contact the LDAP administrator in order to get LDAP suffixes for Group, PersonAccount, OrgContainer entity types, and do the following:

1. Select the Tivoli Integrated Portal on which you have enabled LDAP.

2. Select the Advance Properties tab.

3. Set the following:

• IAGLOBAL_LDAP_GROUP_ENTITY: This should be set to “Group”.

• IAGLOBAL_LDAP_GROUP_SUFFIX: This should be set to the suffix values for “Group”, which can be obtained from your LDAP administrator. For example, "ou=Groups,dc=state,dc=us,dc=ibm,dc=com".

• IIAGLOBAL_LDAP_ORG_ENTITY: This should be set to “OrgContainer”.

• IAGLOBAL_LDAP_ORG_SUFFIX: This should be set to the suffix values for “OrgContainer”, which can be obtained from your LDAP administrator. For example, "dc=state,dc=us,dc=ibm,dc=com".

• IAGLOBAL_LDAP_USER_ENTITY: This should be set to “PersonAccount”.

• IAGLOBAL_LDAP_USER_SUFFIX: This should be set to the suffix values for “PersonAccount”, which can be obtained from your LDAP administrator. For exmaple, "ou=People,dc=state,dc=us,dc=ibm,dc=com".

• IAGLOBAL_LDAP_BASE_ENTRY: This should be set with the base suffix values. For exmaple, "dc=cork,dc=ie,dc=ibm,dc=com".

Step 4: Configuring LDAP entity types in a federated repository configuration

This step must be carried out before installation of DataView. The deployment must be stopped before point at which DataView is installed and this configuration must be carried out.

Local Tivoli Integrated Portal server installation:

For Tivoli Integrated Portal instance hosted on the same server as the Primary Deployer do the following:

1. Enter the commands:

cd <DEPLOYER_HOME>/proviso/bin/Util/ModifyTIPLDAPPackage/cp modifyVMMLDAP.jacl <TIP_HOME>/bin



where:

— <DEPLOYER_HOME> : deployer home folder , that is /opt/IBM/proviso/deployer/

— <TIP_HOME> : Tivoli Integrated Portal home folder , that is /opt/IBM/tivoli/tip

2. Enter the command

where:

— <RESPONSE_FILE> : absolute path to response file, that is/tmp/ProvisoConsumer/Plan/<host>/00001_TIP_step/runtime/tipInstall.cfg

Remote Tivoli Integrated Portal server installation:

Copy the content of ModifyTIPLDAPPackage and tipInstall.cfg from the main server to all Tivoli Integrated Portal instances that are part of distributed environment, by perform the following on each Tivoli Integrated Portal instance:



Note: To ensure the following command does not run off the page, carriage returns have been inserted. A back slash, “\", identifies where a carriage return has been added.


where:

— <DEPLOYER_HOME> : deployer home folder, that is /opt/IBM/proviso/deployer/

— <TIP_HOME> : Tivoli Integrated Portal home folder, that is /opt/IBM/tivoli/tip


where:

— <RESPONSE_FILE> : absolute path to response file, that is /tmp/ldap/tipInstall.cfg

When these steps have finished you can carry on with the DataView deployment.

Step 5: Verifying the DataView installation

When the DataView installation is complete, it should have created two users and two groups in LDAP:

java -jar /usr/ibm/common/acsi/lib/ant-launcher.jar -f changeLDAP.xml -DINPUT_RESPONSE_FILE=<RESPONSE_FILE>

mkdir /tmp/ldap/cd /tmp/ldap

scp user@mainserver:/<DEPLOYER_HOME>/proviso/bin/Util/ \ ModifyTIPLDAPPackage/* /tmp/ldap

scp user@mainserver:/tmp/ProvisoConsumer/Plan/<host>/00001_TIP_step/ \

runtime/tipInstall.cfg /tmp/ldap/

cp modifyVMMLDAP.jacl <TIP_HOME>/bin

java -jar /usr/ibm/common/acsi/lib/ant-launcher.jar -f changeLDAP.xml

-DINPUT_RESPONSE_FILE=<RESPONSE_FILE>



Users:

• tnpm

• tnpmScheduler

Groups:

• tnpmUsers

• tnpmAdministrators

Verify from the UI that the users tnpm and tnpmScheduler are members of the tnpmAdministrators group.

Step 6: Assigning TNPM roles to LDAP users

To successfully authenticate you LDAP user you need to assign them to one of the following roles:

• tnpmUser

• tnpmAdministrator

This can be done by tipadmin user, by navigating to Users and Groups -> Administrative User Roles, and assigning the correct roles.


Appendix I: Deployer CLI Options

To run the deployer from the command line, entering the following command:

# ./deployer.bin [options]

For example, the following command performs a minimal deployment installation:

# ./deployer.bin -Daction=poc

The deployer.bin command accepts the following options:

Option Description

-Daction=mib Used with -Daction=poc to complete a minimal deployment installation on an AIX system.

-Daction=patch Performs a patch installation of Netcool/Proviso. See Appendix K, Installing an Interim Fix for more information.

-Daction=poc Performs a minimal deployment installation. See Chapter 5, Installing Netcool/Proviso as a Minimal Deployment for more information.

-Daction=resume Resumes an interrupted installation at the current step. Note that this option is possible only when the /tmp/ProvisoConsumer directory is available. See Resuming a Partially Successful First-Time Installation on page 104 for more information.

-Daction=uninstall Uninstalls all components marked “To Be Removed” in the current topology file. See Uninstalling Entire Netcool/Proviso System on page 150 for more information.

-DCheckUser Specifies whether the deployer checks to see if it is running as root before performing install operations. Possible values are true and false. For most install scenarios, running the deployer as the operating system root is required. You can use this option to override root user checking. Default is true.

-DOracleClient=oracle_client_home Enables you to specify the Oracle client home, so the wizard screen that prompts you for that information is skipped.

-DOracleServerHost=hostname Specifies the hostname or IP address where the Oracle server resides.

-DOracleServerPort=port Specifies the communication port used by the Oracle server. Default is 1521.

-DOracleSID=sid Specifies the Oracle server ID. Default is PV.



For detailed information about the deployer, see The Deployer on page 76.

-DOracleAdminUser=admin_user Specifies the administrator username for the Oracle server. Default is PV_INSTALL.

-DOracleAdminUser=admin_password Specifies the administrator password for the Oracle server. Default is PV.

-DPrimary=true Indicates that the deployer is running on the primary server. This option is used by the Topology Editor to invoke the deployer. Use this option to force a channel configuration update in the database.

-DTarget=id Instructs the deployer to install or uninstall the component specified using the id parameter, regardless of the current status of the component in the topology.Use this option to force an install or uninstall of a component in a high-availability (HA) environment, or when fixing an incomplete or damaged installation.Table 16 on page 231 contains a list of possible values for the id parameter.

-DTopologyFile=topology_file_path Tells the deployer to use the specified topology file instead of prompting for the file.

-DTrace=true Causes the deployer to log additional diagnostic information.

-DUsehostname=hostname Enables you to override the hostname that the deployer uses to define where it is running. This option is useful when hostname aliasing is used and none of the hostnames listed in the topology.xml file match the hostname of the machine where the deployer is running.

Option Description



Using the -DTarget Option

You can use the -DTarget option to force an install or uninstall of a component in a high-availability (HA) environment, or when fixing an incomplete or damaged installation. The -DTarget option uses the following syntax:

deployer.bin -DTarget=id

where id is a supported target identifier code.

If you are using the -DTarget option to force the uninstall of a component, you must also specify the -Daction=uninstall option when you run the deployer application. The following example shows how to force the uninstallation of DataMart on the local system:

deployer.bin -Daction=uninstall -DTarget=DMR

Table 16 shows the possible values for the id parameter.

Table 16: Target Identifier Codes

Value Description

DB Instructs the deployer to install the database setup components on the local machine.

DM Instructs the deployer to install the DataMart component on the local machine.

DV Instructs the deployer to install the DataView component on the local machine.

DC Instructs the deployer to install the DataChannel component on the local machine.

DL Instructs the deployer to install the DataLoad component on the local machine.

TIP Instructs the deployer to install TIP on the local machine.

DBR Instructs the deployer to remove the database setup components from the local machine. Requires the -Daction=uninstall option.

DMR Instructs the deployer to remove the DataMart component from the local machine. Requires the -Daction=uninstall option.

DVR Instructs the deployer to remove the DataView component from the local machine. Requires the -Daction=uninstall option.

DCR Instructs the deployer to remove the DataChannel component from the local machine. Requires the -Daction=uninstall option.

DLR Instructs the deployer to remove the DataLoad component from the local machine. Requires the -Daction=uninstall option.

TIPR Instructs the deployer to remove TIP fromthe local machine. Requires the -Daction=uninstall option.

DBU Instructs the deployer to upgrade the database setup components on the local machine.

DMU Instructs the deployer to upgrade the DataMart component on the local machine.

DVU Instructs the deployer to upgrade the DataView component on the local machine.

DCU Instructs the deployer to upgrade the DataChannel component on the local machine.

DLU Instructs the deployer to upgrade the DataLoad component on the local machine.



When you run the deployer using the -DTarget option, note the following:

• The deployer does not perform component registration in the versioning tables of the database.

• The deployer does not upload modified topology information to the database.

• The deployer does not allow you to you select other nodes besides the local node in the Node Selection panel.

• In the case of an uninstall, the deployer does not remove the component from the topology.


Appendix J: Using Silent Mode

This appendix describes how to use silent mode to run the deployer or to install the Topology Editor. The topics are as follows:

Sample Properties Files

The Silent subdirectory under the directory that contains the deployer.bin file (for example, /opt/IBM/proviso/deployer/proviso/data/Silent), contains the following sample properties files:

• Fresh.properties runs the deployer in standard mode.

• POC.properties runs the deployer in minimal deployment mode.

• topologyEditor.properties runs the Topology Editor installation in silent mode.

The Deployer

This section describes how to run the deployer in silent mode. The topics are as follows:

• Running the Deployer in Silent Mode on page 233

• Status Messages on page 236

• Restrictions on page 236

Running the Deployer in Silent Mode

Use the Fresh.properties file to run the deployer in standard mode, or the POC.properties file to run the deployer in minimal deployment mode.

For example, to perform a silent fresh installation:

1. Log in as root.

2. Log in to the machine on which you want to run the silent installation.

3. In a text editor, open the Fresh.properties file and make the following edits:

Topic Page

Sample Properties Files 233

The Deployer 233

The Topology Editor 237



3-a. Set and verify that the Oracle client path is correct.

3-b. Set the DownloadTopology flag to True (1) or False (0).

3-c. If you set DownloadTopology flag to False, set the TopologyFilePath to the location of your topology.xml file.

3-d. If you are running the deployer application on the same system where the Topology Editor is installed, set the Primary flag to true.

3-e. Set and verify that the Database Access Information is correct.

3-f. Set and verify the PACKAGE_PATH variable for the relevant system:

On Solaris systems:<DIST_DIR>/proviso/SOLARIS

On AIX systems:<DIST_DIR>/proviso/AIX

On Linux systems:<DIST_DIR>/proviso/RHEL




Your edited file will look similar to the following:

3-g. Write and quit the file.

4. Change to the /opt/IBM/proviso/deployer directory.

#Oracle client JDBC driver path#------------------------------

OracleClient=/opt/oracle/product/10.2.0.4.0/jdbc/lib

#Download Topology from Proviso database

# 1 is true

# 0 is false#-------------

DownloadTopology=0

#Primary

# Specify if the configuration has to be updated

# Specify true if running the deployer on the same# system where the Topology Editor is installed.

# true or false

#-------------Primary=false

#Topology file

# If DownloadTopology=1 this parameter is ignored#-------------

TopologyFilePath=/tmp/ProvisoConsumer/Topology.xml

#Database access information

#---------------------------

OracleServerHost=lab238053OracleServerPort=1521

OracleSID=PV

OracleAdminUser=PV_INSTALLOracleAdminPassword=PV

#Check Prerequisites Flag(true/false)#Use true only for first time install

#-------------------------------------

CHECK_PREREQ=true

# Netcool/Proviso installation packages path

#---------------------------PACKAGE_PATH=/cdrom/SOLARIS

#Silver Stream installation packages path#-------------------------------------

SS_BUNDLE=/cdrom/exteNd40k




./deployer.bin –i silent –f propertyFileWithPath

For example:./deployer.bin –i silent –f /opt/IBM/proviso/deployer/proviso/data/Silent/Fresh.properties

Status Messages

To verify a successful installation, look for a zero status code and the following message in the /tmp/ProvisoConsumer/result.log file:

CMW3019I Silent installation completed.

If the installation fails, the log file will contain a non-zero code and the following messages:

CMW3018W An installation step has failed during silent installation.

CMW0007E Silent installation failed. Installer stopped.

If the installation fails:

1. Log in as root.


./deployer.bin -Daction=resume

The deployer displays the table of installation steps (see Installation Steps on page 78 for an overview of the steps table).

3. Select the step that failed and view the output messages. See Step Status Values on page 80 for information about debugging a failed step.

4. Correct the problem.

5. Continue the installation by following the instructions in Resuming a Partially Successful First-Time Installation on page 104.

Restrictions


• The silent deployer does not support remote installations. You must manually invoke the script on each machine.

• Silent resume is not supported. If you need to resume a partial silent installation, use the -Daction=resume option to complete the installation using graphical mode (the steps table). The step that originally failed might have been in the middle of a step sequence that cannot be re-created by a subsequent -i silent invocation.



The Topology Editor

You can also install the Topology Editor in silent mode. The Topology Editor is installed with the installer named installer.bin, located in:

On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/topologyEditor/Disk1/InstData/VM

On AIX systems:# cd <DIST_DIR>/proviso/AIX/Install/topologyEditor/Disk1/InstData/VM

On Linux systems:# cd <DIST_DIR>/proviso/RHEL/Install/topologyEditor/Disk1/InstData/VM


To install the Topology Editor in silent mode:

1. Log in as root to the server on which you want to run the silent installation.

2. Change to the directory that contains the deployer.bin file (for example, /opt/IBM/proviso/deployer), then change to the /proviso/data/Silent subdirectory.

3. Using a text editor, open the topologyEditor.properties file and make the following edits:

3-a. Set and verify that the Oracle client path is correct.

3-b. Set the DownloadTopology flag to True (1) or False (0).

3-c. If you set DownloadTopology flag to False, set the TopologyFilePath to the location of your topology.xml file.

3-d. Set and verify that the Database Access Information is correct.

3-e. Set and verify the PACKAGE_PATH variable.

3-f. Write and quit the file.


./installer.bin -i silent -f ..../silent/topologyEditor.properties




Appendix K: Installing an Interim Fix

This appendix describes how to install an interim fix (or patch) release of Netcool/Proviso. The topics are as follows:

Overview

Unlike major, minor, and maintenance releases, which are planned, patch releases (interim fixes and fix packs) are unscheduled and are delivered under the following circumstances:

• A customer is experiencing a “blocking” problem and cannot wait for a scheduled release for the fix.

• The customer’s support contract specifies a timeframe for delivering a fix for a blocking problem and that timeframe does not correspond with a scheduled release.

• Development determines that a patch is necessary.

Note: Patches are designed to be incorporated into the next scheduled release, assuming there is adequate time to integrate the code.

Installation Rules

Note the following installation rules for patch installations:

• Fixes for the Database and DataMart must be installed on that host.

• Fixes for the DataChannel, DataLoad and DataView can be installed remotely from the local host in a distributed system.

• Fix packs are installed on general availability (GA) products.

• Sequentially numbered fix packs can be installed on any fix pack with a lower number.

• Interim fixes must be installed on the absolute fix pack.

The patch installer verifies that your installation conforms to these rules.

Topic Page

Overview 239


Installing a Patch 240



Behavior and Restrictions

It is important to note that because the deployer does not support remote DataMart installations, the deployer grays out the any remote DataMart host on the node selection page.

The maintenance deployer must run locally on each DataMart host to apply a patch.

Before You Begin

A patch release updates the file system for the component that the patch is intended for and updates the versioning information in the database.

To verify that the versioning was updated correctly for the components in the database, you can run several queries both before and after the installation and compare the results. For detailed information, see the Netcool/Proviso Technical Note: Tools for Version Reporting document.

Installing a Patch

To install a patch:

1. You must have received or downloaded the maintenance package from IBM Support. The maintenance package contains the Maintenance Descriptor File, an XML file that describes the contents of the fix pack. Follow the instructions in the README for the fix pack release to obtain the maintenance package and unzip the files.

Note that for each tar.gz file, you must unzip them, and then un-tar them. For example:

gunzip filename.tar.gz

tar -xvf filename.tar

2. Log in as root.

3. Set and export your DISPLAY environment variable (see Setting Up a Remote X Window Display on page 9).

4. Start the patch deployer using one of the following methods:

From the launchpad:

4-a. Click the Start Tivoli Netcool/Proviso 5.2 Maintenance Deployer option in the list of tasks.

4-b. Click the Start Tivoli Netcool/Proviso 5.2 Maintenance Deployer link.


— Run the following command:

# ./deployer.bin -Daction=patch

5. The deployer displays a welcome page. Click Next to continue.


7. On the patch folder page, click Choose to select the patch you want to install.

8. Navigate to the directory that contains the files for the fix pack, and click into the appropriate directory. Click Select to select that directory, then click Next to continue.



9. A pop-up window asks whether you want to download the topology file. Click Yes.

10. Verify that all of the fields for the database connection are filled in with the correct values:

• Database hostname — Enter the name of the database host.

• Port — Specifies the port number used for communication with the database. The default value is 1521.

• Database user — Specifies the username used to access the database. The default value is PV_INSTALL.

• Database Password — Enter the password for the database user account (for example, PV).

• SID — Specifies the SID for the database. The default value is PV.

Click Next.

11. When the topology has been downloaded from the database, click Next.

12. The node selection window shows the target systems and how the files will be transferred. The table has one row for each machine where at least one Netcool/Proviso component will be installed. Verify the settings, then click Next to continue.

13. The deployer displays summary information about the installation. Review the information, then click Next.

The deployer displays the table of installation steps.

14. Run through each installation step just as you would for a normal installation.





Appendix L: Error Codes and Log Files

This appendix lists the Netcool/Proviso error messages and log files. The topics are as follows:

See Appendix M, Troubleshooting for information about troubleshooting problems with the Netcool/Proviso installation.

Error Codes

The following sections describe the error messages generated by:

• The deployer (page 243)

• The Topology Editor (page 254)

• InstallAnywhere (page 257)

Deployer Messages

Table 17 lists the error messages returned by the Netcool/Proviso deployer.

Topic Page

Error Codes 243

Log Files 259

Table 17: Deployer Messages

Error Code Description User Action

DataView Messages

GYMCI5000E A system command failed.A standard UNIX system command failed. These commands are used for standard system operations, such as creating directories, changing file permissions, and removing files.

See the installation log for more details.

GYMCI5002E The operating system is not at the prerequisite patch level.Some required operating system patches are not installed.

See the installation log for details. Install the required patches, then try the installation again.

GYMCI5003E The Oracle configuration file, tnsnames.ora, does not include an entry for SilverMaster.

Add an entry for SilverMaster to the tnsnames.ora file, then try the installation again.



GYMCI5004E The Oracle configuration file, tnsnames.ora, was not found.The tnsnames.ora file must be created and stored in the $TNS_ADMIN directory.

Ensure that the file exists in the correct location.

GYMCI5005E Unable to connect to the Oracle database. It is possible that a specified connection parameter is incorrect, or the Oracle server might not be available.

See the installation log for more details. Ensure that the connection parameters you are using are correct and that the Oracle server is up and running.

GYMCI5006E An error occurred while running the DVOptimizerToRule.sql script to initialize the database. It is possible that the Oracle database and listener are not running.

See the installation log for more details. Check that the database and listener are running.

GYMCI5007E An error occurred while trying to remove entries for a resource from a database table. It is possible that the Oracle database and listener are not running.


GYMCI5008E An error occurred while trying to remove version information from a database table.It is possible that the Oracle database and listener are not running.


GYMCI5009E An error occurred while reading the configuration file. The name of a parameter or the format of the file is incorrect.

Contact IBM Software Support.

GYMCI5010E The file system does not have sufficient free space to complete the installation.

See the installation log for more details. Ensure that you have sufficient space on the file system before retrying the installation.

GYMCI5011E The DataView license file is missing.The license file was not found, but this file should not be required. The installation log will contain more details of the error.


GYMCI5012E A configuration file or directory is missing. See the installation log for more details.

GYMCI5013E An error occurred while creating a configuration file. The file could not be created.The installer failed to create one of the required configuration files.


GYMCI5014E An error occurred while updating a configuration file. The file could not be modified.The installer failed to make a required modification to one of the configuration files.


DataMart Messages

GYMCI5101E The DataMart installation failed. See the DataMart installer logs for details.

Database Configuration Messages





GYMCI5201E The database installation failed. See the installation log for details.

See the root_install_dir/database/install/log/Oracle_SID/install.log file.

GYMCI5202E The database uninstallation script failed because of a syntax error. This script must be run as oracle. For example:./uninstall_db /var/tmp/PvInstall/ install.cfg.silent

Check the syntax and run the script again.

GYMCI5204E The database could not be removed because some Oracle environment variables are not correctly set. Some or all of the Oracle environment variables are not set (for example, ORACLE_HOME, ORACLE_SID, or ORACLE_BASE).

Check that all the required Oracle variables are set and try again.

GYMCI5205E An error occurred when trying to start the Oracle database.

See the Oracle alert file for possible startup errors. Resolve any problems reported in the log and try again.

GYMCI5206E An error occurred when trying to shut down the Oracle database.

See the Oracle alert file for possible shutdown errors. Resolve any problems reported in the log and try again.

GYMCI5207E An error occurred while querying the database to determine the data files that are owned by the database.

See the Oracle alert file for details of errors. You might need to manually delete Oracle data files using operating system commands.

DataChannel Messages

GYMCI5301E The database channel installation failed. See the installation log for details.

See the file root_install_dir/channel/install/log/Oracle_SID/install.log.

GYMCI5401E An error occurred while running a script. See the message produced with the error code for more details.

GYMCI5402E Unable to find an expected file. See the message produced with the error code for more details.

GYMCI5403E The data in one of the files is not valid. See the message produced with the error code for more details.

GYMCI5404E Unable to find an expected file or expected data. See the message produced with the error code for more details.

GYMCI5405E Scripts cannot function correctly because the LD_ASSUME_KERNEL variable is set.

Unset the variable and try again.

GYMCI5406E An action parameter is missing. See the message produced with the error code for more details.

GYMCI5407E An error occurred while processing the tar command.

See the message produced with the error code for more details.

GYMCI5408E The product version you are trying to install seems to be for a different operating system.






GYMCI5409E Unable to locate installed package information for the operating system.


GYMCI5410E A file has an unexpected owner, group, or permissions.


GYMCI5411E A problem was found by the PvCheck module when checking the environment.


GYMCI5412E The installation module failed. See the messages in standard error for more details.

GYMCI5413E The patch installation failed. See the messages in standard error for more details.

GYMCI5414E The remove action failed. See the messages in standard error for more details.

GYMCI5415E An unrecoverable error occurred while running the script.


Dataload Messages

GYMCI5501E An error occurred when running the script. See the message produced with the error code for more details.

GYMCI5502E Unable to find an expected file. See the message produced with the error code for more details.

GYMCI5503E The data in one of the files is not valid. See the message produced with the error code for more details.

GYMCI5504E Unable to find an expected file or expected data. See the message produced with the error code for more details.

GYMCI5505E Scripts cannot function correctly because the LD_ASSUME_KERNEL variable is set.

Unset the variable and try again.

GYMCI5506E An action parameter is missing. See the message produced with the error code for more details.

GYMCI5507E An error occurred while processing the tar command.


GYMCI5508E The product version you are trying to install seems to be for a different operating system.


GYMCI5509E Unable to locate installed package information for the operating system.


GYMCI5510E A file has an unexpected owner, group or permissions.


GYMCI5511E A problem was found by the PvCheck module when checking the environment.


GYMCI5512E The installation module failed. See the message produced with the error code for more details.





GYMCI5513E The patch installation failed. See the messages in standard error for more details.

GYMCI5514E The remove action failed. See the messages in standard error for more details.

GYMCI5515E An unrecoverable error occurred while running the script.


Prerequisite Checkers: Operating System

GYMCI6001E The syntax of the check_os script is not correct. The specified component does not exist.The syntax is: check_os PROVISO_COMPONENTwhere PROVISO_COMPONENT is DL, DC, DM, DB, or DV.

Correct the syntax and try again.

GYMCI6002E This version of IBM Tivoli Netcool/Proviso is not supported on the host operating system.

See the check_os.ini file for a list of supported operating systems.

GYMCI6003E The specified component does not exist or is not supported on this operating system.

Ensure that you have specified the correct component. If you have, the operating system must be upgraded before the component can be installed.

GYMCI6004E The operating system is not at the prerequisite patch level.Some required operating system patches are not installed.

Check the product documentation for a list of required patches. Apply any missing patches and try again.

GYMCI6005E The host operating system is not supported for this installation.

Perform the installation on a supported operating system.

GYMCI6006E In the /etc/security/limits file, some values are missing or incorrect. Values must not be lower than specified in the check_os.ini file.

Check the values in the check_os.ini and edit the default stanza in the /etc/security/limits file so that valid values are specified for all required limits.

Prerequisite Checkers: Database

GYMCI6101E The syntax of the check_db script is not correct. The syntax is:check_db [client - server] [new - upgrade] [ORACLE_SID or tnsnames.ora entry]

Correct the syntax and try again.

GYMCI6102E The host operating system is not supported for this installation.

Perform the installation on a supported operating system.

GYMCI6103E This version of the IBM Tivoli Netcool/Proviso database is not supported on the current version of the host operating system.

See the check_os.ini file for a list of supported operating system versions.

GYMCI6104E Some required Oracle variables are missing or undefined.

Check the Oracle users environment files (for example, .profile and .bash_profile).

GYMCI6105E An Oracle binary is missing or not valid. Ensure that Oracle is correctly installed.





GYMCI6106E The instance of Oracle installed on the host is not at a supported version.

Check the list of supported Oracle versions in the check_db.ini file.

GYMCI6107E Unable to contact the Oracle server using the tnsping utility with the specified ORACLE_SID.

Check that your Oracle listener is running on the database server. Start the listener if it is not running.

GYMCI6108E An Oracle instance is running on the host where you have requested a new server installation.

Check whether you have selected the correct host for a new Oracle server installation. If the selected host is correct, remove the existing Oracle instance first.

GYMCI6109E The number of bits (32 or 64) for the Oracle binary does not match the values defined in the check_db.ini file.

Check the list of supported Oracle versions in the check_db.ini file.

GYMCI6110E The installation method passed to the script is not valid. Valid installation methods are New and Upgrade.

Pass the New or Upgrade option to the script.

GYMCI6111E The installation type passed to the script is not valid. Valid installation methods are Client and Server.

Pass the Client or Server option to the script.

GYMCI6112E The script was run with options set for a new server installation, but an Oracle instance configuration file (init.ora) already exists for the specified SID. The presence of the init.ora file indicates the presence of an Oracle instance.

Check that a new server installation is the correct action for this SID. If it is, remove the existing Oracle instance configuration files.

GYMCI6113E A symbolic link was found in the Oracle home path. The Oracle home path cannot contain any symbolic links.

Remove any symbolic links. Specify the Oracle home path using only real directories.

GYMCI6114W Cannot contact the Oracle Listener. The tnsping utility was run to check the Oracle Listener status, but, the Listener could not be contacted.

Check that the Oracle Listener is running. Start it if necessary.

GYMCI6115E The Solaris semaphore and shared memory check failed. The sysdef command was used to check the values for semaphores and shared memory. The command did not report the minimum value for a particular semaphore or shared memory.

Check that the required /etc/system parameters are set up for Oracle. Check that the values of these parameters meet the minimum values listed in the check_db.ini file.

GYMCI6116E Could not find the bos.adt.lib package in the COMMITTED state. The package might not be installed.The package is either not installed or not in a COMMITTED state.

Ensure that the bos.adt.lib package is installed and committed and then try again.





GYMCI6117E Could not log in to the database. The verify base option was used. The option attempts to log into the database to ensure it is running. However, the script could not log in to the database.

Check that the database and Oracle Listener are up and running. If not, start them.

GYMCI6118E The checkextc script failed. The verify base option was used. The option runs the checkextc script to ensure external procedure calls can be performed.

Check that the Netcool/Proviso database was created properly.

GYMCI6119E The tnsnames.ora file is missing.A tnsnames.ora file in should exist in ORACLE_HOME/network/admin directory.

Check that the tnsnames.ora file exists in the ORACLE_HOME/network/admin directory. If it does not, create it.

Minimal Deployment: Post-Installation Messages

GYMCI7500E An internal processing error occurred in the script. Check the logs and the output from the script. Look for incorrect configuration or improper invocation.

GYMCI7501E The required configuration or messages files for the poc-post-install script are not in the same directory as the script. These files should be unpacked by the installer together with the script.

Check for errors that occurred during the installation steps.

GYMCI7502E An environment file is missing or is in the wrong location.

Check the poc-post-install configuration file. The missing environment file and expected path will be identified in the log file.

GYMCI7503E The SNMP DataLoad did not start. The SNMP DataLoad process (pvmd) failed to start.

Check the SNMP DataLoad log for errors during startup.

GYMCI7504E The network inventory failed. New devices cannot be discovered unless the inventory runs successfully.

Check the inventory log for errors. Ensure the DISC server and SNMP DataLoad (Collector) processes are running.

GYMCI7505E The Report Grouping operation failed.This action does not depend on any external application processes. The database must be running, and correct DataMart grouping rule definitions are required.

Check the inventory log file for more details of the Report Grouping failure.

GYMCI7506E The DataChannel command line failed.It is possible that the CNS, CMGR, and AMGR processes are not running.

Ensure that the required processes are running. Check the proviso.log for details of the failure.

GYMCI7507E The Report User was not created. The Web user will not be able to view reports. The DataMart resmgr utility is used to add this configuration to the database. It is possible that the database is not running.

Ensure that the database is running, and check for error logs in the DataMart logs directory.





GYMCI7508E Failed to associate a Report User to a group. The report user is associated with a group to allow the user to view reports. The DataMart resmgr utility is used to add this configuration to the database. It is possible that the database is not running.

Ensure that the database is running, and check for error logs in the DataMart logs directory. Ensure that the specified report group exists.

GYMCI7509E A report user could not be deleted from the database.

Check for error and trace logs in the DataMart logs directory.

GYMCI7510E Failed to create a Web User. The user will not be able to authenticate with the Web/application server.

Check the Web/application server log file for errors. Ensure that the Web/application server is running.

GYMCI7511E The Web group could not be created, and the Web user might not be properly configured to view reports.

Check the Web/application server log file for errors. Ensure that the Web/application server is running.

GYMCI7512E Failed to associate the Web User with a group. The Web user might not be properly configured to view reports unless successfully associated with a group.

Check the Web/application server log file for errors. Ensure that the Web/application server is running. This step relies on the database component only.

GYMCI7513E Failed to delete Web Users. Web user authentication was not removed.

Check the Web/application server logs.

GYMCI7514E The Channel Naming Service failed to start. Cross-application communication cannot function.

Check for walkback or error files in the DataChannel log or state directory.

GYMCI7515E The central LOG server failed to start. Logging for DataChannel will be unavailable.

Check for walkback or error files in the DataChannel log or state directory.

GYMCI7516E The Channel Manager failed to start. DataChannel applications cannot be started or stopped. Application status will be unavailable.

Check the proviso.log file for errors. Check for walkback or error files in the DataChannel log or state directory.

GYMCI7517E The Application Manager failed to start. DataChannel applications cannot be started or stopped. Application status will be unavailable.

Check the proviso.log file for errors. Check for walkback or error files in the DataChannel log or state directory.

GYMCI7518E Failed to create the DV user group. The DV user will remain in the Orphans group.

Check the poc-post-install log in /var/tmp for more details on the error condition.

GYMCI7519E Failed to associate the DV user to the DV group. The DV user will remain in the Orphans group.

Check the poc-post-install log in /var/tmp for more details on the error condition.

GYMCI7520E The Web Application server is not running or took too long to start up.

Start up the Web Application server as documented.

GYMCI7597E The MIB-II Technology Pack jar file was not found in the specified directory.

Add the MIB2 Technology Pack jar to the directory. Remove other jar files and try again.





GYMCI7598E Too many jar files are present in the specified directory.Only two jar file can be present in the directory: the ProvisoPackInstaller.jar and the MIB-II Technology Pack jar.

Remove the other jar files and try again.

GYMCI7599E The Technology Pack installer failed. Check the Technology Pack installer logs for details.

Installer Action Messages and IA Flow Messages

GYMCI9998E Unable to find a message for the key.The message was not retrieved from the message catalog.


GYMCI9999E An unknown error occurred for the component name with the error code code. The message could not be retrieved from the catalog.


GYMCI9001E An error occurred during installation. An exception has been generated during an installation step.


GYMCI9002E An unrecoverable error occurred when running the command command.


GYMCI9003E An unrecoverable error occurred while running a command.


GYMCI9004E An error occurred while connecting to the database.


GYMCI9005E An error occurred while performing a database operation.


GYMCI9006E Remote File Transfer has been disabled. To continue, change the step property to Allow Remote Execution and run the step again, or manually transfer the directory to the host. When the transfer is completed, change the step status to Success and continue the installation.

GYMCI9007E An error occurred while remotely connecting to target.There are connection problems with the host.


GYMCI9008E An error occurred while connecting to target. There are connection problems with the host.


GYMCI9009E An error occurred while copying install_dir. See the installation log for more details.





GYMCI9010E Remote Command Execution has been disabled. To continue:1. Change the step property to Set Allow Remote Execution.2. Run the step again.Or, manually transfer the directory to the host. When the transfer is completed, change the step status to Success and continue the installation.

GYMCI9011E An error occurred during file creation. See the installation log for more details.

GYMCI9012E An error occurred while loading the discovered topology file.


GYMCI9013E An error occurred while loading the topology file. See the installation log for more details.

GYMCI9014E The installation engine encountered an unrecoverable error.


GYMCI9015E An error occurred while saving the topology file. See the installation log for more details.

GYMCI9016E The installer cannot proceed with the installation because there is insufficient disk space on the local host.


GYMCI9017E The installer cannot download the topology from the specified database. Verify that the Netcool/Proviso database exists and that it has been started. If it does not exist, launch the installer, providing a topology file.

Ensure that the correct host name, port, and SID were specified and that the database has been started.

GYMCI9018E The installer cannot connect to the specified database indicated because of incorrect credentials.

Ensure that you provide the correct user name and password.

GYMCI9019W The installer could not establish a connection to the specified database. Check that the Netcool/Proviso database can be contacted. Click Next to proceed without checking the current environment status.

Check that the Netcool/Proviso database can be contacted.

GYMCI9020E The database connection parameters do not match those in the topology file.

Ensure that you provide the correct parameters.

GYMCI9021E An error occurred while loading the Oracle client jar.


GYMCI9022E The configuration file name was not found. The step cannot run.






GYMCI9023W There appear to be no differences between the desired topology state and the current state of the Netcool/Proviso installation.The installer shows this message when it determines there is not work that it can do. Normally, this occurs when the Netcool/Proviso system is already at the desired state. However, it can also occur when there are component dependencies that are not satisfied.


GYMCI9024E The operating system specified for this node in the topology file is not correct.

Correct the topology file.

GYMCI9025E The path is not valid or you do not have permissions to write to it.

Correct the parameter and try again.

GYMCI9026E The path is not a valid Oracle path. The sqlplus command could not be found.

Correct the parameter and try again.

GYMCI9027E The specified port is not valid. Correct the parameter and try again.

GYMCI9028E At least one parameter is null. Specify values for the required parameters.

GYMCI9029E The specified host name contains unsupported characters.

Ensure that host names include only supported characters.

GYMCI9030E The specified host cannot be contacted. Ensure that the host name is correct and check that the host is available.

GYMCI9031E The path not exists on the local system. Correct the path and try again.

GYMCI9032E An error occurred while saving the topology. It has not been uploaded to the Netcool/Proviso database. This error occurs when there is a database connection error or when the Netcool/Proviso database has not yet been created

See the log file for further details.

GYMCI9033E One of the following parameters must be set to 1: param1 param2

Check the log file for further details. Redefine the parameters and try again.

GYMCI9034E An error occurred while creating mount point directories.


GYMCI9035E An error occurred while changing the ownership or the group of mount point directories.


GYMCI9036E The machine hostname was not found in the Netcool/Proviso model (topology.xml file).The machine where the installer is running is not part of the Netcool/Proviso topology.

If a host name alias is used, make the machine host name match the host name in the model.Alternatively, use the option -DUsehostname=hostname to override the machine host name used by the installer.

GYMCI9037E The Deployer version you are using is not compatible with the component that you are trying to install.

Use a Deployer at a version that supports the deployment of the component you are trying to install.





Topology Editor Messages

Table 18 lists the error messages returned by the Topology Editor.

GYMCI9038E The XML file cannot be read or cannot be parsed. Ensure the file is not corrupted. See the log file for more details.

GYMCI9039E The deployment cannot proceed, because an error occurred the deployment plan was being generated.

See the log file for more details. Check that there is sufficient disk space and that the Deployer images are not corrupted.

GYMCI9040E The Deployer cannot manage the indicated component on the specified node.

See the log file for more details about the condition that was detected.

GYMCI9041E The user ID you specified is not defined on the target system.

Check that you have specified the correct user ID.

GYMCI9042E You specified a host that is running on an unsupported platform.

Check that you have specified the correct host name.

GYMCI9043E The value you specified is not supported. Specify one of the supported values.



Table 18: Topology Editor Messages


GYM0001E A connection error was caused by an SQL failure when running the report. Details are logged in the trace file.There is a connection problem with the database. Possible problems include:The database is not running.The database password provided when the engine was created is wrong or has been changed.

Check the error log and trace files for the possible cause of the problem. Check that the database is up and that the connection credentials are correct. Correct the problem and try the operation again.

GYMCI0000E Folder name containing technology pack metadata files was not found.The specified folder does not exist.

Ensure that you have the correct location for the technology pack metadata files and try the operation again.

GYMCI0001E An internal error, associated with the XML parser configuration, occurred.


GYMCI0002I No item has been found that satisfies the filtering criteria.

Ensure that you enter the correct filtering criteria and try the operation again.

GYMCI0003E An error occurred when reading XML file name.The XML file might be corrupt or in an incorrect format.

Ensure that you have selected the correct file and try the operation again.

GYMCI0004E The input value must be an integer. Correct the input value and try the operation again.

GYMCI0005E An unexpected element was found when reading the XML file.

Ensure that you have selected the correct file and try the operation again.



GYMCI0006E A value must be specified. Correct the input value and retry the operation.

GYMCI0007E The value must represent a log filter matching regular expression expression.

Correct the input value and try the operation again.

GYMCI0008E Metadata file name was not found.The specified file does not exist.

Ensure that you have the correct file name and path and retry the operation.

GYMCI0009E Metadata file name is corrupted. Contact IBM Software Support.

GYMCI0010E Metadata file name was already imported. Do you want to replace it?

Click Yes to replace the file or No to cancel the operation.

GYMCI0011E Object name was not found in the repository.The specified object does not exist.

Ensure that you have the correct object name and try the operation again.

GYMCI0012E The specified value must identify an existing directory.The specified directory does not exist.

Ensure that you have the correct directory name and try the operation again.

GYMCI0013E Removing object from host in Physical View. No user action required.

GYMCI0014E File name does not exist. Ensure that you have the correct file name and try the operation again.

GYMCI0015E An unexpected error occurred writing file name. See the trace file for details.

Ensure that there is sufficient space to write the file in the file system where the Topology Editor is running.

GYMCI0016E The user or password that you specified is wrong. Correct the login credentials and try the operation again.

GYMCI0017E The value specified for at least one of the following fields is not valid: host name, port, or SID.

Correct the input value or values and try the operation again.

GYMCI0018E The file name is corrupted. Select a valid XML file.

GYMCI0019E An unexpected error occurred when retrieving data from the database. See the trace file for details.

Ensure that the database is up and running and that you can connect to it.

GYMCI0020E An unexpected error occurred when parsing file name. See the trace file for details.

Select a valid XML file.

GYMCI0021E An unexpected error occurred. See the trace file for details.


GYMCI0022E The input value must be a boolean. Correct the input value and try the operation again.

GYMCI0023E The specified value must be one of the following operating systems: AIX, SOLARIS, or Linux.


GYMCI0024E The value must be a software version number in the format n.n.n or n.n.n.n. For example 7.1.2, or 7.1.2.1.


GYMCI0025E The value must be an integer in the range minValue to maxValue, inclusive.






GYMCI0026E The value must be a comma-separated list of strings.


GYMCI0027E The value must be a file size expressed in kilobytes. For example, 1024K.


GYMCI0028E The value must be a file size expressed in megabytes. For example, 512M.


GYMCI0029E The value must be a file size expressed in kilobytes or megabytes. For example 1024K or 512M.


GYMCI0030E The value must be an FTP or SFTP connection string. For example, ftp://username:password@hostname/directory.


GYMCI0031E The value must be a comma-separated list of directories. For example, /opt, /var/tmp, /home.


GYMCI0032E Value cannot be a fully-qualified domain name, IP address, or name containing hyphen or period.

Supply the unqualified host name without the domain. Do not use the IP address or a name that contains hyphens.

GYMCI0033E Metadata file name contains an technology pack with a wrong structure.


GYMCI0034E Value should be in the format YYYY-MM-DD, cannot be a date prior than 1970-01-01, or later than the current date.

Specify a date that is within the range and in the correct format.

GYMCI0035E The meta-data file contains an technology pack with the wrong structure.

Obtain a valid meta-data file and try again.

GYMCI0036E Value should be in the format YYYY-MM-DD, cannot be a date prior than 1970-01-01, or later than the current date.

Correct the input value and retry the operation.

GYMCI0037E The operation failed because the specified file does not exist.

Ensure that the file name and path you specified is correct and retry the operation.

GYMCI0038E The operation failed because of an error while validating the host name mappings file.

See the trace file for more details.

GYMCI0039E The host name retrieved by the upgrade process is not valid. Fully qualified host names, IP addresses and names containing hyphens or periods are not supported.

Correct the entry for the specified host name in the topology definition.

GYMCI0040E The upgrade process retrieved two entries for the specified host name. The fully qualified host name is not supported.

Remove the entry for the fully qualified host name.

GYMCI0040W The upgrade process did not retrieve a valid value for the specified property. A default value has been used.

Check that the default assigned is appropriate and change it if necessary.





InstallAnywhere Messages

Table 18 lists the InstallAnywhere™ error messages. These messages could be returned by either the deployer or the Topology Editor. See the InstallAnywhere documentation for more information about these error codes and how to resolve them.

GYMCI0041E No component is present on the specified host. Specify a host where at least one component is present.

GYMCI0042E The operation failed because the input value is not the correct data type. The correct data type is Long.


GYMCI0043E The operation failed because the input value is not valid.


GYMCI0044W The upgrade process did not retrieve a valid value for the specified property. A default value has been used.

Check that the default assigned is appropriate and change it if necessary.



Table 19: Install Anywhere Messages

Error Code Description

0 Success: The installation completed successfully without any warnings or errors.

1 The installation completed successfully, but one or more of the actions from the installation sequence caused a warning or a non-fatal error.

8 The silent installation failed because of step Error errors.

–1 One or more of the actions from the installation sequence caused a fatal error.

1000 The installation was cancelled by the user.

1001 The installation includes an invalid command-line option.

2000 Unhandled error.

2001 The installation failed the authorization check, may indicate an expired version.

2002 The installation failed a rules check. A rule placed on the installer itself failed.

2003 An unresolved dependency in silent mode caused the installer to exit.

2004 The installation failed because not enough disk space was detected during the execution of the Install action.

2005 The installation failed while trying to install on a Windows 64-bit system, but installation did not include support for Windows 64-bit systems.

2006 The installation failed because it was launched in a UI mode that is not supported by this installer.

3000 Unhandled error specific to a launcher.



3001 The installation failed due to an error specific to the lax.main.class property.

3002 The installation failed due to an error specific to the lax.main.method property.

3003 The installation was unable to access the method specified in the lax.main.method property.

3004 The installation failed due to an exception error caused by the lax.main.method property.

3005 The installation failed because no value was assigned to the lax.application.name property.

3006 The installation was unable to access the value assigned to the lax.nl.java.launcher.main.class property.

3007 The installation failed due to an error specific to the lax.nl.java.launcher.main.class property.

3008 The installation failed due to an error specific to the lax.nl.java.launcher.main.method property.

3009 The installation was unable to access the method specified in the lax.nl.launcher.java.main.method property.

4000 A Java executable could not be found at the directory specified by the java.home system property.

4001 An incorrect path to the installer jar caused the relauncher to launch incorrectly.

Table 19: Install Anywhere Messages

Error Code Description



Log Files

Several files are used to log errors for the Netcool/Proviso components and its underlying framework. These log files include:

• COI Log Files

• Deployer Log File

• Eclipse Log File

• Trace Log File

See Chapter 6, Installing Technology Packs for information about the technology pack log files.

COI Log Files

The Composite Offering Installer (COI) adds a layer called the COI Plan to the Netcool/Proviso installation. The COI Plan consists of a set of COI Machine Plans, one for each machine where Netcool/Proviso components should be installed. A COI Machine Plan is a collection of COI Steps to be run on the corresponding machine.

The COI Plan is created in the directory /tmp/ProvisoConsumer/Plan.

The COI provides the following log files:

Deployer Log File

Installation errors and messages are written to the file /tmp/ProvisoConsumer/log.txt. The log file supports two levels:

• High (FINEST) — This is the default and only setting.

Eclipse Log File

The Eclipse framework logs severe problems in a file under the Topology Editor installation directory (for example, /opt/IBM/Proviso/topologyEditor/workspace/.metadata). By default, the Eclipse log file is named .log. You should not need to look there unless there is a problem with the underlying Eclipse framework.

Table 20: COI Log Files

Log File Description Log File Location

MachinePlan_machinename_ [INSTALL_mmdd_hh.mm].log

For example:

MachinePlan_delphi_[INSTALL_0610_10.37].log

Contains detailed information about the tasks executed by the COI steps on the specified machine

/tmp/ProvisoConsumer/Plan/ MachinePlan_machinename/logs/

DeploymentPlan.log Contains high-level information about the COI Plan execution

tmp/ProvisoConsumer/Plan/ logs/INSTALL_mmdd_hh.mm



Trace Log File

The trace log file is located in the Topology Editor installation directory (for example, /opt/IBM/Proviso/topologyEditor). By default, this file is named topologyEditorTrace and the default trace level is FINE.

To change the trace level:

1. In the Topology Editor, select Window > Preferences. The Log Preferences window opens.

2. Select the new trace level. If desired, change the name of the log file.

3. Click Apply to apply your changes. To revert back to the default values, click Restore Defaults.

4. Click OK to close the window.


Appendix M: Troubleshooting

This appendix lists problems that might occur during an installation and how to resolve them. The problems are grouped by the interface or component exhibiting the problem. The topics are as follows:

See also Appendix L, Error Codes and Log Files.

Deployment Problems

Topic Page

Deployment Problems 261

Netcool/Proviso Component Problems 264

Topology Editor Problems 265

Telnet Problems 266

Java Problems 266

Testing Connectivity to the Database 266

Testing External Procedure Call Access 267

Problem Solution

The deployer window does not automatically become the focus window after launching from it from the Topology Editor.

Cause: In some cases (for example, when you export the display on a VNC session on Linux systems), the deployer window does not get the focus.User action:Click on the deployer window or move other windows to make the deployer window the focus window.

When the user tries to launch the Firefox browser an error is displayed regarding the Cairo 1.4.10 package:

Cause: Cairo 1.4.10 may not support the requested image format.User action:Start VNC server using the following command:/usr/bin/X11/vncserver -depth 24 -geometry 1280x1024



In a fresh installation, the database installation step fails.

Cause:You did not perform the necessary preparatory steps. User action:This step verifies that the Oracle Listener is working properly before actually creating the Netcool/Proviso database. If the step fails:1. Complete the necessary manual steps (see Configure the Oracle Listener on page 41).2. Change the status of the step to Ready.3. Resume the installation. The step should complete successfully.

An installation step hangs. Cause: There are many possible causes.User action:1. Make sure the installation step is really in a hung state. For example, the Netcool/Proviso database-related steps might take more than an hour to complete; other steps complete in far less time.2. Determine which child process is causing the hang. First, find the installer process by entering the following command:

ps -ef

The installer process has an entry similar to this one:

root 12899 7290 10 13:43:31 pts/7 0:10 /tmp/install.dir.12899/Solaris/resource/ jre/jre/bin/java -Djava.compiler=NONE -

Next, find the process that has that process number (for example, 12899) as its father. Continue until you find the last process. 4. Kill the last process using the following command:

kill -9

At this point, the status of the hung step will change to Error.5. If you can determine the cause of the hang, fix the problem and resume the installation. Otherwise, collect the log files and contact IBM for support.

The deployer hangs when displaying the Preview page. (This step normally takes only a few seconds).

Cause:The NFS file system is not working properly.User action:Run the df -k command and make sure that all NFS mounted file systems are working properly. When the problem has been corrected, restart the deployer.

There is a problem with remote command execution.

Cause:The deployer uses either RSH or OpenSSH to perform remote command execution. You must configure OpenSSH to make this connection possible. User action:After configuring OpenSSH, run the test program provided in deployer_root/proviso/data/Utils/testremote.sh to test your configuration, where deployer_root is the root directory for the deployer. For example:

/export/home/pvuser/443/SOLARIS/Install/ SOL9/deployer

Problem Solution



You specified a remote installation of DataMart even through it is not supported, making the remote host unavailable in the node selection page.

Cause:The remote host is marked as unavailable because remote installation of DataMart is not supported.User action:Start a secondary deployer on the host where you intend to install DataMart.

Installation messages report success, but might include messages similar to the following:

Fatal Error]:4:1: An invalid XML character (Unicode: 0x1b) was found in the element content of the document.

This is screen noise and can safely be ignored.

When you click the Done button to complete a fresh installation, the deployer displays database access error messages.

Cause:You stopped a fresh installation before the installing and configuring the Netcool/Proviso database.User action:If the Netcool/Proviso database has not been installed, complete the installation using the -Daction=resume option (see Resuming a Partially Successful First-Time Installation on page 104).

If the database has been installed, there is another problem. Contact IBM Software Support.

Data does not appear in real-time reports, and right-clicking on a real-time report does not display the option menu.

This problem can occur with a silent installation or a minimal deployment installation on a Solaris system.

Cause: When it starts, the channel manager (CMGR) places information in the database that is needed for real-time reports to start correctly. During installation, a cron job is created that starts CMGR. A silent installation might run fast enough that the cron job does not run before DataView is started. In this case, CMGR does not add the required information to the database, and real-time reports do not start up correctly.User action:1. Make sure that the CMGR process is running (see Management Programs and Watchdog Scripts on page 194 and Starting the DataChannel Management Programs on page 196).2. Restart DataView.

During Tivoli Integrated Portal install, the Deployment Engine failed to find pre-installed Tivoli Integrated Portal.

User action:1. Log in as root.2. Enter the following commands to restart the Deployment Engine:# cd /usr/ibm/common/acsi/bin

# ./acsisrv.sh -start

3. Check DE is running with the following command

# ./listIU.sh

This will list all IUs in the system.

Problem Solution



Saving Installation Configuration Files

When you install Netcool/Proviso components, the deployer creates a set of temporary configuration files that are used during the installation process. These files specify the components that are to be installed on a target system and the deployment information required to install them. You can use these configuration files to troubleshoot a Netcool/Proviso installation.

The temporary configuration files are normally removed from the target system when the deployer completes the installation process. You can prevent the deployer from removing the files by editing the installer XML file associated with a component. This file is named n_comp_name.xml, where n is an index number generated by the deployer and comp is a string that identifies the component. Possible values for the comp string are DataView, DataMart, DataView, DBChannel and DBSetup. Installer XML files are located by default in the /tmp/ProvisoConsumer/Plan/MachinePlan_hostname directory, where hostname is the host name of the target system.

To prevent the deployer from removing the temporary files associated with a component install, open the corresponding install XML file and modify the following element so that the value of the arg2 property is false:

<equals arg1="${remove.temporary.files}" arg2="true"/>

The following excerpt from the file shows the resulting XML element:

<equals arg1="${remove.temporary.files}" arg2="false"/>

When you contact IBM support about a Netcool/Proviso installation problem, the support staff might ask you for these files. You can create a tar file or zip archive that contains the entire contents of the /tmp/ProvisoConsumer directory and send it to the IBM support staff for assistance.

Netcool/Proviso Component Problems

Problem Solution

A Netcool/Proviso component is still listed as Configured in the Topology Editor even though it’s been installed.

Cause: The component is installed, but has not been started.User action:Start the component. Its status changes to Installed.

A new channel component was deployed, or the channel configuration was changed, but the change has no effect.

Cause: The channel components need to be bounced.User action:Bounce the components, as described in Appendix E, DataChannels.



Topology Editor Problems

$ DISPLAY=Host_IP_Address:0.0 $ export DISPLAY

Problem Solution

The Topology Editor won’t open and the application window shows a Java exception (core dump).

Cause: You forgot to set and export your DISPLAY variable. User action:1. Enter the following commands:

2. Restart the Topology Editor.

The splash screen for the Topology Editor is displayed, but the Topology Editor doesn’t start and no explanatory message is displayed.

Cause: You did not log in as root.User action:1. Log in as root.2. Restart the Topology Editor.

The topology editor reports the following error when you attempt to add a UBA collector:

GYMCI0504E An internal error occurred while processing file pack

where pack is the name of the application jar file.In addition, the topology editor log file contains the following error:

YYYY-MM-DD HH:MM:SS SEVERE FileHelper Manifest of file pack is corrupted. It was not possible to determine if its install type is bundle or standalone.

Cause:You tried to add a UBA collector for an SNMP technology pack.User action:Make sure that you read the Netcool/Proviso technology packs release notes before you install and configure a pack and before you add any collectors. The release notes contain information on whether a specific technology pack is a UBA or SNMP pack. UBA and SNMP packs require you to perform different configuration steps.Before you install and configure an technology pack, you must also read the information in Before You Begin on page 129 and follow the steps listed in that section.



Telnet Problems

Java Problems

Testing Connectivity to the Database

To test client connectivity to the Oracle database:

1. Make sure you are logged in as oracle and that the DISPLAY environment variable is set.


$ sqlplus system/[email protected]

In this syntax:

— password is the password you set for the Oracle system login name. (The default password is manager.)

— PV is the TNS name for your Netcool/Proviso database defined in your Oracle Net configuration.

Problem Solution

Telnet client fails at initial connection and reports the following error:

Not enough room in buffer for display location option reply

Can occur when you start Proviso components from a Solaris 10 system where the user interface is displayed remotely on a Windows desktop using an X Window tool like Exceed.

Cause: Length of the DISPLAY variable passed via the telnet client is too long (for example, XYZ-DA03430B70B-009034197130.example.com:0.0).User action:Set the value of the DISPLAY variable using the IP address of the local system, or the hostname only without the domain name. Then, reconnect to the Solaris 10 machine using the telnet client.

Problem Solution

Installer reports a Java Not Found error during installation of technology packs.

Cause: The installer expected, but did not find, Java executables in the path reported in the error message. The technology pack installation requires the correct path in order to function.

User action:Create a symbolic link from the reported directory to the directory on the system where the Java executables are installed, for example:

ln -s bin_path $JAVA_HOME/bin/java

where bin_path is the directory where the binaries are located.After you create the symbolic link, you must re-start the technology pack installation.



For example:

$ sqlplus system/[email protected]

3. Output like the following example indicates a successful connection:

4. Type exit at the SQL> prompt.

Testing External Procedure Call Access

In the Oracle Net configuration, you set up an Oracle listener to wait for connections using external procedure calls. The shared library libpvmextc.so executes system commands from stored Oracle procedures. This file is installed in the $ORACLE_BASE/admin/PV/lib directory (where PV is the ORACLE_SID). A symbolic link to this library file is created by the configure_db script in the $ORACLE_HOME/lib directory.

To test external procedure call access:

1. Make sure you are logged in as oracle and that the DISPLAY environment variable is set.

2. At a shell prompt, change to the following directory path:

$ cd $ORACLE_BASE/admin/skeleton/bin

3. Run the checkextc script, using the system database login name and password as a parameter:

$ ./checkextc system/password

For example:

$ ./checkextc system/manager

SQL*Plus: Release 9.2.0.8.0 - Production on <Current Date>

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:

Oracle9i Enterprise Edition Release 9.2.0.8.0 - ProductionWith the Partitioning option

JServer Release 9.2.0.8.0 - Production

SQL>



4. Output like the following example indicates a successful test.

checkextc - Checking the installation of the library libpvmextc.so

This program try to execute the following unix commands

from a PL/SQL stored procedure.

1- Check ExternalCall : echo "UNIX : Check libpvmextc.so configuration."

2- Check Version

3- Check ExternalPipe : pwd

ORACLE : Connecting to Oracle ...

ORACLE : Creating library LibExtCall ...

ORACLE : Creating function ExternalCall ...

ORACLE : Calling function ExternalCall ...

UNIX : Check libpvmextc.so configuration succeeded.

ORACLE : Creating function Version ...

ORACLE : Calling function Version ...

UNIX : Check Version libpvmextc.so - Revision: 1.0.1.1

ORACLE : Creating function ExternalPipe ...

ORACLE : Calling function ExternalPipe ...

UNIX : Check ExternalPipe - /var/opt/oracle

ORACLE : Dropping function Version ...

ORACLE : Dropping function ExternalCall ...

ORACLE : Dropping function ExternalPipe ...ORACLE : Dropping library LibExtCall ...


Index

A

addingcollector to topology 94database configurations component to topology 89DataChannel administrative components to

topology 93DataChannel to topology 93DataMart to topology 90DataView to topology 92High Availability Manager 138, 143hosts to topology 87UBA collectors 178

Advanced Properties viewabout 68

aggregation setsabout 201, 213configuring 201installing 205

AIXinstalling Netcool/Proviso

distributed environment 81support 1

application programsstarting 196

B

backup hostssee spare hosts

bouncing modified HAM components 144

C

channel manager programsstarting manually 198stop and restart 123

clustersHigh Availability Manager 127, 128ratio of primary to spare hosts 127

collector process 126collector profile 126collectors

adding to topology 94moving to a different host 119

moving to or from a HAM 121co-location rules 185components

adding to deployed topology 116changing configuration parameters 118stop and restart 144

configuration parameterschanging values 118

creating a topology 87

D

data aggregation 194, 226database configurations component

adding to topology 89DataChannel

adding to topology 93application program names 195architecture 193watchdog scripts 194

DataChannel administrative componentsadding to topology 93

DataMartadding to topology 90copyright information for tools 275

DataViewadding to topology 92linking aggregation sets to groups 210poc user 110

deletingSee uninstalling

deployed topologyadding components to 116opening 116

deployerabout 76command-line options 229node selection page 77primary versus secondary 102running 98running in silent mode 233starting 98steps page 78

deploymentmodifying the current 115


Index

designated spare 128DISPLAY environment variable

setting 9distributed environment

installing Netcool/Proviso in 81

E

error codes 243ethernet characteristics 10

F

failover 136fixed spare cluster 128floating spare 128floating spare cluster 128full duplex mode

setting 10

H

HAMsee High Availability Manager

Help menu 75High Availability Manager

about 125bouncing modified components 144clusters 127creating 138, 143examples 129failover 136modifying 144moving collectors 121removing components 144resource pools 134viewing configuration 145

hostsadding to topology 87clusters 127listed on node selection page 77primary and spare 125, 126

I

incremental installation 115example 117

installation

resuming 104setup tasks 5steps

about 78details 80properties 79status values 80

troubleshooting 261installing

Netcool/Provisodistributed 81minimal deployment 105

AIX 110Solaris 107

patches 239resuming 104

Oracle client (patch version 9.2.0.6) 58Oracle client (patch version 9.2.0.8) 47Oracle server 26technology packs 113, 171the Topology Editor 85

interim fixesinstalling 239

L

launchpadabout 62starting 83

Linuxinstalling Oracle client 47support 1

log files 259COI 259deployer 259Eclipse 259technology packs 183trace 260

Logical view 66log-to-traps feature 198

M

managed definitionsabout 126resource pools 134

maximizing views 72minimal deployment 105

AIX 110


Index

post-installation script 110Solaris 107

minimizing views 72modifying a deployed topology

adding components 116example 117

N

Netcool/Provisoarchitecture 1, 60co-location rules 185components

adding 87co-location rules 185overview 2

error codes 243fresh installation 81incremental installation 115installing

distributed environment 81fresh 81interim fixes 239minimal deployment 105modifying the current environment 115patches 239

modifying the current deployment 115pre-installation setup tasks 5prerequisite software 7remote installation

about 187supported platforms 1troubleshooting the installation 261uninstalling 150what’s new in Version 4.4.3 60

node selection pageabout 77

O

Oracleclient (patch version 9.2.0.6) 58client (patch version 9.2.0.8) 47client patch versions 7server 26

P

partial installation

resuming 104Patch versions for Oracle client software 7patches

installing 239Physical view 67poc user 110pre-installation setup tasks 5prerequisite software 7primary deployer 102primary hosts

about 125acting as backup hosts 128

Problems viewabout 70

propertieschanging values 69restoring default values 70

Properties viewabout 68changing a value 69resizing columns 69

pvusersetting 13

R

redundant collection paths 125remote installation

about 187removing

See uninstallingresource limits

setting 16resource pools 134restart Channel Manager 123restoring

default property values 70views 72

resuming a partial installation 104Run menu 74

S

SCOTTY Stackcopyright information 275

secondary deployers 102silent mode 233


Index

SNMP Collectorsevents and states 134High Availability Manager environment 125moving to a different host 119moving to or from a HAM 121starting 196

softwareprerequisite 7

Solarisinstalling Netcool/Proviso

distributed environment 81minimal deployment 107

support 1spare hosts

about 125types 128

steps pageabout 78

T

Technology Pack Installerusing 174

Technology Pack viewabout 68

technology packsadding UBA collectors 178installing 113, 171log files 183pre-installation tasks 157, 173

timezones 201, 213linking to DataView groups 210

topologyadding a collector 94adding a High Availability Manager 138, 143adding DataChannel 93adding DataMart 90adding DataView 92adding hosts 87adding Netcool/Proviso components 87adding the Database Configurations component 89adding the DataChannel Administrative

components 93creating 87opening a deployed file 116opening an existing topology file 97saving 97

Topology Editor

about 64installing 85

using silent mode 237menus 74opening 65starting 86tools 71topology.xml file 71uninstalling 152views 65

maximizing 72minimizing 72restoring 72

Topology menu 74topology.xml file

See topologytroubleshooting 261

U

UBA collectorsadding 178moving to a different host 121

uninstallingcomponents 147High Availability Manager components 144Netcool/Proviso 150

V

viewsmaximizing 72minimizing 72of the Topology Editor 65restoring 72

W

watchdog scripts 194Window menu 74

X

Xwpickcopyright information 277


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 Netcool/Proviso.

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.


Additional Copyright information

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.


281 Netcool/Proviso dbMgr Reference Guide, Version 5.2

Printed in the USA.

IBM®

Documents

Tivoli Netcool Performance Manager 1.3 IBM Wireline ... · Netcool Performance Manager 1.3 IBM Wireline Component (Netcool/Proviso 5.2 ... Chapter 4: Installing Netcool ... 134 How